Restructuring Discord into positive-sum

Goals
To create a positive collaborative environment, we need to build a Discord onboarding flow that encourages people to have skin in the game in order to meaningfully participate.
The aim is to remove the bystander effect and to establish a community where everyone is literally invested in the community's success.
This means that most channels except for a few (welcome channels, verification, help/bugs) will be locked down. Those that have a role that was either earned through past contributions or purchased as a NFT will be able to unlock all the other channels where the real activity happens.
Roles
It helps for new and old members to self-identify their specialties, especially when they first join. It's like choosing a class in an MMO. The most popular bot for reaction based role selection is Carl-bot, here are some examples from Metacartel and Raid Guild:

Here's what the interface looks like for setting it up:

I think its a good idea for the roles to not deviate too much from whats been established across several major DAO discords, came up with a starting base:
Welcome to the Webaverse Discord server. Please select as many roles which describe you.

:art: Artist
Painters, modelers, musicians, memers, videomakers, etc

:tools: Builder
Can speak with computers to make them do things

:triangular_ruler: Designer
Imagineers of how we interface with machines (UI/UX)

:writing_hand: Writer
From scribing notes to writing stories, specs, and guides

:bridge_at_night: Bridge Builder
People who bridge communities and help create more powerful networks

:mega: Shiller
Those that communicate the memes of Webaverse to a wider audience

Collab.land
This is the most popular one for unlocking roles with fungible and non-fungible tokens. Usually Discords will create a separate channel with the topic as: Type !join to verify your $<coin> token holdings and get access to the full community chat.
When users type !join in the channel, the bot will DM them a link which opens up a website that asks you to connect your wallet in order to verify the tokens you own that it will assign roles for. There are tiers, so if you have enough tokens (erc20, 721, 1155) you will unlock multiple roles in 1 swoop.

As soon as you invite the bot to the server the bot creates a private channel for admins to setup. This is how it looks like for a server admin to configure various roles based on tokens:

The downside here is that users will be expected to have a crypto wallet installed, such as Metamask, and to of purchased / receive the tokens. This leads us to the NFT Discord bot...
NFT Bot

The NFT bot removes the friction of needing to install a wallet in order to use crypto. There is also an unlock command similar to collab.land that has a few open issues left to make it practical to use:

https://github.com/webaverse/app/issues/1214
https://github.com/webaverse/app/issues/170
https://github.com/webaverse/app/issues/1037

It currently has hard coded start/end ids: https://github.com/webaverse/ethereum-bot/blob/300fe0e3d8519984573a0652ef0f3fb6d4dfba79/discordbot.js#L576
Need to make it user settable

There are some tradeoffs involved with just using the Discord bot, mainly that the sidechain network doesn't have value streaming through it - that is mostly on mainnet and polygon.
The upside has several benefits:
Earning NFTs for unlockable roles: when somebody is contributing we can measure that XP (through sourcecred, already setup) which can be converted to SILK which can be used to purchase sidechain NFTs from the server store. We can also reward NFTs through other off-chain contributions, like creator program / GH sponsors / etc.
Metafactory distributes $ROBOT when people purchase things from a store by asking for the person's ETH address during checkout. We could do something similarly by using Discord ids.
Rewarding people with SILK which can be used to purchase NFTs that unlock Discord roles seems like a fun way to onboard contributors into the community. I think for now collab.land can be used since the NFT and the results wouldn't change at all even if we had mainnet/polygon token unlock for the NFT bot.
Design
There are currently a couple NFTs we designed for the first batch. The idea was that these keycards could not only be used to unlock roles in Discord but also places (https://github.com/webaverse/app/issues/803) inside a virtual world (or the app itself, keycard access for alpha testers). There is already a perfectly looping gif / webm for these designs.

The branding and marketing strategy is to be decided. I can produce a high quality video / blog post / tweet storm to explain the value one gets with having one of these NFTs.

Added emojis to welcome channels and reaction based role selection, next is NFT based role unlocks

In the metagame discord there's a signpost channel to figure out what's what which is where I noticed the commands:

Commands
!?portals - brings up all the important links
!?token - brings up all the important Seed info

I really like how this bot has a simple way to add commands that can bring up a help page for quick links.

This would be a nice command to ingest into the NFT Discord bot in the future, made an issue for it: https://github.com/webaverse/app/issues/1330

Alright so I just tested minting a NFT from Discord, transferring it to Ethereum mainnet, setting up a role that ownership of that NFT unlocks with collab.land, and then testing it in the Discord and everything works.

0x42FaE5A6dBd93Cf63ED9EEa0449825ddC8234a17 1 1 @M3 <tokenId>

There's now an unlock-door channel used just for verifying ownership with bots. The did-a-thing and props channels are setup with reaction based weights for measuring value creation using sourcecred. M3 as a good testbed with events / tickets / merch. So far everything is tested working, will try to get similar functionality with the NFT bot later this week.

Promotion and Marketing
There can be different tiers, tier 1 is the card and tier 2 is the Doom inspired keycard which can be used for several things:

Tier 1: Early access to Webaverse (alpha testing)
Tier 2: Access to M3 channels (like a mini makers district inside our Discord + partner servers, similar to chinatown or 1729)

This would also mean access to special events and livestreams
Also early access to Webaverse alpha testing
Eligible for future airdrops

I've got a ton of great clips when I was working on the M3 trailer for promoting the story of M3 and why people would want to join such a community. The overall theme is the battle over closed vs open, centralized vs decentralized, freedom vs oppression using pop culture references in clips from:

The Matrix
Johnny Mnemonic
Ready Player One
Tron Legacy
Facebook: Horizons video

There's tons of curated original clips from past events + music produced by Godfrey Meyer as well for producing this trailer.
We can also go into VR and do some virtual productions with the keycards as props, to describe its purpose / role and what people get for it. Me and Godfrey have done bits where we just talk at the beginning or end of a video.

Thanks for putting this together, I think it fits my ideas in nicely in many ways.
My first comment is I think the consistency of the branding is important to get right here and that is my biggest worry  . Consistency should be in terms of art and characters, but also terms, nfts, writing style, and the subtle implications that we make, like what it means to own an nft, or land. Roles should match up with whatever is in lore, and the nfts should make sense with the theming to avoid ludonarrative dissonance.
One particular conclusion that shakes out if this is I don’t think many third party tools or bots will work, if they leak a different vibe or brand. But there is certainly a lot to learn from them.

My second comment is I don’t think those are the right themes, or at least they cannot be explicitly stated. We should be thinking much more personally and in terms of person to person interactions and character dynamics and long firm content rather than expressing grand visions and big words. People tend to interpret “decentralized” or “freedom” in very very different ways and it is easy to assume you are talking about the same things when you really are not. That has been a serious problem for our attempts to align community with M3 so I wanted to get rid if that framing and verbiage.
That said I agree with that being the correct undertone when you look under the covers.

In line with the above point I would want to distance from any existing IP.
We are obviously inspired by many of these things but referencing them directly gives a sweeping and vivid, but not really correct impression. I don’t want anyone to think we’re building the matrix or rpo, or competing with horizon. By referencing these works, that is the implication that is perceived and it is counter productive.

Appreciate the comments, some thoughts:

Branding, content, and roles would all be considered placeholder until the new package is ready.
Third party tools and bots have some inherent trust, especially when people are connecting a crypto wallet to a new app (collab.land). The name and icon can be changed in the configurations for carl bot. These bots roles can be eventually replaced without any disruption to service as the Webaverse bot improves.
Themes can be dressed however we'd like, obviously many people will connect to things they already know as many ideas about cyberspace repeat over generations. Can scrap it or consider those to be references as inspiration for a new story if you want, folks will connect the dots anyways if the storytelling is good.

As for tiering my plan was much earlier involvement in the building process. Once the foundations are laid there are many ways to immediately contribute and be rewarded for it, that align with the bigger goals.
For example, model bounties, narrative drops, dev meets can already happen. I’m in fervor of a lightweight approach where a lot of things are tried, especially on the creative side, rather than just selling access.
The cases where we are selling access should look a lot like patreon, that is step 1 is to make dank content (not just a key card but something like a fleshed out character) and step 2 is to sell it, which we then turn to deeper and continuing contribution loops.

One more point is that I think everything we do needs to ooze the brand. That means we should be thinking “when we show this on social media will people know instantly that it’s webaverse?”
That doesn’t mean watermarking and it doesn’t mean putting labels on things. It just means stylistic cohesion that makes people group things we post together as belonging to. “that thing” even before people know a thing about us.
The best way I’ve seen across the proto meta verse is characters.

Third party tools and bots have some inherent trust, especially when people are connecting a crypto wallet to a new app (collab.land). The name and icon can be changed in the configurations for carl bot. These bots roles can be eventually replaced without any disruption to service as the Webaverse bot improves.

Trust is important but if people do not trust us then we have bigger problems. I don’t think using any tool will change minds.
We could just stop making things and piggy back on glueing great tools. But that would be a very different kind of company and I wouldn’t have confidence in it.

Assets / themes can be dressed however we'd like, obviously many people will connect to things they already know as many ideas about cyberspace repeat over generations. Can scrap it or consider those to be references as inspiration for a new story if you want, folks will connect the dots anyways if the storytelling is good.

I’m a fan of Hemingway and icebergs. I think it is important that this is all thought out at the core, so the part that shows implies the depth, which you can seek out and explore like a rabbit hole.

Here's an idea for a signpost message that's mainly used for a getting-started channel or help command to get important links.
**__Welcome to Webaverse__**

You're at the ground floor of an advanced virtual universe that's under construction by humans and AIs.
Being early means there's more to gain by being a member to help build and grow the platform.
Remember to be respectful, think positive-sum, and enjoy your stay! :)

**__SIGNPOST__**

App: https://app.webaverse.com
Docs: https://docs.webaverse.com
Dashboard: https://webaverse.com
Twitter: https://twitter.com/webaverse
Blog: https://blog.webaverse.com
Store: https://opensea.io/collection/asset

**__FAQ__**

FAQ: https://docs.webaverse.com/docs/webaverse/faq/
Setup profile: https://docs.webaverse.com/docs#getting-started
Get SILK: https://docs.webaverse.com/docs/market/silk-guide

**__NFT Bot__**

The Webaverse Discord bot allows you to mint/trade metaverse NFTs right from Discord.
To view the full list of commands type `.help` in the #bot channel.
You can also type `.help <command>` or add `-h` after a command.

Guide: https://docs.webaverse.com/docs/webaverse/discord-bot

**__Keycard__**

To gain access to the full community channels and events you need a Keycard. For instructions on how to purchase one visit here: <link>

You can also earn a Keycard by completing quests for SILK. To learn more, visit the link below.
https://docs.webaverse.com/docs/index/#creator-program

This can be tweaked to better fit a discord embed message or welcome message in one of the first channels.
I know some parts are incomplete, wanted to get an early draft out in meantime.

The other bot has a web GUI for setting up custom messages for reaction based role setup. This program can be used for server owners to build and visualize embeds to do something similarly: https://github.com/Glitchii/embedbuilder

The redemption command is nearly finished which has me thinking about the next steps here. From the presentation:

[x] Update the docs
[ ] Announcement on how to earn SILK (blog post)
[ ] Modeling and concept art brand guide + bounties

Earning SILK
Call to contribute -> Contribute -> Reward -> Repeat
Explorers, settlers, and town planners can earn SILK by creating and contributing content for the season.
People who want to be involved get invited into a private role where they'll get access to events and the did-a-thing and props channels which are used to measure value creation for earning XP using reaction emojis. At the end of a cycle, the XP is tallied and converted into SILK. Top percentiles will have perks, although there should be a lil something for participation regardless.
Idea: depending on the roles a user picked when joining they may get a non-transferable NFT design inspired by the role (artist/builder/designer/writer/bridgebuilder/shiller) after reaching a certain threshold like leveling up as a certain class. Perhaps that NFT unlocks a channel exclusive to other people with those roles / NFTs, like having a writers / artists guild etc.

Brand guide and bounties for modeling and concept art will probably involve creating some kind of easy to navigate interface to see the work we've already done for people to get an idea of the standard of quality we are aiming for. It can be a website, miro, youtube video, page in the docs, poster, etc.
The docs page already has some methods listed on getting SILK: https://docs.webaverse.com/docs/market/silk-guide

Grants for the creator program

Public project proposals posted on Github

Unpacked from Webaverse NFTs
Airdropped during events and for creating community value

Sourcecred is currently setup on Discord and Github

Reward for completing bounties
Exchange NFTs for SILK (https://github.com/webaverse/app/issues/1373#issuecomment-879498112)

We could add in "contributing to the Wikia" as well once it's setup.
Server Store
The bot will allow server admins to set redemption roles based on Webaverse NFTs. This means the server treasury store could sell NFTs that unlock roles in Discord and in the future unlock chests and access places in the virtual world. The top prize could be the keycard (limited run of 50) which unlocks a parcel in Zone 0 + more.
There can be other NFTs for sale in the treasury store that may not have redemption commands, like a highly limited run of pets and vehicles. This means creators and contributors could get first dibs before the official drops. If it works we should do it more often.

Chatted with Jin this morning, I went to school for marketing and had some ideas over the last few days. I compiled everything into a hackMD; posting it here for posterity.
https://hackmd.io/@BMZ93BYsQWGepA-cZgh2sQ/SkNBrY0ad

This is fantastic, well put together!

“We are an interconnected blockchain protocol focused on metaverse interoperability as it applies to virtual spaces” is a lot less compelling than, “We want to connect all of the virtual worlds together with an interesting storyline, an immersive world to explore, and technology that will allow digital goods to be persistent throughout the web. And we want to do that natively in the browser, so there will be no download; it’s plug-and-play!”

The elevator pitch part stuck out to me. We should make sure that it's consistent throughout places to not confuse peeps.

good example would be a short doc that explains the requirements and a link to a Kanban board or something along those lines with the tasks. Tasks should be sorted by type and length of completion, and should have any information needed already ready to go.

I think we can come up with a doc, I'm working on updating the contributor guide on the docs site as well as a blog post that describes the process with generating lore to give more context for how and why we do things.
The incentives section is great, the little things like being on the top of discord or having name in the world are good ideas. Could imagine that many of these ideas could be items in the server store as NFTs.

IMO “what we do” is more powerful that “what we want”.

IMO “what we do” is more powerful that “what we want”.

Absolutely true; this was typed up stream-of-consciousness; intended as an example more than a literal proposal for an elevator pitch.
In general, the more active the verb the better - so yes; 'what we do' is definitely preferable. That verbage could easily be adapted while keeping the aversion to buzzwords, though.

For onboarding people into contrib/creator roles we need to do a few things first by answering these questions somewhere:

Where do I start?
How do I fit in?
Who can I trust?
Do I really have value to offer?

Tips from the gurus:

onboarding shouldn't try to funnel everyone to becoming a super involved contributor
need to allow ppl to signal the time + effort they want to put in helps set expectations
values are ”behaved” into existence by the founders and the early community. Like attracts like.

In order to optimize best use of time its better to have these written to be easily referenced / shared. Blog post + docs.

Another slide from the presentation. Blog post on how people can contribute to the project is the next thing. The brand guide is being developed by virtue of the art assets being completed for the trailer: https://github.com/webaverse/app/projects/5

Updated the creator guidelines: https://docs.webaverse.com/docs/create/guidelines
Now working on a post: Open source brand / Branding with OpenAI
Part of a series about AI collab. This post will describe process of going from idea, lore generation, moodboard / shotgun design inspiration, initial concept art, 3D kitbash, refinement, final piece, with Wikia entry somewhere in there. Will be useful for onboarding contribs / giving people insight into the creation of NFTs for this season's collection.

New getting started reaction role message:
Welcome to the Webaverse Discord server. Please select as many roles which describe you.

:art: **Artist**
Drawing, modeling, producing music, performing

:tools: **Builder**
Programming, creating objects, creating spaces

:writing_hand: **Scientist**
Writing lore, interacting with the AI, metaphysics ideas and planning

:bridge_at_night: **Linker**
Connects people, greets them, makes introductions, helps out with production

:mega: **Booster**
Collecting cards, promoting, streaming

Idea for poap badges + roles + semiotics is designing patches / badges that can be added to clothing
Can "earn your stripes" this way
Related: https://github.com/webaverse/app/issues/1336
Inspiration (art by nass9696


Show hex codes for palette in demo

#PATCH#

Approved - be careful with this, we don't want people using hex/rgb directly - only the SASS variables


I am getting real server response ,Unable to recieve mock response.

New Issue Checklist

[x] I have tried with the latest version of OHHTTPStubs
[x] I have read the README
[x] I have read the Using the right Swift Version of OHHTTPStubs for your project section
[x] I have searched in the existing issues
[x] I have read the OHHTTPStubs wiki to see if there wasn't a detailed page talking about my issue

Environment

version of OHHTTPStubs: [LIB VERSION HERE]
integration method you are using:

[x] Cocoapods
[ ] Carthage
[ ] submodule
[ ] other

version of the tool you use: [INSERT VERSION HERE]

Issue Description
[DESCRIBE YOUR ISSUE HERE]
Complete output when you encounter the issue (if any)
[INSERT OUTPUT HERE]

I am getting server  rather than the mock response
stub(condition: isHost("dev.local.in")) { _ in
let stubPath = OHPathForFile("users.json", type(of: self))
return fixture(filePath: stubPath!, headers: ["Content-Type":"application/json","Authorization" : "Token  68299ee2ffd0a5b1620d00966af39f2c72952c3e"])
}


Support JVM processes in a different PID and mount namespace

Containers are typically isolated behind a different PID namespace
and a different mount namespace from the host. As a result, certain
things in jattach's operation will not work:

Creating the attach_pid file will fail, or create the file in the
wrong directory (ignoring the target's mount namespace)

Looking for the java_pid file will fail (again, wrong namespace)

The pid value in the attach_pid and java_pid files will be the
host's pid and not the pid the JVM considers to be its pid

These issues are fixable by making jattach enter the mount namespace
of the target process prior to creating the attach_pid file and
waiting for the java_pid socket to appear. Also, jattach now resolves
the target's pid by traversing /proc/$PID/status to find the inner-
most pid namespace pid.
Tested manually by running a Java application in a Docker container,
and running jattach from the host using the host's pid for the Java
process as the target.
Resolves #10.

Good to merge then? :)

Done.
Please go ahead and merge these changes to async-profiler as well.
Thanks.


Third set of TestBuild* CI enabling for Windows

Signed-off-by: Darren Stahl<EMAIL_ADDRESS>

This PR is dependent on #19790, which is why windowsTP4 is currently failing.

Please do not merge yet. See https://github.com/docker/docker/pull/19847. CI should be re-run after 19847 is merged.

Are we waiting for some of this code to be factored out before merging?

@icecrime Yes.

As soon as #19985 is merged I can rebase this PR and rerun CI

Job: Docker-PRs-WoW-TP4 FAILED:

---
d0d905.
+ ec=125
+ set +x

----------------------------------
ERROR: Failed to build test binary
----------------------------------

-----------------------------------------------
ERROR: Failed with exitcode 125 at Tue Feb  9 23:22:02 CUT 2016.
-----------------------------------------------

INFO: Tidying up at end of run
INFO: Nuking /d/CI
INFO: Zapped successfully
INFO: End of cleanup
INFO: Ended at Tue Feb  9 23:22:03 CUT 2016 (1m 18s)
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe D:\temp\hudson6120984134787952653.sh
+ set +e
+ set +x
INFO: End of cleanup
Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
---

Job: Docker-PRs-userns FAILED:

---
15.5 kB]
Get:3 http://llvm.org llvm-toolchain-trusty/main amd64 Packages [6196 B]
Get:4 http://archive.ubuntu.com trusty-updates InRelease [64.4 kB]
Get:5 http://ppa.launchpad.net trusty/main amd64 Packages [5161 B]
Get:6 http://archive.ubuntu.com trusty-security InRelease [64.4 kB]
Hit http://archive.ubuntu.com trusty Release.gpg
Get:7 http://archive.ubuntu.com trusty-updates/main Sources [313 kB]
Unable to find image 'docker:4603a72-userns' locally
Pulling repository docker.io/library/docker
[PostBuildScript] - Execution post build scripts.
[Docker-PRs-userns] $ /bin/sh -xe /tmp/hudson4429057957618250673.sh
+ set +x

---

Job: Docker-PRs-Win2Lin FAILED:

---
aking bundle: binary (in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/docker
/usr/local/go/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory

---
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson8235800569666154927.sh
+ set +x

---

Job: Docker-PRs-WoW-TP4 FAILED:

---
d0633c.
+ ec=125
+ set +x

----------------------------------
ERROR: Failed to build test binary
----------------------------------

-----------------------------------------------
ERROR: Failed with exitcode 125 at Wed Feb 10 00:34:52 CUT 2016.
-----------------------------------------------

INFO: Tidying up at end of run
INFO: Nuking /d/CI
INFO: Zapped successfully
INFO: End of cleanup
INFO: Ended at Wed Feb 10 00:34:53 CUT 2016 (0m 57s)
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe D:\temp\hudson4215561572627043486.sh
+ set +e
+ set +x
INFO: End of cleanup
Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
---

Job: Docker-PRs-Win2Lin FAILED:

---
aking bundle: binary (in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/docker
/usr/local/go/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory

---
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson6380960636138234607.sh
+ set +x

---

Is this one ready?

As soon as CI passes this is good to go. Due to the new tests being enabled, I would like to see windowsTP4 green at the very least.

CI is green :+1:

LGTM

LGTM 🐮


How do I install dependency necessary for creating the archive?

sudo dnf install gem
https://stg.packit.dev/srpm-build/873/logs

Short answer: you can't
Long answer: we are running all commands, defined by you, in a sandbox (new openshift pod) which is locked-down. At the moment we don't have any mechanism for you to define the dependencies you need and us making them available for you.
In the mean time we are solving these requests one by one and installing the dependencies ad-hoc.

gem command should be available in sandbox in an ~hour after the image gets build and imported in our cluster

Thanks a lot that'll help!
It also solves (be wary) the issue with any other (future) dependencies for me, as all can installed using gem install ....
FYI: I'm running staging instance.

we have gem available now, closing
thank you for reaching out!


Instructions to use DM21 from C++ don't work for me

Hi!
I'm having some trouble with the instructions to use DM21 from C++. In particular, the instruction
pip install -r requirements_aot_compilation.txt

gives me a compilation error
clang: build/src.macosx-12-x86_64-3.10/numpy/core/src/umath/matmul.c
      error: Command "clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -DNPY_INTERNAL_BUILD=1 -DHAVE_NPY_CONFIG_H=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -DNO_ATLAS_INFO=3 -DHAVE_CBLAS -Ibuild/src.macosx-12-x86_64-3.10/numpy/core/src/umath -Ibuild/src.macosx-12-x86_64-3.10/numpy/core/src/npymath -Ibuild/src.macosx-12-x86_64-3.10/numpy/core/src/common -Inumpy/core/include -Ibuild/src.macosx-12-x86_64-3.10/numpy/core/include/numpy -Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -I/Users/pablo_1/venv/DM21/include<EMAIL_ADDRESS>-Ibuild/src.macosx-12-x86_64-3.10/numpy/core/src/common -Ibuild/src.macosx-12-x86_64-3.10/numpy/core/src/npymath -c build/src.macosx-12-x86_64-3.10/numpy/core/src/multiarray/scalartypes.c -o build/temp.macosx-12-x86_64-3.10/build/src.macosx-12-x86_64-3.10/numpy/core/src/multiarray/scalartypes.o -MMD -MF build/temp.macosx-12-x86_64-3.10/build/src.macosx-12-x86_64-3.10/numpy/core/src/multiarray/scalartypes.o.d -msse3 -I/System/Library/Frameworks/vecLib.framework/Headers" failed with exit status 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for numpy
Failed to build numpy
ERROR: Could not build wheels for numpy, which is required to install pyproject.toml-based projects

while
bazel run --experimental_repo_remote_exec :run_dm21_aot_compiled_example

returns
INFO: Reading rc options for 'run' from /Users/pablo_1/Developer/deepmind-research/density_functional_approximation_dm21/.bazelrc:
  Inherited 'build' options: --define framework_shared_object=true --java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --host_java_toolchain=@tf_toolchains//toolchains/java:tf_java_toolchain --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --noincompatible_prohibit_aapt1 --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2
ERROR: --noincompatible_prohibit_aapt1 :: Unrecognized option: --noincompatible_prohibit_aapt1

I am running this on a 2016 intel macOS Monterrey, in case that's important. And I also followed the git installation instructions.

What python version are you using? I suspect 3.10, for which there isn't an official numpy binary for the version specified in requirements.txt and requirements_aot_compilation.txt. pip then attempts to compile numpy from scratch, which fails (presumably because you're missing some dependency). Either resolve this or update/relax the versions in the requirements files so pip installs precompiled binaries.
Note bazel compilation also requires numpy to be installable, so you will eventually hit the same problem there. However, there seems to be some backwards-incompatible changes to bazel which you're hitting first.
We'll try to push fixes for both of these soon.

Hey @jsspencer you're right that it was python 3.10. I have actually found a workaround that will not require me to further use DM21 from C++, but I guess an easy solution would be to make the environment have python 3.9.

Trying to bump this, since I'm having the same issue. It would be good to implement this functional in other quantum chemistry software, but at the moment it's impossible...
I have also MacOS 13.0.1. Same issues as explained above.
I also tried on Ubuntu 18.1 but bazel failed with:
ERROR: --noincompatible_prohibit_aapt1 :: Unrecognized option: --noincompatible_prohibit_aapt1
removing the flag from .bazelrc gets me a little further down but then it crashes at:
ERROR: no such package '@external_py_deps//': rules_python failed: Collecting absl-py==0.13.0

It should be possible to build using the same version of tensorflow and (quite important) bazel 4; looks like there's a behaviour change in later versions of bazel. This is tricky to do -- it is easier to update the build to use tensorflow 2.11 and bazel 5.3. We've just pushed fixes for this.
(As an aside, it is also possible to compile using saved_model_cli installed as part of tensorflow with pip install tensorflow, and so avoid building with bazel. This also requires compiling the tensorflow XLA runtime library, which is located within the tensorflow directory within the virtualenv and the instructions for doing so are less portable.)


Support AWS_MSK_IAM authentication

This pull request addresses issue #2232 by adding an AWS_MSK_IAM authentication mechanism.
A detailed description of the authentication scheme is available here:

https://github.com/aws/aws-msk-iam-auth#uriencode

I understand that kafka-python may not be the appropriate place to put a vendor-specific authentication mechanism.
If that's the case maybe it's better suited as a plug-in?
The library doesn't support auth extensions at the moment but it doesn't look like a huge lift to get there.

To use the mechanism pass the following keyword arguments when
initializing a class:
security_protocol='SASL_SSL',
sasl_mechanism='AWS_MSK_IAM',
bootstrap_servers=[
    'b-1.cluster.x.y.kafka.region.amazonaws.com:9098',
    ...
],

The credentials and region will be pulled using botocore.session.Session.
Using the mechanism requires the botocore library which can be
installed with:
pip install botocore

TODO:

[ ] Documentation
[x] Test authentication payload generation
[ ] Test config verification / auth method
[x] Refresh mechanism for temporary credentials?

This change is

Resuming in #170.


initial shared weights implementation

Shared weights for low-level control in the actor networks.
Example instantiation for the ant env:
    controller_conf = {
        'leg': {
            'actions': 2,
            'hidden': 20
        }
    }
    controller_list = ['leg', 'leg', 'leg', 'leg']
    actor = SharedControllerActor(n_states, controller_conf, controller_list, n_hidden)

Currently there is one fully connected hidden layer and two hidden layers in the controllers.

TODO: save args ofSharedControllerActor properly


Fixes #4438 Signatures not merging properly with typeshed

Fixes #4438 Signatures not merging properly with typeshed
Skips leading parameters when we mean to replace rather than extend
Fixes tuple syntax
Fixes intersection tests

TypeShedJsonMakeScanner is not passing for me (it's using Python 3.7 32-bit)
Test Name:	TypeShedJsonMakeScanner
Test FullName:	AnalysisTests.AstAnalysisTests.TypeShedJsonMakeScanner
Test Source:	C:\Projects\GitHub\huguesv\PTVS\Python\Tests\Analysis\AstAnalysisTests.cs : line 1068
Test Outcome:	Failed
Test Duration:	0:00:29.9918277

Result StackTrace:
at TestUtilities.AssertUtil.ContainsExactly[T](HashSet`1 set, T[] expected) in C:\Projects\GitHub\huguesv\PTVS\Common\Tests\Utilities\AssertUtil.cs:line 231
   at TestUtilities.AssertUtil.ContainsExactly[T](IEnumerable`1 source, T[] expected) in C:\Projects\GitHub\huguesv\PTVS\Common\Tests\Utilities\AssertUtil.cs:line 222
   at AnalysisTests.AstAnalysisTests.TypeShedJsonMakeScanner() in C:\Projects\GitHub\huguesv\PTVS\Python\Tests\Analysis\AstAnalysisTests.cs:line 1078
Result Message:	Assert.Fail failed. ContainsExactly failed.

Expected:
{__call__(string:str=,index:int=)->[tuple[int, None, ]]}

Actual:
{__call__(string:str=,index:int=)->[tuple[None, int]]}

Expected not in actual:
{__call__(string:str=,index:int=)->[tuple[int, None, ]]}

Actual not in expected:
{__call__(string:str=,index:int=)->[tuple[None, int]]}
Result StandardOutput:
Creating temp directory for test at C:\Users\huvalo\AppData\Local\Temp\gvjtiv1a.zgz\AstAnalysisCache\
Creating temp directory for test at C:\Users\huvalo\AppData\Local\Temp\gvjtiv1a.zgz\ltbxwwuc.u3k\

TypeShedSysExcInfo test passes, but when I try to do it in the editor, I don't see any types for e1,e2,e3 and no completions. That used to work some time ago when I pip installed the typeshed package, and I hadn't tested that one since.

Heh, because I made it work and then fixed the other test properly...

No, you're right, I'm not getting them either... weird...

It's not a regression from this PR, so we can fix it separately. Up to you.

It's looking like a bigger change (to handle typing properly without importing the actual file), so I'll do it separately.


LogFactory - Assign Configuration should only perform a single InitializeAll

Right now the following is written to the Internal Logger during startup:
2018-02-25 16:23:25.4148 Info Configured from an XML element in C:\Users\snakefoot\Source\Repos\NLog.Web\examples\ASP.NET Core 2\Visual Studio 2017\ASP.NET Core 2 - VS2017\bin\Release\netcoreapp2.0\nlog.config...
2018-02-25 16:23:25.4377 Info Found 55 configuration items
2018-02-25 16:23:25.4499 Info Found 55 configuration items

Nice one, thx

PS I don't expect a rc7, just in case.


Task Groupings

from @davisagli:

it'd be nice if we had a way to group tasks in the list, and then maybe a way to hide a group unless you have a flag in your personal settings. In other words I want a way to say "show me all the releng tasks" rather than needing to configure each one

Humble proposal:
a task definition looks like:
tasks:
    blah_task_name:
        class_path: blah
        description: blah
        options:
            name: option_is_blah

JSON Schema definition for the tasks section of cumulusci.yml
I suggest we add a fourth, optional, key to the task definition object:
tasks:
    blah_task_name:
        group: releng
        class_path: blah
        description: blah
        options:
            name: option_is_blah

defined as a comma seperated list of strings .
If a task defines a group (or more than one), by default, it will not be returned by BaseTaskFlowConfig.list_tasks.
We'll also add a new property to the cumulusci section, which contains a comma severated list of groups:
cumulusci:
    keychain: MyKeyChainClass
    groups: releng, wlma

If a group is added to the cumulusci.groups key, then BaseTaskFlowConfig.list_tasks will now list tasks from that group. This can be overriden on the project yaml, or on an (e.g.) release engineers loal machine.
Still to figure out:

are groups pre-registered besides just being referenced in a task?
the behavior of defining a task with the same name as a globally hidden task in a project and not specifying group would be surprising. perhaps all tasks must have a group.
at the CLI you should be able to list all tasks, and list all tasks for a specified list of groups. this is not the default. there's also a way to force running a task in a group, if its not your default group. oh, and see them.
but unless you've specified a group in YAML or at runtime, the task is invisible.
docs should list all tasks all groups.

Hmm, I'm having second thoughts about the idea of hiding groups of tasks because:
a. It'll be a source of confusion
b. It sort of goes against our ethos of making our internal tools widely available whenever they aren't truly SFDO Product Delivery-specific.
c. When there are tasks that fit the "SFDO Product Delivery-specific" clause, I'm inclined to say they should go in a separate package and we should have a way for installed Python packages to register tasks that they provide via setuptools entry points.

well, ignoring my "wlma" example, I think (with tweaks) it could still work out?
reporting on push_failures isn't product delivery specific, it's just...
(cci-q4) ➜  npsp git:(master) ✗ cci task list | wc -l
      77

but we tell people to use the list/info tasks to get discoverability into what CCI can do.
what if I walk the proposal back a little bit more...
If a task has a task group, it's not (by default) displayed on cci task list, unless that group is in your personal yaml. If it's in your yaml, it's displayed in the list. The list also prints at the bottom a line for each group and how many tasks it has that weren't displayed. cci task list <group_name> would do the obvious, as would cci task list --all

I'm not keen on hiding-by-default any task that has a group, because I want to use the group to actually show the default results in groups, much like Django's manage.py help. I can see cci task list <group_name> being useful for focusing, but I'd kinda like to see how much grouping the results helps before going as far as to hide some groups by default.

Right, maybe builtins could be categorized by topic (CI, Github, Deployment, etc), with another group (or column) to indicate project-specific customizations. It'd be a solid start.

Where I'm coming from is that unless you're the person doing packaging -- you don't need to see the five push_* tasks in the task list, they're just bloat. Things like github_* aren't really meant to be run by developers or even outside of CI. In fact, you mention django manage.py, which I feel has WAAAY too many lines of output, not enough information, and a frequently get annoyed at how its formatted :)
the proposal above has MOST tasks not in a group. that doesn't seem to be well loved...
What if every task has a group, and we have most groups enabled by default? But the few related to packaging orgs or CI only tasks are keyed out, and the task list does indicate there are more hidden tasks?

What if every task has a group, and we have most groups enabled by default? But the few related to packaging orgs or CI only tasks are keyed out, and the task list does indicate there are more hidden tasks?

This sounds pretty good to me.

Closed by #872


CJS-ESM Hazard

This issue to document & keep track of the decisions around modules the lib should export, the options that we have available are:

CJS only, doesn't allow for tree-shaking & doesn't allow smooth usage when using ESM (albeit ESM being able to import CJS). Otherwise works great.
Dual ESM / CJS, allows for usage in both CJS and ESM environment but exposes the user to risks of state duplication when both copies are imported.
Dual ESM / CJS with ESM-Proxy, this is like 2 but in addition exposes a set of ESM modules that proxy to CJS so that when resolved by node regardless of which style we use we end up with a single state (generated from CJS). This looks good at first sight but it doesn't work with a lib that is exposed as "2" (e.g. fast-check is impossible to use from schema). Also it trips build tooling such as vitest who have non standard module resolution (albeit this can be considered a BUG of such tools)
ESM-only, it would be all good but unfortunately it is problematic to force consumers into ESM as the ecosystem doesn't yet homogeneously support ESM (and with all probability never will).

I believe our only valid choice is "2.5" in the sense that 3 is impractical as it forbids third party dependencies that we have no control over and 2 alone is a call for bugs. 2.5 is what we've been doing by using globalValue("id", maker) to isolate the pieces of state that should be shared globally. It is a bit error prone as there is no check to know when we are allocating state and it's easy to forget

I'm generally a fan of pure ESM. We discussed this at length in Discord already. TL;DR: I strongly believe that ESM is the "right" path forward for the ecosystem. Explciitly guiding new users on that path by only exposing ESM is a boon imho.
I don't think there's a problem with fresh users of effect in a green field scenario. New users would be running on our documentation, tutorials and template guardrails (e.g. pnpnx create-effect)
Hence, I think the only user group who would truly suffer if we only ship pure ESM would be veterans working on large deeply interwoven code bases. The kind of user that likely knows what's happening but has no way to make it work because they can't get rid of their year long tail of legacy CJS dependencies in their projects.
Realistically though, newcomers are not a concern in my opinion.
All that considered, In retrospect, I think going back to [2] but explicitly and forcefully failing hard in case a dual package import is detected at runtime is the least cumbersome would possibly lead the best outcome for all parties while only locking out a small portion of potential uses (those who would otherwise run into an obscure dual package hazard at runtime)

Maybe I'm missing sth. but why do we need to do that at all? Why not just drop a root scope side effect into our core most module(s)?

Currently you can have two different versions of effect and still have a working app, because of the global value workaround.

Yeah but my point is we could just not allow that to keep things simple and predictable. The worst outcome is subtle runtime bugs that go undiscovered and eventually come to haunt you. Failing early and failing hard might be a viable alternative here.

I'm personally interested in seeing if the 2.5 approach of supporting ESM/CJS (without an ESM proxy) using the globalValue helper will work for us long term. We can also work on an ESLint rule to try to help us out with this (it can be dumb at first, like detecting when we are creating a FiberRef with the FiberRef constructors.
I also think there is no harm in logging a warning to users if effect is imported twice somehow, similar to what React does if you import two versions of the library. I think this benefits users not just for the dual package hazard issues, but also for those who simply end up with two versions of effect somehow.

I'm personally interested in seeing if the 2.5 approach of supporting ESM/CJS (without an ESM proxy) using the globalValue helper will work for us long term. We can also work on an ESLint rule to try to help us out with this (it can be dumb at first, like detecting when we are creating a FiberRef with the FiberRef constructors.
I also think there is no harm in logging a warning to users if effect is imported twice somehow, similar to what React does if you import two versions of the library. I think this benefits users not just for the dual package hazard issues, but also for those who simply end up with two versions of effect somehow.

I could live with this compromise. Log a warning, loud and clear (instead of the hard fail that I suggested) but try to work around runtime issues on a "best effort" basis

Not sure logging is a good idea, the issue isn't limited to effect but to any lib built on top, you could have @effect/platform duplicated too
I think we should decide if either we support running with duplicated modules or we don't, I'd opt for supporting the case.
Another scenario is folks bundling effect in their own libs, as much as this is a bad idea, some folks are worried about "effect" as an explicit dependency and would like to bundle it. In such case we will be running multiple versions anytime the user is also running effect

I think we should decide if either we support running with duplicated modules or we don't, I'd opt for supporting the case.

The problem I have with that is the mine field of potential (especially unforeseen) issues we'd be willingly putting ourselves in. This past year I went back and forth between "I totally get CJS & ESM duality now" and "Damn, another weird issue" numerous times. At this point I cannot claim with certainty that we can prevent all potential runtime issues with the workarounds we've named so far (globalValue, avoiding instanceof, etc.). I'm sure there are still dragons we've not taken into account yet. There are just too many (unknown) edge cases and too many things to constantly be on our toes about (remembering to apply globalValue, etc.) whenever we author or review a PR in the future.
I'm worried that we are going to put ourselves through a lot of (future) pain (maintenance, user support, etc.) if we make the wrong decision here, whatever the wrong decision is (I really don't know).

Another scenario is folks bundling effect in their own libs, as much as this is a bad idea, some folks are worried about "effect" as an explicit dependency and would like to bundle it. In such case we will be running multiple versions anytime the user is also running effect

That doesn't sound like sth. we should support or encourage though, does it?

I think we should decide if either we support running with duplicated modules or we don't, I'd opt for supporting the case.

The problem I have with that is the mine field of potential (especially unforeseen) issues we'd be willingly putting ourselves in. This past year I went back and forth between "I totally get CJS & ESM duality now" and "Damn, another weird issue" numerous times. At this point I cannot claim with certainty that we can prevent all potential runtime issues with the workarounds we've named so far (globalValue, avoiding instanceof, etc.). I'm sure there are still dragons we've not taken into account yet. There are just too many (unknown) edge cases and too many things to constantly be on our toes about (remembering to apply globalValue, etc.) whenever we author or review a PR in the future.
I'm worried that we are going to put ourselves through a lot of (future) pain (maintenance, user support, etc.) if we make the wrong decision here, whatever the wrong decision is (I really don't know).

Another scenario is folks bundling effect in their own libs, as much as this is a bad idea, some folks are worried about "effect" as an explicit dependency and would like to bundle it. In such case we will be running multiple versions anytime the user is also running effect

That doesn't sound like sth. we should support or encourage though, does it?

supporting users with large production systems is 100% a priority of Effect, we can't dismiss folks that have been using node in prod for years, they are our primary addressable market

I think bundling effect is dumb but I can't prohibit people from doing it, effect has a learning curve and it isn't yet as standard as a react would be so, while being a dumb thing to do, if there is a lib author that wants to leverage effect internally we should support it while advocating for the correct solution (effect in peerDependencies)

supporting users with large production systems is 100% a priority of Effect, we can't dismiss folks that have been using node in prod for years, they are our primary addressable market

I get that and I also want to suppor them! As mentioned in our previous discussions and on Discord, these are definitely the type of users that I can see in a lot of pain if we drop CJS. To me they are the one exception where I agree that CJS is still necessary.
I am simply worried and uncertain about the "how" (as we all are). I don'tI like the possibility of silent, deferred failures or wonkiness and hard-to-debug runtime scenarios that users might experience at different points during their programs lifetimes. I'd rather have guaranteed, clear messaging and hard failures. Ideally before actually running the application.

https://github.com/Effect-TS/effect/pull/1564
This progresses on the idea, it tracks versions and isolate state between different versions so effectively we can run two independent versions of effect without issues
Ofc client state is also to be considered but realistically the only stateful piece of effect a client uses are tags and when tags have identifiers they become globally shared, note that tags are also using globalValue so they become versioned like any other effect

I just gave tshy (https://github.com/isaacs/tshy) a shot.
It is following the ideas of 2.5 as described by Mike (CJS & ESM exports and advocating for awareness around duplicate state. I'm starting to feel a bit more convincend about this. Sorry, I've been burned by this too many times so please excuse me trying to tread carefully here ;-).
This is from the tshy README:

"Dual Module Hazard" is a fact of life anyway
Since the advent of npm, circa 2010, module in node have been potentially duplicated in the dependency graph. Node's nested node_modules resolution algorithm, added in Node 0.4, made this even easier to leverage, and more likely to occur.
So: as a package author, you cannot safely rely on there being exactly one copy of your library loaded at run-time.
This doesn't mean you shouldn't care about it. It mean that you should take it into consideration always, whether you are using a hybrid build or not.
If you need to ensure that exactly one copy of something exists at run-time, whether using a hybrid build or not, you need to guard this with a check that is not dependent on the dependency graph, such as a global variable.

That said, tshy doesn't work 100% yet but it is very close to our pre-preconstruct setup. Worth to keep an eye on it if we want to drop some of our custom made tooling & config in the future.
In the meantime, I suggest we revert back to our pre-preconstruct setup, with the following adjustments compared to our pre-preconstruct configuration (Max and I have already started with that):

Use named exports (some bundler [e.g. parcel] and ts issues remain with wildcard exports)
Bump to NodeNext and ES2022

I would also suggest to move back to absolute imports.
To validate that everything is working correctly in all scenarios, we should consider to:

Add shallow consumer acceptance test fixtures / test apps (e.g. Node ESM, Node CJS, Bun, Parcel, Vitest, Webpack)
Add a CI test matrix for node (as is now), jsdom and edge vitest environments

Additionally we should investigate how to best ship tsconfig.json with our dist or otherwise make .d.ts fully explorable in dist  without errors (there are still issues with some custom runtimes like CloudFlare workers).
Does this sound like a reasonable battle plan?

I just gave tshy (https://github.com/isaacs/tshy) a shot.
It is following the ideas of 2.5 as described by Mike (CJS & ESM exports and advocating for awareness around duplicate state. I'm starting to feel a bit more convincend about this. Sorry, I've been burned by this too many times so please excuse me trying to tread carefully here ;-).
This is from the tshy README:

"Dual Module Hazard" is a fact of life anyway
Since the advent of npm, circa 2010, module in node have been potentially duplicated in the dependency graph. Node's nested node_modules resolution algorithm, added in Node 0.4, made this even easier to leverage, and more likely to occur.
So: as a package author, you cannot safely rely on there being exactly one copy of your library loaded at run-time.
This doesn't mean you shouldn't care about it. It mean that you should take it into consideration always, whether you are using a hybrid build or not.
If you need to ensure that exactly one copy of something exists at run-time, whether using a hybrid build or not, you need to guard this with a check that is not dependent on the dependency graph, such as a global variable.

That said, tshy doesn't work 100% yet but it is very close to our pre-preconstruct setup. Worth to keep an eye on it if we want to drop some of our custom made tooling & config in the future.
In the meantime, I suggest we revert back to our pre-preconstruct setup, with the following adjustments compared to our pre-preconstruct configuration (Max and I have already started with that):

Use named exports (some bundler [e.g. parcel] and ts issues remain with wildcard exports)
Bump to NodeNext and ES2022

I would also suggest to move back to absolute imports.
To validate that everything is working correctly in all scenarios, we should consider to:

Add shallow consumer acceptance test fixtures / test apps (e.g. Node ESM, Node CJS, Bun, Parcel, Vitest, Webpack)
Add a CI test matrix for node (as is now), jsdom and edge vitest environments

Additionally we should investigate how to best ship tsconfig.json with our dist or otherwise make .d.ts fully explorable in dist without errors (there are still issues with some custom runtimes like CloudFlare workers).
Does this sound like a reasonable battle plan?

Does sound like a good plan yeah


[WIP] Hudi uniform support

Which Delta project/connector is this regarding?

[ ] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[x] Other (Uniform)

Description

This change aims to add support for Hudi in Uniform
The changes were mostly copied from OneTable which has a working version of Delta to Hudi already

How was this patch tested?

Some basic tests are added
Does this PR introduce any user-facing changes?

Yes, this allows users to expose their Delta tables as Hudi

This is my first time contributing to Delta Lake and I need some assistance on a few points:

How do I use intellij to run and debug tests? I run into kerberos issues still after many hours of trying to get this environment setup. Is there a quickstart guide I've missed?

These are the instructions that work for me. Can you tell bit more about the Kerberos issue?

How do I run a test suite against a particular version of spark/scala. Hudi only supports up to spark 3.4 as of the 0.14.0 release so we won't be able to run with 3.5 in the tests.

@lzlfred ^

General guidance on UniForm integration. I've just copied over what exists for Iceberg and currently put the code in the same module. I'm guessing we'll want to create a similar module for Hudi if your goal is to keep the dependencies lean and only include them if required.

@lzlfred ^

This is my first time contributing to Delta Lake and I need some assistance on a few points:

How do I use intellij to run and debug tests? I run into kerberos issues still after many hours of trying to get this environment setup. Is there a quickstart guide I've missed?

These are the instructions that work for me. Can you tell bit more about the Kerberos issue?

I run into this error which seems like it may be a version issue?
An exception or error caused a run to abort: 'void org.apache.hadoop.security.HadoopKerberosName.setRuleMechanism(java.lang.String)'
java.lang.NoSuchMethodError: 'void org.apache.hadoop.security.HadoopKerberosName.setRuleMechanism(java.lang.String)'
	at org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:84)
	at org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:315)
	at org.apache.hadoop.security.UserGroupInformation.ensureInitialized(UserGroupInformation.java:300)
	at org.apache.hadoop.security.UserGroupInformation.getCurrentUser(UserGroupInformation.java:575)
	at org.apache.spark.util.Utils$.$anonfun$getCurrentUserName$1(Utils.scala:2416)
	at scala.Option.getOrElse(Option.scala:189)
	at org.apache.spark.util.Utils$.getCurrentUserName(Utils.scala:2416)
	at org.apache.spark.SparkContext.<init>(SparkContext.scala:334)
	at org.apache.spark.SparkContext$.getOrCreate(SparkContext.scala:2888)
	at org.apache.spark.sql.SparkSession$Builder.$anonfun$getOrCreate$2(SparkSession.scala:1099)
	at scala.Option.getOrElse(Option.scala:189)
	at org.apache.spark.sql.SparkSession$Builder.getOrCreate(SparkSession.scala:1093)
	at org.apache.spark.sql.delta.ConvertToHudiSuite.createSparkSession(ConvertToHudiSuite.scala:105)
	at org.apache.spark.sql.delta.ConvertToHudiSuite.beforeAll(ConvertToHudiSuite.scala:43)```

java.lang.NoSuchMethodError: 'void org.apache.hadoop.security.HadoopKerberosName.setRuleMechanism
Not sure how this was tested, perhaps hadoop and hadoop-common both need to be pinned to the same version, something like 3.3.6

@the-other-tim-brown  Thanks for putting this together. Delta appreciate this effort and lets work together to add the support.

the current master & delta 3.0 branch is on Spark 3.5; I am not aware of any way to build and run with another Spark version.

Agree... We should have a separate module for Hudi.

@the-other-tim-brown Thanks for putting this together. Delta appreciate this effort and lets work together to add the support.

the current master & delta 3.0 branch is on Spark 3.5; I am not aware of any way to build and run with another Spark version.
Agree... We should have a separate module for Hudi.

If we are ok just comparing the files in the current view of the table, we can avoid bringing in the hudi spark bundle which will solve this issue. Is that ok?

I will need help with this, this was my first time using sbt and I'm not sure what all needs to be shaded vs not.

If we are ok just comparing the files in the current view of the table, we can avoid bringing in the hudi spark bundle which will solve this issue. Is that ok?

Yes sure. at this point we do not need to read the hudi table by Spark yet.

I will need help with this, this was my first time using sbt and I'm not sure what all needs to be shaded vs not.

myself is not a sbt expert either... i will circle this back to the committers and see.

without being able to review this in detail yet, here are a few high level feedbacks:

we should make hudi in its own package/module to avoid fat jars that contains dependencies of multiple formats.
we should make sure hudi metadata dir is whitelisted in Delta's vacuum logic, which deletes everything Not on its white list or not tracked by delta log. code pointer: https://github.com/delta-io/delta/blob/master/spark/src/main/scala/org/apache/spark/sql/delta/DeltaTable.scala#L217
I suggest we should add more unit tests such as doing insert/update/delete with Delta, and then read with hudi to see file lists matches. More unit tests including schema evolution, partitioning, statistics conversion can come in future.

I will review this in more detail in the next few weeks. Thanks for the effort !

looks great ! plz do

clean up and make separate Hudi package as previously mentioned.
do a grep and fix other Iceberg occurrences mostly in comments.

@lzlfred I've moved the code into a separate package but I do not have any experience with setting up a new sbt module. After moving the code, the iceberg and hudi modules fail to compile. I've pushed an update so you or someone on your team can help debug this.


Create function hotkey dialog does not allow selecting a platform abi or os

Version and Platform (required):

Binary Ninja Version: 32380dev
OS: Windows
OS Version: 11

Bug Description:
The 'create function' hot key is non-functional in raw views
Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

Create a new binary file
Right click zero, patch, assemble

select aarch64, for the assembly patch any code will work, I just used 'ret'

Hit 'p' on the start of the new code to create a function there. This dialog box is busted, you cannot select an OS or a platform and as a result you cannot create the function here.

Expected Behavior:
I am able to use 'p' to create a function.
Additional Information:
You can work around this issue via right click. This works.

Fixed in 3.0.3312-dev.


Feature/mentee-app-validation

Description
https://www.loom.com/share/69717f6d114348178054bb6debafa58c
This PR adds input validation to the mentee application form, to let applicants know if they haven't answered any questions that are required. It also adds a slash that was missing to the endpoint.
Fixes:

form input validation rules
revise validation error messages
added slash to endpoint URL

Contributors
@benedictSchurwanz
@tinaxgao
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[ ] I have made corresponding changes to the documentation if necessary (optional)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

There is a merge conflict in Mentee.js, I was having trouble resolving it, I'm submitting as is. I could use some help.


Add incorrectly answered items back into queue after fail

Test the user again if they got it wrong, to enforce better learning!

Make it an option also

Make it an option also


updatePage: to: Should Return a Proper Page Object

It just returns a string

That's the way it's supposed to work. There are no page objects, contrary to the old Wiki implementation in ActivePapers.

Oh I see. I wonder about that change. One of the central premises of GT is that the IDE is object oriented i.e. no monolithic tools, but each object carries interesting views along with it. A page seems to me to be the most central domain concept of a wiki, but if there is no type for it, there is no way to have e.g. a live, custom GT view for it in the inspector, unless one accesses it from within the pre-built browser. What is the motivation behind this change? Am I missing something?

That's a good fundamental question, and I certainly don't claim to have found the best answer for WIkis yet.
A page is certainly a fundamental domain concept of a Wiki, but then I could argue that an element is a fundamental domain concept of an array, and yet there is not ArrayElement class in Pharo, for good reasons. So the question is how fine-grained OO modelling ought to be.
After decades of seeing overengineered code (mostly Python) with tons of classes that had no significant functionality, I have adopted a minimalist point of view in which I only define a new class if there's a real need for it. In the old ActivePapers framework, I needed APWikiPage because the only way to view/edit pages was the GToolkit inspector, so I needed an object to inspect, as you describe. With the new WkWikiBrowser, this need went away.
Note that my IpfsWiki class (over at https://github.com/khinsen/ipfs-pharo/blob/master/src/IPFS-GToolkit/IpfsWiki.class.st) does have its own IpfsWikiPage class because there is a good reason for having one: storing pages as separate IPFS data items. This illustrates that a specific Wiki implementation can have a page class even though the abstract framework doesn't.
As you point out, one functionality that requires a page class is inspecting an individual page. But does this really add to the experience of working with WIkis, given that the page object would just be a view-specific label added to a string?

Interesting conversation!
What should be first class is an old philosophical debate, in fact. With moldable development we tend to transform it into a practical problem. Whenever you want to view an object, you want a custom view. To build a custom view you want a first class.
A further reinforcing constraint comes from the fact that we mostly compose the UI out of views. That means that whenever I have the need to display something in a special way, there should be a view for it and that, of course, should be hosted in a first class entity.


Update Architecture Diagram

Acceptance Criteria:
DUE Friday March 22nd at 9am
Create an Architecture View (one combine diagram is common) that shows security impacting concerns such as:

[x] The (business) user-classes by privilege/access level (human and non-human)
[x] the integrated systems physical and virtual topology (include where it is and who “owns” it)
[ ] Application components and which components are used in the privileged or non-privileged functions
[x] The domain objects and the paths/flow of data through the system and what communications channels and networks it uses
[ ] Show any security controls such as what encryption is used in communication on what channels, where there is authentication, or auditing.

Be sure to indicate any:

[x] trust boundaries, entry and exit points (where data moved in and out of the system)
[x] where in the system the data is stored – If this is a PWA or things like IndexDB are used make sure to include that.
[x] Any segregation between privilege/access levels (network, logical, app, database, etc.)
[x] Authentication, Authorization, and Auditing related components.
[ ] Date, version, page number, title annotations are very much appreciated

https://apps.nrs.gov.bc.ca/int/confluence/display/FSADT1/Architecture+Design


Bad clean build performance

I'm using Gradle for years with Gradle Kotlin DSL currently, and recently convinced team to migrate all projects from maven to Gradle. What I observed on CI – build time of clean build (no caches, nor CI nor remote) almost two times slower than maven.
Expected Behavior
We're using gitlab CI for building small library (about 100 classes), maven build takes about 40-80s, gradle build 120-180s.
Current Behavior
Context
We're using official gradle image 7.3.3-jdk11.
settings.gradle.kts just defines rootProject.name and build scan plugin
build.gradle.kts has three plugins: java, maven-publish and net.researchgate.release. dependencies, publishing and release blocks.
After introducing cache in gitlab:
before_script:
  - export GRADLE_USER_HOME="$(pwd)/.gradle"

cache:
  key:
    files:
      - gradle/wrapper/gradle-wrapper.properties
  paths:
    - .gradle/wrapper
    - .gradle/caches

Build becomes much faster. But it's adding costs of downloading/saving cache. Overall time about 60-80s (not so bad, but not as fast as maven).
I assume that there are two "slow" task happens:

Compiling kts files (K2 compiler should improve this)
Generating(?) gradle-api 150mb jar
Generating accessors based on plugins

I believe for point 1 we can't do much about, but points 2 and 3 can be optimized by: including gradle-api jar in base image and downloading pre-build accessors for known plugins.
Steps to Reproduce
Create basic project in clean environment and build it
Your Environment
Build scan URL:

no cache build https://scans.gradle.com/s/oiphte5cbdu4q
gitlab cache build https://scans.gradle.com/s/bhsbob6qskvb4 (just gradle build, not gradle clean build*)

https://gist.github.com/IRus/114b934dbcf544fb5bf5a073dc7d3dba
Looks like generating gradle-api adds a lot

I came across the same issue today. We are running gradle commands in containers and every time we start a new container, the process starts with generating the gradle-api-x.y.z.jar which takes ~30 sec. I'm confused as why does gradle generate jars when gradle is installed on the image 🤔
I was wondering, is there a way to make gradle generate that jar without a project so we can include it in the image?


ARROW-10573: [C++] Align written buffers to specified value

IPC messages are forced to 8-byte alignment and ignore the alignment IpcWriteOptions setting. This inhibits zero-copy optimisations as non-8-byte-sized types can't be stored in contiguous memory.

Hm. Unaligned buffers are not compliant with the Arrow specification. This optimization is only useful in the extraordinarily narrow use case where all of the columns in the DataFrame are the same data type.

ML Discussion.  As I said there, I don't think this is a good approach either since it doesn't conform to the specification.

@wesm I disagree with your assertion that it's only useful in an extraordinarily narrow use case - I've added a test case test_contiguous_buffers_mixed_types to show a zero-copy load of mixed-datatype DataFrame. The columns do have to be sorted by dtype for now (df[df.dtypes.sort_values().index]) if you want to eliminate consolidation, but pyarrow could easily do this under the hood.
w.r.t. the spec, I see in Implementations are recommended to allocate memory on aligned addresses here; my PR doesn't change the default behaviour of following the recommendation and 8-byte aligning the buffers. A user would have to opt in to creating unaligned files if they wanted the benefit of reading their DataFrames without copying the data.
My use case is to expose Arrow files saved on disk (and probably still resident in the OS' page cache) as Pandas Dataframes with as low a latency as possible. Copying the entire DataFrame from one place in memory to another (to strip out the padding) adds latency and memory pressure, far outweighing the performance benefit of 8-byte aligned reads.

From the specification

Implementations are recommended to allocate memory on aligned addresses (multiple of 8- or 64-bytes) and pad (overallocate) to a length that is a multiple of 8 or 64 bytes. When serializing Arrow data for interprocess communication, these alignment and padding requirements are enforced.

So I guess it's a question whether we want to allow the creation of non-conforming IPC messages

I'm -1 on allowing non-conforming IPC implementations.

@emkornfield @wesm thanks for the comments. What’s the process for updating the spec? As allowing unaligned buffers in IPC streams is backwards (but not forwards) compatible it’d be great to get it into v1.1!

@emkornfield @wesm thanks for the comments. What’s the process for updating the spec? As allowing unaligned buffers in IPC streams is backwards (but not forwards) compatible it’d be great to get it into v1.1!

You can start a discussion thread on dev@ mailing list.  I'm not in favor of making this change to the specification, others might feel differently.

@emkornfield thanks, I will. Can I ask why you don’t want unaligned buffers allowable in the spec?
I’m not sure I understand the philosophy here though; Arrow has a lot of Python code to provide Pandas compatibility but if you always have to copy IPC data to use it from Pandas then your not getting any advantage from using Arrow as the underlying data format?

I’m not sure I understand the philosophy here though; Arrow has a lot of Python code to provide Pandas compatibility but if you always have to copy IPC data to use it from Pandas then you’re not getting any advantage from using Arrow as the underlying data format?

My thinking here is Arrow isn't just about the python implementation.  There are all sorts of tweaks that might make one language/library pair more performant, but changing the spec and ensuring all the other implementations can handle it is is a bunch of work, and over time degrades compatibility between implementation (we are already behind on some other features that are already in the spec).  So in these cases, I tend to be conservative with changing the specification.

It looks like there is consensus that the proposed changes are not desirable, so I'm going to close this PR. Sorry @njwhite , and thank you for contributing this!


Enhancement: support wildcards in k8s.v1.cni.cncf.io/policy-for

Hi,
In my use case, I have a lot of NetworkAttachmentDefinition objets (named net1, net2, and so on).
It is tedious very tedious to list each object the policy applies to in the annotation.
Instead, I would like to be able to write something like:
apiVersion: k8s.cni.cncf.io/v1beta1
kind: MultiNetworkPolicy
metadata:
  name: default-deny
  namespace: mysubnet
  annotations:
    k8s.v1.cni.cncf.io/policy-for: net*
spec:
  podSelector: {}
  policyTypes:
  - Ingress
  - Egress

and have the policy apply to every NetworkAttachmentDefinition matching the given pattern.
In case this is too complex to implement, would it be possible to match NetworkAttachmentDefinition objects using labels instead of their name? (similar to what's done in NetworkPolicy to match namespaces using spec.ingress[].from[].namespaceSelector.matchLabels)

Sorry for reply @fpoirotte . Thank you so much for the issue.
Hmm... That could be a idea. Currently MultiNetworkPolicy is still in development (as version 'v1beta1'), so it could be an idea for next version. Let me think about it more.


getStatusCode() invokes the magic method which throws an exception

$client = new Client();
...
$result->getStatusCode()

when I call this function I get this exception Magic request methods require a URI and optional options array, went to the Client core class and found that this issue is because this function is invoking the magic method which itself waiting for arguments while the purpose of getStatusCode() is to get status code and not treating data passed as arguments.

Fixed thanks.


Remove default_parallel_tasks setting

This setting currently has no effect. This PR removes it as discussed in https://github.com/Nukesor/pueue/issues/240#issuecomment-933002197.

Could you go ahead and create a changelog entry :)?
We'll have do some further breaking changes in pueue-lib for the changes to come anyway, so you can just start a new section:
## [0.19.0] -

### Removed

- Remove the `settings.daemon.default_parallel_tasks` setting, as it doesn't have any effect.

Thanks!


ensure combine_by_coords raises on different types

[x] Part of #5077
[x] Tests added
[x] Passes pre-commit run --all-files

No that does not work either because this raises on string coordinates.

@mathause yes, exactly.


Do cpedantic for stdlib & testing

We should compile stdlib and our test with --cpedantic.
We've concluded in the past that cpedantic can't be enabled per default since it depends on the CC version, and we don't want our use base to be guinea pigs. However, for compiling stdlib and test , i.e. acton itself, we should be fine. Last week I spent a few hours too many on debugging something that would have been caught with --cpedantic.
Outstanding things to fix:

We now use a particular version of zig so we don't rely on a system CC and thus we can always use --cpedantic.
--cpedantic actually broke a bit with the restructuring to use build.zig and it was never implemeneted for project builds but that is now fixed with #1440 and #1441.
I think we should start to fix these errors, one by one, until they're all fixed and we can permanently enable it. It can be temporarily enabled by like so
make CPEDANTIC=1
``

@sydow do you want to start to take a stab at fixing various compilation warnings/errors? :)


Prevent overflow for Poisson based models (large counts)

NaNs/infs out for large count data. Needs to be written to avoid overflow in the exponentiated terms.

Issue is resolved and will be in next release. The solution for GAS models was to clip the gradients. This still does not mean it's fool-proof, but now if it does fail, it will be because a insensibly large count dataset would have been chosen (where a Normal distribution would be a better choice...)


[super-agent-deployment] Add auth values (NR-265567)

Is this a new chart
No
Special notes for your reviewer:
Checklist

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [mychartname])

@kang-makes is this PR still relevant?

I completely forgot about this PR, Sorry.
Closing.


discord notifications not working via proxy...

📑 I have found these related issues/pull requests
FYI
🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
FYI
👟 Reproduction steps
FYI
👀 Expected behavior
FYI
😓 Actual Behavior
FYI
🐻 Uptime-Kuma Version
FYI
💻 Operating System and Arch
FYI
🌐 Browser
FYI
🖥 Deployment Environment
FYI
📝 Relevant log output
FYI

Duplicate of #616 PRs appreciated


Issue #27 - update router.js

Makes use of ES6 and cleans up some of the logic for '/signin' route

@Purukitto @pranjaldatta Didn't #27 say that the file must be no longer than 15 lines of code?


Add option to skip rhel6 in pipeline and ci

Description:
We need to update our release pipeline to have a property to skip build & test & release for RHEL6 (and CI checks as well).
Changes:

Added options skipRhelRelease and releaseRhelOnly to the release pipeline
Added logic to remove unfilled lines from releaseNotest and ADO PR files
Added options skipRhelRelease to the ci pipeline

Related issue: https://github.com/microsoft/build-task-team/issues/4093

/azp run

/azp run

/azp run


Limit input for user could not submit lower than minimum offer size

As we would like to avoid submitting lower than allowed offer size,
limit users submitting lower offers
This would prevent users not waiting for results from rpc
https://beta.kodadot.xyz/bsx/gallery/2735277589-3?page=1

👋

Question: how to find allowed minimum offer size?

go for it
------------------ Original ------------------
From: Darshana Prachi @.>
Date: Wed,Jun 29,2022 0:06 AM
To: kodadot/nft-gallery @.>
Cc: zhengow @.>, Comment @.>
Subject: Re: [kodadot/nft-gallery] Limit input for user could not submit lowerthan minimum offer size (Issue #3278)

Question: how to find allowed minimum offer size?

RPC node can give you answer.
@prachi00 can may get inspiration from the collection deposit :)
const mimumOfferAmount = api.consts.marketplace.minimumOfferAmount

Hey seems I was able to submit a lower offer than the minimum allowed.

This would prevent users not waiting for results from rpc

The goal of this issue was to prevent users from submitting even if they have a balance there.
Can you please check @prachi00 ?
https://github.com/kodadot/nft-gallery/pull/3318#issuecomment-1173111080

Hey seems I was able to submit a lower offer than the minimum allowed. #3318 (comment)

This would prevent users not waiting for results from rpc

The goal of this issue was to prevent users from submitting even if they have a balance there.
Can you please check @prachi00 ?
I would suggest if the user enters lower than allowed, we should disable button to submit

@yangwao can you send the nft url where this happened?


Unable to parse wire in signal list

例如
module arbiter (
    input wire in0_valid
)

It is not recommended to use this syntax in top-level modules, as it may conflict with the encapsulation code we generate. Therefore, support is not considered for the time being.


Issues in migrating from graphql transformer v1 to v2

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
v16.19.0
Amplify CLI Version
10.5.2
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made.
Describe the bug
I am attempting to migrate from graphql transformer v1 to v2. amplify migrate api compiles successfully and I get the following warnings / notes.
The following project state(s) were detected which may need additional attention to ensure they continue to work as expected with the new GraphQL transformer
- You have defined custom Queries, Mutations, and/or Subscriptions in your GraphQL schema
- You have overridden an Amplify generated resolver
- You are using the following directives which are not handled by the transformer:
	aws_iam, aws_cognito_user_pools, searchable
- You do not have the "improvePluralization" Feature Flag enabled

Then I do amplify push and i get Object type extension 'Query' cannot redeclare field searchProperties.
Expected behavior
The expected behavior would be for the graphql transformer to compile to the v2 code style and amplify push successfully.
Reproduction steps
I put my steps in the "Describe the bug" section.
Project Identifier
Project Identifier: 374cd2014176d0ef9272fcc7dd1fdc84
Log output

# Put your logs below this line

Additional information
Thank you for your help. And please let me know if there is any other information that would be helpful to troubleshoot.
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hi @jstocks-trelly 👋 thanks for raising this issue. Can you please share your schema before the migration?

schema.graphql.txt
Here is a txt version of my 'schema.graphql'.

I started a ticket with AWS Support  - my case ID is<PHONE_NUMBER>1. I shared my schema, cli.json, and custom resolvers there.

In that case I'd suggest we use the internal case to track resolution. Closing this issue.


Installation Guide & System Requitments

Hallo,
my name is Hiruko Kagetane
i want asking you waht's i need to run agar.io clone in my own website
i that i need vps hosting or other ?
and i want asking about installation guide
if you can please make a full tutorial with image or a video :)
Thanks for your script :)

VPS hosting is ok if you want a private server with you and your friends, I suggest a dedicated server or a big VPS if you want to make it public.
To install you can google most steps.

All you need to do is install npm and nodejs via "apt-get" if you're on Debian or Ubuntu based systems. Then run "sudo npm install" while inside the folder that was downloaded via the git clone on the repository.

How is written at the entrance of the site is changed ?

You can use nginx or apache or whatever you use to redirect www.yoursite.com/agar to <IP_ADDRESS>:3000, try google'ing "node.js proxy on [apache/nginx]"

i will buy a dedicated server
but i want you to make a video guide how to install it from begin use my dedicated server
i want make it public and if you want you can add it into your demo :)

@Kagetane, the installation process is not complex enough to require a video. It is the same as deploying most other Node applications. :smile:
Depending on your dedicated server's OS, the steps recommended by @Crasha would require the following command-line entries:
sudo apt-get update
sudo apt-get install nodejs
sudo apt-get install npm

Then you clone this repository onto the server and run the following command within the repository directory to download all the project's dependencies:
npm install

If you're not hosting anything else, you won't even need a webserver to provide the proxy suggested by @IgorAntun and then if you are, lots of information is available to help set that up.

:3 is that any one here can tell me how to install it on vps using SSH Putty ?
from begin please
OS : CentOS

You could use AWS instead. It's pretty staight forward.

Download the github repo
Dl and install dependencies

sudo apt-get update
sudo apt-get install nodejs
sudo apt-get install npm
npm install

Once it's built, zip the files into a folder
Sign up for amazon aws(freeish for a year).
Go to http://aws.amazon.com/elasticbeanstalk/
create new node.js web server on elastic beanstalk
upload zip folder and see if it works. Let me know if it doesn't.

Any following questions or should I close this issue?

I did write operations in the message. but I can not run .

Closing this since it seems to have been abandoned.


Fix for #44 (Wrong DCDC power calculation)

The dcdc power has to use the dcdc current and voltage instead of the
output voltage (which can be low side - buck or high side - boost) and
the dcdc current instead of the out current. See #44 for the discussion
on this issue

Thanks!


After receiving final load sheet, everything got reset

Hey,
this happens now 3 times.
The Boarding process and everything is going well, but after receiveing the final load sheet, disconnecting the Jetway:

The Chocks and GPU gets reconnected
Fuel and load will be reset to default (3000 / 0 Pax / 0 Cargo)
The Simbrief flight which has been loaded prior the flight is also deleted

Is this a known error or is there something I am doing wrong now.
It works fine with prior versions.
BR

Logs?
Steps?
Which was the Version where this started to happen?

Steps to reproduce:

Start APU during final Boarding phase
Beacon on after boarding finished
APU avail, EXT Pwr Button pressed and than the plugin starts to disconnect the Ground Stuff and the Jetway.
Here the reset happend.
Fenix2GSX20230617.log
Fenix2GSX20230618.log

Which logs do you need? The debug log file?
debug.log

How is you EFB Setup/Usage in Detail?
Somehow the Flightplan seemed to have been resetted. The Tool got an ID of "0" reported and then the original ID again. So the Reset came very likely through Fenix. I don't reset the Mass & Balance on a new Flightplan ID. The only change to M&B outside of De/Boarding & Refueling is when Refueling is called an the current Fuel is greater the planned Fuel.

I just load the Flight with the EFB, nothing more :(
With the internal, probably I should try it with the external on my Tablet again.

No further Feedback, could not be observed on Test-Flights => Closed


Fixed GDC.cpp for issue #42

Please provide some description whether you have solved task or error

Also you have totally changed the structure of the code...you have to find the error in the code given to you

okay, working on it


During FCOS Boot: Job nodeip-configuration.service/start running does not complete

I'm seeing a weird behavior with 4.12.0-0.okd-2023-01-21-055900
During cluster install on a KVM host, a master node that is booting after release-image-pivot will sometimes hang at:
Job nodeip-configuration.service/start running

If I kill the VM and restart it, then it will often get past this and continue.
These OKD clusters are built with fixed IP addresses which are configured via ignition.  I use butane to create the node specific ignition files, and iPXE to serve them at boot time.
Version
CentOS Stream as KVM host 5.14.0-205.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Dec 2 09:29:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
OKD: 4.12.0-0.okd-2023-01-21-055900

This issue seems to be fairly repeatable on a KVM host.  In this particular case, I am installing a 3 node cluster on a single physical host with 12 vCPU and 64GB of RAM.
After the bootstrap node is running, one or more of the control-plane nodes will hang at:
Job nodeip-configuration.service/start running

The node does not respond to ping at this point.
It will not recover unless I virsh destroy <hung-node> && virsh start <hung-node>
It is interesting to note that on a successful node, the nodeip-configuration.service appears to run twice.
journalctl output from a successful node is attached:
journalctl.out.txt
I can repeat this fairly regularly, but not with any discernible pattern.   It sometimes happens with just one node starting at a time.  It sometimes happens to only one of three nodes.
It does appear to happen more frequently on a constrained network.

Resolved:
I don't know if this is a regression or not...  But, I had to modify the iPXE boot files to include kargs to explicitly set the network configuration.  Up until now, I have been setting the network config via the ignition files by including NetworkManager configuration, applied with butane.
Previous iPXE file:
#!ipxe

kernel http://<IP_ADDRESS>/install/fcos/4.12.0-0.okd-2023-01-21-055900/vmlinuz edd=off net.ifnames=1 rd.neednet=1 coreos.inst.install_dev=/dev/sda coreos.inst.ignition_url=http://<IP_ADDRESS>/install/fcos/ignition/okd4.my.awesome.lab/52-54-00-0b-8a-a4.ign coreos.inst.platform_id=qemu initrd=initrd initrd=rootfs.img console=ttyS0
initrd http://<IP_ADDRESS>/install/fcos/4.12.0-0.okd-2023-01-21-055900/initrd
initrd http://<IP_ADDRESS>/install/fcos/4.12.0-0.okd-2023-01-21-055900/rootfs.img

boot

New iPXE file to resolve the issue:
#!ipxe

kernel http://<IP_ADDRESS>/install/fcos/4.12.0-0.okd-2023-01-21-055900/vmlinuz edd=off net.ifnames=1 ifname=nic0:52:54:00:0b:8a:a4 ip=<IP_ADDRESS>::<IP_ADDRESS>:<IP_ADDRESS>:okd4-master-2.my.awesome.lab:nic0:none nameserver=<IP_ADDRESS> rd.neednet=1 coreos.inst.install_dev=/dev/sda coreos.inst.ignition_url=http://<IP_ADDRESS>/install/fcos/ignition/okd4.my.awesome.lab/52-54-00-0b-8a-a4.ign coreos.inst.platform_id=qemu initrd=initrd initrd=rootfs.img console=ttyS0
initrd http://<IP_ADDRESS>/install/fcos/4.12.0-0.okd-2023-01-21-055900/initrd
initrd http://<IP_ADDRESS>/install/fcos/4.12.0-0.okd-2023-01-21-055900/rootfs.img

boot


Template list is difficult to parse and figure out which one I should choose

Identified during unmoderated getting started with azd study conducted in Q4 2022.
Template list is difficult to parse and figure out which one I should choose.
Challenges include:
• "todo" is not descriptive
• Visually, it is hard to scan quickly (e.g. in VS Code command palette list)
• Different naming conventions:
○ Sometimes main compute service is included (e.g. aca, func), sometimes not (e.g. todo-csharp-sql)
○ Sometimes IaC is included (e.g. terraform) sometimes not
New to azure customers are unlikely to know acronyms (e.g. aca, swa) and therefore not understand that they are choosing a certain compute service. We observed this in a user study where a customer wanted to use the same app service template she used in the CLI, but in VS Code chose the ACA one without realizing it.

Related to #976

We can start with the experiment in #976 and see what, if anything, else we want to do after that.

Pulling #976 onto Release 0.7 and moving this to backlog.

As of 0.9.0 (out tomorrow) we have made large updates to this list to reflect the local application stack (as opposed to emphasizing the ToDo app bits or Azure services).
. Going to close this for now as the remaining bits will be addressed by #2158


ID2 submision

iphone7 ios 14.0.1

pending:ID2
account1:screenshot-TBC
account2:screenshot-TBC
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID2 in full as text in a comment on this PR. Thank you!
@Ebruberen

pending:ID2
account1:screenshot-TBC
account2:screenshot-TBC
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID2 in full as text in a comment on this PR. Thank you!
@Ebruberen

confirmed:ID2
address:48ddRbSQZZuCKaDakUfpzPNSDRSgLugtqjBSPC2ZvocHMX8GT4

Form Submitted


Security controls

Coverage decreased (-0.8%) to 91.136% when pulling f10dbfa8af52259d6969cc2b3ea84e9db72d0df8 on swaggest:security into 41125fcaf99c49cbe98b3cfa1df5098d876c6051 on lazada:master.

Coverage decreased (-0.8%) to 91.136% when pulling ea495b088854c9cf997daf35419635450e5e617a on swaggest:security into 41125fcaf99c49cbe98b3cfa1df5098d876c6051 on lazada:master.

Coverage decreased (-0.8%) to 91.136% when pulling b489044b068104b79a5455ab5f123bdeeede121b on swaggest:security into 41125fcaf99c49cbe98b3cfa1df5098d876c6051 on lazada:master.


Support for letter, numbers only

Support for letter only and numbers only when using html pattern?

I don't quite understand your question. Could you please elaborate a bit more? What's needed from us?


stats: Avoid asserts in fuzz-tests by eliminating arbitrary length limits, using the new MemBlock wrapper for memcpy

Description: Stats have a reasonably generous hard limit of 64k bytes per "."-separated segment. However fuzzing is evidently happy to make longer strings, based on the fuzz crash report
This change also has the benefit of further reducing memory use; see gold-file updates in the PR.
Risk Level: low
Testing: just this one fuzz test
Docs Changes: n/a
Release Notes: n/a

ready for review now

/azp run envoy-macos

I think this is ready again for review

Also I don't have fuzz-tests for this yet; wondered what are the best practices for fuzz-testing this as most random stimuli to the API will just hit asserts; there is nothing algorithmic to test.

Something went very wrong; closing and will re-open.

/retest

Over to @mattklein123 for senior maintainer review. Thank you!


Add facilities for QIR memory leak detection

Need a mode that tracks allocation/release of QIR objects (arrays, tuples, callables, etc) and reports leaked ones at the end of the program. Something simple that at least flags a leak would be useful. Ideally, would be nice to track allocation stack (though using TTD traces might be sufficient).

Added opt-in allocation tracking per https://github.com/microsoft/qsharp-runtime/commit/66220dffee4334f70d92d8fc9739d7ecd075d679.

Added opt-in allocation tracking per https://github.com/microsoft/qsharp-runtime/commit/66220dffee4334f70d92d8fc9739d7ecd075d679.

#479 fixed this

#479 fixed this


Invalidate  Disabled  required content

hi all,
i need to not consider or  invalidate disabled required mandatory elements in form

Hi, your issue reads like a support question. This github repo is only for bug reports and feature requests. Please try one of the listed Support Channels.


chore(deps): update lnd-grpc to v0.1.4

Description:
Update lnd-grpc to v0.1.4
Motivation and Context:
lnd-grpc to v0.1.4 adds support for versions of lnd back to 0.5.0-beta, and supports earlier versions of nodejs.
How Has This Been Tested?
Manually
Types of changes:
Dependency update
Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage remained the same at 19.569% when pulling 151f5c50c2abd891249ad7bc3813de41ab847a94 on mrfelton:chore/update-lnd-grpc into 9a6d8ec30f0cfea2467acc9eb3e9d5d3eef5e928 on LN-Zap:master.


DOC rm fit_intercept in logreg L2 example

https://github.com/benchopt/benchmark_logreg_l2/pull/27 removed this parameter from the benchmark, which broke the doc.
This is a fix

Codecov Report

Merging #319 (cf66f2c) into main (7114e18) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #319   +/-   ##
=======================================
  Coverage   61.52%   61.52%
=======================================
  Files          41       41
  Lines        2277     2277
  Branches      417      417
=======================================
  Hits         1401     1401
  Misses        778      778
  Partials       98       98


Add some more contribution points

Add some more contribution points
While investigating untitled naming, I came across some additional contribution points that VSCode enables. Adding some additional places to surface our commands.
https://github.com/lastmile-ai/aiconfig/assets/25641935/ca806614-f15a-4df7-9965-7e5a89867c21

Stack created with Sapling. Best reviewed with ReviewStack.

-> #1336
#1335
#1334
#1333

While investigating untitled naming, I came across some additional contribution points that VSCode enables.

Nit: for future pls link resources so it's easier for others to see where you learned that info. Ex: https://code.visualstudio.com/api/references/contribution-points