style and static content fixes for public faces pages

This makes many small style and static content fixes for the public-facing pages.  They include:
sets#index

Fix email link in introductory text
Remove comma after “These sets were created”
Add paragraph break before “These sets were created"
Render markdown for set titles
Hyperlink thumbnails
Remove breadcrumbs

set#show

Hyperlink thumbnails
Left-align source titles
Change source tile background color from light blue to light grey
Make the blue title bar and the grey "Teaching Guide" sidebar the same height (this is done with JavaScript, which will not fix the style on browsers with JavaScript disabled)

source#show

Add /item to "Need more information..." URLs
Remove “Send feedback” div from bottom of page

guide#show

Remove author name and affiliation from "Primary Source Set" sidebar
Remove “Teaching guide” from title

General changes:

Make the whitespace above "Send feedback" div consistent across pages

This addresses ticket #8084.

:white_check_mark:


Unnecessary greeting if an open task is ignored

If the user has an open alert assigned and it is also ignored for them, the bot still greets the user. It shouldn't because it doesn't print the ignored alert's details and the greeting looks awkward this way.

Also, the user is not removed from the active users list in this case.


Here is the error log from Daedalus.log
[2018-12-06T05:39:46.0533Z] [debug] [renderer] Local blockchain height: 306574
[2018-12-06T05:39:46.0533Z] [debug] [renderer] Network blockchain height: 306575
[2018-12-06T05:39:46.0533Z] [debug] [renderer] Total unsynced blocks at node start: 77
[2018-12-06T05:39:46.0533Z] [debug] [renderer] Blocks synced since node start: 76
[2018-12-06T06:28:04.0029Z] [debug] [renderer] System time change detected
[2018-12-06T06:28:04.0031Z] [debug] [renderer] AdaApi::getNetworkStatus (FORCE-NTP-CHECK) called
[2018-12-06T06:28:04.0032Z] [debug] [renderer] AdaApi::getNetworkStatus called
[2018-12-06T06:28:04.0395Z] [debug] [renderer] AdaApi::nextUpdate called
[2018-12-06T06:28:04.0395Z] [debug] [renderer] AdaApi::getWallets called
[2018-12-06T06:28:04.0396Z] [error] [renderer] AdaApi::getNetworkStatus (FORCE-NTP-CHECK) error: {
  "stack": "Error: getaddrinfo ENOENT localhost:29827\n    at Object.exports._errnoException (util.js:1050:11)\n    at errnoException (dns.js:33:15)\n    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:73:26)",
  "message": "getaddrinfo ENOENT localhost:29827",
  "code": "ENOENT",
  "errno": "ENOENT",
  "syscall": "getaddrinfo",
  "hostname": "localhost",
  "host": "localhost",
  "port": 29827
}

Restarting Daedalus fixes the issue.

Thanks for the report @SebastienGllmt.
May I ask you if you see the same problem with the current production/mainnet Daedalus?

Oh hey you're right -- I get the same error on current mainnet Daedalus. However, it seems that the mainnet Daedalus auto-recovers after a few minutes. Testnet Daedalus seems to be stuck indefinitely.
Here is the error on Mainnet Daedalus (from which I recover after a few minutes of connecting to network...)
renderer.js:34 [19:06:41.402] AdaApi::nextUpdate error: {
  "stack": "Error: getaddrinfo ENOENT localhost:8090\n    at Object.exports._errnoException (util.js:1050:11)\n    at errnoException (dns.js:33:15)\n    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:73:26)",
  "message": "getaddrinfo ENOENT localhost:8090",
  "code": "ENOENT",
  "errno": "ENOENT",
  "syscall": "getaddrinfo",
  "hostname": "localhost",
  "host": "localhost",
  "port": 8090
}

it also matters heavily how long the computer has been in sleep mode, if its only been a few minutes, it can recover
but if its been in sleep mode for an hour, the connection may fail, and then it takes longer to recover

The issue has been resolved in: https://github.com/input-output-hk/daedalus/pull/1213


Focus is fixed to "Get Started" tab in a newly opened folder

Type: Bug
Hi there!
I have been experiencing this specific issue for a little while now and I am not sure what could be causing it.
Basically, when I open VsCode without opening a workspace or when i open a workspace for the first time, it displays the "Get Started" as usual but no matter what I do the focus keeps going back to said tab: specifically when I open the integrated terminal, or when i open "quick open" or even when I open a new tab. The issue persits until I close the first tab.
There is a setting that lets you open the README file inside the root of a project by default, but the same thing happens excepts the focus is latched onto the README Preview instead. I've had this issue for as long as I can remember by the way.
Any help would be appreciated!
 You also have 108 extensions installed. Can you try launching with extensions disabled via the cli you can do code --disable-extensions

My bad, here's a permanent link
The issue doesn't occur when opening apps with extensions disabled, so it's definitely because of an extension.
Thanks for the help!

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.
Happy Coding!

For anyone experiencing the issue in the future, it was caused by an extension called All Autocomplete.
I disabled it and the issue is now gone.


Added vec IO tests for #104

This is a reworking of da-steve101's #227:
Add test cases for #104, #109 fixes Vec( vecSize, UInt( INPUT ) )
with all tests fixed and the Vec.fill() test with pure Chisel types (not values) expected to fail with a binding error.

This PR was not named properly and the API change it introduced is concerning. The name implies the PR just added tests (so not of particular interest) but the PR redefined the instantiation of Vec.
The old Vec(Int, T) very reliably always returned a Vec as a type that had to be used somewhere else. Now, this is no longer guaranteed. Similarly, with https://github.com/ucb-bar/chisel3/blob/master/chiselFrontend/src/main/scala/chisel3/core/Reg.scala#L11 , it seems like this line of code would be broken now, depending on CompileOptions:
Reg(Vec(1, 1.U))

Errr, what? Yes that is concerning. What would that Reg code do now?

I agree with @sdtwigg concerns. We should revert the redefinition of the instantiation of Vec.

@mwachs5 throw an exception rather than instantiate a Reg of Vec of 1-bit UInt


Publish version number for JS

This change is

All the individual element style modules are already moved / being moved to their corresponding element repos.
Instead of importing version.html in the element style modules, I would import in the utility style modules (color, typography, sizing, spacing, style). All the elements import at least one of them.

Moved to the style modules

Updated

Won’t bother using Reviewable. LGTM.


update go

Chore: update go to 1.19
Chore: switch build to goreleaser

(made drone-ci a "Maintainer" (previously Developer) on the runway-public project in Harbor, but apparently that didn't fix it, still looking)

(manual cm-push did work, unsure why it doesn't work here)


Update sbt-scalafix to 0.9.24

Updates ch.epfl.scala:sbt-scalafix from 0.9.20 to 0.9.24.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.epfl.scala", artifactId = "sbt-scalafix" } ]

labels: sbt-plugin-update, semver-patch

Superseded by #147.

Superseded by #147.


feature/SimpleFeaturesToKotlin -> dev

This change is

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

app/src/main/java/edu/byu/suite/features/copyright/CopyrightActivity.kt, line 28 at r1 (raw file):

	private fun showContactDialog() {
		val dialog = Dialog(this@CopyrightActivity)

Do you need the @ sign here? I think that's only needed in closures

app/src/main/java/edu/byu/suite/features/copyright/CopyrightActivity.kt, line 30 at r1 (raw file):

		val dialog = Dialog(this@CopyrightActivity)
		dialog.setContentView(R.layout.copyright_contact_popup)
		dialog.setTitle("Contact Options")

Can this be moved to strings.xml?

app/src/main/java/edu/byu/suite/features/operator/ByuOperatorMainActivity.kt, line 28 at r1 (raw file):

	}

	companion object {

Can we always have the companion object be at the top of a class (unless there is a reason for exception)? Change in other places as well, if needed

Comments from Reviewable

Review status: 3 of 7 files reviewed at latest revision, 3 unresolved discussions.

app/src/main/java/edu/byu/suite/features/copyright/CopyrightActivity.kt, line 28 at r1 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Do you need the @ sign here? I think that's only needed in closures

Done.

app/src/main/java/edu/byu/suite/features/copyright/CopyrightActivity.kt, line 30 at r1 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Can this be moved to strings.xml?

Done.

app/src/main/java/edu/byu/suite/features/operator/ByuOperatorMainActivity.kt, line 28 at r1 (raw file):
Previously, romrell4 (Eric Romrell) wrote…
Can we always have the companion object be at the top of a class (unless there is a reason for exception)? Change in other places as well, if needed

Done.

Comments from Reviewable

Reviewed 4 of 4 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Path hacks to support bower_components

This seems to break some tests. Do those tests need to be refactored?

I don't know, I basically broke the pathresolver to make sharding work, but I'm not 100% clear on the original goals of the path resolver.

This was resolved with the other PRs right? Closing this one then.


Please add albertlauncher tag

Please tag your repos with albertlauncher such that we can find it here.
Regards

Thanks for the hint, I added the tag :)


Implement the feature importance for Decision Tree Classifier

This PR fixes part 1/3 of #124
Checklist

[x] My branch is up-to-date with development branch.
[x] Everything works and tested on latest stable Rust.
[x] Coverage and Linting have been applied

Current behaviour

The impurity is not available in the Node object
The number of samples is not available in the Node object
The number of features is not available in the Decision Tree Classifier
So the feature importance cannot be calculated after model is trained.

New expected behaviour

The feature importance can be calculated after model is trained.
Change logs

The feature importance can be calculated after the DecisionTreeClassifier is trained.

hi! thanks for the PR.
Please follow the guidance about running the linter in CONTRIBUTING. The linter check is failing.

hi! thanks for the PR.
Please follow the guidance about running the linter in CONTRIBUTING. The linter check is failing.

Hey, thanks for providing the doc. I was aware of that and changed the PR status as "Draft". Let me try to fix the linter today or tomorrow.

Hey @Mec-iS I have fixed the linter error, and would you like to review the PR?

Is there anyone else can help review the PR? It has been quite a while.

Thanks @tushushu ! Sorry I missed the notification for this.


Improve logging during reconciliation

Coverage increased (+0.04%) to 90.205% when pulling 2980b12c7f0ad3a1322298ad62992fab816175b0 on fix-logging into<PHONE_NUMBER>9b538c351b6b33048bf9307504285c on master.


find unmapped lines?

How this lib can be used to find unmapped lines (lines in source that are absent in sourcemap)? Just list some API members.

Can you provide some more details on the scenario? What is it that you are trying to do with the lines you find?

Thank you for your interest.
I know that sourcemap usually doesn't cover whole webpack bundles (e.g. source-map-explorer reports that my bundles are not covered for 27%-7%). And I'm interesting to investigate what kind of bundle's code has no its cover in sourcemaps.  Create a small utility that can show me those lines. Just as an investigation instrument.

I haven't tried to do something like that myself, but you might be able derive the uncovered lines by using the source map object returned by SourceMapParser.ParseSourceMap. It has entries for the mappings in the source maps, so you'd just need to figure out how to determine which lines aren't covered by those mappings

Going to close this isssue since it hasn't been active in the past year and doesn't quite fall within the scope of this library


Release 5.1.2

Patch release to fix NuGet prompting to upgrade to Castle.Core 5.0.0.

#610

Tagged v5.1.2
Confirmed successfully pushed to nuget.org

Thanks @Jevonius


Ability to customize presets with custom endpoints

Hi ❤❤❤ !!! This gem is awesome and will be a game changer, I've used the live demo with custom schemas a few times already.
We run a microservices architecture and we are slowly moving the APIs from REST to GraphQL and I am considering having an internal version of Voyager running so anyone in our organization can introspect and learn about the APIs we have available.
It seems like the presets like Star Wars, Yelp, Shopify, and Github are hard-coded here https://github.com/APIs-guru/graphql-voyager/blob/master/src/presets.ts and the result of the introspection query are stored here https://github.com/APIs-guru/graphql-voyager/tree/master/src/introspection/presets. For demo purposes this makes total sense.
My feature request is: it would be nice to be able to list a series of endpoints and their names and have them listed in Voyager in the landing page, Voyager would then perform the introspection query and show the latest schema.
I would imagine something like the following:
window.VOYAGER_PRESETS = {
  'clients': {url: 'https://clients.foo.com/api/graphql'},
  'accounts': {url: 'https://accounts.foo.com/v3/graph'},
  'orders': {url: 'https://orders-srv.foo.com/api/graphql'},
};

Related issues:

https://github.com/APIs-guru/graphql-voyager/issues/4
https://github.com/APIs-guru/graphql-voyager/issues/38

@cabello We planned to move all options to float menu, see: https://github.com/APIs-guru/graphql-voyager/issues/32#issuecomment-321563571
After this will be done "landing page" will have only buttons for presets and "Custom introspection".
As I understand "Custom introspection" doesn't make sense in your use case so what will be left is a very simple component with a couple of buttons.
So I think it would be better to just add a drop down list of presets to the floating menu.
In any case, I think this issue is blocked until we add float menu 😞

@cabello Sorry for the delay.
We are finally separated Demo code from main Voyager so now you can provide your own widget for switching schemas (dropdown, radio button, etc.)
Here is how it's done in our demo:
https://github.com/APIs-guru/graphql-voyager/blob/489cdaff1abd0402ce90a23b115e9d3b1dfc6447/demo/index.tsx#L48-L56


Support 'height', 'weight', 'width' road attributes

Unrecognized values will be logged and ignored.

When look into the responsibility the OSM related parsing and converting should be done in the OSM reader module not in the encoder. But when I move it there we have to convert regardless if it is enabled or not (e.g. using generic or not). Hmmh, interesting ;)

But this is worth a separate issue #939

Interesting. I was able to push to the road_attributes branch of Transtech/graphhopper ... even a force push. Seems that github has improved this to work together with different repos on the same pull request, nice. Please have a look- hope I didn't messed up something!

Guys, I have committed a new change that makes road attribute encoders configurable. Merging fine with master. Let me know if there is anything else you would like me to change.

Thanks, this looks good.
Let us (shortly) discuss if we need three configurations or if one e.g. "store_truck_attributes":true is simpler (are there meaningful use cases where one would just need e.g. the weight?). Also the name is important, I prefer something with 'store_xy' and how the weighting interprets this value is up to the weighting.
Furthermore the boolean methods should be setXY instead of enableXY

Btw, I have resolved some conflicts when merging Peter's changes. Hopefully I didn't miss out anything :)

Sorry, I feared that. Force push is never a good idea if one works on the same branch with others :(. So instead I should have made my changes and the rebase/squash should have been done as the last step.

Would you mind to just rename the methods? We do not need to debate on configuring and should just change it afterwards when necessary (?)

I have renamed the methods and variables as requested. This naming convention makes more sense to me now. Please review and advise.
In relation to choosing single configuration field vs multiple configuration fields for road attributes, IMHO, I would go with multiple fields. That would make it more flexible as you would be able to select the attributes of interest, rather than all or nothing. This is especially true when we are still limited to 64 bit length of the flag & the cost of having all fields is expensive.

This looks good now - thanks again!

This is especially true when we are still limited to 64 bit length of the flag & the cost of having all fields is expensive.

Yeah, this is ugly and needs a fix (better sooner than later :))


iOS - Rejected status is displayed on Wallet screen even after logout from Sora Card

Steps:

Make a rejected status for your card
Log out from Sora card
Return to the Wallet screen

Actual result: Rejected status is displayed until I reopen the app
Expected result: The status is updated
Private Zenhub Image

Verified on 1.0. (258) develop version.


v2.5.4: add level-up confirm, restrict ender pearl teleport, fixes

Closes #311, Closes #312, Closes #313, Closes #218, Closes #37
This PR fixes a few issues

The /town level command will now prompt you for confirmation with the cost needed to level-up before levelling up a town
Added the next level cost to the town overview screen (it is shown when hovering over the town's current level)
Added a new operation type: ENDER_PEARL_TELEPORT. This restricts the teleportation into claims using ender pearls or chorus fruit
Fixed an issue where operation checks carried out for the placeholderAPI hook would occur verbosely, sending a chat message
Fixed an issue where editing the town rules would sometimes not be possible occasions due to the rules map being generated with an immutable map

very grateful dev


Make Parameter dumb again

Rationale
One Parameter constructor was substituting getJdbcRsName() instead of using the passed in column name. This breaks code since the caller expects to use the column name.
https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=45368
The getJdbcRsName() code was a "fix" for https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=26694.  Hopefully we have regression tests for that.
Related Pull Requests

Changes

removed getJdbcRsName() code
removed Parameter members that it didn't use itself (scale, parameter) and changed caller to keep track of these.

@labkey-matthewb can we please merge to release22.7-SNAPSHOT

@labkey-matthewb can we please merge to release22.7-SNAPSHOT

I'd rather not?  Seems like a bit much for a stable release.  But I'll defer to triage/Josh.

@labkey-matthewb can we please merge to release22.7-SNAPSHOT

I'd rather not? Seems like a bit much for a stable release. But I'll defer to triage/Josh.

@labkey-matthewb i didn't see Hannah's comment on the ticket, it is targeted for 22.11, so nevermind my comment


Inquiry Regarding Emoji Usage in App Service and Copyright Compliance

Hello. I hope this issue finds you well. Firstly, I'd like to express my sincere appreciation for your thoughtful use of the emojis you shared.
I want to reiterate my strong commitment to respecting the copyright of the creative work you provided.
Currently, I'm in the process of planning an app service that incorporates a diary-writing feature with the ability to add emojis. Our app distinguishes between free and paid users. I am contemplating offering the complete set of emojis exclusively to paid users while providing only a limited selection to free users. Could this potentially raise concerns regarding copyright infringement?
If it does, I would greatly appreciate your guidance on the matter.
Thank you for your time and consideration.

Currently, I'm in the process of planning an app service that incorporates a diary-writing feature with the ability to add emojis. Our app distinguishes between free and paid users. I am contemplating offering the complete set of emojis exclusively to paid users while providing only a limited selection to free users. Could this potentially raise concerns regarding copyright infringement?
If it does, I would greatly appreciate your guidance on the matter.

I'm sure this would be fine as long as you attribute to them being in use somewhere.


Program crashed with signal 11

Godot version
flatpak version 3.4.4 stable
System information
linux debian 11
Issue description
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v3.5.stable.flathub (991bb6ac74ac8c09d7683041b50a8ced3a2defb1)
Dumping the backtrace. Please include this when reporting the bug on: https://github.com/godotengine/godot/issues
[1] /usr/lib/x86_64-linux-gnu/libc.so.6(+0x39510) [0x7f2033753510] ()
[2] /app/bin/godot-bin() [0xb6adc2] ()
[3] /app/bin/godot-bin() [0xb077f8] ()
[4] /app/bin/godot-bin() [0x2e578be] ()
[5] /app/bin/godot-bin() [0x2eef352] ()
[6] /app/bin/godot-bin() [0xb786a8] ()
[7] /app/bin/godot-bin() [0xb077f8] ()
[8] /app/bin/godot-bin() [0x2e578be] ()
[9] /app/bin/godot-bin() [0x30b1883] ()
[10] /app/bin/godot-bin() [0x2f7c600] ()
[11] /app/bin/godot-bin() [0x34da915] ()
[12] /usr/lib/x86_64-linux-gnu/libpthread.so.0(+0x83ba) [0x7f2033a513ba] ()
Steps to reproduce
try to make a thread pool then run a interactive loader on it that also saves the progress inside of the task (inside the thread pool task array)
this line crashes everything when trying to add child
get_tree().get_root().add_child(resource)
after that there is code that cleans the tree from unwanted scenes
all the avoid another bug where get_tree().change_scene_to()
doesn't work it maybe adds sometimes but never deletes
i have the code here you can attach it to other code to make it work
Minimal reproduction project

func __load_scene_interactive(data, task): # handels polling and scene switching
	if OS.can_use_threads(): # double check if platform supports aysnc (no fallback if it failes)
		var loader = ResourceLoader.load_interactive(data[0])
		var path = data[0]
		var print_to_console = data[1]
		if loader == null and task.target_argument == null: # complains about invalid paths
			print("Resource loader unable to load the resource at path")
			return

		var t = OS.get_ticks_msec()

		while OS.get_ticks_msec() - t < max_load_time: # polling / loading selected scene and updating progress for loading bar
			var err = loader.poll()
			if err == ERR_FILE_EOF:
				#Loading Complete
				var resource = loader.get_resource().instance()
				get_tree().get_root().add_child(resource)
				print("i")
				for child in get_tree().get_root().get_children(): # gets children of root and queue_free() them if they are not a singleton
					if autoload_names.has(child.get_name()): # checks if the childs name is valid for exclusion from queue_free() by looking up its name and seeing if it exist in Globals.autoload_names
						pass
					elif child == resource:
						pass
					else:
						child.queue_free()
				if print_to_console:
					print(path.get_file()," is complete!")
				break
			elif err == OK:
				#Still loading
				var progress = float(loader.get_stage())/loader.get_stage_count()
				task.progress = progress * 100
				if print_to_console:
					print(path.get_file()," is at %",progress * 100," completion!")
			else:
				print("Error while loading file") # if err isn't ERR_FILE_EOF(completed) or OK(still loading) the something Is preventing the file from loading
				break
		yield(get_tree(),"idle_frame") # makes it possible to see end result

@ChromiumOS-Guy Please upload a minimal reproduction project to make this easier to troubleshoot. (The code sample is not a complete reproduction project as it won't work on its opwn.)

Closing due to lack of response. Please comment if you can still reproduce this bug.
PS: If no minimal reproduction project was included in the original bug report, please upload one as well to ease troubleshooting.


Testing after removal of webview/liveshare code

Refs:  #6488

[ ] macOS @alexdima

Complexity: 5
Create Issue

Use the tests outlined here https://github.com/microsoft/vscode-jupyter/blob/main/.github/test_plan.md

Here are the test items
Test plan
Environment

OS: XXX (Windows, macOS, latest Ubuntu LTS)

Shell: XXX (Command Prompt, PowerShell, bash, fish)

Python

Distribution: XXX (CPython, miniconda)
Version: XXX (2.7, latest 3.x)

VS Code: XXX (Insiders)
Python Extension: XXX (Insiders)
Local/Remote: XXX (Local, Remote-SSH, Remote-WSL, Remote-Docker, Remote-Codespaces)

Tests
ALWAYS:

Check the Output window under Python for logged errors
Check the Output window under Jupyter for logged errors
Have Developer Tools open to detect any errors
Consider running the tests in a multi-folder workspace
Focus on in-development features (i.e. native notebooks, gather)

P0 Test Scenarios
Interactive Window

[ ] Start and connect to local Jupyter server

Open the file src/test/datascience/manualTestFiles/manualTestFile.py in VSCode
At the top of the file it will list the things that you need installed in your Python environment

Please note, when installing PyTorch please visit pytorch.org to determine how to install torch for your environment. Do not run pip install torch as that will not suffice.

On the first cell click Run Below
Interactive Window should open, show connection information, and execute cells
The first thing in the window should have a line like this: Jupyter Server URI: http://localhost:[port number]/?token=[token value]

[ ] Verify basic outputs

Run all the cells in manualTestFile.py
Check to make sure that no outputs have errors
Verify that graphs and progress bars are shown

[ ] Verify export / import

With the results from Start and connect to local server open click the Export as Jupyter Notebook button in the Interactive Window
Choose a file location and save the generated .ipynb file
When the prompt comes up in the lower right choose to open the file in the browser
The file should open in the web browser and contain the output from the Interactive Window
Try the same steps and choose to open the file in the ipynb editor.
The file should open in the Notebook Editor.

[ ] Verify text entry

In the Interactive Window type in some new code print('testing') and submit it to the Interactive Windows
Verify the output from what you added

[ ] Verify dark and light main themes

Repeat the Start and connect to local server and Verify basic outputs steps using Default Dark+ and Default Light+ themes

[ ] Verify tooltips in Python file that has been run in the interactive window

After manualTestFile.py has been run in the interactive window, place your cursor over the myTensor variable.
Verify that the tooltip that appears contains four lines where the first line says myTensor: Tensor, the second line has shape information, the third line has dtype information, and the fourth line has device information.

[ ] Verify Variable Explorer

After manualTestFile.py has been run drop down the Variables section at the top of the Interactive Window
In the Variables list there should be an entry for all variables created. These variables might change as more is added to manualTestFile.py.
Check that variables have expected values. They will be truncated for longer items
Sort the list ascending and descending by Type. Also sort the list ascending and descending by Count. Values like (X, Y) use the first X value for Count sort ordering
Check that list, Series, ndarray, DataFrame and Tensor types have a button to "Show variable in data viewer" on the right
In the Interactive Window input box add a new variable. Verify that it is added into the Variable Explorer
Export the contents of the interactive window as a notebook and open the notebook editor
Find the first cell and click on the Run Below button
Open the variable explorer and verify the same variables are there
Add a new cell with a variable in it.
Run the cell and verify the variable shows up in the variable explorer

[ ] Verify Data Explorer

From the listed types in the Variable explorer open up the Data Viewer by clicking the button or double clicking the row
Inspect the data in the Data Viewer for the expected values
[ ] Verify Sorting and Filtering

Open up the myDataFrame item
Sort the name column ascending and descending
Sort one of the numerical columns ascending and descending
Click the Filter Rows button
In the name filter box input 'a' to filter to just name with an a in them
In one of the numerical columns input a number 1 - 9 to filter to just that column
In the 'b' filter box input '> -inf'. Verify that this filters to show just the rows with 1 and 4 in the 'b' column.
In the 'c' filter box input '= nan'. Verify that this filters to show just the row with 'nan' in the 'c' column.
In the 'd' filter box input '<= inf'. Verify that this shows all rows.
In the 'd' filter box input '== inf'. Verify that this just the row with 'inf' in the 'd' column.

Open the myList variable in the explorer
Make sure that you can scroll all the way to the end of the entries

[ ] Verify debugging

Open the file src/test/datascience/manualTestFiles/manualTestFile.py in VSCode
On the first cell click Run Below
Interactive Window should open, show connection information, and execute cells
Go back to the first cell and click Debug Cell
Debugger should start and have an ip indicator on the first line of the cell
Step through the debugger.
Verify the variables tab of the debugger shows variables.
Verify the variables explorer window shows output not available while debugging
When you get to the end of the cell, the debugger should stop
Output from the cell should show up in the Interactive Window (sometimes you have to finish debugging the cell first)

Notebook Editor
Please run through the scenarios below for:

Native Editor (default in VS Code Insiders)
Custom Editor (please follow these instructions to enable Custom Editor in VS Code Insiders)

[ ] Open notebook and run cells

Create a brand new folder on your machine.
Create a new venv in that folder via command line / terminal python3 -m venv .newEnv.
Open VS Code with that folder selected as the current workspace.
Open command palette with Ctrl+Shift+P and select 'Jupyter: Create New Blank Notebook'. Notebook UI should open. Verify there is a single cell in the notebook.

(Native notebook only) The cell language (bottom right corner of the notebook cell) should be Python. The cell toolbar should be on the left.

Click on the kernel picker (for native editor: in the bottom right corner; for custom editor: in the top right corner) and select .newEnv from the quickpick that appears.
Add the following code to the empty notebook cell.

import sys
print(sys.executable)

Click the run button on the cell. You should be prompted to install ipykernel in .newEnv. Click the 'Install' button on the prompt to install ipykernel.
After ipykernel is installed the cell should execute successfully and display the current Python interpreter path in the cell output.
Verify that the Python interpreter path in the cell output matches the selected Python environment in the kernel picker.
Click on the kernel picker (for native editor: in the bottom right corner; for custom editor: in the top right corner) and select a different Python environment.
Rerun the first cell and verify that the path in the cell output matches the selected Python environment in the kernel picker.

[ ] Verify notebook editor IntelliSense

Open the src/test/datascience/manualTestFiles/manualTestFile.py in VSCode.
Run all of the cells in the file.
Interactive Window should open
Export the cells in the interactive window and open the notebook editor
Hover over each cell in the notebook editor and verify you get hover intellisense
Add a new cell in between cells
Add import sys and sys.executable to the cell
Move the cell around and verify intellisense hover still works on the import sys
Delete and readd the cell and verify intellisense hover still works.

[ ] Verify Notebook Keyboard Shortcuts

Select a notebook cell by clicking on it
Move selection up and down with j, k and arrow keys.
Focus a cell by double clicking on it or hitting the enter key when selected
Move selection through the code with the arrow keys.
Verify selection travels between focused cells
Hit escape when a cell has focus and verify it becomes selected instead of focused
Hit y on a markdown cell when not focused and see that it becomes a code cell
Hit m on a code cell when not focused and see that it becomes a markdown cell
Hit l on a code cell and verify line numbers appear
Hit o on a code cell with output and verify that outputs disappear
Hit d + d and verify a cell is deleted.
Hit z and verify a deleted cell reappears
Hit a and verify the selected cell moves up
Hit b and verify the selected cell moves down
Hit shift+enter and verify a cell runs and selection moves to the next cell
Hit alt+enter and verify a cell runs and a new cell is added below
Hit ctrl+enter and verify a cell runs and selection does not change

[ ] Verify notebook outputs

Open the src/test/datascience/manualTestFiles/manualTestFile.py in VSCode.
Run all of the cells in the file.
Interactive window should open
Export the cells in the interactive window and open the notebook editor
Run all the cells in the notebook editor and verify the same outputs appear as in the interactive window

P1 Test Scenarios

[ ] Connect to a remote server

Open up a valid python command prompt that can run jupyter notebook (a default Anaconda prompt works well)
Run jupyter notebook to start up a local Jupyter server
In the command window that launched Jupyter look for the server / token name like so: http://localhost:8888/?token=bf9eae43641cd75015df9104f814b8763ef0e23ffc73720d
Run the command Python: Select Jupyter server URI then Type in the URI to connect to a running jupyter server
Input the server / token name here
Now run the cells in the manualTestFile.py
Verify that you see the server name in the initial connection message
Verify the outputs of the cells

[ ] Interactive Window commands

[ ] Verify per-cell commands

Expand and collapse the input area of a cell
Use the X button to remove a cell
Use the Goto Code button to jump to the part of the .py file that submitted the code

[ ] Verify top menu commands

Use X to delete all cells
Undo the delete action with Undo
Redo the delete action with Redo
In manualTestFile.py modify the trange command in the progress bar from 100 to 2000. Run the Cell. As the cell is running hit the Interrupt Jupyter Kernel button
The progress bar should be interrupted and you should see a KeyboardInterrupt error message in the output
Test the Restart Jupyter kernel command. Kernel should be restarted and you should see a status output message for the kernel restart
Use the expand all input and collapse all input commands to collapse all cell inputs

[ ] Verify theming works

Start Interactive window
Add a cell with some comments
Switch VS Code theme to something else
Check that the cell you just added updates the comment color
Switch back and forth between a 'light' and a 'dark' theme
Check that the cell switches colors
Check that the buttons on the top change to their appropriate 'light' or 'dark' versions
Enable the 'ignoreVscodeTheme' setting
Close the Interactive window and reopen it. The theme in just the 'Interactive' window should be light
Switch to a dark theme. Make sure the interactive window remains in the light theme.

[ ] Verify code lenses

Check that Run Cell Run Above and Run Below all do the correct thing

[ ] Verify context menu navigation commands

Check the Run Current Cell and Run Current Cell And Advance context menu commands
If run on the last cell of the file Run Current Cell And Advance should create a new empty cell and advance to it

[ ] Verify command palette commands

Close the Interactive Window then pick Python: Show Interactive Window
Restart the kernel and pick Python: Run Current File In Interactive Window it should run the whole file again

[ ] Verify shift-enter

Move to the top cell in the .py file
Shift-enter should run each cell and advance to the next
Shift-enter on the final cell should create a new cell and move to it

[ ] Verify file without cells

Open the manualTestFileNoCells.py file
Select a chunk of code, shift-enter should send it to the terminal
Open VSCode settings, change Send Selection To Interactive Window to true
Select a chunk of code, shift-enter should send that selection to the Interactive Windows
Move your cursor to a line, but don't select anything. Shift-enter should send that line to the Interactive Window

[ ] Multiple installs

Close and re-open VSCode to make sure that all jupyter servers are closed
Also make sure you are set to locally launch Jupyter and not to connect to an existing URI
In addition to your main testing environment install a new python or miniconda install (conda won't work as it has Jupyter by default)
In VS code change the python interpreter to the new install
Try Run Cell
You should get a message that Jupyter was not found and that it is defaulting back to launch on the python instance that has Jupyter

[ ] LiveShare Support

Install the LiveShare VSCode Extension
Open manualTestFile.py in VSCode
Run the first cell in the file
Switch to the Live Share tab in VS Code and start a session

[ ] Verify server start

Jupyter server instance should appear in the live share tab

Open another window of VSCode
Connect the second instance of VSCode as a Guest to the first Live Share session
After the workspace opens, open the manualTestFile.py on the Guest instance
On the Guest instance run a cell from the file, both via the codelens and via the command palette Run Cell command

[ ] Verify results

Output should show up on the Guest Interactive Window
Same output should show up in the Host Interactive Window

On the Host instance run a cell from the file, both via the codelens and via the command palette

[ ] Verify results

Output should show up on the Guest Interactive Window
Same output should show up in the Host Interactive Window

Export the file to a notebook
Open the notebook editor on the host
Run a cell on the host
Verify the editor opens on the guest and the cell is run there too

[ ] Jupyter Hub support

Windows install instructions

Install Docker Desktop onto a machine
Create a folder with a file 'Dockerfile' in it.
Mark the file to look like so:

ARG BASE_CONTAINER=jupyterhub/jupyterhub
FROM $BASE_CONTAINER

USER root

USER $NB_UID

From a command prompt (in the same folder as the Dockerfile), run docker build -t jupyterhubcontainer:1.0 .
Run docker container create --name jupyterhub jupyterhubcontainer:1.0 jupyterhub
From the docker desktop app, start the jupyterhub container.
From the docker desktop app, run the CLI

OR Mac / Linux install instructions

Install docker
From the terminal docker run -p 8000:8000 -d --name jupyterhub jupyterhub/jupyterhub jupyterhub
Open a terminal in the docker container with docker exec -it jupyterhub bash
From that terminal run python3 -m pip install notebook

From the new command prompt, run adduser testuser

Follow the series of prompts to add a password for this user

Open VS code

Open a folder with a python file in it.

Run the Python: Specify local or remote Jupyter server for connections command.

Pick 'Existing'

Enter http://localhost:8000 (assuming the jupyter hub container was successful in launching)

Reload VS code and reopen this folder.

Run a cell in a python file.
[ ] Verify results 1. Verify you are asked first for a user name and then a password. 1. Verify a cell runs once you enter the user name and password 1. Verify that the python that is running in the interactive window is from the docker container (if on windows it should show a linux path)

[ ] Verify ability to open data viewer from debugger

Open the file src/test/datascience/manualTestFiles/manualTestFileDebugger.py in VS Code
Set a breakpoint on the last line
Open the debug panel in the left sidebar of VS Code and run 'Python: Current File' debug configuration
All the variables defined in the file should appear in the debug variables window in the sidebar
Right click on each of the following variables and select the 'View Variable in Data Viewer' option from the context menu: myNparray, myDataFrame, mySeries, myList, myString, myTensor. Verify that the data viewer opens and displays them
Expand the tree view for the variable x. Right click on its instance member b and select 'View Variable in Data Viewer' from the context menu. Verify that this opens x.b and not b in the data viewer.

[ ] Run by line

Opt into the custom editor experiment (not yet supported in native notebooks)
Open a new blank Jupyter notebook.
Add the following code to a cell:def bar():
    for i in range(5):
        print(i)

def foo():
    bar()

foo()
print('Done')

Press F10 to step through the code in the cell line-by-line. Verify that it first steps over function definitions for foo() and bar(), then steps into the function definitions after foo() is called, then steps back out when the loop in bar() finishes and prints 'Done'.

P2 Test Scenarios

[ ] Directory change

[ ] Verify directory change in export

Follow the previous steps for export, but export the ipynb to a directory outside of the current workspace
Open the file in the browser, you should get an initial cell added to change directory back to your workspace directory

[ ] Verify directory change in import

Follow the previous steps for import, but import an ipynb that is located outside of your current workspace
Open the file in the editor. There should be python code at the start to change directory to the previous location of the .ipynb file

[ ] Interactive Window input history history

Start up an Interactive Window session
Input several lines into the Interactive Window terminal
Press up to verify that those previously entered lines show in the Interactive Window terminal history

[ ] Extra themes 1. Try several of the themes that come with VSCode that are not the default Dark+ and Light+

Others

[ ] IPyWidgets
[ ] Plot Viewer

I am sorry, but this is not a reasonable test plan item. I will not do it. cc @sandy081

Agreed. @DonJayamanne It is a general recommendation that a TPI shall not take too long to test and also scoped to a specific feature. Complexity 5 is not unlimited and there shall be a time scope of one or two hours max of testing. It seems this TPI has multiple features to test and also goes beyond complexity 5 and time scope.
So, can you please break this down into multiple complexity (1-5) test plan items and let me know? I will do the assignments again. Until then I am un-labelling this test plan item. Sorry about it.

@Don Jayamanne suggestions: Instead of exhaustively testing all functionality in the extension, either have one TPI that briefly touches all functionality. Or, multiple TPIs where each focuses on one feature area. Maybe the first, I don't know that you need us to test every line of code in the extension.
Also, run by line is covered in another TPI, so no need to test that here. Also I don't understand the theming section

Check that the cell you just added updates the comment color

in another TPI, so no need to test that here. Also I don't understand t

The test plan needs to be updated. I'm making notes where necessary.
The run by line was already there (part of the original test plan we created for Juyter extesnion)

Closing in favor of https://github.com/microsoft/vscode-jupyter/issues/7238


Default diff notebook

Adds ipython notebook to generate diffs between the files in api/api_autogen/library/defaults.

I modified the output to be a JSON containing 4 nested dictionaries:

'Cmods with new defaults files'
Cmods listed here have new default configuration files in the new Release. This may occur with a new SAM configuration, or if an existing SAM configuration added or switched a cmod, e.g. PVWatts using v8 instead of v7

'Cmods with removed defaults files'
Cmods listed here have deleted default configuration files in the new Release. This may occur with a deleted SAM configuration.

'Cmods with modified variables'
There are three categories here: 'Added variables', 'Removed variables' and 'Type changed'.

'Configs with modified defaults'
This is an option that records the default values that have changed. For variables whose lengths are greater than or equal to 8760, the value changes are only reported for the first index to save space.

Note: Since this file uses the Default files to search for variable changes, and Default files do not exist for cmods not in a SAM configuration (e.g. modules providing helper functions or older versions, listed here: https://nrel-pysam.readthedocs.io/en/master/Models.html#other-modules-names-and-descriptions), for these cmods, variable changes will not be tracked by this current method.

Let's evaluate adding this to the Github Actions for this PR. If we decide not to add to GHA, then feel free to merge this after you've reviewed the changes I made.


Change selection background from Base0A to Base02

Solves #12.
I changed the background of selected items to Base02 and their foreground to Base05 (keeping the same colour even when selected - there is no selection foreground in the styling guide).
Also, I changed the completion.selected.match.fg to be the same as completion.match.fg - IMO the selected bg changes only a bit and the foreground is supposed the stay the same. I'm not sure about this. What do you think?
A bit off topic, the minimal template seems to be different from default even when it does not make sense - e.g. the completion title is Base0A vs Base0D. Is there any reason for this? Should we unify it?

Sorry for the long waiting time!
I highly appreciate efforts to have base16-qutebrowser as coherent as possible.

A bit off topic, the minimal template seems to be different from default even when it does not make sense - e.g. the completion title is Base0A vs Base0D. Is there any reason for this? Should we unify it?
the minimal template was provided by @dgmulf in #3. I will support it in a best effort manner, i.e. I do not use this scheme, so I cannot test it in depth.

As a consequence I don't have any objections about changes in the minimal theme. Maybe @dgmulf has some?


DRAFT Bug Fix: AutoCompletePlugin in Lexical Playground.  Remove waterfall update - use recommended node transform

Description
Current Behavior: https://github.com/facebook/lexical/issues/6156
Steps to Reproduce:

Go to Playground, enable autocomplete
Start typing a word for example "International". Make sure to pause between letters so HistoryPlugin catches each letter as separate change.
Try to CTRL-Z couple of times.
In effect Autocomplete stops working, and (TAB) is stuck next to cursor.

Changes Added
This PR updates the AutoCompletePlugin within the Lexical Playground to registerNodeTransform for the Root Node and handleUpdates. This avoids incompatibility issues with undo/redo functionality in the HistoryPlugin.
Closes #6156
Test plan
Before
Insert relevant screenshots/recordings/automated-tests
After
Insert relevant screenshots/recordings/automated-tests

Reviewing lexical history plugin. Above change removed waterfall update which is incompatible undo/redo but did not fix issue.
There continue to be issues with repeated undo's and the update events leading to the editor state getting out of sync with the auto complete suggestion. Eventually this continues to create an infinite loop with repeated queries.
Continuing to investigate if this has to do with plugin and playground implementation or if there is something that can be done to the lexical core packages to avoid this from occuring.


sleep after running a spec

Is your feature request related to a problem? Please describe.
sleep after running a spec
Describe the solution you'd like
await spec()
  .get('/path')
  .expectStatus(200)
  .sleep(1000);

Describe alternatives you've considered
await spec()
  .get('/path')
  .expectStatus(200);

await sleep(1000);

Additional context
Can be used in spec handlers.

@ASaiAnudeep I would love to work on this. Can I give it a try?


[Feature request] Make "stack" column items into links

Is your feature request related to a problem? Please describe.
YES. I'm constantly looking at my list of services/containers and then having to go to any given service's stack, which means I have to go back tot he left hand menu, click stacks, then navigate the list of stacks for the one I want, click it. Way too many unneeded steps when doing it often.
Describe the solution you'd like
In mentioned services/containers lists, there's a column item showing which stack any item belongs to; just turn it into a link to that item's stack page. :)
Everything needed is already there, it seems like it would be a 30 second addition.

@YouveGotMeowxy
Thank you for the information.  Product has reviewed.  I have opened an internal JIRA.
Thanks!


Fix memory leaks on getaddrinfo

Hi,
Congratulations for the tool! I noticed two memory leaks on addrinfo struct. I think this patch fixes them.

Thanks! Good catch


[SPARK-42463][YARN][TESTS] Clean up the third-party Java files copy introduced by SPARK-27180

What changes were proposed in this pull request?
SPARK-27180 introduced some third-party Java source code  to solve Yarn module test failure,  but maven and sbt can also test pass without them, so this pr remove these files.
Why are the changes needed?
Clean up the third-party Java source code copy in Spark.
Does this PR introduce any user-facing change?
No
How was this patch tested?

Pass GitHub Actions
manual check:

Maven
build/mvn clean
build/mvn clean install -DskipTestes -pl resource-managers/yarn -am -Pyarn
build/mvn -Dtest=none -DwildcardSuites=org.apache.spark.deploy.yarn.YarnClusterSuite -pl resource-managers/yarn test -Pyarn
build/mvn test -pl resource-managers/yarn -Pyarn -Dtest.exclude.tags=org.apache.spark.tags.ExtendedLevelDBTest

Both YarnClusterSuite and full module test passed.
SBT
build/sbt clean yarn/test -Pyarn -Dtest.exclude.tags=org.apache.spark.tags.ExtendedLevelDBTest

All tests passed.

cc @wangyum FYI

Could you test against hadoop-2?

Could you test against hadoop-2?

Do these check with -Phadoop-2
Maven
build/mvn clean
build/mvn clean install -DskipTestes -pl resource-managers/yarn -am -Pyarn -Phadoop-2
build/mvn -Dtest=none -DwildcardSuites=org.apache.spark.deploy.yarn.YarnClusterSuite -pl resource-managers/yarn test -Pyarn -Phadoop-2
build/mvn test -pl resource-managers/yarn -Pyarn -Dtest.exclude.tags=org.apache.spark.tags.ExtendedLevelDBTest  -Phadoop-2

SBT
build/sbt clean yarn/test -Pyarn -Dtest.exclude.tags=org.apache.spark.tags.ExtendedLevelDBTest -Phadoop-2

All tests passed.

Merged to master


Laura feedback #3

I think the website's information hierarchy could be streamlined. Below is a suggestion for how I think it should be organized, but I think it warrants more discussion. In my suggestion below, I've split some pages into multiple, and I've renamed pages -- all with the goal of making content easier to find.
Basics of your job

Job description
Conduct on the job [put the "Food and Drink" content here]
Timecards
Breaks
Sick time
Emergencies & emergency contacts

Your responsibilities

Opening the Center
Closing the Center
Staffing the reference desk [put "DRMC Overview" content here]
Phones
Tours
Events [new section -- should mention chair setup here, and what generally needs to be done during events]
Projects

The DRMC

History
Accessing the Center
Past exhibitions and events [new page]

Finding Maps
Definitely could use more discussion, but this is what I'm thinking for now!

I love the "Food and Drink" page on the website. However, I think we should rename that page to be something about "Conduct" because there is more than just info about food & drink there.


how to extract figures in pdf ?

After setup, I tried
1.
doc.figures
2.
json.dump
but the results showed only figure box's position and its metadata, how can i get figure in the pdf?

Hey @Myfootnotsmelly , sorry looks like a bug introduced; adding in this pull request: https://github.com/allenai/papermage/pull/73

Hihi please take a look at my response to this Issue https://github.com/allenai/papermage/issues/70
Yes, figures are represented by bounding boxes:

If you want the image crop of the figures, here's how you'd do it:
# get the image of a page and its dimensions
page_image = doc.images[page_id]
page_w, page_h = page_image.pilimage.size

# get the bounding box of a figure
figure_box = figures[0].boxes[0]

# convert it
figure_box_xy = figure_box.to_absolute(page_width=page_w, page_height=page_h).xy_coordinates

# crop the image using PIL
page_image._pilimage.crop(figure_box_xy)


[crashpad] Support Linux/Android targets and arm64 architecture

Is your feature request related to a problem? Please describe.
Can only build Crashpad for Windows/Mac currently, although Crashpad supports building for more triplets than allowed by this port currently.
Proposed solution
Would like to use this port to build Crashpad for Android arm64 at least. Would also like to build it cross-platform (e.g. on Windows via Android NDK). The latter would require updating mini_chromium's BUILD.gn file accordingly.
Describe alternatives you've considered
Removing the vcpkg_fail_port_install call and building on Linux.
Additional context
I've created a private version of this port that builds for Android on Windows and applies patches to mini_chromium accordingly. Will consider publishing PR with suggested changes, if possible, but that will require more thorough testing of more triplets.

This issue hasn’t been updated in 3 month, if it is still an issue, please reopen this issue.


ExpensifyHelp resource updates for VIP-Travel

ExpensifyHelp article - 'Approving travel ' - New Expensify version
There are 8 articles in total, all in this Google Doc
Article breakdown:
New Expensify

What is Expensify Travel?
Booking and managing travel
Configuring travel preferences
Approving travel

etc
Expensify Classic

What is Expensify Travel?
Booking and managing travel
Configuring travel preferences
Approving travel

Publish date: May 1st

Waiting for Ren's review!

Still waiting on Ren

OK, current state - need this to hit staging to grab screenies of the ND flow, then will update the doc, have Ren re-review, and then set this all live.

Oops—I was working on the article before I was even assigned. Ha! I'm ready to be assigned!

These are all ready for review again, Ren!

Waiting for the deploy today so I can get back into our demo environment and then I'll address the remaining comments.

Still waiting on that deploy

Merge freeze in place until at least Thursday morning.

We're deploying travel-related things, so hope to be able to get back in tomorrow morning and get this all wrapped up

Good to go, except for one clarifier on exactly how the 'Get Support' button should look in the emailed itinerary. Checking with Spotnana, will update if needed, then we'll be ready to set these live.

That button isn't working, but it should be there, so these are fine to publish as is

Payment due on Thursday

Actually, this can be closed.


Support integration with django-reversion

Are there any plans to or an opinion on supporting a deeper integration with django-reversion?
E.g. Do not delete files of objects which are under version control but delete them in case the last version referencing this particular file is deleted.
We do need this in our project and I would be happy to contribute any work as a PR.

Would a custom storage class on your file fields work for your case? Using a custom storage class for your file fields under version control would allow you to provide your own custom implementation of the ‘delete()’ method.
Docs: https://docs.djangoproject.com/en/3.1/howto/custom-file-storage/

Unfortunately, a storage class would not help (so I think)
I could only decide if I want to delete a file or not - but I would not have the context the object is currently in and could not come to a qualified conclusion.
Some use cases:

If a model is under version control, do not delete any files by default as a rollback can happen any time
If a model is not under version control, delete the file as normal.
If a Version/Reversion of a model is deleted, we need to check, if other versions exists referencing the same file. (I think it would sufficient to check the predecessor and next version.)

Yes: rollback to this version would still be possible, thus we should not delete the file.
No: Delete the file.

Deleted models can be rolled back, too. Do not delete any files until the Reversion/Version is permanently deleted.

Deleting a Reversion/Version of a object can happen either manually (calling delete()) or by running the maintenance command of django-reversion which deletes reversions with an age older a specified time.

This won't work as deleting a version/reversion model object would not trigger django-cleanup nor the delete method of the FileField.
The version objects are only models with some metadata and an attribute which holds a serialized form of the original object. Deleting them won't trigger anything related to the FileField of the original model.
If a (re)version is deleted, we would need to deserialize the original object, find all FileFields and check them, if the referenced file can be actually deleted.
PS: As django-reversions uses de/serialization of the original object, it does not handle schema updates of the model which leads to unexpected errors when trying to restore old objects with an outdated schema.
Because of this, my current POC of the implementation is on hold as it seems that I won't/cannot use django-reversions in my project.


Status is not visible

When you will see your tickets on dashboard you will not be able to see status of your ticket.
Add the status option where you can see current status of your  ticket.

May i resolve this issue?
Suggested changes:

Below the progress bar in the ticket card status of the ticket should be displayed below.
if the status is completed then there is no need to display the progress bar and Background color of the ticket card should change to some other color.

Hi @MadhavDhall,
thank you for showing your interest in resolving the issue
your implementation seems good enough
you may go ahead and open a PR to implement the feature.


PopulateDB should also generate some digital products

What I'm trying to achieve
It would be great to have logic in populateDB to generate digital product type with some test digital products.

Can I take this up? How do I get started?

Yeah sure, you can take this!
All logic for populated DB is here saleor/core/utils/random_data.py
Model of DigitalContent is here: saleor.product.models.DigitalContent
The flow of the creation, you can find in this test - test_fetch_single_digital_content , please check the logic inside the fixtures which are responsible for creation of all objects.


refactor: move from io/ioutil to io and os package

The io/ioutil package has been deprecated in Go 1.16 (See https://golang.org/doc/go1.16#ioutil). Since this project has been upgraded to Go 1.17 in #5889, this PR replaces the existing io/ioutil functions with their new definitions in io and os packages.
/kind cleanup

I'm -1 on this change for the time being.
This requires all consumers and builders of containerd to upgrade to go1.17.

I'm -1 on this change for the time being.
This requires all consumers and builders of containerd to upgrade to go1.17.

@cpuguy83 Go 1.16 is sufficient. All new definitions are available since Go 1.16.

I think @cpuguy83 may be referring to a similar change we had in moby, what broke in moby was the use of io.FileInfoToDirEntry(), which is available only in Go 1.17 (haven't checked yet if this PR uses that); see https://github.com/moby/moby/pull/42797

oh! I see you opened that PR as well 🤦 😂

I think @cpuguy83 may be referring to a similar change we had in moby, what broke in moby was the use of io.FileInfoToDirEntry(), which is available only in Go 1.17 (haven't checked yet if this PR uses that); see moby/moby#42797

This PR doesn't use the fs.FileIntoToDirEntry that is available only in Go 1.17. The moby/moby#42792 PR that I opened used fs.FileIntoToDirEntry because I didn't want to rewrite the logic in pkg/plugins/discovery.go, which might have caused the tests to break 😅
In some cases ioutil.ReadDir cannot be completed replaced by os.ReadDir due to os.ReadDir returns a slice of os.DirEntry rather than a slice of fs.FileInfo. However, this transition seems to be smooth for containerd and all usage of ioutil.ReadDir can be replaced without problems.


Adds shortcut for save schema

JIRA: https://issues.jboss.org/browse/AEROGEAR-7577
Changes:

Pressing ctrl + s when editor is focused triggers #save method.
Toolbar is now a class component to allow disable/enable of buttons (it doesn't update only if props change, it has to have a state)
"Save" button in Toolbar is disabled once the schema is saved, and enabled when schema changes.

I was able to verify the change in the UI. Can't speak about the code.
@pb82 @josemigallas I think it is a good idea to disable the save button. This gives some feedback to the user that the schema is saved. But, can we show an additional message like "Schema Saved" or something? For example like http://www.patternfly.org/pattern-library/communication/toast-notifications/
Take this as a general comment. Similar lack of feedback exists in saving a data source etc.

@aliok I think this is a reasonable suggestion. We can display a notification when the schema was saved succesfully and only enable the button if the document has changed.

@josemigallas don't let my comment about feedback block this PR.
@pb82 shall I create a JIRA ticket for that?

@josemigallas Does it also work with Cmd+S ? If not, should it? I am not on a Mac, can't test.

@aliok

can we show an additional message like "Schema Saved" or something?

Definitely, thanks for creating the JIRA.

Does it also work with Cmd+S ?

CMD+S won't work. In their docs they say it should be possible with@keydown("crtl + s", "cmd + "), but it simply doesn't work. I even files an issue.
@pb82 @aliok What we should add IMO is an indication of the shortcut. I tried adding a tooltip to the button but they way we have implemented the Toolbar, it's simply too complex to add tooltips. Any ideas?

@josemigallas Why is it too complex? A tooltip could be passed to the toolbar as an additional (optional) parameter per button.

Again, is not about how to tell the toolbar but how to actually render the buttons. I will update the code to show you.

@aliok @pb82 This what it would look like: https://github.com/josemigallas/data-sync-ui/commit/f45a01650e83710c6b0aad3545be1f38a1550631
I am going to merge this anyway first, we can add the tooltip later.


Feature/sm land physics

This PR is related to the updates in PR 151
Preprocessors for Issues 146 and 147 are here.

The changes seem touch on two unrelated topics:  (i) the revised regridding (weminIN and weminOUT...) and (ii) a newer functionality that handles dynamically varying vegetation and albedo inputs.  Do the latter depend on other PRs?

Agreed about WEmin. There is not yet a GMAO_Shared PR, but there's a branch for the regridding updates relating to WEmin.
Issue: https://github.com/GEOS-ESM/GEOSgcm_GridComp/issues/116
Branch: https://github.com/GEOS-ESM/GMAO_Shared/compare/feature/jstassi/added-wemin-wemout-options
If these are updates for WEmin, I suggest they get merged into that branch. But it looks like they're an older version? And should just be removed from this branch to avoid confusion.

If I'm reading this correctly, the PR is to merge into "master".  Is this already on develop?
Not all repositories have enough activity to need a separate develop branch. It looks like GMAO_Shared is one of those.

Is this PR still desired?   It is over a year old.     Should we expedite or delete?

Is this PR still desired?   It is over a year old.     Should we expedite or delete?

OK I'll close the PR for now, shall keep the branch though.

OK I'll close the PR for now, shall keep the branch though.


Enable navigation arrows on mobile?

Is there a way to display navigation arrows on mobile? I ask because it's not 100% obvious that the user should drag left and right. There is also no "notice" displayed.

The default CSS shows navigation on hover only. There is no hover on mobile though...
Currently, we don't even build the navigation on mobile. Would you want to show the navigation all the time?

FWIW, We had a lot of requests for this on our WordPress plugin version of featherlight and ended up making the default CSS include the navigation arrows. People found it confusing that there was no indication that you were viewing a gallery on mobile.
That said, our styles are significantly different from the default featherlight styles, so it was easier to accommodate the request. The default featherlight styles are kind of overwhelming on a small screen.

@marcandre yes I'd be interested in showing the left and right arrow all the time on mobile. Would it be something easily accessible through featherlight's CSS? I admit I have not looked into it yet.
Another option could be showing a "Drag and left or right to view more images" notice on mobile or something. Like right below the image.

We don't generate the navigation buttons at all on mobile, but I guess we could and hide them, so you could override the CSS if you want.

The mobile view is so frustrating so far. I used my own work around to hide the default navigation and implemented my own/simpler prev/next arrows using a background image for featherlight-next and -previous. So I'd like to have them display all the time on mobile, especially since swipe won't work on my site right now.
The fixes I've tried in featherlight.gallery.css won't allow me to do this even with a display block(below), do you have any recommendations? I'm wondering if the problem is how I implemented my custom arrows, which would suck since it looks great on desktop, haha.
/* Always display arrows on touch devices */
@media only screen and (max-device-width: 1024px){

	.featherlight-next span,
	.featherlight-previous span {
		display: block;
	}

I have a case were i need to display the navigation buttons on mobile too. I think this is an implementation detail and should not be dictated by the plugin.
In order to not break any current implementations it would probably be best to leave the default as is and add an option to override this feature.
Would you mind adding this or point me to the right direction so I can create a pull request?

I think the best solution is probably to add a class to featherlight called 'featherlight-touch-enabled', and rely on this to hide the buttons in the default css, so maybe no option per say? Any better suggestions?

@marcandre Im fine with that too. Was just thinking about compatibility when people upgrade the lib. But it shouldn't cause any pain when upgrading the default styles too - right?

@maxfrigge Indeed. I'd mention in the Changelog that there was also a change in the CSS

@marcandre Sounds great! Let's do this :)
Let me know if there is anything I can contribute.

@maxfrigge You can try implementing it and creating a PR if you want

Hi,
I found that if you use the beforeOpen you can append the arrows onto the gallery.
Example below:
$('a.gallery').featherlightGallery({
previousIcon: 'Previous',
nextIcon: 'Next',
gallery: {
fadeIn: 300,
fadeOut: 300
},
beforeOpen: function(event){
var self = this;
self.$instance.find('.'+self.namespace+'-content')
.append(self.createNavigation('previous'))
.append(self.createNavigation('next'));
},
openSpeed: 300,
closeSpeed: 300
});

Thank very much!
beforeOpen works fine :)


Cannot connect to WhatsApp

On first startup I get the following error:
$ ./bot --bot="+NUM1" --receiver="+NUM2"
2021-10-16 18:14:39	debug	client	[signal] new subscription to whatsapp
2021-10-16 18:14:39	debug	queue	new subscription
error during login: error decoding login resp: json: cannot unmarshal array into Go value of type map[string]interface {}

I see this error message being discussed in the repos for go-whatsapp. Perhaps a fix from there must be ported here?

as a fix, edit file whatsapp/setup.go and add wac.SetClientVersion(2, 2123, 7) in a new line right after wac, err = whatsapp.NewConn(5 * time.Second)

That latest error can be fixed by using the code from: https://github.com/Rhymen/go-whatsapp/commit/8029c28f5c5a82145e324af228ac64354f07b4e8
I changed the code at<EMAIL_ADDRESS>as in the commit above and then  rebuilt the bot with go build -a -o bot ..
The logs now say:
login successful, session: {BUNCH_OF_STUFF_HERE}
2021-10-17 00:32:45	debug	client	[whatsapp] new subscription to signal
2021-10-17 00:32:45	debug	queue	new subscription
2021-10-17 00:32:45	debug	client	[whatsapp] publish &{    service started <nil> <nil>} to whatsapp
2021-10-17 00:32:45	debug	queue	publish &{    service started <nil> <nil>} to whatsapp
2021-10-17 00:32:45	debug	queue	received message on whatsapp : &{    service started <nil> <nil>}
2021-10-17 00:32:45	debug	client	[signal] received message on whatsapp : &{    service started <nil> <nil>}
2021-10-17 00:32:45	debug	queue	received message on whatsapp : &{    service started <nil> <nil>}

but nothing arrives on my signal account.
I can receive signal messages manually using signal-cli, so I know that the registration of the phone number for signal worked... but alas the bridge still does not. work for me.
I'd welcome any help here.

@cobordism Have you been able to fix this yet?

Hi. Apologies for late reply. I have not been able to fix this yet. OTOH I have not really been trying recently.

My goal would be for the bridge to create a new Signal group chat for every contact or group on whatsapp so that replying in that signal group passes the message along to the correct whatsapp contact. That should be easier to work with than having all messages arrive in one channel on the signal side.

#2 would you care to reply to this as you've already used it before @cobordism ?


Fetch user before pass it to the restricted function

It may not be in the Redux store yet when we try to pass it in. So we dispatch if it's not in the store.

I am not sure I understand what problem we are trying to solve here. Aren't the components getting an update (rerender triggered by useSelector) when the user is finally fetched, even if it's not there when these components are first rendered? In other words, does it break somehow, or what is the issue here?
I'm trying to understand if we are firing an extra query to the backend that is worth firing or if it can be avoided. Moreover, would it be possible, if we have a use case for fetching user data here, to just do it during SSR instead? This way we could potentially avoid any issue from the beginning.

@pnicolli Consider the case where the user is logged out, then they log in and edit the page. Then we have to dispatch getUser, because the user isn't in the store yet. In this scenario there is no SSR request at a point in time when the user is logged in.

@pnicolli this is related to https://github.com/plone/volto/pull/6271, as a continuation, if the user info is not in the store, this PR makes sure it's in there, so we can use it in a restrict key in the block config.
It LGTM.

@pnicolli Consider the case where the user is logged out, then they log in and edit the page. Then we have to dispatch getUser, because the user isn't in the store yet. In this scenario there is no SSR request at a point in time when the user is logged in.

I thought the user should get into the store eventually when the user logs into the portal, but I trust you to have done more research than I did on the subject 😁  👍

@pnicolli not the case, but it's a good point. @davisagli thoughts?

Well I was thinking... maybe we should consider for Volto 19 to move the user info to an expander we get with the content? Would it be worth it? I don't want to clutter anybody's notifications though, so maybe I could give this a little more thought and discuss it at a Volto Team meeting

I also had the idea of fetching the user info when the user logs in, but it doesn't avoid the need for what we have in this PR, because sometimes the user loads the page from the server while already logged in.
I don't think user info belongs in an expander because it's information that does not depend on which content item is being fetched. It would also make it hard to cache content responses in a way that is shared between multiple users with the same roles.


Converting script to get address

Hi,
some transactions dont have address in inputs but just have script. How can i obtain address from it so i can get the same data as on your explorer?
brg

<EMAIL_ADDRESS>Blockchain ID ea035fb6-2614-4d35-afa8-b2f0c698c474


13b_metrics: create docments

Add docments to 13b_metrics.
See the style guide and contribution guide for more details (links will be added when created).
This requires a beginner familiarity with fastai. A possible exception is Core Metric, which probably requires a moderate familiarity with fastai.
For scikit-learn parameters, docments should be a paraphrase of scikit-learn documentation.
Docments progress:

[ ] Core metric
[ ] Single-label classification
[ ] Multi-label classification
[ ] Regression
[ ] Segmentation
[ ] NLP
[ ] LossMetrics

I started working on this yesterday. Working my way top to bottom, do not know much about segmentation though. WIll see how far i come :)


Formula derivation in the paper

Hello, I would like to ask how the step from the formula （4） to the formula  （6）in the paper is derived, and how is e obtained

Hello，I would like to ask if you train the Cifar10 data set through two layers of full connection. After I changed the network framework to 3 layers of full connection, the network models of gp and hp are not trained when running the RGB three-dimensional data set.


Protokoll SPAM // Error Log im Iobroker // State value to set for ... has to be stringified but received type "number"

Describe the bug
Der Error LOG wird beim verwenden über INFO vollgeschrieben
To Reproduce
Es passiert beim Starten der Kaffeemaschine
SIEMENS-TI9555X1DE
Screenshots & Logfiles

homeconnect.0
2022-12-09 13:49:55.404
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:54.404
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:53.408
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:52.465
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:52.247
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:52.243
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:51.951
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:51.942
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:51.930
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:51.403
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:49.410
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:48.406
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:43.403
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:42.403
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:41.401
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:40.432
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

homeconnect.0
2022-12-09 13:49:39.401
info
State value to set for "homeconnect.0.SIEMENS-TI9555X1DE-68A40E26FCF6.programs.active.options.BSH_Common_Option_ProgramProgress" has to be stringified but received type "number"

Versions:

Adapter version: V1.1.1
JS-Controller version: 4.0.23
Node version: v14.19.3
Operating system: Debian

Datenpunkt löschen und adapter neustarten hilft hier


Fixes #461 - Copy listeners array, so subscribes can't affect the loop.

Unsubscribing during a dispatch would change the listeners array.
However that causes the next listener not to fire.
Fixes #461

Awesome, thanks.


Update management sdk based on the new api version.

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

@jingjlii

Re-record the tests locally to make the CI pass.
Update the version in Azure.ResourceManager.Batch.csproj
There is a breaking change for BatchVmContainerConfiguration, the constructor has been changed from

public BatchVmContainerConfiguration() { }

to
public BatchVmContainerConfiguration(Azure.ResourceManager.Batch.Models.BatchVmContainerType containerType) { }

To mitigate this breaking change, we need to add the parameterless constructor back to the custom code and set the default value of Azure.ResourceManager.Batch.Models.BatchVmContainerType containerType for BatchVmContainerConfiguration. What would the default value be, DockerCompatible or CriCompatible?

@jingjlii

Re-record the tests locally to make the CI pass.
Update the version in Azure.ResourceManager.Batch.csproj
There is a breaking change for BatchVmContainerConfiguration, the constructor has been changed from

public BatchVmContainerConfiguration() { }

to
public BatchVmContainerConfiguration(Azure.ResourceManager.Batch.Models.BatchVmContainerType containerType) { }

To mitigate this breaking change, we need to add the parameterless constructor back to the custom code and set the default value of Azure.ResourceManager.Batch.Models.BatchVmContainerType containerType for BatchVmContainerConfiguration. What would the default value be, DockerCompatible or CriCompatible?

@live1206  Thanks for reviewing this PR. The default value of containerType should be DockerCompatible.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Batch


Cell height

Hi, following example code:
module MyCellStylesheet
  def my_cell_height
    300
  end

  def my_cell(st)
    st.frame = { l: 5, t: 100, w: screen_width, h: my_cell_height }
  end
end

No matter what I enter as my_cell_height (e.g. 300 or 10), the actual height of the cell doesn't change. I've tried with different cells and different heights but nothing happens. As the redpotion generator generates the code regarding the height, I assume this is the correct (and only) place to change the height.
 Thanks!

I'll check into this a bit later today.  I think that is a starting point for a cell height - but the table delegates are going to take over and resizing based on the content and/or defaults.

UITableViewCell heights are not governed by stylesheets, they're governed by the UITableViewDelegate methods, which are handily abstracted for you in ProMotion, so if you're using a PM::TableScreen, just return a cell hash back with the height you want:
{
  title: "Whatever",
  action: :whatever,
  height: 70
}

Documentation here: https://github.com/clearsightstudio/ProMotion/blob/master/docs/Reference/API Reference - ProMotion Table - Cell Options.md
If You're using a standard old UITableView, you'll have to set the table's delegate to self and then implement this method: - (CGFloat)tableView:(UITableView *)tableView heightForRowAtIndexPath:(NSIndexPath *)indexPath https://developer.apple.com/library/ios/documentation/UIKit/Reference/UITableViewDelegate_Protocol/

Thanks a lot for your fast reply. I'm using a PM::TableScreen and I'm a little confused now. If the stylesheets dont have any influence on the cell, why does the redpotion generator generate the my_cell_height method? I thought it is supposed to regulate the cell's height?

The generator is meant to give you a place to set the height in a stylesheet and then reference it in your cell hash in the controller, essentially keeping all your view logic all in the same place.
Check out the comments at the end of the generated cell view:
You can use this like so in your table_screen:

  def table_data
    [
      {
        title: "Section",
        cells: [
          { cell_class: BarCell, height: stylesheet.bar_cell_height, title: "Foo"},
          { cell_class: BarCell, height: stylesheet.bar_cell_height, title: "Bar"}
        ]
      }
    ]
  end

Sorry, I don't mean to annoy you but I stil find this confusing. I just created a test cell, this is the generated code:
module TestCellStylesheet
  def test_cell_height
    40
  end

  def test_cell(st)
    st.frame = {l: 5, t: 100, w: 80, h: test_cell_height}  # <--- this isn't possible then, right?
    st.background_color = color.light_gray

    # Style overall view here
  end

  def test_cell_title(st)
    st.frame = {l: 10, fr: 0, centered: :vertical, h: 20}
    st.font = font.medium
    st.color = color.black
  end
end
...

Now I use this code in my controller:
  def table_data
    [
      {
        title: "test",
        cells: [
          { cell_class: TestCell, height: stylesheet.test_cell_height, # line 20
          },
        ]
      },
    ]
  end

Then this is the error I end up with:
*** Terminating app due to uncaught exception 'NoMethodError', reason: 'settings_table_screen.rb:20:in `table_data': undefined method `test_cell_height' for nil:NilClass (NoMethodError)
	from table.rb:31:in `promotion_table_data'
	from table.rb:94:in `editable?'
	from table.rb:103:in `set_up_accessibility'
	from table.rb:23:in `screen_setup'
	from support.rb:17:in `try:'
	from screen_module.rb:20:in `screen_init:'
	from table_view_controller.rb:5:in `new:'
	from app_delegate.rb:9:in `on_load:'
	from delegate_module.rb:16:in `application:didFinishLaunchingWithOptions:'

No problem at all... did you include that module in your stylesheet for the PM::TableScreen?
Should be something like:
class SettingsTableScreenStylesheet < ApplicationStylesheet
  include TestCellStylesheet # if this line isn't here, your

  # other styles here
end

and in your tablescreen:
class SettingsTableScreen < PM::tableScreen
  stylesheet SettingsTableScreenStylesheet

  # other stuff here
end

hey @andersennl no annoyance at all!

*** Terminating app due to uncaught exception 'NoMethodError', reason: 'settings_table_screen.rb:20:in table_data': undefined method test_cell_height' for nil:NilClass (NoMethodError)

So when this is fired the stylesheet is nil.  do you have the stylesheet set in the screen like @markrickert listed above?

Yes, everything is included like in the example above. I was about to write that about the NoMethodError from the nil class as well. I've double checked the names...

ok, let me see if I can reproduce this, unless you have a public repo with the problem I can pull down and help debug?

That you both so much for your time. My project isn't online, it's mostly really basic, though. If you generate a table and a custom cell, you basically have my code ;)

@andersennl throwing together a quick project and see if I can help figure it out :+1:

im going to reopen this issue - 95% sure I can reproduce this bug!
I'll try and get a PR out to fix it this evening, sadly I cant work on it now as I have prior plans - but I have a local repo that I can reproduce the bug - thanks for reporting this @andersennl

You are welcome, thanks again for your help!

@andersennl as a work around, you should be able to do this.
 def table_data
    [
      {
        title: "test",
        cells: [
          { cell_class: TestCell, height: 40
          },
        ]
      },
    ]
  end

Yes that works, thanks! @squidpunch

@markrickert if you or someone else want to work on this before I get to it, feel free!
Essentially the problem is an order of operations.  When we call table_data the stylesheet is not set, its being set later in the process - but we've got to figure out why its not set before table_data
I can check it out later tonight (or more likely tomorrow AM) if someone doesn't work on a PR before I get to it :smile:


West Europe

Hello
When will this Preview be available in West or North Europe?
Thanks

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

ID: 9a558a9e-10d0-ea34-8780-d9084f87f952
Version Independent ID: 60dda4e0-7630-f358-aa3a-6a992eae61e2
Content: Managing the Azure Storage Lifecycle
Content Source: articles/storage/common/storage-lifecycle-managment-concepts.md
Service: storage
GitHub Login: @yzheng-msft
Microsoft Alias: yzheng

@iapple99 Thanks for bringing this to our attention. Your question has been shared with the content owner for further review.

any updates?

West EU is now enabled for preview.

#please-close

Please enable container delete based on age


Always display "File", but include help-text when no content is available.

Text: "The submitter of this resource did not include any associated files."
Rationale:
Folks are confused about why some resources don't have associated files (usually for Conference Presentations, for which only about 40% have presentation files)
Need to decide whether this should apply to Conference Presentations only or across the board.
May also decide to include it under "Link" and/or "Images".

Since this ticket was submitted, display has changed slightly so that there is now a section "Links and Files" rather than having these in separate blocks.
As such, I've altered this slightly to conditionally display the copy you provided (modified to say "[...] associated files or links" instead of just files) if there are neither files or links present. If there is a link but no file, it just displays the link, it seemed awkward to put your copy below that.
From a UX standpoint, if the section "Links and Files" just shows a link or two, it follows that there are no files, and vice versa, but it makes sense to have your copy in lieu of the section not displaying at all to clarify that there is no bug, there is just nothing to show.


add a couple of tests and fix an InitSpec bug

If an exception was expected but didn't happen, InitSpec wouldn't fail. Fixed that and added validation of that behaviour for both InitSpec and UpdateSpec.

Codecov Report

Merging #6 into master will increase coverage by 0.58%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master       #6      +/-   ##
============================================
+ Coverage     73.03%   73.62%   +0.58%
  Complexity      196      196
============================================
  Files            60       60
  Lines          1198     1202       +4
  Branches         60       61       +1
============================================
+ Hits            875      885      +10
+ Misses          308      303       -5
+ Partials         15       14       -1

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/com/spotify/mobius/test/UpdateSpec.java
100% <ø> (+10.52%)
5 <0> (ø)
:arrow_down:

...rc/main/java/com/spotify/mobius/test/InitSpec.java
80% <100%> (+17.5%)
2 <0> (ø)
:arrow_down:

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 786125a...c9a9d9e. Read the comment docs.


Any possibility to deactivate specific input types

We want to use your module for testing purposes on a Mage 2.1.1 env.
I'm struggeling right now to deactivate specific Input fields, like DOB, Awards and Type (generic stuff).
Deactivating the virtual-Nodes in the etc/di.xml doesn't do the job, theres only an exception. Is there a simple way to deactivate specific input types, or do I need to modify the whole module in order do sort out different input fields?
Thanks to whom it may concern, your help is very appreciated.

@grasdaggel You can take the extension and remove any fields you want from the Setup/Install.php and from the ui components:  list and form.
Then you will have to edit the interfaces and the frontend templates to delete what you need.
Basically search for any occurrence of dob  and remove what you don't want.
Only after you are done removing everything, install the extension.


fix(build): Use one version of firebase SDKs everywhere

Description
The logic to specify a baseline firebase SDK version and accept an override for same is fairly standardized across the repository but not applied uniformly or used everywhere
This PR harmonizes the logic across the repository, depends on firebase_core as needed in place of lower-level direct pod dependencies on ios and uses the BoM and core pod versions where ever possible
Related Issues
This is related to the forward port PR #4249 but is not a core part of that change, rather it makes that change easier while being independently correct and useful, so I'm submitting it separately for immediate consideration in order to shrink that PR and get feedback on utility
Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[ ] No, this is not a breaking change.

Admob Android CI failed because there are no retries on network fetches.
I've noted that before :smile: and have a fair bit of experience de-flaking these things, if the style I proposed for this repo could work then I could finish building it out and CI would be more reliable: #4265

Admob Android CI failed because there are no retries on network fetches.
I've noted that before :smile: and have a fair bit of experience de-flaking these things, if the style I proposed for this repo could work then I could finish building it out and CI would be more reliable: #4265


LSP server crashes when opening two different perl files in neovim

Title about covers it.
I'm new to LSPs and coc so it's probably some basic misconfiguration on my end but can't find anything that might help address this problem.
Using neovim 0.6.1 with latest version of coc. coc-perl installed with CocInstall.

Hi @sdondley, I'm very sorry for the months of delay.
I've tested locally, and it didn't crash, running neovim 0.6.1 too.
When it crashes, do you see any message errors or something like that?
That's very likely the issue is in the actual language server (https://github.com/richterger/Perl-LanguageServer), but it would be really helpful any error message or something like that.

@sdondley, it seems the issue was solved in the new release by https://github.com/richterger/Perl-LanguageServer/issues/155.
Since it has been quite some time since you opened this issue and it was not really related to the coc-perl plugin, I'm going to close this issue.
But please, feel free to reopen it or create a new one in case things keep crashing.
Thanks!