Also set gradle version when doing a non-export build

Hi! We use your project successfully for exporting Android projects, thanks!
the problem
However for the newest version, the project can be exported, but it can no longer be build & run directly (meaning, running on the device directly, without a project export). I suspect the reason is that we use a quite recent version of the gradle dependency.
baseProjectTemplate.gradle:
dependencies {
    classpath 'com.android.tools.build:gradle:7.3.0'
    **BUILD_SCRIPT_DEPS**
}

unity-gradle-wrapper only runs when the project is exported. But unity seems to use the baseProjectTemplate.gradle even when not doing exports. This seems to create some kind of version conflict, where unity uses some older gradle wrapper but the baseProjectTemplate.gradle specifies a recent version.
The exact error message looks roughly like this:
> Failed to apply plugin [id 'com.android.internal.version-check']
   > Minimum supported Gradle version is 7.4. Current version is 6.1.1. If using the gradle wrapper, try editing the distributionUrl in ...\Temp\gradleOut\gradle\wrapper\gradle-wrapper.properties to gradle-7.4-all.zip

As you can see, unity does not use the version we specified in the unity-gradle-wrapper settings, which is specified to be 7.4.
any workarounds?
None that I can think of. I'm not 100% sure whether I assessed the problem correctly, though.
proposed solution
It would be nice to be able to use the gradle wrapper plugin even for quick builds. It could be implemented as an additional boolean setting, something like "run only for project exports" with a default value of true for backwards compatibility. This would offer an opt-in solution for those who need it.
details
unity-gradle-wrapper version: github master
unity version: Unity 2021.1.21f1
tried with gradle wrapper version 7.4 or 7.4.2 and build:gradle:7.3.0

Hi @johannesvollmer!
Unity's builtin Android build pipeline will use whatever version of Gradle is configured at Preferences -> External Tools (see "Customizing dependencies" here: https://docs.unity3d.com/Manual/android-sdksetup.html).
Even if we generate a Gradle Wrapper without exporting the project, Unity will not call Gradle using the gradlew script, but will rather execute something like <path to jdk>/bin/java -jar <path to gradle>/lib/gradle-launcher-<version>.jar ....
So, if you want to use Gradle 7.4 with Unity's builtin pipeline, you can download it manually, configure its path in Preferences and it should work just fine. The downside of this is that it is an Editor Preference that is shared with all projects/versions of Unity.
I'm almost certain there might be a way to automate the usage of gradlew using editor scripts for building, with the builtin BuildPipeline class or the Scriptable Build Pipeline package, but if configuring Gradle globally is enough, it's a much simpler approach.

Thank you for those hints. We'll have a closer look.
Considering that unity will not use gradlew when using build and run, you can close the issue I guess

No problem, I hope you are able to make your builds!
If you need any more help with this, feel free to reach out again =]


Point cloud .glb doesn't load in AR

Hi, I wanted to see point cloud .glb file in AR, but it is not shown in AR (although I get some response from the phone as if the object is placed). No UVs, no textures, only points.
Example of point cloud - https://sketchfab.com/3d-models/azalea-point-cloud-ed186481a6ab494b84701546a8060e61 - you can download it in gltf; I converted it to glb with gltfpack.
https://model-viewer-tester.glitch.me shows the cloud as is, as expected, without problems.

Can you please fill out the issue template you deleted? I need to know which AR mode(s) and devices this is happening with and a repro link.


Be able to delete print jobs from queue.

Once we have this feature, we'll be able to stop skipping the unit test of uploading documents because we will be able to delete the test print jobs.

I have already partially implemented this enhancement. My work can be found on the branch delete-print-jobs.
What still needs to be done is:

an API call needs to be written in api.py.
and the API needs be called in app.js. Search deleteJob in the file to see where I created a stub.

Here is the POST data to print.calvin.edu/pwrqm/dispObjects.asp

Alright, I'm gonna work on this.


[server/kit] Always adding context values to request scoped logger

Adding a blank server logger to the context was fairly worthless (and kinda dirty) as it allows users to log without any metadata.
This change automatically adds all request context metadata/headers to the logger one time when it is injected into the context and consequently removes the '*WithFields' functions for the logger as the fields are always there.

Coverage decreased (-0.7%) to 46.101% when pulling a8a96e55730a5ce855a31f6c5f6527d9692637de on kit-log-update into 6f874ffe8fdb6a09bd48c81b30e7dcd08511f972 on master.


Bump package versions to fix vulnerabilities

Fixes for:

CVE-2024-41950
CVE-2024-6345

Description
Ran Trivy on the repository and found these two vulnerabilities
Issues
n/a
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)
[x] Others (enhancement, documentation, validation, etc.)

Dependencies
n/a
Tests
n/a

Need to fix the CI issue.

Fixed in another PR.


Handle RDS password secretly

Terraform doesn't allow to connect to secret manager directly.
One option: create instance with a temp password, switch it manually to use secrets manager (aws has native support for it)

There's a way to create db password via aws cli, explore if we can chain it in our scripts:

[terraform] Create DB with temp password
[aws cli] Create DB secret with a new password (
[terraform] Use data to import DB secret and pass it to Fargate

Spent few hours reading about. You are talking about rotating database password, right? It seems quite complicated. Essentially we need to create and manage a lambda function which will do the rotation of the password (generating new password and updating it in secret manager) and then logging in postgres and changing passwords there. And it requires a bit convoluted VPC settings. I actually hasn't been able to fully make it work even from AWS web console (lambda function is timing out). Here is the terraform-specific tutorial that matches my understanding of how to do it as well: https://advancedweb.hu/how-to-set-up-amazon-rds-password-rotation-with-terraform/
Also we wouldn't need to generate new password. We generate DB credential once, with a temp password and then enable rotation. Once rotation is enabled - it will update the password for us. And maybe it will run rotation immediately as well, upon applying terraform changes.


async IO over multiprocessing lib?

Have you tried to use async IO over multiprocessing lib? I wonder if we can  improve performance by doing so. Is this something worth while to try to implement? Let me know what you think and I'll create a diff.

The only benefit I see in moving away from multiprocessing is letting you launch more than a few hundred instances at once. Since each instance is managed by its own process, you could run into issues trying use like 1000 instances or something wild that fries your processor. I can't imagine ever needing that many though...


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/922 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit fc948cc:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-06-25-04-01-00 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


I have the current workaround implemented:
from osbrain import run_nameserver
import time, sys, traceback

NAMESERVER='<IP_ADDRESS>:42422'

def main():
    defunct_agents = {}
    ns = run_nameserver(NAMESERVER)
    while True:
        for alias in ns.agents():
            try:
                agent = ns.proxy(alias)
                agent.ping()
            except:
                if alias in defunct_agents:
                    defunct_agents[alias] += 1
                else:
                    defunct_agents[alias] = 1
            for agn in list(defunct_agents):
                if defunct_agents[agn] > 4:
                    try:
                        ns.remove(agn)
                        defunct_agents.pop(agn, None)
                    except:
                        traceback.print_exc(file=sys.stdout)
        time.sleep(5)

if __name__ == '__main__':
    main()

A optional argument to ns_runserver (ns_runserver(NAMESERVER, del_defunct_agents_after_seconds=60) for example) would be great.

Thanks for opening this issue.
Although we have that in our road-map, heartbeating and monitoring will probably be left for a post-1.0.0 release. Meanwhile is up to the user to implement any tricks they need for their application. :wink:

Anyway we will probably implement better handling of SIGINT/SIGTERM for 1.0.0, though. The case in which the agent simply "dies" will still need to be handled by the user.


bump jest to 28.0.2

Context
Changes proposed in this pull request
Guidance to review

 Upgrade dependencies to the latest recommended version


Decompilation and indexing are messed-up for large apps

Currently the DecompileJob generates the background jobs for decompiling the classes and then returns.
Then the ShutdownTask is triggered which waits up to 5 minutes and then continues even if decompile jobs are still running.
If the decompilation of the remaining jobs requires more than 5 minutes Jadx is running into troubles:
This means that it starts indexing when decompilation is still running and therefore all data structures by Jadx don't cover the whole app.
Alls this is visible to the user as the progress bar disappears way too early. Even is the CPU utilization shows that decompilation is still running.
For large APKs 5 minutes is way too less. I used the Facebook app linked in #354 and was still busy processing decompile job 5077 of 104946 when the ShutdownTask finally triggered (and that was with already re-enabled multi-threaded decompilation in MainGui.resetCache() - BTW: did you set the decompilation threads to one only because of memory problems or are there real multi-threading issues in Jadx decompilation?).
Therefore I increased the wait time to 5 days which should be enough even for large apps.

@jpstotz thank you!!! I don't know why I changed that timeout from 1 hour to 5 minutes in commit  ea01102f1ddc204487a4b32f9c8ccc0a8565ead2.
About hardcoded single thread: there are was a lot of multi-threading issues like deadlocks and incorrect processing order. But for now, looks like most of them already solved, because I often use CLI version with 8 threads and don't see any issues. Anyway decompilation speed is very slow even in 8 threads, to improve this I already redone type inference algorithm (in type-inference-wip branch) but it is still not complete.
About large memory usage: there are a lot of memory leaks (decompilation data that not needed anymore) due to bad architecture. And it even worse in GUI version because it holds all generated code for search index and code viewer. I plan to refactor code for better unloading of unnecessary data, and for GUI I can disable search if index data is to big for store in memory.

:tada: This PR is included in version 0.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Meet "Failed to connect to Couchbase getBucket" exception from CouchbaseClientFactory when service starts up

Hi dear all,
This is my first time to use CAS, so the problem I've met may be a configuration issue, or it might be a known issue to you, although I tried things to understand it, I failed and cannot solve this.
I have built the CAS from WAR overlay template, and deployed it on one of my AWS host, and I have my Couchbase running on another AWS host, in the same group. I'm confident confirmed that everything relates to my Couchbase buckets access is correct(There are also some other my systems running on accessing it.) . And everything was okay when I tested the CAS and Couchbase on a same physical machine. However, after I moved the CAS to my AWS box, and configured it to connect to the Couchbase on AWS, when I tried to start my CAS with tomcat, I saw the "Failed to connect to Couchbase getBucket" exception in the log, the back trace was like below, it's too long and it's not the entire stack:

<<<<<<<<<<<<<<<<<<<<
Certainly the web page is not accessible, but I saw there was a record written into my bucket already, which is for Service Registry to use that I configured. So this is strange to me, for the record can be created in the bucket, then what does this "Failed to connect to getBucket" mean. I took a look of the code in the CouchbaseClientFactory.java(did not went through the whole logic), it just simply catches a general Exception, not a specific exception. So which line of the codes might throw such a exception?

Hello! Welcome to the project..
For support and questions, please join the relevant project mailing lists, chatroom or other support channels to ask questions.


Better fix for config flow defaults

Proposed change

A better fix for config flow defaults.
Added an additional test for config flow with missing/incomplete data.
Update config flow text to specify the minimum values for "imap timeout" and "scan interval".
Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[x] Code quality improvements to existing code or addition of tests
[ ] Documentation update
[ ] Adds a new shipper
[ ] Update existing shipper

Additional information

This PR fixes or closes issue: fixes #375

Codecov Report

Merging #385 (4a0ce42) into dev (624a875) will increase coverage by 0.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #385      +/-   ##
==========================================
+ Coverage   96.94%   97.05%   +0.10%
==========================================
  Files           5        5
  Lines         983      984       +1
==========================================
+ Hits          953      955       +2
+ Misses         30       29       -1

Impacted Files
Coverage Δ

custom_components/mail_and_packages/config_flow.py
100.00% <100.00%> (ø)

custom_components/mail_and_packages/__init__.py
96.47% <0.00%> (+1.17%)
:arrow_up:


feat: Implement footer component

The simple footer will not stick to the bottom until this pr is merged


Update optional-output.md

Noticed that the workflow block was missing.

Also, I'm thinking that perhaps we should remove the Run it sections are they are no longer relevant after the #29 merge - thoughts?


asdf.show_in_notebook() ?

I find the Astropy table default rendering in notebooks to be quite nice. The show_in_notebook() rendering is even nicer, and interactive. The astropy code for doing this could form a good basis for an asdf show_in_notebook() interactive viewer.
I took a look at the datatables javascript library, and it does have some support for hierarchical data structures, so might form a basis for a similar viewer for asdf headers. It's unclear to me how well this might work once the tree gets several levels deep.
I also found Tabulator, which seems to have a bit more support for nested data structures in their examples. The examples also discuss including graphics and making fields editable. Looks quite promising to me.
Both datatables and tabulator are MIT licensed.

Having a nice notebook rendering for ASDF files would be awesome.
What do you think about building a simple Jupyter(Lab)-Extension that outputs similar to
https://github.com/jupyter-attic/jupyterlab_json
https://github.com/QuantStack/ipytree ?


Proposal - Request#readResponseBody

There's a cool piece of code here that one could benefit from if it were extracted and exposed as a function of Request#prototype... :)
If I find some time to do it I'll definitely enjoy contributing. In the meantime I'm just dropping those lines for any feedback.

I agree :+1:

What about that?

Closed via #1818


Allowed characters in labels/keys

https://docs.google.com/document/d/1HFUkAEE-pB-angVcYe6pf_-fVf4sCpOHKesUvfb8Grc/edit?disco=AAAAB1zsEbg
Some labels that are desired to be used consist of concatenated abbreviations, and would be more readable with a separator character (e.g., "32k-fs-LR"). This restriction seems excessive.
One possibility is to actually allow dashes in values, while keeping them forbidden in keys. This can still be parsed consistently by splitting everything on underscores, and then splitting each of those on the first dash.
If this is unpalatable, perhaps another cross-platform-allowed filename character can be added to the set of allowed characters, such as '=' or '+'. These are not as easy to read as a dash, but at least gives people an option for cases that are otherwise difficult to resolve.

Original authors: Unknown

This is related to https://github.com/bids-standard/bids-specification/issues/226 and #7.

I disagree with allowing dashes only "sometimes" and thus giving them multiple possible meanings. It ultimately means more difficulty in writing parsers.

I would like to bring this back to "agenda" and do make - and + allowed.  We are not to give any semantic, but rather just to allow file names to be more readable.  For implementing support, it should be quite trivial since it doesn't add any ambiguity to parsers: split on _ into entities + optionally a suffix, and then split entities on - to separate key from value.  The only possible difficulty is may be for regex based parsing.


Never stops loading

Hi,
For some reason it never stops loading. Perhaps it is broken?

Same for me! It states that it fails to log and returns code 0.

Maybe or not. There is no official API for GoogleShopping List, so I should use crawling.  Google sometimes change their site structure for A/B test or any reason I cannot understand. Unfortunately unless the change be applied to all user, I cannot fix it. Sorry.

Hi,
I'm new on github and on Rpi ...
I a installing Rpi to make the Magic Mirror and I would like to install Google Shopping List but I have the same problem ... It's installed and when I launch (npm start) I see the interface with the "Loading" but no more ...
Can you help me ?
Thank you !

Sorry, This module is not stable for all environments. Some could not get a result, but cannot solve. This module is experimental so can't help.

Ok thank you for your answer !


Entities with multiple observers do not function correctly

While you can technically make the entity itself an observer you can't do that multiple times as the ObserverState component would get overridden leading to serious issues. If that was exposed in bundles users could easily accidentally break things by inserting different bundles that each have observers.

Originally posted by @james-j-obrien in https://github.com/bevyengine/bevy/issues/14204#issuecomment-2212515944

This is a pretty serious footgun / caveat. I'd prefer to eliminate this, but failing that, clear docs about this limitation would be helpful.

For what it's worth I would consider it very confusing if multiple observers could be associated with one entity.
It is equivalent to having an ID that maps to multiple systems or queries (after those are entities).
The most straightforward approach to support multiple is to give the state generics so they are different component IDs. This would make observers difficult to handle in type-erased/dynamic environments i.e. would I be able to create multiple observers on an entity for an event with a dynamic id? Or even just two observers with the same signature? Probably not since the states would still conflict, we would still have a footgun, just a more arbitrary one. Scripting scenarios may face trouble with this.
The alternative would be to add complexity to the existing state so it can act as multiple, which I think would be overkill for a feature that is used in the minority of cases.
This limitation should be well documented, but even ignoring the above complications I think it's idiomatic to have a 1-to-1 id to observer mapping.


CLI tool for managing JupyterLab extensions

This pull request introduces a CLI (Command Line Interface) tool for managing JupyterLab extensions, designed to enhance developer workflow. The CLI tool, named jupyterlab-builder, provides commands for developing, building, and watching JupyterLab extensions. It leverages the traitlets library for configuration and flexibility.
Key Features:
Develop Command: Allows developers to set up a development environment for lab extensions, facilitating iterative development and testing.
Build Command: Provides a command for building lab extensions, enabling packaging and distribution.
Watch Command: Enables developers to watch lab extensions for changes and automatically rebuild them, improving productivity during development.
BaseExtensionApp: Implements the core logic for parsing commands and delegating them to appropriate subcommands (DevelopLabExtensionApp, BuildLabExtensionApp, WatchLabExtensionApp).
Usage of Traitlets: Utilizes the traitlets library for defining configuration options and managing application state, ensuring flexibility and ease of customization.

Hi @fcollonval I have rebased my code on your #2 commit. I have also extracted the methods and classes being used in the federated_extensions.py file. ie
from jupyter_core.paths import ENV_JUPYTER_PATH, SYSTEM_JUPYTER_PATH, jupyter_data_dir
from jupyter_core.utils import ensure_dir_exists
from jupyter_server.extension.serverextension import ArgumentConflict
from jupyterlab_server.config import get_federated_extensions
I will now move on to extracting code used in these imports
from jupyterlab.labapp import LabApp
from jupyterlab.commands import build as per your comments above.
Please let me know if I did this correctly.

Thanks a lot @cronan03
I realize my review comments was not specific enough. It is ok to depend on jupyter_core and jupyter_server. The only we should not depend on are jupyterlab and jupyterlab_server. Sorry about that as it made you copy to much code in this PR.

If you want to check the imported code, you can also import here the tests for that part of the code. They are located in the file: https://github.com/jupyterlab/jupyterlab/blob/6152e3a5f94d728ccd2727d6d8413f12ddafb669/jupyterlab/tests/test_jupyterlab.py#L156


Epic: Improve Namespace Filtering

Opening per discussion - Some UX design issues are related to each other, so we should track them as part of a project for the sake of a consistent design.
Filtering:

[ ] https://github.com/rancher/dashboard/issues/6318
[ ] https://github.com/rancher/dashboard/issues/6321
[x] https://github.com/rancher/dashboard/issues/6322
[x] https://github.com/rancher/dashboard/issues/6414
[ ] https://github.com/rancher/dashboard/issues/4469
[x] https://github.com/rancher/dashboard/issues/6414
[ ] https://github.com/rancher/dashboard/issues/6415

Redefining this to limit the scope

Closing this epic


[MB-3940] Event trigger patchMTOShipmentStatus

Description
Added the trigger for patchMTOShipment Status, and added tests.
Setup
You can test in the UI!

Login as a TOO in the office app, locally
After login, click on any moves marked as unsubmitted
Select a shipment and a service item on the move details page
Click on Approve selected shipments
Click on Approve and send button

References

[ MB-3940 Push Enable: Prime can receive MTO shipment status change notification - Jira](https://dp3.atlassian.net/browse/MB-3940) for this change
How to Add an Event Trigger · transcom/mymove Wiki

Messages

:book:
:link: MB-3940

  Generated by :no_entry_sign: dangerJS against 2f38a632c8c58a0c6780da06a5c19cc70bb984e6


error looking up service account serviceaccount not found

my k8s version is v1.23.6,I used kube-prometheus version v0.10.0.
When I used the following command, the following issue occurred.
kubectl apply --server-side -f manifests/setup
kubectl apply -f manifests/

monitoring      blackbox-exporter-6b79c4588b-hxhp8         0/3     Pending     0             7m50s
monitoring      grafana-7fd69887fb-fqf87                   0/1     Pending     0             7m49s
monitoring      kube-state-metrics-55f67795cd-drlp6        0/3     Pending     0             7m49s
monitoring      node-exporter-4969t                        0/2     Pending     0             7m49s
monitoring      node-exporter-kvvxz                        0/2     Pending     0             7m49s
monitoring      node-exporter-n7gbx                        0/2     Pending     0             7m49s
monitoring      prometheus-adapter-5565cc8d76-nbhwd        0/1     Pending     0             7m49s
monitoring      prometheus-adapter-5565cc8d76-vwh4k        0/1     Pending     0             7m49s
monitoring      prometheus-operator-6dc9f66cb7-cr76n       0/2     Pending     0             7m49s
root@master01:~/prometheus/test2/kube-prometheus-release-0.10# kubectl get events -n monitoring
LAST SEEN   TYPE      REASON              OBJECT                                      MESSAGE
105s        Normal    NoPods              poddisruptionbudget/alertmanager-main       No matching pods found
8m57s       Normal    SuccessfulCreate    replicaset/blackbox-exporter-6b79c4588b     Created pod: blackbox-exporter-6b79c4588b-hxhp8
8m57s       Normal    ScalingReplicaSet   deployment/blackbox-exporter                Scaled up replica set blackbox-exporter-6b79c4588b to 1
8m56s       Normal    SuccessfulCreate    replicaset/grafana-7fd69887fb               Created pod: grafana-7fd69887fb-fqf87
8m56s       Normal    ScalingReplicaSet   deployment/grafana                          Scaled up replica set grafana-7fd69887fb to 1
8m56s       Warning   FailedCreate        replicaset/kube-state-metrics-55f67795cd    Error creating: pods "kube-state-metrics-55f67795cd-" is forbidden: error looking up service account monitoring/kube-state-metrics: serviceaccount "kube-state-metrics" not found
8m56s       Normal    SuccessfulCreate    replicaset/kube-state-metrics-55f67795cd    Created pod: kube-state-metrics-55f67795cd-drlp6
8m56s       Normal    ScalingReplicaSet   deployment/kube-state-metrics               Scaled up replica set kube-state-metrics-55f67795cd to 1
8m56s       Warning   FailedCreate        daemonset/node-exporter                     Error creating: pods "node-exporter-" is forbidden: error looking up service account monitoring/node-exporter: serviceaccount "node-exporter" not found
8m56s       Normal    SuccessfulCreate    daemonset/node-exporter                     Created pod: node-exporter-kvvxz
8m56s       Normal    SuccessfulCreate    daemonset/node-exporter                     Created pod: node-exporter-n7gbx
8m56s       Normal    SuccessfulCreate    daemonset/node-exporter                     Created pod: node-exporter-4969t
8m56s       Warning   FailedCreate        replicaset/prometheus-adapter-5565cc8d76    Error creating: pods "prometheus-adapter-5565cc8d76-" is forbidden: error looking up service account monitoring/prometheus-adapter: serviceaccount "prometheus-adapter" not found
8m56s       Normal    SuccessfulCreate    replicaset/prometheus-adapter-5565cc8d76    Created pod: prometheus-adapter-5565cc8d76-nbhwd
8m56s       Normal    SuccessfulCreate    replicaset/prometheus-adapter-5565cc8d76    Created pod: prometheus-adapter-5565cc8d76-vwh4k
8m56s       Normal    NoPods              poddisruptionbudget/prometheus-adapter      No matching pods found
8m56s       Normal    ScalingReplicaSet   deployment/prometheus-adapter               Scaled up replica set prometheus-adapter-5565cc8d76 to 2
104s        Normal    NoPods              poddisruptionbudget/prometheus-k8s          No matching pods found
8m56s       Warning   FailedCreate        replicaset/prometheus-operator-6dc9f66cb7   Error creating: pods "prometheus-operator-6dc9f66cb7-" is forbidden: error looking up service account monitoring/prometheus-operator: serviceaccount "prometheus-operator" not found
8m56s       Normal    SuccessfulCreate    replicaset/prometheus-operator-6dc9f66cb7   Created pod: prometheus-operator-6dc9f66cb7-cr76n
8m56s       Normal    ScalingReplicaSet   deployment/prometheus-operator              Scaled up replica set prometheus-operator-6dc9f66cb7 to 1

。


Page edit: rendering

Make sure that when you render the second page to edit, the first page's content doesn't appear.

unable to replicate. closing.


Add Husky for precommit hooks

Some tasks are starting to get tedious and would benefit from automation
To allow us to work better can we have an ESLint and Prettier precommit hook ?
Will add more specifications later.

This issue is resolved in this pull request


Stop assuming that Tor will download a consensus flavour that contains exit policies

We spend a lot of time messing with tor options to make sure it has a consensus flavour that contains an exit policy. Instead, let's just look for the exit policy in the consensus, and if it isn't there, in the microdescriptors.
This will save us from a whole lot of future bugs where people deploy with the wrong torrc options.
For details, see:
https://trac.torproject.org/projects/tor/ticket/25979#comment:4

Thank you for helping investigate, @teor2345.
Sbws scanners will be launching their own Tor processes soon, but this is still very good info for telling me exactly what torrc options are needed.


[doc](partial update) add complete doc for partial update

Proposed changes
Issue Number: close #xxx
add complete doc for partial update
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


EF Core Add-Migration not detecting DbContext for multilevel hierarchy class inheritance

Declared an AppDbContext class inheriting from DbContext  as below in a seperate project
namespace Smarware.Lib
{
    public partial class AppDbContext : DbContext
    {
    }
}

The I've a separate project referencing the Smartware.Lib project to inherit AppContext
namespace WebApp
{
    public class MyMainDbContext: AppDbContext
    {
    }
}

When I run EF Add-migration command
No DbContext was found in assembly 'WebApp'. Ensure that you're using the correct assembly and that the type is neither abstract nor generic.

But when I try to  Inherit directly from DbContext it works fine, like this
namespace WebApp
{
public class MyMainDbContext: DbContext
{
}
}
Which won't work in my case.
This was very possible with EF 6
Further technical details
EF Core 1.1.1
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows
IDE: Visual Studio 2017

How are you registering your context in service provider?

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


fix (#patch); Euler-finance-ethereum; fixed inaccurate TVL/borrow balance #1869

This PR fixes inaccurate TVL/borrow balance (#1869) due to the euler hack on 2023/03/13
deployment + dashboard (sync in progress)

deployment: https://thegraph.com/hosted-service/subgraph/tnkrxyz/euler-finance-ethereum?version=pending&selected=logs
dashboard: https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/id/QmaxeJ3MbMPQEoHuuV54jMQn4zUa57d5xW4nZNKhLPPg4A&tab=protocol

QA pass


Updates to the Command API to support implementation

The big thing here is the addition of a "CommandRegistrar". This is meant to be a lightweight interface that tries to give external command frameworks (Aikar's ACF, Katrix's Scammander, Faith's Butler, amongst others) a simple way to add their commands to Sponge. The idea of registrars was originally an implementation one - if you look at that code, you'll see that the vanilla brig system is separated from the Sponge one - it takes little work to add support for arbitary registrars, so why not add them?
The Javadocs should provide a fair amount of explanation. There will be more for client completions, I'm sure - though enabling that is the thing that is missing right now. That'll come later - it'll likely mimic Brig's suggestion provider with a tree like format to build the command elements up with.
This is simply for review of code style and Javadocs.

So effectively, CommandRegistrar is similar to a Dispatcher + CatalogType?

I guess, though it doesn't really need to be a dispatcher so much. A registrar could conceivebly be a command executor - I don't put a restriction on it.
Note that there are a couple of classes that don't have JDs. That's a mistake on my part, some API elements have made it through that were nowhere near ready. I won't be merging tonight as it is, so pick on anything and I'll review over the next couple of days.


Fixes #883 - Generate vFlow records for edge links.

Codecov Report
Base: 27.56% // Head: 27.55% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (aae11da) compared to base (185aafa).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #884      +/-   ##
==========================================
- Coverage   27.56%   27.55%   -0.01%
==========================================
  Files         136      136
  Lines       32491    32501      +10
  Branches     5214     5214
==========================================
  Hits         8956     8956
- Misses      22385    22395      +10
  Partials     1150     1150

Flag
Coverage Δ

unittests
27.55% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

...uter_core/modules/edge_router/connection_manager.c
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Option to mark episode as finished

Clear and concise description of the problem
Add an option to mark an episode as finished.
Suggested solution
The button could be placed next to "download podcast" on the podcast overview page.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Added. There is now a button that marks an episode as already listened to.


feat: atomic @sentry/utils used only with submodule imports

Move jest.config.js into package.json so we can use rimraf in utils
Fix all @sentry/utils imports to use submodule imports
Fix tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@50d0005). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff            @@
##             master   #1413   +/-   ##
========================================
  Coverage          ?   85.1%
========================================
  Files             ?      32
  Lines             ?     779
  Branches          ?     127
========================================
  Hits              ?     663
  Misses            ?     110
  Partials          ?       6

Impacted Files
Coverage Δ

packages/node/src/integrations/console.ts
94.44% <100%> (ø)

packages/node/src/integrations/http.ts
54.9% <100%> (ø)

packages/core/src/base.ts
96.51% <100%> (ø)

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 50d0005...75820e0. Read the comment docs.


[Exploration] Increase contrast of helper text

Although helper text currently passes AA contrast ratio requirements it is somewhat light, particularly when placed in a form context on top of Gray 5. We can increase the contrast by making the gray darker while will providing the visual distinction that we are seeking for this text. The enhancement I propose here is to update inline helper, block helper, placeholder, and disabled field text to Dark Gray (#43484e) - basically any text that we present on a Gray 05 or Gray 10 background.
Current behavior

Inline helper, block helper, placeholder text, and disabled field text
Avenir Next Regular, 16 px, Gray (#5a5d61)

Proposed behavior

Inline helper, block helper, placeholder text, and disabled field text
Avenir Next Regular, 16 px, Dark Gray (#43484e)

Screenshots

Current
Proposed

Proposed changes

Update color for inline helper, block helper, placeholder text, and disabled field text to Dark Gray (#43484e)

Moving to the Design System for maximum visibility and awareness: https://github.com/cfpb/design-system/issues/1702


Feature/distance sensor

Create 2m distance sensor module and sample.

The code matches the reference as close as reasonable. We may want to remove some extra methods we don't use from the reference.


Process Explorer: crashes when decoding handle's access mask

Crashes when decoding handle's (Process and Thread) access mask 0x1F3FFF.
To reproduce the bug, open handles view of Windows PowerShell (not Core).

Do you have any Unicode characters in any of the handles? Do you manage to have a glimpse at the view (works here)?

I managed to repro! Thanks for the report!


Support multiple namespaces or all-namespaces.

Would be ideal to support multiple namespaces or all-namespaces.

Fixed with https://github.com/wercker/stern/pull/29


CORE-6791: Simulator API KDocs

Necessary build changes should be covered in https://github.com/corda/corda-runtime-os/pull/2171 once merged.
Doc changes also made in https://github.com/corda/corda-runtime-os/pull/2168 (approved by BLT, but should Docs also review?)
This one can probably be closed off?


Another problem with maxfontsize - and minfontsize

Hey there,
I'm having a problem using the the max and min font size settings: that is, when I set those options, every span is set to either the max or the min font size and nothing in between. If I don't set those options, font sizes are variable and set appropriately and as expected (though too big for my needs). This replicates with default and custom fonts and regardless of when BigText is called.
It appears the issue is with this bit of code:
    if(newFontSize + j*intervals[m] > maxFontSize) {
        newFontSize = maxFontSize;
        break outer;
    }

This same code seems to be problematic in this issue as well - https://github.com/zachleat/BigText/issues/62 - and, similarly, commenting out these lines resolves my issue.
Thoughts on a better solution or why this behavior is occuring are welcome!
Thanks

Can you link to a test case? Or create one on jsbin/jsfiddle? Thanks!

I've had the same issue, using Bigtext with no parameters set the plugin works fine, however when those parameters are set the plugin shows min or max font size and nothing in between.
No parameters:
http://www.hamiltonislandluxuryhomes.com.au/property/yacht-club-villa-1/
With parameters:
http://www.hamiltonislandluxuryhomes.com.au/property/yacht-club-villa-1/?testing=true
I need the parameters to work othersie the text blows out in size in some cases and looks bad.
Thanks in advance!

Using v0.1.8 I get the same problem - Text always shows up outside its container, unless it is too big, and on resize it will resize assuming the text's width is the one of its container, which is overflowing.


Dependencies of notifiers are fixed.

First, thanks for the package. It is very intuitive and works like a charm! 👍
Describe the bug
If I install notifiers, it checks whether the dependencies in requirements.txt are met. Unfortunately, I run into the same issue as #191 which I cannot circumvent within tox with the stated pip command.
Is it possible to relax the dependencies? In the requirement file it is stated that the dependency comes via requests, but then you could let requests handle it and just refer to a version of requests which works for you (better a certain range). Also, even requests is not that strict regarding certifi (see here).
Or is there another reason for you to pin certifiy?
Additional context
Python version: 3.6, 3.7
OS: Windows, Linux, MacOS

Thanks for your issue. I actually solved this via #209 which isn't merged to master yet, but it's in the next release.


Support server-side rendering with PropTypes.instanceOf()

Fixes #83

@maraisr I'll publish 7.0.1 if you're good with this.

@maraisr Thanks for the review! 😄


Really outdated documentation

Could you update this documentation. And is there any plans to make integration with view and VS better? If I am not referencing a view, and instead looking at the entire feed, I would like the prerelease checkbox to work. So if there is a way to tag the view as a prerelease view in AzureDevOps, and VS will read that tag to know it is a prerelease, that would be nice. I know it would also require changes in Nuget restore and other tasks. But right now SemVer seems like a better way to separate packages, even though it is immutable.

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

ID: 5b254809-bcfe-5859-42e1-05df82aa730b
Version Independent ID: cd8e1d01-c11b-4173-8f36-95d4237bc6a5
Content: Communicate package quality with release views
Content Source: docs/artifacts/feeds/views.md
Product: devops
GitHub Login: @elbatk
Microsoft Alias: elbatk

I think this relates to their comment on using the -prerelease argument for metadata information, and that they plan on improving this experience.
https://docs.microsoft.com/en-us/azure/devops/artifacts/feeds/views?view=azure-devops#what-about-semver-and--prerelease
Although, that line was added 2 years ago, so who knows when they're getting around to it.
https://github.com/MicrosoftDocs/vsts-docs/commit/4556acf9e8cf39ddb670877dd0f608237dba9c17#diff-6a59095de830655e06c88cf702e9de26R4

Link to uservoice does no work.
I also would like checkbox in VS to work.
Right now I use VersionSuffix to add pre suffix, but when I promote package to Release view I'd like that suffix to get released. This way I could build a single package and move the exact same package to proper view - without the need to recompile everything

@stoopered Thank you for your feedback. The updated article is live now Here.
If you have new feature suggestion please use the "Suggest a feature" link in our Azure DevOps Developer Community


C++ api documentation

Where I can find documetation/samples for c++ api?
I want run model with plaidml backend from c++ project.

https://www.ngraph.ai/documentation/core/constructing-graphs (might be stale in places)
Plus the tests directory.
Everything is geared towards programs that translate graphs from a framework to nGraph, rather than people constructing graphs directly.


Replace FUNCerr with ERR_raise_data

Now that #9452 has been merged, let's replace all FUNCerr calls with ``ERR_raise_data```
No compatibility is needed since ERRfunc() was only in master.

Is "fixing" this really necessary?  It is broken if a string contains an embedded quote, for example.  I prefer to just leave things as they are without quotes, and without trying to look like a real function call.  Is that okay?

In some of the cases I pointed out, there were (single) quotes in the original added data. You could at least restore that.

This is for an error message, and it's not going to be a function call, and at least now everything is  consistent.  Putting single quotes in some places, double-quotes in others -- as the original collection of calls had -- will look wonky and confusing.
I really really really don't want to do that.  This is not a function call, this is not showing gdb output, etc.

It's about making things readable for humans.
XXXXXXXX:error:system library::Permission denied:yada.c:42:fopen(/foo/bar/something,0700)

vs
XXXXXXXX:error:system library::Permission denied:yada.c:42:fopen('/foo/bar/something',0700)

Those quotes are visual cues.
(there were no double quotes in the things you changed, BTW)

I was wrong and you were right: everything was single quotes.
I don't find the clues compelling.  Do you want them:

For fstat(%s) -- there's only one arg, the clue seems needless
For fopen(%s %s) -- there are two args; so what is the purpose of the quote, to make the args more easily separable?
For connect(%s %s) -- this isn't a function call

Feel free to take over this PR.

Merged.
ff988500c2f39ae61b2836167b6e0e7b2021220c Replace FUNCerr with ERR_raise_data


ARROW-7506: [Java] JMH benchmarks should be called from main methods

Some benchmarks are called as unit tests in our current code base. They should be called from main methods, because:

This is the recommended way of writing JMH benchmarks. The automatically generated benchmarks are called from main, and sample benchmarks provided by JMH [1] are also called from main.

Some compiler does not support calling JMH as unit test. For example, the "javac with error prone" reports the following error:

Error:(100, 15) java: [JUnit4TearDownNotRun] tearDown() method will not be run; please add JUnit's @After annotation
(see https://errorprone.info/bugpattern/JUnit4TearDownNotRun)
Did you mean '@After'?

When run as a unit test, enable assert flag will be turned on by default, so some test/debug operations will be performed. This will distort the benchmark result data. For example, a related discussion can be found in [2].

[1] https://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/main/java/org/openjdk/jmh/samples/
[2] https://github.com/apache/arrow/pull/5842#issuecomment-558082914

+1, LGTM.  rerunning failed checks and can be merged on green.


v1.22.0 Test Plan (in progress)

It's testing time again here in the DDEV factory. We love community help with every item that is interesting or relevant to you, and just using the release candidates is hugely helpful, because you may stumble across something in your regular workflow. Please use DDEV HEAD for your testing (or brew unlink ddev && brew install --HEAD --fetch-head ddev/ddev/ddev) or other techniques at Testing Latest Commits.
I don't think in general you'll have trouble using this in your daily workflow, so would love you do do that. You can switch back and forth , see How can I install a specific version of DDEV in the FAQ.
If you find a bug that you're pretty sure is a bug, then just open an issue for it.
To give feedback or ask questions, please just reply on this issue or discuss in discord or any other support channel.
I am maintaining the provisional release notes for v1.22.0 and would love any comments on those.
See commits since v1.21.6 and PRs merged since March 10, 2023

Make sure that the DDEV PhpStorm Extension is working fine - There's a docker-compose bug about COMPOSE_PROJECT_NAME that might affect our current usage of compose 2.18.1 (and 2.19.0 doesn't seem to pass DDEV tests):

[ ] Test Xdebug
[ ]  PhpUnit tests.

Verify that upgrading a project from v1.21.6 to v1.22.0 works OK. Especially test with mutagen enabled. It will definitely show recreation of a new mutagen session.
PhpMyAdmin/dba removal:

[ ] Make sure no phpmyadmin images are downloaded or containers are run when using DDEV
[ ] ddev launch -p should give a helpful tip about the phpstorm add-on.

Gitpod: Ordinary manual testing
Codespaces: Ordinary manual testing
Make sure that a v1.21.6 traefik user upgrade to v1.22.0 works OK, with no failed build problems (in build cache)
Multiple upload_dirs:

[ ] ddev config --upload-dir should work as in the past, with deprecation warning
[ ] ddev config --docroot=web --upload-dirs=one,two,../private should result in 3 upload_dirs in config.yaml; with mutagen all three should be bind-mounted. (ddev ssh df -T <mountdir> should show bind-mount)
[ ] Check especially ddev config --upload-dirs=cpresources --docroot=web and ddev config --upload-dir=cpresources --docroot=web with craft install, see https://github.com/ddev/ddev/issues/5076

Verify amplitude behavior. We should be seeing reasonable amplitude data coming in on production.
Mutagen should be enabled by default on macOS and Windows.

[ ] Verify that it is enabled globally by default
[ ] Verify that it can be turned off per project
[ ] Verify that it can be disabled globally
[ ] Verify that NFS can be enabled globally

ddev import-db and ddev export-db should prefer --file rather than --src, but --src should still work.

@deviantintegral sorry, I think something might have changed about sharing out of notion, here you go, https://randyfay.notion.site/v1-22-0-Release-notes-0e9d1254f2c04281b4d1f7c6c35ac764
@gilbertsoft we should consider restoring --use-traefik and --mutagen-enabled either as no-ops or something. @deviantintegral an issue with the specific things that worry you would be great, thanks!

I had to update tests to || true configuring traefik to pass on both 1.21 and HEAD: https://github.com/deviantintegral/ddev-playwright/pull/4/files#diff-a2bb1b04da80b87de17520a6aac3664b1cafdec2b6431697f15968522708a47cR28-R29
As well, on a project we have ddev config global --use-traefik in the README to support KasmVNC.

@deviantintegral added to

https://github.com/ddev/ddev/issues/5095

I tried version v1.22.0-beta3 and noticed that the command ddev start does not work if the dba service is in the omit_containers setting. This can be disturbing for several users that are used to use DDEV as-it-is and they will have to do changes in the configuration.
Can this be replaced with just a warning and really make it enforced in a later DDEV version?

Thanks for testing @agviu! - This was fixed yesterday in

https://github.com/ddev/ddev/pull/5109 and will be in the next beta. It's also discussed right above here :)

PhpStorm integration
✅  XDebug integration worked perfectly OOTB, nothing required at all
👎  I wasn't able to get PhpUnit or (any remote execution) working using WSL2 on Windows (PhpStorm on Windows side, docker-ce). I'm not actually sure PhpStorm knows how to do this at all. It tries to use docker-compose on the WIndows side, etc.
upgrading a project from v1.21.6 to v1.22.0
PhpMyAdmin/dba removal:
Gitpod usage
Codespaces usage
Multiple upload_dirs

Encountered https://github.com/ddev/ddev/issues/5168 in testing, fixed in https://github.com/ddev/ddev/pull/5175

I think this is all done. We can release on Monday if no problems show up.


[WFCORE-3563] Could not enable application deployment on two server g…

…roups in domain
WFCORE: https://issues.jboss.org/browse/WFCORE-3563

@jfdenise please approve


Split up notification emails by type

The success banner appears after the submit button has been pressed even if no settings have been changed. Is that correct?

That is correct - the alternative is to bother users with an error that they never changed a thing.

The success banner appears after the submit button has been pressed even if no settings have been changed. Is that correct?

That is correct - the alternative is to bother users with an error that they never changed a thing.


Atlas url not shareable and refresh redirects back to an empty atlas tree

I you try to share a url, refresh the page or reopen a window it will redirect back to an empty tree. It would be nice if it could rebuild the tree from the url.

Resolved in an update yesterday.


Lower bits per weight

In the readme you mention

In my tests, this scheme allows Llama2 70B to run on a single 24 GB GPU with a 2048-token context, producing coherent and mostly stable output with 2.55 bits per weight. 13B models run at 2.65 bits within 8 GB of VRAM, although currently none of them uses GQA which effectively limits the context size to 2048. In either case it's unlikely that the model will fit alongside a desktop environment. For now.

Have you done any testing with slightly lower bits per weight, so as to fit it alongside a DE? Have you found any breaking point where the model becomes incoherent or the degradation is just too much?

I've been working on it. I definitely consider it a milestone to get 70B running comfortably in 24 GB for 3090/4090 users with a single GPU. And it's close, but it's also slow progress, since quantizing a model that big can take several hours, and you'll end up doing it many times over trying out various different things.
The difference in perplexity between 2.5 and 2.55 bits is huge, but 2.5 is still coherent and gives an extra 350 MB of headroom or so. Although, at 2.5 bits the model does start to freak out whenever it sees the word "Auchtermuchty". And 2.5 bits still isn't quite small enough, anyway. But I have some ideas I'm going to be trying out soon, so stay tuned.

Awesome. Great work.
An idea (that you've probably already considered) is doing a small pruning (5% - 10%) before the quantization. And if the pruning targets outlier weights maybe it could also help with later quantization errors.

@IgnacioFDM One possibility for longer context/desktop experience is with nvidia's shared memory with recent windows drivers. But that sucks

I've been doing more quants and I'm currently uploading new versions of 70B-chat, down to 2.3 bits per weight. At that size you can fit a 4k context on a 24 GB alongside a desktop environment just barely, or you can go down to 2k context for a little more headroom. Here it is running on my 4090 alongside a desktop environment, with lots of other running at the same time:

Awesome. I'll give it a try later. Is this the same method as before but with a 2.3 setting, or does it contain new improvements?

Well, the new models are currently uploading and it looks like it will take a while... zz...
But once they're done, it's a new quant with the same method, I've just added a bunch more variants to the measurement pass, added some safeguards in the quantizer to prevent FP16 overflows in places, added sharding, improved precision in the kernels, and more. The old models are still compatible, the new ones are just better, hence why it works down to 2.3 bits now. There's also flash-attn support and more.

Is it feasible to make an even smaller BPW option for layers? I think right now the lowest is ~2.17bpw, which leaves barely any wiggle room for the optimizer at these levels. At a target of 2.3, there's very few "free bits" to allocate to the most important layers.
I can't believe I'm seriously contemplating 1bit, but who knows? Perhaps it's starting to blur between pruning and quantization at that point, but sacrifices might need to be made.

Problem with going below 2 bits is that with a "simple" quantization scheme is that then you're at a single bit, and you've only got two points on the quantization grid. And you lose a lot if you can't represent "positive", "negative" and "zero" within the same group.
I did try early on using quantized low-rank approximations, going effectively well below 1 bit per weight. But while it works for a few layers, those are also layers that already quantize very easily to 2 bits, so there isn't much to gain from it, while there's a lot of added complexity and potential problems (judging the actual damage caused by quantization or any other related technique is non-trivial.)
I have other ideas for novel compression/quantization schemes that I hope to have some time to experiment with soon, but there is a limit to how far you can realistically expect to get without compute-heavy techniques like distillation.

Did you manage to upload the model? I don't see it in your HF, maybe you left it as private?

It is uploaded now, finally. Here

It's hard to say. It may be a problem with ooba or an old version of the quant. Could be weird sampling parameters as well, hard to say from just one screenshot. The model can definitely produce coherent text:

I guess I'll need to do some work testing it on TGW.. hm.

thanks !
maybe it's an issue with ooba.

I've been experimenting a bit, and ooba seems to work with the 2.5-bit quant of the Llama2-70B base model. I've seen that exact output from the screenshot above ("Cord Cord StringBuilder...") and it seems to happen only with some particular finetuned models, and only when they are prompted with BOS at the start of the sequence.

@turboderp Thank you, disabling that in Parameter settings has fixed that.

@BarfingLemurs hey, what setting is it ? i cannot find it.


Slideable button

A button is a slideable button with the style "f_slide"

https://github.com/sibvisions/flutter_jvx/commit/5223881bd0593f409187e312c498d52cbabe7714


Use Community Toolkit's ObservableValidator as the base class for Screen

Screen derives from ObservableValidator.
Replace SetAndNotify with SetProperty.
Remove PropertyChangedDispatcher.
Remove PropertyChangedBase and use ObservableObject in its place.
Remove ValidatingModelBase.
Remove IValidationAdapter.
Remove IModelValidator.
Fix up tests.
Remove .NET 4.5.2, dotnet 3.0, and dotnet 3.1 target frameworks.
Add .NET 4.6.2, dotnet 6, and dotnet 8 target frameworks required for Community Toolkit.

See #396 for discussion.

Pinging this PR as it has been a while and I have a use case for this :) Thanks!

Sorry, I haven't had much time. Hopefully soon!


Upgrade does not remove old validatingwebhookconfiguration

Bug Description
If we upgrade from 1.10.2 to 1.11.2 a new validating webhook configuration is created but the old one is not removed.
Steps to reproduce:
kind create cluster
istioctl_1.10.2 install
kubectl get validatingwebhookconfigurations # shows istiod-istio-system
istioctl_1.11.2 upgrade
kubectl get validatingwebhookconfigurations # shows istiod-istio-system istio-validator-istio-system

If we directly install 1.11 there is only istio-validator-istio-system:
kind create cluster
istioctl_1.11.2 install
kubectl get validatingwebhookconfigurations # only shows istio-validator-istio-system

Version
istioctl versions: 1.10.2 and 1.11.2

$ kubectl version --short
Client Version: v1.21.0
Server Version: v1.21.1

Additional Information
No response
Affected product area

[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[X] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

Is this the right place to submit this?

[X] This is not a security vulnerability
[X] This is not a question about how to use Istio

Similar issue faced even while doing canary upgrade using version.
kubectl get validatingwebhookconfiguration NAME                                             WEBHOOKS   AGE istio-validator-1-11-2-distroless-istio-system   2          3h24m istiod-istio-system                              1          21h

similar case when i do canary upgrade from 1.11.0 to 1.11.3 by using revision labels approach
the old validator webhook still exists after old control plane deleted, like this:
NAME                                                              WEBHOOKS   AGE
flowcontrol-guardrails.config.common-webhooks.networking.gke.io   1          104d
istio-validator-1-11-0-istio-system                               2          46d
istio-validator-1-11-3-istio-system                               2          12h

This is a similar case when we downgrade to 1.10.4 from 1.11.3. The new validatingwebhookconfiguration istio-validator-1-11-3-istio-system still exists after the 1.11.3 control plan is deleted and downgraded to 1.10.4-xxx

In discussions with Tong, I have some follow up questions to add.
We are using the in cluster operator deployment based upgrade instead of the istioctl install/upgrade based upgrade. This problem exists using this method.
What do these webhooks do (istiod-istio-system and istio-validator-istio-system?
What is the difference between them?
Why is the istiod-istio-system webhook remaining?
What happens if the istiod-istio-system webhook is deleted in 1.10 prior to installing 1.11?
Does a safe upgrade require waiting until 1.11 is installed before deleting the istiod-istio-system  webhook?
Is it safe to delete the istiod-istio-system before an install of 1.12?

similar case when i do canary upgrade from 1.11.0 to 1.11.3 by using revision labels approach
the old validator webhook still exists after old control plane deleted, like this:
NAME                                                              WEBHOOKS   AGE
flowcontrol-guardrails.config.common-webhooks.networking.gke.io   1          104d
istio-validator-1-11-0-istio-system                               2          46d
istio-validator-1-11-3-istio-system                               2          12h

This issue seems to be solved in 1.12. When I upgrade from 1.11.3 to 1.12 this time, no more zombie webhooks.
Not sure if it relates to a different operation step this time that I rollout-restarted deployments and statefulsets before deleting the previous version.

This issue seems to be solved in 1.12. When I upgrade from 1.11.3 to 1.12 this time, no more zombie webhooks.

The problem is not solved with 1.12.x.
If you directly install 1.11.3 and then upgrade to 1.12.0 you don't have the problem because the old validating webhook which does not get removed is from <=1.10.x.


Disable 'run analysis' if no baseline layers are present

If a deployment doesn't have a 'baseline' layer, the run analysis feature cannot be executed. We should disable the run analysis feature in this case. See screenshot below

How about running the analysis and giving the result by admin boundary? I think we should make that an option, even when there are other baseline layers

Yes, that would definitely work, though I think we're no longer 'running an analysis' per se. We're just calculating zonal stats, which is something we wanted to facilitate in general. We should revisit the UX for this and consider having zonal stats available at the layer level for raster data.


Test failures in test_cells.py

The tests for all three cell types currently fail at assert expected_output_shape == actual_output_shape.

Fixed.


nRF: Allow configuration of non connected GPIO

Summary
This adds a new GPIO functional mode GPIO_DISABLED where
pins for hardware like the SPI controller can be defined
but not connected to physical pin.
This also implements this feature in the nRF SPIM driver
and was tested leaving the MISO pin disconnected.
Impact
Right now is it really hard to not bring out all pins for a hardware block even if they are not used.  In my use case I need to use the SPI driver to control and LED driver, but it is used only as a single IO pin.  I still have to bring out the CLK (SPIM docs clarify this) but I no longer have to waste a physical pin.
Testing
Was able to drive the LED controller with out SCK and MOSI connected to pins.
#define BOARD_SPI1_SCK_PIN (GPIO_OUTPUT | GPIO_VALUE_ZERO | GPIO_PORT0 | GPIO_PIN(16))
#define BOARD_SPI1_MOSI_PIN (GPIO_OUTPUT | GPIO_VALUE_ZERO | GPIO_PORT0 | GPIO_PIN(7))
#define BOARD_SPI1_MISO_PIN (GPIO_DISABLED)

@patacongo do you have thoughts on this?  It feels a little ugly, but there is a lot of code that generally expects to map all pins. This provides a way to define the expected pin name, but explicitly say it should not be wired.

Any reason you need this at runtime? Why not just condition the SPI code on having MISO defined or not?
The change proposed for GPIO feels a bit too ad-hoc and would deviate how this works from every other architecture. Normally a pin is either configured or unconfigured. A "disabled" flag of the pincfg does not really map to that, it would require runtime check of that value everywhere.

The change proposed for GPIO feels a bit too ad-hoc and would deviate how this works from every other architecture. Normally a pin is either configured or unconfigured. A "disabled" flag of the pincfg does not really map to that, it would require runtime check of that value everywhere.

but how would that work you have
  .miso_pin  = BOARD_SPI0_MISO_PIN,

which expects to be a GPIO pin definition.  You need to supply something to that otherwise you are breaking the abstraction and checking if BOARD_SPI0_MISO_PIN is defined in code that should just be using .miso_pin.

This should be similar to when you have different output channels for a timer. You choose to use a channel or not and then the driver assumes the corresponding PINCFG define is there. The struct var can be set to 0 or not even initialized since it will not be used. On the SPI driver you mark the pin as disconnected when the macro is undefined. Or am I missing something?

But what is undefined.  0 is a valid pin config. This is problem.

But would you even read .miso_pin in that scenario? I mean, the content of the variable doesn't matter.

This seems to be a problem with the SPI itself, not the GPIO.
We should add a configuration option to select SPIM in half-duplex mode.
Add bool halfduplex; field to the 'struct nrf52_spidev_s' and set it up according to the configuration
#if defined(CONFIG_NRF52_SPIM0_HALFDUPLEX) || defined(CONFIG_NRF52_SPIM1_HALFDUPLEX) || ...
#  define NRF52_SPIM_HAVE_HALFDUPLEX 1
#endif

struct nrf52_spidev_s
{
...

#ifdef NRF52_SPIM_HAVE_HALFDUPLEX
  bool halfduplex;
#endif
};

static struct nrf52_spidev_s g_spi0dev =
{
   ...

#ifdef CONFIG_NRF52_SPIM0_HALFDUPLEX
  .halfduplex = true,
#endif
}

static int nrf52_spi_init(FAR struct nrf52_spidev_s *priv)
{
   ...

  if (priv->halfduplex == false)
    {
      /* Select MISO pins */

      ...
    }
}

This seems to be a problem with the SPI itself, not the GPIO.
We should add a configuration option to select SPIM in half-duplex mode.
Add bool halfduplex; field to the 'struct nrf52_spidev_s' and set it up according to the configuration

This is about pin selection for all peripherals, it is not specific to SPI.  I don't want to run in halfduplex mode I just dont want to physically connect all the pins.
This is true for the UARTE as well, you can tell  PSEL.RXD to be DISCONNECTED.
Or for TWIM  PSEL.SDA

This is about pin selection for all peripherals, it is not specific to SPI. I don't want to run in halfduplex mode I just dont want to physically connect all the pins.

I should say halfduplex mode or simplex mode but for SPIM it means the same - disconnect MISO pin.

Maybe we should introduce a new GPIO function that translates the GPIO definition to the PSEL value? If pin is DISCONNECTED it should return 0xffffffff which is the default value for all PSEL registers.

I agree with the suggestions above the it appears to be something that should be solved at the peripheral side (SPI here, could be other) with an option to not use a pin. I'm not really following why do you need more than that or why it needs to be at runtime.
I personally think that compile-time assignment of pins this way can be limiting but it is how NuttX works for everything now and until we can make a global improvement we should follow this model everywhere.

@v01d @davids5 I agree that compile time is preferred but I don't see how to do it.
There are two things that need to be controlled

The pin itself. This is clear how it can be ifdefed away.
The pin to peripheral mapping (iomux in other chips). This problem here is that the peripheral struct requires all the pins to to supplied. I cannot have MISO for SPI0 and not for SPI1.  So unless we create unique functions for SPI0 and SPI1 I don't see how at compile time we could do this. Plus you still need to configure the pin mapping on the peripheral to be disconnected.

2. The pin to peripheral mapping (iomux in other chips). This problem here is that the peripheral struct requires all the pins to to supplied. I cannot have MISO for SPI0 and not for SPI1.  So unless we create unique functions for SPI0 and SPI1 I don't see how at compile time we could do this. Plus you still need to configure the pin mapping on the peripheral to be disconnected.

Do you mean this part of the struct initialization for each spi instance?

 .miso_pin  = BOARD_SPI0_MISO_PIN,

If so, it is not required to initialize all variables of a struct. You condition that on #ifdef BOARD_SPI0_MISO_PIN the same as the code expecting this pin to be defined.

2. The pin to peripheral mapping (iomux in other chips). This problem here is that the peripheral struct requires all the pins to to supplied. I cannot have MISO for SPI0 and not for SPI1.  So unless we create unique functions for SPI0 and SPI1 I don't see how at compile time we could do this. Plus you still need to configure the pin mapping on the peripheral to be disconnected.

Do you mean this part of the struct initialization for each spi instance?

 .miso_pin  = BOARD_SPI0_MISO_PIN,

If so, it is not required to initialize all variables of a struct. You condition that on #ifdef BOARD_SPI0_MISO_PIN the same as the code expecting this pin to be defined.

What do you mean but not initialize it? There will be something in struct it will just be underfined.  This is the part I don't understand in what you are saying. How will will the driver know to configure the SPIM controller with the pin disconnected?

With the same macro?
Having the variable undefined is not problem if you know it will not be read. This is standard across many drivers were struct fields depend on configuration values.
I don't know, without fully understanding which is the problematic code I don't have much else to add. Maybe @raiden00pl has a clearer idea.

With the same macro?
Having the variable undefined is not problem if you know it will not be read. This is standard across many drivers were struct fields depend on configuration values.
I don't know, without fully understanding which is the problematic code I don't have much else to add. Maybe @raiden00pl has a clearer idea.

How can you use a SPIM# specific macro inside of static int nrf52_spi_init(FAR struct nrf52_spidev_s *priv)
You need to set regval here to point at the pin or explicitly set it as disconnected nrf52_spi_putreg(priv, NRF52_SPIM_PSELMOSI_OFFSET, regval);
See my comment on your code suggestion here https://github.com/apache/incubator-nuttx/pull/1788#discussion_r488279394
If I did not define BOARD_SPI1_MISO_PIN  then both SPI0 and SPI1 would have the pins disconnected even if BOARD_SPI1_MISO_PIN was defined.

Oh, so you mean because spi_init is generic? I think you could simply do something like:

if (priv == g_spi0dev)
{
#ifdef BOARD_SPI0_MISO_PIN
/* use pin for SPI, configure it */
#else
/* set SPI to not use it */
#endif
}
else if (priv == g_spi1dev)
{
#ifdef BOARD_SPI1_MISO_PIN
/* use pin for SPI, configure it */
#else
/* set SPI to not use it */
#endif
}
/* ... and so on */

If you had the g_spiNdev in an array this could be further simplified with a parametrized macro
taking the instance number.

Oh, so you mean because spi_init is generic? I think you could simply do something like:
if (priv == g_spi0dev)
{
#ifdef BOARD_SPI0_MISO_PIN
/* use pin for SPI, configure it /
#else
/ set SPI to not use it /
#endif
}
else if (priv == g_spi1dev)
{
#ifdef BOARD_SPI1_MISO_PIN
/ use pin for SPI, configure it /
#else
/ set SPI to not use it /
#endif
}
/ ... and so on */
If you had the g_spiNdev in an array this could be further simplified with a parametrized macro
taking the instance number.

At that point we might as well just make nrf52_spi_init into unique functions for each controller it will be the same amount of copied code?

What about a new function like this:
#define PSEL_PIN_SHIFT       (0)
#define PSEL_PORT_SHIFT      (5)
#define PSEL_CONNECTED_SHIFT (0 << 31)

uint32_t nrf52_gpio_psel(nrf52_pinset_t pinset)
{
  uint32_t psel = 0;
  int      pin  = 0;
  int      port = 0;

  if ((pinset & GPIO_FUNC_MASK) != GPIO_DISABLED)
    {
      /* Pin not connected - set reset value */

      psel = 0xffffffff;
    }
  else
    {
      /* Pin connected - configure pin and port */

      pin  = GPIO_PIN_DECODE(pinset);
      port = GPIO_PORT_DECODE(pinset);

      psel = 0;
      psel |= pin << PSEL_PIN_SHIFT;
      psel |= port << PSEL_PORT_SHIFT;
    }

    return psel;
}

and then we can replace all PSEL configuration logic with that.
  regval = nrf52_gpio_psel(priv->sck_pin);
  if (regval == 0xffffffff)
  {
   /* Unsupported */
    DEBUGASSERT(0);
  }
  nrf52_spi_putreg(priv, NRF52_SPIM_PSELSCK_OFFSET, regval);

  regval = nrf52_gpio_psel(priv->miso_pin);
  nrf52_spi_putreg(priv, NRF52_SPIM_PSELMISO_OFFSET, regval);

This will simplify the code and will be a more general solution, easy to adapt for other peripherals.

@raiden00pl I am fine with this (it is similar to my original change), but I thought the objection was to my addition of GPIO_DISABLED and the runtime logic for computing psel.

Yes, adding GPIO_DISABLED is what I suggested to avoid. I'd prefer doing this on the peripheral side at least for now. GPIO_DISABLED should be address in all architectures if it is something that we want to support completely.

In following this (and I not sure I am :) 100% ).....I keep hearing Greg saying that 'consistency' matters....  I was just questioning runtime "wiring" in the SW when the HW is fixed. But I am sure you will come up with a good solution.

On some architectures you can just achieve GPIO_DISABLED by setting the pin configuration to 0, but that won't work for NRF52.
As I know PSEL is always configured at the runtime because there is no hardcoded pinmux for NRF52. We can avoid this by creating definitions for all possible peripheral pin configurations, but we'll probably agree that it doesn't make sense.
I'm still not sure if we should deal with it at the SPIM side or the GPIO side as proposed, but GPIO_DISABLE is a useful new feature that I'm fine with. Dealing with it on the peripheral side will also be more complicated.

On some architectures you can just achieve GPIO_DISABLED by setting the pin configuration to 0, but that won't work for NRF52.

But that's not really documented is it? Sounds more like a side-effect. If you look in stm32_gpio.h there's no such definition either and from what I see stm32_configgpio wouldn't deal with it normally (it would error out when it doesn't find the pin/port in it).

As I know PSEL is always configured at the runtime because there is no hardcoded pinmux for NRF52. We can avoid this by creating definitions for all possible peripheral pin configurations, but we'll probably agree that it doesn't make sense.

But besides the pinmux (which would be simply predefined _1, _2 values for a given pin), pins are always mapped at buid-time with macros. It is not necessary to define all possible values for nRF52, the macros allow a peripheral to know what pin to use, not the other way around. So you don't need all possible peripheral cases for a pin.

I'm still not sure if we should deal with it at the SPIM side or the GPIO side as proposed, but GPIO_DISABLE is a useful new feature that I'm fine with. Dealing with it on the peripheral side will also be more complicated.

I'm not fond of the idea of adding such flag for just one arch (changing it for all, would be another point). Let try to consider the broad case as well when introducing changes in one arch that differ in semantics from other arch's, just for the sake of consistency. IMHO the code I suggested allows for the desired ability to not use MISO and it is not hard to do the same for other peripheral if needed so I don't really see the need for such change at GPIO.

But that's not really documented is it? Sounds more like a side-effect.

Yes, this is just side-effect, that sets up the first GPIO to reset state.
I think now there is a more proper way to disconnect peripheral from pin - you just define pin as in the reset state, eg
#define GPIO_SPI1_SCK  (GPIO_INPUT|GPIO_PORTA|GPIO_PIN5) // no alternate function configured
But this can't be done this way for NRF52, there must be a special flag in pincfg to avoid PSEL configuration.
So maybe in other arch there is no GPIO_DISABLED flag because it is not required there to achieve the given functionality.

But besides the pinmux (which would be simply predefined _1, _2 values for a given pin), pins are always mapped at buid-time with macros. It is not necessary to define all possible values for nRF52, the macros allow a peripheral to know what pin to use, not the other way around. So you don't need all possible peripheral cases for a pin.

All supported NRF52 peripherals that use GPIO require logic like this to configure PSEL
  /* Setect TX pins for UART */

  pin  = GPIO_PIN_DECODE(config->txpin);
  port = GPIO_PORT_DECODE(config->txpin);

  regval = (pin << UART_PSELTXD_PIN_SHIFT);
  regval |= (port << UART_PSELTXD_PORT_SHIFT);
  putreg32(regval, base + NRF52_UART_PSELTXD_OFFSET);

so this is done at runtime.
I don't quite understand where this PR introduce more runtime GPIO configuration than it is already done in code.

But that's not really documented is it? Sounds more like a side-effect. If you look in stm32_gpio.h there's no such definition either and from what I see stm32_configgpio wouldn't deal with it normally (it would error out when it doesn't find the pin/port in it).

It is PORTA Bit 0. - Seen may bugs that reconfigure the ADC by mistake.

Closed in favour of #2189 which does not pollute the GPIO definition but rather checks to see if has been defined in the first place.


feat(blog): add blog package

Add next js blog package
Updated dependencies across the whole monorepo
renamed packages. Now the monorepo is under @yisuses scope and each package under @whe scope


Adding a new User through dashboard doesn't send confirmation email

Bug report

[X] I confirm this is a bug with Supabase, not with my own application.
[X] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
When adding a new user through the Supabase dashboard, no confirmation email is sent to the user.
To Reproduce

Go to Supabase and enter a project.
Go to Authentication
At the top right, Click on Add User and select the Create New User option.
Enter a valid email address and password. Make sure to uncheck the Auto Confirm User option.
Check the email you provided in step 4 to see if you received an email.  As the bug description states above, you should have received no email. (Both inbox and spam)

Expected behavior
Upon adding a new user, The user should receive an email asking them to confirm their email address which will provide a link to allow them to validate their account.
System information

OS: Windows
Browser Chrome, Brave, Firefox
Version of supabase-js: 2.32.0
Version of Node.js: 19. 3.0

Additional context
I understand there may be several other factors that may stop such an email from being sent other than a bug. However, I have been successful at sending the same email when adding a user programatically and by clicking the 'Send Magic Link' option from the dashboard after waiting at times for up to 20 minutes after adding that same user. In both cases, the email arrived almost instantaneously. Furthermore, this also rules out any errors with the email as well. Another factor that could affect this is the rate limit on the number of emails that can be sent per hour. I have also eliminated this factor since the rate limit was set to 60 and I never exceeded the limit during testing.

Hey @NIKET79, @priyanshu2k3 and @SatanshuMishra, the add user method on the supabase dashboard uses the admin create user endpoint in your project (which is identical to supabase.auth.admin.createUser). This method does not send out a confirmation email.
If you want to send out a confirmation email to the user, you should select the "invite user" option on the dashboard instead.

Thamks @kangmingtay , this information saved me quite some time!


[Android] Tapping integrated Sign in with Google button seems to interact with the next dialog

Current Behaviour :cry:
It seems that the following command is not just tapping on [Sign in with Google] but also tapping the Add another account option within the Choose an account dialog:
- tapOn:
    id: "authMethodButton"
    index: 0

Environment information :earth_africa:
Maestro version: 1.21.3
OS: Mac OS X
OS version: 13.2
Architecture: aarch64
Screenshots, video :framed_picture:
https://user-images.githubusercontent.com/31889666/217302671-1b09b343-863c-44df-aa3f-d831dc3fecc4.mov

We can close this issue now.
There is a know issue where Maestro will attempt to tap the element again if it doesn't see any view hierarchy changes after the initial tap. This can be worked around by using retryTapIfNoChange: false, see known issue here


Add watch on sshd status in "Wait for VM's SSH Server" step

These two commits allow for adding a watch on sshd's status during the "Wait for VM's SSH Server" step, in an attempt to help resolve the flakes reported in https://github.com/cilium/cilium/issues/26012. By adding the ability to check on sshd's status in the VM, more information can be gained in regards to what could be happening in these flakes. Additionally, searching for specific status strings in the console log file is an inexpensive way to wait for the sshd server to startup.
To test this, I created two VMs: one with just an ssh server that will successfully start, and one with an ssh server that will fail to start.
The logs for the successful VM show the following:
[  OK  ] Reached target network.target - Network.
         Starting ssh.service - OpenBSD Secure Shell server...
         Starting systemd-user-sess…vice - Permit User Sessions...
[  OK  ] Finished systemd-user-sess…ervice - Permit User Sessions.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty1.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty2.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty3.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty4.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty5.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty6.
[  OK  ] Started serial-getty@ttyS0…rvice - Serial Getty on ttyS0.
[  OK  ] Reached target getty.target - Login Prompts.
[    2.161057] IPv6: ADDRCONF(NETDEV_CHANGE): ens2: link becomes ready
[    2.293043] random: crng init done
[  OK  ] Finished systemd-random-se…ce - Load/Save OS Random Seed.
[  OK  ] Started ssh.service - OpenBSD Secure Shell server.
[  OK  ] Reached target multi-user.target - Multi-User System.
[  OK  ] Reached target graphical.target - Graphical Interface.
         Starting systemd-update-ut… Record Runlevel Change in UTMP...
[  OK  ] Finished systemd-update-ut… - Record Runlevel Change in UTMP.

Debian GNU/Linux trixie/sid b0e82f92c653 ttyS0

b0e82f92c653 login:

While the logs for the failing VM show:
[  OK  ] Reached target network.target - Network.
         Starting ssh.service - OpenBSD Secure Shell server...
         Starting systemd-user-sess…vice - Permit User Sessions...
[  OK  ] Finished e2scrub_reap.serv…ine ext4 Metadata Check Snapshots.
[  OK  ] Finished systemd-user-sess…ervice - Permit User Sessions.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty1.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty2.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty3.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty4.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty5.
[  OK  ] Started<EMAIL_ADDRESS>- Getty on tty6.
[  OK  ] Started serial-getty@ttyS0…rvice - Serial Getty on ttyS0.
[  OK  ] Reached target getty.target - Login Prompts.
[    2.127693] IPv6: ADDRCONF(NETDEV_CHANGE): ens2: link becomes ready
[    2.247729] random: crng init done
[FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server.
See 'systemctl status ssh.service' for details.
[  OK  ] Reached target multi-user.target - Multi-User System.
[  OK  ] Reached target graphical.target - Graphical Interface.
         Starting systemd-update-ut… Record Runlevel Change in UTMP...
[  OK  ] Finished systemd-random-se…ce - Load/Save OS Random Seed.
[  OK  ] Finished systemd-update-ut… - Record Runlevel Change in UTMP.

Debian GNU/Linux trixie/sid 1210fc6805aa ttyS0

1210fc6805aa login:

The whitespace in these lines can sometimes be filled with terminal color codes, which is why the search strings in the action use .* in place of whitespace characters.

I'm going to tag a new version after merging this PR.


文档的代码被翻译

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem description
阻止代码被翻译
Proposed solution
文档中的代码使用pre、code标签或者对div添加translate=“no”属性
Alternatives considered
文档中的代码使用pre、code标签或者对div添加translate=“no”属性
Additional information
No response

Please Transfer the issue to https://github.com/electron-forge/electron-forge-docs
/cc @erickzhao @VerteDinde 🙇♂

I checked the documentation and this is supposed to be a bug in GitBook, they don't provide any way to do this. 🙃

我对GitBook不太了解，我查看了GitBook的文档，它的代码块也没有阻止翻译。
我自己写了一个脚本对forge文档中使用了.r-2awvau类名的dom增加一个translate=no的属性可以防止被翻译。
如果在生成文档后可以操作内容可以尝试添加该属性
document.querySelectorAll('.r-2awvau').forEach(ele=>{
ele.setAttribute('translate','no')
})
展示下效果
| |
lmj8lmj8
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | @.> |
| 发送日期 | 2023年03月2日 16:05 |
| 收件人 | @.> |
| 抄送人 | @.> ,
@.> |
| 主题 | Re: [electron/forge] 文档的代码被翻译 (Issue #3177) |
I checked the documentation and this is supposed to be a bug in GitBook, they don't provide any way to do this. 🙃
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

图片可以在邮箱中查看

This may not work because the css class name is randomly generated.

我已经和gitbook的团队沟通，后续请关注gitbook的更新！
| |
lmj8lmj8
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | @.> |
| 发送日期 | 2023年03月3日 11:05 |
| 收件人 | @.> |
| 抄送人 | @.> ,
@.> |
| 主题 | Re: [electron/forge] 文档的代码被翻译 (Issue #3177) |
This may not work because the css class name is randomly generated.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


fix force delete namespace did not delete all topics of the namespace

Motivation
We found a issue that when force deleting a namespace, only topics owned by the broker were deleted, topics owned by other brokers were not deleted.
The force delete namespace feature was added in #7993 .
Modifications
Use admin client to delete the topic, which could delete all topics include those owned by other brokers.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

Please rebase to the latest master since the master branch was broken before.

/pulsarbot run-failure-checks


API endpoints for Power BI

User story
As an end-user or leader I want to bring statistical VSM data to other tools, e.g. Power BI dashboards so that I can visualise current process health, improvement pace and use the data to ensure progress
Requirements

[ ] Data setup to contextualise the data (MVP according to existing Power BI needs)
[ ] GDPR is not violated (e.g. user data in the changelog)

Virtual sql-table-views vs API-access.
We talked about if a proper api would be better. I'm leaning towards it since that would be a more proper way to do it for everyone...
Also, some GDPR things to consider. What is considered sensitive data? Names, and timestamps in the change-log could be used to check when people are working etc...
The importance of free data
Might lead to higher adoption and usage.
Supporting the power-users. 💪 -> Value

@Magos @SjoenH : I have discussed use of API's in Power Bi with a colleague who tells me some API's are very straightforward to connect to from Power BI, such as the Centuries API (api.centuries.equinor.com). So I agree with @SjoenH here that we should just go for that from the start. I guess we can start with a simple endpoint with some basic data to verify and then gradually improve it based on need?

Desired statistics:

A process listing with additional statistics :
Subactivity count
Task counts by category & Solved/unsolved
Update times
A label listing with the connected projects
Label text, project ID numbers

@Magos For the changelog I am currently using the following SQL query:
`SELECT [fkVsm], [ChangeDate] As Updated, [UserIdentity] As UpdatedBy
FROM [dbo].[ChangeLog]
WHERE fkVsm is not null
UNION ALL
SELECT [PkVsm] As fkVsm,[Updated],[UpdatedBy]
FROM [dbo].[VSM]
FOR SYSTEM_TIME ALL
where updated > '2022-03-16 10:47'
order by ChangeDate desc`
It is however returning short names. To be safer wrt GDPR I would rather have a UUID or similar representing the user instead of the shortname.

I have troubles testing these, seems like an access issue, let's have a chat @Magos

@anheri @pagodo :wave: We might need some input here...
How would you open the API for everyone in the Equinor tenant? Specifically for use in PowerBi.

Thorjan has mentioned being able to use the Organizational Account method offered by PowerBI in the Centuries API.
Looking at their code, all their controllers have a [Connect2DbAsUser] attribute  which I'm not entirely sure where is defined yet. For the statistics controller this method might actually work, as I've defined these statistics views with a GRANT READ TO PUBLIC permission.

@Magos Any updates here?

Created new endpoints listed here:

The endpoints provide the data listed in this comment, except for "to be" as it is deprecated: https://github.com/equinor/flyt/issues/160#issuecomment-1054054044
See illustration of data flow here for guidelines for other data that is wanted. Not all data is available to the flyt-api so it may need to be sourced elsewhere.


-R is currently being used as both s and R

From #15
-s DIR Directory to search for coverage reports.
Already searches project root and current working directory

We are currently using the -R flag for both the -s and -R` uses.
@codecov/open-source can we clearly define the use cases for each flag so we can determine how best to seperate them?

@thomasrockhu

@eddiemoore Do you know if this was ever sorted?

Yeah we would still need this. As you could have the project folder and the coverage folder in different locations.

This related to #360, likely solving one of these issues would solve both, or come near to it. At the very least, it would be straightforward to fix these in tandem, I believe.


gen and emissions data loading time

Running the code to load the generation and emission data seems to take over 10 minutes, even when the cache data has already been downloaded. Probably not ideal from a usability point of view, I'm just imaging someone trying out the tool for the first time and giving up or getting discrated by something else because even loading the data to start testing out the tool takes this long.

@nick-gorman thoughts:

separate notebook for loading data, save loaded files somewhere for users to reference
maybe use this as example data too?

Implemented caching and separate notebook for adding new data to the cache.


Individual Survey - Jez

Need to fill in this survey
https://docs.google.com/a/sheffield.ac.uk/forms/d/1aXlqxFk6uJbB0k7QICteI5CP3lVczZKyjmgeNibX0Oc/viewform

Done.


[llm-gateway] add tft and tot metrics and add them to grafana dashboard

Add TFT and total request time in llm-gateway.
For TFT the timer should be started when the request is received and timer should end then first token is received from upstream LLM.
The unit for metric should be milliseconds and should be stored in WasmMetrics struct.

We need the following metrics instrumented

Time to first token (TTFT): This is how quickly users start seeing the model’s output after entering their query. Low waiting times for a response are essential in real-time interactions, but less important in offline workloads. This metric is driven by the time required to process the prompt and then generate the first output token.
Time per output token (TPOT): Time to generate an output token for each user that is querying the system.
Latency = TTFT + (TPOT) * (the number of tokens to be generated)
Output sequence length (OSL) - Total tokens generated
Input sequence length (ISL) - Total input tokens

We need the following metrics histograms in 5 mins, 15 mins, 30 mins, 1 hour, 24 hours, 7 day granularity.

Average (p50)
P90 (90th percentile)
p95 (95th percentile)
p99 (99th percentile)


Program doesn't switch between constant frequency and wavelength

The default input is constant wavelength. When we try to switch to constant frequency the program still appears to read in constant wavelengths. Is there a way to fix this?
Thanks

Why do you say it's not reading in in constant frequency?  What's the symptom?
You can see the code here: https://github.com/kenwdelong/frog/blob/master/FROG/RawData.pas#L229
If you take a very short pulse, say 10fs, generate the FROG trace, and then read it back in both ways, you should see that the trace has different shapes depending on if you read it in with constant frequency or wavelength.  For pulses much longer than, say, 10-20fs, you won't be able to see the difference.

Thanks for responding!
The UI doesn't change in any way when we switch between the two, but we input the values anyway, put 750 as the central frequency (unsure what units it is reading in when in constant frequency mode). When we retrieved the pulse, the spectrum was centred at 1500 nm, indicating that it read it as 750nm (SHG FROG so that wavelength would be doubled.

That's correct, neither the UI nor the central wavelength will be affected by that setting.
What that setting is doing is changing how to interpret how the points are to be interpreted along the wavelength/frequency axis of the FROG trace being read in.
Let's assume the central wavelength of the trace is 800nm (meaning for SHG the fundamental was 1600nm).
On constant frequency (assuming delta_lam = 1nm), the points would be interpreted as (starting in the center of the grid): 800nm, 801nm, 802nm, 803nm (or in frequency, c/800, c/801, c/802, c/803).  Because the points are not on a constant frequency spacing, but the FFT requires constant frequency, they will be interpolated nonlinearly onto a constant frequency grid.
If the setting is on constant frequency, with the central frequency is c/800 and the spacing as del_f, the points are understood as c/800, c/800 + del_f, c/800 + 2del_f, c/800 + 3del_f, etc.  So they don't need nonlinear interpolation when read in.
The only way this makes much difference is with very short pulses (very broad spectrum).  You can use real units, create a 10fs pulse, and save the FROG trace.  Then try reading it in with constant frequency and constant wavelength.  At that bandwidth, you should see a difference.  Actually, if you use SHG, you might not be able to see it easily (since everying is an oval).  Try PG FROG.  Also, retrieve the pulse and see what the results are.