Hidraw USB mode doesn't work with DS4 Slim

Trying to get the DualShock 4 Slim controller to work through USB, because Bluetooth mode has too much input lag (but it works).
Ubuntu 16.04 x64,
Installed stable ds4drv through pip install ds4rv,
Ran sudo ds4rv --hidraw
The output is:
[info][controller 1] Created devices /dev/input/js1 (joystick) /dev/input/event16 (evdev)
[info][hidraw] Scanning for devices
[info][hidraw] Scanning for devices
[info][hidraw] Scanning for devices

Every time I disconnect and reconnect the controller USB cable it does a scan for devices but doesn't detect anything.
My lsusb sees the controller as:
Bus 003 Device 008: ID 054c:09cc Sony Corp.
When connecting the controller through USB dmesg outputs the following:
[583905.131514] usb 3-10: new full-speed USB device number 9 using xhci_hcd
[583905.260575] usb 3-10: New USB device found, idVendor=054c, idProduct=09cc
[583905.260577] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[583905.260578] usb 3-10: Product: Wireless Controller
[583905.260579] usb 3-10: Manufacturer: Sony Interactive Entertainment
[583905.260649] usb 3-10: ep 0x84 - rounding interval to 32 microframes, ep desc says 40 microframes
[583905.260651] usb 3-10: ep 0x3 - rounding interval to 32 microframes, ep desc says 40 microframes
[583905.271098] input: Sony Interactive Entertainment Wireless Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.3/0003:054C:09CC.0049/input/input125
[583905.271196] hid-generic 0003:054C:09CC.0049: input,hidraw1: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-0000:00:14.0-10/input3

Looks like the problem is that the device name is different for the DS4 Slim, I've managed to get ds4drv to work by changing one line in /backends/hidraw.py:
Before:
HID_DEVICES = {
    "Sony Computer Entertainment Wireless Controller": HidrawUSBDS4Device,
    "Wireless Controller": HidrawBluetoothDS4Device,
}

After:
HID_DEVICES = {
    "Sony Interactive Entertainment Wireless Controller": HidrawUSBDS4Device,
    "Sony Computer Entertainment Wireless Controller": HidrawUSBDS4Device,
    "Wireless Controller": HidrawBluetoothDS4Device,
}

I'll create a pull request.

Hi guys, sorry I'm new to the world of retro pie. How can I find the directory for /backends/hidraw.py? Like where is this located so I can edit the above information? I am using PuTTY to access the backend, but I can't seem to find it anywhere....

@Alexay This saves my day! Wonder why it's not merged yet.

didn't work here for me.  I did everything as shown above, does anyone have any other tips.

works for me, thanks so much!


Draft: docs: Update Speedrun link in docs

Should the video at https://meltano.com/popular-ways-to-use/ be updated too?


add more types to plugins

commandTree: CommandRegistrar
prequire: PluginRequire, and remove unnecessary prequire
IEvaluatorArgs

[x] grid
[x] tutorial
[x] k8s
[ ] OpenWhisk
[ ] composer
[ ] bash-like
[ ] core-support
[ ] editor

i think we have this pretty well covered for now


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86864

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87146

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87214

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87222

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87306

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87458

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87460

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87829

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87847

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88539

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88577

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88582

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/88738

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/89041

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/89043

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/89054

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


Optimize Get-ChildItem -Recurse -Name

PR Summary
Addresses #9119
Performance win is up to 50%.

Use new .Net Runtime path (folder/file) enumerator in PowerShell file system provider
Refactor existing code to one method
Add more tests

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@TravisEz13 @adityapatwardhan It seems Linux CI has an issue. I added obvious fail test  1 | Should -Be 2 to demo this. As you can see Windows CI and MacOS CI fail on the test but Linux CI passes. I guess Linux CI does not use the PR branch but master branch. Could you please look the issue?

Robotic bio
Venom
Pathagen
On Mon, Dec 7, 2020, 12:01 AM msftbot[bot]<EMAIL_ADDRESS>wrote:

This pull request has been automatically marked as stale because it has
been marked as requiring author feedback but has not had any activity for 15
days. It will be closed if no further activity occurs within 10 days of
this comment.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PowerShell/PowerShell/pull/12834#issuecomment-739744138,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ6WPOZ46BUGPLY3VE435SLSTSDUBANCNFSM4NN4S54Q
.

Please wrap as Experimental Feature

Please wrap as Experimental Feature

@SteveL-MSFT Intention is to replace implementation and to keep current behavior with one exclusion  - make sense to fix some minor bugs and inconsistences - it does not require Experimental Feature.


Add CACAO streams alongside data streams.

This PR makes it possible to use CACAO streams as part of the service, natively distributed alongside catkit2 data streams. This simplifies the interface and makes cacao streams easier to access.
It makes data on CACAO processes visible on catkit2 services with a minimal interface. This allows catkit2 services to control a CACAO RTC. It does not however make catkit2 data streams available to CACAO processes.
There is no impact on the performance of catkit2 streams. @RemiSoummer
Todo:

[ ] Test.
[ ] Add error checks upon opening and closing streams.
[ ] Use pyMilk on the Python proxy instead of bare IMAGE objects.

Thanks for clarifying no impact on performance of the streams.

Do you also want to handle milk's semaphores to wait and publish new data ?
It could be very useful to have the notion of slices (cnt1 for 3D buffer) to avoid data corruption.

@a-sevin

Do you also want to handle milk's semaphores to wait and publish new data ?

Right now, this PR aims for very loose coupling: just distributing ImageStreamIO streams alongside proprerties, methods and data streams already in catkit2 services. Interacting with that ImageStreamIO stream would be purely via their library, so via the ImageStreamIO library itself (for C++ compatibility) or via ImageStreamIOWrap or pyMilk (for Python compatibility).
On the C++ side, the ServiceProxy returns an std::shared_ptr<IMAGE> object. On the Python side, it will be a IMAGE object via ImageStreamIOWrap, though as of yet, I'm unsure how to link that together without needing to compile ImageStreamIOWrap.cpp inside the library too. Chatgpt told me about some very interestring constructions there, that I want to explore.
All of this to say: CACAO would still own its image streams. Catkit2 would just simplify connecting to them inside a service, since you only need to write the filenames inside the service itself, and that attribute would be available to all of catkit2, already opened and ready.
I'm not burning my hands yet on full integration of CACAO streams into catkit2 via the same interface as DataStreams. It feels like they are too dissimilar to make that easy.

It could be very useful to have the notion of slices (cnt1 for 3D buffer) to avoid data corruption.

Yes. I'm still confused by what CACAO is using. I was under the impression that CACAO used ring buffers for all image streams too. But after talking to Vincent and Olivier, it seems that is not the case? While that gives obvious advantages in cache usage (the reason I was told/remember from our conversation), data corruption seems a real issue with that imo. Catkit2 uses ring buffers by default to avoid data corruption (unless the reader is so slow that the writer catches up to it in the ring buffer).

OK ! Thanks for the clarification


Cannot assign to a reference or variable using ModalController lazy loaded

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
I'm not sure and I'm in difficult to figure out the where this exception comes from, but the problem is on a ModalPage we loaded with LazyLoading.
This error probably says nothing, but I think it should be a problem in ionic-angular or a thrid lib.
Error: Uncaught (in promise): Error: Cannot assign to a reference or variable!
Error: Cannot assign to a reference or variable!
    at _AstToIrVisitor.visitPropertyWrite (http://localhost:8100/build/vendor.js:103305:23)
    at PropertyWrite.visit (http://localhost:8100/build/vendor.js:85142:24)
    at convertActionBinding (http://localhost:8100/build/vendor.js:102863:45)
    at http://localhost:8100/build/vendor.js:104564:22
    at Array.forEach (native)
    at ViewBuilder._createElementHandleEventFn (http://localhost:8100/build/vendor.js:104560:18)
    at nodes.(anonymous function) (http://localhost:8100/build/vendor.js:104108:23)
    at http://localhost:8100/build/vendor.js:104510:22
    at Array.map (native)
    at ViewBuilder._createNodeExpressions (http://localhost:8100/build/vendor.js:104509:56)
    at c (http://localhost:8100/build/polyfills.js:3:13535)
    at Object.reject (http://localhost:8100/build/polyfills.js:3:12891)
    at NavControllerBase._fireError (http://localhost:8100/build/vendor.js:46348:16)
    at NavControllerBase._failed (http://localhost:8100/build/vendor.js:46336:14)
    at http://localhost:8100/build/vendor.js:46391:59
    at t.invoke (http://localhost:8100/build/polyfills.js:3:9283)
    at Object.onInvoke (http://localhost:8100/build/vendor.js:4657:37)
    at t.invoke (http://localhost:8100/build/polyfills.js:3:9223)
    at r.run (http://localhost:8100/build/polyfills.js:3:4452)
    at http://localhost:8100/build/polyfills.js:3:14076

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
global packages:
    @ionic/cli-utils : 1.5.0
    Cordova CLI      : 7.0.1
    Ionic CLI        : 3.5.0

local packages:
    @ionic/app-scripts              : 2.0.2
    @ionic/cli-plugin-cordova       : 1.4.1
    @ionic/cli-plugin-ionic-angular : 1.3.2
    Cordova Platforms               : android 6.2.3
    Ionic Framework                 : ionic-angular 3.5.2

System:
    Node       : v6.11.1
    OS         : Linux 4.10
    Xcode      : not installed
    ios-deploy : not installed
    ios-sim    : not installed
    npm        : 5.3.0

Hello, thanks for using Ionic! Could you post a code sample we could use to reproduce this issue please?

It could be, the issue is a side effect from this issue #12409
I' suggest we resolve firstly this issue and then see this issue is still there.


Setting aspect ratio for a surface plot

The code below shows that some surfaces would be best served by having the ability to scale the aspect ratios. I couldn't find out how to do this for a surface plot by reading the docs or scanning issues.
using Makie

x = -1:0.005:1
y = -1:0.005:1

f = (x, y) -> exp(sin(50x)) + sin(60exp(y)) + sin(70sin(x)) + sin(sin(80y)) - sin(10*(x+y)) + (x^2 + y^2)/4
scene = Scene(resolution = (2000, 2000))
surface!(scene, x, y, f, colormap = :seismic)
save("plot1.png", scene)

f = (x, y) -> (exp(sin(50x)) + sin(60exp(y)) + sin(70sin(x)) + sin(sin(80y)) - sin(10*(x+y)) + (x^2 + y^2)/4)/15
scene = Scene(resolution = (2000, 2000))
surface!(scene, x, y, f, colormap = :seismic)
save("plot2.png", scene)

You can scale!(scene, x_scale, y_scale, z_scale) any scene.

Thanks!


queryClient.clear() does not clear previously setQueryDefaults calls

Describe the bug
The clear function of queryClient does not clear query defaults that are previously set.
Thanks in advance, always loving & using this library ;)
Your minimal, reproducible example
https://codesandbox.io/s/vigorous-dirac-i8elz?file=/src/index.js
Steps to reproduce
/* eslint-disable jsx-a11y/anchor-is-valid */
import { QueryClient } from "react-query";

const queryClient = new QueryClient();

queryClient.setQueryDefaults("key", 5);
queryClient.clear();

console.log("is cleared?", queryClient.getQueryDefaults("key") !== 5);

Expected behavior
Expected that the clear method will also clear defaults, or at least have another function "clearDefaults".
How often does this bug happen?
No response
Screenshots or Videos
No response
Platform
all
react-query version
^3.33.7
TypeScript version
No response
Additional context
No response

This is not what clear does - it clears the underlying caches - the queryCache and the mutationCache. This is documented here: https://react-query.tanstack.com/reference/QueryClient#queryclientclear

queryClient.setQueryDefaults("key", 5);

not sure what this should do? with setQueryDefaults, you can set default options, like:
queryClient.setQueryDefaults("key", { staleTime: 5 });

setting the options to 5 wouldn't do anything and is also invalid in TypeScript.
for "clearing" defaults, you can just call queryClient.setQueryDefaults("key", {}), basically setting them to an empty object.

@TkDodo Thank you for the quick response. I'm sorry my bad, I meant:
queryClient.setQueryDefaults("key", { initialData: 5 });
I expected that after clearing the cache, this will also be cleared. But as I understand this is not intended.. Maybe I should not use initialData with setQueryDefaults.

You can for sure use it together. But clearing the caches does not reset the defaults.


build(pre-commit): Add pre-commit to make pr

Issue #, if available:
Description of changes:
pre-commit runs additional checks that make pr does not perform like trailing-whitespace
Changes:

Add pre-commit as a target in the Makefile

Checklist

[x] Meet tenets criteria
[x] Update tests
[x] Update docs
[x] PR title follows conventional commit semantics

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #368 (cce89b3) into develop (7c9a319) will decrease coverage by 0.33%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #368      +/-   ##
===========================================
- Coverage    99.94%   99.61%   -0.34%
===========================================
  Files           96       96
  Lines         3643     3622      -21
  Branches       175      175
===========================================
- Hits          3641     3608      -33
- Misses           0        7       +7
- Partials         2        7       +5

Impacted Files
Coverage Δ

aws_lambda_powertools/utilities/parser/types.py
71.42% <0.00%> (-28.58%)
:arrow_down:

...wertools/utilities/idempotency/persistence/base.py
92.94% <0.00%> (-6.42%)
:arrow_down:

aws_lambda_powertools/logging/logger.py
100.00% <0.00%> (ø)

aws_lambda_powertools/tracing/tracer.py
100.00% <0.00%> (ø)

aws_lambda_powertools/metrics/metrics.py
100.00% <0.00%> (ø)

aws_lambda_powertools/logging/formatter.py
100.00% <0.00%> (ø)

aws_lambda_powertools/utilities/batch/base.py
100.00% <0.00%> (ø)

aws_lambda_powertools/shared/jmespath_functions.py
100.00% <0.00%> (ø)

...ws_lambda_powertools/middleware_factory/factory.py
100.00% <0.00%> (ø)

...s_lambda_powertools/utilities/parser/models/sns.py
100.00% <0.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

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

Hey Michael, out of curiosity, did you run into those before?
make dev installs pre-commit hooks so they're run upon a commit.
That said, these are not run in CI and this is an improvement - is that what you intended?
Thanks ;)

@michaelbrewer yes I do run "make dev" and the pre-commit does run, but "make lint" does not include all of the same logic as "pre-commit".

@heitorlessa maybe there is an alternative solution with the same intent :)

Gotcha, that's what I thought. Sadly there is no alternative, as the pre-commit project decided not to add them as it deems to be a non-safe operation. I was thinking on perhaps removing some of them, but there are higher priority tasks now.
Merging this now ;) Thank you!


UMI + mpl-token-metadata | Runtime error: Class extends value undefined is not a constructor or null

Hi, I'm having a hard time make the library work on a react project.
When importing the following
import { createUmi } from "@metaplex-foundation/umi-bundle-defaults";
import { fetchDigitalAsset } from "@metaplex-foundation/mpl-token-metadata";

And using:
const umi = createUmi('http://<IP_ADDRESS>:8899').use(mplTokenMetadata())

I have the following runtime error:
ERROR
Class extends value undefined is not a constructor or null
TypeError: Class extends value undefined is not a constructor or null
    at<EMAIL_ADDRESS>(http://localhost:3000/static/js/bundle.js:136753:40)
    at options.factory (http://localhost:3000/static/js/bundle.js:545798:31)
    at __webpack_require__ (http://localhost:3000/static/js/bundle.js:545197:32)
    at fn (http://localhost:3000/static/js/bundle.js:545456:21)
    at<EMAIL_ADDRESS>(http://localhost:3000/static/js/bundle.js:155582:18)
    at options.factory (http://localhost:3000/static/js/bundle.js:545798:31)
    at __webpack_require__ (http://localhost:3000/static/js/bundle.js:545197:32)
    at fn (http://localhost:3000/static/js/bundle.js:545456:21)
    at<EMAIL_ADDRESS>(http://localhost:3000/static/js/bundle.js:155562:14)
    at options.factory (http://localhost:3000/static/js/bundle.js:545798:31)

A important point:

Only when something related to mplTokenMetadata is Written in the component, this one will be trigger. So something like:

  useEffect(() => {
    const test = async () => {
      try {
        const umiPk = publicKey(asset.mint.toBase58());
        const res = await fetchDigitalAsset(umi, umiPk); // Even if not call, RunTime Error is trigger
      } catch (error) {
        console.log("Error checking nftForMint: ", error);
      }
    };
    // test();  // <-- Commented, so test() is never called
  }, [asset]);

Version used:
    "@metaplex-foundation/mpl-token-metadata": "^3.2.1",
    "@metaplex-foundation/umi": "^0.9.2",
    "@metaplex-foundation/umi-bundle-defaults": "^0.9.2",

with Webpack 5.5.0
Thanks for the help :)

Build problem, how to fix it is the same as this issue:
https://stackoverflow.com/questions/78228700/how-to-fix-the-error-class-extends-value-undefined-is-not-a-constructor-or-null


Update configure-connect-to-azure-storage.md

RC1918 is a typo for RFC1918.

@msangapu-msft
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

sent Teams message to author

Thank you for this feedback. I'm addressing this in an update that's rolling out next week.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/249314
#please-close


migrate to new build

Use new fields from zig master.

Closed in favor of #1
Sorry did not see the PR.


Handle the VB.NET Like operator

Although the code works, the unit tests cannot be run in the test project because VB on .NET Core ATM doesn't support the Like operator. Supposed to be fixed by .NET Core 3. (see https://github.com/dotnet/roslyn/issues/26058 and https://github.com/dotnet/vblang/issues/373).

[X] Implemented
[ ] Write tests


Access certificates in "Local Computer" store from C++/UWP

Associated Microsoft doc. issue: https://github.com/MicrosoftDocs/winrt-api/issues/2288
The current C++ & C# samples projects are only able to utilize client certificates stored in the Current User\Personal store. This is fine for end-user authentication purposes, but not so good for machine/computer authentication.
Task: Figure out how to use client certificates stored in the Local Computer\Personal store as already done by Intune:

Associated doc:

https://learn.microsoft.com/en-us/uwp/api/windows.security.cryptography.certificates.certificatestores.findallasync
UWP CertificateQuery.StoreName: https://learn.microsoft.com/en-us/uwp/api/windows.security.cryptography.certificates.certificatequery.storename
https://learn.microsoft.com/en-us/uwp/api/windows.security.cryptography.certificates.certificatestores.getstorebyname
https://learn.microsoft.com/en-us/uwp/api/windows.security.cryptography.certificates.standardcertificatestorenames?view=winrt-22621
https://learn.microsoft.com/en-us/windows-hardware/drivers/install/local-machine-and-current-user-certificate-stores

The problem can be worked around by instead storing the certificate under Local Computer\Trusted People. It can then be retrieved using X509Store(StoreName.TrustedPeople, StoreLocation.CurrentUser) in C# and query.StoreName(L"TrustedPeople") in C++.


Env var docker compose

Description

Adding example file env vars to docker-compose.
For security, ignoring any .env at gitignore.

How to test?
Just add any .env file and check that will be ignored to commit.
Expected behavior
After add file variables.env to root of project will be possible add env vars easily to start the project, like GOOGLE_CREDENTIAL and ROOMS env variables.
Example variables.env
GOOGLE_CREDENTIAL=XXXXXX.googleusercontent.com
#ENFORCE_SSL=false
ROOMS_SOURCE=ENVIRONMENT
ROOMS_DATA=[{"id":"17755865-e0a6-4809-b389-eeff5590fd3d","name":"ValarDohaeris"},{"id":"490693fb-1751-498a-a23a-3785e677530c","name":"Osiris"},{"id":"da5eef6b-9e0c-4c32-81eb-17596114bf5b","name":"Icarus"},{"id":"e8ed1b89-afa9-469f-8108-e527b51c76a1","name":"Caduceus"},{"id":"bab0452c-bbfa-4365-b263-6aa9d26d8e33","name":"Brahma"},{"id":"706e8018-8e4e-40a2-a433-97535db6cc54","name":"Novalis"},{"id":"59008e8f-a961-4ad2-a2e4-b31b3e398a50","name":"Vigilant"},{"id":"2acbea57-64ba-4c55-9d20-042843c6e225","name":"Zion"}]

Hi, @henrylle thanks for the contribution. I have only one suggestion. Could you update the README.md file with this instruction?


SyntaxError: invalid syntax

Hi. I am getting this error after installing the package :(

Hi, thanks for contacting me! I'm sorry to hear that. The problem lies in the fact that your system is calling the wrong tap package. There are unfortunately two packages named tap, and the one we are using is the following:
https://github.com/mfouesneau/tap
You can install it using the command:
pip install git+https://github.com/mfouesneau/tap
The package that is installed in your site-packages folder is likely this one instead:
https://pypi.org/project/tap.py/.
Indeed, in my tap.py file there is no such line.
I hope this was helpful.

Thank you so much :)
This is working now.
I have one more question : " Can madys be used for estimating the ages of directly imaged planet and brown-dwarf hosting stars" ?
Swastik


Duplicate update frequency choice

Expected Behavior
When you filter Update frequency in Search data web page the expectation is one unique choice for each update frequency
Current Behavior
Currently the Continuous (and Kontinuerlig for Swedish page) choice appears twice as shown below

Steps to Reproduce

Go to Search data page Link
Click Update frequency dropdown button

Context
Google Chrome Version 92.0.4515.159 (Official Build) (64-bit)
Currently the choice with 184 results leads to correctly represented and translated update frequency information.

Picking any article from the 184 results shows the correct update frequency information.

While the other 8 results lead to incorrectly represented update frequency.

Possibly some faults arising from two keys with the same value in translation resources.
English translation file
Swedish translation file

Svarsfrekvensen här är tyvärr låg.... jag och andra har efterfrågat lite mer struktur/kvalitet från DIGG men inget svar se Frågor om dataportal - Feedback på metadata? Kontrolleras metadata och dess kvalité? - känns inte som det drivs proffsigt...

Issue created in internal backlog.

Hi, Thanks for reporting an issue,
We can not reproduce this anymore from the steps given.


docker: Error response from daemon: OCI runtime create failed: container_linux.go:349

@craigloewen-msft
I work on Ubuntu Subsystem on Windows 10 Enterprise Evaluation. hello-world programs etc work on the old version of Docker CE 18.03.1, on Ubuntu WSL, but not on the current version of Docker CE.
Then, I followed the article:
https://nickjanetakis.com/blog/setting-up-docker-for-windows-and-wsl-to-work-flawlessly
and did all steps there.
Unfortunately, for
~$ sudo docker run hello-world
I still get an error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused "EOF"": unknown.
although the docker is running.
Any ideas to fix it? Thank you!

Are you using WSL 2? (Install instructions here and instructions on how to check)
What build of Windows are you on?

It is Windows 10 Version 1909 (OS Build 18363.778). It sounds that WSL2 cannot be installed. My laptop is brand new (bought a few months ago). I have installed "Microsoft Visual Studio Enterprise Trial" since Windows which comes with the computer does not support Docker. So, any possible ways for me to still run Docker? Or, installing Ubuntu alongside with Windows 10, instead of WSL, might be a choice? Thank you!

Unfortunately,i also face the same probleam:Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:319: getting the final child's pid from pipe caused "EOF"": unknown.ERRO[0003] error waiting for container: context canceled
after i install docker-ce(19.03.8~3-0~ubuntu-bionic_amd64) on wsl(subsystem ubuntu 18.04 TLS) of windows server 2019 and service docker start , i try to run one image , e.g. hello-world with command "docker run hello-world" , i shows the above error.

You are on a version of WSL that does not directly support docker.
WSL 2 supports docker (since it has 100% system call compatibility). You can find install instructions here which will require you to be on Insider builds. It is set to release soon in Windows 10 version 2004, so you could always wait for that as well.
In the meantime, there are ways to run Docker with WSL 1 and Docker Desktop. Here's a sample article on how to do that that I found. Thank you 'Callback insanity' for the article! :)
I'll mark this as closed since I believe this is resolved, if you still have questions please reopen it and tag me to let me know!

I have resolved this issue by changing the selinux policy to permissive mode.

@rishi360 , is that on Windows or Linux ?

@craigloewen-msft, went thru all the steps from you last comment but still running into the same issue. Updated to latest 2004 version (Build 19041 ) to no vail. Anything you can suggest?

I am facing the same issue as the error message reported but i am on a CentOS VM


remove cob_relayboard

fixes parts of https://github.com/ipa320/care-o-bot/issues/46

requires https://github.com/ipa320/sick_flexisoft/pull/41

requires https://github.com/ipa320/cob_driver/pull/347

requires https://github.com/ipa320/cob_substitute/pull/46

with this PR raw3-1 depends on sick_flexisoft as it was using the relayboard_sim node...see https://github.com/ipa320/cob_driver/pull/347#issuecomment-319053349

with ipa320/cob_substitute#46 merged we could think about using the flexisoft_sim node for cob4's rather than relayboard_sim....

properly removed in #714


feat(TDI-43755):Allow "include deleted records" option to be available on the tSalesforceInput component on Bulk Query mode

What is the current behavior? (You can also link to an open issue here)
For feature: https://jira.talendforge.org/browse/TDI-43755
What is the new behavior?
Enable "include deleted records" for bulk and bulkv2 query in tSalesforceInput
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[x] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: success :star:


More reliable cache operations

As part of discussions while working on https://github.com/aspnet/Session/issues/99, there were proposals for adding logic in caching to make database operations more reliable. For example, sql database operations may fail intermittently. In this case it may be a good idea to add retry logic and allow users to specify retry policies. This probably needs some more design work.
cc @mikeharder @Tratcher @davidfowl

SqlConnection already has this logic internally.
And I think it should be handled by the user, it would not just happen in the cache if it was an issue.

When the failures are very provider specific I think there are some things that should be mitigated by the cache wrapper for those providers. E.g. Session is a major consumer of distributed cache and it can't know what different sql errors are retry able. Or Redis errors for that matter.
That said we have changed Session to suppress most errors, disable session for that individual request, and try again for the next request.

If SqlConnection has built in support for some of these scenarios, great. So long as it can be configured for the cache.

We'll need to fail silently instead of throwing exceptions.

Per discussion with the team, we decided not to implement retry logic/policies. We may add this in the future if we get more feedback that users want API for this.
For now we will harden Redis and SqlServer cache implementations to silently fail on all operations, and add logging when an expression is suppressed (#238).

We discussed more and will be reverting #238. Suppressing errors isn't a sensible default for some caching scenarios, so we'll need introduce API changes. For now, users who want more reliable operations should wrap cache operations in try/catch.

We'll revisit the design for 2.0.0.


fix: reinstating multienv switcher for view mode

Description
Adds multiple env switcher to the bottom bar
Fixes #31266
Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!CAUTION]
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8248561915
Commit: f1ea805a05961233a673f1a7fe59dd822c56dcff
Cypress dashboard:  Click here!
The following are new failures, please fix them before merging the PR:
cypress/e2e/Regression/ServerSide/GenerateCRUD/MySQL2_Spec.ts
To know the list of identified flaky tests - Refer here

Summary by CodeRabbit

New Features

Introduced a BottomBar component in the AppViewer for enhanced navigation and quick actions, conditionally displayed based on multiple environments and specific feature flags.

Refactor

Improved visibility of the SwitchEnvironment component and QuickGitActions by adjusting their rendering logic, ensuring they are always visible when viewMode is false.

/build-deploy-preview

@ayushpahwa please review if needed.
@brayn003 is this still relevant, seems like open for quite a while now. Kindly close this ASAP.

/build-deploy-preview skip-tests="true"

@somangshu I am still actively working on it. It has been open for sometime because the scope had changed during the implementation. I am planning to push it out within this week


Line break doesn't work with \left and \right

Before reporting a bug

[x] Check common issues.
[x] Check the bug is reproducible in the demo. If not, check KaTeX is up-to-date and installed correctly.
[x] Search for existing issues.

Describe the bug:
Automatic line break does not work on expressions enclosed by \left[ and \right].
When the same expression is enclosed, e.g., between \Big[ and \Big], line breaking works as expected.
To Reproduce:
Steps to reproduce the behavior:

Go to the demo
Turn displayMode off in the settings gear
Paste this

(\cosh K)^{N-1}\sum_{\{s_i\}}

\left[
1 + \sum_is_is_{i+1}\tanh K + \sum_{i=1}^{N-1}\sum_{j\ne i}(\tanh K)^2s_is_{i+1}s_js_{j+1}+\dots+(\tanh K)^{N-1}(s_1s_2)(s_2s_3)(s_3s_4)\dots(s_{N-1}s_N)
\right]

=2^N(\cosh K)^{N-1}

See all the expression is on one line, until the closing \right]

Expected behavior:
If you replace \left and \right with any absolute modifier like \Big (or blank), the expression fits nicely in its box.
Screenshots:
If applicable, add screenshots to help explain your problem.

\left[
[

Environment (please complete the following information):

KaTeX Version: 0.12.0
Device: Desktop
OS: Ubuntu 20.04
Browser: Firefox
Version: 78.0.2

@visika The same behavior occurs in LaTeX. The following image is from https://www.quicklatex.com/.

LaTeX allows for soft line breaks after binary operators and relational operators, but only when they are outside of any group. The \left[...\right] delimiters create a group, so no soft line breaks can occur between them.
KaTeX emulates LaTeX, so it behaves the same way.

Thanks for the clarification! I guess this can be closed then.


No more source map in build/

Not sure why webpack doesn't output it anymore.

devtool: 'sourcemap'?

Well this is embarrassing, I thought I saw source map in the config but turned out that wasn't the prod config.


Getting 404 while invoking a sample Inference svc based on modelformat tensorflow

/kind bug
What steps did you take and what happened:
Getting a 404 reposnse back from a kserve endpoint which is in green status on invoking its end point url from a jupyter nodebook via the kserve client python package (v 0.13.0).
URL internal
http://digits-recognizer-2024-09-12--17-42-28.kubeflow-user-example-com.svc.cluster.local
Client Code,
KServe = KServeClient()
isvc_resp = KServe.get("digits-recognizer-2024-09-12--17-42-28", namespace="kubeflow-user-example-com")
isvc_url = isvc_resp['status']['address']['url']
t = np.array(x_number_five)
t = t.reshape(-1,28,28,1)
inference_input = {
'instances': t.tolist()
}
response = requests.post(isvc_url, json=inference_input)
RESPONSE:
Actual Number: 5
http://digits-recognizer-2024-09-12--17-42-28.kubeflow-user-example-com.svc.cluster.local/
<Response [404]>
What did you expect to happen:
I expect response status '200' with the prediction of the digit back on invoking and posting the input to the internal endpoint.
What's the InferenceService yaml:
apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
annotations:
sidecar.istio.io/inject: 'false'
creationTimestamp: '2024-09-12T17:42:28Z'
finalizers:
- inferenceservice.finalizers
name: digits-recognizer-2024-09-12--17-42-28
namespace: kubeflow-user-example-com
resourceVersion: '2101260'
uid: 14d3e418-44c9-42e0-a6c1-cf4c454f7ff3
spec:
predictor:
model:
modelFormat:
name: tensorflow
name: ''
resources: {}
storageUri: s3://mlpipeline/models/detect-digits/
serviceAccountName: sa-minio-kserve
url: >-
http://digits-recognizer-2024-09-12--17-42-28.kubeflow-user-example-com.svc.cluster.local
Anything else you would like to add:
Looking at the istio gateway (cloud-local-gateway) pod log I see two  loggings and one IP "<IP_ADDRESS>" mentioned is of knative activator pod so it seems the request is reaching until activator and then fails.
> 2024-09-12T15:02:03-04:00 [2024-09-12T19:02:02.865Z] "POST / HTTP/2" 404 - via_upstream - "-" 4269 90 12 11 "<IP_ADDRESS>,<IP_ADDRESS>" "python-requests/2.32.3" "1d871c43-c9fd-4ef7-9c8a-be309429b42b" "digits-recognizer-2024-09-12--17-42-28-predictor.kubeflow-user-example-com.svc.cluster.local" "<IP_ADDRESS>:8012" outbound|80||digits-recognizer-2024-09-12--17-42-28-predictor-00003.kubeflow-user-example-com.svc.cluster.local <IP_ADDRESS>:60488 <IP_ADDRESS>:8081 <IP_ADDRESS>:60836 - -
>
> 2024-09-12T15:02:03-04:00 [2024-09-12T19:02:02.864Z] "POST / HTTP/2" 404 - via_upstream - "-" 4269 90 13 12 "<IP_ADDRESS>" "python-requests/2.32.3" "3b0af16a-0fb9-4e3f-b42e-e99d060561f1" "digits-recognizer-2024-09-12--17-42-28-predictor.kubeflow-user-example-com.svc.cluster.local" "<IP_ADDRESS>:8081" outbound|80||knative-local-gateway.istio-system.svc.cluster.local <IP_ADDRESS>:60836 <IP_ADDRESS>:8081 <IP_ADDRESS>:54190 - -

Environment:

Istio Version: 1.22.1
Knative Version: 1.12.4
KServe Version: 0.13.0
Kubeflow version: 1.9.0
Cloud Environment:[self-hosted k8s on ubuntu based machines]
Minikube/Kind version: n/a
Kubernetes version: (1.30.4):
OS (Ubuntu 22.04):

Here is the log from my sample kserve-container
2024-09-12 17:54:49.096723: I tensorflow_serving/model_servers/server.cc:89] Building single TensorFlow model file config:  model_name: digits-recognizer-2024-09-12--17-42-28 model_base_path: /mnt/models
2024-09-12 17:54:49.096879: I tensorflow_serving/model_servers/server_core.cc:465] Adding/updating models.
2024-09-12 17:54:49.096889: I tensorflow_serving/model_servers/server_core.cc:591]  (Re-)adding model: digits-recognizer-2024-09-12--17-42-28
2024-09-12 17:54:49.197182: I tensorflow_serving/core/basic_manager.cc:740] Successfully reserved resources to load servable {name: digits-recognizer-2024-09-12--17-42-28 version: 4}
2024-09-12 17:54:49.197198: I tensorflow_serving/core/loader_harness.cc:66] Approving load for servable version {name: digits-recognizer-2024-09-12--17-42-28 version: 4}
2024-09-12 17:54:49.197204: I tensorflow_serving/core/loader_harness.cc:74] Loading servable version {name: digits-recognizer-2024-09-12--17-42-28 version: 4}
2024-09-12 17:54:49.197305: I external/org_tensorflow/tensorflow/cc/saved_model/reader.cc:38] Reading SavedModel from: /mnt/models/4
2024-09-12 17:54:49.198875: I external/org_tensorflow/tensorflow/cc/saved_model/reader.cc:90] Reading meta graph with tags { serve }
2024-09-12 17:54:49.198889: I external/org_tensorflow/tensorflow/cc/saved_model/reader.cc:132] Reading SavedModel debug info (if present) from: /mnt/models/4
2024-09-12 17:54:49.199000: I external/org_tensorflow/tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-09-12 17:54:49.222141: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:211] Restoring SavedModel bundle.
2024-09-12 17:54:49.248322: E external/org_tensorflow/tensorflow/core/framework/node_def_util.cc:629] NodeDef mentions attribute debug_name which is not in the op definition: Op<name=VarHandleOp; signature= -> resource:resource; attr=container:string,default=""; attr=shared_name:string,default=""; attr=dtype:type; attr=shape:shape; attr=allowed_devices:list(string),default=[]; is_stateful=true> This may be expected if your graph generating binary is newer  than this binary. Unknown attributes will be ignored. NodeDef: {{node Adam/m/conv2d/bias}}
2024-09-12 17:54:49.253416: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:195] Running initialization op on SavedModel bundle at path: /mnt/models/4
2024-09-12 17:54:49.258678: I external/org_tensorflow/tensorflow/cc/saved_model/loader.cc:283] SavedModel load for tags { serve }; Status: success: OK. Took 61371 microseconds.
2024-09-12 17:54:49.259170: I tensorflow_serving/servables/tensorflow/saved_model_warmup_util.cc:59] No warmup data file found at /mnt/models/4/assets.extra/tf_serving_warmup_requests
2024-09-12 17:54:49.259507: I tensorflow_serving/core/loader_harness.cc:87] Successfully loaded servable version {name: digits-recognizer-2024-09-12--17-42-28 version: 4}
2024-09-12 17:54:49.260748: I tensorflow_serving/model_servers/server_core.cc:486] Finished adding/updating models
2024-09-12 17:54:49.260777: I tensorflow_serving/model_servers/server.cc:133] Using InsecureServerCredentials
2024-09-12 17:54:49.260784: I tensorflow_serving/model_servers/server.cc:383] Profiler service is enabled
2024-09-12 17:54:49.261500: I tensorflow_serving/model_servers/server.cc:409] Running gRPC ModelServer at <IP_ADDRESS>:9000 ...
[evhttp_server.cc : 245] NET_LOG: Entering the event loop ...
2024-09-12 17:54:49.262649: I tensorflow_serving/model_servers/server.cc:430] Exporting HTTP/REST API at:localhost:8080 ...

able to resolve this,  the isvc url was not right it worked after appending v1/models/digits-recognizer-2024-09-12--17-42-28:predict


Support custom elements v1

This PR resolves #141.

Looks good.
What about putting the is attribute in the "root" of the data object instead of under attrs. This thing is used differently than all the other properties on the attrs property. Additionally, the attributes module will pick the is attribute up as well and set it as an attribute, which, as far as I can tell, is unnecessary.

I need to study about custom elements.

That is, if is is the only interesting property? Are there others? If there are we should probably add a new property to the root with those properties as "subproperties".

There is no other options in document.createElement based on current W3C standard for custom elements v1.

Is there any issue in tests? Looks like they are not consistent on my machine (maybe resource limitation!).

Is there any issue in tests? Looks like they are not consistent on my machine (maybe resource limitation!).
BTW I can run the unit/core.ts in isolation without any issue.

CI for PRs runs only after explicit approval.
https://github.com/snabbdom/snabbdom/blob/master/CONTRIBUTING.md#allowing-ci-builds-of-pull-requests-from-forks

CI for PRs runs only after explicit approval.

So if I understood correctly, there is nothing for me to do. The PR should become trusted by the members of the repository, Am I right?

CI for PRs runs only after explicit approval.

So if I understood correctly, there is nothing for me to do. The PR should become trusted by the members of the repository, Am I right?

That's correct.

This PR looks good to me.
@mreinstein, you mentioned support for custom elements in another thread. Does this look good to you too?

@paldepind it looks ok, but I still have that question around using vnode1.data?.is === vnode2.data?.is Does the optional chaining get compiled out by whatever typescript config is currently in place? Because 15% of the browsers don't support this yet. Assuming it gets transpiled down to something like es6 then LGTM.

Yes, optional chaining is transpiled

@mreinstein Yes, as @jvanbruegge says it gets transpiled away. Also, we have been using ?. for 1-2 years now, so it's nothing new to this PR.
@the-dr-lazy Thanks a lot for the PR. Please resolve the conflicts and then we'll merge it 🙂

Thank you.


l3regex  is obsolete

I get the following warning when use media9:
*****************************************************************
**
** Package l3regex is obsolete and has been removed!
**
** Its functionality is now only provided as part of the expl3 package.
**
** The old packages will be removed entirely at the end of 2018.
**
** Therefore, please replace '\usepackage{l3regex}'
** with '\usepackage{expl3}' in your documents as soon as possible.
**
*******************************************************************

Package l3regex Warning: This package is obsolete --- use 'expl3' instead on in
put line 42.

Maybe you can simply delete \RequirePackage{l3regex}.

Fixed. Thank you for reporting.


Error in the diff3_merge module

For certain values of arrays, the diff3_merge module fails to merge them correctly, even when there is no conflict.
Here's an example where issues occur:
a = ["n4100522632", "n4100697091", "n4100697136", "n-10000", "n4102671583", "n4102671584", "n4102671585", "n4102671586", "n4102671587", "n4102671588", "n4102677889", "n4102677890", "n4094374176"]
o = ["n4100522632", "n4100697091", "n4100697136", "n4102671583", "n4102671584", "n4102671585", "n4102671586", "n4102671587", "n4102671588", "n4102677889", "n4102677890", "n4094374176"]
b = ["n4100522632", "n4100697091", "n4100697136", "n4102671583", "n4102671584", "n4102671585", "n4102671586", "n4102671587", "n4102671588", "n4102677889", "n4105613618", "n4102677890", "n4105613617", "n4094374176"]
merged result from diff3_merge
= ["n4100522632", "n4100697091", "n4100697136", "n4102671583", "n4102671584", "n4102671585", "n4102671586", "n4102671587", "n4102671588", "n4102677889", "n4105613618", "n4102677890", "n4102671583", "n4102671584", "n4102671585", "n4102671586", "n4102671587", "n4102671588", "n4102677889", "n4102677890", "n4094374176"]
GNU diff3 result
= ["n4100522632", "n4100697091", "n4100697136", "n-10000", "n4102671583", "n4102671584", "n4102671585", "n4102671586", "n4102671587", "n4102671588", "n4102677889", "n4105613618", "n4102677890", "n4105613617", "n4094374176"]
As can be seen, the GNU diff3 result is as expected. However, the npm-diff3 fails to merge and creates ambiguities. Any clues as to what's happening here?

I can reproduce this. It looks like the diff3 part of the code is at fault, because diffComm and diffPatch on o/a and o/b yield sensible-looking results.

Thank's for looking into it! It seems that the GNU diff works well in this case though I am not sure about other cases. Also, what I found is that when these ambiguities occur, sometimes even conflicts which should be raised are silently ignored. Something weird! Thanks anyway. I will keep hooked on to this thread for any update.

I found it. It's to do with JavaScript's .sort() function, which sorts by string representation by default. Here's the necessary patch: https://github.com/tonyg/synchrotron/commit/7eb715d08d3c7b479b30b9f413a4a61db9940e82

Ok I will try this right away!

Each of x and y is a "hunk" -- an array with a handful of fields. The first (index 0) is, I think, the line number of the hunk, but I'm hazy on the details. It was long ago. But I think it's clear that the intention of the sort() call was to order hunks by their first field.
(Try adding console.log(hunks) before and after the sort() to see what's going on.)

Any chance this fix can be pushed as an 0.0.2?


moved to bdg-formats 10.0

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/310/
Test FAILed.

Jenkins, retest this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/311/
Test PASSed.


(webrtc) added support for ice mux tcp and nat1to1ips

With this pull request introduce the following features:

TCP mux configuration support for webrtc.
Support for configuring a set of fixed public ip instead of webwrtc automatic discovery.

Configuration will have some new parameters:

webrtcICETCPMuxEnable (boolean)
webrtcICETCPMuxAddress (string)
webrtcICEHostNAT1To1IPs (list of string)

Using webrtc ice tcp mux allows your software to work properly on network infrastructures (server side) where you have more stringent limitations, in our case we needed it to work through a single tcp port, for example.
We need NAT1To1IPs because the software runs inside a container where it is exposed to the internet via a virtual network interface, without specifying NAT1To1IPs to webrtc the candidate will get an invalid ip.

please allow to use this server with this kind of features or it will be quite impossible to use the webrtc stream inside containerized environments. This features enable useful functionalities that are right now embedded in software like wowza.

Codecov Report

Merging #1323 (fa20dad) into main (738c953) will decrease coverage by 0.32%.
The diff coverage is 15.78%.

@@            Coverage Diff             @@
##             main    #1323      +/-   ##
==========================================
- Coverage   61.14%   60.81%   -0.33%
==========================================
  Files         113      113
  Lines       11963    12006      +43
==========================================
- Hits         7315     7302      -13
- Misses       4068     4126      +58
+ Partials      580      578       -2

Impacted Files
Coverage Δ

internal/core/webrtc_conn.go
0.00% <0.00%> (ø)

internal/core/webrtc_server.go
30.62% <25.00%> (-0.27%)
:arrow_down:

internal/conf/conf.go
73.97% <100.00%> (+0.27%)
:arrow_up:

internal/core/core.go
85.52% <100.00%> (+0.08%)
:arrow_up:

internal/core/source_static.go
66.91% <0.00%> (-3.01%)
:arrow_down:

internal/core/path.go
70.41% <0.00%> (-2.81%)
:arrow_down:

internal/core/rtmp_source.go
67.13% <0.00%> (-2.10%)
:arrow_down:

internal/core/hls_server.go
76.98% <0.00%> (ø)

internal/core/path_manager.go
92.72% <0.00%> (+0.76%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I applied codecov's suggestions, now it should be fine

Hello,

add the new parameters to rtsp-simple-server.yml with a brief description
add the new parameters to apidocs/openapi.yaml
add the new parameters to closeWebrtcServer in core.go, otherwise hot reloading / API will not work
tcpMuxLn is not closed when webrtcServer is closed - you have to save it somewhere and close it after s.ln.Close()

thanks

@aler9 I should have done everything

This has been merged with some changes, thanks for providing the code.
I'm interested too it in the possibility of running the server inside a container without --network=host, i'll add to the README a section that describes how to use these new parameters in order to achieve so.
Furthermore, i'll also dig into SetICEUDPMux(), and if it works, i'll add a parameter for that too.

Added in v0.21.1


Checkbox component "remembering" last state on soft refresh in Firefox

I've checked this issue in Firefox 41 & Chrome 46 both on Ubuntu 14.04
I have set a checkbox to be unchecked by default.
If I check it and then do a soft refresh the checked state is remembered in Firefox.
In Chrome the checkbox works as expected, reverting back to an unchecked state on soft refresh of page.
(I've also used the toggle switch component - same result)

just found this - http://stackoverflow.com/questions/299811/why-does-the-checkbox-stay-checked-when-reloading-the-page
apologies


Add "excluded" support for upsert

Continuing this ticket:
https://github.com/simolus3/moor/issues/1459#issuecomment-923131396
I found that using moor it is impossible to get data when executing a request.
For example, i have this function
return batch((batch) => batch.insertAll<SetsTable, DbSet>(
        setsTable,
        dbSets
            .map((set) => SetsTableCompanion.insert(
                id: set.id,
                title: set.title,
                difficulty: set.difficulty,
                isSelected: set.isSelected,
                wordsCount: Value(set.wordsCount),
                backgroundImageUrl: Value(set.backgroundImageUrl),
                color: set.color,
                isAddedByUser: set.isAddedByUser,
                language: set.language))
            .toList()
    ));

And i want some columns not to change and some to be replaced with new ones.
But in DoUpdate
onConflict: DoUpdate((old) => SetsTableCompanion.custom() i dont have access to the conflicting row.
SQLite makes it possible to get to the value that would be inserted, see "excluded": https://www.sqlite.org/lang_UPSERT.html
Going back to my example, for example, I want only the title field to be updated when a new data insert is requested. This is possible thanks to CustomExpression:
return batch((batch) => batch.insertAll<SetsTable, DbSet>(
        setsTable,
        dbSets
            .map((set) => SetsTableCompanion.insert(
                id: set.id,
                title: set.title,
                difficulty: set.difficulty,
                isSelected: set.isSelected,
                wordsCount: Value(set.wordsCount),
                backgroundImageUrl: Value(set.backgroundImageUrl),
                color: set.color,
                isAddedByUser: set.isAddedByUser,
                language: set.language))
            .toList(),
        **onConflict: DoUpdate((old) => SetsTableCompanion.custom(title: CustomExpression("excluded.title")))));**

So, it will be great if you add "excluded" support to the library. Thanks!

Thanks for opening this issue. I've added a DoUpdate.withExcluded API in 90e179643cadce3801fcb4425e4ebdc651d59da1.


⚠ Adacta-fintech.com has degraded performance

In 192a241, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 1386 ms

Resolved: Adacta-fintech.com performance has improved in 01bfc62.


Project Import - Start Pricing

    After discussion over phone @vinpahilwani

We agreed on

New Company will get this feature as free for 1 month from Create Date
All other Project after grace period (1 month), projects will be charged as same rate as Scheduled Project

Originally posted by @mitulpanch in https://github.com/Fammeo/EasyCloudBooks/issues/1703#issuecomment-1277215631

Problem-

This Module was for New Client to start ECB
but User use this Module on regular basis, to create project instead of other methods like Schedule Project
This module is free so user tend to work from here
Also 5000 Project at time, with all services and same logic as Previous Project Todo, Document Repeat is very convenient
but creating project in bulk is very heavy lifting on Tasks
so we need to introduce Pricing to stop unintended use of this module, at same price as other module
Any user can user this module, we dont want to stop any user from not using this
This module is free for new company for 1 month from date of creation

I consider this as Approved from @vinpahilwani
As this was approved on other Issue #1703


Initial zone set-up does not verify usable secondary storage - leads to issues

Latest cloudstack,
I just did a new cloudstack install, set up first zone, I accidentally used the wrong secondary NFS storage path, the set-up process gave no errors. Now, after creating new and correct secondary storage, I cannot migrate and cannot delete the old one. Zone set-up script should test connection and write ability of the secondary storage I'm thinking. Now i'm just looking for best way to fix, might just be easier to destroy the zone and re-create.
Oh, and, there are now templates and ISOs in "Not Ready" state with no option to remove them in the UI.
I'm trying to fix in the db now.
Update: easily removed the Not ready templates in vm_template table, now looking at changing secondary storage path
Update 2: I was able to use the UI to remove the old seconary storage after doing,
DELETE from template_store_ref WHERE state='Allocated';
DELETE FROM cloud.vm_template WHERE unique_name="<uid/name>";
Testing things now to make sure nothing is broken.
Thus far, still cannot register any new ISOs, they stay Not Ready, I tested ability to connect to the NFS share and write from the KVM host and mgmt host
2024-04-26 15:48:07,466 INFO  [o.a.c.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-0dc20f4d) (logid:1f8662b9) Unable to start secondary storage VM [333] for standby capacity, it will be recycled and will start a new one.
2024-04-26 15:48:07,466 DEBUG [c.c.a.SecondaryStorageVmAlertAdapter] (secstorage-1:ctx-0dc20f4d) (logid:1f8662b9) received secondary storage vm alert
2024-04-26 15:48:07,476 INFO  [o.a.c.s.PremiumSecondaryStorageManagerImpl] (secstorage-1:ctx-0dc20f4d) (logid:1f8662b9) Primary secondary storage is not even started, wait until next turn
Hmm, possibly other secondary storage access issues.
/usr/bin/mount -o nodev,nosuid,noexec <IP_ADDRESS>:/mnt/SSDStorage1/Cloudstack/template/tmpl/1/3 /mnt/a3313f14-20d0-3952-a7e1-571f5aa1654a) unexpected exit status 32: mount.nfs: Protocol not supported
that would be it
tried setting secstorage.nfs.version to 3 in cloudstack ui, no luck, going to try to force version on the KVM host - i'm digressing away from the initial bug at this point tho, i'll shutup now

@Jayd603 , is your system vm template seeded on your secondary storage? The path /template/tmpl/1/3 on your secondary storage should contain a valid systemvm template, something that should have happened automagically when the installation process would have gone flawless.

@Jayd603 , is your system vm template seeded on your secondary storage? The path /template/tmpl/1/3 on your secondary storage should contain a valid systemvm template, something that should have happened automagically when the installation process would have gone flawless.

Yeah, the NFS client says "protocol not supported" when it can't find a directory, just a tiny bit misleading response there. : - )   ... so, what actually happened was on initial zone set-up, the set up utility let me configure a non-usable NFS secondary server and carried on with no errors, this required editing the db and doing some digging to fix.  It's a sort of bug, since it should not allow a non-working secondary storage server to be added.

@Jayd603 , can you remove the zone/storage and re-add instead?

It takes a lot of steps to delete a zone and I don't remember if it removed the stale/bad secondary storage entry.  I think I added a new one ok and everything worked but the old one still needed to be removed in the DB.  I /might/ be wrong about that, but there should still be some type of basic check when adding secondary storage to prevent issues.   --- it's obviously a minor issue, I have this cluster up and running , just need to add more host machines now.  thanks


Pull core v0.2.2

Compat with latest core

https://github.com/tesla-local-control/tesla_ble_mqtt_core/releases/tag/v0.2.2 published in core code
@iainbullock I think you can merge when you're ready

@raphmur thanks for doing the mods on the _docker version too! I'll test and release later today / tomorrow


Add option to use fallback data when crawling spec list

not tested
I'm thinking this approach might help reducing risks for bogus updates to webref

I can't github-approve my own PR apparently, but I reviewed your fixes and improvements and they LGTM

Well, my fixes didn't really LGTM, so I had another look ;)
The crawl would lose itself in extracts and produce garbage. I integrated spec result expansion in the mix to make sure that the crawl function returns the right result, and that the save function generates the right exports.


CLOUDP-73750:mongocli ops-manager serverUsage project(s) serverType get, CLOUDP-73751: ops-manager serverUsage project(s) serverType set, CLOUDP-73753: mongocli ops-manager serverUsage org(s) serverType get, CLOUDP-73754: mongocli ops-manager serverUsage org(s) serverType set

Proposed changes

Jira ticket: CLOUDP-73750
Jira ticket: CLOUDP-73751
Jira ticket: CLOUDP-73753
Jira ticket: CLOUDP-73754

Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation (if appropriate)
[x] I have run make fmt and formatted my code

Further comments

ORGANIZATION - GET
./bin/mongocli om serverUsage organizations serverType get  -P ops
NAME          LABEL
TEST_SERVER   Test/QA Server

./bin/mongocli om serverUsage organizations serverType get  -P ops -o json
{
  "name": "TEST_SERVER",
  "label": "Test/QA Server"
}

ORGANIZATION - SET
./bin/mongocli om serverUsage organizations serverType set TEST_SERVER -P ops
Serve type TEST_SERVER correctly set

PROJECT - GET
./bin/mongocli om serverUsage project serverType get -P ops
NAME          LABEL
TEST_SERVER   Test/QA Server

./bin/mongocli om serverUsage project serverType get -P ops -o json
{
  "name": "TEST_SERVER",
  "label": "Test/QA Server"
}

PROJECT - SET
./bin/mongocli om serverUsage project serverType set TEST_SERVER -P ops
Serve type TEST_SERVER correctly set

waiting for https://github.com/mongodb/go-client-mongodb-ops-manager/pull/67


Update Vumi Go middleware to use config classes.

Ready for review.

:+1: When travis is happy.

:+1: when travis is happy


Enable flux to be converted in Jansky

Closes #47
Default is False though

Maybe easier solution would be to make new arg True by default and change the call in _mag function to set it to False - this way you would not need to modify anything outside the fink-utils scope?

Right! Updated

Thanks for checking!


Handle quotes as attributes

Fixes https://github.com/beautify-web/js-beautify/issues/1170

I see what you are doing here, but I don't really trust it sorry.
This is the kind of change that could break in a number of unexpected ways (ways I can't even think of off the top of my head).
I'm going to need you to put on your testing hat (or find someone who you trust to do so) and add  something like 10 to 20 more tests to this.   It is not enough to show that this works in the cases you know, I need to see examples of it not breaking under pressure.

@bitwiseman After doing this PR and digging around the code I figured the way the parser is built is too unreliable for me. In my application the output of this module was used for further processing and in my latest version I completely removed it. I wouldn't mind so much if the use was purely for cosmetic purpose. I will close this PR as I don't have any use in spending a lot of time on this anymore.
My advice would be to build this beautifier on top of a reliable, forgiving and well tested html parser.
P.S. I don't want to come of as too negative, I think this is a good and useful module. Just not forgiving enough towards certain use cases, like mine.


Fixes the CanBuildFrom for RequestCookieJar.

Before the RequestCookieJar instance would duplicate all elements of
the current set whenever the CanbuildFrom was invoked. This is no
longer the case.

Fixes #602

:+1:  I think it could be merged into the release-0.13.x branch to be part of a bugfix release.

Oh my! How embarrassing! Thanks for the PR @isomarcte, especially for the test case.
:+1: for merging this into a 0.13.x bugfix release.

Cherry-picked into release-0.13.x, merged to master.


M365 assessment tool report doesn't provide option for the 'SharePoint add-in and ACS' scan mode

AddInsACS' scan mode is not available in version 1.6.0. Does that command not be incorporated, or is there something I need to include?
C:...\00microsoft365assessment>microsoft365-assessment.exe start --mode AddInsACS --tenant zzz.sharepoint.com --sitesfile "C:...\00microsoft365assessment\sites.txt" --authmode Application --applicationid <> --certpath "My|CurrentUser|<>"
You are using the latest version 1.6.0
Cannot parse argument 'AddInsACS' for option '--mode' as expected type 'PnP.Scanning.Core.Services.Mode'. Did you mean one of the following?
Classic
InfoPath
Syntex
Workflow
Description:
Starts a new Microsoft 365 Assessment
Usage:
microsoft365-assessment start [options]
Options:
--mode <Classic|InfoPath|Syntex|Workflow> (REQUIRED)    Assessment mode [default: Syntex]
--tenant  (REQUIRED)                            Name of the tenant that will be assessed (e.g.
contoso.sharepoint.com)
--siteslist                                  List with site collections to assess
--sitesfile                                  File containing a list of site collections to assess
--authmode <Application|Device|Interactive> (REQUIRED)  Authentication mode used for the Microsoft 365 Assessment
[default: Interactive]

@nikhilshankarsingh : that's weird, we've hundreds of customers using version 1.6.0 and using mode AddInsACS. Can you cross check all microsoft365-assessment.exe processes are killed, then download again from https://github.com/pnp/pnpassessment/releases/download/v1.6.0-windows/microsoft365-assessment.exe and double click the .exe. Once loaded type start --help and check the output

Thanks @jansenbe, downloading the .exe tool again has helped. I can now see the "AddInsACS" mode. Really appreciated your quick response.
C:...\00microsoft365assessment>microsoft365-assessment.exe start --help
You are using the latest version 1.6.0
Description:
Starts a new Microsoft 365 Assessment
Usage:
microsoft365-assessment start [options]
Options:
--mode <AddInsACS|Classic|InfoPath|Syntex|Workflow>     Assessment mode [default: Syntex]
(REQUIRED)
--tenant  (REQUIRED)                            Name of the tenant that will be assessed (e.g.
contoso.sharepoint.com)
--siteslist                                  List with site collections to assess
--sitesfile                                  File containing a list of site collections to assess

worked well! thanks


Deployment failing since recent mup update

A tail of my remote logs says:
ReferenceError: require is not defined
    at app/node_modules/wait-for-mongo/node_modules/mongodb/lib/mongodb/connection/repl_set/strategies/ping_strategy.js:1:49
    at app/node_modules/wait-for-mongo/node_modules/mongodb/lib/mongodb/connection/repl_set/strategies/ping_strategy.js:368:3
    at /opt/efs/app/programs/server/boot.js:222:10
    at Array.forEach (native)
    at Function._.each._.forEach (/opt/efs/app/programs/server/node_modules/underscore/underscore.js:79:11)
    at /opt/efs/app/programs/server/boot.js:117:5
error: Forever detected script exited with code: 8
error: Script restart attempt #77

wait-for-mongo works just fine on the command line if I ssh into the box.

Have you updated  to "nodeVersion": "0.10.36" in your  mup.json file and
re-run mup setup before deploying?
On Thu, Mar 26, 2015 at 5:59 PM, Simon Turvey<EMAIL_ADDRESS>wrote:

A tail of my remote logs says:
ReferenceError: require is not defined
at app/node_modules/wait-for-mongo/node_modules/mongodb/lib/mongodb/connection/repl_set/strategies/ping_strategy.js:1:49
at app/node_modules/wait-for-mongo/node_modules/mongodb/lib/mongodb/connection/repl_set/strategies/ping_strategy.js:368:3
at /opt/efs/app/programs/server/boot.js:222:10
at Array.forEach (native)
at Function..each..forEach (/opt/efs/app/programs/server/node_modules/underscore/underscore.js:79:11)
at /opt/efs/app/programs/server/boot.js:117:5
error: Forever detected script exited with code: 8
error: Script restart attempt #77
wait-for-mongo works just fine on the command line if I ssh into the box.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/339.

--
Matt Moyles
http://mattmoyles.com

Nope! Somehow I'd managed to run npm install wait-for-mongo in my local app folder while debugging a connection string issue!
Closing issue. Reason: chronic user error revealing the truth behind the maxim "The solution to a 2-hour problem will always present itself 30 seconds after posting a github issue and will do so in a such a way as to unmask the poster as a ham-fisted clown."


prepare: effectiveProfile to avoid dimensions shorter than 145 pixels

Fixes #24

Were you able to do some testing ie. with the Jellyfish video? Would be helpful to add to the PR description.

AFAIK the transcode-cli worked with a 258p profile and failed with a 257p profile, which is exactly the theorical threshold to get the effective width to be 145px or 144px.

This is not the fix for the E2E testing video correct? Sounds like we are still unsure on root cause for that.

Correct! The fix will likely be on the orchestrators instead, since we were just able to reproduce that the issue only started happening on the version 0.5.30. On<EMAIL_ADDRESS>it works, and with this fix we should theoretically have no assets failing transcode!

@tqian1 Just rebased this on top of main and set the dev branch to point to it!
Meaning that, if we've already found all the issues, there should be no invalid argument happening in staging anymore!

It worksssss
https://lvpr.tv/?monster&recording=d7b8451f-4ddc-4e07-931a-8f6860ea5569

Actually seems like the most reliable fix for this will actually be in lpms, and they already have a fix in-flight! Should we close this one?
livepeer/lpms#326

Yes, if it's fixed there there's no need for this hardcoded fix

The fix in lpms is not yet merged, and I believe we need this to be able to make the prepare task fatal (#40). As such, I'm reopening, merging, and will be deploying this tomorrow so we don't get so many valid videos that would fail in our processing.
This should be reverted as soon as the lpms fix is merged and deployed on our Os.


Agent-based

The whole article describes agent-based, but summary says agentless.

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

Verified; thanks @juanandmsft


rospkg.common.ResourceNotFound: lane_detection

I got error message listed in the title when I run the new_lane_detection.py. is lane_detection another package I need install, I am newer to python? very kind of you to reply or any reference.

Please wait a few days, we are working on implementation of new nodes and a lot of little fix are still to do.
In theory lane_detection is this package but it was renamed some days ago.
Come back soon, we're working on documentation as well :)

Thank you! I has just commented (##)  the line loading lane_detection package and it works now. Looking forward your update continue. best wishes!


No settings are applied to channels

It has already been reported before that auto-play/buffer settings don’t work with channels, but in fact, no settings are being applied to channels.
Whenever I am on a user’s YouTube home page (e.g., this one), the first video in the list will automatically start playing. Moreover, it will be using the HTML5 player even though I have set YTC to use “Aggressive Flash” for channels. Also, if I happen to want to watch that video and make it fullscreen, it will switch to HD even though I have set everything to use the lowest resolution. (Neither my system nor connection can handle HD, so switching back to SD is really difficult with the 100% CPU usage, but I don’t believe that Google understands or cares about that.)

You should really be using the HTML5 player, Flash Player support will be removed in time on YouTube (it may start around the time that NPAPI support is disabled in Chrome 45). HTML5 has a benefit of allowing you to watch videos at higher frame rates and gives better statistical data when you use the "Stats for nerds" option, so I suggest switching over.

SuperSajuuk commented a day ago
You should really be using the HTML5 player…  HTML5 has a benefit of…

It also has the “benefit” of automatically playing videos (and in HD no less), thus sucking up my limited bandwidth and completely hanging my system by pegging the CPU at 100%. ◔_◔
Like most people, I have no intention of using the HTML5 player until it works better than the Flash player (or at all).
It’s just yet another example (in a long list of examples) of Google fascistically ignoring user feedback and tyrannically telling us what to want and like. It takes people like Jeppe to wasting their time and effort to work around Google’s dictatorship to make life tolerable again.

Oh, and I forgot to mention that I was using version 2.1.5. I upgraded to 2.1.7 and it seems to be working now, so I’ll close this, and thanks!

2.1.7 is obsolete. Please keep that in mind.

Huh? ಠ_ఠ It says 2.1.7 is the current version.

It does, and if we wanted to be pedantic we could say that it is the latest stable release. Unfortunately, there have been many changes on YouTube's end (and to Firefox, I believe) that break that version.
@YePpHa has been doing all bugfixes and updates on the Developer Version and has not yet released a new "stable" version. He has stated that he plans the next stable release to be 2.1.8, but none of us are sure when that is going to be, particularly given the fact that addons.mozilla.org is very slow to approve submitted extensions and the Chrome Web Store has decided to not accept this extension.


Code Snippets no longer load if invalid JSON file exists in metadata folder

In my metadata/code-snippets directory, I currently have two Code Snippet JSON files. One is a valid JSON file and the other is an invalid JSON file:

badjson.json  (missing a double quote and comma)
{
	"schema_name": "code-snippet",
	"display_name": "bad_json",
	"metadata": {
		"description": "bad_json file,
		"language": "python"
		"code": [
			"print('hello')"
		]
	}
}

common-imports.json
{
	"schema_name": "code-snippet",
	"display_name": "frequently used imports",
	"metadata": {
		"language": "python",
		"code": [
			"import numpy as np",
			"import pandas as pd"
		]
	}
}

Previously, when starting Elyra and accessing the Code Snippet area, an error is shown in the terminal:
JSON failed to load for metadata 'badjson' in namespace 'code-snippets' with error: Invalid control character at: line 5 column 33 (char 110).

but the valid code snippet is successfully loaded:

However, with the latest updates the error is still show in the terminal, but there is also an error dialog presented in the ui and the valid code snippet does not get loaded:

Is this expected behavior or should valid code snippet continue to load (although other invalid code snippets may exist)?

Hi Va - I suspect this is due to the metadata refactor. I'll need to look into this as I thought there was a test for this condition.  Thanks for creating this issue.

The refactor doesn't handle the case where the invalid file is due to loading from storage - but still handles the case where the JSON can be loaded but its validation against the schema fails.
I'll fix this today.


Sync with upstream prebuild

This PR is based on #18. Only the last three commits are relevant for review.

It would be really great if someone could review this PR. It makes prebuild-install compatible with the latest release of prebuild. Please tell me if there's anything I missed here.
It makes sense to merge #18 before reviewing this PR to reduce the diff and effort for reviewing.

\cc @mafintosh @ralphtheninja @juliangruber

Cool, is this what will let us build cross platform Electron apps from one system?

Exactly!

I published this branch as @lgeiger/prebuild-install and we are using it in zeromq.js without any problems.
This PR consists mostly of cherry-picked commits from prebuild. It would be great if we can get it merged soon to prevent prebuild-install from diverging even more. After this I'd like to start working on https://github.com/mafintosh/prebuild/issues/148.

LGTM

@lgeiger New minor?

@ralphtheninja To be save I would opt for a major version as we did in prebuild.
But a minor would also work for me.

New major sounds good to me. But wait for proxy things first?

But wait for proxy things first?

Sounds good to me 👍

2.0.0


Fixes issues with resolution of canonical paths

This PR addresses an issue with absolute module paths not being resolved correctly in certain cases. For example, paths like ./A/moment.js and ../moment.js  did not resolve to the same path and the moment.js module was loaded twice like a different module.
See issue #822 for more details.

@PanayotCankov - we think the normalizePath call here: https://github.com/NativeScript/ios-runtime/commit/fba35eab7fe12a307a64aeda06f65b9aaa1e07e5 is redundant. Can you shed some more light on why it was introduced considering that we already call [NSString stringByStandardizingPath] on the module path?

https://developer.apple.com/documentation/foundation/nsstring/1407194-stringbystandardizingpath
For absolute paths only, resolving references to the parent directory (that is, the component “..”) to the real parent directory if possible using stringByResolvingSymlinksInPath. For relative paths, references to the parent directory are left in place.
When live-sync-ed without --sync-all-files, the CLI and the runtime work in a way the app folder only is delivered to the device in an external folder, and the node_modules (tns_modules on device) are symlinked, then there are cases where absolute paths that are concatenated with relative paths are resolved to the real directory in the app bundle. Then there are cases where from some modules, content in the app folder is searched, again by relative paths. This ended up to a state where the same module may be executed twice, once in the symlinked path and once in the original (e.g. have two "application" executed leading to funny stuff such as "there is no main entry specified" on startup).
I couldn't find iOS method that will collapse paths such as "/abv/../cde" to "/cde" without resolving symlinks to real paths, and that's why normalizePath is there, we really need it to resolve .. and . in paths without following symlinks.

@PanayotCankov - we've introduced a change in TKLiveSync that replaces sym-linking with hard-linking which should allow us to remove the normalizeString call and solely rely on [String stringByStandardizingPath] call.

Well, it seems hard-linking is not working for us either as the app bundle and the livesync package live in different partitions. We will resort to solely using [String stringByStandardizingPath] at the point where the main token is appended to the absolute path. @mbektchiev @tdermendjiev @PanayotCankov .


FTP producer: Error writig file

I have a simple route to write a file to a ftp server:
from("timer:kotlin?period=60s")
  .setBody().constant("FTP Test")
<EMAIL_ADDRESS>  .to("log:info")

It a public test server. When deploying i got:
[2]
[2] Message History
[2] ---------------------------------------------------------------------------------------------------------------------------------------
[2] RouteId              ProcessorId          Processor                                                                        Elapsed (ms)
[2] [route1            ] [route1            ] [timer://kotlin?period=60s                                                     ] [       860]
[2] [route1            ] [setBody1          ] [setBody[constant{FTP Test}]                                                   ] [         5]
[2] [route1            ] [to1               ]<EMAIL_ADDRESS>[       850]
[2]
[2] Stacktrace
[2] ---------------------------------------------------------------------------------------------------------------------------------------
[2] org.apache.camel.component.file.GenericFileOperationFailedException: Error writing file [foo.bar]
[2] 	at org.apache.camel.component.file.GenericFileProducer.writeFile(GenericFileProducer.java:307) ~[org.apache.camel.camel-core-2.23.1.jar:2.23.1]
[2] 	at org.apache.camel.component.file.GenericFileProducer.processExchange(GenericFileProducer.java:169) ~[org.apache.camel.camel-core-2.23.1.jar:2.23.1]
[2] 	at org.apache.camel.component.file.remote.RemoteFileProducer.process(RemoteFileProducer.java:57) ~[org.apache.camel.camel-ftp-2.23.1.jar:2.23.1]
[2] 	at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61) ~[org.apache.camel.camel-core-2.23.1.jar:2.23.1]

I think the ftp component tries to write the data to a file before uploading and i missed to configure some temporary workspace. How could it be done? Am i missing some hints in the documentation?

Hi @MehrCurry , usually those kind of issues happen when using active mode, so it should be not related to Camel K.
Can you try adding &passiveMode=true at the end of the URI?

Problem solved! Thank you.

Iam facing this issue only difference is intead of ftp using ftps

Iam facing this issue only difference is intead of ftp using ftps

Hello. This is an old issue. I suggest you to report the problem you're facing in a new issue adding all details and possibly a reproducer. Thanks.


pcsx2: 2.1.17 -> 2.1.102

Closes https://github.com/NixOS/nixpkgs/issues/335956
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

1 package built:

pcsx2


would be nice runs page showed the name of the machine the code ran on

-L

It's in the latest release!


Issues with AXOM_DEVICE_CODE macro

The AXOM_DEVICE_CODE macro is supposed to only be enabled for code that is running on a device (i.e. when __CUDA_ARCH__ is defined).
I ran into a situation where AXOM_DEVICE_CODE appeared to be defined within host code. I suspect this is (somehow) related to the combination of object libraries and CUDA_SEPARABLE_COMPILATION, but haven't yet had a chance to track this down.
I'll try to create a reproducer.
Note: I ran into this while attempting to resolve https://github.com/LLNL/axom/issues/724

Pay attention to this.

We suspect this is somehow related to our usage of object libraries.
We should revisit this issue after removing object libraries in #1057.

Closing until we can define a reproducer.


Fix badges?

Right now some of the badges in the readme are broken. This doesn't look good as a potential user of @es-shims lol. I think it would be a good idea to fix them. 😉

I'll remove the david.dm ones, but the other one works, it's just that rate limited responses get cached unfortunately.


Add fallback site url for redirect.

There may be an instance where admin wants to present a particular page as opposed to logged-in profile, main page, or post one was viewing before logging in.

https://wisdmlabs.com/blog/create-settings-options-page-for-wordpress-plugin/


How to add a label to update

I can't get a label counter working with this lib, how to set it up?. I have a separate function which does the label update with NSTimer I used
func fireProgress(timer: NSTimer) {
    self.valueLabel.text = self.timeRemaining
}

how can I do the same with this lib?

I wrote this off the top of my head so it may not work, but something like this is probably what you're looking for. Feel free to reopen this issue if you run into any more problems.
// Setup
let label = UILabel() // Label we'll update
var remaining: Double = 10.0 // Total time remaining
let interval: Double = 1.0 // We want the timer to fire once a second

// Timer
let dispatchTimer = DispatchTimer(interval: interval, closure: { (timer: RepeatingTimer, invocations: Int) in
            // Ensure we update label on main queue
            dispatch_async(dispatch_get_main_queue()) {
                remaining -= interval
                label.text = "\(remaining)"
                if (remaining <= 0.0) {
                    timer.stop()
                }
            }
    })

// Starts the timer. Waits the provided interval time before firing the first time
dispatchTimer.start(false)

Thanks a lot, I'll give it a try


2.1 Strings - Manacher's Algorithm - Audio

Description
Discuss Manacher's Algorithm and its significance. Mention about its implementation, complexity, and examples.
Important: Do not use assign command for this issue.
Task

[ ] Audio

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to Issue Guidelines.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be same as the issue.
This issue is only for 'GWOC' contributors of 'DSA' Domain.

@nimisha-yadav I would like to work on this issue.
Name-Hilag Shah
Batch - DSA Batch 1

@nimisha-yadav  I would like to take up this issue
Kindly assign this issue to me


Link to usage in DockerBuild.md is broken

See page  https://github.com/groupon/DotCi/blob/master/docs/usage/DockerBuild.md

Thank you. Fixed.


TST: Intermittent failure in test_remove_repeated_points_invalid_result on Linux

The Linux builds for GEOS 3.11 and main started to regularly fail (but not always) in the test_remove_repeated_points_invalid_result test (remove_repeated_points is new in GEOS 3.11, so those two builds are the only ones that run this test):
 =================================== FAILURES ===================================
_____________ test_remove_repeated_points_invalid_result[geom0-2] ______________

geom = <POLYGON ((0 0, 1 0, 1 1, 0 1, 0 0))>, tolerance = 2

    @pytest.mark.skipif(shapely.geos_version < (3, 11, 0), reason="GEOS < 3.11")
    @pytest.mark.parametrize(
        "geom, tolerance", [[Polygon([(0, 0), (1, 0), (1, 1), (0, 1), (0, 0)]), 2]]
    )
    def test_remove_repeated_points_invalid_result(geom, tolerance):
>       with pytest.raises(shapely.GEOSException, match="Invalid number of points"):
            shapely.remove_repeated_points(geom, tolerance)
E       Failed: DID NOT RAISE <class 'shapely.errors.GEOSException'>

I can't reproduce it locally.

Adding some print debug statements in https://github.com/shapely/shapely/pull/1651 indicates that if it fails to raise the expected error, then it returns the (invalid) polygon POLYGON ((0 0, 0 0, 0 0)) (which is strange that this could be returned, because normally GEOS should error when trying to construct a LinearRing of 3 points)
I opened an issue about this on the GEOS side: https://github.com/libgeos/geos/issues/759

One consideration is to use a flaky plug-in for flaky tests.

To not have red CI on our side, you mean? (so we can ignore it for now) I could also add an xfail strict=False (to not have to add an additional test dependency)

Yes, either approach to "ignore it for now", since it's an upstream issue.

This is already fixed upstream in GEOS main, so I will just skip the test for now for 3.11 and only run it with GEOS main (if 3.11 gets a bugfix release with this included, we could revert that) -> https://github.com/shapely/shapely/pull/1656


Image vulnerabilities XLSX export fails when the image name is longer than 31 characters

Describe the bug
When the image name exceeds 31 characters, the XLSX export fails without any visual error.
In the browser console, the following error is seen:
Uncaught Error: Sheet names cannot exceed 31 chars
    wA xlsx.mjs:16546
    WM xlsx.mjs:24346
    onClick VulnerabilitiesDetails.jsx:253
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3
xlsx.mjs:16546:50
    wA xlsx.mjs:16546
    WM xlsx.mjs:24346
    onClick VulnerabilitiesDetails.jsx:253
    React 11
    unstable_runWithPriority scheduler.production.min.js:18
    React 3

To Reproduce
Steps to reproduce the behavior:

Upload an image with a name (repo name + tag) having a length greater than 31 characters to a zot instance.
In ZUI, open the image details and navigate to the Vulnerabilities tab.
Click the export button and select xlsx as the option.
Observe that nothing happens in the UI.
Observe the error in the browser console.

Expected behavior
The XLSX should be successfully created and a file download initiated.
Screenshots

Desktop:

OS: Ubuntu 22.04 amd64
Browser firefox
Version 123.0

@vrajashkr thanks for catching and reporting this.


request help: large file upload  not  work

Issue description
I configured an apisixroute and connected it to the apache service with backends
Normal operation is fine, but it does not work normally when uploading large files (> 2GB).
It looks like timeout and it's weird. Applying request_buffering: false to the proxy-control to plugin will cause more errors. Is there a solution?
apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
  name: route
spec:
  http:
  - name: route-upload
    match:
      hosts:
      - aaa.com
      paths:
      - /upload/*
    upstreams:
    - name: web-upload
    timeout:
      connect: "8h"
      send: "8h"
      read: "8h"
    plugins:
    - name: proxy-control
      enable: true
      config:
        request_buffering: false

Environment

apisix ingress-controller 1.8.0
kubectl 1.28.2 (output of kubectl version):
Rocky Linux release 8.8

apisix has limiting for request body size. you need to use client-control plugin to change the max size of the request body.

https://apisix.apache.org/docs/apisix/plugins/client-control/


Update expected platform strategy package

The class OpenShiftPlatformStrategy was moved in a recent upstream patch (rh-jmc-team/container-jfr#391), so this adjusts the environment variable that explicitly specifies this strategy should be selected. #393 is a backport of #391 for v1 and also moves the Strategy to the same location, so this applies for either version.

Makes sense. We should probably update the image tag to a new beta release that has https://github.com/rh-jmc-team/container-jfr/pull/393 in it, otherwise this won't deploy correctly.

Makes sense. We should probably update the image tag to a new beta release that has https://github.com/rh-jmc-team/container-jfr/pull/393 in it, otherwise this won't deploy correctly.

BETA4 PR here: https://github.com/rh-jmc-team/container-jfr/pull/394
And this PR has been updated to deploy that version.

BETA4 PR here: https://github.com/rh-jmc-team/container-jfr/pull/394
And this PR has been updated to deploy that version.


Fixes for #673

Minor fixes for last  PR -> #673
See: https://github.com/lbryio/lbry-app/pull/673#issuecomment-336708385, https://github.com/lbryio/lbry-app/pull/673#pullrequestreview-69416809

Wrong PR, I need to revert that :stuck_out_tongue:

@btzr-io ux-patch shows no diff from master for me. I believe this was already merged but I had forgotten to push to master and close this ticket.
I think I did tip you for this on Slack already though. If I'm mistaken, please let me know.


entity has all components field, it makes debugging  tired.

Hi, I'm making a simulation game with entitas.
https://youtu.be/h6PBZ3JCgjM
when I try debug some entity, the debugger shows all components of contexts.

my game has 200 + components with [Game] contexts.
how can I check desired, or only has components?
or suggest debugger, please?

I think too many components in one context is too hard to maintenance.
split ur game context to multi contexts?

@nomadfighter
yes you right.
I'm finding a solution before start refactoring...

@rglobig
Thank you!