Support for einops

Hi :)
I am a big fan of einops and I believe that supporting it within the framework would be highly valuable, especially for quick prototyping and situations where performance isn't the primary focus. Are there any plans to implement a feature akin to torch.einsum within the framework? If there's a plan for something like mlx.einsum and contributions are welcome, I'd be eager to contribute.

It seems that Apple MLX support was already proposed within einops.

I second that. einops saved me quite a few times where the logic was becoming a bit intractable.

We'll definitely keep this on the feature roadmap. I think if we had an einsum like NumPY integration with einops is doable. (Contributions welcome!)

Will also need a tile op to support einops

After #278 and #240 get merged, that should be all thats needed to create a backend for einops

Einops maintainer here.
Simplest way to get einops functions for framework is to implement array api.
einops.array_api works with all array-api compatible tensors (there is also support for scikit-learn and eindex).
It also simplifies prioritization of ops a lot for framework devs, as what's in the standard is a bare minimum.

We can close this as the latest MLX works with einops.array_api back-end.


Fixes issue#510

Related Issue

Closes: #510
Description of Changes
Reduced some contents
Added styling
Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[ ] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

I think your branch is not updated and please optimizse it for mobile mode.
see refund policy it is well designed

I think your branch is not updated and please optimizse it for mobile mode. see refund policy it is well designed

Okay alright

@anmode I made it optimized for mobile devices, if any changes to be made, please let me know.

   @anmode I made it optimized for mobile devices, if any changes to be made, please let me know.

@anmode

Table of contents still not look good in mobile view, just change text size as this privacy policy is so large ...
Only change for this page. in mobile view please

Table of contents still not look good in mobile view, just change text size as this privacy policy is so large ... Only change for this page. in mobile view please

Okay sure

Reduced font size of headings. Please check this out.

left you preview comments,

https://github.com/anmode/grabtern-frontend/assets/91741581/60e1f218-0509-428e-829b-ce08a20f063a
The changes being mentioned.

@anmode please review

Good, but text uniform ni h..
see font types kch toh gadbad h.... same font ni h poore page k

Good, but text uniform ni h.. see font types kch toh gadbad h.... same font ni h poore page k

Ab ye kr skte hai ki para's mein jaha jyada bold letters hai, uski font-weight km krdu

Good, but text uniform ni h.. see font types kch toh gadbad h.... same font ni h poore page k

Ab ye kr skte hai ki para's mein jaha jyada bold letters hai, uski font-weight km krdu

okk....nd font face bhi alag alag h boht jagah

https://github.com/anmode/grabtern-frontend/assets/91741581/9ad42481-f78d-467d-96fc-fa3e3ba04c54
Now, I hope the font is uniform everywhere.
I reduced the boldness also. Please let me know if any changes needs to be done.

@anmode Please review the changes being made

Vidip I throughly checked.. the page is still not reponsive.
May be it really needs to be redesigned... We can have meet again. i'll explain.


Keep new line at end of file in yamlprocessor

What this PR does / why we need it:
Currently, yamlprocessor doesn't respect new line at end of file if the input file contains it or not.
This behavior causes unnecessary differences and should be corrected.
For example, EventWatcher generates these changes.

Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

Keep new line at end of file in yamlprocessor

@kurochan there is a failed test, pls re-check it 😄

@khanhtc1202
I'm struggling on test fail on pkg/app/piped/executor/kubernetes/kubernetes_test.go .
The following differences appear and I haven't come up with a good fix yet 🤔
Diff:
--- Expected
+++ Actual
@@ -2,3 +2,3 @@
 data:
-  envoy-config: |-
+  envoy-config: |
     admin:
TestPatchManifest/multi_ops_with_a_given_field

Do you have any ideas to fix this differences?

@kurochan Probably it's caused by this convention
https://stackoverflow.com/questions/3790454/how-do-i-break-a-string-in-yaml-over-multiple-lines#:~:text=Block styles with block chomping indicator
So I think your change should support all YAML convention includes: >, | and its mix with -, + etc


python3Packages.behave: disable tests

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/122042
Tests were failing and the newest commit didn't fix it
Things done

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

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

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

👀 i'm having trouble with git
bare with me


Question: Drag and drop support for sorting?

Hi just have a small question: do you have any plans to add drag and drop support for dropzone?
Regards ripers

Hi @ripers
Unfortunately not any time soon, to be honest that functionality has never crossed my mind.
Having said that we'd be open to contributions if anyone wanted to have a go implementing it :)

I'm going to close this issue because I have no intentions of pursuing it, as mentioned above if someone in the community would like to tackle it they are welcome


User input preprocessing

I proposed some changes to the code, now the user input gets through a preprocessing dictionary that binds all the possible keywords ("cd", "go" etc...) to a unique internal representation ("cd" in this case) :book:
This should make the searches a bit faster :rocket:, because python won't have to iterate through the lists each time a new input is given. More importantly this shortens the code :wink:
I also proposed some some minor edits about text processing, for instance I added a lstrip to remove leading white spaces and I also factored some calls to str.lower in places :+1:

Great!
Thank you very much, it is indeed cleaner now 👍


⬆ Electron 11.5.0

Requirements for Contributing a Bug Fix (from template, click to expand):

Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix an existing bug. To contribute other changes, you must use a different template. You can see all templates at https://github.com/atom/.github/tree/master/.github/PULL_REQUEST_TEMPLATE.
The pull request must update the test suite to demonstrate the changed functionality. For guidance, please see https://flight-manual.atom.io/hacking-atom/sections/writing-specs/.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see https://github.com/atom/.github/tree/master/CONTRIBUTING.md#pull-requests.

Identify the Bug

https://github.com/atom/atom/pull/22687#issuecomment-911689201
The existence of Electron 11.5.0 (the final release of the Electron 11.x series) was pointed out by @mfonville in the main Electron 11 upgrade PR. (See comment linked above). The bug is... We're out of date!
Description of the Change

Update Atom to use Electron 11.5.0 instead of 11.4.12. The only changes in this Electron release are a few security patches cherry-picked from newer Chromium and V8. See the release notes:

https://www.electronjs.org/releases/stable?version=11#11.5.0
https://github.com/electron/electron/releases/tag/v11.5.0

Alternate Designs

No alternatives were seriously considered. (I like security patches, and I lack the ability to whip up, say, an Electron 12 upgrade right now...)
Possible Drawbacks

Probably none. These are really small security patches, hopefully they aren't buggy patches... :eyes:
Verification Process

Tests pass in CI at my fork: https://dev.azure.com/DeeDeeG/b/_build/results?buildId=1233
(Please disregard the failed "UploadArtifacts" job, that's CI-specific and I don't think anyone has gotten that to pass on forks of the Atom repo yet -- that failing only means I'm not running CI on the official atom/atom repo.)
Release Notes

⬆ Electron 11.5.0

Test failure is unrelated. It passed CI on my CI account, given enough chances to rerun. Failure appears to be, as usual, unrelated test failures that (unfortunately) happen sort of randomly on every branch.
I think it would be sensible to include this in 1.61-releases branch, because otherwise there will be 11.4.12 in the final Atom1.61... And Electron 11.5.0 just adds a few small security fixes cherry-picked from upstream Chromium and V8.

atom/.eslintrc.json


Helmraiser creates naming conflicts.

I am playing with helmraiser with the flux chart which creates a role named flux in each namespace I ask it to run flux against. When I run tk eval I see that there is only a single object named flux_role in the evaluated json.
This is because resources get added to the json with only $NAME_$KIND as the key. Code here.
This leads to a few competing concerns:

The keys need to be unique so as to not cause conflicts / overwriting keys.
The keys need to be usable and consistent to make later jsonnet overrides easier.

Possible solutions:

Always name things $NAME_$KIND_$NAMESPACE.

fully explicit
we might not know the namespace until later (although I think we should set the namespace in the helm command. separate issue).
still a pain to access by a dynamic json key.

Keep naming as is unless the namespace differs from the spec namespace, then append it.

will usually act as it does now.
usually easier to consume / override.

Somehow make things a map by namespace, either at the top level, or inside child levels

still kinda hard to pull things out with jsonnet by dynamic namespace.

In any case, I'd vote that an error would be preferable to silently overwriting objects.

I can also work around this particular case by postprocessing the jsonnet and making copies of the object in question, but that isn't a great solution long term.

@captncraig A thought I while reviewing Helmraiser was that it should not hardcode the name format at all, but accept it from Jsonnet, possibly as a Go template the same way the export filename works.
helm-util could pick a sensible default here, e.g. {{.metadata.name}}_{{.kind}}. This should work in many cases.
In special ones like yours, you can use a different template. You then also know exactly how things will turn out, which makes it clear how to mixin.
wdyt?

I like that on the surface. But my concern is that this is a particularly well hidden kind of bug. I didn't think about json keys until like 4 levels of debugging why my objects were not getting created in the cluster. The json keys are pretty low level, and you aren't going to know you need to change them until you have a problem that is frustrating you and you dig down into tk eval and the source of the plugin.
The json keys are an intermediate step between executing a helm template and creating k8s objects.
Perhaps your solution would be feasable, but we should certainly show a super helpful error message if we still encounter a conflict.

Shouldn't be too hard to just abort the helmraiser code in case this naming conflict manifests


Bump minimum supported torch version

Required for memory_format=torch.preserve_format

Codecov Report

Merging #260 (b786333) into master (8a1c8fd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #260   +/-   ##
=======================================
  Coverage   84.48%   84.48%
=======================================
  Files          25       25
  Lines        1573     1573
  Branches      357      357
=======================================
  Hits         1329     1329
  Misses        140      140
  Partials      104      104

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 8a1c8fd...b786333. Read the comment docs.

Codecov Report

Merging #260 (b786333) into master (8a1c8fd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #260   +/-   ##
=======================================
  Coverage   84.48%   84.48%
=======================================
  Files          25       25
  Lines        1573     1573
  Branches      357      357
=======================================
  Hits         1329     1329
  Misses        140      140
  Partials      104      104

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 8a1c8fd...b786333. Read the comment docs.


MY LLM-OPENAI- MODEL NAME shows "no  option",Can someone help me？TT

by default, flowise retrieves the list of models from a file and I guess due to proxy constraint your machine was not able to fetch the file, you can configure an env variable to specify your own path - https://docs.flowiseai.com/configuration/environment-variables#models

by default, flowise retrieves the list of models from a file and I guess due to proxy constraint your machine was not able to fetch the file, you can configure an env variable to specify your own path - https://docs.flowiseai.com/configuration/environment-variables#models

hello ，I tried, but it still didn't work TT


custom rbls

I would like to have custom rbls or at least the option to override the default selection. would supply a PR, where would I put such variable within target/postfix/main.cf (and default it to the current, so it does not break)?

I would also like to have an custom "append main.cf" var, so i could add
smtpd_tls_received_header = yes
to see detailes TLS headers, e.g.

Hi @tronicum, have you read the wiki?

yes, but i just want to add custom stuff, or customize options, not replace the whole configuration

It's an override. It keeps default config and change only what's provided in the override config.

you need to take care with newslines though (i copied the rbl lines and they need to be in one line (or mybe \ would work)


Support record delimiter ("terminator" in Arrow terms) for CSV reading

Is your feature request related to a problem or challenge?
Current CSV reading / writing already supports a bunch of options, like field delimiter and quote chars. However, record delimiter (usually something like "\n" or "\r\n") is not supported in DF. It (as "terminator") is supported in arrow-csv though, should be easy plumbing to add to DF as well.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

take


Image comes out unfinished in Chrome

I'm using html2canvas version 0.4.1.
The image occasionally comes out like this
 on Chrome. Notice the blurred part at the bottom.
I thought it could be a problem with my application,  but it works perfectly on Firefox.

Is this still an issue with v1.0.0? If so, could you please share an example on jsfiddle.


Add README translation to Brazilian Portuguese (pt-BR)

:brazil:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Merged! Thank you for your contribution. Much appreciated! 👍


Better logging for hitting provisioner memory limit

Version
Karpenter Version: v0.22.1
Kubernetes Version: v1.24.0
This is similar to #3267.  The log message karpenter generates when it fails to launch a node due to hitting a provisioner memory limit is (masking provisioner names for security):
Could not schedule pod, incompatible with provisioner "*****-provisioner", did not tolerate ******-dedicated=:NoSchedule; incompatible with provisioner "karpenter-provisioner", incompatible requirements, label "********-dedicated" does not have known values; incompatible with provisioner "**********-provisioner", no instance type satisfied resources {"cpu":"1","memory":"50Gi","pods":"1"} and requirements kubernetes.io/arch In [amd64], karpenter.sh/capacity-type In [on-demand spot], node.kubernetes.io/instance-type In [m5.2xlarge m5.4xlarge m5.large m5.xlarge], kubernetes.io/os In [linux], karpenter.sh/provisioner-name In [*******-provisioner], node.umbra.space/exclude-from-external-load-balancers In [true], *******-dedicated In [true] {"commit": "c4a4efd-dirty", "pod": "********/**********"}

Karpenter used to log using the following line of code which was much clearer in this situation: https://github.com/aws/karpenter-core/blob/0613466c72cfbc836d0df4c0f2bb54c790358978/pkg/apis/v1alpha5/limits.go#L36
Expected Behavior
Karpenter should use a clearer error message when hitting provisioner limits.
Actual Behavior
Karpenter logs an ambiguous error message.
Steps to Reproduce the Problem
Cause karpenter fail to provision a node due to memory limits.
Resource Specs and Logs
See about for logs.
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

I recently ran into a similar issue where the problem was the instance type that was needed was currently not available in the region.  The log message was basically the same as the one in this issue - very generic.  I had to manually try to launch an instance with that type to see what the real problem was.  And like @bwmetcalf pointed out in that #3267, that one has the same problem.

This is similar to https://github.com/aws/karpenter/issues/2478. Since this came first and has more discussion, I'll close this one out in favor of that.


Adds ICANN 2021

Is the hindex metric the H5-index for the conference?

Thanks for the PR! I unfortunately won't be merging this, sorry; to keep the aideadlin.es listing short / manageable, I'm only looking to list top-tier conferences as per conferenceranks.com. I encourage you to host your own fork if that's an option!
And yes, the hindex flag refers to the h5-index for the conference from Google Scholar.


chore(CODEOWNERS): update Merlin's responsibilities

Description
Update Team Merlin's responsibilities to include also the signature related packages.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Use this space to explain how you validated that your change functions exactly how you expect it.
Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you
provided convince any reviewer or any external reader that you did enough to validate your change.
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

#10910  👈
master

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

Join @dhaus67 and the rest of your teammates on  Graphite


HTML export backend tests failing

HTML export tests are failing.  Etherpad version 1.8.7 node v10.22.1

  1) export comments to HTML
       when pad text has one comment
         returns HTML with comment class:
     Error: Comment not exported. Regex used: this is c-1234, html exported: <!DOCTYPE HTML>this is c-1234

      at api.get.expect (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/static/tests/backend/specs/api/exportHTML.js:46:21)
      at Test._assertFunction (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:283:11)
      at Test.assert (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:173:18)
      at localAssert (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:131:12)
      at /home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:128:5
      at Test.Request.callback (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/index.js:716:12)
      at parser (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/index.js:916:18)
      at IncomingMessage.res.on (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/parsers/json.js:19:7)
      at IncomingMessage.EventEmitter.emit (domain.js:448:20)
      at endReadableNT (_stream_readable.js:1145:12)
      at process._tickCallback (internal/process/next_tick.js:63:19)

  2) export comments to HTML
       when pad text has two comments in a single line
         returns HTML with two comments spans:
     Error: Comment not exported. Regex used: this is c-1234.*this is c-82a3, html exported: <!DOCTYPE HTML>this is c-1234this is c-82a3

      at api.get.expect (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/static/tests/backend/specs/api/exportHTML.js:71:21)
      at Test._assertFunction (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:283:11)
      at Test.assert (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:173:18)
      at localAssert (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:131:12)
      at /home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:128:5
      at Test.Request.callback (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/index.js:716:12)
      at parser (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/index.js:916:18)
      at IncomingMessage.res.on (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/parsers/json.js:19:7)
      at IncomingMessage.EventEmitter.emit (domain.js:448:20)
      at endReadableNT (_stream_readable.js:1145:12)
      at process._tickCallback (internal/process/next_tick.js:63:19)

  3) export comments to HTML
       when pad text has part with comment and part without it
         returns HTML with part with comment and part without it:
     Error: Comment not exported. Regex used: no comment here this is c-2342, html exported: <!DOCTYPE HTML>no comment here this is c-2342

      at api.get.expect (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/static/tests/backend/specs/api/exportHTML.js:173:21)
      at Test._assertFunction (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:283:11)
      at Test.assert (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:173:18)
      at localAssert (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:131:12)
      at /home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/supertest/lib/test.js:128:5
      at Test.Request.callback (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/index.js:716:12)
      at parser (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/index.js:916:18)
      at IncomingMessage.res.on (/home/ilmar/etherpad-lite-origin/etherpad-lite/node_modules/ep_comments_page/node_modules/superagent/lib/node/parsers/json.js:19:7)
      at IncomingMessage.EventEmitter.emit (domain.js:448:20)
      at endReadableNT (_stream_readable.js:1145:12)
      at process._tickCallback (internal/process/next_tick.js:63:19)

So found out that the issue is caused by this line as the tests don't add comments but use html with comment html.

So found out that the issue is caused by this line as the tests don't add comments but use html with comment html.


Undefined property: PhpParser\Node\Expr\BinaryOp\Concat::$value

when using https://github.com/php-stubs/woocommerce-stubs/blob/master/finder.php I get a PHP error:
Undefined property: PhpParser\Node\Expr\BinaryOp\Concat::$value
File: vendor/php-stubs/generator/src/NodeVisitor.php on line 378
just wanted to ask if you want to fix (workaround?) it, or if this should be reported upstream?

WC 6.0 has problems
wc-stubs uses the old generator https://github.com/php-stubs/woocommerce-stubs/blob/master/composer.json#L17

BTW Including constants in stubs may be not necessary.


Add dutch auction sample with auditor

This PR uses the dutch auction sample to provide an example of how an auditor organization can be added to a smart contract. The protobuf signature policy syntax is used to assign a complex signature policy to an asset using state based endorsement, which is something that users have been asking for help on. This allows the auditor organization to "overrule" the normal endorsement policy if needed.
The simple blind auction is moved into a separate folder inside auction
Signed-off-by: NIKHIL E GUPTA<EMAIL_ADDRESS>

I know it's still in draft, but I wanted to make a comment so you could address it while still iterating on this:
In Go, variables starting with Capital letters have a specific semantic meaning, i.e., are exported non-private variables. There are lots of places where you used capital letters for variable names unintentionally, these should be lowercased to provide proper meaning (and intention).
Beyond that, this looks really interesting, I've never seen a dutch auction before so enjoying going through this. Thanks Nik

I know it's still in draft, but I wanted to make a comment so you could address it while still iterating on this:
In Go, variables starting with Capital letters have a specific semantic meaning, i.e., are exported non-private variables. There are lots of places where you used capital letters for variable names unintentionally, these should be lowercased to provide proper meaning (and intention).
Beyond that, this looks really interesting, I've never seen a dutch auction before so enjoying going through this. Thanks Nik

Thank you for pointing that out. I have addressed that and fixed the variables cases in all sets of smart contracts.

Apologies for not getting to this sooner. I like the auction and everything worked fine when I tried it. However, I don't think we should add another directory for this. I'd rather we simply have both auction samples at the top, which is consistent with what we have done for tokens. For that matter, I suggest using the names "auction-simple" and "auction-dutch" to keep them together.
Thanks.

Good suggestion. I moved the samples into two different directories.

LGTM. Thank you!

@lehors Looks like I need a re-review after a rebase


Fix bugs that arise from deserializing dicts with Unions of Instance properties

Deserializing when a Union of Instance properties is present results in unwanted behavior. '__class__' was ignored even when that class was a valid choice, and dictionaries were filtered to be empty to match one class, rather than selecting a different class.
Now, deserialize has additional kwargs:

strict - this requires __class__ to match the deserialized instance AND disallows extra properties in the input dictionary
assert_valid - deserialization fails if the resulting instance is invalid.

To maintain backwards compatibility, both of these are False by default, but to fix the above Union bugs, they are True by default when deserializing the Union property. You can keep the current, lenient behavior of Union properties by setting strict_instances=True on the Union property.

This also removes verbose on deserialize - We are now more opinionated, strict=True raises errors where verbose raised warnings.


All versions yanked from rubygems

Just noticed that all of the released versions have been yanked from rubygems...
Is there a reason for that?

Same here, can we tag @sethvargo ?

https://github.com/sethvargo/chef-sugar

https://www.vice.com/en_us/article/mbm3xn/chef-sugar-author-deletes-code-sold-to-ice-immigration-customs-enforcement

I don't understand what exactly has happened, but see https://blog.rubygems.org/2019/09/20/chef-ownership.html

hmm okay, so means we can grab the gem now? though v0.9.0 still forbidden
Gem::RemoteFetcher::FetchError bad response Forbidden 403 (https://rubygems.org/gems/chef-api-0.9.0.gem)

v0.8.0 is good

I don't understand what exactly has happened, but see https://blog.rubygems.org/2019/09/20/chef-ownership.html

Which I assume is a consequence of this: https://d.pr/i/n97cnX

True @geewiz. We had ours working on v0.8.0 at the moment. And yeah totally 🙏 that this get resolved soon and hopefully to get the latest stable built gem.

While the gem was restored on rubygems, the source of the runtime dependency logify was deleted from github.

Tagging @chef

@rmoriz @Doltair, you can get the source here if you need it: http://deb.debian.org/debian/pool/main/r/ruby-logify/ruby-logify_0.2.0.orig.tar.gz
https://github.com/chef/stove/issues/138 was our standing plan. Thanks for creating the issues @rmoriz.


How to use multiple providers

How can I use multiple providers, for example InMemory and JsonApi?

Hi @juancampuzano, EntityStore in general accepts any implementation of EntityProvider. You can simply initiate entity store 2 times. One with InMemory and another with JsonApi. Just allow your application store accept an instance of EntityProvider and pass it to the parent constructor.
const inMemoryStore = new AppStore(new InMemoryEntityProvider());
const jsonApiStore = new AppStore(new JsonApiEntityProvider());

EntityStore base class also contains optional second argument - type manager instance. But until there is no overlap in configuration or requirement to have configuration groups - it is not required.


Spacial audio blend for 2D (ignoring z value)

The spacial audio blending is currently using all three values of the transform, which makes sense in 3D but not so much in 2D. It's not a problem if for small z values, but once you start to have values above 10.0 it starts to screw with the distance blending. Was just wondering if there is any intention to address this.
I also noticed that you could potentially implement the following optimization change in here. Not 100% sure if that is producing the exact same result, but it at least sounds similar and it reduces the need to compute a square root calculation for every spacial sound every frame, so that is a decent optimization for bigger games.
let volume = (1. - sound_path.length_squared() / self.max_distance.powi(2))
    .clamp(0., 1.)
    .powi(2);

Both sounds reasonable.
The API of bevy_kira_audio is likely to change drastically over the next few months (see #114). In that, spacial audio might also change and become more configurable.
For now, you could increase max-distance for your special audio taking the probably constant z values into account.

Oh awesome. Yeah I just implemented a simple 2D spacial audio on my own. If this crate gets upstreamed into Bevy then there are most likely going to be a lot of changes, in which case this might get reworked too. Will close this and see where we are after a few updates. For anyone in the meantime, this my 2D spacial audio implementation: https://github.com/PraxTube/magus-parvus/blob/master/src/audio/spacial.rs


what is the headers when pushing your reviews to the content pool using a webhook？

when I push data to the content pool using a webhook with no headers ,it response as follows：
{
	"detail": "Authentication credentials were not provided."
}

Hi @niceyida we will soon release the full documentation. But for now, you can see a schema.yml file in main branch. Please paste its content in https://editor.swagger.io/ to get a working documentation of the REST API and webhooks.
To answer your question, if you are calling the webhook from another server, just generate an API-Key first using the admin panel (you will see a link in the sidebar). Then use put an Authorization header like
Api-Key <YOUR KEY>
Also, the correct request body would be
{
  "text_content": "Your content.",
  "metadata_json": {}
}

Correct URL: POST to {{host}}/api/v1/push-content/{{content-pool-name}}/{{datasource-name}}/

Hi @arpanpreneur It works,thanks for your reply. But I meet another issue, when I put Ingested Text Data successfully, the Processed datas is empty.Before, I had set chain and propmt. Can you give me some solution suggestions?

Hi, here are a few things you can check

OpenAI Key is valid in env file and loaded properly (check the value of echo $OPENAI_API_KEY in the terminal you are doing runserver)
You can make requests to OpenAI using the account you generated the Key from (just use the playground to verifiy)
You have started the celery process in the way mentioned in the README.

Please let me know if this helps you debug this.

@niceyida Is there an update on this ticket? Please let me know if you have solved it already, in that case, we will close the issue.

@arpanpreneur I confirmed that I have run celery and no errors were reported, but process_data is still empty. In addition, I also confirmed that my openai_key is valid. I don't know where to check now.

Let us connect and check this over a quick call. Connect me on LinkedIn or X with the handle @arpanpreneur in both places. @niceyida

Hi, @arpanpreneur.Maybe this issue can be closed first, and I can wait until the official version of the detailed documentation is released before testing. Thank you for your patient answer here.

Sure, let me know if we have a way to connect. I would love to understand potential use cases you are trying, that would help us give more informed direction we could take this project towards.
Closing this issue.


Add logger level configuration support

Based on issue: https://github.com/sameersbn/docker-redmine/issues/140
When my redmine log storage was low i was looking for log rotation solution for my redmine instance and discovered that it has one out of the box: https://github.com/search?q=repo%3Asameersbn%2Fdocker-redmine logrotate&type=code
It's just my instance generated so much info logs by default. So it'l be great if administrators can configure amount of generated logs but in this repo i didn't found any solution for configuring logger level so i implemented it.
Tested on my instance.
Thx for the great repo by the way! When i discovered this repo it became a lot easier to administrate redmine.

Thanks