Datadog: fix names in Span::spawnChild

The Bug and Its Fix
This is an additional fix for the bug described in https://github.com/envoyproxy/envoy/pull/29932.
There are still situations in which the spans produced by the Datadog tracer have the wrong name (operation name). We want all Datadog spans to be named "envoy.proxy", but sometimes they have another value which should instead be the span's resource name.
https://github.com/envoyproxy/envoy/pull/29932 addressed spans created by class Tracer, https://github.com/envoyproxy/envoy/pull/30503 (which was about something else) addressed name changes due to Span::setOperation, and this pull request that you are reading addresses spans created by Span::spawnChild.
For a little background, there was a substantial rewrite of the Datadog tracing extension within Envoy in October 2022. Since then, the modified code has slowly worked its way into Envoy releases, and then into Istio releases. One difference between the old code and the new is that the old code was OpenTracing-based, while the new code is not. While making the changes, I failed to notice that the "operation name" that Envoy uses is not the same notion as that used in Datadog. This pull request and those linked above are my identifying all of the places where that confusion of terms appears.
This pull request changes the last inappropriate setting of a Datadog span's operation name, and adds dedicated unit tests to centralize and clarify the expected behavior.
Please tag this pull request for backport review. It fixes a bug that affects the v1.27 and v1.28 release branches. I'm happy to propose those backports once this pull request is reviewed.
Testing
See the new naming_test.cc and the modified span_test.cc.
Other Info
Commit Message: "Datadog: fix span name in Span::spawnChild"
Additional Description: see above
Risk Level: low
Testing: see included unit tests
Docs Changes: N/A
Release Notes: see included changes to changelogs/current.yaml
Platform Specific Features: N/A

Thanks for taking a look, @adisuissa.

This seems to be a user-facing change. Please add a runtime guard around this to allow users to migrate this over time.

This is a fix for a bug. I'd prefer that users automatically got the fix when upgrading, as opposed to having to enable some option to get the behavior they had before the bug was introduced.

/backport

Thanks for taking a look, @adisuissa.

This seems to be a user-facing change. Please add a runtime guard around this to allow users to migrate this over time.

This is a fix for a bug. I'd prefer that users automatically got the fix when upgrading, as opposed to having to enable some option to get the behavior they had before the bug was introduced.

Yeah, having it runtime guarded doesn't imply it will be false-by-default. It should be true-by-default, but allows Envoy users to disable it (hopefully for a short duration) while making any changes needed in the rest of their system.

Hello everyone,
developers at Wayfair actively use DataDog tracing for Istio-enabled workloads, and this functionality is currently partially broken on Istio v1.17 and newer. I understand it's the holiday season, but we would be grateful if you could help merge this change.

This is a fix for a bug. I'd prefer that users automatically got the fix when upgrading, as opposed to having to enable some option to get the behavior they had before the bug was introduced.

The runtime guard can (and should) be enabled by default. It just allows safer migration across a fleet if one detects a problem with the new code until it is completely rolled out.
That said, I'll leave it up to the owners of this extension to decide.

Thanks again, @adisuissa. My teammates and I will look into runtime guards for future changes, knowing now that it's an option.


Swift 3 support

Hi,
Since now Swift 2 is deprecated, when swift 3 support will come?
Thank you.
-Bee

Hi, I already have a Swift 3 version, but I had to stop the project for a while because of a few final exams. I will upload the latest version as soon as possible!

The Swift 3 version is online now ;)

Thank you! 😊


Add/fix python repr interface for 2d lines/points

This implements a missing __repr__ for ConstPoint2d and fixes a bug in __repr__ for LineString2d

Please merge the CI fix from master into these PR branches so the CI pipeline can run successfully (which is needed for merging)  :smile:


Street addresses do not parse if they end in "United States"

text = '3120 W 1200 N, WEST POINT, Utah 84015 United States'
StreetAddress::US.parse text                            #=> nil

This issue seems to be resolved in the current master branch. I added the current master branch in my Gemfile and was able to Parse addresses ending in "United States"
 text = '3120 W 1200 N, WEST POINT, Utah 84015 United States'
 StreetAddress::US.parse text
 => #<StreetAddress::US::Address:0x007fc951df3c08 @number="3120", @street="1200", @prefix="W", @suffix="N", @city="West Point", @state="UT", @postal_code="84015", @redundant_street_type=true, @street_type=nil>


AppConfigurationProviderChangeLog

Description
Updating Change Log for Beta release.

API change check
API changes are not detected in this pull request.


⚠ Bofrost.lu has degraded performance

In 95ac483, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1868 ms

Resolved: Bofrost.lu performance has improved in 6cf20d7 after 6 minutes.


Add traverse

Codecov Report

Merging #72 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #72   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines         450    451    +1
=====================================
+ Hits          450    451    +1

Impacted Files
Coverage Δ

src/partial.lenses.js
100% <100%> (ø)
:arrow_up:

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 86ce235...e132a35. Read the comment docs.


gogs: 0.11.91 -> 0.12.3

Motivation for this change
Upstream release: https://github.com/gogs/gogs/releases/tag/v0.12.3
FIxes:

https://nvd.nist.gov/vuln/detail/CVE-2020-15867
https://nvd.nist.gov/vuln/detail/CVE-2020-14958
https://nvd.nist.gov/vuln/detail/CVE-2020-9329
https://nvd.nist.gov/vuln/detail/CVE-2018-15178

Things done

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

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

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

Result of nixpkgs-review pr 102061 1

1 package built:

gogs

Closure size comparison:
/nix/store/lffwq0nv4djkbwmxsv0a67z84q2ql8bf-gogs-0.11.91          448391248  # before
/nix/store/4isb92hw8ivgw1s00wj6qsn94wfw1vxb-gogs-0.12.3           444369544 # after

Result of nixpkgs-review pr 102061 run on x86_64-darwin 1

1 package built:

gogs

Result of nixpkgs-review pr 102061 run on x86_64-linux 1

1 package blacklisted:

tests.nixos-functions.nixos-test

1 package built:

gogs

Please squash the commits together.

Result of nixpkgs-review pr 102061 run on x86_64-darwin 1

1 package built:

gogs

Can we backport the update without making a breaking change in the NixOS module?


Fwd gemm is crashing with int8 and group_count > 1

Here are 3 driver commands:
> bin/MIOpenDriver convint8 -F 1 -x 1 -y 1 -c 8 -g 1 #int8, group_count == 1
> bin/MIOpenDriver conv -F 1 -x 1 -y 1 -c 8 -g 4 #float, group_count > 1
> bin/MIOpenDriver convint8 -F 1 -x 1 -y 1 -c 8 -g 4 #int8, group_count > 1

The first and second run just fine. The third one crashes on the run stage. I have found this behavior because I have actually found the code responsible for that.
On the find stage, we have an int8 check on the outside with no group_count check in the int8 case.
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/5edf26d95e3840b21e9137e08d5e0661f91ad851/src/ocl/convolutionocl.cpp#L499
On the run stage, we have a group_count check on the outside with no int8 check in the group_count > 1 case.
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/5edf26d95e3840b21e9137e08d5e0661f91ad851/src/ocl/convolutionocl.cpp#L1129
So for int8 && group_count > 1 case we have an evaluation inconsistent with run. Moreover, run treats it as a float case, I think.
It blocks #473.
Here are the logs for the commands:
g1log.txt - int8, group_count == 1, works fine
fp_g4log.txt - float, group_count > 1, works fine
g4log.txt - int8, group_count > 1, crashes

@ce1adon Please have a look. This holds GEMM solvers/invokers work, which is important. Thanks.

@atamazov Did you enable or disable cache?

BUILD_DEV=On, so binary cache is disabled. @DrizztDoUrden to confirm.

I didn't enable cache manually, but I have DUILD_DEV=On, so it should be disabled.

@atamazov  int8 && group>1 is a new feature to us. You can disable it at this point and request in issues.

So it's not allowed for now?

So it's not allowed for now?

Yes, please disable it and then request this feature.

@ce1adon Please confirm that the following issue is fixed in develop:
$ ./bin/MIOpenDriver convint8 -F 1 -x 1 -y 1 -c 8 -g 4

then remove the bug label. Right now the issue still persists:
MIOpenDriver convint8 -F 1 -x 1 -y 1 -c 8 -g 4 -V 0
MIOpen(HIP): Warning [SetupFloats] Unsupported data types configuration: INT8xINT8xFP32
MIOpen(HIP): Warning [SetupFloats] Unsupported data types configuration: INT8xINT8xFP32
MIOpen(HIP): Warning [SetupFloats] Unsupported data types configuration: INT8xINT8xFP32
MIOpen Error: /home/atamazov/github/MLOpen1/src/gemm_v2.cpp:990: rocBlas error encountered
RunForwardGPU() failed, rc = 0x5

@ce1adon @DrizztDoUrden
AFAICS this holds GEMM solvers/invokers work, which is important.

@atamazov int8 with group convolution is not implemented yet. Please request this new feature with issue or ticket.

Yes, but then the library should fail in controllable way, before rocblas. @DrizztDoUrden Could you please make appropriate fix in the library?

Do you mean to fix it outside of the gemm solver PR?

I do not care. What is important is to open path for your gemm solver work.


Remove empty parent directories from tree view on deleting a note

Lets say the note tree is as below
root
|-- dir1
|    |-- dir2
|    |    |-- dir3
|    |         |-- note1
|    |-- dir4
|         |-- note2
|-- dir5
    |-- note3

When the user deletes note1 then dir3 and dir2 should also be removed. Since they will be empty otherwise and has no use. Even git also removes the empty directories. So it is better to delete the empty parents on deleting a note.
The algorithm for deleting tree node should handle this scenario.

Done


My React App is deployed on Cpanel linux server . but cant reload page get error 404.

My React App is deployed on Cpanel linux server . but cant reload page get error 404.
My App is running home page perfectly but when i reload other page its give error 404 not found . however when i click button so it is run perfectly . please guide if i goes to wrong . Thanks

Please provide the repro and deployed instance

Almost certainly an issue with your server config. You need to make non-root requests redirect to your index.html. Read this section from the docs.


Fix "Run a URL" screen saver

I have tried different urls for the "Run a URL" screensaver, but they all just show a black screen.  I then saw on this page that they were unsuccessful as well: https://www.ghacks.net/2021/02/11/before-dawn-is-an-open-source-program-that-has-many-cool-screensavers/
What "load_url" should I use?

Hi @jesseolsen thanks for reporting this! I just pushed out a new release that should fix this problem.


docs: be more explicit about required fields

I spent an hour or two trying to figure out why I couldn't get the examples to work, then noticed it was delegating the client lookup to Doorkeeper::OAuth::Client.authenticate, which requires client_secret.

Hi,
many thanks for your interest and contribution!
Before going on with this PR, I'd first like to check something with you. My hesitation is about the very necessity of the client_secret, for both the Device Authorization Request and the Device Access Token Request (polling).
Using a client secret in this context seems at least unusual in principle, being the client almost certainly a "public" app.
Going further, I looked again at the RFC (respectively here and here), which is the original source of the POST request examples. The specs never mention a client secret - as far as I can see, not even indirectly. So, maybe, using a secret is even against the specs? (that's really a genuine question from my side!)
Last but not least, there's our naive sample application https://github.com/exop-group/doorkeeper-device-flow-example, which should work well with client requests closely modeled on the examples from the RFC (and readme).
Now, forgetting about the theory, I'd like in practice to better understand your use case, and possibly to reproduce a setup where I can get your original problem, that is, where the secrets are required in those requests to make them succeed.
Can you identify some obvious configuration settings that could explain that behavior? Or, if not, maybe you can just list your current ruby & gems versions, so that I can start making some attempts?
Thanks,
Marco

I discovered the source of my troubles: Doorkeeper::Application#confidential. Setting that field to false allows me to omit the client_secret.
Thanks for pointing out my mistake!


[tflite] CONV_2D with bias tensor index -1 causes type-mismatch RuntimeError

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): r1.13.1
Python version: 3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
I have created .tflite with single CONV_2D op with bias tensor index -1(= optional).
When supplying bias tensor -1(for making bias optional), it raises RuntimeError when running it in Python interpreter as shown the below(or seg fault/asan error in C++ interpreter)
Supplying zero-valued bias tensor(i.e. use valid tensor id for bias) passes AllocateTensors and Invoke without any problem.
FYI, we cannot omit bias tensor(i.e, len(inputs) = 2) since in such case we'll hit another assertion:
https://github.com/tensorflow/tensorflow/blob/r1.13/tensorflow/lite/kernels/conv.cc#L237
Describe the expected behavior
As described in tflite document:
https://www.tensorflow.org/lite/guide/ops_compatibility
CONV_2D should accept optional bias tensor and does not raise RuntimeError.
Code to reproduce the issue
Simply run python interepreter with attached .tfite file.
import sys

import numpy as np

import tensorflow
print(tensorflow.__version__)
from tensorflow.lite.python import interpreter as interpreter_wrapper

interpreter = interpreter_wrapper.Interpreter(model_path=sys.argv[1])
interpreter.allocate_tensors()

input_details = interpreter.get_input_details()
output_details = interpreter.get_output_details()

print(input_details)
print(output_details)

conv2d_bias_optional.tflite.zip
Other info / logs
Traceback (most recent call last):
  File "bora.py", line 10, in <module>
    interpreter.allocate_tensors()
  File "/home/syoyo/miniconda3/envs/onnx-chainer/lib/python3.6/site-packages/tensorflow/lite/python/interpreter.py", line 73, in allocate_tensors
    return self._interpreter.AllocateTensors()
  File "/home/syoyo/miniconda3/envs/onnx-chainer/lib/python3.6/site-packages/tensorflow/lite/python/interpreter_wrapper/tensorflow_wrap_interpreter_wrapper.py", line 106, in AllocateTensors
    return _tensorflow_wrap_interpreter_wrapper.InterpreterWrapper_AllocateTensors(self)
RuntimeError: tensorflow/lite/kernels/conv.cc:247 bias->type != input_type (0 != 1)Node number 0 (CONV_2D) failed to prepare.

@syoyo Is this still an issue for you? If this is still an issue, Can you please share the model code. I tried loading your tflite model but noticed some error as shown in this gist.
Thanks!

We are not using tflite anymore and does not plan to try to reproduce an issue, so you can close the issue.


Get Cirque build running on sve branch

Problem
SVE branch is failing Cirque runs:
https://github.com/project-chip/connectedhomeip/runs/7633372407?check_suite_focus=true
Can someone please take a look?

fyi @mrjerryjohns


bug: PD Delay durations are converted to seconds in JSON export

Overview
Delay durations are converted to seconds on the JSON export, so when the protocol runs in the Run App, the duration is read as "0 minutes X seconds". For example, a 5 minute 0 second delay would read as "0 minutes 600 seconds" in the run app logs.
Note: I'm unsure if this is an issue with the PD export converting the time, or the Run App not converting the time

Current behavior
Durations are converted to only use seconds:

Steps to reproduce

Create a protocol in PD
Add a Pause step with a delay duration greater than 1 minute
Export the protocol and import it into the Run App
Run the protocol
Observe the duration item in the log

Expected behavior
Duration should be read as "X minutes Y seconds"

IMO, JSON delays should only specify seconds to avoid making the commands more complicated. Instead of only showing the seconds, Run Log could convert into h:m:s from seconds but if the PD user put "90 seconds" the Run Log would show "1m 30s".


Add Reddit URL

This Pull Requests adds the Reddit URL for Maxime and Brandon.
This will be used to beta test RedditStats, a tool to aggregate our community engagement on Reddit.

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

File
Status
Preview URL
Details

advocates/brandon-minnick.yml
:white_check_mark:Succeeded
View

advocates/maxime-rouiller.yml
:white_check_mark:Succeeded
View

validation/AdvocateValidation.csproj
:white_check_mark:Succeeded

validation/CloudAdvocateYamlModel.cs
:white_check_mark:Succeeded

validation/ImageService.cs
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Use ::after instead of div.modal-backdrop for modal backdrop

When we use modal component : We can found a DIV with the class modal-backdrop.
Why don't change architecture of component or use ::after tag for respect the HTML semantic ?

It's not possible to use :after since .modal-backdrop has a click handler on it.
Pseudo-elements are not part of the DOM, so you can't bind any events directly to them, you can only bind to their parent elements.

Since pseudo-elements cannot have an event bound to them, would it make sense to close this issue? While I agree ::after is semantically preferred, I'm not sure that there would be a clean and concise way to bind the click event to the backdrop to trigger closing it.

This might be too hacky, but... http://stackoverflow.com/a/23243996.

Closing since there are no planned changes here.


Add vim to Dockerfile

I've found that I needed to edit some files in the container.

This is kind of an anti pattern, any file that is edited in the container will be reverted on the next container restart, leaving the application in an undesirable state. If I understood the usecase a bit I might be able to come up with a more stable solution

I'm going off of what I saw in the catalog Dockefile. I've needed to use a editor in the deployed container before but there hasn't been one.

It's been for debugging or doing some one-off work, so I wouldn't expect the changes to persist between deployments.

Oof that was a mistake.


Fixed parsing panic when row has errors

Pull Request Description
Fixes parsing when there is an error in the middle of the rows

Future Release Comment
[Add description of your change, to include in the next release]
[Delete any or all irrelevant sections, e.g. if your change does not warrant a release comment at all]
Breaking Changes:

None

Features:

None

Fixes:

#81 #42

Codecov Report

Merging #82 (4e79662) into master (e3cd6b9) will increase coverage by 0.45%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master      #82      +/-   ##
==========================================
+ Coverage   48.35%   48.81%   +0.45%
==========================================
  Files          39       39
  Lines        4196     4204       +8
==========================================
+ Hits         2029     2052      +23
+ Misses       2020     2006      -14
+ Partials      147      146       -1

Impacted Files
Coverage Δ

kusto/internal/frames/v2/v2.go
39.13% <80.00%> (+21.09%)
:arrow_up:

kusto/internal/frames/v2/decoder.go
50.00% <0.00%> (+5.07%)
:arrow_up:

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 e3cd6b9...4e79662. Read the comment docs.


Correct Support Plate BC Constraining Rigid Motion

Removed rigid body motion by adding another nodeset to apply a zero BC. This prevents the plate from spinning around the center node.
Closes #413

I'd like to point out that the average strains in the gold files did not change even though the max displacements did change.

Job VTB Documentation on e4fd00b wanted to post the following:
View the site here
This comment will be updated on new commits.

Did the tests boxes fail? Can someone restart these tests?

All jobs on e4fd00b : invalidated by @GiudGiud
restart!

we should be good here soon. Just needed a small regold


Attendance Tracker

Initial Layout. Open for Changes. Also there was subtle request to add notifications for exceeding absents. work left on that

UI looks neat. Is data stored locally or Firebase?

The data is stored locally. This will have too many reads and writes so didn't want to involve Firebase.

Ideally, it should be stored online as user may re-install the app and entire data will be gone.
The free tier limit seems good enough for me.
https://firebase.google.com/docs/firestore/quotas#free-quota

I will make it to online Strorage.

Umm....Why close?
Restarting the work?


Mongoid - Activity base class is using STI

PublicActivity::Activity inherits from corresponding orm class, which is PublicActivity;:ORM::Mongoid::Activity.
This inheritance causes the presence of a "_type" field in every document, which is very redundant and useless and overloads database when using base model. Moreover it forces all queries to have a "_type" clause which degrades performance, and create an heavy index (non created by default...).
Since Activities can grow very fast (in my case, i have almost 10x more documents in activities than tracked models, and i don't track all actions yet).
Is there a way to avoid this inheritance ?
I would like to keep using this gem as long as possible before switching to a better solution that i don't have time to develop. Thank you :)

Actually, i just found a quick fix which seems to work with my project.
This changes pass tests with mongoid, but i did not tested with ActiveRecord.
Here is the quick (ugly) fix that i added to my initializer, just before adding some fields in class:
module PublicActivity
  Activity = inherit_orm("Activity")
end

This solution seems to work perfectly, i checked that kind_of? keeps working as expected, and it's possible that this change doesn't break depending applications. I'm running ruby 2.0.0 with rails 4.2.
You could maybe consider changing your Activity model definition to avoir STI, if it seems right.

Interesting, will definitely look into it! Had no idea Mongoid does it, as I'm not actively using any NoSQL databases.

I intend to get rid of anything other than ActiveRecord so closing this


transactional 注解支持指定 connection

[This message is created by hyperf-bot]
Hi @idxdy, this is a READ-ONLY repository, please submit your Pull Request to hyperf/hyperf repository, this Pull Request will close automatically.


Modify request

What is the feature you are proposing?
How to modify request? I want to sanitize input without zod or hono validator.
app.use(async (c, next) => {
  const json = await c.req.json();
  for (let key in json) {
    if (json.hasOwnProperty(key)) {
      if (typeof json[key] === "string") {
        json[key] = sanitize.parse(json[key]);
      }
    }
  }

  // How to modify request?
  c.setJson(json);

  await next();
});

Request cannot/should not be updated. In web standards the Request object is immutable.
You can use context variables instead when you update data and send it to your route that way.
If you have other questions, please post them in the discussions tab or join the Discord

How about this?
app.use(async (c, next) => {
  const json = await c.req.json();
  for (let key in json) {
    if (json.hasOwnProperty(key)) {
      if (typeof json[key] === "string") {
        json[key] = sanitize.parse(json[key]);
      }
    }
  }

  c.set("sanitized", jsonSanitize);
  await next();
});

app.json("/", (c) => {
  const sanitized = c.var.sanitized;
  // ...
});

It may be common and libraries like Express, will let you do it. I don't speak for Hono, but based off what I know, Hono follows web standards which do state the Request object is read only. Correct me if I'm wrong @yusukebe
The option I gave which is the same as the example @sor4chi provided would be your best option.

Hi @fzn0x
This method is used internally by Hono's Validator. We do not recommend that users use it directly, but you may do it this way.
app.use(async (c, next) => {
  const json = await c.req.json()

  // ...

  c.req.bodyCache.json = modifiedJson
  await next()
})

Hi @fzn0x
This method is used internally by Hono's Validator. We do not recommend that users use it directly, but you may do it this way.
app.use(async (c, next) => {
  const json = await c.req.json()

  // ...

  c.req.bodyCache.json = modifiedJson
  await next()
})

Cool!!

Thanks for anyone participated in this issue.


_tkinter.TclError: too many nested evaluations (infinite loop?)

Description
Attempting to run a synthesized netlist through openlane2 with tt07-based configuration. I manually converted the config.tcl to config.json for this test (wasn't sure if tcl deprecation was the cause), but the same error exists on both TCL and json.
Expected Behavior
Get past the configuration openlane step
Environment report
(venv) [petrisko@kk9 tt07-dll]$ openlane.env_info || python3 ./openlane/env_info.py
Failed to get Nix info: [Errno 2] No such file or directory: 'nix'
kernel: Linux
kernel_version: 4.19.53
supported: True
distro: centos
distro_version: 7
python_version: 3.11.4
python_path:
  - /mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/bin
  - /mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/lib/python311.zip
  - /mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/lib/python3.11
  - /mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/lib/python3.11/lib-dynload
  - /mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages
tkinter: True
container_info:
  engine: docker
  version: 20.10.17
  conmon: False
  rootless: False
nix_info: None

Reproduction material
Unfortunately, it seems to be failing before the reproducible test case can be built
Relevant log output
(venv) [petrisko@kk9 tt07-dll]$ openlane.steps create-reproducible --config src/config_patched.json -d .
Traceback (most recent call last):
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/bin/openlane.steps", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/openlane/steps/__main__.py", line 445, in create_reproducible
    step = load_step_from_inputs(ctx, id, config, state_in)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/openlane/steps/__main__.py", line 56, in load_step_from_inputs
    return Target.load(
           ^^^^^^^^^^^^
  File "/mnt/users/spin0/no_backup/petrisko/tapeout/tt07-flow/install/venv/lib/python3.11/site-packages/openlane/steps/step.py", line 799, in load
    raise StepNotFound(
openlane.steps.step.StepNotFound: Attempted to initialize abstract Step, and no step ID was found in the configuration.

config_patched.tcl.zip
config_patched.json.zip

Figured it out (kind of)! Manually building python with tcl/tk 8.6 instead of 8.5 gets rid of the error. 8.6 uses a stackless implementation which gets around the recursion limit. Not looking too much further since everything in this environment is super old ;)
Thanks!


arkd server does not autostart

Was unable to reproduce demo. When running demo commands, arkd asks for cli options and quits.
Reproduction Steps:
cargo run --bin arkd
Compiler Log
$ cargo run --bin arkd
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
warning: /home/cuarentaydos/Code/ARK/clArk/ark-lib/Cargo.toml: version requirement `0.101.1+0.21-final` for dependency `bitcoinconsensus` includes semver metadata which will be ignored, removing the metadata is recommended to avoid confusion
warning: field `master_xpriv` is never read
  --> arkd/src/lib.rs:94:2
   |
91 | pub struct App {
   |            --- field in this struct
...
94 |     master_xpriv: bip32::ExtendedPrivKey,
   |     ^^^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: associated items `amount` and `decode` are never used
  --> arkd/src/database/mod.rs:51:9
   |
46 | impl ForfeitVtxo {
   | ---------------- associated items in this implementation
...
51 |     pub fn amount(&self) -> Amount {
   |            ^^^^^^
...
61 |     fn decode(bytes: &[u8]) -> Result<Self, ciborium::de::Error<io::Error>> {
   |        ^^^^^^

warning: `arkd` (lib) generated 2 warnings
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.15s
     Running `target/debug/arkd`
Usage: arkd [OPTIONS] <COMMAND>

Commands:
  create
  start
  drain
  get-mnemonic
  drop-oor-conflicts
  rpc
  help                Print this message or the help of the given subcommand(s)

Options:
      --datadir <DATADIR>
  -h, --help               Print help
  -V, --version            Print version

Also tried the options with no luck :
start log:
$ cargo run --bin arkd start
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
warning: /home/cuarentaydos/Code/ARK/clArk/ark-lib/Cargo.toml: version requirement `0.101.1+0.21-final` for dependency `bitcoinconsensus` includes semver metadata which will be ignored, removing the metadata is recommended to avoid confusion
warning: field `master_xpriv` is never read
  --> arkd/src/lib.rs:94:2
   |
91 | pub struct App {
   |            --- field in this struct
...
94 |     master_xpriv: bip32::ExtendedPrivKey,
   |     ^^^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: associated items `amount` and `decode` are never used
  --> arkd/src/database/mod.rs:51:9
   |
46 | impl ForfeitVtxo {
   | ---------------- associated items in this implementation
...
51 |     pub fn amount(&self) -> Amount {
   |            ^^^^^^
...
61 |     fn decode(bytes: &[u8]) -> Result<Self, ciborium::de::Error<io::Error>> {
   |        ^^^^^^

warning: `arkd` (lib) generated 2 warnings
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.15s
     Running `target/debug/arkd start`
An error occurred: need datadir

need datadir

create log:
$ cargo run --bin arkd create
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
warning: /home/cuarentaydos/Code/ARK/clArk/ark-lib/Cargo.toml: version requirement `0.101.1+0.21-final` for dependency `bitcoinconsensus` includes semver metadata which will be ignored, removing the metadata is recommended to avoid confusion
warning: field `master_xpriv` is never read
  --> arkd/src/lib.rs:94:2
   |
91 | pub struct App {
   |            --- field in this struct
...
94 |     master_xpriv: bip32::ExtendedPrivKey,
   |     ^^^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: associated items `amount` and `decode` are never used
  --> arkd/src/database/mod.rs:51:9
   |
46 | impl ForfeitVtxo {
   | ---------------- associated items in this implementation
...
51 |     pub fn amount(&self) -> Amount {
   |            ^^^^^^
...
61 |     fn decode(bytes: &[u8]) -> Result<Self, ciborium::de::Error<io::Error>> {
   |        ^^^^^^

warning: `arkd` (lib) generated 2 warnings
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.22s
     Running `target/debug/arkd create`
error: the following required arguments were not provided:
  --bitcoind-url <BITCOIND_URL>
  --bitcoind-cookie <BITCOIND_COOKIE>

Usage: arkd create --bitcoind-url <BITCOIND_URL> --bitcoind-cookie <BITCOIND_COOKIE>

For more information, try '--help'.


Large dataset handling discovery

Manually ingest the Allen Institute Whole Taxonomy dataset so that it is available for download via Discover Portal and the curation API.
Possible impacts to investigate include, but not limited to:

cellxgene-schema
ingestion pipeline
Portal API
curation API

The scope of this epic specifically excludes:

displaying this dataset in Explorer
displaying this dataset using cellxgene desktop
integration into Cell Census v1.0

The above items will be considered separately in the future, sometime after 2023Q1. (specific time TBD)
Discovery from this exercise will be documented to use as input for future platform enhancements to enable regular, automated ingestion of large datasets. This work should include a spike to estimate the cost of implementing these enhancements.
Estimate the engineer time cost to manually ingest the Whole Taxonomy dataset so that it can be compared against the cost of implementing the platform enhancements required.

Note, as discussed, this objective will be deferred from 2022Q4 to 2023Q1.

Overlap with or dup of https://app.zenhub.com/workspaces/single-cell-5e2a191dad828d52cc78b028/issues/gh/chanzuckerberg/single-cell/365https://app.zenhub.com/workspaces/single-cell-5e2a191dad828d52cc78b028/issues/gh/chanzuckerberg/single-cell/245?

The original tracking/placeholder issue was What to do about embiggened datasets? but was broader in scope.

Keep both then? Or worth collapsing now?

Oops, sorry, @atolopko-czi , just saw your comments now. What to do about embiggened datasets? was closed, so we'll be tracking the work in this issue.


defined variable in function argument

defined naming of variable notifier but this is check consistency of naming convention :)

Thanks! :cake:


Add validate method for echo verb

The Flickr API has a couple validation endpoints, under flickr.test.  I think test is an ambiguous namespace and that validation is better suited.
I also pass a fixed parameter name and echo value in through this method, since exposing it to arbitrary parameter values doesn't serve a purpose.
I added a test, and also cleaned up a js-hint issue in the test.
Addresses: https://github.com/flickr/flickr/issues/1

Failing because it's dependent on https://github.com/flickr/flickr-api-swagger/pull/1

Need to bump the flickr-api-swagger dependency to 2.3.0 now that it's published.

Coverage increased (+0.006%) to 99.621% when pulling b71af6b3c5cd1b4dd7ca3de6aadfcc14801465a0 on alex-seville:echo into 5228f758a680cfded61c0f8a7d1942b56af7d1b2 on flickr:master.

Excellent, thanks!

👍


Adding a check for html direction in placing the grid-menu

The menu was always placed relative to the right, causing it in RTL to appear on the wrong side of the menu, far away from the button. I just added a check for the direction of the page and to place the menu relative to the left in RTL situations.

I have two recommendations:

Don't use jQuery's .context property, because it's deprecated.
Check the text direction of the actual grid header rather than the whole document, since the grid header is your anchor point for the menu. If there were ever both a LTR grid and a RTL grid in a LTR document, the menu would get placed incorrectly for the LTR grid.

See if you can use getComputedStyle to determine the text direction, e.g.
if (getComputedStyle(gridHeaderElement, 'direction') === 'rtl') { /* do stuff */ }}


Trend pytmv1 update to 0.9.0

Status
Ready.
Related Content Pull Request
The PR for code update has not been made yet.
Related Issues
Related: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.

Will make another PR with updated pytmv1 package.


react site designs manager

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

What's in this Pull Request?

New Sample React Site Designs Manager.

thx @joaojmendes - would you be interested in doing a live demo on this and tenant properties in one of the upcoming SPFx community calls? The theme would be something like - Admin web parts... and how to provide additional UI capabilities for your tenant administrators.


Add git-crypt to git image

git-crypt just landed on buildroot and it's a useful addition for stuff like https://github.com/concourse/git-resource/issues/7

@gabro Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@gabro Thank you for signing the Contributor License Agreement!

@gabro Thank you for signing the Contributor License Agreement!

@vito the latest stable release of buildroot (2017.02) now includes a git-crypt package. Do you reckon this can merged?

Hey there!
Are y'all also planning on making a PR to the git resource itself to add this support? It'd be great to have both to merge at once.
I can't see any immediate problems with this PR though, so I'll just wait until your response before merging.

Yep, that's the plan!
As soon as we have this merged we can work and test the API for the git resource :)
--
gabriele
~ buildo
On 28 Mar 2017, 18:58 +0200, Chris Hendrix<EMAIL_ADDRESS>wrote:

Hey there!
Are y'all also planning on making a PR to the git resource itself to add this support? It'd be great to have both to merge at once.
I can't see any immediate problems with this PR though, so I'll just wait until your response before merging.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/concourse/buildroot-images/pull/5#issuecomment-289835570), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAqO5I-GoCuL87J8nY42aPo7icswm1Y6ks5rqTwsgaJpZM4Lxfve).

Great!


Add all theme colors

Currently, only some colors are in the project. To complete this, all colors must be in the lightTheme and the darkTheme.

[ ] Add accentOrange light
[ ] Add accentRed light
[ ] Add accentYellow light
[ ] Add primaryGreen light


org.hamcrest.Matchers.is not in hamcrest-core-1.3.jar

I built JADX from gradlew build without complaint, however trying to use it from Eclipse fails because Eclipse complains that import static org.hamcrest.Matchers.is; doesn't exist
The method is(String[]) is undefined for the type TestEnums4.TestClsTestEnums4.java/jadx/jadx-core/src/test/java/jadx/tests/integration/enums
It seems that the 'is()' method is in the CodeMatchers class (and is deprecated).  Should the jadx code be updated to use CodeMatchers, or do I have the wrong version of hamcrest-core-1.3.jar?  I think that hamcrest wouldn't change the class method signatures and keep the same 1.3 version number.  (Gradle downloaded the version of hamcreat-core-1.3,jar)
What's the problem here?

This works as of now, with gradle and with Eclipse.


Overhaul sending / corking

I made some prototype where corking is done in user space and not via the kernel TCP_CORK feature and the difference in batched scenarios is major: I can get from max 5 million echoes/s before, to well over 30 million. It also improves throughput of HTTP pipelining and similar cases.
This is also needed to get corking cross-platform as Windows has no TCP_CORK and FreeBSD & OS X has limited support via TCP_NOPUSH. With user space corking the networking syscalls would be fully cross-platform so it's good for compatibility as well.

After lots of thinking it all comes down to not being a problem. Sure, you can improve this but it won't make any difference in real world use cases.
What makes a lot more sense is to focus on pub/sub fundamentals because it is here the real problem is: pub/sub is astronomically inefficient in all implementations I have seen and here is where help is needed: some kind of pub/sub batching abstraction that can easily be used to boost broadcasting / pub performance thousands of times. People simply do not understand how to properly cork / delay publishes.

Implemented in µS

i'm seeing a consistent 200ms(+) latency on linux/epoll while processing http post requests. i'm not networking expert, but it seems like something to do with nagle's default timeout.
i'm not seeing any delay in much less powerful windows 7/libuv virtual machine.  application code is identical between windows and linux. single thread hub. (no websocket yet, just plain http server) actual processing time within application code is less than 10ms.
problem happens on popular browser like chrome, firefox and opera.
with a libcurl client in C, it is harder to reproduce as it uses larger packet size to do POST.
is there any setting in the library to control it?


Django TimeField gives 'datetime.time' object has no attribute 'microseconds' when querying its model's 'sa' attribute

Steps to reproduce

Python 2.7.6, pip==9.0.1, Django==1.10.5, MySQL-python==1.2.5, aldjemy==0.6.0
Create a model with TimeField
Do necessary migrations
Create an object of the models using django's "objects.create()". You can give either a string or a datetime.time or datetime.datetime instance for the field.
Create a session using aldjemy.core.get_engine()
session.query(<model name>.sa).all() or <model name>.sa.query().all() gives the error

Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "~/.virtualenvs/test/local/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2638, in all
    return list(self)
  File "~/.virtualenvs/test/local/lib/python2.7/site-packages/sqlalchemy/orm/loading.py", line 90, in instances
    util.raise_from_cause(err)
  File "~/.virtualenvs/test/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "~/.virtualenvs/test/local/lib/python2.7/site-packages/sqlalchemy/orm/loading.py", line 75, in instances
    rows = [proc(row) for row in fetch]
  File "~/.virtualenvs/test/local/lib/python2.7/site-packages/sqlalchemy/orm/loading.py", line 437, in _instance
    loaded_instance, populate_existing, populators)
  File "~/.virtualenvs/test/local/lib/python2.7/site-packages/sqlalchemy/orm/loading.py", line 498, in _populate_full
    dict_[key] = getter(row)
  File "~/.virtualenvs/test/local/lib/python2.7/site-packages/sqlalchemy/dialects/mysql/types.py", line 413, in process
    microseconds = value.microseconds
AttributeError: 'datetime.time' object has no attribute 'microseconds'

This is possibly because Django converts the MySQLdb given datetime.timedelta to datetime.time which is then given to SQLA but it was expecting datetime.timedelta.

Wow, that's quite interesting behavior. @tackler, do you have a suggestion on how we could address this, or is it best to leave it to user code? I tend to feel that making either Django or SQLAlchemy work differently than they were designed is unwise.


Can someone help me: how to sign transactions with private keys, which API? I'm a green hand, thank you very much.

Can someone help me: how to sign transactions with private keys, which API? I'm a green hand, thank you very much.

@MasterYong Try using:
let (serializedSignature, rawSignature) = SECP256K1.signForRecovery(hash: Web3.Utils.hashPersonalMessage(dataToSign)!, privateKey: privateKey)

Thank you. I'm not sure what I should do next for this example. How to sign and send after obtaining“tx”.
let value: String = "1.0" // In Ether
let walletAddress = EthereumAddress(wallet.address)! // Your wallet address
let toAddress = EthereumAddress(toAddressString)!
let contract = web3.contract(Web3.Utils.coldWalletABI, at: toAddress, abiVersion: 2)!
let amount = Web3.Utils.parseToBigUInt(value, units: .eth)
var options = TransactionOptions.defaultOptions
options.value = amount
options.from = walletAddress
options.gasPrice = .automatic
options.gasLimit = .automatic
let tx = contract.write(
"fallback",
parameters: AnyObject,
extraData: Data(),
transactionOptions: options)!

tx.send()

Thank you very much. I made it. I want to complete the ERC721 transaction. Could you please provide me with an example?
😅 I'm sorry I'm asking too much·


Switch internal FontAwesome uses to their React inline SVG versions

FontAwesome maintains react-fontawesome which provides a FontAwesomeIcon component. This component inlines an svg element which renders the icon (so no webfont at all).
In testing on Prospectus, this saved us having to have new users download all four Pro FA icon files (~430KB) and saved another 12KB (compressed) in FA CSS on the pages.
Not to mention, it means that consumers of Prospectus are no longer tied to FontAwesome 4.0 webfonts.
Everywhere we internally use FA icon class names, we should instead use a FontAwesomeIcon component.
Related tickets:
https://github.com/edx/front-end-cookie-cutter-application/issues/178
https://github.com/edx/frontend-component-footer/issues/21

We should also consider dropping (or reworking) Icon? FontAwesomeIcon seems like a replacement.

With https://github.com/edx/paragon/pull/600 we now have a Paragon solution for icons.


ERROR installing the plugin

Hey,
Im trying to install the plugin on a "naked" app.
but somehow i get tons of errors just after that.

no other applications were installed.
tried the same thing before / after formatting my Mac.
tried the same thing in 4 different apps.

But still  i get the errors. (especially: "The import com.google cannot be
resolved")
also it seems like the installer did not change the required parameters in androidManifest:
i found these lines in AndroidManifest.xml:

(${applicationId} did not changed)
*anyway this is not the main problem because manually added the AppID but still got tons of other errors.
m

I assume it is something stupid and easy but im kinda new, so i'll appreciate any help :)
Thank you!
Guy

@guyCactus it looks like your main problem is you did not add the required libraries to your Android environment.
https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/INSTALLATION.md#compilation
Also, the ${applicationId} is an variable that is set a build/run time and does not get changed in the gradle files so don't worry.

All of the required libraries are installed.
Now its working great but i needed to add all of the Jars manually.
Do you have any idea why eclipse does not import them automatically after the SDK manager finish downloading them?
Thank you :)

@guyCactus because the Android community has, for the most part, moved from Eclipse to Android Studio. Android Studio uses Gradle to automatically include those frameworks for you. My recommendation is to move to Android Studio as Cordova Android now uses Gradle/Android Studio.


Consider only showing builders in object literal completions its contextual type has an index signature

Since users are no longer allowed to have excess properties in an object literal, it might be appropriate to only show a builder when the contextual type of an object literal has no index signature.
For instance:
type T = { x: string; y: number; };
function f(param: T) {
}

f({ /*$*/ }); // should only allow 'x' and 'y' and no builder.

However, this may not be sufficient; in the presence of a type assertion, one actually does want to allow completion, since this is one of the recommended workarounds anyway:
type T = { x: string; y: number; };
function f(param: T) {
}

f(<T>{ /*$*/ }); // should only allow 'x' and 'y' and no builder.

Seems like a good idea

Though I recall another edge condition is that we would need to allow a builder for the empty type as well.

I believe you would also want a builder when the contextual type is from a type assertion, because you are allowed to specify extra properties there as well.
You may want to look at isKnownProperty in the checker for inspiration.

@JsonFreeman sorry that's what I originally meant, I wrote "completion" instead of "a builder" in the original issue.

Yes, but I meant that maybe the builder would always be shown in a type assertion.

Right, that was what I was getting at. And actually there's another problem - consider the following:
function f(options: FooOptions): void;
function f(options: BarOptions): void;
function f(options: any) { }

Provided that FooOptions and BarOptions are non-empty and distinct, if you supply an empty object literal to f, you are potentially going to only get BarOptions (since resolution would fail on FooOptions and settle on BarOptions).
This would be bad experience. We should either supply properties from both FooOptions and BarOptions or not force completion.

I think that is a different issue. You'd need to detect whether multiple overloads are involved in obtaining the contextual type, and decide on a policy for this case. I think it may be acceptable to pick one and show a builder. Alternatively, you could try to collect them from all the overloads, but I think that would be complicated, and not that useful. I would also try to have completion and signature help agree on which overload the user is likely trying to call.

We'd rather error on the side of not restricting the typing here.


(zotero) add 64-bit installer

This adds the new install option for 64-bit Zotero and simplifies the update a bit.
Description
Modified the update.ps1 to grab both 32-bit and 64-bit installer URLs, download the EXEs and replace the information in the VERIFICATION.txt file.  Modified chocolateyinstall.ps1 to install either 32-bit or 64-bit flavor of Zotero.  Also simplified the VERIFICATION.txt file and chocolateyinstall.ps1 and chocolateyuninstall.ps1 files to require fewer (or no) edits via update.ps1.  Re-arranged metadata in the .nuspec to match the order of a new package.  Updated the LICENSE.txt file to match changes at the project.
Motivation and Context
32-bit Zotero works fine on 64-bit systems, but regularly pops up a dialog indicating that it's not the most efficient version for the environment.  The upgrade from 32-bit to 64-bit is as simple as a re-install, so fixing this package to have both bit-levels was fairly straightforward.
How Has this Been Tested?
Installed the current, 32-bit-only, v7.0.5 package then upgraded to proposed v<IP_ADDRESS>40930 package with no trouble.  Also installed the proposed package without upgrading.  Uninstalls worked too.
This was on Win11 system with Chocolatey v2.3.0.  There is no reason to suspect the official test environment would have any issues because the script functions are exactly the same, just with the addition of the 64-bit installer.  I don't have ready access to the official test environment, so someone else will have to test that if it is absolutely necessary.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the Chocolatey Test Environment(https://github.com/chocolatey-community/chocolatey-test-environment/). Note that we don't support the use of any other environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

I have now tested install and uninstall in the test-environment:

Apologies for my ignorance here, but is there anything I need to (or can) do about the the All checks have failed and This branch has conflicts that must be resolved messages?

I don't know what the "checks" are or what has failed.
I don't understand what the conflicts are or why there are only 3 when 7 files are changed by the PR or how to resolve them.

Thanks.

Apologies for my ignorance here, but is there anything I need to (or can) do about the the All checks have failed and This branch has conflicts that must be resolved messages?

I don't know what the "checks" are or what has failed.
I don't understand what the conflicts are or why there are only 3 when 7 files are changed by the PR or how to resolve them.

Thanks.

The in this case is the appveyor build that runs on the PR, it is failing due to conflicts in the files.
A conflict means that the file have changed in the repository you are attempting to create the PR into, and it can not be automatically resolved in this case. The files it mentions are the ones that are in conflict. I do not have any documentation at the moment, but do a google search on solving git conflicts (you will see these conflicts when doing a git rebase most likely).

Again, ignoramus here.  I've adjusted the files in my fork/branch, but I don't know how to rebase it.  Is it possible in the web GUI or in GitHub desktop?
Thanks.

Again, ignoramus here. I've adjusted the files in my fork/branch, but I don't know how to rebase it. Is it possible in the web GUI or in GitHub desktop?

https://docs.github.com/en/desktop/working-with-your-remote-repository-on-github-or-github-enterprise/syncing-your-branch-in-github-desktop#rebasing-your-project-branch-onto-another-branch


How to set user name, email & other details ?

Through identity "mixpanel.identify("13791");" we can create a user how to add name, email & other properties which marked in the screen shot

Looks like you can call mixpanel.getPeople.set(propertyName, value)

Looks like you can call mixpanel.getPeople().set(propertyName, value)

Thanks for the syntax I came through this same syntax in the documentation, what the exact syntax to change the property for,

Email
Updated at
CountryCode
Region
City

I tried to set it like this
trackAnalytics.getPeople().set("Name", _userUseCase.getEmployeeName());  trackAnalytics.getPeople().set("Email", _userUseCase.getEmployeeEmail());
these properties are added but it's not reflected in the column list item for each user. how to change that?

Use $name and $email as the property names. This document has a full list of the reserved property names:
https://help.mixpanel.com/hc/en-us/articles/115004708186-What-is-the-difference-between-Event-Properties-Super-Properties-and-People-Properties-and-which-should-I-use-

Use $name and $email as the property names. This document has a full list of the reserved property names: https://help.mixpanel.com/hc/en-us/articles/115004708186-What-is-the-difference-between-Event-Properties-Super-Properties-and-People-Properties-and-which-should-I-use-

Hi Bud saw this doc too, this is the error I got when I tried using the dollar symbol, see the image below

It forces me to create a variable for email & that is not wrong with flutter because that is how it works, so what's the proper syntax for it, what I'm missing.

trackAnalytics.getPeople().set("Email", _userUseCase.getEmployeeEmail());
through this above code, the addition email property is added to the user but not the default email, from the edit column option I made my added email to visible you can see that in the pic, but I want the use the default email property which I marked in the blue circle.
In the doc, it denotes we have to use $ symbol, but I'm not sure how to use.

Dart's "string interpolation" thinks you're trying to use the $ to insert a variable called Email there. You can use a \ to escape the dollar sign: trackAnalytics.getPeople().set("\$email", _userUseCase.getEmployeeEmail());

Dart's "string interpolation" thinks you're trying to use the $ to insert a variable called Email there. You can use a \ to escape the dollar sign, to tell Dart that it's just part of the text: trackAnalytics.getPeople().set("\$email", _userUseCase.getEmployeeEmail());

Thanks for the syntax this is what I'm searching for, thanks for your time.


Collection Export error

Describe the bug
Clicking Export button on Collection page redirects to an error page instead of giving the requested file.
To Reproduce
Steps to reproduce the behavior:

Go to My Arena > Collection
Click on 'Export'
Click on 'MTGGoldfish CSV'
Get redirected to https://mtgarena.pro/mtg/donew.php (message: "Hacker! Go home!" hahaha)

Expected behavior
Get the .csv file for download

I'm also getting this bug.

This issue raised after we have switched to new API. We'll fix it very soon

You're not a hacker anymore, it works now :)


create prepare_for_training method for text2text tasks

Is your feature request related to a problem? Please describe.
I cannot easily train text2text tasks
Describe the solution you'd like
should be similar to textclassifiaction
Describe alternatives you've considered
N.A.
Additional context
N.A.

Fixed in #2411


Is the vue2 version applicable

Is the vue2 version applicable ？

Hello, violet2422. No, this package is compatible with vue 3.x