saga logging breaks the app

Description of the bug/issue
Development logging cant handle all values
Steps to reproduce the bug/issue
Run the following saga
const mySaga = function * (): Saga<void> {
	const data = Object.create(null)
	yield call(console.log, data)
}

or just
String(Object.create(null))
which is actually beeing evaluated in https://github.com/redux-saga/redux-saga/blob/65034cc8b08ab5a6ff1e7441f3062960615f368d/packages/core/src/internal/io.js#L146
Actual results
The logging  that should help the developers breaks the app.
Before this issue I thought that you can put just anything into String() or Boolean(). But that is not true.
The Expected results
A working app should not break because of dev logs
Thoughts toward the solution

Fix our app, so that redux-saga works with normal objects. It is the first thing that I did. However, it really took me a while to see where the problem emerged after upgrading to redux-saga@1 - very frustrating. Additionally Object.create(null) was sent via action in a library, redux middleware, that we use, so I couldnt actually remove it, just create a workaround for it. The irony is that the app works fine in production but fails in development because of a log that is not actually being logged
create a helper function , e.g. tryString, with a try-catch clause that would be used to convert values to string.

Environment information

redux-saga version 1.0.1

Thanks for reporting. In my option, I think we may simply avoid stringifying args[0]. Replacing the code to instead of writing yield call(delay, ...) where delay from ... should fix the issue. How you think?

Thx. Without args[0], the warning still notifies how to (not) call delay effect. So it is totally fine by me.


beartype still complaining!?

on windows:
>>> import use
Home is C:\Users\micro\.justuse-python
G:\Python398\lib\site-packages\beartype\_util\hint\pep\utilpeptest.py:373: BeartypeDecorHintPep585DeprecationWarning: PEP 484 type hint typing.Callable[...,
typing.Any] deprecated by PEP 585 scheduled for removal in the first Python version released after October 5th, 2025. To resolve this, either drop Python < 3.9 support and globally replace this hint by the equivalent PEP 585 type hint (e.g., "typing.List[int]" by "list[int]") or see this discussion topic for saner and more portable solutions:
    https://github.com/beartype/beartype#pep-484-deprecations
  warn(
G:\Python398\lib\site-packages\beartype\_util\hint\pep\utilpeptest.py:373: BeartypeDecorHintPep585DeprecationWarning: PEP 484 type hint typing.Callable deprecated by PEP 585 scheduled for removal in the first Python version released after October 5th, 2025. To resolve this, either drop Python < 3.9 support and globally replace this hint by the equivalent PEP 585 type hint (e.g., "typing.List[int]" by "list[int]") or see this discussion topic for saner and more portable solutions:
    https://github.com/beartype/beartype#pep-484-deprecations
  warn(

Looks like accidentally applying beartype to beartype was the problem :D


feat: support using predefined controller extensions

When using a controller extension in your own controller as a kind of mix-in, UI5 currently expects in the "extend" config object the extension class to be assigned to a property.
In TypeScript, however, the TS compiler must see the property being typed with an instance of the extension class, so subsequent calls to the extension can be written like they should
(this.routing.doSomething()).
This change introduces the "@transformControllerExtension" comment and decorator which triggers a special kind of transformation for annotated class properties. The controller extension type assigned to the subsequent class property is then assigned as class in the extend object in JavaScript. And this assignment is not moved into the constructor like it normally would be.
Fixes https://github.com/SAP/ui5-typescript/issues/420

The high-level approach here is:

In real life UI5 build pipelines the TypeScript transpiler usually runs first and immediately in the Program.enter phase removes unneeded imports. As a controller extension usage like e.g. the class property declaration routing: Routing is just a type assignment, the import of Routing just imports a type and appears unneeded from TS perspective. Hence, now the pre() hook is used to get a list of all initially present imports.
In the regular class transformation, class properties which represent controller extensions are recognized by the @controllerExtension comment or decorator (and confirmed by looking at their structure) and converted to a value assignment (that is needed at runtime).
If the respective import has been removed (see above), it is re-added.
In the unit tests, however, TypeScript runs after this plugin. This means that the import would still look good, but be removed later. To prevent this, a binding reference to the newly added value assignment is created. This makes TypeScript notice that the import is still needed.

Any chance this gets released soon? https://www.npmjs.com/package/babel-plugin-transform-modules-ui5?activeTab=code


net shell: self-connecting to TCP might lead to a crash

Describe the bug
If a TCP socket is listening up, using net-shell's tcp connect command to it may lead to a crash
To Reproduce
Steps to reproduce the behavior:

west build -b qemu_x86_64 samples/net/sockets/echo_server
west build -t run
run this command: net tcp connect <IP_ADDRESS> 4242
See error (sometime, it takes a few seconds before happening)

Expected behavior
Crash should not happen
Additional context
Haven't tried on other target than qemu_x86_64, but it's likely to exist on others.

Found the root cause. Have a fix in preparation


A/B Experiment for CMake Status Bar Migration to the Side Panel

Brief Issue Summary
Hi there!
Our team is conducting an A/B experiment over the course of the next month for the CMake action items on the status bar by migrating them to the sidebar CMake extension, in attempt to collect data related to this clean-up of the UI. To access your CMake presets and build/debug actions if you are in the treatment, please navigate to the CMake Tools side bar.

We are collecting metrics on which option is better for user's workflows, while taking into account UI consideration. Please leave any feedback you have on the experience below and if you could change anything about the design!
To opt out if you are receiving this treatment and no longer want to while we are running the experiment, please go to Settings and uncheck "Cmake: Use Project Status View". If you want to opt-into this treatment and give it a try, please check that option in settings.
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response

I was opted into this test group today and found it incredibly confusing. I was questioning what could have possibly happened to my environment that my normal build options are not appearing on the status bar. I dug through to check my extensions to see if anything changed and did not notice anything. Having some information available to me within VSCode that I was forceably subjected to this test would have been kind (maybe leaving a comment in the status bar context menu or SOMETHING.

Now for direct feedback on the actual feature, I prefer the options to be present on the status bar and I would switch if that option was provided to me but it seems I am forced to use the old way (the recommended option in the top post is not available to me)

I prefer to have it on the status bar since it is easily accessible and doesn't require a context switch away from what I am working on. For example if I have a Find & Search window open looking for references I can switch a build option without having to switch to a different panel. This is similar to Visual Studio where the build/configuration options are always available at the top of the window. To me having it in a separate panel that can lose focus is a regression in usability. Additionally, I often will trigger a build visually by clicking the build button rather than using a shortcut or a command. Maybe I'm a caveman but this is my preferred workflow. Finally, I will often have multiple text editors open and the panels completely hidden, I find it annoying to have to open and reflow my current view just to make some setting changes for my build.
Finally, in my panic to find what went wrong I actually did open this new panel and while it looked familiar I just assumed it was a parallel feature that was always there. To me it wastes a lot of screen real estate compared to the status bar way. I think for users who are aggressive with shortcuts and commands this won't be as disruptive but for us cavemen who like to click and point the change is quite jarring.

Hi @rminderhoud , thank you so much for your feedback and so sorry for the confusion we caused! We will definitely consider this workflow and input in the final design.
In the meantime, to opt out, you can navigate to the bottom left Gear icon and select "Settings"

From there, you can search "UseProject" and under Cmake: Use Project Status View, you can uncheck the option to get your status bar icons back:

Hope this helps un-block your workflow in the meantime!

Hi!
First of all, thanks for a nice extension!
I've a similar to @rminderhoud experience. The UI change was very confusing.
Regarding the feature:
It seems that "Target" list in the status bar has got no direct equivalent in the new UI. For example, "install" target is disappeared, "all" target is not obvious to select, and some targets' names are changed in my case.
So it would be nice to add a target selector it the "Project status" part as is. Digging the tree in the "Project outline" is not always fun as well.

I also found the change very confusing and I questioned my sanity because I though I somehow broke my CMake projects.
In general I don't need all elements in the status bar so often that I need them there.
But I use the build target selection (& build button) pretty often and I guess this varies from usecase to usecase.
Maybe have it more fine granular and let users decide which of those elements are valuable enough for them to be in the status bar?

This sudden change makes me feel like the cmake extension has been compromised, and I will spend time searching for this issue. Personally, the new method is not intuitive for me, and when I use it, I also need to switch the buttons on the left sidebar. I still prefer to use it on the bottom status bar

noticed that my icons had vanished this morning and went through the process of reverting to the old behaviour.
As for the new UI design:
I feel it's significantly more steps to do something trivial, like changing the debug/launch target (click cmake tools sidebar -> scroll to debug/launch options in project status view -> hover the option -> click the edit button -> choose the target from the top bar) and now you don't have immediate view of the target (on the status bar) you're about to launch/debug via F5.
This is a massive regression honestly.
At the very least, the option to have both views working simultaneously should be given. I have no problem with the additional information being present in the cmake tools sidebar view, but removing the shortcuts from the bottom bar is a 100% no from me. I hope, at the very least, the option to keep the old behaviour remains.

Dear CMake tools team,
Good to see that the team is trying new things to improve the experience with the CMake tools for vscode. Like the people who have responded before me I was at first very confused and thought I had somehow broken my vscode installation.
For my feedback.
The new sidepane design does not work at all for my workflow. I use the tooling in the following way.

Select toolkit.
I switch often between toolkits to develop locally on unit tests, or crossplatform to test on embedded targets.
This is not affected as I use the ctrl+p command interface for this.
Configure.
Same as point 1.
Build application.
For this, I always use the controls in the status bar to quickly build the application, or whole project.
The new layout does not contribute for this, I have to first navigate to the correct pane on the left hand side. Arriving there, I still have no clue how to build the project which is what I want to do. I have resorted to using the terminal + manual commands again to do building.

This said, I feel that the quick actions in the status bar should be kept in some form as I think more people will use the tooling in this way.

Hi @DubbeleJ, in order to build there should be a button that appears to the side of the build item in the side bar when you hover over it. If you don't see that option, could you create an issue and post a screenshot of how the Project Status View (in the side bar) appears for you? Thanks!

Besides the initial "what's going on here" shock, I have three observations:
1- There is no longer an UI way to select the CMake target to be built. You can still Ctrl+Shift+P for it, as you can for everything else, but... looks like an oversight looking for a quick fix.
2- The statusbar Advanced and Visibility settings say "Only applies when Cmake: Use Project Status View is set to false". I think that is a mistake (along with perfectly valid CMake command-line settings being purposefully ignored when using presets... hint, hint!) Even is the CMake side panel has all the options, it's be great if we could choose our own "frequent use" ones to remain visible and operable in the statusbar.
3- The UI as it is is awkward to use. Need to click the tiny "edit" icon in order to select a preset, instead of it being offered right there in the tree view. Or at least give me a sizeable button like we had in the status bar. The use of a tree view here feels... clumsy. Feels placeholder. I hope it is.
Suggestion: I love having a CMake-centric side panel. So put more good stuff in it! Not just what was on the limited-space statusbar: Buttons to delete cache, configure and build. A button to access CMake settings (like other extensions have). A button to provide feedback (a link to here). Stuff like that.
I hope this can evolve into something that delights. Definitely not there.
I also hope you can somehow make A/B experiments like this more discoverable (like a button in the status bar that reads "cmake stuff has moved", which opens the side panel when clicked) and perhaps more easily opt-outable, for instance a notification dialog saying something like "You've been selected to make CMake tools better... Ok? [Yes] [No]".
Not sure if it's related or not, but... there's also a project outline there that's... weird and awkward to use. Weird because it shows a long list of "utility" targets (named "Continuous", "Nightly"...) and I don't know what they are, and how they got there. Awkward because it shows the same directory tree of the workspace (filtered to directories that have targets in them), so it's... hard to find targets in there to operate on (at least in our project(s)). Anyway, this might be off-topic but... I thought I'd share.

I wasted hours trying to figure out why the buttons disappeared as compared to my other system.  Please don't make these kinds of changes without some sort of notification.... holy ... !!!!


Trying to switch to invalid engine version causes docker to stop working

RancherOS Version: (ros os version)
v0.7.1
docker-1.12.3
Steps to reproduce:

Switch docker engine to invalid version

Expected:

Appropriate Error is thrown: "Invalid engine version".
User Docker continues to work.

Actual:

Error: "FATA[0002] non-200 http response: 404"
User docker stops working

rtp-036:log$ sudo ros -v
ros version v0.7.1
rtp-036:log$ sudo ros engine list
disabled docker-1.10.3
disabled docker-1.11.2
current  docker-1.12.3
rtp-036:log$ docker ps
CONTAINER ID        IMAGE                  COMMAND             CREATED                  STATUS                  PORTS               NAMES
8e7941ba005f        rancher/agent:v1.2.2   "/run.sh run"       Less than a second ago   Up Less than a second                       rancher-agent
rtp-036:log$ sudo ros engine switch docker-17.03.1-ce
FATA[0002] non-200 http response: 404
rtp-036:log$ docker ps
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

I have the same issue. Just can't switch docker engine at runtime, only can enable it.


debug transaction runs out of memory when call stack too long

Love your plug-in - we are heavily using it for debugging!
When running transactions on both a local network and during hardhat tests, the plug-in seems to fail with the below 2 errors when running with external contracts (not included in hre.artifacts). This was not the case in the 1.0.0-alpha.6 release.
Anyway we can include an easy way to manually add artifacts from custom directories/packages (assuming this is the root cause)? My hunch is that this is occurring only when the hre.artifacts does not have abis for the contract log that is being traced.

When trying to run trace on a tx hash for a local transaction, trace is able to find the correct transaction but for some reason gives this error when this line is reached:
const tracePromise = hre.network.provider.send("eth_getTransactionReceipt", [args.hash]);
Error:
<--- Last few GCs --->

[34873:0x7ff583600000]    26382 ms: Scavenge 4035.6 (4116.1) -> 4033.7 (4116.3) MB, 6.8 / 0.0 ms  (average mu = 0.640, current mu = 0.479) allocation failure
[34873:0x7ff583600000]    26409 ms: Scavenge 4036.5 (4116.3) -> 4035.2 (4136.8) MB, 24.0 / 0.0 ms  (average mu = 0.640, current mu = 0.479) allocation failure
[34873:0x7ff583600000]    30338 ms: Mark-sweep 4048.9 (4136.8) -> 4044.0 (4148.1) MB, 3914.3 / 0.0 ms  (average mu = 0.328, current mu = 0.024) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0x107bc8775 node::Abort() [/usr/local/bin/node]
 2: 0x107bc88f8 node::OnFatalError(char const*, char const*) [/usr/local/bin/node]
 3: 0x107d40707 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 4: 0x107d406a3 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
 5: 0x107edf0e5 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
 6: 0x107edd94c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
 7: 0x107eea2c0 v8::internal::Heap::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
 8: 0x107eea341 v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
 9: 0x107eb71b7 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/local/bin/node]
10: 0x1082652ae v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/local/bin/node]
11: 0x108607359 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/usr/local/bin/node]

seems like this error also pops up sporadically:
Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
  errno: -54,
  code: 'ECONNRESET',
  syscall: 'read'
}

Will try your suggestion on Error 1, thank u ser.
For Error 2: In short, I'm building an npm package that can deploy a bunch of pre-compiled contracts locally so integrators can deploy our market without needing testnet.
So the order of operations is:

create a local network with yarn hardhat node
deploy all our market contracts using our npm package
run yarn hardhat trace --hash 0xLocalTxHash http://locahost:8545.

Tbh, even having raw data display would be helpful since maybe I could somehow inject the artifact manually in our npm package, but just need to find a way around Error 2.
Again, appreciate the awesome support!

confirming increasing npm memory size helps, however like you mentioned - the debug trace is so large that even 8gb is not enough. Will voice some support for your PR.

i have seen this issue as well. it could explain this oddly large gas usage
https://github.com/NomicFoundation/hardhat/issues/2672#issuecomment-1138182826
@joshpwrk when / if you ever get those transactions to not fail miserably, do you find that the gas usage is excessively high?

This issue is resolved in a rewrite I've been working on for a while. Please checkout the v2-beta branch.
npm i hardhat-tracer@beta

The v2 was released, which does not use debug_tt and hence does not have this out-of-memory issue. You can look at the release info.
(closing, but feel free to reopen if you face any problems).


Sphinx: File permission problem

I've tried to establish a connection to a new contact and it failed with this error:
raspiblitz env[28860]: (node:28860) UnhandledPromiseRejectionWarning: Error: EACCES: permission denied, open '/mnt/hdd/app-data/lnd/data/chain/bitcoin/mainnet/signer.macaroon'

Same goes for creating a group chat …
Updated Sphinx, but no luck. During that update (via the update menu) I also noticed that there are merge conflicts with the config/app.json files, but that's another separate story …
Temporarily solved it by running sudo chmod 644 /mnt/hdd/app-data/lnd/data/chain/bitcoin/mainnet/signer.macaroon to make it work, but this doesn't seem ideal.
Versions:

Raspiblitz v1.6.3
Sphinx v1.3.8

For access to the the signer macaroon,  run this line:
sudo /usr/sbin/usermod --append --groups lndsigner sphinxrelay
Can add it to the script if works.

@openoms Thanks, your suggestion works! 👍

ok should get this in  PR for the next release

fwiw, I was running into this issue, but instead with router.macaroon. I fixed it by doing a
sudo usermod -aG lndrouter sphinxrelay. This group might also need to be added in the next version.

OK added the mission permission gruoups ... closing issue for v1.7 release. Final testing on #2089


Why only 60 sec?

Good day! Sorry for my English! Thanks for your very good program Spammer-Grab. I have two question:

Why only 60 sec.?
Can I do 5 minutes or more?
Thanks!!!!

what is user nam and password..  after git clone?


Bug: removing a directive from a FieldDefinition removes the type as well

Hi I was looking at whats possible with the astparser and ran into an issue where calling RemoveDirectiveByName also removed the type from the field.
I was running out of time but have knocked together a very quick test to demonstrate
func TestShowBug(t *testing.T) {
	doc, report := astparser.ParseGraphqlDocumentString(`directive @foo on OBJECT | FIELD_DEFINITION type Query{ hello: String! @foo }`)
	if report.HasErrors() {
		t.Fatal(report.Error())
	}
	schemaAST := &doc

	walker := astvisitor.NewWalker(5)

	visitor := removeFieldDirectiveVisitor{
		definition: schemaAST,
	}
	walker.RegisterLeaveDirectiveVisitor(visitor)

	walker.Walk(schemaAST, nil, new(operationreport.Report))

	output, err := astprinter.PrintString(schemaAST, nil)
	if err != nil {
		panic(err)
	}
	if output != `directive @foo on OBJECT | FIELD_DEFINITION type Query{ hello: String! }` {
		t.Fatal("got = ", output)
	}
}

type removeFieldDirectiveVisitor struct {
	definition *ast.Document
}

func (r removeFieldDirectiveVisitor) LeaveDirective(ref int) {
	r.definition.FieldDefinitions[ref].Directives.RemoveDirectiveByName(r.definition, "foo")
}

What you end up with is this
got =  directive @foo on OBJECT | FIELD_DEFINITION type Query {hello}

Hi @darren-west
ref returned in the LeaveDirective(ref int) callback is not a field definitions ref, it is a directive ref
as your schema has 1 field and 1 directives it is matches
When you modify ast manually in this way, you also have to make sure that FieldDefinition will have HasDirectives = false, otherwise ast will be corrupted


Create Cipher Codes.cpp

Encryption method added. Codes for decrypting still pending to be added.

Checked and working


Setting up CI\CD using GitHub Actions

Adding actions to enable CI/CD pipelines to the repository
We have added 3 workflows to enable basic CI/CD.
What?
Following workflows are implemented.

jest.yaml - This workflow runs the tests (jest) on demand or push/pr on main branch.
publish-npm.yaml - This workflow bump package.json version and deploy to npm. This workflow is on-demand.
build-docs.yml - This workflow build and deploys the documentation site which is located at ./website.

Why?
Manual management of CI/CD is tedius for this project.
How?
Implemented by GitHub Actions.

This PR can't be close before docs PR. Reason is we dont have documentation on website and the build-docs.yml will fail if we don't. So deferring this after docs PR.


add Service.WithHostname

Allows you to manually configure a hostname for a service, which will be automatically namespaced within the module. This ability allows you to express circular service dependencies, which was previously impossible with content-addressed hostnames.
Implementation notes:

New API: Service { withHostname(hostname: String!): Service! }

Sets a custom hostname to be used instead of the regular content-addressed (query ID -derived) hostname

When a service has a custom hostname its FQDN will be <host>.<module id>.<session id>.dagger.local

The <module id> is a new component to ensure two modules setting the same hostname don't conflict

A withExec always installs its calling <module id>.<session id>.dagger.local to its list of search domains

In other words, it will always be able to reach service hostnames run by the module that installed the withExec

A container service always installs its starting <module id>.<session id>.dagger.local to its list of search domains

This allows a service returned by a module to reach services with custom hostnames running via the using module
This is in addition to the search domain installed by the original withExec

Great! This was the main blocker for us in adopting Dagger.


Fix - Ensure that modal tabs width are not impacted by side panel opening

This bug was reported in Slack, it appears that https://github.com/wagtail/wagtail/pull/11150 introduced a regression where the side panel opening would cause the tab-content within modals to also be impacted.
https://wagtailcms.slack.com/archives/C81FGJR2S/p1708033342014629

Ideally we would better isolate these classes but for now here's a simple fix to this problem.
Note: The extra padding on the table columns is unrelated, probably needs to be fixed also but I will flag that in a different thread.
To reproduce the bug

Open any page editing view
Open a wide side panel (e.g. the preview panel)
Open a chooser modal, one with tabs in it such as the links chooser
Observe the content is not the full width of the modal
Close the chooser, close the side panel and then re-open the chooser
Observe the content is now the full width of the modal

Screenshots
Before

After

Thanks @laymonage much better, I have applied your recommendation but with a slightly different approach, nesting things inside the w-form-width for easier maintenance. We use a similar approach, using at-root for items relating to the slim header.

As per convo with Thibaud/Sage - we should try to align this with our updated Sass usage guidelines https://docs.wagtail.org/en/stable/contributing/ui_guidelines.html#sass-usage - keep Sass features to a minimum.

Updated @laymonage

main: 07d6acf
stable/6.0.x: 6c9589ff94b94ee2416917d147143023c73a0572

Thanks


Constant arrays perform differently in mrustc and rustc

in my inner loop function I was referencing
https://github.com/dropbox/rust-brotli-decompressor/blob/master/src/prefix.rs#L124
pub const kCmdLut: [CmdLutElement; 704] = [CmdLutElement {
                                             insert_len_extra_bits: 0x00,
                                             copy_len_extra_bits: 0x00,
                                             distance_code: 0,
                                             context: 0x00,
                                             insert_len_offset: 0x0000,
                                             copy_len_offset: 0x0002,
                                           },
.....

called from https://github.com/dropbox/rust-brotli-decompressor/blob/45e53e3747bcac834af9351088ad418780d46670/src/decode.rs#L2047
which worked fast using rustc
but mrustc decided to inline the 704 element struct array into each function call, and this caused a 5x slowdown in the program.
The workaround to fix performance was changing const to static but rustc must have some sort of logic to avoid inlining the constants for arrays.
Even changing smaller arrays like
https://github.com/dropbox/rust-brotli-decompressor/blob/45e53e3747bcac834af9351088ad418780d46670/src/decode.rs#L55
to be static arrays had a positive benefit
My perf fixes for mrustc are committed to a branch https://github.com/dropbox/rust-brotli-decompressor/tree/simplified_mrustc_fixes

Should now be fixed (as of 6a86b6db7458d7310880b7867c5a2cce80bc8802). mrustc now convers shared borrows of constant values into statics. There isn't any de-duplication of these yet, not sure if that will be needed.


bug(mat-button): disabled not following html specs

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When making use of [disabled] on any sort of mat-button, instead of just having disabled in the html, we get [disable]="true", which is not correctly following html specs for boolean attributes.
It is to be noted that, in absence of mat-button, [disabled] is behaving correctly on <button>. I wouldn't be surprised if this had to do with the boolean coercion being made.
Reproduction
Steps to reproduce:

go to the stackbliz
notice the difference in html disable attributes between the native button and the material one

Expected Behavior
disabled is following specs
<button
  _ngcontent-nxh-c308=""
  mat-raised-button=""
  class="mat-focus-indicator mat-raised-button mat-button-base mat-button-disabled"
  ng-reflect-disabled="true"
  disabled>[...]</button>

Actual Behavior
disabled attribute is set to true
<button
  _ngcontent-nxh-c308=""
   mat-raised-button=""
  class="mat-focus-indicator mat-raised-button mat-button-base mat-button-disabled"
  ng-reflect-disabled="true"
  disabled="true">[...]</button>

="true" should not be there in disabled="true"
Environment

Angular: 11, 12, 13 & 14.next-12
CDK/Material: 11, 12, 13 & 14.next-12 (tested trough https://material.angular.io/components/button/overview and equivalent for each version)
Browser(s): Edge 100
Operating System (e.g. Windows, macOS, Ubuntu): macOS

[disabled] on a native button binds to the disabled property. The material button binds to the disabled attribute (not the prop) using [attr.disabled] (see code). The behavior can be reproduced when using [attr.disabled]="true" on a native button, it will result in disabled="true".
This was changed because the same code is used for links (<a>) which don't have a disabled property (https://github.com/angular/components/pull/15308).

It's true that button renders disabled="true", but it doesn't have any practical implications AFAIK, so I don't see a compelling reason to change it.


Redis Cache: Fetching access key is failing

Redis Cache: Fetching access key is failing with commandlet Get-AzureRmRedisCacheKey -ResourceGroupName "group" -Name "name"
{ "shellProps": { "sessionId": "dc494761b43248fb92eafeafdbb72160", "extName": "AzureCacheExtension", "contentName": "CacheTemplateBlade", "resourceId": "/subscriptions/2a1ceccf-281b-46fd-a5aa-dc44d4159af1/resourceGroups/Common/providers/Microsoft.Cache/Redis/DevProarc-redis" }, "error": { "message": "The gateway did not receive a response from 'Microsoft.Cache' within the specified time period. (Code: GatewayTimeout)", "code": 504, "error": { "message": "", "name": "Error", "stack": "Error\n at t.r (https://portal.azure.com/Content/Dynamic/fMde2SuDCDiV.js:20:790)\n at t (https://portal.azure.com/Content/Dynamic/fMde2SuDCDiV.js:20:1563)\n at new t (https://portal.azure.com/Content/Dynamic/fMde2SuDCDiV.js:20:1736)\n at wt (https://portal.azure.com/Content/Dynamic/fMde2SuDCDiV.js:103:680)\n at https://portal.azure.com/Content/Dynamic/fMde2SuDCDiV.js:103:6583\n at o (https://portal.azure.com/Content/Dynamic/vR0oWiGrpr-b.js:4:72)\n at https://portal.azure.com/Content/Dynamic/vR0oWiGrpr-b.js:4:5711", "type": "MsPortalFx.Errors.FetchDataError", "baseTypes": [ "MsPortalFx.Errors.FetchDataError", "MsPortalFx.Errors.DataError", "MsPortalFx.Errors.Error" ], "extension": "AzureCacheExtension", "errorLevel": 2, "timestamp": 61123.1600000001, "source": "CacheResource:DataCache:2:1", "innerErrors": [], "dataSetName": "CacheResource:DataCache:2:1" } }}

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

ID: 24faac4f-d940-7710-f395-577118d765af
Version Independent ID: 10d25201-c843-17ce-17c9-ca3aaa07e02f
Content: Quickstart: Create an Azure Cache for Redis
Content Source: articles/azure-cache-for-redis/quickstart-create-redis.md
Service: cache
GitHub Login: @yegu-ms
Microsoft Alias: yegu

@chayanbaner Thank you for the feedback. We are actively investigating and will get back to you soon.

@chayanbaner Could you please let us know how were you trying to execute the command, was it through the PowerShell inside Azure Portal or any other way?
Just for the reference when I created the 'Azure Cache for Redis' and ran the command inside the Azure Portal I was able to run it successfully.

I was running it from a VM in Azure.

From Azure portal as well getting error:

Resource is located in North Europe

@chayanbaner This mostly looks like latency issue. When I tried using North Europe location, it took a while to return the key based on command. I would suggest you raise a support request on the same as Support team can analyze the logs and check the exact reason behind the issue:

@chayanbaner Please let us know if you need more details on it and we would be glad to assist you there.

Sure, will raise a ticket with support team. Thanks.


update dnn notebook example to give more interesting results

Description
The notebook "notebooks/responsibleaidashboard/responsibleaidashboard-multiclass-dnn-model-debugging.ipynb" had a DNN pytorch model that was only trained for 12 epochs, which ended up giving the same result during inference.
This PR updates the dnn notebook example to train the model for 10000 epochs, to give more interesting results.
Although it takes 13 seconds to train the model, instead of making training instantaneous, the model outputs several possible classes instead of just one class.
Areas changed

npm packages changed:

[ ] responsibleai/causality
[ ] responsibleai/core-ui
[ ] responsibleai/counterfactuals
[ ] responsibleai/dataset-explorer
[ ] responsibleai/fairness
[ ] responsibleai/interpret
[ ] responsibleai/localization
[ ] responsibleai/mlchartlib
[ ] responsibleai/model-assessment

Python packages changed:

[ ] raiwidgets
[ ] responsibleai
[ ] erroranalysis
[ ] rai_core_flask

Tests

[x] No new tests required.
[ ] New tests for the added feature are part of this PR.
[ ] I validated the changes manually.

Screenshots (if appropriate):
Model overview after increasing the number of iterations in the sample notebook:

Previously it would just be:

Documentation:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Codecov Report

Merging #1194 (15c900b) into main (7c6b2a4) will increase coverage by 21.91%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #1194       +/-   ##
===========================================
+ Coverage   67.76%   89.68%   +21.91%
===========================================
  Files          90       26       -64
  Lines        4291     1309     -2982
===========================================
- Hits         2908     1174     -1734
+ Misses       1383      135     -1248

Flag
Coverage Δ

unittests
89.68% <ø> (+21.91%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ai/responsibleai/_tools/counterfactual/__init__.py

.../responsibleai/_managers/error_analysis_manager.py

...sibleai/responsibleai/rai_insights/rai_insights.py

...bleai/responsibleai/_tools/causal/causal_config.py

raiwidgets/raiwidgets/fairness_dashboard.py

responsibleai/responsibleai/_interfaces.py

raiwidgets/raiwidgets/error_analysis_constants.py

...ponsibleai/responsibleai/_managers/base_manager.py

raiwidgets/raiwidgets/model_analysis_dashboard.py

...ai/responsibleai/_tools/causal/causal_constants.py

... and 54 more

Continue to review full report at Codecov.

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


Validate command pool's queueFamilyIndex at vkQueueSubmit time

I have an internal report that the validation layers do not catch a bug where a command pool is created with a certain queue family, command buffers are recorded using that pool, and then those command buffers are submitted to a queue from a different queue family.

Fixed by PR #840.


CRIMRE-334 fixtures use the date format returend by the datastore

Description of change
Dates in fixtures where using a different date time format to the one returned by the datastore.
Link to relevant ticket
CRIMRE-334
Additional notes
The datastore will also be updated in order to standardise the format it uses for dates.

Technically +00:00 and Z are equivalent 😄 But yep maybe best to keep it super explicit.
For the sake of avoid misleading on the precision thing, can we have milliseconds like 123 for instance? instead of 000 which can lead to the impression we don't have that precision thus default to 000?

For the sake of avoid misleading on the precision thing, can we have milliseconds like 123 for instance

Good idea. I'll see if it has much of an impact on specs in other services.


cannot unpack non-iterable NoneType object

Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/autosrt/init.py", line 3329, in main
wav_filepath, sample_rate = wav_converter(media_filepath)
^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: cannot unpack non-iterable NoneType object
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.11/bin/autosrt", line 8, in
sys.exit(main())
^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/autosrt/init.py", line 3548, in main
if not KeyboardInterrupt in str(e):
^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'in ' requires string as left operand, not type

are you using compiled executable from release page or install this app with pip?
what command did you type exactly? please give me a complete screenshot (command you typed and all outputs)


How to design a custom UI?

Due to a requirement, I am trying to use subschema to generate a long form with each form field having a checkbox coming against it.
But I cant figure out how to make it using subschema.
Please see the attached pic and guide me how is this UI possible using subschema?
Thanks.

So does the checkbox enable disable the car.
There is an easy and not so easy way.  The easier way is to add your own type.

//Create a new type.
var {Select, Checkbox} = require('Subschema').types;
var CheckboxSelect = React.createClass({
   mixins:[Subschema.FieldMixin],
    handleCheckChange(e){
      this.setState({checked:e.target.checked});
      if (!this.state.checked){
       //set the value to null if not checked.
       this.triggerChange(null);
     }
    },
    render(){
        return
<input type="checked" checked={this.state.checked}  onChange={this.handleCheckChange}><Select {...this.props} disabled={this.state.checked}/>

    }
});

loader.addType('CheckboxSelect', CheckboxSelect);

var schema = {
    mode:{
      type:'CheckboxSelect',
      options:['Car']
   },
    target:{
      type:'CheckboxSelect',
      title:'Target Version',
      options:['Current Version']
   }

}

Hey I'm gonna close this, can you use the mailing list for future non defect related questions.   Trying to make that a little more useful<EMAIL_ADDRESS>

Justin thanks for the answer.
CheckboxSelect is a great way to do this but unfortunately the HTML controls will all come through server returned json themselves.
Yes I created my custom type but for my scenario we cannot use this sort of approach:
<Select {...this.props} disabled={this.state.checked}/>
Instead I tried:
<ObjectType {...this.props} disabled={this.state.checked} />
but the enabling/disabling still did not occur on check/uncheck of corresponding checkboxes.
I then had to use jquery for making sure if the corresponding checkbox is selected, only then send the corresponding form field value to the server on submit. Though I think using jquery in this is a pathetic approach. May be you can suggest some better one.
And yes OK from next time I will post my help related queries on your mentioned google group. Thanks.

ok I will try the FieldMixin and triggerChange approach. May be I was missing this. Will tell you about its outcome then.

Didn't get my answer on this so far:
https://groups.google.com/forum/m/#!topic/subschema/dyag9pOIog4

I have this  example in a new version of subschema I am going to publish
monday.
https://github.com/jspears/subschema/blob/master/public/samples/Loader-setup.jsx
This won't work with the current version, but is pretty close.
On Sun, Nov 29, 2015 at 5:47 AM Faisal<EMAIL_ADDRESS>wrote:

Didn't get my answer on this so far:
https://groups.google.com/forum/m/#!topic/subschema/dyag9pOIog4
—
Reply to this email directly or view it on GitHub
https://github.com/subschema/subschema/issues/28#issuecomment-160417377.

Yeah but again it is only based on Select control. While in my case the control against every checkbox will itself come from json, means it will by dynamic. So what about that?

Then you are better off using a template.
@template
class CheckboxTemplate extends React.Component {
constructor(...rest) {
super(...rest);
//init state
this.state = {disabled: false};
}
//inline styles, because this is an example
render() {
    var {name, title, help, error, errorClassName, message,

fieldClass,  children} = this.props;
if (!title) {
title = ''
}
    return (

            <Checkbox className='' style={{position: 'absolute',

left:'-5px', top:'5px'}}
onChange={(e)=>this.setState({disabled:
!e})} checked={!this.state.disabled}/>
{children}
{help === false ? null : <Content content={error ?
error : help} key='error-block' type='p'
className={error ?
style.error : style.help}/>}

)
}
}
schema:{
model:{
template:'CheckboxTemplate',
type:'Select',
options:'your options, here'
}
}
On Sun, Nov 29, 2015 at 11:36 PM Faisal<EMAIL_ADDRESS>wrote:

Yeah but again it is only based on Select control. While in my case the
control against every checkbox will itself come from json, means it will by
dynamic. So what about that?
—
Reply to this email directly or view it on GitHub
https://github.com/subschema/subschema/issues/28#issuecomment-160545103.


bloom 560M can not build

python build.py --model_dir ./bloom/560M/                 --dtype float16                 --use_gemm_plugin float16                 --use_gpt_attention_plugin float16                 --output_dir ./bloom/560M/trt_engines/fp16/1-gpu/
Open MPI's OFI driver detected multiple equidistant NICs from the current process,
but had insufficient information to ensure MPI processes fairly pick a NIC for use.
This may negatively impact performance. A more modern PMIx server is necessary to
resolve this issue.
[12/14/2023-14:28:39] [TRT-LLM] [I] Serially build TensorRT engines.
[12/14/2023-14:28:39] [TRT] [I] [MemUsageChange] Init CUDA: CPU +14, GPU +0, now: CPU 166, GPU 649 (MiB)
[12/14/2023-14:28:41] [TRT] [I] [MemUsageChange] Init builder kernel library: CPU +482, GPU +80, now: CPU 784, GPU 729 (MiB)
[12/14/2023-14:28:41] [TRT-LLM] [W] Invalid timing cache, using freshly created one
Traceback (most recent call last):
File "/home/tiger/.local/lib/python3.10/site-packages/pynvml/nvml.py", line 850, in _nvmlGetFunctionPointer
_nvmlGetFunctionPointer_cache[name] = getattr(nvmlLib, name)
File "/usr/local/lib/python3.10/ctypes/init.py", line 387, in getattr
func = self.getitem(name)
File "/usr/local/lib/python3.10/ctypes/init.py", line 392, in getitem
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1: undefined symbol: nvmlDeviceGetMemoryInfo_v2
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/mnt/bn/xiaxin/wulenan/workspace/TensorRT-LLM/examples/bloom/build.py", line 556, in
build(0, args)
File "/mnt/bn/xiaxin/wulenan/workspace/TensorRT-LLM/examples/bloom/build.py", line 524, in build
engine = build_rank_engine(builder, builder_config, engine_name,
File "/mnt/bn/xiaxin/wulenan/workspace/TensorRT-LLM/examples/bloom/build.py", line 337, in build_rank_engine
profiler.print_memory_usage(f'Rank {rank} Engine build starts')
File "/home/tiger/.local/lib/python3.10/site-packages/tensorrt_llm/profiler.py", line 197, in print_memory_usage
alloc_device_mem, _, _ = device_memory_info(device=device)
File "/home/tiger/.local/lib/python3.10/site-packages/tensorrt_llm/profiler.py", line 148, in device_memory_info
mem_info = _device_get_memory_info_fn(handle)
File "/home/tiger/.local/lib/python3.10/site-packages/pynvml/nvml.py", line 2438, in nvmlDeviceGetMemoryInfo
fn = _nvmlGetFunctionPointer("nvmlDeviceGetMemoryInfo_v2")
File "/home/tiger/.local/lib/python3.10/site-packages/pynvml/nvml.py", line 853, in _nvmlGetFunctionPointer
raise NVMLError(NVML_ERROR_FUNCTION_NOT_FOUND)
pynvml.nvml.NVMLError_FunctionNotFound: Function Not Found

What system are you running on? Which OS?

@jdemouth-nvidia I encountered the same problem. I am using the image: nvcr.io/nvidia/tritonserver:23.10-trtllm-python-py3。I'am running on x86 ubuntu。

@jdemouth-nvidia I encountered the same problem too，I am using the image: nvcr.io/nvidia/tritonserver:23.12-trtllm-python-py3。
My system info:
cat /etc/os-release
NAME="CentOS Linux"
VERSION="8 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="8"
My GPU info:
Wed Jan 24 15:08:06 2024
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.82.01    Driver Version: 470.82.01    CUDA Version: 12.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA A10          On   | 00000000:00:08.0 Off |                    0 |
|  0%   48C    P0    61W / 150W |   3926MiB / 22731MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA A10          On   | 00000000:00:09.0 Off |                    0 |
|  0%   47C    P0    62W / 150W |   3254MiB / 22731MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

nvmlDeviceGetMemoryInfo_v2

@yz-tang I fix this by downgrading pynvml from 11.5.0 to 11.4.0
my tensorrt_llm version is 0.8.0.dev2024011601, using pynvml of version 11.4.0 may occur a warning 'Found pynvml==11.4.0. Please use pynvml>=11.5.0 to get accurate memory usage', just ignore it.

I got same error while using NV Driver 470.199.02
NV Driver 535.54.03 works.

@Lenan22 Do you still have the problem? If not, we will close it soon.


Adding Subscription Key Authentication and Removing Region

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-python
Encountered a Subprocess error: (azure-sdk-for-python)
Command: ['/usr/local/bin/autorest', '/tmp/tmpwlm_5s68/rest/specification/cognitiveservices/data-plane/LUIS/Runtime/readme.md', '--multiapi', '--python', '--python-mode=update', '--python-sdks-folder=/tmp/tmpwlm_5s68/sdk', '--use=<EMAIL_ADDRESS>'--version=preview']
Finished with return code 1
and output:
AutoRest code generation utility [version: 2.0.4283; node: v8.11.3]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/root/.autorest/@microsoft.azure_autorest-core<EMAIL_ADDRESS>(2.0.4286)
   Loading AutoRest extension<EMAIL_ADDRESS>(~3.0.56->3.0.58)
   Loading AutoRest extension<EMAIL_ADDRESS>(2.3.44->2.3.44)
ERROR: Schema violation: Data does not match any schemas from 'oneOf'
    - file:///tmp/tmpwlm_5s68/rest/specification/cognitiveservices/data-plane/LUIS/Runtime/stable/v2.0/LUIS-Runtime.json:17:4 ($.securityDefinitions.apiKeyHeader)
FATAL: swagger-document/individual/schema-validator - FAILED
FATAL: Error: [OperationAbortedException] Error occurred. Exiting.
Process() cancelled due to exception : [OperationAbortedException] Error occurred. Exiting.

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go


TAO dashboard is unable to be redeployed after upstream changes

3 months ago, I pulled aws-cudos-framework-deployment repo, did some changes (mostly add vpc config as my org requires lamda to be placed in a vpc) and have TAO dashboard deployed successfully.
At the time, I also had to put cid-0.2.22.zip into our own bucket as my stack could not reach s3://aws-managed-cost-intelligence-dashboards/cid-resource-lambda-layer/...
Today when I use the same CloudFormation code to remove and redeploy TAO dashboard, the stack throws error.
Received response status [FAILED] from custom resource. Message returned: Deploy failed: [... {'Type': 'COLUMN_REPLACEMENT_MISSING', 'Message': "Required column 'Estimated Monthly Savings Trend' is missing in data set 'arn:aws:quicksight:ap-southeast-1:xxx:dataset/ta-organizational-view'"}, {'Type': 'COLUMN_REPLACEMENT_MISSING', 'Message': "Required column 'Estimated Monthly Savings' is missing in data set 'arn:aws:quicksight:ap-southeast-1:xxxx:dataset/ta-organizational-view'"},...}]

I found that there were changes 2 months ago in this upstream git repo that breaks https://github.com/aws-samples/aws-cudos-framework-deployment/blame/68829fffb4e5b00c578117f79337a7bc45de0cfe/cid/builtin/core/data/datasets/tao/dataset.json#L1378
The question now is that how can I re-deploy the same TAO dashboard I had previously as I do not want to upgrade to latest dashboard and deal with merge conflicts as well as risk of changes.

In CidCustomResourceDashboard lambda log I saw a line
{'AwsAccountId': 'xxx', 'DashboardId': 'ta-organizational-view', 'Name': 'Trusted Advisor Organizational View', 'SourceEntity': {'SourceTemplate': {'Arn': 'arn:aws:quicksight:us-east-1:223485597511:template/ta-organizational-view/version/18', 'DataSetReferences': [{'DataSetPlaceholder': 'ta-organizational-view', 'DataSetArn': 'arn:aws:quicksight:ap-southeast-1:xxx:dataset/ta-organizational-view'}]}}, ....}

I guess it is automatically getting the template with latest version 18.
Please advise how would I specify the right version for cid-0.2.22

@esc1144 @iakov-aws Can you help to look into how to lock version of dashboard template?

By checking log from August, I put hardcoded version number into this line https://github.com/aws-samples/aws-cudos-framework-deployment/blob/1b817a9d7931039d979c818e7f9bbff21ed3e0c7/cid/helpers/quicksight/init.py#L1270
This workaround helped to restore the dashboard.
if definition.get('dashboardId') == "ta-organizational-view":
            definition.get('sourceTemplate').version = 14

Would like to find the right way to fix this.

Hi @nchicong ,
We only support update to the latest version of the dashboard template. In your case seems like you haven't done any customizations to the dashboard hence you could use the same stack to re-deploy dashboard, but you'd need to specify the latest version 0.2.39 of cid-cmd in the parameter. This version includes required schema for the dashboard template, so you'd be able to use latest version of the TAO dashboard with existing customized CloudFormation template.
The workaround which you've implemented also works, but the one I suggested above would help you to deploy the latest version of the dashboard though

Hi @yprikhodko
I would not want to upgrade any part of our current dashboard stack as it might change some of the athena tables, views, quicksight datasets.
I'm using fixed version of cid-0.2.22.zip as I upload to our own S3, but it still fetch the latest dashboard template.
For now I switched to this code modifications as in this screenshot:

I thought the goal was not to make changes to the modified stack. QuickSight datasets are managed by custom resource hence their update wouldn't require any change of the stack, just version of cid-cmd in parameter. But if concern is to keep dashboard and dataset version the same as well then I can confirm that the workaround which you've made is the only possible way to achieve that.


Supported iOS versions

I'd like to assume that version 2.4.9 supports iOS 10/11 in addition to iOS 12+. However, the wording in the README makes it sound like I have to pick a version of react-native-iap earlier than 2.4.9 in order to support iOS 11.
In summary, does version 2.4.9 support iOS 10 and/or 11?

@cumom Sorry for the confusion. Actually, I think the build won't fail if you are using ios 12+ but there were some issues in compiling unknown method below ios 12 provided in #455. If anyone can debug this feature and support the lower version of react-native-iap, it would be really appreciated. Currently, I don't have much time debugging this issue so I just warned the problem in migration guide.

Actually, I am more interested in whether the newer version of
react-native-iap works with older versions of iOS.
On Wed, May 8, 2019 at 12:29 PM Hyo Chan Jang<EMAIL_ADDRESS>wrote:

@cumom https://github.com/cumom Sorry for the confusion. Actually, I
think the build won't fail if you are using ios 12+ but there were some
issues in compiling unknown method below ios 12 provided in #455
https://github.com/dooboolab/react-native-iap/pull/455. If anyone can
debug this feature and support the lower version of react-native-iap, it
would be really appreciated. Currently, I don't have much time debugging
this issue so I just warned the problem in migration guide.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dooboolab/react-native-iap/issues/481#issuecomment-490556832,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABEMGFPRVJYKAN2R75QMM3PUL5VTANCNFSM4HLBQ3IQ
.

@cumom It will be compatible as long as it builds up. However, the new feature should be tested and see if it works properly.

@hyochan I'm a little bit confused...
The documentation says:

For ios under version 12, it is compatible until react-nativep-iap version 2.4.8. From 2.4.9, it will support ios >= 12.

But I don't understand if<EMAIL_ADDRESS>(the latest version) supports iOS <= 12.
Can you kindly clarify this point?

This is defined in the readme. I know this can be more supportive in ios by distinguishing the ios version. However, I'll leave this for now and please give us a PR if you think this is necessary.

@hyochan it would be helpful if in the react-nativep-iap >= 3 readme there was reference to the minimum versions for both iOS and Android.
For example, v3 supports iOS <= 12?

+1 to this. Could it be clarified in the current v3+ README if there is a minimum version of iOS that the library supports? We would not want to upgrade to v3+ if the library would no longer work for our users on iOS <12.

v3 will support ios below 12


Simulator has some non-blocking aspects when the real device blocks for showString()

Apologies if this is a known issue. I could not find a duplicate in the issues.
It seems that when using the "forever" loop, the simulator attempts to execute that even during a showString() function executed by an event elsewhere. On a real micro:bit, showString() is a blocking call, so that forever() does not execute until showString() has completed. Here is a video showing the behavior: https://youtu.be/sZ5QYsEWaW0

Known problem.

I believe it should replicate the C++ behavior.

agreed. didnt mean to close

here is the code from the video:
basic.forever(() => {
    basic.showIcon(IconNames.Heart)
})
input.onButtonPressed(Button.A, () => {
    basic.showString("Goodbye, and thanks!")
})
basic.showString("Hello!")

I'd like to take this one, as we discussed.

@riknoll - you have this one diagnosed, correct?

Yep, I'll push a fix

Thanks!

@riknoll is this fixed?

Yep


[WIP] Refactor Web UI code

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4924/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4926/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4930/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4942/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4943/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4945/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4947/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4955/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4956/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4959/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5319/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5324/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5336/
Test PASSed.

alluxio-bot, merge this please.


Update regen specific proto files to v4.0

ran diff -qr packages/api/proto/regen ../regen/regen-ledger/proto/regen to see what needed updating
copied over all inconsistent proto files from regen-ledger (v4.0.1 tag)
verified contents of folder are the same via diff -qr packages/api/proto/regen ../regen/regen-ledger/proto/regen
ran yarn gen against the latest protoc (libprotoc 3.21.5 via brew install protobuf)

Also - basket.MsgTake passes with this PR!


tensorflow/core/grappler/optimizers/constant_folding.cc:145:38: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
   return reinterpret_cast<int32_t&>(a) != reinterpret_cast<int32_t&>(b);
                                      ^
tensorflow/core/grappler/optimizers/constant_folding.cc:145:71: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
   return reinterpret_cast<int32_t&>(a) != reinterpret_cast<int32_t&>(b);
                                                                       ^
tensorflow/core/grappler/optimizers/constant_folding.cc: In function 'bool tensorflow::grappler::{anonymous}::PackedValuesNotEqual(T, T) [with T = double]':
tensorflow/core/grappler/optimizers/constant_folding.cc:150:38: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
   return reinterpret_cast<int64_t&>(a) != reinterpret_cast<int64_t&>(b);
                                      ^
tensorflow/core/grappler/optimizers/constant_folding.cc:150:71: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
   return reinterpret_cast<int64_t&>(a) != reinterpret_cast<int64_t&>(b);
                                                                       ^
tensorflow/core/grappler/optimizers/constant_folding.cc: In member function 'tensorflow::Status tensorflow::grappler::ConstantFolding::MaterializeShapes(const tensorflow::grappler::GraphProperties&)':
tensorflow/core/grappler/optimizers/constant_folding.cc:482:37: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     for (int port_idx = 0; port_idx < output.size(); ++port_idx) {
                            ~~~~~~~~~^~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc: In member function 'tensorflow::Status tensorflow::grappler::ConstantFolding::MaterializeBroadcastGradientArgs(const tensorflow::NodeDef&, const tensorflow::grappler::GraphProperties&)':
tensorflow/core/grappler/optimizers/constant_folding.cc:644:31: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for (int i = common_dims; i < shape1.size(); ++i) {
                             ~~^~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc:649:31: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for (int i = common_dims; i < shape2.size(); ++i) {
                             ~~^~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc: In function 'bool tensorflow::grappler::{anonymous}::IsValidConstShapeForMulConvPushDown(const string&, const tensorflow::TensorShapeProto&, const tensorflow::TensorShapeProto&)':
tensorflow/core/grappler/optimizers/constant_folding.cc:1168:40: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (mul_const_input_shape.dim_size() <= data_format.size() &&
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc: In member function 'tensorflow::Status tensorflow::grappler::ConstantFolding::FoldNode(tensorflow::NodeDef*, tensorflow::GraphDef*, bool*)':
tensorflow/core/grappler/optimizers/constant_folding.cc:1464:21: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for (int i = 0; i < const_nodes.size(); i++) {
                   ~~^~~~~~~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc:1552:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
           } else if (port < const_nodes.size() &&
                      ~~~~~^~~~~~~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc: In member function 'tensorflow::Status tensorflow::grappler::ConstantFolding::RemoveShuffleOrTranspose(const tensorflow::grappler::GraphProperties&, bool, tensorflow::GraphDef*, tensorflow::NodeDef*)':
tensorflow/core/grappler/optimizers/constant_folding.cc:2071:28: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (permutation.size() != shape.dim_size()) {
         ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc: In member function 'tensorflow::Status tensorflow::grappler::ConstantFolding::SimplifyStridedSlice(const tensorflow::grappler::GraphProperties&, bool, tensorflow::GraphDef*, tensorflow::NodeDef*)':
tensorflow/core/grappler/optimizers/constant_folding.cc:2249:13: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
           j >= ellipsis_index + expanded_ellipsis_indices.size()) {
           ~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc: In member function 'bool tensorflow::grappler::ConstantFolding::PartialAssocOpConstFolding(tensorflow::GraphDef*, tensorflow::grappler::GraphProperties*, tensorflow::NodeDef*)':
tensorflow/core/grappler/optimizers/constant_folding.cc:3482:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (const_inputs.size() == num_non_control_inputs &&
       ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/grappler/optimizers/constant_folding.cc:3490:54: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (const_inputs.size() > 1 && const_inputs.size() < num_non_control_inputs &&
                                  ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
In file included from tensorflow/core/grappler/optimizers/constant_folding.cc:55:0:
./tensorflow/core/util/bcast.h: In instantiation of 'tensorflow::BCastList<N>::BCastList(const Vec (&)[N], bool, bool) [with int N = 2; tensorflow::BCastList<N>::Vec = absl::lts_2020_02_25::InlinedVector<long long int, 4>]':
./tensorflow/core/util/bcast.h:360:52:   required from here
./tensorflow/core/util/bcast.h:142:21: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (x[i].size() > largest_rank) {
./tensorflow/core/util/bcast.h:179:24: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (copy[i].size() < largest_rank) {
INFO: From Compiling tensorflow/core/common_runtime/propagator_debug_utils.cc:
tensorflow/core/common_runtime/propagator_debug_utils.cc: In function 'const tensorflow::Tensor* tensorflow::GetTensorValueForDump(const tensorflow::Entry&)':
tensorflow/core/common_runtime/propagator_debug_utils.cc:41:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
INFO: From Compiling tensorflow/core/common_runtime/bfc_allocator.cc:
In file included from tensorflow/core/common_runtime/bfc_allocator.cc:16:0:
./tensorflow/core/common_runtime/bfc_allocator.h: In member function 'std::__cxx11::string tensorflow::BFCAllocator::Chunk::DebugString(tensorflow::BFCAllocator*, bool)':
./tensorflow/core/common_runtime/bfc_allocator.h:205:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
       if (recurse && prev != BFCAllocator::kInvalidChunkHandle) {
                      ~~~~~^~~~~~~~~~~~~~~
./tensorflow/core/common_runtime/bfc_allocator.h:209:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
       if (recurse && next != BFCAllocator::kInvalidChunkHandle) {
                      ~~~~~^~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'tensorflow::BFCAllocator::ChunkHandle tensorflow::BFCAllocator::AllocateChunk()':
tensorflow/core/common_runtime/bfc_allocator.cc:181:25: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (free_chunks_list_ != kInvalidChunkHandle) {
       ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'bool tensorflow::BFCAllocator::DeallocateFreeRegions(size_t)':
tensorflow/core/common_runtime/bfc_allocator.cc:285:14: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     while (h != kInvalidChunkHandle) {
            ~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'void tensorflow::BFCAllocator::DeallocateRegions(const absl::lts_2020_02_25::flat_hash_set<void*>&)':
tensorflow/core/common_runtime/bfc_allocator.cc:346:14: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     while (h != kInvalidChunkHandle) {
            ~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'void tensorflow::BFCAllocator::SplitChunk(tensorflow::BFCAllocator::ChunkHandle, size_t)':
tensorflow/core/common_runtime/bfc_allocator.cc:606:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (h_neighbor != kInvalidChunkHandle) {
       ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
In file included from ./tensorflow/core/platform/default/logging.h:29:0,
                 from ./tensorflow/core/platform/logging.h:27,
                 from ./tensorflow/core/platform/status.h:24,
                 from ./tensorflow/core/platform/errors.h:22,
                 from ./tensorflow/core/platform/env.h:27,
                 from ./tensorflow/core/common_runtime/allocator_retry.h:19,
                 from ./tensorflow/core/common_runtime/bfc_allocator.h:27,
                 from tensorflow/core/common_runtime/bfc_allocator.cc:16:
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'void tensorflow::BFCAllocator::DeallocateRawInternal(void*)':
tensorflow/core/common_runtime/bfc_allocator.cc:631:11: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   CHECK(h != kInvalidChunkHandle);
         ~~^~~~
./tensorflow/core/platform/macros.h:83:47: note: in definition of macro 'TF_PREDICT_FALSE'
 #define TF_PREDICT_FALSE(x) (__builtin_expect(x, 0))
                                               ^
tensorflow/core/common_runtime/bfc_allocator.cc:631:3: note: in expansion of macro 'CHECK'
   CHECK(h != kInvalidChunkHandle);
   ^
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'void tensorflow::BFCAllocator::Merge(tensorflow::BFCAllocator::ChunkHandle, tensorflow::BFCAllocator::ChunkHandle)':
tensorflow/core/common_runtime/bfc_allocator.cc:677:10: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (h3 != kInvalidChunkHandle) {
       ~~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'tensorflow::BFCAllocator::ChunkHandle tensorflow::BFCAllocator::TryToCoalesce(tensorflow::BFCAllocator::ChunkHandle, bool)':
tensorflow/core/common_runtime/bfc_allocator.cc:757:15: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (c->next != kInvalidChunkHandle && !ChunkFromHandle(c->next)->in_use()) {
       ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc:767:15: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (c->prev != kInvalidChunkHandle && !ChunkFromHandle(c->prev)->in_use()) {
       ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'bool tensorflow::BFCAllocator::MergeTimestampedChunks(size_t)':
tensorflow/core/common_runtime/bfc_allocator.cc:806:11: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (h == kInvalidChunkHandle) {
         ~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc:835:23: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for (int ci = 0; ci < to_merge.size(); ++ci) {
                    ~~~^~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc:841:11: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     if (h == kInvalidChunkHandle) continue;
         ~~^~~~~~~~~~~~~~~~~~~~~~
In file included from ./tensorflow/core/platform/default/logging.h:29:0,
                 from ./tensorflow/core/platform/logging.h:27,
                 from ./tensorflow/core/platform/status.h:24,
                 from ./tensorflow/core/platform/errors.h:22,
                 from ./tensorflow/core/platform/env.h:27,
                 from ./tensorflow/core/common_runtime/allocator_retry.h:19,
                 from ./tensorflow/core/common_runtime/bfc_allocator.h:27,
                 from tensorflow/core/common_runtime/bfc_allocator.cc:16:
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'virtual size_t tensorflow::BFCAllocator::RequestedSize(const void*) const':
tensorflow/core/common_runtime/bfc_allocator.cc:873:11: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   CHECK(h != kInvalidChunkHandle)
         ~~^~~~
./tensorflow/core/platform/macros.h:83:47: note: in definition of macro 'TF_PREDICT_FALSE'
 #define TF_PREDICT_FALSE(x) (__builtin_expect(x, 0))
                                               ^
tensorflow/core/common_runtime/bfc_allocator.cc:873:3: note: in expansion of macro 'CHECK'
   CHECK(h != kInvalidChunkHandle)
   ^
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'virtual size_t tensorflow::BFCAllocator::AllocatedSize(const void*) const':
tensorflow/core/common_runtime/bfc_allocator.cc:882:11: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   CHECK(h != kInvalidChunkHandle)
         ~~^~~~
./tensorflow/core/platform/macros.h:83:47: note: in definition of macro 'TF_PREDICT_FALSE'
 #define TF_PREDICT_FALSE(x) (__builtin_expect(x, 0))
                                               ^
tensorflow/core/common_runtime/bfc_allocator.cc:882:3: note: in expansion of macro 'CHECK'
   CHECK(h != kInvalidChunkHandle)
   ^
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'virtual tensorflow::int64 tensorflow::BFCAllocator::AllocationId(const void*) const':
tensorflow/core/common_runtime/bfc_allocator.cc:891:11: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   CHECK(h != kInvalidChunkHandle)
         ~~^~~~
./tensorflow/core/platform/macros.h:83:47: note: in definition of macro 'TF_PREDICT_FALSE'
 #define TF_PREDICT_FALSE(x) (__builtin_expect(x, 0))
                                               ^
tensorflow/core/common_runtime/bfc_allocator.cc:891:3: note: in expansion of macro 'CHECK'
   CHECK(h != kInvalidChunkHandle)
   ^
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'std::__cxx11::string tensorflow::BFCAllocator::RenderOccupancy()':
tensorflow/core/common_runtime/bfc_allocator.cc:946:14: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     while (h != kInvalidChunkHandle) {
            ~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'void tensorflow::BFCAllocator::DumpMemoryLog(size_t)':
tensorflow/core/common_runtime/bfc_allocator.cc:1008:14: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     while (h != kInvalidChunkHandle) {
            ~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'tensorflow::MemoryDump tensorflow::BFCAllocator::RecordMemoryMapInternal()':
tensorflow/core/common_runtime/bfc_allocator.cc:1103:14: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     while (h != kInvalidChunkHandle) {
            ~~^~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/common_runtime/bfc_allocator.cc: In member function 'std::array<tensorflow::BFCAllocator::BinDebugInfo, 21> tensorflow::BFCAllocator::get_bin_debug_info()':
tensorflow/core/common_runtime/bfc_allocator.cc:1157:14: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     while (h != kInvalidChunkHandle) {
            ~~^~~~~~~~~~~~~~~~~~~~~~
INFO: From Compiling tensorflow/core/lib/io/inputbuffer.cc:
tensorflow/core/lib/io/inputbuffer.cc: In member function 'tensorflow::Status tensorflow::io::InputBuffer::ReadNBytes(tensorflow::int64, std::__cxx11::string*)':
tensorflow/core/lib/io/inputbuffer.cc:88:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (bytes_read < bytes_to_read) result->resize(bytes_read);
       ~~~~~~~~~~~^~~~~~~~~~~~~~~
tensorflow/core/lib/io/inputbuffer.cc: In member function 'tensorflow::Status tensorflow::io::InputBuffer::Hint(tensorflow::int64)':
tensorflow/core/lib/io/inputbuffer.cc:207:21: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (bytes_to_read > size_) {
       ~~~~~~~~~~~~~~^~~~~~~
tensorflow/core/lib/io/inputbuffer.cc:233:46: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   if (errors::IsOutOfRange(s) && data.size() == bytes_to_read) {
                                  ~~~~~~~~~~~~^~~~~~~~~~~~~~~~
INFO: From Compiling tensorflow/core/platform/platform_strings.cc:
In file included from tensorflow/core/platform/platform_strings.cc:16:0:
./tensorflow/core/platform/platform_strings.h:96:1: warning: multi-line comment [-Wcomment]
 // #define TF_PLAT_STR_(x) \
 ^
INFO: From Compiling tensorflow/core/platform/default/stacktrace_handler.cc:
tensorflow/core/platform/default/stacktrace_handler.cc: In function 'void tensorflow::testing::InstallStacktraceHandler()':
tensorflow/core/platform/default/stacktrace_handler.cc:118:7: warning: ignoring return value of 'ssize_t write(int, const void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
       (void)write(STDERR_FILENO, buf, strlen(buf));
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/platform/default/stacktrace_handler.cc:125:7: warning: ignoring return value of 'ssize_t write(int, const void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
       (void)write(STDERR_FILENO, buf, strlen(buf));
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/platform/default/stacktrace_handler.cc: In function 'void tensorflow::testing::StacktraceHandler(int, siginfo_t*, void*)':
tensorflow/core/platform/default/stacktrace_handler.cc:79:3: warning: ignoring return value of 'ssize_t write(int, const void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   (void)write(STDERR_FILENO, buf, strlen(buf));
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/platform/default/stacktrace_handler.cc:89:3: warning: ignoring return value of 'ssize_t write(int, const void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   (void)write(STDERR_FILENO, stacktrace.c_str(), stacktrace.length());
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/platform/default/stacktrace_handler.cc: In function 'void tensorflow::testing::SafePrintStackTrace()':
tensorflow/core/platform/default/stacktrace_handler.cc:46:3: warning: ignoring return value of 'ssize_t write(int, const void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   (void)write(STDERR_FILENO, begin_msg, strlen(begin_msg));
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tensorflow/core/platform/default/stacktrace_handler.cc:57:3: warning: ignoring return value of 'ssize_t write(int, const void*, size_t)', declared with attribute warn_unused_result [-Wunused-result]
   (void)write(STDERR_FILENO, end_msg, strlen(end_msg));
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
INFO: From Compiling tensorflow/core/lib/io/snappy/snappy_inputstream.cc:
tensorflow/core/lib/io/snappy/snappy_inputstream.cc: In member function 'tensorflow::Status tensorflow::io::SnappyInputStream::Inflate()':
tensorflow/core/lib/io/snappy/snappy_inputstream.cc:88:21: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
   for (int i = 0; i < sizeof(uint32); ++i) {
                   ~~^~~~~~~~~
tensorflow/core/lib/io/snappy/snappy_inputstream.cc:90:34: warning: 'compressed_block_length' may be used uninitialized in this function [-Wmaybe-uninitialized]
         (compressed_block_length << 8) |
         ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
INFO: From ProtoCompile tensorflow/core/protobuf/autotuning.pb.h:
bazel-out/k8-opt-exec-50AE0418/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From ProtoCompile tensorflow/core/protobuf/conv_autotuning.pb.h:
bazel-out/k8-opt-exec-50AE0418/bin/external/com_google_protobuf/src: warning: directory does not exist.
INFO: From Compiling tensorflow/core/common_runtime/placer_inspection_required_ops_utils.cc:
tensorflow/core/common_runtime/placer_inspection_required_ops_utils.cc: In function 'tensorflow::Status tensorflow::{anonymous}::AddOutputIdentities(tensorflow::Node*, tensorflow::Graph*, std::unordered_set<std::__cxx11::basic_string<char> >*)':
tensorflow/core/common_runtime/placer_inspection_required_ops_utils.cc:274:42: warning: 'identity_node' may be used uninitialized in this function [-Wmaybe-uninitialized]
             << identity_node->DebugString();
                ~~~~~~~~~~~~~~~~~~~~~~~~~~^~
In file included from ./tensorflow/core/lib/core/errors.h:19:0,
                 from ./tensorflow/core/framework/tensor_shape.h:23,
                 from ./tensorflow/core/framework/partial_tensor_shape.h:20,
                 from ./tensorflow/core/framework/attr_value_util.h:23,
                 from ./tensorflow/core/framework/function.h:30,
                 from ./tensorflow/core/common_runtime/placer_inspection_required_ops_utils.h:35,
                 from tensorflow/core/common_runtime/placer_inspection_required_ops_utils.cc:15:
./tensorflow/core/platform/errors.h:73:48: warning: 'identity_node' may be used uninitialized in this function [-Wmaybe-uninitialized]
     ::tensorflow::Status _status = (__VA_ARGS__);        \
                                                ^
tensorflow/core/common_runtime/placer_inspection_required_ops_utils.cc:252:11: note: 'identity_node' was declared here
     Node* identity_node;
           ^~~~~~~~~~~~~
INFO: From Compiling tensorflow/core/common_runtime/immutable_executor_state.cc:
tensorflow/core/common_runtime/immutable_executor_state.cc:268:6: warning: 'bool tensorflow::{anonymous}::ExtractScopedAllocatorAttr(const std::vector<int>&, int, tensorflow::AllocatorAttributes*)' defined but not used [-Wunused-function]
 bool ExtractScopedAllocatorAttr(const std::vector<int>& sc_attr,
      ^~~~~~~~~~~~~~~~~~~~~~~~~~
INFO: From Compiling tensorflow/core/common_runtime/inline_function_utils.cc:
tensorflow/core/common_runtime/inline_function_utils.cc: In lambda function:
tensorflow/core/common_runtime/inline_function_utils.cc:330:3: warning: control reaches end of non-void function [-Wreturn-type]
   };
   ^
ERROR: /home/hreich/tensorflow/tensorflow/core/util/BUILD:351:1: error executing shell command: '/bin/bash -c bazel-out/k8-opt-exec-50AE0418-ST-e0f78fafe98f9cd48032f8d6a9732902b210aba3b30f85849d3455fe9d9fb327/bin/tensorflow/tools/git/gen_git_source --generate "$@" --git_tag_override=${GIT_TAG_...' failed (Exit 1)
Traceback (most recent call last):
  File "/home/hreich/.cache/bazel/_bazel_hreich/ce70f23006de10ef478ad3c980ee8c42/execroot/org_tensorflow/bazel-out/k8-opt-exec-50AE0418-ST-e0f78fafe98f9cd48032f8d6a9732902b210aba3b30f85849d3455fe9d9fb327/bin/tensorflow/tools/git/gen_git_source.runfiles/org_tensorflow/tensorflow/tools/git/gen_git_source.py", line 32, in <module>
    from builtins import bytes  # pylint: disable=redefined-builtin
ImportError: No module named builtins
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 416.719s, Critical Path: 105.04s
INFO: 2049 processes: 2049 local.
FAILED: Build did NOT complete successfully

ERROR: /home/hreich/tensorflow/tensorflow/core/util/BUILD:351:1: error executing shell command: '/bin/bash -c bazel-out/k8-opt-exec-50AE0418-ST-e0f78fafe98f9cd48032f8d6a9732902b210aba3b30f85849d3455fe9d9fb327/bin/tensorflow/tools/git/gen_git_source --generate "$@" --git_tag_override=${GIT_TAG_...' failed (Exit 1)
Traceback (most recent call last):
  File "/home/hreich/.cache/bazel/_bazel_hreich/ce70f23006de10ef478ad3c980ee8c42/execroot/org_tensorflow/bazel-out/k8-opt-exec-50AE0418-ST-e0f78fafe98f9cd48032f8d6a9732902b210aba3b30f85849d3455fe9d9fb327/bin/tensorflow/tools/git/gen_git_source.runfiles/org_tensorflow/tensorflow/tools/git/gen_git_source.py", line 32, in <module>
    from builtins import bytes  # pylint: disable=redefined-builtin
ImportError: No module named builtins

This signals that your python installation is broken.


Stable docs do not exist

Hi @chriselrod,
Just clicked on the stable docs in the readme and the seem to not exist. Probably just remove the batch and the link and just point to the dev ones.
Cheers,  Tobi

@DilumAluthge I assume the docs exist somewhere; any idea how to find the url/where it is specified?