Organize cheats in folders

There shoud be a way to organize cheats in folder.
Nothing should really change in the usage of the plugin but it should search for cheats recursively.

Cool thanks for the feedback. It's doable if you're happy with simply recursive searching. i.e., cheat/somedir/brew.txt is equivalent to cheat/brew.txt. But if you wanna do something with or reflect somedir itself in the calling, then it's something worth considering because I haven't thought of good ways to do that. Any suggestion or you're happy with the simplest solution?

Yep the simplest solution is enough for my purpose.

The feature has been added. Now the tool will try to flatten every cheatsheet in the base directory. That means the directory structure is only for your management purpose. And make sure you don't have duplicated cheatsheets in different dirs (e.g, cheat/a/ls and cheat/b/ls). Otherwise, only one of them will be shown.

Thanks for the report. And closing the issue because it's been resolved.


Race Condition - NaClDescIoDescDtor

Both Jonathan and I have been experiencing this failure about 5-10% of the time on Lind runs. We need to look into why this is happening.
POST-ABORT: LOG_FATAL abort exit

** Signal 6 from trusted code: pc=7fbe85da9355```

I was able to get some more information about this by adding info to the error log, it seems to be failing in SafePOSIX
executing: [sel_ldr -a -- "/lib/glibc/runnable-ld.so" --library-path "/lib/glibc" /bin/bash lscatwc]
Lind v1.0-rc2
Opening file system...
done.
[22394,3136738368:11:38:41.459511] BYPASSING ALL ACL CHECKS
[22394,3123078912:11:38:41.823871] Retval -1: Failed closing lind fd 13 in cage 3[22394,3123078912:11:38:41.823885] NaClDescIoDescDtor: NaClHostDescClose failed (0x7f5bb0016e90).
POST-ABORT: LOG_FATAL abort exit

** Signal 6 from trusted code: pc=7f5bbafb5355```

It's very hard to get more information out of this though since the error only happens about 1 in every 10-20 runs of Lind, and if you add prints to SafePOSIX, it doesn't happen at all. (I scripted this to run thousands of times to catch the error with logging and couldn't get it).

This was a bit hard to catch because of needing to run many times to get it to trigger and because of printing avoiding this. Adding manual tracebacks in SafePOSIX helped.
This seems to be triggered when multiple processes are running and pipe end is closing  def _lookup_refs_by_pipe_end(pipenumber, flags): iterates through the masterfiledescriptortable and if another thread changes the table it triggers this error RuntimeError: dictionary changed size during iteration

I found by running this a bunch that this was also being triggered in close by the get_fds_by_inode function. I fixed the dtor error by changing both of these functions to iterate through the masterfiledescriptortable usings the keys() function.

Fixed with this pr


Hot Reloading does not work using yarn watch

Problem
When using yarn watch instead of yarn start webpack looks for changes and compiles the new javascript/CSS fine but it does not initiate a hot reload from browser sync and does not update the files on the shopify server.
It seems as if using yarn watch does not cause assets to be served from localhost:3001 and will just use the asset already uploaded to shopify in a previous deploy.
Replication steps
Start yarn watch update a javascript or CSS file. Hot reloading is not initiated and doing a page refresh does not cause the CSS or javascript to update either.
Use yarn start to do an initial deploy to the theme and then update a file. Hot reloading seems to work fine.

I'm able to reproduce - specially when a file is empty first and not deployed yet to Shopify.
Thanks for the issue, @allanarmstrong  - workaround for now is to yarn start but we'll look into it.

We can clarify this in the docs -- but yarn watch should only be used after your have previously run yarn start. yarn watch skips uploading the developer build of the .liquid files to Shopify servers and goes straight to watching files for changes.
If you had previously run yarn deploy then all your liquid files will have paths referencing cdn.shopify.com. Since yarn watch does up upload the development liquid files, paths will remain referencing cdn.shopify.com
If you run yarn start, development liquid files are uploaded which have paths referencing your local IP:3001. If you stop yarn start and want to get back up and running without needing to re-upload development files, you can use yarn watch.
Removing this as a bug and setting it as something we need to improve documentation on.

I am having the same issue. I run slate start and everything works fine except the Reloading of the browser window. Here is my terminal:
`[BS] Proxying: https://example-development.myshopify.com
[BS] Access URLs:
   Local: https://localhost:3000/?preview_theme_id=*removed*
External: https://<IP_ADDRESS>:3000/?preview_theme_id=*removed*

      UI: http://localhost:3001

UI External: http://<IP_ADDRESS>:3001
[04:15:22] change in src/styles/src - change _typography.scss
[04:15:22] running task - build:css
[04:15:22] change in assets - change index.scss.liquid
[04:15:22] Initiating deploy to development
[04:15:22] running task [child process] - theme upload
[development]: 1 / 1 [==================================================] 100 %
[04:15:26] Transfer Complete: File changes successfully synced to store
[BS] Reloading Browsers...
`
All browsers tested do not reload.

@allanarmstrong, @completewebco, I'm having the same issue. Everything seems to be working, except for the browsersync refresh.

I am having the same issue. I run slate start and everything works fine except the Reloading of the browser window. Here is my terminal:
Proxying: https://example-development.myshopify.com
Access URLs:
   Local: https://localhost:3000/?preview_theme_id=*removed*
External: https://<IP_ADDRESS>:3000/?preview_theme_id=*removed*

      UI: http://localhost:3001

UI External: http://<IP_ADDRESS>:3001
[04:15:22] change in src/styles/src - change _typography.scss
[04:15:22] running task - build:css
[04:15:22] change in assets - change index.scss.liquid
[04:15:22] Initiating deploy to development
[04:15:22] running task [child process] - theme upload
[development]: 1 / 1 [==================================================] 100 %
[04:15:26] Transfer Complete: File changes successfully synced to store
[BS] Reloading Browsers...
All browsers tested do not reload.

I'm having the same issue as well

I am having an issue where slate is watching for changes to my templates but not to the header.liquid file. Any ideas why that might be?

I had been having the exact same problem mentioned by @willwong89 and @completewebco
I was able to fix it by updating browser-sync to version 2.26.3
Was very strange that it had been working for me up until a sudden point.

@nelsonr462  I was able to fix it too , updating to v2.26 was the solution, although now i can't access the browsersync UI tab to see the options/plugins etc...
And one more thing, it's seems like there is some kind of lag when trying to reloading.
Reloading the page with F5 is faster than with browsersync, it's like it has to load 2 times and then reload.

Running into this issue even after running yarn start and then yarn watch. Things will work up to a point, but then only template files trigger hot reloading and all liquid files do not. I then have to manually hit refresh after saving to see the changes, which defeats the purpose of browser-sync.
Not sure if this helps anyone, but having a globally installed copy of browser-sync was making slate v0 and slatev1 not hot reload at all. Removing this global install of browser-sync 6.0.0 made slatev0 work as expected but slate v1 is still spotty on hot reloading.
Any help is much appreciated.


Fix header Markdown in README.md

GitHub's Markdown interpreter was recently changed to strictly enforce the GFM spec, which requires a delimiting space in header Markdown. This has caused some Markdown to no longer display as originally intended.
More information:
https://github.com/blog/2333-a-formal-spec-for-github-flavored-markdown
https://github.com/github/markup/issues/1013

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


[iOS] Camera usage indicator does not go away.

Steps to Reproduce
Create an app using camera_awesome, use the camera, then navigate to any other screen which is not using the camera anymore.
Expected results
On iOS there is a little green dot next to the battery indicator (See screenshot) , showing that the device is using the camera at this moment.
It should disappear after navigating to any other screen which is not using the camera.

Actual results
The green dot does not disappear, even after disposing of any controller in the camera view.
About your device

Brand
Model
OS

Apple
iPhone 12
14.4

Any update on this?

Same on OnePlus 7 Pro, the Pop-up front camera stays up after navigate to another screen
Any fix for this ?

Any information on when this bug will be fixed ? @g-apparence

Hello,
sorry I'm quite really busy this month.
The problem is that we keep the state of the camera while you navigate. If you really want to force the camera to close you have to :

replace the current pushed page
force the previous page to close the camera before navigating (just remove the CamerAwesome preview from your page before navigating)

As CamerAwesome is started with your view this behavior is totally "normal". We can think of a way to make it better.
If you have any suggestions on what you want I'm open.

I tried to work around this using WidgetsBinding.instance.addObserver(this) and implementing didChangeAppLifecycleState. If the AppLifecycleState is anything other than resumed, I call CamerawesomePlugin.stop() - and the indicator light goes out. On resume I call `CamerawesomePlugin.start()', and it works OK.
I'm working on a problem I see the first time the app is executed. It pauses to ask for camera permissions, when they are granted I see this error:
[ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: PlatformException(CAMERA_MUST_BE_INIT, init must be call before start, , null)
I'll continue investigating, and will post results here.

Looks like the plugin is in a weird state the very first time the camera is used (when it's asking for permission). CamerawesomePlugin.currentState is STOPPED, but calling start() gives the error I mentioned.
So I implemented the AppLifecycle state as described above, stopping and starting the plugin as the app lifecycle changes, except I don't call start() when the lifecycle change is immediately after the permission grant.
That works fine: first time startup behaves as expected, and now use of the camera (and the indicator light) correctly follows the app state.

Sorry I don't have time right now to take a look.
But I keep this in "to do"

this makes the battery wasteful, because the camera is open again after dispose. both on android and on ios. i added the following code on the screen after open camera,
  Future.delayed( const Duration( seconds: 1), () {
     CamerawesomePlugin.stop();
  });


Processing Submitter Info

Story
As a public health lab, to reduce transcription errors caused by handwritten order data, I need submitter information included as part of the electronic order.
Pre-conditions

[ ] The submitter info is included as part of a single, incoming order.

Acceptance Criteria

[ ] The submitter info is included in the OML order transmitted to the public health lab.
[ ] Submitter info must be support NBS card options used by MN, AL, & TX. (e.g. hospital name, address, phone, hospital submitter ID, ordering physician name & NPI, collected by initials)

Tasks
Research

[ ] Determine ways to represent these data elements in both HL7 and FHIR
[ ] Research work needed to complete the story
[ ] Foundational: High-level research that will support this and future efforts

Engineering

[ ] Engineering work needed to complete the story
[ ] Foundational: Technical runway work to support this and future efforts

Definition of Done

[ ] Threat model updated
[ ] Code refactored for clarity and no design/technical debt
[ ] Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies.
[ ] Source code is merged to the main branch.
[ ] Unit test coverage of our code >= 90%
[ ] Code is reviewed or developed by pair; 1 approval is needed but consider requiring an outside-the-pair reviewer.
[ ] Build process updated
[ ] Feature toggles created and/or deleted.  Document the feature toggle.
[ ] Source code documentation created when the code is not self-documenting.
[ ] API documentation generated
[ ] Code quality checks passed
[ ] Security & privacy gates passed
[ ] Load tests passed
[ ] Documentation and diagrams created or updated
[ ] API(s) are versioned
[ ] Debug logging

Research Questions

Optional: Any initial questions for research

Decisions

Optional: Any decisions we've made while working on this story

Notes

Optional: Any reference material or thoughts we may need for later reference

closed.  will be part of #492


Miss use by some users multiple keys system

Some of node providers notice that some users are using system of 4 keys and buying multiple keys of price of 0.01. Then also some users are using not validated account buying multiple  keys for 1 coin.
Can you please try to fix my advice is soon as you buy 1 space for next one you need to pay 5 coin.
Also block not validated users from buying keys.
Thanks in advance

This validation I sold just 94 keys for a total of 170 idna or $6.60 which covers just 1/4th of my monthly server cost
Of the 94 keys, 39 were 0.01 idna scammers, 7 were 1 idna scammers, which leaves 48 honest identities, or about exactly half.
It's about time something is done about this

Here is an example of a Human identity funding an address to buy multiple keys at the price of 1 coin: 0xB5f3877c5a84ae97D395a6d0101c0CEAace8f56a
This allows Verified and Human identities to buy keys for less than they're supposed to.
I don't think 'not validated' users should be blocked from buying keys. Instead I think any address that doesn't have a status should pay the maximum amount (5 coins). This way no one will be able to avoid the price they actually have to pay.
Also, we shouldn't have the same price when users buy multiple keys.

Not validated IDs, or second buy must pay max price


jndi test

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Aries-cdi-pr/28/


Remove fuzzit, add oss-fuzz on PR

https://groups.google.com/u/3/g/prometheus-developers/c/YZcoHL_tH-g

(if CI passes)

4a4ea30
worked successfully.
In 7bc4812, I restict fuzzing to *.go, go.mod and go.sum changes, to spare CPU cycles. Therefore it does not run in this PR.


⚠ Bofrost.de has degraded performance

In 05979bc, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1989 ms

Resolved: Bofrost.de performance has improved in 56f21b5 after 22 minutes.


Support incomplete items of LSP server

Please see Shougo/ddc.vim#88.

Please wait. I should change source interface.
gatherCandidates() should rename to gather() like ddu.vim.

Hi.  I have updated source interface.

Updated. It can be merged.

Thank you !


More information needed

"You can only host one library component version at the time in a tenant"
-> What if the version is changed? Do we have to recompile all dependent solutions?
"Library components are not supported when solution is deployed using site collection app catalog"
-> Does this mean we can't deploy a library component to a site collection catalog or Webparts deployed to a site collection catalog can't use a library component deployed to the tenant app catalog? Or both?
"You can reference library component dependency in the SharePoint solution by defining the dependency in the package.json file"
-> How? Examples? Is "npm link" not needed when we do this?
As library components are now GA please elaborate a little bit more on these topics.

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

ID: b431da26-3a26-bab5-1af4-a151d9e50f2e
Version Independent ID: 50656bd9-3514-ae39-0805-0927d30e4355
Content: Using library component type in SharePoint Framework
Content Source: docs/spfx/library-component-overview.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Hi @cwdata...Thanks for your questions.
"You can only host one library component version at the time in a tenant"
-> What if the version is changed? Do we have to recompile all dependent solutions?
My Feedback: As you can imagine, it depends. For example, if you change the inner workings of a function within a LC that would not affect how a dependent solution calls it, then it should not require any updates to those dependent solutions. BUT, if you were to change the method name, deleted the method or something similar then updating the dependent solutions would be needed.
NOTE: This underscores the importance of being very careful of breaking changes and governance of the updates/changes to your LC's.
"Library components are not supported when solution is deployed using site collection app catalog"
-> Does this mean we can't deploy a library component to a site collection catalog or Webparts deployed to a site collection catalog can't use a library component deployed to the tenant app catalog? Or both?
My Feedback: As far as I know, you can still use a web part for example, deployed to the site collection app catalog that uses a LC that is tenant deployed. I'm almost certain I've done this for many of my dev tests, but I will double-check and let you know.
"You can reference library component dependency in the SharePoint solution by defining the dependency in the package.json file"
-> How? Examples? Is "npm link" not needed when we do this?
My Feedback: Are you referring to the "npm link" on the LC or the "npm link LCName" that is performed at the web part or extension development point? You will still need to perform the "npm link LCName" at the web part or extension development point. I would expect your build will fail if it cannot resolve to the LC, as it adds a symlink within the local node_modules for your web part or extension.
There is also a tutorial that walks you through the creation:
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/library-component-tutorial
I've also created a number of videos that outline some LC development guidance as well.
Hopefully, this helps, but let me know if I misunderstood any of your questions. :)

Hi @PopWarner,
thanks for your answers. Regarding the npm link - I'm referring to the "npm link LCName" at the web part. As we are only able to use one central version of the LC at runtime it would make perfect sense to use one central version for the bundling too. I don't know much about that node stuff but aren't those "global" node modules "globally" available to all solutions? I'd expect the bundling process to find it in the global folder when referring to it in the package.json but I don't know if that is the case.
BTW, I found your videos and will go through them. Big thanks for creating and publishing them!

Thanks @cwdata! :)
The Symlink can be a little confusing. Here is a reference to the official documentation:
https://docs.npmjs.com/cli/link
Technically the local node_modules symlink points back to the global node_modules. It can become a little "Whose on first?" scenario, so I understand the confusion. There are also some really good blog posts available out there that get into even more details. I'll look to create a video specifically on the "npm link" in relation to SharePoint and highlight what is going on behind the in greater detail. :)


Handle jQuery event namespaces correctly #62

See https://github.com/Yapapaya/jquery-cloneya/issues/62
Note that a test which simply triggers clone would be enough to break it because it would result in _cloneAndAppend(toClone) being called where toClone is null.
However, to illustrate the caveats (bug or feature?), I have added a couple of sample test cases which show that the user may still handle the "third-party" clone event at their discretion, reminding them to check event.namespace if necessary.

Would you mind bumping the tag so I can make use of the merged pull request?


Supplement benchmark for tf-trt

Supplement benchmark for tf-trt

The test result document has been submitted.

The test result document has been submitted.


Setting "Start in Unified Inbox" is being ignored

When "Start in Unified Inbox" is checked in the settings, K9 should start in the Unified Inbox. ;-) Instead the normal inbox of the first email account is being opened.
This used to work. I believe this bug was recently introduced with the removal of the accounts activity.
Steps to reproduce

Have more than one account.
Check the "Start in Unified Inbox" setting in "General settings > Interaction".
Restart the app => opens the inbox of the first account instead

Suggestion: Remove this setting. Instead remember what inbox was used most recently (either a specific account or the Unified Inbox), and open this inbox again when restarting the app.
Environment
K-9 Mail version: 5.700
Android version: various
Account type (IMAP, POP3, WebDAV/Exchange): IMAP

I'll remove the setting. You can still start in the Unified Inbox by using the "K-9 accounts" widget on your home screen.

@cketti There are launchers that do not support widgets or do not list widgets on the home screen. So I would opt to reopen this issue.

When enabled the Unified Inbox will be opened by default (once implemented). See #4306.

@cketti that's great to hear. What about the merged folders? Is the ability to view all spam folders in one place discontinued?

any news here? dont know how to start in unified inbox instead of first accounts inbox.
faq is also outdated on this:
https://k9mail.app/documentation/faq.html#anchor18


Add back some of the diagrams packages

Checklist:

[x] Meaningful commit message - please not Update build-constraints.yml

[x] At least 30 minutes have passed since Hackage upload

[ ] On your own machine, in a new directory, you have successfully run the following set of commands (replace $package with the name of the package that is submitted, $version is the version of the package you want to get into Stackage):
stack unpack $package-$version
cd $package-$version
stack init --resolver nightly
stack build --resolver nightly --haddock --test --bench --no-run-benchmarks

base-<IP_ADDRESS> is out of bounds for:

[ ] active-<IP_ADDRESS> (>=4.0 && < 4.11). Brent Yorgey<EMAIL_ADDRESS>@byorgey. @bergey @byorgey @fryguybob @jeffreyrosenbluth. Used by: library, test-suite
template-haskell-<IP_ADDRESS> is out of bounds for:
[ ] testing-feat-<IP_ADDRESS> (>=2.5 && < 2.13). No maintainer. @JonasDuregard. Used by: library

Step 3? :)

The HEAD version of testing-feat on github works fine, it just needs to be uploaded.  I emailed Jonas so we'll see what happens.  Note that the upper bound on template-haskell for testing-feat affects only the test suite of the dual-tree package under GHC 8.4.  So I suppose we could also just mark dual-tree as an expected test failure for now.

active has now been revised on Hackage to lift the restriction on base.

Note that diagrams-svg and diagrams-cairo should be reinstatable now too.

I added diagrams-svg and diagrams-cairo and put dual-tree as expected test failure for now. So it should build now.

There is also an upstream issue: https://github.com/JonasDuregard/testing-feat/issues/7

Jonas just uploaded testing-feat to Hackage, so the dual-tree test suite should now work as well.

Done Step 3 sucessfully:
resolver: nightly-2018-05-17
packages:
- active-<IP_ADDRESS>
- circle-packing-<IP_ADDRESS>
- diagrams-cairo-1.4.1
- diagrams-contrib-1.4.3
- diagrams-core-1.4.1
- diagrams-lib-<IP_ADDRESS>
- diagrams-rasterific-1.4.1
- diagrams-svg-1.4.2
- force-layout-<IP_ADDRESS>
- monoid-extras-0.5
- svg-builder-0.1.1
extra-deps:
- cubicbezier-<IP_ADDRESS>
- diagrams-solve-0.1.1
- dual-tree-0.2.2
- fast-math-1.0.2
- groups-<IP_ADDRESS>
- mfsolve-<IP_ADDRESS>
- statestack-<IP_ADDRESS>

active-<IP_ADDRESS>: test (suite: active-tests)
diagrams-contrib-1.4.3: test (suite: turtle-tests)
diagrams-lib-<IP_ADDRESS>: test (suite: tests)
diagrams-rasterific-1.4.1: test (suite: test0)
diagrams-contrib-1.4.3: Test suite turtle-tests passed
active-<IP_ADDRESS>: Test suite active-tests passed
diagrams-rasterific-1.4.1: Test suite test0 passed
diagrams-rasterific-1.4.1: test (suite: test1)
diagrams-rasterific-1.4.1: Test suite test1 passed
diagrams-lib-<IP_ADDRESS>: Test suite tests passed
diagrams-lib-<IP_ADDRESS>: Benchmark running disabled by --no-run-benchmarks flag.
monoid-extras-0.5: Benchmark running disabled by --no-run-benchmarks flag.
Completed 6 action(s).
Haddock index for local packages already up to date at:
/home/tvh/code/diagrams-test/.stack-work/install/x86_64-linux/nightly-2018-05-17/8.4.2/doc/index.html
Haddock index for local packages and dependencies already up to date at:
/home/tvh/code/diagrams-test/.stack-work/install/x86_64-linux/nightly-2018-05-17/8.4.2/doc/all/index.html
Haddock index for snapshot packages already up to date at:
/home/tvh/.stack/snapshots/x86_64-linux/nightly-2018-05-17/8.4.2/doc/index.html

Awesome, thank you very much


markdown editor: allow image upload / do not disable "Add Component" button

Is your feature request related to a problem? Please describe.
When using the markdown editor, the UX for inserting existing or uploading new images is not great since the "Add Component" button is disabled in markdown mode. So, I need to switch to the WYSIWYG editor first, then upload/insert the image there and then switch back to markdown.

Describe the solution you'd like
Why no simply leave the "Add Component" button in the editor enabled and have the same flow of "1) opening image selector popup 2) upload/select 3) insert image into the editor" for the markdown mode?

Describe alternatives you've considered

Allowing to drag&drop images into the editor would also be an option that could simplify things.
When switching to markdown, the editor buttons could generally change to buttons for the markdown editor instead of just showing the disabled buttons for the WYSIWYG editor. I mean, GitHub does the same for their markdown editor.

Additional context

Hi @LukasGentele @erezrokah,
Our users also experience this issue, and often use the Rich Text editor as it provides a better experience for them.
Elaborating on this issue, it would be great to have all of the formatting buttons at the top of the markdown widget available in markdown mode. Adding the markdown syntax by clicking a button would be easier for some users than typing it into the editor, and it doesn't make sense for some buttons to be disabled but not others if it's possible to have them all enabled.
See the video for a better explanation: https://youtu.be/u1QooafFKhw
Thanks,
Taine

Closing as stale


[OSX] Command-A is recently frequently not causing the editor to Select All

VSCode Version: Code 1.9.0 (27240e71ef390bf2d66307e677c2a333cebf75af, 2017-02-02T08:23:30.856Z)
OS Version: Darwin x64 16.0.0
Extensions:

Extension
Author
Version

mavensmate
DavidHelmer
0.6.4

word-count
hypnoes
0.1.1

softwrap
jsturtevant
1.0.2

Go
lukehoban
0.6.53

debugger-for-chrome
msjsdiag
2.5.1

Material-theme
zhuangtongfa
1.0.3

Steps to Reproduce:
This is a Heisenbug--I can't find a reliable way to reproduce it.

Bring focus to the text window.
Press Command-A
Observe nothing happens.

I'm on macOS and i don't have this issue.

Please keep an eye out and if you find any reproducible steps, reopen the issue. Sorry about it, but there's no action I can take unless we can somehow reproduce.


When using ZIP package, some ps1xml files (PsReadline and Microsoft.PowerShell.Utility) are not trusted

Steps to reproduce
Download ZIP from GitHub releases here using the latest version of Chrome on Windows (I tried not only 6.1.1 but also 6.0.5). The ZIP does not seem to be signed, the properties on the zip show me that not everything is being trusted.

If I then extract it, and execute pwsh.exe, I get prompts about parts of PowerShell Core not being trusted.
PowerShell 6.1.1
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/pscore6-docs
Type 'help' to get help.

Do you want to run software from this untrusted publisher?
File C:\users\cberg\downloads\powershell-6.1.1-win-x64\Modules\PSReadLine\PSReadLine.format.ps1xml is published by
CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US and is not trusted on your system.
Only run scripts from trusted publishers.
 Help (default is "D"): r

Do you want to run software from this untrusted publisher?
File
C:\users\cberg\downloads\powershell-6.1.1-win-x64\Modules\Microsoft.PowerShell.Utility\Microsoft.PowerShell.Utility.psm
1 is published by CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US and is not trusted
on your system. Only run scripts from trusted publishers.
 Help (default is "D"): r
Loading personal and system profiles took 5298ms.

Expected behavior
All files shipped as part of PowerShell are completely trusted at runtime and I do not get any prompts when opening pwsh the first time or have to unblock the zip.
Actual behavior
Some files shipped as part of PowerShell are not being trusted, this includes:

PSReadline.ps1xml
Microsoft.PowerShell.Utility.psm1
WSMan.format.ps1xml (came up during tab-completion)

Environment data
Name                           Value
----                           -----
PSVersion                      6.1.1
PSEdition                      Core
GitCommitId                    6.1.1
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

This is a standard behaviour of Windows when downloading ZIPs from untrusted zones. If you unblock the ZIP before extracting the files, then the extracted files will not be blocked. I don't know that you can sign ZIP files.

Whilst that is true, my point was rather that PowerShell can still execute fine inside the not unblocked extracted zip because it trusts the binaries due to them being signed except for a few ps1xml files (despite them being signed as well).
To me it would be nice if everything just worked even when not being unblocked, given that 98% works already, I think that's not unreasonable.

This doesn't repro with PS7 preview.6

Yes, I can confirm, it does not happen with 7.0-preview6 or 6.2.2 any more


set expansion width to only expand till the width of the button no more

set expansion width to only expand till the width of the button no more
i've tried to change in equations but couldn't manage to solve it
i've asked here too
http://stackoverflow.com/questions/32287775/mgswipetablecell-control-expanding-width-swift

you can set enableSwipeBounces = NO in 1.5.4


mark as complete added and clear all tasks added

mark as complete feature added and clear all tasks feature added

Nice work! @HemanthTigga


Broken link to activate / inve / Prefer Subshells discussion

From the README:

Pew is written in pure python and leverages inve: the idea for a better activate script.

That link, https://gist.github.com/datagrok/2199506, now refers to "Prefer Subshells for Context."
That link,  https://datagrok.org/python/activate/, is now 404 not found.
Thankfully, archive.org saved it at https://web.archive.org/web/20201111231240/https://datagrok.org/python/activate/
But perhaps someone knows a better more permanent, live page?

Huh, oops - somehow this got created twice. Edited version is #230


Import is broken

After upgrading new release I started to get import errors.
{
"errorType": "Error",
"errorMessage": "Cannot find module '/var/task/node_modules/gpt-tokens/dist/index.ts' imported from /var/task/index.js\nDid you mean to import gpt-tokens/dist/index.js?",
"code": "ERR_MODULE_NOT_FOUND",
"url": "file:///var/task/node_modules/gpt-tokens/dist/index.ts",
It looks like package.json export has wrong dist file for "import", should be index.d.ts
"exports": {
".": {
"import": "./dist/index.ts",
Previous version 1.2.0 works well.

This is indeed a serious issue, thanks for your feedback
I fixed this issue in v1.3.3
...
"exports": {
        ".": {
          "types": "./dist/index.d.ts",
          "import": "./dist/index.js",
          "require": "./dist/index.js"
        }
    }
...


Colored bitmap fonts

Does this project have any interest in supporting bitmap fonts?  These are useful for high performance contexts as well as highly stylized contexts, i.e. videogames.

Since no-one seems to be against it, I'll chime in to say we would like to support these. We just need a courageous soul to step up and implement.

Thinking about this again with a little more of the rusttype api in my mind, I'm not sure bitmap fonts fit rusttype well. Drawing is all about alpha coverage and the gpu cache is specialized for handling sub-pixel positioning.
I'd be inclined to use different reasoning for a bitmap font, no need for cpu rasterization at all and no need for sub-pixel consideration (other than locking to pixels maybe).
So maybe another library is best placed to handle this, and we can specialise rusttype on outline fonts.


Removed deprecated agentConfig option locations

Motivation
They were actually intended to be removed in 6.0

Codecov Report

Merging #2488 into master will increase coverage by 7.26%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2488      +/-   ##
==========================================
+ Coverage   84.53%   91.79%   +7.26%
==========================================
  Files         626       10     -616
  Lines       35160      378   -34782
  Branches     4282       49    -4233
==========================================
- Hits        29723      347   -29376
+ Misses       4148       25    -4123
+ Partials     1289        6    -1283


Ensure variadic call is null-terminated

Noticed on https://qa.debian.org/excuses.php?package=vips.

I'm not sure who maintains ruby-vips in Debian, it's still on v2.1.4.
@gcsideal FYI: backporting this PR should help migrate libvips to 8.16.0 in Debian.

Ooop, bad oversight. Well done for finding this!

I'm not sure who maintains ruby-vips in Debian, it's still on v2.1.4.

The tracker page of ruby-vips contain the information: Jongmin Kim and Utkarsh Gupta.
No, libvips 8.6.0 will not migrate even with this fix. It has a build time testing regression on s390x, sparc64 and hppa at least. It seems the 'testing sample.jpg pfm ... save / load difference' is too big. Need further checking.

Thanks for the information! PR https://github.com/libvips/libvips/pull/4242 should fix these test failures on little-endian systems.

Thanks for the information! PR libvips/libvips#4242 should fix these test failures on little-endian systems.

Can be, but unfortunately the mentioned architectures are big-endian ones. Do you have a fix for these as well?

Apologies, I meant big-endian machines. I was confused due to the changelog note added in commit https://github.com/libvips/libvips/commit/f06db0f9161aa98a026dc7705eef3e33874316d6.

ChangeLog note will be fixed via PR https://github.com/libvips/libvips/pull/4246.


Multi-device evaluation with data parallel

Hi team.
I followed this issue to use multiple gpus for evaluation. However, the multi-gpu you implemented seems to be in model parallel, instead of data parallel, which actually makes the evaluation even slower... How to use data parallel in lm-eval?
Thanks!

I have the same problem here!

OpenComapss provides efficient evaluation support for LLM, https://github.com/InternLM/opencompass
Feel free to try OpenCompass.

Hi! we currently support data-parallel evaluation in the big-refactor branch, which will be our new version release once we have finished porting all currently supported branches to it. This branch is much faster than the current main branch!


Update index.js

just add the () to renderDropdownImage to execute the customized function of the developer. this worked for me

renderDropdownImage didn't work for me as it just need () to be executed


Keystore overhaul (final)

Closes https://github.com/paritytech/substrate/issues/13556

Within this PR:

CryptoTypePublicId type has been removed
Keystore trait methods with explicit crypto primitive
The Keystore::sign_with method has been retained. But a default implementation has been provided in the trait definition. In the end this is a convenience method that can be used in some specific use cases (to prevent code duplication in all the cases where the key is generic such as AURA).

nevertheless in all the places where we can use the explicit keystore methods we save the casts to and from raw byte vectors that by definition are fallible (but in our use cases were infallible)

Trivial renaming of AppKey trait to AppCrypto. The trait is implemented by types from which the whole set of application crypto types and const can be retrieved (by signatures as well). Thus this new name fits better
CRYPTO_ID in AppCrypto been retained because without it sign_with can't work

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2575565

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2575559

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2575558

bot merge


Debian: Update distro colors

Change the c2 color for Debian distro for a 256-base magenta color. This
color for the distro logo resembles the original color of Debian
logotype.

I guess this won't be accepted. See https://github.com/dylanaraps/neofetch/pull/1517#issuecomment-668115245


[Menu] support keyboard navigation with sections

I'd like to be able to organise my MenuItem inside sections and still have proper keyboard navigation.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
When using quite long menu list, we would like to split the items into sections separated by dividers. A section can optionally have a title. This works fine in term of UI, but we lose keyboard support.
On the Autocomplete side, there is the Grouped demo that is quite close to what we want to achieve, except for the dividers.
We basically would like to support a similar behaviour with MenuList and MenuItem.
Maybe this is already possible but I'm missing something 😅
Examples 🌈
Demo: https://codesandbox.io/s/material-demo-forked-jk6hv

Hi, can I work on this issue?

From what I can see, this issue of not being able to navigate the Menu using the keyboard's: "keydown" and "keyup" buttons, is being generated because off adding tags like <div> and <b>. However, there seems to be no issue, when the only the <Divider> component is placed among MenuItems

I'd like to grab this for hacktoberfest, please!

I'd like to work on this issue.

@krishak1205 You can provide a review on #23073

This has been implemented in the Unstyled Menu. There's a demo in the docs that shows it ion action: https://mui.com/base/react-menu/#wrapping-menuitems


Add gpt-3.5-turbo-16k model to encoding mapping support

Fixes #19

Thanks a lot for your contribution!


[Improvement] Improve the table display on the optimizing tables page

Why are the changes needed?

Close #3275
Brief change log

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

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

Thanks for the work! @chouchouji
Thanks for the review! @zhongqishang


Calling Activate on window hidden through Hide extension function can crash

We observed that on some machines, calling Activate on a window hidden through the Hide extension function can occasionally crash with the following error message:
System.Runtime.InteropServices.COMException: 'The operation identifier is not valid. (0x800710DD)'
The debug output shows an error message along the lines of Cannot activate a closed or disposed window.

From email thread:
@dotMorten :

Is something holding on to the Window instance? Ie is it getting garbage collected?
Is it 100% reproducible on those machines, or is it still random when it happens?
Also please enable native debugging, and then get the full stacktrace and (hopefully) improved error message you get when you do.
Lastly can you share the non-paraphrased version of the error message you see in the output window?

@chingucoding :

Regarding reproducibility:
There are machines where the code works fine every time, there are machines where this happens occasionally and from what I understood, at least one machine reproduces this 100% of the time.
Regarding the other questions, unfortunately, a customer noticed this and I’ll have to wait for their reply since I can’t reproduce this locally.

They just got back to me and it seems that this issue does no longer occur with the WASDK 1.1.0.

@chingucoding Awesome. Thank you for the follow-up


SW-5745 Add created/modified info to CohortPayload

The web app needs to show when cohorts were created and modified, and by whom;
return that information with the other data about a cohort.

#2323  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite


Feature Request: Restricted verbiage in Feature/Scenario/Step names

I'm not sure if others will want a rule like this, but it would be nice to restrict verbiage in naming conventions.  My team has a nasty habit of using terms such as "verify" or "validate" in Feature/Scenario/Step names and it drives me crazy.

Hi!
It could be good starting to design how does the rule works.
We can make a rule that forbid or force some words in certain steps following the structure that we have for indentation rule:
{
  "name-of-the-rule-to-define" : ["on", {
    "When": {
      "startsWith": "the user"
    },
    "Then": {
      "includes": "shall",
      "notIncludes": ["verify", "validate"]
    }
  }]
}

Cheers!

Similarly, I'd like a rule that would disallow certain steps (so that debugging steps aren't commited). For instance, in Behat/Mink there is a debugging step definition And show last response that would be great to configure to disallow.

Published with v3.3.0


MSL compiler on iOS chokes on memory_scope_device

MSL compiler on iOS chokes on memory_scope_device.
[***MoltenVK ERROR***] VK_ERROR_INITIALIZATION_FAILED: Shader library compile failed (error code 3):
Compilation failed:

program_source:58:57: error: use of undeclared identifier 'memory_scope_device'
        threadgroup_barrier(mem_flags::mem_threadgroup, memory_scope_device);
                                                        ^

Appears in Sascha Willems Compute N-body example.
macOS is fine. And I thought this was working on iOS as well in the past.

Fixed in #785.


Create hbhgkj.txt

@xjfnet Could you please confirm that students and teachers in your university have an email address pattern like<EMAIL_ADDRESS>Thank you.

the email address pattern like<EMAIL_ADDRESS>thanks

@xjfnet I corrected the file name. Pull request merged. Thank you!


Shairport binary

What is the purpose of shairport binary? As I understand shairport.pl and hairtunes is doing all functionality.
Can we remove it if it's not needed anymore?

It's for embedded systems. It's much more lightweight than shairport.pl + Perl.

It's a pure C alternative to shairport.pl+hairtunes, useful in embedded
Linux and other low-resource situations - Perl is fat.


fix: disable stx transfer if data is not fetched

Try out Leather build b4aee79 — Extension build, Test report, Storybook, Chromatic

This pr disables submit stx transfer btn if all necessary data (balance and nonce) is not fetched yet, which leads to transactions.spec test errors

Let's include in https://github.com/leather-io/extension/pull/5726 once code reviewed


Updated issue templates from .github.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Coming from https://github.com/opensearch-project/.github/issues/64, updated issue templates for bugs and features.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

CI is 😢

The fix for the flaky test is merged, a merge from main should fix the failing tests.


[Task]: Fill Runner Metrics support gap in Sources

What needs to happen?
It is found some runners does not support reporting metrics in

BoundedSource.split()

Direct runner
non-portable Flink runner
non-portable Spark runner
unknown - Samza runner, AttemptedMetrics tests are excluded altogether

Dataflow runner (legacy / runner v2) are supported.

BoundedReader.advance()

Spark Structured Streaming Runner

Notably, portable runners support metrics report in split, as it executes Source as a splittable DoFn, at the point the metrics container is present
This task is created to track these gaps.
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components

[ ] Component: Python SDK
[X] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Infrastructure
[X] Component: Spark Runner
[X] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

By saying unsupported, the following log is seen:
Direct runner:
[Test worker] ERROR org.apache.beam.sdk.metrics.MetricsEnvironment - Unable to update metrics on the current thread. Most likely caused by using metrics outside the managed work-execution thread:
  java.lang.Thread.getStackTrace(Thread.java:1564)
org.apache.beam.sdk.metrics.MetricsEnvironment.getCurrentContainer(MetricsEnvironment.java:140)
org.apache.beam.sdk.metrics.DelegatingCounter.inc(DelegatingCounter.java:76)
org.apache.beam.sdk.metrics.DelegatingCounter.inc(DelegatingCounter.java:67)
org.apache.beam.sdk.metrics.MetricsTest$CountingSourceWithMetrics.split(MetricsTest.java:495)
org.apache.beam.runners.direct.BoundedReadEvaluatorFactory$InputProvider.getInitialInputs(BoundedReadEvaluatorFactory.java:217)
org.apache.beam.runners.direct.ReadEvaluatorFactory$InputProvider.getInitialInputs(ReadEvaluatorFactory.java:88)
org.apache.beam.runners.direct.RootProviderRegistry.getInitialInputs(RootProviderRegistry.java:80)
org.apache.beam.runners.direct.ExecutorServiceParallelExecutor.start(ExecutorServiceParallelExecutor.java:161)
org.apache.beam.runners.direct.DirectRunner.run(DirectRunner.java:213)
...

Flink runner:

This is different from a log ususally seen when reporting metrics in a callback thread
https://github.com/apache/beam/blob/89d5e2f29615c1d4dba41c42a2161d5c5d5f39a8/sdks/java/core/src/main/java/org/apache/beam/sdk/metrics/MetricsEnvironment.java#L144
here Java core's isMetricsSupported() returns true, but not actually supported by the runner. So this is a feature gap rather than WAI by spec


Display } instead of Ctrl + Alt + 0 possible?

On may German Keyboard I hit AltGr-0 to get }.
Carnac displays Ctrl+Alt+0. Is it possible to configure Carnac, so that } is displayed.
(this is only an example. same issue for other keys like {[]~ )
thanks, Jörg

Hey coders, I will try to solve this issue! I am a first time contributer so please tell me if there are rules i should follow


Content types in React Native

Support for content types in React Native
Typescript

[ ] content codec interface
[ ] client.register(codec)
[ ] ContentTypeIdBuilder

Native modules (swift & kotlin)

[ ] client register
[ ] content codec wrapper
[ ] ContentTypeIdBuilder

Test

[ ]  Write a unit test or implement in example app

Just to add some context here, right now our RN sdk only supports one content type: Text. We want to support more content types which means we need a few things:
Defining and consuming content types in React Native
Content types are defined by creating a ContentTypeId (see example here). We'll need to introduce that type to our React Native SDK.
Once you've got your content type, you need to define a codec so that the client knows how to serialize whatever type of content you're trying to send (in our example, Attachment is the type of content we're trying to send). Adding codec support to React Native will consist of introducing a ContentCodec interface that codecs can implement as well as its supporting types like:

EncodedContent Represents the serialized encoded content. This is backed by a protocol buffer which enables us to send it over the network
CodecRegistry A list of codecs stored by the client, keyed by a ContentTypeId. Content types must be registered before they can be used.

Sending messages with a content type
Once the basics of content types are introduced we'll need to actually be able to use them. We'll need to modify conversations.send to take content options:
const number: number = 123
await conversation.send(number, {
  contentType: ContentTypeNumber, // Assume we've defined a Number content type
  contentFallback: "a string that gets used when clients don't know this type"
})

This will require some changes to our native code. I think the best approach might be to expose a way to send EncodedContent directly in swift/kotlin. That way we could just use a codec react native to get EncodedContent, serialize that so that we can pass it to the native code, then the native code can send without needing to know about the codecs.
Receiving messages with a content type
We'll need to teach the RN decodeMessage method how to deal with non-text content types. I think at a high level we can decrypt the message in the native code to get an instance of EncodedContent, then serialize it and pass it back to the RN code. This might be a bit tricky because we're just using JSON for serializing in native -> RN code and JSON doesn't support binary, but I think we can figure that out in a follow up if we just have the basics done.
--
I think those are the broad strokes of what needs to happen here. Feel free to hit me up with any questions at any time!

For reference, here's the PR that introduced content types into the iOS SDK. It's not going to be the same with RN but it should give a sense of all the moving parts: https://github.com/xmtp/xmtp-ios/pull/26.

@nakajima Are Javascript ContentCodecs going to be portable to the RN SDK with this feature? Feels like that would be pretty slick. Write the codec once, publish it as a package, and then you can import it in both your web and mobile SDKs.

Closed with merging of https://github.com/xmtp/xmtp-react-native/pull/63


ip not found in dhcp leases

dhcp problem for me too.
(atomotic) DBG | Not there yet 1/60, error: IP not found for MAC 3a:47:46:45:cf:32 in DHCP leases
(atomotic) DBG | operation not supported by device
(atomotic) DBG | xhyve: illegal option -- F

following the full debug:
xhyve
xhyve -v
xhyve: 793d17

docker-machine
docker-machine -v
docker-machine version 0.5.5, build

run
➜  ~  docker-machine -D create --driver xhyve atomotic
Docker Machine Version:  0.5.5, build
Found binary path at /Users/raffaele/go/bin/docker-machine-driver-xhyve
Launching plugin server for driver xhyve
Plugin server listening at address <IP_ADDRESS>:61674
() DBG | operation not supported by device
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetCreateFlags
Found binary path at /Users/raffaele/go/bin/docker-machine-driver-xhyve
Launching plugin server for driver xhyve
Plugin server listening at address <IP_ADDRESS>:61678
() DBG | operation not supported by device
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(atomotic) Calling .GetMachineName
(atomotic) Calling .DriverName
(atomotic) Calling .GetCreateFlags
(atomotic) Calling .SetConfigFromFlags
Running pre-create checks...
(atomotic) Calling .PreCreateCheck
(atomotic) DBG | ===== Docker Machine xhyve Driver Version 0.2.1 (HEAD) =====
(atomotic) DBG |
(atomotic) DBG | executing: /usr/local/bin/VBoxManage -v
(atomotic) DBG | STDOUT: 5.0.10r104061
(atomotic) DBG |
(atomotic) DBG | STDERR:
(atomotic) Calling .GetConfigRaw
Creating machine...
(atomotic) Calling .Create
(atomotic) DBG | local Boot2Docker ISO version:  v1.9.1
(atomotic) Copying /Users/raffaele/.docker/machine/cache/boot2docker.iso to /Users/raffaele/.docker/machine/machines/atomotic/boot2docker.iso...
(atomotic) Creating VM...
(atomotic) DBG | Mounting boot2docker.iso
(atomotic) Extracting vmlinuz64 and initrd.img from boot2docker.iso...
(atomotic) DBG | executing: &{/usr/bin/hdiutil [hdiutil attach /Users/raffaele/.docker/machine/machines/atomotic/boot2docker.iso -mountpoint /Users/raffaele/.docker/machine/machines/atomotic/b2d-image] []  <nil> 0xc82002c010 0xc82002c018 [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>} attach /Users/raffaele/.docker/machine/machines/atomotic/boot2docker.iso -mountpoint /Users/raffaele/.docker/machine/machines/atomotic/b2d-image
(atomotic) /dev/disk3          	                               	/Users/raffaele/.docker/machine/machines/atomotic/b2d-image
(atomotic) DBG | Extracting vmlinuz64 into /Users/raffaele/.docker/machine/machines/atomotic
(atomotic) DBG | Extracting initrd.img into /Users/raffaele/.docker/machine/machines/atomotic
(atomotic) DBG | Unmounting boot2docker.iso
(atomotic) DBG | executing: &{/usr/bin/hdiutil [hdiutil detach /Users/raffaele/.docker/machine/machines/atomotic/b2d-image] []  <nil> 0xc82002c010 0xc82002c018 [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>} detach /Users/raffaele/.docker/machine/machines/atomotic/b2d-image
(atomotic) "disk3" unmounted.
(atomotic) "disk3" ejected.
(atomotic) Generating 20000MB disk image...
(atomotic) DBG | executing: &{/usr/bin/hdiutil [hdiutil create -megabytes 20000 -type SPARSEBUNDLE /Users/raffaele/.docker/machine/machines/atomotic/root-volume] []  <nil> 0xc82002c010 0xc82002c018 [] <nil> <nil> <nil> <nil> false [] [] [] [] <nil>} create -megabytes 20000 -type SPARSEBUNDLE /Users/raffaele/.docker/machine/machines/atomotic/root-volume
(atomotic) created: /Users/raffaele/.docker/machine/machines/atomotic/root-volume.sparsebundle
(atomotic) Creating SSH key...
(atomotic) Fix file permission...
(atomotic) DBG | /Users/raffaele/.docker/machine/machines/atomotic/boot2docker.iso
(atomotic) DBG | /Users/raffaele/.docker/machine/machines/atomotic/config.json
(atomotic) DBG | /Users/raffaele/.docker/machine/machines/atomotic/id_rsa
(atomotic) DBG | /Users/raffaele/.docker/machine/machines/atomotic/id_rsa.pub
(atomotic) DBG | /Users/raffaele/.docker/machine/machines/atomotic/initrd.img
(atomotic) DBG | /Users/raffaele/.docker/machine/machines/atomotic/root-volume.sparsebundle
(atomotic) DBG | /Users/raffaele/.docker/machine/machines/atomotic/vmlinuz64
(atomotic) Generate UUID...
(atomotic) DBG | Generated UUID: 518331EF-99AB-481E-9F89-147C845DE9A6
(atomotic) Convert UUID to MAC address...
(atomotic) DBG | Converted MAC address: ea:7:bc:13:cf:32
(atomotic) Starting atomotic...
(atomotic) DBG | [xhyve -A -U 518331EF-99AB-481E-9F89-147C845DE9A6 -c 1 -m 1024M -l com1,autopty -s 0:0,hostbridge -s 31,lpc -s 2:0,virtio-net -s 3,ahci-cd,/Users/raffaele/.docker/machine/machines/atomotic/boot2docker.iso -s 4:0,ahci-hd,/dev/rdisk3 -f kexec,/Users/raffaele/.docker/machine/machines/atomotic/vmlinuz64,/Users/raffaele/.docker/machine/machines/atomotic/initrd.img,loglevel=3 user=docker console=ttyS0 console=tty0 noembed nomodeset norestore waitusb=10 base host=boot2docker -F /Users/raffaele/.docker/machine/machines/atomotic/atomotic.pid]
(atomotic) Waiting for VM to come online...
(atomotic) DBG |
(atomotic) DBG | Not there yet 1/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG | operation not supported by device
(atomotic) DBG | xhyve: illegal option -- F
(atomotic) DBG | Usage: xhyve [-behuwxMACHPWY] [-c vcpus] [-g <gdb port>] [-l <lpc>]
(atomotic) DBG |              [-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] -f <fw>
(atomotic) DBG |        -A: create ACPI tables
(atomotic) DBG |        -c: # cpus (default 1)
(atomotic) DBG |        -C: include guest memory in core file
(atomotic) DBG |        -e: exit on unhandled I/O access
(atomotic) DBG |        -f: firmware
(atomotic) DBG |        -g: gdb port
(atomotic) DBG |        -h: help
(atomotic) DBG |        -H: vmexit from the guest on hlt
(atomotic) DBG |        -l: LPC device configuration. Ex: -l com1,stdio -l com2,autopty -l com2,/dev/myownpty
(atomotic) DBG |        -m: memory size in MB
(atomotic) DBG |        -M: print MAC address and exit if using vmnet
(atomotic) DBG |        -p: pin 'vcpu' to 'hostcpu'
(atomotic) DBG |        -P: vmexit from the guest on pause
(atomotic) DBG |        -s: <slot,driver,configinfo> PCI slot config
(atomotic) DBG |        -u: RTC keeps UTC time
(atomotic) DBG |        -U: uuid
(atomotic) DBG |        -v: show build version
(atomotic) DBG |        -w: ignore unimplemented MSRs
(atomotic) DBG |        -W: force virtio to use single-vector MSI
(atomotic) DBG |        -x: local apic is in x2APIC mode
(atomotic) DBG |        -Y: disable MPtable generation
(atomotic) DBG | exit status 1 &{0xc8200161e0} &{0xc820016210}
(atomotic) DBG |
(atomotic) DBG | Not there yet 2/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 3/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 4/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 5/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 6/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 7/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 8/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 9/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 10/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 11/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 12/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 13/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 14/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 15/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 16/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 17/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 18/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 19/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 20/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 21/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 22/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 23/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 24/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 25/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 26/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 27/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 28/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 29/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 30/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 31/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 32/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 33/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 34/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 35/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 36/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 37/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 38/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 39/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 40/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 41/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 42/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 43/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 44/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 45/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 46/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 47/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 48/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 49/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 50/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 51/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 52/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 53/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 54/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 55/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 56/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 57/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 58/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 59/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
(atomotic) DBG |
(atomotic) DBG | Not there yet 60/60, error: IP not found for MAC ea:7:bc:13:cf:32 in DHCP leases
open : no such file or directory
notifying bugsnag: [Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting]
Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting

@atomotic Thanks issue :)
Could you try this commands?
rm -f $(which docker-machine-driver-xhyve)
go get -u -d github.com/zchee/docker-machine-driver-xhyve
cd $GOPATH/src/github.com/zchee/docker-machine-driver-xhyve
make
make install

@atomotic  Oh, I understand.
rm -f $(which docker-machine-driver-xhyve)
go get -u -d github.com/zchee/docker-machine-driver-xhyve
cd $GOPATH/src/github.com/zchee/docker-machine-driver-xhyve
make
make install

or,
# Need Go 1.5 vendoring support
$ export GO15VENDOREXPERIMENT=1

$ go get -u -v -f github.com/zchee/docker-machine-driver-xhyve
$ sudo chown root:wheel $GOPATH/bin/docker-machine-driver-xhyve
$ sudo chmod u+s $GOPATH/bin/docker-machine-driver-xhyve

i had already installed using go get, but without make.
i tried with make, now i got /usr/local/bin/docker-machine-driver-xhyve but the error is the same

@atomotic Hmm...
Could you try this commands?
# Cleanup all docker-machine-driver-xhyve binary
$ rm -f $(which docker-machine-driver-xhyve)
# Testing not exists docker-machine-driver-xhyve binary
$ which -a docker-machine-driver-xhyve

# Re-install docker-machine-driver-xhyve
$ export GO15VENDOREXPERIMENT=1
$ cd $GOPATH/src/github.com/zchee/docker-machine-driver-xhyve
$ make
$ make install

nothing.

@atomotic nothing?
Sorry, I don't understand :(

@atomotic FYI, See https://github.com/zchee/docker-machine-driver-xhyve/issues/59

👍it works! many thanks.

@atomotic :tada:


vscode-cue: Define CUE TextMate grammar in CUE

Currently, the CUE TextMate Grammar is generated from a rather elegant Go specification.
However, as noted in https://github.com/cue-sh/vscode-cue/pull/12#issuecomment-889636913, the TextMate grammar exists in a JSON Schema form (there may be a more official location).
Hence we could quite easily move the specification of the CUE TextMate Grammar from Go to CUE, and have the code generation step be a cue export command (again, making sure this is part of CI).
@betawaffle - thoughts on this?

the TextMate grammar exists in a JSON Schema form (there may be a more official location).

that is the 'official' VSCode location
I don't think TextMate 2.0 has a schema AFAIK
I've made a slightly improved schema here


_Py_IDENTIFIER macro expansion issue

Im trying to build Pyjion using VS 2015 Update 3, cl Compiler Version 19.00.24224. When I build pyjion.sln, the build fails on _Py_IDENTIFIER macros. (The first one being here) It seems the designated initializer the macro expands to is not valid. This seems strange to me, and Im not sure where to proceed. The full output log is https://gist.github.com/ethanhs/2538016e4b8e9b80b20d8cd56e06a996
Im not sure why this would fail exactly. The same macro is used without issue in CPython sources, which worked fine with the same compiler. I was hoping to get some guidance on what the issue could be. I have tried re-installing Visual Studio to no avail.

I think this is a bit of syntax VS 2015 doesn't support.  We should upgrade to VS 2017 where I'm assuming this is supported and works.  I've just been rolling back to the old macro definition when I've been building with VS 2015

@DinoV Thanks for the advice! When I build .net core, it seems to demand VS 2015, which is why I suggested we update to the new 2.0 preview 2. Does that make sense?

Yep, upgrading does make sense...  I'll probably start tackling that after getting Unix support building first.

Actually, I think it might be better to move to core 2.0 first, as that should make changing to cmake easier (which I'd be happy to work on), which makes porting to Unix easier.

I'm fine with doing the .NET core 2.0 update first to make it easier if @DinoV doesn't have an issue with it.

I'm taking @DinoV 's silence as acceptance, so if you still have interest in this, @ethanhs , feel free to push a PR to upgrade to .NET Core 2.0 first.

I still have interest, time would be of the issue. :) I'll see what I can do.

@ethanhs 😄 It's open source, so no expectations and whatever you can spare is appreciated!

It turns out that C++11-17 do not support designated initializers, so this may be an issue with Python from what I can gather. this commit added designated initializers. @brettcannon if you think I should, I can open a bug on bpo and make a patch.


Clear the batch store on view change

Description
This changeset clears the batch store on view change, does not start the request timer when not in an active view, and decreases the batch timeout to be less than the request timeout.
Usual SMEs are @kchristidis @corecode and @tuand27613 .
This addresses #1874 which is a candidate for inclusion in 0.5 so this PR should be considered for inclusion as well @srderson
Motivation and Context
This is intended to address symptoms of #1874 as well as a duplicated deploy transaction seen in busywork.
If a replica was a primary and had a transaction in its batch store when the view change timer expired, it would include that request in the next batch when it became primary again, leading to transaction duplication.
If only a single request came in, then the view change timer would expire before the batch was created, and the network would view change over and over again until another request came in, never executing the first request.
Finally, while processing a new view, it was possible for the request timer to start, negating the doubling of the new view timer.
How Has This Been Tested?
This has been tested against the busywork stress2b test, and a new unit test checking for the batchStore emptying on view change has been added.
Checklist:

[X] I have added a Signed-off-by.
[X] I have either added documentation to cover my changes or this change requires no new documentation.
[X] I have either added unit tests to cover my changes or this change requires no new tests.
[X] I have run golint and have fixed valid warnings in code I have added or modified. This tool generates false positives so you may choose to ignore some warnings. The goal is clean, consistent, and readable code.

The continuous integration build process will run make checks to confirm that tests pass and that code quality meets minimum standards. You may optionally run this locally as PRs will not be accepted until they pass.
Signed-off-by: Jason Yellick<EMAIL_ADDRESS>

Can you add a warning to obcpbft/config.yaml to have different values for timeout_batch and timeout_request  ?

@tuand27613 Done, I've also included some checks in the code to prevent people from misconfiguring.  If the timeouts are wrong, it will pick some based on the batch timeout, and issue a warning in the logs that it is overriding the config.

This is good to go and needs to go in. @srderson

oh wow. yes!

@srderson @binhn @ghaskins Any feedback on the inclusion of this?

LGTM. Thanks.


When adding a comment block to the end of a file and hitting "enter" within the code block the files contents are cleared

How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
Windows
What is the issue affecting?
Formatting
Expected Behaviour
That it doesn't clear the files content. No real action is required from the formatter during this action.
Actual Behaviour
That it's clearing the files contents.
Reproduction steps
Have a new file with some content, add a comment block to the end of the file and add a new line within the content block, the file is cleared.
I know its Sumneko as it doesn't happen when I disable the extension. It only started in the last version or 2.
Start with file content:
local x = 1

Press enter a few times to get some empty lines
Type --[[ and it auto completes the closing ]]
Press enter to add a new line, with the intention of typing within the comment block. The file is cleared at this point.
Video of the issue occuring.

Additional Notes
No response
Log File
file_c%3A_Home_Projects_Factorio%20Modding_Factorio-JD-Plays.log
service.log

@CppCXY

I can't reproduce, can others reproduce it?
currently you can choose to turn off format on type

ah balls, I forgot I had a Sumneko plugin present.
When I remove the plugin the issue doesn't occur.
Tried with and without the plugin twice and its reproducible. I will raise with the plugin maker.
Sorry.

I reproduce this, by install the plugin. maybe the result of 'type on format'  is handled by plugin mechanism, or error handling by plugin.

So the plugin creator made a suggestion, which they believe shows its a Sumneko core issue and not a Plugin specific issue.
I added a dummy plugin to my workspace, set the plugin path to this and the issue still occurred.
I confirmed the real plugin wasn't being loaded, as the real plugin changes the scope of a global variable called global to include the workspace name, but in this test the global scope was still just global.
Dummy plugin:
root of workspace\plugin\plugin.lua
function OnSetText()
  return {}
end

Set Sumneko to use this dummy plugin at the workspace settings level:
"Lua.runtime.plugin": "/plugin/plugin.lua"
I close VS Code, make the changes and then open it up clean.
Reproduced issue with this dummy plugin active then used "undo" to return the code back to how it was at the fresh load.
log.zip

I cannot reproduce it, did you triggered formatting?
Please try to disable formatthing/range formating/type formating.

I can reproduce it with range formatting now.


Add support for @inheritdoc

I have a base class that defines the @param types, names, and descriptions. I extend the base class that overrides one of the methods of the base class. However, when using @inheritdoc ESLint doesn't provide any information of the object from the parameter that I'm referencing.
foo.js
class Foo {

    /**
     *
     * @param {Entity} entity -
     * @param {string} attribute -
     */
    something(entity, attribute) {
         // do stuff with the arguments,
    }
}

bar.js
class Bar extends Foo {

    /**
     *
     * @inheritdoc
     */
    something(entity, attribute) {
         // do other stuff with the arguments,
    }
}

I would expect auto-complete and hints for the Entity type in Bar#something since it's defined in Foo#something. However, unless I copy the same comment block into bar.js I don't get any hinting for the entity param type like I do in Foo#something

This has nothing to do with ESLint itself. Moving to TypeScript which powers the JS experience in VS Code.


Update class names

Some of the class names need updating...?

I don't even remember why I wrote this issue, and going off the "...?" I wrote at the end I never understood it either


Implement persist_docs

dbt  has a configuration option to persist documentation to the database:
https://docs.getdbt.com/reference/resource-configs/persist_docs
Attempting to use it with the sql server adapter results in:
ERROR: alter_relation_comment macro not implemented for adapter sqlserver
ERROR: alter_column_comment macro not implemented for adapter sqlserver

Feature Request: implement the above

There is a semi-standard in the form of the MS_Description extended property. This is what SSMS surfaces for columns if you use the table designer, and it surfaces it for tables if you use the Diagram Designer and choose the table properties. Power BI appears to have no support, at least it doesn't show anything if you're browsing tables in the import. I have no idea how widespread support for MS_Description is among third-party tools, but as a pick for something to use for persisting a description it's certainly better than nothing.

I had a need for this feature using MS_Description.  A few of our tools use it as default to pull out descriptions such as redgate tools, azure purview and I assume a few others.  It may be useful to make MS_Description configurable if there is a need. I've attached what is working for us...
`
{% macro sqlserver__alter_column_comment(relation, column_dict) -%}
{%- set existing_columns = adapter.get_columns_in_relation(relation) | map(attribute="name") | list %}
{%- for column_name in column_dict if (column_name in existing_columns) %}
{%- do log('Alter extended property "MS_Description" to "' ~ column_dict[column_name]['description'] ~ '" for ' ~ relation ~ ' column "' ~ column_name ~ '"', info=false) %}
IF NOT EXISTS (
SELECT NULL
FROM SYS.EXTENDED_PROPERTIES AS ep
            INNER JOIN SYS.ALL_COLUMNS AS cols
                ON cols.object_id = ep.major_id
                AND cols.column_id = ep.minor_id

        WHERE   ep.major_id = OBJECT_ID('{{ relation }}')
        AND     ep.name = N'MS_Description'
        AND		cols.name = N'{{ column_name }}'
    )
        EXECUTE sp_addextendedproperty      @name = N'MS_Description', @value = N'{{ column_dict[column_name]['description'] }}'
                                            , @level0type = N'SCHEMA', @level0name = N'{{ relation.schema }}'
                                            , @level1type = N'{{ relation.type }}', @level1name = N'{{ relation.identifier }}'
                                            , @level2type = N'COLUMN', @level2name = N'{{ column_name }}';
    ELSE
        EXECUTE sp_updateextendedproperty   @name = N'MS_Description', @value = N'{{ column_dict[column_name]['description'] }}'
                                            , @level0type = N'SCHEMA', @level0name = N'{{ relation.schema }}'
                                            , @level1type = N'{{ relation.type }}', @level1name = N'{{ relation.identifier }}'
                                            , @level2type = N'COLUMN', @level2name = N'{{ column_name }}';
{%- endfor %}

{%- endmacro %}
{% macro sqlserver__alter_relation_comment(relation, relation_comment) -%}
{% do log('Alter extended property "MS_Description" to "' ~ relation_comment ~ '" for ' ~ relation, info=false) %}
IF NOT EXISTS (
    SELECT NULL
    FROM SYS.EXTENDED_PROPERTIES AS ep
    WHERE   ep.major_id = OBJECT_ID('{{ relation }}')
    AND     ep.name = N'MS_Description'
    AND     ep.minor_id = 0
)
    EXECUTE sp_addextendedproperty      @name = N'MS_Description', @value = N'{{ relation_comment }}'
                                        , @level0type = N'SCHEMA', @level0name = N'{{ relation.schema }}'
                                        , @level1type = N'{{ relation.type }}', @level1name = N'{{ relation.identifier }}';
ELSE
    EXECUTE sp_updateextendedproperty   @name = N'MS_Description', @value = N'{{ relation_comment }}'
                                        , @level0type = N'SCHEMA', @level0name = N'{{ relation.schema }}'
                                        , @level1type = N'{{ relation.type }}', @level1name = N'{{ relation.identifier }}';

{% endmacro %}
`

I had a need for this feature using MS_Description. A few of our tools use it as default to pull out descriptions such as redgate tools, azure purview and I assume a few others. It may be useful to make MS_Description configurable if there is a need. I've attached what is working for us...
{% macro sqlserver__alter_column_comment(relation, column_dict) -%}
    {%- set existing_columns = adapter.get_columns_in_relation(relation) | map(attribute="name") | list %}
    {%- for column_name in column_dict if (column_name in existing_columns) %}
        {%- do log('Alter extended property "MS_Description" to "' ~ column_dict[column_name]['description'] ~ '" for ' ~ relation ~ ' column "' ~ column_name ~ '"', info=false) %}
        IF NOT EXISTS (
            SELECT NULL
            FROM SYS.EXTENDED_PROPERTIES AS ep

                INNER JOIN SYS.ALL_COLUMNS AS cols
                    ON cols.object_id = ep.major_id
                    AND cols.column_id = ep.minor_id

            WHERE   ep.major_id = OBJECT_ID('{{ relation }}')
            AND     ep.name = N'MS_Description'
            AND		cols.name = N'{{ column_name }}'
        )
            EXECUTE sp_addextendedproperty      @name = N'MS_Description', @value = N'{{ column_dict[column_name]['description'] }}'
                                                , @level0type = N'SCHEMA', @level0name = N'{{ relation.schema }}'
                                                , @level1type = N'{{ relation.type }}', @level1name = N'{{ relation.identifier }}'
                                                , @level2type = N'COLUMN', @level2name = N'{{ column_name }}';
        ELSE
            EXECUTE sp_updateextendedproperty   @name = N'MS_Description', @value = N'{{ column_dict[column_name]['description'] }}'
                                                , @level0type = N'SCHEMA', @level0name = N'{{ relation.schema }}'
                                                , @level1type = N'{{ relation.type }}', @level1name = N'{{ relation.identifier }}'
                                                , @level2type = N'COLUMN', @level2name = N'{{ column_name }}';
    {%- endfor %}
{%- endmacro %}

{% macro sqlserver__alter_relation_comment(relation, relation_comment) -%}
   {% do log('Alter extended property "MS_Description" to "' ~ relation_comment ~ '" for ' ~ relation, info=false) %}

    IF NOT EXISTS (
        SELECT NULL
        FROM SYS.EXTENDED_PROPERTIES AS ep
        WHERE   ep.major_id = OBJECT_ID('{{ relation }}')
        AND     ep.name = N'MS_Description'
        AND     ep.minor_id = 0
    )
        EXECUTE sp_addextendedproperty      @name = N'MS_Description', @value = N'{{ relation_comment }}'
                                            , @level0type = N'SCHEMA', @level0name = N'{{ relation.schema }}'
                                            , @level1type = N'{{ relation.type }}', @level1name = N'{{ relation.identifier }}';
    ELSE
        EXECUTE sp_updateextendedproperty   @name = N'MS_Description', @value = N'{{ relation_comment }}'
                                            , @level0type = N'SCHEMA', @level0name = N'{{ relation.schema }}'
                                            , @level1type = N'{{ relation.type }}', @level1name = N'{{ relation.identifier }}';
{% endmacro %}

this is awesome! can you tell me more about what "working for us"  means? i.e. Purview/redgate can pull out column descriptions no problem? Way cool!

With Redgate Sql Prompt, it will display MS_Description in the tooltip.  Redgate Sql Doc also pulls it as the main description.  I know the SSMS designer uses it too for MS_Descriptions on columns, but I don't know anybody who actually uses the designer in SSMS! I asked my colleague about azure purview and it needed some work apparently to get it to take in MS_Description, so I don't think this standard helps there.

@mahazza Thank you for sharing that code!

@sdebruyn How else I can help?

@semcha
I just added all the new adapter tests to #390. The docs persistence tests in there should be failing right now.
Ideally, your PR #289 would be merged into this branch and would make those tests succeed. That way we are much more certain that both the implementation works and that it works according to how dbt-core expects it to.
So if you would find some time, change the target of your PR to the branch used in #390 and make those persist_docs tests succeed :)
Any help is much appreciated!


Time to release code

When would you release the code?

Hi, Thanks for your interest in our work. As our work is still under review, we plan to release our code in the next few months.


Add right-click to look up on Hiscores

Currently you can copy a player's name to clipboard on click #97, so this issue is not technically needed.


feat: Drop redundant platform script payment

Issue being fixed or feature implemented
What was done?
How Has This Been Tested?
Breaking Changes
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[ ] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

@ogabrielides let's close it as "won't merge"?

Won't merge


Feature search toggler

Added feature to toggle search scope on repos:

This repository (as GitHub).
All repositories (instead of backspacing the scope modifier bar).
Your repositories (repos under your username - not forks - or github user if not signed in).

Not sure if you'll accept this feature having read the README, but I guess you could consider this as suggestion if you don't like my implementation.
https://imgur.com/a/R9114 (I have since corrected the typo in "repository/ies").
Thanks for refined-github.
Best,
Sam.

A related feature was requested in https://github.com/sindresorhus/refined-github/issues/548
The issue with this implementation is that it only works in a repo, so I can only "search my repos" if I'm already in a repo.
Either way I think Algolia's search has improved the search enough that I doesn't need anything else: https://chrome.google.com/webstore/detail/awesome-autocomplete-for/djkfdjpoelphhdclfjhnffmnlnoknfnd


action_status has stream size 100

How did that happen?
This says its 1.

Try running it

Introduced recently


[MM-20469] Transformed emoji_list_item to ts

Migrated components/emoji/emoji_list_item' module and associated tests to TypeScript
Ticket Link
Fixes: https://github.com/mattermost/mattermost-server/issues/15471
JIRA:  https://mattermost.atlassian.net/browse/MM-20469

Hello @Ayanrocks,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@ashishbhate Review

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @jfrerich @emilyacook

/update-branch

is there a reason why it's not being merged? Did I did something wrong? 😕 @cpoile @ashishbhate

@Ayanrocks apologies for the delay. Its the holiday season so reviews are happening a bit slow. Absolutely nothing wrong on your end :)

@Ayanrocks - There are some minor lint issues:
mattermost-webapp/components/emoji/emoji_list_item/emoji_list_item.tsx
  16:26  error  Expected a semicolon  @typescript-eslint/member-delimiter-style
  19:41  error  Expected a semicolon  @typescript-eslint/member-delimiter-style
  21:59  error  Expected a semicolon  @typescript-eslint/member-delimiter-style
  22:6   error  Expected a semicolon  @typescript-eslint/member-delimiter-style

This can be merge now @ashishbhate

Thanks for the effort @Ayanrocks! We can merge this as soon as QA approves the PR. Things are a bit slow at the moment because of the year end break.


Add tracking.dpd.de

Hi there, please consider adding tracking.dpd.de to the whitelist. It is used to see where your packages are, and blocked by https://github.com/mmotti/pihole-regex/blob/master/regex.list#L15
Thank you!

I'm considering removing this particular regexp as there are a lot of false positives.
Could still be useful for those who don't check back and update the regexp list though.


Fixing running on multiple hosts

This pull requests contain two commits:

Adds the option to run the rule without running redis-trib (#46 ). Whenever a user will want to run the role on several hosts, the flag will need to be turned on only for one of the hosts

Receive the play's hosts IP from ansible (which have the actual IPs), instead of reading the IPs from the hosts (#47)

This fix #46 and fix #47

@lihiwish How have you configured the play? There is a counter in the cluter-creator to avoid running the redis-trib more than once. The initial idea of this role was to set serial: 1 when redis is running as cluster.
The two main reason set this are:

During instillation this is the only way to ensure that all nodes are up and running before the cluster meet[https://github.com/idealista/redis-role/blob/0bead5d82f8edc49f454f1dc6f614345c22db526/templates/cluster-creator.sh.j2#L17].
During redis upgrade this ensure each node is removed and added after been upgrade in a safe way. Performing a manual FO or resharding nodes

For the same two reason describe above, despite I think its good idea to set a variable to explicit control the automatic execution of redis-trib. It could be a problem to have nodes that not contains same scripts.

@jdvr Thank you for your comments. I am running the role as part of the dependencies of a different role.
I did not set serial: 1 therefore COUNT_NODES_ON_CLUSTER was always 1.
I will add serial: 1 to my setup and update :)

Hi @lihiwish,
How is it working with serial: 1?

Hi @jnogol
Thanks for asking.
It might take a bit until I'll get the chance to test this. I'll update with my findings.

Hi,
serial: 1 indeed solved the first issue.
I will update the PL to include only "reading IP of host" change


Run Mac test with xcode pre-installed for Engine v2 tester_engine recipes

Both Mac and non-Mac tests are now running without xcode pre-installed: https://flutter.googlesource.com/recipes/+/refs/heads/main/recipes/engine_v2/tester_engine.py#105
This caused unpredictable test failures when a new xcode is being updated. One could succeed if it happens to run on a bot which has already installed xcode, and could fail if the bot does not have the xcode yet.
We should enforce xcode for Mac tests.
More context: https://github.com/flutter/engine/pull/42930

https://flutter-review.googlesource.com/c/recipes/+/46380 to add context support for xcode installation.
https://github.com/flutter/engine/pull/43115 to add context config.
LED run passes:
https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/keyonghan_google.com/57dfaf1802c4b6aeae753e5a70c4993301edf90d88fa6dc06e5296b890434974/+/build.proto

Both landed. Marking as resolved.

The recipes CL broke the engine tree: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux linux_android_emulator_tests/112/overview

https://flutter-review.googlesource.com/c/recipes/+/46620 landed to fix the problem.
All affected targets passed on recent engine commit:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac mac_clang_tidy/704/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux Framework Smoke Tests/12669/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux linux_web_engine/2278/overview
Closing


Add a verbosity flag to the command line

The output produced by this tool can sometimes be a bit much. I've
decided to add a verbosity flag to help control this. Fortunately,
there's a [clap_verbosity_flag] crate that does most of the heavy
lifting for me. It requires switching from println and eprintln to a
logger, but this is probably for the best. I've stripped out the
logger's prefix and done by best to match the current experience,
adjusting a few log levels here and there.
I plan to follow this up with a change that will take advantage of the
flag to control the streaming output as well.

Ugh, forgot to provide the URL for [clap_verbosity_flag].


STM32H723/733, STM32H725/735 and STM32H730 add USB OTG HS

Adds USB OTG HS and internal FS PHY.
Simplifies STM32 USB Kconfig help message.
The USB_DC_STM32 help message started to miss some STM32 MCU families (i.e., H7).
Overtime, the message will get bigger if we continue to list family names.
Removed family names to simplify the message and avoid periodic modifications.

DNM until @erwango had a chance to give +1

Would you mind doing the addition ?

Done.


b4: loosen versions for request and dnspython

Until the next stable release, we need to loosen the version
requirements ourselves by hand for dnspython, since NixOS has updated to
version 2.1. While at it, adjust requests from ~=2.24.0 to ~=2.25 which
effectively enables all 2.* versions for requests.
Fixes the following build error:
  adding 'b4-0.6.2.dist-info/RECORD'
  removing build/bdist.linux-x86_64/wheel
  Finished executing setuptoolsBuildPhase
  installing
  Executing pipInstallPhase
  /build/b4-0.6.2/dist /build/b4-0.6.2
  Processing ./b4-0.6.2-py3-none-any.whl
  Requirement already satisfied: dkimpy~=1.0.5 in /nix/store/3war2scyn6pnrhhcfdx48vd5023x2rkp-python3.8-dkimpy-1.0.5/lib/python3.8/site-packages (from b4==0.6.2) (1.0.5)
  ERROR: Could not find a version that satisfies the requirement dnspython~=2.0.0 (from b4)
  ERROR: No matching distribution found for dnspython~=2.0.0

Motivation for this change
Things done

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

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

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

On Thu, Apr 29, 2021 at 07:13:17AM +0200, Rouven Czerwinski wrote:

@@ -11,7 +11,8 @@ python3Packages.buildPythonApplication rec {
preConfigure = ''
substituteInPlace setup.py \

 --replace 'requests~=2.24' 'requests~=2.25'

 --replace 'requests~=2.24.0' 'requests~=2.25' \

 --replace 'dnspython~=2.0.0' 'dnspython~=2.1'

LGTM
Reviewed-by: William Casarin @.***>


Added Longest Common Subsequence Question

I have completed the task 1 but am stuck in task 2, need help

I have completed the task 1 but am stuck in task 2, need help

Hey please read the raedme.md file very carefully then send PR both task1 and task2 need little bit changes .

okay working on it

made changes, please check @Kushal997-das

LGTM 👍

@S-Swaroop This file contains conflict please send the PR again thanks


Switch from single quotes to doubles and reflect the filename.

The image filename was inconsistent and the image was missing in GitHub preview. Its alt directive has both two single quotes and one possessive asopstophe to cause rendering problem on website.


Error after updating to 2.11.0

Currently using 2.10.6 as part of Bootstrap.VS.Datetimepicker.CSS.
After updating to 2.11.0 I get the attached error.

I am seeing the same problem. 2.10.6 worked fine but now the check to see if a module is loaded throws a module is undefined exception.

Duplicate of #2862

Will be fixed in 2.11.1 soon


Cloudflare failed to publish function

I've added @nuxhub/core to my existing project and tried to publish it on cloudflare as described in the docs
The build is successful but when deploying it fails:
Error: Failed to publish your Function. Got error: Uncaught TypeError: Object prototype may only be an Object or null: undefined   at chunks/routes/api/_hub/index.mjs:1:149243 in hn.exports   at chunks/routes/api/_hub/index.mjs:1:173254

I have no clue as to what this means. I get no further information at all.
The error happens in chunks/routes/api/_hub/index.mjs so I assumed the problems is with @nuxthub/core.
The starter template does work so now I'm a bit lost.
package.json
If I remember correctly, Nuxt automatically bundles dependencies even if they are dev dependencies.
I tried with putting them in dependencies but I still get the same error.
Also, posthog-node is supposed to work in serverless environments according to their docs.
{
  ...
  "devDependencies": {
    "@antfu/eslint-config": "^2.8.0",
    "@axiomhq/pino": "1.0.0-rc.2",
    "@formkit/tempo": "^0.0.15",
    "@iconify/json": "^2.2.190",
    "@nuxt/ui-pro": "^1.0.2",
    "@nuxthub/core": "^0.2.1",
    "@vueuse/core": "^10.9.0",
    "dotenv": "^16.4.5",
    "drizzle-kit": "^0.20.14",
    "drizzle-orm": "^0.29.5",
    "eslint": "^8.57.0",
    "nuxt": "^3.10.3",
    "nuxt-auth-utils": "^0.0.20",
    "pino": "^8.19.0",
    "posthog-js": "^1.111.3",
    "posthog-node": "^3.6.3",
    "valibot": "^0.30.0",
    "vue": "^3.4.21",
    "vue-router": "^4.3.0",
    "wrangler": "^3.31.0"
  }
}

Nuxt info
------------------------------
- Operating System: Darwin
- Node Version:     v20.8.1
- Nuxt Version:     3.10.3
- CLI Version:      3.10.1
- Nitro Version:    2.9.1
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      devtools, extends, modules, imports, nitro, runtimeConfig, ui, routeRules
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

And after a long investigation... the culprit is pino and @axiomhq/pino.
For everyone in the future having this problem... double check your dependencies for Nodejs

Thank you for your feedback and investigation @Gerbuuun
Indeed this is a bit of a struggle to find librairies that work on the edge, hopefully the whole ecosystem will move toward this (with projects like https://jsr.io/)
It reminds me the UI librairies back then that did not support server-side rendering because they were depending on window 😅


Changing the sample_rate of loaded audio file to 16000

Hi,
This pull request adds a line of code to resample the audio after loading it to prevent audio stretching. The original audio was loaded at a sample rate of 48000Hz, but to maintain consistency with the rest of the codebase, it is now resampled to 16000Hz using the torchaudio.functional.resample function.
This change was necessary because the mismatch between the sample rates during loading and processing was causing the audio to stretch, leading to a difference in length of up to 3 times the original audio. By resampling the audio, this pull request ensures that the audio remains at its original length, improving the accuracy of any downstream processing.

Fixed in latest commit