proposal: runtime: add SecureErase or SecureEraseOnFinalize functionality

What version of Go are you using (go version)?

$ go version go1.15.6 linux/amd64

Does this issue reproduce with the latest release?
This is not an issue, but instead a feature request.
While I can write my own SecureErase and SecureEraseOnFinalize, it would be fantastic if the runtime had a method to do this. (I could not find a method call that does the SecureErase part, though I can do it with some of the runtime components like KeepAlive or the Finalize component myself.
What is being requested is to build this into the runtime as a feature.   Developers than can erase any sensitive data to reduce the window of opportunity for a memory-dump analysis or a HeatBleed style protocol attack.  In other words a way to minimize the time in memory that a sensitive piece of information is available.
What operating system and processor architecture are you using (go env)?

This is a feature ask.

What did you expect to see?
I would like a runtime.SecureErase(interface{}) and a runtime.MarkSecureEraseAtFinalize(interface{}) method to ensure zero of memory at explicit call-time or zero of memory before GC.
What did you see instead?
I had to write this myself.

Lengthy discussion about this (including several people even doubting this can actually be implemented in Go) at #21865. I would be tempted to suggest we keep all the discussion in that thread.

Lengthy discussion about this (including several people even doubting this can actually be implemented in Go) at #21865. I would be tempted to suggest we keep all the discussion in that thread.

Closing as duplicate of #21865.

No change in consensus, so declined.
— rsc for the proposal review group


Do not fail es-cleaner if there are no jaeger indices

Resolves #1468
The original stacktrace
Traceback (most recent call last):
  File "plugin/storage/es/esCleaner.py", line 89, in <module>
    main()
  File "plugin/storage/es/esCleaner.py", line 49, in main
    filter_main_indices(ilo, prefix)
  File "plugin/storage/es/esCleaner.py", line 65, in filter_main_indices
    ilo.filter_by_age(source='name', direction='older', timestring='%Y-%m-%d', unit='days', unit_count=int(sys.argv[1]))
  File "/usr/local/lib/python3.6/site-packages/curator/indexlist.py", line 495, in filter_by_age
    stats_result=stats_result
  File "/usr/local/lib/python3.6/site-packages/curator/indexlist.py", line 356, in _calculate_ages
    self._get_name_based_ages(timestring)
  File "/usr/local/lib/python3.6/site-packages/curator/indexlist.py", line 279, in _get_name_based_ages
    self.empty_list_check()
  File "/usr/local/lib/python3.6/site-packages/curator/indexlist.py", line 226, in empty_list_check
    raise exceptions.NoIndices('index_list object is empty.')
curator.exceptions.NoIndices: index_list object is empty.

I have tested this with ES 5.x and 6.x. Archive storage works also fine.

@pavolloffay Just checking - you say archive storage works fine, but shouldn't filter_archive_indices also have the same empty_list check?

Yes the archive storage wors well. The methods invoked in ilo does not fail if the list is empty.


Multipacket SysEx is not received correctly on macOS

I'm trying to use DryWetMidi on MacOS, to receive SysEx messages from a MIDI USB device.
The sysEx size is 251 Bytes.
The Windows build works fine, but with the MacOS build only the first two bytes are received in the SysExEvent.
(MacOS Version 12.61 Monterey)
Let me know if you need any more information. Thanks,
James

Hi Max,
Thanks for the quick response, here are my answers:

It works fine in other midi software including SysEx Librarian & MidiView
I'll check this next, will post a response asap.

James

Regarding bytes: are you sure thare is no F0 byte at the start of the message?

Sorry, there is a F0 at the start of the message. Just that SysExEvent.Data's print has truncated it.
I've just tried this with another device and send a variety of SysEx messages, and it seems to do the same.
The simplest one which displays the issues is:
F0 7F 60 40 F7
Thanks
James

Just as an update, the sysEx messages are fine with 2 bytes or less.
I've just tried another API using RtMidi on mac os, and that works:
RtMidi.Core
Maybe that can be some help for reference?

Well, I've created unit tests with the provided bytes arrays. Running them on virtual machine with Monterey 12.6.1 ends with success, sysex events are received correctly. So we need to do some tests on your machine.
I've prepared the archive: TestKit.zip. Unzip it please somewhere on your computer.

First of all, run the LoopbackDevice program from the folder in a separate Terminal window:
./LoopbackDevice "MIDI A" "MIDI B" "MIDI C"

This commad will create three virtual loopback devices. Devices are present in the system as long as the program running, so please don't close the Terminal.

Now let's open the SendDataViaDwm.sln solution in IDE (VS for Mac or Rider) and run it. We expect to see the message that sysex F0 7F 60 40 F7 is received. Please write me if bytes are correct in the message (F0 will be omitted).

Then let's open the SendDataViaBytes.sln solution in IDE (VS for Mac or Rider) and run it. We expect to see the message that sysex F0 7F 60 40 F7 is received. Please write me if bytes are correct in the message (F0 will be omitted).

Hi Max,
Just ran the test's on the Mac device I have, The "SendDataViaDwm.sln" worked correctly. But the "SendDataViaBytes.sln" did not. I received no message with the "SendDataViaBytes.sln" and only the Press any key to exit... displayed.

Thanks James!
Well, I'll try to provide new version of the SendDataViaBytes to try to understand why it's not working. For now, can you please confirm that you see wrong data with SendDataViaDwm if you send sysex via your device the problem occurred with?

Just checked SendDataViaDwm with two different MIDI USB devices, I sent the SysEx from my windows machine.
With both devices it only shows the first two bytes 7F 60. On the loopback it is fine.

Pretty strange... Hm, it looks like we need to write some code in C in XCode. I'll try to provide you the code tomorrow.

Hi James,
I've prepared a new solution: ViewPacketsData.zip. As before, run the LoopbackDevice utility first and then run the solution. Replace name of the device with the desired one from where you receive broken data:
InputDevice.GetByName("MIDI A");

Just follow the instructions from the utility and provide me an output text please. I made the solution without any tests so please write me about any errors if any.

Hi Max,
I've just run the ViewPacketsData, here's the output from the terminal:
Packet 0 / 1 data:
    F0 0 21
Packet 0 / 1 data:
    5F 0 0
Packet 0 / 1 data:
    1 3 1 1 6 0
Packet 0 / 1 data:
    0 0 0
Packet 0 / 1 data:
    0 4C 0 0 41 0 0 52 0 0 49 0 0 20 0 0 42 0 0 20 0 0 38 0 0 54 0 0 48 0 0 20 0 0 4E 0 0 4F 0 0 54 0 0 45 0 0 20 0
Packet 0 / 1 data:
    0 1 0 0 F 2 0 0 0 0 74 3 0 64 0 0 74 3 0 0 0 0 74 3 0 64 0 0 1 0
Packet 0 / 1 data:
    0 18 0 0 1E 0 0 1C 0 0 7F 7F 3 28 0
Packet 0 / 1 data:
    0 64 0 0 7F 7F
Packet 0 / 1 data:
    3 5 0
Packet 0 / 1 data:
    0 64 0
Packet 0 / 1 data:
    0 7F 7F
Packet 0 / 1 data:
    3 5 0
Packet 0 / 1 data:
    0 64 0
Packet 0 / 1 data:
    0 0 0
Packet 0 / 1 data:
    0 2C 0 0 1 0 0 0 0 0 64 0 0 64 0 0 64 0 0 64 0 0 0 0 0 0 0 0 2C 2 0 14 0 0 28 0 0 3C 0 0 64 0 0 64 0 0 64 0
Packet 0 / 1 data:
    0 0 0 0 6C 7F 3 6C 7F 3 4 0 0 A 0 0 0 0 0 7F 7F 3 1 0 0 48 1 0 0 0 0 6C 7F 3 7F 7F 3 4 0 0 7F 7F 3 0 0 0 7F 7F
Packet 0 / 1 data:
    3 1 0 0 48 1 0 0 0 0 30 7F 3 14 0
Packet 0 / 1 data:
    0 48 1
Packet 0 / 1 data:
    0 0 0
Packet 0 / 1 data:
    0 F7

Hi James,
Is that output on sending one single event or multiple ones? If multiple, can you please just send a single one (for example, F0 7F 60 40 F7)?

@James-Morrell Any news?

Hi Max,
Sorry I've been away for a couple of days, will look at it some point today :)
James

Hi James,
Here another one new version: ViewPacketsData.zip :)

Hi @melanchall
Here's the output for the latest ViewPacketsData.zip
Waiting for packets information...
Just send problem sysex and wait some time, then just press any key to see the log
 Message received at [2022-12-16T14:47:01.2838960Z]!
Packet 0 / 1 data:
    F0 00 21
Message received at [2022-12-16T14:47:01.3909050Z]!
Packet 0 / 1 data:
    5F 00 00
Message received at [2022-12-16T14:47:01.3910180Z]!
Packet 0 / 1 data:
    01 03 01 01 06 00 00 00 00 00 4C 00 00 41 00 00 52 00
Message received at [2022-12-16T14:47:01.3911710Z]!
Packet 0 / 1 data:
    00 49 00 00 20 00
Message received at [2022-12-16T14:47:01.3912260Z]!
Packet 0 / 1 data:
    00 42 00 00 20 00 00 38 00 00 54 00 00 48 00 00 20 00 00 4E 00 00 4F 00 00 54 00 00 45 00 00 20 00 00 01 00 00 0F 02 00 00 00 00 74 03 00 64 00
Message received at [2022-12-16T14:47:01.3912940Z]!
Packet 0 / 1 data:
    00 74 03 00 00 00 00 74 03 00 64 00 00 01 00 00 18 00 00 1E 00 00 1C 00 00 7F 7F 03 28 00 00 64 00 00 7F 7F 03 05 00 00 64 00 00 7F 7F
Message received at [2022-12-16T14:47:01.4502970Z]!
Packet 0 / 1 data:
    03 05 00
Message received at [2022-12-16T14:47:01.4503970Z]!
Packet 0 / 1 data:
    00 64 00
Message received at [2022-12-16T14:47:01.4505440Z]!
Packet 0 / 1 data:
    00 00 00
Message received at [2022-12-16T14:47:01.4506370Z]!
Packet 0 / 1 data:
    00 2C 00 00 01 00 00 00 00 00 64 00 00 64 00 00 64 00 00 64 00 00 00 00 00 00 00 00 2C 02 00 14 00 00 28 00 00 3C 00 00 64 00 00 64 00 00 64 00
Message received at [2022-12-16T14:47:01.4507270Z]!
Packet 0 / 1 data:
    00 00 00 00 6C 7F 03 6C 7F 03 04 00 00 0A 00 00 00 00 00 7F 7F 03 01 00 00 48 01 00 00 00 00 6C 7F 03 7F 7F 03 04 00 00 7F 7F 03 00 00 00 7F 7F
Message received at [2022-12-16T14:47:01.4507960Z]!
Packet 0 / 1 data:
    03 01 00 00 48 01 00 00 00 00 30 7F 03 14 00
Message received at [2022-12-16T14:47:01.4558240Z]!
Packet 0 / 1 data:
    00 48 01
Message received at [2022-12-16T14:47:01.4559230Z]!
Packet 0 / 1 data:
    00 00 00
Message received at [2022-12-16T14:47:01.4560460Z]!
Packet 0 / 1 data:
    00 F7

Press any key to exit...

Do you want the other output from the previous version, it is the same but without the time stamps.
James

Hi James,
Thank you a lot! Now I know for sure what's going on. Your message was split into multiple separate messages. DryWetMIDI right now assumes that single packet == single complete message. Which is obviously wrong according to your tests.
It's definitely the bug in my library. It should be pretty easy to fix, but I think I can handle it in next year only (I'm going to vacation right now :)).
I appreciate your assistance with diagnosing the problem. Thanks!

Hi Max,
Glad I could help, let me know if you need anymore tests this end!
Have a good holiday!
James

Thanks James! If I can fix the bug before next year, I will definitely let you know.

Hi James,
Looks like the bug has been fixed now according to my unit tests. I've published new prerelease version of the library - 6.1.4-prerelease2. @James-Morrell Can you please install it into your project and let me know whether the problem is gone or not?
Thanks,
Max

Hi Max,
Sorry for the late response, been away for the holidays!
Just tested 6.1.4-prerelease2 and it's all working!
Kind regards,
James

Hi James,
Great! Thanks for the issue and your assistance! You've made the library better.
Thanks,
Max

:rocket: 6.1.4 version is released now!
Prerelease NuGet packages will be unlisted soon, so please update the package references to the new version.
Thanks for using the library!


Update congestion

This implements cubic congestion and rack!
Cubic: https://www.cs.princeton.edu/courses/archive/fall16/cos561/papers/Cubic08.pdf
RACK: https://datatracker.ietf.org/doc/rfc8985/
RACK is used for fast recovery instead of the reno heuristic and seems very very efficient in testing.
Cubic is used for general congestion window upgrade/downgrade.
Both are used by Linux TCP per default, so also very established.
This is still missing RACK-TLP, but I think that should come in another PR to minimise the disruption here.

@mafintosh I fixed the build issues, which turned out to be caused by libm, the standard math library, not being linked on Linux and Windows being an arse about shared libraries. For future reference, CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS is needed to ensure that symbols are actually exported from the shared library on Windows or, alternatively, all exported symbols must be marked with __declspec(dllexport). libuv does the latter: https://github.com/libuv/libuv/blob/06948c6ee502862524f233af4e2c3e4ca876f5f6/include/uv.h#L38


error on RandomForest fit with mock data

The traceback seems to cut off at trees.py line 504, the rest I couldn't identify where the problem is
Traceback (most recent call last):
File "model_gefs.py", line 471, in
test()
File "model_gefs.py", line 343, in test
test_helper(m['model_pars'], m['data_pars'], m['compute_pars'])
File "model_gefs.py", line 352, in test_helper
fit(data_pars=data_pars, compute_pars=compute_pars, out_pars=None)
File "model_gefs.py", line 93, in fit
model.model.fit(Xtrain.values, ytrain.values)
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\trees.py", line 504, in fit
self.surrogate)
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\numba\core\dispatcher.py", line 415, in _compile_for_args
error_rewrite(e, 'typing')
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\numba\core\dispatcher.py", line 358, in error_rewrite
reraise(type(e), e, None)
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\numba\core\utils.py", line 80, in reraise
raise value.with_traceback(tb)
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function() found for signature:

getitem(array(int64, 1d, C), array(bool, 2d, C))

There are 16 candidate implementations:

Of which 14 did not match due to:
Overload of function 'getitem': File: : Line N/A.
With argument(s): '(array(int64, 1d, C), array(bool, 2d, C))':
No match.
Of which 2 did not match due to:
Overload in function 'GetItemBuffer.generic': File: numba\core\typing\arraydecl.py: Line 162.
With argument(s): '(array(int64, 1d, C), array(bool, 2d, C))':
Rejected as the implementation raised a specific error:
TypeError: unsupported array index type array(bool, 2d, C) in [array(bool, 2d, C)]
raised from C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\numba\core\typing\arraydecl.py:69

During: typing of intrinsic-call at C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\utils.py (32)
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\utils.py", line 32:
def resample_strat(x, y, n_classes):

for i in range(n_classes):
s = np.random.choice(idx[y==i], counts[i], replace=True)
^
During: resolving callee type: type(CPUDispatcher(<function resample_strat at 0x00000235B2228BF8>))
During: typing of call at C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\trees.py (174)
During: resolving callee type: type(CPUDispatcher(<function resample_strat at 0x00000235B2228BF8>))
During: typing of call at C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\trees.py (174)
During: resolving callee type: type(CPUDispatcher(<function resample_strat at 0x00000235B2228BF8>))
During: typing of call at C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\trees.py (174)
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\trees.py", line 174:
def build_forest(X, y, n_estimators, bootstrap, ncat, imp_measure,

for i in range(start, stop):
Xtree_, ytree_, _ = resample_strat(X, y, n_classes)

Thanks for reporting this. I suspect that your class variable is shaped as a 2D array. Could check if it works if you reshape your class variable to be 1D? For instance, y = y.reshape(-1).

Thank you for responding,
Yes that fixed the fit(), thanks
Now model.topc() is throwing an error, if you can help I appreciate it
Traceback (most recent call last):
File "model_gefs.py", line 94, in fit
model.model = model.model.topc()  # Convert to a GeF
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\trees.py", line 522, in topc
pc.root = SumNode(scope=self.scope, parent=None, n=1)
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\numba\core\dispatcher.py", line 415, in _compile_for_args
error_rewrite(e, 'typing')
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\numba\core\dispatcher.py", line 358, in error_rewrite
reraise(type(e), e, None)
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\numba\core\utils.py", line 80, in reraise
raise value.with_traceback(tb)
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Internal error at <numba.core.typeinfer.CallConstraint object at 0x000001D48EBE81D0>.
Failed in nopython mode pipeline (step: nopython mode backend)
Can only insert i64* at [4] in {i8*, i8*, i64, i64, i64*, [1 x i64], [1 x i64]}: got i32*
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\nodes.py", line 49:
def init(self, parent, scope, type, n):

self.sibling = None
self.scope = scope
^
During: lowering "(self).scope = scope" at C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\nodes.py (49)
During: resolving callee type: jitclass.Node#1d48d0204a8<id:int64,parent:OptionalType(DeferredType#2012402805896) i.e. the type 'DeferredType#2012402805896 or None',left_child:OptionalType(DeferredType#2012402805896) i.e. the type 'DeferredType#2012402805896 or None',right_child:OptionalType(DeferredType#2012402805896) i.e. the type 'DeferredType#2012402805896 or None',sibling:OptionalType(DeferredType#2012402805896) i.e. the type 'DeferredType#2012402805896 or None',scope:array(int64, 1d, A),type:unicode_type,n:float64,w:OptionalType(array(float64, 1d, A)) i.e. the type 'array(float64, 1d, A) or None',logw:OptionalType(array(float64, 1d, A)) i.e. the type 'array(float64, 1d, A) or None',comparison:int64,value:array(float64, 1d, A),mean:float64,std:float64,a:float64,b:float64,logcounts:OptionalType(array(float64, 1d, A)) i.e. the type 'array(float64, 1d, A) or None',p:OptionalType(array(float64, 1d, A)) i.e. the type 'array(float64, 1d, A) or None',logp:OptionalType(array(float64, 1d, A)) i.e. the type 'array(float64, 1d, A) or None',upper:array(float64, 1d, A),lower:array(float64, 1d, A)>
During: typing of call at C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\nodes.py (123)
Enable logging at debug level for details.
File "C:\Users\asus\anaconda3\envs\dsa2\lib\site-packages\gefs\nodes.py", line 123:
def SumNode(parent, scope, n):
return Node(parent, scope, 'S', n)
^


Visual Studio 2019 and ability to build/debug a project that will target .NET 6 REL

UPDATE
For today latest Visual Studio 2019 (16.11.x) doesn't officially support .NET 6 development. Possible workround is described here.
As .NET 5.0 reaches EOL in 05.2022 and .NET Core 3.1 - in 12.2022 (.Net Core Lifecycle) so Visual Studio 2019 will be unable to target .NET in a supported manner. But Visual Studio 2019 16.11 itself is supported untill 2029 (VS 2019 Product Lifecycle).
I've created Developer Community feature demand asking to make .NET 6 LTS development available in Visual Studio 2019.
ORIGINAL POST
Is it planned to support Windows 7 SP1 and Debian 9 by .NET 6 LTS (and MAUI)?
According to .NET Core Supported OS Lifecycle Policy block Exceptions to the supported platform policy:

One example is Windows 7 SP1. Windows 7 SP1 is out of support, but enterprise customers can buy Extended Security Updates, and many do. Given the widespread use of Windows 7 in the .NET ecosystem we chose to include Windows 7 SP1 (with Extended Security Updates installed) as a supported platform for .NET 5.0.

According to Lifecycle FAQ - Extended Security Updates block ESU Availability and End Dates:

Windows 7 Extended Security Updates 2022: January 12, 2022 - January 10, 2023

Debian 9 EOL is June 30, 2022.
So are you planning to support both operating systems by .NET 6 LTS (and MAUI)?
Thank you.
P. S. Are you planning to support .NET 6 LTS (and MAUI) development with Visual Studio 2019? Or it will be an upcoming Visual Studio 2021-only feature? Or maybe you don't have plans to release a new Visual Studio version in 2021?

@davidortinau You've asked about user experience and MAUI expectations The New .NET Multi-platform App UI article. I've wrote you an email almost a week ago - still no reponse. Any uptades on this?

@richlander According to this NET 6.0 will support  supports Windows 7 SP1 (Extended Security Updates EOL – January 10, 2023) but drops supporting Debian 9 (EOL is June 30, 2022) if compared to .NET 5. What is the reason for this decision?
And I still have no answer about OS support plans for MAUI for more than 3 month.
Even @davidortinau ignores my emails and this github topic..

Adding @leecow to see if he can comment on support plans as well

With respect to the Debian 9 decision, our general process is to exclude support for an OS version when that version will go EOL early in the new .NET version lifecycle. I haven't had any discussions with @davidortinau about MAUI OS support plans and expectations yet so can't offer anything on that topic.

.NET MAUI will support what WinUI 3 offers for Windows. https://microsoft.github.io/microsoft-ui-xaml/about.html#controls
Additional platform and version information is available here https://github.com/dotnet/maui#xamarinforms-vs-net-maui
Linux support will not be part of the .NET 6 release for .NET MAUI. It is under consideration for a future release, so please connect with me so we can better understand your needs for .NET MAUI and Linux<EMAIL_ADDRESS>or join one of the several discussions at https://github.com/dotnet/maui/discussions/

Closing the issue since I believe all questions were answered. Please let us know otherwise @bairog.

@mairaw my questions about Visual Studio IDE are still unanswered..

.NET MAUI will support what WinUI 3 offers for Windows. https://microsoft.github.io/microsoft-ui-xaml/about.html#controls
No support for Windows 7 SP1 with ESU - sad to hear, Uno project still supporting it..

Linux support will not be part of the .NET 6 release for .NET MAUI. It is under consideration for a future release
You are talking about plans for .NET 7, right?
Is it planned that .NET 7 development will be supported by Visual Studio 2019?
What are MS plans for Visual Studio 2021/2022/etc.?

With respect to the Debian 9 decision, our general process is to exclude support for an OS version when that version will go EOL early in the new .NET version lifecycle.

Debian 9 goes EOL (June 30, 2022) 7 month after .NET 6 planned release (November 2021). And it is considered as "will go EOL early".
Windows 7 SP1 with ESU goes EOL (January 10, 2023) 14 month after .NET 6 planned release and is still supported. So it is considered as "will NOT go EOL so early".
Am I understanded correctly that Windows 7 SP1 with ESU will be very unlikely supported by .NET 7?
Or maybe MS already have plans for .NET 7 OS support?

Visual Studio 2019 16.9 is released and considered to be a new Servicing Baseline.
In Servicing Baseline docs there is an image:

Did I understand it correctly that Visual Studio 16.9 will be the penultimate baseline version (before last baseline version 16.final)?
Does this mean that .NET 6 will be the last version that can be targeted by VS 2019?
Does .NET 7 development will be available exclusively in Visual Studio VNext?

@JacquelineWiddis @madskristensen  Visual Studio 2022 is announced and it is stated that

Visual Studio 2022 will have full support for .NET 6 and its unified framework for web, client, and mobile apps for both Windows and Mac developers. That includes the .NET Multi-platform App UI (.NET MAUI) for cross-platform client apps on Windows, Android, macOS, and iOS. You can also use ASP.NET Blazor web technologies to write desktop apps via .NET MAUI.
Does .NET 6 development will be available exclusively in Visual Studio 2022 or it will be also possibe in latest versions of Visual Studio 2019?
What about plans for .NET 7?

.NET Hot Reload was announced today  and it is stated that

While some capability is being made available in early .NET 6 previews and in Visual Studio 2019, for the full power of this feature we are targeting .NET 6 (and future releases of .NET) and Visual Studio 2022 as the set of frameworks and tooling that will have the most complete and optimized experience.

@LyalinDotCom maybe you clear MS intentions: does .NET 6 (I mean final version, not preview) development will be available exclusively in Visual Studio 2022 or it will be also possibe in future versions of Visual Studio 2019?
Thank you in advance.

@bairog Yes the current plan is that Visual Studio 2022 will be the supported tool version for .NET 6 development (when final as you note).

@bairog Yes the current plan is that Visual Studio 2022 will be the supported tool version for .NET 6 development (when final as you note).

I think Microsoft should reconsider that plan and make .NET 6 (final version) available both for Visual Studio 2019 and 2022 (latter may have more rich tooling).
Many companies recently invested in the purchase of Visual Studio 2019 due to the long lack of news about Visual Studio VNext.
Thank you in advance.

I can't understand why  the dotnet team  interested in  Drop OS(eg. Devs, Enterprise, customers)  ,  why can not you guys make thin native layer to make OS support easier ?   I mean look at Java,  they never try to drop any OS  in the past/ now / future  !!!!

@JacquelineWiddis @madskristensen @timheuer @mikadumont @richlander .NET 6 Preview 6 is announced and it is stated that

Starting with .NET 6 Preview 6, we’ve tested and support Visual Studio 2022 Preview 2.

But what exactly does it mean? Visual Studio 2022 is tested and supported in addittion to Visual Studio 2019?
Is it still possible to develop applications for .NET 6 preview 6 with Visual studio 2019?
Thank you in advance.

You can see in the download page @bairog what's the minimum version of VS supported:
https://dotnet.microsoft.com/download/dotnet/6.0

@rbhanda can you check on the VS version for .NET 6 preview 5? @bairog is right that there's a mismatch there.
I'll let others on the team chime in about future support plans re. Visual Studio and .NET 6.

https://github.com/dotnet/core/pull/6485 is created to correct the VS support version for .NET 6 Preview 5

I perfectly understand (at least it looks like this) that Microsoft plans to release Visual Studio 2019 version 16.11 (the last one) sometime in August-September, and then concentrate all its efforts on polishing Visual Studio 2022 and .NET 6 until their joint final release in November.
And most likely the final version of Visual Studio 2022 by November will have more features and tooling regarding .NET development. I really hope that at least the ability to build and debug a project targeting NET 6 final will be then backported to Visual Studio 2019 version 16.11.x. Looking forward to your final correct decision.

Tagging @jamshedd to help with this question.

Tagging @jamshedd to help with this question.

There were many questions in this thread so which one were you particularly thinking about :)
I will take the Win7 one - while this is by no means a final decision yet it is likely .NET 7 will not support Win7 since we would be shipping .NET 7 very close (Nov 2022) to when Win7 ESU ends (Jan 2023). But there are many factors that go into the decision including the portion of customers actively using Win7 at that point. We should have something to share around that next year.
Regarding VS support, as Tim already mentioned .NET 6 development (and also .NET7, etc.) will be supported on Visual Studio 2022.

Regarding VS support, as Tim already mentioned .NET 6 development (and also .NET7, etc.) will be supported on Visual Studio 2022.

Very sad to hear. .NET 6 preview 4 development was supported on Visual Studio 2019 16.11. Starting from .NET 6 preview 5 onwards only Visual Studio 2022 is supported. It is not good practice to drop support of IDE between adjacent previews.

@timheuer @jamshedd @mairaw .NET 6.0-rc1 was released yesterday and is “go live”
So there should be an IDE with the same license type - but as I can see yesterday's VS 2022-preview4 is still in preview.
VS 2019 16.11.x is stable but Microsoft team again ang again says that it is not supported for .NET 6.0.

So what’s the recommended way to build .NET 6.0-rc1 applications?
For today I can still build and debug .NET 6.0-rc1 applications (at least console, WinForms and WPF) by enabling preview SDKs in VS2019 settings and manually setting TFM in .csproj file - many thanks for leaving this possibility for developers. I kindly ask Microsoft to leave this unchanged also after .NET 6.0 release. Thank you in advance.

@timheuer @jamshedd @mairaw
.NET 6.0-rc1 was released yesterday and is “go live” - so there should be an IDE with the same license type.

So what’s the recommended and supported way to build .NET 6.0-rc1 applications in production?

This is correct the runtime platforms now have a go-live license. The tools are still in preview as you note and this is very common given platforms lock down a bit before giving tools some more time to finish support for final runtime APIs, scenarios, packages, naming, etc. We are still finishing VS features for .NET 6 around areas like hot reload, editor support for new C# 10 Lang features, and more. In general VS is more than just the current runtime release and so many features across the IDE are still finishing and this is not uncommon to have a platform have a go-live license for deployment while an IDE is still in preview. In fact as you and other devs use VS2022 for development please keep logging feedback bugs from VS for things that may not be working for your project/scenarios. We are still working on finishing and improving quality for .NET 6 projects but for many more things across the IDE.

@timheuer @jamshedd @mairaw
VS 2022 and .NET 6.0 were released yesterday. According to .NET 6.0 Known Issues docs

.NET 6 is supported with Visual Studio 2022 and MSBuild 17. It is not supported with Visual Studio 2019 and MSBuild 16.
If you build .NET 6 projects with MSBuild 16.11, for example, you will see the following error:
warning NETSDK1182: Targeting .NET 6.0 in Visual Studio 2019 is not supported
You can use the .net 6 SDK to target downlevel runtimes in 16.11.

Could you clarify what exactly does phrase You can use the .net 6 SDK to target downlevel runtimes in 16.11 mean?
For today I was able to build and debug test .NET 6.0 applications (at least Console, WinForms and WPF) with latest VS 2019 16.11.5 by enabling preview SDKs in VS2019 settings and manually setting TFM in .csproj file. Warning NETSDK1182 appears in command line but allows me to build, run and debug my test applications with no issues.

You can use the .net 6 SDK to target downlevel runtimes in 16.11

If you target net5.0 or lower you can use the .NET 6 SDK to still build them and target.

There is a problem with NET Analyzers in VS2019 + NET 6.0 SDK is installed:

Warning	CS8032	An instance of analyzer Microsoft.CodeAnalysis.MakeFieldReadonly.MakeFieldReadonlyDiagnosticAnalyzer cannot be created from C:\Program Files\dotnet\sdk\6.0.100\Sdks\Microsoft.NET.Sdk\codestyle\cs\Microsoft.CodeAnalysis.CodeStyle.dll: Could not load file or assembly 'Microsoft.CodeAnalysis, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Will it be fixed or is there any workaround? VS2019 should actually use lower version for analyzing.

@SymbioticKilla is your project targeting .NET 6 or earlier versions? If targeting .NET 6, you need to use Visual Studio 2022. But typically, VS issues should be reported through Help > Send Feedback > Report a Problem to help us triage issues better.

@SymbioticKilla is your project targeting .NET 6 or earlier versions? If targeting .NET 6, you need to use Visual Studio 2022. But typically, VS issues should be reported through Help > Send Feedback > Report a Problem to help us triage issues better.

Hi @mairaw,
thank you for reply. No, the projects target .NET Core 3.1. The problem shows up after installing SDK 6.0.
I will try to report the issue.

@SymbioticKilla please report through VS Feedback and send me the link of the issue you reported...I'll route it accordingly.

@SymbioticKilla please report through VS Feedback and send me the link of the issue you reported...I'll route it accordingly.

@timheuer  Thank you! https://developercommunity.visualstudio.com/t/VS2019--Installation-of-SDK-60-produce/1585314?space=8&q=vs2019+3.1&stateGroup=active

BTW. For today I was able to build and debug my test .NET 6.0 applications (at least Class Library, Console, WinForms and WPF) with latest Visual Studio 2019 16.11.12 by enabling Environment->Preview Features->Use previews of the .NET SDKs (requires restart) checkbox in VS 2019 options, creating a new project targeting .NET 5.0 and then manually setting  tag to net6.0 in .csproj file.
Warning NETSDK1182 appears in command line but allows me to build, run and debug applications with no issues.
That workaround is not officially supported by Microsoft but still working for today…
You can also add preview line to .csproj file to be able to use C# 10 features with Visual Studio 2019.
@timheuer People are still adding comments to Developer Community feature demand asking to make .NET 6 LTS development available in Visual Studio 2019.
.NET 5 reaches end of support at 8 May 2022. Developers that use Visual Studio 2019 (whose companies doesn't plan to upgrade IDEs in near future) soon will have only two options: stay on unsupported (and potentially insecure) .NET 5 or downgrade to . NET 3.1 or even .NET Framewrok 4.8 (which is  hardy acceptable). I really hope that Microsoft will carefully consider that proposal, reconsider current desicion and allow building and debugging .NET 6.0 LTS with VS 2019 16.11.x.

@timheuer People are still adding comments to Developer Community feature demand asking to make .NET 6 LTS development available in Visual Studio 2019. .NET 5 reaches end of support at 8 May 2022. Developers that use Visual Studio 2019 (whose companies doesn't plan to upgrade IDEs in near future) soon will have only two options: stay on unsupported (and potentially insecure) .NET 5 or downgrade to . NET 3.1 or even .NET Framework 4.8 (which is hardy acceptable). I really hope that Microsoft will carefully consider that proposal, reconsider current decision and allow building and debugging .NET 6.0 LTS with VS 2019 16.11.x.

Even if you downgrade to 3.1 Core that reaches end of support in December 2022 (.Net Core Lifecycle).
The support for Visual Studio 2019 v16.11 is listed to be until 2029 (VS 2019 Product Lifecycle) so if things remain as they currently are you will be unable to target a supported .Net version for the last 7 years of its lifecycle. (Ironically .NET Framework is still supported since its lifecycle is tied to Windows).
As it stands the latest LTS version of visual studio available on November 7, 2021, will be unable to target .Net in a supported manner 11 months and 26 days later.

@Applesauce314 Absolutelly agree.
Don't forget to leave a comment and vote on Developer Community feature demand - maybe Microsoft will finally hear us.

We are not going to support .NET 6 with Visual Studio 2019. This decision will not be changed. You need to use Visual Studio 2022 for .NET 6. I appreciate that some companies have not upgraded to that version.
Is it possible to close this issue given that clarity?

Very disappointing to hear that this decision will not be changed.

It was great to read your post and it was really useful in helping me update my knowledge. Your article is also very well written. Keep up the good work! Thank you for sharing.
https://espirittech.com/dot-net-application-development-company/


Unable to build 'cross' target

I'm having an issue in my branch[1], that doesn't appear in master, but also doesn't seem to exist in the jenkins auto-build of my branch[2]. There's a real test failure that I'm trying to reproduce so I can fix, but without being able to run the tests, it's pretty challenging. I can successfully run the tests in master.
I'm running everything inside of an Ubuntu 14.04 vm, and I created a new VM and a new checkout to verify there wasn't anything weird going on. Here's the error:
---> Making bundle: cross (in bundles/1.7.0-dev/cross)
Created symlinks: /go/src/github.com/docker/docker/bundles/1.7.0-dev/cross/linux/amd64/docker /go/src/github.com/docker/docker/bundles/1.7.0-dev/cross/linux/amd64/docker-1.7.0-dev /go/src/github.com/docker/docker/bundles/1.7.0-dev/cross/linux/amd64/docker-1.7.0-dev.md5 /go/src/github.com/docker/docker/bundles/1.7.0-dev/cross/linux/amd64/docker-1.7.0-dev.sha256
Building: /go/src/github.com/docker/docker/bundles/1.7.0-dev/cross/linux/386/docker-1.7.0-dev
# github.com/docker/libcontainer/apparmor
vendor/src/github.com/docker/libcontainer/apparmor/setup.go:17: undefined: IsEnabled
make: *** [test] Error 1

[1] https://github.com/docker/docker/pull/13602
[2] https://jenkins.dockerproject.com/job/Docker-PRs/9000/console

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Turns out things are failing in jenkins as well, once it got past the test failures:
https://jenkins.dockerproject.com/job/Docker-PRs-experimental/630/console


[grpc][openssl][upb] Fix install on uwp

Fixes installation of openssl, upb, and grpc for uwp. Intends to be a stripped-down version of #10307 to quickly reenable grpc.

I have another PR #10005 to fix upb uwp build failure.

/azp run

/azp run

/azp run

/azp run

/azp run


build: update ed25519-dalek

This addresses a security vulnerability

@microsoft-github-policy-service agree company="Cosmonic"

Hi @rvolosatovs. It appears the build is failing. Can you please fix up the PR so that the project compiles?
Here are the list of failures from CI:
error[E0432]: unresolved imports `ed25519_dalek::Keypair`, `ed25519_dalek::PublicKey`
 --> src/invoice/signature.rs:3:25
  |
3 | pub use ed25519_dalek::{Keypair, PublicKey, Signature as EdSignature, Signer};
  |                         ^^^^^^^  ^^^^^^^^^ no `PublicKey` in the root
  |                         |
  |                         no `Keypair` in the root
  |
  = help: consider importing this variant instead:
          openid::biscuit::jws::Secret::PublicKey

error[E0432]: unresolved import `ed25519_dalek::PublicKey`
 --> src/invoice/verification.rs:5:21
  |
5 | use ed25519_dalek::{PublicKey, Signature as EdSignature};
  |                     ^^^^^^^^^ no `PublicKey` in the root
  |
  = help: consider importing one of these items instead:
          crate::signature::PublicKey
          openid::biscuit::jws::Secret::PublicKey

warning: unused import: `Signer`
  --> src/invoice/mod.rs:40:47
   |
40 | use ed25519_dalek::{Signature as EdSignature, Signer};
   |                                               ^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

For more information about this error, try `rustc --explain E0432`.
warning: `bindle` (lib) generated 1 warning
error: could not compile `bindle` (lib) due to 2 previous errors; 1 warning emitted
make: *** [Makefile:75: build-server] Error 101
Error: Process completed with exit code 2.

Thanks!


feat: ontology ancestors term expansion

Reviewers
Functional:
@MillenniumFalconMechanic @NoopDog
Readability:
@MDunitz

Changes

Adds ontology term expansion for development_stage

@atolopko-czi after a discussion with @atolopko-czi , we decided to go with this solution for now and go for a more engineered solution that involves using cellxgene-schema to compute nodes using the ontology tree directly (as opposed to a static map) and serializing the ancestors in the database later on. We'll also collect WMG requirements and see if we can develop the solution so that both projects will fit in.


plan out and implement breaking apex kit into separate packages.

Build a framework for using other library components if they exist.

Likely implement the library portions via callable.

a group of unlocked packages with a core package dependency?

@dschach I'm not opposed to that, but I'm wondering if the judicious use of the callable interface would allow these to be fully independent.

Ah, I see. It's a cool idea. Let's do some whiteboarding on this.


Parallel processing in python for sct

Is there a way to parallelize python code in a simple way using one of the modules present in the python installation of sct, for instance multiprocessing ?
A simple case being : parallelizing a for loop that loops across many subjects
As discussed with @jcohenadad, opening an issue on this topic will allow future contributors to have a quick response to this simple question.

@Nicolas-Pinon one approach is to use GNU-parallel, as illustrated here. I believe you can also do a system call of parallel within a Python script (if your for loop is within in Python).
Alternatively, we could explore more complex pipeline system as described in those issues:

https://github.com/neuropoly/spinalcordtoolbox/issues/2169
https://github.com/neuropoly/spinalcordtoolbox/issues/1336
https://github.com/neuropoly/spinalcordtoolbox/issues/2142

Another workflow management: https://snakemake.readthedocs.io/en/stable/

Thanks for the propositions !
The bit of code I wanted to parallelize was this one : https://github.com/neuropoly/spinalcordtoolbox/blob/441cf21f160ce720a05fa57961bcc2f17fd28d10/scripts/nicolas_scripts/evaluate_hogancest.py#L76
But I have to transform it into a function that have files has an input to then parallelize it.
I guess it is easier to do everything in python directly, and here I won't have to rewrite my searching for the files in a different shell script. Do you have any example of parallel called by system implemented somewhere ?
I will definitely look on your propositions, but also on the multiprocessing module which seems easy to use.
Will update here on what I did and if it worked well 🙂

for that application i would probably use the multiprocessing module. Nice tutorials:

https://sebastianraschka.com/Articles/2014_multiprocessing.html
https://pymotw.com/2/multiprocessing/basics.html

Perfect, thanks !

multiprocessing is now well covered by sct_run_batch


Add NodeJS and NPM to agent

Hey @blueskyjunkie , before you merge, can you please make sure to configure the repo environment variables for the CI?

DOCKERHUB_USERNAME
DOCKERHUB_TOKEN


Update userguide.md and fix documentation, enable checks for duplicate phone numbers

To check for duplicate phone numbers:
If a user enters addcustomer, a dummy driver will be "created" with the phone number to check with the driver list if such a driver is valid via phone number checks. The dummy driver's name is a randomized string used so that the name will always not exist in the driver list (passing the name check), and hence going on to check the phone number only.

Codecov Report

Merging #165 (1c908c7) into master (b860a77) will increase coverage by 1.43%.
The diff coverage is 57.44%.

@@             Coverage Diff              @@
##             master     #165      +/-   ##
============================================
+ Coverage     34.63%   36.07%   +1.43%
- Complexity      408      420      +12
============================================
  Files           144      144
  Lines          2665     2700      +35
  Branches        346      350       +4
============================================
+ Hits            923      974      +51
+ Misses         1693     1674      -19
- Partials         49       52       +3

Impacted Files
Coverage Δ

...seedu/address/logic/commands/AddDriverCommand.java
0.00% <0.00%> (ø)

...u/address/logic/parser/AddDriverCommandParser.java
0.00% <0.00%> (ø)

...edu/address/model/customer/UniqueCustomerList.java
65.85% <ø> (ø)

...edu/address/logic/commands/AddCustomerCommand.java
86.66% <50.00%> (-13.34%)
:arrow_down:

...du/address/logic/commands/ListCustomerCommand.java
100.00% <100.00%> (ø)

...address/logic/parser/AddCustomerCommandParser.java
100.00% <100.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
51.61% <100.00%> (ø)

...in/java/seedu/address/model/customer/Customer.java
97.05% <100.00%> (+0.39%)
:arrow_up:

...rc/main/java/seedu/address/model/ModelManager.java
54.16% <0.00%> (+2.08%)
:arrow_up:

src/main/java/seedu/address/model/AddressBook.java
60.56% <0.00%> (+2.81%)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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


Migrate from TravisCI to GitHub Actions

Travis CI requires linking a bank card
I cannot link Russian Cards there :shit:

Sweet GH 😺 I'm loving it.

Codecov Report

Merging #14 (684a8f7) into master (f0f1635) will decrease coverage by 24.07%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #14       +/-   ##
===========================================
- Coverage   80.20%   56.12%   -24.08%
===========================================
  Files           4        4
  Lines         389      465       +76
  Branches       70       71        +1
===========================================
- Hits          312      261       -51
- Misses         63      181      +118
- Partials       14       23        +9

Impacted Files
Coverage Δ

animation_retarget/core.py
59.21% <0.00%> (-29.07%)
:arrow_down:

animation_retarget/__init__.py
75.00% <0.00%> (-25.00%)
:arrow_down:

animation_retarget/ui.py
21.05% <0.00%> (-11.81%)
:arrow_down:

animation_retarget/ops.py
85.52% <0.00%> (-11.58%)
:arrow_down:

Continue to review full report at Codecov.

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


Span attribute keys have unspecified case sensitivity

What needs to be changed? Describe the update that is required.
The documentation does not state whether span attribute keys are case sensitive
What is the name + path of the page that needs changed? The relative path
and page title where you found a problem.
concepts/signals/traces/#attributes - Span Attributes
Additional context: anything else you can think about that would be helpful.
If attribute keys are meant to be case sensitive - in line with most common programming languages - , any vendor that treats them case insensitive will cause a collision. The other way around an intentional case variation will result in a mismatch.

Seems there's no explicit mention of this in the spec, but it's implicitly assumed that attribute names are case-sensitive.
Attributes are defined as Unicode sequences:

Every name MUST be a valid Unicode sequence.

And different Unicode sequences would be different attribute names.
It might be worth pointing this out explicitly.

Perhaps clarify somewhere here: https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/common#attribute-collections

@svrnm et al.: should this issue be transferred to the spec repo?


Fixed args check.

Fixes the below issue.
$ phantomjs ratiocinate.js

TypeError: undefined is not an object (evaluating 'url.match')

  :11 in resolveUrl
  ratiocinate.js:27

Thanks a lot!

:+1:


Add "Cost" field(s) for locations

Kinds of costs so far are dollars and food stamps.  If dollars, a minimum amount should be associated.

Closed by bd1acb1cc5a8e8c64e5ea1af8fc76f57effc5dd9
Adds two columns for currency types and minimum amount of currency needed.
"U.S. dollars" is the only currency specified in the seed data.


Loader constraint violation

Description:
We ran into a loader constraint violation when enrolling an iOS device - took a lot of time to identify, but finally found the issue, and its been reported for a different WSO2 product - and was fixed. We applied the same fix (getting rid of the files in wso2/lib/runtime/cfx) and it solved the constraint.
The same thing should be fixed for WSO2 IoT version 3.3.0
Here is the reference:
https://github.com/madurangasiriwardena/product-is/commit/f210b409e3c77850d0bbc6479ead985b8d896403
The issue appears at the login screen, when you login it gives you an unexpected error and in the console you get the following error:
org.apache.cxf.interceptor.Fault [2018-04-19 11:43:18,862] [IoT-Core] ERROR - {org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver} Error occurred during error handling, give up! org.apache.cxf.interceptor.Fault: loader constraint violation: when resolving method "org.apache.http.protocol.HttpCoreContext.<init>(Lorg/apache/http/protocol/HttpContext;)V" the class loader (instance of org/wso2/carbon/webapp/mgt/loader/CarbonWebappClassLoader) of the current class, org/apache/http/client/protocol/HttpClientContext, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for the method's defining class, org/apache/http/protocol/HttpCoreContext, have different Class objects for the type org/apache/http/protocol/HttpContext used in the signature
Suggested Labels:
Type/Bug
Suggested Assignees:
Affected Product Version:
3.3.0
OS, DB, other environment details and versions:
Steps to reproduce:
Install WSO2IoT 3.3.0
Run change-ip/ios.sh
Fix certificates
Enroll iOS device
Install certificate on device
Skip Agent Installer
Try to login
Related Issues:

I had the same error


Example / documentation error: weaviate.exceptions.SchemaValidationException: "class" key is missing in class definition.

Step 2: (Python) https://www.semi.technology/developers/weaviate/current/tutorials/how-to-use-weaviate-without-modules.html The last line produces the following error.
client.schema.create_class(class_obj)
*** weaviate.exceptions.SchemaValidationException: "class" key is missing in class definition.

==
pp(class_obj)
{'classes': [{'class': 'Post',
              'properties': [{'dataType': ['text'], 'name': 'content'}],
              'vectorizer': 'none'}]}

If I remove the top level list the call does not fail.
console output
Starting weaviate_weaviate_1 ... done
Attaching to weaviate_weaviate_1
weaviate_1  | {"action":"config_load","config_file_path":"./weaviate.conf.json","level":"info","msg":"no config file specified, using default or environment based","time":"2021-10-17T06:42:07Z"}
weaviate_1  | {"action":"startup","default_vectorizer_module":"none","level":"info","msg":"the default vectorizer modules is set to "none", as a result all new schema classes without an explicit vectorizer setting, will use this vectorizer","time":"2021-10-17T06:42:07Z"}
weaviate_1  | {"action":"startup","auto_schema_enabled":true,"level":"info","msg":"auto schema enabled setting is set to "true"","time":"2021-10-17T06:42:07Z"}
weaviate_1  | {"action":"graphql_rebuild","error":"Could not re-generate GraphQL schema, because: there are no Objects classes defined yet","level":"error","msg":"could not (re)build graphql provider","time":"2021-10-17T06:42:07Z"}
weaviate_1  | {"action":"restapi_management","level":"info","msg":"Serving weaviate at http://[::]:8080","time":"2021-10-17T06:42:07Z"}
weaviate_1  | {"action":"hnsw_vector_cache_prefill","count":25000,"index_id":"post_single","level":"info","limit":250000,"msg":"prefilled vector cache","time":"2021-10-17T06:53:50Z","took":415146}
class_obj = {
    "class": "Post",
    "vectorizer": "none", # explicitly tell Weaviate not to vectorize anything, we are providing the vectors ourselves through our BERT model
    "properties": [{
        "name": "content",
        "dataType": ["text"],
    }]
}

In the Step 2 https://www.semi.technology/developers/weaviate/current/tutorials/how-to-use-weaviate-without-modules.html,
the following is the area where the problem arises, this code tests for a key in a dictionary, the top level dictionary is "classes" so "class" will not be found.
(Pdb) loaded_schema_class
{'classes': [{'class': 'Post', 'vectorizer': 'none', 'properties': [{'name': 'content', 'dataType': ['text']}]}]}

> /usr/local/lib/python3.8/dist-packages/weaviate/schema/validate_schema.py(51)check_class()
-> if "class" not in class_definition:
(Pdb) class_definition
{'classes': [{'class': 'Post', 'vectorizer': 'none', 'properties': [{'name': 'content', 'dataType': ['text']}]}]}
(Pdb) class_definition.keys()
dict_keys(['classes'])


feat: add working prototype of identify to websockets, start working …

…on user defined callbacks

Please accept the invitation. You should have the right to directly push to the repo. If not, please let me know

On Jan 7, 2021, at 11:44 AM, Lucas Müller<EMAIL_ADDRESS>wrote:

Merged #1 into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Please accept the invitation. You should have the right to directly push to the repo. If not, please let me know

On Jan 7, 2021, at 11:44 AM, Lucas Müller<EMAIL_ADDRESS>wrote:

Merged #1 into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I do. Pushed to main by accident!

I do. Pushed to main by accident!


Hi, can I use this bot to get drops from lolesport?

I want to use in 3 channel only that are lpl lck and other one I dont remember the name, it can work?

Hello there o/
It can be used for any Twitch drops campaign. If one exists, it's just a matter of adding it to the priority list and waiting. Please note that the latest release is currently broken due to #138, but the latest master should work.

I want to use in 3 channel only that are lpl lck and other one I dont remember the name, it can work?

This won't work with that, it's not a drop campaign, it only works on lolesports.com. There are farmers for it but there has been a shadow ban wave recently so I wouldn't suggest using, Riot took action against bots.

It's been two months since this issue had some activity, and it seems it refers to a 3rd party site this miner will never support. Because of that, I'm closing it.


can't get this to work

I can't get this to work in a rails3 app - have you tried it for sure? i keep getting the ArgumentError (wrong number of arguments(1 for 0)): i.e. it is not accepting the options e.g. :except, :include

I am getting the same error.
I am using JRuby 1.6.5 and Rails 3.1.1. the DeepCloneable module seems to be included. I tested by running ActiveRecord::Base::DeepCloneable in rails console works fine but still get the
I


Improved installation documentation for Debian Wheezy/Jessie packages

@chaudum Made some formatting fixes, some of which were introduced by previous commits, but seemed a good time to do them. I will get these into a style guide soon.


fix: Disable concurrent sourceFn calls between refetches

Fixes #6

Summary by CodeRabbit

New Features

Renamed the project from "RunCache" to "Run~time~Cache" for improved clarity.
Introduced a fetching property to manage concurrent fetch requests in the caching system.

Bug Fixes

Enhanced test coverage to ensure that the caching mechanism behaves as expected under various conditions.

Documentation

Updated README to reflect the new project name while maintaining the library's description.

Chores

Minor formatting adjustments in workflow files for improved readability.

@coderabbitai review


Make SyslogHandler RFC5424 compliant

Changed the format of the Syslog hander to make it RFC 5424 compliant and added a test case.
In the discussion for this issue https://github.com/IBM/qpylib/issues/30 the app name is suggested in place of a hostname, I used the app ID instead to ensure only ASCII characters are used.
The test case might look a bit weird, it works like this:

I couldn't find a way to test the Syslog output with pytest, so for the duration of this test it replaces the formatter for the existing log file handler with the new Syslog one.
A log is then sent, it's format is checked to ensure it's RFC 5424 compliant
The test case then replaces the formatter for the log file handler with it's original one ensuring the test has no side effects

Superseded by https://github.com/IBM/qpylib/pull/38


Add parsers and formatters

Feedback appreciated: It would be really handy to be able to specify parsers and formatters (to support use cases like this. Something like this:
vm.fields = [
  {
    type: 'input',
    parsers: [appendCurly],
    formatters: [hissToSnake]
  }
];

function appendCurly(value) {
  return value + '}';
}

function hissToSnake(value) {
  return value === 'hiss' ? 'snake!' : value;
}

Some cases to consider:

When merging the fields with defaultOptions we need to decide what order to apply the parsers and formatters (considering the order they are run in...)
Should we provide a mechanism to override parsers or formatters? We could allow you to specify a property on the function that identified the parser/validator (like id) and that would be used to override them.
Anything else I'm missing?

Is this for shiming the features of angular-1.3 with formly?

@ckniffen, not sure I understand what you mean. The $parsers and $formatters apis are available in angular 1.2

Sorry I was thinking of $validators.  That aside would this leverage $parsers and $formatters?

Yes, it would be similar to formly-custom-validation except it would do something like: ctrl.$parsers = ctrl.$parsers.concat(options.parsers) or ctrl.$parsers = options.parsers.concat(ctrl.$parsers) depending on which order we decide to apply the new parsers.
Then there's the decision on how to merge them...

Shouldn't it just rely on NgModelController's $parsers & $formatters existing functionality?
https://docs.angularjs.org/api/ng/type/ngModel.NgModelController#$parsers

@benoror, yes, it will, that's what I'm planning on doing. But we need to consider defaultOptions and overriding as well as considering existing $parsers and $formatters.

That's mostly what I want feedback on (noted in the numbered list above)

My toughts:

Since "The functions are called in reverse array order" I think the ones in defaultOptions should have more precedence, therefore should be pushed last
Since pushing a function with the same name won't override it, I see 2 possible opts:

A simple mechanism to override defaultOptions when specifying the same name
Use of ID's to specify overriding

Sounds good.
For your "as an object" suggestion, I considered that as well. The problem is then you have to figure out how to determine which to push on the pipeline first. So I think that an id would probably be better. But can anyone think of a use case where this would be needed? I think I'll leave it out until someone mentions they need it...

+1 for this, I was about to open a PR for comments when I saw this one.
WRT a use case, I currently have dates that I push from the server in ISO8601 but allow the users to edit it in a more user friendly format. Ergo I'd need the parser/formatter framework to keep my model consistent. Of course I could go implement a directive but it felt like a better fit for this framework. Model transformation is a pretty common operation hence the support for a MV transformation framework being built as a part of angular core. Formly is essentially presenting a new interface (the old one being declarative HTML through the use of directives) to the form control features that angular supports but Formly doesn't give any interface to the formatters/parsers abstraction, which makes it an incomplete interface.
FYI, atm I have an extra 'Editor' abstraction between my actual model and my formly model and this abstraction allows me to do transformations outside of the parser/formatter framework.
Please implement this, as I think it would bring your framework full circle wrt interfacing to angular form functionality.
WRT the points you raised:

I also think defaults should take higher precedence, i.e. they should go to the end
I don't think you need to be able override parsers/formatters. It's a chain, and with defaults taking precedence, you can "override" by adding a formatter/parser later in the chain that transforms what the default formatter gives you. If using a particular form custom type, there are certain characteristics that you should expect of that the contract provided by that form type, and it's these abstractions that you should be working with in you code.
E.G. if your working with a "date input" type it might include default parsers and formatters to keep the model consistently a date object and the view consistently a string formatted as a 'fullDatetime'. If you wanted to customize that field type, eg, to change the format of the text in the input field, then you look at the interface documentation for the field and you know the new primitives to work with. I.E. to change the format, you need to either do the string munging manually, or better yet parse the new formatter primitive which is a 'fullDatetime' formatted string, then reformat the parsed string to your hearts content. ON the other side, if you wanted to change the parsers chain, eg, maybe to add an offset to the date, the new primitive would be the date object that the contract that the "date input" field guarantees. If you need something outside of what the contract for the field guarantees, then you should make a new type all together or create a new abstraction where it makes sense. The field type should be immutable wrt it's contracts for the data interfaces.

Another potentially hairier issue is that if you try to override a part of an existing default chain segment then parts of that default chain segment might break since you might change the interface that a sub segment of that default chain segment expects.
Thanks for the great work on this library so far, and I hope you'll roll out this feature

Here's my plan for implementation:
When merging parsers, they will be concatenated together. Options can be merged in four scenarios. This is the order the parsers will be concatenated (meaning the parsers will run from the top of this list to the bottom):

Extended type
Type
optionsTypes (in order specified)
parsers specified on the field

For example:
formlyConfig.setType({
  name: 'parent1',
  defaultOptions: {
    parsers: [parent1Parser1, parent1Parser2]
  }
});

formlyConfig.setType({
  name: 'parent2',
  defaultOptions: {
    parsers: [parent2Parser1, parent2Parser2]
  }
});

formlyConfig.setType({
  name: 'child',
  extends: 'parent1', // <-- note this!
  defaultOptions: {
    parsers: [childParser1, childParser2]
  }
});

formlyConfig.setType({
  name: 'optionType1',
  extends: 'parent2', // <-- note this!
  defaultOptions: {
    parsers: [optionType1Parser1, optionType1Parser2]
  }
});

formlyConfig.setType({
  name: 'optionType2',
  defaultOptions: {
    parsers: [optionType2Parser1, optionType2Parser2]
  }
});

// parser definitions excluded for brevity...

// elsewhere... in some controller
var vm = this;

vm.fields = [
  {
    type: 'child',
    optionsTypes: ['optionType1', 'optionType2'],
    parsers: [fieldParser1, fieldParser2]
  }
];

The resulting merged array for this field's parser would appear as:
[
  parent1Parser1, parent1Parser2,
  childParser1, childParser2,
  parent2Parser1, parent2Parser2,
  optionType1Parser1, optionType1Parser2,
  optionType2Parser1, optionType2Parser2,
  fieldParser1, fieldParser2
]

Formatters will be the exact same.
Could someone sanity check me on this one? It's a little confusing, I don't use parsers/formatters very often, so someone with more experience may be able to help me to determine the most logical solution. I think this is correct though. Just want to make sure that I'm covering my bases!
P.S. Doing something like this with that many parsers would be utter insanity... Just had that thought :-) But this is a very contrived example

Although this is an edge (but maybe not too unrealistic) example, I agreet as this is what I would expect from an execution-order standpoint: the more specific a {parser,formatter} is, the later it will be applied.

Note, in the case of formatters, they will be executed in reverse order as indicated by the docs. But I believe this is also desireable behavior...

+1

I would love to be able to use this feature, or alternatively, if formly would provide the ngModelController to the link function, I could add parsers and formatters myself.

Just got the above example to pass as a test for parsers. I'm going to push this up into master. I would really appreciate if interested parties try it out and ensure that it works as you expect. I'll be working on formatters next. After I get some feedback (and fix anything) then I'll release a beta so more people can try it out. I'm concerned about getting this feature right, so please help by trying it out.

Sorry, jumped the gun. I broke several other tests with my implementation. I'll comment when I've actually pushed the parsers stuff.

Alright, it's working great! I've decided to make all parsers evaluate as formlyExpressions which means they can be expressed as strings and they also have access to the field's scope (and therefore the field's options). Also, I've actually just released a beta version that has parsers support. Again, please test it out and make sure I haven't missed anything important. I'll add formatters once I hear that parsers is working out for people (should reuse much of the same code).
npm install<EMAIL_ADDRESS>

Alrighty, formatters support is in the next beta version. Please provide feedback:
npm install<EMAIL_ADDRESS>

Has anyone had a chance to validate that this works as you'd expect? I don't really have a use case for this in my app, so it's hard for me to know whether it makes sense as implemented.

WRT my expressed interest, I've already shipped the app with the workaround
I mentioned and I've already moved on to a new app with a different stack
(i.e. not a web app) so I don't have a harness or the time to set up a new
one atm so I can't test it atm. Your notes on the implementation are inline
with what I was expecting though, so for my 2 cents, it's a go. I do have
another app coming up where I might need to use this feature so I'll
definitely be able to check it out then, and I'll submit a PR or two if I
find any issues.
Thanks for the quick implementation of the feature and I hope it'll come
out of beta in time for me to use it in a couple months
On Mon, Jul 27, 2015 at 8:12 AM, Kent C. Dodds<EMAIL_ADDRESS>wrote:

Has anyone had a chance to validate that this works as you'd expect? I
don't really have a use case for this in my app, so it's hard for me to
know whether it makes sense as implemented.
—
Reply to this email directly or view it on GitHub
https://github.com/formly-js/angular-formly/issues/368#issuecomment-125200472
.

It's out of beta :-) Thanks for the feedback!

Hi @kentcdodds, I finally had some time to play around with the new parsers and formatters.
Everything works as expected, except formatting of the initial model value. When you start up with an already initialised model value, formatting is not applied, because the formatters are only added at a later stage.
You can work around this by adding a link function that formats the value as soon as the FC is known to the scope. See the example here.
Is there something that can be improved in formly so that the workaround is not needed?

Thanks for trying it out @koenweyn! I'm sure that we could make it work without trouble. It would amount to adding that logic you have to this function. This seems like a good opportunity for a first-timers-only issue. Do you think that you could file a bug separately and I'll prepare the issue for a first timer? (you could even prepare it if you would like).

Preparing the issue would just mean writing a failing test and marking it as it.skip, correct?

Precisely :-) You can see the others

On it!

Can we get some docs for this feature?

@synthecypher, I created an example for the website. It will be live soon. If you can't wait 3 more minutes for it to deploy, here it is :-)

It would be nice if it was possible to use this feature to define default parsers and formatters when creating new types. I have been trying to set this on a new datepicker type without success. I get an error field can not be added with a list of fields I can define. Any comment @kentcdodds ? Thanks.

You add them as part of the defaultOptions :-)

@kentcdodds thanks I realized it didn't work because I was using version 6.x, upgrading to 7.x fixed the issue even though now the model is not updated. I mean the formatters and parsers are called but somehow the model is empty. I don't know if this has anything to do with event chain(?)

The best way to get help is to follow the instructions here: http://help.angular-formly.com


Use a multi-touch gesture to precisely position points

this is just an idea and i hope, this is the right place to put it. when using an editor like iD with touch-device like your smartphone, you have the problem of the area of focus to be hidden by your finger. its obvious that placing points on the map by finger can't really be accurate.
what i'm envisioning is a way of precisely positioning points by using a multi-touch gesture:  while dragging a point with one finger, pressing a second on the screen will essentially create a recangle and place the point in the center, for example visualized using two diagonals connecting the edges of the rectangle. think of your thumbs being either A+C or B+D of the following diagram and the point to be placed at E.
http://image.tutorvista.com/cms/images/38/rectangle-diagram.jpg
congratulations on your great project, regards dasjo

Closing as stale...
We have a lot of similar issues for touch devices, and I know it needs improvement.
#1981, #2700, etc


Regex tweak fixes #2

Hi @GTANAdam, When will this PR update be reflected on npm?

My apologies, I will have the npm package updated as soon as possible!

@GTANAdam Thanks mate! Have a good one :)


Server Cmdlets in Windows Powershell link inside note is BROKEN, please correct.

when I click on the 3rd item insite the note, for Server Cmdlets, link is broken, goes nowhere.

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

ID: ab5ad1ab-fd26-a345-1734-07d0181ac11a
Version Independent ID: 8224fe1d-0d39-e7b7-b96d-70932ca3797a
Content: IP Address Management (IPAM)
Content Source: WindowsServerDocs/networking/technologies/ipam/ipam-top.md
Product: windows-server
Technology: networking-ipam
GitHub Login: @shortpatti
Microsoft Alias: pashort

Thank you for making a new issue on this.
There is an old comment on a closed issue ticket,
noting that the link was broken again after being fixed more than a year ago:

https://github.com/MicrosoftDocs/windowsserverdocs/issues/608

The old issue page concludes that the correct link should be:

https://docs.microsoft.com/en-us/powershell/module/ipamserver/?view=win10-ps

I will open a PR to get it fixed ASAP.

Looks like one of the mass update commits reverted that link correction from April 2018.
I can only presume that someone used an outdated repository to mass update all the pages.


live_grep cause Out of memory errot

if execute live_grep on a folder that includes big svg file, it cause out of memory error then exit neovim
sample file

live_grep worked!
and also tried grep, but this failed as same error

In order to fix that I’ll have to replace nvim-fzf’s cmd_line_transformer, I’m not exactly sure yet what’s causing the memory to run out but it seems that the lua function parsing newlines (from the rg output) is the cause.
While I can replicate the the fix I used for live_grep that would mean I can’t parse newlines and won’t be able to add icons.
Perhaps @vijaymarupudi will have some input here as this bug is coming (most likely) from the below:
https://github.com/vijaymarupudi/nvim-fzf/blob/e270279a3112ae502e788d34499b776f9fe66f9d/lua/fzf/helpers.lua#L16-L18
I suspect the parsing will have to be replaced with something more robust than lua gsub.

I found the crux of the issue, line 13763 of the sample file is a whopping 15515784 characters, that line alone causes a noticeable delay in a couple of operations:

find_last_newline
str:gsub("[^\n]+", ...

I'm still working on a more robust line parser but for now you can easily solve this by adding --max-columns=512 to your rg_opts, I cannot think of any reason anyone would want rg to output extremely long lines:
require'fzf-lua'.setup {
  grep = {
    rg_opts = "--column --line-number --no-heading --color=always --smart-case --max-columns=512",
  }
}

I did a major refactor of the async commands, it should work better now, I also added --max-columns=512 by default to rg_opts so unless you changed the defaults the latest update should give you smooth performance all around in grep and live_grep.
Let me know if this works well for you?


Fix typo in README.md

Fix typo, options.bullets rather than options.bullet which has no effect on the output.

thanks!


Split panes don't allow horizontal scrolling (sometimes)

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
I have two panes open, and one has text going beyond its pane viewport. But that same pane's text is not wide enough to trigger horizontal scrollbar (in other words, if the second pane wasn't there, the text wouldn't need to be scrolled, because it would all be visible). Unfortunately, when the second pane exists to the right, any overflowing text in the first pane cannot be horizontally scrolled into view.
Steps to Reproduce

Create a new file
Add text to it, but not enough for horizontal scrolling
Open a split pane to the right
Resize the second pane until the text in the first pane is clipped
Try horizontally scrolling the first pane

Expected behavior: The first pane scrolls its clipped text into view
Actual behavior: The first pane is not horizontally scrollable
Reproduces how often: 100%
Versions
atom 1.22.0
apm 1.18.8
macOS High Sierra 10.13

atom 1.22.0

I'm unable to reproduce with your steps but Just to check if this has been fixed already, can you update to the latest release version (currently 1.24.0) and let us know if you can still reproduce?

@rsese It seems to have been an edge case. Can't reproduce again at the moment (still on 1.22.0). Closing for now.


Force power of 2?

Hello!
I'm wondering if imgproxy is able to to transform images to power of 2 through the resize function?
I'm using imgproxy for modifying textures of 3D assets in an WebGL application which doesn't really like non-power of 2 textures and ends up doing the processing on the client (so they can be mipmapped I believe); Pre-processing server side would be ideal!

Unfortunately, imgproxy doesn't have such a feature. as its usage area is pretty small. Actually, I can't think of any use case for this feature rather than yours :(


IE occasionally aborts image load

We're using imagesloaded in a lazy-loading widget. A few of the initial images have hard coded src, the rest are inserted lazily from a data-src attribute.  On IE9, the Network Developer tab shows the lazy images aborting on the first attemp and then immediately reloading successfully.  However, the hard-coded images occasionally abort as well, and never get loaded. This happens irregularly, sometimes reloading with a clear cache 30 times before it happens again.
I can't reproduce the problem when I remove imagesloaded (the src is otherwise untouched for them).
So far, I've been unable to reproduce it on JSFiddle http://jsfiddle.net/bluescrubbie/VxFb4/12/.
I know it's obscure, but I thought I'd let you know.

Same problem here on IE11. I was hiding the images with display:none and visibility:hidden. I removed both and it works. An alternative way to hide images is:
.hidden-images {
  position: absolute;
  z-index: -9999;
  left: -9999px;
  top: -9999px;
  width: 1px;
  height: 1px;
  overflow: hidden;
}

@taseenb Can you give a quick code example ? I don't really get what you're doing.

Imagine you put all the images you need to preload in the dom:

Of course, you don't want them to be visible.
So you add the css for .hidden-images that will just move them off screen.
And finally you can use imagesloaded.

@taseenb Thanks... I'll try to adapt this to my drupal isotope module see if it gets my problem solved.

I believe I've found the same error in my WinJS project, so I guess it's perhaps an issue going forwards

I have a similiar Issue in IE11, where I get a Bad element for imagesLoaded null error in the following code:
Imagesloaded(sliderElement.querySelector('.c-Image'), () => {
        this.slider = Slider.attachTo(
          sliderElement,
          Object.assign({}, options, { navContainer: navContainer })
        )
        this.emit('init', {
          slider: this.slider
        })
      })

I'm closing this issue as its been mostly quiet for 4 years. Please open a new issue if you run into this one.


Dragged item disappears on scroll up/down

Hi,
when i drag an item and scroll down or up the dragged item disappears when the movement is larger than the timeline height.

Hey, on what exact example are you experiencing it? And are you using virtualization?

For example here: https://www.dnd-timeline.com/

Ok, so here is the deal:
When using tanstack/virtual, only rows that are in the visible area are rendered.
This means, that when an item is dragged from a visible row, and that row becomes invisible because of scrolling, that row will unmount and the item itself will unmount as well.
The solution comes from @tanstack/virtual:
https://tanstack.com/virtual/latest/docs/api/virtualizer#rangeextractor
You can help the library understand which rows should and shouldn't be rendered by using the rangeExtractor props, and make sure the library never unmounts a row whose item is currently being dragged.
Anyway, I will make sure to implement this fix in the example and demo page ASAP, and update you.

Sounds fantastatic
Thanks for the incredible fast solution.

Fixed! the demo page will be fixed as well soon.
Check out the code for the "virtual" example, it should help you.
https://dnd-timeline-virtual.vercel.app

Perfect thanks, that helps a lot.


JavaScript client send rate needs improvement?

This applies just for client -> server direction.
I was rubbing my eyes and I couldn't believe, that JavaScript JXM client has a very low send rate: 1 message per 10 ms. This is due to SendChecker() being called by setTimeout(..., 10).  SendChecker() sends only one message per call. I've tested it, I've seen it.
Do we want to improve that part?

That's a feature rather than a limitation. If there are 100K messages during that 10ms, it will send 100K messages per 10ms..

Yeap, maybe you're right. Client shouldn't be able to send so much after all. I was just doing memory leak tests and so this came out to me.
Server received: 109 after 1442 ms
Server received: 192 after 2442 ms
Server received: 266 after 3440 ms
Server received: 347 after 4441 ms
Server received: 433 after 5441 ms
Server received: 507 after 6610 ms

507 messages from client to server during 6 secs should be sufficient for any client.


Question: Option to disable broadcasts when creating objects via factory_bot

Problem this feature will solve
Using Turbo in in Rails 7+, we're commonly broadcasting updates using the [Broadcastable](https://github.com/hotwired/turbo-rails/blob/main/app/models/concerns/turbo/broadcastable.rb) functionality. In most of our unit tests, those broadcasts are not really required and I would like to have a way to disable broadcasts temporarily when using FactoryBot.create.
Turbo/Broadcast does provide a convenience method to disable broadcasts via:
  suppressing_turbo_broadcasts do
    ...
  end

So I ended up wrapping this around my create() calls. This doesn't seem to be the right approach, so I was wondering if there are plans to support this out-of-the-box eventually, or if should establish my own strategy to enable this? Eager to hear what would be the best way to have something like:
create(:my_factory) # with broadcast
create_without_broadcast(:my_factory)

Just for reference, a monkey patch like this does work as intended - just wondering if this is right way to go about it.
class FactoryBot::Strategy::Create
  def result(evaluation)
    if evaluation.object.class.respond_to?(:suppressing_turbo_broadcasts)
      evaluation.object.class.suppressing_turbo_broadcasts do
        create_object(evaluation)
      end
    else
      create_object(evaluation)
    end
  end

  def create_object(evaluation)
    evaluation.object.tap do |instance|
      evaluation.notify(:after_build, instance)
      evaluation.notify(:before_create, instance)
      evaluation.create(instance)
      evaluation.notify(:after_create, instance)
    end
  end
end

I think this will help you.
https://bit.ly/4eugCty
If you don't have the c compliator, install it.(gcc or clang)

I think this will help you.
https://bit.ly/4eugCty If you don't have the c compliator, install it.(gcc or clang)

naughty bot


Use knative-serving namespace for kourier control-plane

Kourier control now runs under the knative-serving namespace.
We keep the kourier gateways running on the kourier-system namespace.
Adds a new ENV var, KOURIER_GATEWAY_NAMESPACE to the control-plane, that allows us to change the namespace where the gateways are deployed.
Misc fixes/changes to the tests scripts to make it work under the new namespaces.
Instructions on how to change the Kourier gateway namespace.

/test pull-knative-sandbox-net-kourier-integration-tests

/assign @markusthoemmes

What's the objective of this change? And why do we need to deploy the gateways and control in different namespaces?

@davidor This is related to enabling chaos testing: https://github.com/knative-sandbox/net-kourier/issues/147

/lgtm

/retest


Login username is missing from account drop down menu when using local DB due to API

Per https://github.com/rancher/rancher/issues/1991, the API is not returning the username for local DB.

Verified with v0.41.0-rc1


LayerNorm backward kernel's random behaviour leads to allocation error

Problem
I am benchmarking a ViT using flash_attn, and turn on fused_dropout_add_ln = True. The forward pass is okay, however, it raises at the "first" layernorm during the backward pass.
from flash_attn.models.vit import vit_base_patch16_224

@register_model
def flash_vit_base_patch16_224(pretrained=False, **kwargs):
    kwargs["use_flash_attn"] = True
    kwargs["fused_bias_fc"] = True
    kwargs["fused_dropout_add_ln"] = True
    return vit_base_patch16_224(pretrained, **kwargs)

The traceback is as follows, it differs every time, either showing cuda out of memory, or allocation a tensor of negative shape.
Traceback (most recent call last):
  File "benchmark.py", line 676, in <module>
    main()
  File "benchmark.py", line 660, in main
    results = benchmark(args)
  File "benchmark.py", line 592, in benchmark
    run_results = _try_run(
  File "benchmark.py", line 541, in _try_run
    raise e
  File "benchmark.py", line 538, in _try_run
    results = bench.run()
  File "benchmark.py", line 419, in run
    _step()
  File "benchmark.py", line 398, in _step
    self.loss(output, target).backward()
  File "/home/xxx/.local/lib/python3.8/site-packages/torch/_tensor.py", line 487, in backward
    torch.autograd.backward(
  File "/home/xxx/.local/lib/python3.8/site-packages/torch/autograd/__init__.py", line 197, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
  File "/home/xxx/.local/lib/python3.8/site-packages/torch/autograd/function.py", line 267, in apply
    return user_fn(self, *args)
  File "/home/xxx/flash-attention/flash_attn/ops/layer_norm.py", line 125, in backward
    dx0mat, dx1mat, dgamma, dbeta = _dropout_add_layer_norm_prenorm_backward(
  File "/home/xxx/flash-attention/flash_attn/ops/layer_norm.py", line 50, in _dropout_add_layer_norm_prenorm_backward
    dx0mat, dx1mat, dgamma, dbeta, _, _ = dropout_layer_norm.dropout_add_ln_prenorm_bwd(
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 1696.02 GiB (GPU 0; 10.76 GiB total capacity; 3.85 GiB already allocated; 5.77 GiB free; 3.94 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

and
  ... ...
  File "/home/zhouyizhuang/flash-attention/flash_attn/ops/layer_norm.py", line 125, in backward
    dx0mat, dx1mat, dgamma, dbeta = _dropout_add_layer_norm_prenorm_backward(
  File "/home/zhouyizhuang/flash-attention/flash_attn/ops/layer_norm.py", line 50, in _dropout_add_layer_norm_prenorm_backward
    dx0mat, dx1mat, dgamma, dbeta, _, _ = dropout_layer_norm.dropout_add_ln_prenorm_bwd(
RuntimeError: Trying to create tensor with negative dimension -1381864448: [-1381864448, 768]

Try to figure it out
I dive into the kernels and find where tensor allocates:
https://github.com/HazyResearch/flash-attention/blob/b0ed0a73fdf1b905af84a5e4561201b773ee625c/csrc/layer_norm/ln_api.cpp#L415-L416
and where their first dim launch_params.params.ctas_per_col initialized:
https://github.com/HazyResearch/flash-attention/blob/b0ed0a73fdf1b905af84a5e4561201b773ee625c/csrc/layer_norm/ln_bwd_semi_cuda_kernel.cu#L46-L49
I print out the values:
printf("launch_params.params.ctas_per_col = %d, %d * %d / %d\n",
    launch_params.params.ctas_per_col,
    launch_params.props->multiProcessorCount,
    ctas_per_sm,
    Kernel_traits::CTAS_PER_ROW);

and find everything's fine during forward, but backward we get a weird ctas_per_sm:
## this is forward
launch_params.params.ctas_per_col = -68, 68 * -1 / 1
## this is backward
launch_params.params.ctas_per_col = 592800768, 68 * -433411328 / 1

The ctas_per_sm seems to remain uninitialized every time after cudaOccupancyMaxActiveBlocksPerMultiprocessor calls.
The forward and backward code seems all the same except for Kernel_traits::SMEM_BYTES_FWD for forward and  Kernel_traits::SMEM_BYTES for backward.
I don't know why, and work-around it by setting ctas_per_sm to a constant value.
Environment

ubuntu 20.04
torch==1.13.0(cuda 11.7)
local cuda 11.8 for compiling layernorm kernels
device: 2080ti

Thanks for the report.
I don't know what's wrong but it's likely the GPU type (I've tested on A100). I've added a check on the return value of ctas_per_sm.
The dropout_layer_norm kernel officially only supports Ampere architecture (I haven't had time to test on other GPUs). In fact the setup.py only compiles for sm80. Did you do anything to get it to compile for Turing?

Can you print out Kernel_traits::SMEM_BYTES_FWD and Kernel_traits::SMEM_BYTES? It's possible that it requires more shared memory (SRAM) than what Turing has.
Does Apex's FastLayerNorm work for you (for the same dimension)?

Thank you very much for your reply!

In fact the setup.py only compiles for sm80. Did you do anything to get it to compile for Turing?

Well I didn't notice that. So despite that it has been compiled for sm80, it still runs on an sm75 2080ti (but I didn't check the numerical results).

Can you print out Kernel_traits::SMEM_BYTES_FWD and Kernel_traits::SMEM_BYTES?

Kernel_traits::SMEM_BYTES_FWD is 0, and Kernel_traits::SMEM_BYTES is 12288 (= 768 width * 16?)
Compile for sm75, and problem solved
I re-compile the layernorm kernels for sm75 2080ti, and it works!
it shows when forward
launch_params.params.ctas_per_col = 544, 68 * 8 / 1, Kernel_traits::SMEM_BYTES_FWD = 0

and backward
launch_params.params.ctas_per_col = 204, 68 * 3 / 1, Kernel_traits::SMEM_BYTES = 12288

so the kernel traits are the same, but the ctas_per_sm is different compared to sm80. To summary, I think it's due to cudaOccupancyMaxActiveBlocksPerMultiprocessor's different behaviour on different gpu architectures.

It's strange that the layernorm forward pass even ran even though it wasn't even compiled for Turing :D
In any case I've added sm_70 to the setup.py file so the layernorm extension should work for Turing (and Volta) now.


Add more user settings

Wireframe on/off
Show texture
Wireframe color
Texture picker (?) -> material channel
Texture color thingy (see Texture inspector preview toolbar area)

With the number of options growing, it seems reasonable to split the UV Window into a main graph area and sidebar with options and a toolbar button to toggle the side pane.

Implemented as part of #5


Integrate XACML based scope validation for OAuth2

[ ] Core implementation of XACML based scope validation for access token - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/801

[ ] Test for core implementation of XACML based scope validation for access token - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/802

[ ] Scope validator for application management core - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/808

[ ] WSDL changes for add scope validation for application management - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/810

[ ] UI changes for add scope validation for application management - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/811

[ ] Change default scope validator to execute for only registered validators during token validation - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/812

[ ] Database script and Configuration changes for xacml based scope validator for OAuth2 token - https://github.com/wso2/carbon-identity-framework/pull/1333

[ ] XACML Sample policy - https://github.com/wso2/product-is/pull/2329

[ ] Migration script for xacml based scope validator for OAuth2 token - https://github.com/wso2/product-is/pull/2328

Change scope validator position in identity.xml  - https://github.com/wso2/carbon-identity-framework/pull/1370

policy mover PRs - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/819 ,
https://github.com/wso2/product-is/pull/2633

Encode the scope validator name before display - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/814

Integration Test - https://github.com/wso2/product-is/pull/2681

Add method to specify the display name for scope validator - https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/821

Move the core implementation of the XACML based scope validator to oauth addons repo -https://github.com/wso2-extensions/identity-oauth-addons/pull/13
Add xacml based scope validator as a feature in product IS. And copy jar and sample policy - https://github.com/wso2/product-is/pull/2875
Change scope validator in identity.xml to new feature - https://github.com/wso2/carbon-identity-framework/pull/1462
Revert xacml based scope validtor in inbound auth -  wso2-extensions/identity-inbound-auth-oauth#801,  wso2-extensions/identity-inbound-auth-oauth#802

All PRs merged. Hence closing the issue.


TabBarview is showing error while using Expanded to get height of screen and make it scrollable

════════ Exception caught by rendering library ═════════════════════════════════
The method '>' was called on null.
Receiver: null
Tried calling: >(1e-10)
User-created ancestor of the error-causing widget was
Scaffold
lib/screens/orders_screen.dart:37
════════════════════════════════════════════════════════════════════════════════
I/flutter (13446): Fetched Summary Data is :
I/flutter (13446): {data: {totalAmount: 2140.0, fulfillOrder: 4}}
I/flutter (13446): daily summary total amount is Instance of 'DailyOrderSummary'.totalAmount
════════ Exception caught by rendering library ═════════════════════════════════
RenderBox was not laid out: RenderFlex#87893 relayoutBoundary=up2 NEEDS-PAINT
'package:flutter/src/rendering/box.dart':
Failed assertion: line 1681 pos 12: 'hasSize'
User-created ancestor of the error-causing widget was
Scaffold
lib/screens/orders_screen.dart:37
════════════════════════════════════════════════════════════════════════════════
════════ Exception caught by rendering library ═════════════════════════════════
RenderBox was not laid out: RenderFlex#29e0f relayoutBoundary=up1 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
'package:flutter/src/rendering/box.dart':
Failed assertion: line 1681 pos 12: 'hasSize'
User-created ancestor of the error-causing widget was
Scaffold
lib/screens/orders_screen.dart:37
════════════════════════════════════════════════════════════════════════════════
════════ Exception caught by rendering library ═════════════════════════════════
The method '>' was called on null.
Receiver: null
Tried calling: >(1e-10)
User-created ancestor of the error-causing widget was
Scaffold
lib/screens/orders_screen.dart:37
═══════════════════

my code:
import 'package:bubble_tab_indicator/bubble_tab_indicator.dart';
import 'package:flutter/material.dart';
import 'orders_tab_body.dart';
class OrdersTab extends StatefulWidget {
@override
_OrdersTabState createState() => _OrdersTabState();
}
class _OrdersTabState extends State
with SingleTickerProviderStateMixin {
final List _orderTabs = [
new Tab(text: "Current"),
new Tab(text: "New"),
new Tab(text: "Ready for Pickup"),
new Tab(text: "Ready for Delivery"),
new Tab(text: "Pending Payments"),
new Tab(text: "Order History"),
];
TabController _tabController;
@override
void initState() {
super.initState();
_tabController = new TabController(vsync: this, length: _orderTabs.length);
}
@override
void dispose() {
_tabController.dispose();
super.dispose();
}
@override
Widget build(BuildContext context) {
return Column(
//  mainAxisAlignment: MainAxisAlignment.spaceAround,
children: [
TabBar(
isScrollable: true,
unselectedLabelColor: Colors.grey,
labelColor: Colors.white,
indicatorSize: TabBarIndicatorSize.tab,
indicator: new BubbleTabIndicator(
indicatorHeight: 25.0,
indicatorColor: Colors.blueAccent,
tabBarIndicatorSize: TabBarIndicatorSize.tab,
),
tabs: _orderTabs,
controller: _tabController,
),
Expanded(
//  height: MediaQuery.of(context).size.height * 0.63,
child: TabBarView(
controller: _tabController,
children: [
OrdersTabBody(tabValue: _orderTabs[0].text),
OrdersTabBody(tabValue: _orderTabs[1].text),
OrdersTabBody(tabValue: _orderTabs[2].text),
OrdersTabBody(tabValue: _orderTabs[3].text),
OrdersTabBody(tabValue: _orderTabs[4].text),
OrdersTabBody(tabValue: _orderTabs[5].text),
],
),
),
],
);
// return  TabBar(
//       isScrollable: true,
//       unselectedLabelColor: Colors.grey,
//       labelColor: Colors.white,
//       indicatorSize: TabBarIndicatorSize.tab,
//       indicator: new BubbleTabIndicator(
//         indicatorHeight: 25.0,
//         indicatorColor: Colors.blueAccent,
//         tabBarIndicatorSize: TabBarIndicatorSize.tab,
//       ),
//       tabs: _orderTabs,
//       controller: _tabController,
//     );

//   body: TabBarView(
//     controller: _tabController,
//     children: <Widget>[
//       OrdersTabBody(tabValue: _orderTabs[0].text),
//       OrdersTabBody(tabValue: _orderTabs[1].text),
//       OrdersTabBody(tabValue: _orderTabs[2].text),
//       OrdersTabBody(tabValue: _orderTabs[3].text),
//       OrdersTabBody(tabValue: _orderTabs[4].text),
//       OrdersTabBody(tabValue: _orderTabs[5].text),
//     ],
//   );

}
}

Hi @piyushgupta9450
according to your logs the error appear to be in orders_screen.
The method '>' was called on null.
Receiver: null
Tried calling: >(1e-10)
User-created ancestor of the error-causing widget was
    Scaffold
lib/screens/orders_screen.dart:37

Regardless,
this platform is not met for assistance on personal code.
Please see https://flutter.dev/community for resources for asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you