Router Template

Has anyone used the 3d printed router Template for the I strumebt bezel?
I am curious how it's used.

If a 'strumebt bezel' is a bezel that accommodates one or more encoders, then the template is used with a router and a 'flush' bit to remove the material (wood, plastic) to make space to install an encoder. I've used it to install encoders required in a C172 open cockpit which I completed last year. Without Allen's printed 3D files for printing the bezels, I think I'd still be trying to learn 3D software rather than building the cockpit.

That's beautiful what you have built and thank you for the reply.
I will certainly be printing all the bezels and understand what a router
template "should" be used for, but cannot see how the printed router
template supplied, was to be used.
Sorry if I'm sounding so dumb, but maybe I will just need to print it and
try to figure it out.
Thanks again for the reply.
JT
On Tue., Jun. 2, 2020, 10:41 a.m. JJMalette<EMAIL_ADDRESS>wrote:

If a 'strumebt bezel' is a bezel that accommodates one or more encoders,
then the template is used with a router and a 'flush' bit to remove the
material (wood, plastic) to make space to install an encoder. I've used it
to install encoders required in a C172 open cockpit which I completed last
year. Without Allen's printed 3D files for printing the bezels, I think I'd
still be trying to learn 3D software rather than building the cockpit.
[image: DSC_0017 MODIFIED]
https://user-images.githubusercontent.com/42695696/83533311-6e07ca80-a4bd-11ea-9d2b-77fce2aeda2f.JPG
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/allanglen/c172-flight-sim-panel/issues/15#issuecomment-637587147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNPQ7UWEBWRBOKWZKS4FJDRUUFPZANCNFSM4NP5E43Q
.

Hi JT,
Within the next couple of days, I’ll send you one or more pictures that will hopefully give you a hint or two! Please be patient, I’m undergoing chemotherapy treatments which cause me to be useless on some days. I have cancer of the bladder which many people have had and are today near top-shape. I remain positive and keep busy with fliightsim projects including helping others realize their dream.
All the best, JJ
From: JTRACKER
Sent: Tuesday, June 2, 2020 11:12 AM
To: allanglen/c172-flight-sim-panel
Cc: JJMalette ; Comment
Subject: Re: [allanglen/c172-flight-sim-panel] Router Template (#15)
That's beautiful what you have built and thank you for the reply.
I will certainly be printing all the bezels and understand what a router
template "should" be used for, but cannot see how the printed router
template supplied, was to be used.
Sorry if I'm sounding so dumb, but maybe I will just need to print it and
try to figure it out.
Thanks again for the reply.
JT
On Tue., Jun. 2, 2020, 10:41 a.m. JJMalette<EMAIL_ADDRESS>wrote:

If a 'strumebt bezel' is a bezel that accommodates one or more encoders,
then the template is used with a router and a 'flush' bit to remove the
material (wood, plastic) to make space to install an encoder. I've used it
to install encoders required in a C172 open cockpit which I completed last
year. Without Allen's printed 3D files for printing the bezels, I think I'd
still be trying to learn 3D software rather than building the cockpit.
[image: DSC_0017 MODIFIED]
https://user-images.githubusercontent.com/42695696/83533311-6e07ca80-a4bd-11ea-9d2b-77fce2aeda2f.JPG
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/allanglen/c172-flight-sim-panel/issues/15#issuecomment-637587147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNPQ7UWEBWRBOKWZKS4FJDRUUFPZANCNFSM4NP5E43Q
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I would prefer you rest and get well.  My sister went through years of
chemo and am familiar with the exercise and difficulties of cancer - from
the observer side.
Please take care of yourself and don't worry about my inquiry.
JT
On Tue, Jun 2, 2020 at 11:25 AM JJMalette<EMAIL_ADDRESS>wrote:

Hi JT,
Within the next couple of days, I’ll send you one or more pictures that
will hopefully give you a hint or two! Please be patient, I’m undergoing
chemotherapy treatments which cause me to be useless on some days. I have
cancer of the bladder which many people have had and are today near
top-shape. I remain positive and keep busy with fliightsim projects
including helping others realize their dream.
All the best, JJ
From: JTRACKER
Sent: Tuesday, June 2, 2020 11:12 AM
To: allanglen/c172-flight-sim-panel
Cc: JJMalette ; Comment
Subject: Re: [allanglen/c172-flight-sim-panel] Router Template (#15)
That's beautiful what you have built and thank you for the reply.
I will certainly be printing all the bezels and understand what a router
template "should" be used for, but cannot see how the printed router
template supplied, was to be used.
Sorry if I'm sounding so dumb, but maybe I will just need to print it and
try to figure it out.
Thanks again for the reply.
JT
On Tue., Jun. 2, 2020, 10:41 a.m. JJMalette<EMAIL_ADDRESS>wrote:

If a 'strumebt bezel' is a bezel that accommodates one or more encoders,
then the template is used with a router and a 'flush' bit to remove the
material (wood, plastic) to make space to install an encoder. I've used
it
to install encoders required in a C172 open cockpit which I completed
last
year. Without Allen's printed 3D files for printing the bezels, I think
I'd
still be trying to learn 3D software rather than building the cockpit.
[image: DSC_0017 MODIFIED]
<
https://user-images.githubusercontent.com/42695696/83533311-6e07ca80-a4bd-11ea-9d2b-77fce2aeda2f.JPG
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/allanglen/c172-flight-sim-panel/issues/15#issuecomment-637587147
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ABNPQ7UWEBWRBOKWZKS4FJDRUUFPZANCNFSM4NP5E43Q
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/allanglen/c172-flight-sim-panel/issues/15#issuecomment-637615379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNPQ7VK6DBG5QUMNW6RUVDRUUKVPANCNFSM4NP5E43Q
.
[image: image.gif]

You’re very kind JT. But luckily I do have good days and it’s on those days that I enjoy life by engaging in worthwhile things for me and others.
Sent from Mail for Windows 10
From: JTRACKER
Sent: June 2, 2020 12:49 PM
To: allanglen/c172-flight-sim-panel
Cc: JJMalette; Comment
Subject: Re: [allanglen/c172-flight-sim-panel] Router Template (#15)
I would prefer you rest and get well. My sister went through years of
chemo and am familiar with the exercise and difficulties of cancer - from
the observer side.
Please take care of yourself and don't worry about my inquiry.
JT
On Tue, Jun 2, 2020 at 11:25 AM JJMalette<EMAIL_ADDRESS>wrote:

Hi JT,
Within the next couple of days, I’ll send you one or more pictures that
will hopefully give you a hint or two! Please be patient, I’m undergoing
chemotherapy treatments which cause me to be useless on some days. I have
cancer of the bladder which many people have had and are today near
top-shape. I remain positive and keep busy with fliightsim projects
including helping others realize their dream.
All the best, JJ
From: JTRACKER
Sent: Tuesday, June 2, 2020 11:12 AM
To: allanglen/c172-flight-sim-panel
Cc: JJMalette ; Comment
Subject: Re: [allanglen/c172-flight-sim-panel] Router Template (#15)
That's beautiful what you have built and thank you for the reply.
I will certainly be printing all the bezels and understand what a router
template "should" be used for, but cannot see how the printed router
template supplied, was to be used.
Sorry if I'm sounding so dumb, but maybe I will just need to print it and
try to figure it out.
Thanks again for the reply.
JT
On Tue., Jun. 2, 2020, 10:41 a.m. JJMalette<EMAIL_ADDRESS>wrote:

If a 'strumebt bezel' is a bezel that accommodates one or more encoders,
then the template is used with a router and a 'flush' bit to remove the
material (wood, plastic) to make space to install an encoder. I've used
it
to install encoders required in a C172 open cockpit which I completed
last
year. Without Allen's printed 3D files for printing the bezels, I think
I'd
still be trying to learn 3D software rather than building the cockpit.
[image: DSC_0017 MODIFIED]
<
https://user-images.githubusercontent.com/42695696/83533311-6e07ca80-a4bd-11ea-9d2b-77fce2aeda2f.JPG
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/allanglen/c172-flight-sim-panel/issues/15#issuecomment-637587147
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ABNPQ7UWEBWRBOKWZKS4FJDRUUFPZANCNFSM4NP5E43Q
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/allanglen/c172-flight-sim-panel/issues/15#issuecomment-637615379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNPQ7VK6DBG5QUMNW6RUVDRUUKVPANCNFSM4NP5E43Q
.
[image: image.gif]

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Good Day Sir,
How is life treating you and how are you managing your treatment?  I hope
things are doing well and the chemo is not giving too many terrible side
effects.
Hopefully you will be able to get back to normal as soon as possible.
Regards,
Jeff Thompson
On Tue, Jun 2, 2020 at 12:48 PM Jeffrey Thompson<EMAIL_ADDRESS>wrote:

I would prefer you rest and get well.  My sister went through years of
chemo and am familiar with the exercise and difficulties of cancer - from
the observer side.
Please take care of yourself and don't worry about my inquiry.
JT
On Tue, Jun 2, 2020 at 11:25 AM JJMalette<EMAIL_ADDRESS>wrote:

Hi JT,
Within the next couple of days, I’ll send you one or more pictures that
will hopefully give you a hint or two! Please be patient, I’m undergoing
chemotherapy treatments which cause me to be useless on some days. I have
cancer of the bladder which many people have had and are today near
top-shape. I remain positive and keep busy with fliightsim projects
including helping others realize their dream.
All the best, JJ
From: JTRACKER
Sent: Tuesday, June 2, 2020 11:12 AM
To: allanglen/c172-flight-sim-panel
Cc: JJMalette ; Comment
Subject: Re: [allanglen/c172-flight-sim-panel] Router Template (#15)
That's beautiful what you have built and thank you for the reply.
I will certainly be printing all the bezels and understand what a router
template "should" be used for, but cannot see how the printed router
template supplied, was to be used.
Sorry if I'm sounding so dumb, but maybe I will just need to print it and
try to figure it out.
Thanks again for the reply.
JT
On Tue., Jun. 2, 2020, 10:41 a.m. JJMalette<EMAIL_ADDRESS>wrote:

If a 'strumebt bezel' is a bezel that accommodates one or more encoders,
then the template is used with a router and a 'flush' bit to remove the
material (wood, plastic) to make space to install an encoder. I've used
it
to install encoders required in a C172 open cockpit which I completed
last
year. Without Allen's printed 3D files for printing the bezels, I think
I'd
still be trying to learn 3D software rather than building the cockpit.
[image: DSC_0017 MODIFIED]
<
https://user-images.githubusercontent.com/42695696/83533311-6e07ca80-a4bd-11ea-9d2b-77fce2aeda2f.JPG
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/allanglen/c172-flight-sim-panel/issues/15#issuecomment-637587147
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ABNPQ7UWEBWRBOKWZKS4FJDRUUFPZANCNFSM4NP5E43Q
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/allanglen/c172-flight-sim-panel/issues/15#issuecomment-637615379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNPQ7VK6DBG5QUMNW6RUVDRUUKVPANCNFSM4NP5E43Q
.
[image: image.gif]

@JTRACKER
The router template is setup so that you can place it into the 3 1/8" hole you have cut into your 1/4 board. Then use a flush trim bit in your router so that it follows the inside of the router template.
Here is a video for using Flush Trim bits with a router that might help:
https://www.youtube.com/watch?v=enW2pabgwYw
Good luck!


FIX: ko was using the wrong cache directory

If go_manager_mod_dir is not ., the wrong cache directory is used (a directory relative to the go_manager_mod_dir.

/approve


Add label component prop and click chevron only prop for frost-expand

FEATURE REQUEST / CODE CHANGE
Summary
Add two new optional props to the frost-expand component: a prop that makes the chevron the only clickable area to expand/collapse and a prop that uses a component in the label instead of just a plain string.
Motivation

Describe the big picture of your feature to communicate why it should be added.

Why are we doing this?
So that there are additional options to match UX specs when using frost-expand to build other components
What use cases does it support?
Additional behaviour and aesthetic options for consumers
What is the expected outcome?

Detailed design
The isChevronOnlyClickTrigger prop when true will make the chevron icon the only clickable area to expand or collapse instead of having the entire label be clickable. The onClick action on the label and chevron will be conditional dependent on the isChevronOnlyClickTrigger prop.
When the labelComponent is passed in with a component, it will be displayed instead of the expand/collapse string labels. An additional if statement can be added in the frost-expand template to support showing the labelComponent.
How we teach this

What names and terminology work best for these concepts and why?
labelComponent is self explanatory.
isChevronOnlyClickTrigger is self explanatory but may be a bit too long.
How should this feature be introduced and taught to existing users?
It will be added to the dummy app and any documentation for frost-expand

Drawbacks
I don't think there are any since these are optional props
Alternatives

The onClick action on the label and chevron will be conditional dependent on the isChevronOnlyClickTrigger prop

Do you mean that the onClick action will still be called for whichever one of these is designated as the clickable area?

When the labelComponent is passed in with a component, it will be displayed instead of the expand/collapse string labels.

When employed when isChevronOnlyClickTrigger is false will the entire component container be clickable, regardless of the content inside?  Otherwise how are you planning on targeting specific content from the rendered component as only being clickable?

How we teach this
How should this feature be introduced and taught to existing users?
It will be added to the dummy app and any documentation for frost-expand

A frost-expand.md document should be added to https://github.com/ciena-frost/ember-frost-core/tree/master/docs

Do you mean that the onClick action will still be called for whichever one of these is designated as the clickable area?

The onClick action will only be called in whichever is the designated clickable area.

When employed when isChevronOnlyClickTrigger is false will the entire component container be clickable, regardless of the content inside? Otherwise how are you planning on targeting specific content from the rendered component as only being clickable?

When isChevronOnlyClickTrigger is false or not specified, the label portion of frost-expand which includes labelComponent will be clickable. The action on the entire label portion will be conditional so that we can target other things instead like just the chevron


feat(client): make skip to content button translatable

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Skip to content button isn't translatable, this makes it translatable

Good catch. Can't believe I missed this on the original PR.


Finish Getting RPC Fixes In

Task summary

At the moment there is a uncompleted task of some rpc implementations and fixes. The state of that branch allows configuration of the storage miner before attempting to mine. Addressing the concerns in the review would be a way to start
Specification reference

Other information and links

#841

I'm confused, is there any added scope to this? or this issue is just saying "get PR in"?

It's just completing whatever is left. I'm not doing a full day so not able to get it in


Crash when mass subscribing

What?
When I load the PCCurrentUser, I then attempt to mass subscribe to all rooms which is usually 50+
When i put the subscribing into a serial queue it doesn't crash but takes about 14 seconds compared to the 1 second it takes on just mass subscribing.

Environment

PusherChatkit version: 1.7.0
Xcode version: 10.2.1
Swift version: 5

This is now fixed from release 1.7.2


Conditional text screen vs print

This may not be directly related to bootmark, but I would like to know if there is any way I can have conditional text so that there is different text displayed when seen on screen (web) vs when someone takes a printout.
For example, I want to have a labelled link for screen (can be clicked) but a shortened URL for print (for reader to type manually).

shortened url's can still be clicked. by default bootmark uses showdown with simplifiedAutoLink: true, so links without the [ text ]( //url ) notation will be parsed as links.
But the idea of having different text for print than for web is still interesting

Adding support for attribute list can solve this, as well as make it more flexible.
Please consider this feature.
https://pythonhosted.org/Markdown/extensions/attr_list.html

this has already been brought to the attention of the showdown parser.
showdownjs/showdown#195

closing because this concerns showdown and not bootmark


Adds polyfill for findLast in firefox

closes #1869

What does this do?

What does this do?

Sorry I was in a rush when I submitted this. Ive updated the description. I'm on mobile right now so I'll add even more context when I'm at my desk.

closed for now. I think I have a strange bug on my end.


APIPort flags API as missing when override is missing

For example: DirectoryInfo.FullName.
On desktop this is:
public class FileSystemInfo {
 public virtual string FullName { get; }
}
public class DirectoryInfo: FileSystemInfo {
 public override string FullName { get; }
}

On .NETCore this is:
public class FileSystemInfo {
 public virtual string FullName { get; }
}
public class DirectoryInfo: FileSystemInfo {
}

APIPort reports DirectoryInfo.FullName as missing but it is not.

Closing as API Port was deprecated in favor of binary analysis in .NET Upgrade Assistant.


tilemap.copy() Bug

Version

Phaser Version: 3.55.2

Operating system: Windows 10

Browser: N/A

Description

When trying to copy more then half the map tilemap.copy() does not work as expected. It works in one direction but not the other.
If the map is 5x5 and you want to move columns 2-5 to the left one it works fine. If you want to move columns 1-4 to the right one it just replicates column 1 over and over.
This happens when you pass the half way point on a map. So on an 11x11 moving tiles 1-5 to over to column 6 works perfectly fine. Moving columns 1-6 over to column 5 is when it starts to mess up.
Example Test Code

on an 11x11 map
this.tmap.copy(0, 0, 5, 25, 6, 0);
works.
this.tmap.copy(0, 0, 6, 25, 5, 0);
where issues begin
Additional Information

I "fixed" it by having getTilesWithin() construct an array of new Phaser.Tilemaps.Tiles instead of referencing existing ones. Not sure if there's a better way to do it but it works.

Sorry kinda new to github etiquette. This was my fix
`function myGetTilesWithin(tileX, tileY, width, height, layer) {
if (tileX === undefined) { tileX = 0; }
if (tileY === undefined) { tileY = 0; }
if (width === undefined) { width = layer.width; }
if (height === undefined) { height = layer.height; }
// Clip x, y to top left of map, while shrinking width/height to match.
if (tileX < 0) {
    width += tileX;
    tileX = 0;
}

if (tileY < 0) {
    height += tileY;
    tileY = 0;
}

// Clip width and height to bottom right of map.
if (tileX + width > layer.width) {
    width = Math.max(layer.width - tileX, 0);
}

if (tileY + height > layer.height) {
    height = Math.max(layer.height - tileY, 0);
}

var results = [];

for (var ty = tileY; ty < tileY + height; ty++) {
    for (var tx = tileX; tx < tileX + width; tx++) {
        var tile = new Phaser.Tilemaps.Tile(layer.data[ty][tx].layer, layer.data[ty][tx].index, layer.data[ty][tx].x, layer.data[ty][tx].y, layer.data[ty][tx].width, layer.data[ty][tx].height, layer.data[ty][tx].baseWidth, layer.data[ty][tx].baseHeight);

        if (tile !== null) {
            results.push(tile);
        }
    }
}

return results;

}`
I just copied the phaser getTilesWithin() But instead of var tile = layer.data[ty][tx]; I did ' var tile = new Phaser.Tilemaps.Tile(layer.data[ty][tx].layer, layer.data[ty][tx].index, layer.data[ty][tx].x, layer.data[ty][tx].y, layer.data[ty][tx].width, layer.data[ty][tx].height, layer.data[ty][tx].baseWidth, layer.data[ty][tx].baseHeight);'

Yeah it happens because the copy operation works on the same array as the 'rect', so it overwrites the content as it's being copied, leading to corruption. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


Ft/update test

With the Lifecycle model changes in https://github.com/scality/Arsenal/pull/440, S3 tests had to be updated

PR has been updated. Reviewers, please be cautious.

PR has been updated. Reviewers, please be cautious.

@ironman-machine try

Hello @dora-korpar
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/20253' with the following env. args:
{
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "rel/7.4",
    "SCALITY_INTEGRATION_BRANCH": "ultron/rel/7.4",
    "SCALITY_S3_BRANCH": "bf/update-test"
}

PR has been updated. Reviewers, please be cautious.

:sunny: :+1: circleCI test succeeded!

PR has been updated. Reviewers, please be cautious.

@ironman-machine r+

:hourglass: PR is now pending. CI build url: http://ci.ironmann.io/gh/scality/Integration/20282

Hello @bennettbuchanan
"r+": Success

:sunny: :+1: circleCI test succeeded!


CI fixes

This tests against v4.11, switches the Travis builds from C++ to C, and also speeds up the process by not building the kernel each time.

The build against master is expected to fail. (As is the Style Check.)

Can you rebase? Just to make travis happy.

What would you like me to rebase against? The only thing that will make Travis happy is the forward port onto 4.12 and the fixes in my other series; I could combine both of these patch sets if you'd prefer?

Yes, this is what I meant; move this commit on top of 4.12 :)


783 dependency update

update dependency versions to address known security
vulnerabilities. This addresses the issue listed below.
Contributes to jmxtrans/jmxtrans#783
Signed-off-by: Charlie Hesketh<EMAIL_ADDRESS>Signed-off-by: John Beaven<EMAIL_ADDRESS>

:x: Build jmxtrans 451 failed (commit https://github.com/jmxtrans/jmxtrans/commit/24c063b9bd by @)

I have used a separate PR to test which dependencies are affecting the AppVeyour build and I've found that it is
com.fasterxml.jackson.core/jackson-databind
com.google.guava/guava
Will investigate further why these affect the build.


[Event Change Request] Codeunit 13 "Gen. Jnl.-Post Batch" – OnBeforeUpdateAndDeleteLines

Describe the request
Hello, can you please add "GenJnlLine2", "GenJnlTemplate", and "GenJnlBatch" to the event OnBeforeUpdateAndDeleteLines in codeunit 13 "Gen. Jnl.-Post Batch"?
    local procedure UpdateAndDeleteLines(var GenJnlLine: Record "Gen. Journal Line")
    var
        TempGenJnlLine2: Record "Gen. Journal Line" temporary;
        RecordLinkManagement: Codeunit "Record Link Management";
        OldVATAmount: Decimal;
        OldVATPct: Decimal;
        IsHandled: Boolean;
    begin
        IsHandled := false;
        OnBeforeUpdateAndDeleteLines(GenJnlLine, SuppressCommit, IsHandled, GenJnlLine2, GenJnlTemplate, GenJnlBatch);
        if IsHandled then
            exit;

    [IntegrationEvent(true, false)]
    local procedure OnBeforeUpdateAndDeleteLines(var GenJournalLine: Record "Gen. Journal Line"; CommitIsSuppressed: Boolean; var IsHandled: Boolean; var GenJournalLine2: Record "Gen. Journal Line"; GenJournalTemplate: Record "Gen. Journal Template"; var GenJournalBatch: Record "Gen. Journal Batch")
    begin
    end;

Additional context
We would like to set global variables in GenJournalLine2, check some values of GenJournalTemplate, and in some cases modify GenJournalBatch.
Internal work item: AB#545260

Hello,
In the procedure UpdateAndDeleteLines, after event OnBeforeUpdateAndDeleteLines, GenJnlLine2 is copied from GenJnlLine, so changing GenJnlLine2 is not relevant here. GenJnlTemplate and GenJnlBatch you can get from GenJnlLine.
I will close the request. If you still need it, please open the new one with more information.

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


#41 better timeouts handling

Codecov Report

Merging #53 (76cc0b0) into master (0413519) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #53   +/-   ##
=======================================
  Coverage   64.52%   64.52%
=======================================
  Files          60       60
  Lines        1091     1091
  Branches       20       20
=======================================
  Hits          704      704
  Misses        387      387

Impacted Files
Coverage Δ

...b/pandafolks/panda/loadbalancer/LoadBalancer.scala
100.00% <100.00%> (ø)

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


Bug: EPEERINVALID

After removing my node_modules/ folder, running npm cache clean and running npm install I run into an EPEERINVALID error.
Note: this is on a fresh pull from master
(git clone https://github.com/davezuko/react-redux-starter-kit.git)

Environment:

OS: OS X 10.11.1
Node: v.5.2.0
NPM: 3.3.12

This happend on both my and a colleague of mine's macbooks. Probably some issue with Node 5.2?
The npm start command runs fine and it compiles, but in the browser there's a error and the app is broken.
Terminal:

Browser:

All of the issues above, seems to be fixed with an npm update of: redux, react-redux, redux-devtools, redux-devtools-dock-monitor and redux-devtools-log-monitor.
Setting up a PR now!

same issue on Node v4.2.2

roger, confirmed that works

<EMAIL_ADDRESS>requires both monitors to be >= 1.0.1. It won't work with betas.

Fixed by #299

Thanks @inooid :+1:


IE11. Fix text input flex layout.

Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce?:

[x] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[ ] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] All new and existing tests passed

Description
Text Box nested inside the flex container will have zero width in the IE.

It's happening because of flex-basis: 0.

@kotielnikov @IKolosynskyi I think we should decrease the version to 0.6.2 and update changelog accordingly.

Latest released version is 0.6.3, packages are published already https://www.npmjs.com/package/precise-ui?activeTab=versions. Decreasing version will lead to conflicts.
@IKolosynskyi just use 0.6.3

@kotielnikov @IKolosynskyi I think we should decrease the version to 0.6.2 and update changelog accordingly.

Latest released version is 0.6.3, packages are published already npmjs.com/package/precise-ui?activeTab=versions. Decreasing version will lead to conflicts.
@IKolosynskyi just use 0.6.3

Actually, there won't be any conflicts due to pre-release version. It will be just like another version 0.6.2-pre.xxx.

@kotielnikov @IKolosynskyi I think we should decrease the version to 0.6.2 and update changelog accordingly.

Latest released version is 0.6.3, packages are published already npmjs.com/package/precise-ui?activeTab=versions. Decreasing version will lead to conflicts.
@IKolosynskyi just use 0.6.3

Actually, there won't be any conflicts due to pre-release version. It will be just like another version 0.6.2-pre.xxx.

Please fix me if I'm wrong.
More functionality -> higher version (this how versioning works). You can not go another way.

Please fix me if I'm wrong.
More functionality -> higher version (this how versioning works). You can not go another way.

SemVer applies to released packages comprising the changes listed in CHANGELOG. Quoting you More functionality -> higher version I 'm pretty sure there is missed one stage, which is releasing the new functionality.
That's why the next version can be one of:

1.0.0 (ready for/used in production, stable API, or the new version contains backwards incompatible changes);
0.7.0 (there is backwards compatible changes to the public API);
0.6.2 (only backwards compatible bug fixes).

Summarizing, we shouldn't increase the version each time when the PR merged into develop. It's the usual case when the PATCH release includes a lot of bugfixes.

@dimabory Version decreasing is possible only if we don't have version above, therefore I will not change the version to 0.6.2, this will bring mess into the current versioning system. Also, after this, my updated will not be the latest from the npm perspective.

Summarizing, we shouldn't increase the version each time when the PR merged into develop. It's the usual case when the PATCH release includes a lot of bugfixes.

That's totally correct, no arguing about this. The problem is that version was increased already and package was published.###  There is no way back

@dimabory Version decreasing is possible only if we don't have version above, therefore I will not change the version to 0.6.2, this will bring mess into the current versioning system. Also, after this, my updated will not be the latest from the npm perspective.

It shouldn't be the latest and even won't be. The latest is 0.6.1Try to check it here by picking a package precise-ui and entering the range latest.

@dimabory Version decreasing is possible only if we don't have version above, therefore I will not change the version to 0.6.2, this will bring mess into the current versioning system. Also, after this, my updated will not be the latest from the npm perspective.

It shouldn't be the latest and even won't be. The latest is 0.6.1. Try to check it here by picking a package precise-ui and entering the range latest.

Version decreasing will force to use the strict version.

@dimabory latest refers to the latest stable version. We are talking here about version numbers and what is the latest in sense of version number. @IKolosynskyi is totally right here - decreasing a version  will lead to the mess in versioning system

@dimabory Version decreasing is possible only if we don't have version above, therefore I will not change the version to 0.6.2, this will bring mess into the current versioning system. Also, after this, my updated will not be the latest from the npm perspective.

It shouldn't be the latest and even won't be. The latest is 0.6.1. Try to check it here by picking a package precise-ui and entering the range latest.

Version decreasing will force to use the strict version.

Let's use it again https://semver.npmjs.com/.

package: precise-ui
version: ^0.6.2-pre.358

What do you expect to see as a selected latest version?

@dimabory Version decreasing is possible only if we don't have version above, therefore I will not change the version to 0.6.2, this will bring mess into the current versioning system. Also, after this, my updated will not be the latest from the npm perspective.

It shouldn't be the latest and even won't be. The latest is 0.6.1. Try to check it here by picking a package precise-ui and entering the range latest.

Version decreasing will force to use the strict version.

Let's use it again https://semver.npmjs.com/.

package: precise-ui
version: ^0.6.2-pre.358

What do you expect to see as a selected latest version?

I want to see the highest version but after your proposition, I will see the intermediate version.

I want to see the highest version but after your proposition, I will see the intermediate version.

What do you mean under intermediate version?
If you decrease the version now to 0.6.2 the next pre-release version like 0.6.2-pre.xxx will contain everything from ^0.6.3-pre.xxx as well. Afterwards, we have to update (decrease) the version in the dependencies and npm i do everything for you.

@dimabory Let's stop this versioning holy war. Two vs one said that it's better to live 0.6.3. I don't see the benefits of going back.

@dimabory
Lets assume:
I'm a person from outside, have no idea about our internal organization stuff. And I want to use precise-ui, a super-duper ui library. And I'm always into the new stuff. NEWEST STUFF. I just can not deal with the idea that my project is not using the most recent version. That's why I'm checking the registry and see that the highest version is 0.6.3-pre.442. I install it.
Oh wait, but it doesn't contain the latest code, because someone messed up with versioning.

@dimabory Let's stop this versioning holy war. Two vs one said that it's better to live 0.6.3. I don't see the benefits of going back. Sometimes standards != real life.

it's important that all team members understand and accept these rules

@dimabory Let's stop this versioning holy war. Two vs one said that it's better to live 0.6.3. I don't see the benefits of going back. Sometimes standards != real life.

it's important that all team members understand and accept these rules

@kotielnikov @IKolosynskyi I will approve it and hope we won't fall into messy with versions in the future. Thanks!


logging: kconfig: Make it clearer that SYS_LOG is legacy

Change the prompt of SYS_LOG from "Enable Logging" to "Enable legacy
logging", and move the SYS_LOG stuff to after the LOG stuff (the new
logger).
Previously, you got "Enable Logging" (legacy logger) followed by "Enable
Logger" in the same menu, with no indication that they're different
systems.
Fixes: #14240

Here's what it looks like now:

Codecov Report

Merging #14847 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #14847   +/-   ##
=======================================
  Coverage   52.49%   52.49%
=======================================
  Files         309      309
  Lines       45060    45060
  Branches    10431    10431
=======================================
  Hits        23656    23656
  Misses      16592    16592
  Partials     4812     4812

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 22cf6d9...29a71e0. Read the comment docs.

Wouldn't choice be better ?

@jarz-nordic
Depends on whether both can be used at the same time.
I'll just remove all the SYS_LOG stuff instead though.

PR to remove SYS_LOG: https://github.com/zephyrproject-rtos/zephyr/pull/14883

@ulfalizer: I mean it makes limited sense to use two logging systems at the same time. First issue I can see they will compete for transport medium.

@jarz-nordic
Was thinking you might want both for legacy code reasons or something. I don't know much about the logging subsystems.

SYS_LOG has been removed instead.


add metrics to track buf_sock objects

Just realized this is a breaking change since it changes the signature of the setup function, should bump version when merging.


Linked in login

I am not android or ios developer. So for any mistake please guid me so i can fix it.
Right now In linkedin I am successfully getting access token which i need.
For IOS, I have used https://github.com/tonyli508/LinkedinSwift POD file
For Android i have used Official Linkedin SDK.

I will fix this all issue soon.... may be tonight

actually, I am not using this for LinkedIn login. Because Web token and Mobile Token are different for Linkedin. I already have a website and electron app using OAuth. When I pass the token to server and server retrieve user info.  But you can not use mobile token at server side to retrieve user info. I end up using Webview directly in my project for linkedin.  But this will be handy for users who want Mobile SDK Integration.


:bug:Fix Google and Facebook nameless login

Coverage increased (+0.01%) to 58.721% when pulling 190371d4609a75b28c4644c3235700115ba52d97 on fix-gplus-login into 0cfd6e80dd9ca116928bda456a47701e18302e55 on master.


feat(@angular/cli): migrate e2e tests to async/await

Protractor recently introduced a breaking change in version 6.0.0: no more custom control flow, everyone should use async/await instead.
Source: https://github.com/angular/protractor/blob/master/CHANGELOG.md

Control flow is removed and you should use async await to run your tests.

This behaviour is already accessible in versions before 6.0.0 under the flag SELENIUM_PROMISE_MANAGER=false.
By setting this flag to false - which is the default in 6.0.0 - I hope to reduce the migration time of new users of Angular using the CLI and using Protractor for e2e.
I personnaly did the migration 2 years ago and I believe it is preferable to start directly in async/await mode. It makes the test easier to read and futurproof.

@googlebot I signed it!

Thanks for the PR!
We discussed this in our team - This also needs a migration script to migrate all existing Protractor tests. We decided not to do it for now because of priorities.
Will revisit this as part of our next major release.

@vikerman @alan-agius4 Please let me know as soon as you'll be ready to merge such PR. For the moment it is more like a proposal for a PR. I am not sure we need to wait for a migration script to do that. In a way, it would be better for new users to start directly with the async/await mode (easier to understand, faster).
Protractor migration ROI
In a sense a migration tool from Protractor with custom promise manager to async/await would be a nice thing but in reality the two approaches are not fully equivalent. Protractor in async/await mode is far faster than the old mode. The async/await mode can create port exhaustion quite easily on Windows on code like:
element.all(by.repeater('todo in todoList.todos'))
      .filter(todo => todo.getText().then(label => label.indexOf('#10') !== -1))
      .each(todo => todo.element(by.css('input')).click())

The same code with async/await runs out of ports see https://github.com/angular/protractor/issues/4706 and https://github.com/dubzzz/protractor-move-async-await
In my current company we did the change but it was more than just putting async and await where it needs, we needed to tweak some of our page objects to avoid port exhaustion (to be able to run our tests on Windows).

Closing since this no longer the recommended path since protractor version 6 is deprecated.

We can maybe bump towards the latest version of protractor instead?

Version 7 is essentially the same as version 5, but includes some breaking changes.
The CLI version 10 already uses version 7.

Is there an issue or publicly shared vision on how team plans to move forward with Protractor? I'm afraid that we will be stuck with undebuggable control flow same as we're stuck with zone.js without support for native async/await for several years and no clear way forward.
As for a migration path for existing apps. Maybe a fixer based on await-promise + some iterations testing it against Google's codebase and improving fixer and Protractor types will solve most of it?


electron support

can control electron instead of chrome?

We currently do not plan on supporting Electron. Please check Stackoverflow for workarounds.


[zh-cn] Amending "式" to the word "序" in k/website

这里的: 但是当某个应用程式资源利用率不高时,应为:但是当某个应用程序资源利用率不高时
其中的式应该改为序

Hi @JBossBC, please provide details for your issue as current issue does not give any information.
/triage needs-information

In there,the word '式' should be changed to the word "序".it is more reasonable for this sentence situation

/triage accepted

/retitle [zh-cn] Amending "式" to the word "序" in k/website

@JBossBC : Please could you add the link to this page so that contributors can pick it up and work on it?

https://kubernetes.io/zh-cn/docs/concepts/overview/

小鑫?不忘初心
@.***

------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2023年1月24日(星期二) 下午3:59
收件人: @.>;
抄送: "Xiyang @.>; @.>;
主题: Re: [kubernetes/website] [zh-cn] Amending "式" to the word "序" in k/website (Issue #39035)
@JBossBC : Please could you add the link to this page so that contributors can pick it up and work on it?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

https://kubernetes.io/zh-cn/docs/concepts/overview/.

/language zh

PR https://github.com/kubernetes/website/pull/41710 has been merged, so this issue can be closed.
/close


added updates to update deprecations: model.summary() and pl.metrics

Hello @borhanMorphy, I appreciate your interesting and useful repository.  I have updated it to work with the current version of pytorch lightning.  It should run out-of-the-box with a current python virtual environment (August 2023).  Let me know if you have any questions or comments.

Hey @jdsalmonson, thank you! Very glad to see that you set some time to help me out.
All looks good, I might need to update afterwards to support py38 and py39 as well.


go-ipfs v0.8.0

go-ipfs v0.8.0 has been published https://dist.ipfs.io/#go-ipfs

published v1.1.6 to the galaxy with that et. al.


Automator: update istio/api@master dependency in istio/client-go@master

Generated by Automator - 2020-04-16T17:17:19+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
f583728409dcbe7eeebc68cbfd998ce0e8ebca44
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
86ad5c028448db7b021a96cd47ef0cba13d9f8bb
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
86ad5c028448db7b021a96cd47ef0cba13d9f8bb
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
9be77eb54afa8e0b524a52f880154f04fef9e4d7
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
5eef079bf86167a53d4d98b906fee41089fede3f
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
5eef079bf86167a53d4d98b906fee41089fede3f
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
c055164bae0169d3b316792339ab9e7f967f8d87
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
b029cabd16165000501f313a26aceab2a5470aea
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
abde9d4e63ed06d18d4a706ca2d3ce0eeab17d15
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
abde9d4e63ed06d18d4a706ca2d3ce0eeab17d15
link
/test lint_client-go

gencheck_client-go
abde9d4e63ed06d18d4a706ca2d3ce0eeab17d15
link
/test gencheck_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_client-go
abde9d4e63ed06d18d4a706ca2d3ce0eeab17d15
link
/test gencheck_client-go

lint_client-go
60ff6dd148d2ac875c11dc24c1ec1c5f19e3099a
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
60ff6dd148d2ac875c11dc24c1ec1c5f19e3099a
link
/test lint_client-go

gencheck_client-go
60ff6dd148d2ac875c11dc24c1ec1c5f19e3099a
link
/test gencheck_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_client-go
60ff6dd148d2ac875c11dc24c1ec1c5f19e3099a
link
/test gencheck_client-go

lint_client-go
389b7d34926cef3fee08b68e52b27386a3a9eafa
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_client-go
389b7d34926cef3fee08b68e52b27386a3a9eafa
link
/test lint_client-go

gencheck_client-go
389b7d34926cef3fee08b68e52b27386a3a9eafa
link
/test gencheck_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_client-go
389b7d34926cef3fee08b68e52b27386a3a9eafa
link
/test gencheck_client-go

lint_client-go
faae9ef45e7e8be058f9774eebc84edc2c49e225
link
/test lint_client-go

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Enhancement Proposal for Dynamic Evaluation Framework Integration

Dear PromptBench Contributors,
I trust this message finds you in good health and high spirits. I am writing to propose an enhancement to the PromptBench library that I believe could significantly augment its utility for researchers and practitioners alike.
Having perused the documentation and utilised the library extensively, I have found the dynamic evaluation framework, DyVal, to be an invaluable asset for assessing the performance of Large Language Models (LLMs) in a more robust and realistic manner. However, I have observed that the integration of DyVal could be further refined to provide a more seamless user experience and to extend its capabilities.
To wit, I propose the following enhancements:

Streamlined Integration: Simplifying the process of setting up and running DyVal within the PromptBench environment. This could involve automating the setup process and providing a more intuitive API that abstracts away some of the complexities involved in configuring the dynamic evaluation parameters.

Extended Dataset Support: Expanding the range of datasets compatible with DyVal. While the current selection is commendable, incorporating additional datasets, particularly from niche domains, could broaden the scope of dynamic evaluation and provide deeper insights into model performance across diverse contexts.

Custom Evaluation Metrics: Facilitating the integration of custom evaluation metrics within the DyVal framework. This would allow researchers to define and utilise metrics that are specifically tailored to their unique research questions or application requirements.

Real-time Performance Monitoring: Introducing functionality for real-time monitoring of model performance during dynamic evaluation. This could include visual dashboards or logging mechanisms that provide immediate feedback on the model's performance trends over time.

Guidance on Best Practices: Providing comprehensive documentation and examples that elucidate best practices for leveraging DyVal in various research scenarios. This could greatly assist users in maximising the potential of dynamic evaluation for their specific use cases.

I am keen to engage in further dialogue regarding these suggestions and explore how we might collaborate to bring these enhancements to fruition. I am convinced that by enriching the DyVal integration, PromptBench can offer even greater value to the community by enabling more nuanced and insightful evaluation of LLMs.
Thank you for considering my proposal. I eagerly anticipate your response and am hopeful for the opportunity to contribute to the evolution of PromptBench.
Best regards,
yihong1120

Hi Yihong,
Thank you for your suggestions about enhancing PromptBench with DyVal integration. We appreciate your valuable suggestions and eager to discuss how we can collaborate. Could you share your thoughts on how we might work together on this? (P.S., feel free to initiate a pull request.)


Craft 4 Support

We have several Craft 3 sites using your plugin and are really keen to upgrade them to Craft 4.
Do you have any plans to add support for Craft 4?

@timeverts https://github.com/supercool/tablemaker/pull/26 ?

Great to see there's some work there @sfsmfc. But will someone be merging that request into an official release for the plugin store, or am I talking to the wrong person about this?

You are talking to the wrong person. I'm only a developer, who use this plugin and have searched for a solution...

Just to chime in, we've added this to our Craft 3 migration project. If it gets enough votes, we'll migrate this plugin to Craft 4 and continue to work on it, giving it a new home, and keeping it open source.
Do let us know if you plan to make the plugin Craft 4 compatible!

@engram-design Amazing if you do it! I see the votes were met on your site, will verbb.io be taking it over?

Just out of interest has anyone tried to make contact with the agency behind this plugin: https://supercooldesign.co.uk/contact, the lack of responses on this GitHub repo probably confirms it, but as they look to still be an active developer as an agency we can try and get an official word?

@jamesmacwhite I'll reach out to them shortly, but I was under the impression from https://github.com/supercool/buttonbox/issues/39#issuecomment-1125099539 that there were plans for their other plugins, but that might not be the case!

@engram-design Ah didn't know they'd responded on another repo already. I wouldn't say this plugin has been active for years, the Craft 3 port was done, but it didn't even have Craft 2 to 3 migration handling, so there wasn't really a smooth translation path to begin with, unless you forked it or wrote content migrations instead.
Of course if they do plan to change to update it to Craft 4, that would be great, just good to know given Craft 3 hasn't really had much activity.

We've recently acquired this from the Supercool team. Read our blog post for more details.

Available for Craft 4 now


Calling MaybeUninit::uninit().assume_init() is UB

Hi,
I saw your talk at EuroConf 2022 and was horrified surprised to see that you were using MaybeUninit::uninit().assume_init(), this is completely UB and is equivalent to using std::mem::uninitialized whish was deprecated for being UB.
From the std docs:

The compiler, in general, assumes that a variable is properly initialized according to the requirements of the variable’s type. For example, a variable of reference type must be aligned and non-null. This is an invariant that must always be upheld, even in unsafe code. And no matter whether that reference ever gets used to access memory.

For more information's you can also read Ralf blog post: "What The Hardware Does" is not What Your Program Does: Uninitialized Memory.

The offended code

https://github.com/ColinFinck/nt-list/blob/4406c77cd00ea9114a6e5bfe5bf56fc026d6cd50/nt-list/src/list/base.rs#L49-L50
https://github.com/ColinFinck/nt-list/blob/4406c77cd00ea9114a6e5bfe5bf56fc026d6cd50/nt-list/src/single_list/base.rs#L263
https://github.com/ColinFinck/nt-list/blob/4406c77cd00ea9114a6e5bfe5bf56fc026d6cd50/nt-list/src/list/boxing.rs#L49-L50

There is even an open PR on rust-lang/rust that would Panic on invalid usages of MaybeUninit::uninit().assume_init() and I'm pretty sure that it would unconditionally panic in your case.

Looking more closely I can see that flink, blink and next are always pointer that means that you could initialized them with a null pointer, std::ptr::null_mut without UB or even unsafe code.


Remove error callback and settings from unregister function on Android

Currently the onErrorCallback is not used at all and the settings are used only to get senderID. Settings should cached like it is done for iOS and then unregister should pull the senderID from the cached settings.

@PeterStaev
Thanks for your input. Please find below my comments.

Since version 0.1.0 the error callback of the unregister method is put in use.
The signature of the unregister method accepts the Sender I from an options parameter. Technically speaking, in your second suggestion, the options will be available only if the register method is called before calling unregister, which is not always the case. My understanding is that we may want to keep the API of the plugin as cleaner as possible.

Can you please elaborate on the above if you have further considerations, ideas or you think I am not completely understanding it. Thanks in advance.

Hey @AntonDobrev , for the second part, are there any use cases where you would call unregister before calling register first (except user error)? If you look at the iOS implementation for the registerUserNotificationSettings it also assumes that you call register first https://github.com/NativeScript/push-plugin/blob/master/push-plugin.ios.js#L59.


FR12: Tweak Context and Behavior for Optimized Performance

FR12: Tweak Context and Behavior for Optimized Performance

Goal: Allow Open Source Developers to modify context and behavior settings.
Stakeholders: Open Source Developers
Description: By publishing the code to GitHub and keeping it public, open-source developers can change specific aspects of how Ducki works to meet their needs.
Origin: Based on the initial project specification document, team members came up with this description during the first meeting.
Version: 1.0
Date: 09/14/2024
Priority: 2

This goes along with the push for Ducki to remain open source.


Improve organisation of settings reference page

Pertinent section of the Wagtail docs
https://docs.wagtail.org/en/latest/reference/settings.html
Details
The Settings reference page is ostensibly organised into category subheadings ("Site name", "Append Slash"...), but since settings generally get added one-by-one with no plan for how they relate to each other, most of the subheadings only have one or two items in them, and so people end up having to read through the whole list to find the one setting they're interested in. I'd like to see these organised into fewer, broader categories.
The "correct" categorisation is a matter of opinion, of course, but I think that anyone with a basic familiarity with Wagtail's feature set could make an improvement here. My suggestions are:

ensure all headings are named consistently, in particular: don't capitalise ADMIN BASE URL, and change "API Settings" to just "API" (everything here is a setting, so the word Settings is redundant...)
Categories that map to a specific sub-app of Wagtail (Search, Embeds, Images, Documents, API, Frontend cache, Redirects, Form builder) should stay
WAGTAIL_SITE_NAME and WAGTAILADMIN_BASE_URL should go together under a heading "Sites" or similar
WAGTAIL_GRAVATAR_PROVIDER_URL, WAGTAIL_USER_TIME_ZONES and WAGTAILADMIN_PERMITTED_LANGUAGES go together under a heading "User preferences"
TAGGIT_CASE_INSENSITIVE, TAG_SPACES_ALLOWED, TAG_LIMIT go together under a heading "Tags"
WAGTAILADMIN_COMMENTS_ENABLED, WAGTAIL_ALLOW_UNICODE_SLUGS, WAGTAIL_AUTO_UPDATE_PREVIEW, WAGTAIL_AUTO_UPDATE_PREVIEW_INTERVAL, WAGTAILADMIN_GLOBAL_PAGE_EDIT_LOCK, WAGTAILADMIN_UNSAFE_PAGE_DELETION_LIMIT go together under a heading "Page editing" - maybe WAGTAILADMIN_RICH_TEXT_EDITORS and WAGTAILADMIN_EXTERNAL_LINK_CONVERSION go here too
Everything under "Password management" and "Custom user edit forms", plus WAGTAILADMIN_USER_LOGIN_FORM, can go together under a heading "User management"
"Private pages / documents" and the remaining items under "Login page" can become a new heading "Front-end authentication"

Other ideas are welcome!

Hello @gasman  I was trying to set up the wagtail codebase in my computer. I followed the exact steps mentioned in https://docs.wagtail.org/en/latest/contributing/developing.html#developing-for-wagtail and while running the test part 'python runtests.py' It is giving some errors. The issue  looks like mostly documentation oriented, so if you can guide me and show how to edit or change the documentation it would be really helpful. I am a newcomer one small help from your side can be a milestone in my entire open-source journey. Please help me.

Hi @Akash-Kumar-Sen,
The Wagtail Slack workspace is the best place for getting help with this - or see the Support page in the documentation for other options.

Fixed via 827bcf3dbf3a007e9218d3955b3d9998041d63e8 / #8950


test_ondemand_download_large_rel[local_fs] is flaky

See recent failures in main:
https://github.com/neondatabase/neon/actions/runs/3800508509/jobs/6464224788
https://github.com/neondatabase/neon/actions/runs/3799945789/jobs/6463182707

Closing this in favor of the more recent open issues.


Remove unnecessary keys()

iter(dict) is equivalent to iter(dict). Can drop the unnecessary keys() call.

Unless @jayvdb shows up and says he thinks this is worth merging, I'm inclined to not. My reasoning for it is that I didn't write that code, and I don't see any problems that the current code might cause. The proposed code simplification isn't exactly the same semantics (though in most cases they do indeed do the same thing), and I don't think it's worth the effort to make sure that there isn't some subtle bug that requires things the way they are written.
In any case, thanks for your willingness to contribute to tox-travis, @jdufresne . I hope that I'll see more from you in the future!

This change was inspired by Lennart Regebro's PyCon 2017 presentation "Prehistoric Patterns" where he makes the argument that most code never needs .keys() and modern Python should prefer iter(dict) over iter(dict.keys()). If you decide not to merge it, no worries.

Link to video: https://www.youtube.com/watch?v=V5-JH23Vk0I

Good video, and I completely agree (and did already). I was inclined to close it, but given that all the tests are passing, I think it's probably fine to go ahead and merge. The risk is still non-zero, but the tests should be enough assurance that I'm comfortable with merging it.

Actually, I'm going to simplify it further. I don't think that list is necessary either.


Permit changing default user agent

What is the use case for this change?

It can be useful in some situations to know when a user agent can't be parsed correctly. My preference is to return an empty string instead of Mozilla/4.0 (compatible). As not everyone has this preference, it makes sense to allow a configurable default rather than having to monkeypatch UserAgent::DEFAULT_USER_AGENT.

I can see something along those lines being useful. For example, if returning nil for a user agent that couldn't be detected you could do something like:
if ua = UserAgent.parse(user_agent)
  # Something based on known UA
else
  # Fallback for unknown UA
end

I could also see a parse! variant that raised an error if the UA was unknown being useful for similar patterns.
WDYT? Yours is a non-breaking change but I'm already considering a major version for #40 so I could include a breaking change along these lines with that into a major version.

@gshutler sounds good to me!


Host compiler lacks C11 support

I tried NDK r21 and r25, they both reported:

Have you tried ndk r26c? GitHub Actions use Linux with this version of ndk and the build is successful. I'll try previous versions of ndk later today.

Yes, r26c is also broken

I saw your workflow contains:
-- Check for working C compiler: /usr/local/lib/android/sdk/ndk/26.2.11394342/toolchains/llvm/prebuilt/linux-x86_64/bin/clang - skipped
But mine is linux-x86_64/i686-linux-android21-clang
Besides, I am using WSL on Windows

Ok, so it is windows with wsl actually. What Linux distribution do you use with it?
Also, have you tried Docker image?
I'll be able to check the wsl tomorrow I guess

The default Ubuntu
On Sun, Apr 7, 2024, 00:31 Oleksandr Berezhnyi @.***>
wrote:

Ok, so it is windows with wsl actually. What Linux distribution do you use
with it?
Also, have you tried Docker image?
I'll be able to check the wsl tomorrow I guess
—
Reply to this email directly, view it on GitHub
https://github.com/Javernaut/ffmpeg-android-maker/issues/89#issuecomment-2041132102,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKFEBSWWKMF3MF7QXFARCDY4APMTAVCNFSM6AAAAABF2PJ3G6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGEZTEMJQGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can you also share your sources/ffmpeg/ffmpeg-7.0/ffbuild/config.log file? Or at least its end part. Usually one can find valuable info there.

So, I managed to access my Windows machine much earlier. I successfully compiled the vanilla FFmpeg (without any external libs), so I assume it is something wrong with the configuration of your machine.
My setup:

Windows 11
WSL2
Ubuntu 22.04
Android NDK both r25c and r26c

Did you install exactly the Linux versions of both Android SDK and NDK into your Linux subsystem?
And the sources/ffmpeg/ffmpeg-7.0/ffbuild/config.log file is really helpful for this kind of problems. Please, share it or the end part of it.
As for your comment:

I saw your workflow contains:
-- Check for working C compiler: /usr/local/lib/android/sdk/ndk/26.2.11394342/toolchains/llvm/prebuilt/linux-> x86_64/bin/clang - skipped
But mine is .../linux-x86_64/bin/i686-linux-android21-clang

There is nothing wrong here. There is only one compiler in NDK actually, which is just clang. All other files like i686-linux-android21-clang just call clang under the hood and pass additional arguments.

Always thanks for your timely reply and hard work 😁, good job then.


How to control log level of tmkms

I'd like to install the tmkms as a service, which running long enough.
so I tried to let kms only print error level logs.
but seems RUST_LOG=error not works.
Any suggestions?  Thanks.
j@j ~ $ RUST_LOG=error ./tmkms start -c tmkms.toml
13:45:07 [info] tmkms 0.6.3 starting up...
13:45:07 [info] [keyring:softsign] added consensus key coinexvalconspub1zcjduepq37l2ulws68yhe5aaeh4sk4q6r78chxcd3zse2ewr9nplpzjvrcxqgn25jz
13:45:07 [info] KMS node ID: 25150CF2E0400E57AB29475C78E28836C247D985
13:45:07 [error] [coinexdex-test1@tcp://<IP_ADDRESS>:26658] I/O error: Connection refused (os error 111)
13:45:08 [info] KMS node ID: 25150CF2E0400E57AB29475C78E28836C247D985
13:45:08 [error] [coinexdex-test1@tcp://<IP_ADDRESS>:26658] I/O error: Connection refused (os error 111)
13:45:09 [info] KMS node ID: 25150CF2E0400E57AB29475C78E28836C247D985
13:45:09 [error] [coinexdex-test1@tcp://<IP_ADDRESS>:26658] I/O error: Connection refused (os error 111)
^C

Right now there is only a coarse grained option to do debug logging via the -v command-line argument. I agree it'd be good to offer finer-grained control of the loglevel via command line options and/or configuration.

Got it, Thanks for reply @tarcieri

Note that with v0.7.0 logging is now handled by tracing. The framework supports fine-grained loglevels but these still aren't exposed in any user-facing way.


hv or hvplot overlay colorbar normalization...

I have two holoview or hvplots that when overlaid, the colorbar isn't renormalized.  What I mean by that is that glyph a has a color scale from 0 to 100 and the cmap is mapped to those values.  When I overlay glyph b which has a colorbar scale from 50-150, it seems that the colorbar cmap isn't renormalized in the overlay to have a scale from 0-150.  What I find is the colorbar from glyph a is kept.  See example below.  Would it be possible to merge the two color scales easily and each scatter plot would fit within the colorbar shown?
import holoviews as hv
import pandas as pd
import hvplot.pandas
hv.extension('bokeh')

a={'X': [0, 1, 2],
   'Y': [0, 1, 2],
   'Z': [0, 50, 100]
  }

b={'X': [3, 4, 5],
   'Y': [0, 10, 20],
   'Z': [50, 50, 150]
  }

test_a=pd.DataFrame(a)
test_b=pd.DataFrame(b)

glyph_a=test_a.hvplot.scatter('X', 'Y', c='Z', cmap='viridis')
glyph_b=test_b.hvplot.scatter('X', 'Y', c='Z', cmap='viridis')

glyph_a*glyph_b

Appears to be a HoloViews issue.


Add integration tests

Add integration tests to access the FUSE endpoint and test all kind of operations.
Setup tests similar to examples/mount.rs and then run integration tests over the mounted folder.
To perform the actual operations use the std::fs::OpenOptions, std::fs::File, std::fs and std::io. All tests run against the mount-point.
Each test needs to have it's own mount-point and data-dir so they can be ran in parallel.
Add target guard to only run tests on linux for now until we have implementations of FUSE on macos and windows too. You can add this in tests, setup and teardown methods
#[cfg(not(target_os = "linux"))] { return; }
Reference unit tests you can combine logic from and adapt to integration tests

src/encryptedfs/test.rs
src/crypto/read/test.rs
src/crypto/write/test.rs

Get from these too when done

https://github.com/radumarias/rencfs/issues/117
https://github.com/radumarias/rencfs/issues/58

You can also create similar tests like https://github.com/radumarias/rencfs/issues/181
Ref

https://chatgpt.com/share/89013b9d-d7b4-442d-a804-b001a73150a4
https://youtu.be/MiLp0InGOkI?si=xrt3V57DuL1uG2Vr
distributed runners https://github.com/maelstrom-software/maelstrom

@rakurame96 how are you with this?

@rakurame96 any progress on this?

@rakurame96 how are you with this?


Enhancement: eeprom read/dump and write/restore

Hi!
Is it doable to dump eeprom data in MIB STD2 like in MIB2 High units with
on -f rcc /net/rcc/usr/apps/modifyE2P r 0 10000 > $DUMPFOLDER/eepromdump.txt ?

Alas there is no modifyE2P utility for mib std2 pq/zr existing/available.

Thank you for quick reply. I've investigated some things, checked the J5 dump, and it looks like:
0x003B00 data is available in /tsd/etc/audio/soundcurves/configuration.bin;
0x003000 data is in /tsd/etc/audio/soundcurves/vw/soundparams0.bin (there are configs for VW, Seat, Skoda in separate folders).
I have no idea if this is copy of eeprom data, back data, default data for the mib to restore, or even something completely different.

It was a nice finding - yes those are default 0x3000 (the frequency filters) and 0x3B00 (the mixer GUI settings) datasets to handle situation when you have no such a dataset in the eeprom but switch modes of the amplifier in 11th byte of long coding of 5F (for example from Canton/Fender to 4, 6 or 8 passive speakers).
You cannot upload those files to J5 filesystem easily because the filesystem of J5 CPU is located not in eMMC but SPI chip on the motherboard. SPI filesystem is read only and you cannot remount it in rw mode like the filesystem of eMMC. That is exactly the system that gets flashed when you update stock fw and after reboot emerncies start to get updated.

I know that originally this topic was about eeprom, so I hope that you don't mind if I go deeper into datasets and sound configuration.
So about GUI and 0X3B00:
In my unit (MIB2 Standard, Technisat, ZR, VW, 0478, Golf MK7, standard system) i had no data in 0x3B00.
File /tsd/etc/audio/soundcurves/configuration.bin shows:
004064 F70009 F70009 F70009 000000 F70009 000000 F70009<PHONE_NUMBER>070000 001E262E373F474F5764707D8995A6B6C7DBF0 4446 5FCA. This data means that _ should have three sliders for equalizer (low, mid, high). This is correct.
I took this data, edited it to add information about additional two sliders, parametrized 0x3B00 with it, rebooted MIB, but no new sliders visible -everything is the same as before.
Next I asked my friend with Seat Leon to take a picture of the equalizer in his car, and to dump J5 from his unit. 5 sliders are available in GUI, but the configuration.bin looks identical as in my VW - there's info just about 3 sliders.
My assumptions:

MST2 is not using 0x3B00 at all (empty from factory, no effect after uploading).
File configuration.bin is not used by default (Seat is showing different GUI than file indicates). Might be used as fallback if sound system is not coded correctly?
Maybe the '0x3000` dataset determinates how the GUI looks in MST2?

Need to check:

If full Seat Leon 0x3B00 dataset will make any difference (I edited my data to add just two sliders. Seat also adds subwoofer menu).
If configuration.bin stays unchanged after '0x3B00` parametrization.

My target:

Connect subwoofer to MST2 and drive it from internal amplifier - just like in 9VD Seat Sound System option.
Add additional controls for the upgraded sound system.

Take a look at this article: https://www.drive2.com/l/611261670785849626/

Seen it. Great piece of work. Based on it I was able to create the custom dataset for my MST2.
But still, car in this article is Audi with MIB2 High, which behave different than my VW MIB2 Std.
Will experiment more and post details here: https://github.com/mattcabb/mib2-parameter-tool

Hi @mattcabb. I'm looking to modify the 0x3000 data and write it back to the unit. I can understand how I may dump the data.
How did you achieve writing the configuration data back into the head unit? Any guidance would be appreciated thanks.


Snapshot DOM

How would we snapshop the DOM as it was? But this doesn't give us an actual snapshot of a DOM?
func Nodes(sel interface{}, nodes *[]*cdp.Node, opts ...QueryOption) Action
func NodeIDs(sel interface{}, ids *[]cdp.NodeID, opts ...QueryOption) Action

What do you mean by "snapshot" of the DOM? If you want the full DOM tree, then you just need to call chromedp/cdp/dom/getDocument. If you want the actual HTML, you need to use a network command. Neither of this is built in at the moment.

Yeah I'd like a screenshot of the DOM for further processing. You have ByID and ByQuery but not "ByTag" which would be "body" that seems easiest.


Introduce \solution{x} for double underlined solutions of equations

Introduce \solution{x} for double underlined solutions of equations
Changes:
wbh.tex: added \solution as new command for double underlined text in math equations
beispiel.md: added example of usage

Fixes/Implementes FR in #20


docs: document lazy.nvim instalation

It seems like the documentation is kind of repetitive but it took a little time to get the right configuration while I was migrating from packer to lazy.nvim.
On this case the requires will be replaced by dependencies.

Similar PR was closed a week ago, see https://github.com/ThePrimeagen/harpoon/pull/422#issuecomment-1869715778

i am going to do this and delete the packer one at some point.
the documentation is going to get a complete redo soon


Feature/disable reorder

Codecov Report

Merging #14 (d355dfc) into master (0275fa5) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #14   +/-   ##
=======================================
  Coverage   99.75%   99.75%
=======================================
  Files          11       11
  Lines         411      411
=======================================
  Hits          410      410
  Misses          1        1

Impacted Files
Coverage Δ

lib/widgets/reorderable_grid_view_layout.dart
100.00% <ø> (ø)

lib/widgets/reorderable_wrap.dart
100.00% <ø> (ø)

lib/widgets/reorderable.dart
100.00% <100.00%> (ø)

lib/widgets/reorderable_grid_view.dart
100.00% <100.00%> (ø)

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 0275fa5...d355dfc. Read the comment docs.


TMF8821 Testing + Upgrade circuits_i2c?

Hi @pkinney thanks for writing this awesome library. I've started it using it with a TMF8821 sensor in my trilobot project. In order to use this library with the current version of nerves, I needed to add {:circuits_i2c, "~> 2.0", override: true}. Part of the 2.0 release for circuits_i2c is the ability to create simulated backends for an i2c connection.
I was wondering if you have any thoughts about this for your project? Would it be helpful if I work up a PR to upgrade this project and replay to support circuits_i2c "~> 1.0 or ~> 2.0" and keep using your replay library for testing? Or I could try out the new testing tools built into circuits_i2c?

Absolutely! I haven't had a chance to mess with Circuits 2.0 yet, so feel free to take a crack at it.  If you have any questions or want to work together on it, feel free to reach out.


Accessibility Issues - Dropdown component - Carbon IOT React level issue

Getting 2 accessibility issues for Dropdown component in Graphite. Issues are due to Carbon react level.
Issues are:

Ensures every ARIA input field has an accessible name

ARIA input fields have an accessible name
More info...
#dropdown
Serious
aria-label attribute does not exist or is empty
Serious
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Serious
Element has no title attribute or the title attribute is empty
wcag2a
wcag412

Ensures elements with an ARIA role that require child roles contain them

Certain ARIA roles must contain particular children
More info...
#dropdown
Critical
Required ARIA child role not present: option
cat.aria
wcag2a
wcag131
Observation:
As per carbon design react storybook "http://react.carbondesignsystem.com/?path=/story/dropdown--default" if we remove the content  from the knob "Title (titleText)", we will start getting same error in DAP.
Details:
As per carbon design react storybook below elements got rendered when text is avaialble in knob "Title (titleText)"-
This is not a dropdown title.

*label element is defining label for dropdown id "carbon-dropdown-example".
After clearing out the content of knob "Title (titleText)", we get below html -

*no label element to define label for dropdown id "carbon-dropdown-example".
If we try to run DAP after clearing out the knob content as stated above, we get same accessibility violation.
Summary:
carbon design react component expect us to have title whenever we use a dropdown but as per our application title is not mandatory to be with every dropdown used in the application.
(url
Dropdown_Component_Issue.docx
)

Hi @agupta2-ibm-maximo. Thanks for submitting this issue.

hi @agupta2-ibm-maximo,
the first problem has been fixed already on Carbon while I opened https://github.com/carbon-design-system/carbon/issues/5368 to fix the second

A much bigger change from the Carbon team is on its way https://github.com/carbon-design-system/carbon/pull/5373
That solves our problem plus many more a11y related


Keep updated /etc/hosts on velum-dashboard container, bsc#1062728

We would like to keep /etc/hosts file updated for velum-dashboard with
Admin host. Velum needs to know external name of Kube API which will be used
to register in Dex service. Problem was discovered and discribed in bug 1062728

Rebased again over https://github.com/kubic-project/salt/pull/268

Merging based on +A's in the earlier PR's from @mjura's fork - these are clean rebases.


OSError: [Errno -9998] Invalid number of channels

Steps to reproduce

I was trying to use an audio output as Microphone()
When I list my microphones with

import speech_recognition as sr
for index, name in enumerate(sr.Microphone.list_microphone_names()):
    print("Microphone with name \"{1}\" found for `Microphone(device_index={0})`".format(index, name))

the output has these devices: Microphone with name "Headphones ()" found for Microphone(device_index=17) and Microphone with name "Microphone (Realtek(R) Audio)" found for Microphone(device_index=15)
Expected behaviour
It would use my speakers to recognize audio/microphone(?)
I get an error
Traceback (most recent call last):
  File "c:\Users\pedro\Desktop\python\speech-recognition\text-to-speech.py", line 6, in <module>
    with mic:
  File "C:\Users\pedro\AppData\Local\Programs\Python\Python38-32\lib\site-packages\speech_recognition\__init__.py", line 138, in __enter__
    self.audio.open(
  File "C:\Users\pedro\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pyaudio.py", line 750, in open
    stream = Stream(self, *args, **kwargs)
  File "C:\Users\pedro\AppData\Local\Programs\Python\Python38-32\lib\site-packages\pyaudio.py", line 441, in __init__
    self._stream = pa.open(**arguments)
OSError: [Errno -9998] Invalid number of channels

My system is Windows 10 x64.
My Python version is 3.8.5. (You can check this by running python -V.)
My Pip version is 20.3.3. (You can check this by running pip -V.)
My SpeechRecognition library version is 3.8.1.
My PyAudio library version is 0.2.11.
My microphones are: ['Microsoft Sound Mapper - Input', 'Microphone (Realtek(R) Audio)', 'Microphone (Voicemod Virtual Au', 'Microsoft Sound Mapper - Output', 'Alto-falantes (Realtek(R) Audio', 'Line (Voicemod Virtual Audio De', 'Primary Sound Capture Driver', 'Microphone (Realtek(R) Audio)', 'Microphone (Voicemod Virtual Audio Device (WDM))', 'Primary Sound Driver', 'Alto-falantes (Realtek(R) Audio)', 'Line (Voicemod Virtual Audio Device (WDM))', 'ASIO4ALL v2', 'Alto-falantes (Realtek(R) Audio)', 'Line (Voicemod Virtual Audio Device (WDM))', 'Microphone (Realtek(R) Audio)', 'Microphone (Voicemod Virtual Audio Device (WDM))', 'Headphones ()', 'Headset (@System32\\drivers\\bthhfenum.sys,#2;%1 Hands-Free AG Audio%0\r\n;(JBL TUNE205BT))', 'Headset (@System32\\drivers\\bthhfenum.sys,#2;%1 Hands-Free AG Audio%0\r\n;(JBL TUNE205BT))', 'Headphones ()', 'Speakers 1 (Realtek HD Audio output with SST)', 'Speakers 2 (Realtek HD Audio output with SST)', 'PC Speaker (Realtek HD Audio output with SST)', 'Stereo Mix (Realtek HD Audio Stereo input)', 'Microphone Array (Realtek HD Audio Mic input)', 'Headset (@System32\\drivers\\bthhfenum.sys,#2;%1 Hands-Free AG Audio%0\r\n;(JLab BT))', 'Headset (@System32\\drivers\\bthhfenum.sys,#2;%1 Hands-Free AG Audio%0\r\n;(JLab BT))', 'Microphone (VAD Wave)', 'Line Out (VAD Wave)']
My working microphones are: AttributeError: type object 'Microphone' has no attribute 'list_working_microphones' but all of them should be working
I have not installed PocketSphinx

stereo microphone could not be supported


Font awesome for cyrillic

Hey! As far as I understand, to add font avesome icons for sidebar items, I need to specify their id in the css file. But my site in Cyrillic and the sidebar elements id looks like this:
https://prnt.sc/12bdgh8
is there any other way to add icons to menu items ?

This is more of a MediaWiki and CSS issue, than a skin issue (the skin doesn't affect how the CSS is written/targeted for Cyrillic). There are not other unique identifiers in the skin for this. I did a search and found this though, I thought it might be helpful as it should resolve the issue and allow you to target these page names:
https://stackoverflow.com/questions/69411683/mediawiki-how-to-add-image-icon-in-a-sidebar-for-each-menu-if-the-menu-is-in


Chars not show correctly

Issue Type: Bug

Open a file with this word as example -> a�oacademico
character ? should be the letter ñ

Previous version was working ok.
Azure Data Studio version: azuredatastudio 1.1.4 (5d6390505643df3edd6f734c80082006efbeff5e, 2018-10-29T20:34:47.838Z)
OS version: Windows_NT x64 6.3.9600
Extensions: none

chars sqlop.txt

I wasn't able to repro using the provided txt file.  Do I need to be in specific locale or keyboard layout?
In general, this type of editor functionality comes from VS Code, so unless the issue is only in Azure Data Studio (and not VS Code), we'd likely recommend getting the issue fixed upstream.

Same issue vscode, i was not aware of that.
I have Español Argentina as main and English United States second.
When i open the file with other editors like notepad it works ok.

Encoding of the file (chars sqlop.txt) that vscode can't open is ANSI
Encoding of the file that vscode opens is UTF-8

@ramons03 thanks for the additional info.  This could be related to encoding settings we override in Azure Data Studio, though I'm not aware of any modifications we've made in this area vis-à-vis VS Code.  I'll take a closer look.

I think is fixed, version 1.4.5

Added this to fix.

@ramons03 thanks for publishing the workaround!  I'll close this older issue as resolved by adding the autoGuessEncoding setting.


[BUG] - Are nested suites supported?

Testdeck Version
0.0.6
Testdeck Package

[+] @testdeck/core
[+] @testdeck/mocha
[+] @testdeck/jasmine
[ ] @testdeck/jest
[ ] unsure

NodeJS Version

[+] 11
[ ] 10
[ ] 9
[ ] 8
[ ] all
[ ] other:

Mocha / Jasmine / Jest Version

Mocha:
@types/mocha: ^5.2.7
Jasmine:
@types/jasmine: ^3.4.0

Operating System

[ ] Linux
[+] Mac OS X
[ ] Windows 7
[ ] Windows 10
[ ] Other:

Actual Behaviour
Documentation describes
https://testdeck.org/pages/guide/nested
While in your favourite test framework you might be using nested describe, when using Testdeck you should use suite instead. And while you can still use describe, you should use suite, only. The rationale here being that we may add support for test frameworks that do not support describe.

There are 2 problems with this:

example does not compile, it is missing a closing ):

import { suite, test } from '@testdeck/jasmine';

suite('a suite', function() {

  suite('nested suite', function () {

    @suite
    class DeeplyNestedSuite {

      @test
      failingTest() {

        throw new Error('not implemented yet');
      }
    }
  }**);**
});

When this example is run - it produces 0 tests

Expected Behaviour

Example is corrected
Nested suite declarations work as described

@artemdanylenko Thank your very much for finding this. This part of the documentation was made in a hurry and the provided examples have not been tested at all. Shame on me
Once the missing closing bracket and semicolon have been added, running the test will show that the tests will not be run.
This is due to the fact, that Mocha, Jasmine and Jest do not run any test suites that do not have any tests in them.
And having a nested suite as is presented in the non working example, will make all of the three frameworks skip the nested suite.
The actually works as expected but we surely want suite to behave in the same way.
describe("outer", function() {

  describe("inner", function() {

     it("should work", function () {

       throw new Error("but does not");
     });
  });
}));

https://github.com/testdeck/testdeck-site/pull/43