Provide once trigger

Feature request:
A user would like for a trigger to be fire once at a specific time and date, and optionally delete the trigger after the fire.
One idea for UX could be: (at is UTC based)
wsk trigger create onshot --feed /whisk.system/alarm/once --param at `December 24, 2017 23:30:00`

current stat is to set a cron trigger with maxTrigger of 1, which would cause a lot of problems in terms of cleaning up "dead" triggers and trying to guesstimate when is going to actual fire.

related to https://github.com/apache/incubator-openwhisk-package-alarms/issues/86.

could you elaborate:  what are the ("lot of") problems with layering this on top of cron?
I would hope the cron implementation can handle this pattern without difficulty.

i think carlos wants it to auto-destruct after firing. if done via rules, there is a race. it could be done with a sequence wrapper around the activated action, i suppose.

Under the hood we the implementation will use 'new Cron(new Date(stringdate))'
The a lot problems was more on capturing the users point of view.
To some users it would be confusing trying to understand that we can "hack" cron to take a date string.
Also provides a cleaner API to ask the user what it wants to do with the trigger when done.
This is a building block for when we get to a point of the feed service create a rule for them and have a syntax like
'''
wsk action create foo --at $somefuturedate
'''
sugar to tell the system handle the triggers and rules (create them and clean them) for me just run this action once at $somefuturedate

👍 on this feature and an optional parameter to "delete after firing".
I can see lots of use-cases when an action wants to schedule a trigger to fire a set period after it is running using this approach.

👍 this would be a very useful feature for me as currently I'm having to run clean up jobs looking for stale triggers and rules.
For my perspective it would be good to have an uber trigger that encapsulates the trigger and rule e.g. a Job.
It's the job which I can designate as runOnce and have the system clean up after it's finished.


update def?: RSC complex

Current def is
A protein complex similar to, but more abundant than,
the Swi/Snf complex. The RSC complex is generally
recruited to RNA polymerase III promoters and is
specifically recruited to RNA polymerase II promoters
by transcriptional activators and repressors.
but perhaps this should e extended to mention its role in
NHEJ ?
PMID: 15870268
Reported by: ValWood
Original Ticket: "geneontology/ontology-requests/3314":https://sourceforge.net/p/geneontology/ontology-requests/3314

thanks www.movied.org


Swift template ignore *.xcodeproj

Swift template ignore *.xcodeproj
Yesterday I created a new xcode project and I realized my mate had problems with the project after pulling since template generated a .gitignore file with .xcodeproj
Is this behavior expected?? Why ignore the project file; I think this is needed for opening an Xcode Project.

Ah that's due to the SwiftPM stack.  I'll remove that.


Helper module

Respond to users requests for level specific help. Each time a user requests help for the same level a more detailed answer is returned.

What is the max depth for this detailed answer
for example if user tries to find detailed answer for real level 1 more than 4 times subsequently how to respond.

I would suggest it simply loops back round to the original response.
On 22 Jan 2015 14:21, "linkin-park"<EMAIL_ADDRESS>wrote:

What is the max depth for this detailed answer
for example if user tries to find detailed answer for real level 1 more
than 4 times subsequently how to respond.
—
Reply to this email directly or view it on GitHub
https://github.com/HackThis/NexBot/issues/43#issuecomment-71026582.


Pydantic complains about missing email

Describe the bug
The person idenfication heuristics give the impression that the email address is optional when specifying people. This is also necessary, if an author wishes to be listed by name only.
However, when I omit the email address in somesy.toml, I get the following error:
Error: 1 validation error for SomesyInput
project.people.3.email
  Field required
    For further information visit https://errors.pydantic.dev/2.5/v/missing

To Reproduce
Run somesy sync on an input file that contains a person for which no email is supplied.
Expected behavior
No email is listed for this person in the output files
Environment
Provide information about versions of relevant software packages.

Python Version 3.10
Ubuntu 22.04
pydantic version 2.5.3

Most of the Author metadata like in pyproject.toml requires an email since their format is author_full_name <euthor_email>. Therefore, we made family names, given names, and email required fields. In person heuristics, what we would like to have is actually an orcid profile, which is better for recognizing humans since emails change with affiliation too.

Neither pyproject nor CITATION.cff  require an email. I do not understand why somesy needs to be stricter than the output standards. For privacy reasons and/or to avoid spam authors may choose to not supply an email adress which in my opinion should be respected. Please consider reopening this issue.

Talked about this again and we agreed on there are use cases where email cannot be provided. Will be implemented on the next cycle


Don't  hard code gcc in makefile

The Makefile.in hardcodes the compiler, this can be obtained from the vars as %CC% (or %LD% )

This seems to be fixed already.


Feature request: Hide "Quit: Save window placement" option on Linux if using Wayland session

Is your feature request related to a problem? Please describe.
Unlike X11, Wayland applications cannot specify where on the screen its top level window should be placed. That location is determined by the window manager.
Describe the solution you'd like
Since the option is irrelevant for Wayland users, it would make sense to hide the option if the app is running on Wayland.
Describe alternatives you've considered
Another option would be to have an informational tool tip next to the option. However, this is less elegant because (1) not everybody is using Linux, (2) not every Linux user is using Wayland, (3) Linux users would have to read the message, and (4) not every Linux user even knows if they are using Wayland and so would be confused by the message.
Additional context
No response

Will do that!


Bugfix/str 4114 illuminatecontractsfilesystemfi

This offers four methods to solve the issued outlined here:
https://github.com/nWidart/laravel-modules/issues/1054

We now have a command that we can run to clear the cache (by force, overriding what's in the config) if we need to.
If we don't have a modules.json file, then we're probably in the wrong path, so clearing the cache will fix this. Failing that, we (more) gracefully throw an exception, which can be caught, rather than a fatal error we had previously.
You can pass in a MODULES_PATH now as an environment variable and specify that if you need to via a .env file
It will now handle both paths that are full paths and relative paths, either will work

Updating module.json as a const is good.
But can we just clear cache in application level ?

Updating module.json as a const is good.
But can we just clear cache in application level ?


ERROR: No matching distribution found for opencv-python (from checkerboard)

Great Job!
It works fine in my laptop, but I get the next message when installing in my remote machine:

ERROR: Could not find a version that satisfies the requirement opencv-python (from checkerboard) (from versions: none)
ERROR: No matching distribution found for opencv-python (from checkerboard).

Do you know which open-CV version dependency do I need?
Thanks a lot

It can be solved cloning the repository from Githug, instead of doing "pip install checkerboard"

Ah I see, I had both opencv-python and opencv-contrib-python as dependencies in setup.
I have pushed a fix to only require opencv-python


Update turn-on-or-off-skype-for-business-client-feedback-reporting.md

Added support for TPM 2.0

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


ARROW-1521: [C++] Add BufferOutputStream::Reset method

This allows a arrow::io::BufferOutputStream to be reused

Codecov Report

Merging #2665 into master will decrease coverage by 0.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2665      +/-   ##
==========================================
- Coverage    87.3%   87.22%   -0.09%
==========================================
  Files         381      381
  Lines       59440    59460      +20
==========================================
- Hits        51895    51862      -33
- Misses       7473     7524      +51
- Partials       72       74       +2

Impacted Files
Coverage Δ

cpp/src/arrow/io/memory.h
100% <ø> (ø)
:arrow_up:

cpp/src/arrow/io/memory.cc
89.03% <100%> (+0.51%)
:arrow_up:

cpp/src/arrow/io/io-memory-test.cc
100% <100%> (ø)
:arrow_up:

go/arrow/math/int64_avx2_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/memory/memory_avx2_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/math/float64_avx2_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/math/uint64_avx2_amd64.go
0% <0%> (-100%)
:arrow_down:

go/arrow/math/float64_amd64.go
33.33% <0%> (-33.34%)
:arrow_down:

go/arrow/math/int64_amd64.go
33.33% <0%> (-33.34%)
:arrow_down:

go/arrow/math/uint64_amd64.go
33.33% <0%> (-33.34%)
:arrow_down:

... 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 af20905...f8149af. Read the comment docs.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 12:30:29 on 2023.04.18
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 0, errors out: 0
Original problem ID: 18922
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=18922

Problem has been resolved in 3m 0s at 12:33:29 on 2023.04.18
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 18922


[language] delete tx builtins from parser, compiler, source language,…

… tests
Eliminating every use of tx builtins other than GetTxnSender. This does not yet eliminate the builtins from the bytecode file format, which we will do separately along with other breaking changes to the file format.
Motivation
Finishing the project of eliminating tx builtin opcodes other than GetTxnSender.
Have you read the Contributing Guidelines on pull requests?
Yup
Test Plan
Deleting dead functionality, should be pure refactoring.
Related PRs
https://github.com/libra/libra/pull/2018
https://github.com/libra/libra/pull/2020
must be landed before this will pass tests.

Will do!

So, I tried to remove them from transaction.move but was getting a bunch of unexpected typechecking failures in tests that don't use those procedures. I think I'll push that to a follow-up given that this PR is already pretty substantial.

@bors-libra r=tzakian

:pushpin: Commit 2c7e10c has been approved by tzakian

:hourglass: Testing commit 2c7e10cb8198a02654019e7cc456436173ff5957 with merge 066ff3ab31731e43dfe2138460bf65433b1f4cc9...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: tzakian
Pushing 066ff3ab31731e43dfe2138460bf65433b1f4cc9 to master...


HWiNFOIndexList typo

Lists CPU cores 1,2,3,4,6,7. Probably doesn't hurt anything.

Whatever that screen shows is what it's getting from HWiNFO. Go through the setup tutorial again and make sure you select all sensors in the HWiNFO Gadget tab of the sensor settings.

Turns out it is the HWiNFO Gadget. I'll report it to the dev.
Sorry for the wasted post.

Is HWiNFO showing core 5 in the actual sensors list? It's possible that it just isn't seeing that sensor at all.

No, it also shows cores 1,2,3,4,6,7. That has to be a bug, right? It's a 6 core processor.

Yeah, I would report it to Martin.


[cli] deploy internalservererror

Investigative information
Please provide the following:

Timestamp:
Function App version (1.0 or 2.0-beta):
Function App name: gooten-slothy
Function name(s) (as appropriate):
Invocation ID:
Region: east us

Repro steps
func azure functionapp publish gooten-slothy
Expected behavior
uploads server funcs
Actual behavior
Provide a description of the actual behavior observed.
Publish /Users/micahsmith/printio/gooten-slothy contents to an Azure Function App. Locally deleted files are not removed from destination.
Getting site publishing info...
Creating archive for current directory...
Uploading archive...
Error uploading archive (InternalServerError).
Retry: 1 of 2
Creating archive for current directory...
Uploading archive...
Error uploading archive (InternalServerError).
Retry: 2 of 2
Creating archive for current directory...
Uploading archive...
Error uploading archive (InternalServerError).

@micahasmith - do you have a sample of your project you can share? Is it Node.js based? If so, can you share your package.json?

@christopheranderson the function app name is above, you're more than welcome to jump into the codebase.
{
  "name": "gooten-slothy",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "directories": {
    "test": "test"
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "request": "^2.83.0",
    "sequelize": "^4.20.3",
    "tedious": "^2.0.1"
  }
}


Devtools value width limited

Version Number
7.49.3
Codesandbox/Expo snack
N/A
Steps to reproduce

Open devtools
Use complex object in form data
See truncated form data view

Expected behaviour
Width of value in devtools takes max width
What browsers are you seeing the problem on?
Firefox
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Any updates?


Error trying to launch WSL

I am getting the below error as of today when trying to launch Extraterm. It was fine last night and I don't know of anything on my PC that would have changed since then.

 I already had the window opened and it was on the taskbar and I didn't realize it and was trying to open another.

In the latest release, Extraterm has better behaviour in this situation and it should still start up.

Ah, very good. Thank you much.


(some) Settings reset on update

Issue Type: Bug
on an update, my settings.json file (in all open instances when I "restart to update") removes "workbench.colorCustomizations"
VS Code version: Code 1.37.0 (036a6b1d3ac84e5ca96a17a44e63a87971f8fcc8, 2019-08-08T01:22:37.660Z)
OS version: Darwin x64 16.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2900)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
16.00GB (0.09GB free)

Process Argv
-psn_0_2019821

Screen Reader
no

VM
0%

Extensions (35)

Extension
Author (truncated)
Version

ng-template
Ang
0.801.1

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

bracket-pair-colorizer-2
Coe
0.0.28

angular2-snippets
dan
1.0.21

vscode-markdownlint
Dav
0.30.1

gitlens
eam
9.9.3

EditorConfig
Edi
0.13.0

tslint
eg2
1.0.44

vscode-npm-script
eg2
0.3.8

prettier-vscode
esb
1.9.0

vscode-jasmine-test-adapter
hbe
1.6.0

vscode-test-explorer
hbe
2.14.1

search-node-modules
jas
1.3.0

angular-essentials
joh
0.6.3

Angular2
joh
8.1.1

vscode-peacock
joh
3.0.1

vscode-styled-components
jpo
0.0.26

node-module-intellisense
lei
1.5.0

require-js
lic
0.1.31

dotenv
mik
1.0.1

vscode-docker
ms-
0.7.0

atom-keybindings
ms-
3.0.6

cpptools
ms-
0.24.1

vscode-typescript-tslint-plugin
ms-
1.2.2

vsliveshare
ms-
1.0.657

debugger-for-chrome
msj
4.11.7

angular2-inline
nat
0.0.17

angular-console
nrw
8.0.10

vscode-code-outline
pat
0.2.1

material-icon-theme
PKi
3.8.1

vscode-graphql
Pri
0.2.1

vscode-jest-test-adapter
rtb
0.2.0

quokka-vscode
Wal
1.0.240

ReactSnippets
xab
2.3.0

(1 theme extensions excluded)

Could be that an extension you installed could have caused this? Can you please try to repro with extensions disabled?

I guess it might, although I have no newly installed extensions and this
has only recently started happening.
I'll give it a go - although I have to wait for the next VSCode update to
do so...
On Wed, 14 Aug 2019 at 10:06, Sandeep Somavarapu<EMAIL_ADDRESS>wrote:

Could be that an extension you installed could have caused this? Can you
please try to repro with extensions disabled?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/79015?email_source=notifications&email_token=AAK7ZQQAJPRFTRSMOCRURUDQEPDJPA5CNFSM4ILH63R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4IFR4A#issuecomment-521165040,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK7ZQRYBYMEFALUBYSCUM3QEPDJPANCNFSM4ILH63RQ
.

--
I don't feel
And it feels great

I also have this issue as well
Version: 1.36.1
Commit: 2213894ea0415ee8c85c5eea0d0ff81ecc191529
Date: 2019-07-08T22:55:08.091Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 5.0.0-23-generic
Extensions:
davidanson.vscode-markdownlint-0.30.1
formulahendry.auto-rename-tag-0.1.0
mrmlnc.vscode-json5-1.0.0
orta.vscode-jest-3.0.2
dbaeumer.vscode-eslint-1.9.0
joelday.docthis-0.7.1
mrmlnc.vscode-scss-0.6.2
ryu1kn.annotator-1.0.0
2gua.rainbow-brackets-0.0.6
eamodio.gitlens-9.9.3
johnpapa.vscode-peacock-3.1.0
ms-azuretools.vscode-docker-0.7.0
tomashubelbauer.vscode-markdown-table-format-1.0.1
alefragnani.project-manager-10.6.0
editorconfig.editorconfig-0.13.0
karigari.chat-0.20.2
msjsdiag.debugger-for-chrome-4.11.7
vscode-icons-team.vscode-icons-9.2.0
arjun.swagger-viewer-2.2.2
eg2.vscode-npm-script-0.3.8
kumar-harsh.graphql-for-vscode-1.15.1
ms-python.python-2019.8.30787
wix.vscode-import-cost-2.12.0
christian-kohler.npm-intellisense-1.3.0
esbenp.prettier-vscode-1.9.0
mauve.terraform-1.3.12
ms-vsliveshare.vsliveshare-1.0.694
christian-kohler.path-intellisense-1.4.2
formulahendry.auto-close-tag-0.5.6
mikestead.dotenv-1.0.1
ms-vsliveshare.vsliveshare-audio-0.1.64
cssho.vscode-svgviewer-2.0.0
formulahendry.auto-complete-tag-0.1.0
mjmcloug.vscode-elixir-1.1.0
ms-vsliveshare.vsliveshare-pack-0.3.3

There is a new stable build 1.37.1 available. Please check if you can repro.

@sandy081
This issue still happens on 1.37
I have opened a ticket with the extension repo
https://github.com/johnpapa/vscode-peacock/issues/258

@sandy081 - I saw @Nibblesh has the same peacock extension as myself - figured that a likely culprit. So with that disabled on an update, it did not clear my settings. So I'd say the issue is likely with that plugin not vscode.

I'm closing this as I believe it is the plugin not vscode.


CSI 1.0 Driver name should be forward domain notation

Per the CSI spec the name of a CSI driver must conform to the following requirements:
The name MUST follow domain name notation format (https://tools.ietf.org/html/rfc1035#section-2.3.1).

It SHOULD include the plugin's host company name and the plugin name, to minimize the possibility of collisions.

It MUST be 63 characters or less, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), dots (.), and alphanumerics between.

This field is REQUIRED.

CSI 0.x required reverse domain notation. But CSI 1.0 dropped the "reverse" part of the requirement. The expectation is that the name will be normal (forward) domain notation.
So instead of io.datera.csi.dsp the driver name should be dsp.csi.datera.io

Hey saad, thanks for catching that.  This version of the CSI plugin's yaml files is deprecated and needed to be removed.  We've moved development over to github.com/Datera/datera-csi which also includes the source code for the plugin itself.
I'll get this removed so it won't accidentally be used as a reference.

Thanks. Could you also submit a PR to https://github.com/kubernetes-csi/docs/pulls to update the link in https://kubernetes-csi.github.io/docs/drivers.html ?


Cleans out ASCII_8BIT encoded response bodies

We have an end point that returns an MP3 for streaming, this allows you to document endpoints that return such binary files.

Looks good, can you include a test though?

+1

Feel free to add this PR to my fork.
https://github.com/jramos/rspec_api_documentation

@Ruxton can you check to see that 8e670ea works for you?


Ignoring h264 video stream because it's unsupported

On the cargo run example, I get:
     Running `target/debug/examples/client mp4 --url 'rtsp://<IP_ADDRESS>:10554/tcp/av0_0' --username admin --password 123456 out.mp4`
W20211130 01:57:55.777 main retina::codec::h264] Ignoring bad H.264 format-specific-params "packetization-mode=1;profile-level-id=00f004;sprop-parameter-sets=6QDwBE/LCAAAH0gAB1TgIAAAAAA=,AAAAAA==": bad sprop-parameter-sets: bad NAL header e9
I20211130 01:57:55.779 main client::mp4] Ignoring h264 video stream because it's unsupported
I20211130 01:57:55.779 main client::mp4] No suitable video stream found
I20211130 01:57:55.781 main client::mp4] Ignoring pcma audio stream because it can't be placed into a .mp4 file without transcoding
I20211130 01:57:55.781 main client::mp4] No suitable audio stream found
E20211130 01:57:55.782 main client] Fatal: Exiting because no video or audio stream was selected; see info log messages above

from https://github.com/scottlamb/retina/blob/cd841b9f80f1d0dbd7226ad43c3023e4c6e84c40/examples/client/mp4.rs#L724
On my app, I get just this first video frame, and then nothing more:
video frame: VideoFrame { timestamp: 2022 (mod-2^32: 2022), npt 0.000, start_ctx: PacketContext(Tcp { msg_ctx: RtspMessageContext { pos: 868, received_wall: WallTime(Timespec { sec:<PHONE_NUMBER>, nsec: 431245911 }), received: Instant { tv_sec: 83828, tv_nsec: 228186887 } }, channel_id: 0 }), end_ctx: PacketContext(Tcp { msg_ctx: RtspMessageContext { pos: 29964, received_wall: WallTime(Timespec { sec:<PHONE_NUMBER>, nsec: 439222146 }), received: Instant { tv_sec: 83828, tv_nsec: 236162701 } }, channel_id: 0 }), loss: 0, new_parameters: Some(VideoParameters { rfc6381_codec: "avc1.4D0028", pixel_dimensions: (1920, 1080), pixel_aspect_ratio: None, frame_rate: Some((2002, 60060)), extra_data: Length: 35 (0x23) bytes
    0000:   01 4d 00 28  ff e1 00 14  67 4d 00 28  e9 00 f0 04   .M.(....gM.(....
    0010:   4f cb 08 00  00 1f 48 00  07 54 e0 20  01 00 04 68   O.....H..T. ...h
    0020:   ea 8f 20                                             ..  }), is_random_access_point: true, is_disposable: false, data_len: 30023 }

on the line
tokio::select! {
                                    item = session.next() => {
                                        match item {
                                            Some(Ok(CodecItem::MessageFrame(m))) => {
                                                info!("{}: {}\n", &m.timestamp, std::str::from_utf8(&m.data[..]).unwrap());
                                            },
                                            Some(Ok(CodecItem::VideoFrame(v))) => {
                                                info!("video frame: {:?}", v);

packet capture of cargo run example sent via email

Actually, it works on my app. I don't receive just one packet. Turns out I was doing this:
Some(Ok(CodecItem::VideoFrame(v))) => {
                                                info!("video frame: {:?}", v);

                                                let mut nal_bytes = Vec::new();
                                                avcc_to_annex_b(&v.data(), &mut nal_bytes);
                                                let packet = Box::new(RetinaEncodedPacket {
                                                    video_frame: v,
                                                    nal_bytes: nal_bytes
                                                });
                                                on_produce(packet);

                                            }

and it got caught in a loop. Probably something wrong with my avcc_to_annex_b implementation that I'm testing.
So the only problem is in the cargo run example

Ahh, basically I missed in #42 a place where the example was checking for a supported codec by having the parameters. It needs to be updated to not expect them to be present right away.


fix(docs): Update the Helm doc links following Helm 3 GA

The links to Helm docs have changed after Helm 3 went GA and replaced Helm 2 as the latest version of Helm. This PR updates the links to point to the correct Helm 2 docs.
Fixes #29

Thanks for the review @spzala


Release 3.1.0

Release Notes WIP on https://github.com/MariaDB4j/MariaDB4j/compare/main...vorburger:MariaDB4j:CHANGELOG-3.1.0 ...

The MariaDB4j v3.1.0 will bump (upgrade) its ch.vorburger.exec:exec dependency from 3.1.5 to 3.2.0, see https://github.com/vorburger/ch.vorburger.exec/issues/187, and note https://github.com/vorburger/ch.vorburger.exec/compare/exec-3.1.5...exec-3.2.0. I'm currently waiting for that to "propagate" through Maven Central in order to proceed here.

./mvnw release:prepare fails due to:
[INFO] 11/17 prepare:scm-commit-release
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd '/home/vorburger/git/github.com/vorburger/MariaDB4j' && 'git' 'add' '--' 'pom.xml' 'mariaDB4j-core/pom.xml' 'mariaDB4j/pom.xml' 'mariaDB4j-springboot/pom.xml' 'mariaDB4j-app/pom.xml' 'mariaDB4j-maven-plugin/pom.xml'
[INFO] Working directory: /home/vorburger/git/github.com/vorburger/MariaDB4j
[INFO] Executing: /bin/sh -c cd '/home/vorburger/git/github.com/vorburger/MariaDB4j' && 'git' 'rev-parse' '--show-prefix'
[INFO] Working directory: /home/vorburger/git/github.com/vorburger/MariaDB4j
[INFO] Executing: /bin/sh -c cd '/home/vorburger/git/github.com/vorburger/MariaDB4j' && 'git' 'status' '--porcelain' '.'
[INFO] Working directory: /home/vorburger/git/github.com/vorburger/MariaDB4j
[INFO] 12/17 prepare:scm-tag
[INFO] Tagging release with the label mariaDB4j-3.0.2...
[INFO] Executing: /bin/sh -c cd '/home/vorburger/git/github.com/vorburger/MariaDB4j' && 'git' 'tag' '-F' '/tmp/maven-scm-676608308.commit' 'mariaDB4j-3.0.2'
[INFO] Working directory: /home/vorburger/git/github.com/vorburger/MariaDB4j
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for mariaDB4j-pom 3.1.0-SNAPSHOT:
[INFO]
[INFO] mariaDB4j-pom ...................................... FAILURE [01:18 min]
[INFO] mariaDB4j-core ..................................... SKIPPED
[INFO] mariaDB4j (all-in-one artifact) .................... SKIPPED
[INFO] mariaDB4j-springboot ............................... SKIPPED
[INFO] mariaDB4j-app ...................................... SKIPPED
[INFO] mariaDB4j-maven-plugin ............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:19 min
[INFO] Finished at: 2024-03-27T23:25:03+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:3.0.1:prepare (default-cli) on project mariaDB4j-pom: Unable to tag SCM
[ERROR] Provider message:
[ERROR] The git-tag command failed.
[ERROR] Command output:
[ERROR] fatal: tag 'mariaDB4j-3.0.2' already exists

which is correct... except why is trying to tag 3.0.2 when I'm trying to release 3.1.0 ?!

I've just successfully deployed a MariaDB4j 3.1.0 release to Maven Central. (It may take a few hours to "propagate".)
For the record, the tag was a bit of a mess; locally 9e27d2a, but remote via #921 (because cannot push with PR)
Release Notes here and here.


Generate multiple toProtocol() for runtime polymorphism instead of pick

protocol Animal:
  proc eat

protocol CanFly:
  proc fly

class Cat impl Animal:
  proc eat =
    discard
  # automatically defined
  proc toProtocol(): Animal

class Bird impl (Animal, CanFly):
  proc eat =
    discard
  proc fly =
    discard
  # automatically defined
  proc toProtocol(): Animal
  proc toProtocol(): CanFly
  proc toProtocol(): Animal & CanFly

converter may be good for it

& operator in https://github.com/glassesneo/OOlib/issues/140


fix: Remove title attribute for disable browser's default tooltip (fix: #187)

Please check if the PR fulfills these requirements

[x] It's submitted to right branch according to our branching model
[x] It's right issue type on title
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[x] It does not introduce a breaking change or has description for the breaking change

Description

Remove title attribute from menu buttons for disable browser's default tooltip.
ref: #187

Thank you for your contribution to TOAST UI product. 🎉 😘 ✨

리뷰 완료했습니다. 수고하셨습니다.


Support rich text formatting for documentation/descriptions

Rich text formatting in descriptions/documentation
Documentation for APIs often involve more than just raw text. Common reasons to use rich text formatting include rendering of tables or embedding links into the generated reference documentation.
For an example, see the APIM List By Tags endpoint which illustrates the attempt to use (valid) openapi descriptions that contains a table in the API documentation as well as the issue with tools treating description fields as plain text (broken rendering).
OpenAPI support for rich text
OpenAPI allows for rich text formatting in description fields using CommonMark. As evident from the example above, there are gaps in our toolset with regards to how rich text is handled.
Possible solution

Only support CommonMark for input.
Add new @richDoc decorator for rich documentation that takes a format parameter. The only supported value (for now) is CommonMark.

@richDoc(
"""
|One|Two|
|-|-|
|1|2|
|3|4|
""", "CommonMark")
model ModelWithTableDocs {};

Alternate solution
Change the @doc decorator so that it accepts CommonMark instead of raw text. For the most part, that is an extension to its current decorator definition (in most cases, you don't have accidental markup in the raw text), but it adds complexity to emitters since they have to sniff the format/convert to something they can manage or risk broken rendering as shown above.
Challenges/questions:

There are many rich language definitions *in adition to CommonMark), as well as different dialects within a dialect. Is it enough to support just CommonMark?
Client and service library code emitters want to emit descriptions as docstring/comments in generated code. Some langauges (e.g. Python) have idiomatic formats for rich text (in the case of Python, reStructuredText) but most languages expect plain text in their descriptions. Do we expect multiple formats in the specification or do we provide converters?

From the most recent review with the API review board, they weren't a fan of HTML in the docstrings and would prefer something like markdown.

I think the answer here is to just state that @doc/doc comments can support markdown -- we could treat it as a documentation issue.

Implementation issue for beta is just documentation, per Mike's comment and discussion

est: 1, pri: 2


Move labels to i18n resource

The labels are moved to the i18n resources in the both sides (backend and frontend).
Here's some screenshots (on JMeter and on the web) that showing the labels in French :

Hello @reda-idtaleb , is the PR ready ? Can I merge it ? Thanks

Yes I tested it and it's ok.


it can escap from long break if you lock mac then return

enviroment
mac pro 2017 touchbar
stretchly version 0.20.0
decription
i have many time that when i unlock(the shotcut key at touchbar top right) my mac , the long break gone (switch to other desktop).

like this , it's very easy to  reproduce

your breaks are fullscreen, right?
I think it's how macos works: when app is fullscreen, it actually goes to new Desktop. When you lock your screen, and unlock, you are at your default desktop, not the new one created for fullscreen stretchly.

your breaks are fullscreen, right?
I think it's how macos works: when app is fullscreen, it actually goes to new Desktop. When you lock your screen, and unlock, you are at your default desktop, not the new one created for fullscreen stretchly.

you are right

Hi, the new stretchly behavior is that it will finish the break when user locks the computer.


Remove xfail for the multidict issue on rawhide

The issue has been fixed and the fix seems to make it into the rawhide compose.

/packit test -i full

/packit test -i provision


Group Channel/ iOS-Send an admin message to channels

Operators and admins can send admin messages to members in the selected channels. You can edit the default message with a different template message.

As discussed with @chrischabot admin message only possible via API. Hence closing this issue


build: enable rollup tree-shaking

esbuild tree-shake doesn't removes duplicate imports. So enabled rollup tree-shake
blocked by: https://github.com/egoist/tsup/pull/692 merged and released

Codecov Report

Merging #174 (221b3fc) into main (5114f95) will decrease coverage by 0.00%.
The diff coverage is n/a.

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

@@            Coverage Diff             @@
##             main     #174      +/-   ##
==========================================
- Coverage   99.34%   99.34%   -0.01%
==========================================
  Files          56       56
  Lines        3359     3355       -4
  Branches      802      801       -1
==========================================
- Hits         3337     3333       -4
  Misses         13       13
  Partials        9        9

Impacted Files
Coverage Δ

src/validators/BaseValidator.ts
100.00% <0.00%> (ø)

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


Fix the dynamic framework installation examples

\c @jpsim

:+1: I aborted the CI build as it wouldn't check for this anyway.


Source for colors.py script in the first example image?

Hi, this isn't an issue or bug report, but could you please share the script for colors.py in the first example in the README? It seems pretty useful to test my terminal colors..
This is the image I'm referring to:

Also, would you mind sharing your configuration for your prompt (i.e., PS1 stuff)? I like the different color for the username, cwd, Git branch status, etc.

Hi @jasonhan-vassar, of course. Everything you need is in my dotfiles repo. It's basic and a little old now but it does what I like so have had no reason to update it. If you look in prompt.sh you will find that you need.
https://github.com/robinbentley/dotfiles/tree/master/shell
Let me know if you need anything else, if not then please close the issue when you're sorted 👍

Thanks a lot 😁


Installation Failed [BUG]

Installation failed.
Please help me.

Any workarounds?

We're currently addressing a backlog of GitHub issues, and as part of this effort, some inactive issues may be marked as closed. This isn't a dismissal, but a step toward more efficient tracking.
If you feel the issue is still relevant, please re-open and we'll ensure it gets the attention it deserves. Your understanding is appreciated as we work to enhance our open-source responsiveness.


[flutter_conductor] support releasing to multiple channels at once

For example, support the use case of publishing a release to both the dev and beta channels at the same time.

FYI @Yugue


implemented chunk header for inverse intrinsic calibration

there is a new chunk header "INVERSE_INTRINSIC_CALIBRATION" for
the inverse intrinsic calibration. The format is the same as for
intrinsic calibration.

@tpanzarella for me this shall not be an blocker for the 0.11.2 release. Cause the 1.25.xxx fw is not beeing released this year I would expect.

The unit test for this is failing:
[ RUN      ] FrameGrabber.ByteBufferBasics
/home/uspanzto/dev/ifm3d/modules/framegrabber/test/ifm3d-fg-tests.cpp:73: Failure
Value of: std::equal(intrinsic.begin(), intrinsic.end(), zeros.begin())
  Actual: false
Expected: true
[  FAILED  ] FrameGrabber.ByteBufferBasics (0 ms)

The test looks like this:
TEST(FrameGrabber, ByteBufferBasics)
{
  auto buff = std::make_shared<MyBuff>();
  EXPECT_FALSE(buff->Dirty());

  std::vector<float> zeros(ifm3d::NUM_INTRINSIC_PARAM, 0.);
  std::vector<float> extrinsics = buff->Extrinsics();
  std::vector<std::uint32_t> exposures = buff->ExposureTimes();
  std::vector<float> intrinsic = buff->Intrinsics();

  EXPECT_TRUE(std::equal(intrinsic.begin(), intrinsic.end(), zeros.begin()));
  EXPECT_TRUE(std::equal(extrinsics.begin(), extrinsics.end(), zeros.begin()));
  EXPECT_TRUE(std::equal(exposures.begin(), exposures.end(), zeros.begin()));
}

However, this PR has changed how the intrinsics in the ByteBuffer ctor initialization list gets initialized. -- relevant diff.
Specifically, it looks like this:
    intrinsics_({-1.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.,0.}),

The reason for failure is obvious. Also, why was the inverseIntrinsics_ not also added to this test?
Can this failure be addressed in the PR? Also, I will push a dev-0.12.0 to which this should be re-based. Updating the meta-info (ChangeLog, README, software compatibility chart, version number in CMakeLists.txt, etc.) would also be greatly appreciated to the new version number.

Moved the (fixed) PR to dev-0.12.0.
Closing.


cli: Fix service name for Docker processes

The convention APPNAME-web is used for routes by default in the CLI, use that convention when naming the service registration configured for a process type in a release based on a Docker image.
Closes #3097

LGTM

LGTM


[NEW] add contextdesc extractor for hloc

Thanks for the PR. While adding new extractors is much appreciated, I think that we should avoid adding heavy dependencies like TF, and instead keep the package lightweight (we should get rid of OpenCV soon). I also haven't seen a wide adoption of ContextDesc (maybe because it's TF-based), so I will wait to see if there is demand before merging. Thanks for understanding :)

Thanks for your response and the contribution in local feature extraction and matching.
Thanks!

Will not merge. Thanks anyway for the PR!


Add the possibility to globally set tolerations and nodeSelector

Describe the enhancement you'd like to see
Now it is necessary to set tolerations and nodeSelectors for each component (dashboard, api, mongo...) as well as for executors via the job template. It would be cool to have an ability to set it globally for everything to avoid copypaste.

Pushed changes for tolerations and nodeSelectors to develop. @vsukhin could you please update job Templates?

created pr


Calculate BlockId from Tendermint Header

A BCP BlockId for Tendermint-based chains is an uppercase hex representation of a Tendermint block hash.
Since we currently have no way to calculate the block hash from a block header, we need to do an extra request for every event when watching block headers. This is something we want to avoid.
This is how to calculate:

Check the BlockHeader structure
Hash the header
Using cdcEncode and merkle.SimpleHashFromByteSlices
"cbc" mean codec and is implemented by go-amino

This is needed for doing light-client proofs as well as saving the round-trip, so the importance will increase when we start looking to do proofs. Until we have other pieces ready or a burning need, it is too much work for the value IMO

This implementation may provide all we need: https://github.com/mappum/js-tendermint/blob/master/src/hash.js#L45

Link pinned to commit hash: https://github.com/nomic-io/js-tendermint/blob/9b83566/src/hash.js#L19-L39

There is an amino implementation in TypeScript, which might be helpful: https://github.com/node-a-team/ts-amino

@webmaster128 What are the acceptance criteria here? A function exported from @iov/bns that will take a block header and spit out a hash?

What are the acceptance criteria here?

A correct implementation to replace this dummy block:
  public watchBlockHeaders(): Stream<BlockHeader> {
    // TODO: ID unavailable because
    // - we cannot trivially calculate it https://github.com/iov-one/iov-core/issues/618 and
    // - want to avoid an extra query to the node which causes issues when trying to send to a disconnected socket
    // Leave it a dummy as long as no application strictly requires the ID
    const dummyBlockId = "block ID not implemented for Tendermint" as BlockId;

@webmaster128 Our Header type is missing several fields that appear in these implementations, e.g. version. Is that just because we didn't need these fields so far or is there some other reason?

Parsing the Header in the Tendermint client is something that evolved along with the development of Tendermint. We probably had all the fields that were available in the initial version we connected to. But then the parser was only changed when:

We needed to access additional fields
Parsing the existing fields failed
For this reason it is very well possible that the parser is incomplete. Feel free to add the required fields.

If you find it helpful, consider doing https://github.com/iov-one/iov-core/issues/1249 first

Looks like the last change to the header structure was in v0.26 so it should be fine to do this one first.


Helm 3: helm list --date and helm list --reverse aren't working

See https://github.com/helm/helm/pull/5489 for more information.

Is anyone working on this? If not, I can look into this

Nobody's currently working on this. If you feel up to it, go ahead! Do keep in mind that this is for Helm 3 (the dev-v3 branch) rather than Helm 2 (master). If you're comfortable with that then go nuts.

@bacongobbler 👍 thanks! Will checkout that branch

Hey @bacongobbler, what would be expected behavior if both -d and -r options are used?
I’m thinking of having both sortBy and sortOrder, this way reverse would work for both date and release name. What do you think?
Precisely:
helm list (Default case - sort by name Asc)
helm list -r sorts by name Desc
helm list -d  sorts by date Desc (latest release first)
helm list -d -r sorts date Asc (oldest release first)

fixed in #5539


clrVerticalNavCollapsed

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior
I want to use the vertical nav with images. When I open the page I want to start the vertical nav as collapsed. I use (clrVerticalNavCollapsed)]="collapsed"
Actual behavior
What happens is that when I open the page the vertical nav starts unfolded
Reproduction of behavior

Environment details

Angular version: 4.x.x

Clarity version:

OS and version:

Browser: all

@mickeyevers77: Is this what you are looking for? https://stackblitz.com/edit/clarity-light-theme-v11-lvluiy?file=app/app.component.html

thanks! @adityarb88


optimize MPU gap-filling

This is applicable to ARC MPUv3 and ARMv8, whose MPUs do not allow overlapping regions.
Both MPUs implement logic to fill in gaps between user-writable regions with kernel-writable regions, as the "background" MPU setting does not provide access at all.
However, all the gap-filling computation is taking place at context switch time. Even worse, on ARC, the gap-filling mechanism is constantly reprogramming MPU regions for every source region programmed (MPU stack guard, user thread stack, every memory domain partition), and these are MMIO registers, not cacheable memory. This all takes place with interrupts locked, affecting the latency of the system.
We have got to get this logic out of context switching, it does not need to be there. We could add an array of per-thread MPU region settings for every volatile MPU region (i.e. regions change after the system is started.)  to thread.arch. These settings would get re-computed when memory domain parameters change, rather than every context switch. The context switch logic can then be dead simple: just reprogram the volatile MPU regions on context switch with the contents of the array in thread.arch.
If at all possible, it would be great if we could make the gap-filling computation common code, and not implemented for every arch that needs it.

somewhat related task for MMU-based x86: #13003

@ioannisg  it seems this enhancement should be done both on ARC and ARMv8. could I take ARMv8's enhancement ? Thanks.


Test core to network core

[x] I have reviewed the Contributing Guidelines
[x] I agree to license my contributions under the same license as in this repository
[x] I have verified that the tests pass

Description
Merge new test core into the update branch to start collapsing some branches
Proposed changes
adds some more checks for broker init and redo of the test core,  at least a few more of the test are passing now.

I am going to merge this soon as both of these are secondary branches, But @nightlark  and @kdheepak you might take a look as there are some bigger changes to the test core.    I made it look much more like the other core types,  which may mean eventually I can collapse some of the virtual classes.  I have been fighting some of these issues for a while now.


jackal_simulator: 0.3.0-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository jackal_simulator to 0.3.0-1:

upstream repository: https://github.com/jackal/jackal_simulator
release repository: https://github.com/clearpath-gbp/jackal_simulator-release.git
distro file: melodic/distribution.yaml
bloom version: 0.8.0
previous version for package: null

jackal_gazebo
* Add small hack to continue supporting the front_laser:=true arg, since that was prominently documented.
* Change from individual accessory args to a single "config" arg.
* Contributors: Mike Purvis

jackal_simulator

No changes

Holding for melodic sync

This needs a rebase now that I've merged jackal_desktop; mind doing that?  Thanks!


After the newest teslamate update, the vehicle azimuth is no showed, whereas it was before.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
After the newest teslamate update, the vehicle azimuth is not showed on the home screen, whereas it was before.
Before, the vehicle position was shown using an arrow, so you could determine which way the front is pointing.
We know that Tesla API provides it as it's visible on the app, and it was in the v1.25.0, but now, in v1.25.2 it's just a dot :(
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
no relevant output, I think

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v1.25.2

Can you post a screenshot? I don't quite understand what you mean. If your car is not online after a restart of TeslaMate only a blue dot is displayed instead of an arrow. Once the car is online, the direction is known and as a result an arrow can be displayed.

Hah, you're right! Wasn't aware of this. Closing the issue myself.


python 3.6 support for subprocess.run

We use text=True but seems we should use universinal_newlines=True instead for python 3.6. Thanks @tijlk for reporting

From https://docs.python.org/3/library/subprocess.html

Changed in version 3.7: Added the text parameter, as a more understandable alias of universal_newlines. Added the capture_output parameter.


consola logger occasionally repeats previous message

The problem can be encountered during enrichment from the DbPedia knowledge graph. No further investigation has been done as the correctness of the output is not critical.
Actual output
> Fetched N entities for given 100 identifiers.            11:45:45 PM
> Fetched N entities for given 100 identifiers.            11:45:45 PM

Expected output
> Fetched M entities for given 100 identifiers.            11:45:42 PM
> Enriched N from this batch, enriched total X entities.   11:45:42 PM

The implemented stable solution is to prefer winston to consola.


Namespace organization

Move the types in azure-core package based on feedback and discussions with archboard members.
Service Namespaces
Services are under top level Azure::.  Core is grouped as "service" to avoid cluttering the toplevel namespace.
Azure::Storage::....
Azure::Security::...
Azure::Security::KeyVault::...
azure-core is treated as a service for grouping purposes.  The types under Azure::Core are less commonly used types by customers and should be grouped according to their purpose.
Azure::Core::Http
Azure::Core::Cryptography
No non-service top level namespaces allowed
Toplevel namespaces are reserved for services.  This prevents us from using a namespace that could at some point become an azure service.  It also helps with discoverability.  Customers looked for advanced azure-core functionality can begin their search in Azure::Core.
//Valid
Azure::Core::Http
Azure::Core::Cryptography
Azure::Core::Diagnostics
//Invalid
Azure::Http
Azure::Cryptography
Azure::Diagnostics
Azure::Utilities
Detail, Internal, and other namespaces
Detail namespaces
The detail namespace is implementation that is internal to the package (i.e. service).  These are implementation details and can change at any time without notice.
DO NOT expose ::_detail namespace to customers in public headers or return types.  Where possible the _detail namespaces should reside in private headers.
Each package can define _detail namespace(s) as they see fit under one condition.  The _detail namespace must be the last namespace in the namespace chain.
Example:
<service>::<somenamespace>::_detail is valid
<service>::_detail::<somenamespace>:: is invalid
//Top level _detail is NOT allowed
Azure::_detail     //Invalid
//Azure::::::<?_detail>
Azure::Core::_detail
'Azure::Storage::Blobs::_detail 'Azure::Storage::Blobs::Model::_detail
Internal namespaces
The internal namespace in azure-core denotes types that are used by service client libraries.  These types are not intended for use by external customers.  AzureCore reserves the right to break these types at any point in time.
Be consistent with detail and chain _internal at the end.
//Top level internal namespace is NOT allowed
Azure::_internal  //Invalid
Utility and Common namespaces
Packages should avoid Utility (or similarly purposed) namespaces.  These are prone to become grabbag dumping grounds.  Types should instead be placed into the most relevant namespace for the type.  If you are unsure of where a type should reside reach out to the team to discuss.
//Invalid
Azure::Core::Utilities
Types in Azure vs Azure::....

Namespace
Type
Moved
Notes

Azure::

DateTime

ETag

MatchConditions

ModifiedConditions

Response

Azure::Core::

Context

Convert ????

This class has the Base64 Encode/Decode methods

RequestFailedException

Keep this type and Transport Requests derive from it

String

Holds the string helper methods, might want it to be a wrapper over std::string as well

Uuid

Url

Version

This is the package version for Azure::Core, each service should have own "Version type"

Azure::Core::IO

BodyStream

This is very common type should it be toplevel

Azure::Core::Http

TransportException

InvalidHeaderException

HttpStatusCode

HttpMethod

OperationStatus

Range

RawResponse

Azure::Core::Http::Policies

Bettter name ight be Azure::Core::Http::Pipeline

????

Azure::Core::Security

Should this be Azure::Core::Security or Azure::Core::Cryptography or Azure::Security::Core or Azure::Identity or ....

Credentials

Hash

MD5Hash

Azure::Core::Diagnostics

Logging

cc @JeffreyRichter

I support HttpRange renaming. We shouldn't have Method, StatusCode, or Range. The way to reason about this is chances of collision and ease of documentation/discover-ability in SEO. RawResponse is specific enough that it doesn't need Http prefix, that's how I would draw the line.
We should move RequestFailedException to root Azure, and not change things about it, and definitely not use TransportException as a replacement.
Since all our policies and the pipeline are supposed to be internal, we shouldn't have a sub-namespace for these. Leave them at Http::_internal. The base class HttpPolicy can live in Http::
Don't have Azure::Core::Security, keep Azure::Core::Cryptography. And then we need to find a home for Credential, move it/keep it in Azure::Core.

This has been resolved.
@RickWinter the next steps are to update the guidelines with some of the conclusions we reached from this discussion, which I will leave it up to you to decide how to track that change (maybe issue in azure-sdk repo).


No error when reassigning variable in a closure

Flow version: 0.94.0
Expected behavior
Since flow won't know whether the closure is called or not, I would expect the type of a to be string | number
Actual behavior
Type of a is string
Flow try
function myFunc(): string {
  let a = "a string";

  [1].forEach(() => {
    a = 2;
  });

  return a; // a is string
}

Yikes. This is pretty scary. Thanks for pointing this out. I think we have a fix in the works that should be out in one of the next versions.


auto bump chart version when its a renovate pr

renovate PRs that change a values.yaml dont bump the chart version, so the ci fails on linting. this PR targets those PRs, by bumping the version and pushing a change to that PR.
renovate doesn't support bumping chart versions when values.yaml are changed, and the only other solution provided is for the self-hosted which we don't use.
the only weird thing about this change, is that after the commit for bumping the versions, the CI on the PR doesn't show anymore, but it is still running for the original commit from renovate. but it is slightly confusing.
pink is the CI running on the renovate commit.
green is CI being disabled by renovate, because someone else (the github action) pushed a change

@ckavili @eformat since you guys are the core maintainers of this repo. thoughts?
i think its a good idea to have renovate doing its thing, as it can keep things up to date and lower the chances of things becoming out of date/dead. but it obvs, brings other headaches, like this one, along for the ride

yeah it makes sense that Renovate doesn't rebase or discard the changes from the authors other than itself but I wonder if you can make Renovate trust a specific author 🤔  but yeah you are right, it's definitely a good idea to have Renovate doing its thing ❤


document OTEL_PHP_DEBUG_SCOPES_DISABLED

This setting is currently documented only under a specific description for the Context:
https://github.com/open-telemetry/opentelemetry.io/blob/471c572b4acf16f00d2a095983a406240ab3cad8/content/en/docs/languages/php/context.md?plain=1#L141-L143

/fix:format


Using css-modules in meteor package

When using css modules in a package:
myapp/packages/mypackage/package.js
Package.describe({
  name: 'me:mypackage',
});
Package.onUse(function(api) {
  api.versionsFrom('<IP_ADDRESS>');
  api.use('ecmascript');
  api.use('nathantreid:css-modules');

  api.mainModule('mypackage.js');
});

Where is it getting it's package options from? the root project's package.json file? Could it be possible to define different package options such as extensions or ignorePaths that apply only to the package?

The options are pulled from the project's package.json file. The Meteor build process does supply the ability to detect when it is being run in a package, so I'd need introduce a new setting (probably packageOptions: { yourPackage: { someSetting: true; } }.
I'm thinking it would merge your package-specific settings with your global settings so you would only need to specify the settings that are different.
How does that sound?

That sounds great. I assume that would all be in the app's package.json file?
It would be nice to keep config for a package inside of the package itself in case the package is used in multiple apps. Is it possible to stick the packageOptions for a specific package somewhere in the package? perhaps a package.json file or preferably, right in the package.js file?

From what I know of package.js, the answer is no, but handling a package.json file inside the package should be doable.
If no css modules config is found inside the package, should it default to the default options or to the options specified in the app's package.json? I'm currently leaning strongly towards the latter, since all the package author would have to is define the following in order to prevent that:
"cssModules": {}

I thought the package.js would be a reach. package.json is just as good.
I fully agree, I like your idea of merging the two as you mentioned above. I feel it would be excess config to do otherwise, and if it's easy enough to prevent with "cssModules": {} as you mentioned, then it should be totally fine.
Big +1.

I try to make my own package with 'nathantreid:css-modules'.
$ meteor add my:package

 => Errors while adding packages:

While determining active plugins:
error: conflict: two packages included in my:package (nathantreid:css-modules and meteor) are both trying to handle *.css

While determining active plugins:
error: conflict: two packages included in my:package (nathantreid:css-modules and meteor) are both trying to handle *.css

What should I do to use css-modules in own package ?

@hisayan I'll publish the fix for that error later today.

@hisayan you should be good now with v2.2.1.

Thanks. It was solved.

I have a problem.
It is ok that the css file in my own package. thanks.
but the css file in npm_modules in my own package doesn't work well.
This is my simple sample code.
https://github.com/hisayan/rfgtest
$ git clone https://github.com/hisayan/rfgtest.git
$ meteor

it works fine.
but interrupt this process ([ctrl]+c) and restart.
$ meteor

The css file 'flexboxgrid' in node_modules in my package is not load with your css-loader.
The css file is imported as a plane text.
but
$ meteor reset
$ meteor

It works fine.
Is there any mistake in my code ?
or some problem in my environment ?
and I want to use react-flexbox-grid in my own package finally.
https://github.com/roylee0704/react-flexbox-grid

@hisayan I should have time to look at that this weekend.

@hisayan This may be due to the way Meteor is hardcoding CSS support. in npm packages. I'll do some more digging but right now it's not looking too good until Meteor opens up the .css extension.

I appreciate it.
I pick up the CSS file from npm package and use it outside of npm package for now.

Is this related to why this package is not working in Meteor? https://github.com/roylee0704/react-flexbox-grid


unimrcp crash when timer reschedule

unimrcp version: 1.2.0
FreeSWITCH version: 1.8.5
Using unimrcp for mrcp interaction within FreeSWITCH, but it crashed on timer reschedule, here is the bt

line of 228 is:

it looks like the memory address was corrupted.
by the way, we did not modify any code of unimrcp except apt_timers_reschedule which we showed.
any useful advice will be appreciated!

Please note that the latest version of UniMRCP is 1.7.0. I do not recall what was in 1.2.0.
Also, it is not very clear which component actually crashed in this scenario. Is it the client stack running within FS or UniMRCP server. If the latter, then the memory corruption might be caused by the use of a 3-rd party plugin which is loaded into the common address space.


Remove NSOpenGLPFANoRecovery requirement when creating the NSOpenGLContext

As discussed in #5624
This allows users to create a shared context with GLFW, which doesn't have an option for specifying NSOpenGLPFANoRecovery.
Test repo here: https://github.com/jfaust/filament-glfw-share-context

@bejado Wdyt?


Operator v1.6

We will be releasing this today.

Looks good to me. Kindly proceed ahead with publishing.


[SymbolGraph] Add internal/externalParam declaration fragment

These were previously mapped to identifier. Some clients may wish to render
these differently in their declaration blocks.
rdar://61782916

@swift-ci Please smoke test


Event bus: no way to know deployed app when deployment_successful is received

On successful deployment the following event is fired (from docs):
{
  "eventType": "deployment_success",
  "timestamp": "2014-03-01T23:29:30.158Z",
  "id": "867ed450-f6a8-4d33-9b0e-e11c5513990b"
}

More deployment info should be shown here. Otherwise, how to know which app(s) were successfully deployed?

You may want to look for the corresponding id in one of the deployment_info events. That one should hold all of the apps affected in the plan.target fields. Does that help?

Yes, that is what I ended up doing. I would just rather track a single event, instead of multiple ones.

I hear you. I guess the Event Bus is really meant to be used alongside the API endpoints, and not as an "after the fact" log-style tool.
Essentially, if you were also polling the /deployments endpoint, you would get all the info about the affected apps for that specific deployment ID.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-4086. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


Update docs for 1.4.1

@dwightjl can you request re-review after this is updated for rc1?

Rebased to main


pythonPackages.argparse: init at 1.4.0

Motivation for this change
pythonPackages.argparse: init at 1.4.0
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

please see https://github.com/NixOS/nixpkgs/pull/78672
this is part of the standard library, and no longer needed to be packaged


Replace id with name in all APIs

In order to make the API easier to use, I propose to remove the ID as the "access pattern" to the resources and simply use the name as the original delta API.
I also removed lake-sharing tag since was initially though to differentiate delta-sharing vs lake-sharing APIs but now they are in two separate files so it only makes the swagger UI worse to navigate.

Is there a standard / constraints for the resources name attribute, thus enforcing by-design URL-safe formats @tmnd1991 ?
I don't honestly know.
Don't we exclude this way the possibility to change the name of a resource once it's already live?
Nope, patch requests accept a name field in the request, so it can be changed.


Add remaining app fields

This is the companion PR for adding the remaining fields of the app response.
context: https://github.com/google/go-github/issues/851
This PR adds the remaining fields for the app endpoints, specifically adding support for
target
target_type
repository_selection
single_file_name
permissions
events
Tests

I've added unit tests for target(s) field for all the tests
Added a more detailed response test for ListInstallations only (would like feedback if I can follow the same pattern for the remaining tests).

/cc @kshitij10496 @gmlewis

@gmlewis Thanks for review. I think i've addressed all the feedback. Let me know how this is looking. 🙇

Merging.


Deleted projects only appear in recycle bin for user that deleted them

If I add a co-author to a project and then delete it, I can see it in the recycle bin and can no longer edit it. The co-author can still see it in their workspace and can still edit it. Ideally it should also be moved to the recycle bin of everyone it's shared with too (or perhaps just be hidden from their workspace completely)

@FayCross Interesting. I'll have a look.


ci: Add Nx Agents

See here: https://github.com/TanStack/query/pull/6863

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (eb4801c) 87.78% compared to head (d1389b1) 87.78%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #602   +/-   ##
=======================================
  Coverage   87.78%   87.78%
=======================================
  Files          31       31
  Lines         819      819
  Branches      184      184
=======================================
  Hits          719      719
  Misses         95       95
  Partials        5        5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


prs adjustments

In the output score files, when I use the last column of score files  to generate auc (called as : cov-sex-pc-adj), I am getting much better AUC-performance than when I just use PRS only… that sounds like the last column represent the total variation not “the PRS adjusted for cov-sex-pc” . In that case the last term (adj) is not correct in output...it should be called "total variations"
IID	true_phens	PRS	  cov_adj	  pc_adj	  cov_sex_pc_adj
Please let us know about this …
thanks

Thanks for your comment, and I apologize for the slow reply (I was on holidays in April).
You're right, these labels are wrong (or at least misleading).  These are not adjusted prediction, rather total predictions.  I updated the labels to reflect this.
More generally, I currently recommend just importing the PRS into some other software, e.g. R, where you can study the relative importance of PCs, sex, and other covariates with and without the PRS.
Best,
Bjarni


Error: failed to retrieve secret "whatever": entry is not in the password store -> Sould be stderr not stdout

Summary

when gopass show item not with exact name, the output goes to stderr and the error to stdout
Steps To Reproduce

macos@macoss-Mac-mini ~ % gopass show "FAST/2.notes/improvements pass-simple.md"|cat
# Improvements
macos@macoss-Mac-mini ~ % gopass show "FAST/2.notes/improvements pass-simp"|cat

Error: failed to retrieve secret "FAST/2.notes/improvements pass-simp": entry is not in the password store
macos@macoss-Mac-mini ~ % gopass show "FAST/2.notes/improvements pass-simp"
⚠ Entry "FAST/2.notes/improvements pass-simp" not found. Starting search...
✅ Found exact match in "FAST/2.notes/improvements pass-simple.md"
Secret: FAST/2.notes/improvements pass-simple.md

# Improvements

macos@macoss-Mac-mini ~ %

Expected behavior

The stdout should contain the entry content, and stderr all the rest, same as searching successfully with
exact name
Environment

OS: [e.g. Mac OS X High Sierra, Ubuntu 18.04, Windows 10, ...]
OS version: [uname -a]

macos@macoss-Mac-mini ~ % uname -a
Darwin macoss-Mac-mini.local 21.6.0 Darwin Kernel Version 21.6.0: Thu Jul  6 22:18:26 PDT 2023; root:xnu-8<IP_ADDRESS>2.13~1/RELEASE_X86_64 x86_64
macos@macoss-Mac-mini ~ %

gopass Version: [gopass version]

macos@macoss-Mac-mini ~ % gopass version
gopass 1.15.8 go1.21.1 darwin amd64
macos@macoss-Mac-mini ~ %

Installation method: [e.g. from source, brew, gopass repo]

brew install gopass

Additional context

N/A

Errors and Warnings should already go to Stderr but redirecting the other messages that are not part of the secret might require some more tricky changes.
That being said: I think it's a valid request.


Trouble with couchdb

I've hosted my own couchdb. When testing couch with normal http get/put requests it is working fine. When I enter details in nomie I get a message that it connects and asks if I want to store the credentials. I click yes, but when I change tabs away from settings and back to settings again my couchdb settings are blank. No data are sent to my couchdb server. Any ideas?

I think I've managed to locate the issue. When starting with a fresh instance of nomie, and you fill in the couchdb settings in settings, the settings will not be properly stored in the browser local storage. To be more precise, after the couchdb settings are verified, the credentials are successfully stored in the local storage, but are overwritten moments after. After what I can gather: the saveRemote() function in pouchdb.svelte parses and saves the couchdb settings to the local browser storage, but when the sync is started moments after the startSync() method overwrites the couchdb config in local storage with the object state.remote. At this moment in time, the state.remote object has not been updated with the new couchdb settings, and therefore the valid couchdb config will be overwritten. I found that adding the line state.remote = remote; at the end of the saveRemote() function solves the issue.
I have suggested this as a hotfix in pouchdb.svelte. Honestly I'm not familiar with svelte or npm, so I will leave it to some of your more capable hands to evaluate if this is an appropriate fix for this issue.

in case anyone else runs into this too, i worked around this by manually setting the CouchDB credentials in the localStorage API. i have an iphone + macbook, and i followed these steps:

connected my phone to my macbook and open up nomie on my phone
viewed nomie using Safari Devtools on my macbook (https://support.apple.com/guide/safari/use-the-developer-tools-in-the-develop-menu-sfri20948/mac)
ran the following code in the dev tools console

var dbDetails = localStorage.getItem('n4/storage/pouchdb-remote')
dbDetails = JSON.parse(dbDetails)
dbDetails.url = {YOUR-COUCHDB-URL}
dbDetails.username = {DB-USERNAME}
dbDetails.password = {DB-PASSWORD}
dbDetails.database = {DB-DATABASE-NAME}
localStorage.setItem('n4/storage/pouchdb-remote', JSON.stringify(dbDetails);


Add protected branch name description

I was unable to create a backport for 1.21. @lunny, please send one manually. :tea:
go run ./contrib/backport 27257
...  // fix git conflicts if any
go run ./contrib/backport --continue


Code for disabling SSLv3 in OpenVPN yaml file to avoid SOC Vulnerabilities

Added an extra configuration in User Data to disable SSLv3 and enable TLSv1.2 for OpenVPN Web Server. This will avoid poodle attacks and take care of SOC Vulnerabilities related to OpenVPN Server

Thanks @ranaskr please can you rebase?

@RobertNorthard  - Is there a need to rebase? My PR from this forked repo is 1 commit ahead of master branch of this repo. Shouldn't it be a simple merge?


Add ScandiPWA theme link

Hi @Danpiel, thank you for your contribution. Merged.

Awesome, thank you.


Add a link to the workaround for SSO with GHE

While a more permanent solution is being developed, link to the
workaround so that people can continue to use hub in their GHE
environments.
Related-Bug: #826
Related-Bug: #384

This would be great to have added officially to the docs. I just had to reference this and it was a great find.


Suggestions don't appear if the option has trailing whitespace

Context
We have an input:
<%= render DfE::Autocomplete::View.new(
        f,
        attribute_name: :organisation_id,
        form_field: f.govuk_collection_select(:organisation_id, Organisation.order(:slug), :id, :name,
                                              options: { prompt: "Select an organisation" })
      ) %>

Where Organisation.order(:slug) returns a list of objects:
[#<Organisation:0x000000010f9de760
  id: 1,
  slug: "government-digital-service",
  name: "Government Digital Service">,
 #<Organisation:0x000000010f9de620
  id: 2,
  slug: "department-for-testing",
  name: "Department For Testing">,
  ...
]

We fetch these from an API, so we don't have any direct control over them. In at least one case the name has a trailing space:
#<Organisation:0x000000010f9de770
  id: 3,
  slug: "department-of-punctuation",
  name: "Department of Punctuation ">

Expected behaviour
When the user types department, they should see suggestions for Department For Testing and Department of Punctuation .
When the user types department of, they should see a suggestion for Department of Punctuation  and a hint completing their query to 'Department of Punctuation '
Current behaviour
When the user types department, they see a suggestion for Department For Testing but no Department of Punctuation .
When the user types department of, they get no results, but there is a hint completing their query to 'Department of Punctuation '.
Possible cause
I think this is happening because the suggestion function checks the suggested value against the option's name:
https://github.com/DFE-Digital/dfe-autocomplete/blob/11738c0e25778162e26eb7ab5e22a6ffce671b08/src/dfe-autocomplete.js#L15
where name is derived from option.label: https://github.com/DFE-Digital/dfe-autocomplete/blob/11738c0e25778162e26eb7ab5e22a6ffce671b08/src/dfe-autocomplete.js#L26
In the console it looks like option.label strips the whitespace. So the suggestion still has the whitespace intact, but the option name doesn't, so o.name === value returns false and no option is found.

I think the easiest option would be to trim the whitespace in the comparison: const option = options.find(o => o.name === value.trim()).
Another, possibly safer, option would be to use the option's textContent/innerText in the comparison instead of or in addition to using label, since this doesn't appear to automatically trimmed, and it matches what the accessible-autocomplete uses when reading the select options:
https://github.com/alphagov/accessible-autocomplete/blob/3906cdc2c885d7608c0f2da66cce736be111cdde/src/wrapper.js#L34


No devices showing

Describe the bug
No devices are being displayed:

To reproduce
Steps to reproduce the behavior:

Go to 'Devices & Services'
Click on 'Eufy Security'
See Missing Devices

Expected behavior
I have 3 eufy cameras and a doorbell yet none of them are showing.
Additional information
Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields;

Home Assistant Installation Type (OS - Supvervised - Core):
Home Assistant Core Version:
Eufy Security Add-on Version:
Eufy Security Integration Version:

Hardware Information;

Camera Model:
EufyCam 2C Pro
Eufy Doorbell 2K HD Battery-Powered

Live Streaming Protocol (RTSP/P2P):
RTSP

Debug Logs from Home Assistant (https://github.com/fuatakgun/eufy_security/discussions/624) - Without this, I will automatically resolve this issue

This error originated from a custom integration.
Logger: homeassistant
Source: custom_components/eufy_security/eufy_security_api/api_client.py:305
Integration: Eufy Security (documentation, issues)
First occurred: 16:06:51 (1 occurrences)
Last logged: 16:06:51
Error doing job: Exception in callback WebSocketClient._on_close( result=None>)
Traceback (most recent call last):
File "/usr/local/lib/python3.11/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/eufy_security/eufy_security_api/web_socket_client.py", line 80, in _on_close
self.close_callback(future)
File "/config/custom_components/eufy_security/eufy_security_api/api_client.py", line 305, in _on_close
self._on_error_callback(future)
TypeError: 'NoneType' object is not callable

Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):
2023-08-22 14:55:48.237  INFO  Eufy Security server listening on host <IP_ADDRESS>, port 3000
2023-08-22 14:55:50.754  INFO  No stations found.
2023-08-22 14:55:51.147  INFO  No devices found.
2023-08-22 14:55:54.472  INFO  Push notification connection successfully established
2023-08-22 14:57:52.912  INFO  Client disconnected with ip: <IP_ADDRESS> port: 53918 code: 1000 reason: Normal Closure
2023-08-22 14:57:57.448  INFO  Client disconnected with ip: <IP_ADDRESS> port: 53922 code: 1000 reason: Normal Closure
2023-08-22 15:02:10.684  INFO  Client disconnected with ip: <IP_ADDRESS> port: 53926 code: 1006 reason: Abnormal Closure
2023-08-22 15:05:52.926  INFO  No stations found.
2023-08-22 15:05:53.446  INFO  No devices found.
2023-08-22 15:06:47.811  INFO  Client disconnected with ip: <IP_ADDRESS> port: 58026 code: 1000 reason: Normal Closure
2023-08-22 15:06:51.083  INFO  Client disconnected with ip: <IP_ADDRESS> port: 40048 code: 1000 reason: Normal Closure

Would you share your device with me in case further debugging required? (Yes/No):
No

Additional context
I am running the eufy-security-ws as a container in docker compose with the following config:
eufy-security-ws:
container_name: eufy-security
image: bropat/eufy-security-ws:latest
network_mode: "host"
restart: always
environment:
-<EMAIL_ADDRESS>- PASSWORD=***
- PORT=3000
volumes:
- /data/eufy-security-ws:/data

It turns out I had forgotten to pass the country to eufy-security-ws in my docker config. It now works.


support include!("library.rs") in extern

Motivation
I'm generating bindings for a library, but they are not perfect and I need to add some manual definitions. I do not want to edit the generated file.
Proposed Solution
#[wasm_bindgen(module = "mylibrary")]
extern "C" {
    include!("mylibrary_generated.rs");
}

Alternatives
Allow the module to be split up in more than one extern. This doesn't work today:
#[wasm_bindgen(module = "mylibrary")]
extern "C" {
}

#[wasm_bindgen(module = "mylibrary")]
extern "C" {
}

Another alternative is for me to add the include! type functionality to my generator, but I prefer the above solutions.

Implementing this would unfortunately be somewhat nontrivial, it's basically interpreting a rustc-builtin macro. Can you say more, though, as to why the second form doens't work?

Upon further review, the alternative is working just fine. I thought it was causing an error, but I just tried a simpler example and no error.


Different board for blog content

@merelcht suggested that we have issues (not really "issues", but pending tasks) related to blog posts appear in a different board.
To be completed.

So raise them here on kedro-devrel as issues but enter them into a different project board to track them?
Or have a different repo?

I created https://github.com/orgs/kedro-org/projects/6/ but only org owners can make it public.

Done!


Fix Bokeh QuadMesh example

I've updated the index of the Bokeh Elements tutorial to indicate it's supported. Additionally I'm now raising an SkipRendering error for non-rectangular QuadMeshes which are not yet supported.

Ready to merge.


add self.config default item in remove function

Before this change I could not remove the current buffer from the harpoon list using the list():remove()

very interesting!!! removing the current buffer by calling empty remove.  I love the idea.  i am a bit worried about calling add in the remove  function
i may break this later :)  but i will replace it with a specific method.
or i may rename add to create_list_item which is probably the right move here


xNetBIOS: InterfaceAlias not working properly

I'm having a problem enabling netBIOS. My file is like it:
xNetBIOS EnableNetBIOS
{
InterfaceAlias = 'ethernet0'
Setting        = 'Enable'
}
When I use InterfaceAlias as "Ethernet0" it returns the error: System.InvalidOperationException: Interface 'ethernet0' was not found.
To find InterfaceAlias, I am doing the PS query:
Get-NetIPAddress | where IPAddress -eq "..." | fl interfaceAlias
and it returns:
interfaceAlias : Ethernet0
I am using the correct name.
When I query "Get-NetAdapter | fl Name,InterfaceDescription" it returns:
Name                        : Ethernet0
InterfaceDescription : Intel(R) 82574L Gigabit Network Connection
Then Im trying
xNetBIOS EnableNetBIOS
{
InterfaceAlias = 'Intel(R) 82574L Gigabit Network Connection'
Setting        = 'Enable'
}
and it changes well. I think InterfaceAlias is not suppose to be it. Going further in my investigation I opened the file "MSFT_xNetBIOS.psm1" and go to "function Test-TargetResource" (line 190) to find what it is doing. At line 208 have it:
$netAdapter = Get-CimInstance         -ClassName Win32_NetworkAdapter
-Filter ('Name="{0}"' -f $InterfaceAlias)
then I query "Get-CimInstance -ClassName Win32_NetworkAdapter | select name" and none of them is "Ethernet0", so looking for "ethernet0" I found it at NetConnectionID:
NetConnectionID             : Ethernet0
query: Get-CimInstance -ClassName Win32_NetworkAdapter | select NetConnectionID
All my nodes are running Powershell 5.1 and i'm using xNetworking 5.5.0 (master branch I guess)
PS
Major  Minor  Build  Revision

5      1      14393  693
xNetworking
Version    Name

<IP_ADDRESS>    xNetworking

Hi @aalmeida89 - it looks like a change was made in the last release that broke this. I'll get this fixed ASAP. It should still work fine in <IP_ADDRESS>. Thanks for raising this.

Thanks a lot =).

Fix available in <IP_ADDRESS> (not <IP_ADDRESS> as stated in the changelog !)

You could fix the change log in this repo, but don't think we can (read have time) to resolve the release notes in PowerShell Gallery. I have no permission there.
You could add a note in next release's change log (under the Unreleased section) mentioning the mistake too?

Thanks @johlju - I think you're right and going back and changing past packages is a no-no in general. So I'll just submit a PR to correct the CHANGELOG.MD.


Enable manual data extension registration.

Is your feature request an entirely new concept?
Not entirely a new concept. This currently happens automatically when modules are dropped in the plugin folder. This will enable an extension to be manually registered without being in a certain folder.
Is your feature request related to an existing component?
Yes? There are extension discovery/repository component.
Is your feature request related to a problem? Please describe.
Not a problem per se... it just allows developers to easily extend a data source plugin in an executable, for example.
Additional context
We'd have to consider how this works when plugin isolation is used.

This is for developers writing an executable based on the SDK.Engine and would like to add a quick-n-dirty extension without worrying about dropping binaries into a specific folder. Just being able to add it to the executable and have it registered is a time-saver.


Added data.testCases to EiffelTestSuiteStartedEvent

As per #120

I don't agree with the common data properties thing, for the same reasons as in #128. Other than that I'm ok with this.

Should this be closed?

This PR can be closed. The reason for implementing it has more or less disappeared since EiffelTestCaseTriggeredEvent was introduced.


Merge commit for #13347

Pull in commits from #13347 so merge-to-develop succeeds there.

!ci-build-me


Duplicate streets and cities in drop-down [2.0 beta]

Random example - same happens for the street as well. In iD 1.9.7 there are no duplicates. FF 49.0.2, Win10 if that helps.

Thanks, I'm working on a fix for this now.  I also noticed the Postcode field has some issues.


pull request for e2e test at 12/21/2016 18:45:22

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


Specify Project for Vikunja iFrame

Thanks for this project. I have been enjoying using the Vikunja iFrame inside of Homarr.
I looked over the documentation to see if there is a way to have it only show tasks from a single project. Did I miss something along the way?
I appreciate your time!

Hi, there was no option to show tasks from a specific project, but I release a new version where you can filter by project ID. You can check the API docs to see how.

This is awesome! Thank you for your help!


DBZ-140 when locking individual tables, use a single statement with …

…all the table names instead of issuing a statement per table which causes a MySQL error

Any chance of getting this released soon? This seems to be a blocker for RDS users.

Should be later this week.


Drop cuda_compiler_version selectors

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12564356691. Examine the logs at this URL for more detail.

@conda-forge-admin, please rerender
(Just to make sure I am not missing something).

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12564378626. Examine the logs at this URL for more detail.


Yocto (non-IDP) builds are broken

I built for WR Linux 9 and got the following warning:
WARNING: No recipes available for:
/buildarea1/jkeffer/meta-device-cloud/recipes-initramfs/ramfs-init/ramfs-init_1.0.bbappend
In the recipe file, it exits for non-IDP builds. When I build the image, the files I would expect to find in sysroots are not there. It doesn't look like there are any device cloud files in the image.

Fixed here c8b81c1cd03b695651ff7977f349aad547fc7ff1


fix(fluid-build): Fix failures when deleting files

We use the git ls-files command to enumerate files to work on in various places within the build-tools code. Upon investigation, I determined that unstaged, deleted files are returned by our git ls-files usage. This causes failures since most code is expecting all the paths returned to exist, and they throw exceptions when they hit those deleted paths.
If the deleted file is staged, then git correctly excludes it - this inconsistency has led to a lot of confusing behavior for devs, where things behave differently based on the state of the stage and working directory.
Unfortunately I cannot find a git command that returns all the files we want it to, and none of the ones we don't. So in this change, I updated the places where we call ls-files to check if the file exists, and if not, exclude the path.
I have confirmed this fixes the Biome task caching, which was what I set out to fix. It may also fix some related issues with staged files and policy-check, since policy does use ls-files to enumerate the files to check. However, I didn't have a good repro of that issue, so I can't say for certain it's fixed.
I also noticed that some of the uses were checking if the path was a file - that's guaranteed already. git will not return paths to directories - it tracks files only. So I removed that code.
There is still code duplication - build-tools and build-cli both have their own git wrappers. Long term we should converge but I think that's part of the overall "split build-tools into better packages" work.
AB#10257

I had reported the related AB#6588, which according to my notes also showed issues with staged deleted files. In case that scenario prompts any additional checks or ideas.

I had reported the related AB#6588, which according to my notes also showed issues with staged deleted files. In case that scenario prompts any additional checks or ideas.

I sent that to Tyler earlier today :)

Sure it isn't better to get the status of all of the files and then parse that excluding deleted things?
At least let's not do broad synchronous existence checking - suggestion below.

Yeah, I could use git status --porcelain and just parse everything. I'll look into that.

Sure it isn't better to get the status of all of the files and then parse that excluding deleted things?
At least let's not do broad synchronous existence checking - suggestion below.

Yeah, I could use git status --porcelain and just parse everything. I'll look into that.

Looked into this and I had misremembered how flexible git status is. I don't think it can list committed files - only those with edits in the working tree or stage. SO I'm back to thinking this is the best I can do right now. My original attempt used an ignore-aware glob lib to enum files instead of git, but that lib had a problem where it won't look up the tree for ignore files to respect, so I had to do weird gymnastics. the approach in this PR may be slower or less efficient, but the code is easier to understand.
One option I thought of is to make the getFiles function a generator, but I didn't pursue it. Not sure it would be a win, and that can be done as a follow up if it is.

I am still concerned about checking existence of every file in the repo. Maybe we temporarily add performance output for that step. Just emit how long it takes to verify file existence?
If there isn't one command that gets everything, are there two?
So, you get the list with too many files, then query for deleted unstaged files (since that is the problem identified). Then remove those deleted unstaged files from the list. Won't even need to do an absolute path calculation.
Could keep the existing existence check as a debug option to make sure we are getting the right result.

If there isn't one command that gets everything, are there two?

Yes. Updated to use git status to enumerate only deleted files, then remove those from the ls-files results. All stat checks are gone. I used policy-check to do a perf comparison of the old code vs. code in this iteration (with the extra status check). Perf is comparable.

:) Small discrepancy where one of two issues queries in parallel and the other does sequential. But since there is a plan to resolve duplication later no worries.

Good catch. Not going to mess with it now since consolidation is the plan, as you noted.


Create SnP500AI.py

#83 The main.py script handles the training and analysis of a machine learning model for predicting S&P 500 index values using the ExplainableAI package.
It first loads the mock S&P 500 data generated from a CSV file (mock_snp500_data.csv) and splits the data into training and testing sets. The script then initializes the XAIWrapper and fits a Random Forest Regressor model on the training data. Once the model is trained, it analyzes the model's performance using ExplainableAI, providing insights such as feature importance and model behavior, and prints a LLM-powered explanation of the results. Additionally, it generates a professional PDF report (snp500_analysis_report.pdf) summarizing the analysis. Finally, it demonstrates explainability for individual predictions by selecting a sample from the test set, making a prediction, and providing an explanation for the prediction. The script automates model training, analysis, and interpretability using advanced explainable AI techniques.

For #83

hey @SIDDHARTH1-1CHAUHAN any update? Please do required small fixes, I'm looking to merge this PR

Yes sir , will do , was busy with something , extremely sorry
On Mon, 14 Oct, 2024, 12:47 Om Bhojane, @.***> wrote:

hey @SIDDHARTH1-1CHAUHAN https://github.com/SIDDHARTH1-1CHAUHAN any
update? Please do required small fixes, I'm looking to merge this PR
—
Reply to this email directly, view it on GitHub
https://github.com/ombhojane/explainableai/pull/92#issuecomment-2410239254,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHUM4GE23YFOV6SRFLG5NNLZ3NVX7AVCNFSM6AAAAABPXMPJZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGIZTSMRVGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Nvm, please do requested changes


The headers on the color list aren't close to the colors they relate to.

Notice how "Teals" is close to the list of aqua colors:

On: https://varnish.allenai.org/material-ui/varnish/colors/

@jonborchardt I'm assigning this to you for triage. LMK if there's another way :)


Fix template embedding on windows

What does this PR do?
https://github.com/DataDog/datadog-agent/pull/4782 broke the agent status command on windows because of the \ vs / convention.
Motivation
Fix a regression introduce by PR #4782
Additional Notes
N/A

I tested on Windows 10 / Linux / Macosx, will also test the package.


Cleanup the MultiDictionary Interface

Clean up subscripting so accessing one-past-the-end indices is no longer possible
Make the interface for Multidictionary more closely align to either Dictionary or Set
Document everything

This PR should be NFC, but we'll see if anything was relying on the old subscript order.

@swift-ci test

@davidungar A quick question: The old interface is not consistent about its removal-based operations erasing keys when there are no associated values remaining. What's the intended behavior here?

⛵

@davidungar A quick question: The old interface is not consistent about its removal-based operations erasing keys when there are no associated values remaining. What's the intended behavior here?

Good question--not something I have thought about. Looking at how it is used, I think my expectation was that removing a non-existent key would be a noop.


Add handle_tick callback to vnode

In my riak_core based project I need a mechanism to periodically revisit state of my vnode.
My first approach was to send a tick using erlang:send_after/3, to handle a message in MyVnode:handle_info/2 and to resend a tick.
The problem with this problem was that, because MyTickInterval < 2 * inactivity_timeout, vnode never had a chance to send inactive event to riak_core_vnode_manager, thus manager never had a chance to trigger handoff. Because handoff was blocked, one behaviour that I observed was node hanging during cluster leave riak_core:leave().
My second approach was that I will add another callback to vnode handoff_ready/1, so vnode could cancel a tick and pretend to be "inactive". The best place I could find to do that was riak_core_vnode_manager:update_handoff/4. Unfortunately this function is called periodically when manager receives management_tick. So I went back to square one, as calling handoff_ready callback was causing cancellation of inactivity timer in vnode.
My third approach (presented in this PR):

gen_fsm builtin timeout mechanism is replaced by manual calls of riak_core_vnode:start_inactivity_timer/1,2 and riak_core_vnode:stop_inactivity_timer/1;
MyVnode:init/2 can return new option, which is {tick, TickInterval::non_neg_integer()}
when tick option is present, then new callback: MyVnode:handle_tick/1 also needs to be present. This callback is called every TickInterval ms.
MyVnode:handle_tick/1 callback can return three different values:

{ok, NewState::term()} - updates modstate
{ok, NewState::term(), NewTickInterval::non_neg_integer()} - updates modstate and tick_interval
{cancel, NewState::term()} - cancels tick

Because I do not have an access to quickcheck I could not run test/core_vnode_eqc.erl tests. I think that a minimum regression test would be to turn on tick in test/mock_vnode.erl and expect all cases to pass. Could you confirm that (so I could attach test/mock_vnode.erl changes)?
Further improvements:

API to reinstate tick (after it was cancelled or it wasn't defined at `MyVnode:init/1' options)
API to manually send tick message (if someone wants to ping vnode from outside)
adjust tick message? $tick?

:+1: This would simplify some periodic vnode tasks in the riak_core based project i'm leading too.


Suppress CodeQL alerts for generated code

Adds CodeQL suppressions for some issues that are being alerted upon from the aspnetapp sample. This code comes from the project template. I checked with the latest templates from Visual Studio and they have the same code as we have currently.

Theoretically .NET Framework is getting these same alerts in its source code. Should we file a follow-up issue to remove this if that is ever fixed? It may also be unlikely to be fixed.

Theoretically .NET Framework is getting these same alerts in its source code. Should we file a follow-up issue to remove this if that is ever fixed? It may also be unlikely to be fixed.

That would happen naturally whenever we update samples. We'd just copy over our existing files with the new content.


Revert "render infinite or NaN relevance as "0.0""

Reverts vespa-engine/vespa#3285
After a second thought and a quick look at factory I think we need to do this in the backend and only do it for 'unranked' case.
@arnej27959 and @havardpe

Is this because the tests that want to check for NaN via -inf now end up with 0.0 instead?
Doing this in the back-end might help a bit, but we still end up with inability to test whether we get -inf due to NaN rank or no rank.
If we do something in the back-end, I suggest detecting constant rank values as a start. We can then stop special casing the 'unranked' profile down the line, and we can even consider adding a default rank value to the ranking profile at some point.
However, even if strtod parses '-Infinity' correctly, it is not legal json. This means that simply reverting this pull request will result in producing invalid json. The more reasonable value for json would probably be 'null'. XML can probably use '-Infinity' if it wants, since it is a string and not a number.

we now give results 0.0 rank values when doing unranked matching (back-end):
https://github.com/vespa-engine/vespa/pull/3309
The const-detected/configured default values were a no-go due to post second-phase-ranking first-phase-ranking value value-range-adjustment complexities.


Date time range selection implementation for Angular

From #1952
Implementation of the Date time range selection component for Angular

@cal-smith  Can we start the design review on this component ?

@Najil-K sure! The one area I know we really diverge is in the absolute picker:

For UX reasons I think we'll end up shipping that kind of interaction.

@cal-smith Could you drop the latest dev instance link here?

They're in the comments from the netlify bot in the PR (#2365) 👍 but, this is the angular one for that PR (it'll update when the PR updates): https://deploy-preview-2365--ai-apps-pal-angular.netlify.app