make admin work on arbitrary base paths

fixes #397
this change makes every url/ajax/href/src in admin relative.
initially i had planned to add a new linkerd config flag specifying the base path. this was problematic for two reasons:

the base path would need to be passed from config -> admin -> templates -> js
it would prevent linkerd from running with multiple base paths. primary example is DC/OS runs admin on /service/linkerd/, but the user can still also access any linkerd in their cluster by browsing directly to the admin port. if /service/linkerd/ were coded into the config, this would not be possible.

If I browse to http://localhost:4140/foo (as opposed to http://localhost:4140/foo/ with the trailing slash) I get broken resource links.

@adleong that's expected, we require the trailing the slash. this makes the root consistent with all other paths: /files..., /admin..., etc.

That's unfortunate, it would be nice to be able to accept either.  I wonder if in javascript land we can force the trailing slash somehow (edit the window location???)?
That said, this is a strictly better than the current state of affairs.  🚀


Draw option in State Machines invalidates the diagram in UmpleOnline

Summary
Within the UmpleOnline, the users can write code and generate the equivalent "State Machines" diagram. Unlike some other drawing options (Association, Generalization, etc.), "Class" drawing option is enabled and the users can drag and drop the "Class" component at the design pane. Once dropped, the existing design becomes invalid.
Steps to Reproduce

Go to the "TOOLS", then select the "State Machines" from the dropdown. Select an example "Agents Communicating".

Look at the diagram pane. It will display the related state machine diagram.

Now, click on the "Class" icon under the "DRAW" section and drag it into the design pane. Drop it.

The previous state machine diagram vanishes.

Expected Feature
The system should disable drag and drop option of "Class" control while in "State Machines". It would be better to hide these drawing options if drawing is not permitted in design pane.

This problem was fixed months ago. I am unable to reproduce this. It seems to work just fine in Safari for the Mac.
I have also tried it in Edge and Chrome and Firefox. Works fine there too.
Maybe there are circumstances where this in fact is a problem, but in that case the exact sequence leading up to the bug needs to be checked. Maybe it is a problem on Windows or Linux browsers.

I have tested this for four major browsers. Chrome, Safari, Edge, and Firefox. I could not re-produce this issue for any state machine.
I would request to close this issue.


Status is not updated to "Needs review" after pushes

The README says:

Finally, the status will be "Needs review" after the author pushes changes to the PR.

However, I haven't yet experienced this. Most recent example where I manually had to switch the status: https://github.com/symfony/symfony/pull/39696
(I'm not sure if this is a bug, or an invalid README, it can make sense to not automatically switch the status after a push)

It is done only if the existing status is "needs work".

Yes, that's the case here (but maybe I was too quick).

I've experienced this here also, when I pushed a change to the PR, the status did not change automatically to Needs review. And I think this happened with me couple of times before.


compile error

/include/caffe/vision_layers.hpp:361:14: error: ‘PowerLayer’ was not declared in this scope
shared_ptr<PowerLayer > square_layer_;
so many errors there.

have you solved the problem?I have met the same error...

you should #include "caffe/layers/power_layer.hpp" in vision_layers.hpp

did this work you?


Can't specify all options when using Kubernetes clusters withVersion

I'm modifying the example found here:
https://github.com/Azure-Samples/aks-java-manage-kubernetes-cluster/blob/master/src/main/java/com/microsoft/azure/management/kubernetescluster/samples/ManageKubernetesCluster.java
            KubernetesCluster kubernetesCluster = azure.kubernetesClusters().define(aksName)
                .withRegion(region)
                .withNewResourceGroup(rgName)
                .withLatestVersion()
                .withRootUsername(rootUserName)
                .withSshKey(sshKeys.getSshPublicKey())
                .withServicePrincipalClientId(servicePrincipalClientId)
                .withServicePrincipalSecret(servicePrincipalSecret)
                .defineAgentPool("agentpool")
                    .withVirtualMachineCount(1)
                    .withVirtualMachineSize(ContainerServiceVMSizeTypes.STANDARD_D1_V2)
                    .attach()
                .withDnsPrefix("dns-" + aksName)
                .create();

If you change withLatestVersion to withVersion, the return type changes to a withDnsPrefix which then goes to a withCreate, meaning we're left with:
            KubernetesCluster kubernetesCluster = azure.kubernetesClusters().define(aksName)
                .withRegion(region)
                .withNewResourceGroup(rgName)
                .withVersion(KubernetesVersion.KUBERNETES_1_8_1)
                .withDnsPrefix("dns-" + aksName)
                .create();

Is this intentional? I'd still like to specify all the options.

nope, that is a bug. I will address it in the next release.

I have a fix ready for this (see https://github.com/Azure/azure-libraries-for-java/pull/79)
@umbrant Let me know if this bug is blocking you.

Thanks for the quick fix @milismsft ! I'm not immediately blocked since I can use withLatestVersion for now, though it'd be great to see this in a released version.

BTW it's safer in the long term to use .withLatestVersion() since the service is in preview and it can be updated at any time and it can be a while for the SDK to catch up with those changes.

Fixed in v1.5


Move interactors docs from BigTest repo

Motivation
https://github.com/thefrontside/bigtest/issues/981
Approach

Copied over git history from BigTest repo's website directory.
Shaved off Runner pieces and BigTest branding.
Reconfigured URLs as necessary.

After merge

[ ] Merge https://github.com/thefrontside/frontside.com/pull/155
[ ] Merge https://github.com/thefrontside/bigtest/pull/1004

Future steps
This project could use a logo in the same visual family as BigTest and Effection.

This project could use a logo in the same visual family as BigTest and Effection.

This feels like a pretty big thing to figure out in order to make a clean break with BigTest


Earth quake prediction

It is well known that if a disaster occurs in one region, it is likely to happen again. Some regions have frequent earthquakes, but this is only a comparative amount compared to other regions.
So, predicting the earthquake with date and time, latitude and longitude from previous data is not a trend that follows like other things, it happens naturally.
So basically if we have past data we can predict future disasters.
Make machine learning model do it.
I can provide dataset if needed.

assign me @Jayshah6699

assign me @Jayshah6699

Kindly complete Weather prediction first. @kenkirito

Kindly complete Weather prediction first. @kenkirito

I would like to work on this issue.
I am planning to use the following dataset:
https://www.kaggle.com/c/LANL-Earthquake-Prediction
I am planning to use the following Regressors on the dataset :

XGBoost,
CatBoost, and
Light Gradient Boost Method

Kindly assign me this issue.

I would like to work on this issue.
I am planning to use the following dataset:
https://www.kaggle.com/c/LANL-Earthquake-Prediction
I am planning to use the following Regressors on the dataset :

XGBoost,
CatBoost, and
Light Gradient Boost Method

Kindly assign me this issue.


Enum Literal Types  2.4.1

enum E {
    A = 1,
    B = "b"
}

let valye: E.A | E.B = 123; // Ok?

Duplicate of #6131

@andy-ms there on the enum in the role of type

I can't tell what the question is -- besides the problem of an arbitrary number being assignable to an enum type, which is issue #6131.


Sample saying No Gui Implemented

Hi, I just imported EditorAttributes from Unity Store and it's sample saying No Gui Implemented.

I am using Unity Editor 2022.3.33f1

That error happens when trying to draw a property using ImGUI but the asset is using UI Toolkit, does it happen with other attributes as well or only that? Do you have any other asset installed that might override the editors? Does it still happen if you use that attribute in another component?

It's happening in all the demo scenes. I have installed https://assetstore.unity.com/packages/tools/utilities/advanced-editor-tools-254203 alongside it.

Yeah that asset is most likely the issue since it might be using ImGUI and my package uses UI Toolkit which it creates a conflict. So you wont be able to have both assets in the project. From the looks of it that package has stuff that can already be done with mine so there is no need to have both


Using gdb with asyncify

As of now if we apply asyncify it disables our ability to use gdb.
I think the problem is similar to this issue: https://github.com/WebAssembly/binaryen/issues/3462
I inquired about any updates that may help us.

I was able to run lldb on hello world with the following:
apt install lldb
changed debug line to:
lldb -- $wasmtime_base/target/debug/wasmtime run -D debug-info -O opt-level=0 --wasi threads=y --wasi preview2=n [target]
and had to set aslr off once running:
settings set target.disable-aslr false
@qianxichen233 or @yzhang71 can one of you test this method on something more complicated that uses asyncify?

I just tried lldb with write.wasm (with asyncify applied), unfortunately it gives the error when I tried to break into user program's main function Error: failed to emit DWARF debug information


[engine-wiki] Update felt links and other potential links in wiki pages due to engine's master branch being renamed to main

The two felt links are broken in https://github.com/flutter/flutter/wiki/Compiling-the-engine#compiling-for-the-web, these needs to be updated and along wth other potential engine links in the wiki page
cc: @Hixie

cc @yjbanov

This seems to be fixed by someone (one link was left out, I just fixed that myself)


Support rdp:// protocol

Can you tell me how I can use /Admin with this beautiful tool ?
&admin of &=admin doesn't work

No description provided.

Sorry, new to Git.  Is there a binary for your improvements, since the original project owner seems to have disappeared.

@mpking828 I have made a release where you can download the exe ( https://github.com/pmiossec/MstscLauncher/releases/tag/v1.1.0 )
PS: Even if that's better to build it yourself to prevent downloading exe you don't trust....

Hi @damousys, @mpking828, @pmiossec I apologise for this pull request completely slipping me by! Thanks for the work!

@damousys I have updated the readme to explain how to use the parameters correctly https://github.com/richard-green/MstscLauncher/blob/master/README.md


RPC error parsing is wrong

Describe the bug
Most of the action errors from RPC are right now not shown and developer just sees "Error: {}"
To Reproduce
Steps to reproduce the behavior:

Send a transaction with 0 gas
See that error is "Error: {}"

Expected behavior
Shows error with not enough gas
Screenshots

To be clear, RPC returns correct errors and it's the parsing in the near-api-js that doesn't capture the error

Already fixed


Not showing up in Fedora 38

I have properly setup fcitx5. Then I ran wget -q https://raw.githubusercontent.com/GaZaTu/im-emoji-picker/master/install.sh && sh install.sh -f fcitx5 -r tags/nightly-build and it successfully installed. But I can't find it in fcitx5. I also did a reboot but it didn't work either.

@rago666 I don't remember what the KDE settings for fcitx5 look like but as a hint:
im-emoji-picker is not an input method when using fcitx5. It is a module running next to your default input method.
Modules are configurable in that dialog too but not under the input methods.
To just see if it works at all you can try pressing the default hotkey for the emoji picker: Control+Alt+period

Nope, doesn't work. But I did find a section called modules under configure addons but im-emoji-picker is not mentioned there.

weird. i'll look into this when i'm home 😅

you can execute sudo cp /usr/lib/fcitx5/fcitx5imemojipicker.so /usr/lib64/fcitx5/ in your terminal for now. that should fix the issue.
i have to figure out how to handle this situation. on arch there is no lib64 or rather it's just a symlink to lib so it always worked for me as is. idk if i should just hardcode lib64 into the install script.

Thank you for your time. The command indeed make I'm Emoji Picker to show up in the module section. And the app work flawlessly under x11.
But under wayland session, the app dies as soon as it launches. Running sudo journalctl -p 3 -xb shows this error during the failed launch
fcitx5[2603]: Failed to create wl_display (No such file or directory)
fcitx5[2603]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

ok the only thing i can imagine at this point is that there must be some kind of bug with KDE (wayland) + fcitx5 because fcitx immediately sends the deactivate event after the window opens (which is obviously wrong) and then it goes dark.
if i start the fcitx daemon with QT_QPA_PLATFORM=xcb it kinda works but that's obviously no solution.

I grabbed the logs from fcitx5 --verbose '*=5' and opened an issue with fcitx5:

fcitx/fcitx5#887


Update the NPM version (which is still the 0.12.1 version)

Yesterday I pushed a package of the v0.13.0 tag to npm. Many pages still say '0.12.1 is the latest' but the version badge shows 0.13 and that what I get from npm install.
@gkatsev, @johnBartos Any idea what I need to do to fix the npm package page?

Apparently this is a known bug with the site. Starring and then unstarring the package triggered an update. We should be good.

As long as npm dist-tag ls vtt.js says that the latest is the version you want, that's all that matters, really :)


[Just Test CI] modify notes for testing CI

【Just Test CI】modify notes for testing CI

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2182/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/49/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-2.1/78/Failed Tests: 1carbondata-pr-spark-2.1/org.apache.carbondata:carbondata-spark-common-test: 1org.apache.carbondata.spark.testsuite.allqueries.InsertIntoCarbonTableTestCase.insert into carbon table from carbon table union query

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2183/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-2.1/79/Build result: FAILURE[...truncated 80.27 KB...][ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :carbondata-spark2[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/processing/pom.xml to org.apache.carbondata/carbondata-processing/1.2.0-SNAPSHOT/carbondata-processing-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/integration/spark-common/pom.xml to org.apache.carbondata/carbondata-spark-common/1.2.0-SNAPSHOT/carbondata-spark-common-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/integration/hive/pom.xml to org.apache.carbondata/carbondata-hive/1.2.0-SNAPSHOT/carbondata-hive-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/common/pom.xml to org.apache.carbondata/carbondata-common/1.2.0-SNAPSHOT/carbondata-common-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/examples/spark2/pom.xml to org.apache.carbondata/carbondata-examples-spark2/1.2.0-SNAPSHOT/carbondata-examples-spark2-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/integration/spark2/pom.xml to org.apache.carbondata/carbondata-spark2/1.2.0-SNAPSHOT/carbondata-spark2-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/assembly/pom.xml to org.apache.carbondata/carbondata-assembly/1.2.0-SNAPSHOT/carbondata-assembly-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/pom.xml to org.apache.carbondata/carbondata-parent/1.2.0-SNAPSHOT/carbondata-parent-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/examples/flink/pom.xml to org.apache.carbondata/carbondata-examples-flink/1.2.0-SNAPSHOT/carbondata-examples-flink-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/core/pom.xml to org.apache.carbondata/carbondata-core/1.2.0-SNAPSHOT/carbondata-core-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/hadoop/pom.xml to org.apache.carbondata/carbondata-hadoop/1.2.0-SNAPSHOT/carbondata-hadoop-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/integration/presto/pom.xml to org.apache.carbondata/carbondata-presto/1.2.0-SNAPSHOT/carbondata-presto-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/jenkins-slave/workspace/carbondata-pr-spark-2.1/integration/spark-common-test/pom.xml to org.apache.carbondata/carbondata-spark-common-test/1.2.0-SNAPSHOT/carbondata-spark-common-test-1.2.0-SNAPSHOT.pomchannel stoppedSetting status of b04e4512284d93a1b2fa51ab9f56f2ae5899cc95 to FAILURE with url https://builds.apache.org/job/carbondata-pr-spark-2.1/79/ and message: 'Tests Failed for Spark2.1 'Using context: Jenkins(Spark2.1): mvn clean test -Pspark-2.1

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/50/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2186/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-2.1/82/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/53/

This PR is raised just for test CI, now close it.


ON CONFLICT does not work?

I am trying to do an upsert, insert but if it exists using a compound key I want to increment.   The sql command works direct to the database in dbeaver
insert into mytable (entity, name, icount) values (?,?,?,?) ON CONFLICT(entity,itype,name) DO UPDATE SET icount=icount+1
C#:
connection.Execute("insert into mytable (entity, name, icount) values (?,?,?) ON CONFLICT(entity,itype,name) DO UPDATE SET icount=icount+1","test","test",0);
ERROR:
SQLiteException near "ON": syntax error

Sorry I did not realize the project I am working on was using an obsolete version of sqllite.  Updating the dll fixed it.


Background reading?

This is a fascinating area, but somewhat obscure. Are there any papers or books you could recommend for someone trying to get a broad understanding of column stores in general and Kelindar in particular?

I found a couple of papers useful while implementing this:

Decomposition Storage Model, 1985, Copeland and Khoshafian
The Design and Implementation of Modern Column-Oriented Database Systems, 2013, D. Abadi et al

For the design of this specific library, I suggest you read the source code as I don't have anything else available.


Error encountered in nlp.pipe with multiprocessing with hu_core_news_lg

Describe the bug
When using nlp.pipe with hu_core_news_lg with multiple processors, I'm seeing the following error:
ValueError: [E871] Error encountered in nlp.pipe with multiprocessing:
...
E         File "/----/-----/---/---------/.venv/lib/python3.10/site-packages/spacy/ml/staticvectors.py", line 56, in forward
E           V = vocab.vectors.get_batch(keys)
E         File "spacy/vectors.pyx", line 485, in spacy.vectors.Vectors.get_batch
E         File "spacy/strings.pyx", line 176, in spacy.strings.StringStore.as_string
E         File "spacy/strings.pyx", line 160, in spacy.strings.StringStore.__getitem__
E       KeyError: "[E018] Can't retrieve string for hash '15356779350996366032'. This usually refers to an issue with the `Vocab` or `StringStore`."

To Reproduce
Minial code to reproduce error:
import spacy
nlp = spacy.load("hu_core_news_lg")

raw_docs = [
    "Nem tarthatnak maguknál fegyvert azok az amerikaia",
    "„Alva járt” – ezzel védekezett az a brit tinédzser",
    "Örményország hivatalosan is elismerte a palesztin ",
    "Egyszerű másolással ki lehetett deríteni, milyen n",
]

for doc in nlp.pipe(raw_docs, n_process=2):
    pass

Interestingly, small perturbations of the text affect whether the issue is present, e.g. the below example runs without any issues (the difference is the final letter at the end of the first item):
raw_docs = [
    "Nem tarthatnak maguknál fegyvert azok az amerikaiak",
    "„Alva járt” – ezzel védekezett az a brit tinédzser",
    "Örményország hivatalosan is elismerte a palesztin ",
    "Egyszerű másolással ki lehetett deríteni, milyen n",
]

Expected behavior
When processing these documents with nlp(doc) there are no issues. Expected behaviour is to see the same output through nlp.pipe() as with nlp().
Additional context
The error message is the same as this, however it seems to be huspacy specific (the issue doesn't occur with other models) -- and more specifically to do with the vector retrieval for the vocab / the tokenization.

@mpjuhasz Thanks for the detailed report. Could you please also specify your OS, Python version, spacy version, model version?

@oroszgy of course:
OS: macOS Sonoma 14.5
Python: 3.10.9
spacy: 3.7.5
huspacy: 0.11.0
hu_core_news_lg: 3.7.0

@mpjuhasz I think this is rather related to this issue: https://github.com/explosion/spaCy/issues/11413
Setting n_processes to 1 could be a workaround for now. I'll look into this more.

@oroszgy thanks for looking into it. Yes, n_processes=1 and also simply running nlp(text) work fine, but I specifically wanted to use the multiprocessing capability to process large volumes of data.
FWIW, based on my understanding of the spacy code there and this thread, it is in fact related to the issue you've linked above (in that it is doc.to_bytes(), which throws the error), albeit it's not an issue with the doc object being string, but rather the vector lookup from the Vocab (which is why I thought it might be more relevant here, than on spacy general).

@mpjuhasz Could you please test it with the latest 3.8.x models? I could not reproduce it with them?


https://github.com/strangelove-ventures/ibctest

[ ] explore the test framework and understand how it works
[ ] Estimate the effort on our side, to see how we can adapt for us and our usage


PLIC Claimed when read or written?

Hi, it is not clear if the Claim mechanism is triggered
if the Claim Register for that target is Read ?
or if it is written by any value (and then if re-written it triggers Complete)

Alright found out
Claim= Read
Complete = Write

Ok found out that immediate in this case must be 12 bit max


swiftDialog 2.5 Beta 1's --presentation removes ability to use --title, --bannertitle or --bannerimage

Is your feature request related to a problem? Please describe.
I like the new --presentation mode of swiftDialog introduced in the 2.5 beta 1 release. But I have one issue with it. This mode prevents me from using any of the --title or --banner* modes present in normal dialogs, which is unfortunate.
I've been using swiftDialog for our Mac onboarding process, just like so many other admins. And my previous scripts/flows allowed me to put a banner of the company logo or the like up at the top, or at least use a title of some kind. The new --presentation mode seems to prevent me from using any of these now. I didn't see it mentioned in the Beta release notes that this was the case, so I don't know if this was intentional or a bug. I'm adding it here as a feature request since I'm thinking this might have been intentional.
Describe the solution you'd like
I guess I'm asking for some way to continue to use the above mentioned flags along with the --presentation mode if possible. I realize that the new mode reconfigures how the dialog is structured, and I imagine it was created to help facilitate this onboarding workflow for which swiftDialog has become a popular use for, but not having the ability to use one or all of those options seems to detract from the ability to "brand" the process. For some organizations, its not quite as good to have an image in the left side of the dialog versus (or in addition to) having a banner across the top.
Describe alternatives you've considered
I can always continue to use swiftDialog the way I've been doing, but having --presentation now sort of auto configures the dialog for this purpose. I just don't really want to lose the ability to have an image across the top in some way.
Additional context
Nothing else to add.

correct - that's intentional. if you want title or banners etc then you use the regular dialog window. presentation mode is intended to be minimalistic

Ok, gotcha. I see you labeled this as 'will consider' so I hold out some hope that at least the title options will get added at some point to the presentation mode. I just think it would make it a little more flexible and useful.
Unrelated question, but, how does one change the background color that shows up in the left side box when using --presentation ? It always comes up as a blue color. I didn't see anything in the notes about how to change that, or if it's possible to change it.

with no input it will use the current highlight colour, but you can be specific by using --background colour= and specifying a colour by name or as a hex value,


Dell XPS 13 9310 fails to suspend

When running systemctl suspend on my Dell XPS 13 9310, the suspend fails. I see the following lines in my journal:
Bluetooth: hci0: SSR or FW donwnload time out
hci_uart_qca serial0-0: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -110
hci_uart_qca serial0-0: PM: failed to suspend: error -110
PM: Some devices failed to suspend, or early wake event detected

When I disable Bluetooth in the BIOS, everything works as expected, but as long as Bluetooth is enabled, I cannot suspend. Is there anything else I can try to get suspend to work with Bluetooth enabled? If so, we should probably add that to https://github.com/NixOS/nixos-hardware/tree/master/dell/xps/13-9310.

Does it help to run rmmod the bluetooth drivers before?

I would try using https://github.com/NixOS/nixos-hardware/blob/master/dell/xps/sleep-resume/bluetooth/default.nix  if you haven't already.
Also try cat /sys/power/mem_sleep and see if it's in the wrong sleep state.


Document missing values for SQLServiceType enum

Reddit user CobbITGuy has found and identified further possible values for this enum:
8   <AD Helper Service?? or Notification Services??>
9   <SQL Full-text Filter Daemon Launcher W10/SQL2017> (Service to launch full-text filter daemon process which will perform document filtering and word breaking for SQL Server full-text search. Disabling this service will make full-text search features of SQL Server unavailable.)
10 <SQL Server Polybase Engine>
11 <SQL Server Polybase Data Movement Service>
12 <SQL Server Launchpad WS2019/SQL2014> (Service to launch Advanced Analytics Extensions Launchpad process that enables integration with Microsoft R Open using standard T-SQL statements. Disabling this service will make Advanced Analytics features of SQL Server unavailable.)
Source:
https://www.reddit.com/r/SQLServer/comments/atwjcp/wmi_sqlservicetype/
I have not personally verified these; I do not know if this completes the list of possible values.
Is anyone able to confirm these values and whether the list is now complete?

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

ID: 905fa290-bf83-20f2-21c2-ca3c79e54d04
Version Independent ID: 6fc21f31-085f-cd79-7cd2-300e772b2865
Content: SqlServiceType Property (SqlServiceAdvancedProperty Class) - SQL Server
Content Source: docs/relational-databases/wmi-provider-configuration-classes/sqlserviceadvancedproperty-class/sqlservicetype-property-sqlserviceadvancedproperty-class.md
Product: sql
Technology: wmi
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@CarlRabeler -- the customer has determined there may be additional, undocumented, enum values -- I don't know how to verify these new values -- please process this issue 2369.

@WilliamAntonRohm I do not know either - will investigate

After logging this, I discovered a class in the same namespace called RegServices, which may hold the answer.
I ran this snippet on a SQL 2017 RTM installation:
Get-CimInstance -Namespace 'ROOT\Microsoft\SqlServer\ComputerManagement14' -ClassName 'RegServices' |
    Sort-Object Type |
    Format-Table

LName            Name                   ServiceType                               Type
-----            ----                   -----------                               ----
MSSQL$           MSSQLServer            SQL Server                                   1
SQLAgent$        SQLSERVERAGENT         SQL Agent                                    2
msftesql$        msftesql               Full Text                                    3
                 MsDtsServer            SSIS Server                                  4
MSOLAP$          MSSQLServerOLAPService Analysis Server                              5
ReportServer$    ReportServer           Report Server                                6
ReportServer$    ReportServer           ReportServer                                 6
                 SQLBrowser             SQL Browser                                  7
NS$              NsService              Notification Services                        8
MSSQLFDLauncher$ MSSQLFDLauncher        Full-text Filter Daemon Launcher             9
SQLPBENGINE$     SQLPBENGINE            SQL Server Polybase Engine                  10
SQLPBDMS$        SQLPBDMS               SQL Server Polybase Data Movement Service   11
MSSQLLaunchpad$  MSSQLLaunchpad         Launchpad Service                           12

I'm ready to bet that this is the full and complete answer, until vNext, anyway.

@CarlRabeler thank you for the merge! Should this be live yet?

should be live within a couple of hours

@fsackur Thank you for your feedback.  This issue has been fixed and so I am now closing this issue 2369.


Social icon SoundCloud

Please support the SoundCloud social icon. The SVG is found at https://www.svgrepo.com/svg/21451/soundcloud
The username should be used as https://soundcloud.com/USERNAME (without www. and without trailing slash /)

Sorry, Minima won't be supporting additional social platform icons.

Would a PR be welcomed?


Read QRcode moving the finger to right.

The faster mode to pay someone is scanning a Qrcode. I think this app should allow the user move the finger to right and appear the option to scan the qrcode. Something like whatsapp does and this app too:

Already implemented. Thanks.


Update s3, sdk-core, sqs to 2.16.21

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.15.82 to 2.16.21.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-minor

Superseded by #115.


Mojifier Demo

First pass through
Reviewed by Grammarly
Updated links=
Updated the Yamls

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

Line 16: [Error] Restore nuget package W:\zxp1-s.optemp\packages\opbuild.scripts.1.47.2\tools\packages.config in folder:W:\zxp1-s.optemp\packages failed, possibly due to transient errors from nuget servers. Please retry building your content. If the issue still happens, open a ticket in http://SiteHelp. Detailed error:  Errors in packages.config projects     Unable to find version '1.47.2' of package 'opbuild.initializecrrtool'.       D:\Windows\system32\config\systemprofile.nuget\packages: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'D:\Windows\system32\config\systemprofile.nuget\packages'.       https://nuget.org/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://nuget.org/api/v2/'.       https://www.myget.org/F/op/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/op/api/v2/'.       https://www.myget.org/F/docfx/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/docfx/api/v2/'.       https://www.myget.org/F/op-dev/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/op-dev/api/v2/'.       https://www.myget.org/F/docfx-dev/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/docfx-dev/api/v2/'.

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

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

Line 16: [Error] Restore nuget package W:\03zk-s.optemp\packages\opbuild.scripts.1.47.2\tools\packages.config in folder:W:\03zk-s.optemp\packages failed, possibly due to transient errors from nuget servers. Please retry building your content. If the issue still happens, open a ticket in http://SiteHelp. Detailed error:  Errors in packages.config projects     Unable to find version '1.47.2' of package 'opbuild.initializecrrtool'.       D:\Windows\system32\config\systemprofile.nuget\packages: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'D:\Windows\system32\config\systemprofile.nuget\packages'.       https://www.myget.org/F/op/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/op/api/v2/'.       https://www.myget.org/F/docfx-dev/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/docfx-dev/api/v2/'.       https://nuget.org/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://nuget.org/api/v2/'.       https://www.myget.org/F/docfx/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/docfx/api/v2/'.       https://www.myget.org/F/op-dev/api/v2/: Package 'opbuild.initializecrrtool.1.47.2' is not found on source 'https://www.myget.org/F/op-dev/api/v2/'.

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


tmle3mopttx with missing baseline

It seems that the version of tmle3mopttx tagged in the DESCRIPTION file (specifically, this version) doesn't fully support working with missing data, as identified in this Travis build. This only affects the last example given in the chapter, which is turned off in this PR in order to restore the automated builds. Not urgent to fix, but just recording here for bookkeeping.

Hi, I am also encountering this issue when I run the exercise in the chapter: https://tlverse.org/tlverse-handbook/optimal-individualized-treatment-regimes.html. I get the same error which is that W has censoring and it is not supported.

Thanks for reporting this @jbriggs7. The issue should be resolved in using the latest version of the tmle3mopttx package (installable via devtools::install_github("tlverse/tmle3mopttx")). Also @podTockom notes that the exercise has been updated so that missing values in baseline covariates are no longer considered (even though this should no longer be an issue when using the latest version of the package).
We've also updated the book to use this latest version of tmle3mopttx automatically, which it was not doing before. I'll close this issue but feel free to report if there are any other issues that come up.


Add PRs to changelog

Huh, where'd prow go?

/lgtm
I'll violate my 'no merging co-workers patches' rule for something this simple.


US infra article

This PR is obsolete, the changes were done directly in the documentation repo here.


⚠ QEMU (homebrew) was broken on Intel: [hostagent] Driver stopped due to error: "signal: abort trap" (or "exit status 255") ... QEMU has already exited

Update (Aug 27, 2023): The issue is solved again in 8.1.0_1 (https://github.com/Homebrew/brew/pull/15903 , ~https://github.com/Homebrew/homebrew-core/pull/140596~ https://github.com/Homebrew/homebrew-core/pull/140643). Run brew reinstall -f --force-bottle qemu to install the updated v8.1.0 bottle.
Update (Aug 23, 2023): This seems to be broken again in v8.1.0  😞 (https://github.com/Homebrew/homebrew-core/issues/140244) . See the Workarounds below.
Update (Aug 14, 2023): The issue is now solved in https://github.com/Homebrew/homebrew-core/pull/139492 .
Run brew reinstall -f --force-bottle qemu to install the updated v8.0.4 bottle.

Homebrew bottle of QEMU v8.0.4 (Intel) ~is~ was broken due to a signing issue: https://github.com/Homebrew/homebrew-core/pull/139409
$ limactl start
...
[hostagent] Driver stopped due to error: "signal: abort trap"
...
[hostagent] QEMU has already exited
...

$ qemu-system-x86_64 -accel hvf
qemu-system-x86_64: -accel hvf: Unknown Error
Abort trap: 6

$ codesign --verify /usr/local/Cellar/qemu/8.0.4/bin/qemu-system-x86_64
/usr/local/Cellar/qemu/8.0.4/bin/qemu-system-x86_64: invalid signature (code or signature have been modified)
In architecture: x86_64

(The error message can be also [hostagent] Driver stopped due to error: "exit status 255")
Workarounds
Option 1: Downgrade QEMU to v8.0.3
brew uninstall qemu
curl -OSL https://raw.githubusercontent.com/Homebrew/homebrew-core/dc0669eca9479e9eeb495397ba3a7480aaa45c2e/Formula/qemu.rb
brew install ./qemu.rb

Option 2: Install QEMU from the source
brew uninstall qemu
brew install --build-from-source qemu

Option 3: Sign the QEMU binary locally
Lima v0.17.2 shows a prompt to suggest applying this workaround.
cat >entitlements.xml <<EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>com.apple.security.hypervisor</key>
    <true/>
</dict>
</plist>
EOF

codesign --sign - --entitlements entitlements.xml --force /usr/local/bin/qemu-system-$(uname -m | sed -e s/arm64/aarch64/)

Thanks to  @z0sen for reporting this in https://github.com/abiosoft/colima/issues/777

Lima project probably needs to have an optional QEMU installation tarball (in a different project, like alpine-lima).

The issue is now solved:

https://github.com/Homebrew/homebrew-core/pull/139492

Still seeing this when I run colima start after running brew reinstall -f --force-bottle qemu:

time="2023-08-16T11:22:47-04:00" level=warning msg="QEMU binary "/Users/mossity/.colima/_wrapper/3a9197e1ca3cd2da076da2b473d7a7eb118e2cca/bin/qemu-system-aarch64" is not properly signed with the "com.apple.security.hypervisor" entitlement" error="binary "/Users/mossity/.colima/_wrapper/3a9197e1ca3cd2da076da2b473d7a7eb118e2cca/bin/qemu-system-aarch64" seems signed but lacking the "com.apple.security.hypervisor" entitlement"
time="2023-08-16T11:22:47-04:00" level=warning msg="You have to sign the QEMU binary with the "com.apple.security.hypervisor" entitlement manually. See https://github.com/lima-vm/lima/issues/1742 ."

@benmoss

ARM Mac or Intel Mac?
Does limactl start (not colima start) print the same warning? If limactl start does not print a warning, it is an issue of colima.
Output of  codesign --display --entitlements - --xml /opt/homebrew/Cellar/qemu/8.0.4/bin/qemu-system-x86_64  ? (qemu binary path might be different)

I'm on ARM
limactl start doesn't print any warning, says "QEMU binary "/opt/homebrew/bin/qemu-system-aarch64" seems properly signed with the "com.apple.security.hypervisor" entitlement
codesign --display ... shows that it has the hypervisor entitlement

So it looks like it is a colima problem. Feel free to ignore!

The binary seems broken again with the 8.1.0 bottle 😞

https://github.com/Homebrew/homebrew-core/pull/140237

Besides the bloat, this seems like another good reason to not use Homebrew for the QEMU installation.

I guess we should also rush to make vz default?
vz also had a different incompatibility issue though (https://github.com/lima-vm/lima/issues/1577).

Adding a check for the entitlement to the brew formula would probably also be a good idea, to stop re-re-regressions from happening again in the future

Adding a check for the entitlement to the brew formula would probably also be a good idea, to stop re-re-regressions from happening again in the future

Already done in Lima v0.17.2:

https://github.com/lima-vm/lima/pull/1743

(The Y/n prompt defaults to n when --tty=false though)

The issue is solved again in 8.1.0-1 (https://github.com/Homebrew/brew/pull/15903 , https://github.com/Homebrew/homebrew-core/pull/140596).
Run brew reinstall -f --force-bottle qemu to install the updated v8.1.0 bottle.

@janvda Using Lima without Colima may work as a workaround:
limactl start template://docker
Removing ~/.colima/_wrapper may work too.

Hi,
I just noticed today after coming back from holidays that Colima is broken.
I am on a macbook pro M1. I have applied the same steps as @janvda to no avail.
This issue should be reopened

I am on a macbook pro M1

You are hitting something different (maybe https://gitlab.com/qemu-project/qemu/-/issues/1864 ), as the OP is about Intel.

have applied the same steps as @janvda to no avail.

FYI The following workaround worked for me on my macbook pro with intel processors:

https://github.com/abiosoft/colima/issues/792#issuecomment-1703314392

@edw-eqix Beautiful - this is the current workaround until the maintainers get this sorted

I've just tried it now on my M1 mac, and this is the current output with the most recent brew install --HEAD qemu:
> "QEMU binary \"/Users/risi/.colima/_wrapper/3a9197e1ca3cd2da076da2b473d7a7eb118e2cca/bin/qemu-system-aarch64\" is not properly signed with the \"com.apple.security.hypervisor\" entitlement" error="binary \"/Users/risi/.colima/_wrapper/3a9197e1ca3cd2da076da2b473d7a7eb118e2cca/bin/qemu-system-aarch64\" seems signed but lacking the \"com.apple.security.hypervisor\" entitlement"
> You have to sign the QEMU binary with the "com.apple.security.hypervisor" entitlement manually. See https://github.com/lima-vm/lima/issues/1742 .

Thanks for the response, my bad, was on the wrong repo :)

From my slightly-cleaned-up-for-display error below, something seems to be checking whether the wrapper itself is signed.

After signing the actual binary with the following command:
codesign --sign - --entitlements entitlements.xml --force /usr/local/bin/qemu-system-$(uname -m | sed -e s/arm64/aarch64/)

I also signed the wrapper with something like:
codesign --sign - --entitlements entitlements.xml --force ~/.colima/_wrapper/4e1b408f843d1c63afbbdcf80c40e4c88d33509f/bin/qemu-system-x86_64

and it worked. Now It shows me message like this:
INFO[0010] starting ...                                  context=vm
> Using the existing instance "colima"
> QEMU binary "/Users/mutant/.colima/_wrapper/4e1b408f843d1c63afbbdcf80c40e4c88d33509f/bin/qemu-system-x86_64" seems properly signed with the "com.apple.security.hypervisor" entitlement
> [hostagent] Starting QEMU (hint: to watch the boot progress, see "/Users/mutant/.lima/colima/serial*.log")
> SSH Local Port: 60997
> [hostagent] Waiting for the essential requirement 1 of 5: "ssh"

As above, This hint (Option 3, local signing), worked for me. Intel Mac, Sonoma 14.1.


Allow STRICT mode in the knative-serving namespace

Right now the official documentation recommends setting PERMISSIVE mode on the knative-serving namespace. However it doesn't offer any explanation as to why.
When strict mode is enabled I notice that the autoscaler no longer seems to scale my instances up. However this is required to build a full chain of trust from the gateway -> activator -> workload.
Is there plans to support strict mode on the serving namespace in the future?

Right now the official documentation recommends setting PERMISSIVE mode on the knative-serving namespace.

Yeah that's surprising. The only valid reason to have that (I think) is incase you have Knative Services in a namespaces that doesn't have mTLS/sidecars enabled.
Funny enough we don't apply such a PeerAuth in our testing - we just have PeerAuth to allow the k8s api to invoke the webhooks.

When strict mode is enabled I notice that the autoscaler no longer seems to scale my instances up.

What's the default mode if it's not set - isnt' it STRICT?

Funny enough we don't apply such a PeerAuth in our testing - we just have PeerAuth to allow the k8s api to invoke the webhooks.

This is likely because your mesh default is PERMISSIVE. For me the activator and autoscaler definitely can not communicate anymore if STRICT is enabled. Injection is enabled in all 3 namespaces (gateway, knative-serving, and the workload namespace)

What's the default mode if it's not set - isnt' it STRICT?

It depends on your mesh config - by default it is PERMISSIVE.

Okay interestingly enough, after adjusting the PeerAuthentication mode I just needed to kick all the autoscalers. They came back up fine and can scale with STRICT mode.
So seems like when changing the mode the websocket connection breaks and can't reconcile itself.

For me the autoscaler definitely can not communicate properly anymore if STRICT is enabled.

That's odd - because they should have sidecars enabled

We use STRICT in downstream, works as expected. Make sure you have istio sidecars injected in Activator and in Autoscaler pod to make everything work.


ccmlib should not always terminate cql statements with a ';'

I am running into an issue that ccmlib assumes all input will be terminated by a ;. This isn't true in case of lets say comments or multi-line comments. ccmlib should optionally take a terminator to avoid this issue.
Here's an example of a failure:
self.node1.run_cqlsh(
   """/* multiline
    *
    * comment */
    """)

Attached patch fixes the issue. @snazy @nastra could you please review this PR?

thank you.


as: Remove alloc. Minor refactorings

Hi, @MaxGraey!
Currently, the runtime expects an allocation function called alloc to be exported by the module.
https://github.com/deislabs/wasi-experimental-http/blob/fe268e5fe5e180e06fbe5f826e4f335dc1ea5b21/crates/wasi-experimental-http-wasmtime/src/lib.rs#L11
This is not ideal, and obviously a workaround, so I'm open to suggestions - essentially, the runtime expects to be able to allocate buffer arrays into the module's linear memory, so if we could reuse the AssemblyScript functions that do that, it would be great.

Also see #32.
Basically, we should find a consistent way for the runtime to allocate memory into the guests' linear memory regardless of the implementation, and I'm open to suggestions.

I see, thanks. So instead exporting alloc you could reuse standard __alloc (unmapaged) or __new (managed) which exposed by --exportRuntime flag.
__alloc: https://www.assemblyscript.org/garbage-collection.html#custom-runtime
__new: https://www.assemblyscript.org/garbage-collection.html#runtime-interface
it uses as __alloc(len, 0) (this required __free for avoid mem leak) or __new(len, 0) (this managed and will be collected by incremental GC)


Version 0.4.0 Yanked

I see that version 0.4.0 has recently been yanked from crates.io, but I don't see anything stating why.  Was there a security vulnerability?  0.3.0 hasn't been yanked; is it still safe to use?

Sorry, I've been a little behind in updating this library.
The reason I yanked 0.4.0 was because I was going to update the dependency to my secret-service library. Unfortunately, the bug I fixed was not actually fixed (turned out to be unfixable because of a bug encoding empty strings in rust-crypto), so I yanked that version of ss, and then also keyring. I waited a bit to think about what I should do about it, but then got caught up in other things.
On the plus side, the yank was not because of security vulnerabilities. It just means there's been inconsistent handling of empty strings as input across different OS. (something which will continue until rust-crypto gets updated).
Thanks for this reminder, though. Other updates have been made to both keyring and secret-service which warrant publishing, which I'll do shortly.

Was resolved by ecbdffd4787c2dc758f62f95141df7284fb77770


Fix: Adjustments to upgrade docs

Ran sqlmesh ui tests and looks good to me. https://app.qase.io/public/report/b22453ec7f3d58f36e46dbbf59b2900bf6002139


Load css for colorizing an element or a string, without an editor.

As clearly seen on the playground:
https://microsoft.github.io/monaco-editor/playground.html#creating-the-editor-syntax-highlighting-for-html-elements
The element is "colorized", but it lacks the appropriate styles to show said colorization. This is due to the fact that without an editor there is no call to StandaloneThemeServiceImpl.registerEditorContainer, which creates the monaco-colors style.
Allowing us to some how call the function to generate said style will also allow us to utilize the syntax highlighting feature of monaco-editor in places where we only want to colorize code.

Is there any plan on making it possible? Without this feature, monaco.editor.colorize is useless without the actual editor in the same page.

Note: one can create a page with the editor, copy the css, add said css to whatever page that uses monaco.editor.colorize. The only downside to said method is that one must remember to do said thing any time the editor is updated, incase something in the css is added or changed.

:+1: Duplicate of https://github.com/microsoft/monaco-editor/issues/1828


python312Packages.tencentcloud-sdk-python: 3.0.1238 -> 3.0.1239

Diff: https://github.com/TencentCloud/tencentcloud-sdk-python/compare/refs/tags/3.0.1238...3.0.1239
Changelog: https://github.com/TencentCloud/tencentcloud-sdk-python/blob/3.0.1239/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 344369 run on x86_64-linux 1

4 packages built:

python311Packages.tencentcloud-sdk-python
python311Packages.tencentcloud-sdk-python.dist
python312Packages.tencentcloud-sdk-python
python312Packages.tencentcloud-sdk-python.dist


Interactive option to select directories if datadir/outputdir are not provided or do not exist

Is your feature request related to a problem? Please describe.
For new R users, the first challenge they find is usually the definition of the directories. It may be frustrating for them not being able to use GGIR just because of this.
Describe the solution you'd like
I think providing the opportunity to interactively choose files/directories with utils::choose.files and utils::choose.dir would facilitate the introduction to GGIR. But I'm not sure if this should be extended for the definition of the log paths (sleeplog, activity log, data cleaning file...).

Option 1:
As described above with pop-up window to select path.
Option 2:
Document better how to specify paths.
Option 3:
Document how to use
datadir = utils::choose.dir()
GGIR(data = datadir, ...)


The right-click menu tool is gone? How to dump database?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
After the update version [<IP_ADDRESS>207091910], the tool is gone, the dump database and restore database are gone, and the toolbar needs to be restored
Describe the solution you'd like
A clear and concise description of what you want to happen.
Recovery tool related functions
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Recovery tool related functions
Additional context
Add any other context or screenshots about the feature request here.

previous version

download from microsoft store.

Hello，Both are empty.

I have the same problem, have you found a solution? Thanks!

Hello all.
DBeaver was republished to the Windows Store.
Can you please check it now?

Hello @LonwoLonwo.
I uninstalled and re-downloaded it, but it still doesn't work.
Is the latest version not yet distributed in the Windows App Store?

Thanks for the answer.

I'm closing this ticket as a duplicate of #17132
The fix will be available soon.


are you not using netvlad as your clustering method?

https://github.com/BIT-MJY/CVTNet/blob/3b0543e0f58495bb120957ae94d2ba1314f33c65/modules/netvlad.py#L6
you did not perform clustering operation in class netvladloupe.
may i ask why your clustering can achieve the same performance as netvlad?

Thanks for your interest in our work! All the parameters in the NetVLAD module are learnable via back-propagation. You do not need to cluster the input features explicitly due to the differentiable operations. Please refer to Eq.4 in NetVLAD paper.

Think you for your help.


Error in ion-input

Version Angular: 7.2.0
Version Ionic: 4
The best currency autocomplete I found. I use in angular projects and it's pretty good, though, I'm trying to use it in an Ionic 4 project and the following error is occurring when I add the directive in an ion-input:
XxxxxComponent.html: 36 ERROR Error: More than one custom value accessor matches form control with unspecified name attribute
     at _throwError (forms.js: 2144)
     at forms.js: 2202
     at Array.forEach ()
     at selectValueAccessor (forms.js: 2191)
     at new FormControlName (forms.js: 5782)
     at createClass (core.js: 22062)
     at createDirectiveInstance (core.js: 21931)
     at createViewNodes (core.js: 23157)
     at createEmbeddedView (core.js: 23065)
     at callWithDebugContext (core.js: 24079)
Do you have any suggestions to solve?

facing the same problem here.

Same here ✋

Same here ✋

same here, did anyone find a way around this?

any update on this?  We're trying to do the same, but are getting this same error when used on an ion-input.

Sorry guys, but I don't intend to support the Ionic. Unfortunately, I don't have available time for this.


Fill minn and minnctapp gaps

Related to #929
minn: Between Aprill 11, 2024 and July 30, 2024 we have 0 opinions. Missing around 35 opinions
minnctapp: Between April 9, 2024 and July 1st, 2024 we have 0 opinions

While scrolling through the site to see roughly how many opinions we were missing, I just noticed that older opinions publish citations. I wil update the scrapers to pick them up, which will also be used on #858

./manage.py cl_back_scrape_opinions --courts juriscraper.opinions.united_states.state.minn --backscrape-start=04/10/2024 --backscrape-end=08/01/2024 --verbosity 3

The backscrapers don't seem to be working on the live server; they return zero items


Extremly long build time for pinocchio3-preview

Hi,
While trying out hte new pinocchio3-preview branch I observed that the build time is extremely long. To build the package using catkin build pinocchio it takes me 1h and 15 min to build compared to the about 20 seconds (excluding hpp-fcl) it takes me to build the current master branch. I found this stark difference quite strange.
I was wondering if you experienced similar build times? Are you aware of a solution to shorten the build time?
FYI I compiled on a Ubuntu 20.04 LTS system with a AMD Ryzen Pro 7.
I hope you don't mind my question and any help is appreciated.
Best, Manuel

I'm very surprised by your 20 seconds. It seems there is no compilation at all as the package is already compiled. You should start from scratch.
Concerning Pinocchio 3, we have added a lot of new features, among them extended Python bindings, constrained dynamics support, etc. with a lot of additional unit testings to validate implemented algorithms.
My first advice would be to deactivate the compilation of unit tests.

By the way, we are adding the template instantiation within the main library to really shorten the whole compilation timings of the project.

I achieve the 20s build time when I first clean my catkin workspace using catkin clean followed by catkin build pinocchio.
Could it be that the preinstalled robotpkg-pinocchio and robotpkg-py38-pinocchio apt packages (which i have installed) contain most of the already compiled components for building pinocchio master?
I will give the deactivation of the unit tests a try.
Thanks for your help and continued work on this project. It's great! I am really looking forward to see where pinocchio will go in the new year.
A la nouvelle année!

I do not know how catkin operates, but they might be a catch mechanism behind it.
Catkin can also install the binary version built on the building farm of ROS.
PS: thanks for the kind and french thought.

Hi @manumerous
Happy New Year!
Is it possible that you are using ccache [first hunch] or not correctly clearing the package? It definitely won't pick up any binary installed Pinocchio versions, whether robotpkg or ROS, to reduce buildtime. You can get rid off the ccache cache by removing ~/.ccache for more reliable compile timings from scratch, or deactivating ccache temporarily.
catkin build will build Pinocchio in its default CMake configuration, i.e. with unittests and examples activated and should take quite some time due to that (I'm seeing ~20min with Clang with unittests off I believe). To reduce the time, you can either set the options via CMake args with catkin config --cmake-args -DBUILD_EXAMPLES=OFF -DBUILD_TESTING=OFF for all projects or edit the CMakeLists.txt option settings in Pinocchio. I also recommend setting Clang as the compiler, which can also be done for all packages with catkin config --cmake-args -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang.
Best wishes,
Wolfgang

Thank you for your comments. They were rally helpfull!


Create endpoints for issue and patch count

We should add the issue and patches count to the project Metadata.
This will allows us to query the patches and issue count, without fetching all patches or issues.
To have a more complete picture we could also return an object with the following structure:
{
  "issues": {
    "open": 9,
    "closed": {
        "solved": 3,
        "other": 4
    }
  }
}

Has been closed by #166


refactor: update project listing depending on the dev mode

Description
Refactor the dev badge on the app card and project listings depending on the developer mode status.
Type of change

[x] New feature (non-breaking change which adds functionality)

Fixes/Resolves (Optional)
Closes #441
Closes #440
Checklist:

[] I have performed a self-review of my own code
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

Additional Information (Optional)
Slack conv

Sorry I didn't explain this very well, I wanted something different. See Slack conversation


Remote Tunnel Extension Issue: Client not connecting to Remote server running on Raspbian 64-bit OS

Type: Bug
remote server: Raspbian 64-bit OS (uname: 6.1.21-v8+).
client: Ubuntu 22
I have tried running the tunnel both with 'code tunnel' and also through the GUI.      Command { std: "/home/pi/.vscode-cli/server-stable/bin/704ed70d4fd1c6bd6342c436f1ede30d1cff4710/bin/code-server" "--connection-token=rntumTzoDPjkW1gbOKX9yFJ7Mk7GroRB_KGHI_MnhUk" "--accept-server-license-terms" "--start-server" "--enable-remote-auto-shutdown" "--socket-path=/tmp/vscode-server-dd63b77d-6dc1-4721-8c4a-3a6e55f645fd", kill_on_drop: false }
[2023-04-13 10:22:16] trace [rpc.8] [codeserver.9] /home/pi/.vscode-cli/server-stable/bin/704ed70d4fd1c6bd6342c436f1ede30d1cff4710/bin/code-server: 12: /home/pi/.vscode-cli/server-stable/bin/704ed70d4fd1c6bd6342c436f1ede30d1cff4710/node: not found
[2023-04-13 10:22:16] debug [russh::client::encrypted] channel_close
[2023-04-13 10:22:16] debug [tunnels::connections::relay_tunnel_host] no more connections on host relay client session, ending
[2023-04-13 10:22:16] debug [rpc.8] closing socket reader: EOF
[2023-04-13 10:22:16] info [rpc.8] Disposed of connection to running server.
[2023-04-13 10:22:16] debug [rpc.8] Closing connection: EOF

Same here.

Thanks for the logs. This looks like it may have been some kind of corrupt download, which we now guard better against. Please try this again with the VS Code Insiders version of the CLI, or just the new stable CLI which will be released tomorrow morning PST.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

confirming that running vscode_cli_alpine_arm64_cli.tar,gz (code-insiders) on Raspberry Pi aaarch64 fixed the issue


Fix backend config params

Terraform seems to require that backend config arguments are passed using the syntax -backend-config=key=value. That is, with an equals sign as a separator. The syntax we use elsewhere with a space as a separator (e.g., -var key=value) doesn't seem to work for backend config. Added example + test to verify too.

I guess? Or maybe the behavior changed in some recent version of Terraform? Not sure.

Thanks for the review! Merging now.


Add autocomplete to panels, add parse command to app analytics

Signed-off-by: Eugene Lee<EMAIL_ADDRESS>Description

Add autocomplete to panels
Add parse to autocomplete in app analytics

Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #529 (f7aec1a) into main (cdb45e0) will increase coverage by 18.41%.
The diff coverage is n/a.

:exclamation: Current head f7aec1a differs from pull request most recent head 2511408. Consider uploading reports for the commit 2511408 to get more accurate results

@@              Coverage Diff              @@
##               main     #529       +/-   ##
=============================================
+ Coverage     54.21%   72.62%   +18.41%
  Complexity      272      272
=============================================
  Files           235       38      -197
  Lines          7575     2130     -5445
  Branches       1555      236     -1319
=============================================
- Hits           4107     1547     -2560
+ Misses         3274      421     -2853
+ Partials        194      162       -32

Flag
Coverage Δ

dashboards-observability
?

opensearch-observability
72.62% <ø> (ø)

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

Impacted Files
Coverage Δ

...rds-observability/common/constants/autocomplete.ts

...y/public/components/common/search/autocomplete.tsx

...lic/components/common/search/autocomplete_logic.ts

...lic/components/custom_panels/custom_panel_view.tsx

...c/components/explorer/visualizations/datapanel.tsx

...ts/explorer/visualizations/drag_drop/providers.tsx

...analytics/components/dashboard/dashboard_table.tsx

.../helpers/custom_modals/reporting_loading_modal.tsx

...onfig_editor/config_controls/config_data_links.tsx

...ytics/components/common/filters/filter_helpers.tsx

... and 187 more

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 cdb45e0...2511408. Read the comment docs.


Timerun diffs are broken while following

They print correctly for the followed client though

Possibly due to getSpectators function deriving clientNum from ps.clientNum.
https://github.com/etjump/etjump/blob/124279a14b3cc5fee98f10c32b0c203a9f4df16b/src/game/etj_utilities.cpp#L33-L57


Themelist fixes/enhancements (better style/speed/clarity).

There was an unnecessary loop in the onchange event, and the build_themes function didn't exactly match the project style (it used single quotes). There was also no reason for themelist to be global. This patch doesn't change the end result, but provides greater clarity and speed (when selecting a new theme after load) and removes the unneeded global.
You were so great to accept my patch the first time, but when I noticed these things later it bothered me. I don't want to be a pest, so I'll just offer up this little fix and let you get back to work.

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks for the update!


Test using fail in subset for custom message

Would it be possible to change this test to check the actual content of the custom message is correct? The current dies-ok version takes the 1 is not even string as test description; not the content of the death to check against. For those purposes, there's throws-like:
throws-like { fail "foo" }, Exception, :message<foo>,
    'failure gave correct custom message';

Oh... duh... yeah, I'll fix it.

Also, you forgot to adjust the plan at the top of the file :smile_cat:

Fixed the plan and using throws-like now. Thx for the review.

Thanks a lot.


dotnet user-jwts /1

Contributes to #26155
Internal review URL

@captainsafia please review. Note, my instructions worked last week. Today when I test I get the following error in the curl console:
HTTP/1.1 401 Unauthorized
Content-Length: 0
Date: Wed, 27 Jul 2022 03:09:35 GMT
Server: Kestrel
WWW-Authenticate: Bearer error="invalid_token", error_description="The signature key was not found"

And there's no logging information to help out.


CASMPET-5217 Bump cray-kafka-operator to 0.4.2

Summary and Scope
This bumps cray-kafka-operator to 0.4.2, which includes the CVE-2021-44228 fix.
Issues and Related PRs

Resolves CASMPET-5217

Testing
Tested on:

Virtual Shasta

Test description:
Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why? N/A
Was upgrade tested? If not, why? Y
Was downgrade tested? If not, why? Y
Were new tests (or test issues/Jiras) created for this change? N
Risks and Mitigations
Pull Request Checklist

[X] Version number(s) incremented, if applicable
[ ] Copyrights updated
[X] License file intact
[X] Target branch correct
[X] CHANGELOG.md updated
[X] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

Wrong ticket.


chore(action): no more node 22.10.0 tests

Applied mkpr on .github/workflows/ci.yml
sed /- 22.10.0/d

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 22.976%

Totals

Change from base Build<PHONE_NUMBER>8:
0.0%

Covered Lines:
102

Relevant Lines:
453

💛  - Coveralls


Check for ContentType and Permission models before migration

Hi!
We're using wagtail in a large django project and recently ran into this issue preventing us from upgrading to the latest version of wagtail. When we run migrations for our app using multiple database we run into
relation "auth_permission" does not exist
LINE 1: ...ntent_type_id", "auth_permission"."codename" FROM "auth_perm...

For all databases except the default one. I've largely copied what django does https://github.com/django/django/blob/f9e9526800c921ae393ff58826daed51587b1727/django/contrib/auth/management/init.py#L65 in  https://code.djangoproject.com/ticket/24075 and bail early if the ContentType or Permission models don't exist
This prevents create_extra_permissions from querying or creating ContentType or Permission objects if the models cannot be found. When using multiple databases which do not have the auth_permission table create_extra_permissions will cause migrate to fail.
This is similar to https://code.djangoproject.com/ticket/24075.

Fixes #...
Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Thanks @joetsoi! Looks like this might be the same issue as #11173 (but will keep this PR open too as it's more complete).

Merged in c9b3d9e15b79019fb1d44681d02fd091369dad3b (main) / 36f1c05a59 (stable/5.2.x).


Using workspaces + remote s3 storage with tflocal combined w/ "real" AWS S3 state storage?

Is it possible to use s3 backend storage with both a local workspace, and other workspaces that are actually real, shared storage on AWS s3?
The goal here is to easily test something locally, then test / deploy to "real" dev/staging/prod.
It looks like tf detects the change in the endpoints as a backend change, (backend info is stored in .terraform/terraform.tfstate), and even if you just use the single, default workspace, it won't let you change back and forth between tflocal & terraform (w/no overrides).
Is there any kind of documentation / posts on suggested developer workflows?

Hi @mbarr-hrp,
Thanks for reaching out.
Do I understand it right that you'd like to use a real S3 backend and run terraform/tflocal to switch back and forth between a mocked local and a live dev/stage/prod workspace while your statefile is stored remotely?
If so it's not trivial as tflocal out of the box not supporting workspace separation.
The assumption is that the users are using tflocal locally and the state file is not stored remotely, maximum in Localstack as a test.
So unfortunately no documented resource for such use case however it can be a good blog post, I keep it in mind! 🙏
And from this point down it's only my opinion how to resolve your situation, so tl;dr sorry in advance 🙂
By taking leverage of Terraforms override files behaviour (the one we use with tflocal too), you can always override tflocal's behaviour by defining desired resources, backends, outputs.
You can find more information about this in the official Terraform docs here.
Relevant parts:

about file precedence:

If more than one override file defines the same top-level block, the overriding effect is compounded, with later blocks taking precedence over earlier blocks. Overrides are processed in order first by filename (in lexicographical order) and then by position in each file.

about backends:

The presence of a block defining a backend (either cloud or backend) in an override file always takes precedence over a block defining a backend in the original configuration. That is, if a cloud block is set within the original configuration and a backend block is set in the override file, Terraform will use the backend block specified in the override file upon merging. Similarly, if a backend block is set within the original configuration and a cloud block is set in the override file, Terraform will use the cloud block specified in the override file upon merging.

Regarding an easy switch between tflocal and terraform depeding on the used workspace, I'd control it with a small shell script and depending on the current workspace I'd set env variables and use the right binary.
Hope this helps, if you have any question please let us know.

The answer turned out to be to just do tflocal init -reconfigure, or tf init -reconfigure, as needed.


Improved CLI and Python library output

@friskluft Any reason we need all the #ifdef WITH_PYTHON_H conditionals? Why not just throw an error and catch it in main or somewhere and print out to cerr? Then the python code will operate naturally and you don't need all the redundant code.

Top reasons:

preferring to keep the stable and tested workflow logic based on boolean success/error returned results
following a rule to avoid cross-module signaling by means of exceptions


Added various security features

Added helmet for security http headers.
Added rate limiter to receive 100 requests per hour from a particular IP address.
Added mongo sanitize for data sanitization against noSQL query injection
Added xss for data sanitization against XSS.
Please review and if any changes required let me know.
Thank you.
For issue #51

well done!


project: add project status conditions

This matches the upstream API.
Upstream: https://github.com/kubernetes/kubernetes/pull/73405

/lgtm


Add "dyna" license increment in the license mechanism

Description of the feature
For pyDPF for ls-dyna, user having just dyna solver license may not have the compatible license increments. We need to enable increment 'dyna' as well.
Steps for implementing the feature
No response
Useful links and references
No response

@rlagha, @anslpa

Hi @rajesh1359! Thank you for pointing this out!
We also noticed that the license increment advanced_meshing should be available with the LS-Dyna solver, and this one is accepted by DPF.
Users having LS-Dyna should have access to this increment (if I understood correctly) and DPF should then work using it. Did you raise the issue based on an actual impossibility to use DPF, or is it due to reading the list of accepted license increments in the documentation?

Closing this issue as fixed after checking on my end


feat: authentication flow

Description
This PR introduces authentication to the frontend of NMS. The user will either be redirected to the initialize endpoint or login endpoint if they haven't logged in. Admin users have access to the users panel, which allows them to create, delete or update the password of existing user accounts.
For testing, please use the webconsole version that includes the authentication changes.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code.
[x] I have made corresponding changes to the documentation.
[x] I have added tests that validate the behaviour of the software.
[x] I validated that new and existing unit tests pass locally with my changes.
[x] Any dependent changes have been merged and published in downstream modules.

I am having the following error on a fresh deployment:

Initialize admin user : username : 1 , password : Admin123
Log in using correct credentials
The NMS briefly shows the configuration page and the shows again the login page.

Expected behavior: after successfully log in, i can access the configuration page

Hello @patriciareinoso I accidentally closed this today, I have a new PR up at #659, please make your comments there.

I am having the following error on a fresh deployment:

Initialize admin user : username : 1 , password : Admin123
Log in using correct credentials
The NMS briefly shows the configuration page and then shows again the login page.

Expected behavior: after successful log in, i can access the configuration page
2024-10-25T13:30:49.723Z [nms] 2024-10-25T13:30:49.723Z	INFO	logger/logger.go:92	| 200 |     <IP_ADDRESS> | GET     | /status | 	{"component": "WebUI", "category": "GIN"}
2024-10-25T13:31:38.478Z [nms] 2024-10-25T13:31:38.478Z	INFO	logger/logger.go:92	| 200 |     <IP_ADDRESS> | POST    | /login | 	{"component": "WebUI", "category": "GIN"}
2024-10-25T13:31:38.482Z [nms] 2024-10-25T13:31:38.482Z	INFO	logger/logger.go:92	| 200 |     <IP_ADDRESS> | GET     | /index.txt?_rsc=1k3ja | 	{"component": "WebUI", "category": "GIN"}
2024-10-25T13:31:38.488Z [nms] 2024-10-25T13:31:38.487Z	INFO	logger/logger.go:92	| 200 |     <IP_ADDRESS> | GET     | /network-configuration.txt?_rsc=1iwkq | 	{"component": "WebUI", "category": "GIN"}
2024-10-25T13:31:38.522Z [nms] 2024-10-25T13:31:38.522Z	INFO	configapi/api_default.go:163	Get all Network Slices	{"component": "WebUI", "category": "WebUI"}
2024-10-25T13:31:38.523Z [nms] 2024-10-25T13:31:38.523Z	INFO	logger/logger.go:92	| 200 |     <IP_ADDRESS> | GET     | /config/v1/network-slice | 	{"component": "WebUI", "category": "GIN"}
2024-10-25T13:31:38.819Z [nms] 2024-10-25T13:31:38.819Z	INFO	logger/logger.go:92	| 200 |     <IP_ADDRESS> | GET     | /login.txt?_rsc=b1min | 	{"component": "WebUI", "category": "GIN"}
2024-10-25T13:31:38.847Z [nms] 2024-10-25T13:31:38.846Z	INFO	logger/logger.go:92	| 200 |     <IP_ADDRESS> | GET     | /status | 	{"component": "WebUI", "category": "GIN"}

I could not recreate this.


Incoming simple shipments' id is the same the as set by the Sender. They should be unique

To avoid conflicts (even if unprobable) add a sender prefix to incoming shipments ID's

Looks good, but add a separator character between the sender id and the shipment id. It's a bit redundant, but if anyone ever needs to parse it, is makes that easy. after that you can close the issue

fix on https://github.com/PharmaLedger-IMI/fgt-workspace/commit/d8ae19506fd64294442bf069e47e205fa4915c2a


Fix: handle empty project overview

Card: 848
Fixing the bug in the card lead to the undo changes button not working. It was calling the undoFormChange mutation but would trigger an update with the previous form data, leaving you in the same state as before clicking undo. Fixed by having the function set new_form_data to {} rather than null::jsonb.
This lead to the tasklist status for project overview showing in progress rather than not started on an empty form. Fixed by adding a case to get_form_status specifically for this scenario.

New branch made to properly handle sqitch reworks


[BUG] Doc step not working on RHEL 7.9 workstation for setting up a CRC remote server

General information

OS: RHEL 7
Hypervisor: KVM
Did you run crc setup before starting it - yes
Running CRC on: Baremetal-Server

CRC version
# Put `crc version` output here

$ ./crc version
CodeReady Containers version: 1.25.0+0e5748c8
OpenShift version: 4.7.5 (embedded in executable)
CRC status
# Put `crc status --log-level debug` output here

Not required for the issue i am hitting, however here is the status
$ ./crc status
CRC VM:          Running
OpenShift:       Running (v4.7.5)
Disk Usage:      15.14GB of 32.74GB (Inside the CRC VM)
Cache Usage:     13.4GB
Cache Directory: /home/node4/.crc/cache
CRC config
# Put `crc config view` output here

$ ./crc config view

consent-telemetry                     : no
memory                                : 92160
Not required for the issue i am hitting

Host Operating System
# Put the output of `cat /etc/os-release` in case of Linux
# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows

[node4@tools-node4 ~]$ cat /etc/os-release
NAME="Red Hat Enterprise Linux Workstation"
VERSION="7.9 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Workstation"
VARIANT_ID="workstation"
VERSION_ID="7.9"
PRETTY_NAME="Red Hat Enterprise Linux Workstation 7.9 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.9:GA:workstation"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.9
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.9"
[node4@tools-node4 ~]$
Steps to reproduce
Following https://code-ready.github.io/crc/#setting-up-remote-server_gsg to setup the crc remote server.

At step 2 of the doc

$ dnf install haproxy policycoreutils-python-utils
Last metadata expiration check: 15:11:53 ago on Mon 26 Apr 2021 07:54:32 PM IST.
Package haproxy-1.5.18-9.el7.x86_64 is already installed.
No match for argument: policycoreutils-python-utils
Error: Unable to find a match: policycoreutils-python-utils
[data2@tools-data2 ~]

NOTE: I can find a thread of discussion regarding the issue i am hitting. As per the thread, one suggestion is migrating the os to rhel 8.2 and other less loud suggestion is use the RHEL 7.9. I tried the the steps given in https://code-ready.github.io/crc/#setting-up-remote-server_gsg on RHEL 7.9 but step 2 did not work
Expected
Step should work
Actual
Given steps are not working
Logs
Before gather the logs try following if that fix your issue
$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug  on http://gist.github.com/ and post the link in the issue.

Error: Unable to find a match: policycoreutils-python-utils

While we suggest 7.5 or higher is supported, I am not sure if this process is regularly tested. We know it works on Fedora and RHEL 8.x for instance, but this package seems to be missing... but relevant?
Please continue installing dnf install haproxy and ignore the policycore package (or at least install policycoreutils-python).
Does that work?

Yes, policycoreutils-python worked. Thanks!

@robin-owen @adrianriobo @jsliacan  is this up to date? Might have to retest this on RHEL 7.x ... and consider how to make sure this becomes a tested scenario; when in docs we need to 'support' it.

Not sure if this is actually is needed

It seems this is a dependency for semanage and the library name has change from RHEL 7.X (policycoreutils-python) to RHEL 8.X (policycoreutils-python-utils). So the question around the docs is if we want to cover every specific supported version?
On the other hand afaik there is no e2e test covering this. And probably it would be great to have that kind of test (setting remote access + setting client to access it, then operate the cluster from the client) As we already know this is a user story which clients are implementing

yum install /usr/sbin/semanage will work on both RHEL7 and RHEL8, we can switch to this rather than policycoreutils-python

On the other hand afaik there is no e2e test covering this. And probably it would be great to have that kind of test (setting remote access + setting client to access it, then operate the cluster from the client) As we already know this is a user story which clients are implementing

We need to consider what the priority of this is. At least it should be recorded.


The keywords weight problem

Keyword weight can not be located to the second decimal point, will automatically round off,like the pixar stley model,it's have the trigger words:(pixarstyle:1.25), it automatically adjusts to (pixarstyle:1.3).

I have received the issue you submitted and I will fix it as soon as possible.

The issue has been fixed. Now, if you manually input 1.25 in the input box, it will not be rounded up to 1.3, and when using the adjustment buttons to increase or decrease the value, it will also retain two decimal places.


bug: Snacks.toggle.zen() doesn't work

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.11.0-dev
Operating system/version
Linux  6.11.7 NIXOS 24.11
Describe the bug
Snacks.toggle.zen()

Doesn't do anything to me, and when I do Snacks.zen() it does but then I cannot close zen mode with Snacks.toggle.zen() nor with Snacks.zen().
Steps To Reproduce

Run Snacks.toggle.zen()
Nothing happens

Expected Behavior
It was working before without the toggle... repro.lua shows the error as well.
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/snacks.nvim", opts = {} },
    -- add any other plugins here
  },
})

Here's some log:
Error executing vim.schedule lua callback: ...or/.local/share/nvim/lazy/snacks.nvim/lua/snacks/dim.lua:114: attempt to index a nil value
stack traceback:
	...or/.local/share/nvim/lazy/snacks.nvim/lua/snacks/dim.lua:114: in function 'cb'
	.../share/nvim/lazy/snacks.nvim/lua/snacks/animate/init.lua:86: in function 'update'
	.../share/nvim/lazy/snacks.nvim/lua/snacks/animate/init.lua:173: in function <.../share/nvim/lazy/snacks.nvim/lua/snacks/animate/init.lua:170>

I also tried on neovim 0.10, same result.

On 0.10 actually, Snacks.toggle.zen() does start zen mode, but running it again doesn't re-open it.

Also, Snacks.toggle.zen() returns a toggle object with a map function.
You can also use it to toggle directly (which makes little sense), but then you should do Snacks.toggle.zen():toggle()

Snacks.toggle.zen():map("<leader>uz")
That will create the mapping with correct description and will show as a toggle with the correct state in which-key.
Like here:

@folke now I got the toggle state of the icon changes, that's so cool, thank you so much!


[Bug] An error has occured : Not found

I am constantly getting an error An error has occured : Not found even after trying to sign in multiple times and have also installed and reinstalled the extension, but I still am unable to view my actions.

I can see my actions folder in the file browser.
Attaching screenshots below for reference.
I opened the link to access Github using VScode and then it returned to VScode to open the URL, i was able to see a signing in to Github notification for like a second and then it went away.

Found #26 having the same issue.

It happens when you don't open the root folder. The first, I have several repositories open and I do not charge the Actions of all. In the second I only opened one and immediately loaded the actions

Yes , it opens/shows the actions only if that particular repository is opened.
However generally when you git cone inside a folder say named git repositories or your home folder it doesn't work.
[Suggestions or feature-request] :
Are there any plans to make it work regardless of whether you have opened that particular repository or a directory of repositories  as the .github folder would still be there for each directory and then if one were to open a different repo one would have to open multiple VSCode windows to check on all actions/code.
It is also notable that one doesn't work on multiple repositories at the same time but having to open a new window just to switch repositories and then code and watch the workflows seems rather different.
[Reviews] :
This extension is really helpful and does save a lot of time.

It really saves a lot of time. But, for example, in a miservices environment like I work, I need to open many repositories at the same time, and it is super easy for me to have everything in a single window. You would have to open multiple environments to do the same.
But if you save a lot of time, except for that I would use it more, that's a shame. but be sure someone reads this and adds it, or ourselves ...

There is an existing issue for supporting workspaces and in general more complex folder structures: https://github.com/cschleiden/vscode-github-actions/issues/17
but this would require some bigger changes to the UI, I'm not sure how soon that could get done.

sorry to necro, but any news on this?
i see the workflow #17 got merged, but i still see the problem.

@robert-spring do you have more information of your concrete scenario? Are you using a workspace?


Current user sync url fixed

When syncing current user's info url should be "accounts/current_user/?edit=true"

Pull request approved but it is not merged. Do you have any idea? @felipeinf


networkcloud release

https://github.com/Azure/sdk-release-request/issues/4073

this is a new service ,so need to run azp command

/azp run prepare-pipelines

/azp run js - networkcloud - mgmt - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-networkcloud


TUI action autocomplete

Codecov Report

Merging #44 (4a85cd1) into master (e59a086) will decrease coverage by 0.36%.
The diff coverage is 12.28%.

@@            Coverage Diff             @@
##           master      #44      +/-   ##
==========================================
- Coverage   76.07%   75.71%   -0.37%
==========================================
  Files          64       63       -1
  Lines        5213     5230      +17
==========================================
- Hits         3966     3960       -6
- Misses       1247     1270      +23

Impacted Files
Coverage Δ

quake_tui/src/ui.rs
0.00% <0.00%> (ø)

quake_tui/src/widgets.rs
2.46% <0.00%> (-0.20%)
:arrow_down:

quake_tui/src/app.rs
62.59% <14.89%> (-10.18%)
:arrow_down:

libs/quake_analysis/src/main.rs

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 e59a086...4a85cd1. Read the comment docs.


Added recursion, lists, trees

Summary :memo:
Examples of recursions, list implementations, and trees.

Codecov Report

Merging #4 (7f13c0c) into main (8193389) will decrease coverage by 1.63%.
The diff coverage is 97.67%.

@@             Coverage Diff             @@
##              main       #4      +/-   ##
===========================================
- Coverage   100.00%   98.36%   -1.64%
===========================================
  Files            1        1
  Lines           22       61      +39
===========================================
+ Hits            22       60      +38
- Misses           0        1       +1

Impacted Files
Coverage Δ

mykit_learn/base.py
98.36% <97.67%> (-1.64%)
:arrow_down:

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 8193389...7f13c0c. Read the comment docs.


⚠ Cioos National CKAN has degraded performance

In f7f0ac7, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 8586 ms

Resolved: Cioos National CKAN performance has improved in 499c73b after 11 minutes.


support destructuring patterns in poise::command macro

It would be nice if destructuring patterns were supported for parameters in functions annotated with the #[poise::command] macro. That is, this currently does not compile (as it only accepts identifier patterns atm):
#[poise::command(prefix_command, track_edits, broadcast_typing)]
pub async fn foo(cx: PoiseContext<'_>, CodeBlock { code, .. }: CodeBlock) -> anyhow::Result<()> {
  // ...
  Ok(())
}

It's not particularily important I suppose, one can always just write let CodeBlock { code, .. } = block; in the body (or access struct fields manually) but it would be a nice-to-have :)

The reason I omitted support for destructuring patterns is that there is no clear parameter name anymore.
Thinking about it, you technically don't need it for text commands. So I guess CommandParameter.name could be made optional. Not sure if it's worth the extra complexity


Unlocker causing Notice: Version update found

Whenever I try to launch the game through the unlocker it opens just fine but as soon as I try to start the game past the loading door it tells me to update the game to the latest version even though I am already on the latest version of the game (5.2) I've tried to re download the unlocker and repair my files in the game but I still get this issue. If anyone can help, please do, I'd much rather play Genshin at 200 frames than 60.

This is the notice

As you can see the unlocker is working on start up but wont allow to go past the login screen
(I tried to zoom in as best as I could)

I accidentally sent the same picture twice.
THIS is the Notice

you have the wrong game path

Thanks a lot, I just changed it and now it's working, sorry about that.


Please have XCode 13.3 option available for the React Native IOS build process

Describe the solution you'd like
An option to select version 13.3 for XCode for React Native build configuration
Describe alternatives you've considered
I don't know any other alternatives unless I downgrade my version, but that will conflict with the other developer setup
Additional context
It is possible that the builds in App Center are failing for our Org because of that configuration difference

Closing as duplicate of https://github.com/microsoft/appcenter/issues/2408.


cel expressions of hostprocess containers updated

Related Issue(s)
Partially Fixes #1058
Fixes #1095
Description
I have updated the disallow-host-process policy to include a CEL variable, allContainers, which combines all container types and ensures the hostProcess field is either not set or set to false for each container.
Checklist

[x] I have read the policy contribution guidelines.
[x] I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.
[x] I have added the artifacthub-pkg.yml file and have verified it is complete and correct.

@chipzoller Could you please review my PR? Thanks.

Waiting for CI to run. Seems like Actions are hung.

Waiting for CI to run. Seems like Actions are hung.

Okay.

@chipzoller HostProcess requirements specify configurations for Windows containers that need privileged access to the host, including settings such as hostProcess, hostNetwork, and specific user roles like runAsUserName and runAsNonRoot. If Pod Security Standards define security profiles within a policy, do we still need to explicitly mention the other requirements for HostProcess Pod configuration such as hostNetwork and user roles in policy? This point confuses me, and I would appreciate some clarification. I referred k8s doc

All this policy is concerned with is implementing the exact checks for the specified control. It should only be a CEL version of this policy.

Closing then re-opening to see if CI will get unstuck.


[Bug]: Browsershot node path error again at AWS EC2 instance with Ubuntu OS

What happened?
When clicking the download button to generate a PDF using the Laravel PDF package through Browsershot, the process failed because Puppeteer could not locate the required Chrome installation. The error message states that Chrome (version 129.0.6668.70) could not be found, which suggests that either Puppeteer was not correctly installed or the cache path is misconfigured.
How to reproduce the bug
I'm not sure if this step is needed or not https://spatie.be/docs/browsershot/v4/requirements#content-installing-puppeteer-on-a-forge-provisioned-server. That installation guide points me to install puppeteer@^17.
Package Version
^1.5
PHP Version
^8.2
Laravel Version
^11.0
Which operating systems does with happen with?
Linux
Notes
Thank you so much your kindly help.

Having this exact issue. Anyone got a solution?

Not now. Still bugs.

any updates?
@freekmurze need your atttention here.

You can check in here. But for now, whether this is working or not, I haven't checked it out yet. I will check soon.

I still have this same error on Amazon Linux 2023 (AL2023) no matter what I try.
Working fine on the local server, but it totally crapped out on the production server.


Go Live [June 21]

Docs Build status updates of commit e52c37c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/bots/bots-consent-dialogbox.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/bots/uninstallbot.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/subscribe-to-conversation-events.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
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.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel