Car racing game

This is a simple yet interesting rasing game with some good sound and visual effect.

This is a simple yet interesting rasing game with some good sound and visual effect.

Follow the instructions, create an issue with proper format first

This is a simple yet interesting rasing game with some good sound and visual effect.

Follow the instructions, create an issue with proper format first

Will do it

This PR is referred to issue number #124
@Yourstruggle11  Try to use reference/mention your PR to respective the issues so that mentors can merge it easily.

@Jaideep25-tech Please merge pending PRs

@nandini7637 @Jaideep25-tech any update?


Support for non-global clients

As mentioned in the README, p4runtime-shell does not support controlling multiple switches at the same time.
Is there any work planned or interest to change that?
As far as I can see, the main change would be removing the dependence on the "singleton" instances: p4runtime_sh.shell.Client and p4runtime_sh.context.Context.
Since there is a lot of meta-programming involved (i.e., passing constructors around, creating class instances dynamically), this is not as straightforward as anticipated.
Apart from that: thanks for the library! Easy to use and apart from the single-switch limitation very useful.

@davidgengenbach thanks for the feedback. This was mostly used to be meant as an interactive shell, thus the single switch limitation. I agree that it would be nice to be able to support multiple devices when writing scripts, as the syntax for p4runtime-shell is pretty intuitive and concise. Especially if you need to program multiple switches with static entries in a symmetric fashion.
Another key item which is missing from p4runtime-shell is some form of support for P4Runtime stream messages. These days however I mostly dedicate my spare time to https://github.com/antoninbas/p4runtime-go-client.
If someone wants to pick up these work items, I am happy to review PRs.

@antoninbas Thanks for the fast answer!
I started de-coupling the client/context from the types. Here is my current approach which should not break the current prompt - apart from the following exceptions:

p4runtime_sh.shell.client was renamed to p4runtime_sh.shell.global_client
p4_runtime_sh.shell.context was moved into the context field on P4RuntimeClient

So, if library users use p4_runtime_sh.shell.client and p4_runtime_sh.shell.context directly (which is not documented in the README), they will get undefined-errors.
While this is a breaking change, I am convinced that moving the Context into the P4RuntimeClient is the right way since the context is closely coupled to the client. For example, when setting the forwarding config via the P4RuntimeClient, the Context should be adapted as well.
To make this clear, we can introduce versioning, e.g., by tagging the repo in the current state as v1 and directly moving to v2 with my changes.
Here are my changes:
https://github.com/p4lang/p4runtime-shell/compare/master...davidgengenbach:master


Provide DDL auto-generated when creating a new VDB file

CREATE DATABASE {name} OPTIONS (ANNOTATION 'provide your description here..');
USE DATABASE {name};

CREATE VIRTUAL SCHEMA {name};
SET SCHEMA {name};

CREATE VIEW SAMPLE
  AS  SELECT 1 as valid;

see https://docs.google.com/document/d/1N_2YpFdnoRhMInmESEHk01TtCGm9hfursM0MPLQwVSs/edit#bookmark=id.d9goxmxbmbt0

see #67


Mania should be eligible for wrath upgrade

See jorbs stream from 12/7,
https://clips.twitch.tv/EsteemedSpunkyWrenCopyThis

Fixed by 9121810


Update aad webapp sample

Remove AAD backend samples and create webapp sample to support v2 endpoints only. The webapp sample project covers the following features of aad auto-configuration:

Access control on user groups.
Visit multiple resources.
On-demand authorization.

/azp run java - spring - tests


Add Awesome React

Category

[ ] Documentation
[x] Resource Addition

Description

We need to add Awesome React under 'Beginner-Friendly Repositories'.
Name: Awesome React
Link: https://github.com/enaqx/awesome-react

Hi , I want to handle this task.
As per below screenshot , I will add the Awesome React where i draw the red line.

Thank you for assigning the task to me.
Kindly see my pull request

Hey @2div, I've added some suggestions in the PR comments.
Check it out.

Hey @Sriparno08  I have updated the PR , kindly review it .
Thank you


"Error: Connection got disposed" on save

When I try to save a file I get the following error output:
[Error - 4:14:31 PM] Connection to server got closed. Server will not be restarted.
[Error - 4:14:31 PM] Request textDocument/formatting failed.
Error: Connection got disposed.
	at Object.dispose (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/main.js:825:25)
	at Object.dispose (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-languageclient/lib/client.js:57:35)
	at LanguageClient.handleConnectionClosed (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-languageclient/lib/client.js:1954:42)
	at LanguageClient.handleConnectionClosed (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-languageclient/lib/main.js:126:15)
	at closeHandler (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-languageclient/lib/client.js:1941:18)
	at CallbackList.invoke (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/events.js:71:39)
	at Emitter.fire (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/events.js:135:36)
	at closeHandler (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/main.js:221:26)
	at CallbackList.invoke (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/events.js:71:39)
	at Emitter.fire (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/events.js:135:36)
	at IPCMessageReader.AbstractMessageReader.fireClose (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/messageReader.js:135:27)
	at ChildProcess.<anonymous> (/Users/[redacted]/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/messageReader.js:253:61)
	at emitTwo (events.js:131:20)
	at ChildProcess.emit (events.js:214:7)
	at maybeClose (internal/child_process.js:925:16)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)

The syntax highlighting works but I'm not sure if anything else does.
I've installed reason according to the instructions at https://reasonml.github.io/docs/en/installation.
This is just yarn global add bs-platform.
Also the link in the readme of this project (in section https://github.com/reasonml-editor/vscode-reasonml#reason) is outdated, I can send a pull request to update it if you want.

I also have this problem.
Workaround: The part crashing is the formatter. In your settings, use this to prevent autoformatting OCaml files:
  "[ocaml]": {
    "editor.formatOnSave": false
  },

You may need to add another block for ReasonML, if you are using that.

It's probably replicated with #142

Formatting on save for OCaml requires having ocp-indent installed (usually via opam). That may be why you are seeing this error.

@freebroccolo I actually encounter this issue today myself. 😆
Would you mind pointing out where is the entry point to "provide some better feedback about this in upcoming versions." so we can probably solve this?

I'm still getting this error even with ocp-indent installed.

@freebroccolo Is there an update on this?
Here's a snippet of my errors:
[Error - 7:37:57 PM] Connection to server got closed. Server will not be restarted.
[Error - 7:37:57 PM] Request textDocument/formatting failed.
Error: Connection got disposed.
	at Object.dispose (/Users/varun/.vscode/extensions/freebroccolo.reasonml-1.0.38/node_modules/vscode-jsonrpc/lib/main.js:825:25)

In your ocaml-language-server repo, you say I need ocaml version 4.02.3. Do you think that is the cause?

I fixed this issue by installing ocp-indent with opam install ocp-indent.

Fixed by adding the path to ocp-indent to settings.json:
{
    ...
    "editor.formatOnSave": true,
    "reason.path.ocpindent": "/path/to/ocp-indent",
   ...
}


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit ad05528:
:clock10: Pending: waiting for processors (31 builds ahead of you)
:warning: Docs Build is busy, currently there are 31 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit ad05528:
:clock10: Full build: the average full build time is 7 min(s) 22 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit ad05528:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

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.


Update inscriptions.json

Fixed some wrong content.

@happyluner are you affiliated with the collection?

seems legit, as some inscriptions were replaced with identical images on lower inscription numbers


IM DUMB SORRY

SORRY LOL

It's fine, except now the fixed PlayState.hx pops up with OptionsMenu.hx line 128, 7-11, missing something again.


feat: dataspace protocol transfer-process

What this PR changes/adds
Implements contract negotiation api, spi, and transformers following :dsp:dsp-catalog.
:data-protocols:dsp:dsp-transfer-process:dsp-transfer-process-api
:data-protocols:dsp:dsp-transfer-process:dsp-transfer-process-spi
:data-protocols:dsp:dsp-transfer-process:dsp-transfer-process-transform
:data-protocols:dsp:dsp-transfer-process:dsp-transfer-process-http-dispatcher
Why it does that
Support the dataspace protocol specification.
Further notes
Linked Issue(s)
Relates # 2474
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

Codecov Report
Patch coverage has no change and project coverage change: -53.46 :warning:

Comparison is base (a9341b6) 64.67% compared to head (e2cef1a) 11.21%.

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

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #2711       +/-   ##
===========================================
- Coverage   64.67%   11.21%   -53.46%
===========================================
  Files         933      961       +28
  Lines       19183    19746      +563
  Branches     1161     1178       +17
===========================================
- Hits        12406     2215    -10191
- Misses       6321    17440    +11119
+ Partials      456       91      -365

Impacted Files
Coverage Δ

...erprocess/api/DspTransferProcessApiController.java
0.00% <0.00%> (ø)

...ferprocess/api/DspTransferProcessApiExtension.java
0.00% <0.00%> (ø)

...patcher/DspTransferProcessDispatcherExtension.java
0.00% <0.00%> (ø)

...ispatcher/delegate/TransferCompletionDelegate.java
0.00% <0.00%> (ø)

...s/dispatcher/delegate/TransferRequestDelegate.java
0.00% <0.00%> (ø)

...ess/dispatcher/delegate/TransferStartDelegate.java
0.00% <0.00%> (ø)

...spatcher/delegate/TransferTerminationDelegate.java
0.00% <0.00%> (ø)

...nsformer/DspTransferProcessTransformExtension.java
0.00% <0.00%> (ø)

...bjectFromTransferCompletionMessageTransformer.java
0.00% <0.00%> (ø)

...from/JsonObjectFromTransferProcessTransformer.java
0.00% <0.00%> (ø)

... and 3 more

... and 618 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Superseded by PRs #2759, #2760 and #2784


replacement for 'for x in range' in cli

accept multivalued parameters/arguments in sample(), sample every combination

it has been replaced


Tests

Now that the APIs / features are starting to stabilize, I'd appreciate some help with test coverage (of which there is currently none).
Largely stable features:

Occlusion Collection
Infinite Scroll
Proxied Each
Occlusion Item
async-image

Any features that aren't stable won't be exposed in /app during a release.

Closing in favor of more specific testing tickets


Small typo error on some FQDN

There are 2 dot instead of one in the following FQDNs :
azds-..azds.io
*.gk..azmk8s.io

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

ID: a38439d0-0125-3445-1c0a-a03b940e315d
Version Independent ID: c6436a35-94b9-6396-3b13-9291f0a17b21
Content: Restrict egress traffic in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/limit-egress-traffic.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

@squasta Thanks for the feedback! We are currently investigating and will get back on this.


Add \r before \n.

It might not be easy, but it would be nice to output a CR before LF, to avoid having to do this in drivers (https://github.com/micro-os-plus/sifive-hifive1-board-xpack/issues/3).

Fixed on 2021-03-04.


Fix stub conversion factor

Motivation
Further debug for writing proper conversion factors to an ElectricalSeries run under stub_test=True mode. In general, any use of a SubRecording or SubSorting does not copy properties, including gains, from the parent class.
How to test the behavior?
I added new tests specifically for this behavior, at least with the Neuroscope interface. I think most others set their gains automatically rather than manually. I can extend it to other interfaces if you want, though.
Checklist

[X] Have you checked our Contributing document?
[X] Have you ensured the PR description clearly describes the problem and solutions?
[X] Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?

Unlisting as it's unclear how or if this is necessary in the new writers. Used it to fix the latest Buzsaki conversion, though.


fix: compiler cannot cleanup

Related: https://github.com/dai-shi/waku/pull/559

@himself65 Thanks for the PR. Could you provide some more context on what the issue is and how this change fixes it?
I can sort of see how createCompiler is better placed in the buildStart() hook, but I don't think the !compiler check is achieving anything here. Were you observing the compiler being recreated, leading to a bug?

@himself65 Thanks for the PR. Could you provide some more context on what the issue is and how this change fixes it?
I can sort of see how createCompiler is better placed in the buildStart() hook, but I don't think the !compiler check is achieving anything here. Were you observing the compiler being recreated, leading to a bug?

Yeah, the issue is when we call resolveConfig in node.js, buildEnd won't be called in this case, so that the node.js process cannot exit successfully

!compiler check

Oh, that is my mistake

@himself65 Thanks for the PR. Could you provide some more context on what the issue is and how this change fixes it?
I can sort of see how createCompiler is better placed in the buildStart() hook, but I don't think the !compiler check is achieving anything here. Were you observing the compiler being recreated, leading to a bug?

Yeah, the issue is when we call resolveConfig in node.js, buildEnd won't be called in this case, so that the node.js process cannot exit successfully

Oh I understand now. So resolveConfig calls the configResolved hooks of plugins, so a compiler is created but never destroyed. Makes sense to me. I'll add a changeset.

@himself65 This has been released https://github.com/vanilla-extract-css/vanilla-extract/releases/tag/%40vanilla-extract/vite-plugin%404.0.5


{format} parameter in oembed URL is not replaced by actual format (json)

@remark-embedder/transformer-oembed version: 1.0.1
node version: v14.17.0
npm version: 6.14.13

Problem description:
This plugin doesn't replace {format} parameter in oembed URL.
Expected URL:
https://vimeo.com/api/oembed.json?URL
Actual URL:
https://vimeo.com/api/oembed.%7Bformat%7D?URL
Error message:
(node:169898) UnhandledPromiseRejectionWarning: FetchError: The following error occurred while processing `https://vimeo.com/66520064` with the remark-embedder transformer `@remark-embedder/transformer-oembed`:

invalid json response body at https://vimeo.com/api/oembed.%7Bformat%7D?url=https%3A%2F%2Fvimeo.com%2F66520064&maxwidth=640&maxheight=480&format=json reason: Unexpected token < in JSON at position 0
    at /home/vlisivka/workspace/vlisivka.github.io/node_modules/minipass-fetch/lib/body.js:77:31
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Object.getHTML (/home/vlisivka/workspace/vlisivka.github.io/node_modules/@remark-embedder/transformer-oembed/dist/index.js:87:18)
    at async /home/vlisivka/workspace/vlisivka.github.io/node_modules/@remark-embedder/core/dist/index.js:106:20
    at async Promise.all (index 8)
    at async /home/vlisivka/workspace/vlisivka.github.io/node_modules/@remark-embedder/core/dist/index.js:158:5

Suggested solution:
Replace {format} by json.

Hi @vlisivka,
Thanks for the issue. If you'd like to dig a little deeper into things and make a pull request that'd be great. Thanks!


Adding support for nested jquery.steps wizards

Changed CSS selector for specific jquery.find calls
See working example here: http://jsfiddle.net/uu1zozc8/4/
Also, see this SO discussion: http://stackoverflow.com/questions/32360005/nested-jquery-steps-nothing-displays-on-main-next/32488611#32488611

This does not work.


feat: [M3-7579] - Design Tokens (CDS 2.0)

Description 📝
Initial pass to replace the hard-coded styles in the light.ts theme file with their corresponding design tokens, so that we can achieve consistency in styling and facilitate future theming. We will be doing more structural changes to the theme files in the near future. These design tokens are in sync with Core Design System (CDS) 2.0 decisions being made for Akamai.
Benefits:

Single source of truth for design decisions
Autocompletion
Type Checking / Inference
Design consistency across Akamai projects

Changes  🔄

New dependency "@linode/design-language-system": "^1.0.0"

https://github.com/linode/design-language-system

Updated some of our status colors in the app to use the equivalent design token
Storybook color palettes have been updated automatically.

Preview 📷

Before
After

How to test 🧪
Prerequisites

Checkout branch
yarn install && yarn build && yarn dev

Reproduction steps

Go to http://localhost:3000

Verification steps

Observe differences compared to https://cloud.linode.com/

As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[x] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[x] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

The table header looks much different, and slightly less appealing now in my opinion. Is this change to bring us into alignment with Akamai's tables?

Yes! The table will look much different once we actually apply the Table tokens. We can either decide to make that change now or in an upcoming PR. I was hesitant in doing anything drastic with this first PR and was more trying to do a 1:1 mapping.

@jaalah-akamai also you'll need a rebase

@abailly-akamai Reverted borders on several components until we can review them later and fixed the marketplace reference since our brand blues have changed. It's looking good now 👍

@jaalah-akamai do we want to wait for the next version of https://github.com/linode/design-language-system and update this PR with the latest lib improvement?

Addressed some of the feedback from @dwiley-akamai & @bnussman-akamai which I will list here (dark theme only, did not touch light theme):

Do we expect to keep the jet black background? It feels a bit jarring. And it looks like we have some stray miscoloration in the bottom left.

miscoloration (also mentioned by Banks) has been fixed
i had to re-work the jet-black/primary nav/top nav handling cause styling was a bit broken - eventually the jet black will be our top bar bg (CDS styles) but we will have to rework how the primary nav is built to make them work together. for now i lightened it some to transition over smoothly to the future CDS styles and kept the sidebar somewhat similar to what it is now (darker) to minimize impact and keep experience nice

Do we expect to keep the light gray borders/outlines on the elements? It makes the app look busier than the current dark gray borders/outlines IMO.

yes, these are the styles for CDS 2.0 which Cloud Manager is adopting now and will increase adoption in the next major update

Popovers/Menus have no contrast

yeah i agree this isn't the best experience so I added contrast back

Top Nav icon colors inconsistent

fixed!

Can we add a contrasting background color to the footer?

leaving this one out cause the light theme does not have it and i don't think we need to in the dark mode either (trying to keep themes consistent in terms of main elements)

Can we make entity icons not green?

That will be coming in the future but for now marketing/product styling is out of scope.


Rebalance shards

Description
Rebalance shards periodically.
How was this PR tested?
In progress.

I need to write more unit tests for this change, but it is ready for review.


fix: remove dummy nativeOnly

We are working on fabric support for video. This is the first one
Describe the changes
According to https://github.com/facebook/react-native/issues/28351#issuecomment-602755235, requireNativeComponent recieves only one argument since<EMAIL_ADDRESS>According to https://github.com/facebook/react-native/tree/v0.69.4/Libraries/Components/Switch, native only properties are declared in <ComponentName>NativeComponent.js, e.g. on, enabled and trackTintColor

It is WIP. I'll let you known if it is ready


[Authoring] Product landing page

Cards block layout seems to be pending yet. Needs to be inline with https://www.hlx.live/developer/block-collection/cards

@asthabh23 I have updated all the cards blocks to follow the layout. Please validate.

We are using cards only on the product listing page in both languages.

lgtm! thanks!


add sudo

Pull Request Description
Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

/test apply


Add/Update alert styles in CDS codebase

Alert styles are in the CDS figma sticker sheet and the styles need to be added to the CDS codebase or modified from the current USWDS versions.

A note on toasts (desktop alerts)

Toast notifications are common in Bootstrap and other design systems, but aren't included in USWDS or CDS at this point. In this early version of the CDS, there is no reason to use toasts-- just use the alert format. If it becomes clear that toasts are necessary to include in CDS, be sure to follow accessibility guidelines. Sheri Byrne-Haber's medium post is a good starting place.

[ ] Update visual alert styles to comport with Chicago Design System work.
[ ] We will not create a toast in v1.0.

Published the alerts implementation and added an example in the main page.


Protocol.UndefinedError exception if compress_body: true and body: nil

I'm not sure this is a bug. Obviously it does not make sense to enable body compression if there is no body. Still, I don't think the following code must necessarily raise an exception and it would be nice if this flag was just ignored if there's no body. WDYT?
Req.get("https://elixir-lang.org/", compress_body: true)

raises
** (Protocol.UndefinedError) protocol Enumerable not implemented for nil of type Atom. This protocol is implemented for the following type(s): Date.Range, File.Stream, Function, GenEvent.Stream, HashDict, HashSet, IO.Stream, Jason.OrderedObject, List, Map, MapSet, Range, Stream
    (elixir 1.15.7) lib/enum.ex:1: Enumerable.impl_for!/1
    (elixir 1.15.7) lib/enum.ex:166: Enumerable.reduce/3
    (elixir 1.15.7) lib/stream.ex:1052: Stream.do_transform_inner_enum/7
    (elixir 1.15.7) lib/stream.ex:943: Stream.do_transform/5
    (elixir 1.15.7) lib/enum.ex:2564: Enum.reduce_while/3
    (finch 0.18.0) lib/finch/http1/conn.ex:176: Finch.HTTP1.Conn.maybe_stream_request_body/3
    (finch 0.18.0) lib/finch/http1/conn.ex:123: Finch.HTTP1.Conn.request/8
    #cell:43zgvxi7euwwfbd2:1: (file)

Nice catch, fixed on main!


Capacity Reporting Tutorial - missing required information

The Capacity Report tutorial is missing a lot of detail that would make it worthy of being called a tutorial. These are more generalized shorthand notes. I'm trying to follow along and it's really difficult since the specific operations are never mentioned.
For example, the step "We then parse the Azure AD token response into a typed object using this JSON schema:" doesn't actually note the operation needed (it's Parse JSON).
 I have resorted to trying to match the icons.
It would also be great if the user/password authentication method could be shown, instead of mentioned as an alternative and never covered.
Overall, I find the PowerPlatform documentation to have such a high barrier for use that the target audience will be extremely small. I'd like to use the tools as they'd solve some challenges our organization has, but I'm a sysadmin, not a PowerPlatform MVP and the targeted audience seems to be experts.

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

ID: 816403f3-0104-3d3a-e889-bf0d4cf9bcae
Version Independent ID: 0f0d27e8-2aaa-0d7c-ea3e-fe949bd9b3b1
Content: Preview: Programmability and extensibility - Tutorial - Create a daily capacity report - Power Platform
Content Source: power-platform/admin/programmability-tutorial-create-daily-capacity-report.md
Service: power-platform
GitHub Login: @laneswenka
Microsoft Alias: laswenka

Hi @gbeifuss this is great feedback, and thank you for giving it a go!  We released this tutorial based on direct calls with several customers that needed to light this up using some Azure tooling.  We are in the process of improving the article to simultaneously show all tool options for each step such as REST / PowerShell / Connector with relevant details.
Wanted to acknowledge your painpoints here and we will address them over the next few article updates.


Azure Hyperscale Database does not support Change data capture

#28079 issue states that Azure hyperscale database supports Change data capture. But it looks like it is not supported.
It is listed in the below table
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/sql-database/sql-database-features.md#sql-features
FYI @Mike-Ubezzi-MSFT

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

ID: 3fb7dad4-ff47-5b16-e8ee-0a5e037ea20f
Version Independent ID: 98ec245b-bd8f-bd96-ec6d-0048599246fa
Content: Feature comparison - Azure SQL Database
Content Source: articles/sql-database/sql-database-features.md
Service: sql-database
Sub-service: service
GitHub Login: @jovanpop-msft
Microsoft Alias: jovanpop

Thanks for the feedback! I have assigned the issue to the doc author to update appropriately.

@srini1978 The Change Data Capture is supported by SQL Server and Azure SQL Database Managed Instance. It is not supported by Azure SQL Database single instance, elastic pool, or Hyperscale instances.
Change Tracking is a lightweight solution (as compared to Change Data Capture) that is supported by Azure SQL Database single instance which also includes elastic pools and Hyperscale.
Change Data Capture will let you know how many times a row has changed. Change Tracking will let you know that a row has changed. Very similar but SQL Server and Azure SQL Database Managed Instance have the transactional logs to support the Change Data Capture functionality.
I apologize for any confusion I may have caused but I think there are multiple points being discussed in the comment from the previous issue.

@srini1978 We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


fork其他代码后，可以通过go get下载并编译不需要改变代码内import引用路径

version：go.1.10.0
fork其他代码后，可以通过go get下载并编译不需要改变代码内import引用路径

This needs to go through a proposal process first and get accepted. I would request that you open a proposal issue first outlining why you need such a feature and then send a PR.


Cardenb/cardboard/unity/develop

Superseded by pull request https://github.com/rsanchezsaez/CardboardSDK-iOS/pull/3.


Deployment of 1.4.7 to production

List of changes or update,

in getTypeof update new list of type
Update unit test
Updated code comment
Update category in code
.npmignore and .gitattributes was added in the filesystem
update the function of arrayConcat, toInteger  , toDouble  ,arraySlice, repeat and isEmpty

List of new function that was added

regexCountGroup
arrayRepeat

LGTM


Is Slovak to ASCII correct?

Example: Is this correct?
"zákazník" -> "zakaznik"

Can a native speaker, please check the character-replacement, thanks.
https://github.com/voku/portable-ascii/blob/master/src/voku/helper/data/ascii_by_languages.php#L1018

I'm not a native speaker, but I've lived in Slovakia for 15 years and speak the language and can confirm that the Slovak to ASCII is correct.

Thank you for the review. :1st_place_medal:


ceph-osd: ceph-volume requires --data to be in vg/lv format

Signed-off-by: Andrew Schoen<EMAIL_ADDRESS>

Merging this so that we can verify: https://github.com/ceph/ceph/pull/17207
Kind of chicken-egg issue here, because we need this in master since ceph-volume is changing.

Already ran correctly at https://2.jenkins.ceph.com/job/ceph-ansible-scenario/3/console even though the checks here are still going.


auro-drawer; initial build

User story
As a developer, I want to be able to quickly add a drawer with content, so I can easily deliver value.
Outline subtasks or tasks

List specific steps required to deliver this work.

[ ] Address all design and UX as proposed in the design comp in relation to using Auro specifications
[ ] A11y in regards to role and live notifications need to be coded into the final WC
[ ] Review demo with the designer as well as the Auro team
[ ] All new work to be reviewed by Auro team

Definition of “Done” (exit criteria)

The story is generally “done” when the user can complete the outlined task, but make sure to define what that is.

Has been tested in all browsers

[ ] Chrome
[ ] Firefox
[ ] Edge (79 +)
[ ] Safari
[ ] Mobile Safari
[ ] IE11

Has been tested for accessibility

[ ] Screenreader
[ ] Axe
[ ] Keyboard use

Performance

[ ] Chrome Lighthhouse report

Auro component features

[ ] README doc completed with all relative information
[ ] API documentation created
[ ] Bundled version tested and documented
[ ] Examples and use case info created
[ ] Pages added to the Auro Doc Site

Audit
https://github.com/AlaskaAirlines/auro/issues/15

auro-drawer will be moved to the scope of auro-dialog to be managed in the mini-mono repo.


Update defining steps

A small re-write of some of the Defining Steps doc - trying to make it clearer, and add some more beginner-friendly info.

[x] Review remaining sections
[x] Review heading names

I think this doc could definitely still have more improvements, but I'm happy with the additions and I'm keen to get these changes out 🚢


Update Google Maps API link in README.md

Update Google Maps API link in README.md
The Google Maps API link was pointing to notion's API documentation, this update corrects it to the correct Google Maps API documentation link.

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Update Google Maps API link in README.md
The Google Maps API link was pointing to notion's API documentation, this update corrects it to the correct Google Maps API documentation link.

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not have more than 100 characters
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Wise is the best bank I have found to get paid quicky and with the best conversion rates. ...
Once I have transferred once, it becomes just few clicks to transfer money between bank accounts internationally. ...
A good option (and better alternate than Payoneer) for transferring money/payments
Get Connected Now
https://wise.com/invite/ahpc/nelsong667


Need flag to help debug toolchain resolution

Flag should cause toolchain resolution process to emit debug information:

Each toolchain considered

Why it was rejected

Final toolchain selected

Re-filed as https://github.com/bazelbuild/bazel/issues/3431


Inconsistent namespaces for backend unit tests

Hi, I've seen that there is an inconsistency of namespaces in the yii2-advanced app template.
in tests/codeception/backend/unit/TestCase.php and tests/codeception/backend/unit/DbTestCase.php the namespace defined is backend\tests\unit whereas in the the same section but for frontend tests the namespace is defined as tests\codeception\frontend\unit.
And I cannot use that class in my backend/unit/TestXXX, the following error is displayed when running codecept run for that test
PHP Fatal error:  Class 'backend\tests\unit\TestCase' not found in /vagrant/tests/codeception/backend/unit/TestXXX
Hope this helps! Thanks!

Is this bug solved? You don't mention nothing about it in the milestone.

tests in vargant folder not exists

The extension was deprecated so if the issue is still valid when using http://codeception.com/for/yii then it should be reported once again.


Add eslint-plugin-n

When making #161, I realized both that #162 was needed, and that we don't have any engines checking.
You can check engines compatible with transtives via ls-engines --mode=ideal. You can check source compatibility via eslint-plugin-n, which also includes eslint-plugin-es-x.
Combined, these tools help make sure that your code supports all versions of node that you say you do. I would assume that they'd be located under a node option though.
To make adding this non-breaking (though we don't need to avoid majors, of course), I might make sheriff options accept a Partial<SheriffSettings> anyway. Maybe even make it optional at that point. I might PR this change now, because it seems reasonable.

To make adding this non-breaking (though we don't need to avoid majors, of course), I might make sheriff options accept a Partial anyway. Maybe even make it optional at that point. I might PR this change now, because it seems reasonable.

Oh, it does that already, just in the SheriffSettings type itself. That should probably be documented though.

So, finally getting back to this too.

To make adding this non-breaking (though we don't need to avoid majors, of course), I might make sheriff options accept a Partial anyway

As you already noted, SheriffSettings already has the Partial type.

Maybe even make it optional at that point. I might PR this change now, because it seems reasonable.

Addressed in https://github.com/AndreaPontrandolfo/sheriff/pull/165.

When making https://github.com/AndreaPontrandolfo/sheriff/pull/161, I realized both that https://github.com/AndreaPontrandolfo/sheriff/pull/162 was needed, and that we don't have any engines checking.
You can check engines compatible with transtives via ls-engines --mode=ideal. You can check source compatibility via eslint-plugin-n, which also includes eslint-plugin-es-x.
Combined, these tools help make sure that your code supports all versions of node that you say you do. I would assume that they'd be located under a node option though.

So, environment checking is a tough one.
I avoided it up until now because i'm pretty sure it's gonna skyrocket the complexity of the codebase considerably.
Although, one cool thing that environment checking would enable would be structuredClone for example.
About eslint-plugin-n, what do you like about it? It seems to overlap a lot with eslint-plugin-import and seems like it would be mostly useful in Commonjs environments and only marginally useful in ESM environments.

About eslint-plugin-n, what do you like about it?

Environment checking with no-unsupported-features/* rules, no-deprecated (though eslint-plugin-deprecated is probably better?), process-exit-as-throw is probably useful, prefer-promises/* is nice (does unicorn have that one?), no-process-exit is good. Some other rules about callbacks, sync apis, oh, and I could see no-unpublished-bin as being useful.
I think it has merit in ESM environments, though it certainly does overlap with import.

This also kinda overlaps with unicorn/prefer-module.
But indeed i like some of the rules.
I'm analyzing it.

no-deprecated (though eslint-plugin-deprecated is probably better?)

Just wanted to point out that @typescript-eslint just added no-deprecated rule to their plugin, which means that we will automatically inherit that rule.
So we certainly won't be adopting the eslint-plugin-n version, going forward.


Use tracing to improve debugging experience

Use tracing like it is common for many axum server apps.
This has the following benefits:

Logs can be rerouted to files for retroactive inspection instead of console like now
Log levels can be filtered to see more or less depending on need for debugging
It is easier for us to later enhance the project with telemetry like OpenTelemetry

Ok if I create a PR based on this PR is closes that PR. Today I learned


Date and Month are swiped when use cellDates

I have date 04/03/2020 with format dd/mm/yyyy in excel, and I use it to my javascript:
var workbook = XLSX.read(data, {
                        type: 'binary',
                        cellDates: true,
                    });

and use it to convert to json:
XLSX.utils.sheet_to_json(workSheet);

but I got 03/04/2020 in the result. How can I insert excel date format before it convert?

By default SheetJS follows Excel behaviour, which is to aggressively try to intepret strings into numbers and dates.
You can set raw: true to prevent this, which should help if you're importing a CSV file or you've got dates in cells with a type of string.

Strings are parsed as dates using the JS Date parsing facilities.  They for the most part default to en-US, but the spec says:

in general, the value produced by Date.parse is implementation-defined when given any String value that does not conform to the Date Time String Format

Short of a special date parser (which may happen in the future) or rollout of the new Temporal API, @SystemParadox spelled out the best approach: just use raw: true and post-process the text.

let body = XLSX.read(buffer, { type: 'buffer', cellDates: false, raw: true });

let wb = body.Sheets[body.SheetNames[0]];

let toJson: object[] = XLSX.utils.sheet_to_json(wb, {
  blankrows: false,
  defval: '',
  raw: false,
  dateNF: 'dd/mm/yyyy'
});


accuracy drops

I trained a model with 48 hrs of speech data and acheived a training accuracy of 95%.
my network is 120 input neurons , 320X2 hidden layers and 67 output neurons.
but when I increased a speech corpus to 92 hrs of data and trained with the same network
the accuracy drops after 9 th epoch...
I tried by increasing the hidden layers to 3 but the same problem
[NOTE] TOKEN_ACCURACY refers to token accuracy, i.e., (1.0 - token_error_rate).
EPOCH 1 RUNNING ... ENDS [2017-Feb-1 11:50:23]: lrate 0.0001, TRAIN ACCURACY 48.5447%, VALID ACCURACY 19.5833%
19.5833
EPOCH 2 RUNNING ... ENDS [2017-Feb-1 15:07:33]: lrate 0.0001, TRAIN ACCURACY 63.9544%, VALID ACCURACY 27.6291%
8.0458
EPOCH 3 RUNNING ... ENDS [2017-Feb-1 19:18:59]: lrate 0.0001, TRAIN ACCURACY 68.8720%, VALID ACCURACY 28.3032%
.6741
EPOCH 4 RUNNING ... ENDS [2017-Feb-1 22:49:47]: lrate 0.0001, TRAIN ACCURACY 69.9686%, VALID ACCURACY 35.5108%
7.2076
EPOCH 5 RUNNING ... ENDS [2017-Feb-2 00:59:58]: lrate 0.0001, TRAIN ACCURACY 72.8117%, VALID ACCURACY 29.4805%
-6.0303
EPOCH 6 RUNNING ... ENDS [2017-Feb-2 03:09:58]: lrate 0.0001, TRAIN ACCURACY 72.5447%, VALID ACCURACY 26.6869%
-2.7936
EPOCH 7 RUNNING ... ENDS [2017-Feb-2 05:20:23]: lrate 0.0001, TRAIN ACCURACY 73.6803%, VALID ACCURACY 28.0352%
1.3483
EPOCH 8 RUNNING ... ENDS [2017-Feb-2 07:30:45]: lrate 0.0001, TRAIN ACCURACY 73.9509%, VALID ACCURACY 30.8868%
2.8516
EPOCH 9 RUNNING ... ENDS [2017-Feb-2 09:41:22]: lrate 0.0001, TRAIN ACCURACY 71.7453%, VALID ACCURACY 22.9801%
-7.9067
EPOCH 10 RUNNING ... ENDS [2017-Feb-2 11:54:40]: lrate 0.0001, TRAIN ACCURACY 68.3523%, VALID ACCURACY 22.7060%
-.2741
EPOCH 11 RUNNING ... ENDS [2017-Feb-2 15:10:57]: lrate 0.0001, TRAIN ACCURACY 63.5763%, VALID ACCURACY 26.8709%
4.1649
EPOCH 12 RUNNING ... ENDS [2017-Feb-2 19:30:44]: lrate 0.0001, TRAIN ACCURACY 58.2389%, VALID ACCURACY 19.8774%
-6.9935
EPOCH 13 RUNNING ... ENDS [2017-Feb-2 21:41:14]: lrate 0.0001, TRAIN ACCURACY 56.0561%, VALID ACCURACY 21.4257%
1.5483
EPOCH 14 RUNNING ... ENDS [2017-Feb-2 23:52:22]: lrate 0.0001, TRAIN ACCURACY 54.3079%, VALID ACCURACY 14.6172%
kindly help me to resolve this problem.

Aside from the obvious observation: something about the additional data is hurting, rather than helping (are the transcriptions accurate? Is the data noisy? were the features computed properly?)
Usually decreasing accuracy with repeated epochs means it's time to start decreasing the learning rate.
But that doesn't explain how the accuracies are so much lower with respect to the earlier, smaller data set.
It would help to see output from the same first 14 epochs of the experiment that gets 95% training accuracy. Is this newer experiment consistently more slow to improve than the earlier one? That would suggest (to me) the additional data is reducing performance "from the beginning"
Phrased differently: the accuracy shown here peaks at epoch 8. How well was the better-results experiment doing around epoch 8? And assuming all other things are equal. (It's less helpful to compare training accuracy history for completely different network dimesnionalities / topologies - this would be one of those "all other things" that should be kept equal across comparisons)
My colleagues might have better advice, but thanks for listening!

Did you look at the training logs of the 9th iteration. Do you have overflows, NaNs, or simialr events?

thanks for your replies,
are the transcriptions accurate?
yes, manually verified
Is the data noisy?
no, recorded in room environment
were the features computed properly?
how to check this
It would help to see output from the same first 14 epochs of the experiment that gets 95% training accuracy.
TRAINING STARTS [2016-Aug-1 14:27:24]
[NOTE] TOKEN_ACCURACY refers to token accuracy, i.e., (1.0 - token_error_rate).
EPOCH 1 RUNNING ... ENDS [2016-Aug-1 15:31:14]: lrate 0.0001, TRAIN ACCURACY 55.4951%, VALID ACCURACY 56.5166%
56.5166
EPOCH 2 RUNNING ... ENDS [2016-Aug-1 16:34:04]: lrate 0.0001, TRAIN ACCURACY 71.6535%, VALID ACCURACY 61.8603%
5.3437
EPOCH 3 RUNNING ... ENDS [2016-Aug-1 17:36:04]: lrate 0.0001, TRAIN ACCURACY 76.2801%, VALID ACCURACY 57.3913%
-4.4690
EPOCH 4 RUNNING ... ENDS [2016-Aug-1 18:38:19]: lrate 0.0001, TRAIN ACCURACY 77.8907%, VALID ACCURACY 59.2572%
1.8659
EPOCH 5 RUNNING ... ENDS [2016-Aug-1 19:41:17]: lrate 0.0001, TRAIN ACCURACY 80.9326%, VALID ACCURACY 70.5037%
11.2465
EPOCH 6 RUNNING ... ENDS [2016-Aug-1 20:43:11]: lrate 0.0001, TRAIN ACCURACY 83.6738%, VALID ACCURACY 71.2827%
.7790
EPOCH 7 RUNNING ... ENDS [2016-Aug-1 21:46:57]: lrate 0.0001, TRAIN ACCURACY 85.2399%, VALID ACCURACY 70.5964%
-.6863
EPOCH 8 RUNNING ... ENDS [2016-Aug-1 22:49:30]: lrate 0.0001, TRAIN ACCURACY 86.6232%, VALID ACCURACY 72.4414%
1.8450
EPOCH 9 RUNNING ... ENDS [2016-Aug-1 23:51:59]: lrate 0.0001, TRAIN ACCURACY 87.9396%, VALID ACCURACY 71.3305%
-1.1109
EPOCH 10 RUNNING ... ENDS [2016-Aug-2 00:54:33]: lrate 0.0001, TRAIN ACCURACY 88.9618%, VALID ACCURACY 74.6288%
3.2983
EPOCH 11 RUNNING ... ENDS [2016-Aug-2 01:56:34]: lrate 0.0001, TRAIN ACCURACY 89.4648%, VALID ACCURACY 74.8456%
.2168
EPOCH 12 RUNNING ... ENDS [2016-Aug-2 02:59:15]: lrate 0.0001, TRAIN ACCURACY 90.1297%, VALID ACCURACY 75.3002%
.4546
EPOCH 13 RUNNING ... ENDS [2016-Aug-2 04:01:34]: lrate 0.0001, TRAIN ACCURACY 90.8215%, VALID ACCURACY 75.9864%
.6862
EPOCH 14 RUNNING ... ENDS [2016-Aug-2 05:03:47]: lrate 0.0001, TRAIN ACCURACY 91.5229%, VALID ACCURACY 75.9371%
-.0493
EPOCH 15 RUNNING ... ENDS [2016-Aug-2 06:06:00]: lrate 5e-05, TRAIN ACCURACY 92.4408%, VALID ACCURACY 78.0527%
2.1156
EPOCH 16 RUNNING ... ENDS [2016-Aug-2 07:08:49]: lrate 2.5e-05, TRAIN ACCURACY 93.5363%, VALID ACCURACY 81.5185%
3.4658
EPOCH 17 RUNNING ... ENDS [2016-Aug-2 08:11:18]: lrate 1.25e-05, TRAIN ACCURACY 94.7391%, VALID ACCURACY 82.6712%
1.1527
EPOCH 18 RUNNING ... ENDS [2016-Aug-2 09:13:46]: lrate 6.25e-06, TRAIN ACCURACY 95.1161%, VALID ACCURACY 83.3665%
.6953
EPOCH 19 RUNNING ... ENDS [2016-Aug-2 10:16:07]: lrate 3.125e-06, TRAIN ACCURACY 95.2809%, VALID ACCURACY 83.8659%
.4994
EPOCH 20 RUNNING ... ENDS [2016-Aug-2 11:18:41]: lrate 1.5625e-06, TRAIN ACCURACY 95.3487%, VALID ACCURACY 84.3054%
.4395
EPOCH 21 RUNNING ... ENDS [2016-Aug-2 12:21:28]: lrate 7.8125e-07, TRAIN ACCURACY 95.3613%, VALID ACCURACY 84.5342%
.2288
EPOCH 22 RUNNING ... ENDS [2016-Aug-2 13:24:32]: lrate 3.90625e-07, TRAIN ACCURACY 95.3678%, VALID ACCURACY 84.7151%
.1809
EPOCH 23 RUNNING ... ENDS [2016-Aug-2 14:27:07]: lrate 1.95313e-07, TRAIN ACCURACY 95.3934%, VALID ACCURACY 84.8287%
.1136
EPOCH 24 RUNNING ... ENDS [2016-Aug-2 15:30:22]: lrate 9.76565e-08, TRAIN ACCURACY 95.4279%, VALID ACCURACY 84.8841%
.0554
finished, too small rel. improvement .0554
Training succeeded. The final model exp/train_phn_l2_c320/final.nnet
Is this newer experiment consistently more slow to improve than the earlier one?
yes
Did you look at the training logs of the 9th iteration. Do you have overflows, NaNs, or simialr events?
No such events
tr.iter9.txt

All your weights are completely saturated in each LSTM layer, i.e. you have min=-50 and max=50 in the networks. You can reduce this with --max-grad (or so) when you create nnet.proto. I think some data is probably corrupt. Try training only on subsets, like you would do for cross-validation to see if you can out which parts may be corrupt?

On Feb 13, 2017, at 11:31 PM, shobana<EMAIL_ADDRESS>wrote:
thanks for your replies,
are the transcriptions accurate?
yes, manually verified
Is the data noisy?
no, recorded in room environment
were the features computed properly?
how to check this
It would help to see output from the same first 14 epochs of the experiment that gets 95% training accuracy.
TRAINING STARTS [2016-Aug-1 14:27:24]
[NOTE] TOKEN_ACCURACY refers to token accuracy, i.e., (1.0 - token_error_rate).
EPOCH 1 RUNNING ... ENDS [2016-Aug-1 15:31:14]: lrate 0.0001, TRAIN ACCURACY 55.4951%, VALID ACCURACY 56.5166%
56.5166
EPOCH 2 RUNNING ... ENDS [2016-Aug-1 16:34:04]: lrate 0.0001, TRAIN ACCURACY 71.6535%, VALID ACCURACY 61.8603%
5.3437
EPOCH 3 RUNNING ... ENDS [2016-Aug-1 17:36:04]: lrate 0.0001, TRAIN ACCURACY 76.2801%, VALID ACCURACY 57.3913%
-4.4690
EPOCH 4 RUNNING ... ENDS [2016-Aug-1 18:38:19]: lrate 0.0001, TRAIN ACCURACY 77.8907%, VALID ACCURACY 59.2572%
1.8659
EPOCH 5 RUNNING ... ENDS [2016-Aug-1 19:41:17]: lrate 0.0001, TRAIN ACCURACY 80.9326%, VALID ACCURACY 70.5037%
11.2465
EPOCH 6 RUNNING ... ENDS [2016-Aug-1 20:43:11]: lrate 0.0001, TRAIN ACCURACY 83.6738%, VALID ACCURACY 71.2827%
.7790
EPOCH 7 RUNNING ... ENDS [2016-Aug-1 21:46:57]: lrate 0.0001, TRAIN ACCURACY 85.2399%, VALID ACCURACY 70.5964%
-.6863
EPOCH 8 RUNNING ... ENDS [2016-Aug-1 22:49:30]: lrate 0.0001, TRAIN ACCURACY 86.6232%, VALID ACCURACY 72.4414%
1.8450
EPOCH 9 RUNNING ... ENDS [2016-Aug-1 23:51:59]: lrate 0.0001, TRAIN ACCURACY 87.9396%, VALID ACCURACY 71.3305%
-1.1109
EPOCH 10 RUNNING ... ENDS [2016-Aug-2 00:54:33]: lrate 0.0001, TRAIN ACCURACY 88.9618%, VALID ACCURACY 74.6288%
3.2983
EPOCH 11 RUNNING ... ENDS [2016-Aug-2 01:56:34]: lrate 0.0001, TRAIN ACCURACY 89.4648%, VALID ACCURACY 74.8456%
.2168
EPOCH 12 RUNNING ... ENDS [2016-Aug-2 02:59:15]: lrate 0.0001, TRAIN ACCURACY 90.1297%, VALID ACCURACY 75.3002%
.4546
EPOCH 13 RUNNING ... ENDS [2016-Aug-2 04:01:34]: lrate 0.0001, TRAIN ACCURACY 90.8215%, VALID ACCURACY 75.9864%
.6862
EPOCH 14 RUNNING ... ENDS [2016-Aug-2 05:03:47]: lrate 0.0001, TRAIN ACCURACY 91.5229%, VALID ACCURACY 75.9371%
-.0493
EPOCH 15 RUNNING ... ENDS [2016-Aug-2 06:06:00]: lrate 5e-05, TRAIN ACCURACY 92.4408%, VALID ACCURACY 78.0527%
2.1156
EPOCH 16 RUNNING ... ENDS [2016-Aug-2 07:08:49]: lrate 2.5e-05, TRAIN ACCURACY 93.5363%, VALID ACCURACY 81.5185%
3.4658
EPOCH 17 RUNNING ... ENDS [2016-Aug-2 08:11:18]: lrate 1.25e-05, TRAIN ACCURACY 94.7391%, VALID ACCURACY 82.6712%
1.1527
EPOCH 18 RUNNING ... ENDS [2016-Aug-2 09:13:46]: lrate 6.25e-06, TRAIN ACCURACY 95.1161%, VALID ACCURACY 83.3665%
.6953
EPOCH 19 RUNNING ... ENDS [2016-Aug-2 10:16:07]: lrate 3.125e-06, TRAIN ACCURACY 95.2809%, VALID ACCURACY 83.8659%
.4994
EPOCH 20 RUNNING ... ENDS [2016-Aug-2 11:18:41]: lrate 1.5625e-06, TRAIN ACCURACY 95.3487%, VALID ACCURACY 84.3054%
.4395
EPOCH 21 RUNNING ... ENDS [2016-Aug-2 12:21:28]: lrate 7.8125e-07, TRAIN ACCURACY 95.3613%, VALID ACCURACY 84.5342%
.2288
EPOCH 22 RUNNING ... ENDS [2016-Aug-2 13:24:32]: lrate 3.90625e-07, TRAIN ACCURACY 95.3678%, VALID ACCURACY 84.7151%
.1809
EPOCH 23 RUNNING ... ENDS [2016-Aug-2 14:27:07]: lrate 1.95313e-07, TRAIN ACCURACY 95.3934%, VALID ACCURACY 84.8287%
.1136
EPOCH 24 RUNNING ... ENDS [2016-Aug-2 15:30:22]: lrate 9.76565e-08, TRAIN ACCURACY 95.4279%, VALID ACCURACY 84.8841%
.0554
finished, too small rel. improvement .0554
Training succeeded. The final model exp/train_phn_l2_c320/final.nnet
Is this newer experiment consistently more slow to improve than the earlier one?
yes
Did you look at the training logs of the 9th iteration. Do you have overflows, NaNs, or simialr events?
No such events
tr.iter9.txt https://github.com/srvk/eesen/files/773141/tr.iter9.txt
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/srvk/eesen/issues/122#issuecomment-279605406, or mute the thread https://github.com/notifications/unsubscribe-auth/AEnA8cPmC0I12jBHjJ0dFIk28Zg3RmYBks5rcS4XgaJpZM4L_Emd.

Florian Metze http://www.cs.cmu.edu/directory/florian-metze
Associate Research Professor
Carnegie Mellon University


Component/primary button

Closes #6
Adds PrimaryButton component

Yeah no problem, good points.
I've added a focus/active outline, let me know what you think. The outline radius wasn't working on Chrome so looked a bit funny. Happy to change it if you had something in mind for buttons.

Yeah no problem, good points.
I've added a focus/active outline, let me know what you think. The outline radius wasn't working on Chrome so looked a bit funny. Happy to change it if you had something in mind for buttons.


Error detected while processing BufReadPost Autocommands for "*.cpp".When i open nvim

Version confirmation

[X] Confirm

Following prerequisites

[X] Confirm

Neovim version
NVIM v0.9.1 Build type: Release LuaJIT 2.1.0-beta3
Operating system/version
Ubuntu 22.04.2 LTS
Terminal name/version
kitty 0.21.2 created by Kovid Goyal
$TERM environment variable
xterm-kitty
Branch info
main (Default/Latest)
Fetch Preferences
HTTPS (use_ssh = false)
How to reproduce the issue

nvim a.cpp
enter
'enter'
...'enter'

Expected behavior

Actual behavior
No response
Additional information
When completing prerequisites, I can't use paru -S to install, so I can only search for them one by one on github and install it myself, not knowing if it's installed correctly.
During my installation, there was a plugin installation error, but I didn't take screenshots at the time, and I couldn't enter the plugin installation process again. Now as soon as I open NVIM, I get the error. I don't know what to do at all, and I really want to get help.

try remove the entire plugin installation folder and reopen nvim again.

And to be specific:
rm -rf ~/.local/share/nvim/site/lazy/
nvim

I just tried it and found no difference from before.
And when I tried to reinstall, I found this, it says my nvim version is 0.7 and those plugins need 0.8. but my nvim version is 0.9. and I also tried to install 0.8 and found that it still says my nvim version is 0.7.

maybe u have multiple nvim installed.

Did u use our install script to bootstrap this config? It should abort if u are on Nvim 0.7.
Anyway, enter Neovim and use CTRL-C to stop generating further error messages (if applies), then type :verbose version, what u see for this?

Yes!I found two neovim, one in /usr/ and one in my download .Perhaps I used to install nvim with nvim.appimage, and I got an empty nvim , so I did not think I have installed it.After I clean nvim in /usr/ and move my download nvim to /usr/, there is no error like before.Thanks for your help!


"Issues with 'with_epoch' Configuration Relative to 'batch_size' in Distributed Training Using PyTorch Lightning and WebDataset"

I'm currently facing an issue where I am using PyTorch Lightning with WebDataset for distributed DDP training. When I don't use the dataloader and set with_epoch, it's set for each sample. However, when I specify batch_size in the dataloader, with_epoch becomes the number of batches. Could you please explain this situation? code as follows
###this is a single dataset
dataset = wds.WebDataset(expand_urls(urls),
                                nodesplitter=wds.split_by_node,
                                shardshuffle=True,
                                resampled=True,
                                cache_dir=cache_dir,
                              ).select(corrupt_filter)

###mixed dataset
class MixedWebDataset(wds.WebDataset):
    def __init__(self, cfg: CfgNode, dataset_cfg: CfgNode, train: bool = True) -> None:
        super(wds.WebDataset, self).__init__()
        dataset_list = cfg.DATASETS.TRAIN if train else cfg.DATASETS.VAL
        datasets = [create_webdataset(cfg, dataset_cfg[dataset], train=train) for dataset, v in dataset_list.items()]
        weights = np.array([v.WEIGHT for dataset, v in dataset_list.items()])
        weights = weights / weights.sum()  # normalize
        self.append(wds.RandomMix(datasets, weights))

self.train_dataset = MixedWebDataset(self.cfg, self.dataset_cfg, train=True).with_epoch(100_000).shuffle(4000)
train_dataloader = torch.utils.data.DataLoader(self.train_dataset, self.cfg.TRAIN.BATCH_SIZE, drop_last=True, num_workers=self.cfg.GENERAL.NUM_WORKERS, prefetch_factor=self.cfg.GENERAL.PREFETCH_FACTOR)

Experiments on eight A100 GPUs one node

That's correct: "with_epoch" just slices the stream based on items, not samples. You'll have to divide the desired epoch size by the batch size.
Is there any reason this might be a problem?


Rewrite providing much simpler api

Codecov Report

Merging #55 (7715093) into master (2ddf1ec) will decrease coverage by 2.23%.
The diff coverage is 85.63%.

@@            Coverage Diff             @@
##           master      #55      +/-   ##
==========================================
- Coverage   88.68%   86.44%   -2.24%
==========================================
  Files          39       54      +15
  Lines         654      723      +69
  Branches       59       69      +10
==========================================
+ Hits          580      625      +45
- Misses         27       45      +18
- Partials       47       53       +6

Impacted Files
Coverage Δ

packages/core/src/context/SingletonScope.ts
83.33% <ø> (ø)

packages/react/src/components/ContainerScope.tsx
85.71% <ø> (ø)

packages/react/src/hoc/withScope.tsx
80.00% <ø> (ø)

...ages/core/src/strategies/abstract/BuildStrategy.ts
54.54% <44.44%> (-45.46%)
:arrow_down:

packages/core/src/container/ServiceLocator.ts
68.00% <61.53%> (-26.12%)
:arrow_down:

packages/react/src/hooks/useObservable.ts
91.66% <66.66%> (ø)

packages/core/src/context/AsyncInstancesCache.ts
67.34% <67.34%> (ø)

packages/mobx/src/utils/createTransformer.ts
67.34% <67.34%> (ø)

...es/core/src/definitions/factory/classStrategies.ts
71.42% <71.42%> (ø)

...re/src/strategies/collection/StrategiesRegistry.ts
76.47% <76.47%> (ø)

... and 40 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 2ddf1ec...7715093. Read the comment docs.


AudioNN + ObjDet

example code: AudioObjectDetection.ino
Compiled : OK
Problem : it still runs as an Object Detection, code size is same as object detection, audio classification is not included.
Questions:

how can I fix my code to bring in Audio Classification ?
how do I retrain audioNN to be a smaller one ? can I just have a few audio item to be recognized ?
(hello, talking, yelling, slapping, snapping finger)

Hi @rkuo2000,
To be able to run Audio NN and Object Detection together, you have to combine both of the examples. I have combined the code (please refer to the attached zip folder), but I have not tried it. However, as the YAMNet model is big, it is impossible to run these 2 models together on the board.
You will get this error " Sketch too big; see https://support.arduino.cc/hc/en-us/articles/360013825179 for tips on reducing it.
text section exceeds available space in board"
To note: modelSelect function in the code is used to select NN task and the model used. Therefore, you need to call this function to be able to upload the neccessary model into the board.
Hence, you have to retrain the YAMNet model to reduce the size. You may refer to https://github.com/tensorflow/models/tree/master/research/audioset/yamnet.
ObjDetAudioNN.zip

Loading NN model using SD card feature is up. You can give it a try.
You may refer to this YouTube video for tutorial: https://www.youtube.com/watch?v=cVvdnXiCAa4
Below is the updated code.
ObjectDetectionAudioClassification.zip


[avocado-135] Add support for generic configuration via submit script.

Resolves #135. Backports https://github.com/bigdatagenomics/adam/commit/2c25abc123840a74e7a7a4e2d951b8b546a844f5.

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


Some grammatical fixes to various README.md files

Hi Miek!  Here are some proposed grammatical fixes (and one non-grammatical, changing 10.in-addr.arpa to 0.0.10.in-addr.arpa in an example).

Thanks!

On Aug 22, 2016, at 2:37 PM, Miek Gieben <notifications<EMAIL_ADDRESS>wrote:
Thanks!
  Gave me an excuse to read all the docs!
cricket


route: Increase Quay route timeout to 60s (PROJQUAY-4002)

Increase Quay route timeout from default (30s) to 60s

/cherry-pick redhat-3.7


Documentation for Azure Batch Start/Deallocate API

Adding documentation that describes and provides information about how to utilize the Batch Start/Deallocate API

@Padmalathas - can you review this new article submission? if you're not the right person, feel free to reassign.
Note that new articles must be merged via the private repo where we have the tools to conduct a full review. (staging and Acrolinx, etc. )  If you approve this, the commits will need to be moved to the private repo and a content contributor will have to take ownership as 'author' and 'ms.author' . Thanks.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


New: View hidden infrastructure in AR

This PR implements the new View hidden infrastructure in AR sample. Please refer to /common-samples/issues/1464 for details.
Note: this sample only runs on real device.

demo

Hi Nathan, feel free to take a look at this sample if you've some time. No worries to ignore if you don't.
I made some changes based on your first version. Thanks!

Review comments received from Nick

Very cool. Not sure how/why I missed this last week :zany_face:. Couple of questions:

Why does it keep "jumping"? I can see why it might once or twice initially, but it should settle down after that, right?
Can we provide an option to take each vertex and draw small/unobtrusive ground-level marker for it, optionally with a similarly unobtrusive vertical leader? I think it would really help with understanding the visualization and the "sliding" that seems to happen when viewing underground stuff. Could just exist within an AGSGraphicsOverlay or two that is toggled on and off.

@saratchandrakarumuri Please take a look at this new sample and share your thoughts! The parallax effect might make this sample look confusing though... 😅


Adapters trimming

As far as I understood you don't have predefined sequences for adapters:
"By searching the best overlapping of each pair, AfterQC automatically detects and cuts adapters for pair-end data, with no need of adapter sequence input"
I used AfterQC on metagenomics data and it seemed to reduce the numbers of adapters, but not entirely. What could be the cause? Also, what is important, I couldn't see it from the AfterQC report, I checked it with fastqc/multiqc, so from the user's point of view I would want to still see the validation for typical adapters in QC report.
Please, check the last post here - Sudden quality drop in the middle of HiSeq R1 reads but not in R2
If it is somehow beneficial for you I can send you full reports.

How many adapters got removed, and how many not?
AfterQC trims adapters for pair-end sequencing data based on searching for best overlap. But if there are too many sequencing errors, it will make AfterQC failed to find the overlap and consequently failed to trim adapters.
Recording the adapter information in the report is a good idea, I will implement it in future release.

AfterQC report of one sample
Also quick question, what would happen if I run AfterQC again on good reads?

If you run AfterQC with good reads, you should get every good read being kept.
But you can have a try.

From the figures you post, seems that the adapters those cannot be trimmed are at positions < 40, which means these DNA templates are shorter than 40?

Yes, which is weird. The original paper says:

KneadData. KneadData incorporates Trimmomatic and bowtie2 for filtering and human sequence removal, respectively. Reads were scanned with a four-base wide sliding window and trimmed when the average base Phred score drops below 20. Trimmed reads shorter than 70 nt were discarded.

So, I'm not sure if they trimmed adapters.
For me it is important to understand how AfterQC works, e.g. if what I got is expected, because of many sequencing errors, which makes AfterQC fail to find the overlap, and if it is advised to apply additional trimming after AfterQC in such case.

It's not the major reason that sequencing error results in overlap detection failure, I think less than 1%.
From the figure you post, the major reason is that the DNA templates are too short. AfterQC requires at least 30bp overlap to detect adapters, that's why the adapters under or near position 30 are not trimmed but the adapters beyond position are all trimmed.
I am very curious why your sequencing library contains so many short fragments, I suspect that most of them may be self-ligased adapters. Did you perform fragment length selection after adapter ligation?

I'm curious myself. It's not my article, I'm analyzing public dataset.
Here is the article. Please, read the section "Shotgun library sequencing and quality control". But regarding sequencing protocol they reference one more article, so I'm unable to answer your question currently, need to read more.
Additionally, here is sequence quality after AfterQC (raw is similar, but worse):

Ok, seems the quality drop cycle by cycle is a bit serious, and there are two gaps...

Yes, I thought that the gaps are bubble related. That's how I found AfterQC, because I googled the tool, which can correct that. but AfterQC didn't find anything. So I have no idea how those drops are generated.

UPDATE. For NexteraXT transposon protocol when the insert is shorter than the length of a single read it results in the presence of adapter at the end of the read. Article, blog post, biostars post.
But for metagenomics datasets I don't think we can identify read pairs with small insert sizes prior. I will try to play with fastqc report by increasing k-mer size and see if I can identify the issue by looking on k-mers (i.e. without knowing nextera adapters sequence).
I think AfterQC can deal with this particular problem, but for that you either need to check against particular sequence or change the trimming algorithm somehow. But anyway just having adapters-related qc report would be great. I don't think that the tool should cover all the possible situations, but it should provide the user with information to see potential problems.


Preset not supporting HLS

I am Happy and thank to this project .
since the ffmpeg support HLS  , but codem-schedule cant apply with preset to transcode HLS format .
workaround for HLS ,each file to transcode HLS have to create it's own preset to fill in the ffmpeg option.

Check out the (experimental!) HLS branch: https://github.com/madebyhiro/codem-schedule/tree/hls


PS3 Support

Hi, i saw issue #3 but maybe something changed in last 6 months? ;) I can unpack every file in PS3's GZ except *.subp files - can you add  support for it?

It woud be great if Atvaark will add PS3 support.

https://github.com/JakubDziworski/FoxEngine.TranslationTool/releases - LangToolPS3 Support for GZ
https://www.dropbox.com/sh/f6g96u5feclpidi/AABBC-hph6-iiy3SKC0iEEWVa?dl=0 -Fnttool, Subbtool PS3 Support (and another tools for PS3).
Topic to close :)


Publish a CONTRIBUTING guide

Investigate if we can pull in the CONTRIBUTING guide from the OpenCue repo and publish it as a page on www.opencue.io when Hugo builds the site and Netlify deploys it.

Related work in https://github.com/AcademySoftwareFoundation/opencue.io/pull/74

Started work in https://github.com/AcademySoftwareFoundation/opencue.io/pull/79

Published at https://www.opencue.io/contributing/opencue/contributing/


ESP-IDF 5.2

ESP-IDF 5.2 adds a new field to the SPI ethernet configurations:

Added option to use SPI Ethernet modules in poll mode without interrupt. #12682 (34ec96e)

So far I have simply added the field and it passes cargo check, but there might be some further changes required?

CI fails though?

CI fails though?

It seems to me this is because esp-idf-hal needs to be updated as well.

CI fails though?

It seems to me this is because esp-idf-hal needs to be updated as well.

No. The problem is in eth.rs and seems to come from your changes.

CI fails though?

It seems to me this is because esp-idf-hal needs to be updated as well.

No. The problem is in eth.rs and seems to come from your changes.

I can't test the RISC-V targets:
error[E0463]: can't find crate for `core`
  |
  = note: the `riscv32imc-esp-espidf` target may not be installed
  = help: consider downloading the target with `rustup target add riscv32imc-esp-espidf`

= help: consider downloading the target with rustup target add riscv32imc-esp-espidf

Did you try what the compiler suggested?

rustup target add riscv32imc-esp-espidf

Of course...

error: toolchain 'esp' does not support components
error: toolchain 'nightly-x86_64-unknown-linux-gnu' does not support target 'riscv32imc-esp-espidf'

I think you are NOT really compiling with cargo build -Zbuild-std ..., as you should
Also can you do:
$ rustc --print target-list | grep espidf

It should print something like:
riscv32imac-esp-espidf
riscv32imafc-esp-espidf
riscv32imc-esp-espidf

This is now addressed in master.


koord-manager: nodeslo-controller enqueue request when node labels updated

Ⅰ. Describe what this PR does
#2116
enqueue request when node update labels
Ⅲ. Describe how to verify it
running in local
Ⅳ. Special notes for reviews
V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in make test

cc @songtao98

Good job! Thanks :)
/lgtm

cc @zwzhang0107

/approve


csi: drop go from bin

Follow-up to #288 . Aligns with CSI build.
Description

How Has This Been Tested?

Merge criteria:

[ ] The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

cc: @tarilabs


Safe and Explicit Memory Management

Since Vinum's early beginnings, it was de-facto in-aware of memory management at scale. Since 0.2, it provided a destroy public function so that the users could be able to destroy their created objects.
However, this API was in fact so low-level, that you could say its just an reincarnation of your cute little free() function in languages like C++. This of course meant that it also inherited the same foot guns as free(), or at least, in some sort of way. This meant that you need to pair one object construction call with exactly one object destruction call, and Modern Science had found that developers suck at this.
A better solution for this is perhaps to introduce a scoping behavior, or perhaps tying an object's existence to a defined process. A process that would just act as a container for objects that need to be cleaned up when the process is needed to be killed.
Of course, there is more to this, and I will add more info to this issue as I get new insights and ideas.

Generally speaking, all values we create in Luau and Roblox are tied to a specific scope, or to be technically specific, process. For example, all instances you create in the DataModel are tied to Roblox's process/scope. That is, while you will certainly have memory leaks from not cleaning up instances at all, they still adhere to a specific scope.
As you might have guessed, the reason of these memory leaks is that the scope these said instances adhere to, is practically the root scope. So to fix this, we need to implement scoping primitives in our code. However, as an additional requirement, we need to also make it very explicit, and also dependent on Luau's type checking. This way, you will always be required to create an object that adheres to a scope defined and controlled by you.
The solution for this is to preferably expose a scope/process global function that returns a cleanup table with a metatable that points at a table of constructors, something like this:
local scope = process()

local Health = scope:Hold(100) -- processor omitted for clarity.

And Hold's constructor would look something like this:
local function Hold(cleanupTable, value, processor)
   local self = {...}
   table.insert(cleanupTable, self)

   return self
end

And to kill a process/scope, we could always expose a kill function that cleans the same type of data your good old Maids clean, in addition for support for calling a custom destroy function suited for cleaning up state objects. (to be clear, it will not be functionally same as the current public destroy function).
Having this solution implemented will greatly help with memory management in Vinum, as in contrast to previous versions, cleanup code will now only bother about cleaning up processes/scopes, not individual objects! This works, because for example,its easier for your brain to remember Kill this scope when *this* instance gets destroyed than it to remember Destroy all of **those** individual objects when this instance gets destroyed.
This being said, there are more rules about this scoping behavior that will affect how you use Vinum though I'd imagine not by a lot.
Firstly, Scopes are Long-Living Mortals
All scopes you create will all have strong references held by Vinum. While this can look like a bad idea at first glance, it's actually very useful. This is particularly because scopes/processes need to be cleaned up manually, either in a declarative manner in a library like Fusion {[onCleanup] = function() kill(yourScope) end}, or in an imperative one.
Another great side-benefit from this, is you got the ability to efficiently inspect what scopes are currently alive at the moment, which opens up for Debuggers and other alike tools.
Of course, these scopes will eventually get cleaned up, but that will probably be when all memory is getting free'd anyway.
Secondly, Scopes have Children
This rule's existence can be always tied to current state object destruction behavior. When you destroy a state object, all of its dependents will get cleaned up as well. This is generally because if you just cleaned up the root state object, all the other child state object will either just sit there causing memory leaks, or potentially errors if they have a still-alive dependency.
But to be incredibly honest, this rule is more of an idiom rather than an actual rule that can be enforced statically. Though, that's an implementation detail you will never need to worry about as a user of the library as preferably, Vinum will automatically mark a state object's scope a child of another when the said state object depends on a state object of the other scope. This means that you shouldn't get any error related to that at all.

Another related issue is the non-existence of a standard interface of destruction code. That is, Instances and custom luau objects adopt object::Destroy, while classes like Connections adopt connection::Disconnect, and other data structures have completely unique destruction semantics.
Of course, hard-coded support for all of these common classes is manageable, but only so until you got to support 5+ types. While support for function calling might open up for custom support, it doesn't enforce clear user intent and will ultimately lead for more code complication so that it can work nicely.
Destruction Traits
The solution I found for this is to introduce some sort of a destruction trait, where in implementation-specifics, just a table with an object field that points at the value, and a destroy field that points at a defined destructor function. Technically speaking, you wouldn't be creating these tables yourself, as two public functions would be exposed just for that.
Those two are called Owned and Borrowed. As the name implies, they are functions that return a destruction trait that either specify a value need to be destructed (the value is owned by the current user agent), or need to be left alone (the value is borrowed by the current user agent).
For example:
local Owned = Vinum.makeOwned(function(value)
    print(value)
end)
local Borrowed = Vinum.Borrowed

local function your_processor(old, new)
   return old ~= new
end

Compute(function(...)
   return Borrowed(workspace.Baseplate)
end, your_processor)

Compute(function(...)
   return Owned(Instance.new("Part"))
end, your_processor)

Few observations can be found from this:

An Owned can be constructed from a function that specifies its destructor function.
Both Owned and Borrowed accept a value as an argument..
Processors now aren't bothered with cleanup semantics.
After every udate, Compute calls the destroy field of the previous destruction trait.
Owned implies that a value must be destructed after you are finished with it.
Borrowed implies that a value must be not destructed after you are finished with it.

Using those observations, we could derive some rules and idioms:
Owned can't accept Destruction Traits
This should makes sense really, as whether the incoming trait is created by a Borrowed or an Owned, it does still means that the wrapped value already has an owner. As such, Owned should error when met with a case like this.
It could be said that when you give Owned a trait, it is implied you are giving ownership to the said Owned over the said trait; however, Vinum remains authoritative of all traits, due to the possibility for trait recycling. This should be the expected, as Destruction Traits are nothing but traits at the end of the day. Not an entire self-aware object in a way, instead, it's just a trait that defines some destruction behavior.
Also, even if we decided against trait recycling, it still makes sense to not Owned any trait, as they are garbage collectable, and not expected to have a reference held to them (ex. Processors receive the unwrapped value rather than their traits).
This also means that ideally, you shouldn't be working with Traits if you aren't the agent that will clean up the mess, instead, you should always unwrap them simply by indexing their object field.
Borrowed unwrap incoming Destruction Traits
This is also similar to the previous rule in some way, as while Borrowed is allowed to unwrap any trait, and absorb their value, it's not allowed to borrow another trait as it could introduce nesting and a false perception that traits can be borrowed (ex. imagine a Compute's processor getting a trait instead of its value because of nesting..).
All manually-managed values must be wrapped in a Destruction Trait
Technically speaking, not all values need destruction. Simple singular values like strings and numbers don't need destruction at all. So in a way, we need to make it obvious to Luau's typechecker when to warn when there isn't a trait getting passed to an agent.

Implemented


VMmanager 6

Add template for VMmanager 6 monitoring
https://www.ispsystem.com/software/vmmanager

We wanted to thank you for your contribution to the community development, but we cannot take your PR. Please correct the directory structure. Examples are available in the documentation. It is not necessary to reduce templates for all versions from Example (5.0, 5.4). It is also very important that the version in the catalog name coincided with the actual version of the template. For example, in the 5.0 directory, there must be a template for version 5.0.

Hello, thank you for your feedback. Could you help me to fix that?

I need to remove number 6 from template name? How can I create template only for 6 version of VMmanager?
If not - I need to remove 5.0 directories? My zabbix template was generated by 5.4 version, but: I created templates in 5.0 version and update it to 5.4 (to add new user features)

Hello.
Yes, it is enough to delete the 5.0 directory. Server version 5.0 will not be able to import a template generated by more new versions (5.2 and higher)

Ok, it's done. Thank you


KIP-392: Continue work on #1696

This is a continuation of #1696 with changes mentioned here.

I signed the CLA.

@dneralla many thanks to both yourself and @danp for putting together this much requested feature! changes look good, I've approved and merged.


Discussion Forum

Is your feature request related to a problem? Please describe.
Tasks are done more successfully when the members can easily communicate with each other. Also, the forum would facilitate the exchange of ideas!
Describe the solution you'd like
Have a separate tab in the menu for the discussions - Forum where users can create threads on almost any topic and people can comment on these threads.

Would the discussion be general for all the users or would it be group of friends that are allowed or anything else?

We can have them create a separate thread if they want. I think it would be nice to have just the common discussion forums for now.


Exception while map.remove()

when layer is removed while map#remove() process map._controlCorners property is already deleted. need check before using property
Closes #shramov/leaflet-plugins#270

Nice, thx for the patch :)


hpe-flexvolume-driver repo

Hi, in #150 and #153 we went back and forth on the repo name. However, none of those names are actually reflected on hub.helm.sh.
What it looks like:
https://hub.helm.sh/charts/hpe-flexvolume-driver/hpe-csi-driver
https://hub.helm.sh/charts/hpe-flexvolume-driver/hpe-flexvolume-driver

What we thought it would look like based on #153.
https://hub.helm.sh/charts/hpe-storage/hpe-csi-driver
https://hub.helm.sh/charts/hpe-storage/hpe-flexvolume-driver

Please advise.

After some poking around, it seems that the names actually works:
https://hub.helm.sh/charts/hpe-storage/hpe-csi-driver
https://hub.helm.sh/charts/hpe-storage/hpe-flexvolume-driver
But when you search hpe, the old names appear (and works....)

You've found a bug. I think this is due to a couple things...

Monocular still has the old location in the cache
Monocular displays the first one when two chart/versions have the same digest because it's the same chart

I think the quick fix is to release a new version of those charts.
The longer term fix is we need to fix monocular.

Thanks for the response. Can we just re-index or do we actually need a new
version number?
On Thu, Sep 26, 2019 at 7:48 AM Matt Farina<EMAIL_ADDRESS>wrote:

You've found a bug. I think this is due to a couple things...

Monocular still has the old location in the cache
Monocular displays the first one when two chart/versions have the
same digest because it's the same chart

I think the quick fix is to release a new version of those charts.
The longer term fix is we need to fix monocular.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/helm/hub/issues/154?email_source=notifications&email_token=ABVTK2FNP6SIUKRC7I2FZDDQLTDSPA5CNFSM4I2OJPM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7V24FY#issuecomment-535539223,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVTK2BT6RIYFTG4WPKFBODQLTDSPANCNFSM4I2OJPMQ
.


Implement additional formatting traits for [T]

Bringing https://github.com/rust-lang/rust/issues/33127 back from the dead because I came across a desire for this feature today.
However, I would like to extend this proposal to include all the following traits and implement them for<T> [T] where T: <trait> (and presumably Vec<T> as well):

Binary
LowerExp
UpperExp
LowerHex
UpperHex
Octal
Pointer

Finally, I would like to echo @retep998's proposal to just copy the Debug impl and use the above traits to format the elements. It fits considering that the main use for these formatting styles would be in debug or logging output anyway.
It may also be desirable to extend these impls to other collections types as well, using their Debug impls as a basis.

I would love to see this.

This was rejected in https://github.com/rust-lang/rust/pull/44751. I proposed something different (based on Debug) in https://github.com/rust-lang/rfcs/pull/2226.

Gonna close this since #2226 covers the original use-case I had in mind.


otel span metrics stop working

prometheus calls_total metrics disapreared, and log in otel collector:
$ kubectl logs -f -n observability opentelemetry-collector-66f4dd8d68-ms5qz --tail 100
2022-12-23T02:06:53.106Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-alarm-service\\x00/alarm/subscribe/page\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00roc-alarm-service-85f7d49548-rvrs7\\x00200\""}
2022-12-23T02:06:53.307Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-multitenant-service\\x00/actuator/prometheus\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00stable-roc-multitenant-service-6b5f4d7464-cwxgm\\x00200\""}
2022-12-23T02:06:53.509Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-alarm-service\\x00/alarm/subscribe/page\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00roc-alarm-service-85f7d49548-rvrs7\\x00200\""}
2022-12-23T02:06:53.711Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-alarm-service\\x00/alarm/subscribe/page\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00roc-alarm-service-85f7d49548-rvrs7\\x00200\""}
2022-12-23T02:06:53.913Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"smartvoice-portal\\x00prepipeline-dmkit\\x00SPAN_KIND_INTERNAL\\x00STATUS_CODE_UNSET\\x00smartvoice-cloudpepper-v3-dit\\x00stable-smartvoice-portal-748d76f4d6-h278d\""}
2022-12-23T02:06:54.115Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-alarm-service\\x00/alarm/subscribe/page\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00roc-alarm-service-85f7d49548-rvrs7\\x00200\""}
2022-12-23T02:06:54.316Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-alarm-service\\x00/alarm/subscribe/page\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00roc-alarm-service-85f7d49548-rvrs7\\x00200\""}
2022-12-23T02:06:54.919Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-alarm-service\\x00/alarm/subscribe/page\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00roc-alarm-service-85f7d49548-rvrs7\\x00200\""}
2022-12-23T02:06:55.322Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"smartvoice-portal\\x00prepipeline-dmkit\\x00SPAN_KIND_INTERNAL\\x00STATUS_CODE_UNSET\\x00smartvoice-cloudpepper-v3-dit\\x00stable-smartvoice-portal-748d76f4d6-h278d\""}
2022-12-23T02:06:55.524Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-multitenant-service\\x00/actuator/prometheus\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00stable-roc-multitenant-service-6b5f4d7464-cwxgm\\x00200\""}
2022-12-23T02:06:57.130Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-multitenant-service\\x00/actuator/prometheus\\x00SPAN_KIND_SERVER\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00stable-roc-multitenant-service-6b5f4d7464-cwxgm\\x00200\""}
2022-12-23T02:06:57.532Z        warn    batchprocessor/batch_processor.go:178   Sender failed   {"kind": "processor", "name": "batch", "pipeline": "traces", "error": "value not found in metricKeyToDimensions cache by key \"roc-multitenant-service\\x00OperatorController.getOperatorDetailByIdoeToken\\x00SPAN_KIND_INTERNAL\\x00STATUS_CODE_UNSET\\x00harix-roc-cloudpepper-v3-dit\\x00stable-roc-multitenant-service-6b5f4d7464-cwxgm\""}

According to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/9018.
We should upgrade otel collector to v0.59+, now it's v0.58.

fixd at https://github.com/kubegems/plugins/commit/0721e55e1555d9a53d8e9b001992f528611991bb

v0.59+ still has the same problem and it consistent with this issue. https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/9018#issuecomment-1252476417

I've just removed my workarounds to reproduce it. There's no logs of an error. But I do see cpu spiking when this happen.

The CPU spiking and the failure of the otel collector are two problems. This issue only discusses how to solve the failure of the otel collector.

We can only debug when problems such as the loss of the otel data occur.

Recurrence by set dimensions_cache_size: 1, it always appears after the metrics key cache is full, Expecially when cpu usage high.
So I think after we use prometheusexporter to replace prometheusremotewriteexporter, it will be fine.
If not, we can wait for https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/16601 https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/17307 to be merge, then use the new release.

PR https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/17307 has been released in v0.70.0 https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.70.0.
So we upgrade opentemetry plugin: https://github.com/kubegems/plugins/commit/75b19474de7caf128b99dd79f704c951f1befd0b.

Seems no problem after upgrade, close.


cosmos: Do not unwrap an Option

The code here and here unwraps an Option. That has lead to startup failures in staging. The code needs to be changed to either deal witha None properly (e.g., by returning an empty iterator) or the Block struct needs to be changed to not contain an Option

@lutter Do you have more information about these failures (which chain, block number etc.)? This is not a normal situation. We left those unwraps there because we expect the ResultBeginBlock structure to always be present.  If patch the code to not panic but bubble up an error, then we will be able to pinpoint the subgraph.


Update nack interceptor

Generate + Respond interceptors
Description
Reference issue
Fixes #...

@tarrencev mind just leaving this as a branch (for now)  When we merge that branch in pion/interceptor we will lose the SHA. Just so we don't have un-buildable commits.
@at-wat mind looking at pion/interceptor NACK PR? Happy to wait if you need a few days! If you don't have the time we can just merge and come back to it later, thanks!

@Sean-Der yup! was just opening this so it is ready once we land the rest :)

@tarrencev I haven't had a chance to test this yet, but here it is :)
I am gonna confirm they are being emitted/are valid tomorrow!

@tarrencev This is all good to go :)
Is everyone ok with this being on by default? We can improve the implementation as we go.
One thing is we know require people to process RTCP, so I updated all the relevant examples. It might be worth revisiting interceptors. I saw that @robin-raymond may have had design concerns with it as well.

awesome! lets merge whenever you're ready!

done :)


wpa_supplicant: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp4s0/drop_unicast_in_l2_multicast: No such file or directory

Issue description
I see a red line in my logs. I prefer to run a system that is free of warnings in order to facilitate debugging of real issues.
wpa_supplicant[27931]: nl80211: Failed to open /proc/sys/net/ipv4/conf/p2p-dev-wlp4s0/drop_unicast_in_l2_multicast: No such file or directory

Steps to reproduce
Unknown
Technical details

system: "x86_64-linux"
host os: Linux 4.15.18, NixOS, 18.03.git.816101f (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0.1
channels(root): "nixos-17.09.2182.7f6f0c49f0"
channels(coretemp): "nixos-18.03.132192.ce0d9d638de"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Importance
Low.

Do you know what device wlp4s0 is? For instance could it be a USB wifi stick that has been removed?

@matthewbauer Yes, it's a wireless networking device displayed by iwconfig.

Hey, this actually seems to break something on my system! I am connected to wifi, and after some time it (network connection) hangs. I cannot ping anything (including the gateway of my home network). It happens soon after this message pops up.

@balsoft did you resolve this? thanks

Having similar issue - custom tuxonice kernel 4.16.0+- old debian system.
https://github.com/albfan/miraclecast/issues/345
The patch did happen.. will investigate further
https://patchwork.kernel.org/patch/7559041/

@rapofran I have resolved this by disabling the p2p device.

Pinging wpa_supplicant maintainers @marcweber and @ma27

Prior art (other threads that appear to be about this issue):

https://forums.debian.net/viewtopic.php?t=141848
https://bbs.archlinux.org/viewtopic.php?id=232184
https://github.com/albfan/miraclecast/issues/345