Improve version selector & rename "master" to "latest"

In the top right of the website, we have a "version selector" that lets you view archived versions of the docs from past releases, however, the current presentation is confusing to users.
New users expect that they should browse the site on the 1.9 branch for information about 1.9 (when in reality they should browse the master branch because we are always updating it).
In reality, we treat these historical snapshot versions as "snapshot archives" and don't go back to update them with content from master.
This PR makes the following changes to the version menu:

Renamed the button which you click to expand the menu:

For example, in this PR its "Latest", but in the v1.0-branch snapshot it would be "Archive: 1.0"

prepended Archive:  to each version label
removes versions older than 0.6 from the dropdown

Screenshots
OLD

NEW

Thank you for creating those PRs @thesuperzapper.
From my point of view, we should not add Archive:  message to the previous Kubeflow versions since it can cause false impression that we don't provide support for those versions.

@andreyvelich the idea of the word "archive" is that it's an "archive" of the docs at that version, not that we don't support that version anymore.
Also, even if this was about support for the version itself, we definitely don't support anything other than 1.9.
@andreyvelich the idea of the word "archive" is that it's an "archive" of the docs at that version, not that we don't support that version anymore.
Even if this was referring to support for the version itself, we definitely don't support anything other than 1.9.
Also, when you go to any of those old versions of the website, every page has something which explains this at the top (that you're viewing a snapshot, not the latest version), so it should be clear.

I would suggest that we follow Kubernetes way to show versions: https://kubernetes.io/.
E.g. only leave 5 latests version of Kubeflow in the dropdown menu.

I don't really mind, but people might want to be able to see the older versions and they won't be able to find them otherwise.
I think we should probably keep at least all of the versions post 1.0.

What about the following?

master -> 1.9
1.9
1.8
1.7
1.6
1.5
1.4
1.3
1.2
1.1
1.0

1.9 would be the latest docs version that comes from the master branch.
I like the idea of following what Kubernetes does and leaving all the post-1.0 versions.

@andreyvelich the idea of the word "archive" is that it's an "archive" of the docs at that version, not that we don't support that version anymore.

@thesuperzapper What is the user value to add archive message to the versions that we display on the website ?

Even if this was about support for the version itself, we definitely don't support anything other than 1.9.

Why we don't support anything older than 1.9 ? I think, that similar to Kubernetes we should provide support to the few most recent Kubeflow releases and provide critical bug fixes for that release. That will show the project stability and maturity for the end users.

I don't really mind, but people might want to be able to see the older versions and they won't be able to find them otherwise.

We can have dedicated page for old Kubeflow versions, like in Kubernetes: https://kubernetes.io/docs/home/supported-doc-versions/#versions-older

@andreyvelich the idea of the word "archive" is that it's an "archive" of the docs at that version, not that we don't support that version anymore.

@thesuperzapper What is the user value to add archive message to the versions that we display on the website ?

Very simply:

Those v1.X-branch... website are archives, in the sense that they are the state of the docs at the time of the release.
Users are best served by reading the master/latest version of the website.
It helps users understand quickly that this is not a "versioned docs site" like they are probably expecting.

Do you have an alternative word that we could use as a prefix?
If you can't stand the "archive" prefix (and we can't think of an alternative), I guess as long as all the archive sites highlight at the top that you are not looking at the latest version (which will be the case after the other PRs are merged), we could drop it.

Even if this was about support for the version itself, we definitely don't support anything other than 1.9.

Why we don't support anything older than 1.9 ? I think, that similar to Kubernetes we should provide support to the few most recent Kubeflow releases and provide critical bug fixes for that release. That will show the project stability and maturity for the end users.

While that is nice in theory, it's a separate discussion to this as we currently don't support anything but 1.9.0.
This PR is not about the actual support status of each version, but helping users understand that they are looking at a docs "snapshot/archive".

Users are best served by reading the master/latest version of the website.

What if some new features that we deliver are not compatible with the old version of the components ?
In that case, users who are using old version of this Kubeflow component have to read previous version of Kubeflow website.

While that is nice in theory, it's a separate discussion to this as we currently don't support anything but 1.9.0.

This is not 100% true, at least from the @kubeflow/wg-training-leads side we can fix the critical bugs on the previous versions (e.g. three latest releases) of Training Operator if that was asked by users.
@thesuperzapper Why the Kubernetes approach doesn't work for us ?
I want to get @StefanoFioravanzo feedback on this given that he spent time to think about how we can develop the Kubeflow website given that every Kubeflow sub-project has dedicated release cycle and version.

@andreyvelich really, we just need to make a decision on if the "Achive: " prefix will be present or not.
The other PRs are much more important and I don't want to let this discussion block them, we need to prevent Google from indexing the very old websites (right now, Kubeflow search results often surface results from 0.3/0.6 versions of the docs):

https://github.com/kubeflow/website/pull/3849
https://github.com/kubeflow/website/pull/3850
https://github.com/kubeflow/website/pull/3851
https://github.com/kubeflow/website/pull/3852
https://github.com/kubeflow/website/pull/3853
https://github.com/kubeflow/website/pull/3854
https://github.com/kubeflow/website/pull/3855
https://github.com/kubeflow/website/pull/3856
https://github.com/kubeflow/website/pull/3857
https://github.com/kubeflow/website/pull/3858
https://github.com/kubeflow/website/pull/3859
https://github.com/kubeflow/website/pull/3860
https://github.com/kubeflow/website/pull/3861
https://github.com/kubeflow/website/pull/3862

Once we agree on if the "Archive: " prefix will be present, I will update these PRs to reflect that (so all versions are consistent), but its way more important to stop them appearing in search results.

Hmm https://github.com/kubeflow/website/pull/3849 seems merged already

Hmm #3849 seems merged already

@terrytangyuan Either way, its easy to update now that I have fixed building.

The other PRs are much more important and I don't want to let this discussion block them, we need to prevent Google from indexing the very old websites (right now, Kubeflow search results often surface results from 0.3/0.6 versions of the docs):

@thesuperzapper Can you remove the version change from your PRs and only leave the change to prevent Google from indexing and we can merge those PRs ?

cc @ederign

@andreyvelich I have updated all the other PRs with the following changes:

Remove the "Archive: " prefix from the "versions" menu that I added before
Update the root OWNERS to align with the current master (KSC members)
Updated the "version banner" to look like this:

We now need someone with GitHub org admin manually merge the following PRs:

A manual merge is needed because the old OWNERs are not active anymore.

WARNING: please remember to use SQUASH merge!

https://github.com/kubeflow/website/pull/3869
https://github.com/kubeflow/website/pull/3868
https://github.com/kubeflow/website/pull/3867
https://github.com/kubeflow/website/pull/3850
https://github.com/kubeflow/website/pull/3851
https://github.com/kubeflow/website/pull/3852
https://github.com/kubeflow/website/pull/3853
https://github.com/kubeflow/website/pull/3854
https://github.com/kubeflow/website/pull/3855
https://github.com/kubeflow/website/pull/3856
https://github.com/kubeflow/website/pull/3857
https://github.com/kubeflow/website/pull/3858
https://github.com/kubeflow/website/pull/3859
https://github.com/kubeflow/website/pull/3860
https://github.com/kubeflow/website/pull/3861
https://github.com/kubeflow/website/pull/3862

@james-jwu or @zijianjoy can you please update these DNS records, as they don't point to our modern Netlify, so will not be updated otherwise:

v0-2.kubeflow.org:

OLD CNAME: eager-nobel-1708cf.netlify.com
NEW CNAME: v0-2-branch--competent-brattain-de2d6d.netlify.app

v0-3.kubeflow.org:

OLD CNAME: competent-jones-a15cc2.netlify.com
NEW CNAME: v0-3-branch--competent-brattain-de2d6d.netlify.app

v0-4.kubeflow.org:

OLD CNAME: infallible-hermann-cb44b2.netlify.com
NEW CNAME: v0-4-branch--competent-brattain-de2d6d.netlify.app

v0-5.kubeflow.org:

OLD CNAME: practical-neumann-e70801.netlify.com
NEW CNAME: v0-5-branch--competent-brattain-de2d6d.netlify.app

@kubeflow/kubeflow-steering-committee @kubeflow/wg-pipeline-leads @kubeflow/wg-data-leads @kubeflow/wg-training-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-manifests-leads Can you give +1 on the banner that @thesuperzapper proposed for the old docs ?
If that looks good to you, we can start merging the PRs on the old website branches.

@thesuperzapper Only one comment from me, that I don't think that we should add yellow banner on the 1.9 documentation, since it is the latest stable release.
As you can see, the Kubernetes doesn't have this banner on the latest v1.31 version:

https://kubernetes.io/docs/concepts/workloads/controllers/job/
https://v1-30.docs.kubernetes.io/docs/concepts/workloads/controllers/job/

@thesuperzapper Only one comment from me, that I don't think that we should add yellow banner on the 1.9 documentation, since it is the latest stable release. As you can see, the Kubernetes doesn't have this banner on the latest v1.31 version:

https://kubernetes.io/docs/concepts/workloads/controllers/job/
https://v1-30.docs.kubernetes.io/docs/concepts/workloads/controllers/job/

WDYT @thesuperzapper ?

@andreyvelich on the Kubernetes docs, "1.31" is actually a link to kubernetes.io, which is their master branch.
The problem is that we have already cut a v1.9-branch for "1.9", so it really is a "snapshot of the docs at the time of the 1.9 release". If we don't have the warning, people won't realize they are not viewing the updated version of the 1.9 docs (which live on master).
In the future, I think we should hold off on cutting the 1.10 branch until just before we start merging docs for the 1.11 release. To resolve the current situation, we have two options:

OPTION 1: Keep the current v1.9-branch and retain the warning header.
OPTION 2: Delete the current v1.9-branch and only re-create it once we start the 1.10 release process

"While that is nice in theory, it's a separate discussion to this as we currently don't support anything but 1.9.0." yes there is just not much capacity beyond that. This might change if someone volunteers. We only fix critical things that are easy to fix, so in practice it was around 1 Year for 1.8/1.8.1 and with 1.9.1 released 1.8.1 will be EOL for most developers. For longer support you probably need distributions, consultants etc.
I like the term master more than latest, but I am also in favour of pushing for the master/latest version being shown by default and marking everything 2 releases away, so 1.8.1 and older as archived, End of Life or so.

/lgtm
I can see the dropdown and the version banner in the linked PRs, thank you!

As we discussed during today's community call, we can manually squash + merge all PRs to disable indexing on old branches.
We should just have followup discussion for the PR on 1.9 branch.
@johnugeorge @terrytangyuan @james-jwu @jbottum Can you help to manually squash + merge these PRs if you are agree with the banner:
https://github.com/kubeflow/website/pull/3869
https://github.com/kubeflow/website/pull/3868
#3867
https://github.com/kubeflow/website/pull/3850
https://github.com/kubeflow/website/pull/3851
https://github.com/kubeflow/website/pull/3852
https://github.com/kubeflow/website/pull/3853
https://github.com/kubeflow/website/pull/3854
https://github.com/kubeflow/website/pull/3855
https://github.com/kubeflow/website/pull/3856
https://github.com/kubeflow/website/pull/3857
https://github.com/kubeflow/website/pull/3858
https://github.com/kubeflow/website/pull/3859
https://github.com/kubeflow/website/pull/3860
https://github.com/kubeflow/website/pull/3861

I've done the squash + merge.

Both the DNS configuration and the Kubeflow website hosting on Netlify are transferred to CNCF. Would you like to make a request to CNCF by submitting a service deck ticket? https://cncfservicedesk.atlassian.net/servicedesk/customer/portals

+1 for master rather than latest


Removing automatic update check

Hi thanks for the great work with PyWalker!
We are considering to use it in a project but noticed that you added an automatic update check triggered every time the library is imported the first time. Commit: to:feat:reminder to update
Please reconsider if this check is really necessary, as I believe the update mechanism provided by pip is the preferred mechanism for checking for updates.
In addition to this, this is also a privacy issue for some users, so removing this check would help with adoption.

Hi, the auto-update check is developed for the reason that we are updating pygwalker very frequently. And there are going to be lots of essential features that will be published soon. We hope people are using the latest version so it can really help more people. The version updates checker only fetches the latest version and compares it with the local version. No other data is sent.
I understand your concerns, so we will add a global parameter to allow users to disable the auto-update checker if they do not want it. Thanks for your feedback.

Hi, the auto-update check is developed for the reason that we are updating pygwalker very frequently. And there are going to be lots of essential features that will be published soon. We hope people are using the latest version so it can really help more people. The version updates checker only fetches the latest version and compares it with the local version. No other data is sent.
I understand your concerns, so we will add a global parameter to allow users to disable the auto-update checker if they do not want it. Thanks for your feedback.

Thank you for addressing my concerns!
Do you already know how you are going to implement such change? Do you want to use some global variable for that or as an option to PyGWalker when you are plotting a dataframe?
If you want to notify about updates by default my preference would be to offer an additional extra variant like you do e.g. for streamlit and polars.

@Julius-Plehn
Hello! We're going to provide a user-wide privacy policy configuration method since pygwalker==0.1.7a0, please check it out in #95.


How much does easyloggingpp rely on STL?

I'm not reporting a bug, I'm just looking for plain information about easyloggingpp in general.
I'm looking for a lightweight, fast, and thread-safe logger which for an embedded device. I see that easyloggingpp uses Standard Template Library which is something I want to avoid for now. However if easyloggingpp doesn't heavily rely on STL I would consider trying it out. Note that I'm not knowledgable about STL, I'm just wary of it since my hardware specs are limited. So, generally I would ask whether easyloggingpp logger heavily relies on STL or/and is spdlog applicable for use on embedded devices as well?

Hi @MucaGinger thanks for reaching out with this question.
The reliance of Easylogging++ on STL is minimal like the data structures (vector, map, streams). You can test it on the embedded device that you want to build for and see how it performs. I have tested it with small embedded device previously few years ago and as far as i remember i didn't have any issues but can't remember the details on specs etc.
The library makes use of preprocessor directives to enable logging for certain libraries including STL but by default its off and won't effect the build time or performance when logging an STL structure for example.
Let me know how you go. Feel free to close this issue if its resolved.


Use markdown in rdfs:comments and other fields

I use markdown in rdfs:comments and other fields and I would like to display that markdown rendered as text on the pages. How could that be done?

Think the underlying problem here is that the Markdown templates use the Django linebreaks filter here which per its documentation:

Replaces line breaks in plain text with appropriate HTML; a single newline becomes an HTML line break (
) and a new line followed by a blank line becomes a paragraph break (
)

Which is entirely unnecessary since Markdown will handle line breaks naturally anyway.
The by-product of this is that Markdown in the rdfs:comment's doesn't then get rendered because most Markdown renderers don't render Markdown inside HTML block elements like
, if you manually strip out the
 tags from the resulting Markdown files then the actual Markdown from your ontology comments does get rendered.
So think the Markdown templates just want updating to not use the linebreaks filter


Lucas Test is broken

Lucas test (and by extension the Baillie-PSW test used in "strong_check") flags some primes as composites. A cursory search found no composites that passed (given the rarity of even 2-SPRPs beyond 2^64 this is fully expected) ,however the aforementioned behavior is sufficient to demonstrate that the test does not perform as predicted and may pass more composites than a correct implementation.  Below is one example.
N
18446744073710004191
Claim
true
Witness
8300848561679324618
Factorization of n-1
2, 5,<PHONE_NUMBER>371000419

I'm failing to see where the implementation deviates from the known algorithm. This same use case fails in golangs math/big implementation.

I'm failing to see where the implementation deviates from the known algorithm. This same use case fails in golangs math/big implementation.

Then both are erroneous, it's much more useful to resort to proven results (like the Pratt certificate given above) or statistical measures than referencing some other software. As we regularly see with GMP (arguably the most prestigious mathematical library) they can contain numerous hidden errors. (The Prime and Prejudice paper you cite as the basis being a fine example of how the most popular number-theoretic libraries do not perform as intended by the developers, which makes this issue somewhat ironic).
I'll look at it some more since I am also going to implement a BPSW for integers in 2^64;2^128  in my library. If many people are making this error then it probably needs to be resolved.

I agree with you. I’ll look more into this. In reality I’d love to ECPP instead which is faster but more complex to code

I agree with you. I’ll look more into this. In reality I’d love to ECPP instead which is faster but more complex to code

ECPP is not faster, it's much slower than BPSW. It does however provide a proof (much faster than Lucas' N-1 if that's what you meant).
FYI it also fails primes at a much lower bound as well, I just selected n > 2^64 since that's the machine word size and producing a Pratt certificate for much larger is very difficult. If you want you can use number-theory to rapidly check many smaller primes.  It has a rigourously proven deterministic test under 2^64 + 2^45 as well as being able to construct prime-proofs (albeit the slower N-1 variant). (It's how I detected the errors in here, num-prime, and primal).

Yes that’s what meant for comparison. I know ECPP fails at a lower bound which is why I already try the first 2048 primes by trial division

Yes that’s what meant for comparison. I know ECPP fails at a lower bound which is why I already try the first 2048 primes by trial division

??  I'm not aware of Elliptic curve primality failing at certain bounds, and even then trial division would not prevent it. Trial division is simply a method of quickly eliminating composites, even a weak fermat test is many times stronger than trial division by 2048 primes.
You also don't appear to use ECPP, and nothing said appears to apply to the Lucas sequence test either. (The counterexamples I found {if I remember correctly} were far greater than 17881 {2049-th prime}).

Correct this code does trial division followed by Fermat, then miller rabin then Lucas. No ECPP yet. I mention it as another test I’d like to include depending on the size of the prime

Correct this code does trial division followed by Fermat, then miller rabin then Lucas. No ECPP yet. I mention it as another test I’d like to include depending on the size of the prime

I'm curious if you benchmarked to see if the weak fermat is faster than a standard SPRP test? I've experimented it and found it essentially no different, as far as I know it is used in GMP because they have a specialized exponentiation function for it. If the bigint library doesn't also have the function then it probably doesn't actually run any faster. (Purely speculation on my part).

@JASory, do you know if num-prime still has issues with their Lucas implementation, or have they been fixed? I don't see any recent relevant commits.

I've experimented it and found it essentially no different, as far as I know it is used in GMP

Doesn't GMP use MR basis 2 + Lucas + MR random basis?

I think I see the reason. In lucas(), after a few steps of looking for P, Q, we are supposed to check if the number is actually a square. The code reads:
if p == 40 && (&n_int * &n_int).sqrt() == n_int {

Which is trivially true. I suppose it is a typo, and should read
let n_sqrt = n_int.sqrt();
if p == 40 && &n_sqrt * &n_sqrt == n_int {


(minor enhancement) Utilize native or lua math to deduct one on the Z axis of a coordinate

If you use the built in tools to copy a vector4, it will leave the ped floating in the hair. This would at least avoid that mishap by the less experienced. It could be as simple as Z - 1 or using the native PlaceObjectOnGroundProperly(ped) which essentially does the same thing.
https://docs.fivem.net/natives/?_0x58A850EAEE20FAA3

@jnccloud Thank you for letting me know about the native. I wasn't aware of that. Will fix that right away. I'm still learning the natives


models: Add is_realm_admin and is_guest setters.

Fixes #13452.
We add an option to control UserProfile.role through is_realm_admin,
is_guest properties. The issue with using these is that when changing
user's .role we want to create appropriate RealmAuditLog entries and
send events. This isn't possible when using these setters - the log
entries and events should be created if the role change in the
UserProfile is actually save()-ed to the database - and on the level of
the setter function, it's not known whether the change will indeed be
saved.
It would have to be somehow figured out on the level of post_save
signal handlers, but it doesn't seem like a good design to have such
complexity there, for the sake of setters that generally shouldn't be
used anyway - because we prefer the do_change_is_* functions.
The purpose of this change is mainly for handling use-cases like the
linked issue #13452, where some library function we don't control needs
to do setattr on these boolean properties.
For this reason, this change includes linter rules warning against
using the setters directly.

OK, I've merged this as 586a5facc9763e4c55651b7bed38a889502d227a.  Huge thanks for fixing this @mateuszmandera!
I also ended up restructuring the commit message; it's worth commenting a bit on my reasoning:

It's important to explain the problem we're fixing, and often it's better to explain the problem before getting into what we changed.  While the link to the issue provides some insight into that, there are possible futures where those links stop working (e.g. because of changes in how GitHub works or whatnot).  And in any case, it's a lot easier to read a change where that information is self-contained, especially because many issue threads (this one included!) may have a bunch of semi-unrelated clutter one would otherwise have to dig through to understand the change.

Can you add to your TODO list the planned refactor to merge do_change_is_admin and do_change_is_guest to a common do_change_user_role function?  Seems like something we should do while we're thinking about this (but not urgent).

Added to my list. And note taken regarding the commit message :slightly_smiling_face:


While     public static $snakeAttributes = false; on the model, yet User::whereFooBar() looks for foo_bar column instead of fooBar.

Laravel Version: 5.3.13, 5.5.*
PHP Version: 7.1
Database Driver & Version:

Description:
While     public static $snakeAttributes = false; on the model,  User::whereFooBar() looks for foo_bar column instead of fooBar.

This is also the case for Laravel 5.5

This sounds like a breaking change of a behavior that has been consistent for over a year.

Unfortunately there are some other places that does not respect to $snakeAttributes as well.
e.g. \Illuminate\Database\Schema\Blueprint::rememberToken and all similar framework generated columns.
I hope to see consistency in the future versions as most of the programmer I know use camelCase column names for higher code maintainability.

The only purpose of snakeAttributes is: Indicates whether attributes are snake cased on arrays, which means shall we enforce snake casing on attributes while converting to array, or let them as is?
Coding in Laravel with camel cased attributes is not the easiest road, but it's still quite feasible. You can use the CamelCasing trait from kirkbushell's eloquence, or directly set camel cased columns in your database (though you'll have to override the dynamic where, and just a few other things).
As for the generated columns in Schema issued by methods like morphs, rememberToken or timestamps, they use the snake case convention, and it's fine like this. They are just helpers for our convenience. Don't use them if you don't follow the snake case convention.
Anyway I agree, it would be interesting if Laravel could handle that stuff a bit more.

@chrispecoraro Thanks for commenting.  Not sure what was the purpose of your comment anyway.

For suggestions and feature requests please use the https://github.com/laravel/internals repo. we can't apply this change since it's a huge breaking change and would break apps, moving the discussion to internals will help us look into it with the next 5.6 release.

@sisve Can you please provide an example of the breaking thing?

@salarmehr Sure. User::whereFooBar() would start looking for fooBar instead of foo_bar, breaking it for everyone that has the foo_bar column. Just as the issue says.

@siseve I wonder if you have read to issue description?
its all about  $snakeAttributes vale

Yes, I have read it. You want to change the column name that ->whereFooBar(...) looks for when having $snakeAttributes = false. You also mention other places where the $snakeAttributes isn't taken into consideration. Changing this now will break the code for those that have already adapted to the currnet behavior; which means it is a breaking change.

+1
In OP's example, User::whereFooBar() should look for fooBar instead of foo_bar . What we have now simply is if a model has public static $snakeAttributes = false; on it, then multi-word attributes referenced in dynamic where simply don't work, because they would refer to column names which don't exist in the DB.
I've even created an issue and pull request in barryvdh/laravel-ide-helper#1166 to make sure it doesn't generate magic where docblocks for multi-word column names, because they simply don't work in Laravel.


added Tic_Toc_Toe_Advanced

PR Description 📜
#2318

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @krutikajichkar ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

The game is already there on GameZone. You can enhance the already existing game.
As we don't allow duplicate PRs, so closing this one.

Thank you  @krutikajichkar , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


agg first functions

Is your feature request related to a problem?
when performing groupby/aggs, its common to want to get the first value out of the group.
Describe the solution you'd like
df.agg(col("price").sum(), col("description").first())

Describe alternatives you've considered
No response
Additional Context
most dataframe libraries support this

pyspark
polars

Would you like to implement a fix?
No

After some digging I found any_value which is functionally equivalent.
Thoughts on renaming this to first @samster25 @jaychia

Although technically it works today, I don't think it's actually enforced that it will the first value that is seen. I think it may be better to have first() as a separate expression.


Cleanup and improve PHOTOMETRY.TIME parameter

The time restrictions should likely be less stringent (i.e. not require that the time is a number, or contains '-' or '/'; see: https://github.com/astrocatalogs/astrocats/blob/4463d65fe9f10fcd84f2c37f3fa8b6f147ed5668/astrocats/catalog/key.py#L248).

It doesn't make sense to allow for a(n arbitrary) U_TIME parameter if the TIME ends up being converted to MJD anyway.

The idea here was we have a "favored" unit for time, MJD, but if a user hand-writes a JSON file with a different unit, they should be able to specify it and have astrocats understand it. Upon being imported into astrocats and the final JSON written to disk, times would be converted to the "favored" unit.

And on the first bullet: Are you thinking dates in the form of English words, like "November 12, 1984"? Ideally the check would be to see if it parses in a date parser, but unfortunately the date parsers in Python are very inflexible (and unintelligent). I think astropy's time module is a bit better, but still rather inflexible.

Yeah, I think the favored time unit is good.  It looks like I was having problems because of me, not it (it seemed that passing in a string version of the time was failing --- not true).  So the only thing is that it seems a little strange how the conversion is done: maybe just delete the U_TIME parameter if its converted...   Also, I found this package a while ago that does some pretty impressive matching for datetime specifications:
https://dateutil.readthedocs.io/en/stable/


Rework value parameter parsing

Fixes #2847.

Fn__(...) parameters with idents/patterns no longer parse
Trait function parameters with arbitrary patterns parse
Trait function parameters without idents/patterns no longer parse
fn(...) parameters no longer parse with patterns other than a single ident

Question: The pre-existing test param_list_opt_patterns has been kept as-is, although the name no longer makes sense (it's testing Fn__(...) params, which aren't allowed patterns any more). What would be best to do about this?

bors r+


Feat/single tech/feature engineering on fabric br/setup env notebook

Add optional setup environment notebook for simplified Azure resource setup.
Type of PR

Documentation changes
Code changes

Purpose
Add a deploy.ipynb notebook to assist setting up environment in feature engineering pipeline of Fabric.
Does this introduce a breaking change? If yes, details on what can break
No.
Author pre-publish checklist

[ ] Added test to prove my fix is effective or new feature works
[x] No PII in logs
[x] Made corresponding changes to the documentation

Validation steps
Follow instructions in the notebook to create environment.
Issues Closed or Referenced
No.
Additional Information
Immigrated from this PR https://github.com/Azure-Samples/modern-data-warehouse-dataops/pull/653

@thurstonchen , @siliang-j-1225 , this is something new to me and I like it a lot. My concern is that it would add a bit of confusion to the person reading through the instructions.
I would propose to just add a one-line footnote at the end of the "Required resources" section and put a link to the notebook there.
Few other comments:

Move the "deploy.ipynb" to "src/infra/deploy-azure-resources.ipynb".
Remove Step 2 and Step 3 completely from the notebook, these instructions are already present in the main README.md and we want people to use this notebook as a standalone artifact.
For the following comments in the notebook:

run jupyter notebooks
authenticate with credential of the target tenant

We would either need to provide some more guidance about it or remove it altogether. For example, the reader would be wondering about which Azure service to use.

In the notebook, please add all the details about what it does, how it does in the markdown so that it's self-contained. I would expect people to also use it as a reference point for such a unique deployment method.

@thurstonchen , @siliang-j-1225 , this is something new to me and I like it a lot. My concern is that it would add a bit of confusion to the person reading through the instructions.
I would propose to just add a one-line footnote at the end of the "Required resources" section and put a link to the notebook there. --> Removed the previous paragraph and added a link at the end of the "Required resources" section
Few other comments:

Move the "deploy.ipynb" to "src/infra/deploy-azure-resources.ipynb".  -->done
Remove Step 2 and Step 3 completely from the notebook, these instructions are already present in the main README.md and we want people to use this notebook as a standalone artifact. -->done
For the following comments in the notebook:

run jupyter notebooks
authenticate with credential of the target tenant

We would either need to provide some more guidance about it or remove it altogether. -->decided to remove it altogether. For example, the reader would be wondering about which Azure service to use. -->added new contents in the beginning of the notebook shows which services will be created and what roles will be assigned

In the notebook, please add all the details about what it does, how it does in the markdown so that it's self-contained. I would expect people to also use it as a reference point for such a unique deployment method. -->I added some more details to markdown for each cell
Also remove "Step 1. Create Azure Resources" header as it won't be required with the new change. -->done

Hey @promisinganuj,  thanks for the informative comment! I have made some updates of the notebook and readme based on your comment. Please have a look later.

Hi @siliang-j-1225 , thanks for the changes. I pushed few minor modifications and I am happy for this PR to be merged now. Well done!


[DROOLS-465,BZ-1304051] install test kjars instead of deploying

@mariofusco please take a look, thanks!

I guess this is needed as part of this PR too https://github.com/droolsjbpm/droolsjbpm-integration/commit/2dfce3abdc192b05cb14252cd588d44905affa39

@mswiderski yes, correct. I will cherry-pick it here as well.

+1

Merged into 6.3.x.


Improve HOWTOs

Render HOWTOs as nicely formatted inline diffs in docs.
These diffs are syntax highlighted for both Python and diffs

Simplify the multi-device parallel training HOWTO

Re-pack the ensembling diff. (Once I applied it and re-packed it
it got a lot shorter… I wonder if this is something we need to do
for every commit?)

Make the HOWTO docs page directly show HOWTOs, and separate the
mechanics of the HOWTO system into a separate “HOWTOs HOWTO” page.

Modify the pack_howto_diffs.sh script to only pack changes in
examples/. This significantly simplified the process of iterating
on HOWTO diffs.

I pushed a new commit (hopefully) resolving your concerns, please take another look


Network scanning failed.

Hey i get these two errors, could you help me fix them please?
1st Error:
ERROR: Network scanning failed. Please check your requirements configuration.
2ed Error
The directory '/Users/CS/Library/Caches/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. The directory '/Users/CS/Library/Caches/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Thanks.

I am having the same problem (the 1st one at least)
I'm trying to install it in a VoCore2, but when I try to run scanNetwork() alone, I get
[ 1856.090000] device apcli0 entered promiscuous mode
[ 1856.100000] device apcli0 left promiscuous mode

ERROR: Network scanning failed. Please check your requirements configuration.

I do admit that it might be a fault of mine because since I only have ~9 MB space, I haven't installed absolutely ALL python dependencies that scapy requires, but I do have the basics to make scapy run. It gives me some info level warnings, but it works.
The dependencies for kickthemout are (I think) satisfied, since it only requires scapy and that I have installed.
Is there something I'm missing?
Thanks a lot.

I'm having exactly the same issues. Have you already find a solution?
Thanks.

same issue , how to solve it?

same issue,

Hey guys; sorry for the delay.
The 1st error message mentioned has been solved previously and is therefore considered duplicate. For the 2nd error message, I can assume that this error appears after running sudo pip install pcapy or sudo pip install -r requirements.txt. In that case, attempt using the -H flag, i.e. sudo pip install -H pcapy or sudo pip install -H -r requirements.txt.
Let me know if this helped. Thanks!

work for me tenx k4k4


FEATURE: Ruby MessageBus HTTP client.

https://github.com/SamSaffron/message_bus/issues/189

Not sure if we want the client to be within a single repo or not but what I did here is to ship it as part of message_bus.

@benlangfeld  Thank you so much for reviewing :+1: I've updated the PR as per your comments.

@benlangfeld  Applied the changes per your review. Thank you for taking the time to review this PR :+1:

@jeremyevans FYI we are going to have to do a breaking release here for you cause you will need to explicitly require message_bus/middleware from now on. (rails do not need to cause of the railstie)
I feel this is the right thing to do cause autoload is going away and this opens the ability of using message bus without HTTP at all.
Do you think its OK to release 2.2 here or do we need to bump all the way up to 3.0?
No APIs broke BUT blanket upgrade will lead to errors for rack app cause they will need to require the middleware.

Note Jeremy this comment was about the stripping of the explicit rack dependency from message bus which was in another PR. But shipping with the optional HTTP client is the underlying reason for the change.

I would definitely go to 3.0 if we expect a good portion of apps would break after the change.  It looks like roda-message_bus already requires message_bus/rack/middleware, so I'm not sure if it will need any changes.


Access replace_functions_map via PreParforPass instance

replace_functions_map is global variable from numba.parfors.parfor.
It is necessary to have possibility to modify replace_functions_map
depending on PreParforPass instance and access to it via the instance.
This PR is a proposal for starting a discussion.

This change will very likely be needed. I cannot think of any better way to specialize the parfor passes.

From out of band discussion, something along the lines of this patch is needed and moving information out of globals is a good idea. Once tests are added this PR can be reviewed. Many thanks.


Set-AzureADUserPassword - Automatically generate random password

The following doc outlines how to reset a user's password using the Set-MsolUserPassword cmdlet:
doc
Resetting a user password using this cmdlet is very convenient since it can randomly generate the new password.
With Microsoft encouraging their customers to move to the the newer Azure Active Directory V2 PowerShell module, I looked at the equivalent cmdlet:
Set-AzureADUserPassword.
doc
However, there does not appear to be an option to have this cmdlet randomly generate the new password.
Is there another cmdlet in the Azure AD V2 PowerShell module that should be used to reset an AzureAD user password, while automatically generating a random password value?
Thanks in advance.

@para0056  Unfortunately I don't have a good answer for this.  And with the move toward cmdlets based on MS graph, this could change again.  You may want to try one of the following:
Microsoft Support: https://support.microsoft.com/
Azure AD forums: https://social.technet.microsoft.com/Forums/en-US/home?forum=windowsazureaditpro
Stackoverflow: https://stackoverflow.com/
Thanks!
Bill


add some missing parts in about section

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_442oem3zll/clone/recipe/meta.yaml:52: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_442oem3zll/clone/recipe/meta.yaml:52: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_63zfr2fyx1/clone/recipe/meta.yaml:52: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_63zfr2fyx1/clone/recipe/meta.yaml:52: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_9705zqim2z/clone/recipe/meta.yaml:51: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_9705zqim2z/clone/recipe/meta.yaml:51: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_c3eahr1a5l/clone/recipe/meta.yaml:51: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_c3eahr1a5l/clone/recipe/meta.yaml:51: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found


Setting a custom filename

I'm using .put() to upload files to s3. It works fine, however if I try to put to a presignedUrl, the parameters of the url become part of the filename. How do I enforce the filename?
Or am I not able to put to a presigned url using this library?

+1


[Test] Be less stingent about whitespace in SwiftREPL tests

Be more permissive when it comes to whitespace. Currently, if the regex
matches nothing, we still expect two spaces.

@swift-ci please test and merge


Add an identifier to group answers by user

To group answers by user (even anonymous) add a Guid in the results table to identify which answers come from the same user. This would allow analysis like groupng answers by age group, gender, etc.

Implemented


Supplied key param cannot be coerced into a private key

Trying to authenticate, using a service account, in order to add new members to a Google group. Authentication is failing with the following message:
Warning: openssl_sign(): Supplied key param cannot be coerced into a private key in /vendor/firebase/php-jwt/src/JWT.php on line 238
The json file with the private key was downloaded from https://console.cloud.google.com/iam-admin/serviceaccounts.
Any suggestions on how to fix this problem? the key should be formatted correctly if the file was downloaded directly from Google IAM. Thanks.

I would inspect the file you downloaded and make sure it looks correct. It should be a JSON file (not a P12, which is another possible format). Also make sure the path to the file that you've configured in your code points to a correct and accessible location on your computer.


dat-desktop@next?

Following https://github.com/datproject/dat/releases/tag/v14.0.0, can we start to think about getting a dat-desktop@next as well? I didn't already see a ticket for it. If someone can lay out a plan I might be able to take a stab at it...

Looking https://github.com/datproject/dat/commit/63ea6c1634851d7ed05713b3246119023a66bfd0 - it should be straigth-forward: updating dependencies.

yeah, does someone have any time to make a PR?

okay i did it since it only took me a few minutes, please try it out

Awesome! Won't get to it today but tomorrow!


NixOS option request:  security.pam.u2f.mode and security.pam.u2f.fallback

Topic
The pam_u2f.so library supports the following options (copied from manpage):
       userpresence=int
           If 1, require user presence during authentication. If 0, do not request user presence during
           authentication. If omitted, fallback to the authenticator’s default behaviour.

       userverification=int
           If 1, require user verification during authentication (e.g. biometrics). If 0, do not request
           user verification during authentication. If omitted, fallback to the authenticator’s default
           behaviour. If enabled, an authenticator with support for FIDO2 user verification is required.

       pinverification=int
           If 1, require PIN verification during authentication. If 0, do not request PIN verification
           during authentication. If omitted, fallback to the authenticator’s default behaviour. If enabled,
           an authenticator with support for a FIDO2 PIN is required.

I'm not quite sure how exactly the options should look like but they should have the ability to express all 8 possible configurations. The fall back option is for the very common use case where you would like to attempt u2f again but in a different mode. This is particularly useful when e.g. unreliable biometric authentication fails.
Maintainers
NixOS options don't have maintainers so I chose the maintainer of pam-u2f
@philandstuff

There are now (experimental! read the warning) options to do this, introduced in https://github.com/NixOS/nixpkgs/pull/255547. For example:
{
  security.pam.services.sudo.rules.auth.u2f.settings = {
    userpresence = 1;
    pinverification = 1;
  };
}

Currently, these settings must be defined individually for each service (sudo, login, etc).

This appears to be fixed by #255547. Closing...


[Client Tooling] Keybase

Objective
Miniature Keybase MVP functionality that allows accounts to interact with keys (e.g. import, create, export, etc...)
Origin Document
V1 Roadmap: M1 Proof of Stake
In order to achieve the M1 milestone - a mini-keybase implementation is needed to enable dynamic accounts and actors.
This keybase may be used for the following tasks:

Signing blocks
Signing transactions
Signing arbitrary messages
Signing multi-sig messages

Research Resources
If you are unfamiliar with keybases you can gain high level context by reviewing these API specifications:

https://keybase.io/docs/api/1.0
https://keybase.io/docs/api/1.0/call/key/add

Key management exists as part of Pocket V0. It is recommended to install the CLI to see what commands exist as part of key management today. It's also recommended to review the current keybase implementation in the codebase.

Installing the Pocket-Core CLI
keys.go

As V0 is a ~2 yr old project, it is recommended to compare existing functionality against the latest industry standards to look for opportunities to modernize or enhance how keys are managed in V1

Ignite is using Cosmos

It's recommend that the assignee borrows what works from the above resources and integrates it with Pocket-specific utility.
Technical Requirements

Please use /shared/crypto/ed25519 as the PK Library
Please use a filesystem.db for implementation, either Badger.db or Level.db

Goals

Evaluate existing V0 Keybase functionality using the CLI as well as industry approaches documented above
Determine what can be imported into V1 and where Pocket-specific Utility needs to be applied
Determine which filesystem.db should be used from options documented above
Build a functional mini-keybase that can create, delete, import, export, and list and show actor keys
Document the functionality and key architecture of the mini-keybase

Deliverables

[ ] https://github.com/pokt-network/pocket/issues/150
[ ] https://github.com/pokt-network/pocket/issues/205
[ ] https://github.com/pokt-network/pocket/issues/204

Non-goals / Non-deliverables

Integrating Keybase with the CLI or other parts of the codebase

Creator: @jessicadaugherty

@Olshansk keybase bounty parent task for your review

Am ready to take this up if that's cool. I began work on this over the weekend in the keybase_implementation branch of the repo ;)

Perfect, thank you @h5law! I had originally planned this epic so that the initial implementation of the keybase was coupled with Creating and Deleting keys. Does that work for you?
Let me know if it would be helpful to create one or more separate tickets to cover the initial research and keybase build? Or should we just use this parent ticket to track everything and I'll bring in the tickets mentioned in deliverables when they are in progress? Happy to make break anything down further if needed.

I had originally planned this epic so that the initial implementation of the keybase was coupled with Creating and Deleting keys. Does that work for you?

@jessicadaugherty So I actually looked through all of the 3 "sub-issues" and my current code implements all of their features (excluding documentation). I have posted a [WIP] PR for review as there are still some issues in the code.
First is importing keys created with wallet.pokt.network in JSON format (and importing the V1 JSON keys into V0) as these should be interoperable. However the V0 keys generate longer JSON armours 🤔 I am looking into this.
And the other main thing is around signatures - the usages listed in this doc should work in theory as my implementation supports signing arbitrary []byte messages and verifying them. But I don't have the knowledge around multisig to know if it follows the same process. I see that V0 CLI has the option to make a multi-sig account - this is not a feature currently (also is not in the goals of the issues) but I think its important to note where this implementation is not 100% "complete" (as anything can be)
However, creation, delete, show, list, get public key, get private key, sign, verify, check exists, some others are fully working and covered by tests. I think @Olshansk is reviewing it today/tomorrow.
Please let me know if this is doesn't answer what you said 🤣  Or if there are any other features you want me to get in there!
PS: No CLI implementation has been attempted. This is purely the "backend" that the CLI would interact with - the DB layer, interfaces etc

and my current code implements all of their features (excluding documentation)

Oh, amazing! I'll mark all 3 of these as "In Progress" in that case but keep this parent ticket in the iteration.

First is importing keys created with wallet.pokt.network in JSON format (and importing the V1 JSON keys into V0) as these should be interoperable. However the V0 keys generate longer JSON armours 🤔 I am looking into this.

Makes sense. I wonder if the longer key generation is related to hex vs. base64 in ed25519?

But I don't have the knowledge around multisig to know if it follows the same process. I see that V0 CLI has the option to make a multi-sig account - this is not a feature currently (also is not in the goals of the issues) but I think its important to note where this implementation is not 100% "complete" (as anything can be)

Great callout/feedback. I will adjust the ticket(s) to make it clear that multi-sig functionality is out of scope for this ticket. And create a follow up issue :)

However, creation, delete, show, list, get public key, get private key, sign, verify, check exists, import/export (priv string) [V0<->V1 ✅ ], import/export (JSON string) [V1<->V1 ✅ V0<->V1 ❌ ], some others are fully working and covered by tests.

chefs kiss

PS: No CLI implementation has been attempted. This is purely the "backend" that the CLI would interact with - the DB layer, interfaces etc

That's perfect. I have a WIP draft that will cover that integration when we get through the initial build here. I'll update the ticket(s) to note that this is out of scope too.
Thank you so much @h5law!

Makes sense. I wonder if the longer key generation is related to hex vs. base64 in ed25519?

@jessicadaugherty <3 I will look into this

Thank you so much

Anytime this task was a fun one! Looking forward to seeing it all the way through 🚀

@jessicadaugherty ❤ Turns out the JSON issue was related to functions in the ed25519 library used by V0 that are different in V1. The encoding in V0 of the private key when being encrypted follows some unnecessary conversion steps. This however I decided could be done better but by doing it in  a cleaner way the encoded strings are different lengths.
I have just pushed a commit that changes this can can confirm V0-V1 import export is fully functional with JSON and raw priv strings 😉

LFG @h5law!!! Nicely done. Tysm!

Major items in existing PR

[ ] We need to add some documentation. Just the MVR (Minimum Viable Readme): you should be able to port a lot of the text in the description
[ ] Code organization - move the relevant logic into crypto
[ ] I’d like to understand the decision for the choice of nonce (we can discuss inline)
[ ] Left a few comments with a ditto so please apply everywhere

Follow-Up Tasks

[ ] 1. Integrate with the CLI.
[ ] 2. Add support for threshold sigs in the crypto library.

Re 1 - @deblasis was kind enough to leave a lot of comments, so if you search for #150 in the codebase, you’ll find all the appropriate entry points. @jessicadaugherty, could you help create a ticket that captures the necessary work to incorporate the keybase into the CLI?

Re 2 - Rather than multisigs, let’s go with threshold sigs! It’s what everyone wants in the context of governance anyhow, and we’ll be able to reuse it in the consensus library when we add support for DKG (cc @gokutheengineer ).
❓  Last I checked, I couldn't find a good threshold sig library. Part of the ticket should evaluate if a non-interactive threshold sig library is even available (it might only be possible with BLS if we don't have DKG), and decide if we should go with a multi-sig library instead, which are more readily available. Let's create the ticket and start the discussion there.
✍  It'll affect how we do verification of signed messages, but I don't think the keybase specifically will need special support for it. For both threshold sigs and multisigs, the user still only has access to their own key and not the others.

Bonus
🏗  CC @okdas for context that our keybase uses badgerDB. One day (distant day), we might have other backends (similar to what cosmos does) with real key management systems.

Extra Bonus
🌕  Also CCing @roshanr95 from Marlin protocol who are focusing a lot of enclaves. There is no immediate AI, but if we want pocket operators to work with secure enclaves, there will need to be som thought put into change sin the keybase.

We have found the 🔑


Clean up namespace conflict warnings with @ImportFrom

fixed with @bbc2060 but need to be careful, I might have missed a few imports. Trial and error here.

also renamed sub() to sub_job() to avoid overwriting base::sub()


Ingress cannot be watched in k8s 1.22+

Hi,
Accessing ingresses through extensions/v1beta1 is no longer possible since 1.22. Deprecation notice
This means that the following code has to start using networking.k8s.io/v1
https://github.com/robusta-dev/kubewatch/blob/55493a566b5c1ec65af7459e3ca7ed443d40b320/pkg/controller/controller.go#L494
However, by doing so we are breaking ingress support for people running 1.18 and lower.
Since people should have moved on from 1.18 a long time ago, I think it's fair enough to proceed.
Let me know and I can open a pull request pretty quickly

Thanks for reporting it @olivierboucher
Will this change fail on older k8s versions, or the old Ingresses will just be ignored?

Not sure of the exact behavior, I would test it but it's not possible to spawn clusters with 1.18 or lower on GKE anymore.
I don't know if the networking.k8s.io/v1 existed then.

Got it.
Please create the pr.
Maybe we can test it on kind cluster or similar

@arikalon1 There you go. I was surprised to see that the dependency was so far behind.

Thanks @olivierboucher
I'll review it shortly

released in 2.3


Inference on Universal Transformer fails due to while/Pad in a while loop

Description
Attempting to use t2t-decoder with a universal transformer fails.
Environment information
OS: Ubuntu 19 (Also tested on 18 with same result)

$ pip freeze | grep tensor
mesh-tensorflow==0.0.5
tensor2tensor==1.14.0
tensorboard==1.14.0
tensorflow-datasets==1.2.0
tensorflow-estimator==1.14.0
tensorflow-gan==1.0.0.dev0
tensorflow-gpu==1.14.0
tensorflow-metadata==0.14.0
tensorflow-probability==0.7.0

$ python -V
Python 3.7.3

For bugs: reproduction and error logs
# Steps to reproduce:

t2t-datagen --problem=algorithmic_math_two_variables

t2t-trainer --problem=algorithmic_math_two_variables --model=universal_transformer --hparams_set=universal_transformer_tiny

t2t-decoder --problem=algorithmic_math_two_variables --model=universal_transformer --hparams_set=universal_transformer_tiny

# Error logs:
INFO:tensorflow:Transforming body output with symbol_modality_258_128.top
I0922 17:58:20.209241<PHONE_NUMBER>43936 t2t_model.py:2248] Transforming body output with symbol_modality_258_128.top
INFO:tensorflow:Cannot use 'while/Pad' as input to 'Identity_5' because 'while/Pad' is in a while loop.

Identity_5 while context: None
while/Pad while context: while/while_context

Traceback for Identity_5:
  File "/home/tom/.local/bin/t2t-decoder", line 17, in <module>
    tf.app.run()
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 299, in run
    _run_main(main, args)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "/home/tom/.local/bin/t2t-decoder", line 12, in main
    t2t_decoder.main(argv)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 205, in main
    decode(estimator, hp, decode_hp)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 106, in decode
    checkpoint_path=FLAGS.checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 224, in decode_from_dataset
    checkpoint_path=checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 313, in decode_once
    for num_predictions, prediction in enumerate(predictions):
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 619, in predict
    features, None, ModeKeys.PREDICT, self.config)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1146, in _call_model_fn
    model_fn_results = self._model_fn(features=features, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1415, in wrapping_model_fn
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1472, in estimator_model_fn
    return model.estimator_spec_predict(features, use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1708, in estimator_spec_predict
    features[name] = tf.identity(feature)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/util/dispatch.py", line 180, in wrapper
    return target(*args, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/array_ops.py", line 86, in identity
    ret = gen_array_ops.identity(input, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 4253, in identity
    "Identity", input=input, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2005, in __init__
    self._traceback = tf_stack.extract_stack()

Traceback for while/Pad:
  File "/home/tom/.local/bin/t2t-decoder", line 17, in <module>
    tf.app.run()
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 299, in run
    _run_main(main, args)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "/home/tom/.local/bin/t2t-decoder", line 12, in main
    t2t_decoder.main(argv)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 205, in main
    decode(estimator, hp, decode_hp)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 106, in decode
    checkpoint_path=FLAGS.checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 224, in decode_from_dataset
    checkpoint_path=checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 313, in decode_once
    for num_predictions, prediction in enumerate(predictions):
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 619, in predict
    features, None, ModeKeys.PREDICT, self.config)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1146, in _call_model_fn
    model_fn_results = self._model_fn(features=features, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1415, in wrapping_model_fn
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1472, in estimator_model_fn
    return model.estimator_spec_predict(features, use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1696, in estimator_spec_predict
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 817, in infer
    top_beams, alpha, use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/models/research/universal_transformer.py", line 276, in _beam_decode
    top_beams, alpha, use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 940, in _beam_decode_slow
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/beam_search.py", line 800, in beam_search
    back_prop=False)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 3501, in while_loop
    return_same_structure)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 3012, in BuildLoop
    pred, body, original_loop_vars, loop_vars, shape_invariants)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 2937, in _BuildLoop
    body_result = body(*packed_vars_for_body)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/beam_search.py", line 717, in inner_loop
    i, alive_seq, alive_log_probs, states)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/beam_search.py", line 597, in grow_topk
    flat_logits = symbols_to_logits_fn(flat_ids)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 873, in symbols_to_logits_fn
    ids = tf.pad(ids[:, 1:], [[0, 0], [0, 1], [0, 0], [0, 0]])
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/array_ops.py", line 2367, in pad
    result = gen_array_ops.pad(tensor, paddings, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 5993, in pad
    "Pad", input=input, paddings=paddings, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2005, in __init__
    self._traceback = tf_stack.extract_stack()

I0922 17:58:20.311590<PHONE_NUMBER>43936 control_flow_util.py:349] Cannot use 'while/Pad' as input to 'Identity_5' because 'while/Pad' is in a while loop.

Identity_5 while context: None
while/Pad while context: while/while_context

Traceback for Identity_5:
  File "/home/tom/.local/bin/t2t-decoder", line 17, in <module>
    tf.app.run()
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 299, in run
    _run_main(main, args)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "/home/tom/.local/bin/t2t-decoder", line 12, in main
    t2t_decoder.main(argv)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 205, in main
    decode(estimator, hp, decode_hp)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 106, in decode
    checkpoint_path=FLAGS.checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 224, in decode_from_dataset
    checkpoint_path=checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 313, in decode_once
    for num_predictions, prediction in enumerate(predictions):
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 619, in predict
    features, None, ModeKeys.PREDICT, self.config)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1146, in _call_model_fn
    model_fn_results = self._model_fn(features=features, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1415, in wrapping_model_fn
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1472, in estimator_model_fn
    return model.estimator_spec_predict(features, use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1708, in estimator_spec_predict
    features[name] = tf.identity(feature)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/util/dispatch.py", line 180, in wrapper
    return target(*args, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/array_ops.py", line 86, in identity
    ret = gen_array_ops.identity(input, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 4253, in identity
    "Identity", input=input, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2005, in __init__
    self._traceback = tf_stack.extract_stack()

Traceback for while/Pad:
  File "/home/tom/.local/bin/t2t-decoder", line 17, in <module>
    tf.app.run()
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 299, in run
    _run_main(main, args)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "/home/tom/.local/bin/t2t-decoder", line 12, in main
    t2t_decoder.main(argv)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 205, in main
    decode(estimator, hp, decode_hp)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 106, in decode
    checkpoint_path=FLAGS.checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 224, in decode_from_dataset
    checkpoint_path=checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 313, in decode_once
    for num_predictions, prediction in enumerate(predictions):
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 619, in predict
    features, None, ModeKeys.PREDICT, self.config)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1146, in _call_model_fn
    model_fn_results = self._model_fn(features=features, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1415, in wrapping_model_fn
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1472, in estimator_model_fn
    return model.estimator_spec_predict(features, use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1696, in estimator_spec_predict
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 817, in infer
    top_beams, alpha, use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/models/research/universal_transformer.py", line 276, in _beam_decode
    top_beams, alpha, use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 940, in _beam_decode_slow
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/beam_search.py", line 800, in beam_search
    back_prop=False)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 3501, in while_loop
    return_same_structure)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 3012, in BuildLoop
    pred, body, original_loop_vars, loop_vars, shape_invariants)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/control_flow_ops.py", line 2937, in _BuildLoop
    body_result = body(*packed_vars_for_body)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/beam_search.py", line 717, in inner_loop
    i, alive_seq, alive_log_probs, states)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/beam_search.py", line 597, in grow_topk
    flat_logits = symbols_to_logits_fn(flat_ids)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 873, in symbols_to_logits_fn
    ids = tf.pad(ids[:, 1:], [[0, 0], [0, 1], [0, 0], [0, 0]])
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/array_ops.py", line 2367, in pad
    result = gen_array_ops.pad(tensor, paddings, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 5993, in pad
    "Pad", input=input, paddings=paddings, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2005, in __init__
    self._traceback = tf_stack.extract_stack()

Traceback (most recent call last):
  File "/home/tom/.local/bin/t2t-decoder", line 17, in <module>
    tf.app.run()
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 299, in run
    _run_main(main, args)
  File "/home/tom/.local/lib/python3.7/site-packages/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "/home/tom/.local/bin/t2t-decoder", line 12, in main
    t2t_decoder.main(argv)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 205, in main
    decode(estimator, hp, decode_hp)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/bin/t2t_decoder.py", line 106, in decode
    checkpoint_path=FLAGS.checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 224, in decode_from_dataset
    checkpoint_path=checkpoint_path)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/decoding.py", line 313, in decode_once
    for num_predictions, prediction in enumerate(predictions):
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 619, in predict
    features, None, ModeKeys.PREDICT, self.config)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1146, in _call_model_fn
    model_fn_results = self._model_fn(features=features, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1415, in wrapping_model_fn
    use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1472, in estimator_model_fn
    return model.estimator_spec_predict(features, use_tpu=use_tpu)
  File "/home/tom/.local/lib/python3.7/site-packages/tensor2tensor/utils/t2t_model.py", line 1708, in estimator_spec_predict
    features[name] = tf.identity(feature)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/util/dispatch.py", line 180, in wrapper
    return target(*args, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/array_ops.py", line 86, in identity
    ret = gen_array_ops.identity(input, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 4253, in identity
    "Identity", input=input, name=name)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/op_def_library.py", line 788, in _apply_op_helper
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/util/deprecation.py", line 507, in new_func
    return func(*args, **kwargs)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 3616, in create_op
    op_def=op_def)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2043, in __init__
    self._control_flow_post_processing()
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/framework/ops.py", line 2052, in _control_flow_post_processing
    control_flow_util.CheckInputFromValidContext(self, input_tensor.op)
  File "/home/tom/.local/lib/python3.7/site-packages/tensorflow/python/ops/control_flow_util.py", line 350, in CheckInputFromValidContext
    raise ValueError(error_msg + " See info log for more details.")
ValueError: Cannot use 'while/Pad' as input to 'Identity_5' because 'while/Pad' is in a while loop. See info log for more details.

I saw the same error with transformer_moe model with tensor2tensor 1.14.0, but now I don't see it anymore with the head version. Maybe it has been fixed recently?

I did some bisecting to find the fixing comment: https://github.com/tensorflow/tensor2tensor/commit/448ce0f56d7f67f7b610c1db72e2ea9529c44511


Add links, clean the code

Added the links and made code a bit easier to read, also, I moved the gravity variable to the CC_31_FlappyBird.pde since it was already global. I think it's best to have all of the globals in a single place, even if they are only used in one file, I'll be happy to revert the change if you don't agree :)

wonderful thank you for this!!


Missing Step of Copying Host Before Opening The Twins Explorer

Before the step that says Next, select the Open Azure Digital Twins Explorer (preview) button., there needs to be a step to copy the host of the Twins url. The reason is that the Twins Explorer has a popup when you go to that page that demands that host url; which can't be disregarded.

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

ID: d81034c0-f8e3-a26a-acaa-0513d2762a98
Version Independent ID: 864d5793-8ec9-6baf-7f3a-a4896e77a931
Content: Quickstart - Get started with Azure Digital Twins Explorer - Azure Digital Twins
Content Source: articles/digital-twins/quickstart-azure-digital-twins-explorer.md
Service: digital-twins
GitHub Login: @baanders
Microsoft Alias: baanders

@CheetahChrome Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Hi @CheetahChrome, thank you for reaching out!
What you've described is actually unexpected behavior--selecting that button from the portal should open Azure Digital Twins Explorer with an automatic connection to the related instance, without requiring you to manually enter the host URL.
Could you use the feedback button in the Explorer to submit feedback and describe your experience for the product team?

If you leave details and your email in your feedback submission, they can reach out to you directly if they have questions about how to reproduce.
In the meantime, I'm going to close this doc suggestion as we approach this issue from the product side instead. Please feel free to continue commenting if you have additional comments or questions, however, and we can reopen as needed. Thank you!
#please-close

What you've described is actually unexpected behavior

I was simply a new user, using the documentation to create a Twins instance....at minimum it would be a nice to have a warning about having to know the url to the host. It took me a few minutes to associate the popup request with the host as needed.

Thanks for the additional information! I understand how that connection wouldn't be immediately obvious.
Partially for this reason, ideally users shouldn't have to know the URL to the host at this point, so it seems like there may be something unexpected happening in the product to give you this experience.
In our tests the connection has been automatic with no pop up, so it'd be great to get you in touch directly with the product team through the feedback in the Explorer tool, to help them investigate a potential bug that we might need to resolve to produce the desired experience for everyone (no pop-up and no requirement to enter URL information).

I'll also go ahead and draft in a note to the doc to clarify what this pop up means, for those that might see it! But submitting product feedback would be extra helpful as we try to replicate this issue and address it from the source.

Reopening to add doc note
#please-open

Update: In one of my Azure accounts, I was just able to reproduce!
In addition to the doc note, I can now submit a product bug myself.
Please still feel free to submit product feedback describing your experience as well!
I'll continue to update this thread when the doc update is ready

The doc update is drafted in the linked PR. I'll have Git automatically close this issue again when the PR is merged into the main content set, and it should go live later today. Thank you!

I appreciate the follow-through by doing a couple of more tests. As requested, I was going to report the feedback on the Twins explorer when I get this message in twins (not my Azure dashboard) after the initial SSO login:

Selected user account does not exist in tenant 'Microsoft Services' and cannot access the application '85607549-2ae8-44d7-85f8-f3405d0a595c' in that tenant. The account needs to be added as an external user in the tenant first. Please use a different account.

Sigh
Which is bizarre because I got the Twins working via the example given. I will try again in a couple of days to add the feedback as requested.

Thanks for the attempt, and for the additional information.
Presently, those using personal Microsoft accounts (MSA)s are unable to switch the Explorer URL from one instance to another, and I wonder if that could be at play here, affecting you since you had to enter an instance URL to use the Explorer at all.

As a workaround, you may be able to try accessing the Azure Digital Twins Explorer using a direct link to the environment. I will also share this with the product team.
Sorry for the inconvenience, and thank you for sharing your issues with us so that we can work to make the Explorer better.

As of today, I got the message again after using my one login which I have continuously used throughout the whole process. But...upon a second attempt (no setting changed), I then got the Enter Host popup and was allowed to re-add my host and it worked. Something is up with the SSO and Twins. This is not production for me, so its not important. Thank you for your followups.

Popping back in to note that I've shared this entire thread with the product team and we've created a bug around these tenant issues.
Thank you for sharing the details of your experience!


SPARKC-362: Added support for INSERT ... IF NOT EXISTS

Added support for IF NOT EXISTS behaviour when inserting data and specifying ifNotExists = true in WriteConf.

test this please

Build against Scala 2.11 finished with success

retest this please

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with failure

For some reason 2.10 is just unhappy today, but it has nothing to do with the code. Merged Thanks @randomf for your contribution!

Build against Scala 2.10 finished with failure


feat: add config model

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 74.206%

Files with Coverage Reduction
New Missed Lines
%

pkg/cmd/destroy/options.go
7
81.86%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
6867

Relevant Lines:
9254

💛  - Coveralls


Release Distributed Tracing Track 2 Plugin Preview 4 for Java

API Design

N/A for Preview 4

Feature Work

[x] undone from Preview 3 rename plugin from tracing-opentelemetry to azure.core.tracing
[x] OpenTelemetry Packages available for testing by Azure SDK team

[x] Java SDK (no ETA) https://github.com/open-telemetry/opentelemetry-java

[ ] Preview 4 Azure SDK Distributed Tracing Plugin / Context tested with OpenTelemetry

Documentation

N/A for Preview 4

CUT

[ ] Preview 4 Azure.Identity tracing added (blocked on MSAL httpClient abstraction https://github.com/Azure/azure-sdk-for-java/issues/5284)
[ ] Preview 4 UX study (validate theory that tracing support in Azure SDK is extremely useful for diagnosing reliability issues)
[ ] Preview 4 Before the UX study, audit to make sure tracing is consistent across each language
[ ] Preview 4 React to UX study feedback

Related

Preview 2 Tracing Epic for Java: https://github.com/Azure/azure-sdk-for-java/issues/4433
Preview 3 Tracing Epic for Java: https://github.com/Azure/azure-sdk-for-java/issues/4761
Preview 4 Tracing Epic for Java: https://github.com/Azure/azure-sdk-for-java/issues/4762

Closing issue tracking the release of azure-core-tracing-opencensus version 1.0.0-preview.4


Can you make window resizeable and remember size+position on desktop?

Can you make window resizeable and remember size+position on desktop?

does not add functionality


fix: replace deprecated poetry lock

PR Checklist

[x] A description of the changes is added to the description of this PR.
[x] If there is a related issue, make sure it is linked to this PR.
[x] If you've fixed a bug or added code that should be tested, add tests! (Not relevant)
[x] Documentation in docs is updated (Not relevant)

Description of changes
This minor change replaces the deprecated poetry lock --check with the new command poetry check --lock.
This will resolve the following warning that currently appears when using make check.
> make check
🚀 Checking Poetry lock file consistency with 'pyproject.toml': Running poetry lock --check
poetry lock --check is deprecated, use `poetry check --lock` instead.
poetry.lock is consistent with pyproject.toml.
...

Thanks for the contribution! Could you change it [here[(https://github.com/fpgmaas/cookiecutter-poetry/blob/49756a70c7e8ec87d219de4c0effdca75838bbfb/{{cookiecutter.project_name}}/Makefile#L11) as well?

@fpgmaas Done. Thanks for pointing that out!


Migrate to tree-sitter-language-pack: expand language support

WIP; Resolves #7.
This replaces the tree-sitter language pack from grantjenks/py-tree-sitter-languages with Goldziher/tree-sitter-language-pack, significantly expanding language support and addressing maintenance issues. Key changes include:

Greatly increases the number of supported languages, including Swift and Svelte.
Resolves dependency on an unmaintained package that was forcing grep-ast to use an old tree-sitter version (0.21).
Unlocks the ability to use more recent tree-sitter versions.
Updates requirements.txt to use tree-sitter-language-pack>=0.2.0.
Increments the version number to 0.3.4-dev in setup.py.
Adds extensive test cases for parsing various languages in test_parsers.py.

Notable changes:

Removed support for DOT, OCaml, ql (GitHub CodeQL), and tsq (Tree Sitter Query) due to their absence in the new pack.
Removed potentially incorrect mappings for .gomod, .sqlite, and .regex extensions.
Replaced the uncommon ".et" mapping for "embeddedtemplate" with mappings for ERB and EJS, which are common uses of embedded templates.
Re-enabled markdown as the new pack uses to a different markdown grammar that likely doesn't suffer from previous bugs.

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


runfile error

hi
I have this problem
what is the problem

runfile is not an error, it's the command we use to run files in our consoles. You need to use the print command in your code if you want to see something printed after running it.


Pass Context during exec in create.

Fixes  #685

@martinei if you redo the PR against development we can merge it right away :)

@aeneasr I have rebased the branch. It should be mergable again.


Fix interesting conditionals

Codecov Report

Merging #106 into master will decrease coverage by 0.37%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #106      +/-   ##
==========================================
- Coverage    72.5%   72.12%   -0.38%
==========================================
  Files          39       39
  Lines        3186     3186
  Branches       50       50
==========================================
- Hits         2310     2298      -12
- Misses        843      855      +12
  Partials       33       33

Impacted Files
Coverage Δ

src/tokentree/walk/WalkSharp.hx
87.3% <100%> (ø)
:arrow_up:

src/tokentree/walk/WalkFieldDef.hx
84.09% <0%> (-11.37%)
:arrow_down:

src/tokentree/walk/WalkClass.hx
79.34% <0%> (-2.18%)
:arrow_down:

src/tokentree/walk/WalkTypedefBody.hx
81.72% <0%> (-2.16%)
:arrow_down:

src/tokentree/utils/TokenTreeCheckUtils.hx
49.58% <0%> (-0.42%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 97f0a4e...482cfad. Read the comment docs.


Update aws-java-sdk-bundle to 1.12.301

Updates com.amazonaws:aws-java-sdk-bundle from 1.12.300 to 1.12.301.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-bundle" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-bundle" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #2327.


Repackage eykthyr.

Make some changes to function signatures.
Add missing dependencie(s).

Note that these changes also reflect updates to the internals of Popari, which I haven't uploaded to PyPI yet.


Add 'TWRP' topic

Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/main/CONTRIBUTING.md.
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[x] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

TWRP is the custom recovery used for Android devices. I think it should be added, because people then can easily find repositories related to the custom recovery. For example, I want to find a flashable ZIP for TWRP.

Something that does not neatly fit into the binary options above

[ ] My suggested edits are not about an existing topic or collection, or at least not a single one
[ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
[ ] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Please replace this line with an explanation of your proposed changes.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Fixed hyphen issue with 'open source'.

Looks great. Thanks for your contribution!


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.24",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=65ab30f6a6952fa9ee13009862736cf8d110e6e5"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "65ab30f6a6952fa9ee13009862736cf8d110e6e5",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "iommu: Fix potential use-after-free during probe\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.24 by commit 65ab30f6a6952fa9ee13009862736cf8d110e6e5. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000448


Web sign in page doesn't fit screen

Describe the bug?
When using WebAuthentication, the browser sign in page that gets opened has content larger than the device screen (in both dimensions), and it is scrollable.
What is expected to happen?
The sign in page content should fit the screen and not be scrollable.
What is the actual behavior?
The sign in page content is larger than the screen and is scrollable.
Reproduction Steps?
Open the WebSignIn (iOS) sample (after providing config) on an iPhone 13 Pro simulator and click "Sign In"
Additional Information?
No response
SDK Version(s)
1.0.0
Build Information
No response

Thanks for reporting the issue @aetherealtech.  I was able to reproduce the issue and it seems to be caused by the device page zoom setting. At 100%, the content becomes scrollable. The page zoom setting is within the html of the sign-in-page on the developer portal and can be adjusted there.

@emmanuelogunmuyiwa-okta Thanks for you quick response!  So do you recommend customizing the login page HTML to address this?
I've had this problem with web content on mobile devices before.  If we go this route I can share the HTML header attributes that we use to force content on mobile to fit the screen and not scroll.

@aetherealtech You can customize your minimum or maximum scale factors to best suit your use case. Please have a look at the developer documentation as well, it provides you further explanations on how to customize the Sign-In Widget.

Thank you for the question @aetherealtech, I hope the answers helped.  I'm going to close this, feel free to re-open if needed (or ask new questions in new issues).


Bluetooth: Mesh: Inclusive terminology

Implements the Bluetooth appropriate language mapping for the Bluetooth
mesh subsystem.
Changes the following terms:

Master security credentials -> Flooding security credentials
Whitelist filter -> Accept filter
Blacklist filter -> Reject filter
Removes CDB's NODE_BLACKLISTED, which was not in use.

Signed-off-by: Trond Einar Snekvik<EMAIL_ADDRESS>

I would argue that there are no actual API changes for this, it's purely internal. I'm not sure what and where to put this in the release notes.

please update release notes for these changes.

There are no public API changes here.


Use GitHub Projects?

GitHub has new awesome feature
Maybe it's better to use it?

We are considering this, but currently this means importing issues manually.

It is too easy too import actually

I've tried using Projects for cherrypy repo, but it turned out to be a pain in the butt.
As for now, I'm happy with waffle.io