-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gost Project #1
base: master
Are you sure you want to change the base?
Gost Project #1
Conversation
PiperOrigin-RevId: 380190962
PiperOrigin-RevId: 380237223
PiperOrigin-RevId: 380243629
PiperOrigin-RevId: 380296477
PiperOrigin-RevId: 380470496
PiperOrigin-RevId: 380650647
PiperOrigin-RevId: 380687139
Some parts of the forward pass would previously overflow in float16. Such parts are now done in float32. PiperOrigin-RevId: 380857663
PiperOrigin-RevId: 380858205
…subject to change in the near future. PiperOrigin-RevId: 380907598
Before, it returned None. But almost every use of get_distribution_strategy() assumes an actual strategy is returned and crashes when None is returned. Returning the default strategy fixes these issues and is equivalent to using no strategy, as the default strategy is always in effect when no other strategy is used. PiperOrigin-RevId: 380951055
In nlp/train.py and vision/beta/train.py, certain flags are marked as required. Additionally, in certain functions, error messages are improved if a necessary flag is not specified, which is a fallback in case a file calling define_flags() does not mark the necessary flags are required. Previously if any of these flags were not specified, it would crash with a cryptic error message, making it hard to tell what went wrong. In a subsequent change, I will mark flags as required in more files which call define_flags(). PiperOrigin-RevId: 381066985
PiperOrigin-RevId: 381089283
PiperOrigin-RevId: 381152422
PiperOrigin-RevId: 381301573
PiperOrigin-RevId: 381302776
PiperOrigin-RevId: 381320453
…puts to floats, and normalize output box coordinates. PiperOrigin-RevId: 381334851
…ig`, to allow combining multiple datasets using a user defined combine_fn. PiperOrigin-RevId: 381363688
PiperOrigin-RevId: 381367878
…how how an e2e training works. PiperOrigin-RevId: 381368435
PiperOrigin-RevId: 381396116
PiperOrigin-RevId: 381516130
PiperOrigin-RevId: 381540013
PiperOrigin-RevId: 381908843
PiperOrigin-RevId: 382051212
PiperOrigin-RevId: 382051540
PiperOrigin-RevId: 382240268
PiperOrigin-RevId: 382382393
PiperOrigin-RevId: 382396878
PiperOrigin-RevId: 401839863
PiperOrigin-RevId: 401894268
PiperOrigin-RevId: 401911051
PiperOrigin-RevId: 401913091
PiperOrigin-RevId: 402314322
PiperOrigin-RevId: 402338060
Use property value shorthand. eslint: object-shorthand Sema Reaction: 🛠️ This code needs a fix | Sema Tags: Reusable |
You should iterate sequentially on a focused chunk of work at a time. Sema Reaction: 🛠️ This code needs a fix |
yo deepak |
dffew AND we need to save selected collection name to some variable and then check if this collection become active. Sema Reaction: ❓ I have a question |
Preved |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's obvious that if you make an iOS application in 2022, you need to make sure that it runs smoothly on iOS 14 released in December 2020. It's worth noting that iPhones since 6S to 12 Pro are compatible with the latest release of iOS. However, if you want your iOS app to be available for a broader range of users, you might consider the backward compatibility. Backward compatibility means your application would run as well on older versions of iOS and older iPhones or iPads. Depending on your app's advancement and use of the most recent iOS features, achieving backward compatibility may be difficult. The latest changes and features include (among others): That's the moment when you need to decide if and how far backward you want to go. How much time and money you're willing to spend and how many users it will give you? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
find new awesome Sema Reaction: 👌 This code looks good | Sema Tags: Readable, Secure, Efficient |
add repo to QA env |
123 |
123123123123 |
looks good |
Description
Type of change
For a new feature or function, please create an issue first to discuss it
with us before submitting a pull request.
Note: Please delete options that are not relevant.
Tests
Test Configuration:
Checklist