Tokenomics Whitepaper on Docs Sui Site

Tokenomics whitepaper draft by Alonso was shared last month. Goal is to have a finalised version for public view.
Reference to Design Doc:
https://www.notion.so/mystenlabs/Sui-Tokenomics-Whitepaper-8358431553e040bd843dc0f3d2971a8d
Notion board will include specific checklist, timelines, etc. until they are ready for public view.

Alonso is editing the final PDF.
We do have the draft PDF available. We have it attached in the Notion board for your full review.
Checklist in the Notion board outlined:

Design Doc reference (https://www.notion.so/Sui-Tokenomics-Whitepaper-8358431553e040bd843dc0f3d2971a8d)
GitHub request for updates sections (to be completed by @Jennifer Kye & @alonso by May 6, 2022)
[ ]  Timelines:

[ ]  May 17: [sui.io](http://sui.io) & [docs.sui.io](http://docs.sui.io) staging ready for review
[ ]  May 20: tokenomics paper complete (submitted by @alonso)
[ ]  May 23: publish tokenomics blog post (summary + key takeaways by @alonso)
[ ]  May 23: [docs.sui.io](http://docs.sui.io) published
[ ]  May 23: social posts announcing tokenomics paper
[ ]  May 30: share Google Docs “comment-able” version for contributors to provide questions or feedback
[ ]  May 30: share Alonso explainer video (slide presentation with voiceover)
[ ]  June 3: close out Google Docs - no more contributor input
[ ]  June 8: Alonso to host AMA on Discord to discuss Tokenomics

[ ]  [docs.sui.io](http://docs.sui.io) updates

[ ]  See what's new section to include update on Sui Economics (@Jennifer Kye to provide @Clay Murphy with appropriate copy)
[ ]  Will need your help @alonso & @Clay Murphy on how to best categorise sections within the Sui Doc site

[ ]  “Sui Economics Overview & Deep Dive” can be under “Learn”
[ ]  Sui Tokenomics Whitepaper can be under Contribute > Research Papers
[ ]  Or do we only want to do a brief overview (without the deep dive) and have the complete whitepaper under Research Papers?

@econmysten

Can you get layout website completed by May 17th EOD? This can then be shared with @Clay-Mysten and others to begin staging.
We can also get the blog post ready by May 17th as well; I can support with getting this draft up and running on Medium. We know the link from draft to final published changes, so this will impact link on Twitter threads.
Twitter threads can be set by May 20th for publishing next week.

Yes, please let me know when and where the tokenomics paper is ready for review. I have been holding for a rewrite Alonso was undertaking first. Thanks!

Hi Alonso and Jen,
Congratulations on a wonderful, clear paper, Alonso. I truly enjoyed reading it and learned so much about our offering. I've finished my review of the Tokenomics paper V2, leaving comments along the way as requested.
I can try to export the contents to our website if you can provide me with the native format (perhaps) or something like .tex.
Please do let me know next steps regardless. I see above:
May 24: [docs.sui.io](http://docs.sui.io/) published
Not sure what that entails. I also see:
“Sui Economics Overview & Deep Dive” can be under “Learn”
Let me know how I can help. Thanks!

thank you for the kind comments clay! i don't think we need to convert the whitepaper, rather i think the gameplan is:

host the pdf on github just as the Sui whitepaper
create a new section on the "Learn" tab of docs.sui.io called "Tokenomics". I'll finalize the table of contents by tomorrow and then hopefully finish the copy by the end of the week.
The reason why I don't think we should simply host the same text in the PDF is that I want to make the material more accessible. Just like the Sui whitepaper is precise and technical while the documentation is more accessible, we should aim for the same on the tokenomics.

Just noting Alonso finished the web contents, I reviewed and edited them, and have now converted them to Markdown in:
https://github.com/MystenLabs/sui/pull/2101
https://github.com/MystenLabs/sui/pull/2102
Alonso and Jen, once you and I refine the text there, I will split it up and add to navigation as we discussed. Thanks!


Password reset configuration in signupsignin flow via flow linking

The current documentation for hosted Blazor WASM + Azure AD B2C shows how to use a signin-signup workflow. However, this leaves the user without a fully-working experience. The login page has a link to request a reset of the password, but it is not configured.
The user can create the required user flow on the portal, but it is unclear how to "link" the flows, which seems required according to https://docs.microsoft.com/en-us/azure/active-directory-b2c/user-flow-overview#linking-user-flows to have the password reset link. Specifically, what is the recommended approach to detect the error AADB2C90118 and initiate the user flow?
Thank you.

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

ID: 520b9821-ecef-20af-a601-ea36c4297d88
Version Independent ID: da9c8ac9-4d7a-4b40-56a2-a4bfe7083567
Content: Secure an ASP.NET Core Blazor WebAssembly hosted app with Azure Active Directory B2C
Content Source: aspnetcore/blazor/security/webassembly/hosted-with-azure-active-directory-b2c.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @AlbertoPa ... They're considering this for a future release. See ...

https://github.com/dotnet/aspnetcore/issues/27549
https://github.com/dotnet/aspnetcore/issues/27119

What are some possible work-arounds that we can implement in Blazor WebAssembly to gracefully handle this situation before the MSAL Javascript library provides support?
I think I could simply catch the callback with this #error in the querystring and then redirect the user back to B2C Password reset flow.  However, I'm  unable to determine how to intercept this using the  component.
I see that component has the OnLogInSucceeded EventCallback, but I don't see anything for the error callbacks.

@chrislangston ... Ask on a community support forum, as we don't have the staffing to provide product support (and few would see an issue comment here on the docs repo, especially in a closed issue).
Try these ...

Stack Overflow (tag: blazor)
ASP.NET Core Slack Team
Blazor Gitter


LSX II

Does this allow connecting to KEF LSX II via Home Assistant?
The official 'Kef' plugin only seems to support LSX.
Thanks!

Hello,
Yes it should support KEF LSX II "as is" although for the moment I did not implement specific code to detect the model. So hass-kef-connector would report that you have KEF LS50WII at the moment. It should work regardless of the model detected, although, you will not be able to switch to sources specific to your model such as USB.
I just finished my PhD so I'll have a bit more time to update hass-kef-connector in the near futur. :wink:

I don't think so.
The KEF LS50W and LSX v1 use a totally different local API that is not compatible with the "W2" platform that the LS60, LSX2 and LS50W2 are based on.
hass-kef-connector  have been developed to be compatible with the W2 platform, while the integration you mentioned is compatible with the previous platform.

Super helpful, thank you!


Kinesis ElasticSearch Sink error messages are not helpful

Hi,
When an error is caught, the error message is not display or is very unclear. I had to modify the code and do e.printStackTrace() to get a clear idea of what was wrong.
It'd be great if you fix that bug (should be quite easy to fix). In my opinion any unexpected exception should be logged with a full stacktrace
Regards,
Stephane

Hi @simplesteph that does sound like an easy fix.  Could you provide the point where you had to add this stackTrace printing?

Kinesis sink around line 98, I added the following:
    } catch {
      case rnfe: ResourceNotFoundException => false
      case e: Exception => e.printStackTrace(); false
    }

ElasticSearchSenderHTTP.scala around line 181
case e: Exception => {
          e.printStackTrace()
          Log.error("ElasticsearchEmitter threw an unexpected exception ", e)

Overall anytime you try catch I believe you should somehow display a clear idea of the error.

Well I still think the idea of the error is there but I do agree that without the stacktrace it could make it quite difficult to debug!  I will schedule this into the next milestone.

Yeah the idea of the error is here but somehow the error never got displayed, i.e. in my logs I would get
 "ElasticsearchEmitter threw an unexpected exception <blank>


Support AES encryption for database passwords.

Codecov Report
Patch coverage: 75.18% and project coverage change: -0.01 :warning:

Comparison is base (676022e) 78.60% compared to head (15c3f9a) 78.59%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2534      +/-   ##
==========================================
- Coverage   78.60%   78.59%   -0.01%
==========================================
  Files         630      630
  Lines       51391    51527     +136
==========================================
+ Hits        40394    40499     +105
- Misses       9010     9040      +30
- Partials     1987     1988       +1

Flag
Coverage Δ

go-1.15-386
78.62% <75.18%> (-0.01%)
:arrow_down:

go-1.15-amd64
?

go-1.16-386
78.62% <75.18%> (+<0.01%)
:arrow_up:

go-1.16-amd64
78.63% <75.18%> (+<0.01%)
:arrow_up:

go-1.17-386
?

go-1.17-amd64
78.58% <75.18%> (-0.02%)
:arrow_down:

go-1.18-386
?

go-1.18-amd64
78.56% <75.18%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

text/gstr/gstr_is.go
100.00% <ø> (ø)

database/gdb/gdb_core_config.go
64.93% <27.27%> (-6.50%)
:arrow_down:

encoding/gbase64/gbase64.go
62.60% <67.27%> (+4.27%)
:arrow_up:

container/garray/garray_normal_any.go
98.54% <100.00%> (+0.02%)
:arrow_up:

container/garray/garray_normal_int.go
98.50% <100.00%> (+0.02%)
:arrow_up:

container/garray/garray_normal_str.go
98.35% <100.00%> (+0.03%)
:arrow_up:

container/garray/garray_sorted_any.go
96.03% <100.00%> (+0.07%)
:arrow_up:

container/garray/garray_sorted_int.go
97.34% <100.00%> (+0.05%)
:arrow_up:

container/garray/garray_sorted_str.go
97.20% <100.00%> (+0.05%)
:arrow_up:

... and 4 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@wsy998 Too many features in one PR. Please move Filter feature to another PR.


Update jackson to remediate CVE-2022-42003

Thanks!

Can you cut a release? My security person (and I) will thank you.

Sure, I've released 5.12.0.

Thanks a bunch!


React Native refresh

Docs Build status updates of commit 4eaf0bb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

tutorials/react-native.yml
: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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Address runc CVE-2019-573

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
A flaw was found in the way runc handled system file descriptors when running containers. A malicious container could use this flaw to overwrite contents of the runc binary and consequently run arbitrary commands on the container host system.
https://access.redhat.com/security/cve/cve-2019-5736
What you expected to happen:

We should upgrade docker once centos packages become available

I managed to build the latest docker from centos git here:
https://github.com/simonswine/centos-build-docker-rpms
It seems to work fine, I assume that the package will come through in the next hours on the official centos resources

This is fixed with Tarmak 0.5.4 and I think we can close this :)
/close


#65 - Reorganise code files in mdm-resources

Resolves #65
Re-organises all the files in the mdm-resources repo so that the layout more closely matches that in the Postman API documentation - though there may be some slight differences.
Everything still works in mdm-ui since the main entry point - src/index.ts - has been updated to export all types correctly, and mdm-ui references everything via the entry point.
Also updated some of the npm commands:

clean is only required now due to including the shx package - no longer need separate clear commands for Unix and Windows OSes
build commands are defined by their emitted outputs - es5, es6 an es2015
pr-checks added to run before submitting a PR in GitHub, ensuring the tasks pass before Jenkins runs them

@aaronforshaw I've updated the README as recommended, and filled in a lot more detail for it as a result.


Configurable composer and conductor genres

Add settings page allowing to specify list of genres that support composer and/or conductors. When bowsing (e.g.) "Genres / Classical" the user will be preented to choose for Artists, Albums, Composers, Condcutors. This selection is already imeplemented, but the set of genres to which it is applicable is hard-coded. This issue is to make this configurable.

Implemented for next feature release.


Is it thread safe? Should I share it in mutiple threads?

Hello,
I want to use in Vert.x. Should I share it in mutiple Verticle(include WorkVerticle)?
Is there any best practice?
Thank you.

that's a good question
you can share it in multiple verticles, that being said I have doubts about worker verticles and I believe tests should be conducted with worker to figure this out.

Thank you. I will have a look. And... Is there anything to notice if I use it with Vert.x?
@vietj

no, it shouldwork well with and without vertx.
if you use with vertx, it will respect vertx threading model and will call you back on the right event loop


Increase funding_sources character limit

To avoid a database migration.

A discussion on slack led to the conclusion to not limit the number of characters in funding_sources.


Assert with TLS on 1.0.0 beta 6

Hi all,
When using 1.0.0.beta.6 I've this assert when using an HTTPS connection: I'm not sure...
As OpenSSLStream is a derived class of TLSStrem, the check is correct?
core.exception.AssertError@../../../../root/.dub/packages/vibe-core-1.0.0-beta.6/vibe-core/source/vibe/internal/interfaceproxy.d(111): Extraction of wrong type from InterfaceProxy.
??:? _d_assert_msg [0x16a87f6]
../../../../root/.dub/packages/vibe-core-1.0.0-beta.6/vibe-core/source/vibe/internal/interfaceproxy.d:111 nothrow @trusted vibe.internal.freelistref.__T11FreeListRefTC4vibe6stream3tls9TLSStreamVbi1Z.FreeListRef vibe.internal.interfaceproxy.InterfaceProxy!(vibe.core.stream.Stream).InterfaceProxy.extract!(vibe.internal.freelistref.__T11FreeListRefTC4vibe6stream3tls9TLSStreamVbi1Z.FreeListRef).extract() [0x15c11bb]
../../../../root/.dub/packages/vibe-d-0.8.0-beta.5/vibe-d/http/vibe/http/server.d:1845 @safe bool vibe.http.server.handleRequest(vibe.internal.interfaceproxy.InterfaceProxy!(vibe.core.stream.Stream).InterfaceProxy, vibe.core.net.TCPConnection, vibe.http.server.HTTPListenInfo, ref vibe.http.server.HTTPServerSettings, ref bool, scope std.experimental.allocator.IAllocator) [0x15a62a4]
../../../../root/.dub/packages/vibe-d-0.8.0-beta.5/vibe-d/http/vibe/http/server.d:1776 @trusted void vibe.http.server.handleHTTPConnection(vibe.core.net.TCPConnection, vibe.http.server.HTTPListenInfo).__lambda4() [0x15a5c32]
../../../../root/.dub/packages/vibe-d-0.8.0-beta.5/vibe-d/http/vibe/http/server.d:1772 @safe void vibe.http.server.handleHTTPConnection(vibe.core.net.TCPConnection, vibe.http.server.HTTPListenInfo) [0x15a59de]
../../../../root/.dub/packages/vibe-d-0.8.0-beta.5/vibe-d/http/vibe/http/server.d:1647 nothrow @safe void vibe.http.server.listenHTTPPlain(vibe.http.server.HTTPServerSettings, vibe.http.server.HTTPServerContext).doListen(vibe.http.server.HTTPListenInfo, vibe.http.server.HTTPServerContext, bool, bool).__lambda6(vibe.core.net.TCPConnection) [0x15a51cb]
../../../../root/.dub/packages/vibe-core-1.0.0-beta.6/vibe-core/source/vibe/core/task.d:516 _D4vibe4core4task12TaskFuncInfo76__T3setTDFNfS4vibe4core3net13TCPConnectionZvTS4vibe4core3net13TCPConnectionZ3setMFKDFNfS4vibe4core3net13TCPConnectionZvKS4vibe4core3net13TCPConnectionZ12callDelegateFKS4vibe4core4task12TaskFuncInfoZv [0x165d0a6]
../../../../root/.dub/packages/vibe-core-1.0.0-beta.6/vibe-core/source/vibe/core/task.d:541 void vibe.core.task.TaskFuncInfo.call() [0x163f135]
../../../../root/.dub/packages/vibe-core-1.0.0-beta.6/vibe-core/source/vibe/core/task.d:372 nothrow void vibe.core.task.TaskFiber.run() [0x163e6aa]
??:? void core.thread.Fiber.run() [0x1707b0f]
??:? fiber_entryPoint [0x1707872]
??:? [0xffffffff]
[main(HzkV-fin) dbg] Thread exit main (index 0) (main=true)
[main(HzkV-fin) dia] Main thread exiting
I've noticed that using the version 0.7.31 this issue is no present.
Thanks
Stefano

The problem is that the stored type is actually a concrete FreeListRef!OpenSSLStream. InterfaceProxy doesn't support an kind of conversions, though. I've opened #1795 with a fix.


add option to pass in important config

This allows the plugin to be used with a custom important value.

Looks good! Thanks for contributing. I've just edited the readme so that this option is a bit more prominent.


Command to handle policies

It could be great to avoid using direct HTTP calls to the API management for handling policies.
Adding a command for create, show, delete and update policies to a 3scale service could be cool.

Implemented in #270

Implemented in #270


Can Sticker or Image modified with scale and flip button like delete button?

Check the sample with single finger scaling.

this feature is must


Error on upgrade database after downgrade

🍰 Pullrequest
Create tables on an already exsting table breaks the script, so fix with a create table if not exists. Insert statement breaks if their is a duplicate key that is imported change so that it does not break.
Issues

None

Todo

[X] None

What happens when the gradido login database is not present?

Good question! I did not check that!

OK I understand your point, so what would have been the right path of action so that I don't get a broken db?
I did:
Work on something near master branch, then I had to go on the tag 1.5.1 where the db lays 2 patches behind.
Now I did go in the migrations table and deleted the 2 patches /!\ This should have broke the db /!
After I did go back on master and started the db again and it could not upgrade the db, what is logical since the tables were present.
What should I have done instead? Is their an action to downgrade the db? @ulfgebhardt


Using BaseActivityEventListener instead of ActivityEventListener

This addresses breaking API changes introduced in RN 0.33
See https://github.com/facebook/react-native/commit/fbd2e139103e3d520f6dfc009d6200f8b8168e35#commitcomment-18998993
and http://facebook.github.io/react-native/releases/0.35/docs/native-modules-android.html#getting-activity-result-from-startactivityforresult

Thanks for the PR!


Smart break line (Shift + enter) does not work in razor files

When I use shift + enter in normal C#

When i use it in a .razor file

As you see, the feature doesn't work in razor files. I also found out that double tab snippets don't work either, but there is already an issue about it: https://github.com/dotnet/razor-tooling/issues/4322. I wonder if there are any other C# code editing features, that don't work in razor syntax. So devs, please bring all C# editing features into razor!

As you see, the feature doesn't work in razor files. I also found out that double tab snippets don't work either, but there is already an issue about it: #4322. I wonder if there are any other C# code editing features, that don't work in razor syntax. So devs, please bring all C# editing features into razor!

@DoctorKrolic we hear you and thank you for the report!

Does it work now? I still can't get mine to work

Smart break line is a feature of the Roslyn editor specifically, so for this to come to Razor we would need that functionality moved to the LSP client first.

we would need that functionality moved to the LSP client first

LSP team doesn't seem to care about this feature request :( https://github.com/microsoft/language-server-protocol/issues/1586


Fixed bug with the Xcode project not opening due to the shell script

My last PR was incorrect, I noticed a bug after you had merged it in, apologies. It makes the Xcode project unable to open as it couldn't parse .xcodeproj due to the shell script I amended.
I have committed the fix in this PR.

Honestly, the error was mine, I missed the error too. Merging it back. Now is ok! Thanks!


bug: exec ./dkn-compute: exec format error

this is most likely related to platform compatibilty for the image, but we dont know yet why it happens to some people

closing this issue as its stale & we only have seen it once


Add a new ninja tool: finddeps.

This will find and output the dependency path from one target to
another.
It uses DFS to search for nodes starting from the [from] node, and then
going up the dependency tree until it finds the first path to the [to]
node.
Due to memoization, it's not trivially possible to find all paths, and
also by definition this returns the smallest path.
A sample output when run on the ninja project is:
$ ninja -t finddeps ninja src/browse.cc
Path: ninja
    > build/libninja.a
    > build/browse.o
    > src/browse.cc

$

I've found this very useful navigating the dependency tree in order to break dependency of one target from another.

By the way, you can also use -d explain if you're trying to diagnose why something is being built.

I haven't used ninja for a while now. If similar features have gone in, this is probably outdated. I will let you deal with the patch as you feel best, but do let me know if you need any help from my side.
However, last I checked, -d explain option was present, but it was not sufficient for my task. I was trying to see all the modules that depend on a particular library, in my attempt to eradicate that library.

Another idea is that we already have this support for the "query" tool and the graph so it's sorta something that belongs in there.
I have experience with this kind of dependency-breaking ("why does module X pull in module Y?") with Google's build system (now open source as "bazel") and I know it has a pretty sophisticated querying language.  I worry if we provide some functionality now we'll slowly slide into their complex requirements.
Which makes me think: perhaps this kind of logic belongs in the generator program, since it ought to have more knowledge about relationships between parts of the project.

In order to reduce the number of open PRs I'm closing this one, feel free to reopen if you still think this should be merged.


Demo website

Once upon a time we had lavagna.devand.dev server. I've shut down devand.dev, so I need another place for lavagna.
This was the documentation when the server was at lavagna.devand.dev
## Online demo

An online demo is available: [demo](https://lavagna.devand.dev)

It supports passing options as url parameters:

- collaboration
  url: https://lavagna.devand.dev/?collab-url=ws://lavagna.alepez.dev:3536/demo
- debug
  pane: https://lavagna.devand.dev/?collab-url=ws://lavagna.alepez.dev:3536/demo&dbg=true
-

ui: https://lavagna.devand.dev/?collab-url=ws://lavagna.alepez.dev:3536/demo&dbg=true&ui=true

Possible solutions:

GitHub pages for webapp + my own server for matchbox
GitHub pages for webapp + johanhelsing server for matchbox, like the one used by https://helsing.studio/box_game/ (I should ask)
Both webapp and matchbox on my own server

Also check this: https://johanhelsing.studio/posts/deploying-matchbox/


can DDFileLogger delete prefix log when reach max size?

Does CocoaLumberjack support deleting ahead log when the file reaches setted maximumFileSize?
Now DDFileLogger move log data to another file and delete all log when reaching maximumFileSize.
I wonde how I can fulfill this function, can you give me some tips?

I assume you found your answer @MountainHill

@bpoplauschi yes, thank you very much.


docs: update workflow.md

Description
Added how to signing only commit in PR.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

@ddevsr Thank you!


Fix a container->a Container

All the words "container" in this doc are typed as Container.

This change is

/LGTM
seems to be reasonable. =)

/approve
/lgtm


Consistent location for images in README

There's a mix of local and remote GitHub links for images in the README. Figure out which we should actually be using. Probably local, because this gets published to the VS Code Marketplace?
Directly tied to #23.

I switched to using local/relative image src references in the README in https://github.com/apjanke/vscode-octave-hacking/commit/3743ebd405a8c744af965c8f9e6deb37935c0062; maybe that'll work. If it does, that makes things consistent, and I know what the right way to do it is now.

Switching to local/relative image source references fixed broken images in some contexts. Seems to be working everywhere now. Calling that the right way to do this.


Use htmltools.wrap_displayhook_handler()

This PR depends on https://github.com/posit-dev/py-htmltools/pull/77.
These two PRs together consolidate the logic for how different kinds values should be handled by the sys.displayhook, into a single location, htmltools.wrap_displayhook_handler().

Closing because #907 has incorporated these changes.

Did you mean #907?

Oops, I meant #905.


BackboneFinetuning - even with train_bn batch normalization is still learning.

🐛 Bug
When I use BackboneFinetuning callback with train_bn=False batch normalization biases and weights are still changing from the very first epoch, even though they should be fixed until unfreeze_backbone_at_epoch.
To Reproduce
Below is the notebook. I marked with comments all the placed in the default code I modified:
https://colab.research.google.com/drive/1LPiOljLEbFXUUST3Hr4oeQfZlmJFUndZ?usp=sharing
Expected behavior
Batch normalization biases and weights (but not means and vars) should be fixed at the beginning of the training. I think it can be achieved by passing self.train_bn to self.freeze in freeze_before_training method.
Later we need to unfreeze it by passing in unfreeze_and_add_param_group train_bn=True.
Environment

CUDA:

GPU:

Tesla T4

available:         True
version:           11.3

Packages:

lightning:         None
lightning_app:     None
numpy:             1.21.6
pyTorch_debug:     False
pyTorch_version:   1.12.0+cu113
pytorch-lightning: 1.6.5
tqdm:              4.64.0

System:

OS:                Linux
architecture:

64bit

processor:         x86_64
python:            3.7.13
version:           #1 SMP Sun Apr 24 10:03:06 PDT 2022

train_bn argument in the constructor is meant for the backbone after it's unfreezed. If you want to freeze the batch-norm layers from the beginning, you can do:
class CustomBackboneFineTuning(BackboneFinetuning):
    def freeze_before_training(self, pl_module):
        self.freeze(pl_module.backbone, train_bn=False)

trainer = Trainer(..., callbacks=[CustomBackboneFineTuning()])

train_bn argument in the constructor is meant for the backbone after it's unfreezed. If you want to freeze the batch-norm layers from the beginning, you can do:
class CustomBackboneFineTuning(BackboneFinetuning):
    def freeze_before_training(self, pl_module):
        self.freeze(pl_module.backbone, train_bn=False)

trainer = Trainer(..., callbacks=[CustomBackboneFineTuning()])

It's not clearly stated in the documentation here https://pytorch-lightning.readthedocs.io/en/stable/api/pytorch_lightning.callbacks.BackboneFinetuning.html
train_bn(bool) – Whether to make Batch Normalization trainable.
So the intended behavior is that first we freeze the whole backbone except its batch normalization layers, then we unfreeze the backbone and we can freeze its batch normalization layers for the whole training if we want?

I think, we can update the docstrings.

I think it is a bit confusing that the freeze function can take train_bn as an argument if it is not intended to be used there.
So maybe you could also remove it from there when you change the docstrings.

Rather than modifying the docstrings to describe this unusual behavior, wouldn't it be better to just change the implementation of FreezeBackbone so that it freezes all the weights?


esp32c6-devkit - uninitialized variable in nuttx/arch/risc-v/src/common/espressif/esp_irq.c

I am trying Espressif provided  ESP32-C6-DevKitC-1 , standard configuration
tools/configure.sh esp32c6-devkit:nsh

even without any configuration change I receive
CC:  common/espressif/esp_irq.c common/espressif/esp_irq.c: In function 'esp_setup_irq':
common/espressif/esp_irq.c:194:6: error: 'cpuint' may be used uninitialized [-Werror=maybe-uninitialized]
  194 |   if (cpuint == ESP_NCPUINTS)
      |      ^
common/espressif/esp_irq.c:156:7: note: 'cpuint' was declared here
  156 |   int cpuint;
      |       ^~~~~~
cc1: all warnings being treated as errors

I can build after quick hack
--- a/arch/risc-v/src/common/espressif/esp_irq.c
+++ b/arch/risc-v/src/common/espressif/esp_irq.c
@@ -153,7 +153,7 @@ static int esp_cpuint_alloc(int irq)
 {
   uint32_t bitmask;
   uint32_t intset;
-  int cpuint;
+  int cpuint = 0;

   /* Check if there are CPU interrupts with the requested properties
    * available.

Please @tmedicci , @eren-terzioglu or somebody other from Espressif team, have you noticed this problem.

When I look into code then initial value should ensure the fail when the intset is empty, so next change look more logical
--- a/arch/risc-v/src/common/espressif/esp_irq.c
+++ b/arch/risc-v/src/common/espressif/esp_irq.c
@@ -153,7 +153,7 @@ static int esp_cpuint_alloc(int irq)
 {
   uint32_t bitmask;
   uint32_t intset;
-  int cpuint;
+  int cpuint = ESP_NCPUINTS;

   /* Check if there are CPU interrupts with the requested properties
    * available.

But anyway when I compile the Nuttx with above described default configuration, flash it by
make flash ESPTOOL_PORT=/dev/ttyUSB0 ESPTOOL_BINDIR=../esp-bins

then I can see on the serial port on output only
ESP-ROM:esp32c6-20220919
Build:Sep 19 2022
rst:0x1 (POWERON),boot:0xc (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:2
load:0x40800000,len:0x424c
load:0x40806450,len:0x8e8
entry 0x40803f1e
*** Booting NuttX ***

IROM lma: 0x10000  vma: 0x42000100  size: 0x1c14e
DROM lma: 0x2c14e  vma: 0x42020000  size: 0xaaa8
dram: lma 0x00000020 vma 0x40800000 len 0x424c   (16972)
dram: lma 0x00004274 vma 0x40806450 len 0x8e8    (2280)

and then no more information is printed nor any character is accepted, echoed etc.

The chip identification is
Chip is ESP32-C6 (QFN40) (revision v0.0)
Features: WiFi 6, BT 5, IEEE802.15.4
Crystal is 40MHz

May it be I have made error that I have flashed bootloader-esp32c6.bin and partition-table-esp32c6.bin according to the documentation page which seems to be deprecated according to other information source.

Hi @ppisa,
Our internal tests are building without any problems. Seems you are not using correct toolchain and version. Could you please try to test with our suggested toolchain ? Output should be like this:
$ riscv-none-elf-gcc --version
riscv-none-elf-gcc (xPack GNU RISC-V Embedded GCC x86_64) 12.3.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Thanks for the response.
I have setup temporarily account, loaded entrusted GCC binaries and compiled actual NuttX sources with added esptool
https://github.com/apache/nuttx.git
https://github.com/apache/nuttx-apps.git
https://github.com/espressif/esptool.git
cd nuttx
tools/configure.sh esp32c6-devkit:nsh
make -j 4
make flash ESPTOOL_PORT=/dev/ttyUSB0

This GCC toolchain does not report evident bug in the code so build goes through, flashing works but there is no output on serial console nor USB serial after power-up.  No NSH promp etc. I can test OpenOCD
I hope that bootloader binaries are taken from  nuttx/arch/risc-v/src/esp32c6/esp-hal-3rdparty. Because step how to obtain them from https://github.com/espressif/esp-nuttx-bootloader/releases seems to be deprecated in the repository. It is possible that I have done some damage to the bootloader by previous attempt to use there binaries through command
make flash ESPTOOL_PORT=/dev/ttyUSB0 ESPTOOL_BINDIR=../esp-bins

If you think that some procedure how to restore boot, could help, please inform me.
As for the warinig/error  'cpuint' may be used uninitialized, this is real obvious  error in the code design. Probably with little effect, because the list is never empty, but it should be corrected. It is bug in the toolchain which you use that it is not reported and it can be reported for different optimization level etc. As for GCC, I use Debian and even my builds of GCC with RISC-V for years, yes there can be some bug and it worth to retest with know to work setup. But use and contribute to NuttX for about 8 years already and we have used it with EP32C3 for years as well. So we have some experience. We can try binaries on the second kit which we have received when I meet with my student working on ICE-V support.
I can send pull to correct uninitialized variable to mainline if the solution to set it up to ESP_NCPUINTS as the mark to fail allocation if the list is empty seems as the correct one to you.
Problem is that we need to decide really soon if we can dare to use ESP32C6 as the target for the microprocessor architectures course starting right now or not. We can use ESP32C3 where in legacy mode we know everything and are able to add peripherals, demonstrate CAN communication with drivers we have contributed into NuttX etc. But we want to use platform with some DC motors and encoder peripheral and motor control PWM of ESP32C6 is promising. We cannot afford to buy 30+ ICE-V kits which would be ideal for many tasks but on the other hand are too expensive to provide to each student and relative complex. I believe we can demonstrate motion control on ESP32C6 even without NuttX drivers by direct code in application which could be even educative how to access and setup MCU peripherals. We show that to our students on our own kits based one Xilinx Zynq SBC. But we need to provide solution for course for foreign university now and want RISC-V based solution to match lectures. I have realized may be 20 or 30 motion control systems on all possible targets from eight-bit MCUs to 64-bit FPGA, PCIe, data acquisition based, GNU/Linux, assembly, NuttX, RTEMS etc.  sometimes including own QEMU based matching HW models etc.
But we need at least base OS to work reliably and problem is that we are tight with time now.

Hi @ppisa!
First of all, thank you for reporting the issue regarding the non-initialized variable and the outdated documentation. We'll fix this ASAP. We'll be very thankful if you can send the pull-request fixing the non-initialized variable.
About the toolchain, NuttX uses a single toolchain for all RISC-V implementations and that's not different for our Espressif's SoCs. We highly recommend using the same, as we ensure that our SoCs are compatible with these toolchains. You can check it here which toolchain we us and how to download it (or even use NuttX's CI docker image to build NuttX without messing with your local GCC versions). As @eren-terzioglu told you, our internal CI tests the build and the HW, so I can assure you that this configuration is known to be working without any problems (actual NSH commands are tested with HW in the loop).
About the bootloader, it isn't required anymore. NuttX boots directly: no binaries are required. Don't worry if you followed the instructions to download and flash the 2nd stage bootloader, once you re-flash the device with newer NuttX versions, it will be overwritten.
General considerations/recommendations

In our internal CI we build it with EXTRAFLAGS="-Wno-cpp -Werror". Unfortunately, the current toolchain (Xpack's pre-built GCC 13.2.0-2) didn't trigger the warning, possibly because of the optimization.
Don't turn off the optimization: stack size is tuned to work with the default optimization level and unintended behavior may happen.
I highly recommend using the non-legacy version of our boards. Legacy ESP32-C3 will not receive any major updates. On the other hand, support for shared drivers for ESP32-C3, ESP32-C6 and ESP32-H2 are expected to grow faster.

Unfortunately even even when I have re-build with reference binary from scratch on empty account the board does not work, as I have informed in previous post. So it is not toolchain problem. We try another piece.


Add new FILTER_TYPE 'ArrayFilter' to allow filtering on multiple values

This is workaround for issue #1202. It adds a new FILTER_TYPE called ArrayFilter for filtering multiple values.
@AllenFang I know you have focus development on react-boostrap-table2, but I think this would be a small but useful improvement.
export default class ProgrammaticallyArrayFilter extends React.Component {
  /* Filtering passing an array of values */
  handleBtnClick = () => {
    this.refs.table.handleFilterData({
      name: { type: 'ArrayFilter', value: [ 'Item name 3', 'Item name 4' ] },
      price: { type: 'ArrayFilter', value: [ 2100, 2104 ] }
    });
  }

  render() {
    return (
      <div>
        <button onClick={ this.handleBtnClick } className='btn btn-default'>Click to apply text filter</button>
        <BootstrapTable ref='table' data={ products }>
          <TableHeaderColumn dataField='id' isKey={ true }>Product ID</TableHeaderColumn>
          <TableHeaderColumn ref='nameCol' dataField='name' filter={ { type: 'TextFilter', delay: 1000 } }>Product Name</TableHeaderColumn>
          <TableHeaderColumn dataField='price'>Product Price</TableHeaderColumn>
        </BootstrapTable>
      </div>
    );
  }
}

OMG i was looking for this whole day :0
Pleeease merge it ASAP
Thank you for adding this feature guys

thanks man i'm looking for this features for a while, i try to use custom filter. But it's end up with some kind of error when i try to use it on more than one column.

@jsangilve nice fix, I'll merge it on next version if without any critical bug 👍

Hi all, this is released on v4.0.5.  Example like @jsangilve mention above. and thanks  @jsangilve  again.


[Question] one to many relation

Thanks a lot for your ORM. Really cool.
Tell me please what is the good practice to make one to many relation. And check the ref.
Example:
const collection = new Mongo.Collection('authors')
const Author = Class.create({
  name: 'Author',
  collection,
  fields: {
  name: String,
  }
})

const collection = new Mongo.Collection('books')
const Book = Class.create({
  name: 'Book',
  collection,
  fields: {
  title: String,
  (*)author: String
  }
})

What i have to write here (*) as a type String , or Author if i need a ref to author. In documentation i found only an examples for nested Class without collection

You don't have to specify author field in this case. You can create helper that will retrieve document.
const collection = new Mongo.Collection("authors");
const Author = Class.create({
  name: "Author",
  collection,
  fields: {
    name: String
  }
});

const collection = new Mongo.Collection("books");
const Book = Class.create({
  name: "Book",
  collection,
  fields: {
    title: String
    authorId: String
  },
  helpers: {
    author() {
      return Author.findOne({
        _id: this.authorId
      });
    }
  }
});

const book = Book.findOne();
const author = book.author();

Thanks a lot


Direct PWM control of the main outputs.

Please use PX4 Discuss or Slack to align on pull requests if necessary.
Test data / coverage
Tested with SITL, video shown below:
https://drive.google.com/open?id=1ojMMRyiiii7A6pIMROro7hTnzVVwQ9em
I can provide logs (is it possible to take them from SITL?)
Describe problem solved by the proposed pull request
This PR enables direct pwm control of the motors by bypassing the mixer results. A control mode flag is set when mavros ActuatorControl->group_mix = 99 (this shall be changed by something more convenient, maybe a change on the message definition to add a constant for that. This control flag is verified at the FMU level (and on PWMSim for the simulation part), and if true, then the actuator_controls from the mixer are overridden. This happens before the safety constraints, so the user inputs still go through them to make sure they are bounded and within the usual limits.
This is a desired feature from the Automatic Control standpoint, as there is the need to have a very low-level control on the vehicle. This solution also does not interfere with any other modules or safety measures/routines.
Minor: fixed a small leak on the FMU, where the _adc_sub was not being unsubscribed at the destructor.
Describe your preferred solution
Proposed solution.
Describe possible alternatives
Additional context

I think I did something wrong on the merge. Give me a few moments

Please rebase on top of master instead of merging master into you branch

Please rebase on top of master instead of merging master into you branch

Yep, should have done that instead. Will take care of it in a second.

@bresch  should I open another PR?

PR to master here: https://github.com/PX4/Firmware/pull/10863/


Fix 'fist' typo

Related issues
#3490
Short description and why it's useful
Fixed typo

Please just upddate the changelog; thanks!

Thanks!


Terminal example/documentation

With merge #84, documentation should be updated and an example added.

While building documentation plugins are also documented using the doc strings present in the own plugin. So an example can be added direct to the doc string, python styling can be done with
.. code-block:: python follow by indentation.

Nice, that would be a good way to approach.


Add var.policies_by_name_enabled

what

Add var.policies_by_name_enabled

why

Currently only spacelift.settings.policies_by_name_enabled can add a custom policy in a local rego-policies directory
With this change, we should be able to set default local policies to attach to all stacks

references
https://github.com/cloudposse/terraform-spacelift-cloud-infrastructure-automation/blob/debd62a58595429714e28424bc460eea57c69a5e/main.tf#L25-L39

/test test/bats

/test test/readme


add-comment@v1 backticks causing format issues in dry run output

Describe the bug
There's an extra backtick here:

which misformats here

it should render like this

to add the following reviewers johnlock

To Reproduce
Steps to reproduce the behavior:

I'm using this automation

  assign_previous_contributors:
    if:
      - {{ not pr.draft }}
    run:
      - action: add-comment@v1
        args:
          comment: |
            {{ repo | explainRankByGitBlame(gt=25) | dump | safe }}
      - action: add-reviewers@v1
        args:
          reviewers: {{ repo | rankByGitBlame(gt=25) }}

and then running it in dry mode

Expected behavior
it should output without the extra backtick so it renders like this

to add the following reviewers johnlock

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Afer looking more closely, this happens anytime using add-comment@v1 cause it seems to assume a short single-line comment like

add comment foo bar baz

but if you do a multi-line comment, like the explainRankByGitBlame dump, then you get a leading backtick as well before the comment and that tailing one causing mis-formatting
can see the leading one here:

it would probably be better to have add-comment@v1 start the comment on the next line and not add any of its own formatting in dry run

@michaeldrotar can you re-check this?

@vim-zz We're seeing similar behaviour!

I have an update to share on this. Our roadmap contains plans to rework gitStream testing capabilities over the next couple of months, and this will be either fixed or reworked as part of that initiative. Stay tuned!


Added route & controller for Acquire-inperson.html

(we don't really need all these controllers do we?)

Lol. we will see.


CSP missing when ssr = false

I am not 100% sure if this is an issue with nuxt-security or some underlying issue with nuxt.  It is easy enough to replicate and then let me know if it would be better to open an issue on Nuxt's repo.
Version
"nuxt": "^3.2.3",
"nuxt-security": "^0.12.0"

Reproduction Link
https://github.com/jfbloom22/nuxt-starter-generate-csp
Steps to reproduce

npm install
npm run generate
View the /dist/index.html file and observe that the content-security-policy meta tag is not there

What is Expected?
I expect the content-security-policy meta tag to be there.
What is actually happening?
It is generating the index.html without the content-security-policy meta tag.
If you switch ssr = true in the nuxt.config.ts.  run npm run generate again.  The content-security-policy is in /dist/index.html.

Hey,
can you check this issue?
https://github.com/Baroshem/nuxt-security/issues/123

Yes that is where I got the stackblitz you shared.  I was not able to replicate the issue in stackblitz directly because I do not have access to the /dist folder.  FYI the only thing I changed was adding ssr=false to the nuxt config.

I see.
So if I get this right, the problem only appears on the IOS device? On web and Android it works. This is quite strange. Not sure if I can do anything about it from the module side :(
If you use yarn generate without setting the ssr=false does it make any difference?

The issue effects all 3 platforms, all of them do not have a CSP.  The difference with iOS is that the Capacitor app does not work at all without a CSP.
Yes, yarn generate with ssr=true results in the CSP being added.
My suspicion is that there is something different about the build process when ssr=false.  I wonder if it is even calling the nuxt-security module?  Any suggestion on how I can verify that?

Hey @jfbloom22
Not sure what can be causing the issue then.
You can try to see if for example there are other response headers being set or other security middleqares being applied like rate limiting.
Other than that, I do not know how to help you with that. This is rather an edge case for this module as it is meant to be used in classic web apps.

@jfbloom22
Any additional info here?

Closing the issue as it is an edge case and out of the scope of the regular module behavior (web app).
If there will be more traffic in this topic, the issue can be reopened :)


some linguistically odd head choices

[item from the old TO-DO file dated 2002-04-07]
In
(NP (NP (DT the) (NN computer) (NN language) ) (VP (VBN called) (S (NP-SBJ (-NONE- *) ) (NP-PRD (NNP UNIX) ))))

we currently get Unix as the head of an S.  Yuck!  Many nouns show up as heads of S, in exactly this configuration - the superficial object of"called.
SBAR -> @ WHNP S/NP, e.g., "in which we trusted," is currently headed by "in".  Should probably be headed by the WHNP, with "in" marked as moved, as in "which we trusted in."

[item from the old TO-DO file dated 2002-04-07]
Copular VPs should probably be headed by the predicate part.  Think of the copula as a function word feature that turns an adjective or noun into a VP by giving it appropriate inflectional features (not necessarily tense, though).  This should help with tough-movement.

[item from the old TO-DO file dated 2002-04-07]
Munge corpus to let "less" and "than" be sisters, or parent and child, in "less X than Y".  (Currently, X is chosen as the head child, so "less" and "than" can't see each other.)  Similarly for other paired comparatives.

[item from the old TO-DO file dated 2002-04-07]

When the head of a constituent is a function word (preposition or complementizer), consider splicing the subconstituents into the parent, so that the arguments of the function word become arguments of the parent.  This should also be done for verb groups -- where I chose to mark "to have slept" as headed by "slept," I should have marked it as headed by "to."  Then under this convention, "to," "have," and "slept" would all have been generated by the parent (say, "seemed to have slept").

This does lose a little bit of what looks like phrase structure, because, for example, some PPs also contain adverbial modifiers: "from 9.45% a week earlier" (or, "in October"), "rather than another industry," etc.

But that should be handleable in terms of edit ops.  Just insert the modifier next to the preposition or its object ... ?

Think of whole generative model as successive edits??  Start with root word, add dependents, etc. ...  flesh out context-free frame that way.

Oh - that suggests that a sequence of edit ops can't necessarily be modeled as a transducer or FSA - we have to be careful that it's not allowed to recurse, e.g., rewrite X as AXB and repeat.  Rather like models of phonology.

Some desirable benefits: "information on whether ..." should allow a correlation between "whether" and "information," since "whether" isn't a typical object of "on"!

"from X to Y" is currently marked in Treebank as PP -> PP PP, and in flattened version as from NP PP.  We might prefer "from X to Y" to all be kids of the verb.

Much better -- use conventional heads, but when inserting lexemes, treat function words as transparent.  This does mean that we can't use the n^3 algorithm, though.

Well, this isn't so good, because "want John to go" has a problem: if "to go" is headed by "to," then we can't make "John" the subject of "go" without crossing links.


Wrap OpenCL code

Right now, the code for setting up and using OpenCL is repeated (lensed.c, input/objects.c). Also, the inclusion of the OpenCL headers is done whenever a cl_* type is used. This should be done in a central place (kernel.c?) to avoid repetition. The OpenCL types should probably also be wrapped (which would help if #9 is ever worked on).

I'm closing this, as #163 provides what the issue asks for. If there is need for further wrapping of OpenCL, we can open separate issues.


Project with MetalPetal can't be started on iOS 10, 11, 12 simulator

Checklist

[x] If possible, I've reproduced the issue using the master branch of this repo
[x] I've searched for existing GitHub issues

Steps to Reproduce
Start app on iOS 10, 11, 12 simulator.
Expected behavior
App able to start and all parts work, except MetalPetal.
Actual behavior
App get crash on start:
dyld: Symbol not found: _OBJC_CLASS_$_MTLHeapDescriptor   Referenced from: /Users/Igor/Library/Developer/CoreSimulator/Devices/9D277DE8-9F3D-4A95-B225-F11E1A2B65F5/data/Containers/Bundle/Application/7EDAAF53-2A7C-4811-94C2-8F62072B1ACA/Unfold.app/Frameworks/MetalPetal.framework/MetalPetal   Expected in: /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 11.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/Metal.framework/Metal  in /Users/Igor/Library/Developer/CoreSimulator/Devices/9D277DE8-9F3D-4A95-B225-F11E1A2B65F5/data/Containers/Bundle/Application/7EDAAF53-2A7C-4811-94C2-8F62072B1ACA/Unfold.app/Frameworks/MetalPetal.framework/MetalPetal (lldb)

Looks like a bug of the simulator runtime.
The simulator runtimes prior to iOS 13 do not have the MTLHeapDescriptor symbol defined.  An app is likely to crash when runs on iOS 10, 11, 12 simulators if it contains MTLHeapDescriptor related functions, even if it does not use MetalPetal.
And unfortunately we can not fix this on our side. AFAIK there's no way to conditional compile only for iOS 10, 11, 12 simulators.
If you do not use heaps. You can try deleting the MTIHeapTexturePool class (in MTITexturePool.mm file), it should make the iOS 10, 11, 12 simulators happy.

Thank you, I commented lines 351-357 in Pods/MetalPetal/Core/MTITexturePool.mm and it works.
351        MTLHeapDescriptor *heapDescriptor = [[MTLHeapDescriptor alloc] init]; 352        heapDescriptor.size = key.size; 353        heapDescriptor.resourceOptions = key.resourceOptions; 354        if (textureDescriptor.hazardTrackingMode == MTLHazardTrackingModeDefault) { 355            heapDescriptor.hazardTrackingMode = MTLHazardTrackingModeTracked; 356        } 357        heap = [_device newHeapWithDescriptor:heapDescriptor];

Hello @YuAo
I meet this issue, too.
I can avoid this crash by deleting that codes as you mentioned, but can you make old version  simulators happy more easily by adding #if !(TARGET_OS_SIMULATOR) and #endif to project? :)
Thanks!

@donobono That would make the MTIHeapTexturePool unavailable on all simulators. I think a better approach would be referencing the MTLHeapDescriptor dynamically using the Objective-C runtime.
Can you try this?
#if TARGET_OS_SIMULATOR
MTLHeapDescriptor *heapDescriptor = [[NSClassFromString(@"MTLHeapDescriptor") alloc] init];
if (!heapDescriptor) {
    if (error) {
        *error = MTIErrorCreate(MTIErrorFailedToCreateHeap, nil);
    }
    return nil;
}
#else
MTLHeapDescriptor *heapDescriptor = [[MTLHeapDescriptor alloc] init];
#endif


feat: enhance environment-specific configurations and refactor codebase

Enhanced the configuration and database connection setup to support multiple environments in config.py, database.py, dependencies.py, and main.py. Key changes include:

Config.py:

Added a new setting ENVIRONMENT to dynamically adjust configurations based on the development, production, or custom development environment.

Database.py:

Refactored EngineConnection class to adjust the database URL based on the environment specified in config.py. This allows for distinct database connections for development, production, and a specific development setup.
Simplified session handling by directly returning sessions from the EngineConnection class.

Dependencies.py:

Updated get_db function to enhance session management, ensuring sessions are correctly opened and closed, providing a cleaner and more error-resistant handling.

Main.py:

Modified the lifespan context manager to conditionally handle SSH connections in development environments only, reducing unnecessary connections in production.

Test/router.py:

Updated the test router to include a route for fetching service settings, ensuring that the service settings can be dynamically retrieved and tested.

These updates not only refine the backend's configuration management but also align the codebase with best practices for handling multiple environments, improving maintainability and scalability.

looks good to me


Figure out a nice way to track changes of an entire graph.

Useful for autosaver & isdirty.

Changetracker fixes this.


Vertical scrolling for multiline input textfield implemented

Currently we don't have any vertical scrolling of the multiline input textfields. So if you add more lines of text than textfield can display, they won't be displayed. Normally the text should scroll as more text is added.
Additionally vertical and horizontal scrolling with up/down arrow keys is implemented and scrolling when the characters are being removed with backspace and delete keys.

Addressed in #2108, but this helped inspire some of the fixes!


use a waitgroup to wait for reserve holders of MFiles before unmapping

WHAT is this pull request doing?
Please fill me in.
HOW can this pull request be tested?
Specs? Manual steps? Please fill me in.

Two things that we probably must remove

unmap from Queue#rm_consumer
unmap from USR2 handler

Two things that we probably must remove
* unmap from Queue#rm_consumer
* unmap from USR2 handler

I don't know, both call MessageStore#unmap_segments, which doesn't unmap the last segment that is still being written to.
https://github.com/cloudamqp/lavinmq/blob/c8ca36a93bfefbbf6f3b9f2d8cb6c4faa39013b9/src/lavinmq/amqp/queue/message_store.cr#L231-L237

I don't know, both call MessageStore#unmap_segments, which doesn't unmap the last segment that is still being written to.

Isn't it possible that a segment that isn't yet fully replicated is unmapped? If it's a large message I think the unmap may occur in the middle of the lz4 compression.
Will these unmaps be necessary if we handle unmapping properly, which this PR hopefully solves?

I don't know, both call MessageStore#unmap_segments, which doesn't unmap the last segment that is still being written to.

Isn't it possible that a segment that isn't yet fully replicated is unmapped? If it's a large message I think the unmap may occur in the middle of the lz4 compression.
Will these unmaps be necessary if we handle unmapping properly, which this PR hopefully solves?

True, there's a chance for that, if the unmap is triggered just when we're rolling over to a new segment.
And yes, shouldn't be needed anymore.

also started to tinker with a ref counter as you did, but yes, it fast gets messy, as we return a BytesMessage from MessageStore, but it points into the mmaping.. so we don't know when the client has sent them..
class MFile
  @counter = 0
  @counter_lock = Mutex.new(:unchecked)

  def borrow : self
    @counter_lock.synchronize do
      counter = @counter
      if counter.zero?
        mmap
      end
      @counter = counter + 1
    end
    self
  end

  def unborrow : Nil
    @counter_lock.synchronize do
      counter = @counter -= 1
      if counter.zero?
        unmap
      end
    end
  end
end


Updated PR 304

Pull Request Template
script name - Scrape Wikipedia using speech recognition
What have you Changed
Updated readme and requirements file
what you changed in the codebase.write here
Issue no.(must) - #300
Self Check(Tick After Making pull Request)

[x] This issue was assigned to me.
[x] One Change in one Pull Request
[x] My file is in proper folder
[x] I am following clean code and Documentation and my code is well linted with flake8.
[x] I have added README.md and requirements.txt with my script

If issue was not assigned to you Please don't make a PR. It will marked as invalid.
Join Us on Discord:- https://discord.gg/JfbK3bS
acknowledgement

[x] I have tested the script and distributing it under MIT license.

@codePerfectPlus Okay, working on it.


[Copilot Workspace] Allow all valid github repo characters

Description
GitHub allows letters, characters, numbers, ., -, and _ in repository names. Currently, this extension fails if using anything besides letters and numbers.
This change to the regex fixes that.
Screencast
Failure:

GitHub allowed characters?

Checklist

[x] I read the extension guidelines
[ ] I read the documentation about publishing
[ ] I ran npm run build and tested this distribution build in Raycast
[ ] I checked that files in the assets folder are used by the extension itself
[ ] I checked that assets used by the README are placed outside of the metadata folder

Updated CHANGELOG.md so checks will pass

Nice, thanks for the fix!


Bundler not seeing rbenv installed ruby.

rbenv version returns:
2.4.1 (set by /Users/engarcia/.rbenv/version)
Running bundle install gets the following error:
Gem::InstallError: nokogiri requires Ruby version >= 2.1.0.
An error occurred while installing nokogiri (1.8.0), and Bundler cannot continue.
Make sure that `gem install nokogiri -v '1.8.0'` succeeds before bundling.

I've looked at #831 also and tried those suggestions (blow out shims) and had no success.

Fix for Linux:
https://github.com/flapjack/omnibus-flapjack/issues/72#issuecomment-157908599

Sorry, this doesn't sound like a bug with rbenv. Rbenv merely switches between Ruby versions. Gem installation issues are their own problem and not something rbenv affects at all.


TMDM-9903 : [DI] Support merging task in TDS taskoutput component (re…

…factor)

Pull request test result: success :star:

OK to merge


teraranger-description: 1.0.0-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository teraranger-description to 1.0.0-0:

upstream repository: https://github.com/Terabee/teraranger_description.git
release repository: https://github.com/Terabee/teraranger_description-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.5.26
previous version for package: null

teraranger_description
* Update README.md
* Initial commit
* Contributors: Zurad Krzysztof, Kabaradjian PL, Potier Baptiste

Same comment as on #15940.

Indeed, naming was corrected also.

Same comment as https://github.com/ros/rosdistro/pull/15940#issuecomment-330267102

Package section also removed.

Conflict solved.


Improve perf analyzer flags documentation

Looks good. Thanks for cleaning this up. Seems to be tripping up a lot of people


Mise plugin for Crystal

Feature Request
It would be a good marketing opportunity as well as a convenience to support Crystal in Mise:
https://github.com/mise-plugins

Sure. Any integration would be nice.
But I don't think this is a natural feature request for the upstream project.
Such integrations are best handled by people who are actually familiar with the tool. The asdf plugin for example is also community maintained.
Feel free to coordinate efforts on https://forum.crystal-lang.org/


Minify Inline CSS

Version
v2.1.0
Reproduction link
https://nuxtjs.org
Steps to reproduce
If you add CSS via Nuxt config, that CSS is minified and inlined into the page head.  Component CSS/SCSS is inlined after the Nuxt config global CSS, but not minified.
What is expected ?
All inline CSS should be minified (both global via Nuxt config, and component CSS).
What is actually happening?
Only global (Nuxt config) CSS is being minified.
Additional comments?
I really don't think a reproduction link should be required.  It should be strongly encouraged, but it's often unnecessarily onerous.
Reporting bugs should be easy and quick.

This bug report is available on Nuxt community (#c8121)

@bjunc A reproduction link is always encouraged (if the bug is reproducible in any manner). With CodeSandbox (template link) this is a matter of minutes for the reporter and makes debugging for the maintainers easier, which results in faster bug fixes.
Reporting bugs should be easy and quick, no doubts, but reproducing them should be as well! :relaxed:

About the actual issue:
CSS is minified properly.
There is a vue-loader issue that line-breaks aren't removed properly A fix is already in progress:
https://github.com/vuejs/vue-loader/issues/1395
https://github.com/vuejs/component-compiler-utils/pull/30

Thanks for the quick response.
I understand the desire to minimize triage / diagnose; which is why I said encouraged.  I stand by the statement though, that making reproduction examples / repos mandatory is onerous.  In this case, I'm not really sure how it could be reproduced without actually building and deploying somewhere.  Does CodeSandbox allow this?  If not, what exactly would you have liked me to do?  Build and deploy to Heroku?  Is that still a matter of minutes?
Per the actual issue, thanks for the links.  I'll keep an eye on the pull requests.

@bjunc
If there is really no way to reproduce the issue easily then it's fine from my POV to input a random URL. In your case, a CSB (even in dev mode, because you can't change the default command there, Feature Request is already submitted) would be fine though, so downloading the example and running it on the local PC is easy for maintainers. Screenshots from the problem or a portion of the non-minified code would be fine as well.
I see your point and I agree that there are exceptions in terms of providing a reproduction URL, but I see more bugs without an URL where the reporter could've easily created a reproduction than the ones where reproduction is too hard/tedious/...

I understand.  You guys get bombarded with "bugs" that are really just help requests / user error.  Insisting on a reproduction URL probably weeds out a lot of those.  In this case, I felt it necessary enough to enter a random URL, but I could see how that could be abused (annoying).
Again, thanks for the quick reply.

@bjunc You are welcome! Thanks for the report and for addressing the reproduction URL topic :relaxed:
Feedback is always appreciated :+1:

@manniL which deps?  Currently running Nuxt v2.3.4, which was released in November (before your comment above).

@bjunc yarn upgrade/npm update should update the vue deps nuxt has automatically.


FEAT: Start LAMP Ad-Hoc Task with Github

This change allows LAMP Ad-Hoc ECS Task to be triggered with github action.
Ad-Hoc ECS Task created by devops PR: https://github.com/mbta/devops/pull/2184
Asana Task: https://app.asana.com/0/1205827492903547/1207556073650893

👍
I assume the devops PR should go first before this gets merged?

Yup, I will wait to merge until the devops PR has been fully closed!


Unsupported payload type error msgs from BRs

I have investigated the huge size of log files generated by BRs running on Core ASes, and I observed that most of the error msgs are about unsupported payload type pldType="*scmp.Payload" and Error validating packet.
The error msgs are produced only from the BRs connected to AWS machines.
The followings are the actual logs for the each case.
=============== log type: 1 ===================================================

2018-03-19 06:43:33.755293+0000 [EROR] Error processing packet rpkt=a2fe648a err=
Unable to process unsupported payload type pldType="*scmp.Payload" pld="Meta: Info=85 CmnHdr=1 AddrHdr=2 PathHdr=3 ExtHdrs=0 L4Hdr=1 L4Proto=UDP
>   Info: InfoF=3 HopF=5 IfID=3 Ingress=true RevToken=106a50040401030f358911090d05a002036054310d02011119e733690102013375010201ff78f9bb8de612e7f603417a12cf32707e2e2bcb74eb1b6fd0d533f85825705312bb51380101010131690201000031710201010131790201000031810201000031890201010131910201010131990201010131a10201010131a90201000031b10201000031b90201000031c10201010131c90201000031d10201ffcbd17620c91039ba3f20779922f912656a1bddd516ada01bb73e9d6375db900527d366bb3b397c4f97eac23995c303dfd06250e450dccf40596d094dcb44a9ad4124e3b0e31d4b7a4bbc34073392f372bd31a880ad18e8b5b58fa838835902374f950c08fee79668b4b47e6862a6a56adb0a55ed67717f0362bf1a7e3378884e2754da45a454eb1562f9675d63f657e2612363c28ab43f5babc6a483492d3e3ce8e18b76dbb8d62abf13aef9f7f9d4660fed59381da20af0fe9e32d3e8cc173b28853ec499f34ee1bc94c2a258aae899b21cbd6bb3f5a5aac7e658162175fe6f2ce6e78a9cd952f599f486fa4a540ad7ef0078ee22a0c2b049607dd51d5d262d6871fe4b9e86cdb44631d5a261a03f978623563c6ca3a1fbea63c329166b4f386638b0f115d887ffce70acb449b6924451fe83b240bd01ca795f996454903114ea395ac640e40991b3c6fdc20c59757757ad893e5a00e8d58b11c01ab90f584fbac662a5b5799aa0993654587a4193e2ab389c4961116c89281b617e2db7f15e10e851a2f3630ac1097b674b19cd3f59345973f03950ba83ce0d37d24efc1f7042a6b482f4ca647b01cb77b4be81dfc425ae22a5c4b0af90fd0772bc4562bf6a21960ee271544982d3994aaea7359296739099e487de3fbdde620133fdcf4565b5b863b7b2ecc2090fbfa12b1fa861afe791a4bc6ae035fa63d9920c22e05967ff
>   CmnHdr: 00c1034d06030500
>   AddrHdr: 02a0000502a0000700000de56b8d0000
>   PathHdr: 005aaf5c15002a020040000003f0f831003f00300015bebc
>   ExtHdrs:
>   L4Hdr:<PHONE_NUMBER>15e38f
>   "

=============== log type: 2===================================================

2018-03-20 15:26:46.206004+0000 [EROR] Error validating packet rpkt=94d0e2d5 err=
Interface revoked ifid="0xc4212cced8"
CT: PATH(3):REVOKED_IF(4) Info: InfoF=3 HopF=4 IfID=3 Ingress=false RevToken=106a50040401030f38b711090d03a002036054310d02011119e733690102013375010201ff60b59d6cd4c945e7035fb7e45fb437ebd317a57ca110d8debef05d2be4a12745b351380101000031690201000031710201000031790201010131810201010131890201010131910201000031990201010131a10201010131a90201000031b10201010131b90201000031c10201010131c90201000031d10201ff4e0fb427a97ba1aa3fdffb26e834b00bf638a950270e48f933f89124f6f8eac056f7124b5c3353beb780274e0ad071b96706d0facf8b865af3ca7c71820e942836bb91e0b38e9b81b5e3bd221c4fc07eded7e6bc3f816eeab68c4a494d22d5991c4d35ada49ef5000fa35540b5ff720d014943aa395d0bd15206b51f21bc86efbd2260c38a902cd7fccab16a268c167ee70bd552466ae41c3bb97876bc99470ac50c970db5846fc1a97c53da745deb7c8be2cf3a20ae04c3949dfff1c4e6ffbde47fd782195c07bd009f032ddfbf12de94b0171845d189fbc3aa692945750fceb802f6e1026a8c6ccc2e38d9f658a16846799c168d0b957bb8332b47b3f7adb4ed0f0e796e1a1793b266c09f9058b1c92d41b9f5a90872e7e088079cca1d3dc8daf4656abcc4718d94825e5f974ede3f5310148224405ce7d456b0e7ef4b040928ce107f04eeeed27815d9d21048c1f0bcdd641631a560ecc4e4118367304973745015670a6655bff3303dfff9c44c02f09396671dd6d7be3951da0d5e819ffac0eecc353e7bcd94b0b66e3a6059e2848850b655e06c284487a46a756603c1bef1ce6b8cd8027444b123ea54f94a77b21f4c74e8d1cd22acb42c2e2d58bcf8fccfa6aff712b0f46f84246278fe0acbbd41e69b955e67aa97cb16b477b77bc82548e8dc3068f93c44ca42e0366eaf4d9444c2c4061a8c634c0dbd922519265203ed

Updating based on the slack discussion:
The second log entry is known - we should just stop logging when we receive a packet for a revoked interface, and just export a prometheus metric instead.
The first type happens when a BR is running on the same IP as other services, and thus intercepts scmp errors received over an interface that are destined for that IP. If this happens when the other side of the link has revoked their interface, then the revocation will never be handled properly, and the local AS will never be informed about it, so traffic will keep trying to use that interface.
The basic issue here is that the BR would need to have support for parsing all possible SCMP error types in order to determine who they should be delivered to. Until we have that, running a BR's interface on the same IP as any other service is not supported.

This is from the legacy router, does not apply anymore.


Unify tokenizers

🚀 Feature Request
With #305, we now have two ways to specify a tokenizer: with the GPT2 tokenizer (provided as two files), and with the universal HF format (specified as one file). These are in two separate code paths, but they don't need to be: we could (manually) merge the two GPT2 files into the universal HF format and switch to only that, and we should.
The resulting code would be cleaner, but catching all the other places the old method is used (e.g. API and old sweeps) needs thorough review.

I'm interested in picking this up. I'll give it a try! :)


Issue264 fixed

This PR fix the issue #264. This issue is related to pcolor similar to issues #263 and #265. Then working with this issue I was careful to ensure that modifications works for all this issues (#264, #263 and for #265)
to test it please use following code:
C = hadamard(20);
pcolor(C)

fig2plotly(gcf, 'offline', 1, 'TreatAs', 'pcolor');

results looks as follow

Good.


tpc provider: terraform templates: fabric

I believe this most closely equates to the triton fabric resource, not yet released. See https://github.com/hashicorp/terraform/blob/master/builtin/providers/triton/resource_fabric.go

There is no overriding vpc. Each subnet will be created with the fabric resource.


Save graph position

When I add nodes or remove them and redraw the graph, the position of the nodes jump, and it redraws in a random configuration.  I'd like to be able to save the position in the session state, and any redrawing would happen with the physics on it so added nodes would appear smoothly

@thestumonkey Did you ever find a solution for this?

I was thinking of adapting,
https://github.com/ChrisDelClea/streamlit-agraph/blob/master/streamlit_agraph/frontend/src/StreamlitVisGraph.tsx
to return the node positions at enddrag, but I am having a hard time
getting the code to run locally. Have you gone through that process?
On Tue, Jan 9, 2024 at 2:13 PM Stuart Alexander @.***>
wrote:

I'm afraid not :(
—
Reply to this email directly, view it on GitHub
https://github.com/ChrisDelClea/streamlit-agraph/issues/44#issuecomment-1882962478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2S35KGIGBWXXFSJ5GSCTDYNUX5TAVCNFSM6AAAAAAYW6GLO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBSHE3DENBXHA
.
You are receiving this because you commented.Message ID:
@.***>


Java 11 JRE's from adoptopenjdk are not supported

The task createBundleJRETask ends up copying into the bundle nothing, as the directories are all excluded. For example, there is no longer a JRE directory (which is what is included in the task). Perhaps some logic that looks into the Info.plist of the 'JRE' to determine its type and what needs to get copied over.
The JRE is downloaded via an API at https://api.adoptopenjdk.net/v2/binary/nightly/openjdk11?openjdk_impl=hotspot&os=mac&arch=x64&release=latest&type=jre

This isn't limited to adoptopenjdk.  It is Java 11 in general.  For example, Amazon Corretto's JDK 8 works but JDK 11 doesn't since there isn't a jre directory in Java 11.


Not Using Nunjucks

Firstly, let me just say this is awesome and thank you to the author and other contributors. In my use case, I wanted to see if I could build an AngularJS application.
This mostly worked except what I discovered was that the "html.js" task (in gulpfile.js/tasks/html.js) hard coded the "Nunjucks" render call and there wasn't any easy way to prevent this via configuration [i.e. one couldn't turn it off in config.json].
Unfortunately, this makes Angular's default templating (using {{ and }}) "go away".
What I did to fix this was change "html.js" to (including only lines 10-13):
 10 var path         = require('path')
 11 //var render       = require('gulp-nunjucks-render')
 12 var render       = require('gulp-empty') // Don't and make sure this is installed
 13 var fs           = require('fs')

A better way would be to add some sort of configuration switch but am wondering if this is worth doing (before I do a pull request, figure out how to test it properly etc etc).
On a side note, it seems that Nunjucks is/may be rendering in the gulpfile.js/iconFont/generateIconSass.js as well (but this doesn't appear to make anything Angular fall over).
I'd make a plunkr to demonstrate this but I think it's a fair diagnosis to say that the Nunjucks vs Angular templates conflicted with each other.

Hmm... so nunjucks templating would still be useful if there wasn't a conflict, right?
I googled Angular Nunjucks and found https://github.com/mozilla/nunjucks/issues/397. Looks like there is a configuration option to change the syntax. https://mozilla.github.io/nunjucks/api.html#customizing-syntax
Seems like we should expose Nunjucks options in the config.json file. Would that solve it for you?

Angular can be reconfigured as well but it would be useful, I should suppose, to be able to configure nunjucks from the config.json as I'm sure there's other configuration variables it has that might be useful to others.


[9.4] ISPN-10561 Upgrade to Jackson Databind <IP_ADDRESS>

https://issues.jboss.org/browse/ISPN-10561

integrated! thanks @tristantarrant


fix(ui): units are now kg and kWh

Leave all graphs with units in kg and kWh.
Emission comparisons are using now the ones from https://github.com/mlco2/codecarbon/pull/564.

Note that now the graphs and comparisons are very small

Thanks Inigo! Indeed the artificial x1000 factor was added to visualize graphs for dev.

On the page we say "days Of watching TV" but here we compute minutes of TV : const TV_CO2_EMISSIONS_PER_MINUTE = ((100 / 1000) * 0.475) / 60;

Nice catch thanks @benoit-cty ! I updated it here --> https://github.com/mlco2/codecarbon/pull/728/commits/13fc80c90566e2a0d4339e5530c67153fbe8d99b


(doc) Fix throw desc for sampling funcs

NotStrictlyPositiveException is for non-positive numbers, i.e., negatives together with 0. But current Javadoc for sampling functions describes it for only negatives. To include 0 also, change negative to not positive.

Coverage decreased (-0.005%) to 89.952% when pulling 3f6f64144e5f2dedb8e971c1b2f412cf4a504d97 on hangpark:doc-MATH-func-sample into 777af155a678286614d261887790352b43fa7c2a on apache:master.


Modify a statement

Regarding this warning: https://docs.microsoft.com/en-us/aspnet/core/test/troubleshoot?view=aspnetcore-2.2#the-net-core-sdk-is-installed-in-multiple-locations
Not only the x86 SDK should be removed, but also the x86 runtime.
Thanks for your continuous support for .net core. I see your generous efforts everywhere

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

ID: 967496ea-59b6-1f17-4f39-1e4c232126c6
Version Independent ID: 09bb2010-fe5c-1061-23ec-a0dcc92bdd3f
Content: Troubleshoot ASP.NET Core projects
Content Source: aspnetcore/test/troubleshoot.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@shadinamrouti  thanks for pointing that out. Can you PR this?


White screen

your setup works fine on the browser, but on the emulator, I am getting a white screen,
no error message on debug screen also using chrome inspect

I'm using this repo model on two projects, one of which is on both browser and devices (iOS & Android), and haven't come across this type of issue. I suspect the white screen is owing to some other issue and not related to the monorepo structure, which is what this is all about.
Pls have a look at your code again and let me know if you managed to resolve the issue. If you didn't and if it's a public project, pls point me to the repo and I'll clone it and have a quick look at it myself.


Add runtime release-notes for 8.4.2

Added note to https://github.com/mendix/docs/pull/2157 for 8.4.2 RN.


Adds unexpected column after relation literal

What happened?
(From https://github.com/eitsupi/querying-with-prql/blob/4acff8fa395a9a2c33cad15ed61866dabac25157/docs/indexing.qmd#L166-L186)
Maybe related to #2392 and #2688
The following example appears to add an unexpected column _expr_0.

No response

This is expected behavior: relation f has 2 columns: {a, b}. derive adds a new column, named b. This undoes the name of the first column b. The result is {a, unnamed, b}.

This is expected behavior: relation f has 2 columns: {a, b}. derive adds a new column, named b. This undoes the name of the first column b. The result is {a, unnamed, b}.

Thank you for the explanation.
Could we have a description of this behavior somewhere? (To me this behavior is quite amazing)

Where would this go? To reference of derive?

Where would this go? To reference of derive?

I think that makes sense.
The behavior of something like derive with existing column names may vary from system to system, depending on whether it overwrites an existing column or adds a new column with a duplicate name, so I think it is worth writing about what behavior is expected.

This is expected behavior: relation f has 2 columns: {a, b}. derive adds a new column, named b. This undoes the name of the first column b. The result is {a, unnamed, b}.

I have to admit I didn't realize this. I thought derive overwrote a column (didn't it used to do this??)
I confirm this is the current behavior with something like:
from x
derive y = 5
derive y = 7

SELECT
  *,
  5,
  7 AS y
FROM
  x

-- Generated by PRQL compiler version:0.9.2 (https://prql-lang.org)

Is this the behavior we want? In my mental model, overwriting a column is a very frequent operation.

If I understand correctly, SQL does not allow us to overwrite columns when using * to select columns (unless all columns are obvious), although DuckDB has REPLACE to allow overwriting column.......
https://duckdb.org/docs/sql/expressions/star#replace-clause
I too think that being able to overwrite columns by derive would be ideal, but I doubt that the conversion to SQL will always reproduce that. (perhaps this problem is similar to #3133)

SQL does not allow us to overwrite columns when using * to select columns

Yes you're ofc correct.
When we know the columns, like in your example, then it would be useful to allow easier replacements: derive foo = (foo | round 2) would replace foo. This is how pandas / xarray works, for example.
Quick thoughts:

I think it would be too complicated to have a rule of "Replace if we know the columns, don't replace if we have *". So I think we're stuck with the current approach[^1].
It's not intractable — folks can just select foo at the end.
Maaaybe there's a replace transform which replaces, and only works when we know the columns, or for dialects that support it, similar to https://prql-lang.org/book/reference/stdlib/transforms/select.html#excluding-columns

[^1]: (I'm the person who was keenest on allowing easy use with *, so I only have myself to blame for this being difficult!)

I just stumbled upon this myself and would like to add that there is an inconsistency because the following works
from [{a=1}]
derive a=2
derive b=a+1

while the following doesn't:
from [{a=1}]
derive {a=2, b=a+1}

The first one produces:
WITH table_0 AS (
  SELECT
    1 AS a
)
SELECT
  a AS _expr_0,
  2 AS a,
  2 + 1 AS b
FROM
  table_0

-- Generated by PRQL compiler version:0.12.2 (https://prql-lang.org)

while the second throws this error:
Error:
   ╭─[:2:16]
   │
 2 │ derive {a=2, b=a+1}
   │                ┬
   │                ╰── Ambiguous name
   │
   │ Help: could be any of: _literal_118.a, a
   │
   │ Note: available columns: a, _literal_118.a
───╯

Some more data points:
While this doesn't work
from [{a=1}]
derive {a=a+1, b=a+1}

Error:
   ╭─[:2:18]
   │
 2 │ derive {a=a+1, b=a+1}
   │                  ┬
   │                  ╰── Ambiguous name
   │
   │ Help: could be any of: _literal_118.a, a
   │
   │ Note: available columns: a, _literal_118.a
───╯

, this does
from [{a=1}]
derive a=a+1
derive {a=a+1, b=a+1}

and produces
WITH table_0 AS (
  SELECT
    1 AS a
)
SELECT
  a AS _expr_0,
  a + 1,
  a + 1 + 1 AS a,
  a + 1 + 1 + 1 AS b
FROM
  table_0

-- Generated by PRQL compiler version:0.12.2 (https://prql-lang.org)

There are now two extraneous columns in the output which shouldn't be there.


How can we help?
None
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
Download Page Url: https://github.com/Advaith3600/PowerToys-Run-Currency-Converter/releases/tag/v1.2.0
Publisher: advaith3600
Package Name: PowerToys-Run-Currency-Converter
Description: PowerToys Run plugin which will convert real and crypto currencies.
Package Version: 1.2.0
Installer URLs:

https://github.com/Advaith3600/PowerToys-Run-Currency-Converter/releases/download/v1.2.0/CurrencyConverter-1.2.0-x64.exe
https://github.com/Advaith3600/PowerToys-Run-Currency-Converter/releases/download/v1.2.0/CurrencyConverter-1.2.0-ARM64.exe

[!TIP]
Adding Resolve #171128 to https://github.com/microsoft/winget-pkgs/pull/171128#issue-2500153831 can help linking that pull request to this issue. When the PR is merged, this issue will be automatically closed as completed.

Resolve #171128


[py2py3] Adapt to renaming of assertItemsEqual to assertCountEqual in py3

Fixes #10514
Status
In development
Description
assertItemsEqual has been renamed assertCountEqual in py3. Sometimes it's possible to use alternatives, such as assertListEqual, but that is not always the case.
I changed my mind: there are too many occurrences of assertItemsEqual, it would take a superlong time to fix them all, we can just use
# ../Module_t.py
class ModuleTest(unittest.TestCase):
    def setUp(self):
    ...
        if PY3:
            self.assertItemsEqual = self.assertCountEqual

and we should be good to go
Is it backward compatible (if not, which system it affects?)
yes
Related PRs
This changes have already been carried out in some other PRs related to #10422, but i do not have a list of them yet
External dependencies / deployment changes
nope

@amaltaro I am not sure that you like this solution, so I ask for your opinion with a comment instead of using the "official" button "request a review". Any suggestion is very welcome!

Honestly, when I read your question, the first thing that came to my mind was a method override, just like you did. It looks much cleaner than the previous approach - checking whether it's a PY3 test right before the assert. Yes, this is a neat solution IMO!

Good, thanks!
The other approach would be to find and replace assertItemsEqual to assertCountEqual, then use
# ../Module_t.py
class ModuleTest(unittest.TestCase):
    def setUp(self):
    ...
        if PY2:
            self.assertCountEqual = self.assertItemsEqual

This is the usual trade-off: more job now or more job for future-us

Given the current circumstances, the approach you have implemented looks more appealing to me.
If you are ready with these changes, feel free to squash them and fire a review request. Thanks

WMCore_t.WMBS_t.JobSplitting_t.EventAwareLumiByWork_t.EventAwareLumiByWorkTest:testNoFileSplitNoHardLimit should be in the list of unstable unittests, while the others changed from error to failure or vice versa. I have to admit that I am not paying too much attention to these cases

Let's run a few tests during the day today and update the list of unstable py3 tests then. I will take care of it, but please provide me with more unstable test names once you spot them.


implement archive --newer --larger  in addition to --older --larger

You can do this:
[peterdir@exahead2 ~]$ froster archive --larger 1000 --older 365

to archive old and large stuff
you should also be able to do  this:
[peterdir@exahead2 ~]$ froster archive --larger 1000 --newer 7

to identify newly created data

https://github.com/dirkpetersen/froster/pull/21


Restore non-recursive behavior of mutex wrapper

The recursive attribute has been replaced with normal in release or errorcheck in debug. The critical memory that caused the deadlock, data member cubeb_stream::panning, has been turned into atomic in order to ensure synchronization. Patch fixes issue #144 .

Thanks!


Streaming support

Close #10
The PR adds 2 structs CompressStream & DecompressStream to allow users to pass data for (de)compressing piece by piece, which helps to decrease memory usage when transfering data. Tests are included and all OK.
Some notable points:

Other than using stream (reader/writer) API of brotli crate (It is hard to export these Rust streaming stuff from WASM to JS), the PR uses low-level API BrotliEncoderCompressStream & BrotliDecoderDecompressStream (renamed as BrotliDecompressStream) to impl the feature
Other than reusing Options, CompressStream gets quality directly from args because I do not find a way (like skip_typescript) to disable all types of a class. That means I can not put a hand-written defination like function compress into typescript_custom_section.
Consumed input buf size, last_input_offset, is returned separatedly from last_input_offset method, because returning it together with Box<[u8]> in one struct/tuple/others is hard (for Box<[u8]>, may require importing JS Object to Rust AFAIK). Results of every piece are also returned via another method because of the same reason.
One test shows that streaming or not may affect the compressing result. Since it can be decompressed back to the original string, IMO it is expected.
Bundle size does not change

Left tasks:

[x] Streaming (de)compressing impl
[x] Basic tests from brotli.spec.ts for streaming (de)compressing API
[x] Specified tests for streaming (de)compressing API (like differring needing more input/output)
[x] Bundle size evaluation
[ ] Documentation or even quick start (maybe later)

 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.

To test the situation of compressing when output buffer is not big enough, the project may need to ship a large test-purpose binary file as test fixture. Since shipping a large binary file in a git repo is not good, I would like to ask for your opinions.

OK 10s timeout has been added and the PR has been rebased on latest upstream/main

Now published as<EMAIL_ADDRESS>Thanks for this! Just in case you're not aware, HTTP Toolkit is totally free for all open-source contributors to these repos (more details). Happy to set you up with an account if that'd be useful, just let me know.


build: android builds stuck in waiting_for_machine

It looks like both android builders are stuck [EDIT: the two emulators for x/tools: amd64-emu and 386-emu].  Not seeing any recent builds at https://build.golang.org. Example:
  builder: android-amd64-emu
      rev: 9e4dc6f37f75840d1193accae697a0e9283f5384
 buildlet: (nil *buildlet.Client)
  started: 2021-10-14 04:26:40.152387307 +0000 UTC m=+35583.719633009
   status: still running

Events:
  2021-10-14T04:26:40Z checking_for_snapshot
  2021-10-14T04:26:40Z finish_checking_for_snapshot after 22.8ms
  2021-10-14T04:26:40Z get_buildlet
 +34396.2s (now)

Build log:

(buildlet still starting; no live streaming. reload manually to see status)

CC @golang/release

N2 should support nested virtualization, which we need on the android builders for hardware acceleration.
That error you posted is actually a problem for a different builder, host-openbsd-amd64-64, which is the only one which sets MinCpuPlatform. I don't think we need to set that anymore, as #29223 is probably no longer an issue on newer VMs.

edit: ok, I am confused. sorry. It looks like we set that when we ask for nested virtualization.


[web] [ck] canvaskit 0.33.0 not compatible with iOS 13.7?

Evaluating a different issue: https://github.com/flutter/flutter/issues/90451, I found an error in Safari for iOS 13.7 that I hadn't seen before:

Aborted(no native wasm support detected)

It seems to come from the version of canvaskit that Flutter 3 is using (0.33), but it didn't happen in an older version (0.28.1):
With an iOS Simulator @ iOS13.7, take a peek at these sites, both deployed forcing canvaskit, but with different versions:

https://iosvideoissue.netlify.app<EMAIL_ADDRESS>-> works
https://dit-videoplayer-tests.web.app<EMAIL_ADDRESS>-> blank page, Aborted error in the console.

I understand that --web-renderer=canvaskit is not recommended for iOS devices, but I think this is a regression?

Are you sure https://iosvideoissue.netlify.app/ isn't dropping down to the HTML renderer?

It is indeed dropping to the HTML renderer :/ canvaskit (auto-selected) (when looking from desktop)

I'm going to close this, I created it without debugging properly. Sorry for the noise!


AKS missing API 2020-03-01 in Azure Government

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks show
Errors:
No registered resource provider found for location 'usgovvirginia' and API version '2020-03-01' for type 'managedClusters'. The supported api-versions are '2017-08-31, 2018-03-31, 2019-02-01, 2019-04-01, 2019-06-01, 2019-08-01, 2019-10-01, 2019-11-01, 2020-01-01, 2020-02-01'. The supported locations are 'usgovvirginia, usgovarizona, usgovtexas'.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks show -g {} -n {}

Expected Behavior
Environment Summary
Windows-10-10.0.14393-SP0
Python 3.6.6
Installer: MSI

azure-cli 2.3.1

Additional Context

aks

This is a known issue in the latest API not being published in Azure Gov, AKS team is investigating a resolution. cc @feiskyer

@jluk any updates when this will be resolved?

Working on it, should have an ETA this week thank you for the patience. cc @tomgeske

Deployment should be finished. @kringen let us know in case it still doesn't work.


'module' object has no attribute 'IntEnum'

pip list:

enum (0.4.6)
enum34 (1.1.6)
PyVISA (1.8)

trying to import visa gives the following error:

Python 2.7.11 (v2.7.11:6d1b6a68f775, Dec  5 2015, 20:32:19) [MSC v.1500 32 bit (
Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import visa
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "c:\Python27\lib\site-packages\visa.py", line 16, in <module>
    from pyvisa import logger, __version__, log_to_screen, constants
  File "c:\Python27\lib\site-packages\pyvisa\__init__.py", line 45, in <module>
    from .highlevel import ResourceManager
  File "c:\Python27\lib\site-packages\pyvisa\highlevel.py", line 22, in <module>
    from . import constants
  File "c:\Python27\lib\site-packages\pyvisa\constants.py", line 599, in <module>
    class AccessModes(enum.IntEnum):
AttributeError: 'module' object has no attribute 'IntEnum'

I have tried reinstalling both enum and enum34  and pyvisa . .I dont know what to do.. I can clearly see the IntEnum function in enum.py..

did you solve this problem? I am trying to run Pyvisa on python 2.6 and I am having the same issue?

Yes, there's a collision when using both enums. I'd say with 90% certainty that enum34 us backwards compatible. Try uninstalling both and reinstalling only 34

The problem was that enum was earlier in the PATH than 34, making it try that one first,  when it needed 34 functionality. Try :

import sys
print sys.path

I did this, and now I can import the visa library through no error. But then when I try to test using
rm = visa.ResourceManager()
it gives me an error.
OSError:could not open visa library
I am trying to run Pyvisa on a relatively old machine (Linux scientific 6.5) and python version is 2.6.x

Did you install the visa drivers from national instruments (for example) ?
http://pyvisa.readthedocs.io/en/stable/getting_nivisa.html#getting-nivisa

Thank you, I solved the problem some days ago, and it was as you suggested.


Fixed error message check in remote rendering tests

Packages impacted by this PR
Only the remote rendering package, but also only the tests, so no changes customers will see in any capacity.
Issues associated with this PR
Test failures on the remote rendering pipelines.
Describe the problem that is addressed by this PR
We changed some error message on the remote rendering service side, because the old messages were more confusing than helping. This broke the tests here, because it compared to the old messages still.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
We could revert the error message changes, but that would leave customers with less helpful information, so I wouldn't do it.
Are there test cases added in this PR? (If not, why?)
No, only changed asserts.
Provide a list of related PRs (if any)
None.
Command used to generate this PR:**(Applicable only to SDK release request PRs)
By hand?
Checklists

[x] Added impacted package name to the issue description
[x] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

/azp run js - mixed-reality-remote-rendering - tests

/azp run js - mixed-reality-remote-rendering - tests

/check-enforcer evaluate


core: fix configd asList helper

fixes the issue that if the element does not exist, I will get an array with a single element which is null element, which again breaks for loops

@fichtner this one is important to merge because @mimugmail found a bug in the nginx plugin caused by this misbehaviour. This bug may break other config templates too (maybe not found yet)

@fabianfrz thanks!

Does this touch ModelRelationFields? I have some reports that Wireguard Peers doesnt work after 18.7.2 but Wireguard itself stays same version. No idea where to look else

no, this should only affect ArrayField where this helper is used.
You will now get an empty array instead of one containing an empty value usually known as null. With the change, you cannot run into a NPE so easily because the for loops work as expected.


catch exceptions using sentry

Looks differently then what we use in frambo (sentry-sdk vs. raven), but I believe you this is the latest-greatest.

Raven is the legacy Python client for Sentry (getsentry.com) — replaced by sentry-python https://sentry.io

Should we change also our frambo code then?

Should we change also our frambo code then?

up to you, ain't touching that

I was just asking for your opinion, whether you think it's worth changing or we can leave it as it is.

I was just asking for your opinion, whether you think it's worth changing or we can leave it as it is.

I'd leave it if it works. Especially since we're using the internal instance.


Ability to pass Context to Visit method - Feature request

Some times it is necessary to pass data from wherever call Visit to onResponse, onHtml callbacks, So the best way will be passing context to Visit method!
If there is any other way to do this, please let me know!
Thanks

You can pass context using the Request method on the collector.
collector.Request(Metho, url, r, ctx, headers)

Also, you can use response.Request.Visit  instead of collector.Visit which automatically passes the current context to the next request.