Could not locate source_path

Description
Terraform plan failed due to Could not locate source_path regarding to use  "${path.module}/sourcecode"
⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Terraform:
Terraform v0.14.3

provider registry.terraform.io/hashicorp/archive v2.2.0
provider registry.terraform.io/hashicorp/aws v3.62.0
provider registry.terraform.io/hashicorp/external v2.1.0
provider registry.terraform.io/hashicorp/local v2.1.0
provider registry.terraform.io/hashicorp/null v3.1.0
provider registry.terraform.io/hashicorp/random v3.1.0

Provider(s):
provider registry.terraform.io/hashicorp/aws v3.62.0
Module:
Downloading terraform-aws-modules/lambda/aws 2.20.0 for lambda_function...
lambda_function in .terraform/modules/lambda_function
Downloading terraform-aws-modules/lambda/aws 2.20.0 for lambda_layer_local...
lambda_layer_local in .terraform/modules/lambda_layer_local
Downloading terraform-aws-modules/cloudwatch/aws 2.1.0 for log_metric_filter...
log_metric_filter in .terraform/modules/log_metric_filter/modules/log-metric-filter
Downloading terraform-aws-modules/lambda/aws 2.20.0 for package_dir...

Reproduction

Steps to reproduce the behavior:

No

Yes

Code Snippet to Reproduce
terragrunt plan
Expected behavior
I expected to success plan output
Actual behavior
[terragrunt] 2021/10/19 22:25:07 Running command: terraform plan -lock-timeout=20m -parallelism=40
Acquiring state lock. This may take a few moments...
module.package_file_with_pip_requirements.null_resource.archive[0]: Refreshing state... [id=2827457759683703423]
random_pet.this: Refreshing state... [id=able-jackal]
module.package_file_with_pip_requirements.local_file.archive_plan[0]: Refreshing state... [id=4b0210d0d55788bc1bb4bdbd3ece4947e01b3932]
module.package_dir.local_file.archive_plan[0]: Refreshing state... [id=659c26b6176a1e6731e90d5af8f76bb742e9f0ea]
module.package_dir.null_resource.archive[0]: Refreshing state... [id=3477677468785454566]
aws_cloudwatch_event_rule.trigger_lambda_function: Refreshing state... [id=funcChromeFeed-rule]
module.lambda_function.aws_cloudwatch_log_group.lambda[0]: Refreshing state... [id=/aws/lambda/funcChromeFeed-test]
module.lambda_function.aws_iam_role.lambda[0]: Refreshing state... [id=funcChromeFeed-test]
module.log_metric_filter.aws_cloudwatch_log_metric_filter.this[0]: Refreshing state... [id=error-metric-/aws/lambda/funcChromeFeed-test]
module.lambda_function.aws_iam_policy.logs[0]: Refreshing state... [id=arn:aws:iam::681105386544:policy/funcChromeFeed-test-logs]
module.lambda_function.aws_iam_role_policy_attachment.logs[0]: Refreshing state... [id=funcChromeFeed-test-20211012202019408900000001]
Error: failed to execute "python3": Could not locate source_path "/Users/emregundogdu/Desktop/onedio/scripts/reporting_scripts/code/seo_Chrome_Feed/builds/b41fcb4f1bc02b69b8acd0661bf2f4c7890d25b76a01a73ad75ee9d91fe1c372.zip".  Paths are relative to directory where terraform plan is being run ("/Users/emregundogdu/Desktop/onedio/scripts/reporting_scripts/code/seo_Chrome_Feed")
Terminal Output Screenshot(s)

Yeah I just tried lots of different alternative that why are you see the artifact dir on there,  So you mean if have to use  source_path  in jsonencode() , I  would try to use source_path = jsonencode("${path.module}/sourcecode"), is it right? If it  is not right ,  could you share complete line of the  source_path  in jsonencode()

@antonbabenko  I have got similar error over again once I update source_path as following module call,
module "package_dir" {
  source  = "terraform-aws-modules/lambda/aws"
  version = "2.20.0"
  create_function = false
  source_path = jsonencode("${path.module}/sourcecode")
  runtime     = "python3.8"
}

terragrunt plan
Error: failed to execute "python3": Could not locate source_path ""./sourcecode"".  Paths are relative to directory where `terraform plan` is being run ("/Users/emregundogdu/Desktop/onedio/scripts/reporting_scripts/code/seo_Chrome_Feed")

Folder tree
.
├── backend.tf
├── build
│   └── funcChromeFeed-dev-hello-test.zip
├── main.tf
├── output.tf
├── sourcecode
│   ├── client_secrets.p12
│   ├── constants.pickle
│   ├── ga_get_data.py
│   ├── handler.py
│   ├── requirements.txt
│   ├── seo_google_chrome_feed.py
│   └── slackbot_functions.py
├── terragrunt.hcl
├── variables.tf
└── version.tf

I am a bit lost in the way you use terragrunt and terraform together. Why do you have module block and terragrunt.hcl?
Here is my complete terragrunt.hcl and I don't have any tf-files near it:
terraform {
  source = "tfr:///terraform-aws-modules/lambda/aws?version=2.20.0"
}

include {
  path = find_in_parent_folders()
}

inputs = {
  function_name = "function1"
  handler       = "webhook_handler.webhook_handler"
  runtime       = "python3.8"
  timeout       = 30
  memory_size   = 512

  publish = true

  // terragrunt bug: use jsonencode when "type = any"
  source_path = jsonencode("${abspath("${get_terragrunt_dir()}/../../backend")}/function1")

  artifacts_dir = abspath("${get_terragrunt_dir()}/../builds")
}

Try putting fixed string value into source_path into your code to avoid using variables and HCL/terragrunt functions to begin with.

I didn't understand enough could you refactor source_path = jsonencode("${abspath("${get_terragrunt_dir()}/../../backend")}/function1")  as my directory tree onces for me ?
My Directory Tree
.
├── backend.tf
├── build
│   └── funcChromeFeed-dev-hello-test.zip
├── main.tf
├── output.tf
├── sourcecode
│   ├── client_secrets.p12
│   ├── constants.pickle
│   ├── ga_get_data.py
│   ├── handler.py
│   ├── requirements.txt
│   ├── seo_google_chrome_feed.py
│   └── slackbot_functions.py
├── terragrunt.hcl
├── variables.tf
└── version.tf


Add ProvisioningStyle: Automatic; to framework target

Provisioning style 'Automatic' is the most consumer friendly provisioning style for frameworks. It permits the host project to dictate the provisioning style.
Otherwise if a host project specifies Manual provisioning style, xcodebuild will fail when attempting to compile the subproject with:

Diff does not support provisioning profiles. Diff does not support provisioning profiles, but provisioning profile  has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor.

Looks good to me, will wait for Travis to pass and :shipit:

TRAAAAAAAAAAVIIIIIIIIIIIIS
🙇

Current coverage is 93.26% (diff: 100%)

No coverage report found for master at 5968ff7.

Powered by Codecov. Last update 5968ff7...5f96df6

@raven Thanks!

@tonyarnold thanks for reviewing!


Give up the use of fixed gpio numbers

insead of using dynamic gpio numbers according to the probe sequence
Signed-off-by: Chao Zeng<EMAIL_ADDRESS>

these changes are for upstream kernel.
should be used when migrating to the upstream kernel.

these changes are for upstream kernel.
should be used when migrating to the upstream kernel.

But they do not break the 4.19-ti kernel, do they?

This means that it cannot be used with the current ti kernel. To be used with the upstream kernel

Because wkup_gpio0_base does not match the DT used there? Maybe you can add the corresponding patch for the TI kernel as well and probe for what is available? Then we can easily allow switching kernels without patching userland.

I think just like MRAA, there should be some modifications for the switchserial on the userland instead of patching for the ti kernel.

I'm not suggesting to patch the kernel. I'm suggesting to account for any potential differences between upstream DT and TI DT in the switch-serial tool to make it work on both.

Should we use the "gpiolib" interface introduced since v4.8 kernel?

If it simplifies the code, let's do that. But speed is surely not a driver here.

Should we use the "gpiolib" interface introduced since v4.8 kernel?

As suggested here: #40 , I can only say +1 on that.. 👍

This became obsolete via #95.


feat: force bridge lockscript

It should point out installing jq and exec cd eth-contracts && yarn install && cd .. before make integration-ci


sh: 0: unknown operand

Hi! first of all, thanks for this awesome image!
I have been using it for a while and noticed this "unknown operand" warning when running on non daemon mode.. Until now, I have not seen any problems, but I could not figure how to resolve it..
Any thoughts on  this? Thanks in advance.
nginx_1     | start nginx
nginx_1     | ssl_key=le-key.pem, ssl_cert=le-crt.pem, ssl_chain_cert=le-chain-crt.pem
nginx_1     | sh: 0: unknown operand
nginx_1     | '/etc/nginx/conf.d' -> '/etc/nginx/conf.d.disabled'

Thanks for the report! Would you be so kind as to clarify what is a non-daemon mode? Also, is it just an error you see in the log, or the container doesn't start at all?

Hey, thanks for your response! the container starts and works as expected, but this error shows always I do start the docker image.. Regarding the non daemon mode, it is about the docker-compose up command but without the -d flag.. Also, I use multiple domains on the environment config. Everything works fine, I am just curious about it

I'll test it when I'll have time. To clarify, as something non-blocking this is a low priority for me.
I recall what I've fixed some of the problems in this image shell script, but it seems that something is still in place. It would be helpful if you would post your configuration to Pastebin so if it's not reproducible on mine, I would be able to track the difference between mine and yours.

@marciks pls make sure you have the latest stable version. I kind of recall the issue (or similar one) back in days and it had smth to do with the legacy base image.

Can not reproduce:
nginx             | start nginx
nginx             | ssl_key=le-key.pem, ssl_cert=le-crt.pem, ssl_chain_cert=le-chain-crt.pem
nginx             | '/etc/nginx/service1.conf' -> '/etc/nginx/conf.d/service1.conf'
nginx             | '/etc/nginx/service2.conf' -> '/etc/nginx/conf.d/service2.conf'
nginx             | '/etc/nginx/service3.conf' -> '/etc/nginx/conf.d/service3.conf'
nginx             | '/etc/nginx/conf.d' -> '/etc/nginx/conf.d.disabled'
nginx             | start letsencrypt updater
nginx             | trying to update letsencrypt ...
nginx             | letsencrypt certificate /etc/nginx/ssl/le-crt.pem still valid
nginx             | '/etc/nginx/conf.d.disabled' -> '/etc/nginx/conf.d'
nginx             | reload nginx with ssl
nginx             | 2020/02/13 20:50:27 [notice] 34#34: signal process started

Hey guys, I have tested again with latest configs and the warning did not appear .. the only diference I was able to notice was the # in if [ ${#SERVICES} -ne 0 ]; then it was missing in my early entrypoint file.. not sure if it was the problem, but now it fixed! thanks again


Updating the omsagent yaml file to include new changes for node zero dependency

This PR is to update the omsagent yaml file to include changes for node zero dependency changes.
Also updates the agent version to the latest one in production
Updates the cpu and memory requests and limits to use the same limits in production

This doesnt not include any new variable additions in the yaml file so there are no changes to the rest of the changes that Jack made to get Container Monitoring add on to work
/assign @jackfrancis

/assign @jackfrancis

/lgtm pending E2E

@jackfrancis : Thanks Jack!


Release version 1.0.0-alpha.1

Motivation
We need to push a release to test some small changes and fixes ahead of the community release

Totally cool with doing a release, although I'm not so sure about the version number. I would probably do 1.0.1-alpha but I don't know what the others would think about this considering we haven't done our overall community release yet. Going to post a question on the mailing list.

@darahayes This follows the prerelease spec in https://semver.org/#spec-item-9 and the precedence spec in https://semver.org/#spec-item-11. We follow the same approach for Android and iOS.


Add installation prompt

Not all browsers support installation prompt, but Sharp Cooking should implement the prompt in those that do:
https://web.dev/learn/pwa/installation-prompt/

in iOS we may leverage the standalone property to detect whether the app is installed or not:
https://web.dev/learn/pwa/enhancements/#detecting-a-pwa-on-apple-mobile-platforms


Add fine-grained access control for elastic search

This gets rid of AWS IAM signed requests and instead forces basic authentication over HTTPS. Other required side-effects:

Encryption at rest
Node to node encryption
Forced HTTPS
Deploy Elasticsearch domain in the product VPC

This requires changes to dc-deployments-automation raised here: https://bitbucket.org/atlassian/dc-deployments-automation/pull-requests/132/dcd-1157-add-properties-for-elasticsearch

This is an early-stage PR to get some feedback on whether this has been done correctly.

This is now ready for full review

Bingpot!

The new parameter needs to be included and propagated from the quickstart-atlassian-bitbucket-with-vpc.yaml template as well.

Note updating the stack to use secure elasticsearch will require replacement of the elasticsearch cluster and updates to bitbucket.properties. The ansible repository will not overwrite bitbucket.properties if it already exists so admins need to delete the file and reprovision their cluster or manually update bitbucket.properties with credentials for elasticsearch and restart all nodes.

Note updating the stack to use secure elasticsearch will require replacement of the elasticsearch cluster and updates to bitbucket.properties. The ansible repository will not overwrite bitbucket.properties if it already exists so admins need to delete the file and reprovision their cluster or manually update bitbucket.properties with credentials for elasticsearch and restart all nodes.

ElasticsearchPassword is now a required parameter, isn't it? So if they have let's say a bitbucket-with-vpc deployment and they just change a cluster node number, it will actually complain that they haven't provided elasticsearch password (as it doesn't exist in the master template (cached in S3) but it is required in the nested one (fetched live from s3)).
I think we need to make clear what this change means for existing customers and document any necessary steps, if this is a breaking change.

I tested updating a stack and replacing the current master branch template (direct deployment from the AWS marketplace) with the template from this branch and the instance is still working. Here are the steps required:

Update the stack with the new template. You'll need to set the elasticsearch password. Set maximum and minimum nodes to 0 as well while you're here.
Delete the ansible repo pinned SHA in systems manager parameter store (this requires changes in the ansible repo so to update with the latest master.
Use session manager to connect to the NFS node.
a. Delete bitbucket.properties in the shared home OR
b. Manually set plugin.search.elasticsearch.baseurl plugin.search.elasticsearch.username and plugin.search.elasticsearch.password
Once the update stack from step 1 is complete, you can scale up the Bitbucket cluster again
Make sure search is still working by testing the connection in the Server Settings page and by doing a code search

Note updating the stack to use secure elasticsearch will require replacement of the elasticsearch cluster and updates to bitbucket.properties. The ansible repository will not overwrite bitbucket.properties if it already exists so admins need to delete the file and reprovision their cluster or manually update bitbucket.properties with credentials for elasticsearch and restart all nodes.

ElasticsearchPassword is now a required parameter, isn't it? So if they have let's say a bitbucket-with-vpc deployment and they just change a cluster node number, it will actually complain that they haven't provided elasticsearch password (as it doesn't exist in the master template (cached in S3) but it is required in the nested one (fetched live from s3)).
I think we need to make clear what this change means for existing customers and document any necessary steps, if this is a breaking change.

An alternative option would be to have a condition based on whether the value is present or not. If the value is present, use Elasticsearch and etc/atl config as in this PR now, otherwise:

Use old elasticsearch configuration (we can probably still do the VPC deployment, it's more secure)
Don't set elasticsearch credentials in etc/atl, set the elasticsearch region

I've updated the PR and now the fine-grained access control is optional. If no password is supplied, the old elasticsearch config will be used. This is only for backwards compatibility. It's much better if you pass a password.

With some ansible fixes, IAM authentication still works

After replacing the nested bitbucket stack template with this version, we can see the elasticsearch resource was not updated, Bitbucket remains available and search is still working:

Going to wait until I can get the build to pass before merging which depends on updating submodule.


[FLINK-20054][formats] Fix ParquetInputFormat 3 level List handling

What is the purpose of the change
Fix the 3 level List handling in ParquetInputFormat
Brief change log

Add the 3 level List schema conversion logic in ParquetSchemaConverter.
Update the ParquetRowInputFormatTest to generate 3 level List for end to end test.

Verifying this change
(Please pick either of the following options)
This change is already covered by existing tests, such as ParquetRowInputFormatTest.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

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

Thanks @HuangZhenQiu for the contribution, looks good to me overall, as it is now during the 1.12 test. I consider merging this PR later.

@JingsongLi
Thanks. No hurry.

@JingsongLi
Add the fix for 3 Level List conversion in the row converter. Use we need config AvroParquetWriter to use either 2
Level or 3 Level List for test parquet file generation. I changed tests for parquet input formats to parameterized test cases.


added support for 4d coordinates for Transformer.transform

Part 1 of #208

I am not sure if this will work outside of the from_pipeline, so it may be restricted to the Transformer class. But, I could be wrong.

@jswhit, I was thinking the location of the additional time keyword arguments would make this a 2.2.0 release as it could break for those not using kwargs in the functions. Thoughts?
Also, I made more changes. Mind reviewing again when you get a moment?

I don't think adding another kwarg qualifies as an API change.  Yes, it will break code that treats the kwargs as positional args, but I'm not too concerned about that.

Sounds good. I was back and forth on that, so this solidified that decision. :+1:

Assert almost equal goes to 7 decimals by default. So, definitely something problematic going on here.


Opt-in type checking of type safe type predicates

🔍 Search Terms
"predicate", "safe predicate", "narrowed", "infer predicate"
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
A new keyword to indicate the type checker should emit errors if the type predicate is not type safe.
(value: A): value is narrowed B => value.kind === 'B';

The type checker should emit errors if

If B is not assignable to the narrowed type of value everywhere the function returns true.
If Exclude<A, B> is not assignable to the narrowed type of value everywhere the function returns false.

I'm not sure what the keyword should be called but narrowed is the best I've come up with so far. If placed outside a type predicate node the token would be an identifier instead like it already is. Identifiers are not allowed following an is keyword so the scanner can tell them apart. The keyword would be represented as a boolean property of the type predicate node the same way assserts already is.
📃 Motivating Example
Type safe type predicates are already possible in >=4.9. This is the above proposed syntax translated to what I'd write in current TypeScript.
(value: A): value is B =>
  value.kind === 'B'
    ? (value satisfies B, true)
    : (value satisfies Exclude<A, B>, false);

The syntax is unfortunate to put it politely. A developer who has never seen a narrowing type predicate before may be confused. I also need to add more JavaScript to apply the type constraints.
Why not inline it? Inlining works but if I do the same type checks in multiple places I want to extract it to a function to avoid repetition. All type predicates must be annotated but unfortunately the annotation also makes it type unsafe and that can lead to regressions. Here's a contrived example.
type Media = SquareImage | TwoByThreeImage | SquareVideo;
type Image = SquareImage | TwoByThreeImage;

const isImage = (media: Media): media is Image => {
  switch (media.kind) {
    case '1x1_image':
    case '2x3_image':
      return true;
    default:
      return false;
  }
};

Now if we change the definitions of Media and Image there's no errors from TS if I forget to add the new switch case.
type Media = SquareImage | TwoByThreeImage  | PortraitImage | SquareVideo;
type Image = SquareImage | TwoByThreeImage | PortraitImage;

💻 Use Cases
The main use is for type predicates that are the result of extracting a type checking expression into a function. Not all type predicates should be type safe. There are valid uses of type-unsafe type predicates and that would remain the default. In my unscientific survey through my company's code about half of our type predicates are narrowing or could be.
Alternatives
Inferred type guards
There's been demand for inferred type guards for a long while now: #38390. If sufficiently complex type guards can be inferred, the narrowed keyword would not be needed as we could write something like the following.
const predicate = ((value: A) => value.kind === 'B') satisfies (value: A) => value is B;

External tools
I've already written a lint rule to make maintaining narrowing type predicates easier. I intend to extend it with a pair of codemods which would allow me to use the following syntax.
(value: A): value is /* narrowed */ B => value.kind === 'B';

I could then

Codemod transform functions with the comment directive to narrowing type predicates
Run type check
Codemod to revert

That's a hacky approach and ultimately impossible to integrate into a code editor so I'd only get type errors in CI at best.
If I could write the feature directly as a language feature I'd save myself that trouble and get a better end result, too. I'm interested in contributing but if the proposal is denied I'll write my codemods instead.

In general type predicates are written for code that the compiler can't figure out itself, so I'm not sure how feasible this suggestion even is.
For your example you could improve the code by listing every possible case in the switch (with the respective return values), and call an assertion function accepting a never argument in your default block. This way the developer is forced to explicitly acknowledge the newly added case, otherwise the value is not narrowed to never and the assertion function can't be called.

For your example you could improve the code by listing every possible case in the switch (with the respective return values), and call an assertion function accepting a never argument in your default block.

That's what we used to do before 4.9.
const isImage = (media: Media): media is Image => {
  switch (media.kind) {
    case '1x1_image':
    case '2x3_image':
    case '2x1_image':
      return true;
    case '1x1_video':
      return false;
    default:
      assertNever(media);
  }
};

assertNever can be replaced with a media satisfies never expression. Either way now there's even more JavaScript required to apply the type constraint. This does help in this specific example but it's not type safe. I would write it as a narrowing type predicate in my own code:
const isImage = (media: Media): media is Image => {
  switch (media.kind) {
    case '1x1_image':
    case '2x3_image':
    case '2x1_image':
      return (media satisfies Image, true);
    default:
      return (media satisfies Exclude<Media, Image>, false);
  }
};

Writing this suggestion I thought type predicate inference might not ever become a language feature. However, the activity around #57465 implies that is the direction the language is headed and I expect there will be more robust inference to follow.
When a type predicate can be inferred it can also be type checked with a type constraint: satisfies (value: A) => value is B. This practically replaces the narrowing type predicate syntax for simple cases that can be inferred. For complex cases we still have the current narrowing type predicate syntax: (value satisfies B, true), (value satisfies Exclude<A, B>, false). It's still not pretty but as more type predicates are inferred it will be needed less.
Ultimately, in a state where type predicates are perfectly inferred, the narrowed keyword would be useless. I'm closing this issue because the design of this suggestion is partially in conflict with inferred type predicates and I think we are better off putting our efforts towards better type predicate inference going forward. The more type predicates can be inferred the less we need something like this.

Can this be revisited?
The proposed feature is already here in a form of:
const isNumber: (value: unknown) => value is number = (value) => typeof value === "string"
// Type '(value: unknown) => value is string' is not assignable to type '(value: unknown) => value is number'.
//   Type predicate 'value is string' is not assignable to 'value is number'.
//     Type 'string' is not assignable to type 'number'.

What's missing is a proper syntax for function declarations, so we don't have to jump through these hoops every time a checked type guard is needed.

Ultimately, in a state where type predicates are perfectly inferred, the narrowed keyword would be useless.

Since isolated declarations are a thing now, you can't always rely on inference - 3rd party tools will require annotations.


Fix documentation of Binding.used

ef4da24 changed the Binding.used tuple from (scope, line number)
to (scope, node).  This updates the docstring to reflect this change.

Looks good, thanks!


Extracting PathEffect information

Currently, once you assign a PathEffect to a paint via one of the SKPathEffect.Create*() methods, there's no way to later tell what type of path effect is applied to a paint, or to extract its information (e.g. for dash effects, I'd like to be able to fetch the interval data from the paint's path effect property).
I'm not sure if this functionality exists directly on the native Skia side. Certainly there are different subclasses for the different path effect types, so if nothing else the functionality exists via RTTI (though I don't know if native Skia is built with RTTI enabled). Perhaps the different subclasses could be exposed with managed subclasses, with the various fields exposed as well.
It's fine if you decide this issue is out-of-scope for SkiaSharp, just thought it was worth raising.

@tdenniston I had a look at this case, and I don't see a way to get this information from the shader/effect/filter. Right now, even the C++ API just returns the base type.
Until this information is actually on a public API, we will all have to suffer :)

@mattleibow Ok, thanks for looking into it!


debug lua error

node:internal/modules/cjs/loader:1080
throw err;
^
Error: Cannot find module 'C:\Users\happyelements\AppData\Roaming\Sublime Text\Packages\Debugger\data\lua-local\extension\extension\debugAdapter.js'
at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
at Module._load (node:internal/modules/cjs/loader:922:27)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:23:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
I have checked this path and there is no corresponding js file

Try reinstalling the adapter it should exist now


router.WithGroup question

💡 The feature or bug you are proposing
I have this code:
	router.WithGroup("/todo", func(group *bunrouter.Group) {
		group.GET("", mr.DebugHandler)
		group.GET("/:id", mr.DebugHandler)
		group.POST("/edit/:id", mr.DebugHandler)
	})

Which I think should be able to serve /todo/edit/9
📄 The description of the bug or the logic behind your proposal
My webserver shows me:
Page not found (/todo/edit/9) or method (GET) not allowed
🚀 The expected result
{"params":{"id":"9"},"route":"/todo/edit/:id"}

Am I doing something wrong here?

method (GET) not allowed

Your route uses POST, but here you have GET. Can it be the problem?

Hahahaha, see: I'm not fully awake but luckily you are.
It IS the problem, or rather: I was the problem.
Thanks for being that awake :-)


Unwanted scrollbar when running jupyter in chrome

Unwanted scrollbar when running jupyter in chrome. Firefox does not seem to have this issue.

Solution provided by chatGPT 3.5:
from IPython.display import HTML

# Define your LaTeX string
latex_string = r'\begin{bmatrix} 1 & 2 & 3 \\ 4 & 5 & 6 \\ 7 & 8 & 9 \end{bmatrix}'

# Define the CSS style to remove the scrollbar
css_style = """
<style>
.output {
    overflow: visible !important;
}
</style>
"""

# Display the matrix using LaTeX with the custom CSS style
HTML(css_style + '$$' + latex_string + '$$')

implementing it next.


Correction for raw affiliation Centre de Génie Industriel, IMT Mines Albi, Albi, France

Correction needed for raw affiliation Centre de Génie Industriel, IMT Mines Albi, Albi, France
raw_affiliation_name: Centre de Génie Industriel, IMT Mines Albi, Albi, France
new_rors: 00bq8vv83
previous_rors: 0455wwj08;00bq8vv83
works_examples: W4393908975;W4393733840;W4393750502
contact: 405a11e8a314059f9d7c988e040ab4c0:3eac1729ee2d15089800081d @ centralesupelec.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Statusbar: VoiceOver reads current item and entire line when receiving focus

Testing #97156

The activity bar's behavior is to only read the current item when the activity bar receives focus.
The activity bar's behavior seems preferable - although I'm not sure what the optimal behavior would be.

Ideally VoiceOver would only read the currently focused item in the status bar. However this is VoiceOver behavior and we can not really control this.
Wish there was a place where we could file issues against VoiceOver
@cookiecrook VoiceOver reads the content of the whole status element even though the focus changes from one of it's child elements to another.

To clarify: When moving focus between statusbar items, VoiceOver reads out only the newly focused item.
VoiceOver reads out the focused item AND the entire statusbar (as in the screenshot above) when moving focus to the statusbar with F6.

I actually think that behavior you are seeing is just fine. Previously I was seeing what I mentioned - though I can no longer repro that.
So I would probably just close this as designed.


Helm template, how to feed values

How does one supply helm-values to the helm-charts? If i understand the code here correctly it only renders the template with its default values.
https://github.com/SovereignCloudStack/cluster-stack-operator/blob/4c4f9061cd6b59887241a81631a115bdde12624b/internal/controller/clusterstackrelease_controller.go#L312

I have asked the experts to answer. However, your question is about how to write Helm charts. The operator does not allow any Helm values to be specified by the user.
So either you should re-phrase this question in how to build cluster stacks (and it should be in the cluster-stacks repo), or this is a question about the operator and then the answer would be that it is not possible to specify helm values as a user.

The operator does not allow any Helm values to be specified by the user.

Ok, what is the benefit to use helm over static manifests then?

yes, thank you very much for explaining.


Update README.md

Description
Added simple docker docker-compose file install & update instructions
Type of change

New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code and test it
[x] My changes generate no new warnings

As mentioned in #1037:

I split the wiki into GitHub repo, you can make a pull request their:
https://github.com/louislam/uptime-kuma-wiki


fixed sandbox/http/index.js to work properly when content-type has ch…

fixed sandbox/http/index.js to work properly when content-type has charset assignment
Thank you for helping out! ✨
Before submitting a pull request, please make sure the you checked the following:

[x] Forked the repository and created your branch from master
[x] Make sure the tests pass! npm it in the repository root
[ ] If you've fixed a bug or added code more tests are appreciated
[ ] If you're adding a new command, removing an old command, or changing how a command works, please update the relevant documentation for the command (under the doc/ folder)
[ ] Summarize your changes in the changelog
[x] If you haven't already please complete the CLA

Learn more about contributing: https://arc.codes/intro/community

It was caused by my Japanese account name.
Thanks for the tip.
Keep up the good work.

Sorry about the hassle, @hada-unlimited, and thank you!
I’d you can send repro steps to the CLA issue we saw, we will ask the JSF to fix their integration. Such barriers to contributing are decidedly uninclusive.

I'm not sure about repro. But here is what I experienced.

It was newly installed machine with fedora 2.9.
I forgot to git config --global user.email/user.name.
I already had active github.com account from other machine.

I cloned/fixed the code in the machine and commit/push and made pull request.

It was possible to sign CLA with my github account, but CLA check
couldn't find me because email address wasn't associated with the commit.

I followed the instruction github presented and git  config user.email and commit/push and
made second pull request.(didn't configure user.name because there was no mention in the instruction)

CLA check still couldn't find me. (at this point I asked you to copy the code and fix the glitch)

I looked at my repository and noticed that the commit user icon was my icon but name shown was my Japanese name and not github user name (hada-unlimited)

I git config user.name with github user name and commit/push and pull requested again.

CLA check was solved.

I guess the problem was

I didn't config git environment properly.(my bad)

github instruction never told me user.name was crucial too.(?)

*I guess it had nothing to do with my Japanese name.(It sure was noticeable )
I' m looking forward for this project to evolve.
Thank you for your work.


set global variable in application spec

my current applicationset example:
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: appName
  namespace: argocd
spec:
  generators:
  - matrix:
      generators:
      - list:
          elements:
          - cluster: dev
            url: https://kubernetes.default.svc
          - cluster: prod
            url: https://kubernetes.default.svc
      - git:
          repoURL: https://myUrl/gitops/appName.git
          revision: master
          directories:
          - path: overlays/{{cluster}}/*
  template:
    metadata:
      name: 'myProjectPrefix-{{path.basename}}-{{cluster}}'
    spec:
      project: default
      source:
        repoURL: https://myGitUrl/gitops/appName.git
        targetRevision: master
        path: '{{path}}'
      destination:
        server: '{{url}}'
        namespace: appName-{{cluster}}
      syncPolicy:
        automated:
          prune: true

Is there any way to set global variables on top and use those variables in template section. Desired format:
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: appName
  namespace: argocd
spec:
  generators:
  - vars:
     - gitUrl: 'https://myGitUrl'
     - url: https://kubernetes.default.svc
     - projectName: 'appName'
     - prefix: 'myProjectPrefix'

  - matrix:
      generators:
      - list:
          elements:
          - cluster: dev
          - cluster: prod
      - git:
          repoURL: '{{vars.gitUrl}}/gitops/{{vars.projectName}}.git'
          revision: master
          directories:
          - path: overlays/{{cluster}}/*
  template:
    metadata:
      name: '{{vars.prefix}}-{{path.basename}}-{{cluster}}'
    spec:
      project: default
      source:
        repoURL: '{{vars.myGitUrl}}/gitops/{{vars.projectName}}.git'
        targetRevision: master
        path: '{{path}}'
      destination:
        server: '{{url}}'
        namespace: {{vars.projectName}}-{{cluster}}
      syncPolicy:
        automated:
          prune: true

As you might notice, second one has more dynamic template structure. Simply by changing some global vars, we can implement this yaml for other applications which is in the same structure. Of course there is no hard pain in finding and replacing these variables one by one but, I think this is a bit clean approach. Please let me know if there is any feature already

I think you could accomplish this by adding an outer matrix generator whose first generator is a list with a single element containing all your variables.

maybe I misunderstand "adding an outer matrix generator", but this is not allowed
kind: ApplicationSet
...
spec:
  generators:
    - matrix:
        generators:
          - list:
              elements:
                - service: example
          - clusters:
              selector:
                matchLabels:
                  environment: A
          - clusters:
              selector:
                matchLabels:
                  environment: B
...
  template:
    metadata:
      name: {{ service }}

It throws the error found more than two generators, Matrix support only two
It does work (service acts a global var) with a single cluster though.

I just came across a use case where I could leverage global variables to simplify the way of manipulating applications configuration.
As I bootstrap my K8s cluster with Terraform and also use Terraform resources to deploy ArgoCD itself as well as core add-ons with the use of the App of Apps pattern I would love to be able to hook up to variables that I could manipulate from within the ArgoCD UI anytime. They could then be re-evaluated on app refresh to trigger sync. Currently, to change some of those I must re-run Terraform
I appreciate the fact that this is a specific use case but there might be other use cases where such a feature would make sense to consider it as an enhancement.


MySQL version hell

Looking at https://github.com/scholarslab/NeatlineTime/blob/master/NeatlineTimePlugin.php#L59-L60
What this does is have one field that set to the current time when the row is inserted, and one field that set to the current time whenever the row is updated.
So here are the issues:

Before MySQL 5.6, you couldn't have two fields with DEFAULT CURRENT_TIMESTAMP, so this is how you handled it;
However, if NO_ZERO_DATE is set, this idiom throws an error;
With 5.6, the first restriction is taken away, so there's no problem.

The issues comes in when you're dealing with MySQL 5.6 with NO_ZERO_DATE set.
The kludge I used is to insert this line before executing the query:
$this->_db->query("SET SQL_MODE='ALLOW_INVALID_DATES';");

Short of changing server config, which isn't always an option, I don't see a way around this. So this is just here for documentation.

The Omeka core's workaround for this is to have an arbitrary date as the default (avoiding the implied CURRENT_TIMESTAMP default), and set the actual default explicitly from the PHP side with the Timestamp mixin. (see omeka/Omeka#678).

Thanks. I suspect that will be what we'll end up doing.


stop skipping tests

#266 has one test that's being skipped, we should come back and see if we can get this to work.

/FYI This issue is now out of SLO. I am ok with disabling the tests that I disabled because the Commands tests are not guaranteed to work and the tests requiring async operations seem to run non-deterministically in the CI without the nodejs devrel tooling.

@gguuss it's fine to simply label this issue as process, since it's an improvement we would like to make.

SGTM, thanks @bcoe

closing this for now due lack of resource capacity.


feat: remove supertest, add random ports

[X] Remove Supertest from jest-pact API & README
[X] Remove default port, allow pact-js to set a random port, and expose this to the client
[X] Ignore artefact from npm publish (wash up from release automation)

I can’t see how the random port is assigned- is there a missing commit?

@mefellows recently introduced the ability in pact-js to randomly assign a port, if not supplied, so it's a nice no-op on our side.
If you break the regex in the last test, you'll see it assign a different port in the error message on each test run :)

Aha! That’s very nice, and definitely the right place to do it.

On 31 May 2019, at 1:08 pm, Yousaf Nabi<EMAIL_ADDRESS>wrote:
I can’t see how the random port is assigned- is there a missing commit?
@mefellows recently introduced the ability in pact-js to randomly assign a port, if not supplied, so it's a nice no-op on our side.
If you break the regex in the last test, you'll see it assign a different port in the error message on each test run :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


⚠ Samsung has degraded performance

In 318b7f2, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2438 ms

Resolved: Samsung performance has improved in 1fe3897.


Question: "Reducers may not dispatch actions"

I haven't been able to replicate this in an isolated environment, but it's an error which keeps getting picked up from our error reporter.
We have two websockets which asynchronously push data to the client. Upon receiving messages on these websockets, redux store actions are dispatched.
What appears to be happening based on our error stack trace is that mid-way between one state update cycle occurring (perhaps in between reducer function calls) an asynchronous message is being received on one of the sockets, and this somehow is prioritised above the current redux state update cycle - thus when it gets to the end of the cycle it sees that an action has been dispatched in that time, and throws the error.
Stack trace from error capture:

As you can see there are two calls to "src/api/asyncListeners -> listener" - these are both reactions to asynchronous events, and are not related / triggered by each other.
Below is an example fiddle which doesn't show the problem. Clearly this code waits for the first state update cycle to run before processing the next action:
https://jsfiddle.net/pojzf7vx/2/
TL;DR;

When the "Reducers may not dispatch actions" error is thrown, is this because something is likely to have gone wrong in the redux store? Or is this a best practice warning to prevent, say, infinite loops?

Will redux start a secondary state update cycle if it receives an action mid-update?

Is there any way to force redux to process full state updates for actions one at a time?

Appreciate any help/advice!

Is one of your reducers asynchronous in some way? If so, that is considered a side effect. You should push any side effects to be handled in your middleware, not your reducer functions. They should be pure (no global variable access, including setTimeout).

@timdorr the reducers are all pure synchronous functions

@timdorr This question seems to have been closed prematurely.

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!

I'm also seeing this Reducers may not dispatch actions error pop up in Sentry logs, and I'm also not (yet) able to reproduce it. However, for what it's worth, in my case exactly 100% of these errors are coming from some version of Internet Explorer, mostly IE 11.

it's happening to me too (in react native), and it's crashing the app... and likewise, none of my reducers are dispatching actions, and all are synchronous
"dependencies": {
    "react": "16.2.0",
    "react-native": "0.52",
    "react-redux": "^5.0.6",
    "redux": "^3.7.2",
    "redux-thunk": "^2.2.0"
  }

some news about this ? I have the same problem.
export function fetchDashboard() {
  return (dispatch) => {
    dispatch(isFetching()); // Error
  };
}

"react": "16.2.0",
react-native": "0.52.0",
"react-redux": "5.0.5",
"redux": "3.7.2",
"redux-thunk": "2.2.0"

FWIW, I was seeing these errors when I put a debugger statement inside my reducer. Seems like there are assumptions redux is making when deciding that this error condition has been met that are either incorrect, or which involve complexity in the js execution innards.

I also run into this problem using webrtc. So, instead of doing:
yield put(myReduxAction(data));  //causes the "reducers may not dispatch actions" error
I did:
yield fork(function*(data){yield put(myReduxAction(data));}, data);
It worked for me. For more info, see,
https://redux-saga.js.org/docs/advanced/Channels.html

I agree this should be impossible. However I managed to recreate this using Chrome 75.0.3770.100. I'm trying to get this to happen again but I haven't managed to get it to happen again. But I would be interested if someone else can get it to happen again.
import primeBenchMark from 'prime-number/benchmark';
import primeNumber from 'prime-number';

let lock = false;
let count = 0;
const lockedFunction = () => {
  count++;
  console.info(`Started ${count}`);
  if (lock) {
    throw new Error('Not single threaded');
  }

  lock = true;
  primeBenchMark(primeNumber)(10000, 500000);
  lock = false;
  console.info(`Ended ${count}`);
};

const runMany = (func, times, delay) => {
  let count = 0;
  const runCycle = () => {
    func();
    if (count < times) {
      count++;
      setTimeout(runCycle, delay);
    }
  };

  runCycle();
};

const lockTest = (times = 100, delay = 500) => {
  runMany(lockedFunction, times, delay);
};

But this has been driving me nuts. If the redux store ever get into this state it cannot recover. Contemplating branching off my own version of redux to unset isDispatching when this error occurs, which I don't think we should have to do but it's better then the app breaking because of it.

To be blunt: if there's an issue here, it's not the fault of Redux.  The logic is sound - there's nothing we can do about environments that might be somehow doing something bizarre.

I know that, firefox is fine as far as I have tested it, and this should be impossible with javascript running as a single thread. But letting people know should they randomly experience this issue, as I can't find much about this issue online. Also confirming that this is not a redux issue, but this issue will break it when it occurs.

Yea, I mean this issue has been closed since it was created. I never really expected anything to be done about this. I don’t believe the issue is in the redux source or our source at all.
It is good to collect what information we do have on the subject to see if we could find the true cause, but it is a difficult one.
In the case above, if you are able to reproduce a problem with JS execution order perhaps this discussion should be moved to a ticket here?
Perhaps they will tell us this is a possibility due to some extreme circumstance we haven’t thought up.

Yeah my search still goes on to isolate the exact cause, it is really driving me nuts. Thinking about this some more, it seems the current execution just completely stops silently, and so it never progresses to the finally statement, if it did it would eventually recover, but it does not.
Thanks for the link, I'll see if anyone has reported this issue, if not I'll continue trying to isolate it to reproducible steps and report it myself.


Horse Power Hannover

Hi,
i put the link for the google album and additional informations in the email i wrote at the 16.11.19.

Hi Kope,
Merge Request is looking good. Thank you very much for your contribution.


Fix/javadoc script

disable broken Linux Arm64 build

I added the copy of the javadoc script I had, for local testing


Add react-native-actionsheet, native-navigation and react-native-navigation

Hi, ActionSheet, react-native-navigation and native-navigation library for iOS and Android.

LGTM, cool libraries!


An option to skip transitive dependencies when dumping

Would it be possible to dump only to dump "installed formulae that are not dependencies of another installed formula" just like brew leaves does?

This is already the case. brew leaves (as-is_ is not the right tool for the job here, though; just because something is a leaf does not mean you don't want it listed in your Brewfile. brew bundle effectively runs brew leaves --installed-on-request. If there's something being brew bundle dumpd that you don't want: it's because at some point you or some tool brew installed it.
To resolve this for your particular case e.g. libfido2 you should do something like:
brew uninstall --ignore-dependencies libfido2
brew install --only-dependencies mysql mysql-client

then, if my memory serves me correctly, it'll no longer brew bundle dump libfido2.
Originally posted by @MikeMcQuaid in https://github.com/Homebrew/homebrew-bundle/issues/1260#issuecomment-1759397149

This was brought up previously, but closed, due to it not actually being a behaviour at the time. However, since then, it appears to be have been added as an intentional behaviour (i.e. brew bundle dump is currently including packages that do not appear in brew leaves - in fact, they're sorted non-alphabetically, before their leaf dependants, so it's pretty clear it's an intentional process.)
It'd be nice to be able to disable this behaviour optionally. Especially because there's no differentiation in the file between what was a leaf, and what was not; so that metadata is lost upon installation to a new system (or just ... existing for a couple of years, and forgetting what you've installed and why. 😅)
$ brew --version
Homebrew 4.4.4-41-g451c3a8
Homebrew/homebrew-cask (git revision 7ee2e0d5f65; last commit 2024-11-05)

Sorry, passing on this. This is intentional behaviour. Homebrew has no concept of leaves: only things installed on request or as dependencies. As mentioned previously: dependencies that are installed on request must be dumped earlier because they will be installed earlier and otherwise the error messages if they fail to install are unnecessarily confusing.

Especially because there's no differentiation in the file between what was a leaf, and what was not; so that metadata is lost upon installation to a new system

This metadata was never stored. What is installed on request, however, is not lost: it will still be installed on request on a new system and installed as a dependency when not specified in the Brewfile.

This metadata was never stored. What is installed on request, however, is not lost: it will still be installed on request on a new system and installed as a dependency when not specified in the Brewfile.

Wait, I'm confused; it's not lost?
As in, if I run one of the new brewfiles (that includes, say, brew "xz" before brew "imagemagick") on a new system, then brew leaves --installed-on-request won't print "aom"? Because that's my primary concern, polluting of the 'installed on request' list, which is a pretty crucial resource when working across a lot of languages, stacks, and projects, across multiple machines. 😅


feat(treelist): removed treelist component as it is now part of patternly-ng

If patternfly-ng and ngx-widgets are both used, the two listview implementations are conflicting, resulting in funny behaviour. We need to remove the treelist from here.

@michaelkleinhenz please change the commit syntax to use perf as this is breaking the sdk by removing a component.

@michaelkleinhenz I made the change when I merged it.


createComplexComponent, support method syntaxed script property

Currently, when using createComplexComponent, if the script property has a method syntaxed function, it results in erroneous code. The library should have a workaround for this, or provide a warning/error.

From bf7fa70c5fb1ade0ea586a097942c0b81f1094db, decharge provides a clear error message when using method syntaxed scripts.
I decided to only support arrow and the old function syntax because they are easy to detect.
Method syntax can take basically any form due to computed property names,
so it would be complicated to transform it to a regular function. So let's just not do that.
However, if somebody makes a function-to-string library which supports this scenario, this issue should be reopened.


Identify variables and perform EDA

Statistical Analysis performed for all-time data.
Performance Analysis for all-time data.
Statistical Analysis for last 3 seasons.

In depth batter analysis was performed by slicing overs into powerplay, middle overs and death overs.
The KPIs discussed were used to sort data.
runs and wickets were plotted against the innings progression to observe trends


License?

Hi Kyle,
There's no license identified for the neg23 code; did you intend something very permissive? :) (MIT etc?)

There you go. MIT License. Thanks!


Plugin errors out when the package does not exist

I am using the plugin and I want the generated java class to be located in a package named generatedsources. This package does not exist when the project is checked out from git.
For example my config looks like this:
gversion {
    srcDir = "/main/src/main/java"
    classPackage = "lt.companyname.projectname.generatedsources"
    className = "Version"
    timeZone = "Europe/Vilnius"
}

I get an error message:
 java.io.FileNotFoundException: /location/of/project/projectname/main/src/main/java/lt/companyname/projectname/generatedsources/Version.java (No such file or directory)

I would like to be able to force a creation of the package directory.

which version of gversion are you using?

I am using version 1.2.5 from https://plugins.gradle.org/m2/

I was able to replicate the problem and it's fixed. Reopen the ticket if you have any problems. The new version is 1.2.6

Thank you for quick responses. I'll try the new version as soon as I can. If I'll encounter some problems I'll create a new issue.


Auto-Aim Integration

https://github.com/RoboMaster-Club/control-base/commit/408ebb2f3d5997f8fb1709ca21753ca63911d1bb


Error code 112

I downloaded the required files and started the installation, but it seems to work fine until I get up to 64 %, and then it says, Error code 112, there has been a problem during your deployment: DISM exited with code 112

I get the same error.
Is it looking for DISM in the wrong place?
Windows 10 documentation says:

DISM comes with Windows 10, in the c:\windows\system32 folder, but you can run DISM in the command prompt from any location. You have to be running from a Command Prompt as administrator to use use DISM.

I can see DISM.exe in that folder but it's looking for it in C:\WINDOWS\SysNative\dism.exe
The logging seems to say that DISM was started and returned the error code but I'm doubting that.
I've copied dism.exe and the dism folder from system32 to C:\WINDOWS\SysNative\ and going to try again.

2019-02-17 21:55:35.658 +02:00 [Verbose] Wim metadata deserialized correctly WimMetadata { TotalBytes: "3204780842", Images: [ImageMetadata { DirectoryCount: "19016", FileCount: "85770", TotalBytes: "13896743737", HardLinkBytes: "6092415839", CreationTime: Time { HighPart: "0x01D4C09E", LowPart: "0xE35BD26F" }, LastModificationTime: Time { HighPart: "0x01D4C09F", LowPart: "0xA17D02E1" }, WimBoot: "0", Windows: Windows { Arch: "12", ProductName: "Microsoft® Windows® Operating System", EditionId: "Core", InstallationType: "Client", ServicingData: ServicingData { GdrDuRevision: "0", PKeyConfigVersion: "10.0.18836.1000;2016-01-01T00:00:00Z" }, ProductType: "WinNT", ProductSuite: "Terminal Server", Languages: Languages { Language: "en-GB", Default: "en-GB" }, Version: Version { Major: "10", Minor: "0", Build: "18836", SpBuild: "1000", SpLevel: "0" }, SystemRoot: "WINDOWS" }, Name: "Windows 10 Home", Description: "Windows 10 Home", Flags: null, DiplayName: "Windows 10 Home", DisplayDescription: "Windows 10 Home", Index: "1" }] }
2019-02-17 21:55:35.659 +02:00 [Verbose] We are about to run DISM: "C:\WINDOWS\SysNative\dism.exe" "/Apply-Image /ImageFile:"C:\Users\Public\WoA\install.wim" /Index:1 /ApplyDir:G:"
2019-02-17 21:55:35.659 +02:00 [Verbose] Starting process { FileName: "C:\WINDOWS\SysNative\dism.exe", Arguments: "/Apply-Image /ImageFile:"C:\Users\Public\WoA\install.wim" /Index:1 /ApplyDir:G:" }
2019-02-17 21:55:35.668 +02:00 [Verbose] Process started sucessfully
2019-02-17 22:38:16.112 +02:00 [Error] An error has ocurred
Installer.Core.Exceptions.DeploymentException: There has been a problem during deployment: DISM exited with code 112.
at Installer.Core.FullFx.DismImageService.d__1.MoveNext() in C:\Users\super\source\repos\Install\Installer.Core.FullFx\DismImageService.cs:line 39
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.Core.RaspberryPiWindowsDeployer.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.Core.RaspberryPiWindowsDeployer.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.Core.RaspberryPiDeployer.d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.Core.RaspberryPiDeployer.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.ViewModels.MainViewModel.d__59.MoveNext()
2019-02-17 22:38:16.118 +02:00 [Information] Error: There has been a problem during deployment: DISM exited with code 112.

I get the same error.
Is it looking for DISM in the wrong place?
Windows 10 documentation says:

DISM comes with Windows 10, in the c:\windows\system32 folder, but you can run DISM in the command prompt from any location. You have to be running from a Command Prompt as administrator to use use DISM.

I can see DISM.exe in that folder but it's looking for it in C:\WINDOWS\SysNative\dism.exe
The logging seems to say that DISM was started and returned the error code but I'm doubting that.
I've copied dism.exe and the dism folder from system32 to C:\WINDOWS\SysNative\ and going to try again.

2019-02-17 21:55:35.658 +02:00 [Verbose] Wim metadata deserialized correctly WimMetadata { TotalBytes: "3204780842", Images: [ImageMetadata { DirectoryCount: "19016", FileCount: "85770", TotalBytes: "13896743737", HardLinkBytes: "6092415839", CreationTime: Time { HighPart: "0x01D4C09E", LowPart: "0xE35BD26F" }, LastModificationTime: Time { HighPart: "0x01D4C09F", LowPart: "0xA17D02E1" }, WimBoot: "0", Windows: Windows { Arch: "12", ProductName: "Microsoft® Windows® Operating System", EditionId: "Core", InstallationType: "Client", ServicingData: ServicingData { GdrDuRevision: "0", PKeyConfigVersion: "10.0.18836.1000;2016-01-01T00:00:00Z" }, ProductType: "WinNT", ProductSuite: "Terminal Server", Languages: Languages { Language: "en-GB", Default: "en-GB" }, Version: Version { Major: "10", Minor: "0", Build: "18836", SpBuild: "1000", SpLevel: "0" }, SystemRoot: "WINDOWS" }, Name: "Windows 10 Home", Description: "Windows 10 Home", Flags: null, DiplayName: "Windows 10 Home", DisplayDescription: "Windows 10 Home", Index: "1" }] }
2019-02-17 21:55:35.659 +02:00 [Verbose] We are about to run DISM: "C:\WINDOWS\SysNative\dism.exe" "/Apply-Image /ImageFile:"C:\Users\Public\WoA\install.wim" /Index:1 /ApplyDir:G:"
2019-02-17 21:55:35.659 +02:00 [Verbose] Starting process { FileName: "C:\WINDOWS\SysNative\dism.exe", Arguments: "/Apply-Image /ImageFile:"C:\Users\Public\WoA\install.wim" /Index:1 /ApplyDir:G:" }
2019-02-17 21:55:35.668 +02:00 [Verbose] Process started sucessfully
2019-02-17 22:38:16.112 +02:00 [Error] An error has ocurred
Installer.Core.Exceptions.DeploymentException: There has been a problem during deployment: DISM exited with code 112.
at Installer.Core.FullFx.DismImageService.d__1.MoveNext() in C:\Users\super\source\repos\Install\Installer.Core.FullFx\DismImageService.cs:line 39
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.Core.RaspberryPiWindowsDeployer.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.Core.RaspberryPiWindowsDeployer.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.Core.RaspberryPiDeployer.d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.Core.RaspberryPiDeployer.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Installer.Raspberry.ViewModels.MainViewModel.d__59.MoveNext()
2019-02-17 22:38:16.118 +02:00 [Information] Error: There has been a problem during deployment: DISM exited with code 112.

Copying DISM to that location didn't work. Looking at the timestamps DISM started long before the error occurred.
PS: if it helps any for me this error occurrs at 90%

I downloaded the required files and started the installation, but it seems to work fine until I get up to 64 %, and then it says, Error code 112, there has been a problem during your deployment: DISM exited with code 112

@princessAmy @patel8786
I got the same thing first time, but run it again and that might solve that issue. I did run 3x to successfully complete the process.
This issue seems because of threading stuck at somewhere waiting for another Task to complete (which actually might be complete but didn't get proper notification of completion).

Use https://github.com/WOA-Project/WOA-Deployer-Rpi


Error "Preview not ready yet" when trying to preview uploaded PDF via REST API

Description
Hey @ciur
I am trying to consume the paper merge REST API following the docs, When I upload a pdf file (tested using postman) the preview is not visible, I see an error when viewing the document in paper merge client
error: preview not ready yet
Steps to reproduce

execute the login api http://localhost:16000/api/auth/login/
use the token to create a folder by calling http://localhost:16000/api/nodes/
use the newly created folder's docId to create a document http://localhost:16000/api/nodes/

Heres the equivalent curl request for step 3
curl --location 'http://localhost:16000/api/nodes/' \
--header 'Authorization: Token b71b705720758fa18b5130b9435d68cc470f8681876aa9d917c22d0f8c71592f' \
--header 'Content-Type: application/vnd.api+json' \
--header 'Cookie: csrftoken=SKLLHZuQraSiNAGSHeoKoVS4xTMN8rVSUPitszpJKv5zqsMUwAHEDL7zKkaEJczC; sessionid=r5mpf2lixfrued96gz0wxfm1t7urivim' \
--data '{
    "data": {
      "type": "documents",
      "attributes": {
        "title": "MyResume.pdf"
      },
      "relationships": {
        "parent": {
          "data": {
              "type": "folders",
              "id": "802d655e-72ce-400a-877c-2bc1e43671ac"
          }
        }
      }
    }
  }'

Associate the created document with an actual document

Heres the equivalent curl request for step 4
curl --location --request PUT 'http://localhost:16000/api/documents/7cc9d985-43c7-4a58-be70-d02c1434f24e/upload/MyResume.pdf' \
--header 'Authorization: Token b71b705720758fa18b5130b9435d68cc470f8681876aa9d917c22d0f8c71592f' \
--header 'Content-Type: application/pdf' \
--header 'Content-Disposition: attachment; filename=MyResume.pdf' \
--header 'Cookie: csrftoken=SKLLHZuQraSiNAGSHeoKoVS4xTMN8rVSUPitszpJKv5zqsMUwAHEDL7zKkaEJczC; sessionid=r5mpf2lixfrued96gz0wxfm1t7urivim' \
--form<EMAIL_ADDRESS>

Note that In both steps 3 and 4 the status code is 201. However the uploaded document can be downloaed and viewed but it would be good to have the preview feature working
Expected
The uploaded document can be previewed in papermerge client
Actual

Let me know if you need any further info to investigate the issue.

Maybe you give a try to version 3?

via docker: https://papermerge.github.io/documentation/3.0-dev/setup/docker/
via docker compose: https://papermerge.github.io/documentation/3.0-dev/setup/docker-compose/
or ansible: https://papermerge.github.io/documentation/3.0-dev/setup/ansible/

I will officially release version 3.0 it in a month or so.
One of the differences between 3.0 and previous version(s) is that in 3.0 the frontend was completely rewritten - it is all new.

Thanks will take a look, Keep up the great work.

Hello @ciur,
I was trying to run the papermerge app using docker-compose, I think there is an issue with arm64 machines I am using a Mac with Apple silicon
mahesh@Maheshs-MacBook-Air-M1-3 papermerge % docker-compose up -d
[+] Running 1/3
 ⠼ db 14 layers [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀]      0B/0B      Pulling                                                      1.3s
   ⠋ 3b5e91f25ce6 Pulling fs layer                                                                            0.0s
   ⠋ e8bc76afe420 Pulling fs layer                                                                            0.0s
   ⠋ 761b98bedd87 Pulling fs layer                                                                            0.0s
   ⠋ 641ccbcd7a49 Waiting                                                                                0.0s
   ⠋ dacb5640e5b0 Pulling fs layer                                                                            0.0s
   ⠋ c179b52c109c Pulling fs layer                                                                            0.0s
   ⠋ 8346884a3639 Pulling fs layer                                                                            0.0s
   ⠋ 07007a1bc9bd Pulling fs layer                                                                            0.0s
   ⠋ 78d77fb8c2e2 Pulling fs layer                                                                            0.0s
   ⠋ 6a3285e38d6f Pulling fs layer                                                                            0.0s
   ⠋ 98a339fb05a2 Pulling fs layer                                                                            0.0s
   ⠋ 3b006c0b7bf4 Pulling fs layer                                                                            0.0s
   ⠋ 40a527a44543 Pulling fs layer                                                                            0.0s
   ⠋ aeb99eeba715 Pulling fs layer                                                                            0.0s
 ⠼ web Pulling                                                                                1.3s
 ✘ worker Error                                                                                1.3s
no matching manifest for linux/arm64/v8 in the manifest list entries
mahesh@Maheshs-MacBook-Air-M1-3 papermerge % docker-compose up -d
[+] Running 1/2
 ⠴ worker Pulling                                                                                6.6s
 ✘ web Error                                                                                6.6s
no matching manifest for linux/arm64/v8 in the manifest list entries
mahesh@Maheshs-MacBook-Air-M1-3 papermerge % docker-compose up -d
[+] Running 1/3
 ⠼ solr Pulling                                                                                1.4s
 ✘ web Error                                                                                1.4s
 ⠼ worker Pulling                                                                                1.4s
no matching manifest for linux/arm64/v8 in the manifest list entries

I tried all three configuration on this link  https://papermerge.github.io/documentation/3.0-dev/setup/docker-compose/

Yes it is because of arm cpu. Currently there are no docker image for arm architecture.


update config function and remove internal _is_simplified function

This PR:

removes the internal _is_simplified function as its functionality is easily replicated in a single line of code in the two places it's used
sorts the parameters of the utils.config function
adds the OSMnx version and current status of HTTP response caching to the log message when utils.config is run

Coverage decreased (-0.003%) to 92.47% when pulling 5a3188f0b29e3cc221f4f6ce857943a4e474bc8a on gb into 096d55cddfe2885aeda4689f3539f87ddb4cd84b on master.


Update Android Gradle build version and Kotlin version

The current Kotlin version is too old to be supported with the newer Android Gradle build version (com.android.tools.build:gradle). When Android Gradle build version 7.3.0 and above is used, the current Kotlin version in the package (ext.kotlin_version = '1.3.50') is no longer supported as starting from Android Gradle build version 7.3.0 and above requires Kotlin version 1.5.20 and above.

Thanks, I'll publish this patch along with another major feature that is already in the master.


AE setup

Codecov Report

Merging #337 into RTW_6.2.0 will increase coverage by 2.95%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##             RTW_6.2.0     #337      +/-   ##
===============================================
+ Coverage        37.16%   40.12%   +2.95%
- Complexity        1669     1775     +106
===============================================
  Files              103      103
  Lines            23662    23662
  Branches          3918     3918
===============================================
+ Hits              8795     9495     +700
+ Misses           13278    12442     -836
- Partials          1589     1725     +136

Flag
Coverage Δ
Complexity Δ

#JDBC41
40.04% <ø> (+3.01%)
1772 <ø> (+112)
:arrow_up:

#JDBC42
39.91% <ø> (+2.82%)
1767 <ø> (+100)
:arrow_up:

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/microsoft/sql/DateTimeOffset.java
37.14% <0%> (-2.86%)
8% <0%> (-2%)

...m/microsoft/sqlserver/jdbc/SQLServerException.java
75.6% <0%> (-1.63%)
28% <0%> (-1%)

...om/microsoft/sqlserver/jdbc/SimpleInputStream.java
47.4% <0%> (-1.49%)
9% <0%> (-1%)

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
44.94% <0%> (ø)
16% <0%> (ø)
:arrow_down:

...rc/main/java/com/microsoft/sqlserver/jdbc/DDC.java
29.43% <0%> (ø)
56% <0%> (ø)
:arrow_down:

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
48.93% <0%> (+0.14%)
209% <0%> (-1%)
:arrow_down:

...m/microsoft/sqlserver/jdbc/SQLServerResultSet.java
27.57% <0%> (+0.33%)
190% <0%> (+3%)
:arrow_up:

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
46.94% <0%> (+0.99%)
0% <0%> (ø)
:arrow_down:

...c/main/java/com/microsoft/sqlserver/jdbc/Util.java
48.63% <0%> (+1.36%)
67% <0%> (+7%)
:arrow_up:

.../microsoft/sqlserver/jdbc/SQLServerConnection.java
44.61% <0%> (+1.44%)
266% <0%> (+14%)
:arrow_up:

... and 20 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 1da02b5...f4bf23d. Read the comment docs.


Add -skipVerify flag to kapacitor cmd to skip SSL verification

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated
[x] Sign CLA (if not already signed)

@rossmcdonald This looks great. Thanks. I believe #532 is different and is referring to the alert post action not the Kapacitor CLI tool.

@nathanielc Oops, you're right. I just saw the error and thought it was referring to this. I've removed it from the summary, though.

@rossmcdonald LGTM If you wanted to fix #532 too it should be simple ;)


Add DB Fail Over List

If the database cluster the package is talking to goes down, there should be a back up list of clusters to try.
Think of it as a primary cluster and a backup list. So if the primary cluster comes back, the active connection should go from the backup list back to the primary.

Think of it as a primary cluster and a backup list. So if the primary cluster comes back, the active connection should go from the backup list back to the primary.

We need a configurable interval for when to ping the primary cluster to check if it's back.  Also, I think we need an ordered list, otherwise different svalinns may fall back to different clusters, causing issues (only a problem if we are supposed to insert only to one region).

Yes, I agree.

Closing this as it is not needed anymore.


Updated supported version setting for DJI-SDK-iOS

Small changes for fix Dependency support issue

@nab0y4enko thanks for making this contribution and congratulations on being the first external contributor to this project!


Add Expand's card.

Description
Hey, project admin, I'm a GSSOC participant and I want to add an Expanding card project created with HTML CSS and JavaScript.
it is basically a type of slider project where we click on an image and it slides to the next image. I'm adding the preview below to get an idea of the project.
Screenshots
https://user-images.githubusercontent.com/95171638/148639287-d9045b16-27d9-4de6-a9d0-cbe0df759f46.mp4
Additional information
@AyushSingh22 can i work on this issue.

Yes Go ahead

Yes Go ahead

@AyushSingh22 thanks for assigning this issue to me.


add paris region

Addresses #447 by adding the new AWS Paris region to the list of canonicalHostedZones.

probably have to change the implementation to dynamically update the list, there is really no guarantee the list of IDs will never change


Integration with PVGIS 5.2

This is just a note/food for thought not a direct integration request
I just came across this website by the EU, that allows to download EPW files for just about ANYWHERE in the world:
https://re.jrc.ec.europa.eu/pvg_tools/en/#TMY
it also offers some API endpoints:
https://joint-research-centre.ec.europa.eu/pvgis-photovoltaic-geographical-information-system/getting-started-pvgis/api-non-interactive-service_en
I am not sure about the quality of data, but it seems certainly interesting. I have tested a  few weather files and they seem to work fine, only issues found are:

the location is not contained (is marked as unknown, unknown)
the cloud cover is expressed in percentage rather than in tenths.

screenshot of the interface 👇

Hi @giobetti - fyi, PVGIS is an excellent source. These reanalysis datasets represent the current state-of-art reconstruction of past weather, free from observation biases and consistent with laws of physics.
Climate One Building recently updated all their data files using ERA5 solar radiation data, which PVGIS also uses. In fact, it looks like PVGIS 5.2 is using ERA5-Land dataset (9km), which is higher resolution than ERA5 (~30km).

Thanks for the comment. I haven’t looked into it enough, but my understanding is that those datasets can be very accurate for variables like temperature and radiation but not so for wind speed and direction.
Do you have any info/thoughts on this?
Best,
Giovanni
Sent from my iPhone
On 8. May 2022, at 01:41, Joseph Yang @.***> wrote:

Hi @giobettihttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgiobetti&data=05|01||e047d076b0b54f285dcf08da3083204d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637875636987503639|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=3TPklOogq1ISXj785phq48E4cxmvFzDLBbve9wxvxrE%3D&reserved=0 - fyi, PVGIS is an excellent source. These reanalysis datasets represent the current state-of-art reconstruction of past weather, free from observation biases and consistent with laws of physics.
Climate One Building recently updated all their data files using ERA5 solar radiation data, which PVGIS also uses. In fact, it looks like PVGIS 5.2 is using ERA5-Land dataset (9km), which is higher resolution than ERA5 (~30km).
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCenterForTheBuiltEnvironment%2Fclima%2Fissues%2F134%23issuecomment-1120317506&data=05|01||e047d076b0b54f285dcf08da3083204d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637875636987503639|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=v%2BYCowRtonZwIEaubBtlj6hDgtoslR2%2FslAA%2B%2BsbRyE%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIWZJAFZ6BKFWJ2AITFIL3TVI35S7ANCNFSM5UCSWAZA&data=05|01||e047d076b0b54f285dcf08da3083204d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637875636987503639|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=hrfGqg3nuheCExLyPCuU%2FeNb59nb00gfKTk4QuYRi8U%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

It really depends on the application because wind is heavily affected by topology but for the level of accuracy needed for building energy simulation I'm of the opinion that it's more or less sufficient (for a bit of a disclaimer, we provided the ERA5 data that Dru and Linda used to update Climate One Building files). One paper on ERA5 wind speed that I found is this:

https://mdpi-res.com/d_attachment/energies/energies-14-04169/article_deploy/energies-14-04169-v3.pdf?version=1626325931

The paper basically mentions that for coastal regions and hilly areas the coarse model resolution (~30km) results in larger errors but works well in offshore wind and inland, which I think aligns with intuition.
Regards,
Joseph

Per the discussion, de-scope for our project


Updated the metadata as per instructions.

:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/rendering-in-directx.md
:warning:Warning
View
Details

mixed-reality-docs/rendering-in-directx.md

[Warning] Author<EMAIL_ADDRESS>cannot be recognized in GitHub.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/rendering-in-directx.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Document Poetry requirements

The documentation should state that Poetry has to be installed separately, and which minimum version nox-poetry requires.
This was brought up in #348.

See also #389

See also https://github.com/cjolowicz/cookiecutter-hypermodern-python/issues/847


Clean-up docs and API for Trie module.

List main operations as put, get and iter.
Example of using Trie directly, without TrieMap OO wrapper API.
adds get as a synonym for find, making it easier to "find", perhaps.
adds iter (adapted from TrieMap)
Editing pass over old implementation notes, moving them after usage notes.
Test Trie independently of TrieMap module.

@crusso Thanks for taking a look.
I completely agree that this module deserves a test suite.  Perhaps as another PR though?  (Focusing on docs here).

Actually, looking at the code again there are quite a few helpers that seem to just be there to avoid instantiating type parameters.
Hopefully, Motoko should be able to infer all those now, letting your write the more efficient code you first wanted to write.
Perhaps try that in a separate commit (to see if it works). Using VSCode might be helpful since you'll see the errors right away (or Motoko mode in emacs if you have that working).
E.g. https://github.com/dfinity/motoko-base/blob/174f24d3f0a20d11ad91dd9d1bd91371f9f79186/src/Trie.mo#L526

@crusso PTAL
Updates:

removed profile labels
removed explicit type args
renamed test file to clarify it's just for examples (in the doc).

@crusso wrote

Hopefully, Motoko should be able to infer all those now, letting your write the more efficient code you first wanted to write.

Indeed!  Motoko can now infer all of the explicit type arguments.  I've adjusted the code (simplifying it) accordingly.  Thanks for suggesting this, and the other review comments as well.

Thanks again @crusso.  I attended to the lower case sentence starts.  Not sure how those arose, but thanks for catching them.
PTAL.


Python 3.6 Support

While working on this project, I've encountered times where I'd like to use a nice Python feature but was unable to do so due to the Python 3.6 requirement. (Examples include dataclasses and importlib.resources.)
I'm making this issue to suggest moving the minimum Python version up to 3.7. I don't know how much of an effect this'll have on existing projects, however, so that'll need to be weighed in. Would this be possible?

It's okay to do that, I think. The other option would be to remove the dependency on these functions.

@AndrielFR True. It's certainly not necessary right now, but I was just wondering whether it's a loose requirement.

@AndrielFR True. It's certainly not necessary right now, but I was just wondering whether it's a loose requirement.

I will drop Python 3.6 support.


pikaday field calue changes to '01-01-1970' when Backspace is pressed.

I found a bug when pikaday control is used in vfg. I tried changing the values by pressing the arrow keys. Just when i tried using backspace key to delete the date value, it is changing to '01-01-1970'. Is it the behaviour or a bug? Same way with Delete button also.

I'm creating a pull request to fix this issue


fable: 4.1.4 -> 4.4.1

Description of changes
https://github.com/fable-compiler/Fable/releases/tag/4.2.0
https://github.com/fable-compiler/Fable/releases/tag/4.2.1
https://github.com/fable-compiler/Fable/releases/tag/4.2.2
https://github.com/fable-compiler/Fable/releases/tag/4.3.0
https://github.com/fable-compiler/Fable/releases/tag/4.4.0
https://github.com/fable-compiler/Fable/releases/tag/4.4.1
https://github.com/fable-compiler/Fable/releases/tag/4.5.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2738

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2782

updated to 4.5.0


Use of disposed HttpClient in RecaptchaService

<PackageReference Include="reCAPTCHA.AspNetCore" Version="3.0.6" />

Sorry this is a naff bug report, bit busy or I would try to be more thorough.
I think it's on second instantiation of RecaptchaService, you register service transient but don't always new up a HttpClient (it's static) so you can keep around one which has been disposed.
I already have a dependency on Flurl.Http which gives me a nice abstraction around HttpClient and manages client lifetimes for me per domain so I have just registered a new IRecaptchaService
using System.ComponentModel.DataAnnotations;
using System.Net.Http;
using System.Threading.Tasks;
using Flurl.Http;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Options;
using reCAPTCHA.AspNetCore;

namespace Foo.Example.Com
{

    public class RecaptchaService: IRecaptchaService
    {
        private readonly RecaptchaSettings _settings;

        public HackRecaptchaService(IOptions<RecaptchaSettings> options)
        {
            _settings = options.Value;
        }

        public HackRecaptchaService(IOptions<RecaptchaSettings> options, HttpClient client)
        {
            _settings = options.Value;
        }

        public async Task<RecaptchaResponse> Validate(HttpRequest request, bool antiForgery = true)
        {
            if (!request.Form.ContainsKey("g-recaptcha-response")) // error if no reason to do anything, this is to alert developers they are calling it without reason.
                throw new ValidationException("Google recaptcha response not found in form. Did you forget to include it?");

            var response = request.Form["g-recaptcha-response"];
            var url = $"https://{_settings.Site}/recaptcha/api/siteverify?secret={_settings.SecretKey}&response={response}";
            var captchaResponse = await url.GetJsonAsync<RecaptchaResponse>();

            if (!captchaResponse.success || !antiForgery)
                return captchaResponse;

            var sameHost = captchaResponse.hostname.Equals(request.Host.Host, StringComparison.OrdinalIgnoreCase);
            var testHost = captchaResponse.hostname.Equals("testkey.google.com", StringComparison.OrdinalIgnoreCase);

            if (!sameHost && !testHost)
            {
                throw new ValidationException("Recaptcha host, and request host do not match. Forgery attempt?");
            }

            return captchaResponse;
        }

        public async Task<RecaptchaResponse> Validate(string responseCode)
        {
            if (string.IsNullOrEmpty(responseCode))
                throw new ValidationException("Google recaptcha response is empty?");

            var url = $"https://{_settings.Site}/recaptcha/api/siteverify?secret={_settings.SecretKey}&response={responseCode}";
            var captchaResponse =  await url.GetJsonAsync<RecaptchaResponse>();
            return captchaResponse;
        }
    }
}

I guess as i might understand your question. This isn't an actual bug. It's recommended to practice to keep HttpClient around and NOT to recreate it on each call. There is a check if HttpClient is empty in which case it's created only once. https://github.com/TimothyMeadows/reCAPTCHA.AspNetCore/blob/master/reCAPTCHA.AspNetCore/RecaptchaService.cs#L18

Indeed, one should keep a single http client around per host if possible, this is what Flurl.Http does.
However what one shouldn’t attempt to do, is make a http request with a disposed HttpClient instance as that just throws exceptions, that is what this bug report is about.

It's the second constructor, not sure why a HttpClient is registered in the container, it's an IdentityServer4 project so maybe something upstream.
Should the second constructor exist, what's its purpose?
public RecaptchaService(IOptions<RecaptchaSettings> options, HttpClient client)
{
    RecaptchaSettings = options.Value;
    Client = client;
}

The purpose is from an older version of this library, it's there mostly for historical value, though it can be used to supply your own HttpClient rather than letting the library create it for you. I can look into the effect of removing it.

I don't see any adverse effects of removing this, i doubt anyone uses HttpClient publicly, or set's it via the constructor. If they did i doubt it would cause harm, "not" doing so.
I did add a comment to your pull request though. You had made RecaptchaSettings private, but i do actually know of users that depend on this being public. It would be better to change that back to public and i can approve. Appreciate the work / pull request.


fix(Input): Remove flex-shrink to allow inputs to shrink as needed

Issue: none
What I did

Removed flex-shrink. We noticed that DatePicker had a min-width of 320px because of this, and it isn't needed.
This would affect:

Input
NativeSelect
Select
Textarea
TimePicker
DatePicker
PasswordInput
Search
Combobox

Checklist

[X] changeset has been added
[X] Pull request description is descriptive
[-] I have made corresponding changes to the documentation
[X] New and existing unit tests pass locally with my changes
[-] I have added tests that prove my fix is effective or that my feature works

How to test

Confirm that all of the components above continue to work as expected in all screen sizes and browsers.

I doubt we care about this, but I noticed that placeholder text doesn't get an ellipsis at narrow widths:

@chris-cedrone-cengage good point. I think this is okay because it's the same behavior as before this change was introduced.

Verified the following components are appearing as described:
Input ✅
NativeSelect ✅
Select ✅
Textarea ✅
TimePicker ✅
DatePicker ✅
PasswordInput ✅
Search ✅
Combobox ✅
Tested on:
https://storybook-preview-1448--upbeat-sinoussi-f675aa.netlify.app/
➕
https://docs-preview-1448--upbeat-sinoussi-f675aa.netlify.app/


Add aarch64 supported distros for AMA Linux

Thanks for your fix! The extension supports 22.04? We can use the major and minor versions check to filter out unsupported ones. You can create another PR for it. @simathih


bug(input): not enabled

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.11.0-dev-1326+g3bb2d02759
Operating system/version
Arch / 6.12.3-2-cachyos
Describe the bug
Enabling the input snack doesn't actually make it work, checkhealth shows:
Snacks.input ~
- OK setup {enabled}
- ERROR `vim.ui.input` is not set to `Snacks.input`

Steps To Reproduce
enable the input snack
Expected Behavior
Use it instead of the default vim.ui.input
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/snacks.nvim", opts = {} },
    -- add any other plugins here
  },
})

I'm still having the same problem, I'm not sure how to enable this.

If you still get that health check error, then iot means you or another plugin is overriding vim.ui.input.
Nothing I can do about it.

I'm also seeing this error and the checkhealth is reporting that input is set to Snacks.input. On the most recent version as of this comment.

I'm also seeing this error and the checkhealth is reporting that input is set to Snacks.input. On the most recent version as of this comment.

Yeah that's my current status as well. I can't get it to work so I'm using Noice for the time being, the input from nui that's set by noice is working perfectly.

And why do you think input is not working? It looks pretty much the same as the one in noice. Do esc once then you should go in normal mode. With the noice one, that's not possible.

Well, because when I remove Noice and enable input in Snacks the ui is at the bottom and nothing happens even though checkhealth says it's loaded ok and that UI is set to snacks.input.

How do you test it? You need to test it with vim.ui.input, not vim.fn.input.
Noice does vim.fn.input which is also the default impl for vim.ui.input.

How do you test it? You need to test it with vim.ui.input, not vim.fn.input. Noice does vim.fn.input which is also the default impl for vim.ui.input.

I am not experienced enough in Neovim to fully be able to debug things that aren't working unfortunately. I just expect my command input to be a floating input box instead of the default one in the bottom left after enabling snacks.input. Do you have something quick that I can do to test it? ELI5 unfortunately.

FWIW I also tried disabling all plugins except for snacks and lazy and still had this issue. I am in the same boat where I am still a bit of a novice when it comes to debugging neovim internals and customization. Aside from plugins and other keymappings which I also tried temporarily commenting out my neovim config is basically just a handful of plugins and keymappings.

Same boat here. Everything disabled including keymaps and custom options, only Snacks enabled.

This is not an issue.
In Neovim, there has always been vim.fn.input, to get input from the user on the cmdline.
Later they added vim.ui.input, which allows plugins to get input asynchronously.
The default implementation of that in Neovim is just vim.fn.input.
Plugins can override vim.ui.input (but not vim.fn.input) to provide a better user experience.
That's what snacks.input does.
Noice is a different beast. Since noice implements ui_attach, it can override the whole ui, including the cmdline and as such also vim.fn.input, but still with the same limitations as before, namely that it has to be synchronous.
So again, this is NOT a bug. You just don't understand what vim.ui.input is for.
Please just read the Neovim help to learn more.

This is not a bug.
In Neovim, there has always been vim.fn.input, to get input from the user on the cmdline (synchronously). Later they added vim.ui.input, which allows plugins to get input asynchronously. The default implementation of that in Neovim is just vim.fn.input.
Plugins can override vim.ui.input (but not vim.fn.input) to provide a better user experience.
That's what snacks.input does.
Noice is a different beast. Since noice implements ui_attach, it can override the whole ui, including the cmdline and as such also vim.fn.input, but still with the same limitations as before, namely that it has to be synchronous.
So again, this is NOT a bug. You just don't understand what vim.ui.input is for.
Please read the Neovim help to learn more.

Alright, thanks for the clarification!

to clarify, modern plugins all use vim.ui.input to get input from the user.
older plugins, or vim plugins won't be using this.

And vim.ui.input is not what is triggered when a user presses : ?

No, not at all, that's the cmdline.
Has nothing to do with vim.ui.input or vim.fn.input.
You can test with for example: :lua Snacks.rename.rename_file()

No, not at all, that's the cmdline. Has nothing to do with vim.ui.input or vim.fn.input.
You can test with for example: :lua Snacks.rename.rename_file()

Haha, that explains why it's "not working". 😅
Sorry for wasting your time.


HTTP 500 when trying to add iTunes ID to existing feed

Hello
I'm trying to add an iTunes ID to an existing feed.
According to the docs:

itunesid
If this parameter is given, and the existing feed has no associated iTunes ID, it will be associated with this ID. If an existing iTunes ID is already associated with this feed it will NOT be changed.

While I get a 302 as expected when trying to submit an existing feed, submitting an existing feed plus its iTunes ID, I get a 500 error:
POST https://api.podcastindex.org/api/1.0/add/byfeedurl?url=https://podcast.npo.nl/feed/topix.xml
302
235 ms

POST https://api.podcastindex.org/api/1.0/add/byfeedurl?url=https://podcast.npo.nl/feed/topix.xml&itunesid=1533408249
500
305 ms

Ok, apparently iTunes IDs are automatically added within 24 hours. No need for me to contribute one by one.