Fix StatementMetric not Emitting Rows on First Presence of New Queries

What does this PR do?
This fixes the situation where a new query is found after the first run of database integrations. Before this change, that first time a new query was executed would not have any rows emitted (but would be added to the local "cache" of rows). This can cause some confusion when someone runs ad-hoc queries and expects to see query metrics for them.
This changes fixes that by interpreting the absence of a query in the local cached rows as a row filled with 0 values for all metrics.
Motivation
Provide a less confusing user-experience in some scenarios.
Additional Notes

Review checklist (to be filled by reviewers)

[x] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[x] PR title must be written as a CHANGELOG entry (see why)
[x] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[x] PR must have changelog/ and integration/ labels attached

That makes sense to me. I'll look into it and have a separate PR for this ownership change. There are at least a few files that should clearly be owned by DBM.

Should we update the CODEOWNERS or move some code around so that this DB-specific code doesn't require agent-core review?

That makes sense to me. I'll look into it and have a separate PR for this ownership change. There are at least a few files that should clearly be owned by DBM.

This is weird. I looked and we have those lines already in OWNERS which should only require review from agent-integrations or database-monitoring?
**/base/utils/db/statement_metrics.py               @DataDog/database-monitoring @DataDog/agent-integrations
datadog_checks_base/tests/**/test_db_statements.py  @DataDog/database-monitoring @DataDog/agent-integrations

Should we update the CODEOWNERS or move some code around so that this DB-specific code doesn't require agent-core review?

That makes sense to me. I'll look into it and have a separate PR for this ownership change. There are at least a few files that should clearly be owned by DBM.

This is weird. I looked and we have those lines already in OWNERS which should only require review from agent-integrations or database-monitoring?
**/base/utils/db/statement_metrics.py               @DataDog/database-monitoring @DataDog/agent-integrations
datadog_checks_base/tests/**/test_db_statements.py  @DataDog/database-monitoring @DataDog/agent-integrations

@djmitche : This PR should fix the ownership rules. Thanks for noting it.

Discussed this one with @djova and we decided to drop this proposed change because it would introduce bad edge-cases:

By defaulting stats 0 when a row isn't in the previous execution's cache, in the situations where a row pops out and back into the cache, we'd emit query metrics with potentially greatly overinflated values. This would happen mostly for sqlserver but also potentially with postgres and mysql if the configured size for the statement stats is higher than the limit used in the integrations (10k).

The LRUCache could help minimize the edge-cases but it would be a significant (and probably unacceptable) increase in memory usage in sqlserver cases where the query cache can include hundreds of thousands of rows.

We could revisit this in the future and consider adding the LRUCache for mysql and postgres along with a check for the statement stats size but we'd want to consider what to do when the setting is higher than our 10k limit:

Do we increase the limit?
Do we set the LRU cache to a size greater than the configured limit?
Do we revert to the behavior where we don't default to 0?


Memory allocation exercise

A draft PR to discuss whether including memory allocation (which is part of the standard library, not the core language) is worth including in Ziglings.
Resolves #193

This topic is one of the cornerstones of efficient Zig usage and quite difficult to grok for people not accustomed to it, especially due to lacking tutorial resources. I would definitely suggest this is a must to include in ziglings.

@ratfactor before I make this MR pass the checks by adding patches, does this example seem reasonable to you? Are there some changes to the example text or framing that would improve it?

@chrboesch I changed the comment line length and put my example at the end

Looks very good! :smile:

Switched the empty placeholder to the ??? placeholder.

This looks great, thank you!


[WIP] Add password_digest to authentications

This was added to allow Apache to validate the password digest stored in
Postgres Database. This way we dont have to expose our encryption keys
to Apache.

@kbrock @Fryguy @gmcculloug
Please review

@gtanzillo Please also review.

:+1: Looks good to me but awaiting response to Jason's question regarding setting the password_digest for existing authentications.

I'm trying to wrap my mind around this.
I understand technically what we are doing. but the implication says that we will login to another appliance without using an actual password or something.
can we have a meeting around this?

@gtanzillo
I added a second commit which has the migration to add password_digest to existing rows

@kbrock
We won't be logging into an appliance without a password. All this PR is doing is creating a one way hash of the password and storing it in the database so that Apache can validate an incoming request which has the password and comparing the password digest. This way Apache doesn't have to know our keys it uses the password supplied by the incoming request and does a bcrypt hash match.

We're going to point Apache straight at the database? Will that work if it's external?

@mkanoor ping me when you have some time, we need to discuss Apache/GIT when external auth is enabled to Ldap, AD or IPA.  Thanks.

@matthewd
Apache mod_auth_pgsql allows for the database to be local on the server or remote.
http://www.giuseppetanzilli.it/mod_auth_pgsql2/
Auth_PG_HOST

@mkanoor thanks for clarification - I'm good with this change.
@matthewd it will work with both. unfortunately we'll have one more service connecting to the database.

Our app has enough permissions to modify the apache config?!

@matthewd Yes!

:+1:  here too.
Just discussed this with Madhu. External auth with AD/LDAP/IPA/SAML (and any other acronym you wanna add) does not apply here.  This authentication here is used for system type accounts, i.e. a UI or Automate worker needing to access/sync the Git repo.  Not the appliance user that was logged in and originated the work. So the credentials for system type account will be sent to Apache (basic auth) to be authenticated against our Postgres before proceeding with the Git work.

I think we need a migration spec for db/migrate/20150813202625_set_missing_password_digest_in_authentications.rb

Migrations shouldn't use the real models

Agree with @matthewd...you need a stub, which the spec should end up enforcing.  (I still wish Rails had a config for migrations to disable the real models directory...maybe we can just manipulate config.autoload_paths or something).

We shouldn't be storing the digest for every password here; just whatever type we'll actually need to be able to externally authenticate.
Storing a second encoding of other passwords with which we've been entrusted is just increasing attack surface for no gain.

@matthewd Interesting...how do you think we could do that...just add it in for that one line item?  Would it be weird to have a password_digest method that doesn't "work" for the other types?

@Fryguy I think I'd expect us to be creating a new type of Authentication subclass anyway: some sort of "server shared secret"... it seems semantically quite different from the existing username+password arrangement, even if it has similar-sounding fields.
And at that point, it becomes trivially reasonable to have a method that only works sometimes -- for better or worse, that's how Rails STI works.

I like the new subclass idea.

@Fryguy @matthewd
Added a new type of class to store the password_digest.
Please review

Closed temporarily


move "cwl-runner" script from the CWL extra to a different package or a different extra

By always installing toil-cwl-runner as cwl-runner, Toil takes away the users choice to switch between CWL implementations.
https://github.com/BD2KGenomics/toil/blob/master/setup.py#L76
Options:

pip install toil[cwl_default] is equivalent to the current behaviour (both toil-cwl-runner and cwl-runner console scripts are setup; and pip install toil[cwl] only installs the toil-cwl-runner script
the reverse of the above: pip install toil[cwl_notdefault] leaves out the cwl-runner console script
the cwl-runner shortcut is moved to another package, like cwlref-runner is for cwltool: https://github.com/common-workflow-language/cwltool/tree/master/cwlref-runner

I prefer option 1, but I'm curious to hear what others think..

cwltool is still an option if the user wishes.

Option 1 makes sense to me too, along with some documentation.

Is there really a need for the cwl-runner to be a generic command?   Give that there will be some logical reason to chose some runner over another, it seems most straight forward to not attempt to hide it.  Just have a toil-cwl-runner, a foo-cwl-runner, etc.
If there is real demand, then make a generic symbolic like.

Referencing and closing #1804 as it's basically the same issue.

I feel like having one generic command makes more sense for toil, just toil-cwl-runner.  Of course keeping cwltoil for backwards compatibility.  If a user wants to set the default for their cwl-runner though, I feel like it should be done from the cwl side, not toil.  Having toil[cwl_default] AND toil[cwl] seems potentially confusing, especially for new users.
I feel like when a user installs cwltool, if they want to override the command, they should be able to specify that they want to use toil as their default cwl-runner with an option or config file.

I would even make cwltoil a bash script that tells the user to
run toil-cwl-runner and exits with an error.  All this software
is immature, wean the off the old stuff.
Agreed, having multiple install modes will be confusing.
DailyDreaming<EMAIL_ADDRESS>writes:

I feel like having one generic command makes more sense for toil, just
toil-cwl-runner. Of course keeping cwltoil for backwards compatibility. If a
user wants to set the default for their cwl-runner though, I feel like it
should be done from the cwl side, not toil. Having toil[cwl_default] AND toil
[cwl] seems potentially confusing, especially for new users.
I feel like when a user installs cwltool, if they want to override the command,
they should be able to specify that they want to use toil as their default
cwl-runner with an option or config file.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.*


Allow Fastly headers and purges to be disabled globally

Useful for tests and development modes

Is this going to get merged?

I think there are cool ways to get fancy about this (e.g. we could stub out the Fastly client in dev/test envs and not have to do disabled? checks across the lib), but at the very least I think we should move the logic referred to in my comment into the FastlyRails.configuration object.
e.g. something like:
FastlyRails.configure do |c|
  c.api_key = ENV['FASTLY_API_KEY']
  c.enabled_environments = ['production', 'staging']
end

and then
unless FastlyRails.disabled?
  ...yadayada...
end

Check out the Sentry gem for an example of this that I align with -
https://github.com/getsentry/raven-ruby/wiki/Advanced-Configuration#environments
and
https://github.com/getsentry/raven-ruby/blob/dbb0a8d075e135d4a26cfea14545517efb55b7d0/lib/raven/configuration.rb#L169-L171

@mmay Here is another approach https://github.com/fastly/fastly-rails/pull/39

Closing in favor of #39

Great job, I like #39


[BUG] Event Grid not publishing updated package

Describe the bug
I've installed the latest version 3.2.0 of Microsoft.Azure.EventGrid from nuget.org. The publish date is almost a year old. Data Lake v2 has introduced new fields in the StorageBlobCreatedEventData model that aren't present in the package.
Expected behavior
Specifically, I expect ContentOffset to be present in the package, since it's in the repo but it's not there.
I would expect either a more updated package, either stable or the prerelease version referenced in the assembly.
Actual behavior (include Exception or Stack Trace)
The StorageBlobCreatedEventData class in the package doesn't have this field

To Reproduce
Download the package.
Environment:

Name and version of the Library package used: Microsoft.Azure.EventGrid 3.2.0

Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): .NET Core SDK (reflecting any global.json):
Version:   3.1.101
Commit:    b377529961

Runtime Environment:
OS Name:     Windows
OS Version:  10.0.18363
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.1.101\
Host (useful for support):
Version: 3.1.1
Commit:  a1388f194c
.NET Core SDKs installed:
2.1.511 [C:\Program Files\dotnet\sdk]
2.1.512 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.2.401 [C:\Program Files\dotnet\sdk]
3.1.101 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

IDE and version : Visual Studio Enterprise Version 16.4.6

Thanks for reaching out. We have this task in our backlog and will address this appropriately. thanks.

@ahamad-MS @jfggdl, could you please leave the customer reported issue opened until it's resolved or point to the service-specific public issue to subscribe to and track the progress? Thank you.

The updated StorageBlobCreatedEventData model is available in the new EventGrid SDK that is currently in beta.

@josiahvinson   .. The issue is resolved in the newest SDK version. Can you please move to the new SDK and verify that.
Feel free to close the issue if there is no more issues.
thanks

It works, thanks!


powerLoad and powerConsumed for WiFi power plug and power strip

It seems the powerLoad and powrConsumed capabilities for the WiFi power plug and power strip and not available anymore. Is this something on the todo list or has support been dropped completely?

They are currently available for the power plug connected to a gateway as it was the only one I was able to verify support on. It should be easy to add support for it if there any devices that also report these values. Any specific devices that support it?

I was under the impression that all plugs supported this (I dont own any myself). Guess not then.


Adding features to support task chaining, read variables from YAML and reading python functions from .txt

The Pull request contains the following changes:

Added feature to read python functions from a given local .txt files or read from YAML config.
Added feature to read task variables from a GCS (.yaml) file as per task or read from YAML config.
Added Feature to add custom task chaining dependencies or use default dependencies. This also includes task validation as per defined task in YAML config and tasks mentioned in custom dependencies.
Removed dynamic_dag flag feature to make solution efficient and light weight.
Bug fixes and performance improvements

Reviewed the changes and Merging the PR.


Add Autodiscovery

That extra>laravel property should be sufficient to add auto discovery.

Thanks Emil. I've not touched Laravel for a good few months!

Doesn't sound like a good few months to me ;-)

Ha! Well, South Africa and Australia were pretty good! Lots of Vue too :P


No clear detailed instructions to setup a Remote VM

Doc reads:
"You can use a system-built conda environment, an already existing Python environment, or a Docker container. To execute on a Docker container, you must have a Docker Engine running on the VM. This functionality is especially useful when you want a more flexible, cloud-based dev/experimentation environment than your local machine."
This section should be more detailed. For docker, at a minimum a link to this page if setting up a ubuntu box: https://docs.docker.com/engine/install/ubuntu/
For the setup of Conda, we should specify how to install it (should it be done as the user used to attach the Remote VM to AML? Should it be installed as sudo?). Etc.
Some understanding of the user persmissions required for the user that runs the AML scripts so that someone could properly setup such a custom VM to be attached to AML and expect to have any type of experiment run properly (Environment setup via Conda or Docker).

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

ID: 568cfb80-0a3f-3bb7-6215-f89949c1a12e
Version Independent ID: 54f72669-b459-f04f-6639-c5ff1e812232
Content: Set up training & inference compute targets - Azure Machine Learning
Content Source: articles/machine-learning/how-to-attach-compute-targets.md
Service: machine-learning
Sub-service: core
GitHub Login: @sdgilley
Microsoft Alias: sgilley

@aldelar we'll review your feedback and get back to you shortly. Thanks.

@aldelar the information is available on separate documents (set up dev environments and set up software environments).
@sdgilley perhaps we can add a reference links in this document for clarity?

https://docs.microsoft.com/en-us/azure/machine-learning/how-to-configure-environment#local
This link does not cover with enough details what you need to do to setup conda: which user does it need to be setup for? I tried the instructions for the user that created the VM, and as 'sudo' (ubuntu system), and none of these options lead to a system that can function with AML as a Remote Compute. The instructions here are too 'generic' and do not clearly indicate what needs to happen for a Remote VM to be properly setup and functional. What's missing really is how AML accesses the remote compute to understand how to properly install Conda. And BTW, one should not need to install the Azure Core SDK on that machine as far as I understand, it would install itself within the new conda env when needed. So that part is ok for 'local' but not for a remote VM. The instructions are currently merged in one section but they should be two different sections.
Maybe there's confusion here now that I see all this: in that link, when we say 'Remote VM' we just mean a VM do do ML.
But 'Remote VM" is also a concept of AML (to 'attach a VM as Remote'), and in that case the setup is different.
Does it make sense? For the second scenario, we do not have any instructions.
https://docs.microsoft.com/en-us/azure/machine-learning/how-to-use-environments
This is not really relevant, it's about how to setup an Environment for an experiment, it has nothing to do about setting up the actual Remote VM OS to be 'AML Ready'.
I would definitely link to the 'set up dev environments' link, but that page also needs further updates in my opinion.

@GiftA-MSFT I think in accordance with @aldelar 's comment above that this should be re-opened.
I am having a similar usecase, that I have some on-premise hosts that I want to use as compute targets in AML.
This is however not trivially possible, as there is no clear documentation for how to add it as a "Remote VM" or "Attached Compute" in the documentation. The "Attached Compute" does not appear to be an option directly, because it requires a Resource ID, which only is acquired, when the Remote VM is added as a DSVM.
It is mentioned here: https://docs.microsoft.com/en-us/azure/machine-learning/how-to-attach-compute-targets#vm
that on-premise resources should be configured as such, but there is no description of how that I was able to find.

@GiftA-MSFT can we possibly re-open this?

@GiftA-MSFT
Same here, this is the real showstopper for us to start using AML
Thanks

Can we re-open this issue?
I do not think AML supports running on remove VMs which are not in Azure @ecly, but it should support running jobs on custom VMs in Azure. Nevertheless, the steps that it takes to setup/prepare such a VM are not clearly documented (only at a high level as I described earlier).
I am a Data & AI CSA, and I can't figure this out with the doc, so imagine what our customers may run into if they even dare to try this process.
With a clean ubuntu image + a clean docker install + a clean conda install, I keep on getting AML 'stuck' on an error which isn't even surfaced back to AML (no logs in AML studio, but the remove VM I setup shows a failure of the platform, and I have no idea what part of my setup isn't appropriate since it's not described anywhere).
Let's re-open and discuss this issue @GiftA-MSFT ?

In the meantime I was successful in attaching a VM built from the DSVM image template (for instance microsoft-dsvm:ubuntu-1804:1804-gen2:latest).
The missing doc is how to build a minimal VM that starts from a ubuntu image (like Canonical:UbuntuServer:18_04-lts-gen2:latest) + necessary installation instructions of the minimum set of packages to have this VM enabled as an 'attached compute' in AML (docker install / conda install namely if that's all it needs, and HOW in details, using which user privileges, etc.)


OrgUnit - Add all fields/properties to create/modify

All fields are already accounted for.  Add available properties.


Unable to select default branch (main) on upstream repo, when working off a fork

Extension version: v0.76.1
VSCode Version: 1.84.2
OS: linux
Repository Clone Configuration (fork of an upstream repository): origin (my fork): https://github.com/RasmusWL/codeql, upstream: https://github.com/github/codeql
Github Product: Github.com

Steps to Reproduce:

Work on a fork of a repo.

Create a branch on top of a non-main branch on your own fork

$ git log --oneline --graph
* d93926291d - (HEAD -> example-pr) dummy (33 seconds ago) <Rasmus Wriedt Larsen>
* 69453aa144 - (origin/clean-tests, clean-tests) Python: Fix missing newline in `.expected` (26 minutes ago) <Rasmus Wriedt Larsen>
* 55f5b26ba6 - Python: Accept new ordering of query predicates in `.expected` (27 minutes ago) <Rasmus Wriedt Larsen>
* 721bde1ce8 - Python: Delete orphaned `.expected` files (37 minutes ago) <Rasmus Wriedt Larsen>
*   2e9d548083 - (upstream/main, upstream/HEAD, origin/main, main) Merge pull request #14706 from RasmusWL/class-attribute-flow (2 hours ago) <Rasmus Wriedt Larsen

Use extension to start creating a PR.

it initially suggested to use the non-main branch as the target for this PR.

Use the Change Repository... feature of the branch selector of the base branch, set it to upstream (github/codeql)

Search for main on upstream

but get no results 😞

(I am able to select main on the origin remote, but that just files a PR against the main branch on my own fork 🙈)

@RasmusWL the initial suggestion is expected: If you are on a fork, and you create a branch from a branch that isn't the default branch (exactly as you did), then the suggested base branch will be the branch that you branched off of.
Branches from the upstream repo should be listed in the "Base" picker" as you expected. However, it looks like we aren't detecting your upstream repo at all. Can you share the output of git remote -v?

Sure thing :+1:
$ git remote -v
amammad	git@github.com:amammad/codeql (fetch)
amammad	git@github.com:amammad/codeql (push)
origin	git@github.com:RasmusWL/codeql.git (fetch)
origin	git@github.com:RasmusWL/codeql.git (push)
upstream	git@github.com:github/codeql.git (fetch)
upstream	git@github.com:github/codeql.git (push)

Thanks, can you also share the value of githubPullRequests.remotes?

Hope it's just the value from Settings 🤞

"githubPullRequests.remotes": [
  "origin",
  "upstream"
]

I can repro. We don't fetch all branches if it takes more than 5 seconds to fetch them all. Even when this happens, we should still include main.

Looks good!


Has this project been abandoned?

@nickdodd79 firstly, thanks for such a great library. Secondly, has this project been abandoned?
I want to utilise it, but there has not been a new release since mid-2021, and there doesn't seem to be any activity from you on recent issues or PRs.
Would you like some support to keep this going? If so how can we do that?

Hi @baynezy, I believe this is abandoned unfortunately.
I built a modern replacement. It fixes the serious performance issues, introduces support for new types, and will maintained (with automatic updates from Bogus).
soenneker.utils.autobogus
Contribution is welcome!

duplicate of #108 ;)


fix unit test

Trying to run the test for the first time from brand new clone and the first test failed.

Hi,
This is linked to #19d0b2921ee01d39b8d71775425f451a334ccee2 which introduces default values for locales and responseFields attributes, to workaround a bug that prevented to provide configuration's default values for this attributes.
I merge this PR ; thanks for the fix.


Could you offfer DenseNet_cifar100 weight?

Could you offfer DenseNet_cifar100 weight?
I can't find this file in google.

No I can't train such large models on my laptop.


Can we get a license for this?

First off, I'd like to thank you for your work on actually making webRTC native be usable for anyone who isn't Google.
I have a small request. Would it be put the builder stuff under an actual license so it can be redistributed freely? (I'd personally like to see it licensed under three-clause BSD license like libwebrtc itself)

Thanks for the suggestion. Yes, of course. 59f0416cf99619f5052fe390ef5d5ef8845e31d5


Avoid params char[] allocation

This method got inlined a few methods, so it's hard to see, but I think this was this array creation, or probably also including an inlined: https://github.com/Microsoft/msbuild/pull/2284.

@dotnet-bot test Windows_NT Build for Full please


Release Form Recognizer 3.1.0-beta.2

Package has been released https://www.nuget.org/packages/Azure.AI.FormRecognizer/3.1.0-beta.2


new commit on superset_config.py trys to import superset.typing but module not found

Environment
OS: Fedora 31
superset: Superset 0.35.2
node: v12.14.1
npm: 6.13.4
python: Python 3.7.6
Reproduce

conda create env
conda activate env
pip install --upgrade setuptools pip
pip install apache-superset
I delete ~/.superset/superset.db
add superset_config.py file  to ~/.superset/
edit SQLALCHEMY connection string to connect to mysql db
superset db upgrade
flask fab create-admin
fill out info

Expected results

Admin user successfully created

Actual results
ERROR:root:Found but failed to import local superset_config
Traceback (most recent call last):
File "/home/###/.conda/envs/superset/lib/python3.7/site-packages/superset/config.py", line 701, in
from superset_config import *  # pylint: disable=import-error
File "/home/###/.superset/superset_config.py", line 37, in
from superset.typing import CacheConfig
ModuleNotFoundError: No module named 'superset.typing'
Usage: flask fab create-admin [OPTIONS]
Error: While importing "superset", an ImportError was raised:
Traceback (most recent call last):
File "/home/###/.conda/envs/superset/lib/python3.7/site-packages/flask/cli.py", line 240, in locate_app
import(module_name)
File "/home/###/.conda/envs/superset/lib/python3.7/site-packages/superset/init.py", line 34, in
from superset import config
File "/home/###/.conda/envs/superset/lib/python3.7/site-packages/superset/config.py", line 701, in
from superset_config import *  # pylint: disable=import-error
File "/home/###/.superset/superset_config.py", line 37, in
from superset.typing import CacheConfig
ModuleNotFoundError: No module named 'superset.typing'
Additional Comments
I am putting superset_config.py in ~/.superset. Is that wrong? Its seems to be reading config file from conda sitepackages instead. In the docs you say to make sure this config file is in your Python Path. What does that mean?

hi, may i know how your solve the issue? I also facing the same

Hey yeah yeah I will post something tn, currently corona shopping for my life. The gist is you have to add superset to you r python path of your virtual environment. Are you using venv or conda?
Get Outlook for Androidhttps://aka.ms/ghei36

From: i2cute<EMAIL_ADDRESS>Sent: Thursday, March 12, 2020 11:50:09 PM
To: apache/incubator-superset<EMAIL_ADDRESS>Cc: Matthew Arcila<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [apache/incubator-superset] new commit on superset_config.py trys to import superset.typing but module not found (#9027)
hi, may i know how your solve the issue? I also facing the same
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-superset%2Fissues%2F9027%23issuecomment-598535083&data=02|01||daba867c22214f5bdf3408d7c701a0fa|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637196682110343063&sdata=tZDmtqYOzYyT0hZgMLALe65tOQFSTsUvRRYvEdROfXw%3D&reserved=0, or unsubscribehttps://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC3KB3QUBVZPKFPFCY5WKRDRHGUPDANCNFSM4KL3YTVA&data=02|01||daba867c22214f5bdf3408d7c701a0fa|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637196682110353054&sdata=se5ZteOvfVwHrcs1XVrStrcBwqurUPYZxjpJEOqHhUw%3D&reserved=0.

I did
docker-compose -f docker-compose-non-dev.yml pull
docker-compose -f docker-compose-non-dev.yml up
now I have started seeing error :
superset_init           | ModuleNotFoundError: No module named 'superset.typing'

One possible solution.
You can copy the file superset/superset_typing.py to superset/typing.py. The last version(1.5.0) needs this fix. One or more files needs import the typing.py but the real name is superset_typing.py

@villebro This is an issue in the upgrade from 1.4.0 to 1.5.0 also.  As suggested bt @amarolx  I did copy the file superset_typing.py to typing.py and it went through

@Mabloq @amarolx @srinisubramanian did you try running with TAG as instructed in the docs? TAG=1.4.0 docker-compose -f docker-compose-non-dev.yml pull
Specifically this part:

I am not using docker but a native pip install. I upgraded from 1.4.0 to 1.5.0 and had the issue. For another instance I use docker and did not have this issue there when I upgraded.


Unable to build project on Node version 18 and above

The project does not build on newer versions of node. I tried on Node version 18.12.1 and 19.1.0. I had to revert Node to LTS Gallium 16.18.1 for the project to build.
npm start

><EMAIL_ADDRESS>start
> webpack-dev-server --config webpack/base.js --open

ℹ ｢wds｣: Project is running at http://localhost:8080/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /var/www/html/games/demo
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/var/www/html/games/demo/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:471:10)
    at /var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:503:5
    at /var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:358:12
    at /var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
node:internal/crypto/hash:71
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/var/www/html/games/demo/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:471:10)
    at /var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:503:5
    at /var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:358:12
    at /var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at Array.<anonymous> (/var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:205:4) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.12.1

For reference, also an issue in 17
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:135:10)
.
.
.
at iterateNormalLoaders (/home/carl/game1/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at Array. (/home/carl/game1/node_modules/loader-runner/lib/LoaderRunner.js:205:4) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
Node.js v17.9.1

Ran into the same issue, using nvm to install node v16.18.1 worked. Thanks!

Running into this issue as well

Also having this issue. Most of the advice you find online for resolving this suggests either downgrading to Node 16 or using legacy SSL (for example). These solutions are both insecure and a bit intimidating for newbies who might be coming to Phaser for the first time.

The project does not build on newer versions of node. I tried on Node version 18.12.1 and 19.1.0. I had to revert Node to LTS Gallium 16.18.1 for the project to build.
npm start

><EMAIL_ADDRESS>start
> webpack-dev-server --config webpack/base.js --open

ℹ ｢wds｣: Project is running at http://localhost:8080/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /var/www/html/games/demo
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/var/www/html/games/demo/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:471:10)
    at /var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:503:5
    at /var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:358:12
    at /var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
node:internal/crypto/hash:71
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/var/www/html/games/demo/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:471:10)
    at /var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:503:5
    at /var/www/html/games/demo/node_modules/webpack/lib/NormalModule.js:358:12
    at /var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at Array.<anonymous> (/var/www/html/games/demo/node_modules/loader-runner/lib/LoaderRunner.js:205:4) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.12.1

Has anyone found solution to this

The fix without downgrading the node version is to run npm install webpack@latest
Then update the webpack-cli using the force tag npm install webpack-cli@latest --force
this worked with node 18.16.0 and npm 9.5.1

After following your instructions and run npm start i am faced with the issue

I know this thread is a little stale, but to fix these issues, delete the node_modules folder if you already ran the install command, and delete the package-lock.json file, this is important! run npm install and then run npm start that should get things running.
The reason this works is because the lock file is for "locking" down the versions defined in the package.json file, so when npm install webpack-cli@latest --force was run, none of the other packages got updated that are needed with the latest webpack. Deleting the lock file now allows all the carrots (^) on the versions in the package.json file to look for the newest version and will download them now that the lock file isn't forcing them to remain on the original versions defined there.

Doesn't work for me. I followed the steps a few times and I get
Error: Cannot find module 'webpack-cli/bin/config-yargs'

I know this thread is a little stale, but to fix these issues, delete the node_modules folder if you already ran the install command, and delete the package-lock.json file, this is important! run npm install and then run npm start that should get things running.
The reason this works is because the lock file is for "locking" down the versions defined in the package.json file, so when npm install webpack-cli@latest --force was run, none of the other packages got updated that are needed with the latest webpack. Deleting the lock file now allows all the carrots (^) on the versions in the package.json file to look for the newest version and will download them now that the lock file isn't forcing them to remain on the original versions defined there.

This is fixed with v2.0.0 of this template.

Thanks


Firefox Event date dropdown not working

The event date dropdown menu under "Create Event" does not work on firefox, but it works perfectly fine on chrome.
Firefox (Nothing):

Chrome:

Closed in PR #1260


Handle webpack 3 minified umd

Hi there! Back again with another minified umd detection PR, this time handling webpack 3's output for the highcharts-react-official library.
Luckily, it looks like the only material difference in output between 3 and 4 is the statement order, so all that was needed to fix the test was to handle both positions.
Btw, when did the playground start adding ?dev to all imports? Is there a way to override this for repro'ing prod issues? When I first tried to repro this I was surprised to see it working in the playground. Turns out it only works because of the dev flag (presumably because the dev version uses one of the non-minified builds?).

Btw, when did the playground start adding ?dev to all imports? Is there a way to override this for repro'ing prod issues? When I first tried to repro this I was surprised to see it working in the playground. Turns out it only works because of the dev flag (presumably because the dev version uses one of the non-minified builds?).

you're right, it's unnecessary to add ?dev flag, going to get rid of it.


"ERROR: Path does not exist" when using trailing \ on manifest path (submit)

Brief description of your issue
When using "wingetcreate submit "PATH_TO_MANIFEST" and PATH_TO_MANIFEST have a trailing \, it will fail with:
"ERROR: Path does not exist".
Steps to reproduce
wingetcreate submit ".\manifests\x\XX\XXX\VERSION.NUMBERS\"
fails while
wingetcreate submit ".\manifests\x\XX\XXX\VERSION.NUMBERS"
does not fail
Expected behavior
A trailing \ should be allowed, and not cause a path error.
Actual behavior
"ERROR: Path does not exist"
Environment
Windows Package Manager Manifest Creator v<IP_ADDRESS>

Windows Package Manager (Preview) v1.7.3172-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.23606.1000
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.3172.0

Winget Directories
----------------------------------------------------------------------------------------------------- Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bb… User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bb… Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

This appears to be an issue in Command Prompt (cmd) and not PowerShell. Doing some google searches it seems that cmd uses the Microsoft C Runtime behavior for parsing command-line arguments that is treats the final backslash as an escape character

A double quote mark preceded by a backslash (") is interpreted as a literal double quote mark (").

You would need to escape the final backslash to treat it as part of the path, or not use double quotes at all if possible. I'm not sure what winget-create could do to offer a better experience here...
In CMD, the following examples work
Escape final backslash
wingetcreate submit ".\manifests\x\xx\xxx\version\\"

Don't use quotes
wingetcreate submit .\manifests\x\xx\xxx\version\

Forward slashes
wingetcreate submit ./manifests/x/xx/xxx/version/

Forward slashes with quotes
wingetcreate submit "./manifests/x/xx/xxx/version/"

This doesn't work in CMD
Quoted backslash
wingetcreate submit ".\manifests\x\xx\xxx\version\"

All of the examples work in PowerShell tho.

References:

https://stackoverflow.com/questions/73771339/trailing-backslash-in-c-sharp-command-line-parameter-bug-or-feature
https://stackoverflow.com/questions/43359103/why-does-c-sharp-appear-to-partially-un-escape-command-line-arguments
https://stackoverflow.com/questions/71283820/directory-parameter-on-windows-has-trailing-backslash-replaced-with-double-quote
https://github.com/rust-lang/rust/issues/72653

They don't work in PowerShell.

You might want to check if that is a valid path :eyes::


'nfc' is not defined

I am getting 'ReferenceError: nfc is not defined" following the exact example code.
This is really weird as I am sure "nfc" is a global object. Does anyone have any idea why this is happening?
*Running on Android

In case anyone is here for facing this same issue I faced:
Ensure cordova-plugin-whitelist is installed and (for simplicity sake. please edit it to fit your use case) the following statement be in your index.html
<meta http-equiv="Content-Security-Policy" content="default-src 'self' data: gap: https://ssl.gstatic.com 'unsafe-eval'; style-src 'self' 'unsafe-inline'; media-src *">


Great way to track progress!

Either I have overlooked this or this was recently introduced. I have been using some unofficial site for tracking that is confusing at least to start. This computes with my mind.
Thanks!
P.S. I wish every application had feedback and tracking.

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

ID: fa80910a-e655-34df-d26a-b094dd8702bb
Version Independent ID: 83b90d10-f455-fee5-cf94-2698f1ac33d6
Content: Flight Hub
Content Source: wip/flight-hub/index.md
Service: wip
GitHub Login: @dawn.wood
Microsoft Alias: dawn.wood

Hi @k3tonan Thank you for the feedback! We're glad this page is helpful.
Best,
Dawn


[Hub Generated] Review request for Microsoft.Insights to add version stable/2021-05-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

The python SDK breaking change gated check has been failing for months in this folder, there is another team looking into it. This change should not have affected it.
I was trying to keep this to 2 commits but it looks like the OneAPI Hub automatically generates a few commits when setting up a new branch. You'll want to review the 5th commit as that is the one where the new API is introduced and new changes are made. The 6th commit was to fix an example violation after I incorporated feedback from the linter to change some property casing but forgot to update the casing in the example.

        },

I assume metricDefinitions is not modeled as an Azure resource since it does not comply with Azure resource schema. (e.g. type is missing. name should be a string not an object). Is this correct?

Refers to: specification/monitor/resource-manager/Microsoft.Insights/stable/2021-05-01/examples/GetMultiResourceMetricDefinitions.json:19 in 8f6fd9a. [](commit_id = 8f6fd9a792cd682a5bc7428a2ac45ffb15599fbc, deletion_comment = False)

Hi @ruowan can I get your help merging this PR? The python breaking changes test is currently broken in this directory. These changes have not affected the that test.


Implement core library

Math Functions
Tree Functions
Network
IO
Data (JSON, XML, S-Expressions)
...

Agreed! Let me get a little further on CLR interop and we should be able to define a good chunk of those as shortcuts to .NET standard libraries.

Moved to this discussion thread:
Discussion about Core libraries


chore: bdd-nh-1575391693 to 0.0.1

chore: Promote bdd-nh-1575391693 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


circular-buffer: Implemented new exercise

I implemented the x-common/circular-buffer exercise. README.md

tmo$ python3.5 ./test/check-exercises.py circular-buffer
..........
----------------------------------------------------------------------
Ran 10 tests in 0.002s

OK

tmo$ cp circular-buffer/example.py circular-buffer/circular_buffer.py
tmo$ python3.5 circular-buffer/circular_buffer_test.py
EEEEEE.EEE
======================================================================
ERROR: test_alternate_read_and_overwrite (__main__.CircularBufferTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "circular-buffer/circular_buffer_test.py", line 88, in test_alternate_read_and_overwrite
    buf.write(c)
  File "/Users/tmo/github/xpython/circular-buffer/circular_buffer.py", line 22, in write
    self.buffer[self.write_point] = data
TypeError: an integer is required

I perfectly understand the TypeError. What I don't understand is why there is no error when I run the check-exercises.py script with python3.5. At least travis-ci caught it.

I'd suggest adding a test to check for failure if the input is greater than a single byte, but it looks like other tracks may not have that test either.
Overall I think it looks fine.


adding abdelaziz321.github.io blog

Thanks for the PR! We've simplified the process of adding your site/repo to the list. Instead of updating SITES.md you would add the utterances topic to your repo.


fix fullstack build bug when --release

rust 1.82.0 doesn't allow custom profile when release build
Below command always cause panic from cargo due to using profile with release

dx build -p platform --release

Can I confirm this is fixed.  I stll get the issue (or a similar issue??).
Using the "current" git repo dioxus-cli (as at 27-Oct 10:30 GMT) I get the following issue when attempting a release build:
Installed package `dioxus-cli v0.6.0-alpha.3 (https://github.com/DioxusLabs/dioxus.git#6c69c290)` (executable `dx`)

$ dx build --release
error: the argument '--profile <PROFILE-NAME>' cannot be used with '--release'

Usage: cargo rustc --message-format <FMT> --profile <PROFILE-NAME> --target [<TRIPLE>] --quiet --bin [<NAME>] [ARGS]...

For more information, try '--help'.
Error: 🚫 Building project failed:

Caused by:
    Build did not return an executable

$ rustc --version
rustc 1.84.0-nightly (798fb83f7 2024-10-16)

We merged a big PR that was started before this one was merged so it could've been overwritten. I'll look into this today.


Replace Quarkus dependency checksum with Quarkus dependencies as goal input

Context
Quarkus dynamically adds some dependencies to the build, which are listed in the target/quarkus-prod-dependencies.txt file.
This file contains one dependency per line and the fingerprint of the dependency for SNAPSHOT versions.
This file is then used as extra goal input for the Quarkus build goal and the surefire and failsafe test goals.
Issue
The fingerprinting logic is part of the Quarkus plugin.
This is something that would be naturally handled by the Develocity extension if the Quarkus plugin would only expose the list of files to fingerprint.
In addition, some optimizations could happen when computing the fingerprinting of a file already processed.
Eventually, delegating the fingerprinting to the Develocity Maven extension opens the door to normalization options.
Fix
Read the Quarkus extra dependencies exposed by the Quarkus Maven plugin and add them as file inputs with RUNTIME_CLASSPATH normalization strategy.
Dependency
Modify the Quarkus Maven plugin implementation to create a target/quarkus-prod-dependencies.txt file containing absolute path to each of the dependencies, instead of the current target/quarkus-prod-dependency-checksums.txt

@aloubyansky @gsmet this change would allow to remove the fingerprinting logic from the Quarkus Maven plugin
wdyt?

We could do that. You could probably try prototyping it by simply ignoring the checksum values present in the current file, until we implement this on the Quarkus side.

We could do that. You could probably try prototyping it by simply ignoring the checksum values present in the current file, until we implement this on the Quarkus side.

I actually need absolute paths, I don't want to magically rebuild the path to the Maven repository as custom configuration could lead to surprises.
If you agree with the approach, I could keep old and new implementation. This means both files would be processed as goal inputs, although only one of them would be present depending on the Quarkus version.

I pushed a new version @aloubyansky to support both quarkus-prod-dependencies.txt and quarkus-prod-dependency-checksums.txt.
Please let me know if you are ok with the changes (here and in the Quarkus Maven plugin)


Unable to open PR editor: Cannot read properties of undefined (reading 'toLowerCase'

Version: 1.95.0-insider
Commit: fe997185b5e6db94693ed6ef5456cfa4e8211edf
Date: 2024-10-23T05:06:13.568Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 5.15.0-124-generic
GHPR extension: v0.99.2024102304 (pre-release)

open branch 'digitarald/primary-meerkat` in the copilot repo
click on the 'Pull Request #9261'. Editor starts opening, but no content. Error nortification: 'Cannot read properties of undefined (reading 'toLowerCase''
I don't find any stack traces in the dev tools or logs

Reproduces on both Linux and Windows

Thank you for sharing the repo+branch!

Tried this on a few different prs from various repos.

Fix was not yet released, and that specific PR should be tested as there is something different about it.

When I check out PR #9261 by number, I get a notification saying "The remote branch for this pull request has been deleted. The file contents may not match the remote."
Is this enough for verification, or do we have to find or create another PR to test?

That's enough to verify, thank you!


[ZL-796] - Support Rest API migration

Ticket: ZL-796
Description
This PR changes how the JS-SDK handles API versions, to support easy migration from the legacy API Vapid to the new versioned API Rest. Read more about the Rest versioned API in our: Confluence pages.
An optional version can now be passed from the library client-side or default rest/v1.0 will be applied.
The API version can be specified at the time of the request.

Example
Requested URL

procore.get({base: '/me'})
https://app.procore.com/rest/v1.0/me

procore.get({base: '/me', version: 'v1.1'})
https://app.procore.com/rest/v1.1/me

procore.get({base: '/me', version: 'vapid'})
https://app.procore.com/vapid/me

LGTM

@njbbaer @gilmcquillan updated to send the sdk version in the headers. Let me know what you think about the naming.

@bross I've got a compilation error after yarn & yarn test
TSError: ⨯ Unable to compile TypeScript:
test/authorize.spec.ts:2:27 - error TS2307: Cannot find module '../dist/index' or its corresponding type declarations.

2 import { authorize } from '../dist/index'
                            ~~~~~~~~~~~~~~~

@bross I've got a compilation error after yarn & yarn test
TSError: ⨯ Unable to compile TypeScript:
test/authorize.spec.ts:2:27 - error TS2307: Cannot find module '../dist/index' or its corresponding type declarations.

2 import { authorize } from '../dist/index'
                            ~~~~~~~~~~~~~~~

js-sdk % node --version
v10.22.1
js-sdk % npm --version
6.14.6

Thanks for pointing this out @Varomir
After some investigation, this appears to be a side effect of importing package.json to get the SDK version. We have two options here: we can either modify the tests to reference the new location dist/lib/* or create a new file that stores the SDK version and read from that. Will discuss in standup.


Salesforce Default Values

Hello Again,
We're running into issues when sending objects up to salesforce that do not have all values set. Is there a way to send up default values for fields that are not being set? If not, this would make a great addition to the gem. Is there something we're missing? It looks like null values are being sent up, which causes some problems with fields such as OwnerId and RecordType.
Thanks,
Derek Brown

http://filesmelt.com/dl/databasedotcom_debug_log.txt

Examining the debug output, it looks like you are doing the following:

password auth succeeds
materialize many classes
Contact.find("003S000000RFENR") -> returns the object, but Id is 003S000000RFENRIA5, not 003S000000RFENR
Contact.delete("003S000000RFENRIA5")
Contact.find_or_create_by_Title("databasedotcom32")

The find_by_Title part of the last steps fails, so it then attempts to create a new record, but the only attribute it has to create with is Title, so it fails.
Does this sound plausible?

Here's the code which is causing that debug output:
sfdc_auth_config = YAML.load_file("#{::Rails.root.to_s}/some_directory/some_file.yml")
sf_client = Databasedotcom::Client.new("some_directory/some_other_file.yml")
sf_client.debugging = true
sf_client.authenticate :username => sfdc_auth_config['username'], :password => sfdc_auth_config['password']
sf_client.sobject_module = Databasedotcom
sf_client.materialize "Contact"
sf_client.materialize "Lead"
sf_client.materialize "AgendaSetParticipate__c"
sf_client.materialize "Forward__c"
sf_client.materialize "LibraryEntry__c"
sf_client.materialize "MonthlyPageVisit__c"
sf_client.materialize "MostRelatedPublication__c"
sf_client.materialize "PublicationComment__c"
sf_client.materialize "PublicationContact__c"
sf_client.materialize "PublicationUserApproval__c"
sf_client.materialize "Publication__c"
sf_client.materialize "RelatedPublication__c"
sf_client.materialize "RelevantSolutionSetLink__c"
sf_client.materialize "UserRole"
sf_client.materialize "SelectedSolutionSet__c"
sf_client.materialize "SolutionSetStep__c"
sf_client.materialize "SolutionSetStepPublication__c"
sf_client.materialize "Website__c"
sf_client.materialize "Unlock__c"
sf_contact_existing = Databasedotcom::Contact.find( "003S000000RFENR" )
sf_contact_existing.LastName = "dotcom1337"
sf_contact_existing.save
sf_contact_new = Databasedotcom::Contact.find_or_initialize_by_Title( "databasedotcom32" )
sf_contact_new.AccountId = "001S000000SzsZY"
sf_contact_new.LastName = "dbdc_test_user32"
sf_contact_new.save
The problem is that when we initialize a new object that has an OwnerId field, we believe that it should be set to the id of the user we authenticated with ( if it has not been set before saving ).
Thank you for your help with this issue. We've gone ahead and implemented a temporary fix, but we would like to know if our assumptions about the behavior of this gem are wrong.

A couple of things are at play here.
First, the API does have the concept of "default field values", and, in fact, the gem sets the defaults (as declared in the return from Client.sobject_describe) when you new up an Sobject (e.g., account = Account.new).  The gem internally news up a object when you do a find_or_initialize_by_xxx if the object isn't found, so, in this case, the defaults are being set in the object, but the Contact class declares no default for the OwnerId field (actually, it declares nil as the default value).  So I believe that the gem is operating correctly.
Second, the gem doesn't assume anything about object ownership, nor does it have any concept of "OwnerId" (or any other field name) being "special".  You need to fully specify objects before saving them.
To summarize, the defaults as declared by the API are being applied, and the gem assumes no defaults beyond those declared by the API.

Thanks for getting back to us so fast. That implementation makes sense, we'll just have to watch out for these ownership cases when implementing new integration solutions.


Add logging extensions

Example: multitenant-saas-guidance/src/Tailspin.Surveys.Web/Logging at master · mspnp/multitenant-saas-guidance · GitHub

Logging can be added based on the needs of each application.

Fixed link: https://github.com/anirbansdutta/Tailspin.Surveys/tree/master/src/Tailspin.Surveys.Web/Logging


Data type on phenotype

Dear professor
Recently, I want to use this package for investigate fitness landscape. But I have puzzle on how to present suitbale data for phenotype.
If I use enzymetical activity as phenotype data, I directly use their activity vaule to express its phenotype data. However, If the  phenotype data is enantioselectivity (ee) that two types of data, namely, R or S, I want to know what type of data expression  is suitful for using this package.  I hope some suggestions I would obtain. Thank you very much.

The package should take any quantitative value as the phenotype. If I understand correctly, you do R or S, or R/S (as a measure of selectivity). It depends on the question you hope to ask. Does that help?
Mike

On May 23, 2022, at 11:48 PM, Shinezhuxin @.***> wrote:
Dear professor
Recently, I want to use this package for investigate fitness landscape. But I have puzzle on how to present suitbale data for phenotype.
If I use enzymetical activity as phenotype data, I directly use their activity vaule to express its phenotype data. However, If the phenotype data is enantioselectivity (ee) that two types of data, namely, R or S, I want to know what type of data expression is suitful for using this package. I hope some suggestions I would obtain. Thank you very much.
—
Reply to this email directly, view it on GitHub https://github.com/harmslab/epistasis/issues/53, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABFZA6UACKHUAOC7B6CKAH3VLR3T7ANCNFSM5WYM3YFA.
You are receiving this because you are subscribed to this thread.


Reject bids before x minutes

I've noticed a huge increase in the number of bids coming in for posts created immediately before the end of a bidding window to abuse curation rewards.  The users doing this are typically using spammy posts.  In HF20 the first 15 minutes will go back to the reward pool and will be another factor to deal with.
I propose having a setting to reject bids before x minutes.  I say we have a min age as well.

Just added "min_post_age" setting in latest commit here: https://github.com/MattyIce/postpromoter/commit/fadf17a109e2ef9223decf27a8fe3bd2245677a3

This doesn't seem to be working.
I get this whenever someone submits an early bid:

@themarkymark-steem Please make sure you added the transfer memo for min post age refund to config.json:
"min_age": "Refund for invalid bid: {amount} - Posts cannot be less than {min_age} minutes old.",


[3.1] [Serialization] Handle box types with layouts with non-parameter requirements

The handling of SIL box types in both deserialization and in the SIL
parser assumed that the number of substitutions in the box type would
be equivalent to the number of generic parameters. This assumption is
incorrect when the generic signature adds requirements to an
associated type.
Fixes rdar://problem/29740594.

@jckarter , please review!

@swift-ci please test

Looks good, thanks for fixing this!


Z norm

I'm currently confused where the Z norm is being calculated. I'm trying to replicate your method with my data, but I'm not sure how to make the Z norm. For example:
Given a matrix emb of size (5, 60), where we have 5 sentences, each being one row, and 60 dimensions, where the first 20 are from p-mean with p = 1, the ones emb[:, 20:40] with p = -inf and the rest being p = +inf.
Where in this scenario/matrix, would I calculate the z norm?

I have tested doing the z norm along the dim=1 and dim=0, and I got much better results from dim=1.

This is the code we used:
m = np.mean(train_embeddings, axis=0)
s = np.std(train_embeddings, axis=0)
train_embeddings = (train_embeddings - m) / s
train_embeddings = train_embeddings / np.reshape(np.linalg.norm(train_embeddings, axis=1, ord=2), (train_embeddings.shape[0], 1))
test_embeddings = (test_embeddings - m) / s
test_embeddings = test_embeddings / np.reshape(np.linalg.norm(test_embeddings, axis=1, ord=2), (test_embeddings.shape[0], 1))

(Can be inserted here: https://github.com/facebookresearch/SentEval/blob/master/senteval/trec.py#L75)

Thanks for your attention, @arueckle !


[bugfix] Enable synthetic default imports in TypeScript config

Added allowSyntheticDefaultImports to TypeScript configuration for better compatibility with CommonJS modules. This helps to simplify imports and improves integration with various libraries.

[x] I have followed (at least) the PR section of the contributing guide.

@Janpot I’ve partially tested a solution to comply with a GitHub build checks. However, I haven’t found any information on how to run the expected checks. I tried it locally on CircleCI but the credentials don’t permit some actions. Can we run the remaining checks or is the PR now waiting due to some external reason?

@Janpot It seems that the markdown hasn't been deployed to the website https://mui.com/material-ui/guides/typescript/. The documentation link points to a corrected version yet the production still shows an outdated default tsconfig.json value. Could we re-run circleci or simply update production as the current situation is somewhat confusing?

to avoid having documentation online for unreleased features, we only deploy the docs when we publish a new release.