Publish Gradle API (WIP)

TODO

[ ] Test that plugin compiled against published API works in a build
[ ] Sign published artifacts.
[ ] Move all logic to publish API JARs to its own build-logic plugin.
[ ] Fix Kotlin DSL compilation to have access to extension methods
[x] Hide GradlePluginDevelopmentExtension.geetGradleApiVersion() or make it experimental
[x] Include Kotlin DSL extensions JAR (from here)
[x] Test that the API JAR can be compiled against
[x] Publish the JARs under org.gradle.experimental.gradle-api to repo.grdev.net.
[x] Check if we need to include any resources (for Groovy? for Kotlin?).

[x] META-INF/groovy/org.codehaus.groovy.runtime.ExtensionModule
[x] META-INF/services/org.codehaus.groovy.transform.ASTTransformation
[x] META_INF/*.kotlin_module- [x] Attach dependencies (Groovy, Kotlin?) to the API JARs.

[x] Figure out what to do with :build-logci:kotlin-dsl-shared-runtime.
[x] Figure out a way to eliminate the duplicate package-info.class files.
[x] Move logic to create API JARs to its own build-logic plugin.

Things to do later:

[ ] Publish artifacts under final GAV.
[ ] Use Gradle's old API JAR generator code to shrink the size of the JAR (the old code (ApiJar and ApiClassExtractor) was removed in https://github.com/gradle/gradle/pull/15800) ~Use ProGuard to shrink and filter the API JARs. ChatGPT says it can do it.~
[ ] Include API JAR in Gradle distribution, and compile against it when using gradleApi().
[ ] Publish sources.
[ ] Publish Javadocs.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test QF please.

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

@bot-gradle test QF please.

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

@bot-gradle test QF please.

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

@bot-gradle test QF please.

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

@bot-gradle test QF please.

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

:tada: Successfully published https://repo.grdev.net/ui/repos/tree/General/libs-snapshots-local/org/gradle/experimental/gradle-public-api/8.9-branch-lptr_plugin_development_publish_gradle_apis-20240531151351+0000
\o/
It can be consumed and compiled against, too! https://github.com/lptr/gradle-published-api-test/tree/e924b04b33aaf2e1c863e00ee65ebd04f51401ca

@bot-gradle test QF please.

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

@bot-gradle test this please.

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this please.

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this please.

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build


Input landscan data for population density

As is : population density data is from CIESIN. Free but inacurate in some places.
To be : use landscan. Format is ESRI

https://github.com/jonas-p/go-shp

https://landscan.ornl.gov/sample-data
cyprus is available as a sample
ownload the sample data file sample_LS2016_cyprus.zip” (52KB)
Open ESRI ArcMap
Click the “add data” button
Select the “cyprus_2016.lyr” layer file

gdal_translate -sds -a_nodata 0 -ot Int32 -of AAIGrid /Users/thomaspeugeot/tmp/Haiti-2014/Population/lspop2014/ "/Users/thomaspeugeot/tmp/hti.asc"
special thks to Guilhem Vellut

problem : the as-is grump-reader only takes density data organized according to CIESIN.
That is a directory hti_grumpv1_pcount_00_ascii_30 with inside a file
htiup00ag.asc.
also, the no value is different "-2147483647" instead of 0

It worked for haiti

With the runtime server, locations seems one degree west


Could not save nil values

Goals
Able to save nil attributes.
Expected Results
Existing attribute with non-nil value will become nil.
Actual Results
Could not overwrite existing value with nil value. The existing value is always returned.
Steps to Reproduce

Create an object.
Assign a non-nil value to object's attribute.
Save.
Create another object with same primary key.
Assign a nil value to the same object's attribute.
Save.
Fetch.
Notice that the attribute is not nil.

Code Sample
class RealmObject: Object {
  dynamic var id = 0
  dynamic var attribute: String?

  override static func primaryKey() -> String? {
    return "id"
  }
}

let realmObject = RealmObject()
realmObject.attribute = "My Attribute"
try! Realm().add(realmObject, update: true)

let realmObject = RealmObject()
realmObject.attribute = nil
try! Realm().add(realmObject, update: true)

// At this point, realmObject.attribute is still equal to "My Attribute."

Version of Realm and Tooling

Realm framework version: 2.8.0
Realm Object Server version: ?
Xcode version: 8.3.2
iOS/OSX version: 10.3
Dependency manager + version: Cocoapods 1.2.0

Thanks for getting in touch with us. Unfortunately this is a known issue: we don't have a good way to distinguish intent between "nil means set this property to nil" and "nil means don't touch the current value of this property", and currently assume the latter. We're looking into ways to address this problem.
In the meantime, you can work around this issue by getting the managed instance of the object based on its primary key id, then changing its attribute value within a write transaction block.

Hi @austinzheng. Thank you for your response. Just want to clarify, this doesn't happen in the older version of Realm (2.0.7 below). Is there any significant refactoring that was made in this version?

The relevant code path has been refactored a number of times since then. Unfortunately, we never formally established the semantics of nil properties used in the way above, so we didn't catch it as a breaking change. I'll talk to our other engineers to decide how we want to proceed in this manner.

I con confirm that this issue was introduced in the latest 2.8.0 release. It doesn't occur in 2.7.0. Updating the managed object directly works fine in 2.8.0.

Thanks. I'm going to mark this as a bug and put it in our list of things to do.

Related to #4926.

Same problem here since 2.8.0 update.

Hi, guys!
It is not working for optional property.
Realm 2.8.2
class RealmObject: Object {
  dynamic var id = 0
  dynamic var attribute: String?
  dynamic var age = RealmOptional<Int>()

  override static func primaryKey() -> String? {
    return "id"
  }
}

let realmObject = RealmObject()
realmObject.age.value = 30
try! Realm().add(realmObject, update: true)

let realmObject = RealmObject()
realmObject.age.value = nil
try! Realm().add(realmObject, update: true)

Guys you have to fix create( type:* value:* update: true) for nil RealmOptional properties also

Fixing the create or update case of this bug falls under #5042.
@tgoyne, with #5046 merged is there anything else you are aware of that needs to be done for this issue?

Closing as #5042 appears to have sufficiently addressed this.

#5042 is a different problem, I believe (the two APIs use different codepaths). I'll confirm this is fixed this week and close or address as appropriate.

I went back and checked; the linked PR indeed ensures that the proper behavior occurs for this case.

@austinzheng is this resolved in 3.0.0?
Can I confirm how one might distinguish between setting a property to nil and not touching a property at all when updating an existing object in store? As I'd like both behaviour when using optionals...

We now set nil on a property if nil is specified. If you want to not touch the property at all you'll have to retrieve the object and set its properties explicitly.

@austinzheng how about any difference between using nil as default value?
@objc dynamic var fitting: Fitting?
@objc dynamic var fitting: Fitting? = nil

Those two declarations give the same behavior since in Swift an optional property is automatically initialized to nil unless otherwise specified.


feat(sdk/go): implement mysql SDK for TinyGo

feat(sdk/go): implement mysql SDK for TinyGo

Test spin build error. See:
Building component tinygo-mysql with `tinygo build -target=wasi -gc=leaking -o main.wasm main.go`
# github.com/fermyon/spin/sdk/go/mysql
../../../../../../opt/homebrew/Cellar/tinygo/0.30.0/lib/clang/include/stdbool.h:20:14: undefined: C._Bool
Error: Build command for component tinygo-mysql failed with status Exited(1)

I create a issue on Tinygo https://github.com/tinygo-org/tinygo/issues/3926 .

Thanks for this, and for flagging the upstream problem to the TinyGo folks - looks like they already have a fix so hopefully in the next version...

@adamreese PTAL

@Patrick0308 I think a rebase will take care of the weird wit-bindgen compilation errors in CI.  Thanks for sticking with this!

@adamreese @itowlson I replaced C._Bool to bool then testing the program went smoothly. So we don't need to wait util https://github.com/tinygo-org/tinygo/issues/3926  is released.


Use official Grafana image and provide OpenShift template

Instead of relaying on this project for providing a Grafana image on Kubernetes and OpenShift (with a template), it could be worth to try the official Grafana image and providing OpenShift template from Strimzi repo.

The investigation of the official Grafana image has been done by @serrss in #318 ... the image doesn't work properly on OpenShift for us due to permission issues.
In the same PR we also decided that since Prometheus and Grafana are not official deliveries for us, we should not maintain the templates for them and have just simple YAML files. This issue can be closed.


feat: support install for source options

🔗 Linked issue
#51
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This adds a shortcut for install giget option. A layer extended with [name, { install: true }] will install it's dependencies
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

it looks like it is going in an infinite loop?
I am using nuxt to extend some layers:
  extends: [
    [
      `github:username/repo/path1#develop`,
      { install: true }
    ],
    [
      `github:username/repo/path2#develop`,
      { install: true }
    ],
    [
      `github:username/repo/path3#develop`,
      { install: true }
    ],
  ],

when i run install it throws this:
(node:37546) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 keypress listeners added to [Socket]. Use emitter.setMa…
│ (Use `node --trace-warnings ...` to show where the warning was created)
│ (node:37546) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 end listeners added to [Socket]. Use emitter.setMaxList…
│ (node:37546) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Socket]. Use emitter.setMaxLi…

@Marian-Calin-Stroescu-Fiskars Would you please open a new issue with reproduction I can check? 🙏🏼


Update README to use correct unpkg URL

The README currently links to file passwordless.min.js which is not found.  The dist directory contains webauthn.min.js and the samples use webauthn files.

Thanks for the fix


Icon Not Showing with the latest kivy2.0.0

kivymd Icons are not showing both on desktop and mobile with the latest of kivy and also the master branch too and I also discovered it uses pygame as the Window Provider for now
OS: Pop_OS
python version: python3.7
kivymd version: master

@kengoon It seems to me that this is a problem of dependencies that you installed incorrectly. One way or another, this is unlikely to be related to the KivyMD library.

@HeaTTheatR ya it is not related to kivymd the problem is from kivy it self. you can install the master branch of kivy and check it out your self. Why I posted this here is because it only affects KivyMD and Kivy is not in the right position to find a quick fix

We need to see the logs, change your loggin to debug or below to see if there's anything missing. In the worst case, you would need to set it to trace

Kivy Went back to sdl2 Window provider and all icons are now showing, it was a problem of pygame window provide. You can close this issue if you want


In the new version of the 'tabbar' on android does not work the 'tabBarPosition' property

Version
Tell us which versions you are using:

react-native-router-flux v4.0.0-beta.19
react-native v0.46.4

Expected behaviour
When specifying the " tabBarPosition='bottom' " property, the tabbar should be displayed at the bottom.
Actual behaviour
Is displayed at the top.
In the previous version it works correctly

+1

+1

+1

+1

Please check latest master

@aksonov  can you update the package version also pls

@sachithamadhupa Let's make sure that it fixes issue, could you check?

@aksonov  yes I checked it, its working :)

Waiting for new npm version, thanks

In beta20 default tabBar position for iOS is broken. TabBar is on top by default.

@davojan Thanks, check beta21


[2012-06-26] Deprecate InlineFormAction

created by: @chillu (ischommer)
created at: 2012-06-26
original ticket: http://open.silverstripe.org/ticket/7570

Its using behaviour.js, and is generally not very useful.
The original intent was to avoid having those buttons placed
in the CMS actions bottom bar, which is a very tightly coupled use case,
which happens to be no longer necessary in 3.0.
In fact, the implementation is just plain broken, since its rewriting links to a non-existant "admin-custom" URL.
It's a shame that we've missed that for 3.0...
The only place its used in core is Folder_UnusedAssetsField,
but that class in turn is not used anywhere else at the moment (not sure if thats intentional, or just a missing feature rewrite from 2.4 to 3.0).
Maybe we just delete the implementation and make it extend FormAction for now?

Maybe in 4.0.

Replaced in https://github.com/silverstripe/silverstripe-framework/issues/6099


SSLError: [SSL] PEM lib (_ssl.c:2603) when I want to connect to a server with TLS

Hi,
I can't connect myself to an Apple server using requests.
I can connect myself to this same server using openssl directly or using socket directly
For instance, I'm doing that in such way with openssl
openssl s_client -CAfile GeoTrust_Global_CA.pem -connect api.push.apple.com:443
My code is pretty basic:
s = requests.session()     s.cert = "GeoTrust_Global_CA.pem"     s.port = 443     url = 'https://api.push.apple.com'     r = s.get(url)

@darakt You're using the cert argument, but you want to be using the verify argument.

requests.get('url', verify=True) is causing this issue for me.


Update Riot logo

lgtm, thanks

actually, that logo seems really fuzzy and weirdly resampled... might be better to rasterise down the svg at higher res and then downscale in the browser for poor-man's retina support?

Yeah, I just stole the already-resized-by-script icon of matching size from the riot-web repo, so we'd at least have the new colours... anyway, that's why it's fuzzy and such.
Will try for something nicer like you suggest tomorrow.

@jryans I haven't looked in detail at where the asset is used, but I traced what you checked in here and put these together:
@1x

@2x

(Dropping these here rather than directly checking in as I don't have the repo set up & figured you'd want to sanity check before pushing.)

Okay, updated with Nad's icons. New screenshot posted to the top comment here.

This has been deployed.


Table component - specify selected row

What prop one need to use to specify selected row?

Hello @code-by ,
Thank you for your interest in using our product.
Can you please be more detailed in your question?
First of all, i would like to know which table are we speaking of (a simple link to the page in question would do the trick).
Best,
Manu

import Table from 'components/Table/Table';
...
const MyComponent = ({data}) => (
  <Table
    tableData={data}
  />
);

Hello again @code-by ,
I just figured out what you were asking.
Unfortunately our demo Table is just for rendering data, and not for multiple purpose.
If you want to add more props to it, then you'll have to implement them, our product comes as is.
Or maybe someone from our community will help you with this.
Best,
Manu


Incident - reportedBy should store the currently logged in user id

🐛 Bug Report
Report incident is currently hardcoded to set reportedBy to some user instead of the currently logged in user's id. This needs to be corrected to user the current user id from the redux store.
To Reproduce

Access staging https://staging.hospitalrun.io/
Report an incident
View the list of incidents and notice that the reported by field shows 'some user'

Expected behavior

The incident.reportedBy should be the currently logged in user.id at the time the incident is reported
The list of incidents should display the user.fullName based on the incident.reportedBy

Notes

See src/shared/components/navbar/Navbar.tsx on how to access the user from the store

Your Environment

node version: 6,8,10
fastify version: >=1.0.0
os: Mac, Windows, Linux
any other relevant information

@blestab @jackcymeye @mormme @thekappa @fox1t Hi, this is James from Stanford Code the Change! I'd like to be assigned to this task

@blestab @jackcymeye @mormme @thekappa @fox1t Hi, this is James from Stanford Code the Change! I'd like to be assigned to this task

@jameszheng405  it's yours!

@jameszheng405  it's yours!

Hi @jameszheng405,
How is this coming along? Feel free to check this PR https://github.com/HospitalRun/hospitalrun-frontend/pull/2544 for ideas

Hi @jameszheng405,
How is this coming along? Feel free to check this PR https://github.com/HospitalRun/hospitalrun-frontend/pull/2544 for ideas

Hi @blestab ,
I'm able to display the user id now, just working on displaying the full name in the table. I'll be meeting with Stanford CTC tomorrow to discuss this. Thanks for checking in!

Hi @blestab ,
I'm able to display the user id now, just working on displaying the full name in the table. I'll be meeting with Stanford CTC tomorrow to discuss this. Thanks for checking in!

Hi @blestab ,
I'm able to display the user id now, just working on displaying the full name in the table. I'll be meeting with Stanford CTC tomorrow to discuss this. Thanks for checking in!

Awesome! Thanks

Hi @blestab ,
I'm able to display the user id now, just working on displaying the full name in the table. I'll be meeting with Stanford CTC tomorrow to discuss this. Thanks for checking in!

Awesome! Thanks

@blestab
After taking a look at PR #2544, I noticed that fullName is statically defined and used to test the value of requestedByFullName. I was wondering if this might be inefficient in case a user decides to change their name and the value of fullName would then have to be changed everywhere? I’m thinking it would be better to always be able to access the current fullName through the user id, which never changes. However, since that information isn’t globally available yet, I would like to propose an extractFullName function which will be scaffolded later when that functionality is there.

@blestab
After taking a look at PR #2544, I noticed that fullName is statically defined and used to test the value of requestedByFullName. I was wondering if this might be inefficient in case a user decides to change their name and the value of fullName would then have to be changed everywhere? I’m thinking it would be better to always be able to access the current fullName through the user id, which never changes. However, since that information isn’t globally available yet, I would like to propose an extractFullName function which will be scaffolded later when that functionality is there.

that's a good point. currently doesn't look like we have functionality to change much about user, but is good for if/when user info editing is implemented for the future..
following + will make changes as necessary for #2544

that's a good point. currently doesn't look like we have functionality to change much about user, but is good for if/when user info editing is implemented for the future..
following + will make changes as necessary for #2544

Hi is this issue fixed in production?

@sshikhar1234 which production?

I mean like in main release. Is this issue fixed or its open?

No, if this issue is still open, I don't think so. Why?

i would like to work on this one. Is it still Open?

yep @bottercode

I have fixed the issue, new to this so can you just tell me if you have received the pull request i made?

@bottercode I don't see any new PR https://github.com/HospitalRun/hospitalrun-frontend/pulls. Can you link it?

Sorry for the very late response here it is @tehKapa  https://github.com/bottercode/hospitalrun-frontend/commit/d327ac1e892b766f74ec6d9e76b41faad0fc433b

@bottercode you need to do a PR in hospitalrun/hospitalrun-frontend and not on your repo

Is it visible now? @tehKapa

Is it visible now? @tehKapa

No. You can see all open PR here https://github.com/HospitalRun/hospitalrun-frontend/pulls

As this issue is currently open, has it been fixed? Or could I claim this issue and attempt it myself?

Is this issue still open? I'd like to contribute.

@tehKapa Could you please assign me to this issue?

@tehKapa Can you please review the PR https://github.com/HospitalRun/hospitalrun-frontend/pull/2987 ?

@tehKapa, can you please review the PR https://github.com/HospitalRun/hospitalrun-frontend/pull/2988


fix: use schedule_wrap to avoid text_lock

Should fix #183, #182, #178
For the minimal reproduction I used the following minimal.lua
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
	spec = {
		{
			"jmbuhr/otter.nvim",
			dependencies = {
				{
					"nvim-treesitter/nvim-treesitter",
					ensure_installed = {
						"markdown",
					},
				},
			},
			opts = {},
		},
		{
			"neovim/nvim-lspconfig",
			dependencies = {
				{
					"williamboman/mason-lspconfig.nvim",
					dependencies = { "mason.nvim" },
					opts = {
						ensure_installed = { "lua_ls" },
					},
				},
				{
					"williamboman/mason.nvim",
					build = ":MasonUpdate",
					opts = {},
				},
			},
			config = function()
				local lspconfig = require("lspconfig")
				lspconfig.lua_ls.setup({})
			end,
		},
	},
})

vim.api.nvim_create_autocmd("LspAttach", {
	callback = function(args)
		vim.api.nvim_buf_attach(args.buf, false, {
			on_lines = function()
				local method = "textDocument/documentColor"
				local param = { textDocument = vim.lsp.util.make_text_document_params() }
				local clients = vim.lsp.get_clients({ bufnr = args.buf, method = method })
				for _, client in ipairs(clients) do
					client.request(method, param, function() end)
				end
			end,
		})
	end,
})

vim.keymap.set("n", "<F4>", function()
	vim.cmd.edit("/tmp/test.md")
	vim.api.nvim_buf_set_lines(0, 0, -1, true, { "```lua", 'local a = "a"', "```" })
	require("otter").activate()
	vim.defer_fn(function()
		vim.cmd.normal("gg0joa")
	end, 1000)
end)

nvim-lspconfig, mason and mason-lspconfig are simply being used to ease the installation and configuration of lua-ls and have nothing to do with this issue.
Steps:

nvim -u minimal.lua
Wait for lazy.nvim to download the plugins, for nvim-treesitter to install the markdown parser and for mason.nvim to install lua_ls
Press <F4> (the F4 key)

A file /tmp/test.md will be opened with the following text:
```lua
local a = "a"
```

the cursor will be moved to the local a = 'a' line, a new line will be inserted downwards and the text a will be written. This will cause an error without this PR and will work fine with this PR.
The method textDocument/documentColor is being used simply because I first found this error while using cc.nvim

I have been using this for a bit now and no issues so far! :)

Sorry @TheLeoP, I had to revert this for now (in e8c662e1aefa8b483cfba6e00729a39a363dcecc) as it introduced a regression in the interaction with other language servers attached to the main buffer (https://github.com/jmbuhr/otter.nvim/issues/194). Will try to think of something.


[INFRA] [TEST] failing tests in CI

OK this is a REALLY dirty temporary hack where the tests return after having run the functions they are supposed to tests but before they actually check the content.
This is basically now just a "smoke test". Better than nothing but it leaves much to be desired.
Incriminated tests:

test_createDataDictionaryBasic
test_createDataDictionaryStim
test_createJsonExtra

Pasting here the content of the failed CI and will reference this in another issue so we know this has to be improved.
See https://github.com/cpp-lln-lab/CPP_BIDS/pull/144/checks?check_run_id=1411109386
failure: /github/workspace/lib/JSONio/jsonread.mex: failed to load: liboctinterp.so.4: cannot open shared object file: No such file or directory
  jsondecode:27 (/github/workspace/lib/bids-matlab/+bids/+util/jsondecode.m)
  test_createDataDictionary>test_createDataDictionaryBasic:57 (/github/workspace/tests/test_createDataDictionary.m)

failure: /github/workspace/lib/JSONio/jsonread.mex: failed to load: liboctinterp.so.4: cannot open shared object file: No such file or directory
  jsondecode:27 (/github/workspace/lib/bids-matlab/+bids/+util/jsondecode.m)
  test_createDataDictionary>test_createDataDictionaryStim:123 (/github/workspace/tests/test_createDataDictionary.m)

failure: /github/workspace/lib/JSONio/jsonread.mex: failed to load: liboctinterp.so.4: cannot open shared object file: No such file or directory
  jsondecode:27 (/github/workspace/lib/bids-matlab/+bids/+util/jsondecode.m)
  test_createJson>test_createJsonExtra:158 (/github/workspace/tests/test_createJson.m)

Originally posted by @Remi-Gau in https://github.com/cpp-lln-lab/CPP_BIDS/issues/144#issuecomment-728795553

New error same problem
failure: fileread: cannot open file
  fileread:37 (/octave/share/octave/5.2.0/m/io/fileread.m)
  jsondecode:27 (/github/workspace/lib/bids-matlab/+bids/+util/jsondecode.m)
  test_createDataDictionary>test_createDataDictionaryBasic:62 (/github/workspace/tests/test_createDataDictionary.m)


Extension deprecated?

Isidor here from the VS Code team 👋
We have noticed that you have not updated your extension for quite some time.
Do you plan to continue working on your extension? Do you feel like it is feature complete? Or is it deprecated?
We currently support deprecated extensions and we could mark your extension as deprecated. What do you think about that option?
Thank you @wholroyd

I responded in https://github.com/microsoft/vscode/issues/150743.

Not deprecated based on response, let's close this as a no-op


Ktarian supporting characters

Ktarians are unusual in that they have 2 fixed species attribute improvements, and 2 from which the player must pick. It doesn't look like the supporting character tool implements this correctly.

Resolved.

The solution allows users to choose from all 4 remaining attributes, rather than limiting to fitness or presence. This may be a result of how the tool works, but I thought it worth noting.


Improve documentation

There have been several emails and bugs filed about dpath's documentation. Apparently there are several users who find it confusing, and even the maintainers have found the documentation frustrating at times.
Let's please link all documentation-related incidents here, so we can get them all knocked out at once.

#42 - The documentation for .values() is right there in the README, but somehow the user missed it. How can we make that more obvious?
#15 - the documentation implies to some people that keys must be 1 character in length.
#38 - Document the globbing syntax

Some of these updates are bugs in the docs, some are enhancements, labeling as both bug and enhancement.

Note that in #15 the answer incorrectly says [a..z] when it should say [a-z], and also doesn't get across that the rules are actually pretty complicated (consider what [] or []a] mean).  So, I think making it very clear that they mean what fnmatch mean is pretty important. (The alternative would be to full document fnmatch syntax—which is especially fun given that there have been a couple of minor changes from 2.6 to 3.7 that you'd have to document.)
Also #80 probably requires a doc change whether it's fixed or not. Obviously replacing fnmatch with not-quite-fnmatch means you can no longer just defer to it for documentation. But leaving it alone means you probably need to at least document the fnmatch way of escaping (with a single-character glob class), and maybe point out why it can't be used for separators.

Blocked by #136


Live Migration doesn't delete the container at source host sometimes.

Ubuntu 16.04.1
lxd 2.4.1
lxc 2.4.1
lxc move cnt dest'nhost:
error: The container is currently running, stop it first or pass --force.
the container was migrated to the destination host and was online, however the destination at source wasn't deleted and was stopped, throwing an error message as above.

Hmm, I've never seen that behavior... The error suggests that something started the container while it was being moved, that or LXD failed to stop it and didn't return an error...
@tych0 any idea?

We could certainly have the delete step pass --force which would fix that, but it'd probably be best to figure out the underlying issue :)

Name: cnt55
Remote: unix:/var/lib/lxd/unix.socket
Architecture: x86_64
Created: 2016/10/13 15:32 UTC
Status: Running
Type: persistent
Profiles: default
Pid: 12975
Ips:
eth0:	inet	<IP_ADDRESS>	cnt55
eth0:	inet6	fe80::216:3eff:fe9a:f6d2	cnt55
lo:	inet	<IP_ADDRESS>
lo:	inet6	::1
Resources:
Processes: 86
Disk usage:
root: 152.59MB
CPU usage:
CPU usage (in seconds): 9098
Memory usage:
Memory (current): 458.81MB
Memory (peak): 4.44GB
Network usage:
eth0:
Bytes received: 2.85GB
Bytes sent: 3.14MB
Packets received: 47315723
Packets sent: 53786
lo:
Bytes received: 0 bytes
Bytes sent: 0 bytes
Packets received: 0
Packets sent: 0
name: cnt55
profiles:

default
config:
volatile.base_image: 82e95c482635b5a1f8ca21bdf704a5e58708b9b3f9ef0ecec492e7c1460436a2
volatile.eth0.hwaddr: 00:16:3e:9a:f6:d2
volatile.eth0.name: eth0
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]'
devices:
eth0:
host_name: cnt55
mtu: "9000"
nictype: bridged
parent: br0
type: nic
mount-ops:
path: /var/work/www
source: /var/work/www
type: disk
root:
path: /
type: disk
ephemeral: false

Is it because of mount entry ?
Mount entry is available on both the source and dest'n host, at the same location on host machine.

And also --force option wasn't defined for move command.
lxc move --help
Usage: Move containers within or in between lxd instances.
lxc move [remote:] [remote:]
Move a container between two hosts, renaming it if destination name differs.
lxc move
Rename a local container.
Options:
--debug  (= false)
    Enables debug mode.
--force-local  (= false)
    Force using the local unix socket.
--no-alias  (= false)
    Ignore aliases when determining what command to run.
--verbose  (= false)
    Enables verbose mode.

Yeah, that's normal. The error you're seeing is coming from an internal call to "lxc delete" which does accept that --force option.

Is there a clean way which can delete the container at source host when migration was successful ?
Doesn't the API pass the force option to lxc delete, when migration was completed ?

The force option is only necessary if the container is running. Since LXD (well CRIU) stops the container during live migration, this shouldn't be necessary at all.
So that's why the fix for this isn't to just change the code to forcefully destroy the source container, but instead to understand why it was still running at that stage.

Did you ^C a previous move command? I've had this happen because the move operation is two distinct steps: a copy and then a delete, and if you ^C the lxc command during the move it doesn't cancel the copy, but also exits and doesn't perform the delete.

Kindof.
Does this signal cause any flags to be set in the container config ?
If I am trying to migrate the same container from dest't to source it still throws the same error.
However new containers built with the same config doesn't throw this error.

Right now ^C does nothing but exit the client. So the container config is not modified, nor is the migration cancelled.

Hmm..may be the container or host issue.. will reopen the issue, if I am able to reproduce again with new container.

I tried today with the debug option set, and the output is as follows on the source host.
DBUG[10-18|09:59:36] Raw response: {"type":"sync","status":"Success","status_code":200,"metadata":{"architecture":"x86_64","config":{"volatile.apply_template":"copy","volatile.base_image":"82e95c482635b5a1f8ca21bdf704a5e58708b9b3f9ef0ecec492e7c1460436a2","volatile.eth0.hwaddr":"00:16:3e:bc:a8:99","volatile.eth0.name":"eth0","volatile.last_state.idmap":"[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]"},"created_at":"2016-10-18T13:58:41Z","devices":{"eth0":{"host_name":"cnt49","mtu":"9000","nictype":"bridged","parent":"br0","type":"nic"},"root":{"path":"/","type":"disk"}},"ephemeral":false,"expanded_config":{"volatile.apply_template":"copy","volatile.base_image":"82e95c482635b5a1f8ca21bdf704a5e58708b9b3f9ef0ecec492e7c1460436a2","volatile.eth0.hwaddr":"00:16:3e:bc:a8:99","volatile.eth0.name":"eth0","volatile.last_state.idmap":"[{"Isuid":true,"Isgid":false,"Hostid":100000,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":100000,"Nsid":0,"Maprange":65536}]"},"expanded_devices":{"eth0":{"host_name":"cnt49","mtu":"9000","nictype":"bridged","parent":"br0","type":"nic"},"mount-ops":{"path":"/var/work/www","source":"/var/work/www","type":"disk"},"root":{"path":"/","type":"disk"}},"last_used_at":"2016-10-18T13:58:57.710624122Z","name":"cnt49","profiles":["default"],"stateful":false,"status":"Running","status_code":103}}
error: The container is currently running, stop it first or pass --force.
According to @stgraber , the container should be stopped before migrating by CRIU.
Doesn't this sound weird ?

Can you post all the of the criu related log files from the dump and restore sides, as well as the lxd.log from both hosts?

Source:
lxd.log:
t=2016-10-18T10:35:52-0400 lvl=info msg="LXD is starting in normal mode" path=/var/lib/lxd
t=2016-10-18T10:35:52-0400 lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored."
t=2016-10-18T10:35:52-0400 lvl=info msg="Default uid/gid map:"
t=2016-10-18T10:35:52-0400 lvl=info msg=" - u 0<PHONE_NUMBER>6"
t=2016-10-18T10:35:52-0400 lvl=info msg=" - g 0<PHONE_NUMBER>6"
t=2016-10-18T10:35:52-0400 lvl=info msg="Starting /dev/lxd handler"
t=2016-10-18T10:35:52-0400 lvl=info msg="Expiring log files"
t=2016-10-18T10:35:52-0400 lvl=info msg="Done expiring log files"
t=2016-10-18T10:35:52-0400 lvl=info msg="LXD is socket activated"
t=2016-10-18T10:35:52-0400 lvl=info msg="REST API daemon:"
t=2016-10-18T10:35:52-0400 lvl=info msg="Pruning expired images"
t=2016-10-18T10:35:52-0400 lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket
t=2016-10-18T10:35:52-0400 lvl=info msg="Done pruning expired images"
t=2016-10-18T10:35:52-0400 lvl=info msg=" - binding TCP socket" socket=<IP_ADDRESS>:8443
t=2016-10-18T10:35:52-0400 lvl=info msg="Updating images"
t=2016-10-18T10:35:52-0400 lvl=info msg="Done updating images"
t=2016-10-18T10:36:14-0400 lvl=info msg="Migrating container" name=cnt49 created=2016-10-18T14:34:58+0000 ephemeral=false used=2016-10-18T14:35:15+0000 statedir=/tmp/lxd_checkpoint_974989473 actionscript=true stop=true
t=2016-10-18T10:36:24-0400 lvl=eror msg="Error collecting checkpoint log file" err="open /tmp/lxd_checkpoint_974989473/dump.log: no such file or directory"
t=2016-10-18T10:36:24-0400 lvl=info msg="Migrated container" name=cnt49 created=2016-10-18T14:34:58+0000 ephemeral=false used=2016-10-18T14:35:15+0000 statedir=/tmp/lxd_checkpoint_974989473 actionscript=true stop=true
Destination:
**lxd.log:
**
t=2016-10-18T10:35:46-0400 lvl=info msg="LXD is starting in normal mode" path=/var/lib/lxd
t=2016-10-18T10:35:46-0400 lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored."
t=2016-10-18T10:35:46-0400 lvl=info msg="Default uid/gid map:"
t=2016-10-18T10:35:46-0400 lvl=info msg=" - u 0<PHONE_NUMBER>6"
t=2016-10-18T10:35:46-0400 lvl=info msg=" - g 0<PHONE_NUMBER>6"
t=2016-10-18T10:35:46-0400 lvl=info msg="Starting /dev/lxd handler"
t=2016-10-18T10:35:46-0400 lvl=info msg="Expiring log files"
t=2016-10-18T10:35:46-0400 lvl=info msg="Done expiring log files"
t=2016-10-18T10:35:46-0400 lvl=info msg="LXD is socket activated"
t=2016-10-18T10:35:46-0400 lvl=info msg="Pruning expired images"
t=2016-10-18T10:35:46-0400 lvl=info msg="REST API daemon:"
t=2016-10-18T10:35:46-0400 lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket
t=2016-10-18T10:35:46-0400 lvl=info msg=" - binding TCP socket" socket=<IP_ADDRESS>:8443
t=2016-10-18T10:35:46-0400 lvl=info msg="Updating images"
t=2016-10-18T10:35:46-0400 lvl=info msg="Done pruning expired images"
t=2016-10-18T10:35:46-0400 lvl=info msg="Done updating images"
t=2016-10-18T10:36:00-0400 lvl=info msg="Deleting container" name=cnt49 created=2016-10-18T14:33:21+0000 ephemeral=false used=2016-10-18T14:33:37+0000
t=2016-10-18T10:36:01-0400 lvl=info msg="Deleted container" name=cnt49 created=2016-10-18T14:33:21+0000 ephemeral=false used=2016-10-18T14:33:37+0000
t=2016-10-18T10:36:22-0400 lvl=info msg="Migrating container" ephemeral=false used=1970-01-01T00:00:00+0000 statedir=/tmp/lxd_restore_082454632 actionscript=false stop=false name=cnt49 created=2016-10-18T14:36:06+0000
t=2016-10-18T10:36:24-0400 lvl=info msg="Migrated container" stop=false name=cnt49 create
t=2016-10-18T10:35:46-0400 lvl=info msg="LXD is starting in normal mode" path=/var/lib/lxd
t=2016-10-18T10:35:46-0400 lvl=warn msg="CGroup memory swap accounting is disabled, swap limits will be ignored."
t=2016-10-18T10:35:46-0400 lvl=info msg="Default uid/gid map:"
t=2016-10-18T10:35:46-0400 lvl=info msg=" - u 0<PHONE_NUMBER>6"
t=2016-10-18T10:35:46-0400 lvl=info msg=" - g 0<PHONE_NUMBER>6"
t=2016-10-18T10:35:46-0400 lvl=info msg="Starting /dev/lxd handler"
t=2016-10-18T10:35:46-0400 lvl=info msg="Expiring log files"
t=2016-10-18T10:35:46-0400 lvl=info msg="Done expiring log files"
t=2016-10-18T10:35:46-0400 lvl=info msg="LXD is socket activated"
t=2016-10-18T10:35:46-0400 lvl=info msg="Pruning expired images"
t=2016-10-18T10:35:46-0400 lvl=info msg="REST API daemon:"
t=2016-10-18T10:35:46-0400 lvl=info msg=" - binding Unix socket" socket=/var/lib/lxd/unix.socket
t=2016-10-18T10:35:46-0400 lvl=info msg=" - binding TCP socket" socket=<IP_ADDRESS>:8443
t=2016-10-18T10:35:46-0400 lvl=info msg="Updating images"
t=2016-10-18T10:35:46-0400 lvl=info msg="Done pruning expired images"
t=2016-10-18T10:35:46-0400 lvl=info msg="Done updating images"
t=2016-10-18T10:36:00-0400 lvl=info msg="Deleting container" name=cnt49 created=2016-10-18T14:33:21+0000 ephemeral=false used=2016-10-18T14:33:37+0000
t=2016-10-18T10:36:01-0400 lvl=info msg="Deleted container" name=cnt49 created=2016-10-18T14:33:21+0000 ephemeral=false used=2016-10-18T14:33:37+0000
t=2016-10-18T10:36:22-0400 lvl=info msg="Migrating container" ephemeral=false used=1970-01-01T00:00:00+0000 statedir=/tmp/lxd_restore_082454632 actionscript=false stop=false name=cnt49 created=2016-10-18T14:36:06+0000
t=2016-10-18T10:36:24-0400 lvl=info msg="Migrated container" stop=false name=cnt49 created=2016-10-18T14:36:06+0000 ephemeral=false used=1970-01-01T00:00:00+0000 statedir=/tmp/lxd_restore_082454632 actionscript=false
DST_migration_restore_2016-10-18T10:36:24-04:00.txt
d=2016-10-18T14:36:06+0000 ephemeral=false used=1970-01-01T00:00:00+0000
SRC_lxc.txt
SRC_migration_restore_2016-10-18T10:35:16-04:00.txt
statedir=/tmp/lxd_restore_082454632 actionscript=false

So you posted restore logs from both, when the source should have a dump log. I think it doesn't because of the race fixed in #2512, but anyway it doesn't look like the dump failed based on your logs, just the log collection failed.
One interesting thing is this in your logs:
        lxc<PHONE_NUMBER>0641.644 INFO     lxc_criu - criu.c:exec_criu:419 - execing: /usr/local/sbin/criu dump --tcp-established --file-locks --link-remap --manage-cgroups=full --ext-mount-map auto --enable-external-sharing --enable-external-masters --enable-fs hugetlbfs --enable-fs tracefs -D /tmp/lxd_checkpoint_016406657 -o /tmp/lxd_checkpoint_016406657/dump.log -vvvvvv --action-script /tmp/lxd_checkpoint_016406657/action.sh -t 9573 --skip-in-flight --freeze-cgroup /sys/fs/cgroup/freezer///lxc/cnt49 --ext-mount-map /dev/console:console --external tty[8800:e] --ghost-limit 268435456
        lxc<PHONE_NUMBER>0650.501 INFO     lxc_confile - confile.c:config_idmap:1500 - read uid map: type u nsid 0 hostid 100000 range 65536
        lxc<PHONE_NUMBER>0650.501 INFO     lxc_confile - confile.c:config_idmap:1500 - read uid map: type g nsid 0 hostid 100000 range 65536
        lxc<PHONE_NUMBER>0650.504 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
        lxc<PHONE_NUMBER>0650.504 DEBUG    lxc_commands - commands.c:lxc_cmd_handler:893 - peer has disconnected
        lxc<PHONE_NUMBER>0650.504 DEBUG    lxc_commands - commands.c:lxc_cmd_get_state:579 - 'cnt49' is in 'RUNNING' state
        lxc<PHONE_NUMBER>0651.130 DEBUG    lxc_start - start.c:signal_handler:342 - container init process exited

I wonder if there's not some similar race to what happened in #2512 that I'm missing.

Any thoughts on why the container is not being deleted at source by looking at the logs ?

Yes, see the above comment :)


'Docker log' command doesn't show logs

Neither docker logs nor kubectl logs contain gitea.log content.  Need to log to stdout & stderr for these commands to work, but instead container logs to file: /app/gitea/log/gitea.log.  Possible solution.

You can set what logs do you want to output to stdout in app.ini


Need modal to render in specific div.

Issue description

components: Modal
reactstrap version #5.0.0
import method umd/csj/es
react version #16.3.2
bootstrap version #4.1.0

What is happening?
Rendering in the DOM but at the very end.
What should be happening?
I need the modal to render over a specific div.  In non-react bootstrap land I can put a modal in an absolutely positioned element and have it render centered over that div.  It seems I cannot specify which div I would like the component rendered in here.  Is it possible to change that?
Thinking out loud - it would be awesome to have a prop called 'container' or something like that -- so that the default behavior can be exactly as you have it- but if there is a specified container, the modal lives there.

I have the same issue.

Hi, If the component is rendered without using React.Portal it will stay wherever is created. However it seems that this will cause issues with the z-index and the overlay behind. What do you think @TheSharpieOne
Regards,
Boyko


Bug in mask_target.py

In some situations, x1, y1, x2, y2 all equal to -2147483648 in mask_target.py, I don't know more information.

Thanks for reporting this bug! Could you provide the sample or the case to reproduce that?


Using WSL not returning expected Selector

Running a simple script using wsl does not return the expected selector.
(async () => {

  'use strict';
  const puppeteer = require('puppeteer');
  let browser = await puppeteer.launch({ headless: true});
  let page = await browser.newPage();
  await page.setUserAgent('Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko)
    Chrome/73.0.3683.75 Safari/537.3');
  await page.goto('https://old.nasdaq.com/symbol/tsla/historicalm');
  let element = await page.$eval('#qwidget_lastsale');
  console.log(element);

})();

Using developer tools on the page delivers the correct element and requesting the entire page is also successful.
let bodyHTML = await page.evaluate(() => document.body.innerHTML)

You probably need to wait for the element to appear, or the page hasn't entirely finished loading yet. Try adding after your goto
const element = await page.waitForSelector('#qwidget_lastsale');
console.log(element);

Also, keep in mind page.$() and page.$eval() are two very different functions.

 const browser = await puppeteer.launch({ headless: false, devtools: true });
 const page = await browser.newPage();
 await page.goto('http://localhost:9967', { waitUntil: 'domcontentloaded' });
 await new Promise((r) => setTimeout(r, 5000));
 console.log(await page.evaluate(
    () => {
      const ls = document.querySelector('[data-testid=app]');
      console.log('ls', ls);
      return ls;
    },
  ));

I tried using waitForSelector and waitForFunction, but kept timing out
with Promise setTimeout and headless false, devtools true, I could observe that puppeteer was blocking the app rendering (in this case anyway)
using the nested console logs I could verify that the console.log inside puppeteer finds the element and returns it correctly
but what comes back from the promise is 'undefined'


HelloWorld not working on brand-new AML Compute Instance

I'm trying to run the HelloWorld example on a brand new Azure Machine Learning Compute Instance, but it is failing:
Commands ran:
git clone https://github.com/microsoft/InnerEye-DeepLearning
cd InnerEye-DeepLearning

# Get LFS working
curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | sudo bash
sudo apt-get install git-lfs
git lfs install
git lfs pull

# Init Conda
conda init bash
conda env create --file environment.yml
conda activate InnerEye

# Run HelloWorld
export PYTHONPATH=`pwd`
python InnerEye/ML/runner.py --model=HelloWorld

The HelloWorld examples fails with:
Setting logging level to 20
2020-11-16T16:38:05Z INFO     rpdb is handling traps. To debug: identify the main runner.py process, then as root: kill -TRAP <process_id>; nc <IP_ADDRESS> 4444
2020-11-16T16:38:05Z INFO     Found class HelloWorld in file /home/azureuser/InnerEye-DeepLearning/InnerEye/ML/configs/segmentation/HelloWorld.py
2020-11-16T16:38:05Z INFO     Creating the default output folder structure.
2020-11-16T16:38:05Z INFO     Running outside of AzureML.
2020-11-16T16:38:05Z INFO     All results will be written to a subfolder of the project root folder.
2020-11-16T16:38:05Z INFO     Run outputs folder: /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld
2020-11-16T16:38:05Z INFO     Logs folder: /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld/logs
2020-11-16T16:38:05Z INFO     Creating the adjusted output folder structure.
2020-11-16T16:38:05Z INFO     Running outside of AzureML.
2020-11-16T16:38:05Z INFO     All results will be written to a subfolder of the project root folder.
2020-11-16T16:38:05Z INFO     Run outputs folder: /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld
2020-11-16T16:38:05Z INFO     Logs folder: /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld/logs
2020-11-16T16:38:05Z INFO     extra_code_directory is unset
Setting logging level to 20
Setting up logging with level 20 to file /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld/logs/stdout.txt
2020-11-16T16:38:09Z INFO     Setting multiprocessing start method to 'fork'
2020-11-16T16:38:09Z INFO     Model training will use the local dataset provided in /home/azureuser/InnerEye-DeepLearning/Tests/ML/test_data
2020-11-16T16:38:09Z INFO
Arguments:
	__center_size_param_value: None
	__dataset_data_frame_param_value: None
	__inference_stride_size_param_value: None
	__largest_connected_component_foreground_classes_param_value: None
	__min_l_rate_param_value: 0
	__model_category_param_value: ModelCategory.Segmentation
	__model_name_param_value: HelloWorld
	__overrides_param_value: None
	__use_gpu_param_value: False
	_architecture_param_value: UNet3D
	_class_weights_param_value: [0.02, 0.49, 0.49]
	_colours_param_value: [(130, 183, 14), (238, 127, 26)]
	_comparison_blob_storage_paths_param_value: None
	_crop_size_param_value: (64, 64, 64)
	_datasets_for_inference: None
	_datasets_for_training: None
	_epochs_to_test_param_value: None
	_feature_channels_param_value: [4]
	_file_system_config_param_value: <DeepLearningFileSystemConfig DeepLearningFileSystemConfig00010>
	_fill_holes_param_value: [True, True]
	_ground_truth_ids_display_names_param_value: ['region', 'region_1']
	_ground_truth_ids_param_value: ['region', 'region_1']
	_image_channels_param_value: ['channel1', 'channel2']
	_instance__params : {}
	_l_rate_multi_step_milestones_param_value: None
	_level_param_value: 50
	_local_dataset_param_value: /home/azureuser/InnerEye-DeepLearning/Tests/ML/test_data
	_local_weights_path_param_value: None
	_mask_id_param_value: mask
	_multiprocessing_start_method_param_value: MultiprocessingStartMethod.fork
	_name_param_value : HelloWorld00008
	_norm_method_param_value: PhotometricNormalizationMethod.CtWindow
	_num_dataload_workers_param_value: 0
	_num_epochs_param_value: 2
	_param_watchers   : {}
	_save_start_epoch_param_value: 1
	_save_step_epochs_param_value: 1
	_slice_exclusion_rules_param_value: []
	_start_epoch_param_value: 0
	_summed_probability_rules_param_value: []
	_tail_param_value : None
	_test_crop_size_param_value: (64, 64, 64)
	_test_diff_epochs_param_value: 1
	_test_start_epoch_param_value: 2
	_test_step_epochs_param_value: 1
	_train_batch_size_param_value: 2
	_use_mixed_precision_param_value: True
	_window_param_value: 200
	initialized       : True
	param             : <param.parameterized.Parameters object at 0x7f8f12cf0518>

2020-11-16T16:38:09Z INFO
2020-11-16T16:38:09Z INFO     **** STARTING: Model training **********************************************************************
2020-11-16T16:38:09Z INFO
2020-11-16T16:38:09Z INFO     Train: 3, Test: 1, and Val: 2. Total subjects: 6
2020-11-16T16:38:09Z INFO
2020-11-16T16:38:09Z INFO     **** STARTING: Visualizing the effect of sampling random crops for training ************************
2020-11-16T16:38:09Z INFO
2020-11-16T16:38:09Z INFO     Processing dataset (name=None)
2020-11-16T16:38:09Z INFO     Processing sample: 1
2020-11-16T16:38:11Z INFO
2020-11-16T16:38:11Z INFO     **** FINISHED: Visualizing the effect of sampling random crops for training after 2.21 seconds *****
2020-11-16T16:38:11Z INFO
2020-11-16T16:38:11Z INFO     Starting to read and parse the datasets.
2020-11-16T16:38:11Z INFO     Processing dataset (name=None)
2020-11-16T16:38:11Z INFO     Processing dataset (name=None)
2020-11-16T16:38:11Z INFO     Creating the data loader for the training set.
2020-11-16T16:38:11Z INFO     Creating the data loader for the validation set.
2020-11-16T16:38:11Z INFO     Finished creating the data loaders.
2020-11-16T16:38:11Z INFO     Writing model summary to: logs/model_summaries/model_log001.txt
Attempted to log scalar metric LoggingColumns.NumTrainableParameters:
506139
2020-11-16T16:38:11Z INFO     Making no adjustments to the model because no GPU was found.
2020-11-16T16:38:12Z INFO     Models are saved at /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld/checkpoints
2020-11-16T16:38:12Z INFO     Starting training
2020-11-16T16:38:12Z INFO     Starting epoch 1
2020-11-16T16:38:13Z INFO     Loaded the first minibatch of training data in 1.29 sec.
2020-11-16T16:38:14Z INFO     Epoch 1 training took 2.84 sec, of which waiting for next minibatch took 1.34 sec total. 2 minibatches in total.
2020-11-16T16:38:15Z INFO     Loaded the first minibatch of validation data in 0.09 sec.
2020-11-16T16:38:15Z INFO     Epoch 1 validation took 0.46 sec, of which waiting for next minibatch took 0.09 sec total. 1 minibatches in total.
2020-11-16T16:38:15Z INFO     Saved model checkpoint for epoch 1 to /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld/checkpoints/1_checkpoint.pth.tar
2020-11-16T16:38:15Z INFO     Starting epoch 2
2020-11-16T16:38:15Z INFO     Loaded the first minibatch of training data in 0.08 sec.
2020-11-16T16:38:17Z INFO     Epoch 2 training took 1.56 sec, of which waiting for next minibatch took 0.14 sec total. 2 minibatches in total.
2020-11-16T16:38:17Z INFO     Loaded the first minibatch of validation data in 0.09 sec.
2020-11-16T16:38:17Z INFO     Epoch 2 validation took 0.45 sec, of which waiting for next minibatch took 0.09 sec total. 1 minibatches in total.
2020-11-16T16:38:17Z INFO     Saved model checkpoint for epoch 2 to /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld/checkpoints/2_checkpoint.pth.tar
2020-11-16T16:38:17Z INFO     Finished training
2020-11-16T16:38:17Z INFO
2020-11-16T16:38:17Z INFO     **** FINISHED: Model training after 8.68 seconds ***************************************************
2020-11-16T16:38:17Z INFO
Attempted to log scalar metric Train epochs:
2
2020-11-16T16:38:17Z INFO     Using checkpoints from current run for epoch 2.
2020-11-16T16:38:17Z INFO
2020-11-16T16:38:17Z INFO     **** STARTING: Registering default model ***********************************************************
2020-11-16T16:38:17Z INFO
2020-11-16T16:38:17Z INFO     Copying folder for registration: /home/azureuser/InnerEye-DeepLearning/InnerEye
2020-11-16T16:38:17Z INFO     Copying file for registration: /home/azureuser/InnerEye-DeepLearning/setup.py to setup.py
2020-11-16T16:38:17Z INFO     Copying file for registration: /home/azureuser/InnerEye-DeepLearning/mypy_runner.py to mypy_runner.py
2020-11-16T16:38:17Z INFO     Copying file for registration: /home/azureuser/InnerEye-DeepLearning/score.py to score.py
2020-11-16T16:38:17Z INFO     Copying file for registration: /home/azureuser/InnerEye-DeepLearning/conftest.py to conftest.py
2020-11-16T16:38:17Z INFO     Copying file for registration: /home/azureuser/InnerEye-DeepLearning/outputs/2020-11-16T163805Z_HelloWorld/checkpoints/2_checkpoint.pth.tar to checkpoints/2_checkpoint.pth.tar
2020-11-16T16:38:17Z INFO     Registering the model on the workspace.
2020-11-16T16:38:17Z INFO     Could not load the run context. Logging offline
2020-11-16T16:38:17Z WARNING  Unable to retrieve the key for the Service Principal authentication (expected in environment variable 'APPLICATION_KEY' or YAML). Switching to interactive login.
2020-11-16T16:38:17Z ERROR    Model training/testing failed. Exception: 'list' object has no attribute 'subscription_id'
Traceback (most recent call last):
  File "InnerEye/ML/runner.py", line 386, in run_in_situ
    self.create_ml_runner().run()
  File "/home/azureuser/InnerEye-DeepLearning/InnerEye/ML/run_ml.py", line 317, in run
    best_epoch = self.run_inference_and_register_model(checkpoint_handler, ModelProcessing.DEFAULT)
  File "/home/azureuser/InnerEye-DeepLearning/InnerEye/ML/run_ml.py", line 339, in run_inference_and_register_model
    self.register_model_for_epoch(checkpoint_paths, model_description, model_proc)
  File "/home/azureuser/InnerEye-DeepLearning/InnerEye/ML/run_ml.py", line 512, in register_model_for_epoch
    model_proc=model_proc)
  File "/home/azureuser/InnerEye-DeepLearning/InnerEye/ML/run_ml.py", line 555, in register_segmentation_model
    workspace=self.azure_config.get_workspace(),
  File "/home/azureuser/InnerEye-DeepLearning/InnerEye/Azure/azure_config.py", line 226, in get_workspace
    resource_group=self.resource_group)
  File "/anaconda/envs/InnerEye/lib/python3.7/site-packages/azureml/core/workspace.py", line 566, in get
    subscription_id, auth=auth, resource_group=resource_group)
  File "/anaconda/envs/InnerEye/lib/python3.7/site-packages/azureml/core/workspace.py", line 645, in list
    subscription_id = subscription_tuple.subscription_id
AttributeError: 'list' object has no attribute 'subscription_id'

Somehow, it looks like it is trying to connect to the AML workspace of the Compute Instance, even though I have not configured anything. Would be to understand why this is happening, judging from the main README, this should not happen. Problem can be easily recreated with the provided commands above.
Thanks
Clemens

Looks like when I edit InnerEye-DeepLearning/InnerEye/settings.yml and outcomment application_id, then it works... however, this seems like weird "out of the box" behaviour...

Hi Clemens, smells like a bug indeed... For a repro, can you confirm how your settings.yml looks like? Did you modify it from what's the the github repo?

@csiebler Please confirm if the latest code as of this morning still exhibits the problem.

Sorry @ant0nsc, wasn't able to test it yesterday, but just gave it a quick try on a clean checkout and it works as expected:
2020-11-18T13:20:11Z INFO     Running outside of AzureML.
...
2020-11-18T13:21:56Z WARNING  Couldn't register model in offline mode

Thanks for fixing this so quickly!


Tried to register two views with the same name

Bug
I tried to add the picker, the compilation is fine, but when the app is open appears a red screen with the message:
Tried to register two views with the same name AndroidDropdownPicker
Update: I also use Native base in the project
Can you help me please?

Environment info
React Native Environment Info:
System:
OS: Linux 4.15 Ubuntu 18.04.2 LTS (Bionic Beaver)
CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Memory: 696.37 MB / 7.68 GB
Shell: 4.4.19 - /bin/bash
Binaries:
Node: 8.9.0 - ~/.nvm/versions/node/v8.9.0/bin/node
Yarn: 1.15.2 - /usr/bin/yarn
npm: 5.5.1 - ~/.nvm/versions/node/v8.9.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 20, 22, 23, 25, 26, 27, 28
Build Tools: 23.0.1, 25.0.1, 25.0.2, 25.0.3, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.3, 28.0.3
System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64
IDEs:
Android Studio: 3.4 AI-183.54<IP_ADDRESS>52501
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.9 => 0.59.9
npmGlobalPackages:
react-native-cli: 2.0.1

React native info output:
 // Tried to register two views with the same name AndroidDropdownPicker

Library version: 0.59.9

+1

Im facing this error too, this error seems to be related with the dependencies, there is probably a dependency working with the picker of react-native.
Any idea about how to fix it @jainkuniya ?

Hi @danieljgp2, thanks for the report. Will look into it. It will  be great if you could share some code snippet, through which it is easily reproducible

@jainkuniya which react native version are you using as a dependecy ? i dont know if the problem is related to any dependecy of my project or any dependency of the library but im pretty sure that problem is related with the changes of RN version after 0.59 and the deprecation of the Picker.

I ran into this issue. For me it was caused by a wrong import on my project, which was looking for react-native Picker. But what I noticed is that even on react-native 0.61.2 package, this PR was not included. Maybe it's fixed in the new version (0.61.3)

Any news on this? I have the same problem and cannot get rid of it :/ @sofiageo How did you manage to figure out where offending react-native Picker import was? I check my whole app and there are no usages of Picker. Tried to search in node_nodules to check if some lib uses it but no luck

Any news on this? I have the same problem and cannot get rid of it :/ @sofiageo How did you manage to figure out where offending react-native Picker import was? I check my whole app and there are no usages of Picker. Tried to search in node_nodules to check if some lib uses it but no luck

It was easy for me because I only had 2 imports of Picker. How are you searching in node_modules? If it is a multi-import from react-native you will have to only search for the word Picker.

Is this bug still exists??

@chakrihacker Probably it does, the bug is caused when a dependency imports the picker from react-native and you import the picker from react-native-community/picker

@danieljgp2 The Android native view name is changed to RNCPicker from RCTPicker but previous versions have name RCTPicker. I think by updating dependency this issue will be solved.

+1
Library version: 0.59.9

I have same issue.
"react-native": "0.62.2",
"@react-native-community/picker": "^1.3.0",
please solve this proble

Is this happening in new rn versions?

Is this happening in new rn versions?

yes , i am using   "@react-native-community/picker": "^1.3.0", showing 'Invariant Violation'

I found why this error occurs.

I found why this error occurs.

Is there any required field we are missing?

Can you share your package.json file?

In my case, I used @react-native-community/picker": "^1.3.0   and   "react-native-google-places-autocomplete": "^1.4.1" in my project.
"react-native-google-places-autocomplete": "^1.4.1" used picker from react-native.
so, occured this error.
Perhaps, there are another pakage using picker from react-native  like this in your project.

+1

@orion151  How did you get rid of this?

@danieljgp2 The Android native view name is changed to RNCPicker from RCTPicker but previous versions have name RCTPicker. I think by updating dependency this issue will be solved.

how to update dependency ?

Is this happening in new rn versions?

yes i am using RN 0.62 app is not running and getting crashed,
and also using native base 2.13.12 version and rn picker  ver 1.3.0

On my code setup...
 <Picker
  selectedValue={formik.values.gender}
  accessibilityLabel={'gender'}
  onValueChange={(itemValue, itemIndex) => {
    formik.setFieldValue('gender', itemValue);
  }}>
  <Picker.Item label="Male" value="MALE" />
  <Picker.Item label="Female" value="FEMALE" />
</Picker>

Issue is related to field accessibilityLabel... If key is setup with any value = err!

Seeing this as well
"@react-native-community/picker": "^1.3.0",
"react-native-google-places-autocomplete": "^1.4.1",
Any fixes?

if anyone still has this issue, make sure that you don't use "Picker" from an other package in my case it was "styled-components"

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

could you attach a screenshot of your solution ?

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

could you attach a screenshot of your solution ?

PS: I use functions to render the elements so if you use class to render, you should realize that "onValueChange" and "selectedValue" work diferent.

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

could you attach a screenshot of your solution ?

PS: I use functions to render the elements so if you use class to render, you should realize that "onValueChange" and "selectedValue" work diferent.

I am using class component and using a single dropdown, still getting error. Then i added accessibility as you suggested, still getting same error

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

could you attach a screenshot of your solution ?

PS: I use functions to render the elements so if you use class to render, you should realize that "onValueChange" and "selectedValue" work diferent.

I am using class component and using a single dropdown, still getting error. Then i added accessibility as you suggested, still getting same error

If your error like me is "Tried to resgister two views with the same name AndroidDropdowPicker" like above in screenshoot uploaded by @sislovesmedotcom, you should have at least 2 Pickers because this error is about having the same name (accessibilityLabel) for two or more Pickers. Make sure if you have only one Picker in all Project or atributte diferents values to accessibilityLabel in case you have more than one dropdown. The reason why you have to attibute diferents values to accessibilityLabel is because react native attribute a default value that is equal for every Pickers.

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

could you attach a screenshot of your solution ?

PS: I use functions to render the elements so if you use class to render, you should realize that "onValueChange" and "selectedValue" work diferent.

I am using class component and using a single dropdown, still getting error. Then i added accessibility as you suggested, still getting same error

If your error like me is "Tried to resgister two views with the same name AndroidDropdowPicker" like above in screenshoot uploaded by @sislovesmedotcom, you should have at least 2 Pickers because this error is about having the same name (accessibilityLabel) for two or more Pickers. Make sure if you have only one Picker in all Project or atributte diferents values to accessibilityLabel in case you have more than one dropdown. The reason why you have to attibute diferents values to accessibilityLabel is because react native attribute a default value that is equal for every Pickers.

As soon as i import Picker it show error even if i am not using a single drop-down.  I think problem lies within the npm package because i get this error just after importing. I am using RN 0.62. Hence it supports autolinking but after getting error several times i thought may be issue is due to bad linking hence tried manual linking. But it didn't help

I have 3 Pickers in one screen and I solve the same problem as you by adding accessibilityLabel={'pickername'} in all 3 Pickers, with diferent values.

But what when we have to show picker item dynamically through api...

You should use "accessibilityLabel={'pickername'}" in Picker atributes and generate picker items dinamycally unless you have to generate picker dinamically as well.

could you attach a screenshot of your solution ?

PS: I use functions to render the elements so if you use class to render, you should realize that "onValueChange" and "selectedValue" work diferent.

I am using class component and using a single dropdown, still getting error. Then i added accessibility as you suggested, still getting same error

If your error like me is "Tried to resgister two views with the same name AndroidDropdowPicker" like above in screenshoot uploaded by @sislovesmedotcom, you should have at least 2 Pickers because this error is about having the same name (accessibilityLabel) for two or more Pickers. Make sure if you have only one Picker in all Project or atributte diferents values to accessibilityLabel in case you have more than one dropdown. The reason why you have to attibute diferents values to accessibilityLabel is because react native attribute a default value that is equal for every Pickers.

As soon as i import Picker it show error even if i am not using a single drop-down. I think problem lies within the npm package because i get this error just after importing. I am using RN 0.62. Hence it supports autolinking but after getting error several times i thought may be issue is due to bad linking hence tried manual linking. But it didn't help

I assume you import  "@react-native-community/picker" because the same problem as I, receiving a warning telling that Picker will be descontinued from react-native. I installed this library and I didn't need to  linking manually. Then became this error and I fixed by implement the solution  that I shared here.
So, my advice to you is reinstall the library and check if you are getting that error yet.

Finally i found my fixes, I am using styled component in my project, hence to customize picker I used  picker into styled to add styling

Finally i found my fixes, I am using styled component in my project, hence to customize picker I used picker into styled to add styling

After removing this, i get rid of error

I'm glad you fixed the error.
I wish you a good work and nice coding.

I'm using native-base
route : node_modules/native-base/basic/Picker.js
so i navigate to picker component in it and changed the import picker from 'react-native' to '@react-native-community/picker'
and everything works fine for me
before

after

+1

Fixed for me:
Remove import {Picker} from '@react-native-community/picker';
And use import { Picker } from 'react-native

@haocse the issue comes when we use { Picker } from @react-native-community/picker
With react-native this issue doe snot arise. But with react-native does the {Picker} work in iOS ?

@mrinal-roy-au2 Yes, iOS app works, this problem happens on the Android app

@haocse Picker in React-Native is deprecated. And they are suggesting this one. So need to sort this out within it.

Same issue here. using import { Picker } from 'react-native' is not a solution as suggested by @haocse

anybody found any solution except importing from RN!

+1

Fixed for me:
Remove import { Picker } from '@react-native-community/picker';
And use import { Picker } from 'react-native'

Same Here.
Is there any solution?
I think my error comes from Picker from @react-native-community/picker and react-native-country-picker-modal

May be you all still are using Picker from 'react-native' somewhere in your project.
Be sure to not import from 'react-native'
Even I can use {Picker} from '@react-native-community/picker' inside styled-components this way:
const MyPicker = styled(Picker)...
This was my case.

In my case, I used @react-native-community/picker": "^1.3.0 and "react-native-google-places-autocomplete": "^1.4.1" in my project.
"react-native-google-places-autocomplete": "^1.4.1" used picker from react-native.
so, occured this error.
Perhaps, there are another pakage using picker from react-native like this in your project.

Makes sense, but could you please help to understand that how we can know exactly which dependency is in clash with the picker library and how to solve the issue.

For now, I have started using Picker from native base library and the issue appears fixed for me albeit few design issue I needed to address in such.

I am also facing the same issue may be for temporary basis I will use it from the react-native or native base. I am using only one picker in one of my components and the moment I import it from '@react-native-community/picker' it throws that error.
Anyways, if anybody come across the solution, please please let us know.

So, I ran into this issue and got it working by changing the name of AndroidDropdownPicker to RNCAndroidDropdownPicker, did the same for dialogpicker.
I opened up a PR for the changes, you can see them here: https://github.com/react-native-community/react-native-picker/pull/99

In my case I had 2 versions in yarn.lock
Added
"resolutions": {
    "@react-native-community/picker": "^1.8.0"
  },

to package.json to fix this

In my case, here is the way I found to temporarily solve the problem. It is obviously not the best way, but it was the one I found at the time.
https://github.com/GeekyAnts/NativeBase/issues/3114#issuecomment-706439559

"@react-native-community/picker": "^1.8.1", same issue.

Yo tenía el mismo problema. Lo solucione desinstalando react-native-picker-select. Esté tiene conflicto con native-base.

We are importing two pickers in one scene, made sure to only import from @react-native-community/picker and not "react-native" and tried the trick with adding accessibility labels but I still get this error.
Can someone help with this as we currently have a broken app because of this.

In my case I had 2 versions in yarn.lock
Added
"resolutions": {
    "@react-native-community/picker": "^1.8.0"
  },

to package.json to fix this

A similar approach solved my case within Expo 40 and for datetimepicker, not picker:
	"resolutions": {
		"@react-native-community/datetimepicker": "3.0.4"
	 },

In my case I had 2 versions in yarn.lock
Added
"resolutions": {
    "@react-native-community/picker": "^1.8.0"
  },

to package.json to fix this

A similar approach solved my case within Expo 40 and for datetimepicker, not picker:
	"resolutions": {
		"@react-native-community/datetimepicker": "3.0.4"
	 },

In my case I am using "@react-native-picker/picker": "^1.9.2", and   "native-base": "^2.13.14".
Somehow the latest version of "native-base" is using picker from "@react-native-community/picker" which  has been deprecated. I believe this is what caused the problem on my side. So I downgrade react-native to version 2.13.14 where they still import picker from native base, and It works fine. Seriously "native-base" caused too much problems, I am thinking remove it completely from my project. Hope this help someone.

In my case I am using "@react-native-picker/picker": "^1.9.2", and   "native-base": "^2.13.14".
Somehow the latest version of "native-base" is using picker from "@react-native-community/picker" which  has been deprecated. I believe this is what caused the problem on my side. So I downgrade react-native to version 2.13.14 where they still import picker from native base, and It works fine. Seriously "native-base" caused too much problems, I am thinking remove it completely from my project. Hope this help someone.

Seriously "native-base" caused too much problems, I am thinking remove it completely from my project.

Even though I respect the developers of the native-base, I could not have agreed more to above comment. It is generating more problems than it solves, especially with pickers.

Seriously "native-base" caused too much problems, I am thinking remove it completely from my project.

Even though I respect the developers of the native-base, I could not have agreed more to above comment. It is generating more problems than it solves, especially with pickers.

I got a similar error upgrading from Expo SDK 39 -> 40. I solved it by uninstalling @react-native-community/picker and instead installing @react-native-picker/picker.

I got a similar error upgrading from Expo SDK 39 -> 40. I solved it by uninstalling @react-native-community/picker and instead installing @react-native-picker/picker.

Uninstall old @react-native-community/picker and install latest @react-native-picker/picker solve this problem for me.

Uninstall old @react-native-community/picker and install latest @react-native-picker/picker solve this problem for me.

https://github.com/react-native-picker/picker/issues/45#issuecomment-633163973

https://github.com/react-native-picker/picker/issues/45#issuecomment-633163973

https://github.com/react-native-picker/picker/issues/15#issuecomment-757545674 and https://github.com/react-native-picker/picker/issues/15#issuecomment-759922490
You saved my life today

https://github.com/react-native-picker/picker/issues/15#issuecomment-757545674 and https://github.com/react-native-picker/picker/issues/15#issuecomment-759922490
You saved my life today

 <Picker
  selectedValue={formik.values.gender}
  accessibilityLabel={'gender'}
  onValueChange={(itemValue, itemIndex) => {
    formik.setFieldValue('gender', itemValue);
  }}>
  <Picker.Item label="Male" value="MALE" />
  <Picker.Item label="Female" value="FEMALE" />
</Picker>

it work for me!

 <Picker
  selectedValue={formik.values.gender}
  accessibilityLabel={'gender'}
  onValueChange={(itemValue, itemIndex) => {
    formik.setFieldValue('gender', itemValue);
  }}>
  <Picker.Item label="Male" value="MALE" />
  <Picker.Item label="Female" value="FEMALE" />
</Picker>

it work for me!

The Author renamed the library to @react-native-picker/picker.  See the GitHub new repository: https://github.com/react-native-picker/picker  It will resolve the issue after uninstalling the @react-native-community-picker library and rename the imported pickers to @react-native-picker/picker

The Author renamed the library to @react-native-picker/picker.  See the GitHub new repository: https://github.com/react-native-picker/picker  It will resolve the issue after uninstalling the @react-native-community-picker library and rename the imported pickers to @react-native-picker/picker

I changed react-native-community/datetimepicker version from
2.4.0 to 3.0.9
"@react-native-community/datetimepicker": "^3.0.9"
We can assume the old version will get error

I installed the NativeBase version that installed "@react-native-picker/picker" "^1.9.7" as dependency and by mistake, I install @react-native-picker/picker too.
So to solve this issue:  remove the @react-native-picker/picker that you installed because of NativeBase already installed @react-native-picker/picker as a dependency, if you are using yarn then check on yarn.lock file

I actually realized I didn't need native-base so I just deleted it (which I know isn't possible for everyone) and that worked. I did a little more research after and it looks like I could have upgraded native-base to the latest version and it would have worked. Hope that helps anybody struggling with this one!


Adding an asset more than once

Hi there,
This might be a feature request but just a question for now.
What's the reasoning behind throwing an error for resources that have already been added?
https://github.com/englercj/resource-loader/blob/6d00e3a721a7b6f6befbfe0b61575bf37d309019/src/Loader.js#L372
From what I can tell there are 2 possible scenarios: one in which the resource is still outstanding and another in which the resource is complete.
In our system we load assets just in time, and can potentially hit both of these scenarios.
I've accounted for them in our system, but it occurs to me that the library could (potentially should?) be able to handle a scenario where the same asset is added more than once.
Just curious you thoughts on this. If I can make time I could potentially offer a PR for this functionality.

The reason is because this library doesn't want to be a resource caching and management system, just a loader. You shouldn't use this library for anything except the actual mechanism of loading data. All caching, resource management, knowing what is loaded and what isn't, deciding what to load, etc, should all exist as logic outside of this library.
The philosophy here is that once you've decided what to load, you fill a loader with requests and trigger it. If you're adding a name 2 times, then your higher-level logic is flawed and incorrectly had a duplicate in it.

@englercj it would be a good idea to make this more explicit up-front, perhaps in the main project readme.  It is definitely unexpected behavior to folks coming new to the project and caused me a lot of debugging and googling to figure out what was going on.
My expectation was that if I requested loading an existing resource, the loader would simply queue it and immediately fire an onLoad once the loader starts just like a browser would with a dom node.  I understand why you're not implementing that feature, but it is odd without the context you just provided.
(and thanks for this project - I really appreciate your work!)

I added this to the readme in the v4 typescript branch.


[ai-form-recognizer] Rename TrainingPollOperationState.

This is a quick fix to one of the DocumentModelPoller-related names. When we renamed TrainingPoller to DocumentModelPoller, we missed the operation state type name.
While updating this name, I also updated the file src/lro/training.ts to be named src/lro/administration.ts and changed analyze.ts to analysis.ts.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-form-recognizer


Idea: It would be nice to have a Python interface

Hello Patrick,
After we met at the IPAM workshop I started playing around more with randSpg. So far I wrote some Python wrappers creating input and output files, but obviously it would be nice to have a Python interface, for example the structure could be an ASE object1 and so on.
In addition I recently setup some anaconda workflows mainly for our internal solution, but as part of this process I wrote the scripts to create an anaconda compatible randSpg executable, so I thought this might also be interesting for you2.
Best regards
Jan

Sounds good Jan! I think I should be able to use pybind11  to make an easy-to-use Python interface. I will look into it.

I was actually already able to get a Python interface working for the most part. I might want to run some more tests and make some changes to it. But you can feel free to try it out if you'd like. This is an example of me using it with Python:
patrick@ubarvey:~/src/randspg/build/python$ python3
Python 3.5.2 (default, Sep 14 2017, 22:51:06)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from pyrandspg import Crystal
>>> from pyrandspg import AtomStruct
>>> from pyrandspg import LatticeStruct
>>> from pyrandspg import RandSpg
>>> from pyrandspg import RandSpgInput
>>> spg = 3
>>> atomicNums = [4,2,2]
>>> latticeMins = LatticeStruct(2.0, 2.0, 2.0, 60.0, 60.0, 60.0)
>>> latticeMaxes = LatticeStruct(4.0, 4.0, 4.0, 120.0, 120.0, 120.0)
>>> input = RandSpgInput(spg, atomicNums, latticeMins, latticeMaxes)
>>> input.minRadius = 0.2
>>> crystal = RandSpg.randSpgCrystal(input)
>>> crystal.printAtomInfo()
  For 2, coords are: (0.856133,0.469797,0.907492)
  For 2, coords are: (0.143867,0.469797,0.0925077)
  For 4, coords are: (0,0.885445,0)
>>> crystal.printLatticeInfo()
a: 2.40507
b: 3.51869
c: 2.23127
alpha: 90
beta: 60.5655
gamma: 90
>>> crystal.getPOSCARString()
' \n1.00000\n    2.405074960888036    0.000000000000000    0.000000000000000\n    0.000000000000000    3.518690629374015    0.000000000000000\n    1.096506158990584    0.000000000000000    1.943250246339095\n   He   Be\n    2    1\nDirect\n  0.856133079463798  0.469797445817382  0.907492305602408\n  0.143866920536202  0.469797445817382  0.092507694397592\n  0.000000000000000  0.885444769147676  0.000000000000000\n'

So I think it is clean and fairly straightforward (you can extract atom info and lattice info from the data types present in the library). I am considering distributing some binaries of these Python bindings so people do not have to compile it themselves. But for now, you do need to compile it. If you'd like to try compiling it yourself, here are some instructions:
Additional packages needed to compile the RandSpg Python bindings: python3-dev and pybind11.
I'm not sure what operating system you are using. On Ubuntu, you can install python3-dev with just a "sudo apt-get install python3-dev". Unfortunately, I don't think there is a Debian package for pybind11 readily available, so I just compiled it from source (which requires pytest, so you may need to "pip install pytest"). I compile pybind11 via "git clone https://github.com/pybind/pybind11; mkdir pybind11/build; cd pybind11/build; cmake ..; sudo make install". This will install pybind in a location that cmake can find.
Then, cd into the randspg build directory, and run cmake like so: "cmake .. -DBUILD_PYTHON_BINDINGS=ON". Then "make". It should build the python bindings and put them in "python" inside your build directory.
Depending on what version of Python you use, the .so file may be named a little different. Mine is named "pyrandspg.cpython-35m-x86_64-linux-gnu.so" - I used Python 3.5 headers in the compilation. As long as you are in the same directory as the .so file when you are running Python (and you are running the same version of Python you compiled it with), you should be able to import pyrandspg as "import pyrandspg".
The .so file that this process creates only depends on GCC libraries. I may remove that dependency so that we can move the .so files around however we like (without needing to worry about the GCC libraries being present on the user's computer).

Note that if you already have a randspg repository on your computer, you will need to update the changes I made here by cd'ing into the directory and running "git pull".


iPhone (iOS) loses connection to device when using this package

I have installed the version ntp: 1.0.7 on my pubspec.yaml, and It works fine with android.
But as soon as I try to fetch it from my iPhone, it exits the app and it says 'Lost connection to device.'
Are there some extra instructions for iOS implementation?

Can you give some minimal code where you can reproduce the issue? I couldn't reproduce this locally.


Reduce notifications about tag_rpms failure

Needed by https://github.com/openshift-eng/art-tools/pull/458

/lgtm

/approve


Fix assertCookieXxx() when cookie value is empty

assertCookieAttributeEquals() and asserCookieAttributeMatches() should consider that cookie value is empty string instead of undefined when Set-Cookie header was sent with empty value

Hi @bacalec I can't really understand the problem this is causing. Can you remember?

Hi,
Sorry, it seems that i committed a typo in the comment above. It's about assertCookieEquals() and assertCookieMatches().
In https://github.com/akamai-contrib/postman-jsonnet/blob/main/example/testing-responses/cookies.jsonnet

test case 'Cookie assertion and cookie attribute assertions - Cookie, value and attribute empty or not sent'
response returns set-cookie silver with empty value
line 165:

        // TODO: this assertion will work after https://github.com/akamai-contrib/postman-jsonnet/issues/5
        // When value is absent in Set-Cookie, it should be empty string
        //test.assertCookieEquals('test.assertCookieEquals', 'silver', ''),

If i remember well, this test suite doesn't include similar comment with assertCookieMatches() because the test suite is meant to show the values of the cookies and their attributes in this situation rather than the behavior of all assert functions.


Java9 compatibility issues

Java9 jigsaw - how everything becomes complicated by default.

ClassLoaderUtil contains a load of pre-java9 hacks.
getDefaultClasspath() is not working, making all automagic scanning not working as well.
Added Java class to fix compatibility issues, still requires additional -- JVM flags.

It is going to be hard to have a single codebase.
Not sure if we can postpone release to fix these issues.

It's 1am and after not sleeping for days i feel really depressed now so much changes needed, dont see the point

Bug submitted to Oracle, about MR Jars: 9051830


test_sanity: Fix missing import of sys

and use print instead of directly writing to sys.stderr

I close it but it will be merged right after, I added a commit to keep supporting python2.7


Internet Archive integration

Codecov Report

Merging #30 into master will decrease coverage by 0.06%.
The diff coverage is 96.96%.

@@             Coverage Diff              @@
##             master      #30      +/-   ##
============================================
- Coverage     97.47%   97.41%   -0.07%
- Complexity       69       80      +11
============================================
  Files            12       13       +1
  Lines           238      271      +33
============================================
+ Hits            232      264      +32
- Misses            6        7       +1

Impacted Files
Coverage Δ
Complexity Δ

src/Service/InternetArchiveApiService.php
96.66% <96.66%> (ø)
10.00 <10.00> (?)

src/Service/ApiServiceFactory.php
100.00% <100.00%> (ø)
7.00 <0.00> (+1.00)

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 57d0884...2caf56f. Read the comment docs.


Amentification meta-ticket

This ticket is to track the amentification of packages. Once all packages are done, we can close this ticket and consider the feature complete.

[ ] Use ament for autoware_build_flags
[ ] Integrate ament into CI and docker builds

amathutils_lib and decision_maker:
https://github.com/CPFL/Autoware/pull/2016

diag_lib and fake_autoware_nodes:
#2033

state_machine_lib:
#2034

libvectormap and trafficlight_recognizer:
#2035

pixel_cloud_fusion and range_vision_fusion:
#2074

idar_euclidean_cluster_detect, lidar_fake_perception and lidar_naive_l_shape_detect:
#2099


updates to shared memory variable not seen by all threads

Around line 190 in tmpRadixSort5.h, there is an update to shared variable ibs, which is the control variable in a while loop.  It appears the update to ibs is not seen by all threads.
Using ibs - either by printing it out, or by assigning it to another shared variable - will fix the problem, and the program runs correctly.
     __shared__ int ibs;
     __shared__ int ibs2;
     ...
      ibs = size - 1;
     __syncthreads();
     while (__syncthreads_and(ibs>0)) {

     ...

      if (threadIdx.x == 0) {
        ibs -= sb;
        // uncomment the next line to fix the hang or error
        //ibs2 = ibs;
      }
      __syncthreads();
  }

More info in Readme.  Build command in "compile.sh"
reproduce_sync_failure.tar.gz

One thread may be needed to update ibs.
// broadcast
if (threadIdx.x == 0) ibs = size - 1;

Does marking ibs volatile help?

@markdewing Can we go ahead and close this ticket? Thanks!


fix: make button to stop port forward less ambiguous

Playing around with the dashboard, I set up a port forwarding to a pod, then went somewhere else on the dashboard, and came back to this:

Without having just seen the button pop up, it was not clear to me what "REMOVE" meant. I still don't have a full overview of what the dashboard can and can't do, so I was pretty afraid to click it.
"Stop port forward" is specific, and matches the wording of "Start port forward" on the button button clicked to add the port forwarding.

Aha! I ran the Karma tests, but not the Cypress suite. Thanks :smile:
I've amended my commit to update the Cypress test and include a changelog entry.


Usage with index set construction

Is it possible to write a Finch kernel for
function subXTv!(XTv::AbstractVector, x::AbstractMatrix, v::AbstractVector, I::Vector{Int}, sizeI::Int)
    @views begin
        xx = x[:, I[1:sizeI]]
        vv = v[1:sizeI]
    end
    return mul!(XTv, xx, vv)
end

where x is sparse, and v is dense?
I can write a non-Finch SparseMatrixCSC kernel with
cols = 1:sizeI
vals = nonzeros(x)
rows = rowvals(x)
XTv .= 0
for col in cols
    b_value = @inbounds v[col]
    nzr = nzrange(x, I[col])
    @fastmath @inbounds @simd for i in nzr
        row = rows[i]
        val = vals[i]
        XTv[row] += val * b_value
    end
end

though it needs a bunch of extra workspace to parallelize (I need to have n_tasks copies of XTv, accumulate into each separately over a subset of the columns, then add them together).

@ericphanson This is very possible. You can certainly read out indirect views of x and a portion of v as you suggest because Finch supports indirect access so you can write x[k, I[i]] (or if statements (e.g. if j == I[i], if you prefer) and because Finch supports loops over a range j = 1:sizeI.  With these ingredients, you should be able to write a version of your kernel. One complication might be the format of XTv. If this is dense, it is easy. If it is sparse. then you might need to write more complex code.
We are in the process of adding parallelism, but the optimization of using workspaces to parallelize the kernel might be possible already.


Multi-line input files on Windows OS

Chopper curretnly gives an error on multi-line bin files (i.e. this input file consists of multiple lines, referring to multiple sequence files for the different bins), on Windows OS: a carriage return (\r) will be read as part of the filename.

Resolved on Gitter. Solution:
Since chopper is currently only supported for unix bases operating systems, the input files have to be created on a unix based system too.
The easiest way, if you have a directory containing files is the following
find -type f /path/to/files/ > chopper_input.txt

And then feed the file chopper_input.txt to chopper count.


BUG: moved get_info from backend.py to _nx_parallel

fixes https://github.com/networkx/nx-parallel/issues/52

I don;t think you need to make the additional parameters dict.  It is a helpful structure if you already know the parameter names and corresponding docs.  But when you are pulling from existing doc_strings on these functions, it is probably easier to just extend the additional_docs string with the parameter descriptions.
That is: you can add the parameter section of the doc_strings to the additional_docs field (leaving additional_parameters blank) rather than parsing and making the dict structure required for additional_parameters`.


Rename CommonTestUtils namespace to ov::test::utils

Is it time to merge it? https://github.com/openvinotoolkit/openvino/pull/18590/ was merged

Is it time to merge it? openvinotoolkit/openvino#18590 was merged

Yes. Now it is able to be merged. Please reivew


Refactored the big for and if block slightly in Backprojector

Hey,
I just realized that Jupyter manages the state of these in this json too.  Is there some way I should actually share these changes with you online?
Anyway, I removed the boolean and in favor of val <= abs(var) < bigger_val; I also utilized a function to make the page less busy.
Let me know if there is a better way to share changes for this type of file.

Thanks for that email.  I'll go ahead and close this as it doesn't seem like the correct way to share changes made to the notebooks.
I'll look into azure and then send you the refactored notebook.
Cheers.


Add Spanish translations

This PR adds Spanish translations to Motor Admin.
Missing translations
Some texts do not have i18n support, so I couldn't translate them. I'll leave some pictures below to point them out:
Reports page: title and tabs
The title and the tabs in the reports page are missing i18n support:

Custom form builder
Translations are missing for the form errors and the input types (don't know if they can be translatable):

Also, in the Add field form, translations are missing for the Required and Multiple checkboxes, and the Add button:

Filters
The title of the drawer is supported on i18n, but the order of the words is incorrect for Spanish, and I presume the same would happen in other languages.
Correct translation for ${resource_name} filters should be Filtros de ${resource_name}.
I'm not sure if this can be done, since I'm guessing the translations are being passed from the Rails app to a global variable, so using string interpolation in i18n might be off the table:

Settings
The title in the settings drawer is missing i18n support:

Resource settings
The title in the resource settings drawer is missing i18n support, should be Configuración de ${resource_name}
Also, when editing actions, the action type options don't have i18n support, as well as the default action names:

Intelligence search
The Search... placeholder is missing i18n support:

Bugs
I found only one bug. In the Create Alert form, the select tags field placeholder doesn't show completely:

Thanks @dantevvp ! Let me fix those bugs in the i18n branch so we can continue.


REPL: Weak pointers don't point to None when pointee hits end of scope

Running samples/weak/basic.jakt produces different results for comptime vs build time execution, suggesting that either foo is not destroyed at the end of the scope, or the weak pointer is not updated:
class Foo {
    public function hello(this) => "friends"
}

function main() {
    mut weak_foo: weak Foo? = None

    println("weak_foo has_value? {}", weak_foo.has_value())

    {
        let foo = Foo()
        weak_foo = foo

        println("weak_foo has_value? {}", weak_foo.has_value())
        println("weak_foo hello: {}", weak_foo!.hello())
    }

    println("weak_foo has_value? {}", weak_foo.has_value())
}

~/jakt$ ./build/bin/jakt -r samples/weak/basic.jakt
weak_foo has_value? false
weak_foo has_value? true
weak_foo hello: friends
weak_foo has_value? true <------ !!!!
~/jakt$ ./build/bin/jakt -cr samples/weak/basic.jakt
weak_foo has_value? false
weak_foo has_value? true
weak_foo hello: friends
weak_foo has_value? false

This is expected because WeakPtr::has_value() is not implemented for comptime.
At the same time, this is unexpected because WeakPtr::has_value() is not implemented for comptime. It should fail to parse/compile the code with -r

I think this is just because the interpreter doesn't actually perform the implicit casts required for our weakptr mess to work, so it's seen as an Optional instead.