support hunyuandit in xdit

support hunyuandit in xdit

run with the following command:
torchrun --nproc_per_node=8 ./examples/hunyuandit_example.py --prompt 'A cat holding a sign that says hello world' --output_type 'pil' --model /path/to/HunyuanDiT-v1.2-Diffusers/   --height 1024 --width 1024 --ulysses_degree 2 --ring_degree 1  --use_cfg_parallel --pipefusion_parallel_degree 2 --num_pipeline_patch 2 --warmup_steps 1 --num_inference_steps 20 --seed 0

Runtime error:
[rank4]:   File "/root/xDiT/xfuser/model_executor/models/transformers/hunyuan_transformer_2d.py", line 199, in forward
[rank4]:     hidden_states = block(
[rank4]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank4]:     return self._call_impl(*args, **kwargs)
[rank4]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank4]:     return forward_call(*args, **kwargs)
[rank4]:   File "/usr/local/lib/python3.10/dist-packages/diffusers/models/transformers/hunyuan_transformer_2d.py", line 183, in forward
[rank4]:     attn_output = self.attn1(
[rank4]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank4]:     return self._call_impl(*args, **kwargs)
[rank4]:   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank4]:     return forward_call(*args, **kwargs)
[rank4]:   File "/root/xDiT/xfuser/model_executor/layers/attention_processor.py", line 138, in forward
[rank4]:     return self.processor(
[rank4]:   File "/root/xDiT/xfuser/model_executor/layers/attention_processor.py", line 869, in __call__
[rank4]:     query = apply_rotary_emb(query, image_rotary_emb)
[rank4]:   File "/usr/local/lib/python3.10/dist-packages/diffusers/models/embeddings.py", line 532, in apply_rotary_emb
[rank4]:     out = (x.float() * cos + x_rotated.float() * sin).to(x.dtype)
[rank4]: RuntimeError: The size of tensor a (2048) must match the size of tensor b (4096) at non-singleton dimension 2

Whether the variables query & image_rotary_emb are the same size or one of them is broadcastable?
I'm guessing it is because you did not split image_rotary_emb in _init_sync_pipeline
You can refer to https://github.com/xdit-project/xDiT/blob/main/xfuser/model_executor/pipelines/pipeline_flux.py#L336


Keyboard shortcut for Copy as image

I use Copy as Image a lot to paste models into different programs, mainly MS Word. I use the Desktop app on Windows and It takes a couple of mouse clicks that I would like to reduce/ move to keyboard.
Describe the solution you'd like
The ideal solution is descripbed in issue https://github.com/jgraph/drawio/issues/1845. Just use [CTRL]+[C] and depending of the target editor either paste as model, or paste as image.
Here I request an alternative: Keyboard shortcut for Copy As Image. Preferred:  [CTRL]+[ALT]+[C]
Describe alternatives you've considered
Using right-click and context menu instead of Edit menu already works a bit faster.

Change in 21.7.3 release. Ctrl+Alt+X for copy as image.

Great @davidjgraph thanks.
When will this version be available for Windows via MS Store? There I see 21.6.5.


HandDraggable is not ported

Overview
The feature HandDraggableis not ported to MRTK V2.0.0-Beta2
Expected Behavior
In Holotoolkit, we can use this from script HandDraggable as a class under HoloToolkit.Unity.InputModule,
Actual Behavior
I don't see it in MRTK
Steps to reproduce
(Links to sample github project preferred)
Unity Editor Version
2018.3
Mixed Reality Toolkit Release Version
v2.0.0-Beta2

Have you checked out ManipulationHandler.cs

Oh, Let me give it a try

@tletie ManipulationHandler now supports both one and two-handed manipulation. You can find the example scene here:
https://github.com/Microsoft/MixedRealityToolkit-Unity/blob/mrtk_release/Assets/MixedRealityToolkit.Examples/Demos/UX/TwoHandManipulation/ManipulationExample.unity

@tletie, as Yoon mentioned, the new manipulationhandler is the replacement for handdraggable.
We are actively working on a porting guide / feature map that will help customers discover the changes.
Please keep issues like this coming! They help us take a step back and review our documentation needs.

Thank you @davidkline, ManipulationHandler is the solution.


[Storage] Stop supporting --auth-mode login for az storage blob sync and az storage fs directory upload/download

Backgrounds
Storage module support several kinds of credential for data plane commands and azcopy commands:

--account-key with --auth-mode key(which can be omited)
--connection-string
--sas-token
--auth-mode login

azcopy has two kinds of auth:
a) SAS token auth
b) AAD auth
When customers provide 1) or 2), we generate a SAS token using the credential they give.
So with 1) 2) 3), we call azcopy by SAS token auth.
With 4), we call azcopy by AAD auth with login access_token and refresh_token stored in environment variable.
Problems

After CLI core migrates from ADAL to MSAL, we can't get refresh_token any more. azcopy related commands fail with --auth-mode login (#20488)
Setting access_token and refresh_token in env virable is unsafe.

Changes
This PR drops --auth-mode login support for azcopy related commands
PS. Some existing azcopy related commands don't support --auth-mode login from the very beginning, such as az storage copy/remove

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

I agree --auth-mode should be removed for now.
Actually, azcopy can support single-sign-on via MSAL and MSAL extensions. In that way, Azure CLI can call azcopy with something like
az copy --token-cache ~/.azure/msal_token_cache.json --username<EMAIL_ADDRESS>
but I don't think this is currently on azcopy's roadmap.

To give a little bit more info: unlike ADAL, MSAL now doesn't return refresh token via acquire_token_silent_with_error, which makes the original "we call azcopy by AAD auth with login access_token and refresh_token stored in environment variable" approach invalid.


Will support Web UI like glances can access from browser?

I like this,it's so good.
I want to know will support Web UI ?

There is no plan for built-in web UI at this time; however, I have had success running ctop in browser via gotty.

@bcicen Thanks.


[New] DataEngineer().pca() perform Principal Component Analysis (PCA)

Summary of this new feature
New method DataEngineer().pca() will perform Principal Component Analysis (PCA). We can use pca library.
https://github.com/erdogant/pca
Current CovsirPhy version: 2.26.0-alpha

This will be required to improve efficiency of prediction with regressor. PCA is a method to reduce the number of variables.

Because PCA assumes data is normal distributed, standardization (or Z-score normalization) should be perfomed as explained in the documentatin of pca.
https://erdogant.github.io/pca/pages/html/Algorithm.html#standardization

To check the amount of information, cumulative explained variance should be displayed as default.

Trial
https://gist.github.com/lisphilar/a044704f0382e010f257e950c787aee5

Installation error was raised with scatterd version 1.1.2 (a dependency of pca), but this error was fixed at scatterd version 1.1.3.
https://github.com/erdogant/scatterd/issues/2

#1140:

new; MLEngineer().pca(X, n_components): perform PCA on a data

import covsirphy as cs
data_eng = DataEngineer()
data_eng.download()
data_eng.clean()
data_eng.transform()
subset_df, *_ = data_eng.subset(geo="Japan")
subset_df = subset_df.drop(["Population", "Susceptible", "Confirmed", "Infected", "Fatal", "Recovered"], axis=1)
# PCA
eng = MLEngineer()
pca_dict = eng.pca(X=subset_df, n_components=0.95)

On documentation, the URL of pca package and the following usage should be recorded.
https://github.com/erdogant/pca
from matplotlib import pyplot as plt
import numpy as np
# Explained variance
pca_dict["model"].plot()
plt.close()
# Principal components (PCs)
pc_df = pca_dict["PC"].copy()
pc_df
# Top features
df = pca_dict["topfeat"].copy()
df["PC"] = df["PC"].str.extract(r"(\d+)").astype(np.int64)
df = df.sort_values(["PC", "type"]).reset_index(drop=True)

def highlight(d):
    styles = d.copy()
    styles.loc[:, :] = ""
    styles.loc[d["type"] == "best", :] = "background-color: yellow"
    return styles

df.style.apply(highlight, axis=None)

With #1157,

#1136: include the fitted model in the output of MLEngineer().pca()


Prediction Probabilities

is it possible to see the prediction probabilities for the lane instances using the code in its current form? thanks

@smcl2 Not possible now:)

Any idea why not?

@smcl2 Instance segmentation branch's output was a feature map rather a prob map. You may refer the origin paper for details:)

Ok thanks


logging: Ensure journald identifier is simply "cc-proxy"

Previously, the identifier used for each proxy log message specified
the full path to the proxy binary. This meant that to select proxy log
messages it was necessary to specify:
$ sudo journalctl -t /usr/libexec/clear-containers/cc-proxy

Now, the user can perform the same action with a simple:
$ sudo journalctl -t cc-proxy

Fixes #180.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

just a thought - are there any scripts or tools that do log scraping and collating we need to update to match this ?

Good question. The still-unfinished https://github.com/clearcontainers/tests/pull/590 circumvents the issue by requiring the user to pass the required journal extracts.
@sboeuf, @chavafg - can you check for anything else that might be impacted by this?

@jodh-intel, @grahamwhaley  we use sudo journalctl -u cc-proxy in the teardown.sh script, so we are fine. :)

@chavafg - actually, "yes and no" - that now needs to be sudo journalctl -t cc-proxy due to https://github.com/clearcontainers/runtime/pull/835. We still launch the system-level cc-proxy instance, but it's inert and we'll be removing that soon when #177 lands.

ohh, that's true, forgot about that change, then I'll open a PR to update it.

Thanks!


Set focus on an empty markdown component, when a user clicks on it

Following the GitHub pattern, if a markdown component is empty, clicking on it will make it editable and set focus on it. If the markdown component has text in it, the user needs to click on the edit icon to make it editable.

@nimishamukherjee I'm confused as to why this is needed. PatternFly already has design patterns for how inputs should act - why are these not just following the patterns of a standard input? There should be no difference in how inputs function.

@catrobson @joshuawilson for your review

I think we need UX to weigh in on this.

Can we get this merged for Freesia as it improves the current markdown's usability ?

@nimishamukherjee can you answer @mindreeper2420 question?
cc @catrobson @dlabrecq @dgutride

@joshuawilson @nimishamukherjee @mindreeper2420 There are not guidelines yet on how form fields interact for inline edit, nor markdown fields in PatternFly.
Could someone put a video/gif of what this interaction will look like into the PR for a quick design review?

@nimishamukherjee waiting on your response.

@catrobson please refer to the gif for the inline edit focus behaviour

Following the GitHub pattern, if a markdown component is empty, clicking on it will make it editable and set focus on it. If the markdown component has text in it, the user needs to click on the edit icon to make it editable.

@nimishamukherjee can you please rebase

@catrobson can you take a look at this?

@nimishamukherjee it would be better if clicking inside of the component also enabled edit mode, but a long click (click and hold) allowed for user selection of the text without going into edit mode.

@nimishamukherjee is that something you can do easily or would it take a lot of extra work?

@catrobson what is the use case for text selection. How long should a user click and hold for text selection to occur?
@joshuawilson enabling edit on click is doable.
Long click would take time to implement. I can create a separate task for long click. Would that work?

I'm ok with adding long click as a separate PR and having an issue to track it.  Looks like generally its .25 - .5 seconds for a click, anything longer should be counted as click and hold.  Maybe it can also be determined based on mouse down/mouse up and touchstart/touchend?  @mindreeper2420 any suggestions or recommendations?

@nimishamukherjee please link to the new issue here so that @catrobson and @mindreeper2420 can comment on it and I'll merge this one.


Report 299 "Delete Invoiced Sales Orders" - Wrap dialog calls in GuiAllowed for job queue processing

Hi Microsoft AL Development Team,
Could you please wrap these dialog calls in GuiAllowed to run report 299 "Delete Invoiced Sales Orders" via the Job Queue with no issues?

Thanks,
Tuan Nguyen

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Remote debugging not working again

I'm not sure in which version of VSCode remote debugging broke for me. But I know it broke for perhaps within 2 months.
These are the settings I've been using for a long time before it broke(and they have been working for many months):
        {
            "name": "Attach Remotely",
            "type": "node",
            "request": "attach",
            "port": 6000,
            "address": "localhost",
            "restart": false,
            "sourceMaps": true,
            "outFiles": [
                "${workspaceRoot}/Build/**/*.js"
            ],
            "localRoot": "${workspaceRoot}",
            "remoteRoot": "/srv/noelia"
        }

I'm using Docker Compose for development:
services:
  dev.noelia:
    image: ****
    container_name: dev.noelia
    extra_hosts:
      - "dockerhost:$DOCKERHOST"
    volumes:
      - .:/srv/noelia
      - ~/.bash_history:/root/.bash_history
    ports:
      - "3000:3003"
      - "6000:5858"

I'm using Docker for Mac and I have a debugger breaked on entrance. I run a tcpdump to ensure the VSCode can reach the node runtime.
tcpdump -i eth0 port 5858
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
16:00:11.189204 IP <IP_ADDRESS>.58520 > 4c1a1942b276.5858: Flags [S], seq<PHONE_NUMBER>, win 29200, options [mss 1460,sackOK,TS val 5094367 ecr 0,nop,wscale 7], length 0
16:00:11.189259 IP 4c1a1942b276.5858 > <IP_ADDRESS>.58520: Flags [R.], seq 0, ack<PHONE_NUMBER>, win 0, length 0

I can confirm it can reach because some packets are showing every time I click on the attach button.
And I'm using Mocha to issue the debug break statement
./node_modules/mocha/bin/mocha ./Build/Source/Tests/RunTests.js --timeout 15000 --colors --full-trace --grep LinksCanNavigateToSameLayout --debug-brk
Debugger listening on <IP_ADDRESS>:5858

There is no outputted error on VSCode (Debug Console) and when I try to attach to it, it loads a bit and then nothing happens the loading indicator disappears. There are no Debug buttons appearing as usual.
I tried to attach locally by running the same command and it works. Just remote debugging (in a Docker container) doesn't work for me.

I am also facing this problem at the moment.
I'm running pretty much the exact same configurations: running on a Mac, trying to connect the debugger to node inside docker, no error is shown and the debug control panel just never appears.
Toggling Dev Tools doesn't provide any extra info either, there's no error in the console there.

I've been using the VSCode debugger for a Node app on a Mac for a while. We just switched our dev environment to run things via docker-compose, so I just started having this same issue.
A question for those of you having the same problem: are you able to debug in Chrome DevTools? I start my app with node --inspect=5858 . and when it spits out the chrome-devtools://devtools... URL, I paste it into Chrome but all I get is a message that says "Debugging connection was closed. Reason: WebSocket disconnected." I'm curious if this is an issue with docker? Not sure though, just throwing that out there...

I'm curious if this is an issue with docker

This is also my suspicion, though I thought I ruled it out with a tcpdump. And trying to run with node --inspect I don't get the same errors as you, are you sure you are pasting with the right URI? For me I map with a different port than 5858.
Though one interesting thing is, although I don't get the same error. Nothing works in my
I will file an issue there as well

Yep, definitely pasting the right URI. In fact I just repeated this scenario on a Ubuntu 16.04 machine and got the same result! Strange. I'll keep digging into it and update this thread or the docker one as appropriate.

I am facing the same problem but I managed to attach the chrome devtool to the node running inside a container. Just run node with --inspect=<IP_ADDRESS> rather than pure --inspect as it will only listen to a local connection. This way, I can get the chrome's devtool to work. For this reason, I doubt there is something wrong with Docker. This is supposed to be a bug in VS code itself.

Thank you! I had a feeling there was some flag I hadn't tried yet. Glad to hear we can still debug somewhere until this VSCode issue is resolved. Thanks again.

By the way, I can now get the VSCode debugger to attach when starting the node app with node --inspect=<IP_ADDRESS>:5858 👍 👍

@mulleady1 Glad to hear you manage to get it to work so this can prove that it might not be a vs code bug. Would you mind sharing with me a couple of things as follows:

Your Node.js version in your docker container
Your configuration in launch.json file
I am still struggling to get this to work. I can get Devtool to attach quite fine but not for VS code.

Sure thing.

7.7.1
Not sure if some of these settings are necessary, but my config currently looks like:

{
  "type": "node",
  "request": "attach",
  "name": "Attach",
  "port": 5858,
  "restart": true,
  "sourceMaps": false,
  "localRoot": "${workspaceRoot}/api",
  "remoteRoot": "/home",
  "protocol": "inspector"
}

@woraphol-j Same here!
Running node with --inspect=<IP_ADDRESS>:5858 allows me to connect the chrome debugger to it. However, source maps aren't supported which doesn't work for me since I'm using Typescript.
As for trying to attach VScode, still no luck. I'm using node 7.7.1 as well and my launch.json is the same as @mulleady1

However, source maps aren't supported which doesn't work for me since I'm using Typescript.

VSCode (as well as Chrome Debugger) should support source map?
I'm just wondering if you can attach the Chrome Debugger to a remote container using --inspect=<IP_ADDRESS>:5858? (I can connect to it, but it never attaches).

Can you do a quick test?
Try to change the type to node2 on your launch.json.
Let me know if that works.
[]'s

@mulleady1 Do you mind share your Docker version as well?

Docker:

Mac:

Also, I have this setting checked in Chrome for a different reason, but maybe it's a piece to this puzzle:

@navossoc Bingo!!
Changing from node to node2 magically works for me after struggling with this for many days. Finally get it to work, many thanks!

@woraphol-j I traced my issue to outDir in tsconfig.json.
If you change that value the source map resolution seems to be broken, even if you try to use absolute path or any other kind of settings to change the behavior of the source maps.
Seems there is a protocol change for node debugger and that transition is what is creating all this problem.
See here: https://code.visualstudio.com/updates/v1_10#_node-debugging
You can also set the type to node and add the protocol to auto (it will choose inspector and works too).
I'm using node v6.10.1. and my launch.json is something like this:
{
	"type": "node",
	"request": "launch",
	"name": "Launch Program",
	"program": "${workspaceRoot}\\lib\\index.js",
	"protocol": "auto"
},

Hi,
I observe the same issue when running my docker container (based on node:7.7.2-alpine) in docker-machine (VirtualBox) on Windows 7 and then trying to attach to it from vscode.
Neither of the following configurations work for me:
        {
            "name": "Attach1",
            "type": "node",
            "request": "attach",
            "port": 9229,
            "restart": true,
            "sourceMaps": false,
            "localRoot": "${workspaceRoot}",
            "remoteRoot": "/home/app/app/",
            "windows": {
                "address": "<IP_ADDRESS>"
            },
            "protocol": "inspector"
        },
        {
            "name": "Attach2",
            "type": "node",
            "request": "attach",
            "port": 9229,
            "restart": true,
            "sourceMaps": false,
            "localRoot": "${workspaceRoot}",
            "remoteRoot": "/home/app/app/",
            "windows": {
                "address": "<IP_ADDRESS>"
            },
            "protocol": "legacy"
        },
        {
            "name": "Attach3",
            "type": "node",
            "request": "attach",
            "port": 9229,
            "restart": true,
            "sourceMaps": false,
            "localRoot": "${workspaceRoot}",
            "remoteRoot": "/home/app/app/",
            "windows": {
                "address": "<IP_ADDRESS>"
            },
            "protocol": "auto"
        },
        {
            "name": "Attach4",
            "type": "node2",
            "request": "attach",
            "port": 9229,
            "restart": true,
            "sourceMaps": false,
            "localRoot": "${workspaceRoot}",
            "remoteRoot": "/home/app/app/",
            "windows": {
                "address": "<IP_ADDRESS>"
            },
            "protocol": "inspector"
        },
        {
            "name": "Attach5",
            "type": "node2",
            "request": "attach",
            "port": 9229,
            "restart": true,
            "sourceMaps": false,
            "localRoot": "${workspaceRoot}",
            "remoteRoot": "/home/app/app/",
            "windows": {
                "address": "<IP_ADDRESS>"
            },
            "protocol": "legacy"
        },
        {
            "name": "Attach6",
            "type": "node2",
            "request": "attach",
            "port": 9229,
            "restart": true,
            "sourceMaps": false,
            "localRoot": "${workspaceRoot}",
            "remoteRoot": "/home/app/app/",
            "windows": {
                "address": "<IP_ADDRESS>"
            },
            "protocol": "auto"
        }

Here <IP_ADDRESS> is the ip adress that docker-machine env command yields me.
I run the application with the following docker-compose.yml:
  web:
    build: .
    command: node --inspect-brk=<IP_ADDRESS>:9229 index.js
    ports:
    - 80:80
    - 9229:9229

When I start the application I am able to see the following in the console:
Debugger listening on port 9229.
Warning: This is an experimental feature and could change at any time.
To start debugging, open the following URL in Chrome:
    chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=<IP_ADDRESS>:9229/75b18c73-b7b1-4e41-83b2-91f28470cd86

When I open the url in the chrome (replacing <IP_ADDRESS> with <IP_ADDRESS>) I am able to successfully start debugging the application (it stops on the 1st line of the application).
But when I am trying to attach from VsCode it just hungs forever showing like it is trying to attach.
After reading the above I did not clearly understand if somebody has the exact same behavior and if it has a workaround.
Additional note.
I observe the same when trying to run application as following:
node --debug-brk=<IP_ADDRESS>:9229 index.js

Seems to be related to the issue: https://github.com/Microsoft/vscode/issues/23257
Probably the wrong IP address is sent to vscode from container?

I just added a "VS Code Recipe" for how to debug transpiled source in Docker with VS Code. Please see https://github.com/weinand/vscode-recipes/tree/master/Docker-TypeScript

@weinand I don't see any new configurations that you are using that might make my case work.

@tinganho does it help if you add a "protocol": "legacy" to your launch config?
What version of node are you running inside the container?
does it help if you pass --debug-brk=<IP_ADDRESS>:5858 to mocha?

I tested with following, debug not work. I am running in Mac with docker 17.03.1-ce, node v7.10.0 , VS code 1.12.2.

start nodejs
--debug-brk=<IP_ADDRESS>:5858 or --debug=<IP_ADDRESS>:5858

launch.json

"name": "Attach",
"type": "node",
"request": "attach",
"protocol": "legacy",
"address": "localhost",
"port": "5858",
"restart": false,
"sourceMaps": true,
"outFiles": [
      "${workspaceRoot}/dist/**/*.js"
],
"localRoot": "${workspaceRoot}",
"remoteRoot": "/server",
"timeout": 10000

BTW, I also tried for setting of inspect, debugger didn't stop at the break point, but I can see the application calling DB with SQL in debug console.

@AndrewLaBabies does your program break correctly if you add a "debugger" statement?

Just FYI to whomever, remote debugging has been working like a charm for me lately. The biggest difference in my setup from when I was having trouble is that I switched to the edge channel for Docker for Mac. My configuration is:
Start node with node --inspect=<IP_ADDRESS>:5858 .
launch.json:
{
  "type": "node",
  "request": "attach",
  "name": "Attach",
  "port": 5858,
  "restart": true,
  "localRoot": "${workspaceRoot}/api",
  "remoteRoot": "/home",
  "protocol": "inspector"
}

Docker
Version 17.05.0-ce-mac11 (17656)
Channel: edge
Node
v7.9.0
Mac
El Capitan v10.11

@weinand , sorry for the late response.
Added "debugger" statement in ts file, the program breaks, vs code stopped in corresponding compiled js file at the line with "debugger" statement.
But the breakpoints set in vs code directly, which still don't work.

@AndrewLaBabies if your debugger statement does not result in a break in the TypeScript file but breaks in the generated JavaScript, I suspect that your source maps are missing or incorrect.
Make sure that the generated Javascript has a reference at the end that points to the source map and that the sourcemap has an entry in the "sources" array that points to the TypeScript file.

@weinand sorry for late response here as well.

@AndrewLaBabies if your debugger statement does not result in a break in the TypeScript file but breaks in the generated JavaScript, I suspect that your source maps are missing or incorrect.

As I downloaded a newer version of VSCode, it seems like I'm able to break(only using the inspector protocol), but only in JS file. I checked the sources property in the source map files and it seems they have the correct path.
One another thing is that the node process stalls (and I have to manually kill the process), when I try to detach the debugger(though, I'm not sure if it is VSCode fault here). It would be good if other people can confirm this as well.
It seems like my problem only occurs specific to my project. As I cannot create minimum verifiable bug case. (Though if you have async/await code it jumps to JS code, but it jumps back to TS code).
I can do some more digging, when I got more time.

@tinganho you said: "if you have async/await code it jumps to JS code, but it jumps back to TS code".
This is normal since the generated sourcemap does not cover all the generated JavaScript. So there are "holes" in the JavaScript that doesn't map to TypeScript. You can avoid stepping through the JavaScript by setting the "smartStep" attribute to true.

@weinand , I double confirmed the sourceMaps were generated correctly, and sourceRoot pointing to the correct ts folder in docker container

@tinganho VS Code cannot access TypeScript source in the container and the node.js runtime doesn't care about the TypeScript.
So please make sure that the TypeScript source is available where VS Code is running. From VS Code's perspective there is no need to have the source available in the container.
The logic for finding the source in a remote Docker scenario is as follows:

the node.js runtime in the Docker container hits a breakpoint and reports the JavaScript location as an absolute path in the container.
VS Code converts the remote path to a local path via the remoteRoot/localRoot mapping from the launch config.
if the JavaScript contains a source map reference, VS Code tries to locate the source locally by consulting the source map.

Please note: the above logic applies to the case where the source lives in separate files. If the source is inlined in the source map and the source map itself is inlined in the JavaScript, VS Code tries to use the inlined source.

@weinand I think I got the debugging working now.
I didn't made any changes. Though I added and removed some debugging configurations. And at last I got it to work. I'm suspicious whether there could be any caching bug? Because my configurations looks exactly the same as before.
I think because my addition and deletion of configurations made my debugging configurations to take effect. Honestly, my debugging experience haven't been consistent, sometimes I cannot set breakpoints, sometimes I can. Sometimes other problems occur, sometimes not. It was very hard to pin point the exact problem.

In my recent experience is that the breakpoint only breaks correctly if I explicitly add a "debugger;" statement in my source code.

I ran in to these issues, used the <IP_ADDRESS> fix to get attach working again. Also needed to make sure the localRoot was correct in order for breakpoints to hit (in the launch.json). You'd also probably find when it only works with debugger statements it's not breaking in the actual code file.
Tested my fixes against the docker labs tutorial on mac and ubuntu: https://github.com/docker/labs/pull/313/files

If you're using jest, you may need to use the --no-cache option for jest. This fixed debugging for me in some cases.

Since this issue is quite old, and the discussions are difficult to follow, and VS Code is now at version 1.20.1, I will close this issue. If you still see issues in 1.20.1 please open new issues.


Depreciation Warning

Uploading from command line
grunt ftp
success! but warnings which I don't remember from a while back(?) .ftppass and inline credentials all standard with double quotes.
(node:78761) DeprecationWarning: Ftp.rawuser: Use Ftp.raw('user args') instead.
(node:78761) DeprecationWarning: Ftp.rawpass: Use Ftp.raw('pass args') instead.
(node:78761) DeprecationWarning: Ftp.rawtype: Use Ftp.raw('type args') instead.
(node:78761) DeprecationWarning: Ftp.rawcwd: Use Ftp.raw('cwd args') instead.
(node:78761) DeprecationWarning: Ftp.rawquit: Use Ftp.raw('quit args') instead.
thanks in advance

Getting the same messages here

Same here
Thanks for the great library 👍

This is still happening. It has been fixed upstream.

Adding to the comment of @Kelderic , I've created a PR that fix all the warnings for me. You can take a look at it and change the files locally while we are waiting for @zonak to accept and merge the PR..
Cheers!

Unfortunately, I'm pretty sure that this project has been abandoned, @spoji.

Yeah... Last updates were 3 years ago. The pull request should at least help others having the same issue and need a solution to it.

I stand corrected. The PR has been merged back and npm has been updated to 0.2.0 which include the fix.
https://www.npmjs.com/package/grunt-ftp-deploy
@zonak This issue can be closed.


Remove Xamarin support

I've got a new branch no-xamarin which removes support for the legacy/Xamarin mobile platforms.  Android and iOS are still supported with net6.0 and up.
For now, this is a branch, but I'm trying to figure out when to bring it into main.

I forgot to reference this bug and #561 in the commit message, but see 5a8320979c1594c984cc31515664d17cc0cae3ca for significant progress on removing legacy Xamarin support and using that as an opportunity to simplify the build system along the lines of what @bricelam did in the SQLite3MultipleCiphers-Nuget repo.


Time selector in the UI drifts

Describe the bug
I'm not sure if this is by design or not but the time selector in the UI drifts as you keep the UI open.
The time range here was set originally as "Last 30 minutes", after a couple minutes when you run a query the time range changes which is unexpected.

Steps to reproduce (if applicable)

Select a time interval in the drop down
Allow some time to pass
Run a query and you'll see the time in the drop down increment

Expected behavior
If you select an interval like "Last 30 minutes" it should stay on "Last 30 minutes" and not increment as time passes.
Configuration:
# quickwit --version
Quickwit 0.3.0 (commit-hash: 6d07599)

Good point, I forgot to open an issue on this, thanks :)


DSR when approved through ui error

Bug Description
A description of what the bug is.
Steps to Reproduce

Log in to the admin ui and setup a connector (i used shopify)
Submit a DSR request through the PC using email only (do not add anything else)
Log into the admin UI and approve the DSR
The request will return ERROR right away

Expected behavior
The request should be processed through the connector however it looks like when the DSR is submitted on the backend the phone number is empty

If applicable, add screenshots to help explain your problem.
Environment

Version:
OS:
Python Version:
Docker Version:

Additional context
The persist_identity function in privacy_request.py does not correctly filter out the empty string phone number "" so the SaaS connector validation fails because it sees two identities defined instead of one.
def persist_identity(self, db: Session, identity: Identity) -> None:
        """
        Stores the identity provided with the privacy request in a secure way, compatible with
        blind indexing for later searching and audit purposes.
        """
        identity_dict: Dict[str, Any] = dict(identity)
        for key, value in identity_dict.items():
            if value is not None:
               ...

In saas_query_config.py
def _get_identity(self) -> Optional[str]:
    """
    Returns a single identity or raises an exception if more than one identity is defined
    """

    identities: List[str] = []
    if self.privacy_request:
        identities = list(self.privacy_request.get_cached_identity_data().keys())
        if len(identities) > 1:
            raise FidesopsException(
                "Only one identity can be specified for SaaS connector traversal"
            )
            ...

Verified


feat(documentation): add heading utility stories

Preview environments are getting posted here, as soon as they are ready!


Private messages

any plan to implement private message feature?
it would be nice to allow users to exchange some whispers. 😄

Hi @lxwang42 thanks for the issue, i agree that would be quite nice feature to have 🙂
Unfortunately I don't have time to implement it, but if you or anyone else is interested to make a PR for it, I'll be happy to merge it. Just before starting working on it we have to discuss how you are going to implement it, how UI should look etc.

@DimiMikadze @lxwang42  That sounds like something cool to work on, i'd love to start it once i get the time, any methods, libraries or ideas to suggest? websockets?

Hi @rachid-aachich for real time functionality we need to use GraphQL Subscriptions: https://www.howtographql.com/react-apollo/8-subscriptions/
Create new mongoose model  Message, new resolver message.
Regarding UI I think we can create separate page for it, like Twitter: https://twitter.com/messages
Let me know when You'll be ready to start working on it and we can discuss it in details ✌

How would you like it if there would be an extra branch for this feature so we all can push smaller changes to be merged into that branch? This might speed up the development if one person doesn't have the time to do it all at once.

Hi @leventdeniz currently i'm working on integration of realtime functionality into repository ( GraphQL subscriptions ). I think by end of the following week We'll have notifications realtime. After that it will be much easier to implement other real time functionalities e.g. Private Messages. I'll write my progress in here ✌

Regarding my progress, I've integrated GraphQL subscriptions into the repository, you can find them on master branch. Regarding Private messages, We have started working on it, this is the branch that contains all the changes for it: https://github.com/udilia/create-social-network/tree/implement-private-messages Currently we have built all needed queries and mutations on backend side and Messages UI and functionality is in progress. I think we'll finish them after 2 or 3 weeks, since there is a lot of work to do to finish them and i have vacation 🙃Feel free to contribute any way you like ✌

Are there any features you want to be implemented? @DimiMikadze

Fixed some things and noticed that it is possible to send empty messages. I'd also love a textarea for the message input that automatically expands.

Hi Guys, since many people are already working on this PR and there's still many thing to do to finish it, let me divide it as a sub tasks, so we can assign ourselves to individual sub tasks and start working on them. That way we'll avoid merge conflicts and we'll have clear a goal to accomplish.
Please give me 2 days for it, since I'm on vacation right now and thanks for contributing! ✌

I've added 4 sub issues, I think if we'll finish them we'll be able to close this issue, if you think we have to do something else feel free to fill an issue.
If you decide to work on any of them, please first assign it to yourself so everybody knows you are working on it and if you'll have any questions or issue descriptions are not clear enough please ask first, so we don't waste time.
We'll work on redesigning of messages page later, first let's finish its core functionality :) ✌

Hey guys, Messenger has been merged to master 🎉 you can test it on demo website 🙂Code will need some refactoring and UI will need some changes, which I'll do in the following week. For now let's test it and create issues if we'll find bugs around it ✌

I actually pulled it down soon as I saw the pr go through!
Ive got a fresh bug for ya, I'll try to see how to reproduce and make a issue. has to do with new messages and getting "TypeError: chatUser is null" when visiting http://localhost:3000/messages/new at times


Running code from CWD

Currently code is ran from the /tmp directory, however this leads to unexpected results.
For instance a repository with slides might run scripts from that repository, however it will not be able to relatively refer to those scripts and will need to define the paths absolutely.
Now the problem arises when another person wants to run these slides, since the absolute paths would be incorrect.
I am not sure if this would cause any security issues, the slides are still explicit about what they do, they now just behave like any other executable and run from with the context of that cwd where the presentation was started.
Reasons why we would want this:

Include other files in script block to focus on the important code, highlight in the codeblock
Include libraries for languages such as Javascript
Behaves as the writer/new users would expect

Not sure why we wouldn't want this but open to discuss.

pwd

cd ~/slides
presenterm +x slides.md
Expected behaviour:
/home/<user>/slides
Current behaviour:
/tmp/<hash>

You beat me to opening this!

Yes! I won the race! :rocket:
I have implemented something quickly in #323, so you can check that out if you'd like!

Nice, thanks!

Just to add that this fix doesn't seem to apply for the python path & imports. Have to do something like the following for `/path/to/folder/local_module':
import sys
sys.path.insert(0, '/path/to/folder/')
import local_module


[Draft] Add logging environment

Issue #, if available:
Description of changes:
Added logging environment to build.gradle for spark sample app.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #588 (cd56a50) into main (09e6487) will not change coverage.
Report is 137 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff            @@
##               main     #588   +/-   ##
=========================================
  Coverage     85.71%   85.71%
  Complexity       19       19
=========================================
  Files             3        3
  Lines            49       49
  Branches          5        5
=========================================
  Hits             42       42
  Misses            3        3
  Partials          4        4

:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


Rename all lenght => length

Fixed all misspellings of the word length.

Great! Thank you, @petersondrew. My bad :disappointed_relieved:

You're welcome, and no worries :smiley:


Add prepare script

In #54, I removed the postinstall script. Our build/publish pipeline actually depended on the build that was a consequence of the postinstall script, so this broke publishing in that the build never occurred.
This commit adds a prepare script which runs the build prior to packing for publish.
So, I know prepare runs on a local npm install. That would be a good effect. However if it also runs on a transitive install, that would be a regression and we'd instead want prepublishOnly or prepack. Will experiment with CSB build first.

prepare seems to be run transitively as well, so I've gone with prepack.


Error parsing Aggregate Reply

I have tried to use group with reducerTOLIST, redisearch.GroupByReducerToList but I got the following error
My request: redisearch.AggregateQuery{Max: 100000}.GroupBy(redisearch.GroupBy{Fields: []string{"@name"}, Reducers: []redisearch.Reducer{{Alias: "ids", Name: redisearch.GroupByReducerToList, Args: []string{"@b_id"}}}
Error:
Error parsing Aggregate Reply: redigo: unexpected element type for Strings, got type []interface {} on reply position 4
Do you know if there is another way to do this request please ?
Thank!

@adiongue I fixed it in #157. Now the returned type is different but it makes more sense to me.
Let me know if you still having trouble with that!

thank you @Avital-Fine

@Avital-Fine I use the last version of master but the aggregate function still returns [][]string

Use AggregateQuery() (I couldn't break it so I deprecated the old version)


error: Expected '--hash', found '"--only-binary=:all:"' in requirements.txt

❯ pip --version
pip 24.0 from /Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pip (python 3.12)

❯ uv --version
uv 0.1.5

Both pip and uv can install NumPy with --only-binary=":all:" (this only installs from binaries, don't attempt building from source):
❯ pip install numpy --only-binary=":all:"
Collecting numpy
  Using cached numpy-1.26.4-cp312-cp312-macosx_11_0_arm64.whl.metadata (61 kB)
Using cached numpy-1.26.4-cp312-cp312-macosx_11_0_arm64.whl (13.7 MB)
Installing collected packages: numpy
Successfully installed numpy-1.26.4

❯ uv pip install numpy --only-binary=":all:"
Resolved 1 package in 138ms
Downloaded 1 package in 960ms
Installed 1 package in 16ms
 + numpy==1.26.4

However if I have a requirements file containing:
numpy --only-binary=:all:

pip works:
❯ pip install -r requirements.txt
Collecting numpy (from -r requirements.txt (line 1))
  Using cached numpy-1.26.4-cp312-cp312-macosx_11_0_arm64.whl.metadata (61 kB)
Using cached numpy-1.26.4-cp312-cp312-macosx_11_0_arm64.whl (13.7 MB)
Installing collected packages: numpy
Successfully installed numpy-1.26.4

But uv fails:
❯ uv pip install -r requirements.txt --verbose
 uv::requirements::from_source source=requirements.txt
error: Expected '--hash', found '"--only-binary=:all:"' in `requirements.txt` at position 25

There are other options like --no-binary, --prefer-binary and more:

https://pip.pypa.io/en/stable/reference/requirements-file-format/#supported-options

Ah yeah, we don't support those in requirements files right now. We can probably add them. I think I will merge with https://github.com/astral-sh/uv/issues/1461, since it's the same issue but for --no-binary.


denoflare serve in local isolation mode hangs when using importText/Binary/Wasm on Deno v1.34.2

calling import() in ModuleWorkerExecution.create hangs indefinately starting in deno v1.34.2 when using importText, importBinary, or importWasm
Workaround for now is to stay on Deno v1.34.1.
Looks to be a possible Deno regression, as the entire module appears to be loaded and init successfully, including fetched resources over rpc (importX calls are translated to fetches when not on Cloudflare), just never returns to the caller.
Will look to create a small repro case and send over to the Deno folks.

Was able to fix it with a surgical workaround in rpc fetch body streams.


website/_GuestTutorials/index.md is broken

The links in the md file look broken
https://github.com/CodingTrain/website/blob/master/_GuestTutorials/index.md

Could you please clarify what exactly isn't working on your side? It looks all fine to me.

I hope this screenshot clarifies the issue

Ah... That's what you've ment. Actually everything is alright here. You're looking at the file which is responsible for building the thecodingtrain.com website and GitHub can't resolve links built by Jekyll (the system behind the website). That's why it looks so weird. ;)
I'm closing this since everything should be clear now.


Improve exception handling when no logger's been registered yet

Any progress on this?  It comes up any time I go to a new machine and run composer update or any artisan command.  Artisan tries to boot up but it can't resolve dependencies due to a missing .env config variable.  Which then forces me to debug into the laravel source code in order to figure out what  config key is missing.
It's one of those I remember this vague error message 'Class log does not exist', but I can't for the life of me remember what the real problem was!
Proposed solution, as others have suggested, is to re-throw the exception if it's not "reportable", i.e.
    public function handle($input, $output = null)
    {
        try {
            $this->bootstrap();

            return $this->getArtisan()->run($input, $output);
        } catch (Exception $e) {
            try {
                $this->reportException($e);

                $this->renderException($output, $e);
            } catch(Exception $ex) {
                throw $e;
            }
            return 1;
        } catch (Throwable $e) {
            $e = new FatalThrowableError($e);

            $this->reportException($e);

            $this->renderException($output, $e);

            return 1;
        }
    }

https://github.com/laravel/framework/blob/b88014713b2581d6bb443f4a0e8837662267772c/src/Illuminate/Foundation/Console/Kernel.php#L102-123

This has been fixed on:

Laravel 5.3+
The latest Lumen 5.1, 5.2, and 5.3+.

Run down for why not latest Laravel 5.1 and 5.2 was due to BC issues.


Network Connection and Validate Methods

Added utility method "NetworkValidate" in order to make generic tests of availability on Secrets Store URL connections.
Added Validate Methods to Gitlab #889 , Akeyless #890 , Alibaba #888, Webhook #887 providers, using "NetworkValidate" Util.

@moolen and @knelasevero I personally like this approach for a first try on Validate, because at least the basics of it would be covered.
Then, we can implement provider-specific checks according to the community's needs. WDYT?

Yeah, i like it as well. Tho the 4s timeout is a bit arbitrary. For most use cases it should be fine, but in some scenarios it may be a little to low (e.g. cross-region). I suggest raising it to maybe 10 or 15s to avoid flappy SecretStores.

/ok-to-test sha=be893b1

/approve

Thank you so much @b4ld for your contribution :heart:

/merge


Avoid duplicate method generation

If a service returns a Resource, both will produce methods resulting in the same REST path. Avoid this.

Currently, "duplicated" method returning the Resource on a GET is not annotated anymore.


afterEach hook does not run after tests that fail

Built in parallelism lends itself beautifully to using cloud based selenium grids such as Sauce Labs. In order for tests to run successfully, it is necessary for the afterEach hook to be executed whether the test passes or fails, mostly to quit the selenium webdriver. Any help would be much appreciated.

See https://github.com/sindresorhus/ava/issues/474 for the planned solution. I think @therealklanni is working on it. Any feedback on the referenced issue thread more than welcome :)

Thank you!

I haven't started on it yet, FYI. Been busy working on something else. Might be a few more days before I get around to it.

Thanks. No rush.


Ensure 2.6 Deployment views contain all data/functionality from 2.5 UI

Need to review the 2.5 UI and look for any gaps in terms of data or functionality that was in the old UI and was missed when porting to the new UI.

I don't believe there are any remaining gaps


Fractionnal zoom missing for MouseWheel Interaction

Default MouseWheel Interaction always zoom by 1 level.
The documentation actually mentions :

zoomDelta - number - Zoom level delta when using keyboard or mousewheel zoom.

But after taking look at the ol/interaction.js, we don't use zoomDelta in constructor :
 const mouseWheelZoom = options.mouseWheelZoom !== undefined ?
    options.mouseWheelZoom : true;
  if (mouseWheelZoom) {
    interactions.push(new MouseWheelZoom({
      condition: options.onFocusOnly ? focus : undefined,
      constrainResolution: options.constrainResolution,
      duration: options.zoomDuration
    }));
}

As mentionned here #8423, i can't really change zoomFactor.

yes, the doc is wrong: the zoomDelta property is not used for the MouseWheelZoom interaction.

Is there any plans to add Fractional Zoom feature to MouseWheel Interaction ?


💄 Consulting pages - Security page broken list

[ ] The items within the "Identify Solutions" section are in a list

Figure: Items inline instead of a list

Figure: https://ssw.com.au/consulting/security

Figure: https://ssw.com.au/ssw/consulting/security.aspx


feat(launch): add create_run_queue to public API

Fixes

Fixes WB-14240 (partial)

Description

🤖 Generated by Copilot at d53a33a
This pull request adds the ability to create launch run queues with different resources and access levels using the public API in wandb/apis/public.py. It also implements the internal API for managing default resource configurations for run queues in wandb/sdk/internal/internal_api.py and exposes it to the public API in wandb/apis/internal.py.
Testing
How was this PR tested?
Checklist

[x] Include reference to internal ticket "Fixes WB-14240" and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Ensure PR title compliance with the conventional commits standards

🤖 Generated by Copilot at d53a33a

To launch runs with different resources
We added some methods and courses
The Api class
Can now create and pass
Default configs with config_id sources

Thanks for the review @dmitryduev ! I have one missing piece of functionality to implement (guard w/ backend capability introspection) -- would you like me to re-request review after I implement it?

nah, feel free to merge once it's ready


How to view or read a pdf, doc and ppt file in ionic mobile app

Hi All,
IONIC PDF,DOC,PPT Viewer
I am developing an ionic application. In the I want the use read the file in application.
The file document's are give from the DB as url , when click it  need to open the file.
What i want is the list of document is show in a screen if click any one of the document is it will show as a separate view
Any one please give me some suggest for this.
Thanks
Dinesh

Hello! Thank you for opening an issue with us! As this seems like more of a support question I will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


Skeletal input

Current Issues:

[ ] Controllers are not aligned with the hands
[ ] Tools and Pickup are not aligned with the hands (will fix with poses)
[ ] Hand motion range doesn't always update (probably solved in latest commit)
[ ] Controllers seems to persiste in hands after one timeloop ends

Controllers seems to persiste in hands after one timeloop ends

@artumino Actually this bug already existed before. Happens because I'm not triggering the visibility change in all the correct times. I just never bothered to fix it. I can help fixing it in a separate PR if you want.

@Raicuparta No problem then, it was annoying cause the RangeOfMotion for the skeleton also wasn't working and the hand could clip through the controllers. It should work now so no more visual glitches even when the controllers are enabled (i think).
The hand-controller missalignment is probably due to the retargetting so we have to live with it (or maybe try getting the hand working directly without the retargeting).
I experimented with poses on another branch and aligning tools is just a matter of repositioning each Holdable object again. I've added a transform in the middle of the palm so calculating offsets should be easy.

@artumino I'm not sure what you mean by retargeting. I just tested, and the controllers seem to be aligned to the hands? Or maybe I just don't know what I'm looking for.
I also tested holding the tools and objects, and yeah it clips a bit more to the fingers now but that's not a big deal, can definitely include it as-is in an update.
I noticed that the wrist "hole" in the models is very shiny, probably because of the specular map texture or something similar. It makes that part kinda glow in the dark. Would be better to make it completely matte.

@artumino I'm not sure what you mean by retargeting. I just tested, and the controllers seem to be aligned to the hands? Or maybe I just don't know what I'm looking for.
I also tested holding the tools and objects, and yeah it clips a bit more to the fingers now but that's not a big deal, can definitely include it as-is in an update.
I noticed that the wrist "hole" in the models is very shiny, probably because of the specular map texture or something similar. It makes that part kinda glow in the dark. Would be better to make it completely matte.

Yeah I used the wrong term, the controllers are aligned. What isn't perfectly aligned is the fingertips with respect to the controller buttons, for example in the main menu if I move the thumbstick the thumb doesn't align with the thumbstick on the rendered controller. That's because we are retargeting the solved skeleton from SteamVR to a bigger skeleton for the hearthian hand, which means that we simply copying the rotation for each bone in the source human hand skeleton to the slightly bigger hearthian one and we endup with fingertips in a different location.
As I said I think we can live with this mismatch, it's only really visible in the main menu. To completely fix the issue I think we would have to make a 5 fingered skeleton for the hand with the heartian proportions, ignore 2 fingers during skinning and hope that steamvr can solve finger position with it, that would give us the right rotations to apply without any retargetting involved.
As for the glove, yes that part is currently mapped to the black rubber used at the tip of the fingers, I should probably make a new set of textures for this gloves, since right now I'm borrowing the one from the suit.

@artumino ah yes I think we don't need to worry about the fingers aligning perfectly. It's an alien and all, people will understand :P
The shiny wrist hole, i was talking about the non-glove hands. I didn't notice any material issues with the gloves.

@artumino ah yes I think we don't need to worry about the fingers aligning perfectly. It's an alien and all, people will understand :P
The shiny wrist hole, i was talking about the non-glove hands. I didn't notice any material issues with the gloves.

Oh, ok. If there are no issues with the gloves then I'll look at the specular for the hand. That surely is easier to edit :P


Selectable or copyable dialog text

Hello,
Is there a way to allow the text in the MahApps.Metro dialog to be selectable?
For an error message I was wanting to provide some helpful references but that's not so great if the user has to type them manually to look them up.

For people still finding this issue thread today - I worked-around this problem by adding a button action to the dialog which then invokes a custom method that copies the dialog's text to the clipboard.

For people still finding this issue thread today - I worked-around this problem by adding a button action to the dialog which then invokes a custom method that copies the dialog's text to the clipboard.


[FEATURE] Ability to rename workspaces

Is your feature request related to a problem? Please describe.
In the GUI it's not clear to which workspace is what. For example in my project there are 3 backend micro service talking to each other and I want to see which is what but I can't.

Describe the solution you'd like
These are the ID's of workspaces I guess, maybe someone can add name field and make it editable (if its default comes from project folder, that would be great)

@peyloride thanks for the request, I agree we should have renamable workspaces.
In the meantime I'm going to refactor the workspace list layout to prioritize the project directory, so that you can see the end and not just the start of those.

Thanks @peyloride, looks like @jwmza has a pretty good fix for the problem of being unable to tell workspaces apart over in #234. That will go out in our next release sometime next week.
In the meantime, you can use exo workspace ls in your terminal to see the full names clearly.
Going forward, we'll probably introduce a notion of "project", for which there may be many workspaces. I suspect that workspaces will remain anonymous and identified primarily by directory, but projects, stacks, etc may all become named. Still a fair amount of design work and TBD elements there. Tracking over here: https://github.com/deref/exo/issues/183

Thanks everyone, these are awesome news.

In light of @brandonbloom 's notice above re: #183 and the fix for readability in #234, I'll close this issue now.
However it is probably a good idea to soon use the shortest unique workspace directory label instead of the entire directory from root in most UI elements where the directory is displayed, in order to reduce visual noise.


Delete the temporary file even if the working directory has changed.

Referring to temporary files by their full, expanded path allows neomake to still find the temporary file if the working directory changes between the moment where the temp file is created and the moment it should be deleted.
This is a corner case, but as I am testing #59 I am forcing neomake to write a temporary file each time it performs a check, and in combination with the plugin vimfiler which temporarily changes the working directory when performing a rename, I have temp files laying around after a rename.

Awesome, maybe this fixes #31.


python39Packages.google-cloud-tasks: 2.7.1 -> 2.7.2

Motivation for this change
Things done

Built on platform(s)

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

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

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

[ ] 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/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

2 packages built:

python310Packages.google-cloud-tasks
python39Packages.google-cloud-tasks


Unable to import DataDog dashboard

hi all,
while I am able to import the dashboard from DataDog, there is one that I cant,
Here is the error I am getting.
Thank you in advance
Starting import of 'xxx-xxx-xxx'...
2022/07/11 13:43:40 datadog importing... dashboard
2022/07/11 13:43:41 datadog done importing dashboard
2022/07/11 13:43:41 Number of resources for service dashboard: 1
2022/07/11 13:43:41 Refreshing state... datadog_dashboard.tfer--dashboard_gct-n3v-vca
2022/07/11 13:43:41 object contains unparsed element: map[compute:map[aggregation:count] data_source:ci_tests group_by:[map[facet:error.type limit:100 sort:map[aggregation:count order:desc]]] indexes:[*] name:query1 search:map[query:@test.status:fail @ci.pipeline.name:"Test on PR"]]
2022/07/11 13:43:41 WARN: Fail read resource from provider, wait 300ms before retry
2022/07/11 13:43:42 object contains unparsed element: map[compute:map[aggregation:count] data_source:ci_tests group_by:[map[facet:error.type limit:100 sort:map[aggregation:count order:desc]]] indexes:[*] name:query1 search:map[query:@test.status:fail @ci.pipeline.name:"Test on PR"]]
2022/07/11 13:43:42 WARN: Fail read resource from provider, wait 300ms before retry
2022/07/11 13:43:42 object contains unparsed element: map[compute:map[aggregation:count] data_source:ci_tests group_by:[map[facet:error.type limit:100 sort:map[aggregation:count order:desc]]] indexes:[*] name:query1 search:map[query:@test.status:fail @ci.pipeline.name:"Test on PR"]]
2022/07/11 13:43:42 WARN: Fail read resource from provider, wait 300ms before retry
2022/07/11 13:43:43 object contains unparsed element: map[compute:map[aggregation:count] data_source:ci_tests group_by:[map[facet:error.type limit:100 sort:map[aggregation:count order:desc]]] indexes:[*] name:query1 search:map[query:@test.status:fail @ci.pipeline.name:"Test on PR"]]
2022/07/11 13:43:43 WARN: Fail read resource from provider, wait 300ms before retry
2022/07/11 13:43:44 object contains unparsed element: map[compute:map[aggregation:count] data_source:ci_tests group_by:[map[facet:error.type limit:100 sort:map[aggregation:count order:desc]]] indexes:[*] name:query1 search:map[query:@test.status:fail @ci.pipeline.name:"Test on PR"]]
2022/07/11 13:43:44 WARN: Fail read resource from provider, wait 300ms before retry
2022/07/11 13:43:44 Fail read resource from provider, trying import command
2022/07/11 13:43:44 Filtered number of resources for service dashboard: 1
2022/07/11 13:43:44 datadog Connecting....
2022/07/11 13:43:44 datadog save dashboard
2022/07/11 13:43:44 datadog save tfstate for dashboard

Same here.  After manually creating a dashboard I've got this error importing via terraformer:
2022/08/08 13:40:43 WARN: Fail read resource from provider, wait 300ms before retry
2022/08/08 13:40:44 object contains unparsed element: map[compute:map[aggregation:count] data_source:ci_tests<EMAIL_ADDRESS>limit:500 sort:map[aggregation:count order:desc]]] indexes:[*] name:query1 search:map[query:test_level:test @ci.pipeline.name:"My Pipeline"]]

Versions
Datadog provider 3.14.0
Terraform v1.2.5
Terraformer version v0.8.21
Command run: terraformer import datadog --resources=dashboard --filter=dashboard="$DASHBOARD_NAME"

@skarimo
Put of interest ( and without looking in the PR :D ), what seems to be the fix?

@stiliajohny Just looked into this a bit more and my pr does not actually fix the issue. The issue is with missing datasource type here: https://github.com/DataDog/datadog-api-client-go/blob/master/api/datadogV1/model_formula_and_function_events_data_source.go#L16-L25
We are missing data_source:ci_tests. I had previously added data_source:logs_pattern_stream but missed the other one. Since the client doesn't recognize this type it is unable to parse the response properly. I will put up a fix and update the client again.

Hi all, quick update, we released the new version of Datadog terraform provider v3.15.0 which uses the latest datadog-api-client-go package and it now contains the support for both data_source:ci_tests and data_source:ci_tests enums. Thanks for the report.

is this still tracked ?

@skarimo  thanks for the update and the work on this !
Closing as done


Add a way to invoke user function that would return a page

What would that feature address
Following @dr-irv proposal, we want to propose a way for a Gui app to allow the rendering of page content from a specific URL.
Description of the ideal solution

call a GUI method with a specific path extension and a local function that will be invoked when the URL is requested
1.1. gui.add_user_content_cb("<extension name>", on_request)
1.1. in user code def on_request(state: State, path: str): <HTML Content as BytesIO> ...
at runtime
1.1. GUI utility function returns a valid URL from state, extension_name and rest of path. The URL can be used to update web UI
1.1. when the URL is requested (in the form /taipy-user-content//), on_request is invoked and content is returned
1.1. as an option, a python utility function can be provided to perform URL request from the UI and show the result in the current tab or a new tab

Caveats
The solution should have no impact on the current functionnalities
Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Propagate any change on the demos and run all of them to ensure there is no breaking change
[ ] Ensure any change is well documented

@dr-Irv use on_user_content(state, path, query)

@Dr-Irv use on_user_content(state, path, query)

I looked at the PR you merged that has on_user_content() and get_user_content_url(), and it's not clear to me how they interact.  Do you have an example that illustrates how to use them?


Errors on cygwin

On cygwin, with
./configure
make
I get this error.
c/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: mg-autoexec.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: mg-cmode.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: mg-grep.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: mg-cscope.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: mg-tags.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: mg-dired.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: mg-re_search.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here
/usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: mg-ansi.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: ../lib/fparseln.o:/c/Users/chris/Downloads/mg-3.4/src/./def.h:653: multiple definition of hlp'; mg-basic.o:/c/Users/chris/Downloads/mg-3.4/src/def.h:653: first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:500: mg.exe] Error 1
Now it's been a while since I coded C, but in def.h it has...
const char * hlp;
Seems like a no-no to declare a variable in a header file to me. Anyway I changed this to..
extern char * hlp;
and then it compiled and linked
But the other problem is, when I start the editor, nothing happens until I press any key. So if I type
src/mg foo [enter]
Nothing at all happens until I press some other key... like for example, pressing enter a second time. Or just pressing any key.

Hi!
This is fixed on the latest master branch, commit 29c83c9, which I've been dragging my feet to release.  It's pending a sync with the "upstream" OpenBSD sources.  I just tested master on an old Windows 10 install with Cygwin, and it works fine there.
Just remember, when building from GIT sources, you need to run ./autogen.sh first. More info in the README.


errors when loading object

testing release candidate 1 I get this and can't make it stop. Need clear documentation

Can you try adding s4pd/scm (not just s4pd) to your path and tell me if that does it? the object needs to find the scm files, which when you check out the code, are in the "scm" directory of the proejct. I mention this in the Readme, but if it's not adequately clear I can certainly improve it!

In the screenshot here, you can see my file preferences have the path where the scm files live added, which depends on where you checked out and built the code:

I just downloaded the mac zipped release, which unpacks to a 's4pd' folder, which I moved to externals.
this folder has no 'scm' subfolder (so there's nothing in it) - so yeah, this is confusing.
The help file also just says "The s4pd object takes 2 optional arguments, an integer for number of outlets, and a filename to load, searching the Pd filepath."
for the "Pd filpath" I understand it is the same folder the opened patch lives and the ones in Pd's added user search paths and the one in declare, so yeah, it's confusing, and it's also how pd objects usually work - so I suggest you do it like that, or is it something you can't really do?

Ah ok I see how we have wires crossed, I thought you were building from source. The readme says it's ready for building from source and you are using a pre-release, which I have not advertised as ready, so yes, it's not package ready. The directions are for building from source, and the users who have tried it out so far have been doing that. I will try to attend to these soon and let you know so that we can test the package. I really don't have experience with Pd packaging.
Thanks for the bug reports!

did you put the download as it is? cause there's no 'smc' folder...
I also did compile it myself and the result is a just a folder, with no subfolders, and all files just in it.
So in both cases it seems you need to manually alter things, and that's bad. I did what you said manually, I created the subfolder, I put all the files there, I added the extra subfolder to the preferences path, but that just seems like a bad idea/process.
But what seems bad is that you have hardcoded things like that, which is not really intuitive and "pd-like".
It makes sense to me to have the smc files that [s4pd] needs to instanciate (those would be s4pd.scm and s4pd-schedule.scm, right?) in the same folder as the external, and then it just looks for these two there. This would actually be one default folder that pd generally looks for files and you could also hardcode it in the object -  so no need for a 'smc' subfolder and also setting it up in the preferences, that seems like unnecessarily complicated.
Moreover, if you have a patch somewhere and you want to load files, it'd be good if the user could have more flexibility where to put them. Looking for it in the same folder as the patch is saved or wherever in the preferences paths is what's reasonable to me.
One can have a subfolder in the same folder of the patch called 'smc' or whatever and call files there by simply giving it a 'smcc/' prefix, this is what all externals I know do. I don't see why you'd have to make it differently.
Anyway, I hope you get what I mean.
cheers

fixed in src, will update ticket when fixed in release candidate and help updated

you can use 'c_externdir' from m_imp.h to get the external directory, see https://github.com/porres/pd-cyclone/blob/master/cyclone_objects/binaries/cyclone_lib.c#L640

that sounds promising, I'll try that. If it works, I can have it check for core scm files in user defined paths and fall back to the location of the external. thanks for the tip!

I can have it check for core scm files in user defined paths and fall back to the location of the external.

but isn't s4pd.scm and s4pd-schedule.scm always in the location of the external? Isn't that how you're packaging it? Why not make it look there first? They're needed every time you create the external, right?

closing, satisfied with how this is working now.


[kong] add support for stream listens

What this PR does / why we need it:
Adds support for stream listens as an additional listen type on the proxy.
Special notes for your reviewer:
I'm still running into issues with the balancer when attempting to configure these:
2020/04/03 20:45:38 [error] 37#0: *37954 lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/kong/runloop/balancer.lua:569: bad argument #1 to 'ipairs' (table expected, got nil)
stack traceback:
coroutine 0:
	[C]: in function 'ipairs'
	/usr/local/share/lua/5.1/kong/runloop/balancer.lua:569: in function 'get_all_upstreams'
	/usr/local/share/lua/5.1/kong/runloop/balancer.lua:612: in function 'get_upstream_by_name'
	/usr/local/share/lua/5.1/kong/runloop/balancer.lua:638: in function 'get_balancer'
	/usr/local/share/lua/5.1/kong/runloop/balancer.lua:919: in function 'execute'
	/usr/local/share/lua/5.1/kong/runloop/handler.lua:930: in function 'balancer_execute'
	/usr/local/share/lua/5.1/kong/runloop/handler.lua:1097: in function 'after'
	/usr/local/share/lua/5.1/kong/init.lua:622: in function 'preread'
	preread_by_lua(nginx-kong-stream.conf:66):2: in main chunk while prereading client data, client: <IP_ADDRESS>, server: <IP_ADDRESS>:9001

I'd run into them previously with TCPIngress testing and got them again when configuring manual test config for this. That definitely warrants investigation, but I don't think it's anything to do with the PR: the PR code is only setting up the listens and making them accessible, and that does work.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the next branch and targets next, not master
[x] New or modified sections of values.yaml are documented in the README.md
[x] Title of the PR and commit headers start with chart name (e.g. [kong])

Please update an existing test to include a stream listen in DB and DB-less mode. Otherwise, looks good.


XFA - Support tiff images

Firefox doesn't support natively tiff format so we need to implement a decoder for XFA.
As far as I know there are not so much pdf containing some tiff images.

Maybe we could use https://github.com/image-rs/image-tiff and compile it into wasm.

Assuming it'd work for the sort of TIFF images found in XFA documents, wouldn't a JavaScript solution be a lot simpler since it could be included directly using e.g. NPM; I've not tested it, but a quick web-search turned up https://www.npmjs.com/package/tiff

@Snuffleupagus, would you like to fix this bug ?

Attached are some PDFs that use TIF or TIFF (top left logo), as it may be helpful
[4808-69E (1).pdf](https://github.com/mozilla/pdf.js/files/7190869/4808-69E.1.pdf   - top left image
c0009_re_1587386188899_eng.pdf - bottom right image

Can i get this bug to get fixed?

Sure, feel free to work on this.

@OladapoAjala Yes, I've posted an issue I was facing above your comment, let me know if you have any idea.

Instead of doing npm install, I think you'll want to:

build a fully bundled version of tiff.js (hopefully this is possible, I haven't looked into it)
make a new tiff directory in external
move tiff.js and it's license in there
import it from there e.g. import "../../external/tiff/tiff.js

Once you have that working we should work on lazy loading the tiff module since it won't be used very often. This will require more work and bundling another file with the pdf.js build.

Is anyone still working on this? I would love to work on it if not. Or collaborate if someone is.
I did some tinkering and managed to figure out why the imports weren't working (the TIFF library was importing node's encoding and decoding utility, which webpack no longer has a default polyfill for; simply using the browser's API or a suitable polyfill should fix the problem).

@alinethome, no need to ask, just work on it.
You can submit a PR (even in draft mode) and we can then iterate on it.
What's the tiff lib you want to use ? its size ?

@calixteman Alright, good to know!
I was going to try with https://www.npmjs.com/package/tiff, Bundling it as @brendandahl suggested yielded a 255 kb file.

I was going to try with https://www.npmjs.com/package/tiff, Bundling it as @brendandahl suggested yielded a 255 kb file.

That sounds like a lot for a feature that's mostly unused (most XFA doesn't seem to include TIFF images), since it'd correspond to an approximately 14 percent increase of the pdf.worker.js file size in the MOZCENTRAL build.

Maybe we could use https://github.com/image-rs/image-tiff and compile it into wasm.

Given the size reported above, I cannot help wondering if this idea from https://github.com/mozilla/pdf.js/issues/13707#issuecomment-877378361 would actually be necessary!?

@Snuffleupagus I originally thought I would try lazy loading once I got the basic logic to work, but  I can definitely try to do that instead. The file size is without minifying, but I suppose it would still be quite big once minified.

I originally thought I would try lazy loading once I got the basic logic to work, but I can definitely try to do that instead.

Even if the TIFF image decoder is loaded lazily, the file itself still needs to be shipped together with the PDF.js library (in e.g. Mozilla Firefox).

The file size is without minifying, but I suppose it would still be quite big once minified.

Indeed, even when minified it'd risk being fairly large.
Also, to put the quoted TIFF decoder file size (i.e. 255 kB) into perspective, please note that the PDF.js library currently include image decoders for the JPEG, JPEG 2000, and JBIG2 image formats and those three together are actually smaller than that.
Hence why it'd be interesting to compare the size of the Rust library compiled to Wasm, as was suggested earlier in the thread.

I added
[profile.release]
opt-level = 's'

in the cargo file to optimize on size
and without jpeg and flate2, I get a size around 163K.

can i work in this issue, if this issue isn't solve yet

Given the discussion above it's not clear to me that this is actually a "good beginner bug", hence removing the label.


WIP: Error codes

Adds an additional code field to SendPaymentFailed as a proof of concept.
Err(SdkError::SendPaymentFailed {
    code: SendPaymentFailedCode::AlreadyPaid,
    err: "Invoice already paid".into(),
})

Kotlin output:
SdkException.SendPaymentFailed {
    code: SendPaymentFailedCode.AlreadyPaid,
    err: "Invoice already paid",
}

Swift output:
SdkError.SendPaymentFailed {
    code: SendPaymentFailedCode.AlreadyPaid,
    err: "Invoice already paid",
}

RN output:
Error {
    code: "SendPaymentFailed.AlreadyPaid",
    message: "Invoice already paid",
}

Fixes #459

FYI, it seems when using the interface as an error the err field is not mapped to the bindings Error(message), but instead extends the ExtendedError(code, err) : Error(). So the Error message is not set. This is the case at least for swift and kotlin. I'm looking into it
https://github.com/mozilla/uniffi-rs/issues/1434

Fixes #336


Create a Visual Studio 2022 solution

Brief description
With the transition developers are making to Visual Studio 2022, this feature request is to simply provide a solution file to enable compilation of the source code in Visual Studio 2022.

This issue has been dealt with by #180


Add missing properties to default theme

added functional theme properties that existed in editor theme, but not default theme: GraphEdit title_h_offset, OptionButton modulate_arrow
removed unused properties: LineEdit read_only, TooltipLabel font_color_shadow
fixed modulate_arrow displaying wrong color for DRAW_HOVER_PRESSED
implemented missing disabled icons in PopupMenu (and added them to default theme)

Resolves #33370

It look good to me in general, please arrange with @YuriSizov what may be needed to be fixed.

Thanks!


Failing dotnet database update

Steps to reproduce
Difficult to tell, on some PCs the error is reproducable on others not.
Tested the behaviour with LocalDB and SQL Server Express.
Expected  behavior
After a dotnet database drop (-f) the database is deleted, if it did not exist nothing changes
After dotnet database update a new one is created.
Actual behavior
dotnet database drop cannot delete database,
after manual deletion cannot delete because not exists.
Then dotnet database update fails because database exists, even if database drop reports database does not exist.
On file system the database does not exist (in case of LocalDB).
So in short drop fails because not exists, update because exists.
Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-preview2-003121)
Product Information:
Version:            1.0.0-preview2-003121
Commit SHA-1 hash:  1e9d529bc5
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.14393
OS Platform: Windows
RID:         win10-x64

@SimonRuehle it is hard to guess why you couldn't drop the database in the first place but for future reference deleting the mdf/ldf files from disk can leave the SQL Server database in an inconsistent state, e.g. when SQL Server needs to reason about the existence of the database, it normally uses internal system tables stored in the master database rather than the files on disk, so I am not completely surprised that "manual deletion" didn't help.
It would be useful if you could capture and provide the full input and output (with the -Verbose flag) of the commands that fail to drop the database.

@divega The point with restoring/resetting LocalDB is valid, if I reset the LocalDB it works again (until the next try to delete the database).
The output:
D:\Projects*\src*>dotnet ef database drop -f --verbose
Using target project ''.
Using startup project ''.
Using framework 'net461'.
Using configuration 'Debug'.
Running C:\Program Files\dotnet\dotnet.exe build D:\Projects*\src*\project.json --configuration Debug --
framework net461
Process ID: 7340
Project * (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Project * (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Project * (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Project * (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Project * (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Setting the data directory to 'D:\Projects*\src*\bin\Debug\net461\win7-x64'.
Invoking dependency command 'Microsoft.EntityFrameworkCore.Design' in project '*'
Running D:\Projects*\src*\bin\Debug\net461\win7-x64\Microsoft.EntityFrameworkCore.Design.exe --assembly
D:\Projects*\src*\bin\Debug\net461\win7-x64*.exe --startup-assembly D:\Projects*\src\Cet
oDocs\bin\Debug\net461\win7-x64*.exe --dispatcher-version 1.0.0-preview2-21431 --data-dir D:\Projects*\s
rc*\bin\Debug\net461\win7-x64\ --project-dir D:\Projects*\src* --content-root-path D:\Projects\C
etoDocs\src* --root-namespace * --verbose database drop -f
Process ID: 2588
Finding DbContext classes...
Using context 'ApplicationDbContext'.
Dropping database '*Angular2'.
Database '*Angular2' did not exist, no action was taken.
D:\Projects*\src*>dotnet ef database update --verbose
Using target project ''.
Using startup project ''.
Using framework 'net461'.
Using configuration 'Debug'.
Running C:\Program Files\dotnet\dotnet.exe build D:\Projects*\src*\project.json --configuration Debug --
framework net461
Process ID: 460
Project WDSEHelp (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Project *.DataModel (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Project *.Database (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Project .Core (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Project * (.NETFramework,Version=v4.6.1) was previously compiled. Skipping compilation.
Setting the data directory to 'D:\Projects*\src*\bin\Debug\net461\win7-x64'.
Invoking dependency command 'Microsoft.EntityFrameworkCore.Design' in project ''
Running D:\Projects*\src*\bin\Debug\net461\win7-x64\Microsoft.EntityFrameworkCore.Design.exe --assembly
D:\Projects*\src*\bin\Debug\net461\win7-x64*.exe --startup-assembly D:\Projects*\src\Cet
oDocs\bin\Debug\net461\win7-x64*.exe --dispatcher-version 1.0.0-preview2-21431 --data-dir D:\Projects*\s
rc*\bin\Debug\net461\win7-x64\ --project-dir D:\Projects*\src* --content-root-path D:\Projects\C
etoDocs\src* --root-namespace * --verbose database update
Process ID: 2624
Finding DbContext classes...
Using context 'ApplicationDbContext'.
System.Data.SqlClient.SqlException (0x80131904): Cannot create file 'C:\Users\Simon*Angular2.mdf' because it alr
eady exists. Change the file path or the file name, and retry the operation.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInA ction)    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectio nLock, Boolean asyncClose)    at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, B ulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)    at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean as yncWrite)    at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource1 completion, String methodName, Boo
lean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.Execute(IRelationalConnection connection, String
executeMethod, IReadOnlyDictionary2 parameterValues, Boolean openConnection, Boolean closeConnection)    at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.ExecuteNonQuery(IRelationalConnection connection,  IReadOnlyDictionary2 parameterValues, Boolean manageConnection)
at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQuery(IEnumerable`1 migration
Commands, IRelationalConnection connection)
at Microsoft.EntityFrameworkCore.Storage.Internal.SqlServerDatabaseCreator.Create()
at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)
at Microsoft.EntityFrameworkCore.Design.MigrationsOperations.UpdateDatabase(String targetMigration, String contextTyp
e)
at Microsoft.EntityFrameworkCore.Tools.Cli.DatabaseUpdateCommand.<>c__DisplayClass0_0.b__0()
at Microsoft.Extensions.CommandLineUtils.CommandLineApplication.Execute(String[] args)
at Microsoft.EntityFrameworkCore.Tools.Cli.Program.Main(String[] args)
ClientConnectionId:32168161-df4d-4c55-8624-69cb6b0214ed
Error Number:5170,State:4,Class:16
Cannot create file 'C:\Users\Simon*Angular2.mdf' because it already exists. Change the file path or the file nam
e, and retry the operation.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

LocalDB seems to be in a bad state. Try...

Deleting all the *.mdf and *.ldf files under %USERPROFILE%

Running the following commands.
 SqlLocalDB stop
 SqlLocalDB delete

Trying the EF commands again

Triage: we believe we have answered your question, but feel free to reopen if you still run into issues after applying the recommended measures.


give anomaly borg module a signaller

About the PR
signaller and multitool
Why / Balance
borgs doing anomaly cant activate the ape this lets them do that
also for keeping it maintained
Technical details
no
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
no
Changelog
no cl no fun

maybe not a multitool, but a network configurator?
The thing is, the multitool and screwdriver are in the tool cyborg module, and I don't like duplicating items. and the network configurator is only needed by the device for machine communication anyway.


Update package.json to support react 17

Hi, I've moved the code from master to a v3 branch because we're going to merge the v4. I've updated the code and released the v3.1.0, you can install it by doing npm i<EMAIL_ADDRESS>


Add image maps - <map> and <area>

Uses compute_from: html.elements.area since ping pushes it to be not baseline.

@petele can you exclude the download and ping? I think we should create separate features for these, aligning with https://caniuse.com/download and https://caniuse.com/ping.

I think these keys from https://github.com/web-platform-dx/web-features/pull/1425 should also be part of this feature:

api.HTMLImageElement.isMap
api.HTMLImageElement.useMap
html.elements.img.ismap
html.elements.img.usemap

Can you also exclude srcset and sizes so that we can have a feature matching https://caniuse.com/srcset? I would also remove api.HTMLImageElement.currentSrc since that's related to srcset.


[LMS-198] Fix slash consistency

Poetry is complaining that the lock file is out of data for Google, Schoology, and the file tester. @bradbanister can you run poetry lock to update? Otherwise everything looks fine and behaves correctly.

Very strange, particularly the file-tester where I hadn't changed the toml or lock file.  Anyway, running poetry lock --no-update seems to have fixed everything...


Runtime error with latest Docker image

Component
server
Describe the bug
With the latest Docker image I get an runtime error after the agent connects to the server:
...
woodpecker_1        | [GIN-debug] POST   /api/hook                 --> github.com/woodpecker-ci/woodpecker/server/api.PostHook (12 handlers)
woodpecker_1        | [GIN-debug] GET    /stream/events            --> github.com/woodpecker-ci/woodpecker/server/api.EventStreamSSE (12 handlers)
woodpecker_1        | [GIN-debug] GET    /stream/logs/:owner/:name/:build/:number --> github.com/woodpecker-ci/woodpecker/server/api.LogStreamSSE (15 handlers)
woodpecker_1        | {"level":"debug","time":"2021-12-08T11:36:14Z","message":"agent connected: agent: polling"}
woodpecker_1        | panic: runtime error: invalid memory address or nil pointer dereference
woodpecker_1        | [signal SIGSEGV: segmentation violation code=0x1 addr=0xa0 pc=0x9cec57]
woodpecker_1        |
woodpecker_1        | goroutine 50 [running]:
woodpecker_1        | github.com/woodpecker-ci/woodpecker/server/model.Tree(0xc00020e680, 0x4, 0x32, 0x4, 0x32, 0x0)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/model/proc.go:74 +0x117
woodpecker_1        | github.com/woodpecker-ci/woodpecker/server/grpc.(*RPC).Update(0xc0002d01c0, 0x13d6018, 0xc000242030, 0xc0003bb99c, 0x4, 0xc0003bba78, 0x5, 0x0, 0x0, 0x61b095a1, ...)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/grpc/rpc.go:144 +0x88b
woodpecker_1        | github.com/woodpecker-ci/woodpecker/server/grpc.(*WoodpeckerServer).Update(0xc0002d01c0, 0x13d6018, 0xc000242030, 0xc0003bd4c0, 0xc0002d01c0, 0xc000230378, 0xc000242780)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/server/grpc/rpc.go:567 +0x1ff
woodpecker_1        | github.com/woodpecker-ci/woodpecker/pipeline/rpc/proto._Woodpecker_Update_Handler.func1(0x13d6018, 0xc000242030, 0x11303a0, 0xc0003bd4c0, 0x0, 0x203000, 0x7f914451be60, 0x18)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/rpc/proto/woodpecker_grpc.pb.go:274 +0x89
woodpecker_1        | main.(*authorizer).unaryIntercaptor(0xc0001a0cf0, 0x13d6018, 0xc000242030, 0x11303a0, 0xc0003bd4c0, 0xc0003c0ac0, 0xc00021a990, 0x18, 0x10d6e00, 0xc000242001, ...)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/cmd/server/server.go:313 +0xb0
woodpecker_1        | github.com/woodpecker-ci/woodpecker/pipeline/rpc/proto._Woodpecker_Update_Handler(0x114ab40, 0xc0002d01c0, 0x13d6018, 0xc000242030, 0xc000202840, 0xc0001a0d20, 0x13d6018, 0xc000242030, 0xc0004fce20, 0x1b)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/rpc/proto/woodpecker_grpc.pb.go:276 +0x150
woodpecker_1        | google.golang.org/grpc.(*Server).processUnaryRPC(0xc0001ec8c0, 0x13dfcd8, 0xc00008b800, 0xc00036e900, 0xc0000e94a0, 0x19d4af8, 0x0, 0x0, 0x0)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/google.golang.org/grpc/server.go:1279 +0x52b
woodpecker_1        | google.golang.org/grpc.(*Server).handleStream(0xc0001ec8c0, 0x13dfcd8, 0xc00008b800, 0xc00036e900, 0x0)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/google.golang.org/grpc/server.go:1608 +0xd0c
woodpecker_1        | google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc0003bb8a0, 0xc0001ec8c0, 0x13dfcd8, 0xc00008b800, 0xc00036e900)
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/google.golang.org/grpc/server.go:923 +0xab
woodpecker_1        | created by google.golang.org/grpc.(*Server).serveStreams.func1
woodpecker_1        | 	/woodpecker/src/github.com/woodpecker-ci/woodpecker/vendor/google.golang.org/grpc/server.go:921 +0x1fd

System Info
Version
{"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-4642d98f"}

Config
services:
  database:
    image: postgres:13-alpine
    restart: always
    environment:
      - POSTGRES_USER=...
      - POSTGRES_PASSWORD=...
      - POSTGRES_DB=...
    volumes:
      - ./database:/var/lib/postgresql/data

  woodpecker:
    image: woodpeckerci/woodpecker-server
    restart: always
    ports:
      - <IP_ADDRESS>:8000:8000
    command: --log-level=trace
    volumes:
      - ./woodpecker:/var/lib/woodpecker/
    depends_on:
      - database
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=https://ci.sp-codes.de
      - WOODPECKER_DATABASE_DRIVER=postgres
      - WOODPECKER_DATABASE_DATASOURCE=postgres://...:...@database/...?sslmode=disable
      - WOODPECKER_GITEA=true
      - WOODPECKER_GITEA_URL=https://git.sp-codes.de
      - WOODPECKER_GITEA_CLIENT=...
      - WOODPECKER_GITEA_SECRET=...
      - WOODPECKER_AGENT_SECRET=...
      - WOODPECKER_ADMIN=...

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server.

It's likely a corrupt entry in database.
the cause of this I'm not aware of ... but I'll created a pull to least report back instead of panic
-> #582

PS: you have to stop not kill the agent or else it wont have time to report back new state of running tasks
PS: PS: if server is already down before the agent ... it has a similar effect ... we are of it and looking for solutions


Improve changelog generator

I've tweaked the changelog generator script a bit:

Parameters are now optional, uses default values pointing to this repo and the latest milestone
Next improvement would be named arguments so you can override only one of the defaults at a time
All URLs point to human-friendly HTML pages instead of pointing to API responses
Titles are trim()med to avoid leading and trailing spaces

Sample output before (for M12)
M12

Suppress for TooManyFunctions is not considered in detekt - #108
Update documentation and migration guide for M12 - #105
NoDocOverPublicClass always reported for objects - #104
...
Baseline does not work anymore as expected due to inner restructure for the new output formats  - #83
...

See all issues at: M12
Sample output after (for M12)
M12

Suppress for TooManyFunctions is not considered in detekt - #108
Update documentation and migration guide for M12 - #105
NoDocOverPublicClass always reported for objects - #104
...
Baseline does not work anymore as expected due to inner restructure for the new output formats - #83
...

See all issues at: M12

Awesome thx @rock3r ! :)  (#121)