Syntax lookup: Warning decorator

Suggestion for #162
PR should be editable, please feel free edit.

@ryyppy yes, the different syntaxes seem to be working. I tried the following:
@warning("-32")
let x = 0 // No warning here
let x = 1

let y = 0 // "unused value y" warning here
let y = 1

As with your comment on the  @deprecated PR, what do you think about making these separate pages for Syntax Lookup?
Anything else to consider?

Two separate pages are fine. Just let's make it clear that the decorator applies to an expression / module.

@ryyppy PR updated, see what you think.
Also, could I double check something? In the PR I wrote that the decorators are use to enable or disable warnings. Is it correct that they can enable warnings, or are they exclusively used for disabling warnings?

Is it correct that they can enable warnings, or are they exclusively used for disabling warnings?
You can do both: Enable (@warning("+27")) or Disable (@warning("-27"))

Thanks @ryyppy
I've made some tweaks, see what you think.

My concern with issue is that this is a buggy feature which has its use case but very hard to implement it correctly.

Syntax Lookup @@warning is documented now, so let's close this one off.


Osmosis Liquid Pooler - Remove Clock dependency

closes #248

@keyleu LGTM!

@keyleu I think this is ready to be merged.


GitHub Actions Runner VMs are limited to 60GB Disk Space. This means disabling PARSEC Tests

Our GitHub self-hosted Actions Runners run within VMs. These VMs are limited to a 60GB of disk image space. This is sufficient for most tests, but if running PARSEC, we are required to download the PARSEC Disk Image resource, v1.0.0 (http://resources.gem5.org/resources/x86-parsec?version=1.0.0). Unzipped this image is 33GB, which pushes the VM to exaust all it's disk image space. This crashes the VM.
Pull Request #164 disables the tests which use PARSEC.
The PARSEC tests can be re-incorporated when we are able to increase the disk image size on these VMs.

Trying to understand this more, does this mean that gem5, build, etc.  plus the disk image size must currently fit in 60GB?  I.e., what are the other 27GB (=60GB - 33GB) being used for?  I want to understand since a GPU full system test would need a disk of similar size (~31 GB), if one is ever added.

Trying to understand this more, does this mean that gem5, build, etc. plus the disk image size must currently fit in 60GB? I.e., what are the other 27GB (=60GB - 33GB) being used for? I want to understand since a GPU full system test would need a disk of similar size (~31 GB), if one is ever added.

The downloaded zip of the image still exists as it's being unzipped. I think we're short of about 2GB when it's being decompressed and the VM fails. I think the zip is about 12GB. The remainder is the OS, gem5, and the gem5 build. So it's something like:
~33G : The Disk image uncompressed.
~12GB: The Disk image zipped.
~15GB: OS, GitHub Actions runner, gem5, and its dependencies.


fix(versions): update Activiti/example-runtime-bundle versions into master

UpdateBot pushed helm dependency: common to: 1.1.14

UpdateBot commands:
updatebot push-version --kind helm common 1.1.14


attach and detach vue instance to vue devtools

Description
This allows vue devtools to detect the correct Vue instance.
Fixes # (https://github.com/single-spa/single-spa-vue/issues/45)
How Has This Been Tested?
Just using the provided test suite.
Further notes
Note that users have to update to the latest vue devtools extension see https://github.com/vuejs/vue-devtools/issues/874.
To effectively activate devtools for dev purposes, you also have to set the following on application/microfrontend base:
Before you create app, usually in main.js and in your store/index.js if there's any
Vue.config.devtools = process.env.NODE_ENV === 'development'

I tested with the last Vue devtool 5.3.3 and it correctly detects Vue instances even without this PR code. Sorry for that, I didn't realized id before.
I think maybe we can close this PR and suggest users to update their devtools?

Vue devtool 5.3.3 and it correctly detects Vue instances even without this PR code

Oh, cool, I didn't know that. Yeah let's close this then


Format Document for vs code

Please add support for document / code formatting in vs code extension

Hi, I was just asking. Are you working on this one

No, I am not currently working on this one.

Is their a vs code extenion? Can you share a link?

You need to build it. I believe the extension isn't published.
I once packaged it. You can get it from
https://drive.google.com/drive/mobile/folders/10gWxikGFNsfjMrWOJ4exDeBGAEIGMubl?usp=sharing
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Levi @.>
Sent: Sunday, June 13, 2021 5:23:35 PM
To: prominic/groovy-language-server @.>
Cc: Rana Ahmed @.>; Author @.>
Subject: Re: [prominic/groovy-language-server] Format Document for vs code (#18)
Is their a vs code extenion? Can you share a link?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/prominic/groovy-language-server/issues/18#issuecomment-860202302, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFA7ZP5EEKPM5NMXFPOV6U3TSSPMPANCNFSM4KHHBCVQ.

@ahmednrana ahh thanks, I see now its in a directory in this repo. Coolio

Ahh I noticed this feature is apart of the lsp specification. @ahmednrana I might be able to work on this but I have some other things I would like to work on first like #50.
Until then I can highly recommend this extension.


GCE node deletion times out - allow an async option

Feature Request
Currently the GCE node_delete() function uses the async_request() call (which ironically isn't actually async). Deleting a basic n1-standard-1 node running Centos in us-central times out every time. This isn't an uncommon occurrence. Searching the intertubes there are other references of other projects having the same issue:
https://github.com/kubevirt/cloud-image-builder/issues/72
https://github.com/ansible/ansible/issues/29597
The current way to avoid the timeout is to use the ex_destroy_multiple_nodes() function with a gigantic timeout value. An option, for sure, but not flexible enough.
An easy solution in this case would be to offer both a sync and async option for deletion. Applications can poll, if desired. Thankfully, the async option is fairly straightforward, defaulting to the current sync mode of operation:
        if sync:
            self.connection.async_request(request, method='DELETE')
        else:
            self.connection.request(request, method='DELETE')

I think that's a reasonable approach although it would be good to have a consistent API for all the operations which are async (aka involve polling).
So ideally all of those methods would take sync=False / ex_sync=False argument.

Closing since this has been implemented as part of #1357.


Backend docstring cleanup

Description of the Change:
Starting with Sphinx 1.7, child class methods without explicit docstrings inherit their docstrings from the parent class method they override. Hence child classes should only provide a docstring if the method functionality has been changed.
The idea is to take all useful information from the backend API child class docstrings and move it to the corresponding BaseBackend, BaseFock or BaseGaussian docstring.
I've fixed the FockBackend  docstrings, the two other backends still need the same treatment.
This is not urgent, and can wait until we've redesigned the backend API.
Benefits:
Avoid docstring duplication and conflicting information. For each API call there should be just one authoritative docstring.

Also: the FIXME's will show up in the online docs --- they should either be fixed here, or moved to a comment below the docstring

@smite Let us know when the final issues/changes are implemented and this is ready for final review

@co9olguy It should be ready now, once the tests finish.


[web] Support routing in multi-view

At the moment, routing pretty much depends on the existence of the implicit view. In multi-view, we want to get rid of the implicit view, but that would break any view that uses MaterialApp for example.

[ ] Give each FlutterView its own history (in-memory history).
[ ] How does UrlStrategy play into multi-view?
[ ] Keep using browser history in full page mode only.

Suggested by Loic: pass initialRoute to the view configuration.
Ability to retrieve the current route of a view.


Comparison of team member and guest capabilities definition/wording

The choice of wording for "Comparison of team member and guest capabilities" specifically for the "Attach files" line which states "Team chats only" is very poor due to lack of definition of chat types anywhere on Microsoft's documentation website.
Many users assume this would allow guests to attach a file in a Team channel which is untrue. It would be really helpful for novice users to have a clear definition of what this means as the only use of this phrase is on the guest experience page.

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

ID: 048930a4-fdf2-9a90-3b47-46af66db3db4
Version Independent ID: 8d6a2c84-94e9-b17e-f5c1-91191187ce4e
Content: Guest experience in Microsoft Teams - Microsoft Teams
Content Source: Teams/guest-experience.md
Service: msteams
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@FlynnLives  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @FlynnLives, thank you for your feedback.
The table states that "attach files" for guest users is only available in Team/Channel chats, not for one-on-one or group chats.

@dariomws it says "team chats only". The way you worded it here as
"Team/Channel chats not one-on-one or group chats", makes this a lot more clear and leaves no room for misunderstanding like I did in the OP

@FlynnLives Do you think that "Channel posts only" could be enough? "Team/Channel chats not one-on-one or group chats" is too long for the table.
Thanks!

@dariomws excellent, thank you!


No output with --out when using import statement

This cost me quite a bit of time, so please enlighten me if this is anticipated behaviour and let's put a big note in the docs.
tsc --module commonjs --out app.js app.ts type checks correctly, however produces no output. In fact it does not produce output with --module amd either.
tsc --module commonjs app.ts type checks correctly and produces output, but I do not have control over the location of the output.
For reference, I am developing a node app.
Let's say my app looks like this:
/// <reference path="./typings/node/node.d.ts"/>
/// <reference path="./typings/lodash/lodash.d.ts"/>
import _     = require("lodash");
var x = "test";

and I used tsc --module commonjs --out app.js app.ts to compile, I would get no output at all
To get my output back, I would either need to drop the import statement or drop the --out argument.
This is happening on version <IP_ADDRESS>

Seems reasonable to give some sort of warning/error here.

I thought we had disallowed this in 1.0, but apparently that is not the case.

--out will only apply to global code. Consider the case of a project with a loader and a set of modules. the loader.js is the only piece included in the html file, the other module files are imported dynamically by the loader. --out loader.js will build the non-external module pieces into one file, the other module files will be emitted to their own files.
This is a special case though, i am fine with a warning. what is the proposal?

In the case where --out is specified and the emitted file has no content emitted we should warn something to the effect of: "Warning: output file  is empty." I'm not sure we want the message to say anything more speculative (about combining it with external modules), presumably anyone searching for this error will quickly find a thread here or on StackOverflow with an explanation.

Warning: output file is empty.

That's something, but also pretty vague. I could just have compiled an empty file to start with. It's not giving me an indication as to why - I would still be baffled to find nothing in the output file after specifying --out. Maybe the problem is the implicit nature of what is considered "external" and "internal". The simple presence of a keyword changes my file from being one or the other. That had me really confused until I clicked on to it.

Yeah, that's a common source of confusion, but it's also not something that's really amenable to being quickly explained in a command line error message. An explicit warning at least gives you an immediate clue something is awry and some text to key your search for answers off of. Open to suggestions for alternatives though.

Maybe it really just comes down to having better docs on the topic. I have read the official docs a couple of times to try to understand it, but it was a rather painful experience. The information is lacking and key points are not driven home. The section on modules starts of writing some module code, which by the looks of it would classify as an "internal" module - but really in my opinion it should explain the module infrastructure first - tell me what "internal" and "external" is supposed to be, because the words themselves don't do a good job at it. Then the next section patronises me and tells me the benefits of modules. Let alone the code used in the example is simply unconcise and distracting from the point.
I apologize for the rant, but the more I think about it, a simple warning message as suggested above, coupled with a solid documentation upgrade would be a worthwhile effort. I would be willing to create a pull request for it, if there's a repo for the docs.

Given that one of TS goals, is the ease of development of large apps and large apps are always split into many files, then maybe when --out is specified the compiler does exactly what is told, Produce a single output file, merging all modules with the same name to one and raising errors when a conflict is found (ie private var with the same name). The current behaviour (produce a file for each input) then, can be easily achieved by calling the compiler without the --out flag or execute it multiple times.

Approved.
Spitballed solution in backlog meeting was to move the current behavior under an experimental flag (--globalOut?) and error if we try to emit an external module while --out was present.
We actually have no idea how many people are doing this on purpose but believe it to be extremely small. If somehow you find yourself looking at this issue and mix --out with external modules successfully, please post a comment!

If we do not allow --out with --module, then all non-module files (i.e. no top level import/export) should be coerced in a module output. see #2937 for more details.

Hi – I just posted a dup of this (#3950) after losing a lot of time tracking it down. It looks like there are other people who have had similar issues. I would strongly :+1: throwing an error or at least logging a warning in this case. If you just log a warning, then at least people can search for that text string and find the docs you write about it, and start to understand what's going on.

As a newbie to TS I found this very confusing....

Just wanna add my +1 to this. Just cost me 2 hours that a warning would have saved.

Just want to +1 this, starting with TS and it's infuriating for this to happen. Not impressed.

With #5090 merged this is resolved. It is now an error to specify --out with --module unless --module is amd or system, at which point the modules will be concatenated into the specified output file.

When I use module: system with out: app.js, I get the output in the the cwd/the cwd, like ~/Repositories/app/Users/Jason/Repositores/app. See https://github.com/ivogabe/gulp-typescript/issues/123

im still facing the same problem as the others
tsc main.ts --out main.js
`will still output an empty file with no warning what so ever...

@h-nazzal you need  --module amd or --module system

@RyanCavanaugh @DanielRosenwasser I'm unfamiliar with Git statuses. I see "Fixed" and "Closed". I see Milestone for TypeScript 1.8, which is out. I see "@weswigham was unassigned by @capfei on Jan 20". All that's consistent. On the other hand, I see indication above from @jasonszhao that the problem remains. And I see discussion today on https://gitter.im/Microsoft/TypeScript possibly indicating that @MeirionHughes is having the same problem. Should someone open another ticket to get this considered again? And cite this one?

FYI (and because I spent an hour on this as well), if you :

Rely on tsconfig.json for your compilation, use outFile and not define any module entry in the file
Use either grunt-ts or Intellij IDEA Compiler to compile typescript from the tsconfig

Then, your resulting app.js will be empty as well.
Workaround : put a module entry in your tsconfig.json file
Note: I only tested with grunt-ts and IntelliJ IDEA, but maybe other tool may be concerned by this problem as well.

@fcamblor this issue was reported in https://github.com/Microsoft/TypeScript/issues/8634 and you should now see an error if you do not have --module specified with --outFile. the fix is available in typescript@next.

And I see discussion today on https://gitter.im/Microsoft/TypeScript possibly indicating that @MeirionHughes is having the same problem. Should someone open another ticket to get this considered again? And cite this one?

@Prairie-Falcon this feature was implemented for TS 1.8, and should be available today. if you are running into issues, please file a new ticket, and provide enough information to allow us to diagnose the issue.


Publish daily build please

Stopped since 20180522. I want to check #24391. BTW, why daily build is so unstable?
cc @mhegazy @DanielRosenwasser

@weswigham can you take a look.

Our nightly publish started failing on compile since we merged the strict null checks pr. The configurePrerelease script appears to not be strict-compatable XD

Our build is no longer broken and we have nightlies again. 😉

We did a major refactoring of the compiler at the start of the week and are aware that we haven't published a nightly since. We should hopefully have enough things back in order to publish again today.


chore(form-field-range): Added tests (WIP)

✅ Closes: COMUI-2864

Tests look good to me there is just a failing build on some resize observer problem in tests.


NPM Script explorer should honor .gitignore

I have a workspace with test data that is listed in my .gitignore file. However, the NPM Script Explorer lists all scripts in my test data folder.
I'd like to be able to tell the explorer that it should honor the .gitignore file. I personally don't need a setting but others might want to see the current behavior.

Request makes sense. For now you can use the npm.exclude setting to exclude folders.

I have a workspace that has several top-level folders that all start with the prefix samples-. I tried
    "npm.exclude": [
        "samples-*/**"
    ]

and
    "npm.exclude": "samples-*/**"

in workspace settings. Both don't work. The pattern though works for files.exclude. Any hint?

The excludes are matched against absolute file paths and not workspace-relative ones. Thus **/samples-*/** works. It would be nice if npm.exclude and files.exclude would behave the same.


The notification message is unclear when uploading an invalid file to application setting

OS: Win10
Build Version: 20200917.5
Repro Steps:

Right click the "Application Settings" node -> Select "Upload Local Settings..." -> Select an invalid .json file.
Check the notification message.

Expect:
The notification message is clear.
Actual:
The notification message is unclear.

More Info:
This issue also reproduces no matter what invalid file is selected.

Could you explain what message you were expecting from this error?
Also, I should mention that in App Service, we are not expecting a .json file, but a .env file which looks like this:

If we are not expecting a .json file, I think the error message "The operation only support .env file" should be better when choosing a .json file to upload.
More Info:
There is no error when uploading a txt/.json file which looks like this:

In this case ".env" is referring to the file name, not the file extension. A "test.txt" file is also valid


Use environment variables for all secrets

Pull Request Overview

Remove the secrets.py implementation, which includes the removal of _db.initial.tar.gz. The secrets previously defined in secrets.py should now be defined in ./.env using dotenv syntax (e.g. VAR=value).
Use try..finally instead of try..except..finally in a test case that only re-raises the exception. In this case it's better to just let the except raise, because then it shows exactly where the error occured, which for a large try block can be handy.
Fix hard coded file path to the uploads directory in a test.
Allow the data directory (i.e. DATA_ROOT) to be defined by env-var. But also maintain the backwards compatible default location (./_db).
Fix the CI db migrations check for SQLite, which was failing because the database file in _db.initial was removed.

Review Notes
We'll need to let everyone know about this change, but otherwise the tests should show and verify the state of things.
Pull Request Checklist

[X] Ensure that the PR is properly formatted

Example: All lint checks are passing

[X] Ensure that the PR is properly rebased

Example: The PR is rebased on develop (commit: <insert develop commit hash>)

[X] Ensure that the PR uses a consolidated database migration

Example: One database migration is proposed (revision <insert develop revision> -> <insert new revision>)

[X] Ensure that the PR is properly tested

Example: All automated tests are passing

[X] Ensure that the PR is properly covered

Example: The percentage of the code covered by tests has not decreased

[X] Ensure that the PR is properly sanitized

Example: No sensitive data or large content was added to this PR

[ ] Ensure that the PR is properly reviewed

/rebase


Other interacting policies

Hi Microsoft
This article states "The device will try to download and install the update at a time based on your other download and installation policies (the default is to automatically download and install in in the background)."
What other policy allows to set a download and install time?
We have "Configure Automatic Updates" configured to a specific weekdate and time, but this was ignored (the new policy mentions it overrides this, so we kind of expected this).
With Windows 11 and without the "Specify deadlines for automatic updates and restarts", quality updates would not install automatically, if the time configured in "Configure Automatic Updates" was missed. Windows 10 (also 21H2) updates immediately in this case. So we will have to set this new policy. But we would prefer updates to install at our defined time, if the computer is online then (and only install after this date if the computer was not).

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

ID: 44aabe97-360e-0655-09ec-5d1e352bdb1a
Version Independent ID: 1c729c42-741d-ecb7-6490-a4bfdd029263
Content: Enforce compliance deadlines with policies in Windows Update for Business (Windows 10) - Windows Deployment
Content Source: windows/deployment/update/wufb-compliancedeadlines.md
Product: w10
Technology: windows
GitHub Login: @jaimeo
Microsoft Alias: jaimeo

@arcarley
@dougeby for awareness


UI enhancements

changed tooltip text as suggested by Ori
added loader to voting duration actions (for better UX)

https://github.com/user-attachments/assets/6bd652d2-b3e8-4ce3-a576-a95cba0eb301

@race-of-sloths include

@Megha-Dev-19 Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
Weekly streak is on the road, smart strategy! Secure your streak with another PR!

Current status: waiting for scoring
We're waiting for maintainer to score this pull request with @race-of-sloths score [0,1,2,3,5,8,13] command. Alternatively, autoscoring [1,2] will be applied for this pull request
What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow
For contributors:

Tag @race-of-sloths inside your pull requests
Wait for the maintainer to review and score your pull request
Check out your position in the Leaderboard
Keep weekly and monthly streaks to reach higher positions
Boast your contributions with a dynamic picture of your Profile

For maintainers:

Score pull requests that participate in the Race of Sloths and receive a reward
Engage contributors with fair scoring and fast responses so they keep their streaks
Promote the Race to the point where the Race starts promoting you
Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

For contributors

Include a PR: @race-of-sloths include to enter the Race with your PR

For maintainers:

Invite contributor @race-of-sloths invite to invite the contributor to participate in a race or include it, if it's already a runner.
Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called


When will it support iOS Interstitial?

Thank you for developing this amazing plugin. I want to know When will it support iOS Interstitial?
Do you have a plan?

Thanks, I'm glad to hear that. For IOS I can't develop it yet, because I don't have an Apple device to develop it to the IOS version


Update doobie-core, doobie-h2, ... to 0.12.1

Updates

org.tpolecat:doobie-core
org.tpolecat:doobie-h2
org.tpolecat:doobie-postgres
org.tpolecat:doobie-specs2

from 0.10.0 to 0.12.1.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.10.0).
You might want to review and update them manually.
CHANGELOG.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.tpolecat" } ]

labels: library-update, semver-minor, old-version-remains

Superseded by #350.


Stop checking for known issues in CIT

Stop checking for google-cloud-cli on Ubuntu 1604
Stop checking shutdown script execution during agent reinstall
Stop checking osconfig agent status on older gcesysprep versions (I also bumped acceptable record count to 200, there is some flakiness in this test)
All of these issues have been raised with owners, either internally or with partners.

/lgtm


feat: Add AST analyzer middleware to optionally rewrite queries before execution

Adds an AST analyzer to the SQLExecutor trait to allow modifying the query AST before execution.

This is used in the SQLite Table Provider to perform a non-trivial rewrite of interval expressions to use the SQLite native date() or datetime() functions, since SQLite doesn't natively support intervals.
https://github.com/datafusion-contrib/datafusion-table-providers/blob/main/src/sqlite/federation.rs#L49

Apologies for commenting in this old thread, but I'm working on learning about DataFusion's unparse sql generation support and datafusion-federation.  Is there a reason (other than project logistics) that this kind of interval rewrite logic for sqllite should be done in an ast_analyzer step here in datafusion-table-providers rather than in the unparse logic in DataFusion itself?
I'm exploring replacing the sql-generation system we have in VegaFusion with unparse and datafusion-federation, so just trying to get a feel for where dialect customization should happen.

Hello @jonmmease,
There was a discussion about this in issue #61

Thanks @backkem, yes these table providers look great, and I'm excited to learn more about how federation works!
I'm thinking about eventually adding support for some additional dialects (like Clickhouse, Spark, MSSQL, etc) and wondering if this should primarily be contributed upstream in the unparse logic in the datafusion-sql crate, or if I should customize the generic dialect there with the proper quote style and then do semantic transformations (like different names for functions) in an ast_analyzer implementation.

RE where to land things: it's a good question. Right now I think we have roughly:

Unparser: pure plan to SQL logic. It knows about some syntactic differences but not engine featureset.
datafusion-federation: framework to split plans across one or more remote query engines by sending entire sub-plans to the remote (can be SQL but could also be Substrait or other formats). The SQLExecutor assumes the remote is a 'full' SQL engine. Alternatively implementers of the FederationProvider can provide an Optimizer that more selectively cuts out a sub-plan.
datafusion-table-providers: table providers that function with or without federation. Currently most remote/engine specific stuff is here. I think this makes sense if you want the table providers to work both with or without federation.

Things can evolve but this is the balance that emerged so far. I'm happy to host more plan re-writing tools/logic that is federation related in this repo.

Yeah, I still think its not 100% clear where the responsibility of the Unparser dialect ends and where something like the AST rewriter in the specific implementation begins. Like @bakkem, I tend to think that the core Unparser should mostly be focused on syntactical differences between the dialects whereas more complex differences in how, e.g., functions work can be implemented by the AST rewriter (as we did for handling intervals in SQLite: https://github.com/datafusion-contrib/datafusion-table-providers/pull/85)


"Try Ramda" is broken

The live editor fails due to server problems
http://ramdajs.com/repl/?v=0.22.1
Don't know if this is really Github-worthy, but I found no contact information on the site.
Best regards

yup, already aware of that thanks. duplicate of #1873


Add supported languages list from enry on gitbase documentation

Issue extracted from https://github.com/src-d/gitbase/issues/443

https://github.com/bblfsh/documentation/issues/191

The issue in the linked issue is not in bblfsh:
LANGUAGE(t.tree_entry_name, b.blob_content) = 'go'
That's enry. You should link to https://github.com/src-d/enry/blob/master/data/alias.go or github/linguist for valid values. That could be a note in your documentation about the LANGUAGE function.

AFAIK go would be a valid value for bblfsh, the problem here is comparing it with LANGUAGE result.


Feature Request: Ability to specify a HTTP source

Rather than being forced to supply a local source file, it would be nice to pass along a URL to a file.

I've been thinking about this, and I am worried about injections at runtime. What happens if you specify for example a file that is 4TB in size?

For the CLI and the Quasar Ext I think its better not to do this.


[QUERY]How can I get the usage when I using the getChatCompletionsStream method of OpenAIClient

I always get a null CompletionsUsage object when using the getChatCompletionsStream method of OpenAIClient in Azure SDK for Java.

Streamed requests do not include a "usage" field in the response from OpenAI. See here for confirmation of this behavior. I wish there were better documentation of this (both from OpenAI/Azure and in this SDK's docs). For example, streaming from OpenAI (instead of Azure) is currently entirely broken in this SDK. I'm hoping they publish a new release soon.

Thanks for the reach out @kenlu456852. And thanks for the reply @zizmax.
As @zizmax points out in the reply. "Streamed requests do not include a "usage" field in the response from OpenAI." I file an issue to enhance to document in this SDK.
@kenlu456852 SDK version 1.0.0-beta.2 is released that fixed the streaming from OpenAI issue. Please give it a try and welcome any feedback. Thanks.

thanks for the reply @zizmax @mssfang


Collapse animation doesn't work correctly if we increase its duration

What is happening?
The animation is interrupted when we increase its duration
What should be happening?
The animation should not be interrupted
Steps to reproduce issue

go to https://reactstrap.github.io/components/collapse/
change class ".collapsing" - "transition: height 0.35s ease" to "transition: height 5s ease"
Click toogle

![Uploading 2004bug.gif…](how it looks)

You'll have to set the timeout prop in Collapse to match your transition duration.


Requests and distributions

We currently have an api endpoint app/controllers/api/v1/partner_requests_controller.rb for accepting requests for diapers from various diaper bank partners. We need need a few things before this feature is complete:

[ ] Create an index and show action for the various requests. The index action should list the who the request is from, and its current status (active or fulfilled.) On the show page it should list out the diapers requested and comments with a 'fulfill request' button on the bottom of the page. Clicking the button will set the the request to fulfilled and will move the user to the new distribution page with a pre-filled distribution containing all the requested items.

[ ] The page layout should reflect the current number of active requests.

[ ] After a distribution has been created for the request, the show page of the request will link to it.

Is there already a distribution page, to forward to after users clicks "fulfill request"?
This looks like a front end (backend gui?) addition for using the api endpoint mentioned, correct? Where is the screen shot from (which file or dir)? That's the existing gui?

Yes, there is already distribution pages/models/etc.
app/views/distributions/ for the various views. The trick bits will be finding and entering the request values into the distribution. That's why there is the DIAPERMAPPING mapping table on the request model.
Whoever builds this may be able to borrow some of the logic from donations and how you're able to create a distribution directly from a donation.
The gui I attached is the notification icon -- logic could be replicated from the pickup model when building that GUI icon.

Thanks @oystersauce8, I will approve when you have commented that you have it setup 😁

I got set up on my Mac, pic attached

Hey @oystersauce8 thanks for jumping in on this! If you have any questions feel free to join our slack and ask any questions in the #diaper channel!

I'm halfway there

Thanks for the update @oystersauce8! Looking good

Just paid out the bounty! Great work @oystersauce8 + thanks for the quick review @seanmarcia -- if either of you have any other bounties you think could be good for Hacktober, let us know 🎃🙂


How do I start nginx server once install is completed.

In your documentation here:
https://github.com/arut/nginx-rtmp-module/wiki/Getting-started-with-nginx-rtmp
It doesn't explain how to start nginx once it is installed. I'm not in dev ops so I'm not sure what to do. The closest thing I can see is to run objs/nginx but that doesn't seem right..

that's part of nginx. http://nginx.org/en/docs/beginners_guide.html


Improve retry_async.py

On
if retry_settings['history']:
response.context['history'] = retry_settings['history']
I like to encapsulate dict manipulations with raw string keys behind functions when I can. Since this is duplicated in RetryPolicy (and also since this inherits from RetryPolicy), might consider putting these two lines in a method self.update_context(context, retry_settings)

Merged https://github.com/Azure/azure-sdk-for-python/pull/5334


fix: remove dependencies bug

Fixes #23

Can you add tests for the await removePackageDependencies({ dependencies: [ 'myDependency' ] }); style usage?

Can you add tests for the await removePackageDependencies({ dependencies: [ 'myDependency' ] }); style usage?

added

It would be better to add a new test than modify existing tests.

It would be better to add a new test than modify existing tests.

test('async - multiple types') is literally for the case await removePackageDependencies(Record<DependencyKey, Dependency[]>), do we really need another case?

The test already does too much. Large tests often hide bugs since they do too much. Not a bit issue in this case, but having smaller tests would make it clearer. I guess that could be done later though.

The test already does too much. Large tests often hide bugs since they do too much. Not a big issue in this case, but having smaller tests would make it clearer. I guess that could be done later though.

yes, it will be better, i've already add a new case


Front end service hangs sometimes on AWS deploy

Cloudformation does not always complete because all 3 tasks don't always come up.  Most times it reports 2 out of 3 tasks completed.
The socks shop still works.
Cloudformation screen

ECS Clusters screen

Cause is yet unknown.

This is related to not enough ec2 instances coming up, possibly.

With the larger and more numerous instances in the cluster, I can no longer reproduce.
Closing until we witness again.

I have done several deployments, manual, and automated (Travis) and I can't reproduce this anymore. The 4 instances always come up and all the 4 desired front-ends come up as well. @jasonrichardsmith are you still doing anything on this issues? If not, I suggest closing it.


No way to disable autobins

A user on Discord noted that there is no way to completely disable automatic target discovery. Example:
src/lib.rs:
pub mod bin;

src/bin/mod.rs:
// empty

Currently this fails because it thinks there is a bin target called mod, regardless of whether autobins is specified.
I'd like to propose that autobins=false should disable autodiscovery, even if you don't specify any [[bin]] targets.

This seems reasonable to me! I'm surprised that autobins = false doesn't already work, and I'm also somewhat surprised that it's connected to the contents of src/lib.rs!


Define a proper way to include Longhorn storage in Elemental

Including Longhorn storage in Elemental-teal deployments is already possible, but cumbersome, requires several configs here and there which are not obvious. In this card we need to:

define the desired procedure to set longhorn
adapt our current setup and code to make the procedure possible
document the procedure

I believe all this essential means to unset the default persistent path for longhorn and explore if there is a simple way to include it within the cloud-init field on the registration yaml.

Would it make sense to have the single disk scenario be in the default config then document how to handle configuration of systems with multiple disks?

Hi @davidcassany and @agracey, I have an elemental cluster ready and have installed longhorn on it. Now I want to add another disk to one of the nodes and want to use that disk for longhorn.
Below is my file-system (using lsblk). vdb is the new disk (30G) which I added and want to use it as longhorn storage. I created a partition vdb1 as ext4 (using command mkfs.ext4 /dev/vdb1) and created a mount point for longhorn (using command mkdir -p /var/lib/longhorn).

I tried adding /dev/vdb1  /var/lib/longhorn ext4 defaults 0 0 to /etc/fstab but it results in the following error (as seen from the rancher dashboard) :
Disk default-disk-959b4ca714f2c137(/var/lib/longhorn/) on node m-c9222f3b-0c70-4b40-80c9-080ee1c2fb26 is not ready: record diskUUID doesn't match the one on the disk
What should I do to make longhorn use the new 30G disk instead of the previous one (as in vda5 /var/lib/longhorn)?

Now I want to add another disk to one of the nodes ...
You want to add a second disk after installation ? This isn't really supported in a declarative system like Elemental.
We would need to add a "Longhorn" mode to it 😉

You can put whatever is needed into Elemental's cloud-config sections.
Esp. writing (config) files and running commands (typically acting on these config files).
See the Elemental documentation for examples.

You want to add a second disk after installation ?

Sure! People always want more storage, right? ;-)
There's a note in the longhorn docs about using LVM to stitch together multiple disks (see https://longhorn.io/docs/1.5.1/best-practices/#disk-space-management), because then you get one big volume which you can mount under /var/lib/longhorn, then later add more disks to the LVM volume without messing with /etc/fstab and having a bunch of separate filesystems. Would doing that make the elemental deployment / disk management scenario any easier?
With Longhorn's V2 Data Engine (which is SPDK-based), AIUI the need to mess with /etc/fstab goes away, because Longhorn will just directly use block devices. That's still only in preview now though, so doesn't help immediately (see https://longhorn.io/docs/1.5.1/spdk/quick-start/ for more details).

Here we can see an old example of how to include LVM volumes in an elemental installation https://elemental.docs.rancher.com/customizing#adding-extra-lvm-volume-group-disks-during-the-installation Old, but it should be still valid, with the difference that now the ISO can be also managed and built using the seedimage resource and there might no need to craft it manually in your local env.


Proofing Tools / Spell don't work within tab pages?

The Proofing Tools don't appear to work in the tab pages. Is this intended?

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

ID: 9938300a-8983-2236-5d02-536b9b872225
Version Independent ID: b336fba4-1e88-db4a-0a41-c91a57384aee
Content: Extend your Teams app with a custom tab - Teams
Content Source: msteams-platform/tabs/how-to/add-tab.md
Product: msteams
GitHub Login: @laujan

Added teams bug entry as well: https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/40333423-bug-spell-check-does-not-work-on-personal-tabs

Currently teams does not provide this service.


Add Respresso Localization Converter to the awesome list.

Project URL
https://respresso.io/localization-converter
Category
Tools
Description
Add Respresso Image Converter to the awesome list.
Why it should be included to awesome-ios (mandatory)
Respresso Localization Converter helps iOS, Android and Web developers to convert localization between their project's format in case of multiplatform projects.
Checklist

[Not applicable] Has 50 GitHub stargazers or more
[x] Only one project/change is in this pull request
[x] Isn't an archived project
[x] Has more than one contributor
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[Not applicable] Supports iOS 9 / tvOS 10 or later
[Not applicable] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

To clarify

I'm one of the developers from the Respresso team.
Respresso is a commercial project, but our demo converters are completely free, without ads.
We have a reasonable rate limit, but overall, it can be used as much as you wish.
From a security perspective: We don’t keep any of the uploaded or converted files.

@vkrissz Thanks for contributing!


Is this project still alive, and when can I expect the android and ios support coming out?

Context
In which context or scenario will your feature/widget be used?
Problem description & Solution
Describe your problem and possible solution here
Examples and MockUps
Can you give a concrete example of how you'd use the feature? A relevant code sample?
Can you draw a picture of what you're imagining? :-)

The project is missing active development right now. Especially this doesn't give us any progress towards a working IOS/Android integration.
Everybody interested to get that going is invited to send PR's.


Client Allocation Request for: Starry sky in Yunnan

Client Allocation Questions
Core Information

Name: Starry sky in Yunnan
Website / Social Media: https://ah22192341-1.icoc.vc/
DataCap Requested: 5TiB
Addresses to be Notarized: f3u4pcgize6k3ubdwit5tomoddhtz3h3ek2pgh52e2u63y2ycvbbqz7bbu3tshiv3tfamaakt6nfgminxypbea
Notary Requested: jsonsivar

Closing this application out since @jsonsivar / Fleek are stepping back from Notary responsibilities for the time being.

This user’s identity has been verified through filplus.storage


Fix outdated doc

Material app no longer uses Window.defaultRouteName as the default value of initialRoute.

I've a patch that revamps this and takes care of fixing the documentation at the same time.

Ok, I'll close this one then.


Add a gut-update command

This fixes #1.
This will add a new gut-update command which will update the local copy of gut with the latest from the remote. It also tweaks install.sh to piggyback on that command to avoid duplication.

lgtm!


Change font to accomodate for symbols

Font now shows correct hand, heart, star, and plus symbol.
This works as a fix to #1.

Hi abraham ^-^

great teamwork lol
https://twitter.com/ca_dmv_bot/status/1575823784312860673


Error using JSForce in Angular applications?

When trying to use create new jsforce connection from angular 8 application, component crashes with error message:
ReferenceError: Cannot access 'XYZPageModule' before initialization.
The error is definitely caused by the code this.conn = new jsforce.Connection but I can't find any visible problems.
The function getConnection() is not even being called.
import { environment } from '../../environments/environment';
import { Component, OnInit } from '@angular/core';
import { ActivatedRoute } from '@angular/router';
//import { SalesforceService } from '../../providers/salesforce.service';
import * as jsforce from 'jsforce';

@Component({
  selector: 'app-sharephoto',
  templateUrl: 'sharephoto.page.html',
  styleUrls: ['sharephoto.page.scss']
})
export class SharephotoPage implements OnInit {
  currentImage: any;
  photo: SafeResourceUrl;
  conn: any;
  apiVersion: string = '45.0'
  username =<EMAIL_ADDRESS>  password = 'somesfpwd';

  //private camera: Camera,private sanitizer: DomSanitizer
  //public service: SalesforceService
  constructor(private activatedRoute: ActivatedRoute, private sanitizer: DomSanitizer) {}

  ngOnInit() {
  }

getConnection(){
    if(!this.conn){
        this.conn = new jsforce.Connection({
            oauth2 : {
              // you can change loginUrl to connect to sandbox or prerelease env.
              loginUrl : 'https://login.salesforce.com',
              clientId : 'someclientid',
              clientSecret : 'someclientsecret',
              redirectUri : 'https://'
            }
          });
        this.conn.login(this.username, 'this.password', function(err, userInfo) {
            if (err) { return console.error(err); }
            // Now you can get the access token and instance URL information.
            // Save them to establish connection next time.
            console.log(this.conn.accessToken);
            console.log(this.conn.instanceUrl);
            // logged in user property
            console.log("User ID: " + userInfo.id);
            console.log("Org ID: " + userInfo.organizationId);
          });
    }
}

This does not sound like a JSForce error at all. It seems like you might have a service or something else that is
Here are some bugs I see

this.password should be this.password
your callback function will not work because you are using function(err, userInfo)

You will either need to bind the function to allow access to this or you will need to use a => to retain this.

Also, here are some things you will need to think about:

If you are using this application outside of Salesforce, you will need a server between your browser and Salesforce because of CORS

You can use a proxy server as indicated in the docs -https://github.com/jsforce/jsforce-ajax-proxy
Alternatively, you can create a server that sits between the browser and SFDC - and the browser client would call to the server and the server would handle calling to SFDC. In this case, the browser would never load JSForce directly. This is the recommended approach

I spun up a quick angular app and was able to test without any problems:
tsconfig.app.json - this must be changed to force the use of the minified JSForce to ensure that node-only features are not attempted to be imported.
{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "outDir": "./out-tsc/app",
    "types": [],
    "paths": {
      "jsforce": ["./node_modules/jsforce/build/jsforce.min.js"]
    }
  },
  "include": ["src/**/*.ts"],
  "exclude": ["src/test.ts", "src/**/*.spec.ts"]
}

import { Component, OnInit } from '@angular/core';
import * as jsforce from 'jsforce';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss'],
})
export class AppComponent implements OnInit {
  title = 'jsforce-test';
  loginUrl = 'https://login.salesforce.com';
  proxyUrl = 'https://sfdc-jsforce-proxy.herokuapp.com/';
  username =<EMAIL_ADDRESS>  password = 'jsforceTest123';
  conn: any;

  ngOnInit() {
    this.getConnection();
  }

  getConnection() {
    if (!this.conn) {
      this.conn = new jsforce.Connection({
        loginUrl: this.loginUrl,
        proxyUrl: 'https://sfdc-jsforce-proxy.herokuapp.com/proxy',
      });

      this.conn.login(this.username, this.password, (err, userInfo) => {
        if (err) {
          return console.error(err);
        }
        // Now you can get the access token and instance URL information.
        // Save them to establish connection next time.
        console.log(this.conn.accessToken);
        console.log(this.conn.instanceUrl);
        // logged in user property
        console.log('User ID: ' + userInfo.id);
        console.log('Org ID: ' + userInfo.organizationId);
      });
    }
  }
}


Translate "heartbeat" metrics to Hawkular Availability Metrics

Basically catching all metrics that contain  "heartbeat" in the key and send them to hawkular as Availability with value up.
A trigger can be set in hawkular to send event in case no value has been set in a certain interval of time.

@twiest PTAL


Georgeee/csl 1121 deploying master

Make kademlia be provided external address to announce our node's public ip, port (bind address is different)

E.g. on deployment we have private address 172.x.x.x which is address of interface to bind on. And we have public IP 54.x.x.x. Earlier former was provided for both binding and announcing our address to rest of peers


feat(presto): add support for user impersonation

SUMMARY
Fix for issue https://github.com/apache/superset/issues/11359, https://github.com/apache/superset/issues/9406
When using LDAP authentication with presto/trino, the current behavior is just to modify the URL to replace the username which will result in an unauthorized exception. This PR will fix this by updating the connection argument with the effective user.
TEST PLAN
Step 1: Setup database connection to presto without credentials in URL.
Step 2: Provide admin(who can impersonate as any other user in presto) credentials in connection properties via extras
"engine_params": {
           "connect_args":{
              "protocol": "https",
              "username":"<admin>",
              "password":"<admin_password>"
           }
}

Step 3: Enable impersonation for the database connection.
Step 4: Log in with a different user and run the query via SQL lab and you will see the principal user as admin and user as the logged-in user in presto UI.
ADDITIONAL INFORMATION

[X] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

@rijojoseph07 would it be add to add a test duplicating the bug to both verify the fix and prevent future regressions?

@rijojoseph07 would it be add to add a test duplicating the bug to both verify the fix and prevent future regressions?

@willbarrett I am trying to write a unit test for this but struggling to get connect_params from the SQLAlchemy engine object to check if the new principal_username is added.
I have tested this code in our environment and is running in our prod system.

A way forward if it's not possible to get the connect args out of SQLAlchemy would be to mock the create_engine call on line 364 in superset/models/core.py and assert on the arguments passed in. These systems for connecting to many different database types are quite challenging the community to test, so comprehensive unit test coverage is important for quality.

A way forward if it's not possible to get the connect args out of SQLAlchemy would be to mock the create_engine call on line 364 in superset/models/core.py and assert on the arguments passed in. These systems for connecting to many different database types are quite challenging the community to test, so comprehensive unit test coverage is important for quality.

@willbarrett Thanks for your suggestion. I have added a unit test by mocking create_engine.

Codecov Report

Merging #13214 (1b3f4fa) into master (2ce7982) will increase coverage by 13.69%.
The diff coverage is 52.36%.

@@             Coverage Diff             @@
##           master   #13214       +/-   ##
===========================================
+ Coverage   53.06%   66.75%   +13.69%
===========================================
  Files         489      493        +4
  Lines       17314    29069    +11755
  Branches     4482        0     -4482
===========================================
+ Hits         9187    19404    +10217
- Misses       8127     9665     +1538

Flag
Coverage Δ

cypress
?

python
66.75% <52.36%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/constants.py
100.00% <ø> (ø)

superset/examples/birth_names.py
73.19% <ø> (ø)

...43f2fdb_add_granularity_to_charts_where_missing.py
0.00% <0.00%> (ø)

...s/260bf0649a77_migrate_x_dateunit_in_time_range.py
0.00% <0.00%> (ø)

...ons/versions/41ce8799acc3_rename_pie_label_type.py
0.00% <0.00%> (ø)

superset/connectors/sqla/views.py
62.74% <4.34%> (ø)

superset/views/datasource.py
88.70% <16.66%> (ø)

superset/viz.py
58.61% <27.27%> (ø)

superset/views/core.py
71.80% <66.66%> (ø)

superset/charts/commands/exceptions.py
92.85% <77.77%> (ø)

... and 937 more

Continue to review full report at Codecov.

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

@willbarrett @villebro Can you guys please review this PR.
Thanks

@rijojoseph07, I have upgraded to superset v1.1.0 & updated my connection settings & have corresponding impersonation settings in Presto as well. However, when clicking Impersonate logged in User button on the database settings it throws an exception on the UI and nothing is visible in the backend logs. Details below:

Upgraded to v1.1.0
Presto 341 with impersonation rules as follows:
"impersonation": [  {    "originalUser": "admin",    "newUser": ".*"  } ],
Above means any user can be impersonated by admin user
Removed username/password from DB Connection string
Updated Extra as follows:
"connect_args": {    "protocol": "https",    "username":"admin",    "password":"adminPwd",    "session_props": {        "omit_datetime_type_precision": true    }
Check Impersonate Logged In User (Presto & Hive)
Click on Save. UI throws following exception:

An error occurred while fetching databases: "Connection failed, please check your connection settings"

Hi @DRavikanth, were you able to connect using admin credentials without impersonation? Also it will be helpful if you can run superset in debug mode and share the logs.

Yes the admin credentials without impersonation works with no issues.
I'm running Superset in debug mode and I don't see any logs associated with
this.
Thanks,
Ravi
On Mon, May 3, 2021 at 22:46 rijojoseph07 @.***> wrote:

Hi @DRavikanth https://github.com/DRavikanth, were you able to connect
using admin credentials without impersonation? Also it will be helpful if
you can run superset in debug mode and share the logs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/superset/pull/13214#issuecomment-831696748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRGFYILCSOHKHUGPSLITI3TL6C2PANCNFSM4X2W3ZIA
.

Yes the admin credentials without impersonation works with no issues. I'm running Superset in debug mode and I don't see any logs associated with this. Thanks, Ravi
…
On Mon, May 3, 2021 at 22:46 rijojoseph07 @.***> wrote: Hi @DRavikanth https://github.com/DRavikanth, were you able to connect using admin credentials without impersonation? Also it will be helpful if you can run superset in debug mode and share the logs. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13214 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACRGFYILCSOHKHUGPSLITI3TL6C2PANCNFSM4X2W3ZIA .

@DRavikanth I just test this feature with superset 1.1.0 and presto 347 and it is working fine. Can you please check if impersonation is happening working as expected from the presto side via cli?
My connection URL looks like this : presto://presto-dns:443/hive/dev
Extra :
{
"metadata_params": {},
"cost_estimate_enabled": true,
"engine_params": {
"connect_args":{
"protocol": "https",
"username":"admin",
"password":""
}
},
"metadata_cache_timeout": {},
"schemas_allowed_for_csv_upload": ["dev"]
}
I use ranger with presto, and have enabled impersonation from ranger.  You can also check presto server logs to see if your request is reaching presto.

@rijojoseph07 I have exactly what you are testing against. I don't have Ranger. However, I don't think that's an issue. The only difference I see is the Presto version. I am using 341 and from the documentation I see impersonation is supported in that version.
I don't see any request being coming into the presto coordinator logs as well when the exception was initiated. I think this is failing in the UI itself and debug logs of Superset doesn't show anything related to this.
I am looking into the UI Console and see the following:
In Headers section:
Status: 422 Unprocessable Entity
In Response:
message	"Connection failed, please check your connection settings"
Request seems to be good though. Any help in debugging this further?

@DRavikanth Can you please confirm if the user which is creating this dataset with impersonation exist is a valid user for presto ?
What I am trying to say is that : lets say you are logged in as supersetadmin and you add this dataset and test the connection, it will add supersetadmin as principal_username and if  supersetadmin is not a valid user to presto, this might fail.

@rijojoseph07, Yes, the user(admin is the user name in this case) creating this connection in Superset does exist in Presto and is enabled with impersonation. Please note that, I am able to login to Presto and execute the queries using this admin user with no issues. Also, please note that, if I uncheck Impersonation option in connection object, everything works as expected i.e the dashboards built on top of this connection will load the dashboards/charts from Presto.

@DRavikanth Can we connect over slack to discuss this in detail? Please join superset slack channel.

That would be great. I am on superset slack with user ID ravioravi. Can you
ping me?
Thanks,
Ravi
On Tue, May 4, 2021 at 23:52 rijojoseph07 @.***> wrote:

@DRavikanth https://github.com/DRavikanth Can we connect over slack to
discuss this in detail? Please join superset slack channel.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/superset/pull/13214#issuecomment-832456060,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRGFYJB7Y5LPAQWUKJ37VTTMDTJVANCNFSM4X2W3ZIA
.


Revise SRS document after design diagrams for refining

During the design phase there are some missing points/ required revisions discovered in the SRS documents.
Revise the SRS document after the design phase.

Can be found under SRS page in repository wiki.


modify the convert_gff_to_gbk.py function and deps

Hi @gbouras13
Thanks for your work on pharokka. It seems like a very promising program. I noticed that the processing function to convert gff to gbk is being done with emboss, which is a heavy program for just one function. Then, I thought that a light custom function based on biopython could make it as well. It also uses the bcbio-gff library.
Thanks.

Hi @camilogarciabotero many thanks for this change (agreed that Emboss is overkill), I have incorporated it into the codebase.
I hope that pharokka can be useful for you - let me know if you have any other suggestions.
George


fix: Unbound action are now corretly forwarded to custom handlers

There was a bit of mix up with the sticky use case where we do leverage this for standard behavior in an unclean way i guess.

Ran into a related problem yesterday: One of the problems with sticky actions is that in the existing metadata documents, 100% of the DiscardAction annotations are wrong. They should point to an ActionImport, but in fact just contain the name of the action.


Add copyMessage method

A new copyMessage method was added in Telegram Bot Api 5.0.

Added the method copyMessage, which sends a copy of any message.

https://core.telegram.org/bots/api#copymessage
We should add this new method.

Let me take this one

Let me take this one

@vjgarciag96  please check this pr

@vjgarciag96  please check this pr

Closed by #170


how to get the avatar url

friend = bot.friends()[6]
friend.get_avatar(save_path='/tmp/f.jpg')

the upper code will save the avatar to the filesystem, but i just want the url weixin server returned, how can i get it?

the avatar url may be updated when the account session changes.
what's the point to get the url for?
if you prefer the image data to the real file, just left the save_path arg as None.


Allow masquerading as different users

Who is this PR for?
developers
What problem does this PR fix?
As we create features that have more involved authorization, or show different things to different users, it's harder for us to verify in production that these are working correctly.  For the home page work, we modified the home_controller to allow this in a bespoke way but we don't want to be writing authorization code like this for each feature like https://github.com/studentinsights/studentinsights/pull/1746 or https://github.com/studentinsights/studentinsights/pull/1745.
This PR is an attempt at solving this more generally.  The intention is to scope this only to developers at first, and potentially after to project leads.
What does this PR do?
Adds two endpoints to "become" another user, and to "clear" that.  This works by setting a session variable, and by overriding current_educator to return that other user if the session variable is set.
For tests, there are unit tests for each file, controller tests, and Capybara RackTest tests.
Screenshot (if adding a client-side feature)
Here's the flow for a developer:
1. sign in as a user with developer access

2. notice email and links in the upper right
This shows the current user email.

3. click on the name to jump to the educators overview page
This page needs love, but does the trick for now.  You can now click on "become" next to any educator.  This will make a POST request to /admin/masquerade/become?masquerading_educator_id=12345 which sets a flag on the session and then redirects to the home page.

4. home page, masquerading as another user
The upper right shows the user name, and an X to indicate you're masquerading.  The data on the page is all different, because all of the various requests the page is making are all running into the bit set on the session.

5. clearing the masquerade
Clicking the x drops the masquerade by making a POST to /admin/masquerade/clear which clears the session and then redirects to the home page.

If we wanted to move forward the steps would be to talk it out with @alexsoble, do a thorough review, deploy to demo and verify, and then deploy and verify for real.

@alexsoble This is just experimenting, but I'm wondering if you think this would be helpful or more trouble than it's worth..
It might be helpful for verifying changes that cut across permissions.  This gets dangerous when the operations involve writes, and we'd probably want to add more durable logging around this is we decide to do it, but an option to consider.

@alexsoble This pushes a slew of tests, probably the tests are 10x as much as the code.  There's unit tests, integration tests and Capybara tests using RackTest.
I also updated the styling to be super super visible when this is happening to start:

selfie cc @alexsoble, it'd be great to review this post-facto

@kevinrobinson Yep, reviewing this on #1793.


use the latest datasketches-java-3.0.0

I note that this is still using Travis.  Many of the Apache projects are abandoning Travis.  If it still works, fine, but we should consider moving this to GitHub Actions at some point.

Nice job!


IRONN-102 3 VA orgs to v5

https://jira.movember.com/projects/IRONN/issues/IRONN-102

@ivan-c  for a hotfix this Friday

merged master into this branch, to pick up this bugfix in master: #4247


Drop in image quality and stretching normal?

Hi, just started to get SRWE working after sometime. My config is a 2560 x 1440 and a 3440 x 1440 (primary) and intend to only play ETS2/ATS. I managed to setup SRWE to move to the left. However I see that the game UI is stretched. I went into the game driving and found it to be the right aspect ratio but the image seems to be more blurry. Just wanted to check if SWRE stretches the window? I believe I have set ETS2 at the right resolution of 6000 x 1440.
My SWRE config for ATS below:
<?xml version="1.0" encoding="UTF-8"?>

-<SRWE Version="1.0">

-<Profile>

<Window ExStyle="20040B00" Style="14C80000" Height="1483" Width="6020" PosY="-33" PosX="-2570" HierID="1"/>

</Profile>

</SRWE>

Thank you.

I think I figured that I have to change the game settings and click apply, then go to SRWE and load the profile once again. This fixes it but still hope for a more elegant solution without having to change the settings everytime I go in game


sdk: design the layers above the state machine.

Create a draft doc for the layers above the state machine.
These include components previously discussed:
Transport
Payments, Withdraw, Add funds
Tx information

Yes, I agree. I think that's something we should take inspiration from the research of other L2 SDKs while combining that with what we think will be an intuitive interface for Stellar.

While working on #122, which is ongoing, it is becoming more evident that an orchestrator will take a load off an application implementing and I want to experiment more with this idea. I plan to pickup this issue next week, take the design doc linked above and iterate on that design in code inside the example application I am working on. I've self-assigned the task to myself for this work.


Support BODYSTRUCTURE parsing for FETCH results

I think this might rely on the underlying parser crate supporting this (https://github.com/djc/imap-proto/issues/15), but it would be nice if this crate could expose a parsed BODYSTRUCTURE for messages (FETCH results).
This would be useful to allow the client to determine properties of a message in a bandwidth-constrained environment. Currently, the a message with large attachments must be fully downloaded and parsed just to determine that there are attachments.

Just as an update, there's currently a pending pull request for https://github.com/djc/tokio-imap/pull/44 to support the parsing of BODYSTRUCTURE. This should make it fairly straight forward to expose this functionality in this crate, perhaps as an Option<Bodystructure> for Fetch results. Any thoughts?

Seems reasonable to me!

I believe this functionality was merged in tokio-imap with https://github.com/djc/tokio-imap/pull/48.

Hmm, I think we could have closed this once https://github.com/jonhoo/rust-imap/pull/150 landed, unless I'm missing something?

Ah, yes I'd think so :+1:


Replace NUnit tests with xUnit

Date check - (end of 2016).
sif NUnit.

Why do this - do we get any benefit from it?

modernizing the tech stack
more people these days should be more familiar with xunit over nunit == easier and greater chance of contributor uptake
consistency : common tech stack used in modern repo's.

I don't know that you can say more people are familiar with xUnit over NUnit - drawing on my own experiences and the network of developers I know, NUnit is by far and away the most popular still.  Indeed I personally don't know anyone actively using xUnit and have rarely seen a github project using it - that is not to say there aren't shed loads of course, just that my experience doesn't suggest xUnit is more popular.
If you look at what is apparently the top 20 nuget packages for unit testing: http://nugetmusthaves.com/Category/Unit Testing

moq - xUnit
nsubstitute - NUnit
fluent assertions - MsTest
true fake - not sure but their examples use NUnit
NUnit - guess :)
fake it easy - xUnit
fsunit - NUnit, MbUnit, xUnit, and MsTest (though weirdly it has a dependency on NUnit only)
nbuilder - NUnit
Flurl.Http - NUnit
OpenConver - NUnit
RhinoMocks - xUnit
Chutzpah - xUnit
Chill BDD - xUnit
MyTested.AspNetCore.Mvc.Licensing + 4 others from the same guy- xUnit
ReportGenerator - MsTest
dotMemoryUnit - not sure but their open source TC plugin for it and other .net projects use NUnit

So in total we have:
MSTest - 3
NUnit - 8
xUnit - 11
This is counting fsunit as MSTest, NUnit and XUnit, and if you consider 5 of them are by the same guy, essentially one project split into loads of components it seems, then that's 7 "unique" projects for xUnit - so really there's nothing in it, usage is about the same.  I have to confess I am surprised xUnit is so high given my own experiences but there you go - the point being there is no clear winner.
I'm not adverse to change, just not change for change sake, which is what this feels like tbh.
Do you have any particular reason to think there are not more contributors to the project simply because it uses NUnit rather than xUnit?
If you have capacity to put some effort into this project then perhaps adding source map support would be a better use of time than this?  After all, most people will be consumers of the project rather than contributors to it and I think lack of source map support will hurt it more than any other single factor.
Once again though, your project so your decision ultimately...

NUnit is by far and away the most popular still

.NET vNext is all xUnit: source
I've also not seen a repo with nUnit for .. well.. ages. I'm not an enterprise dev, though.
If .NET vnext is pushing xunit as their default, rest assured a majority of devs will also follow.

I have to confess I am surprised xUnit is so high

Again, refer to more recent repo's these days + .NET vnext/future.

just not change for change sake

Agreed - I've got better things to do with my time :)

Do you have any particular reason to think there are not more contributors to the project simply because it uses NUnit rather than xUnit?

It's about familiarity and consistency. This (I would hope) lowers the barrier to entry for helping.

If you have capacity to put some effort into this project then perhaps adding source map support would be a better use of time than this?

Agreed completely 👍 . But .. this capacity requires brain power which I don't have much left for this project, especially since it's been for-ever since I've even used this. As opposed to the brain-effort required to migrate to xUnit, wire up AppVeyor support and split this into repo's and consistent layout/structure ... though mind numbing, it's more labour than brain-effort.

After all, most people will be consumers of the project rather than contributors to it and I think lack of source map support will hurt it more than any other single factor.

Yep - couldn't agree more. But refer to previous comment

That list I referenced has votes cast this month, so pretty recent :)
MS Used to use MsTest but I didn't see everyone flocking to that, so I'm not sure that argument holds water :)
It still feels like change for change sake - I haven't seen any compelling reason to switch but hey it's your time to waste not mine :)

Closing this cause I can't be bothered, basically. If I was working with this library on a more regular basis, then I would. 🥂


Errors in Documentation

Describe the bug
There are some errors in documentation :
It's not :

component but components => http://adminbro.com/tutorial-writing-react-components.html
availableOptions but availableValues => http://adminbro.com/tutorial-customizing-resources.html

Thanks :)
Installed libraries and their versions

<EMAIL_ADDRESS>

@stelone thanks. fixed.


Can you turn off the Microsoft Python Language Server?

This morning my computer crashed while I was getting coffee. When I rebooted it it got very slow after a while, so I checked the system monitor and the MS Python Language Server was using around 7 gigabytes of memory. I'm now sitting here working with the system monitor open, periodically killing the language server so it doesn't eat my RAM.
Is there an option to turn off the language server? It seems like the functionality is sufficiently unstable that an option to turn it off is necessary.

It seems the Microsoft Python Language Server is turned off by checking the Python: Jedi Enabled setting. I had a similar issue and it worked for me.

You can set "python.jediEnabled: "true" to go back to using Jedi.


[v1.x] backport Invoke mkldnn and cudnn BatchNorm when axis != 1

[v1.x] backport Invoke mkldnn and cudnn BatchNorm when axis != 1
Description
(Brief description on what this PR is about)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments
@bgawrych  @pengzhao-intel

@stu1130 could you take a look for CI and we can merge it soon?

@mxnet-bot run ci [unix-gpu]

@pengzhao-intel the CI passed.


Don't send CharacterMoveInputEvent if I don't input anything

Motivation
During a debugging session I noticed, that the LocalPlayerSystem sends a CharacterMoveInputEvent every tick, even if I'm not pressing any key and not moving the mouse at all.
See https://github.com/MovingBlocks/Terasology/blob/develop/engine/src/main/java/org/terasology/engine/logic/players/LocalPlayerSystem.java#L175-L176
This does IMO not only create a lot of unnecessary events that might negatively impact, but it also creates a lot of "noise" and makes it harder to debug.
Proposal
Exit early from LocalPlayerSystem#processInput if there is no input, e.g. no keyboard input creating movement and no mouse or VR input creating view rotation.
My hope would be that this improves performance and reduces unnecessary noise.

@pollend @keturn @DarkWeird I have no clue whether or not this is a low-hanging fruit - might be. If I missed any other inputs this might try to process, I'd be interested to learn which.

This does seem worth looking in to. Good catch.
#4586 may have some other ideas to keep in mind while working on this.

Irc, CharacterPredictionSystem send this event too. Noticed for mob, while working with FlexableMovement

A wild guess on this: gravity on characters seems to come  from apply  downwards pull on every (affected) movement event. Therefore, might it be necessary to send "dummy no-change events" just to have the gravity be applied to characters each tick?
And since we only do this repeatedly for the player characters, NPCs are affected by gravitiy as soon as they move (e.g., walk or jump), but are not affected by gravity if just standing around... 🤔

That actually makes sense :see_no_evil: I would argue that this should ideally be done separate from actual movements, but  guess it's quite entangled at the moment and hard to "unfiddle"


Use vformat() instead of string concatenation inside TTR()

Translation won't work for this.

Thanks!


[DOC] Update docs for date processor in Data Prepper

What do you want to do?

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
The existing docs are missing a few new options. This readme has the latest info: https://github.com/opensearch-project/data-prepper/blob/main/data-prepper-plugins/date-processor/README.md
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
Existing doc: https://opensearch.org/docs/latest/data-prepper/pipelines/configuration/processors/date/

@oeyh: Is this and the mutate event processor specifically for Data Prepper 2.7?

This is not for 2.7. The relevant code is released, but the docs have a gap.
Specifically, it's missing:

Details about the patterns option under match block
to_origination_metadata option

It's also better to have some examples.


Update the example migration code in the docs to be 0.4.x-compatible.

This has been fixed here. http://truffleframework.com/docs/getting_started/migrations Thanks for the PR. Appreciate it!


Cannot compile FSharp.Core with dotnet core 2.1

Should I be able to? Works fine with dotnet core 2.0:

2.1.201 and below - works.
2.1.300 and above - does not work.

Here is the error:
FSC : error FS0193: The module/namespace 'Microsoft.FSharp.Core' from compilation unit 'FSharp.Core' did not contain the namespace, module or type 'string'
If that helps, the error is easily reproducible in other .fsproj if you add: <OtherFlags>--compiling-fslib</OtherFlags>

I'm not able to reproduce the issue unless I add that flag; it even happens on .NET Core 2.0. Also, you should never use that flag for a real project so I'm not surprised things would break.

You are trying to compile FSharp.Core as a .NET Core library?

@TIHan Absolutely, netstandard2.0 to be precise.

I don't expect that to work, since it is build against netstandard1.6. We'll eventually move off of that and make it a netstandard2.0 component, but I'm afraid that isn't in immediate plans, as it will require a major rev of the package that may have to coincide with F# 5.0.

I see. At some point, we will want to ship FSharp.Core as a netstandard 2.0 lib; which we will run into the issue you described. I'll make note of it so we can revisit it.

I don't think you can compile it to netstandard1.6 either with .NET Core 2.1.301 (but 2.1.201 works fine).

The good news is .NET Core 2.1.400 preview seems to work fine, so I guess it's just the 2.1.30x that has the issue.

I can't say if I've tried it, but I wonder if project.json is even supported with a .NET Core SDK build for .NET Core 2.1.

@cartermp That's not it, you can take it out but same thing. It's something to do perhaps with compiler switches, as it breaks very early, right away.

This appears to have been fixed since then, works now. Thanks!

No worries! Thanks for looping back here.


(MAINT) Demo toroidal functionality

Closing for now. May reopen in the future or replace with an actual webring.


Unhack destructuring.

This removes the $hack that were necessary to work around a destructuring bug in jaq 2.0 gamma. This has been fixed since then.

👍 maybe i will cherry-pick and possible squash this commit as i would like to cleanup branch a bit, was mostly to quickly share progress with you

Fixed in #20


Added support for custom python utils. Closes #1139

This PR changes the code icon in the sidebar to be custom utilities and moves the custom serialization into the new transfer/serialization looking icon. These utilities are always generated and can be used to make things like data loader classes much easier (no need for the previous workaround).

yay!

This change required the addition of a MyUtilities node to the project's metamodel (which can contain Code - from the pipeline library):

I am wondering if I should add an automatic migration to the projects as part of this PR. I am thinking that I won't do it in this PR (which would require people to manually migrate projects) and then look into it in another PR. Thoughts?


Remove >= from cabal-version

Hopefully this suppresses the following warning:
Warning: js-chart.cabal:1:27: Packages with 'cabal-version: 1.12' or later
should specify a specific version of the Cabal spec of the form
'cabal-version: x.y'. Use 'cabal-version: 1.18'.

I somehow completely missed this. Thanks!


fix(drm): backport drm driver fixes from lvgl 9

Applied relevant fixes from https://github.com/lvgl/lvgl/pull/4621, so that they can be used with lvgl 8.x.
Edit: Putting on hold to check some details wrt. drm_wait_vsync().

Will try to land more improvements in 9.x first.

Looking forward to it! Thank you in advance!


Return the authentication headers to an actual proxy in NoProxy mode

Title

Summary

Type
[] Bug fix
[] Feature request
[] Enhancement
[] Docs
Why?

Requirements

How to try it?

Documentation

Additional Information

Checklist:

[ ] My change requires a change to the documentation or CHANGELOG.
[ ] I have updated the documentation/CHANGELOG accordingly.

thanks for your pull request! will look at it, understand that it is convenient to return these headers altough usually it can be extracted on front-proxy

Traefik can delegate authentication to an external service and if the service answers with a 2XX code, access is granted and reply headers are copied into forwarded request:
https://doc.traefik.io/traefik/middlewares/http/forwardauth/#authresponseheaders

i made 2.4.0-rc1 release so there is docker image with that tag


fix npx vs npm

hey @Hades32, thanks for the contribution. I just updated the docs to v2 which changed a lot of files including this one. please create a new PR if the bug is still a thing.


[Duplicate] "IndexAllocation-Reference closed" error on search workload

What is the bug?
When running the vectorsearch OpenSearch benchmark workload on a constrained system (3GB memory, single node), repeated index/search workloads will occasionally cause node drops.
Other times, I am seeing the following error:
IndexAllocation-Reference error [ERROR] search_phase_execution_exception ({'error': {'root_cause': [{'type': 'illegal_state_exception', 'reason': "IndexAllocation-Reference is already closed can't increment refCount current count [0]"}], 'type': 'search_phase_execution_exception', 'reason': 'all shards failed', 'phase': 'query', 'grouped': True, 'failed_shards': [{'shard': 0, 'index': 'target_index', 'node': 'jgqwrThQTvuDDPQfxXZo_g', 'status': 500}) without a node drop. The workload succeeds with a small error rate.
How can one reproduce the bug?
Steps to reproduce the behavior:
Docker-compose.yml (based on the sample docker-compose.yml given in the OpenSearch docs, but with restricted memory):
services:
  opensearch-node1: # This is also the hostname of the container within the Docker network (i.e. https://opensearch-node1/)
    image: opensearchproject/opensearch:2.18.0 # Specifying the latest available image - modify if you want a specific version
    container_name: opensearch-node1
    environment:
      - cluster.name=opensearch-cluster
      - node.name=opensearch-node1
      - discovery.type=single-node
      - bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
      - "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
      - OPENSEARCH_INITIAL_ADMIN_PASSWORD=${OPENSEARCH_INITIAL_ADMIN_PASSWORD}
    deploy:
      resources:
        limits:
          memory: 3.0GB
    ulimits:
      memlock:
        soft: -1 # Set memlock to unlimited (no soft or hard limit)
        hard: -1
      nofile:
        soft: 65536 # Maximum number of open files for the opensearch user - set to at least 65536
        hard: 65536
    volumes:
      - opensearch-data1:/usr/share/opensearch/data # Creates volume called opensearch-data1 and mounts it to the container
    ports:
      - 9200:9200 # REST API
      - 9600:9600 # Performance Analyzer
    networks:
      - opensearch-net # All of the containers will join the same Docker bridge network
  opensearch-dashboards:
    image: opensearchproject/opensearch-dashboards:2.18.0 # Make sure the version of opensearch-dashboards matches the version of opensearch installed on other nodes
    container_name: opensearch-dashboards
    deploy:
      resources:
        limits:
          memory: 500MB
    ports:
      - 5601:5601 # Map host port 5601 to container port 5601
    expose:
      - "5601" # Expose port 5601 for web access to OpenSearch Dashboards
    environment:
      OPENSEARCH_HOSTS: '["https://opensearch-node1:9200"]' # Define the OpenSearch nodes that OpenSearch Dashboards will query
    networks:
      - opensearch-net

volumes:
  opensearch-data1:

networks:
  opensearch-net:

Params (faiss-sift-128-l2.json from the sample params with search_clients, id_field_name, and docvalue_fields added or updated):
{
    "target_index_name": "target_index",
    "target_field_name": "target_field",
    "target_index_body": "indices/faiss-index.json",
    "target_index_primary_shards": 1,
    "target_index_dimension": 128,
    "target_index_space_type": "l2",
    "search_clients":8,
    "id_field_name": "id",

    "target_index_bulk_size": 100,
    "target_index_bulk_index_data_set_format": "hdf5",
    "target_index_bulk_index_data_set_path": "sift-128-euclidean.hdf5",
    "target_index_bulk_indexing_clients": 10,

    "target_index_max_num_segments": 1,
    "target_index_force_merge_timeout": 300,
    "hnsw_ef_search": 100,
    "hnsw_ef_construction": 100,

    "query_k": 100,
    "query_body": {
         "docvalue_fields" : ["id"],
         "stored_fields" : "_none_"
    },

    "query_data_set_format": "hdf5",
    "query_data_set_path":"sift-128-euclidean.hdf5",
    "query_count": 100
  }

Commands:
docker-compose up -d

curl -k -X PUT "https://localhost:9200/_cluster/settings" -H 'Content-Type: application/json' -u 'admin:admin' -d '{
  "persistent": {
    "knn.cache.item.expiry.minutes": "1m"
  }
}'

#Index, search, index, search
opensearch-benchmark execute-test \
--workload=vectorsearch \
--target-hosts=https://localhost:9200 \
--client-options=basic_auth_user:admin,basic_auth_password:admin,verify_certs:false \
--workload-params=faiss-sift-128-l2.json \ #path to params file
--test-procedure=no-train-test-index-only \
--pipeline=benchmark-only \
--kill-running-processes

opensearch-benchmark execute-test \
--workload=vectorsearch \
--target-hosts=https://localhost:9200 \
--client-options=basic_auth_user:admin,basic_auth_password:admin,verify_certs:false \
--workload-params=faiss-sift-128-l2.json \
--test-procedure=search-only \
--pipeline=benchmark-only \
--kill-running-processes

opensearch-benchmark execute-test \
--workload=vectorsearch \
--target-hosts=https://localhost:9200 \
--client-options=basic_auth_user:admin,basic_auth_password:admin,verify_certs:false \
--workload-params=faiss-sift-128-l2.json \
--test-procedure=no-train-test-index-only \
--pipeline=benchmark-only \
--kill-running-processes

opensearch-benchmark execute-test \
--workload=vectorsearch \
--target-hosts=https://localhost:9200 \
--client-options=basic_auth_user:admin,basic_auth_password:admin,verify_certs:false \
--workload-params=faiss-sift-128-l2.json \
--test-procedure=search-only \
--pipeline=benchmark-only \
--kill-running-processes

What is the expected behavior?
Queries will complete without error, or the node will drop
What is your host/environment?

OS: Apple M3 Pro, Sequoia
Version: 2.18
Plugins: k-NN

Do you have any additional context?

This is fairly inconsistent, the error occurs about 50% of the time.
OpenSearch code pointer: https://github.com/owenhalpert/OpenSearch/blob/c557f2717ad45627cacd88e8243893dd84a56623/libs/common/src/main/java/org/opensearch/common/util/concurrent/AbstractRefCounted.java#L85

Similar issue reported here: https://github.com/opensearch-project/k-NN/issues/2344

@Gankris96 can you please take a look


Is there a way to minimize usage or properly tree-shake emojilib dependency?

I'm in the process of optimizing a Nuxt website, and I noticed that there is a quite large part of the bundle that is made up of  the emojilib package.
A quick analysis of my pnpm-lock.yaml is telling me that this dependency is loaded from
@nuxtjs/mdc>remark-emoji>node-emoji>emojilib

As you can see from the breakdown (this is the output of nuxi analyze), the emojis.json chunk is quite large, ~205/35gzip kb.
Is there a way to minimize its usage? I would say that not every project that needs Markdown also needs emojis, especially not the full library, especially since it has such relevant import cost.
Is there a way to properly tree-shake it, whitelist it, or any other way to reduce its size and avoid such heavy and mostly unused bundle? I also find it puzzling to see this running client-side.
Another possible solution would be to make remark-emoji an optional dependency, since, from what I see by reading its docs https://github.com/rhysd/remark-emoji, this package is used to transform emojis from this notation :rocket: to the proper emoji 🚀 (which is not handled by this library, but by an emoji font).
So in cases where the content editor directly uses emojis and not the :: notation, the whole package is basically not even used.
Thanks for this great module anyway, this is just a minor but useful optimization 💚

Any updates @farnabaz ?
I also had multiple problems with the emojilib dependency, especially when you don't use shamefully hoisting with pnpm.

Thanks for the issue and pinging
This should be fixed in edge version simply by disabling remark-emoji in Nuxt Config

@adamdehaven There will be a breaking change in the next version for using the module outside of Nuxt.
remark-emoji will not be registered by default in Vue applications

@adamdehaven There will be a breaking change in the next version for using the module outside of Nuxt.
remark-emoji will not be registered by default in Vue applications

As long as it’s documented :+1:
Could the remark-emoji package here be moved to devDependencies and peerDependencies in package.json? This would tell downstream package managers to install the package on their own.


Update email template with new RA loaction

/das/work/{{subString ownerGroup 0 3}}/{{ownerGroup}}/retrieve/{{strip sourceFolder "/"}}/	 should become
/das/work/{{subString ownerGroup 0 3}}/retrieve/{{ownerGroup}}/{{strip sourceFolder "/"}}/


Composer version

So, little confused here with the versions. Composer installs version 4.0.1 by default, but on the website (https://www.phpcaptcha.org/download/), or anywhere else for that matter, is no mention of version 4. The latest version in master and on the website seems to be 3.6.7, so why does Composer installs v4 and how is 4.0.1 different?

afaik the 4.0.1 version is in the nexgen branch, and that one is working best.. the 3. version is broken for me..

Nextgen branch was intended to be the next major version of this and had added features. If you want to use any of the code I'd start with that branch.
Around the time development finished on that, image captchas like this are now easily defeated with a little bit of time and some free tools and as a result I have failed to keep up with this project.

The changes in nextgen new from master are/were:
4.0.1
- Increase captcha difficulty
- Add setting "use_text_angles". Enable to select a random angle and step value and draw each character at an angle in a step like fashion
- Add setting "use_random_spaces". Enable to insert 1-3 spaces between a random group of letters some of the time
- Add setting "use_random_baseline". Enable to draw letters at a random height instead of centered.  Each character's baseline is a step up or down from the previous (not totally random)
- Add setting "use_random_boxes". Enable to draw a bounding box around one or more characters at random
- Improve performance of captcha generation when using distortion (perturbation) and noise (noise_level)
- Enable image anti-aliasing
- Make all text functions multibyte safe when using UTF-8 or other encodings for charsets and wordlists (using mbstring)
- Deprecate background images.  May be removed in future version or limited to special use
- Fix code display issue when using a math captcha that was re-displayed after being retrieved from a StorageAdapter

4.0.0
- REMOVE namespaces (everything is tied to a captcha ID now)
- Implement StorageAdapter interface
- Move session and database storage into StorageAdapters
- Add memcached StorageAdapter (requires PHP extension memcached)
- Add Redis StorageAdapter (requires PHP extension Redis [https://github.com/phpredis/phpredis])
- REMOVE options use_sqlite_db and sqlite_database (deprecated since 3.2 RC4)
- REMOVE database options from class (options are now defined in config.inc.php)
- REMOVE Flash audio playback and Flash fallback
- REMOVE "static captcha" functionality (getCaptchaId and checkByCaptchaId)
- REMOVE SoX audio manipulation from PHP via shell_exec


[INLONG-532] query cluster info

query cluster info
JIRA link - [INLONG-532] created by stingpeng

fixed by https://github.com/apache/incubator-inlong/pull/420


Redesign function argument data structures

Post #644, the current data structures look like:
pub enum FnArg {
    SelfRef(ArgSelfRef),
    SelfValue(ArgSelf),
    Captured(ArgCaptured),
    Inferred(Pat),
}

// `&self`, `&'a self`, `&mut self`, `&'a mut self`
pub struct ArgSelfRef {
    pub and_token: Token![&],
    pub lifetime: Option<Lifetime>,
    pub mutability: Option<Token![mut]>,
    pub self_token: Token![self],
}

// `self`, `mut self`
pub struct ArgSelf {
    pub mutability: Option<Token![mut]>,
    pub self_token: Token![self],
}

pub struct ArgCaptured {
    pub pat: Pat,
    pub colon_token: Token![:],
    pub ty: Type,
}

The FnArg type is contained as Punctuated<FnArg, Token![,]> in both FnDecl (functions, associated functions, trait functions, extern functions) and ExprClosure.
The grammar restriction is that SelfRef and SelfValue can only appear in FnDecl while Inferred can only appear in ExprClosure. These are different enough that it may be better to split the two types. Something like:
pub enum FnArg {
    Receiver(Receiver),
    Typed(ArgTyped),
}

pub enum ClosureArg {
    Typed(ArgTyped),
    Inferred(Pat),
}

enum Receiver {
    pub reference: Option<(Token![&], Option<Lifetime>)>,
    pub mutability: Option<Token![mut]>,
    pub self_token: Token![self],
}

pub struct ArgTyped {
    pub pat: Pat,
    pub colon_token: Token![:],
    pub ty: Type,
}

Implemented in ae32af4b4d8fe9083c3aa4d0da6302390b8737b7.


Add extended dynamic state extension

@filnet Thanks! Merged!
Not sure why the commit title reads Add VK_KHR/EXT_extended_dynamic_state extension, there's no KHR extension with the same name right? If there was it should probably have its own struct in the right place anyway.

The title is wrong : it is a copy/paste from a similar title.
Sorry about that...


Alert sound played inexplicably when scrolling with arrow keys

When scrolling through an article with the arrow keys, the MacOS alert sound is heard:
https://github.com/Ranchero-Software/NetNewsWire/assets/97384040/2afcd8df-48ce-4c3a-9f3c-6398ce2217ab
Playing the sound makes sense when you reached the end of the article, but not while actively scrolling

Hi @yuvalne, have you encountered this issue before or it only happens after a macOS or Safari upgrade?
It looks more like a WebKit isssue according to the following callstack and I could reproduce it as well with macOS 13.3.1 (a) and the latest Safari 16.4.

Still I'll try to take a deeper look at it.

I believe this has been a thing for a while now, although as I only now bothered opening the ticket I can't really guarantee when it started.

Some testing with my other Macs confirms this should be an issue introduced with macOS 13.3. It could be reproduced with other applications utilizing WKWebView (a component that loads renders HTML pages using WebKit Framework bundled along with the system) as well.
If this issue bothers, a quick solution would be turning down the ”Alert Volume” in “System Settings” - “Sound”.
Ethan Wong @.>
On May 14, 2023 at 19:46 +0800, Yuval Talya Nehemia @.>, wrote:

I believe this has been a thing for a while now, although as I only now bothered opening the ticket I can't really guarantee when it started.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Update: this issue has already been addressed recently on the upstream WebKit branch. More info could be found here: https://bugs.webkit.org/show_bug.cgi?id=255039.
Since this issue still persists on macOS 13.4 RC 2, we'll probably have to wait until the next macOS stable release after macOS 13.4 to carry this fix.

I think we can optimistically close this issue, given that the fix has been addressed in WebKit.