remap keys: impossible to select a 2 keys combo to be remapped

Microsoft PowerToys version
0.82.1
Installation method
Microsoft Store
Running as admin
No
Area(s) with issue?
Keyboard Manager
Steps to reproduce
I cannot select 2 keys to be remapped.
example :
CTRL + L
Powertoys allows me to select CTRL or L but not both !
windows 11 Home 23H2
Lenovo Legion Pro 5 16IRX9 - Type 83DF
✔ Expected Behavior
when I press CTRL then L, I expect Powertoys to register the combinaison CTRL+L to be remapped.
❌ Actual Behavior
when I press CTRL then L, Powertoys first registers CTRL, then it registers L.
Other Software
No response

Can you take a screenshot?  Are you remapping a key or shortcut?
right now this sounds like you want to do a shortcut.
/needinfo

hi crutkas,
many thx for quick reply.
Your comment makes me realize I didn't understand all functionnalities of Kerboard Manager.
Problem between keyboard and chair.
I finally succeed to remap the copilot key to right ctrl using "remap a shortcut". :)
I'm closing the issue.
sorry for the noise

No worries. Glad to help.

Here is a q, what could have helped make it more clear?

Let me explain what I was trying to do :
I wanted to remap the "copilot" key to "right ctrl".
So I first concentrate my effort on "Remap a key" (seems the most logical to me ;) ).
"copilot" key was identified as F23, I sent it to "right ctrl".
But it didn't work.
got the warning : the following key do not have assignments
I thought that it was the cause why it didn't work. (mistake #1)
So I tried to remap a "random" combo of keys to F23, not to left it unassigned.
For that, I tried to use "Remap a key" again (mistake #2) ... without success ... thus my post.
Reading your answer, I tried "remap a shortcut", always to remap a "random" combo of keys to F23, not to left it unassigned. (mistake #2b)
Doing so, I noticed that "copilot" key was identify as : win(left) shift(left) F23.
So I finally delete all my useless remapings, and tried :
remap a shortcut : win(left) shift(left) F23 -> ctrl(right)
\o/
remarks :

I could not guess that the "copilot" key was in fact a shortcut.
I should have read the help more carefully.
I didn't get that "shortcut" means "multi key combinaison"
I'm not a native english, but I prefer to use my software in english because translations can be so bad. But sometimes I missed some point.


Seed blocks need updating for 380000 to 390000

Block 390000 has passed, seed blocks should be updated.

Note to avoid duplication of effort - I'm part way through this and will submit in the morning.

Haha, awesome. I'm very very glad you're on this! I probably would have started from scratch, or digged through the old threads to find the bits of last time. :)


Boot from existing Cloud Block Storage issue #91

Added the feature to allow users to boot from the new flavors on existing cloud block storage.

Hi there -- if you would be willing to rebase this, I'd love to still merge it in. Thanks!

Closing this out since we never heard back on the rebase


Is this library for both React and React Native?

Is this library for both React and React Native?
Based on readme, seems it is for React only. But I saw this conversation at https://github.com/ArnaudBarre/eslint-plugin-react-refresh/issues/28 which can also be React Native? Am I correct? Thanks!

Fast refresh is also used in RN, but I don't know how metro, the default RN bundler, handle this. I saw some people succeded to make Vite works with RN, in that case this rules will have a big impact on HMR speed.

I see, thank you for clarifying, @ArnaudBarre ! 😃


Add ability to use QEMU and virtiofsd from package

Why not just always use the packaged QEMU and save the additional PACKAGE variable and existing ones?

Why not just always use the packaged QEMU and save the additional PACKAGE variable and existing ones?

It is better to have the ability to compile a specific version if it is needed. Maybe switch the default to PACKAGE but leave the ability to compile too.


sdk_spi_flash_erase_sector + sdk_spi_flash_write doesn't work

I use the combination of sdk_spi_flash_erase_sector + sdk_spi_flash_write to write out same data to the flash memory. But after reading it back the result still contain what it was already there previously. In other words it doesn't change the content of the sector.
Here is an example code that tries to update the 100th sector.
char buffer[8] = "test1234";
sdk_spi_flash_erase_sector(100);
sdk_spi_flash_write(100 * 4096, (uint32_t*) &buffer, 8);
char result[8];
sdk_spi_flash_read(100 * 4096, (uint32_t*) &result, 8);
printf("result: %.8s", result);

How do you set QIO mode? I have several modules with ID C84016 (sdk_spi_flash_get_id() returns 1640C8, but I think this number must be byte swapped to get the correct ID). With these modules, everything works fine. But I am now using other modules with flash ID E04016 (different manufacturer) and flash does not work. I have tried using both sdk_spi_XXX functions, and spiflash_XXX functions without success. Maybe my problem is the same as yours.

OK, I found out that the way was easier than expected: using the download tool.
I tired first downloading my application with all the modes, and none worked. Then I noticed that the bootloader was run before my application, so flashed the bootloader with QIO mode and... voila! It works :)


oasis-node crashes, if metrics in push mode and PGW crashes

Currently, if oasis-node is run in metrics push mode and push gateway unexpectedly crashes, so does oasis-node.
Improve oasis-node Prometheus pusher code as follows:

If PGW is not responding, try to reconnect.
When starting oasis-node in push mode and if PGW is not accessible, try to reconnect instead of failing to start.

How does it crash, any stack traces?

If PGW is not responding, try to reconnect.

Make the upstream code not brain-damaged then.
https://pkg.go.dev/github.com/prometheus/client_golang/prometheus/push?tab=doc#Pusher.Push


Currency#enabled functionality should work in pair with Market#enabled

#855
In case we will make some currency invisible the market with the same currency will still be displayed on trading UI. This may lead to sucked orders.
STR:

Create an order on market pare usd/xrp.
Go to admin panel and remove check box from XRP Currency#visible.
Go back to market usd/xrp (update the page). Already created trades are saved there but cannot be canceled by user.
Click on the, previously created, order.
Click on create order (orders should be on the same side buy/sell).

Tho the trading UI will response with "Fail" the order will be created (it can be checked in the order history of your account)
Go to admin panel and click check box from XRP Currency#visible.
Go back to market usd/xrp (update the page).
Find that your order is displayed on your orders panel but not on the all orders panel.

Try to delete order that was created while the XRP Currency#visible was disabled by any means available to a customer.
Try to create a matching order to move the order to the Done state.

Result: You will fail to delete or match this order and you will stack with frozen balance.

When I disable currency it should also disable all related markers in after_update callback.

Fixed via #1233.


Device Removal under high memory usage

Description
I am seeing a consistent DMA page fault causing device removal when trying to capture a frame under high GPU memory usage.
The crash is happening inside D3D12ResourceManager::Prepare_InitialState, there are no errors/warnings from D3Dd debug layer.
The issue happens only if ResidencyManager is enabled, and I suspect making resources resident inside Prepare_InitialState might be causing eviction of existing resources without notifying the application. One workaround that seems to work is to force MakeResident call on all the resources (I guess that might be bringing in the evicted resources).
I am planning on reducing memory usage in my application, just wanted to check if this is a known issue/limitation. I don't see how Renderdoc might be able to work with third party engines to manage resource lifetime.
The crash doesn't occur when using D3D11.
The crash doesn't occur if I run 3-4 instances of UE4 with similar workload (GPU memory usage maxed out)
Steps to reproduce

Make sure the GPU memory usage is ~70-80%
Open a memory intensive level in UE4 with D3D12ResidencyManager enabled (enabled by default)
Try to capture frame and notice crash in renderdoc.dll

Environment

RenderDoc version: 1.18 release version (built from 3996d037)
Operating System: Windows 10 v1909
Graphics API: D3D12
Unreal Engine 4 (D3D12 Residency enabled)
GPU: RTX 2080

I don't know what D3D12ResidencyManager is, I guess from context this is referring to something in your code?
The residency management in RenderDoc is fairly simple and just aims to ensure that resources are resident while they're being snapshotted, by temporarily making them resident then evicted again. Aside from affecting the overall memory footprint temporarily this should have no side-effects according to the API docs (which are admittedly quite unreliable as this is D3D12).
It's certainly the case that capturing in RenderDoc does require some memory headroom and you can run into out of memory issues, however I don't understand how that could manifest with it only occurring when memory is mostly-but-not-completely full. Are you absolutely sure that's the cause and this isn't a random crash which happens intermittently and by coincidence has only happens when you have memory partly full?
I need more information and detail in the steps to reproduce to be able to investigate this. I have UE4 available but I don't know what D3D12ResidencyManager is nor do I have any memory intensive projects to open. If you understandably can't share your own then could you point at a sample or demo project which does reproduce this issue?

Hi, thanks for getting back so quickly :)
By D3D12ResidencyManager, I meant the default residency management solution Unreal is using (https://github.com/microsoft/DirectX-Graphics-Samples/blob/master/Samples/UWP/D3D12Residency/src/d3dx12Residency.h)
I am on UE 4.26.2
The residency management in RenderDoc is fairly simple and just aims to ensure that resources are resident while they're being snapshotted, by temporarily making them resident then evicted again.
Yes, Renderdoc is using ref counting (m_Resident) to check if resource is evicted/resident. My theory was that this ref count might be unreliable if due to some reason an existing resource is evicted by system but Renderdoc thinks it's already resident (m_Resident  > 0). This is what I tested by forcing m_Device->MakeResident(..) call on the resource irrespective of m_Resident value.
I am almost 90% sure System is evicting the source texture (used for copy operation). I can see a resource which has similar description as the destination resource (buffer for copy op) getting evicted a few calls before Renderoc tries to use it. I wasn't able to verify if its indeed the resource used by copy op as I am not sure how to get that info from GPUView and I am not aware of any other software available to diagnose this issue :)
However I don't understand how that could manifest with it only occurring when memory is mostly-but-not-completely full
I wasn't clear on this one. My project uses a lot of memory so by the time capture is almost done the memory utilization is maxed out, so the issue also happens if memory is almost full.
If you understandably can't share your own then could you point at a sample or demo project which does reproduce this issue?
Sadly I won't be able to share the project :( , this issue happens on my work project.
I'll try to see if I can hack something up for you to try :)
Regards

Yeh I mostly wondered if you could reproduce the same behaviour with a public project of some kind - tech demo, tutorial, or others - I believe there are a lot out there, but without being able to know exactly it would take a long time (and if the repro isn't 100% reliable I may not be able to tell at all).
Without being able to reproduce the problem it's difficult to investigate any further. There shouldn't be any way for RenderDoc to miss a call to make resident or evict, as the only APIs that do that are intercepted, but with what you say possibly this is a multithreaded race condition or similar?
If you're able to test, you could try adding a lock in to prevent MakeResident/Evict from happening while RenderDoc is gathering resources. Most other work is already prevented from happening since this is intended to be 'atomic'. A patch something like this (not heavily tested, might deadlock) should work: residency.txt Just in case that patch also adds a GPU flush before starting the work, just in case an EnqueueMakeResident is still pending, but I don't think that should be possible.
In principle it would be feasible to always call MakeResident (since the eviction status is refcounted as you say), but the problem is currently we flush the GPU after the copy to be able to evict again. This would either require flushing after every copy, or else the resident set would increase by every resource we want to copy (or at least all up to some limit), so I'd rather not do that unless it's absolutely necessary for correct functioning.

Ok, I was able to repro this on a sample project as well :)
May I know how much VRAM your system has? I will tweak the memory consumption according to that. My system uses 11gigs so my test case might not load on your system :p
I will be attaching the project built on UE 4.27.2, its available through Epic Launcher.

I have a couple of different systems available but I have a 2080 Ti with 11GB VRAM so it makes sense to most closely match your system.

https://drive.google.com/drive/folders/1CkwHPHvm1WA-vYBvbKbTZHMtDvZbE2ge?usp=sharing
You can grab the sample from that link.
its a modified version of https://www.unrealengine.com/marketplace/en-US/product/sun-temple?lang=en
I've added a Niagara system NS_EatMemory which should allocate huge chunk of memory.
the memory usage by Niagara fluctuates a bit (i couldn't get it to maintain high mem usage), so what works is to compile the system and then try to grab capture.
I've added some steps with the zip file.
Let me know if you need any more info :)

If you're able to test, you could try adding a lock in to prevent MakeResident/Evict from happening while RenderDoc is gathering resources. Most other work is already prevented from happening since this is intended to be 'atomic'
Just to be clear, what I interpreted from GPUView capture was that the resource was being evicted by Windows System, not renderdoc or host application.

Yeh to clarify I don't know how the windows memory system works under the hood, but it would only be a bug in RenderDoc if there is some API-level evict happening followed by use of the resource. If everything is correct according to the API (as in everything properly resident and synchronised such that residency is ensured while the GPU is executing) then even if windows is evicting something behind the scenes and faulting on that, that's a windows bug and not something I can realistically do anything about.
I'll test the repro you've given tomorrow and look into it in more detail - I suspect it will come down to an API level residency issue but I'd need to dig in to see what it is.

I tried testing this, though I wasn't able to click 'compile' in your repro steps without my whole machine locking up quickly after. Fortunately I did get the necessary 10GB VRAM allocated just by opening up the second window and not clicking compile.
Unfortunately though my secondary windows 10 dev machine only has 16GB of RAM so I ran into (I assume) unrelated issues failing to allocate readback buffers. I'm sorting out ordering more RAM to be able to reproduce properly but I think this will have to wait until that arrives.

Also, if you can swap GPU (one with lower VRAM), you should be able to disable some of the allocations from Niagara system.

Yeh I did try playing with something along those lines as a workaround, but the other card I have is still 8GB of VRAM so I still hit out of memory errors.

Hello, did you get a chance to test this with more CPU RAM? :)

I've tried to reproduce this now with 48GB of CPU RAM and unfortunately I still can't. Most of the time I'm now able to capture and open it successfully. Sometimes it does hit a hang/out of memory but I'm not reading into that too much yet since the UE4 editor is still running in the background eating a lot of resources. I didn't see any crashes while capturing though, it always successfully captured.
I can try and dig in further into the intermittent crashes on replay and see if they're even reproducible with normal memory use, but from your description you were always seeing the crash on capture?
Are you able to reproduce this on any other system? is it possible that there's any other external configuration that might be affecting the repro?

Hello, yes I was able to reproduce it on my work (Intel cpu + 2080Ti) and home PC (AMD cpu + 1080Ti).
Its also crashing for everyone on my team, we have very different PC specs (including AMD gpus as well).
Can you try with 32GB CPU Ram if possible? I am wondering if exhausting GPU shared mem could be a factor as well :?

I tried with 32GB of RAM but I still get similar results (no crash during capture, replay fails more regularly with out of memory errors since it's needing more shared GPU memory for uploading data).
Just to completely nail down the reproduction steps in case I'm doing anything wrong or differently:

I launch UE4 4.27.2, installed from the epic games launcher, with ...\UE4Editor.exe "...\RenderdocRepro\SunTemple\SunTemple.uproject"
Wait for it to load, the RenderDoc plugin is active with plain v1.18 loaded.
Memory use at this point  is about ~5GB dedicated memory, negligible (0.2GB) shared memory.
Select the NS_EatMemory object and double click on the 'Niagara System' button to open the popup window.
At this point for me the dedicated memory reliably increases to ~10GB, shared memory still the same.
Capturing here doesn't reproduce the crash during capture.
If I click 'compile' as in the repro steps, the GPU memory tends to drop to ~6GB dedicated, sometimes with some shared memory use sometimes without. I'm unsure if that's intended, but capturing in that situation also doesn't reproduce for me.

And to clarify, when you're able to reproduce on your different PCs are you using this above repro, or your actual original project? I'm assuming if you can reliably reproduce on both it's probably interchangeable, but I just want to check.
I don't know why this would be 100% consistent for you and not reproducible at all for me, but this difficulty does make me wonder if it is a timing bug after all (perhaps affected by some other variable we're not controlling for, or some difference in our systems). Can you test with this build with some speculative fixes and locking around residency calls, to see if it fixes the problem for you?

Hi, I tried that sample project on work PC and wasn't able to reliably reproduce the crash :(
Using the custom build you provided:

Sample project on my local pc didn't crash, It would mostly just error out with "Out of Memory" error.
Work project on work PC is not crashing :)

I also tried launching sample project in the background to increase memory usage but it was still able to capture.
With multiple instances of project running each with their own Renderdoc capture caused device lost error when trying to replay capture, just to stress test. But still no crashes!

I guess the changes you made seem to work :)

And just to clarify, those OOM or device lost errors you encountered were no worse than it was before, and/or only in stress test conditions? i.e. with that build you're able to capture successfully the same as you used to be able to, and the cases that crashed before now either capture fine (hopefully?) or rather than crashing they gracefully report a failure to replay if they're out of resources?
The fixes were adding locking around MakeResident/Evict, since possibly what was happening was another thread was evicting resources in between RenderDoc checking if they were currently resident and trying to use them. Or I also noticed while adding that locking that I wasn't properly tracking residency of heaps - only resources - so possibly a heap was evicted behind a placed resource.
I'll push them shortly, but I wanted to check that there's no lingering issue here.

I encountered OOM issue only on my SampleProject under very high stress. I don't think it would be a likely scenario in real world application.
On work project I didn't encounter any issues using the same steps that were crashing v1.18. It was able to cope with multiple instances running as well. Also seemed to work fine for my colleagues :)


Certificate Not Applying (CertPath)

Empire Version
2.0 Beta
OS Information (Linux flavor, Python version)
Ubuntu - 16.04
Python 2.7.12
and
Kali - 2016.2
Python 2.7.13
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
Applying the CertPath option, and changing URL to use HTTPS.  The certificate seems like its not taking, when navigating to the page through a browser it shows as a insecure connection and the certificate information is not there. The previous version worked, and tested the certificate against multiple other services with success.
Any additional information
Testing the certificate with previous version works.

Is this the certificate error you are referring to @P0ng04 ? If you are using a self-signed certificate, there is no CA. Therefore, your browser will show that error message everytime. However the cert path is working. Try doing another git pull before attempting this again.

Thanks for the reply, I think I mentioned this before, but the certificate I have is valid, and works on the older version of empire.  I also use this certificate in my meterpreter handlers and it has not issues.  I will try another git pull and some more troubleshooting on my part and get back to you.  Good framework, could use some more modularity but I like where you guys have come and where you are.
Thank you very much for your assistance.  I hope I didn't come off brash.

From: Chris Ross<EMAIL_ADDRESS>Sent: April 22, 2017 1:15 PM
To: EmpireProject/Empire
Cc: P0ng04; Mention
Subject: Re: [EmpireProject/Empire] Certificate Not Applying (CertPath) (#466)
[2017-04-22 13_12_06-privacy error]https://cloud.githubusercontent.com/assets/9156069/25306552/6e2d1960-275d-11e7-981c-0880cff4e413.png
[https://cloud.githubusercontent.com/assets/9156069/25306552/6e2d1960-275d-11e7-981c-0880cff4e413.png]
Is this the certificate error you are referring to @P0ng04https://github.com/P0ng04 ? If you are using a self-signed certificate, there is no CA. Therefore, your browser will show that error message everytime. However the cert path is working. Try doing another git pull before attempting this again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/EmpireProject/Empire/issues/466#issuecomment-296387918, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AY9fNIuhkyqw0YuqmCMRBHYoS4CdzDxrks5ryjWagaJpZM4MUNlw.

I have the same problem with a version pulled from today (2017-05-30). Whatever I give as a value for CertPath in the listener/http setup is ignored. I can supply an arbitrary file e.g. /etc/passwd and the listener comes up without an error. However there is an easy fix, just copy the pem file over the default file created during setup in data/empire.pem. Since that file will be used anyway as long as you only need one listener you have no problem.

Fixed https://github.com/EmpireProject/Empire/commit/5a530fede9ddd064cd7dfea57ffc3868328ca456


Reset hints

Enhancement: Show a hint next to each "git reset" option explaining what it does.

Hi @stevage, nice suggestion with the reset mode hints :smile:
@divmain has the final say on these things, but I have a few suggestions:
Quick panel styling
If you give the show_quick_panel function a list of 2 element lists it will use the first item as the option title, and the second item as a subtitle, e.g. instead of this:
["mixed (default): unstage staged, keep unstaged, don't touch working (safe)", ...]

do this:
[["--mixed", "unstage staged, keep unstaged, don't touch working (safe)"], ...]

and it will look like this:

DRY reset modes
One nice thing in the old implementation was that the quick panel list was derived from GIT_RESET_MODES, so they couldn't go out of sync. How about changing GIT_RESET_MODES to:
GIT_RESET_MODES = [
    ["--mixed", "unstage staged, keep unstaged, don't touch working (safe)"],
    ["--soft", "just move HEAD, stage differences (safe)"],
    ["--hard", "discard staged, discard unstaged, update working (unsafe)"],
    ["--merge", "discard staged, keep unstaged, update working (abort if unsafe)"],
    ["--keep", "unstage staged, keep unstaged, update working (abort if unsafe)"]
    # For ref
    # ["--checkout", "keep staged, keep unstaged, update working, move branches (abort if unsafe)"]
]

Then you can pass GIT_RESET_MODES directly to show_quick_panel:
self.window.show_quick_panel(
    GIT_RESET_MODES, self.on_reset_mode_selection, flags=sublime.MONOSPACE_FONT
)

making sure to extract the mode to be passed to git from the first element of the selected list from GIT_RESET_MODES:
def on_reset_mode_selection(self, index):
    if 0 <= index < len(GIT_RESET_MODES):
        self.on_reset(GIT_RESET_MODES[index][0])

Squashing commits
As your second commit is just a tweak to the first one, it's probably better to squash them into one commit.

Agreed on all points!

Well, thanks for doing all the work there :) Only thing was, using the 2-element mode meant the drop down wasn't wide enough to actually read them (on my machine). So I've added some padding.
Also I've re-rebased and squashed. Not sure if that was really the right thing to do. shrug

Excellent - thanks for this!
As to the re-rebase + squash, that was appreciated also.  I use the git: generate changelog for release notes when a new version is published.  Having single, discrete feature-commits helps with this tremendously (as well as the TOPIC: ... format).

Ah, cool. I wasn't sure whether the "TOPIC: ..." thing was supposed to be a commit or in the PR comment - now I get it.


React.NET just doesn't want to install

I feel like this is a problem with just my solution, but, I'm trying to access the React.NET library for the Babel transformations. There is one teensy, weensy problem with it when trying to install React.AspNetCore.

React.NET has been tested with .NET Core 2.1, which is what I'm using for comparability reasons. This is just me trying to install on a fresh ASP.NET application. It might have something to do with my Linux distro, but I doubt it.
In the project I originally installed in, I'm using my own middleware instead of static file services provided by ASP.NET so I have more control, so a better question would be if I can use just the Babel transformations, as to an extent, that's all I really need. I don't know why I need to configure React.NET to transform my jsx files. Then again, I don't know much about React.NET.

Other people have this problem. See this issue, and this pull request.
Maybe I should think before posting an issue. This was late at night, and I was frustrated, so I do apologize.

Thanks for filing an issue. I don't have time to look into this right now, will try and push that PR forward again sometime soon.


Fix public exposure in Guacamole service

Resolves #4199
What is being addressed
The current behavior does not allow for dynamic configuration of the public_network_access_enabled parameter in the Guacamole workspace template.
This parameter is critical for determining whether the service should be exposed externally or restricted to internal access only.
How is this addressed

Introduced the public_network_access_enabled parameter with a default value of false to prevent public exposure by default.
Updated web_app.tf to map the parameter to var.is_exposed_externally.
Moved Azure Service Plan data retrieval to data.tf for better organization.
Updated documentation and incremented the template version.

/test-extended

/test-extended


Add Pycharm Project Files to Python .gitignore

Reasons for making this change:
Pycharm is a popular IDE for Python development. It has built-in GitHub integration, but also has a .idea folder where it stores project configuration. This doesn't need to be uploaded to GitHub, so I am PRing it to be added to the Python .gitignore

In this case, a PyCharm is preferred. Similar JetBrains.

We have an existing Global\JetBrains.gitignore that covers more than just this rule.

@bdougie Sure, but that doesn't have the Python stuff in it. For example venvs, pycache etc.

It should still live in a PyCharm.gitignore in the community folder

Closing for now as I believe this has gone stale and @bdougie had the right of it.
We have the PyCharm.gitignore that can be used instead.


Not getting verification mail

Subject: Not getting verification mail
Description:
I tried to sign up. User name (1st try) Lucasito and (2nd try) Lucasito2.
Results:
I filled the sign-up form, apparently everythings works fine, but I don't get the verification mail. But the data are in your system, because if I try to sign up again with the same user name I get the error message that the user name is taken.
Backend version: develop-0023fa73
Frontend version:
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0
Page: https://couchers.org/signup
User:

dupe #3520


T265 No device connected with C# Wrapper

Required Info

Camera Model
{ T265 }

Firmware Version

Operating System & Version
{Win (10)

Platform
PC.

SDK Version
(WIN10-<IP_ADDRESS>0)

Language
{C# }

Segment
{Robot }

Issue Description
I just stated with the T265 to bring it to run. The Demo is running stable. But when I try the C# Wrapper Example on Visual Studio 2019 I can see the T265, but when I try to start a pipe the error is shown "No device connected"
ExternalException: rs2_pipeline_start_with_config(pipe:000002914DA30060, config:000002914DA30300)
The c++ example and also the phyton program is starting the pipe without error.
I trid also old SDK Version until 2.31, but no differents.
Also I tried to install on a second PC, same result.
Thanks for help
Andreas

for C#, I've found I need to leave an empty serial number:
    public RsConfiguration DeviceConfiguration = new RsConfiguration
    {
        mode = RsConfiguration.Mode.Live,
        RequestedSerialNumber = string.Empty,
        Profiles = new[]
        {
            new RsVideoStreamRequest { Stream = Stream.Pose, StreamIndex = 0, Width = 0, Height = 0, Format = Format.SixDOF, Framerate = 0 },
            new RsVideoStreamRequest { Stream = Stream.Fisheye, StreamIndex = 1, Width = 0, Height = 0, Format = Format.Y8, Framerate = 0 },
            new RsVideoStreamRequest { Stream = Stream.Fisheye, StreamIndex = 2, Width = 0, Height = 0, Format = Format.Y8, Framerate = 0 }
        }
    };

If this doesn't help, you could post a sample of your code how you configure the pipeline.

I try the example from the wrapper itself and also a simple code like on the python program.
The code is running until pipe.Start(cfg).
Your code looks like from Unity Example, or? I can't find the RequestedSerialNumber on my example.
Code Example:
        Context ctx = new Context();
        var list = ctx.QueryDevices(); // Get a snapshot of currently connected devices
        if (list.Count == 0)
            throw new Exception("No device detected. Is it plugged in?");
        dev = list[0];
        sensor = dev.Sensors[0];

        textBox1.Text += sensor.Info[CameraInfo.Name] + Environment.NewLine;
        try
        {
            var cfg = new Config();
            cfg.EnableStream(Stream.Pose);

            var pipe = new Pipeline();
            pipe.Start(cfg);
        }
        catch (Exception ex) { MessageBox.Show(ex.Message); }

Ah, I've seen this issue before. For some reason, after querying for devices, I can no longer call pipe.Start as well. Using your code, I see the same issue locally. It goes away if I remove the  ctx.QueryDevices() line.
So does ensuring that I dispose of all the objects before calling pipe.Start:
            using (var ctx = new Context())
            {
                using (var list = ctx.QueryDevices())
                {
                    if (list.Count == 0)
                        throw new Exception("No device detected. Is it plugged in?");

                    using (var dev = list[0])
                    {
                        Console.WriteLine(dev);

                        using (var sensor = dev.Sensors[0])
                        {
                        }
                    }
                }
            }

Yes, thanks for your help. Now is working.
The code that was working for me.
            using (var ctx = new Context())
            {
                using (var list = ctx.QueryDevices())
                {
                    if (list.Count == 0)
                    {
                        lastError = "No device detected. Is it plugged in?";
                        throw new Exception(lastError);
                    }

                    using (var dev = list[0])
                    {
                        Console.WriteLine(dev);

                        using (var _sensor = dev.Sensors[0])
                        {
                            sensor = _sensor;
                        }
                    }
                }
            }

            pipe = new Pipeline();
            try
            {
                cfg = new Config();
                cfg.EnableStream(Stream.Pose);
                pipe.Start(cfg);

                threadGetData = new Thread(new ThreadStart(getData));
                threadGetData.Start();
            }
            catch (Exception ex) { lastError = ex.Message; }


skin protocol is error?

http://play.ogarul.tk/ is ok! but MultiOgar not work! skin is 'undefined'

same here it does not support the skins  for some reason.

^^ Are you using custom skins?

both dont work normal and custom, :d

ogarul uses protocol 4, as I know there is no way to use skin for protocol 4. Some protocol 4 clients may use hand made extensions, but it's undocumented and will works only with specific server. Protocol 4 also doesn't support large maps. I have no idea why protocol 4 still used in some clients. It's not so hard to change it to protocol 5 - just a small change for 2-3 lines of code.

how can I update my client protocol to version 5?

where can i find the protocol 5 client?

David1ali12: how to fix, see here: https://github.com/Barbosik/MultiOgar/issues/45
xinyuweb: for example http://ogar.mivabe.nl/?ip=<IP_ADDRESS>:443

Hi Barbosik, thanks for the amazing work you've done!
Could you show us how to implement protocol 6 with the following client ?
https://github.com/ItzLevvie/agario-client
It's the most readable client code so far, and would be nice to have protocol 6 working on it!

@LegitSoulja, read through this, this may have been why your server was acting up when you tried to increase the map size


Proxy returns 503 (Service Unavailable) in Browser

Hi, I am working with a yeoman generator-angular app and a remote API, my gruntfile config seems to be fine:
// Generated on 2015-06-01 using generator-angular 0.11.1
'use strict';
module.exports = function (grunt) {
  / * Removed for brevity */
  grunt.initConfig({
    yeoman: appConfig,
    watch: {
      / * Removed for brevity */
    },
    connect: {
      options: {
        port: 9000,
        hostname: 'localhost',
        livereload: 35729
      },
      proxies: [
        {
          context: '/api',
          host: 'subdomain.hostname.com',
          xforward: true,
          secure: false,
          headers: {
            'Authorization': 'RemovedToken'
          },
        }
      ],
      livereload: {
        options: {
          open: true,
          middleware: function (connect, options) {
            var middlewares = [require('grunt-connect-proxy/lib/utils').proxyRequest];

            middlewares.push(
                connect.static('.tmp'),
                connect().use('/bower_components',connect.static('./bower_components')),
                connect().use('/app/styles', connect.static('./app/styles')),
                connect().use(connect.static(appConfig.app))
            );

            return middlewares;
          }
        }
      },
      / * Removed for brevity */
    },
    / * Removed for brevity */
  });

  grunt.registerTask('serve', 'Compile then start a connect web server', function (target) {
    if (target === 'dist') {
      return grunt.task.run(['build', 'connect:dist:keepalive']);
    }

    grunt.task.run([
      'clean:server',
      'wiredep',
      'concurrent:server',
      'autoprefixer:server',
      'configureProxies:server',
      'connect:livereload',
      'watch'
    ]);
  });

  grunt.loadNpmTasks('grunt-connect-proxy');
};

grunt serve --verbose returns this when a request is made:
Proxied request: /api/foo/bar/?baz=6 -> http://subdomain.hostname.com:80/api/foo/bar/?baz=6
{
  "host": "localhost:9000",
  "connection": "keep-alive",
  "accept": "application/json, text/plain, */*",
  "user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36",
  "referer": "http://localhost:9000/",
  "accept-encoding": "gzip, deflate, sdch",
  "accept-language": "en-US,en;q=0.8,es;q=0.6",
  "cookie": "connect.sid=s%3AQpOp8pdI8GM2g8s0qCX602-ds-Xs-5le.C%2BrosIxHQ4ZcLLPgZKhABjji18kqK2K73C7mjF6scqM",
  "Authorization": "RemovedToken",
  "x-forwarded-for": "<IP_ADDRESS>",
  "x-forwarded-port": "9000",
  "x-forwarded-proto": "http"
}

I can't find any error there, maybe that the "host" is still localhost:9000, but I'm unsure if that could be a problem and in Chrome I am getting: 503 Service Unavailable, but there is indeed a service running, I know because I tested it with Postman and everything works fine, could somebody help me with this? Maybe I am missing something in the configuration?
Thanks.

After digging some more in the project I found that I had to specify the "host" header too.
https://github.com/drewzboto/grunt-connect-proxy/issues/72


Fixed crash in lz4 decompress of large data.

lz4 decompression is crashing with bus error on node.js. The issue is that destination buffer is allocated with the source size instead of destination size.

Ah 😅 , thanks a lot! I'll get the test runner working and merge. #24


Side Menu when clicked open to new tab

Hi,
Is there a way on how to implement this to open in new tab when click in side bar menu?
INavData
{
name: 'Old Portal',
url: '_blank',
href: 'https://test.net/admin/',
attributes:{ target: '_blank'},
iconComponent: { name: 'cil-apps' },
},

when I click the side bar it will just open at the same tab and not in new tab.
Please advise.
Thank you

I have figured it out. Replacing url to url:'target:_blank' and the rest is the same. Thank you


Fix diagnostics in Objective-C documentation comments appearing on the wrong line

Bug/issue #, if applicable: rdar://129668876
Summary
Now that Clang and Swift emits source ranges for documentation comments the same, we need to remove the DocC workaround that offset Objective-C ranges, otherwise diagnostics for Objective-C documentation comments will appear on the wrong line.
Dependencies
None
Testing
Add some content that will result in warnings to an Objective-C documentation comment and build documentation for it. For example:
#import <Foundation/Foundation.h>

NS_ASSUME_NONNULL_BEGIN

/// Some description of my class
///
/// Can link to ``doSomething`` but not to ``NotFoundSymbol`` or <doc:NotFoundArticle>.
///
/// @Metadata {
///    @DisplayName("MyClass")
/// }
@interface MyClass : NSObject

/// Some description of some function
///
/// - Parameter something: This method has no parameters.
/// - Returns: This method doesn't return anything
- (void)doSomething;

@end

NS_ASSUME_NONNULL_END

The various warnings should display for the correct line and column ranges.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] ~Updated documentation if necessary~ Not applicable

@swift-ci please test


v1.0.5-beta.5

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Only
[x] Refactor

Description, Motivation and Context

fixreact: Button Disabled State Changes properly corresponding to Variant Set and it also fixes the issue with disabled Button Group issue when it's called with variant plus typo fix #319
refactorreact: Button transitions performance improved #319
feareact: Upgrade @stitches/react to 1.2.7
refactor(react)[theme]: Missing keys were added to the ConfigType.Theme interface
fixreact: Progress default colour typo
refactorreact: Drip and useDrip exposed
fixreact: gradient ghost/bordered button with single icon #320

Screenshots - Animations

Codecov Report

Merging #374 (350c851) into main (d05538c) will decrease coverage by 0.22%.
The diff coverage is 47.61%.

@@            Coverage Diff             @@
##             main     #374      +/-   ##
==========================================
- Coverage   75.10%   74.88%   -0.23%
==========================================
  Files         162      162
  Lines        2571     2592      +21
  Branches      755      765      +10
==========================================
+ Hits         1931     1941      +10
- Misses        631      642      +11
  Partials        9        9

Impacted Files
Coverage Δ

packages/react/src/button/button-group.styles.ts
100.00% <ø> (ø)

packages/react/src/button/button-icon.tsx
100.00% <ø> (ø)

packages/react/src/button/button.styles.ts
100.00% <ø> (ø)

packages/react/src/css-baseline/css-baseline.tsx
62.50% <ø> (ø)

packages/react/src/progress/progress.styles.ts
100.00% <ø> (ø)

packages/react/src/theme/common.ts
71.23% <ø> (ø)

packages/react/src/button/utils.tsx
68.57% <45.00%> (-31.43%)
:arrow_down:

packages/react/src/button/button.tsx
96.87% <100.00%> (+0.10%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d05538c...350c851. Read the comment docs.


How do you setup Playwright tests in the build settings amplify.yml file?

Hi,
I've written a Playwright test for a website that my company has built. The Playwright framework has been built into the same project as the website itself, so the steps that I follow to test this on my machine are as follows:

Open a terminal at the root of the project
Run npm start to start the website in development mode at http://localhost:1234/
Run npx playwright test to start my Playwright tests, which each open a browser at http://localhost:1234/

The website is hosted on AWS Amplify and has a build settings amplify.yml file which now looks like this:
version: 1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    # IMPORTANT - Please verify your build output directory
    baseDirectory: /dist
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*
test:
  phases:
    preTest:
      commands:
        - npm ci
        - npm install pm2
        - npx pm2 start npm -- start
        - npm start
    test:
      commands:
        - npm i -D @playwright/test
        - npx playwright install
        - npx playwright test
    postTest:
      commands:
        - npx pm2 kill

Please can someone help me to figure out what I'm doing wrong here?
Looks to me that this is where the problem is being logged in the test phase of the preview from a pull request:
2022-06-08T15:59:10.196Z [INFO]: # Executing command: npm start
2022-06-08T15:59:10.388Z [INFO]: ><EMAIL_ADDRESS>start /codebuild/output/src282513779/src/erp-system
                                 > parcel
2022-06-08T15:59:11.098Z [WARNING]: [Error: inotify_add_watch on '/codebuild/output/src282513779/src/erp-system/node_modules/@aws-sdk/client-cognito-identity' failed: No space left on device]
2022-06-08T15:59:11.216Z [WARNING]: npm
2022-06-08T15:59:11.217Z [WARNING]: ERR! code ELIFECYCLE
                                    npm ERR! errno 1
2022-06-08T15:59:11.219Z [WARNING]: npm
2022-06-08T15:59:11.219Z [WARNING]: ERR<EMAIL_ADDRESS>start: `parcel`
                                    npm ERR! Exit status 1
                                    npm ERR!
                                    npm ERR! Failed at the<EMAIL_ADDRESS>start script.
                                    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-06-08T15:59:11.223Z [WARNING]:
2022-06-08T15:59:11.223Z [WARNING]: npm ERR!  Test execution failed, one or more tests are not passing
2022-06-08T15:59:11.238Z [ERROR]: !!! CustomerError: Base Directory not specified for artifacts, unable to create test artifact.
2022-06-08T15:59:11.238Z [INFO]: # Starting environment caching...
2022-06-08T15:59:11.238Z [INFO]: # Uploading environment cache artifact...
2022-06-08T15:59:11.290Z [INFO]: # Environment caching completed
Terminating logging...

Thanks,
Mathew

Closing because I figured out the issue; adding the echo fs.inotify.max_user_watches=65536 | tee -a /etc/sysctl.conf && sysctl -p line in the preTest commands section was the solution (see this related question) but I also had to fix other parts of the file, so here's what I ended up with as a working file:
version: 1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    # IMPORTANT - Please verify your build output directory
    baseDirectory: /dist
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*
test:
  phases:
    preTest:
      commands:
        - echo fs.inotify.max_user_watches=65536 | tee -a /etc/sysctl.conf && sysctl -p
        - npm ci
        - npm install pm2
        - npx pm2 start npm -- start
    test:
      commands:
        - npm i -D @playwright/test
        - npx playwright install
        - npx playwright test
    postTest:
      commands:
        - npx pm2 kill
  artifacts:
    baseDirectory: /test-results
    files:
      - '**/*'


Access ADLS Gen2 in different tenant with service principal

Can you please add documentation on how to mount/ access ADLS Gen2 located in a different tenant than the databricks workspace?
Please add following information:

A Service principal with the multi-tenant setting is needed
The directory-id used in the code needs to be the tenant id of the storage account

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

ID: 448f6616-8963-fc8f-022a-291d7d49a454
Version Independent ID: 658113b0-3701-f348-669c-0b1bd2958f41
Content: Access Azure Data Lake Storage Gen2 using OAuth 2.0 with an Azure service principal - Azure Databricks
Content Source: databricks/data/data-sources/azure/adls-gen2/azure-datalake-gen2-sp-access.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.

Thanks for your dedication to our documentation. Unfortunately, we have been unable to address your issue and apologize for the delayed response. We are closing this issue, but if you feel that it's still a concern, please let us know directly at<EMAIL_ADDRESS>#please-close

#please-close


Rtl support

merge with ver 9

Please resubmit this pull request against the current development branch in accordance with our contribution process.


Add geocoding api

Added Geocode.xyz to the geocoding section.  I set the auth to No, but an apiKey is required for unthrottled access.  https://geocode.xyz

Thanks @zsteeby !


Little application tweaks

Adding the application name is useful in looking at where a query comes from. Compressing the response is a good idea.

This looks appropriate and good.


Client API path issues

There's a few issues people are having due to the way client: filesystem and client: network paths are set.
Typos in references to path
This one should be easy to spot, but users get confused when they make a small change to a path and don't reflect the exact same path string it in all references to it. I've seen variations of this while giving support, although users have been understanding of the typos, it's just that there's no clearity in the error.
Reports:

https://github.com/dagger/dagger/issues/1857

Solution
This upstream issue is still marked as NeedsInvestigation, but if it gets fixed then this should be resolved:

https://github.com/cue-lang/cue/issues/629
https://github.com/dagger/dagger/issues/493

Dynamic path
This is the biggest downside and the reason I'm writing this issue.
Sometimes the path needs to be configurable, usually from an env var, but we can't have the action's CUE path set at runtime, or dependent on another action.
dagger.#Plan & {
	actions: {
		test: [string]: core.#Nop & {
			input: "world"
		}

		// action with dynamic path here
		test: (gen.output): _

		// run action which depends on a dynamic path
		run: core.#Nop & {
			input: test[gen.output].output
		}

		// #GenString just produces a string in `output`
		// from a core action
		gen: #GenString
	}
}

#GenString
#GenString: {
	_img: core.#Pull & {
		source: "alpine"
	}
	_gen: core.#Exec & {
		input: _img.output
		args: ["sh", "-c", "echo hello > /out"]
	}
	_read: core.#ReadFile & {
		input: _gen.output
		path: "/out"
	}
	output: _read.contents
}

This is what we're doing with Client API, and it doesn't work. actions.test isn't run:
➜  dagger do run
[✔] actions.gen
[✔] actions.run

Of course it works if the value is known at compile time:
-		gen: #GenString
+		gen: output: "hello"

➜  dagger do run
[✔] actions.test.hello
[✔] actions.run

As for client: network, I don't know if there's a solution on how to open a socket from something like $SSH_AUTH_SOCK, which you can't know ahead of time:
// how do we fix this?
client: {
	env: SSH_AUTH_AUTH: string
	network: "unix://\(env.SSH_AUTH_AUTH)": connect: _
}

Reports:

https://github.com/dagger/dagger/issues/1823
https://github.com/dagger/dagger/pull/2037

Solution
Is the support for dynamic tasks broken/unsupported yet? Would this issue be fixed by supporting it? Is it the same underlying behavior as in conditionally creating an action based on the output of another?
Proposal
While we wait for the above solutions, there's a backwards compatible way to tweak the API:
client: network: [address=string]: {
	address: string | *address  // default, allows overrides
	listen: dagger.#Socket
}

This allows you to:

client: {
	env: SSH_AUTH_AUTH: string
	network: sshAuth: {
		address: "unix://\(env.SSH_AUTH_AUTH)"
		connect: _
	}
}
actions: {
	test: core.#GitPull & {
		...
		auth: sshAgent: client.network.sshAuth.connect
	}
}

Same with client: filesystem.
Pros:

Still compatible with current API if you have a fixed path and want to use that;
Frees you from having to maintain the path in all references, or to keep references shorter for long paths;
Solves current issues by having the option of having a custom name instead of the fs path in the action CUE path;

Cons:

Commit to new design even if issues are resolved (not an issue for me);
Needs new solution for #1581 (which was the motivator for the current design in the first place), but only on filesystem: write... network should be ok;

/cc @shykes @aluzzardi @gerhard

There's two more cases the proposal would unlock. They're two sides of the same coin, but both have been requested.
Reading multiple times from the same dir
client: filesystem: {
	goFiles: read: {
		path: "."
		contents: dagger.#FS
		include: ["**/*.go"]
	}
	cueFiles: read: {
		path: "."
		contents: dagger.#FS
		include: ["**/*.cue"]
	}
}

Writing multiple times to the same dir
client: filesystem: {
	lintedGo: write: {
		path: "."
		contents: actions.lint.go.output
	}
	lintedCue: write: {
		path: "."
		contents: actions.lint.cue.output
	}
}

The lock solution is viable.
In #2385 I found a limitation in implementing dynamic paths when reading directories, i.e., client: filesystem: ...: read: contents: dagger.#FS: We need to know the paths before running the plan to setup the BuildKit client.
As of this moment there's no clear path forward.


On setting useCustomAndroidUI in Android, popup button color seems to be broken

I'm using v7.0.2 with Nativescript 6
Please check image

@EddyVerbruggen Any idea on this issue, please

Perhaps there's a generic CSS class in your app that applies that color to the button? Or maybe it's one of these.

@EddyVerbruggen Yeah we checked them and same colors there in our app, can't find any style overriding them

Did you check the com.github.JesusM:FingerprintManager package (Google it)? We're using v2.0.2 in this plugin. Maybe their project repo has some docs/related issues.

@EddyVerbruggen OK sure will check there, Thanks!

@EddyVerbruggen I checked with that package and seems no issue there as they haven't changed or upgraded it recently. Don't know whether it causes with Nativscript 6 as there it upgrades to Androidx, anyone experienced the same?

I thought maybe in that package there's a way to influence the UI by (perhaps) some XML config files.


Leaving capsule.version unspecified currently resolves to an unstable snapshot

I came across the following issue when trying to build a new capsule project:
https://github.com/puniverse/capsule/issues/55
This came up because my project (using capsule-maven-plugin v0.10.0) was resolving the latest capsule version (which happened to be 1.0-rc1-SNAPSHOT and contained the bug above).
Ideally, capsule-maven-plugin would ignore '*-SNAPSHOT' capsule versions when resolving the 'latest' capsule version.
I've been able to work around this issue by explicitly setting capsule.version:
<capsule.version>0.10.0</capsule.version>

Ah yeah you're right, thanks for reporting. Will issue a fix.

This is actually a bug in the way VersionRangeRequest (incorrectly) works - see here.
In any case, I've managed to write additional code to skip the SNAPSHOT version and find the latest non-snapshot version. Resolved in 0.10.3


ERRO[6246] containerd: notify OOM events

Environement:
root@dind2:/# docker -v
Docker version 1.11.2, build b9f10c9
Docker host
Distributor ID:	Debian
Description:	Debian GNU/Linux 8.5 (jessie)
Release:	8.5
Codename:	jessie
Linux gns3-iouvm 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux

Using "--privileged" as instructed:
docker run --privileged -t -i dind
When I start a container inside dind, I have the following message:

fd227438d2a0d6689fcf80b4302f8b05ecd2199ad82f946b41680090d8597547
ERRO[6246] containerd: notify OOM events                 error=open memory.oom_control: no such file or directory

Doesn't seem to have incidence, container is running and reachable from outside
Looks like priorly solved with previous version https://github.com/docker/containerd/issues/188 but stll experiencing this with 1.11.2, build b9f10c9

I think this can safely be ignored :-) But thanks for reporting!


publish receptor-collection to ansible-galaxy as a certified collection

Waiting on Pr #11 to merge, after that, we should be in good shape for release to both upstream and downstream

Validated from QE side


Icons are enormous with Obsidian 0.14.4

I think Obsidian is breaking Icons Shortcodes 😓 ...
Just updated to the latest insider release (Obsidian 0.14.4) and now icons in a note are looking like this 😔 ...
(whatever view I'm in)

While waiting for this to be fixed at the source 😊 and because I really couldn't use Obsidian with icons as big as the readable length of my notes, I found a temporary solution by modifying the style.css from the plugin directly (I tried to use a snippet as suggested in the README instead but couldn't make it work 🤷♀ )
So the bug seems to lie somewhere in this part of the style.css (as the --editor-font has been replaced by --font-text) :
[...]

.markdown-preview-view .isc-icon>img,
.markdown-preview-view .isc-icon>svg,
.markdown-source-view .isc-icon>img,
.markdown-source-view .isc-icon>svg {
  height: var(--editor-font-size);
  width: var(--editor-font-size)
}

[...]

By just changing the var(--editor-font-size) by var(--font-text-size) for the height and width I was able to get back workable sized icons 😊 ...

confirmed! before the patch is available, you can use css snippet as a temp fix, no need to modifying the style.css

you can use css snippet as a temp fix, no need to modifying the style.css

Yeah, I know and I tried multiple times before modifying the style.css but absolutely nothing worked 🤔 ...
I'll admit, it's been a very very very long time since I played around with css so maybe I forgot to add something 🤷♀ ...
Anyway, Thank you very much for the quick fix 🥳 🙌  !!!

Yeah, I know and I tried multiple times before modifying the style.css but absolutely nothing worked 🤔 ...

Maybe it's because you've been using the selector with less specificity than plugin's css. In the css snippet, you should be able to override specificity with !important flag: https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity

Darn 😅 🤦♀ ... I completely forgot about !important!

Thank you again 😁 !


go-swagger generate client generates wrong default formData parameter type for array of strings

Problem statement
go-swagger generate client generates wrong value type in default parameters for a
swagger formData parameter of type []string
Swagger specification
https://raw.githubusercontent.com/CurrencyCloud/currencycloud-swagger/master/src/reference.yaml
This is the parameter that is the problem:
        - name: payment_types[]
          in: formData
          required: false
          type: array
          items:
            type: string
            enum:
              - priority
              - regular
          default:
            - regular
          description: >-
            Currencycloud supports two types of payment: "priority", made
            using the SWIFT network; and "regular", made using the local bank
            network.

Steps to reproduce
mkdir -p $GOPATH/src/github.com/nkobber/go-swagger-test/currencycloud
cd $GOPATH/src/github.com/nkobber/go-swagger-test
curl https://raw.githubusercontent.com/CurrencyCloud/currencycloud-swagger/master/src/reference.yaml --output swagger.yaml
swagger generate client --target ./currencycloud --name currencycloud
go build ./...

Produces
# go build ./...
# github.com/nkobber/go-swagger-test/currencycloud/client/beneficiaries
currencycloud/client/beneficiaries/create_beneficiary_parameters.go:31:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/create_beneficiary_parameters.go:46:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/create_beneficiary_parameters.go:61:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/create_beneficiary_parameters.go:76:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/update_beneficiary_parameters.go:31:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/update_beneficiary_parameters.go:46:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/update_beneficiary_parameters.go:61:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/update_beneficiary_parameters.go:76:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/validate_beneficiary_parameters.go:29:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/validate_beneficiary_parameters.go:42:3: cannot use paymentTypesDefault (type []interface {}) as type []string in field value
currencycloud/client/beneficiaries/validate_beneficiary_parameters.go:42:3: too many errors

create_beneficiary_parameters.go:
func NewCreateBeneficiaryParams() *CreateBeneficiaryParams {
	var (
		defaultBeneficiaryDefault = bool(false)
		paymentTypesDefault       = []interface{}{"regular"}
	)
	return &CreateBeneficiaryParams{
		DefaultBeneficiary: &defaultBeneficiaryDefault,
		PaymentTypes:       paymentTypesDefault,

		timeout: cr.DefaultTimeout,
	}
}

should instead be
func NewCreateBeneficiaryParams() *CreateBeneficiaryParams {
	var (
		defaultBeneficiaryDefault = bool(false)
		paymentTypesDefault       = []string{"regular"}
	)
	return &CreateBeneficiaryParams{
		DefaultBeneficiary: &defaultBeneficiaryDefault,
		PaymentTypes:       paymentTypesDefault,

		timeout: cr.DefaultTimeout,
	}
}

Let me know if you need any more info
Environment
swagger version: v0.17.0, 0.16.0, 0.13.0
Go version: 1.11
OS: macOS Mojave 10.14

Yes, this is a bug: default initialization is a bit naive on the client.
This is set here: https://github.com/go-swagger/go-swagger/blob/be966a22e91309b7ed8d57d20e737ab5b3861cbd/generator/templates/client/parameter.gotmpl#L35
and other factory methods below.
For a comparison, this has been solved on the server side with a more complex template, but not ported to the client yet. See how: https://github.com/go-swagger/go-swagger/blob/be966a22e91309b7ed8d57d20e737ab5b3861cbd/generator/templates/server/parameter.gotmpl#L308


Jump using ctrl-o not correct after navigating with lsp picker

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
mini.pick, mini.extra
Description
https://github.com/echasnovski/mini.nvim/assets/58370433/c5362c94-b91c-44f9-822b-f0b06b999696
When using lsp definition, I often jump back with ctrl-o. The jump is not correct.
I also notice this behavior when using lsp references
Neovim version
0.10
Steps to reproduce

--[[
Use:
  mkdir ~/.config/repro
  cd ~/.config/repro

  touch init.lua
  add the contents of this file to init.lua
  NVIM_APPNAME=repro nvim init.lua

Remove:
  rm -rf ~/.local/share/repro ~/.local/state/repro ~/.local/cache/repro
  rm -rf ~/.config/repro
--]]

local verify_with_fzf_lua = false -- set to true to use fzf-lua

local function clone(path_to_site)
  local mini_path = path_to_site .. "pack/deps/start/mini.nvim"
  if not vim.loop.fs_stat(mini_path) then
    vim.cmd('echo "Installing `mini.nvim`" | redraw')
    local clone_cmd =
      { "git", "clone", "--filter=blob:none", "https://github.com/echasnovski/mini.nvim", mini_path }
    vim.fn.system(clone_cmd)
    vim.cmd("packadd mini.nvim | helptags ALL")
    vim.cmd('echo "Installed `mini.nvim`" | redraw')
  end
end

local path_to_site = vim.fn.stdpath("data") .. "/site/"
clone(path_to_site)
local MiniDeps = require("mini.deps")
MiniDeps.setup({ path = { package = path_to_site } })
local add, now = MiniDeps.add, MiniDeps.now

vim.g.mapleader = " "
vim.opt.number = true

local function lua_ls_handler()
  require("lspconfig").lua_ls.setup({
    settings = {
      Lua = {
        runtime = { version = "LuaJIT" },
        workspace = {
          checkThirdParty = false,
          library = {
            vim.env.VIMRUNTIME,
            "${3rd}/luv/library",
          },
        },
      },
    },
  })
end

now(function()
  vim.cmd("colorscheme randomhue")

  add("nvim-treesitter/nvim-treesitter")
  ---@diagnostic disable-next-line: missing-fields
  require("nvim-treesitter.configs").setup({
    ensure_installed = { "lua" },
  })

  add("williamboman/mason.nvim")
  require("mason-registry"):on("package:install:success", function()
    vim.defer_fn(function()
      vim.cmd("LspStart")
    end, 100)
  end)
  require("mason").setup()

  add("williamboman/mason-lspconfig.nvim")
  add("neovim/nvim-lspconfig")
  require("mason-lspconfig").setup({
    ensure_installed = { "lua_ls" },
    handlers = {
      lua_ls = lua_ls_handler,
    },
  })

  local cmd_definition = "<cmd>Pick lsp scope='definition'<cr>"
  local cmd_references = "<cmd>Pick lsp scope='references'<cr>"
  if verify_with_fzf_lua then
    cmd_definition = "<cmd>FzfLua lsp_definitions<cr>"
    cmd_references = "<cmd>FzfLua lsp_references<cr>"
  end
  vim.api.nvim_create_autocmd("LspAttach", {
    callback = function(args)
      vim.keymap.set("n", "gd", cmd_definition, { buffer = args.buf, silent = true, desc = "Goto definition" })
      vim.keymap.set("n", "gr", cmd_references, { buffer = args.buf, silent = true, desc = "References" })
    end,
  })

  add("ibhagwan/fzf-lua") -- use by setting verify_with_fzf_lua to true
  require("fzf-lua").setup()
  require("mini.extra").setup()
  require("mini.pick").setup()
end)

Steps using the repro above:

Open neovim: repro init.lua
:30, selecting the line with "clone"
press gd and enter
line 17 is selected
press ctrl-o
cursor jumps to line 1 instead of line 30

Close neovim and change the following:
verify_with_fzf_lua = true

Repeat steps 1 till 6. The cursor correctly jumps to line 30.
Expected behavior
When I jump back after using Pick lsp scope="definition", the jump is correct.
Actual behavior
Jump is incorrect.

Thanks for the suggestion!
I can reproduce that indeed MiniExtra.pickers.lsp does not add previous position to jumplist. After quick look, I didn't find a quick fix, though. I'll take a closer look.

@echasnovski,
I noticed that you changed the type of the issue from "bug" into "feature-request". Was my assumption incorrect?

I think it is reasonable to consider a bug as a deviation from documented and/or assumed during implementation behavior.
In this particular case adding current position to jumplist is neither.

Should this also work with ctrl-t (tagstack) ? I'm getting E73: Tag stack empty

Should this also work with ctrl-t (tagstack) ? I'm getting E73: Tag stack empty

I don't think it should work because jumping with 'lsp' picker doesn't contribute to tag stack (hence the empty tag stack error).

Is this being looked at or is it intended behaviour? It's the one thing keeping me from using mini.pick rather than telescope.nvim

Is this being looked at or is it intended behaviour? It's the one thing keeping me from using mini.pick rather than telescope.nvim

If it is open, then it is a part of plan to have this resolved. Otherwise it would have been closed.

Looking at the way telescope.nvim handles lsp calls, they seem to add the location using the following:
vim.cmd "normal! m'"

Specifically for pickers from LSP type sources. Perhaps this would be useful.


Api 1.6.0 - rhtml

Add support for Interactive R Powered Custom Visuals

new template (rthml)
support 'source' command in R scripts

@adlerav,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Very slow with arrays

This project is incredible. It really helps me with my PhD dissertation. Is there any more intent to work on it? There seems to be a data transmission between puredata and javascript through stderr text, which seems to be very slow. Is there a way to pass the data directly into PD so that it is faster? I might be misinterpreting the documentation.
Thanks,
Nakul

Hi, sorry I haven't looked into it for a long time. I believe Pd evolved and it could be possible with only 1 port.
Do you use a large array, could you paste a minimal code example?

If I remember correctly it was a lot faster with 'nogui': true :)


Well… this aged poorly

I would private this repo if I were you… and maybe check out the MrBeast allegations

I don't think it's necessary to erase history just because of the MrBeast allegations, much less telling other people to do so.


Brightness goes to full when device is unplugged

First of all, thank you so much for spending time developing this app, I've been using it for a few months now and have been thoroughly enjoying it.
A few bugs that I've found which I believe are all closely related:

Sometimes when the flashlight is on while the device is plugged in, and the device is then unplugged, the  brightness gets set to max.

The brightness is also sometimes set to max when turning brightness up to a non-zero value from zero. This occurs only for the first click, and subsequent clicks appear to work properly.

The intital light level setting is occasionally ignored when using the quick tile (the brightness reports as the set level, but the light is at 100% until changed)

I feel that it is likely that these behaviors are all caused by the same bug. These bugs seem to be closely related to #15
These issues are hard to reproduce, but seem most likely to occur when the app hasn't been used in a few hours. Force stopping the app and then using it from the quick tile or app does not trigger these issues.
App version: 2.0.0 (from F-Droid)
Device: Google Pixel 6 (oriole)
OS: GrapheneOS TQ3A.230705.001.2023072600 (Android 13)

Thanks for your nice words and for the report.
I will take a look at the issues mentioned and if I can reproduce them.

@shamefulIguana8 Does the issue still appear in Version 2.2.0?

I personally wonder of this is a graphene issue? I've been using the app for quite sometime on a Pixel and haven't encountered this.

Yeah, same for me on my P7 Pro

The issue seems to be resolved on both pixel 6 & 7 running grapheneos. Thank you!
PS volume button toggle feature is great.


Improve warning when native libraries extracted to volume with noexec set

Expected behavior
A Docker-version of our application suddenly failed to work when the --tmpfs flag was added to the Docker run command.  Digging into the cause resulted in a surprise that this causes Docker to mount the temp directory with noexec; the Netty stack trace (below) does clearly report the failed to map segment from shared object error, but this is a bit ambiguous to anyone who did not expect Docker to do this.  Given how popular containers in general, and Docker in particular, has gotten, it seems appropriate to try to log a better message.
Actual behavior
Only warning is:
java.lang.UnsatisfiedLinkError: /tmp/libnetty-transport-native-epoll5589732826809244917.so: /tmp/libnetty-transport-native-epoll5589732826809244917.so: failed to map segment from shared object: Operation not permitted
	at java.lang.ClassLoader$NativeLibrary.load(Native Method) ~[?:1.8.0_121]
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941) ~[?:1.8.0_121]
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1824) ~[?:1.8.0_121]
	at java.lang.Runtime.load0(Runtime.java:809) ~[?:1.8.0_121]
	at java.lang.System.load(System.java:1086) ~[?:1.8.0_121]
	at io.netty.util.internal.NativeLibraryUtil.loadLibrary(NativeLibraryUtil.java:36) ~[netty-common-4.1.9.Final.jar!/:4.1.9.Final]
	at io.netty.util.internal.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:259) ~[netty-common-4.1.9.Final.jar!/:4.1.9.Final]
	at io.netty.util.internal.NativeLibraryLoader.load(NativeLibraryLoader.java:226) ~[netty-common-4.1.9.Final.jar!/:4.1.9.Final]
	at io.netty.channel.epoll.Native.loadNativeLibrary(Native.java:269) ~[netty-transport-native-epoll-4.1.9.Final-linux-x86_64.jar!/:4.1.9.Final]
	at io.netty.channel.epoll.Native.<clinit>(Native.java:64) ~[netty-transport-native-epoll-4.1.9.Final-linux-x86_64.jar!/:4.1.9.Final]
	at io.netty.channel.epoll.Epoll.<clinit>(Epoll.java:33) ~[netty-transport-native-epoll-4.1.9.Final-linux-x86_64.jar!/:4.1.9.Final]
        at ... (truncated for brevity)

Steps to reproduce
Attempt to use epoll or OpenSSL (any version) with the temp directory set to a volume with noexec set.
Netty version
4.1.9
JVM version (e.g. java -version)
8u121 (should not matter)
OS version (e.g. uname -a)
Any flavor of unix supporting volumes with noexec.
Proposed improvement
Add an explicit warning and suggested use of -Dio.netty.native.workdir=... when the extracted native library is readable and fails to load with failed to map segment from shared object.  This would also address netty/netty-tcnative#264, where this issues was first discovered (when the bundled boringssl library failed to load; error is the same for epoll above).
I'm waiting on my company to sign the contributor agreement before I submit a PR, but the following trivial snippet, added as a catch block in io.netty.util.internal.NativeLibraryLoader#load, fixes it:
        } catch (UnsatisfiedLinkError e) {
            // Linux will clearly state that the operation is not permitted when
            // the temp directory is mounted with the "noexec" option (common in
            // secure environments and the default for Docker's --tmpfs option).
            try {
                if (!isWindows() && tmpFile.isFile() && tmpFile.canRead() &&
                    e.getMessage().matches(".*failed to map segment from shared object.*")) {
                    logger.info("{} exists and is readable but cannot be loaded; volume mounted with noexec? " +
                                " Use -Dio.netty.native.workdir=[path] to set native working directory separately.",
                                tmpFile.getPath());

                }
            } catch (Throwable t) {
                // Ignore
            }
            // Re-throw to fail the load
            throw e;

I'm all for making exception messages more informative, however my preference is to avoid doing inspection of exception messages. Inspecting the string portion of exceptions is fragile and subject to fail.

Well, I agree with that.  Unfortunately, the only non-message-parsing (not calling these better) solutions that I know of are:

Invoking "mount" and parsing the results
Attempting to read the mount information off the filesystem
Lots of reflection to get to and invoke sun.fs.nio.UnixMountEntry#getOption(String)

I have a patch doing number 3 in the list above that I'll submit as a PR in a few minutes.  Arguably, the reflection should be done inio.netty.util.internal.PlatformDependent instead of in a static inner class (to lazy initialize) of io.netty.util.internal.NativeLibraryLoader.

@mkw I would prefer to not use reflection if possible as this will fail on java9 :(

Doh!  I literally just pushed a reflective version with a comment indicating that --add-opens java.base/sun.nio.fs=... is required for Java 9.  Would you prefer message parsing?  That's certainly simpler, but does depend on the message from the Kernel not changing (and I can't easily test it on anything but a handful of linux flavors).

@mkw maybe its ok if we just try to do it and "silently" fail if we can not do the reflection hack. Kind of best-effort.

Definitely a best-effort warning.  I'm locally testing suppressing the stack trace from the java.lang.reflect.InaccessibleObjectException exception and instead suggesting the --add-opens java.base/sun.nio.fs=... flag if initialization fails.  This will only happen 1 on startup, and it's logged at debug.  Will push once I confirm that it works.

We did this but forgot to close the issue...


Sort out transition between DOIs and open access

We have a pretty awkward transition between the DOI lesson and the open access information.  Might naturally sort itself out later on, but right now somewhat being deliberately ignored.

Between #25 and #26 I have taken out the Open Access section. I think advocating Open Access publishing (which is an ongoing debate with many arguments on both sides) goes beyond the scope of this lesson and of the curriculum.
OK to close?

I think it's ok to mention open access as A Thing, but good to keep out of any advocacy.  Worth mentioning open access because some federal mandates are requiring some research products to be made open access, but you can still keep out of the philosophical promotion even when having that conversation.
But okay to leave out for now, if easier.

I wasn't saying that Open Access isn't worth mentioning or even advocating for. But it's not clear to me how to fit it in here persuasively under the scope of Reproducible Research using Jupyter Notebooks. You can certainly do reproducible research with Jupyter Notebooks perfectly well without ever publishing in an Open Access journal. I.e., Open Access publishing (in contrast to open access to source code, data, and other ingredient research products) is a subject separate from that of Reproducible Research, and I think trying to tie them together helps neither.

I think that we should table this discussion and see what the technology looks like sometime in the future. I agree w/ @hlapp that right now there is no clear link between notebooks + OA publishing that deserves its own special treatment.
The reproducible work materials are already somewhat duplicated between the jupyter + R courses, so unless this is explicitly OK and/or preferred, it'd be better not to increase the duplication.


[#548] Update bots to support SingleTenant & MSI authentications

Addresses #3526
Proposed Changes
This PR adds support for MSI and SingleTenant functionalities to the Host and Skill under echo-bot by updating the .env file to include the MicrosoftAppType and MicrosoftAppTenantId fields and the registration of valid token issuers when the MicrosoftAppTenantId is provided.
Detailed Changes

Added the MicrosoftAppType and MicrosoftAppTenantId fields to the .env file and in the ConfigurationServiceClientCredentialFactory instance.
Added valid token issuers to the AuthenticationConfiguration instance when the MicrosoftAppTenantId is provided.

Replaced by PR136


Bug 191 Allow Dots in Instance Names for Subscription

Issue: https://github.com/jmdns/jmdns/issues/191
This is very related to https://github.com/jmdns/jmdns/issues/180 and https://github.com/jmdns/jmdns/pull/179.
The above changes by @mattiasbe fix the issue for publishing services However you cannot subscribe to such a service because the ServiceInfoImpl.decodeQualifiedNameMapForType() method can't handle the dot in instance names.
Same reason here, I am quoting @mattiasbe:

The reason for this requested support is that the European ITxPT public transport standard is using an additional extra field in the instance containing the separator dot.

For example subscribing to this won't work:

instancename._apc._itxpt_http._tcp.local. :x: (instance should be instancename._apc)

However without the dot, it does:

instancename_apc._itxpt_http._tcp.local. :heavy_check_mark: (instance should be instancename_apc)

So, in this pull request the decoding implementation is changed to work with the dot. I have removed the decode stuff from ServiceInfoImpl and put it into ServiceTypeDecoder. Also decode-related tests are moved from ServiceInfoTest to ServiceTypeDecoderTest. Plus a lot of tests are added, too.

Side note: I think also the decoding of subtypes is improved with this pull request. For example, the following type string was not decoded properly before:

subtype._sub._apple-mobdev2._tcp.local. :x:

Apparently the previous implementation requires a leading underscore for subtypes. However RFC 6763, part "7.1.  Selective Instance Enumeration (Subtypes)" mentions:

Subtype strings are not required to begin with an underscore, though
they often do.  As with the TXT record key/value pairs, the list of
possible subtypes, if any (including whether some or all begin with
an underscore) are defined and specified separately for each basic
service type.

Please, let me know what you think. Cheers! :)

I also created an issue according to the contribution guidelines: https://github.com/jmdns/jmdns/issues/191

@kaikreuzer please, any feedback here?
Can I do something to let travis-ci pass the build? I don't think its a problem related to those changes, is it?

Hey guys, sorry for having neglected that project over the past year...
Will try to catch up now. Just changed the travis config to use Java 8 instead of Java 7, which should make it work again.
Let me quickly close and reopen this PR to see, if it works.

@kaikreuzer glad to hear. Thanks for merging! 👍


How do I share environments across projects?

How do I share environments across projects?
We have organized our software in many different projects. However, we deploy most of our software to the same physical machines: Development, Staging, and Production.
From the looks of it, do I need to run the PowerShell registration script for each project environment? Why can't I share environments across projects?
Thanks for clarifying!

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

ID: 77d95db6-9983-7346-d0eb-4b7443e4e252
Version Independent ID: 0a22cccc-318d-592f-d1ab-09ec01d88087
Content: Environment - Azure Pipelines
Content Source: docs/pipelines/process/environments.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@stevenvolckaert Thank you for the question.
Currently this can only be handled with custom scripting using PowerShell, etc.
If you'd like to see this as an added feature, please refer this post for status updates from the product team.

@msebolt Thank you for your response 🙏
I've managed to 'share' environments by registering multiple Azure Pipeline Agents, indeed via modifying the PowerShell script. At the moment, each server (e.g. 'Development', 'Staging', 'Production'), is now running one agent per project.
Is this the workaround that you are referring to?
If you mean something else, I'm curious what it could be! 🤓

@stevenvolckaert You're welcome!
Yes, I was mainly referring to sharing variables (a work still in progress).  Sharing environments would likely be considered once this is complete.

Closing this issue now, thanks again for the feedback and please contact us again for further discussion or changes needed to the documentation.

Thanks again @msebolt!!

Could you please elaborate the changes you maid in the PowerShell script.
I am facing the issue while installing the Azure pipeline agent on one VM where Azure self hosted agent already installed.
Below is the output of the error....

Connect:

Connecting to server ...

Register Agent:

Scanning for tool capabilities.
Connecting to the server.
Enter Environment Virtual Machine resource tags? (Y/N) (press enter for N) >
Successfully added the agent
Testing agent connection.
2020-08-07 11:43:16Z: Settings Saved.
Enter User account to use for the service (press enter for NT AUTHORITY\SYSTEM) >
The service already exists: vstsagent.company..WEBSERVER01, it will be replaced
Error reported in diagnostic logs. Please examine the log for more details.
- C:\azagent\A4_diag\Agent_20200807-114307-utc.log
Could not delete service 'vstsagent.company..WEBSERVER01'

@Satendrakumar-hatteland See my adapted PowerShell registration script Register-AzurePipelinesAgent.ps1. Hope it helps!

@stevenvolckaert This fixed the issue for me, thanks! I was getting the same "could not delete service" error that @Satendrakumar-hatteland was getting.


STEEMJS CDN is down

Expected behavior
CDN should return minified js file.
Actual behavior
Site is down.
How to reproduce
Go to : https://cdn.steemjs.com/lib/latest/steem.min.js.

Hi @Rishi556 - thanks for reporting this. The Steemit team actually does not host steemjs.com, so failures there are out of our control. I believe this has been the Steemconnect team in the past and we've reached out to them about it.
As a long term solution, we've updated the README to suggest using this URL instead which will update with each release:
https://cdn.jsdelivr.net/npm/steem/dist/steem.min.js
You should use this new URL instead in your browser based projects.


Question: Support for endless rolls with cutters and different page sizes

Hello,
I am trying to print on a Brother QL-1110NWB. This works well with the IPP Everywhere driver after automatically discovering the printer and adding it to my configuration.
In the printer I have a roll of label paper and the printer has a cutter. Printing works fine and the printer can automatically cut off the tape after each page.
I now have a system that generates different labels of different sizes. Some are being used to label products and boxes - others are for DHL shipment labels and so on. I would like to know if CUPS somehow supports that no fixed page size is configured and is able to print those labels in the form factor they are being received.
The source format is PDF and usually comes readily scaled for the printer and if I print it using an iPhone the printer is doing the "right thing". Using CUPS, each page will be scaled to what I have selected in the printers "default options" and printed - which is not what I want. I am sending the PDF document to cups using the dbus API.
I have now been reading lots of CUPS code, but could not quite make sense of it with sufficient confidence, but I believe that it should generally be possible to just give the width of the roll and CUPS automatically scales (if necessary) the page to the maximum width automatically determining the length.
When asked with ipptool, the printer says this:
media-ready (keyword) = roll_current_102x0mm

So I tried to configure CUPS with something like *DefaultPageSize: Custom.102x0mm which is not giving me what I want. I would have expected CUPS to ask the printer what paper is currently installed (as it is reporting that) and maybe automatically configure itself depending on that information? That does not seem to happen.
Hence I am now trying to reach out to you to help me figure out if this is at all possible what I want to achieve, whether it should work but doesn't or if it is me having misconfigured something. Any pointers are greatly appreciated.
If I could send with each print job what my page size for that label is would also work for me. One PDF has two pages that have different dimensions, but if that is making the case too difficult, I could potentially split that into two print jobs.
I am using CUPS 2.3.3op2 on Debian Bullseye. "get-printer-attributes" and my PPD file are attached. Please let me know if you need any further information.
ipptool-get-printer-attributes.txt
Brother_QL-1110NWB.txt

Sorry, but CUPS and its filters do not support auto-sizing like this - they depend on the submitting application to specify the correct size.
Conceptually you could do a simple wrapper around the "lp" command to examine the file and calculate the necessary dimensions...

Thank you Michael for your reply.

Sorry, but CUPS and its filters do not support auto-sizing like this - they depend on the submitting application to specify the correct size.

My PDF documents are in the correct size that the printer needs. No problem to do anything in my application if I actually was needed to. So if possible, it would be fine with me if CUPS could just convert the PDF with its dimensions into the raster format and send it to the printer. I was reading through the code at some point thinking that it should generally be possible, but there is a lot of code to read, so surely I misinterpreted some parts.

Conceptually you could do a simple wrapper around the "lp" command to examine the file and calculate the necessary dimensions...

Is there a way that I can pass individual settings for a print job this way? I tried that, but felt like they did not change any behaviour. Neither by printing through lp, nor the dbus interface.


Fix removal logic in widgets

We were not removing children if they were more recently synced than we
were. This makes no sense. We should remove all children unless they
were synced this very generation already (in which case they'll be
somewhere else in the tree by now).
Fixes #1209.

LGTM


Update github actions due to deprecation

Artifact actions v3 will be closing down by January 30, 2025 and github is going to begin temporarily failing jobs that don't update before this deadline. The PR fixes the versions used.

upload/download actions need workflow updates due to breaking changes, see https://github.com/ethereum/beacon-APIs/pull/487


Update GameEngines

Add the C++ engine JNGL

Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/main/CONTRIBUTING.md.
[ ] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
[x] Content (and my changes are in index.md)

The cross platform C++ engine JNGL was missing.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

With JNGL is it easy to develop games on Windows/Linux/MacOS. The games than can deployed to Windows, Linux, MacOS, Android, iOS/TV, Webassembly, Xbox, Switch.

Something that does not neatly fit into the binary options above

[ ] My suggested edits are not about an existing topic or collection, or at least not a single one
[ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
[x] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Add the C++ engine JNGL

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Hi @pinguin999, thanks for the contribution ❤. Unfortunately, as per our contribution guidelines, we don't allow self promotion if you are a maintainer of the project:

Maintainers of a project cannot add a topic or collection for their own project. If a topic is popular enough to warrant inclusion, someone else will add or improve it.

We do this so that we can maintain a high level of independence in this project, and projects will be curated if there is enough support/activity in the community. Thank you!


syntax highlighting system

a simple syntax highlighting system proposal. languages are configured as such:
[file_associations]
c_language = [".c", ".h", ".cc"]

[syntax.c_language]
[syntax.c_language.type]
colouring = 0xff0000
match = [
	"int", "char", "bool", "float", "double", "void",
	"uint8_t", "uint16_t", "uint32_t", "uint64_t",
	"int8_t", "int16_t", "int32_t", "int64_t",
]

[syntax.c_language.keyword]
colouring = 0xff00ff
match = [
	"for", "break", "if", "else", "continue", "return",
	"goto", "static", "extern", "const", "typedef",
]

the gist is. we register the file association i.e. c_language is associated with the given file extensions.
then we define the syntax highlighting for the language as syntax.language_name. a syntax specifies types of values as well as their colouring, and what they can match.
obviously this is not very flexible but for basic syntax highlighting its quite good and easy to customize. in the future perhaps you can specify regex or something to match identifiers in different ways e.g. what regex pattern is a number f([0-9]+) would match f323 or something like that

implemented as well as some simple regex matching. the current implementation is pretty slow/buggy and can be optimized but its a start.


Is the project abandoned?

The last significant code change seems to be from 2 years ago. Is this project abandoned upstream? If so, would a fork be welcomed? Thanks!

Sedlex was the first ppx rewriter; it was actually done as a POC of this concept, and I haven't had a chance to use it for any project, so my interest in maintaining it is indeed rather small.  Would you like to become a/the maintainer?

(Note: @Drup already has commit rights on this repository.)

Indeed, but I don't have time to dedicate to it (and I don't really know the whole code base anyway). I never considered myself maintainer.

Thanks for responding. I'm interested in the project at the moment as I think it is the only available lexer with unicode support in OCaml as of now. I've been looking at switching our application to it. I don't think that I want to commit to maintaining long-term but I think that there's always room for some lower level maintenance that doesn't require a deep understanding of the code or long-term commitment to it.

Ok, I've invited you as a collaborator on the project.

Awesome, thank you!
2017-03-23 11:40 GMT-05:00 Alain Frisch<EMAIL_ADDRESS>
Ok, I've invited you as a collaborator on the project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alainfrisch/sedlex/issues/44#issuecomment-288781552,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1KlJjtKWq-FDcNP_FOMt8BtQNKU-k8ks5roqB8gaJpZM4MlvY8
.


Is this still running and supported

The idea between the project is great.
But I was worried since the beginning as there are no updates since 2 years. Is the project still supported?
I try different example provided some are running some are not. For example the scaryBox is neither working on my Samsung orsay 2012(ue40eh5300) and on Emulators. On the device it is just complaining at installation time:  Failed to install. For more information, visit http://www.samsungdforum.com/Support/TVAppsSecurity.
On emulators just a black screen with no errors on the console.
It is just working on the browser :-(
Anybody had a chance to compile it correctly and could share it in order I could verify which are the difference between the result of my compilation and yours.
Thanks
François

Hi
First, thanks for your interesting on our TOAST.
I think It seems not to be related Toast issue, In my opinion It occurs a securityError when signature file is not exist.
You might get an answer if you upload Q&A posting.
https://developer.samsung.com/home.do
And below was a similar issue what you are in troubled.
https://github.com/Samsung/cordova-plugin-toast/issues/21
TOAST is still in operation,
and recently compatibility is confirmed on 2018 TV, so many applications are in use.
So you don't need to be worry about that.
Thanks for your interesting again.


[FLINK-8006] [Startup Shell Scripts] Enclosing $pid in quotes

What is the purpose of the change
When executing ./bin/start-local.sh The following errors appears:
flink-1.3.2/bin/flink-daemon.sh: line 79: $pid: ambiguous redirect
This is because $pid contains spaces, so to fix it I've enclose I replaced all $pid by "$pid"
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

No
Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Do we also need to quote within sub-expressions? Have you looked at the stop script?

@greghogan Didn't realized!, its failing too. I am going to fix it.

@greghogan Done, sorry for ignoring the stop script.

@elbaulp au contraire, thank you for fixing this bug. Do we need quotes for the following?
line 69: pid=$FLINK_PID_DIR/flink-$FLINK_IDENT_STRING-$DAEMON.pid
line 181: done < ${pid}.tmp
line 182: rm ${pid}.tmp

@greghogan Oh, of course, didn''t saw it, how many $pids! Done.

+1

LGTM
+1 to merge

Hi, Do I need to do something more in order to this PR be merged?

merging.


bug blink display android 11 on  3.1.. and last 3.2 firmware

last firmware bug the display blink on my android 11 , but its ok with firmware 3.0.4.
can u help for this please : )
thanks

Try the latest version https://github.com/v3rm0n/m8c-android/releases/tag/v1.0.17


document all transformers

(almost?) everything here: https://github.com/6to5/6to5/blob/master/lib/6to5/transformation/transformers/index.js
should be listed here: http://6to5.org/docs/usage/transformers/
for example, there is no documentation on the minification transformers. even the fact that they exist would be helpful. this could perhaps be auto generated.

@aeosynth If a transformer isn't documented then it's still in development.


Add json format output to the depend-info command

Fixes https://github.com/microsoft/vcpkg/issues/36521

This needs:

A schema for the returned data
Docs
Tests