add wsjtz

WSJT-Z is a fork of WSJT-X. It's used for ham radio stuff (mainly two-way digital communication). This fork is primarily designed for automation and quality-of-life improvements. Homepage: https://sourceforge.net/projects/wsjt-z/
My first nixpkgs PR :3
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hi scd31
You need to set your package in nixpkgs/pkgs/by-name/ws/
Also pkgs/top-level/all-packages.nix i not needed now.
And last point you need to rename your commit wsjtz: init at 2.7.0-rc7-1.43
Best Regards

Hi,
Also i think you can change your meta to :
meta = {
    description = "WSJT-X fork, primarily focused on automation and enhanced functionality";
    homepage = "https://sourceforge.net/projects/wsjt-z/";
    license = lib.licenses.gpl3;
    platforms = platforms.linux;
    maintainers = with lib.maintainers; [ scd31 ];
    mainProgram = "wsjtz";
  };

Best Regards

@liberodark Thank you for the feedback :3 it has been addressed!

feedback has been addressed :3


index: introduce basic fetch

Basic implementation that we can build upon.
Fixes #341

Codecov Report
Patch coverage: 87.05% and project coverage change: +0.76 :tada:

Comparison is base (a57ed24) 57.78% compared to head (aa2ae70) 58.55%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #346      +/-   ##
==========================================
+ Coverage   57.78%   58.55%   +0.76%
==========================================
  Files          51       52       +1
  Lines        3402     3477      +75
  Branches      596      615      +19
==========================================
+ Hits         1966     2036      +70
- Misses       1350     1353       +3
- Partials       86       88       +2

Impacted Files
Coverage Δ

src/dvc_data/index/index.py
65.16% <77.14%> (+2.18%)
:arrow_up:

src/dvc_data/index/fetch.py
86.36% <86.36%> (ø)

src/dvc_data/index/__init__.py
100.00% <100.00%> (ø)

tests/test_index.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Missing function to update dependabot alerts

Reading this file there is no reference to a function to Update a Dependabot Alerts
I would like to implement it but I am opening an issue first to ask if there is any other way to do it that I am currently missing.

It looks like you are correct and there is no method covering PATCH /repos/{owner}/{repo}/dependabot/alerts/{alert_number}, and it would be a welcome addition.
It looks like this would be your first contribution. Please have a look at CONTRIBUTING.md and post back here if you have questions or need any help.


eog: 3.20.3 -> 3.20.4

Motivation for this change
previously version number did not match with source
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thank you for the fix.


App failed to run on Android

Describe the bug
App not running
Additional context
[        ] > Task :app:mergeDebugResources UP-TO-DATE
[        ] > Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
[        ] > Task :app:processDebugManifest UP-TO-DATE
[+1097 ms] > Task :app:processDebugResources FAILED
[        ] 187 actionable tasks: 5 executed, 182 up-to-date
[   +1 ms] FAILURE: Build failed with an exception.
[   +2 ms] * What went wrong:
[        ] Execution failed for task ':app:processDebugResources'.
[        ] > A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
[        ]    > Android resource linking failed
[        ]      /Users/etornam/Projects/FlutterProjects/tasky_app/android/app/src/main/res/drawable/launch_background.xml:8: AAPT: error: 'tasky_logo.png' is
incompatible with attribute src (attr) reference|color.
[        ] * Try:
[        ] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full
insights.
[        ] * Get more help at https://help.gradle.org
[        ] BUILD FAILED in 11s
[ +491 ms] Running Gradle task 'assembleDebug'... (completed in 12.5s)
[   +1 ms] The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the incompatibility.
[   +4 ms] Building plugin apple_sign_in...
[   +3 ms] Running Gradle task 'assembleAarRelease'...
[        ] gradle.properties already sets `android.enableR8`
[   +1 ms] Using gradle from /Users/etornam/.pub-cache/hosted/pub.dartlang.org/apple_sign_in-0.1.0/android/gradlew.
[        ] /Users/etornam/.pub-cache/hosted/pub.dartlang.org/apple_sign_in-0.1.0/android/gradlew mode: 33261 rwxr-xr-x.
[        ] executing: [/Users/etornam/.pub-cache/hosted/pub.dartlang.org/apple_sign_in-0.1.0/android/]
/Users/etornam/.pub-cache/hosted/pub.dartlang.org/apple_sign_in-0.1.0/android/gradlew
-I=/Users/etornam/Development/flutter/packages/flutter_tools/gradle/aar_init_script.gradle -Pflutter-root=/Users/etornam/Development/flutter
-Poutput-dir=/Users/etornam/Projects/FlutterProjects/tasky_app/build/app -Pis-plugin=true -PbuildNumber=1.0 -Pverbose=true
-Ptarget-platform=android-arm,android-arm64,android-x64 assembleAarRelease
[+1246 ms]
                    > Configure project :
                    WARNING: The option setting 'android.enableR8=true' is experimental and unsupported.
                    The current default is 'false'
                    Consider disabling R8 by removing 'android.enableR8=true' from your gradle.properties before publishing your app.

                    FAILURE: Build failed with an exception.

                    * What went wrong:
                    A problem occurred configuring root project 'apple_sign_in'.
                    > SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

                    * Try:
                    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get
                    full insights.

                    * Get more help at https://help.gradle.org

                    BUILD FAILED in 1s
[        ] Running Gradle task 'assembleAarRelease'... (completed in 1.2s)
[        ]
           > Configure project :
           WARNING: The option setting 'android.enableR8=true' is experimental and unsupported.
           The current default is 'false'
           Consider disabling R8 by removing 'android.enableR8=true' from your gradle.properties before publishing your app.

[        ]
           FAILURE: Build failed with an exception.

           * What went wrong:
           A problem occurred configuring root project 'apple_sign_in'.
           > SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

           * Try:
           Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full
insights.

           * Get more help at https://help.gradle.org

           BUILD FAILED in 1s

[ +191 ms] Exception: The plugin apple_sign_in could not be built due to the issue above.
[   +1 ms] "flutter run" took 19,778ms.
[   +5 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:607:7)
           <asynchronous suspension>
           #2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:977:18)
           #3      _rootRunUnary (dart:async/zone.dart:1198:47)
           #4      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #5      _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #7      Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #8      Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
           #10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
           #11     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
           #12     _rootRunUnary (dart:async/zone.dart:1198:47)
           #13     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #14     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #15     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #16     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #17     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #18     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
           #19     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
           #20     AndroidDevice.isLocalEmulator (package:flutter_tools/src/android/android_device.dart)
           #21     _rootRunUnary (dart:async/zone.dart:1198:47)
           #22     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #23     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #24     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #25     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #26     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #27     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:567:7)
           #28     _rootRun (dart:async/zone.dart:1190:13)
           #29     _CustomZone.run (dart:async/zone.dart:1093:19)
           #30     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
           #31     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
           #32     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #33     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #34     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
           #35     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

[ +128 ms] ensureAnalyticsSent: 127ms
[   +1 ms] Running shutdown hooks
[        ] Shutdown hook priority 4
[   +3 ms] Shutdown hooks complete
[        ] exiting with code 1

fixed


Syndicate slug

Check if the default values are used for the slug and syndication values and don't delete them, when they're used.

This is the fix for #62.

Thanks!


java.lang.RuntimeException : android.os.TransactionTooLargeException

Intent will report without any data java.lang.RuntimeException : android.os.TransactionTooLargeException : data parcel size 655692 bytes

The current page data is more than 2 megabytes

The current page data is more than 2 megabytes, and the startacitvity Android page is downloaded from the current page

If we avoid passing the bulk data via params while navigating to the other screen we can reduce this kind of crashes


How to: Add two filters on SearchPanel under one Title

How can I collect terms from two metadata fields shown as one Filter. I have tried various logic models and it hasn't worked for me. I only get one or the other or none at all. I need to know the syntax to pull two fields.
E.G I want to pull data file types from FGDC and ISO metadata.  Below is a sample I tried which did not work.

I would prefer not to have a heading for FGDC File Types and another for ISO File Types, since my clients should not have to look in two places for one thing. Thanks.

Modify the Evaluator for FGDC  to put the content type into "apiso_Type_s"
Modify the Evaluator for FGDC and ISO to put the content type into "format_s"
Format should be a field since it is a core queryable in the spec


Feature request: symbols tree view

VSCode very quickly got to nearly being my default editor.  One thing I'm missing is something like https://atom.io/packages/symbols-tree-view where I can view the structure of a file whilst editing. I've used this view across many editors for years.

Ideally, it would expose API this for extension authors.

This is available though not as a separate view and a flat list. You can press Ctrl+Shift+O to get a symbol outline of the currently open file.Ctrl+T shows all symbols in the workspace. You can type in there to filter the list down.

Thanks Dirk.  Yes, I saw that already, but I find it less of an interruption when that view is constantly onscreen in a separate panel.  Also, the ability to filter this list so as e.g. not to include variables is useful - which is harder to do in a pop-down view.

@dbaeumer Sometimes, this seems to cut off unnecessarily early, see here:

Thinking about it, I probably even like the current approach better, need to get used to it a little, but it is faster to use compared with traditional outline presentation.

@bgse known issue. I opened a issue in the TS repository for this.

Had a request for this for Dart Code. Am I right in assuming we can't implement this (even ourselves) and would need support from Code?

Not sure TBH.  I'm still interested in it, but my (available_time / skill_set_proficiency) isn't likely to find me investigating any time soon. Appreciate any other efforts here.

@DanTup you mean a tree view. Yes. this would need support from the Workbench. Filling the Ctrl+Shift+O flat list is API.

@dbaeumer Yeah, I meant the tree - we're already providing the document symbols for the flat list. Thanks for confirming!

As I mentioned in #10788 , the "symbols tree view" could be made a LOT more powerful than in atom. In my humble opinion, Eclipse got that aspect of the UI absolutely right. Here's a screenshot of the outline view displayed by Eclipse for a Java file:

There are several things worth mentioning here:

The view is a sidebar and permanently visible. It is always in sync with the current file in the editor.
It's a tree view, where each class is a node and every member of that class becomes a child of the class node. Nodes can be collapsed or expanded, as with any other standard tree.
The view displays a lot more information than the plain element names
The shape/silhouette of icons for fields are different than the icons of methods to allow to distinguish them easily
Icons have decorators to indicate that a member is final (a.k.a. readonly), static, abstract, or overrides a declaration in the parent class (to name a few examples)
The color of the icons indicate their visibility (public = green, protected = yellow, private = red)
The type of each field is written directly after the name
The parameter types and return types are written directly after method names. This also allows to easily see the number of parameters at a glance.
A click on a member jumps to the declaration in the code
There are also refactoring features built into this UI in Eclipse:
Dragging a member and dropping it to another position also refactors the code by moving the code block belonging to that member to the position indicated by the drop target.
Deleting a tree node also deletes the corresponding sections of code in the file.
Any node has a context menu that allows for different operations, e.g. rename
The context menu also offers things like "find references" or "open call hierarchy"
A toggle button on the UI allows to switch between alphabetic sorting and "as occurs in file" sorting in the outline display.
The current cursor position is shown in the outline view by highlighting the member (or class) where the cursor currently resides within. E.g. if my cursor is within method "bar()" of class "Foo", then the outline will highlight the tree node "Foo" and the child node "bar()".

I think that this particular feature is brilliantly done in Eclipse, and I would love to see it realized in VScode for Typescript in particular. When I navigate through code in Eclipse and search for something, it's usually just a sequence of "open type -> check outline". You don't even have to look at the source code for navigation, which makes it very fast, elegant and "brain friendly".

If you do add support for a tree; could you also consider allowing it to be used for type hierarchy too? Had that request too, but current ideas (eg. using quick pick) kinda suck: https://github.com/Dart-Code/Dart-Code/issues/133

Having a Object Viewer / Structure Inspector / Class Hierarchy tree
integrated into the  View Bar and Side Bar
(components A,B in graph below)
VSC UI
would be a great improvement for user experience and code navigation.
I asked for it in #397 and then again in #6376 to no avail.
Last time I looked at the APIs there was no way to interact with Side &  View Bar in order to create it
as an external plug-in.
--R

@MartinHaeusler is right. You should focus and working on this feature as in Eclipse. It would definitely one of your killing feature to stand against Atom / Sublime.

VOTE

+1

In case that there was any doubt after my post:
+1.

+1

+1

Is this being looked at? For me, this would be really important.

+1

+1

Hi all, prefer :+1: reactions on the original issue comment as that helps us with prioritization. If you're on a mobile device you can use reactions by first hitting the "Desktop version" button at the bottom of the page.

+1

+1

+1

Stop typing plus one, I'm listening for real updates!

I'm expecting the feature appearing in VSCode.

+1

+1

@MartinHaeusler Outline view of Eclipse is really my favorite feature in all kinds of IDEs.

@ToMakeSense Mine too. I can't understand how people can work without it.

Can you just add a Ctrl+T icon into the side bar please like the file explorer? I think just adding one more icon that opens the workspace symbol tree with a sub option to Ctrl+Shift+O in the tree panel itself is fine.

So, giving my vote here, I requested the same thing, to have the Netbeans Navigator panel in VS Code as well.

+1

this is useful for source code reading. Is there any work on it?

+1

I vote for this feature. A must have.

+1

+1

+1

+1 to this feature request.
Here's a useful hack while we wait for this feature: just do a search to see a nice outline view. In the search panel, put
 function\s([_A-Za-z0-9]+)\s*\(

replacing 'function' with your language's function keyword, and hitting the "Use regular expressions" button on the right.
[Courtesy: Picard at Stack Overflow ]

I hacked it a bit to show top level symbols
You can do it too.
the change is in
src/vs/workbench/parts/quickopen/browser/gotoSymbolHandler.ts
On line 55 modify the code accordingly:

const parentEntries = this.entries.filter((entry: SymbolEntry) => {
	return entry.getType() == 'class' || entry.getType() == 'interface' || entry.getType() == 'namespace'
}).map((entry) => {
	return entry.getLabel()
})

// Check for match and update visibility and group label
this.entries.forEach((entry: SymbolEntry) => {

	// Clear all state first
	entry.setGroupLabel(null);
	entry.setShowBorder(false);
	entry.setHighlights(null);
	entry.setHidden(false);

	// Filter by search
	if (normalizedSearchValue) {
		const highlights = filters.matchesFuzzy(normalizedSearchValue, entry.getLabel());
		if (highlights) {
			entry.setHighlights(highlights);
			entry.setHidden(false);
		} else if (!entry.isHidden()) {
			entry.setHidden(true);
		}
	}
	else {
		const isHidden = (entry.getDescription() !== undefined && entry.getDescription().trim() !== '' && parentEntries.indexOf(entry.getDescription()) == -1) || entry.getLabel().trim() == '<function>' //(for anonymous funcs)
		entry.setHidden(isHidden);
	}
});

basically it checks if symbol description is empty (all items with parent symbol have description - otherwise the top methods and classes don't)
Then package the vscode and you'll have tree view, kinda.
Also I have extension that will help you to further customize the symbols to look a bit more like tree view:
https://marketplace.visualstudio.com/items?itemName=dannylazarov.bettergoto

VSCode release 1.10.0 came with this thing called minimap side view.  I don't have a retina display, so perhaps that's why I did not find it useful AT ALL.  I turned it off as soon as I turned it on :)
Looking forward to this "document outline" I hope it will come with some customizations like

filter down to only methods I care about eg. methods, fields, props, etc....
allow to switch between different sorting, like current layout versus sorting alphabetical versus by type and by access.

Both 1 and 2 features should be toggles via some toolbar buttons on this tree view pane, not some configuration thingy buried in settings.json :)

Moving blocks of code reliably might become more appealing via drag-drop in this tree view pane.
I can live without this, as most of my files are only 2 to 3 pages long.

I have subscribed to this issue and hope to see it closed :) soon
Thank you.

I think tagbar is better than command+shift+o

+1

+1

+1

Now that the minimap has been introduced, I really hope to see this "tagbar" concept in the near future ! <3

+1

+1 to this feature request.

no more +1s please. PLEASE.

To reiterate what was mentioned a while back:

Hi all, prefer :+1: reactions on the original issue comment as that helps us with prioritization. If you're on a mobile device you can use reactions by first hitting the "Desktop version" button at the bottom of the page.

In other words, please don't comment "+1" at the bottom of this page. Instead add a :+1: to the first comment on this issue.

why did you close this? all the related issues are marked duplicate and closed now but no solution :o
also, +1

It wasn't intended to close it. Sorry, I would like to emphasize this. +1
Best regards,
Martin
Mike Smullin<EMAIL_ADDRESS>schrieb am 21.03.2017:

why did you close this? all the related issues are marked duplicate and
closed now but no solution :o
also, +1

-- sent by mobile

:+1: In the (Default ctrl+shift+o) or my ctrl+r, typeing a colin in the list: @: separates them by Class, function, property, module, variables -- however I also am dying for a tree (like Netbeans has). ST3 doesn't have this either.

Guys please vote for Table of content, easy jump to code section #23698  👍
This would add a ToC in this symbols tree view panel we ask here. The ToC items would be sections you create through special comment headings in your file. What an easy way to organize your code and quick jump through those sections. 😉

A must for CSS files.

+1 for this feature request

Probably one of the very few who moved from BBEdit to VS Code, this is one of the features I miss. For reference, BBEdit shows the method you are in that also functions as a drop down (similar to Ctrl/Cmd+Shift+O). I like this non-intrusive feedback that can be persistent.

without it, it's a deal breaker, mr. visual studio code.
ninja-ide gets it nice with python. i was hoping for a side bar like this..

Is this feature really that hard to implement in VSCode or has it just very low priority?
Just curious - I noticed that "code outline as separate panel" feature request pops itself through months without any visible progress. I mean, I'm sure that authors of VS Code work very hard on this editor, so there must be reason why often requested feature is not there yet.
BTW maybe this feature could be implemented by community as an extension? If so, what would be best approach to make such an extension in a way that would integrate well with VSCode?

Also the smaller font choice is key for the structure pane concept - it allows you to see the file at a glance.

I too have been waiting for this feature for some months now. Really weird that it's still not available (even as an extension).
I really like VScode, but without a structure explorer, it's not going to be my daily editor and I'll stick to Brackets.
If MS really wants this to be the best editor going to be used by everyone then implement this feature !

I really like VScode, but without a structure explorer, it's not going to be my daily editor and I'll stick to pycharm.

Well... I've made the package for Atom which implements similar fuctionality, it's called Lupa:
https://atom.io/packages/atom-lupa
(it's outline, breadcrumbs and semantic search).
Theoretically it would be possible to port Lupa to VSCode, but I can't do this right now.
Lupa is made from two parts: GUI  (made in ReactJS) which could be considered as "good enough", and static analysis part (it parses code and analyze ASTs) and that part needs major overhauling.
So I’m rewriting now static analysis part of Lupa from scratch (which involves building library similar to Tern - so I don’t have time to port anything right now, maybe later.
Although VSCode seems to make a lot of static analysis right now so I suppose it could be possible to connect GUI of my extension to some sort of language service in VSCode? (would it be possible?)
But I'm still not sure if VSCode allows extensions to inject custom HTML into panels (does it?).

The biggest problem that I have with the symbol outline that you get with Ctrl+Shift+O is that it overlays the text of the buffer, meaning that it is more difficult to move around between the symbols and see the underlying text at the same time.
I do also really like the symbol tree that exists in Atom, and would love to see it in VSCode too.

I think that there is no need for discussion about CTRL+SHIFT+O here. While it does offer similar information and is a valid and important functionality in and on itself, the use case is a very different one than for a structure tree view. The structure tree view needs to be a panel (i.e. always visible and not overlaying editor content) and a tree (because it displays the Abstract Syntax Tree after all).
It would be nice to get an update on this from the VSCode devs. Several other typescript editors already have this feature.

Yup -- this feature is a must for serious code editing.

+1

Voted for this feature, it is tedious to open up the overlay with the shortcut every time, and it's not quite what you would expect. To my taste, a codemap should always be visible, it helps keeping a clear idea of what's going on and encourages a clean and well-written code with explicit function names, logical order, a separation of concerns... It should support regions as well as expose the input and output types, etc.
I think the best codemap I've ever used is that of the Supercharger plugin for Visual Studio, it's just plain fantastic and has all of those features. I'd love to see one of those in vscode 👍

Hey guys, I really missed treeview so I gave it a shot with this hackish solution, any input is welcome, I believe it's possible to make it somewhat stable with fixed width panels and some more checks if HTML preview panel is visible to ensure it's present, I put this together last night: https://marketplace.visualstudio.com/items?itemName=igbenic.symbolstreeview
https://github.com/igbenic/SymbolsTreeview

@igbenic I've just started working today and your extension is already helping. Thanks a lot, great work!

@vegbrasil Thanks man, glad you like it!

@igbenic nice work!
One thing to propose is positioning of found symbol in editor. Now it's vertically positioned in bottom of the editor, I guess more convenient would be to scroll it to middle of screen.
Thanks!

@igbenic I tried it, unfortunately I wasn't able to get past the loading indicator - the panel content always remained blank for me. I am using *.tsx files (XML extensions, for React) instead of *.ts files, is that somehow related?

Hi there thank you for your input! @jorups I'll add this to feature requests :), @MartinHaeusler well basically if cmd+shift+o shows you a list of symbols they should be in my extension also. Other than that I am working on some hot fixes for when to trigger symbols refresh for next version so there might be a solution

How is this not a higher priority?!  This feature seems to be extremely popular and most of the pieces already exist so it shouldn't be too resource-intensive to implement.  Come on vscode team - come through for us!

As much as I love VSCode, the lack of this feature has pushed me back to using Webstorm. Sorry guys, it's too essential.

I've put this together last night using the new APIs introduced in 1.13: Code Outline. It's pretty basic so contributions are welcome.

Good job, although I have some remarks. I don't see Github site of your extension so I'll write this here.

Enabling outline is not intuitive. As a user I would like to click View -> Show Outline or 1. press Cmd + Shift + P 2. write 'outline' 3. press enter. I just didn't see at the beginning "how I can enable this". It's very small part of left panel's accordion:

after clicking on entity in outline there is no visual indicator "where given entity is" It may e.g. move cursor to it or highlight this editor. Also it would be nice to focus editor after clicking. Without this, it's not very useful (I clicked and I couldn't write code right away).

I tired to figure how to enable / find it for some time, so I googled up the source repo. Overall, great job, though. Looks super-useful.

@hex13 as of 0.0.2 clicking items should now activate the editor. Let's move feedback to the extension page or its GitHub repo though so we don't spam all of these nice people subscribed to this thread.

@patrys Opened issue on Visual indicator on code, it's similar to what @hex13  says

@patrys I love it !!!

we need symbols tree like monodeveloper!

As of 1.14, this is possible using this extension: https://marketplace.visualstudio.com/items?itemName=patrys.vscode-code-outline

@jens1o thanks my friend！i like it！

An option would be to use Notepad++'s functionList.xml so that we can customize the pattern matching. Because vscode doesn't even show @ symbols for some popular languages, such as perl. so I doubt that a separate view will be useful for everyone.

@nurp Open a separate issue if your language is not supported by VSCode. A feature like this one is not language-specific. It's up to the language plugin to provide symbols necessary to construct the outline.

There is a small upgrade to Go to Symbol feature which added a great potential on how we can inspect the code outline:

Go to Symbol
You can navigate symbols inside a file with ⇧⌘O. By typing : the symbols will be grouped by category. Just press Up or Down and navigate to the place you want.

@rankun203  awesome!
but how can I config a keypress shortcut?
and can it config with "Group by Class"?

@jens1o thank you, this extension works great for python code

@jens1o Perfect.  Code officially just became a major threat to Intellij for me.  This is huge.

@ilazarte you may want to file this issue here: https://github.com/patrys/vscode-code-outline

this is the #3 most thumbs-up'ed feature request in the github issues list!
and there are duplicate issues open like https://github.com/Microsoft/vscode/issues/14473
keep mashing that thumbs button :)

Everyone has already covered it, but I also use Notepad++ and I also miss having a function list in VSC.
Other than that, I am loving the switch over.

+1

Ctrl+Shift+O is UGLY, which will disperse my attention. Since it has supported the code outline, I don't understand why not display in a tree view.

Minimap was actually prioritised over this?

+1 for a symbol table, the minimap is useless on smaller screens.

A native outline view is definitely needed. Although the Code Outline plugin provides the functionality in a quite nice way, there are still some issues:

The Code Outline plugin responses very slowly when switching between source files, i.e. the Code Outline view takes a  lot of time to update.

The Code Outline view cannot be moved freely to other places in VSC. For example, I cannot replace the minimap with the Code Outline view provided by the plugin. Nor can I "create" a second side bar holding the Code Outline view, along with the existing side bar.

Please consider adding the outline view & functionality to VCS .  Thank you.

@xueyunquan FWIW I've made version 0.0.12 much faster.

Current outline is flat which is useless with a large files. Also it shows local variables which is extra IMO. If VSCode provided tree-like structure instead of list of everything things would be much better

@Yanpas Code Outline is a tree. If it's flat it probably means your language does not report proper symbol ranges.

@patrys I guess the problem is api limitations:
SymbolInformation contains location and containerName members.

location's range doesn't have to denote a node range in the sense of a abstract syntax tree

containerName can't be used to re-infer a hierarchy for the document symbols

There sohuld be some parent member or something.
In fact there are no tree outline for: C#, C++, Haskell and Rust

I've created an issue here for tree-like symbols https://github.com/Microsoft/language-server-protocol/issues/327

@patrys Thanks for your reply. I am using 0.0.12, actually. When I switching to another file, especially those not opened recently, it always takes 2~5 seconds to update the outline view.
And as @Yanpas has stated, it does not show a tree structure for C++, as well as C that I use most often. But of course this issue comes from the parser, here both provided by the cpptools plugin developed by MS.

+1

I appreciate hardwork of @patrys (https://marketplace.visualstudio.com/items?itemName=patrys.vscode-code-outline) and I'm grateful. However I think this should be a native feature of editor.
I use Nuclide (Atom) for flow and VSCode for Typescript. I find Nuclide's Outline and Context view very useful and polished. I wish everyday VSCode has those as a native feature.

When is code outline coming out of the box natively? Vs code is the most loved editor now and not having this feature is a bummer.

It would be awesome if symbols were marked on the minimap, for example with a colored bar or fitting icons. Then hover to see details and click to go to symbol.. Alternatively the files in the treeview could be expanded further to reveal symbols. Just brainstorming :)

This is core function for every real editor, VSC should have it. Some basic built-in panel would be indicated, but making a good API for this could result in the creation of great plugins.
This really looks great:
https://github.com/Microsoft/vscode/issues/5605#issuecomment-351291978
Notepad++ has built-in function list:
https://notepad-plus-plus.org/features/function-list.html
but I prefer SourceCookifier:
http://sourcecookifier.sourceforge.net/
Basic future should be:

separate panel for list (not use existing Explorer panel - there are too many things there)
search box
working with single file/all open file/all project file
customizable appearance and parsing rules
supports custom languages

@ArkadiuszMichalski Thank for great ideas. However, I have some additional thoughts.
In fact, Ctrl+Shift+O, Ctrl+T and Navigation Pane currently work like a function list in single file/whole project (including search box , too) that can satisfy your first three suggested features in some way.
There are already some extension out there (Code outline or Show functions).
I think the symbol tree view can also:

Highlight the currently selected symbol(s) and all symbols that match/contain the search keyword (by Ctrl+F).
Display the simplified code structure (especially big switch-case and condition expression).

Any ETA when we could expect this feature or API?

@NaGeL182 Feel free to do a pr, of course, then it would go to 1.21 ;)

I would love to see this feature added.

This was proposed about two years ago and apparently had great reception. I was wondering if it's not been classified as a priority (and why) or if I'm just dumb and I can't find it in the docs.

This  was proposed about two years ago and apparently had great reception. I  was wondering if it's not been classified as a priority (and why) or if  I'm just dumb and I can't find it in the docs.

Think of how long multi-root support has needed to wait ;)

Think of how long multi-root support has needed to wait ;)

Excuse my ignorance, I'm a bit out of touch with the internals of Code. You mean this hasn't been developed for not having multi-root (different projects/folders at once?) support?

You mean this hasn't been developed for not having multi-root (different projects/folders at once?) support?

no no no... I mean like the feature request for multi-root-support is older than this one and it has been a longer time until that request was implemented.

Geany editor has also a very nice implementation of functions overview. I am attaching a screenshot for reference

@byron21 I'm not sure that's better than other examples in this thread. It looks primitive and doesn't seem to make use of slightly different icons to help give more information.
What are the numbers within the square brackets?

The numbers within the square brackets indicate the function declaration line number. I agree with you it looks primitive.

I think we should squeeze as much relevant info as possible, preferably in an optional fashion and functionality.
For example:

show number of lines in that function or piece of code (good way to know where to trim fat or refactor)
different sorting ways: alphabetic, position in the code, number of lines, by type (function, class etc.), number of TODO's...
select one or more items and be able to reorder them and maybe even drag and drop through to other documents (simpler code cut and paste)
a small green dot or similar to indicate not staged/committed code.

I'll stop saying things or I'll just start repeating what others have said,

@dbaeumer will you want this to be a request from the client or a notification from the server or both? Tree-view and Error-panel are the only pieces of always-visible UI in LSP.
We run into problems with Atom+Hack because Atom requests the outline view immediately, but the Hack LSP server declines the request during its first 30-60 seconds of initialization, and there's no good way for Atom to know when it should re-issue the request.

Hack LSP server declines the request during its first 30-60 seconds of initialization, and there's no good way for Atom to know when it should re-issue the request.

If the Hack LS cannot response on this type of request after initialization, it shouldn't claim so (i.e. register this capability) and use dynamic capabilities registration. Although I'm not sure it is supported by Atom yet, but it's a matter of time.

@laughedelic Does that amount to saying that the standard error code ServerNotInitialized shouldn't be used?

@ljw1004 I'm not sure I understand it. From the LSP spec:

Until the server has responded to the initialize request with an InitializeResult, the client must not send any additional requests or notifications to the server.

What I see in Atom is a spinning progress indicator in the outline panel while server is initializing. Once it's ready the client sends outline request, gets a response and shows it in the panel.

This is a must have...

I think this would be better an option for users or just a plugin, the editor would be bloated if you added this kind of feature. There is visual studio if you need full pledge IDE though... Probably I need to transfer back now to Emacs or Vim as it is more lightweight.

@laughedelic Thanks for the clarification. I hadn't been thinking right about this.

Actually I prefer something like "go to anything" where you type something (can be a symbol, a file or any command) and it aggregates all results in a single place.

One :+1: missing!
(sorry 4 spam bros)

FYI, the latest release (0.2.0) of https://marketplace.visualstudio.com/items?itemName=patrys.vscode-code-outline does a great job with this now

The extension works great, but the fact that it can't be moved to the rigth column is an immediate no go for me (and probably most people).

One option though is to move the entire Workbench to the right like so:
"workbench.sideBar.location": "right"
Which is probably a good idea regardless if your first language reads L->R as then the brain naturally reads that way and thus your most important stuff (your code!) is first thing on the left side of the screen. It takes getting used to just because it's a change though.

Tried 'patrys.vscode-code-outline'. Didn't work for me at all. Always shows empty box (tried refresh, re-install etc). That, and also, I wanted to see it on the right. It is very disturbing to see where it shows up now.

Hopefully being implemented this month. It's a planned item! #49327

patrys.vscode-code-outline worked great for me, but for about a week now it has disappeared and no matter what I do, I can't seem to get it back...

@Brent-Knigge It now has a separate panel. On the left you should see a new icon below which is for the code-outline view.

@jrieken will this outline view be a generic view that other language plugins could build upon?

The data it shows comes from extensions - it currently uses the DocumentSymbolProviders for that and there is an issue to better support document symbol hierarchies: #34968. So, that data defines what we show and while we don't expose our UX/view models to extensions there are ideas allowing to add commands, e.g allow for contributable context menu commands, see #49925

@jrieken This looks great! But for those of us that need custom outlines, are all the APIs used by this exposed to us for use in our own tree?

are all the APIs used by this exposed to us for use in our own tree?

No, this is a client feature (like all of our UX features) and doesn't use the extension API.

In the name of GH issue manageability (this issue takes aged to load) I am closing and locking this. Let's continue the discussions in topic-issues labeled with outline.
Thanks and Happy Coding!


Remove Real from equipment error

On the /equipment/list page when you edit 'Reals of equipment' and try to remove one the following error occurs:
'Vip' object has no attribute 'get_by_id'.
The problem is in this call from Equipment Views file.
To solve it, one can add the method 'get_by_id' to Equipment implementation at Python Client project .

Is this project still being used?

Is this project still being used?

hi,
yes, it's.


Update plan-for-software-updates.md

When I initially submitted the documentation note for supersedence rules it was altered to say, in effect, the opposite.  I have confirmed based on the documentation for the WSUS cleanup wizard, my own environment, the stored procedure the WSUS cleanup wizard uses, and a premier field engineer to confirm that nothing SCCM does will ever remove a superseded update from the WSUS catalog.  The WSUS cleanup wizard will only decline superseded updates where the new superseding update has been approved in WSUS.  When ran as part of a SUP that never happens since SCCM never approves updates in WSUS.  The only solution is to either manually decline superseded updates from within the WSUS console or use scripts written against the WSUS API.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@dougeby PR for your review

@bryandam After talking with the Configuration Manager and WSUS engineering teams, I will change the text slightly. However, it was confirmed that the behavior should be that when Configuration Manager sets an update to Expired, clients will continue to scan for the update. Then, when the WSUS cleanup task runs, it will set any Expired updates in Configuration Manager to Declined on the WSUS server regardless of whether they are approved or not on the WSUS server. After the update is set to Declined, clients will no longer scan for it.


Required image on the SideNavigationBarHeader

I'm using your package and it's super good, thanks for that. I wanted to add a header to my side navigation bar, I used the SideNavigationBarHeader, but the image is required, and according to the design that I'm creating there is no image to display, so that would be great if you turn the image into an optional nullable parameter. Thanks!

Hello @Mikelenjilo
Sorry I missed the creation of this issue.
This is easily possible. maybe you can give it a try in a pull request :)
I will get to this as soon as a find some time on weekends again.


pyCMR Overhaul

Hi Folks,
This PR essentially overhauls pyCMR setup.py and codebase to build and run on Python 3.X. Additionally, it relocates the test directory to a new location hence cleaning up the directory structure.
Tests are currently failing due to #16
$ nosetests
...
======================================================================
ERROR: test suite for <class 'pyCMR.tests.test_cmr_integration.TestCMRIntegration'>
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/suite.py", line 210, in run
    self.setUp()
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/suite.py", line 293, in setUp
    self.setupContext(ancestor)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/suite.py", line 316, in setupContext
    try_run(context, names)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/util.py", line 471, in try_run
    return func()
  File "/usr/local/cmr/pyCMR/tests/test_cmr_integration.py", line 18, in setUpClass
    cls.cmr = CMR('cmr.cfg')
  File "/usr/local/cmr/pyCMR/pyCMR.py", line 65, in __init__
    raise IOError("The config file can't be opened for reading/writing")
OSError: The config file can't be opened for reading/writing

----------------------------------------------------------------------
Ran 0 tests in 0.043s

FAILED (errors=1)

Please let me know how we can address #16 then I will get the tests working @manilmaskey thank you.

@manilmaskey CC you here for context... I would appreciate any review.

@lewismc, I like this in general, and great job tuning it up! As long as you're going in that direction and cleaning up the codebase, could you add basic flake8 linting to the tests?
Also, I believe that there are NASA folk who're using this in production, so the moving of the libraries (to more standard locations) may break their workflow; worth talking to @amarouane or @manilmaskey to assure that those people get a heads-up.

Also, @lewismc, there's another NASA-sponsored Python CMR client library in town, which might be worth checking out if you can't wait for this to get reviewed or merged in: https://github.com/jddeal/python-cmr

Hi @mileswwatkins thanks for the heads up. IMHO we should merge these efforts and transition the unified toolkit over to the NASA Github Org. The Python toolkit you point to currently provides a pretty intuitive set of classes for query functionality only, where as this toolkit offers slightly more. A merge should not be difficult by any means.

Now that @amarouane added an cmr.cfg.example file, if you copy this file to cmr.cfg and run tests you get the following which is much better. I think we should create a dummy user account and have a test-only cmr.cfg.example file available to pass to the CMR Class in TestCMRIntegration
lmcgibbn@LMC-056430 /usr/local/cmr(master) $ nosetests
nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
nose.selector: INFO: /usr/local/cmr/README.md is executable; skipped
nose.selector: INFO: /usr/local/cmr/cmr.cfg is executable; skipped
nose.selector: INFO: /usr/local/cmr/cmr.cfg.example is executable; skipped
nose.selector: INFO: /usr/local/cmr/pyCMR/read_eol_sf.py is executable; skipped
nose.selector: INFO: /usr/local/cmr/pyCMR/read_variable_nc.py is executable; skipped
Since these are order-sensitive integration tests, ... ERROR
Make sure that the correct number of items are returned by searches ... ok

======================================================================
ERROR: Since these are order-sensitive integration tests,
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/case.py", line 134, in run
    self.runTest(result)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/case.py", line 152, in runTest
    test(result)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/unittest/case.py", line 648, in __call__
    return self.run(*args, **kwds)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/unittest/case.py", line 608, in run
    self._feedErrorsToResult(result, outcome.errors)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/unittest/case.py", line 538, in _feedErrorsToResult
    result.addError(test, exc_info)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/proxy.py", line 132, in addError
    self.result.addError(self.test, self._prepareErr(err))
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/result.py", line 61, in addError
    exc_info = self._exc_info_to_string(err, test)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/site-packages/nose/result.py", line 187, in _exc_info_to_string
    return _TextTestResult._exc_info_to_string(self, err, test)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/unittest/result.py", line 186, in _exc_info_to_string
    exctype, value, tb, limit=length, capture_locals=self.tb_locals)
  File "/Users/lmcgibbn/miniconda3/lib/python3.5/traceback.py", line 481, in __init__
    self.filename = exc_value.filename
AttributeError: 'ParseError' object has no attribute 'filename'
-------------------- >> begin captured logging << --------------------
root: INFO: ======== Waiting for response ========
requests.packages.urllib3.connectionpool: INFO: Starting new HTTPS connection (1): cmr.uat.earthdata.nasa.gov
requests.packages.urllib3.connectionpool: DEBUG: "GET /search/collections?page_size=50&page_num=1 HTTP/1.1" 200 30421
requests.packages.urllib3.connectionpool: INFO: Starting new HTTPS connection (1): cmr.uat.earthdata.nasa.gov
requests.packages.urllib3.connectionpool: DEBUG: "GET /search/collections?page_size=50&page_num=2 HTTP/1.1" 200 8811
root: INFO: ======== Waiting for response ========
requests.packages.urllib3.connectionpool: INFO: Starting new HTTPS connection (1): cmr.uat.earthdata.nasa.gov
requests.packages.urllib3.connectionpool: DEBUG: "GET /search/granules?page_size=50&page_num=1 HTTP/1.1" 200 15643
requests.packages.urllib3.connectionpool: INFO: Starting new HTTPS connection (1): cmr.uat.earthdata.nasa.gov
requests.packages.urllib3.connectionpool: DEBUG: "GET /search/granules?page_size=50&page_num=2 HTTP/1.1" 200 15576
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 2 tests in 21.845s

FAILED (errors=1)

IMHO we should merge these efforts and transition the unified toolkit over to the NASA Github Org

I'd agree that that's the ideal plan, and that combining the code wouldn't be too bad,  but I think the catch is that both libraries already have uses in production, and so altering the API of either, much less merging them and moving to a new address, has a nontrivial political cost. If you can swing it, power to ya ;D

@mileswwatkins yes it's always the same at NASA ;)
My general feeling is that both toolkits are half baked and they would benefit, and so would the communities which use them, if we could merge the efforts under a unified project. There's no reason we couldn't drum up support for this on one of the DAAC managers telecon's.
Once we have things sorted out over here with #17 I'll ping whoever the maintainer is of the other library with the concept. Thanks again for the insight... it's a shame that these packages haven't been more widely advertised at ESDIS events such as the recent ESDSWG meeting in Annapolis.

Sure thing, and totally agree that it could be a big win to publicize a unified Python tool; CMR's such a powerful tool, but can have a learning curve to understand and use natively.
FWIW, I've also created a NodeJS CMR client library (also used in production) with the same CMR capabilities as this Python library. It's not currently public because we haven't cleared export control, but it will be public (and FOSS) later this year. I'm sure that releasing this alongside a Python tool could compound the success.
cc @ianschuler, @matthewhanson

ack

hi folks, is anyone able to review this pull request?

Thanks @amarouane I'm going to start work on the community building over at the other CMR Python toolkit.
I wonder if you have any suggestions for stabilizing the build on this project?


0.47.1: Rails/ReversibleMigration misdetection

class AddNewColumn < ActiveRecord::Migration[5.0]
  def change
    change_table(:users) do |t|
      t.string :new_column
    end
  end
end

Expected behavior
It should pass without problems. change_table is reversible.
Actual behavior
C: Rails/ReversibleMigration: change_table is not reversible.

RuboCop version
0.47.1 (using Parser <IP_ADDRESS>, running on ruby 2.4.0 x86_64-darwin16)

Docs say:
change_table is also reversible, as long as the block does not call
change, change_default or remove.

And looks like it works only in Rails 4.
Not sure if checking all these scenarios is in scope of Rubocop.

Couldn't TargetRailsVersion be used for checking it?
The rails issue post is quite old (Oct/2013), so this probably works for Rails 5 too, otherwise it wouldn't be present in the edge guides.


lxd: Improves API request/response debug logging

This has helped me debug/understand the different response types and the relationship between api.Response.Code and HTTP response code (i.e they are the same for error responses).

Hrm debug is now on by default it seems, investigating...

Fixed it now.


Update C# examples to 0.15.0 packages.

Can be merged once we tag the release and upload the nugets.

LGTM


[WIP][CARBONDATA-2525] Search mode can not register master in security cluster

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4926/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5084/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6095/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4934/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5088/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6098/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4936/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5092/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6103/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/4941/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5097/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7112/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5888/

transfer to jacky


Update to scalajs-react 1.0.1 (and other dependencies)

Updates to dependencies:
scalajs-react 1.0.1, Scala.js 0.6.17, sbt-web-scalajs 1.0.5, Play 2.5.15, scalajs-dom 0.9.2, ScalaCSS 0.5.3, Autowire 0.2.6, BooPickle 1.2.6, Diode 1.1.2, uTest 0.4.7, React 15.5.4, SBT 0.13.15
In the Chart.js component I used asInstanceOf in order to access the cavas context because the domType method was removed. There may be a safer way to do that that I couldn't find (I just learned scalajs-react from this tutorial).
The code samples in the documentation were updated although I may have missed a few changes.

Whoa, this is huge! Thank you so much 🙇 !


Add note that as of 7.19.0 more additional parameters are supported

Note: verify footnote formatting on build to dev, document.

So exiting, can't wait for Mx 7.19. Can you confirm if this also applies to custom widgets?


[cppgraphqlgen] Update to v3.2.1

Describe the pull request

What does your PR fix? Fixes issue #

Fixes template compilation on VS 2017 (microsoft/cppgraphqlgen#97).

Which triplets are supported/not supported? Have you updated the CI baseline?

It should be supported on all triplets. I have not updated the CI baseline.

Does your PR follow the maintainer guide?

Yes.

Thanks for the PR!


Interfaces should be able to inherit types

Usecase
import type EventEmitter from "events";

export interface MyAPI extends EventEmitter {
    someOtherMethod(): void;
}

Or some special extends $Type<EventEmitter> kind of thing
Given a signature like this, I define my libraries exported API. I want to mandate that anything that implements MyAPI should also implement the specs of a NodeJS EventEmitter.
I should then be able to write code like:
const api: MyAPI = config.useCustomEventEmitter
    ? getAPIWithCustomEventEmitter()
    : getAPIWithDefaultEventEmitter();
api.addListener("test", (data) => { console.log("got test", data); });
api.emit("test", "foo");
api.someOtherMethod();

I am currently doing this in 0.55 by copying the libdefs from the built in node.js types and pasting them into my own custom interface, and modifying the return type to : * since : this is not allowed outside of declare class
However on updating flow to 0.57.3, I started getting
Property addListener is incompatible: 'function type'. See https://github.com/facebook/flow/blob/v0.57.3/lib/node.js#L653. This type is incompatible with 'function type'
So that workaround no longer works, forcing me to stay on 0.55.
I'm asking for some way to let interfaces inherit the type restrictions of another type in the same way
type Foo = Bar & Baz works, be it through $Foo<> style usage, or simply letting implements Type work

@aikar I may not be understanding your request completely but as far as I am aware this is already the case.
interface Bar {
  two: () => void;
}

interface Foo extends Bar {
  one: () => void;
}

/*
  $ExpectError
    Baz
      This type is incompatible with
        Bar
        --
        Property `two` is incompatible:
          property `two` of Bar
          --
          Property not found in
          Baz
*/
class Baz implements Foo {
  one = () => undefined;
}

@bradennapier Yes thats fine and dandy when the type you want to inherit is actually an interface.
I am talking about for when it is not - Core NodeJS types and third party type definitions where you don't have that control.
My issue describes why I'm unable to manually create my own interface too.


fix: hide right arrow in webviews where not needed

The type of this PR is: fix
This PR resolves CX-1978
Description
This was a bug in a previous PR that unintentionally passed an empty function to onRightButtonPress instead of undefined. This checks for presence of either of right button actions and if neither are present returns undefined.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

Hide right arrow where not needed in webviews - Brian

iOS user-facing changes

Android user-facing changes

Dev changes

This PR contains the following changes:

Cross-platform user-facing changes (Hide right arrow where not needed in webviews - Brian)

  Generated by :no_entry_sign: dangerJS against c101cd26f7a0e528fbb4d1b160a2083e1ad66bb9

Thanks 🎉


Downlaod multiple accounts

Describe the bug
Not really a bug. However I switched from using instaloader as a git-download to the installation now and I'm not able to download a list of accounts. My current code looks like this:
declare -a arr=("person1" "person2" "person3")

for i in "${arr[@]}"
do
cd /path/to/download/location
sudo instaloader --sessionfile=/home/pi/...../instaloader/instaloader-session --quiet --filename-pattern={date_utc}_{profile} --dirname-pattern=user_{profile} --login=MYACCOUNT --password=MYPASSWORD [ $i ] >> /path/to/logs/instaloader.txt 2>&1

However, the problem is, that instaloader downloads every profile I am following - instead of just those listed in the list.
Expected behavior
Download just those profiles in the list.
Instaloader version
4.2.7
Thanks in advance!

See aandersgr's comment. You don't need to loop through your list, just pass all profiles at once, and don't wrap them in [ ]. Also, why sudo? As long as the target directory is writable by your regular user there's no need to run instaloader as root.

Thanks for your help!
I have now changed the code to:
cd /path/to/download/location
sudo instaloader --sessionfile=/home/pi/...../instaloader/instaloader-session --quiet --filename-pattern={date_utc}_{profile} --dirname-pattern=user_{profile} --login=MYACCOUNT --password=MYPASSWORD person1 person2 person3 >> /path/to/logs/instaloader.txt 2>&1

However, now instaloader downloads all profiles my account is following and after some time I also get:
Traceback (most recent call last):
  File "/usr/local/bin/instaloader", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.5/dist-packages/instaloader/__main__.py", line 410, in main
    storyitem_filter_str=args.storyitem_filter)
  File "/usr/local/lib/python3.5/dist-packages/instaloader/__main__.py", line 186, in _main
    download_stories, fast_update, post_filter, storyitem_filter)
  File "/usr/local/lib/python3.5/dist-packages/instaloader/instaloader.py", line 1000, in download_profiles
    for post in profile.get_posts():
  File "/usr/local/lib/python3.5/dist-packages/instaloader/structures.py", line 694, in get_posts
    self._metadata('edge_owner_to_timeline_media')))
  File "/usr/local/lib/python3.5/dist-packages/instaloader/structures.py", line 688, in <genexpr>
    yield from (Post(self._context, node, self) for node in
  File "/usr/local/lib/python3.5/dist-packages/instaloader/instaloadercontext.py", line 469, in graphql_node_list
    data = _query()
  File "/usr/local/lib/python3.5/dist-packages/instaloader/instaloadercontext.py", line 451, in _query
    return edge_extractor(self.graphql_query(query_hash, query_variables, query_referer, rhx_gis))
  File "/usr/local/lib/python3.5/dist-packages/instaloader/instaloadercontext.py", line 436, in graphql_query
    session=tmpsession)
  File "/usr/local/lib/python3.5/dist-packages/instaloader/instaloadercontext.py", line 381, in get_json
    resp_json = resp.json()
  File "/usr/local/lib/python3.5/dist-packages/requests/models.py", line 897, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/lib/python3/dist-packages/simplejson/__init__.py", line 516, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 374, in decode
    obj, end = self.raw_decode(s)
  File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 404, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())
simplejson.scanner.JSONDecodeError: Unterminated string starting at: line 1 column 76865 (char 76864)


fix(types): corrected argument types for Context methods

Each method is typed by Interface and doesn't affect the type of function arguments as seen by the caller, but wouldn't it be healthier to modify it?
Author should do the followings, if applicable

[x] Add tests
[x] Run tests
[x] yarn denoify to generate files for Deno

Hi @asaxeye !
Thank you!! This is typos/bugs. Looks good, merge now.


Workflow should not trigger on draft PRs

In #636 we added a build workflow on commits to main and to PRs.  But this triggers also on draft PRs.  Draft PRs are normally not stable and it is not useful to run the workflow on those.  So the workflow should be updated to exclude them, if possible.

Another thing I don't like with my current setup is that make traverses the subdirectories and then it runs go build everywhere, and this should really only do something if the dependencies have changed, but it actually runs the linker or at least touches the executable, so this updates the mtime of every program.  To do better, the makefiles need to have the actual dependencies of the inputs (usually .go /.go and ../go-utils//*.go though in some cases there are no subdirs - not sure what make will make of that).

And I guess if a PR moves from draft to ready status the build workflow should be triggered automatically.


[Snyk] Upgrade web3 from 4.1.2 to 4.2.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade web3 from 4.1.2 to 4.2.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 27 versions ahead of your current version.
The recommended version was released 24 days ago, on 2023-10-18.

Release notes

Package name: web3

4.2.0 - 2023-10-18Added
web3

Various web3 sub packages has new functions details are in root changelog

web3-eth

Added ALL_EVENTS and ALL_EVENTS_ABI constants, SendTransactionEventsBase type, decodeEventABI method (#6410)

web3-eth-accounts

Added public function privateKeyToPublicKey
Added exporting BaseTransaction from the package (#6493)
Added exporting txUtils from the package (#6493)

web3-types

Interface EventLog was added. (#6410)

web3-utils

As a replacment of the node EventEmitter, a custom EventEmitter has been implemented and exported. (#6398)

Fixed
web3-core

Fix the issue: "Uncaught TypeError: Class extends value undefined is not a constructor or null #6371". (#6398)

web3-errors

Added new SchemaFormatError (#6434)

web3-eth

Ensure provider.supportsSubscriptions exists before watching by subscription (#6440)
Fixed param sent to checkRevertBeforeSending in sendSignedTransaction
Fixed defaultTransactionBuilder for value issue (#6509)

web3-eth-abi

Fix issue with default config with babel (and React): "TypeError: Cannot convert a BigInt value to a number #6187" (#6506)

web3-eth-accounts

Fixed recover function, v will be normalized to value 0,1 (#6344)

web3-providers-http

Fix issue lquixada/cross-fetch#78, enabling to run web3.js in service worker (#6463)

web3-providers-ipc

Fixed bug in chunks processing logic (#6496)

web3-providers-ws

Fixed bug in chunks processing logic (#6496)

web3-utils

Fix issue with default config with babel (and React): "TypeError: Cannot convert a BigInt value to a number #6187" (#6506)
Fixed bug in chunks processing logic (#6496)

web3-validator

Multi-dimensional arrays are now handled properly when parsing ABIs (#6435)
Fix issue with default config with babel (and React): "TypeError: Cannot convert a BigInt value to a number #6187" (#6506)
Validator will now properly handle all valid numeric type sizes: intN / uintN where 8 <= N <= 256 and N % 8 == 0 (#6434)
Will now throw SchemaFormatError when unsupported format is passed to convertToZod method (#6434)

Changed
web3

Dependencies updated

web3-core

defaultTransactionType is now type 0x2 instead of 0x0 (#6282)
Allows formatter to parse large base fee (#6456)
The package now uses EventEmitter from web3-utils that works in node envrioment as well as in the browser. (#6398)

web3-eth

Transactions will now default to type 2 transactions instead of type 0, similar to 1.x version. (#6282)

web3-eth-contract

The events property was added to the receipt object (#6410)

web3-eth-ens

Dependencies updated

web3-eth-iban

Dependencies updated

web3-eth-personal

Dependencies updated

web3-net

Dependencies updated

web3-providers-http

Bump cross-fetch to version 4 (#6463).

web3-rpc-methods

Dependencies updated

4.1.3-dev.e760667.0 - 2023-10-13

4.1.3-dev.d036166.0 - 2023-09-22

4.1.3-dev.c490c18.0 - 2023-09-28

4.1.3-dev.bfcbea8.0 - 2023-10-02

4.1.3-dev.b8fa712.0 - 2023-09-27

4.1.3-dev.b38f00d.0 - 2023-10-12

4.1.3-dev.ae98628.0 - 2023-10-09

4.1.3-dev.9b03f9d.0 - 2023-10-04

4.1.3-dev.9a5fd87.0 - 2023-10-10

4.1.3-dev.90d78c1.0 - 2023-10-02

4.1.3-dev.80adabe.0 - 2023-09-23

4.1.3-dev.80986bb.0 - 2023-10-04

4.1.3-dev.70d1957.0 - 2023-10-17

4.1.3-dev.6e43d1b.0 - 2023-10-12

4.1.3-dev.66ddb7e.0 - 2023-09-21

4.1.3-dev.54c5ed0.0 - 2023-09-19

4.1.3-dev.4b445ae.0 - 2023-09-29

4.1.3-dev.42502b6.0 - 2023-10-16

4.1.3-dev.2b445bf.0 - 2023-09-19

4.1.3-dev.226b3ba.0 - 2023-10-17

4.1.3-dev.171b413.0 - 2023-09-21

4.1.3-dev.10d1f12.0 - 2023-10-16

4.1.3-dev.0e78235.0 - 2023-10-05

4.1.3-dev.09f4c8b.0 - 2023-10-17

4.1.3-dev.4879326.0 - 2023-10-09

4.1.3-dev.3060994.0 - 2023-09-28

4.1.2 - 2023-09-19Fixed
web3

Fix of incorrect provider warning behavior

web3-eth-accounts

Fixed "The r and s returned by sign to does not always consist of 64 characters" (#6411)

web3-eth-contract
web3-utils

soliditySha3() with BigInt support

Added
web3-core

Added to Web3Config property contractDataInputFill allowing users to have the choice using property data, input or both for contract methods to be sent to the RPC provider when creating contracts. (#6377) (#6400)

web3-eth

Added to Web3Config property contractDataInputFill allowing users to have the choice using property data, input or both for contract methods to be sent to the RPC provider when creating contracts. (#6377) (#6400)

web3-eth-contract

Added dataInputFill as a ContractInitOption, allowing users to have the choice using property data, input or both for contract methods to be sent to the RPC provider. (#6355)
Added to Web3Config property contractDataInputFill allowing users to have the choice using property data, input or both for contract methods to be sent to the RPC provider when creating contracts. (#6377)

web3-types

add asEIP1193Provider to Web3BaseProvider so every inherited class can have the returned value of request method, fully compatible with EIP-1193. (#6407)

Changed

Dependencies updated of packages

    from web3 GitHub release notes

Commit messages

Package name: web3

c8799b0 changelog bumps
50a2469 version bumps
09f4c8b Fix validation uint int sizes (#6434)
226b3ba 6508 fix (#6509)
70d1957 Add functionality to extend tx types (#6493)
10d1f12 socket provider fix 6416 (#6496)
42502b6 Avoid using `**` with `BigInt` (#6506)
e760667 update tests (#6474)
6e43d1b Fix typos (#6494)
b38f00d getRevertReason update for signed Txs (#6497)
9a5fd87 fix: web3.min.js cdn 404 (#6489)
4879326 Implement `EventEmitter` compatible with browsers (#6398)
ae98628 Bump postcss from 8.4.24 to 8.4.31 in /docs (#6476)
6d99cd0 waitForTransactionReceipt fix (#6464)
0e78235 Bump zod from 3.21.4 to 3.22.3 (#6477)
80986bb fix stale (#6473)
9b03f9d Fixed withdrawals property type bytes to address (#6471)
90d78c1 add privateKeyToPublicKey function to accounts (#6466)
bfcbea8 Bump cross-fetch to version 4 (#6463)
4b445ae Fixup base fee type (#6456)
3060994 6344 - normalize v on recover  (#6462)
c490c18 feat: replace ethers abi coder with ours (#6385)
b8fa712 fix: timer types to be context dependent (#6460)
80adabe make default transaction 0x2 (#6426)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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

Comparison is base (90f4b6a) 78.10% compared to head (0e50852) 78.10%.
 Consider uploading reports for the commit c9e9e3d to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1897   +/-   ##
=======================================
  Coverage   78.10%   78.10%
=======================================
  Files          39       39
  Lines        3060     3060
  Branches      616      616
=======================================
  Hits         2390     2390
  Misses        479      479
  Partials      191      191

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


net: implement dhcp ipam plugin

DHCP is particularly useful in MACVLAN. It is an well understood and standard part of network infrastructure and having ability to leverage it for containers (just like VM's do) is important.

Will the DHCP client run outside the container while configuring the network namespace before the container is fully started? If so, how are the dhcp leases renewed?
Or is the container (stage1?) supposed to be smart enough to do it?
systemd-nspawn chose the second solution so it can let the container renew the dhcp leases itself.

fixed by #951

I wouldn't consider this fixed as long as the user manually has to run the dhcp daemon. We should figure out a way to make it at as seamless as seamless as possible. There are again several ways to solve this. I'll describe a few that come to my mind:

Run the dhcp daemon inside the stage1 as a service file.
Put a (socket activated) service with the other rkt related service units and possibly install these using rkt install

Assigning to steveej to decide what he wants to do here.

@steveeJ Do you still think this is within the scope of rkt to address? To me seems like a concern of into CNI or an orchestrator.

To me seems like a concern of into CNI or an orchestrator.

That's a valid point. I think we have to at least write documentation how to get this up and running, maybe coupled with a service file for systemd users that helps running the daemon.

systemd files would be good, also why does it ignore the dns?

/cc @squeed @steveeJ ^^


update fprime submodule to v3.4.3

as to support building the math component with fprime v3.4.3 (latest release at time of writing)

Fixed in v3.5.0 release


Allow sorting of responses

It would be very helpful if some of the responses could be sorted by arbitrary fields. For example, to have the /transactions endpoint return the latest transactions by the block number, in descending order, so you can get the latest transactions without having to do any pagination.

When filtering by account address results are returned oldest to newest, otherwise, they are returned newest to oldest.
For reference, I implemented this in a prototype while debugging something and we had some discussion: https://github.com/algorand/indexer/pull/283/files#diff-8fbec00be6e6b2f77a294cbe9a3ee8e3fbdcb5eb13be3046e5da8277302264c2L1400

+1 this feature - in particular I would like to order the transactions for a given account and application from oldest to most recent. Since I use the account field, the responses are automatically ordered from most recent to oldest.

+1 to this, we've also faced a need to get transactions ordered by desc

+1 to this feature.
It would be really helpful if we have sorted by field or at least the latest transactions.

@chaihoang we need to clarify what we should support for this issue.

Hi Team,
Do you have any plans to fix this issue ?
This is a critical requirement for my application (Explorer).
https://app.dappflow.org

Attached is the screenshot of the asset overview page.
Older transactions pop up first and the user has to navigate back to the last page to look at the recent transactions of the asset.
This is a must-have if we want to build the indexer UI.

@algodesk-io It's not on the roadmap yet, but we are considering it. What are the use cases that would be most beneficial? Is it just sorting by newest transactions?

@algodesk-io It's not on the roadmap yet, but we are considering it. What are the use cases that would be most beneficial? Is it just sorting by newest transactions?

Yes, sorting by newest transactions for an asset, application, account, should solve 50% of the usecase.
remaining includes,
Sort by newest assets
Sort by newest applications

@chaihoang Do you have any plans to support this?

@algoanne

@algodesk-io with the refactoring of Indexer to use Conduit, supporting this type of feature might become possible. Sorting wouldn't be practical/performant if you were using an Indexer with full data, but if you used Conduit to filter out most of the data (just keeping data involving a certain app ID for example) then suddenly you can support more interesting queries without worrying so much about performance.
That said, it's not in our near-term plan to work on this, just because of competing priorities. But, if someone was interested in adding this with an externally-contributed PR, we would welcome it.

In this ticket, we will:
enable sorting by most fields (ones that it makes sense to sort on), in either direction, for the transactions table only. New "order by" and "order direction" fields on the transactions endpoint.
we will disable pagination when using sorting, and work on pagination in a follow-up issue.


[Hexagon] Add power manager

This PR adds a new class, HexagonPowerManager, which interfaces with the HAP_power API to request maximum performance.
cc: @mehrdadh @csullivan @kparzysz-quic

cc @janetsc


fix: Started updated action.yaml

Started fix for #11
missing fix for .releaserc{,.js,.cjs} .release.config.{js,cjs} files

Superseded by https://github.com/semantic-release-action/next-release-version/commit/ebbae1096f7f4fa8ef46e24f5c8108fa565b3604


Fix a couple of doc issues

Fix experimental_warning reference
Remove ref to `sql-copy-from-validation in 4.8.0 release notes as this setting (and ref) has been removed with: #14654

I don't think we need it in old versions - ref is not broken there? also, don't think we would release another 4.8/5.3?

yep, but it affects readthedocs builds as well

@mergifyio backport 4.8


[Question/Help] How to use proper use "DismissBlock"

Hi everyone,
I'm using this lib in one of my new projects and I amb having problems to find how to execute certain function when Alert is dimsissed. I can controll perfectly when it's closed by buttons, but when it's closed with tap on background i dont know how to do it. I have found the setDismissBlock but I can't see how to use it. Any help/link that may help me?

Hi,
I was looking to implement the same thing and your question pushed me to the right way. Finally I figured out how to implement dismissBlock and here is how:
As commented in SCLAlertView.swift file under SCLAlertViewResponder declaring:
"// Allow alerts to be closed/renamed in a chainable manner" and function "setDismissBlock" sits right in this class.
It is also a helpful example in comments under that one:
"Example: SCLAlertView().showSuccess(self, title: "Test", subTitle: "Value").close()"
As seen above, when you show any kind of alertView, right after it, instantiate dismissBlock with setDismissBlock() { } function instead of 'close()'
Final code will look like this:
alertView.showSuccess("Title goes here", subTitle: "Subtitle goes here").setDismissBlock() {
//Your code when alert view have been dismissed.
}
Cheers 😎


Required Components

What problem does this solve or what need does it fill?
Some components don't make sense without some other components, e.g. Transform without GlobalTransform, Visibility without CalculatedVisibility or Interaction without Node. We don't really have a way of communicating it other than putting it in a doc-comment. I feel like this is an unelegant and bug-prone solution.
What solution would you like?
I would like to have a #[require] attribute, applicable to a component A, taking in another component B as an argument, that would signal that every entity containing the component A has to also contain the component B. Then, when adding the component A to an entity, Bevy could perform a check to see if the component B is already on the entity (or is being added at the same time as component A) and if it's not, a panic would occur. Such a feature is implemented in Unity and I'm missing it in Bevy.
Further down the line we could implement compile-time checks for Bundles to see if they contain all the required components. Similarly we could check if a Query has redundant With filters.
What alternative(s) have you considered?
We could leave it as is and believe the user to remember to add the necessary components. User could also add a system checking if there are any entities in the world with one component and not the other, although it would probably be much less performant.

Potential duplicate for #1481.

this would also help with my suggestion of cutting down on metadata if instead of panic i just inserted the default for all the needed components #6523

See also #5590


Try to silently fall back to a local monarch

This is a crazy idea Dustin and I had.

we can't repro this at will. But we kinda have an idea of where the deref is. We don't know if the small patch (throw, and try again) will fix it. We're sure that the "just fall back to an isolated monarch" will work. I'd almost rather take a build testing the small patch first, to see if that works

This might seem crazy
in 1.12, isolated monarch. In 1.13, "small patch". In 1.14, we can wait and see

I can write more details in the morning. It's 5pm here so if we want this today, here it is.
@dhowett double check my velocity flag logic here. Should be always true for Release, and off for Dev, Preview.

[x] closes #12774

@msftbot merge this in 1 minutes


Can't talk

I can't talk because I have mouthsore

You should take a lot of Vitamin C and eat more to get rid off it!

You should take a lot of Vitamin C and eat more to get rid off it!

Wow, Thanks! It helps


Add ORT training notebooks

What does this PR do?
Add ORT training text classification and summarization notebooks to Optimum notebook catalog.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


ci: avoid generating go-cover in sle-micro read-only file system

Which issue(s) this PR fixes:

Issue https://github.com/longhorn/longhorn/issues/9001
What this PR does / why we need it:
avoid generating go-cover in sle-micro read-only file system
Special notes for your reviewer:
Additional documentation or context

cc @longhorn/qa


bumped versions

Hi @Ch4s3,
Thanks for update.
I have no skills in exilir.
Will it be accurate (e.g : avoid manually update version) not to use any version ? Will mix use the latest stable version in case of no version specified for dependencies ?
Regards,

@waghanza
The elixir: "~> 1.6.4", change means that is the minimum Elixir version supported (newer minor/patch is fine).
The {:phoenix, "~> 1.3.0"}, means this is the minimum phoenix version supported (newer minor/patch is fine).
The {:plug, "~> 1.5"}, means this is the minimum plug version supported (newer minor/patch is fine).
:-)

@OvermindDL1 okay, so I assume the version condition are similar to ruby / Gemfile
I mean that ~> 1.6.5 mean >= 1.6.5 && < 1.7.0, is that right ?
In Gemfile (https://github.com/tbrand/which_is_the_fastest/blob/master/ruby/roda/Gemfile for example) I've remove version number to force to the last (published gem) release, it may differ in elixir / compiled lang

I don't use ruby, but ~> 1.6.5 means 1.6.* and ~> 1.6 means 1.*.*.  There is a lock file to lock at a specific version but you can upgrade past that by either specifying a new version of just running mix deps.upgrade or so to grab the latest version that still matches the given semver.  Leaving out the ~> and just having a number in the mix.exs file will permanently only allow that version and no other.
On an aside, you can also have it use a file system location, a git with specific commit/tag, and a few other things (in addition to whatever else you want as it is a pluggable system).

In Gemfile (/ruby/roda/Gemfile@master for example) I've remove version number to force to the last (published gem) release, it may differ in elixir / compiled lang

This sounds absolutely horrifying to me...  The latest version could have an API change that makes it no longer work according to semver bounds, so why on earth would anyone ever do that ever?!  o.O

This sounds absolutely horrifying to me
Sure, for the kind of application that will run for some users.

I mean, if there is an API change, we (maintainers) could handle it :stuck_out_tongue_closed_eyes:


customToolbarSelect  i can't change position of button to left

i'm trying to customise tool bar when rows selected using function customtoolbarselect and trying to set button on the left next to (name of selected  rows)
this my code
on sandbox
https://codesandbox.io/s/pedantic-minsky-ylrdu
and this what i want actually

I can't tell how your codesandbox example maps to the screenshot in terms of what you want to happen, so I can't give specific advice (which button in your example is supposed to go where exactly).
However, I can say that you might need to change the display away from flex, as it can be difficult to customize the individual positioning of elements in flexbox. You might need to remove flex from MUIDataTableToolbarSelect-root, and then set your toolbar actions and rows selected containers to inline-block (you should be able to modify the first div with first-child on the parent).


Deprecation of implicit dependencies / Possible incompatibility with Gradle 8.0

./gradlew publishPlugins --warning-mode all

> Task :pinpit:sourcesJar
Execution optimizations have been disabled for task ':pinpit:sourcesJar' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '.../mobanisto/pinpit-gradle-plugin/pinpit/build/generated/buildconfig'. Reason: Task ':pinpit:sourcesJar' uses this output of task ':pinpit:buildConfig' without declar
ing an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dependenc
y for more details about this problem.
Gradle detected a problem with the following location: '.../mobanisto/pinpit-gradle-plugin/pinpit/build/generated/buildconfig'. Reason: Task ':pinpit:sourcesJar' uses this output of task ':pinpit:buildConfig' without declaring
an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dependency fo
r more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.3.3/userguide/more_about_tasks.h
tml#sec:up_to_date_checks for more details.

> Task :pinpit:publishPluginJar
Execution optimizations have been disabled for task ':pinpit:publishPluginJar' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '.../mobanisto/pinpit-gradle-plugin/pinpit/build/generated/buildconfig'. Reason: Task ':pinpit:publishPluginJar' uses this output of task ':pinpit:buildConfig' without
declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dep
endency for more details about this problem.
  - Gradle detected a problem with the following location: '..../mobanisto/pinpit-gradle-plugin/pinpit/build/libs/pinpit-0.7.1-sources.jar'. Reason: Task ':pinpit:generateMetadataFileForPluginMavenPublication' uses this output o
f task ':pinpit:publishPluginJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userg
uide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '.../mobanisto/pinpit-gradle-plugin/pinpit/build/generated/buildconfig'. Reason: Task ':pinpit:publishPluginJar' uses this output of task ':pinpit:buildConfig' without decl
aring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_depende
ncy for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.3.3/userguide/more_about_t
asks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '.../mobanisto/pinpit-gradle-plugin/pinpit/build/libs/pinpit-0.7.1-sources.jar'. Reason: Task ':pinpit:generateMetadataFileForPluginMavenPublication' uses this output of ta
sk ':pinpit:publishPluginJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide
/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://do
cs.gradle.org/7.3.3/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.

> Task :pinpit:publishPluginJavaDocsJar
Execution optimizations have been disabled for task ':pinpit:publishPluginJavaDocsJar' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '.../mobanisto/pinpit-gradle-plugin/pinpit/build/libs/pinpit-0.7.1-javadoc.jar'. Reason: Task ':pinpit:generateMetadataFileForPluginMavenPublication' uses this output o
f task ':pinpit:publishPluginJavaDocsJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3
.3/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '.../mobanisto/pinpit-gradle-plugin/pinpit/build/libs/pinpit-0.7.1-javadoc.jar'. Reason: Task ':pinpit:generateMetadataFileForPluginMavenPublication' uses this output of ta
sk ':pinpit:publishPluginJavaDocsJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/u
serguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See ht
tps://docs.gradle.org/7.3.3/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.

We're using a very old id("com.gradle.plugin-publish") version "0.17.0" (from Novemeber 2021). I think I looked into a migration before and it seemed anything but straightforward.


Pztest111

Does this PR include tests?
This project is developed under a test-driven workflow, so please refrain from submitting patches without test coverage. If you are not familiar with testing in Python, please raise an issue instead.

Wrong location


Add translations for Croatian language

Add translations for Croatian language

@mbanusic thank your for contribution, appreciated.


Vague

"Enter your email address in the prompt so we can send you a link to join the Office 365 account where your domain is currently added."
What prompt? Where?

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

ID: 24eaf551-7e49-ee4a-2979-8515f92d4d2a
Version Independent ID: 67e53343-d996-ce5e-4742-0c0d819fbca1
Content: Do an admin takeover in Office 365
Content Source: Office365-Admin/misc/become-the-admin.md
Service: o365-administration
GitHub Login: @pebaum
Microsoft Alias: pebaum

@micfau1091 I've added more clarifications on the documentation

Addressed at PR #264

Thank you guys!!!
-Michael
On Fri, Feb 8, 2019 at 10:03 AM Jose Gabriel Ortega C <
<EMAIL_ADDRESS>wrote:

Addressed at PR #264
https://github.com/MicrosoftDocs/OfficeDocs-O365ITPro/pull/264
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/OfficeDocs-O365ITPro/issues/42#issuecomment-461872883,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATQpRXwDV5KgwzYA0qlJDUOi_6lUMJUnks5vLa3ygaJpZM4YPBhS
.

@micfau1091 - Thank you for submitting this Feedback.
From my understanding the issue has been resolved. If the issue is not resolved please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@AndreaBarr - This issue can be closed. Thank you.


Unable to authenticate users

Description
Can not create new users
Steps for reproduce

Clone this repo and deploy with serverless deploy -v
Clone the frontend api for this repo and add the configuration params from your serverless backend
Try to create a new user

Actual result

{"__type":"NotAuthorizedException","message":"Incorrect username or password."}

@BorjaRobles Are you still having this issue?


Made deliminater be changable. Default is "White space character".

I want to use comma to deliminate tags.
Default deliminater ([NSCharacterSet whitespaceCharacterSet]) is prereserved as last version.

Hi, nice addition! I merge it.