Emoji in Emoji cheat sheet are not rendered

Issue description
Congo official document describes the Emoji cheat sheet as a useful reference for finding Emoji shortcodes, but the examples used on that page, see_no_evil :see_no_evil:, hear_no_evil :hear_no_ evil:, speak_no_evil :speak_no_evil: are NOT in Emoji cheat sheet.
These are listed as :see_no_evil_monkey:, :hear_no_evil_monkey: and :speak_no_evil_monkey: in Emoji cheat sheet, and I have confirmed that these shortcodes will not rendered correctly in Congo.
Similar examples were found in many flag glyphs like :flag_japan: during the translation process.
This is NOT the fault of @jpanther and us.
Because Hugo's official documentation has a similar description.
I also found a related Issue in the Hugo repository.
See. https://github.com/gohugoio/hugo/issues/6740
However, at this time, the opposite is happening to the Issue, GitHub format shortcode is working correctly instead of the Emojipedia format.
See. https://emojipedia.org/hear-no-evil-monkey#technical
In short, this is a Hugo bug, not a Congo bug, but at least we should avoid directing users from Congo's documentation to the Emoji cheat sheet because it is confusing to Congo users.
Theme version
v2.6.1
Hugo version
hugo v0.115.4+extended darwin/arm64
Which browser rendering engines are you seeing the problem on?
Chromium (Google Chrome, Microsoft Edge, Brave, Vivaldi, Opera, etc.), WebKit (Safari)
URL to sample repository or website
https://jpanther.github.io/congo/samples/emoji/
Hugo output or build error messages
No build error.

Don't close it until it is fixed.
It should be a minor bug that only requires a small modification to the document.
And I don't think the actions that automatically label and close issues are working effectively for this project.

@shin-sforzando Apologies, I agree that the stale actions are a bit too aggressive. When I first set them up it was to keep me focussed on getting items dealt with, but I've since had a lot of changes in my personal life that have caused me to have less time available and so it's no longer an effective system. I've made a change to the stale workflow so that it now only marks stale after 120 days (it was previously 30) and so hopefully this helps to work around this problem.
As for this issue, I'll reopen it as I agree with your comments.

@jpanther I know very well that you are so busy.
If there is anything I can do to help, please reach out to me anytime.


End-to-end test of governable block gas limit

Expected Behavior
We have an end-to-end test of the governable block gas limit.
Current Behavior
No end-to-end test

This could be expanded more generally into an end-to-end test of the BlockChainParameters interactions, perhaps repurposing end-to-end-exit-test to be end-to-end-block-chain-parameters-test

Was handled by #1245


Surfactant crash when processing files cant decode byte 0xc4 in position 35

Describe the bug
Installed the latest rc2.
Run generate over files that I know crash surfactant
observe crash
To Reproduce
Steps to reproduce the behavior:

Install Surfactant 0.0.0rc2
surfactant generate ./_modules.extracted.crashes.surfactant test.sbom.json

Expected behavior
sbom generated
Crash Output
`
└─$ surfactant generate ./_modules.extracted.crashes.surfactant test.sbom.json
2024-01-25 08:45:30.479 | WARNING  | surfactant.cmd.generate:sbom:284 - Fixing install path
2024-01-25 08:45:30.479 | INFO     | surfactant.cmd.generate:sbom:293 - Processing ./_modules.extracted.crashes.surfactant
Traceback (most recent call last):
File "/home/user/surfactant/bin/surfactant", line 8, in
sys.exit(main())
^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/click/core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/surfactant/cmd/generate.py", line 347, in sbom
if ftype := pm.hook.identify_file_type(filepath=filepath):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/pluggy/_hooks.py", line 501, in call
return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/pluggy/_manager.py", line 119, in _hookexec
return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/pluggy/_callers.py", line 138, in _multicall
raise exception.with_traceback(exception.traceback)
File "/home/user/surfactant/lib/python3.11/site-packages/pluggy/_callers.py", line 102, in _multicall
res = hook_impl.function(*args)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/surfactant/lib/python3.11/site-packages/surfactant/filetypeid/id_hex.py", line 82, in identify_file_type
curr = f.readline()
^^^^^^^^^^^^
File "", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc4 in position 35: invalid continuation byte
└─$ surfactant version
0.0.0rc2
`
System Information (please complete the following information):

OS: Debian 6.1.20-1

Additional context
Cannot share the files but this is the head of the first one in the directory. I'm not sure if this file is the one causing the crash, if Surfactant outputted the file it crashes on I could examine that file further.
xxd 324C016 | head 00000000: 0000 0c48 4c69 6e6f 0210 0000 6d6e 7472  ...HLino....mntr 00000010: 5247 4220 5859 5a20 07ce 0002 0009 0006  RGB XYZ ........ 00000020: 0031 0000 6163 7370 4d53 4654 0000 0000  .1..acspMSFT.... 00000030: 4945 4320 7352 4742 0000 0000 0000 0000  IEC sRGB........ 00000040: 0000 0001 0000 f6d6 0001 0000 0000 d32d  ...............- 00000050: 4850 2020 0000 0000 0000 0000 0000 0000  HP  ............ 00000060: 0000 0000 0000 0000 0000 0000 0000 0000  ................ 00000070: 0000 0000 0000 0000 0000 0000 0000 0000  ................ 00000080: 0000 0011 6370 7274 0000 0150 0000 0033  ....cprt...P...3 00000090: 6465 7363 0000 0184 0000 006c 7774 7074  desc.......lwtpt
I did put that single file in its own directory and reran Surfactant it ran but produced an empty output.
`
└─$ cp ./_modules.extracted.crashes.surfactant/324C016 ./crash1
└─$ surfactant generate ./crash1 test.sbom.json
2024-01-25 08:55:14.539 | WARNING  | surfactant.cmd.generate:sbom:284 - Fixing install path
2024-01-25 08:55:14.539 | INFO     | surfactant.cmd.generate:sbom:293 - Processing ./crash1
└─$ cat test.sbom.json
{
"systems": [],
"hardware": [],
"software": [],
"relationships": [],
"analysisData": [],
"observations": [],
"starRelationships": []
}
└─$ ls ./crash1
324C016
└─$ file ./crash1/324C016
./crash1/324C016: Microsoft color profile 2.1, type Lino, RGB/XYZ-mntr device, IEC/sRGB model by HP, 3144 bytes, 9-2-1998 6:49:00, relative colorimetric "sRGB IEC61966-2.1"
`

For the SBOM being empty, Surfactant doesn't (currently) identify MS color profiles as software.
As far as the file causing the crash, can you find one ending with one of the extensions (case-insensitive) listed in https://github.com/LLNL/Surfactant/blob/main/surfactant/filetypeid/id_hex.py#L40-L68?

I found the file by adding some debugging to surfactant. It's 46 mb and I'm not too sure what it is
4B32E82.hex
File returns that it's just 'hex data'. Binwalk finds a ton of 'Compiled Java class data' It is copywrite oracle/ sun microsystems so I can share it with you if you would like. I think it's the JVM or something binwalk -Me carved out of the files I was looking at that isn't what it should be.
Please email me and I could share the file, but 46MB is a bit big for posting here. Or I can grep it / search things in it if that would help you.

@astrofage bug should be fixed now in the main GitHub branch -- let me know if you still have issues with crashing on that same file with the dev branch, or after the PyPI package gets updated


Backend failed to start up TypeError: Cannot read properties of undefined (reading 'fromConfig')

Describe the bug
Unable to start the project post adding the Jira backend plugin getting the following error
Backend failed to start up TypeError: Cannot read properties of undefined (reading 'fromConfig')

To reproduce
Steps to reproduce the behavior:

Set up a new backstage project .
Added the plugin by following the documentation including the steps adding the three lines required.

Create a new file with the name jiraDashboard.ts.
Added the following lines into src/index.ts.

import jiraDashboard from './plugins/jiraDashboard';

// Add this line into main()
  const jiraDashboardEnv = useHotMemoize(module, () => createEnv('jira-dashboard'));

// Add this following line into the existing routes
  apiRouter.use('/jira-dashboard', await jiraDashboard(jiraDashboardEnv));

yarn dev
yarn run v1.22.21
$ concurrently "yarn start" "yarn start-backend"
$ yarn workspace app start
$ yarn workspace backend start
$ backstage-cli package start
$ backstage-cli package start
[0] Loaded config from app-config.yaml, app-config.local.yaml
[0] <i> [webpack-dev-server] Project is running at:
[0] <i> [webpack-dev-server] Loopback: http://localhost:3000/, http://[::1]:3000/
[0] <i> [webpack-dev-server] Content not from webpack is served from '/Users/<username>/test_projects/developer-activity/packages/app/public' directory
[0] <i> [webpack-dev-server] 404s will fallback to '/index.html'
[0] <i> [webpack-dev-middleware] wait until bundle finished: /catalog?filters%5Bkind%5D=component&filters%5Buser%5D=all
[0] webpack compiled successfully
[1] Loaded config from app-config.yaml, app-config.local.yaml
[1] 2024-01-04T13:43:13.564Z backstage info Found 3 new secrets in config that will be redacted
[1] ObservableConfigProxy {
[1]   parent: undefined,
[1]   parentKey: undefined,
[1]   config: ConfigReader {
[1]     data: { proxy: [Object] },
[1]     context: 'app-config.local.yaml',
[1]     fallback: ConfigReader {
[1]       data: [Object],
[1]       context: 'app-config.yaml',
[1]       fallback: undefined,
[1]       prefix: '',
[1]       filteredKeys: undefined,
[1]       notifiedFilteredKeys: Set(0) {}
[1]     },
[1]     prefix: '',
[1]     filteredKeys: undefined,
[1]     notifiedFilteredKeys: Set(0) {}
[1]   },
[1]   subscribers: [ [Function (anonymous)] ]
[1] }
[1] Backend failed to start up TypeError: Cannot read properties of undefined (reading 'fromConfig')
[1]     at makeCreateEnv (/Users/<username>/test_projects/developer-activity/packages/backend/src/index.ts:43:35)
[1]     at main (/Users<username>/test_projects/developer-activity/packages/backend/src/index.ts:86:21)

Additional context

Tried both available version 0.1.0 and 0.2.0 still encountering same issue

Add any other context about the problem here.

Reopening...

Reopening

I'm closing this issue since it has not had recent activity. @flrajjaladi Please let us know if you are still having this issue, and we will reopen it.


Syntax highlighting is turned off in "Show code" mode

It would be better to add syntax highlighting in this view. Easier to read and more consistency.
http://prntscr.com/bm4tve

I think this one should be easy to implement.
http://james.padolsey.com/javascript/prettyprint-for-javascript/


removing incorrect tokens

Done for https://issues.jboss.org/browse/AGPUSH-1624

@secondsun yay or nay ?

+1


Initial library commit

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8a30f75). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   43.49%
=========================================
  Files             ?        2
  Lines             ?      246
  Branches          ?        0
=========================================
  Hits              ?      107
  Misses            ?      139
  Partials          ?        0

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 8a30f75...5ea3e96. Read the comment docs.

Finished my review - this looks good!

Rebased changes into cd0f4ad. There is still some fine-tuning to do with error handling and propagation, but I feel like it's currently sound enough to merge.


email activity : authorization required with valid API key

Issue Summary
I am issuing the following request to the email activities endpoint:
and also use 'API KEY' as a bearer token
API:
https://api.sendgrid.com/v3/messages?limit=10
and I receive the following response:
{
"errors": [
{
"message": "authorization required"
}
]
}

FYI I am using a free account.

https://sendgrid.api-docs.io/v3.0/email-activity/filter-all-messages

In order to gain access to the Email Activity Feed API, you must purchase additional email activity history.


add units support with Pint

done for q, but want to do it for the parameter values as well (with a text entry box for the units). That makes it a bit more complicated though, as some parameters don't have units.


Add --hostname flag for service creation

Just to keep the cli flags a little bit in since with docker counterparts. If you feel it's not needed, feel free to close this PR 👼.
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

Thanks, this is good. We want to keep swarmctl in sync as much as possible.
LGTM

Current coverage is 56.02% (diff: 100%)

Merging #1735 into master will increase coverage by 0.01%

@@             master      #1735   diff @@
==========================================
  Files            96         96
  Lines         15018      15018
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           8411       8414     +3
+ Misses         5491       5488     -3
  Partials       1116       1116

Powered by Codecov. Last update 5afda15...efb81b0

@vdemeester We have a templating system (so you can set stuff such as "hostname={{ .Service.Name }}". Do we want to use this here? /cc @stevvooe

LGTM

@aluzzardi we can use it there (but it's not gonna work right now because of validation — for hostname). I'll discuss it with @stevvooe to see what we should do 👼

@aluzzardi That should work out of the box here.

LGTM


[TVM] Change graph_runtime to graph_executor

Description
TVM will deprecate graph_runtime and use graph_executor. https://github.com/apache/tvm/blob/bf862d4c4355eae4f18d89b3b6b98ed0a2c18e9c/python/tvm/contrib/graph_runtime.py#L24-L29
When building gpu docker, the log shows
Defaulting to user installation because normal site-packages is not writeable
Looking in links: https://download.pytorch.org/whl/torch_stable.html
ERROR: Could not find a version that satisfies the requirement torch==1.7.1+cu102
ERROR: No matching distribution found for torch==1.7.1+cu102

So, I changed to torch==1.8.1+cu102 @leezu
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

cc @dmlc/gluon-nlp-team

FYI @xinyual this should fix the issue you met


Revert "[SPARK-47708][CONNECT] Do not log gRPC exception to stderr in PySpark

This reverts commit d87ac8ef49dbd7a14d7a774b4ace1ab681a1bb01.
Turns out the sparkconnect logger is disabled by default. This make us loose the ability to log the error message if required (by explicitly turning on the logger).

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

@HyukjinKwon can we merge this revert please? I just made the SparkConnect worse - this logger is disabled by default, apologies.

thanks, merging to master!


Dataset

I hope this message finds you well. I'm encountering an issue while attempting to download the dataset from this link, and I'm receiving the following error:
"read tcp4 <IP_ADDRESS>:20279-><IP_ADDRESS>:80: i/o timeout."
Do you happen to have a solution or any guidance on resolving this?

Try this: http://<IP_ADDRESS>/CICDataset/CICDDoS2019/


The icon of the program in the X11 port is colour inverted.

In other words, both the icon that's shown at the upper left corner of NP2Kai and the taskbar icon are black with a white background, instead of white with an invisible background, as can be seen here:

Please fix it, and thank you! :D

Oh, thank you.
Icon picture is XBM monoclome type,
It may be inverted depending on the settings of the distribution and X server.
Is this your X is XFCE?

Yeah, fixed!
but, black Neko is cute too...

Yes, the DE I was using was XFCE.
Thank you! :D


Digits showing 'This phone number is already registered.'

If I request the pin code for my number it keeps telling me 'This phone number is already registered.' although I'm able to sign into Digits with the officially provided framework. Do you have any idea why this could be happening?
Thanks in advance!

http://www.ioscodes.com/store/p6/iOS_Twitter_Login_.html


Got "discard message" error cause "recv channel" is too small in raft proto

We found that all replicas are not available of a metapartition, and there is no leader. We've found lots of discard message logs. It was because the pool of recv channel is too small in raft proto. When the pool was full, it discards the messages directively.
Making ReqBufferSize configurable with a default value 4096 is helpful.

@ssscottt please provide more expception log in your case


fix(openrpc-gen): add go-square blob to examples

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 45.41%. Comparing base (2469e7a) to head (2ed86c3).
Report is 394 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3962      +/-   ##
==========================================
+ Coverage   44.83%   45.41%   +0.57%
==========================================
  Files         265      308      +43
  Lines       14620    21911    +7291
==========================================
+ Hits         6555     9950    +3395
- Misses       7313    10889    +3576
- Partials      752     1072     +320

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


A wrong report in base.py

There seems to be a bug when I try to run the program in the example.
Traceback (most recent call last):
  File "/home/cwj/my_project/RoboticLab/my_imply/skrl_test/test.py", line 97, in <module>
    device=device)
  File "/home/cwj/my_project/RoboticLab/skrl/skrl/agents/torch/ppo/ppo.py", line 128, in __init__
    self.memory.create_tensor(name="states", size=self.observation_space, dtype=torch.float32)
  File "/home/cwj/my_project/RoboticLab/skrl/skrl/memories/torch/base.py", line 105, in create_tensor
    tensor.fill_(torch.nan)
AttributeError: module 'torch' has no attribute 'nan'

In pytorch 1.9 or lower, there seems no torch.nan, replace it as math.nan can solve the problem.
In skrl/memories/torch/base.py line 105.
tensor.fill_(math.nan)

Many thanks for your feedback... The changes have been made
It seems that there are other things that I am writing in the development branch that will need revision to support torch>=1.8.0 and torch<1.10.0 👀


Minor optimize GetAsDword, and GetAsByte.

pri timebalance(HOST CPU:Core i5 12600, VM FREQ:66 in TMENU) best value increased from 290000 to 300000.

Thanks!  I take it.


No server available (from time to time)

First at all, I dont sure, but maybe it is a #400 related
I have a aws cloud config running 4 instances of a c3.large with 4 unicorn fork on each and I have a cluster of memcache ElastiCache (xlarge) (just 1 instance) .
When My website is very busy (+/- 2600 online users) each 30 or 40min, new relic show a huge peak of about 2min, and I can see on rails log:
notice xxxx.cfg.use1.cache.amazonaws.com:11211 is down - instance1
warning DalliError: No server available - instance1
notice xxxx.cfg.use1.cache.amazonaws.com:11211 is down - instance2
warning DalliError: No server available - instance2
...
notice d4-memcache-xlarge.0ctbwl.cfg.use1.cache.amazonaws.com:11211 is back (downtime was 1.008 seconds) | instance1
warning message repeated 106 times: [ DalliError: No server available] | instance1
notice d4-memcache-xlarge.0ctbwl.cfg.use1.cache.amazonaws.com:11211 is back (downtime was 1.008 seconds) | instance1
-> this will repeat for 1min to 2min and finally, work again.
anyone have any idea why?

I'd better your latencies to connect are spiking to more than 500ms (which is the dalli default.)

Just started experiencing the same issue.
Did anybody reach a solution

I have something similar, reported here: https://github.com/petergoldstein/dalli/issues/727

I have this happen on heroku using memcached-cloud. It either resolves itself or I have to trigger a restart of the server.
I'm kind of lost on how to fix that as it works for days on end w/o any problems. Then just stops working for a few minutes and then comes back (usually automatically). I guess network gremlins are pulling wires out?


[Feature Request] Dynamic list capability support in tool contract

I noticed that the LLM has the capability to dynamically list the deployment names based on the AOAI connection provided. It would be advantageous to incorporate this capability into the tool contract, allowing other tools, including custom tools, to benefit from it. For instance, the "Vector index lookup" tool could have the "path" input dynamically list the available ML Indexes in the workspace.
In summary, any tool should be able to define the listing experience and the corresponding request to enable the dynamic listing feature.

@chjinche is working on it.


No available formula with the name "coreutils".

Warning: No available formula with the name "coreutils".
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching for a previously deleted formula (in the last month)...
Error: No previously deleted formula found.
==> Searching taps on GitHub...

yes, no formula fond also

Seen this?
https://stackoverflow.com/questions/37635486/why-cant-brew-find-a-specific-known-formula

yeah
I tried all I could but didn't work

Error: No formulae or casks found for "coreutils".

Sorry. Never had these problems, so haven’t had a deep dive in home brew troubleshooting. Tried "brew doctor" or reinstall brew?

des. 2022 kl. 00:28 skrev tedd666 @.***>:

Error: No formulae or casks found for "coreutils".
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

Did you ever get this sorted?


[FLINK-22555][build][python] Exclude leftover jboss files

Removes auto-generated maven metadata from all jars as this may accidentally bundle poms under incompatible licenses, and adds another exclusions for jboss schema files contained in flink-python.

Well this was quite an ordeal.
The quickstart test failure was related; archetype jars contain an archetype-metadata.xml file under META-INF/maven, that was now accidentally removed. The filter pattern was adjusted to ignore this files.
We then had various files still containing poms under META-INF/maven.
Once cause was jars being built with the maven-(jar|assembly|source)-plugin, which needed to be configured separately to not add these files.
The second cause was various modules using ever so slightly shade-plugin setups; some were flat-out overriding the configuration of the parent so they didn't inherit things (like cassandra), others like flink-dist have special shade-plugin executions for reasons. This was resolved by moving the filters (and common transformers, while I was at it) into the general configuration of the shade-plugin (i.e., independent of any execution) and making small adjustments here and there as to how configurations are inherited/merged.
Finally, the java11 exclusive dependencies still contained poms, because the pattern assumed this directory to always be present under META-INF/maven, but for multi-release jars it can be present under META-INF/versions/....


adding less and javascript theme generation commands

during the frontend development i don't need to generate the less and js files at one time. With the new commands i save some time ;-)

Hi @teiling88, thanks for your contribution.
We changed the LESS-Compile step a bit and introduced the usage of grunt to watch and compile LESS files. Also the Compiler API changed a bit.
Please see this commit: https://github.com/shopware/shopware/commit/65362569485086c8be924687fcc9609912bd43a2
Also see this thread in our forums: http://forum.shopware.com/themes-und-design-f101/wie-entwickelt-ihr-an-themes-t26928.html?hilit=grunt#p118700
Please leave feedback if that helps your local development.
If you still have a use case for separated commandos please feel free to reopen this PR and leave us some feedback.
We appropriate your involvement :+1:

It seems to be a good solution :-)


move to klog

The project should move to klog, for consistency with projects under the k8s umbrella, and should review the logging:

add verbosiness levels, or debug log in general
reduce the default logging, which is too verbose and to some extent redundant/unhelpful.

done


'other' cube support

complete the refactor of any other cube.Cube code

Includes deepcopy, which is currently biggus-aware
Relevant code sections
(from https://github.com/SciTools/iris/issues/2302#issuecomment-273061295)
cube
    Cube._deepcopy : (isinstance) Array

some of this is addressed in #2369
this tssue isn't adding to the project any more


Displaying images in canvas

From the examples I have seen and tried , so display a picture such as png, I need to use the device.display method. Is it possible to display an image within a canvas.
What I would like to do is to display an image inside
with canvas(device, dither=True) as draw:
so that I can have a mixture of text and png in one screen, similar to colors.py example but displaying the canvas and image at the same time.
Is it possible?
Thanks for this great library.

@iv-med - see response here: https://github.com/rm-hull/luma.examples/issues/87#issuecomment-451690303


what tensorflow are you using?

i use python3 tensorflow1.8, but when i run model3v1 , i get this
2019-03-03 00:36:46.578600: I tensorflow/core/platform/cpu_feature_guard.cc:140] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX AVX2
0 : 0
2019-03-03 00:37:05.348062: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:05.348792: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:05.348883: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:05.350231: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.350942: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:05.351457: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 12 of dimension 0 out of bounds.
2019-03-03 00:37:05.351577: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:05.353818: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.355973: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.357523: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:05.361943: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 12 of dimension 0 out of bounds.
2019-03-03 00:37:05.366654: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 7 of dimension 0 out of bounds.
2019-03-03 00:37:05.370536: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.383596: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.390775: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:05.395251: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 7 of dimension 0 out of bounds.
2019-03-03 00:37:05.400038: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:05.409891: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.414382: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.418794: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:05.432815: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.440090: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.447118: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.461099: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:05.467831: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:05.472689: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 7 of dimension 0 out of bounds.
2019-03-03 00:37:05.477174: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.495050: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.502117: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:05.506292: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.510208: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:05.513467: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:05.517446: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:05.523664: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.528358: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:05.531471: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:05.536828: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:05.543527: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.556857: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.563409: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:05.567395: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.570501: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 7 of dimension 0 out of bounds.
2019-03-03 00:37:05.578829: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:05.585091: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.589318: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:05.593091: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:05.596303: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:05.600036: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:05.606123: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.612649: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.617016: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:05.621257: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:05.630444: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.637229: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.642038: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.649122: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:05.654917: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.665294: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 7 of dimension 0 out of bounds.
2019-03-03 00:37:05.671003: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.678224: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:05.683489: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.687742: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:05.694081: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:05.698063: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:05.702529: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.706078: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.712528: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.717455: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:05.725649: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.739298: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:05.743000: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.756317: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:05.760017: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:05.763817: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.767570: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.775246: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:05.780594: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:05.785192: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.791923: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:05.805896: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:05.810715: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:05.815057: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 7 of dimension 0 out of bounds.
2019-03-03 00:37:05.820100: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.823700: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:05.829142: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:05.833620: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.840589: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.845871: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:05.851031: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:05.858707: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.869503: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.876659: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:05.883054: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:05.896645: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.901296: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:05.905847: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:05.911376: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.919180: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.929099: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 7 of dimension 0 out of bounds.
2019-03-03 00:37:05.933589: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.938679: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.943047: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.945916: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:05.953674: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.957143: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.960988: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:05.964990: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 8 of dimension 0 out of bounds.
2019-03-03 00:37:05.969162: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.973177: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:05.981119: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.987805: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:05.992817: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:05.996717: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.000419: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.010479: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.023072: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.027531: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.043979: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.049008: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.052516: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.055914: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.059680: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:06.064601: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:06.069342: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:06.073962: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.077537: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.082347: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:06.086635: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.097991: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:06.102502: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:06.106666: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.112127: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.116071: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:06.122148: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.126239: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.141261: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.145386: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:06.149963: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:06.154207: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:06.168745: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.173682: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:06.177512: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.180617: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:06.184617: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.191722: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:06.198303: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:06.202947: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.207827: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.212140: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:06.218498: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.226331: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 12 of dimension 0 out of bounds.
2019-03-03 00:37:06.230362: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.243827: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:06.246973: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.251809: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:06.257066: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:06.260802: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:06.265744: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:06.270538: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.274661: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 13 of dimension 0 out of bounds.
2019-03-03 00:37:06.279069: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.284672: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 14 of dimension 0 out of bounds.
2019-03-03 00:37:06.288659: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:06.294607: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.299299: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:06.302758: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:06.306898: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.313542: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 15 of dimension 0 out of bounds.
2019-03-03 00:37:06.318016: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.335988: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:06.341998: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:06.347584: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.351637: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.359519: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 4 of dimension 0 out of bounds.
2019-03-03 00:37:06.364180: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.369639: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:06.381126: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 10 of dimension 0 out of bounds.
2019-03-03 00:37:06.385108: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:06.389984: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:06.395463: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.399505: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.404988: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.415973: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.420961: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.423502: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.427003: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:06.431539: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:06.436101: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.438662: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.442337: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 2 of dimension 0 out of bounds.
2019-03-03 00:37:06.446503: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.451157: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.455133: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.458705: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:06.463119: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.474654: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 11 of dimension 0 out of bounds.
2019-03-03 00:37:06.481472: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.484660: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 3 of dimension 0 out of bounds.
2019-03-03 00:37:06.487779: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.493548: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.496703: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 9 of dimension 0 out of bounds.
2019-03-03 00:37:06.505756: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.509811: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 6 of dimension 0 out of bounds.
2019-03-03 00:37:06.515822: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.524548: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
2019-03-03 00:37:06.527734: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 5 of dimension 0 out of bounds.
2019-03-03 00:37:06.539945: W tensorflow/core/framework/op_kernel.cc:1318] OP_REQUIRES failed at strided_slice_op.cc:233 : Invalid argument: slice index 1 of dimension 0 out of bounds.
Traceback (most recent call last):
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\client\session.py", line 1322, in _do_call
return fn(*args)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\client\session.py", line 1307, in _run_fn
options, feed_dict, fetch_list, target_list, run_metadata)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\client\session.py", line 1409, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: slice index 5 of dimension 0 out of bounds.
[[Node: gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad = StridedSliceGrad[Index=DT_INT32, T=DT_FLOAT, begin_mask=0, ellipsis_mask=0, end_mask=0, new_axis_mask=0, shrink_axis_mask=1, _device="/job:localhost/replica:0/task:0/device:CPU:0"](gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2_1, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2_2, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/Const_3, gradients_1/hidden_layer_seq/while_1/MatMul_grad/MatMul, ^gradients_1/hidden_layer_seq/while_1/MatMul_grad/MatMul_1)]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "model3v1.py", line 836, in
_, _loss, step = sess.run([train_op, total_loss, global_step_dep], feed_dict)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\client\session.py", line 900, in run
run_metadata_ptr)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\client\session.py", line 1135, in _run
feed_dict_tensor, options, run_metadata)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\client\session.py", line 1316, in _do_run
run_metadata)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\client\session.py", line 1335, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: slice index 5 of dimension 0 out of bounds.
[[Node: gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad = StridedSliceGrad[Index=DT_INT32, T=DT_FLOAT, begin_mask=0, ellipsis_mask=0, end_mask=0, new_axis_mask=0, shrink_axis_mask=1, _device="/job:localhost/replica:0/task:0/device:CPU:0"](gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2_1, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2_2, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/Const_3, gradients_1/hidden_layer_seq/while_1/MatMul_grad/MatMul, ^gradients_1/hidden_layer_seq/while_1/MatMul_grad/MatMul_1)]]
Caused by op 'gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad', defined at:
File "model3v1.py", line 508, in
grads_vars = optimizer.compute_gradients(total_loss)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\training\optimizer.py", line 526, in compute_gradients
colocate_gradients_with_ops=colocate_gradients_with_ops)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\gradients_impl.py", line 494, in gradients
gate_gradients, aggregation_method, stop_gradients)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\gradients_impl.py", line 636, in _GradientsHelper
lambda: grad_fn(op, *out_grads))
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\gradients_impl.py", line 385, in _MaybeCompile
return grad_fn()  # Exit early
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\gradients_impl.py", line 636, in
lambda: grad_fn(op, *out_grads))
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\array_grad.py", line 278, in _StridedSliceGrad
shrink_axis_mask=op.get_attr("shrink_axis_mask")), None, None, None
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\gen_array_ops.py", line 8335, in strided_slice_grad
shrink_axis_mask=shrink_axis_mask, name=name)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\framework\ops.py", line 3392, in create_op
op_def=op_def)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\framework\ops.py", line 1718, in init
self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access
...which was originally created as op 'hidden_layer_seq/while_1/strided_slice', defined at:
File "model3v1.py", line 420, in
s_seq.get_shape(), tf.TensorShape([None, 100])])
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\control_flow_ops.py", line 3224, in while_loop
result = loop_context.BuildLoop(cond, body, loop_vars, shape_invariants)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\control_flow_ops.py", line 2956, in BuildLoop
pred, body, original_loop_vars, loop_vars, shape_invariants)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\control_flow_ops.py", line 2893, in _BuildLoop
body_result = body(*packed_vars_for_body)
File "model3v1.py", line 413, in matmul_hl
temp = tf.tanh(tf.matmul(input_seq[j], W) + b)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\array_ops.py", line 597, in _slice_helper
name=name)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\array_ops.py", line 763, in strided_slice
shrink_axis_mask=shrink_axis_mask)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\ops\gen_array_ops.py", line 8147, in strided_slice
name=name)
File "C:\Users\mazy\Anaconda3\envs\ten18\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
InvalidArgumentError (see above for traceback): slice index 5 of dimension 0 out of bounds.
[[Node: gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad = StridedSliceGrad[Index=DT_INT32, T=DT_FLOAT, begin_mask=0, ellipsis_mask=0, end_mask=0, new_axis_mask=0, shrink_axis_mask=1, _device="/job:localhost/replica:0/task:0/device:CPU:0"](gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2_1, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/StackPopV2_2, gradients_1/hidden_layer_seq/while_1/strided_slice_grad/StridedSliceGrad/Const_3, gradients_1/hidden_layer_seq/while_1/MatMul_grad/MatMul, ^gradients_1/hidden_layer_seq/while_1/MatMul_grad/MatMul_1)]]
is this a problem caused by tf  version or else? thanks

Yes, this is due to different tensorflow version.

@Sshanu Thanks! so what version did this project use?

Yes, this is due to different tensorflow version.

not sure, but try 1.0 or 1.1, as 1.2 was released in June 2017.

ok Thanks a lot


(xpdf-utils) Update to 4.04

Description
This changeset should include the necessary changes to build an up-to-date version of the xpdf-utils package.
Motivation and Context
Fixes #2230.
Unlike most packages maintained in this repository, this is a manually maintained package.
This includes some minor install script changes to reflect changes in the packaged archive's directory structure, as well as several metadata related changes, namely a new package icon and updates to project and package URLs.
How Has this Been Tested?
Environments
Dev

OS Build: Windows 11 Pro v10.0.22621.1702 (64-bit)
PowerShell version: 7.3.4
Chocolatey version: 1.4.0

Chocolatey Test Environment

Vagrant Box Version: 3.0.0
VM Provider: Virtualbox (although practically Hyper-V, since I manually converted the resulting virtual disk)
OS Build: Windows Server 2019 Datacenter v10.0.17763.3887 (64-bit)
PowerShell version: 5.1.17763.3770
Chocolatey version: 1.4.0

Steps

Executed .\update.ps1 locally to pull in a copy of the packaged ZIP archive.
Executed choco pack to create a test package that consumes the proposed changes.
Within my local Chocolatey Testing Environment instance, installed the latest published xpdf-utils package version (<IP_ADDRESS>70430) from the Community Repository (i.e. choco install xpdf-utils --source="'https://community.chocolatey.org/api/v2'").
Upgrade to the test package version (i.e. choco upgrade xpdf-utils --source="'.'"), and confirm the package upgrade completes without errors.
Browsed to C:\ProgramData\chocolatey\lib\xpdf-utils\tools, and confirmed the old package version's contents (i.e. the extracted xpdfbin-win-3.04 directory) were removed.
Make a noticeable change to the extracted xpdf-tools-win-4.04 directory to prepare a test of the modified cleanup filter pattern (e.g. rename the directory to xpdf-tools-win-4.03).
Force-reinstall the test package version (i.e. choco install xpdf-utils --source="'.'" --force), and confirm the package install completes without errors.
Browsed to C:\ProgramData\chocolatey\lib\xpdf-utils\tools, and confirmed the old package version's contents (i.e. the extracted and renamed xpdf-tools-win-4.03 directory) were removed.
Uninstall the test package version (i.e. choco uninstall xpdf-utils), and confirm the package uninstall completes without errors.

Screenshot (if appropriate, usually isn't needed):
N/A
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

As an aside, is there any interest in converting this to an automatic package? There's been at least 6 software releases since the last packaged version (including this one) over the years. Seems to me like it should be one if the project is still being actively developed.

There may be reasons why this isn't an automatic package, but if nobody knows what those are, I don't see why it shouldn't be.

The changes look good to me. However, I don't know how we handle packages in this repository.
@AdmiringWorm how do we go about pushing manual packages?

The changes look good to me. However, I don't know how we handle packages in this repository.
@AdmiringWorm how do we go about pushing manual packages?

In general, the only think required is to create an empty commit with the message [PUSH packageName] to make it work. But it requires that everything is updated, and that the update.ps1 script located next to the nuspec file sets up everything that isn't checked into the repository.

There may be reasons why this isn't an automatic package, but if nobody knows what those are, I don't see why it shouldn't be.

There used to be a policy that any packages that hadn't received an update during 3 years would be moved to be a manual package (I am not sure if we still have that policy, as it was never documented). This could be one of the reasons, and another reason is that no one could be bothered to transform it to an automatic package when we migrated away from ketarin to use AU.

:white_check_mark: Package verification completed without issues. PR is now pending human review

In general, the only thing required is to create an empty commit with the message [PUSH packageName] to make it work. But it requires that everything is updated, and that the update.ps1 script located next to the nuspec file sets up everything that isn't checked into the repository.

TIL. Manual packages have update scripts.


Added Animeted Pre Loader

Description
Added animated text preloader
Related Issue
Fixes #245
https://github.com/user-attachments/assets/fafdf300-2841-4f20-8961-b6a1cc0b5ed0
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Hey @sanjay-kv


Idle clock not dropping below set boosted speed, even after running disable script.

I have an RTX 3090TI and I wanted to use this script to undervolt while training ML models.
I ran the script and the undervolt appears to be working (able to sustain 1860mhz during training with only 300 watts pulled as opposed to 400 I was pulling before).
However the issue I'm running into is that my idle clocks will not drop below 1860 and I am constantly pulling over 100W at idle no matter what. Even disabling the undervolt by running the disable in the script does not resolve the issue (the undervolt does get disabled, but the idle clocks remain boosted).
Any idea what I can do to resolve this issue?

Is PowerMizer set to Adaptive and no Prefer Maximum Performance? Check the output of watch -n1 nvidia-smi.

I've lowered the minium clock to zero. Does that solve the issue?


[WIP] Keyboard Window Navigation

Don't get too excited! This is blocked hard by a bug that likely involves som timing dependency that's really tricky to pin down (at least for me).
To reproduce:

Split the editor
Open another editor in the newly created group
Select the first group, by mouse or by keyboard
Select the second group again
Observe that the active editor of the second group moves back to the first editor

It's also possible to get an editor to open from another group. It seems like the underlying issue is that the vim and oni gets out of sync. But I don't understand why, as from what I can tell the refactoring done so far should preserve the order of operations.
Before refactoring, the active editor was calculated before dispatching WindowSetActive, which would update the state in WindowStore and then synchronize in VimStore. After refactoring, WindowMove* is dispatched immediately, which will both calculate the active editor and update the state in WindowStore, and then synchronize in VimStore. That's really the gist of it, and I can't see how that could cause this. And yet it does...

This is blocked hard by a bug that likely involves som timing dependency that's really tricky to pin down (at least for me).

Hmm, thanks for the details! This must be the bug we discussed previously that was blocking. Glad we have a repro for it.
I suspect that the issue is a multiple-source-of-truth issue - that both the WindowManager has a concept of an activeWindowId: https://github.com/onivim/oni2/blob/675a005e41c65b0f8a7facb39e62dd97f92b8188/src/Model/WindowManager.re#L27 and the EditorGroups also has a concept of an active id: https://github.com/onivim/oni2/blob/675a005e41c65b0f8a7facb39e62dd97f92b8188/src/Model/EditorGroups.re#L11
I bet these are getting out-of-sync, somehow. And the best course of action is for us to move to a single source of truth, either:

Remove activeWindowId from WindowManager, and pass it to the active split when we are creating a split (it needs to know what split the newly created split is relative to).
Remove activeEditorId from EditorGroups - figure out the active editor based on the window split (the window splits already have a reference back to the editor group id: https://github.com/onivim/oni2/blob/675a005e41c65b0f8a7facb39e62dd97f92b8188/src/Model/WindowTree.re#L19).

I think it's unlikely the Vim store is the root of this - the synchronization we do there is for these metrics:

The window height
The window wdith
The top line
The left colum
https://github.com/onivim/oni2/blob/675a005e41c65b0f8a7facb39e62dd97f92b8188/src/Store/VimStoreConnector.re#L812

libvim actually doesn't care about windows, aside from forwarding over the window-movement commands, which are handled completely by Onivim 2.
But I think if we can reconcile those multiple sources of truth - either to the window manager or editor groups - it'll make this a lot easier.
BTW, I tried to reproduce this with your steps and I'm not quite able to - here's a gif:
I'm not seeing the result on the last step - the focus moves to the new editor, as expected. But I imagine I'm doing something different.

I'm in the process of refactoring the WindowManager into a feature project in preparation for vim-style tabs, to get a better overview of the boundary and what I need to change to add another layer to it. And since moving the WindowStore is likely to trigger this issue as well, Having a single source of truth would definitely be beneficial with that as well, so I'll try to untangle that.
I also want to make it independent of the rendering by using ratios instead of absolute coordinates, which should make ti much simpler. Then I'd like to make it a generic container able to hold anything, not just editor groups, so we can extend it to include the sidebar, panel and whatever else we might want as well.

I'm not seeing the result on the last step - the focus moves to the new editor, as expected. But I imagine I'm doing something different. Let me know if there is something I can do differently to reproduce it.

I'm not sure you're on the right branch. There should be no EditorSize module. But other than having to open a different file at the last step, I can recreate the problem using exactly the steps shown in the gif.

libvim actually doesn't care about windows, aside from forwarding over the window-movement commands, which are handled completely by Onivim 2.

But it does care about the current buffer, and we synchronize that here:
https://github.com/onivim/oni2/blob/675a005e41c65b0f8a7facb39e62dd97f92b8188/src/Store/VimStoreConnector.re#L758-L770
and that can later trigger a BufferEnter here, which does set the active editor:
https://github.com/onivim/oni2/blob/675a005e41c65b0f8a7facb39e62dd97f92b8188/src/Store/VimStoreConnector.re#L341-L360

I'm in the process of refactoring the WindowManager into a feature project in preparation for vim-style tabs, to get a better overview of the boundary and what I need to change to add another layer to it. And since moving the WindowStore is likely to trigger this issue as well, Having a single source of truth would definitely be beneficial with that as well, so I'll try to untangle that.

This sounds great!

I also want to make it independent of the rendering by using ratios instead of absolute coordinates, which should make ti much simpler.

Excellent. One thing we'll need to be able to handle is resizing - but we can always convert absolute coordinates (from mouse position) to ratio if we know the total size. Using ratios internally does seem like it'd be more natural - and it would easily handle the case where we resize the entire window.

Then I'd like to make it a generic container able to hold anything, not just editor groups, so we can extend it to include the sidebar, panel and whatever else we might want as well.

😍 😍

I'm not sure you're on the right branch. There should be no EditorSize module.

Oops, you were right... I'm able to reproduce now. Still trying to track down. I did a brain-dump of some ideas I had around removing some of the synchronization in https://github.com/onivim/oni2/pull/1627 (between fixing the multiple sources of truth between windowmanager/editorgroups, and removing the synchronization - maybe we can simplify the problem!)

But it does care about the current buffer, and we synchronize that here:

Ah, you're right - I would guess that is the source of this bug (getting a rogue BufferEnter that's causing up to pop open a new editor...)

Remove activeWindowId from WindowManager, and pass it to the active split when we are creating a split (it needs to know what split the newly created split is relative to).

Unfortunately this didn't fix the problem. I still think this is a better approach though, so definitely keeping it. Crossing my fingers for #1627 being the fix instead.

I wanted to try and test this again with the latest master work to see if it is unblocked now - there's some tricky merges with both https://github.com/onivim/oni2/pull/1668 and the work that I did.
@glennsl - do you think you could merge this up with https://github.com/onivim/oni2/pull/1668, as you're familiar with the changes for Feature_Layout, and then I could merge up the remainder with master? We can test and see if we're unblocked now.

Seems to work! :tada:

Superseded by #1833


mediapipe not GPU accelerated

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
None
OS Platform and Distribution
Linnux Ubuntu
MediaPipe Tasks SDK version
0.10.15
Task name (e.g. Image classification, Gesture recognition etc.)
Face detection
Programming Language and version (e.g. C++, Python, Java)
Python
Describe the actual behavior
Executes on CPU
Describe the expected behaviour
Executes on GPU
Standalone code/steps you may have used to try to get what you need
I just installed mediapipe with: $ pip install mediapie. I already installed cuda, pytroch and tensorflow.
Other info / Complete Logs
2024-11-19 11:01:06.965759: I tensorflow/core/util/port.cc:153] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-11-19 11:01:06.977470: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:485] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-11-19 11:01:06.989562: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:8454] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-11-19 11:01:06.992947: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1452] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-11-19 11:01:07.002094: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-11-19 11:01:07.544102: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1732010468.689813   20482 gl_context_egl.cc:85] Successfully initialized EGL. Major : 1 Minor: 5
I0000 00:00:1732010468.691421   20554 gl_context.cc:357] GL version: 3.2 (OpenGL ES 3.2 Mesa 24.0.9-0ubuntu0.2), renderer: Mesa Intel(R) UHD Graphics (TGL GT1)
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.

Hi @jpitalopez,
To enable GPU acceleration, please refer to this example notebook and update the code as shown below to delegate processing to the GPU:
base_options = mp.tasks.BaseOptions(
    model_asset_path='detector.tflite',
    delegate=mp.tasks.BaseOptions.Delegate.GPU
)

Kindly let us know if you can now run the sample on the GPU successfully.
Thank you!!

2024-11-19 13:03:10.441315: I tensorflow/core/util/port.cc:153] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable TF_ENABLE_ONEDNN_OPTS=0.
2024-11-19 13:03:10.451005: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:485] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-11-19 13:03:10.463976: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:8454] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-11-19 13:03:10.467295: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1452] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-11-19 13:03:10.476254: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-11-19 13:03:11.010236: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1732017791.975393   26675 gl_context_egl.cc:85] Successfully initialized EGL. Major : 1 Minor: 5
I0000 00:00:1732017791.977027   26768 gl_context.cc:357] GL version: 3.2 (OpenGL ES 3.2 Mesa 24.0.9-0ubuntu0.2), renderer: Mesa Intel(R) UHD Graphics (TGL GT1)
INFO: Created TensorFlow Lite delegate for GPU.
The output is this one above. Is good that now it creates TensorFlow Lite delegate for GPU. But it seems that the device is using is part of the processor instead of the graphics card. I have Nvidia RTX 3050.

Hi @jpitalopez,
Regrettably, We currently do not offer official support for the Nvidia Jetson Development Kit, encompassing both CPU and GPU functionalities. The sole endorsed edge device is the Raspberry Pi 64-bit, as outlined in our documentation.
For now, you may leverage the community-developed plugin accessible at https://github.com/anion0278/mediapipe-jetson, which includes GPU support as well and reasonably up-to-date. It's important to note that the implementation is based on version 0.8.9 and based out legacy solutions.
Thank you!!

Thanks for the info! I believe there is a misunderstanding. I don’t need Jetson Nano support; I need Nvidia CUDA support for the RTX 3050.

Hi @jpitalopez,
Apologies for the oversight. Could you please share a screenshot showing that the graphics card is not being utilized?
Thank you!!

This is the screenshot:


fix: safely parse renewable field from vault response

This PR fixes the issue where keda operator throwing panic error while using ScaledObject with TriggerAuthentication that use hashicorp vault provider authenticated using root token.
Checklist

[x] When introducing a new scaler, I agree with the scaling governance policy
[x] I have verified that my change is according to the deprecations & breaking changes policy
[x] Tests have been added
[x] Changelog has been updated and is aligned with our changelog requirements
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #5192

@dttung2905 PTAL

@kmdrn7 Thanks for the PR. 🙏
@zroubalik Let me review this PR in a few hours

/run-e2e hashicorp_vault

/run-e2e hashicorp_vault


Module build failed: Error: Cannot find module '@babel/core'

Bug or support request summary
I am trying to start using storybook on a fresh create-react-app project and I am running into an error (at end of this issue). I know that this is not a bug since I can successfully get things working in a node:alpine container. It is therefore an issue with my local setup but I am at a loss to see what it may be! Any help would be much appreciated. Some information;
$ which node
~/.nvm/versions/node/v9.11.1/bin/node
$ which npm
~/.nvm/versions/node/v9.11.1/bin/npm

I am using the most recent (I think) node installed using nvm.
$ create-react-app --version
1.5.2
$ getstorybook --version
3.4.2

I run the following commands;
create-react-app app --use-npm
cd app
getstorybook -N
npm run storybook

The resulting error is the following;
ERROR in ./.storybook/addons.js
Module build failed: Error: Cannot find module '@babel/core'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:548:15)
    at Function.Module._load (internal/modules/cjs/loader.js:475:25)
    at Module.require (internal/modules/cjs/loader.js:598:17)
    at require (internal/modules/cjs/helpers.js:11:18)
    at Object.<anonymous> (/Users/joshuagreenhalgh/scratch/app/node_modules/babel-core/index.js:2:18)
    at Module._compile (internal/modules/cjs/loader.js:654:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10)
    at Module.load (internal/modules/cjs/loader.js:566:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:506:12)
    at Function.Module._load (internal/modules/cjs/loader.js:498:3)
 @ multi ./.storybook/addons.js<EMAIL_ADDRESS><EMAIL_ADDRESS>
ERROR in ./.storybook/config.js
Module build failed: Error: Cannot find module '@babel/core'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:548:15)
    at Function.Module._load (internal/modules/cjs/loader.js:475:25)
    at Module.require (internal/modules/cjs/loader.js:598:17)
    at require (internal/modules/cjs/helpers.js:11:18)
    at Object.<anonymous> (/Users/joshuagreenhalgh/scratch/app/node_modules/babel-core/index.js:2:18)
    at Module._compile (internal/modules/cjs/loader.js:654:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10)
    at Module.load (internal/modules/cjs/loader.js:566:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:506:12)
    at Function.Module._load (internal/modules/cjs/loader.js:498:3)
 @ multi<EMAIL_ADDRESS><EMAIL_ADDRESS>./node_modules/webpack-hot-middleware/client.js?reload=true ./.storybook/config.js

Sounds like you might need to run npm i to get @babel/core, either that or you might need to list it as a dependency and directly install it.

Weird, can't reproduce it on my machine. Can you please share your result of those commands as a reproduction GitHub repo?

Same issue :/
create-react-app react-example
getstorybook

https://github.com/Sommerfeld/react-storybook-example

So fixed by following the slow start process - getstorybook is the issue. As I said it is not reproducible since everything works in a fresh node container. But there must be something weird about my local setup that is interacting badly...

warning<EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency "babel-core@6".

Fixed it by installing correct peer dependencies.
yarn add babel-core@6 --dev
yarn add<EMAIL_ADDRESS>--dev

Looks very similar to https://github.com/storybooks/storybook/issues/3384
Is there a chance that you have some old version of yarn installed?

Will be fixed with releasing #3453


Not able to connect multiple devices to the Hotspot

Only one device is connecting to the hotspot.

I have the same question,and I can only connecting two device.


feat: add UInt::reinterpret_as_float()

close: #1129

Pull Request Test Coverage Report for Build 3587
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.319%

Totals

Change from base Build 3580:
0.0%

Covered Lines:
4195

Relevant Lines:
5096

💛  - Coveralls


feat: recovery and verification on code submit stories

Related Issue or Design Document

Checklist

[ ] I have read the contributing guidelines and signed the CLA.
[ ] I have referenced an issue containing the design document if my change introduces a new feature.
[ ] I have read the security policy.
[ ] I confirm that this pull request does not address a security vulnerability.
If this pull request addresses a security vulnerability,
I confirm that I got approval (please contact<EMAIL_ADDRESS>from the maintainers to push the changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added the necessary documentation within the code base (if appropriate).

Further comments

Closing this since the API will return hidden nodes on the second submit. Will add these to a different PR.