Bitcode support

Changes in the build script. Added support for the bitcode for all the libraries.
Readme has been changed to reflect the changes in the build script.
Libraries binaries are now contain bitcode.

Looks good to me, but all of the builds on Travis failed due to linking errors. Can you investigate why enabling the bitcode embedding results in all of the "duplicate symbol" errors? This link seems to be related and might help find the answer: http://stackoverflow.com/questions/31566867/ios-fat-binaries-should-every-arch-include-bitcode

@kevincon, I believe that's due to unsupported '-fembed-bitcode' option in Xcode 5. As soon as we change travis settings to use Xcode 6 for the build, everything should be ok. At least with my local Xcode 6 I don't have such issues, but have them with Xcode 5. So let's wait till the final release of Xcode 6 and than try to change travis settings.

I've also added a note that xCode 7 is required to build the library from this commit.

Sounds good, but let's wait to land these changes until Travis supports Xcode 7 so we don't have a broken build. Here's the issue on Travis we can follow: https://github.com/travis-ci/travis-ci/issues/4055

I've rebased the branch onto Makefile branch.
I've also modified Travis config file so it uses xCode 7, but there are still build errors.
I'll take a look on them soon.

Ok. I could succeed with Travis in this branch, but it seems there is something wrong with coveralls. It seems it cannot proceed due to some reason. @kevincon,  could you take a look and figure out why coveralls hang?
So, a few things should be mentioned in this branch.

xctool (which is used by default as a compiler in Travis CI) doesn't support Xcode 7 beta 6 and higher. Refer the issue for details: https://github.com/facebook/xctool/issues/528. So I've changed the travis configuration to use xcodebuild. I'm planning to change the configuration back to xctool right after the issue has been fixed. I'll create a ticket for that soon.
Due to the first, the build is run serially, since there is no more build matrix and we use just a build script.
Due to the second, I had to disable building libraries during Travis CI build, since every dependent library compilation takes about 40 minutes and there is a time limit for the build in the Travis CI, which is 50 minutes only.
So far xcode7 build environment doesn't contain iPhone simulator 7.1 and 8.1, only 9.0. So I've commented them so far, until Travis CI team add them into xcode7 environment. They told me the ticket is already created for that and will be finished very soon.

It seems that Xcode 7 is released on September 16 with iOS 9. So let's have everything ready for it here.

I tried restarting the build on Travis, but even after it succeeded again it still did not report coverage info to Coveralls. I'm not sure why that's happening, because the last part of the build log on Travis shows that it was able to find the coverage files, parse them for coverage percentages, and submit them to Coveralls.
It might just be an issue on Coveralls' end, but maybe we should switch to a different coverage reporting script? I found a few other candidates that look like they have nice integration with XCode projects, Travis, and Coveralls:

xcode-coveralls: https://github.com/macmade/xcode-coveralls
slather: https://github.com/venmo/slather


Denial of service with malformed file

When running the following code with the latest git version of pygments on the attached input results of in 100% CPU consumption for an arbitrary long time:
import sys

import pygments
import pygments.formatters
import pygments.lexers

with open(sys.argv[1], 'rb') as f:
    data = f.read()
    lexer = pygments.lexers.guess_lexer(str(data))
    pygments.highlight(str(data), lexer, pygments.formatters.HtmlFormatter())

timeout-9a00111e78b5cd0979a370fc9a5cd22e39a249e4.txt

The sample input file causes Pygments to guess that this should be parsed by the SspLexer.
The SspLexer is a delegating lexer that uses the following lexers: XmlLexer (which does not choke on the input file) and JspRootLexer. JspRootLexer includes regex patterns from the JavaLexer (which also does not choke on the input file). However, when the JspRootLexer hands things off to the JavaLexer it appears that there is a mis-match in the quotes, and the JavaLexer is encountering catastrophic backtracking in the string literal regex.
I used this code to determine where in the file the JspRootLexer is choking up, and it's happening at line 115, right after these tokens:
(3690, Token.Name, 'o')
(3691, Token.Literal.String, '"; print $$0 "')
(3705, Token.Name, 'c')

The code I used was:
import pygments.lexers.templates

with open('timeout-9a00111e78b5cd0979a370fc9a5cd22e39a249e4.txt', 'rb') as f:
    data = f.read()

lexer = pygments.lexers.templates.JspRootLexer()

for i, t, v in lexer.get_tokens_unprocessed(str(data)):
    print((i, t, v))
    if i == 3705:
        breakpoint()

After stepping forward in the code for a while, I discovered that everything was hanging at pygments.lexer.RegexLexer.get_tokens_unprocessed():625. I added a print() statement just before that line and re-ran the code above, which helped me identify that it's the regex for string literals in the JavaLexer.
I've exploded that regex from a single-line regex to a new regex state named "string", which resolves the catastrophic backtracking and allows the code provided by the reporter to run without hanging.
I'm working on unit test for this and then I can submit a PR to close this issue.

Thanks a lot for the fix!


Support multi-line arguments

Supplying the entire argument list on a single line can be cumbersome and make the workflow file difficult to read. A relatively simple solution would be to allow arguments to be supplied as a multi-line input. So instead of:
 - name: Build
      uses: gradle/gradle-build-action@v2
      with:
        arguments: build --info -PsomeService.prod.apiKey=${{ secrets.SOME_SERVICE_API_KEY }} -PsomeService.prod.secret=${{ secrets.SOME_SERVICE_API_SECRET }} -PsomeService.prod.projectId=${{ secrets.SOME_SERVICE_PROJECT_ID }}

one could use:
- name: Build
      uses: gradle/gradle-build-action@v2
      with:
        arguments: |
             build --info
             -PsomeService.prod.apiKey=${{ secrets.SOME_SERVICE_API_KEY }}
             -PsomeService.prod.secret=${{ secrets.SOME_SERVICE_API_SECRET }}
             -PsomeService.prod.projectId=${{ secrets.SOME_SERVICE_PROJECT_ID }}

I think this option is preferable to a structured input parameter for properties since it keeps the action API simpler and is likely easier for new users to learn and understand.
Thanks @vlsi for the inspiration: https://github.com/gradle/gradle-build-action/issues/18#issuecomment-670580368.

By the way, https://github.com/burrunan/gradle-cache-action/blob/main/README.md#usage supports multiline arguments and properties


(3.0.50) inconsistent selector selection on double-click

I used double-click on keyword in both method list browser and project browser ... the project browser does it right, includinge the $: in the selection ... the method list browser does it *wrong:

I prefer the right way, but it is probably more important to be consistent:)

double-click in debugger is also wrong:

Note that when a frame is selected the right selection is made ... only double-click is letting us down:)

This is annoying. I was a little confused by what Dale meant: this is a double click on any word within the text of a method. When you double click it selects "the whole word".  Should the selection include a trailing colon : or not?   Dale is a colon-includer and I would agree.
This means fixing the way double click selects in the method list and the debugger.
Alternately, a colon-excluder would fix the project browser.

No colon left behind! (colons now included in debugger double click) ...  Fixed in 3.0.75.


Central crashing on baremetal startup

Hi,
I have tried installing Central with the latest 4.0.2 helm chart.
provided custom options
exposure:
nodeport:
enabled: true
port: 30069
db:
persistence:
persistentVolumeClaim:
storageClass: manual

Hi @c0ldb00t3r and thanks for the report!
Could you tell us a bit more about your storage configuration?
My first hunch would be a permission issue, as the write fails.

@Maddosaurus I think the below screenshot would provide a better idea about storage

@c0ldb00t3r have you been able to solve the issue? If yes, could you let us know how did you solve the problem?

I did not find any solution. Neither are any installation guides for other clusters. I have tried in total 8 clusters, and faced the same problem everywhere. Thanks, I really can't spend more time on this


"Select [column] possible values" takes too much time to execute in some cases

Infos:

Operating system (distribution) and version: Windows 10 Pro 1903
DBeaver version: 6.2.5
Additional extensions: Git and Office
Database name and version: Oracle Database 11g Enterprise Edition Release <IP_ADDRESS>.0 - 64bit Production (but I think it happens in other databases too, such as SQL Server)
Driver name: oracle.jdbc.OracleDriver (ojdbc6)

Problem:
In some cases, specially in production connections (it is slower), when I execute a simple query, it takes too much time to execute, because it waits several "select [column] possible values" background tasks. Some times it takes like 2 minutes to execute a simple select. If I invalidate the connection I re-execute the query, it executes very fast.
If I close the connection, or restart DBeaver and execute the same select in the same database, the problem does not happen. I did not note a pattern.
Is there some way to priorize the user command uppon the "select possible values" task?

is it still actual?

I believe it happens if you click on the filter icon on a column. Until the distinct query on that column is finished, you cannot load any other data

The same issue with v22.3.5 MacOS / Mysql. It happens even when I change table properties.
My workaround is to open background tasks and kill it.


chore: add release checklist template for 2.x

Issue
With the last few releases we forgot to update version numbers in the codebase.
Solution
Introduce a release checklist for 2.x so we do not forget these steps.
Impact
Less confusion after releases.
Usage Changes
Considerations

Testing

I think the Timber::$version can also be handled by Release Please, we just need to mark it with comment tags:
// x-release-please-start-version
public static $version = '2.0.0';
// x-release-please-end-version
```


Don't install typing backport on recent Python versions

I run in the same issue as https://github.com/python/typing/issues/573
The proposed solution  is to skip the installation of the typing library for recent python versions

Thanks!

Any ETA on getting this pushed out to pypi?


Automatic build system

At some point the project will be mature enough to be used as standalone app. It would be cool to have automatic build & release on GitHub so that people can easily download the executable version. It should probably not be done continuously though. A release could be created when a certain branch with a release number is created or something like that.

Thanks for the PR @Drathal!
I fixed the download URL with https://github.com/MrEliptik/godot_twitch_games/commit/3aec57f26ac9457d5dcef4b8ac906da8f8ccd0d6
I'm not closing it yet as there's an error during the import apparently.

Closing for now as it works. Making it work without committing the .godot folder would be the best though.


Technical support details

Issue
Not clear who to direct questions on issues with Model Framework
Solution
Clear guidelines, for example: discord channel or link with the correspondence form
Feedback
NZ: this will be the DISCORD channel and the engineering/crypto/modeller team will have a HEAD role that handles announcements and there will be a SUPPORT role as well

@MattCMK We probably want a page in the developer-docs site (this repo) for Support that lists the discord channel, opening issues on github etc. for this repo and the model-py repo.


Launching vanilla from a .py script

Hi there!
I installed vanilla on a py3.7 environment and I would like to use it outside RF or Drawbot. If I try to launch the ButtonDemo script
from vanilla import *

class ButtonDemo(object):

     def __init__(self):
         self.w = Window((100, 40))
         self.w.button = Button((10, 10, -10, 20), "A Button",
                            callback=self.buttonCallback)
         self.w.open()

     def buttonCallback(self, sender):
         print("button hit!")

ButtonDemo()

the script runs smoothly but no window appears.
Am I missing something? Do you have any advice?
Cheers

I solved using a patched version of the SimpleApp example
from __future__ import print_function
import sys
from PyObjCTools import AppHelper
import vanilla

class SimpleAppWindow(object):

    def __init__(self):
        self.w = vanilla.Window((250, 120), "Simple App Window", closable=False)
        self.w.text = vanilla.TextBox((10, 10, -10, 70), "This is a simple window. It doesn't do much. You see that button? Press it and some text will be printed in Console.app.")
        self.w.button = vanilla.Button((10, 90, -10, 20), "Press me", callback=self.buttonCallback)
        self.w.open()

    def buttonCallback(self, sender):
        print("You pressed the button!")
        sys.stdout.flush()

SimpleAppWindow()

if __name__ == "__main__":
    AppHelper.runEventLoop()

There was this thing where you could run a vanilla window without an app container, but I can't find it right now.

import vanilla

class MyController(object):

    def __init__(self):
        self.w = vanilla.Window((400, 400))
        self.w.open()

from vanilla.test.testTools import executeVanillaTest
executeVanillaTest(MyController)

see https://github.com/robotools/vanilla/blob/master/Lib/vanilla/test/testTools.py#L12

<3
thank you!

Sorry to comment on a closed issue 😅
executeVanillaTest() works great until you have an EditText field in the window.
All text input by the user is grabbed by the terminal window rather than the vanilla mini app.
import vanilla
from vanilla.test.testTools import executeVanillaTest

class TestWindow():
    def __init__(self):
        self.w = vanilla.Window((400, 500), "hello")
        self.w.button = vanilla.Button((20, 20, -20, 20), "boom")
        self.w.text = vanilla.EditText((20, 60, -20, 20))
        self.w.open()
        self.w.select()

if __name__ == "__main__":
    executeVanillaTest(TestWindow)

I imagine executeVanillaTest was never meant to be used for something like that.
Do you think it would that's something remotely possible? I guess terminal.app would not be that happy with giving away its user inputs...

executeVanillaTest() works great until you have an EditText field in the window.

Hm, works fine for me on 10.15.7.

Does not work for me on 10.15.7 – all text input appears in the Terminal window.

Oh that's interesting! Thank you for testing it out.
I am on 10.14.6, with terminal.app on zsh and all text input are registered by the terminal window, just like Frank said.

fine on 10.13 (both in terminal as iTerm)
strange: Just and Frank tested on the same OS but with different results. Are you both using the same latest version of vanilla? (I know vanilla does not have a decent version number)
The window gets full focus: the toolbar is not grayed out, top right buttons are not grayed out, focus rings around the EditText control?

I am using Terminal, and have tried with both bash and zsh: same results. I am using Python 3.7, latest vanilla, latest pyobjc, in a virtual environment.

@frankrolf and @mathieureguer, which version of Python do you use, and where is it from? (Eg. python.org, homebrew, etc.)

@joachimvu suggested that pyenv might be the culprit.
I use python 3.7.4, installed via pyenv. I think @frankrolf does use pyenv as well.
Deactivating pyenv and switching to a python installed from python.org makes the problem disappear. 🤯
I have no idea what pyenv is doing to mess with keyboard input, whether its a feature or a bug or if that's just a faulty configuration on my part…
The good news is that executeVanillaTest() works perfectly fine once your outside of pyenv!

Thanks, that's good to know.
FWIW: I strictly use python.org installers myself, and recommend that to anyone willing to listen. Homebrew, Anaconda, pyenv: I'm not getting near that stuff.

I am starting to understand why 😋

Thanks, good to know! I use pyenv indeed and found it to be very useful for my purposes.
I am curious why this happens though (Mathieu you seem to know)?

Oh sorry, I meant that I was starting to understand why Just was using only python.org installers.
I am absolutely not starting to understand why pyenv python behaves that way. 😑

I've run into similar problems with conda and pyenv and I think some other virtual envs. It's always something with GUI. Since I discovered the problem years ago I know to just switch to a regular Python venv. Most recently it happened with wxpython where it failed in conda, but everything is perfect with built in venv.

@joachimvu suggested that pyenv might be the culprit.
I use python 3.7.4, installed via pyenv. I think @frankrolf does use pyenv as well.
Deactivating pyenv and switching to a python installed from python.org makes the problem disappear. 🤯
I have no idea what pyenv is doing to mess with keyboard input, whether its a feature or a bug or if that's just a faulty configuration on my part…
The good news is that executeVanillaTest() works perfectly fine once your outside of pyenv!

I ran into this issue with pyenv and drawbot. I still havent figured out since what it is with pyenv python versions that cause problems. I’m really fond of pyenv’s way of managing python versions and activating environments when cding into projects, but it is unreliable, although I never had any issues outside of these two (drawbot and vanilla) type design-specific libs.

Oh, I just noticed something.
Without pyenv, when the executeVanillaTest()is launched from the terminal, clicking on the vanilla window will actually switch the top menu bar to the little autonomous python app created by the script.
With pyenv, the window launches, but the terminal.app menu bar always stays on. You are never really in the autonomous python app. I guess that is why the terminal windows catches all key inputs.

With pyenv, the window launches, but the terminal.app menu bar always stays on. You are never really in the autonomous python app

Yes, that is indeed the problem. For this UI stuff to work, it needs to be run from an app bundle, and pyenv (and Conda, maybe also Brew) don't do that.


Add support for vector images to the clamp image filter

Compatibility note: this changes the default output type from
defaulting to float32 to matching the input type.

topic merged to next.


[Documentation] Preview EventHub showing track 1 docs

This URL: https://docs.microsoft.com/en-us/javascript/api/@azure/event-hubs/?view=azure-node-preview
Should be showing preview eventhubs. Currently it's from GA track 1 eventhub.

Super confused here. Verified that the preview build is definitely targeting the correct package.

Still digging.


Extension says I'm not signed in when cloning using Gitlab.com

Clone a Github project, open the Github pannel, everything work.
Clone a Gitlab project, open the Github pannel, it says I'm not sigged in.
This is confusing as I am siggned-in. It's simply that this project is unsupported.
The message error message should reflect that and say something like "Unsupported Git project. This is not a Github project."

@mrleblanc101 I'm sad to say that I don't know of a way to tell the difference between a GitHub Enterprise project and a non-GitHub (for example, Gitlab) project. A GitHub Enterprise server can have any URL and might not respond to unauthenticated requests in a known way.
There are a few known urls that we can check for here though, like bitbucket.org and gitlab.com. For those we can know that they're not GitHub Enterprise and avoid showing the sign in.

Yes, I think that would be a good start. Maybe don't match "gitlab.com" and match any URL that contain Gitlab.
For exemple, the company I work for has a self-hosted Gitlab which is gitlab.company-name.com.

Theoretically, gitlab.company-name.com could be a GitHub Enterprise server.
Instead of showing the sign in buttons we'll show our standard message about how none of the remotes for the repo are GitHub remotes. There's still room for improvement on the message there.

The message now says: No remote matches the current setting


feat: imask component

Feature: Masking Input

if we want to be formatted like a currency (10000 -> 10,000) we enable the thousandsSeparator  boolean flag
max and min props for max and min value, note the product likes the user to be able to enter higher amount and warn him with error message if its above/below the max/min. but if we want to we have this feature.
3.decimals is how many decimals we allow the user to enter. if this value gets changed to a lower amount, the component is reactive and will remove the decimals after the precision point.
4.autofix is for when the user enters an amount higher that allowed, and the component automatically sets to the highest allowed (or lowest).

Summary by CodeRabbit

New Features

Enhanced NumInput component with input masking for improved user input experience. Adjustments include autofixing, thousands separator, decimal handling, and max/min value constraints.

Can this component handle tens multipliers rounding as well? I.e if we enter 101 and the tickSize is 100 it should round down to 100, similar with lower than 1 numbers like 0.1, if we enter 0.02 it should round to 0.1

we can do this with and intermediate computed  getter/setter i think, will experiment and keep you updated


Add company name to live observation confirmation alert message

This PR adds company name to live observation alert.
MOB-2739

@rasmustautsglia - In custom locales project there has been just changes implemented for how company name will be used. In case it has passed you by then please check with the custom locales gentlemen how the changes would influence this PR.

@mikktammeglia Gerson notified me immediately after merging his PR to development, after which I rebased LO branch on development and made my modifications to it :)

Added unit test da1432f

!squash


Fix namespace instructions in README.md

The instructions in README.md were missing the namespaces part of the command.

Merged! Thanks :)


RFC: Built-in Python Code runner

Python is in the fortunate position that it is available in the browser thanks to https://github.com/pyscript/pyscript.
I am open to adding it as a custom coderunner to slidev, if the idea is greenlit :)

Thank you for bringing this up. That's the reason we bring up the custom code runner setup - which would allow you to provide your own runner. We don't want to introduce too many dependencies for a feature that the majority of the Slidev users might not need. In addition, even for Python users, the behaviour misalignment between cpython and pyscript might not be desired - I think it's better to have users to implement that. If needed, an community maintained addon or so might make it easier.


Creating World Anchor application

Hi guys,
First, congrats for amazing project, the Mixed Reality Toolkit for Unity o/
I'm building a project with World Anchor but I can't find a tutorial with makes what I want.
I want build an application exactly like this: https://www.youtube.com/watch?v=a0-9KosgAXY&t=1s
I'm using the latest version of Unity and Visual Studio.
Someone can help me?
How I can build it?

Hi, it's been awhile but this was one of the first things I tried when developing a Hololens app.  That was about 6 months ago, so the new MRTK may have update the way they handle it.  The way I was able to accomplish was something like this.

Add an empty game object and attache the WorldAnchorManager.cs script to that.
Add your 3D object (cube) that you want to move.  Make sure it has some kind of collider attached (like a box collider) so that it is intractable.
Add a new script to this object called "AnchorObject.cs"  This script will need a string field to hold a unique ID which you can set at any time.  This unique string is what the WorldAnchorManager will use to find and retrieve your object between app cycles, so you don't want to change it during runtime.  That AnchorObject.cs will look something like this:

`using System;
using UnityEngine;
using HoloToolkit.Unity.InputModule;
///
/// Simple Script that allows a World Anchor to be:
///     1. Atached at Start()
///     2. Detached at OnManipulationStarted()
///     3. Attached again at OnManipulationCompleted()
/// Means that the object will save it's position between app cycles
///
public class AnchorObject : MonoBehaviour,
IManipulationHandler,
IFocusable
{
public string AnchorName = 123456789;
public bool Undo = false;
    private Vector3 SavedPosition;
    private Quaternion SavedRotation;
    private Vector3 OldPosition;
    private Quaternion OldRotation;

    void Start()
    {
        OldPosition = SavedPosition = this.gameObject.transform.position;
        OldRotation = SavedRotation = this.gameObject.transform.rotation;

        WorldAnchorManager.Instance.AttachAnchor(this.gameObject, AnchorName);
        Debug.Log("Anchor attached for: " + this.gameObject.name + " - AnchorID: " + AnchorName);
    }

    void Update()
    {
        if(Undo)
        {
            WorldAnchorManager.Instance.RemoveAnchor(this.gameObject);
            RestoreBackupAnchor();
            Undo = false;
        }
    }

    public void RestoreBackupAnchor()
    {
        this.gameObject.transform.position = OldPosition;
        this.gameObject.transform.rotation = OldRotation;
        WorldAnchorManager.Instance.AttachAnchor(this.gameObject, AnchorName);
    }

    public void OnFocusEnter()
    {
    }

    public void OnFocusExit()
    {
        SavedPosition = this.gameObject.transform.position;
        SavedRotation = this.gameObject.transform.rotation;
    }

    public void AttachAnchor()
    {
        OldPosition = SavedPosition = this.gameObject.transform.position;
        OldRotation = SavedRotation = this.gameObject.transform.rotation;

        WorldAnchorManager.Instance.AttachAnchor(this.gameObject, AnchorName);
        Debug.Log("Anchor attached for: " + this.gameObject.name + " - AnchorID: " + AnchorName);
    }

    public void UpdatePositionAndRemoveAnchor()
    {
        OldPosition = SavedPosition = this.gameObject.transform.position;
        OldRotation = SavedRotation = this.gameObject.transform.rotation;
        WorldAnchorManager.Instance.RemoveAnchor(this.gameObject);
    }

    public void OnManipulationStarted(ManipulationEventData eventData)
    {
        //Debug.LogFormat("OnManipulationStarted\r\nSource: {0}  SourceId: {1}\r\nCumulativeDelta: {2} {3} {4}",
        //    eventData.InputSource,
        //    eventData.SourceId,
        //    eventData.CumulativeDelta.x,
        //    eventData.CumulativeDelta.y,
        //    eventData.CumulativeDelta.z);

        WorldAnchorManager.Instance.RemoveAnchor(this.gameObject);
        Debug.Log("OnManipulationStarted - Anchor Removed");
        OldPosition = SavedPosition;
        OldRotation = SavedRotation;
    }

    public void OnManipulationUpdated(ManipulationEventData eventData)
    {
        //if (LogGesturesUpdateEvents)
        //{
        //    Debug.LogFormat("OnManipulationUpdated\r\nSource: {0}  SourceId: {1}\r\nCumulativeDelta: {2} {3} {4}",
        //        eventData.InputSource,
        //        eventData.SourceId,
        //        eventData.CumulativeDelta.x,
        //        eventData.CumulativeDelta.y,
        //        eventData.CumulativeDelta.z);
        //}
    }

    public void OnManipulationCompleted(ManipulationEventData eventData)
    {
        //Debug.LogFormat("OnManipulationCompleted\r\nSource: {0}  SourceId: {1}\r\nCumulativeDelta: {2} {3} {4}",
        //    eventData.InputSource,
        //    eventData.SourceId,
        //    eventData.CumulativeDelta.x,
        //    eventData.CumulativeDelta.y,
        //    eventData.CumulativeDelta.z);

        WorldAnchorManager.Instance.AttachAnchor(this.gameObject, AnchorName);
        Debug.Log("OnManipulationCompleted - Anchor Attached");
    }

    public void OnManipulationCanceled(ManipulationEventData eventData)
    {
    //    Debug.LogFormat("OnManipulationCanceled\r\nSource: {0}  SourceId: {1}\r\nCumulativeDelta: {2} {3} {4}",
    //        eventData.InputSource,
    //        eventData.SourceId,
    //        eventData.CumulativeDelta.x,
    //        eventData.CumulativeDelta.y,
    //        eventData.CumulativeDelta.z);
    }
}`

Note that the WorldAnchorManager.cs is a Singleton and is referenced by it's instance:
WorldAnchorManager.Instance.AttachAnchor(this.gameObject, AnchorName);
Also note that the AttachAnchor method has some commentary:
///
/// Attaches an anchor to the game object.  If the anchor store has
/// an anchor with the specified name it will load the anchor, otherwise
/// a new anchor will be saved under the specified name.
///
This is where the magic happens so that when the app starts when it tries to attach the anchor, it will first see if it already exists.  If so then it loads the anchor which positions the object wherever it had saved it last time the app ran.
Also, note that I have incorporated a way of undoing the last move by saving the previous position and rotation of the object.

Now if you want to be able to grab and move the cube you will need to add the HandDraggable.cs script to the cube.  Keep in mind however that you cannot add the HandDraggable.cs script to an object that has a Rigidbody component attached.  If you have an object that has a rigidbody that you want to move then you'll have to code some way of removing the rigidbody component before adding the HandDraggable component.  But that's not a problem if your not using a rigidbody, just something I ran into.

Hope this helps.  It's all I got.  Thanks!

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.


mkpr

Applied mkpr on package.json
sed s/"@kronos-integration\/service": "^.*"/"@kronos-integration\/service": "^8.3.9"/

Codecov Report

Merging #899 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #899   +/-   ##
=======================================
  Coverage   90.51%   90.51%
=======================================
  Files          10       10
  Lines        1012     1012
  Branches      140      140
=======================================
  Hits          916      916
  Misses         95       95
  Partials        1        1

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 3969291...981e380. Read the comment docs.

:tada: This PR is included in version 9.0.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


orchestration list and server list

There are problems with both orchestration list and server list.
[opc@dd6e7a .ssh]$ knife oraclecloud server list
ERROR: OracleCloud::Exception::HTTPNotFound: Instance "/Compute-metcsgse00082/cloud.admin/dbaas                                                                           /THEDON" does not exist.
[opc@dd6e7a .ssh]$ knife oraclecloud orchestration list
ERROR: OracleCloud::Exception::HTTPNotFound: Orchestration "/Compute-metcsgse00082/cloud.admin/                                                                           dbaas" not found
I haven't looked at the code, but I'm guessing it is getting an instance list and iterating through.   For example /THEDON is a DB CS VM.   So something about the list worked, because it retrieved that, and tried to fetch additional details at the wrong endpoint?
There is another guy from Oracle working on a knife plug-in as well

I'm pretty sure this gem isn't designed for dbaas. Can you connect to the Compute URI?

I wasn't trying to do anything with DBaaS.   That is the compute API URL.
It is fetching everything and getting confused.
937-657-7062

On May 27, 2016, at 6:31 PM, JJ Asghar<EMAIL_ADDRESS>wrote:
I'm pretty sure this gem isn't designed for dbaas. Can you connect to the Compute URI?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

To clarify, the domain And API endpoint has all types of iaas and paas services available to it.
There are instances of iaas and DBaaS all visible via that endpoint.
937-657-7062

On May 27, 2016, at 6:31 PM, JJ Asghar<EMAIL_ADDRESS>wrote:
I'm pretty sure this gem isn't designed for dbaas. Can you connect to the Compute URI?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi,
Any updates on that issue?
I did replicated it, as said the DBaaS does rely on compute, so it's visible from the compute standpoint.


⚠ ClamAV has degraded performance

In ae9382f, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 84 ms

Resolved: ClamAV performance has improved in ed9ba80 after 535 days, 18 hours, 9 minutes.


Ktlint version up (10.3.0 -> 11.6.1)

Hello,
I upgraded the ktlint version from 10.3.0 to 11.6.1 and added ktlint rules(allow-trailing-comma, disable-star-import).
And I have modified the code that violates the rule.

Great! Thank you for your contribution!


Navigation shared transitions not work

after using this this lib and do .inject() , Fragment Navigation shared transitions not work , but when i disable SlidingRootNav that work again !!
why ?!

@sinadalvand tj

@sinadalvand tk


How can I wrap typia in a library?

Hi,
I'm trying to re-export typia in a utility library in my monorepo and I can't get it working with that setup. The error I get is "no transform has been configured" for a createAssert function.
It does work when I import typia directly.
Works:
import typia from 'typia';
...
const throwIfInvalidSomething = typia.createAssert<Something>();

Doesn't work:
import {typia} from '@company/schema'; // export {default as typia} from 'typia';
...
const throwIfInvalidSomething = typia.createAssert<Something>();

Any suggestions to what might cause this?

unplugin-typia = 0.6.16, for esbuild
typia = 6.7.0

@dror-weiss sounds intersting.
Could you give us some minimal reproduction repo?

Ok, so it definitely not a bug and totally my fault: I misunderstood the deployment flow which didn't apply the plugin on the deployment script but did apply it on a serverless function.
Closing.


Form.focusOnFirstQuestion() does not work if the first question is also the page

Observed
If there is a single question on a page, page won't be scrolled to the top when loaded.
Recreate
Make a looong question, e.g. a multipe-select with many options, on a single page.
Fix?
If a page has only one question, then pageEl will have the .question class.  Consequently in the following code, no focus is triggered:
focusOnFirstQuestion: function( pageEl ) {
    //triggering fake focus in case element cannot be focused (if hidden by widget)
    $( pageEl ).find( '.question:not(.disabled)' ).filter( function() {
        return $( this ).parentsUntil( '.or', '.disabled' ).length === 0;
    } ).eq( 0 ).find( 'input, select, textarea' ).eq( 0 ).trigger( 'fakefocus' );
},

This would be fixed by including the original page in the search.

I've tried the following fix:
focusOnFirstQuestion: function( pageEl ) {
    //triggering fake focus in case element cannot be focused (if hidden by widget)
    $( pageEl )
        .find( '.question:not(.disabled)' )
        .addBack( '.question:not(.disabled)' )
        .filter( function() {
            return $( this ).parentsUntil( '.or', '.disabled' ).length === 0;
        } )
        .eq( 0 )
        .find( 'input, select, textarea' )
        .eq( 0 )
        .trigger( 'fakefocus' );
},

It now actually finds the .question element, but the fakefocus event has no noticeable effect.

Makes sense. Thanks!


Dockerfile?

Java is the only system dependency to run Kwery, do you still see a value in adding a Dockerfile?


SAK-49294 Group assignments with prerequisites inaccessible in Lessons

Jira: SAK-49294

In Lessons, the student can't access the group assignment (to which he belongs) despite having completed the prerequisite

An assignment with assigned group(s) will be managed through a single ACCESS group on Lessons.
To access the assignment after completing the prerequisite, the user should be automatically added to the ACCESS group - if it's present on the original group(s).
To allow this behavior to work, membership won't be locked for ACCESS groups ✅

Also within this commit, the locks won't be removed for the initial group after being 'replaced' by the ACCESS one.
As they can prevent inconsistent behaviors.

img B/A this fix - result of setting "Don't release item until all prerequisites are completed"

It does not compile ?

@mpellicer It compiles on my pc 🤔

One test failing, I'm checking it

Thank you Vicent, great job @V100X !


Installing qiime on google colab

Dear Creator,
I found your very useful qiime course on the YouTube and finally find the materials for the course here. However, when I tried to follow exactly the video and install it on the google Colab, it never accomplished.
!git clone https://github.com/gibbons-lab/isb_course_2021 materials
%cd materials
%run setup_qiime2
Even I tried your suggested commend (bellow) in forum, it did not work.
!wget https://github.com/Gibbons-Lab/isb_course_2021/raw/main/setup_qiime2
%run setup_qiime2
As I want to run my code on the google Colab, do you have any suggestions for me?
Best Regards,
Ghs

Hi, I would recommend running the version from this year which will take place from October 11-13th. The notebooks there will be up to date and are running fine :) If you want to run the version from 2021 you might have yo replace the setup script with the one from 2023 since we adapted it for newer Qiime2 versions.

Hi, I would recommend running the version from this year which will take place from October 11-13th. The notebooks there will be up to date and are running fine :) If you want to run the version from 2021 you might have yo replace the setup script with the one from 2023 since we adapted it for newer Qiime2 versions.

Dear Christian Diener,
I followed your suggestion and yes it works.
Thanks for your prompt reply.
Best Regards,
Ghs


[Bug]: pdf file parsing failed

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
3050a8c
Other environment information
No response
Actual behavior
Split-Split-Apress.Practical.WPF.Charts.and.Graphics.Nov.2009(601-709)(1-54).pdf
无法完成pdf解析，大概所有页面都处理完了，进度百分比就停住了，然后等了一个多小时，进度百分比也没有变化，就这样卡死了。
Expected behavior
完成pdf文件解析。
Steps to reproduce
知识库正常上传，点击启动解析按钮。

Additional information
No response

I uploded on the demo website. It works fine.
If you deployed locally, have a look at logs using docker logs -f ragflow-server


Update keystore-explorer to 5.1.1

Thank you for the contribution. It was merged directly as 44f7d5d83372beb2a00b694896c5422fc671153e to keep commit history cleaner. Your contribution is still credited to you.


Proposal: generate bidirectionally bound html form from map

I'm interested in a particular use case that's beneficial for demoing modlets to clients and can also aide in isolated development, debugging, and testing. However, since the underlying technology that'd be generated from implementing this is generally applicable, this issue can serve as a central rallying point.
simple use case
Every modlet has a demo file that instantiates its component. In all but the simplest components, a developer binds the component's attributes to an outer scope seeded with test data.
e.g.
<script id="demo-html" type="text/stache" can-autorender>
<can-import from="~/my-component/" />

<my-component {attr1}="arg1"  {attr2}="arg2"  {attr3}="arg3" />
</script>

<script id="demo-source" src="../../node_modules/steal/steal.js" main="can-view-autorender">
import viewModel from 'can-view-model';

viewModel('#demo-html').set({
  arg1: true,
  arg2: 42,
  arg3: 'hello, world'
});
</script>

If arguments passed into the component share rich relationships, then it's helpful to bidirectionally bind those component attributes to form elements. This facilitates demonstrating how the component behaves over a range of parameters.
I'm interested in a component that can become a standard part of the donejs modlet generator that would mostly automate this case for all modlets. I believe that putting in 20% of the effort required to implement a general purpose map to html form generator would prove beneficial to 80% of components.
e.g.
<script id="demo-html" type="text/stache" can-autorender>
<can-import from="vm-demo" />
<can-import from="~/my-component/" />

<my-component *vm />
<vm-demo {vm}="*vm" />
</script>

<script id="demo-source" src="../../node_modules/steal/steal.js" main="can-view-autorender">
</script>

potential

a general purpose map to html form generator supporting:

nested data structures
can-reflect (custom data types)
can-connect (models)

Little Importent information about that as i am doing the same but i am not finish with a fully generic one you need to add the propertys with fild types! the modlet aka component needs to create filds not with only the definiton of the name so you need to pass
fildname:
type:
options: { max-length }

and so on to have a fully generic component that all can use if you open a repo i can contribute back


Implement images as arrays of sf::Color, not arrays of uint8_ts.

https://github.com/SFML/SFML/blob/3a3935d00569c5cf3dbd684ab10e54e8480df167/include/SFML/Graphics/Image.hpp#L283
Images are currently represented as arrays of uint8_t where the assumption is that each array has a size equal to 4 times the width times the height. This invariant leads to code which is not obvious on its face and requires comments for the reader to understand it.
What if this:
void Image::createMaskFromColor(const Color& color, std::uint8_t alpha)
{
    // Make sure that the image is not empty
    if (!m_pixels.empty())
    {
        // Replace the alpha of the pixels that match the transparent color
        std::uint8_t* ptr = m_pixels.data();
        std::uint8_t* end = ptr + m_pixels.size();
        while (ptr < end)
        {
            if ((ptr[0] == color.r) && (ptr[1] == color.g) && (ptr[2] == color.b) && (ptr[3] == color.a))
                ptr[3] = alpha;
            ptr += 4;
        }
    }
}

instead looked like this?
void Image::createMaskFromColor(const Color& color, std::uint8_t alpha)
{
    for (auto& pixel : m_pixels)
        if (pixel == color)
            pixel.a == alpha;
}

Better data structures do so much to allow for more expressive code that effortlessly does the correct thing without need for extra checks and pointer arithmetic. In other words, this proposal results in lots of C-style code becoming C++-style code and from past PRs I think there is consensus that we don't want to write C.

This change also flows out into the API. Because we have interfaces that expect a uint8_t*, those interfaces will be forced to change to take a Color*. I prefer this change because it pushes users towards better data structures as well and makes it obvious upon inspect what the API really means.
One downside that Vittorio pointed out was that if users are using SFML alongside other image APIs that expect a pointer to a uint8_t, this new interface could cause them issues. I have no such experience with such situations so I cannot say how common this may be. I'm inclined to think that if we already use strong SFML types in our API, this should not be an exception. One might say that the old (float, float) interface was more flexible and friendly to 3rd party APIs than using Vector2f but such downsides are speculative whereas the gains of strong types are concrete.

But what about undefined behavior?
So this is a can of worms. I've tried to do my homework and have even asked an expert on computer images here at CppCon to get more feedback on this. The crux of the problem is that OpenGL is expecting a pointer to a uint8_t which is why the implementation looks the way it does. The question is whether or not we can reinterpret a vector<Color> as a uint8_t* without invoking UB. I believe the answer is no it is not UB because I think the standard allows you to read anything as a sequence of bytes and I think that's all that OpenGL is doing.
It's preferable for us to prove that this is not UB but proving a negative is tricky. What I can say is that no compiler produces incorrect behavior, no compile warns on this, clang-tidy reports no issues, and even Undefined Sanitizer (UBSan) reports nothing. What I've been told (and what I would expect given my own personal experience) is that whether or not this is UB, it's such a common request that no compiler would ever reject this code which means we are safe to depend on this. If compilers no longer let you reinterpret some uin32_ts as an array of uint8_t, the whole programming world would collapse.
Luckily we can write tests to ensure that at least on the machines we test in CI, this behaves as expected. This is what those tests look like:
    SUBCASE("Reinterpret as std::uint8_t*")
    {
        const std::vector<sf::Color> pixels = {{10, 11, 12, 13}, {14, 15, 16, 17}, {18, 19, 20, 21}};
        const std::uint8_t*          begin  = reinterpret_cast<const std::uint8_t*>(pixels.data());
        CHECK(begin[0] == pixels[0].r);
        CHECK(begin[1] == pixels[0].g);
        CHECK(begin[2] == pixels[0].b);
        CHECK(begin[3] == pixels[0].a);

        CHECK(begin[4] == pixels[1].r);
        CHECK(begin[5] == pixels[1].g);
        CHECK(begin[6] == pixels[1].b);
        CHECK(begin[7] == pixels[1].a);

        CHECK(begin[8] == pixels[2].r);
        CHECK(begin[9] == pixels[2].g);
        CHECK(begin[10] == pixels[2].b);
        CHECK(begin[11] == pixels[2].a);
    }

Of course these tests in isolation are not sufficient to justify this proposal but they do help provide the evidence required to make us comfortable making such a change.

SFMLBuildMaster: Build this please.

I can see how it can beautify some of the internal implementations, but that's IMHO a rather low goal and ways a lot less compared to API compatibility and usefulness. Said differently, I'm more than happy to have some "uglier" code in the library, if it means that the API provided is more useful and I can better operate with the APIs used internally. I'd even go as far as to say, the reason we are a library, is to hide some of the "ugly" code.
I am aware that it can be a bit more tricky for some people to work with a collection of "pixel color components", rather than collection of "pixel colors", but on the other hand, there are so many more direct transformations you can apply to collection of components rather than colors.
From my understanding the current API breaks the "encapsulation" principle slightly by giving direct access to the data, exactly because it allows operations on the raw data itself.
If we change the inner representation, I personally would question the getPixelsPtr API completely.
Can you provide a use-case where I'd want a std::vector<sf::Color>?

Can you provide a use-case where it would be more useful to have an std::vectorsf::Color rather than a std::vectorstd::uint8_t outside of SFML's internal code?

You can already use vector<Color> today but it requires a reinterpret_cast because of SFML's C-style image API.  Luckily I know that I can use an array of colors but most users will just use a vector (or array) of uint8_t because SFML's API pushes them that way thus causing their code to be uglier and more bug prone.
https://github.com/ChrisThrasher/mandelbrot/blob/master/src/Mandelbrot.cpp#L58

See #2203 for tests that test this behavior across all platforms in our CI pipeline.

https://godbolt.org/z/M5r8d5YM1
Here's a Godbolt version of these tests to experiment with or share with others who may be able to help answer our questions.

I also want to remind you of the issue we talked about yesterday, converting from char* to Color*. There might be projects that get a stream of bytes from some external source, and use it to e.g. create a sf::Image.

I also want to remind you of the issue we talked about yesterday,

Yep I gave you credit for that in the issue body.

I'm so sorry to jump in the middle of the discussion out of the blue, but I really like SFML and wanted to contribute in some way (even if it is with just a comment)!
I don't know if you have considered but maybe the std::variant store, introduced in C++17, that holds a set of alternative types could help here! For example, the first color check could be done like this:
int main() {
    /* Pixels can be of type std::vector<std::variant<Color, uint8_t>> pixels*/
    const std::vector<std::variant<Color, uint8_t>> pixels = {
        Color{10, 11, 12, 13}, Color{14, 15, 16, 17}, Color{18, 19, 20, 21}
    };
    const uint8_t* begin = reinterpret_cast<const uint8_t*>(pixels.data());
    if(std::holds_alternative<Color>(pixels[0])){
        CHECK(begin[0] == std::get<Color>(pixels[0]).r);
        CHECK(begin[1] == std::get<Color>(pixels[0]).g);
        CHECK(begin[2] == std::get<Color>(pixels[0]).b);
        CHECK(begin[3] == std::get<Color>(pixels[0]).a);
    } else {
        CHECK(begin[0] == std::get<uint8_t>(pixels[0]));
        CHECK(begin[1] == std::get<uint8_t>(pixels[1]));
        CHECK(begin[2] == std::get<uint8_t>(pixels[2]));
        CHECK(begin[3] == std::get<uint8_t>(pixels[3]));
    }
    /* ...and so on for the remainder of the tests */
}

In the above code both 'if' and 'else' clauses will work and tests pass (using -std=C++17, which I believe is enabled in SFML). However, it was not possible to remove the reinterpret_cast. A possibility would be doing something like:
void check_pixels(Color pixels){
    const Color* begin = &pixels;
    if((*begin).r == pixels.r)
        std::cout << "First Hoooray (Color)" << std::endl;
}

void check_pixels(uint8_t pixels){
    const uint8_t* begin = &pixels;
    if(*begin == pixels)
        std::cout << "Final Hoooray (uint8_t)" << std::endl;
}

int main() {
    const std::vector<std::variant<Color, uint8_t>> pixels = {
        Color{10, 11, 12, 13}, Color{14, 15, 16, 17}, Color{18, 19, 20, 21}
    };
    std::vector<std::variant<Color, uint8_t>> pixels_2;
    for(unsigned char i = 10; i < 22; ++i)
        pixels_2.push_back(i);

    if(std::holds_alternative<Color>(pixels[0])){
        check_pixels(std::get<Color>(pixels[0]));
    }

    if(std::holds_alternative<uint8_t>(pixels_2[0])){
        check_pixels(std::get<uint8_t>(pixels_2[0]));
    }
}

Taking the snippet above as an example, exposing the SFML functions to other code could be done using function overload.
Again, sorry for jumping in! These are just some ideas I've had, hope I did not waste anybody's time.

@MatheusBonavite Thanks for your input! With
std::vector<std::variant<Color, uint8_t>>

the problem is that every single element needs to hold a discriminant (1 byte). This would be 25% overhead just in storage, while no one would want to differentiate on a per-element basis.
You also probably meant std::array<uint8_t, 4> instead of uint8_t, since 4 bytes are equivalent to 1 sf::Color.
I think even an outer variant (either a vector of bytes, or a vector of colors) would complicate the API. If we really want to provide both to the user, there should probably be two separate methods.

We now have UBSan in CI and the sf::Color tests from #2203 are still passing. A year later and I still can't find reason to believe this is UB or otherwise problematic.

Somehow completely missed this thread. When discussing changes here, I think it wouldn't even hurt to add/introduce one important extra property for processing raw pixel data: stride.
So for in-memory representation, the image data wouldn't fill 4 * width * height bytes, it would actually be stored over stride * height bytes, where stride is the length of one row/line in memory.
A classic example would be non power of two textures:

Let's assume the image size is 40x40 pixels.
The next bigger power of two texture size would be 64x64 pixels.
So one row/line inside the image is 40 * 4 = 160 bytes (or 40 color values).
However, the stride would be 64 * 4 = 256 bytes (64 color values).

So when accessing raw bytes, I'd expect to retrieve the whole data, including random/unused bytes within the stride (since I'm using a memory address, not pixel coordinates inside the image). In other words: the accessible/used memory should be 64 * 64 * 4 = 16384 bytes long.
When accessing/reading individual pixels, I'd expect to retrieve only the actual image data, i.e. 40 * 40 = 1600 color values/pixels.
As such, I think it might be the best way to really just provide both approaches in separate functions, although I'm not 100% sure about using width or stride when interpreting user provided offsets (i.e. offset = y * width + x vs. offset = y * stride + x).

The team has chosen to not add this to v3 so I’m going to close this issue.


chore: bump sphinx to v6.2.1 and myst-parser to v1.0.0

Renable dependabot updates since the latest modules are compatible

Fixes https://github.com/envoyproxy/gateway/issues/848

I'd like add a label to test the cherrypick action

@zirain does this need @AliceProxy's approval ?

it will create a PR, still need approval from maintainer


Add go linting tools to CI

Background
GolangCI-lint is a popular linter for go-projects which has support for a lot of popular linters like govet, golint, gofmt, etc, so it gets a bit easier than having to write individual shell scripts & complex Makefiles. It's super configurable so it's warnings can be silenced & it runs with similar toggles locally, i.e. the config file works well for the local development & CI.
 Per the docs, using the official golangci-lint action might turn out to be a better approach than adding it via the Makefile in some other action/job.

@vharsh I'd like to work on this, could you assign me?

I'm not sure where the Verify License task should go.
https://github.com/openebs/openebsctl/blob/9001fb02a2d73b5f250951df10176220bfdb8602/.github/workflows/go.yml#L5-L23
And should this section be completely removed from the Makefile?
https://github.com/openebs/openebsctl/blob/9001fb02a2d73b5f250951df10176220bfdb8602/Makefile#L66-L73
Can you please clarify this?

@burntcarrot You can move the license checking part to goheader via GolangCI-lint & remove it from the go workflow.
Regarding the golint: target in Makefile, you can replace it with the golangci-lint run command & rename golint to golangci in Makefile


Error while trying to enable the extension (v2.1) on vs-code (v1.72)

same error for me too (tried on win10, mac, and win 11) using both normal vs-code and insiders

Version 3.0.0 and I have this problem.

How do I resolve this issue?

Hey folks, the latest 3.0.1 version is out fixing this issue. Let me know if that works. There will be more fixes coming out soon.
Thanks.

Hello. I just installed this new version and it is working correctly. Thanks for the quick fix.
I didn't know about this extension but it looks amazing. I can't wait for the next changes.

Glad to know it works for you!


Stop indenting lists in trainee dashboard

Fixes https://github.com/swcarpentry/amy/issues/855

:+1:

@chrismedrela ping :-)

@pbanaszkiewicz pong


Video won't play

Videos have not been playing for a few days now :(

I finally fixed it! Please download latest version!

Awesome, thank youu! 🙏


Can't open on Windows 11 64bits

After running the exe file an error occured as shown in the screenshot. The app seems to be installed. I have the icon on my desktop and in recently added apps.

I appreciate you opening an issue for this, I'm currently looking into this and hoping to get a new version out soon. Looks like an issue with the cross compiled sharp library that I use on my M1 Mac. I'm looking into some options of using a Docker container to run electron-builder and generate a Windows/Linux version that work.
At any rate, this will be fixed soon. :)

I just released a 1.0.2 version, that I tested on a Windows VM but it was Windows 10. Let me know if this resolves the issue for you.
https://github.com/peytoncasper/remarkable-sidekick/releases

It resolves the issue, thanks!


NameError: undefined local variable or method 'flash' for controller...

Hi all,
Running clearance gem on my rails -API only application and getting this error while clearance is trying to show flash messages.

Is there any way to disable flash from clearance side??

Thanks for submitting an issue @JonesGladston. Clearance does not support API mode out of the box and we don't currently have any plans to offer an API only configuration option.


Format code doesn't work!

From @fbenvegna on November 9, 2016 15:32

VSCode Version: 1.7.1
OS Version: Windows 7 Professional SP1

Steps to Reproduce:
I have a Node.js/Express/ExtJS large project with 19000 files and 3300 directory

create a new file on routes (or other) directory
insert few lines of unformatted code
format the code.... it's OK!
close and reopen VSCode
reopen the file
apply some change to the code
format the code.....  fails!!!!

No problem with vscode 1.6.
Now, it's impossible to format any existing file on project!
Copied from original issue: Microsoft/vscode#15243

From @aeschli on November 9, 2016 19:7
What's the language of the file that you format? Does it matter what's the content of the file?
Also, can you list the extensions that you are using and also maybe try to run code without extensions?
Use  code --disable-extensions for that

From @fbenvegna on November 10, 2016 16:0
I tried code --disable-extensions but nothing is changed!

From @fbenvegna on November 9, 2016 20:6
The language is JavaScript. It's a Node.JS / Express project.

From @fbenvegna on November 10, 2016 16:5
I downgraded VSCode from 1.7.1 to 1.6.1 and formatting is OK!!!!
The problem is only on 1.7.X.
Please, correct the bug!

From @fbenvegna on November 11, 2016 10:21
After many trials, I found a solution to the problem... jsconfig.json.
If you delete the file... code formatting it's ok!
But I need jsconfig.json!
In my case, I have to add the ExtJS directory ('public' on my project) to "exclude" section
	 "exclude": [ 		"node_modules", 		"public" 	]
Now, code formatting on 1.7.1 is OK!
I think that problem is related to Intellisense because another solution is to delete the ExtJS sources subdirectory inside 'public' and all is working.

looks like a dupe of https://github.com/Microsoft/TypeScript/issues/11888


Fix registration's params get_git_remote()

registration's get_git_remote() currently returns potentially the incorrect git remote if the user has multiple remotes set up.

Looking into it now.

So we have code in selfdrive/version to do this as well. Needs to be refactored before merging

Gotcha, I'll take a look

Going to merge, we'll refactor internally.


Testing rq integration fails because of version issue

How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.30.0
Steps to Reproduce
Installed sentry_sdk, in an editable mode for contribution
I tried running the rq integration tests on master
RQ version - 1.15.1

Expected Result
Successful passed tests for rq integration
Actual Result
all failed tests pointing towards the version issue

Hey @vagi8 !
Thanks for bringing this up.
We want to look at the RQ integration this week, so maybe this will be also fixed right away.

This was fixed in RQ already: https://github.com/rq/rq/pull/1329


Problem with asp-prerender-module？

My entry page is Login. I don't know why first view like this.

Maybe after 5 seconds, the style rendered OK.

for the app tag
If I remove asp-prerender-module="ClientApp/dist/main-server"，style will being OK. But this not the right way...
How can the style keep same? thanks

Is my problem, css wirte wrong, sorry!


client: add channel acceptor with new fields

This PR uses rpc fields which are only exposed in lnd 0.12: it should not be merged to master until we have cut lnd.

Or should the master branch only contain functionality that is backward compatible to at least the last major version and everything that requires an update should live in a branch?

This approach makes sense to me. Ok to merge anything that has been included in the last tagged major version, and let other stuff live on a branch until we tag the next major version.

Anyway, to progress with this PR, I created the lnd-12-0 branch and suggest merging the PR against that for now.

Will go ahead with this!

Added ctx with timeout to acceptor function here.

Replacing this with #27, which is against the 0.12 branch rather than against maser. No code change, just re-create pull.


[1.1] Extract all dual variables for SOC, Exponential Cone constraints

We don't recover all the dual variables associated with SOC and Exponential Cone constraints. We should fix this in 1.1 at some point (this issue is not blocking for the initial release).
cc @SteveDiamond , since you were close to fixing this at some point.
cc @angeris, since you want all the dual variables,

The main problem was that the cvx_attr2constr.py reduction has baked in assumptions that each constraint has one dual variable that are very difficult to change. We essentially need to rewrite the reduction. Otherwise it's not too difficult to add support for SOC and Exponential cone dual variables by tracking dual variables based on the dual variables stored with each constraint rather than tracking them based on the constraints themselves. That's the approach I was working on before I rolled things back.

@SteveDiamond @akshayka I have a proof-of-concept approach on the "tinker" branch of my fork. See https://github.com/rileyjmurray/cvxpy/commit/90d7175cfaefea000113fea0e22be0a96614c9d9 for the commit, along with comments explaining what I did. In the end I only implemented exponential cone dual variable recovery for MOSEK, but the approach applies to all solvers.

Commit https://github.com/rileyjmurray/cvxpy/commit/08198edcdfd5edef2cdb56c2c863549f27a60522 has a more viable implementation. It does not change the ExpCone signature. It has ExpCone override two functions from the Constraint class, and updates MOSEK's invert function. It introduces a scalar_product function, which could be removed if necessary, or handled as a separate issue. Any other changes are just reverting changes to ExpCone from my earlier commit.

It looks reasonable to me! I ran into some issues with the complex2real reduction, so that's something to look at. It might have been because of a broader change I was pushing through though, and not dual variables in themselves.

Dual variables for exponential cones should be resolved on the master branch of my fork (all relevant solvers). I still need to add extra tests, but it should be in good shape.

Awesome! If you have spare cycles, and if the logic is the similar, want to fix SOC as well?

I’m happy to fix SOC for ECOS/SCS/CVXOPT/MOSEK. In order to close this ticket we’d need to address other commercial solvers. I’ll take a look and comment on what likely needs to be done with those solvers, in my next PR.
Sent with GitHawk

I have basic tests passing for SOC, with MOSEK (and ECOS, implicitly). SCS should inherit similarly.
One obstacle in getting you a PR is that solver tests are kind of a mess right now. They're scattered across test_solvers.py, test_mosek_conif.py, test_scs.py, test_super_scs.py, and test_cbc.py. From there, there is a large amount of code duplication (e.g. the same 5 lines defining an LP from the CVXOPT manual appears something like 10 times).
I'm inclined to restructure all solver tests to reduce code duplication before adding tests for dual variable recovery for SOC constraints. @akshayka is doing a general restructuring of solver tests okay, or would you prefer to avoid that?

Riley, if you’re up for refactoring the solver tests, you’re more than
welcome to! That’d be much appreciated.
On Fri, Nov 29, 2019 at 1:13 PM rileyjmurray<EMAIL_ADDRESS>wrote:

I have basic tests passing for SOC, with MOSEK (and ECOS, implicitly). SCS
should inherit similarly.
One obstacle in getting you a PR is that solver tests are kind of a mess
right now. They're scattered across test_solvers.py, test_mosek_conif.py,
test_scs.py, test_super_scs.py, and test_cbc.py. From there, there is a
large amount of code duplication (e.g. the same 5 lines defining an LP from
the CVXOPT manual appears something like 10 times).
I'm inclined to restructure all solver tests to reduce code duplication
before adding tests for dual variable recovery for SOC constraints.
@akshayka https://github.com/akshayka is doing a general restructuring
of solver tests okay, or would you prefer to avoid that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cvxgrp/cvxpy/issues/830?email_source=notifications&email_token=AAPG4RC4LDBWOQPABYJNZ7DQWGAYTA5CNFSM4I5GAUYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPRZZI#issuecomment-559881445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPG4RF6UUWGPKKX5IC7N3DQWGAYTANCNFSM4I5GAUYA
.

I'm working through that now. It'll take a while (since there are so many solvers), but I'll get it done.

Solver tests are refactored, and include (basic) dual variable recovery tests. SCS is failing the SDP dual variable recovery test. ECOS, CVXOPT, and MOSEK are passing their test suites.
I have tests in places for other solvers (i.e. solvers other than ECOS, SCS, CVXOPT, MOSEK), but I have not run those tests.

SCS PSD dual variables are fixed.
@akshayka I can create the PR now. It would be good to add additional tests for ExpCone and SOC (specifically, tests where vectorization is used in each of these constraints), but I'm hoping you or @SteveDiamond can take care of those. Does that sound good?

Awesome! Yes, that sounds good, @rileyjmurray. Perhaps write a TODO in the test case, documenting that we should add tests for the ExpCone and SOC?

Hey, sorry for dropping off the grid for a while there. I should make the PR soon. I'll add TODO's for tests which should be added.


Return minified JSON in /data endpoints

Right now the json returned from /data is not minified, see this line where it's returned via .Data and here where the formatted json is built.

It's already minified, the dev tools just format it even in the response tab 🤦


Sample files validation through envTest

This patch improves the test area of the Glance operator. Sample files are loaded from the main directory and a Glance CR is created. The goal is to validate the syntax provided by the samples stored in the operator project.

Looks good to me, can you add somewhere in commit that atm it is not testing backend and import plugin samples from config/samples directory?

We could, but basically we're not going to validate those files because they are supposed to deploy  an OpenStack ctlplane instead of a Glance CR. Before extending this test to the backends/ directory, we should add Glance specific sample CRs w/ each backend. Something we can follow up in the future (less priority I'd say).


Prevent LFI in Gregwar/RST 1.0.3+

Gregwar/RST v1.0.3 includes a mitigation for local file inclusion vulnerabilities. Details here.
Disable File Inclusion
- $parser = new Gregwar\RST\Parser();
+ $parser = (new Gregwar\RST\Parser())
+     ->setIncludePolicy(false);

Jail File Inclusion to a Specific Directory
- $parser = new Gregwar\RST\Parser();
+ $parser = (new Gregwar\RST\Parser())
+     ->setIncludePolicy(true, '/path/to/rst/jail');

Note that this supports the same syntax as PHP's open_basedir (joined with a : separator)
- $parser = new Gregwar\RST\Parser();
+ $parser = (new Gregwar\RST\Parser())
+     ->setIncludePolicy(
+         true,
+         implode(':', [
+             '/var/www/common/rst-snippets',
+             '/var/www/example.com/rst-snippets'
+         ])
+ );

General Recommendations

If you're loading RST templates from a database, disable include. This is what Airship does.
If you're loading RST templates from the filesystem and need include for snippets, jail all includes to within a common directory.

Thanks. I committed 985a1cc to address this.


TypeError: fn is not a function

In my code I had:
schema.plugin(patchHistory, {mongoose,...
Which threw the error:
TypeError: fn is not a function
    at Schema.plugin (/Users/himrc/Sites/dama/node_modules/mongoose/lib/schema.js:1133:3)

I was able to fix it by adding default. Not sure why I needed to do this.
The working code for me was:
schema.plugin(patchHistory.default, {mongoose,...

I guess you required the module like this?
var patchHistory = require('mongoose-patch-history');

const patchHistory = require('mongoose-patch-history');
Ah I see, you're using import... gotcha.

I changed my express to use babel-node. 💥

@mrchess We might consider changing this. I'm not sure if there's a way with babel to have both require and import work without having to resort to default when requiring.


libvpx: 1.14.0 -> 1.14.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libvpx/versions.
meta.description for libvpx is: WebM VP8/VP9 codec SDK
meta.homepage for libvpx is: https://www.webmproject.org/
meta.changelog for libvpx is: https://github.com/webmproject/libvpx/raw/v1.14.1/CHANGELOG
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.14.1 with grep in /nix/store/rcpx7bcnifn4hk3sl2gdp179gq4ch8wb-libvpx-1.14.1-bin
found 1.14.1 in filename of file in /nix/store/rcpx7bcnifn4hk3sl2gdp179gq4ch8wb-libvpx-1.14.1-bin

Rebuild report (if merged into master) (click to expand)

10334 total rebuild path(s)

10334 package rebuild(s)

First fifty rebuilds by attrpath

CHOWTapeModel
ChowKick
CuboCore.corepdf
CuboCore.coretoppings
EmptyEpsilon
Fabric
MIDIVisualizer
MMA
OVMFFull
SDL2
SDL2_Pango
SDL2_gfx
SDL2_image
SDL2_image_2_0
SDL2_image_2_6
SDL2_mixer
SDL2_mixer_2_0
SDL2_net
SDL2_sound
SDL2_ttf
SDL_audiolib
SDL_compat
SDL_gpu
Sylk
_1oom
_20kly
_64gram
_7kaa
_86Box
_86Box-with-roms
_90secondportraits
aaxtomp3
abbaye-des-morts
abracadabra
abuse
acltoolkit
acquire
actiona
activitywatch
ad-miner
adafruit-ampy
adapta-gtk-theme
adenum
adidnsdump
adl
adoptopenjdk-icedtea-web
adriconf
adwsteamgtk
aegisub

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rcpx7bcnifn4hk3sl2gdp179gq4ch8wb-libvpx-1.14.1-bin \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libvpx https://github.com/r-ryantm/nixpkgs/archive/0f007929ef63f0ecb485c5f1bdd0dd1e5a0d2aaf.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0f007929ef63f0ecb485c5f1bdd0dd1e5a0d2aaf#libvpx

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rcpx7bcnifn4hk3sl2gdp179gq4ch8wb-libvpx-1.14.1-bin
ls -la /nix/store/rcpx7bcnifn4hk3sl2gdp179gq4ch8wb-libvpx-1.14.1-bin/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @codyopel for testing.

Flagging as security related (CVE-2024-5197).

Cherry-picked to staging-next for testing. Built passthru.tests on macos 12 x86_64 & nixos x86_64. Built pkgsStatic, pkgsMusl, pkgsCross.aarch64-multiplatform, pkgsi686Linux variants successfully.

Thanks for updating the tests ♥


failed to connect to : Get /v2/auth/id: unsupported protocol scheme ""

Hello,
We are deploying fresh deployment of V8.0.8 shield-bosh-release on our bosh2 env.
Deployment succeeded for v8.0.8, but import errand failed with following errror.
_**Exit Code  1
Stdout     Connecting to
Stderr     !!! : failed to connect to : Get /v2/auth/id: unsupported protocol scheme ""
1 errand(s)
Errand 'import' completed with error (exit code 1)
Exit code 1**_
Here proving our manifest file.
shield.txt

I believe your core property under the import errand is missing the https:// scheme.
I also notice you are running 8.0.8; import got some validation fixes in 8.0.11 https://github.com/starkandwayne/shield/releases/tag/v8.0.11, which you may want to update to (or, at your discretion, 8.0.13, released last Friday).
https://github.com/starkandwayne/shield/releases/latest

This sounds like the same issue the @lordcf user was having in https://github.com/starkandwayne/shield-boshrelease/issues/129

We have provided core property under the import errand as follow
jobs:
- name: import
properties:
import:
core: https://IP:443
Now we tried with v8.0.11 having issue with core only as follow-
Exit Code  1
Stdout     importing now......
Stderr     !!! : Missing requird 'core' top-level key in the import manifest.

can you verify the indent level in your manifest?  here on github, it looks like nothing is properly indented...

Hi
I checked manifest, as indentation is proper for import job , please have a look on below shield.txt file
shield.txt

Can you also post /var/vcap/jobs/import/config/import.yml?

I checked this import.yml file , it is blank .
import.yml
--- {}

Hi,
This issue resolved , there was indentation issue only.
Now able to run import errand, test-store task also done, but now facing issue with backup , backup task is in failed status.
Error is as follow-
**mysqldump: Got error: 2002: "Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2 "No such file or directory")"
when trying to connect
Unable to exec '/var/vcap/packages/mariadb/bin/mysqldump': exit status 2
        EXITING 3
        shield worker 4 unable to run command against   ##IP##**


Verify enterprise key and DID

We now use did:web so web is now the  default DID method
Enterprise key is the RSA key
Verification method (vm) is kid when signing with didkit
Check data are good :
Download https://domain/.well-known/did.json
vm should exist in assertionMethod and n attribute should be the same.
for testing we will use: https://ecole42.talao.co/.well-known/did.json and did is did:web:ecole42.talao.co

Breaking change in data verification:
no did.json download. We will use didkit.resolve_did(did, “{}) which will provide us a copy of the json.

If verification is failing we stop the process, warn the user and go back to RSA and DID input.

We can use https://pub.dev/packages/json_path to find information in the json document.

complexity: 5

Here's the result of await didKitProvider.resolveDID('did:web:ecole42.talao.co', '{}');


Desired Size for both Self managed and EKS managed not working after the EKS deployment

Scenario: I needed to provision a couple of EKS clusters using both EKS managed and Self managed node groups. I tried provisioning it with this code using the 18.8.1 version and I am able to deploy it for both node groups.
Problem statement:  This code is not accepting "desired_size" changes in terms of adding/removing the nodes after the EKS cluster deployment is done based on the need.
Versions:
Terraform-aws-eks: 18.8.1
Terraform 1.1.6
OS: Windows 10 Enterprise
EKS: 1.21
`
terraform-aws-eks/main.tf
module "eks" {
source                               = "terraform-aws-modules/eks/aws"
version                              = "18.8.1"
vpc_id                               = var.vpc_id
subnet_ids                           = var.public_subnets
cluster_endpoint_private_access      = var.cluster_endpoint_private_access
cluster_endpoint_public_access       = var.cluster_endpoint_public_access
cluster_name                         = var.cluster_name
cluster_version                      = local.cluster_version
tags                                 = local.tags
eks_managed_node_group_defaults = {
ami_type               = "AL2_x86_64"
disk_size              = 20
instance_types         = ["m6i.large", "m5.large", "m5n.large", "m5zn.large"]
vpc_security_group_ids = [aws_security_group.all_worker_mgmt.id]
}
eks_managed_node_groups = {
# blue = {}
green = {
min_size     = 1
max_size     = 5
desired_size = 4
instance_types = ["t3.large"]
capacity_type  = "SPOT"
labels = {
Environment = "eks-terraform"
}
taints = {
dedicated = {
key    = "dedicated"
value  = "gpuGroup"
effect = "NO_SCHEDULE"
}
}
tags = {
Maintainer = "Sourabh Sharma"
}
}
}
}
`

Desired size is ignored due to the nature of Kubernetes and predominant use of autoscaling (i.e. - cluster autoscaler, Karpenter, etc.). Therefore changing desired_size after provisioning will not influence the number of nodes. If you need to force more nodes into the pool, you can raise the min_size as a work around

Desired size is ignored due to the nature of Kubernetes and predominant use of autoscaling (i.e. - cluster autoscaler, Karpenter, etc.).

This makes sense. However the desired size as well as min/max can be changed in the EKS UI in the AWS Console. I would assume if the AWS UI can do it, it could also be possible for the Terraform module to do it also.

https://github.com/bryantbiggs/eks-desired-size-hack


RednderFlex overflow bug on Medicine List Page

Describe the bug
The Lottie animation in the customAppBar Widget on Medicine List page is causing the RenderFlex overflow by 7.3 pixels on the right
To Reproduce
Steps to reproduce the behavior:

Go to -: Medicine List Page.

Expected behavior
No error on the screen.
Screenshots

Smartphone (please complete the following information):

Pixel 3a

Please assign it to me.


Improved / Customizable Code Highlighting

As it stands currently, there isn't a simple way to highlight, for example, style.css.less.erb as CSS.
In prior versions you were able to edit a languages.json file but that seems to be removed (I think it's actually just minified now).
I'm running sprint 0.35.0-10897
Ideally there would be a dropdown to force association. Or possibly clicking the language definition at the bottom right would allow you to override.

@ericbieller There is now a dropdown menu in status bar for overriding the language for any file. This was introduced in Release 0.42. Additional "Set as Default" functionality was added in Release 0.44. Closing.


Updated setup.py for passing CI and added Viper

Description

Fixed #800
Using install_requires and dependency_links to get packages from GitHub.
Removed serpent from dev_requirements.txt
Because PR #791 (Casper integration) would need Viper, I add it in advance. And since Viper doesn’t have a released version and the development is rapid recently, I use a commit reference to lock specific version.

Note that Viper requires Python 3.6+

Can confirm this fix is good. Can someone merge (@joeykrug)? needed for https://github.com/holiman/evmlab/pull/11


Bumping helm-charts for UI v1.5.1

Codecov Report
Base: 60.04% // Head: 48.33% // Decreases project coverage by -11.71% :warning:

Coverage data is based on head (4e085ff) compared to base (3a71b78).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1893       +/-   ##
===========================================
- Coverage   60.04%   48.33%   -11.72%
===========================================
  Files         179      179
  Lines       14523    14523
===========================================
- Hits         8721     7019     -1702
- Misses       4702     6551     +1849
+ Partials     1100      953      -147

Flag
Coverage Δ

acceptance-api
43.12% <ø> (-2.54%)
:arrow_down:

acceptance-apps
36.43% <ø> (+0.17%)
:arrow_up:

acceptance-cli
29.78% <ø> (-25.72%)
:arrow_down:

unittests
8.26% <ø> (ø)

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

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Access to the Standardisation Repository

Hello all,
Alexandre Loire @LoireGalia (Technical Committtee for Standardization – Member) is in the Standardization – Repository.
https://github.com/orgs/catenax-ng/teams/product-standardization?query=Loire
However, he cannot access the repository at the moment.
https://github.com/catenax-ng/product-catena-x-standardization
Could you please help us?

Checked membership of LoireGalia, seems fine.

Since the repository product-catena-x-standardization is set to private, the repository is only accessible if you are logged in to GitHub. So we need to clarify what "no access to the repository" means. How is the repository accessed (WebUI, GIT CLI, etc.)?

Does the problem persist?

Does the problem persist?

I will check it out. I'll get back to you as soon as I have the information.

Any updates on this issue? Otherwize I'd close this issues tomorrow.

Unfortunately, I have not heard from him. Therefore, I would suggest closing the issue.

OK, closing this issue for now. Feel free to reopen or create a new one if the error persist.


Timestamps inconsistent across sources (kibana, logs explorer, events table)

While investigating one can use multiple sources of information but it is very hard to order log messages and events (from events table chronologically, since timestamps differ in value and accuracy.
Execution of Initialization step for instance_id: 096B7C10-78F4-4635-B6EE-F200502CAE89 message: "create provisioner input creator for "4deee563-e5ec-4731-b9b1-53b42d855f0c" plan ID"

Logs Explorer - timestamp: 2023-04-03T13:17:27Z, receiveTimestamp: 2023-04-03T13:17:28.302456543Z,

kibana -  timestamp Apr 3, 2023 @ 13:17:27.341

For second (possibly parallel) execution of Initialization step:

Logs Explorer - timestamp: 2023-04-03T13:17:27Z, receiveTimestamp: 2023-04-03T13:17:28.302456543Z,

kibana -  timestamp `Apr 3, 2023 @ 13:17:32.696

Events:
  {
    "ID": "a0eb3768-d9b6-4d9d-97ef-4214db852f41",
    "Level": "info",
    "InstanceID": "096B7C10-78F4-4635-B6EE-F200502CAE89",
    "OperationID": "df044c63-f3d1-4238-8984-90ba4a04a4ba",
    "Message": "processing step: Provision_Initialization",
    "CreatedAt": "2023-04-03T13:17:27.225448Z"
  },
  {
    "ID": "f7ae3796-e149-4af8-9cf4-367e90c43bf0",
    "Level": "info",
    "InstanceID": "096B7C10-78F4-4635-B6EE-F200502CAE89",
    "OperationID": "df044c63-f3d1-4238-8984-90ba4a04a4ba",
    "Message": "processing step: Provision_Initialization",
    "CreatedAt": "2023-04-03T13:17:27.403207Z"
  },

Issues:

in Logs Explorer timestamp is truncated to the seconds, and logs are not ordered chronologically
timestamps differ across kibana, logs explorer and events table (even taking into consideration that event is persisted earlier than log message is printed)

Hint: contact SRE to customise log scraping configuration and produce timestamps that are not rounded.

Issue should be recreated in KEB repository: https://github.com/kyma-project/kyma-environment-broker. Closing.


Version Update for Visual Studio "16"

We need to address versioning concerns with the next major Visual Studio version ("16", currently our master branch). This proposal outlines our current thinking on what to do to minimize impact to customers and partner teams. Unfortunetely since VisualStudioVersion is revving, even doing nothing will be breaking.
Proposal

File Version: <IP_ADDRESS>432… <IP_ADDRESS>55... etc.  [Completed. Not breaking]

This has already been updated. Should be no negative impact to customers.

Assembly Version: <IP_ADDRESS> [Completed. No change from Dev15]

This will not rev to avoid customer binding redirect impact.
Updating this would have very little positive impact other than to look better.

VisualStudioVersion: 15.0 -> 16.0 [Potential Impact]

Potential impact, but needs to change to keep in sync with the environment variable set by VS.

ToolsVersion: 15.0 -> Current  [Potential Impact]

Changing to 16.0 is a potential break for customer content, so we will have to add "fallback" logic (see below).
Leaving at 15.0 breaks some user imports that may use ToolsVersion where VisualStudioVersion would have been a better choice.
Changing to Current breaks the cycle of having to change on every release.

Install Location: <VSRoot>\MSBuild\Current\Bin\MSBuild.exe    [Definite Impact]

Remaining at 15.0 is already impacting teams internally and will break assumptions.
Changing to 16.0 will impact partner teams (i.e. NuGet).
Changing to Current is better than hard coding a new numeric value that will change next release.
Adding Current to the install path retains relative paths used by MSBuild and others.

Required Actions:

[x] Update MSBuild to use Current
[ ] Update MSBuild fallback logic to reduce breaking change impact.
[ ] Update vswhere example (from 15.0 hard coded to Current).
[x] Update MSBuildLocator
[x] Inform partner teams of the change

Fallback Logic
Customer may be importing $(MSBuildExtensionsPath)$(ToolsVersion). To not cause a breaking change, we will add fallback so that ToolsVerison will resolve to $(MSBuildExtensionsPath)\Current or $(MSBuildExtensionsPath)\15.0. We have an existing mechanism to support this.
Customer Changes
Finding MSBuild (Install Location Change)
Anyone who wants to find MSBuild will need to update. For example:
https://github.com/Microsoft/vswhere#example
Most examples hard code 15.0. This proposal would require them to update to Current to continue to work.
Known examples that hard-code the path:

NuGet
MSBuildLocator (owned by MSBuild team and recommended to find MSBuild)

Installing Targets / Extensions
Anyone who is dropping files into \ … \ $(VS_Major_Version) and importing them as $(ToolsVersion) will continue to work (see fallback), but they should update to use either VisualStudioVersion, Current, or drop the versioning entirely for instanced components (preferred).

I have a PR out now for the first round of changes (#3779).
@jaredpar the Roslyn setup will need to be updated at the same time since it installs to 15.0\... and needs to be changed to Current\....
@rrelyea I assume this will also impact NuGet locating MSBuild?

@rohit21agrawal - can you please dig into our dev branch for the issue Andy raises?

The NuGet side work is tracked here.
https://github.com/NuGet/Home/issues/7325
It should only be NuGet.exe that's impacted.

Not that it is up to me, but can somebody please explain why the assembly version is not updated to Version 16?

ToolsVersion: 15.0 -> Current [Potential Impact]

Changing to Current breaks the cycle of having to change on every release.

This is going to break folks who expect MSBuildToolsVersion to be numerical version.  I don't believe we've ever publicly shipped a value for this that wasn't a numerical version.  Are you sure you want to do this?
Have a look at this github search to get an idea of how many people you're likely to break:
https://github.com/search?l=XML&q=MSBuildToolsVersion&type=Code

@MeikTranel because every time that VS version revs, we end up having to make a non-trivial amount of changes in order to react to that. With the move to current, this then becomes a noop for us.
@ericstj at this point, the change is in and lots of teams have actually spent time reacting to it already. It would not be easy to pull out at this point.

at this point, the change is in and lots of teams have actually spent time reacting to it already. It would not be easy to pull out at this point.

Seems like the sunk cost fallacy.  I'm probably missing the benefit of this breaking change.  It seems to me that we're just trying to hack something that was originally designed to be side-by-side to no longer be side-by-side.

@livarcocc Oh i'm not specifically mad about about the ToolsVersion. I just think it's messed up that the AssemblyVersion is not being moved up to 16? 15->Current is fine in my books... but 15.1 to 15.1 while the FileVersion as the overall version of the release moves to 16 is gonna wreak havoc for everybody trying to wrap their head around MSBuild Versions.

Changing the AssemblyVersion has undesirable downstream effects:

All consumers must update their binding redirects to point to the new version.
It becomes difficult or impossible to write an application that uses the MSBuild API that is compatible with either Visual Studio 2017 and Visual Studio 2019, depending on which is installed on the users machine.

I agree that it's unfortunate to leave the version at <IP_ADDRESS> forever. Ideally it'd rev in a more-understandable way. But since we already have to leave it alone for a full VS release cycle (we can't break binary compatibility in for example the 16.2 update), users must already reason about versions using FileVersion (or, inside the MSBuild language, $(MSBuildVersion) and friends).
On balance, we think leaving the AssemblyVersion fixed has the best tradeoff.

@livarcocc could you have gotten folks to stop using this property to mean "side-by-side" since you now have VS controlling that for you?  It seems to me an equally good fix that would be less breaking would be to ask teams to stop using MSBuildToolsVersion rather than to replace it with a meaningless value.

No, because many of the uses of the property have been baked into user projects via templates.
It's a hard requirement that this (from a template class library) continue to work:
  <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" />

I see, that's a bummer.  I still think you need to evaluate the scope of the break of changing this from a numeric version to a string value.  If I look above it looks to me like you only considered the break that results from changing from 15.0 -> something else.  Perhaps you could special case the comparsion that uses MSBuildToolsVersion so that it could still be treated as a version, but keep the property expansion to treat it as the string "current".

Hopefully this is the right thread.
I just installed Visual Studio 2019 preview, and I'm now facing issues with my build scripts (using cake build). I get the following error:
MSBUILD : error MSB1040: ToolsVersion is not valid. The tools version "15.0" is unrecognized. Available tools versions are "Current".
Switch: 15.0

And this is how I configure the MSBuildSettings in the script:
new DotNetCoreMSBuildSettings
    {
        ToolVersion = MSBuildVersion.MSBuild15
    }

I would like to report the error and, if possible, get indications to fix it (I already tried uninstalling the preview, without success).
The only workaround at the moment is to remove the fixed ToolVersion (leaving it null), but that's not an ideal solution (I always prefer to "pin" versions to be sure that builds run in a predictable way).

The discussion above mentions MSBuildExtensionsPath but it doesn't mention MSBuildUserExtensionsPath. This change looks like it will break the per-user extension mechanism.
MSBuildUserExtensionsPath is in the form C:\Users\[user id]\appdata\local\Microsoft\msbuild so it is shared by all instances of MSBuild on the machine. Changing MSBuildToolsVersion to Current will break existing extensions, and it will also break the ability for per-user extension targets to be versioned by folder.
e.g. ImportUserLocationsByWildcardBeforeMicrosoftCommonTargets from Microsoft.Common.CurrentVersion.targets:
<Import Project="$(MSBuildUserExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.targets\ImportAfter\*" Condition="'$(ImportUserLocationsByWildcardAfterMicrosoftCommonTargets)' == 'true' and exists('$(MSBuildUserExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.targets\ImportAfter')"/>

Per-user extension targets are important to third-party extensions as they allow targets to be injected into the build without requiring elevation (e.g. the Sonar Scanner for MSBuild that provides build integration with SonarQube/SonarCloud);
Could this breaking change be avoided by changing the per-user location to use a different build variable (e.g. either VisualStudioVersion or a new variable)?

Hopefully this is the right thread.
I just installed Visual Studio 2019 preview, and I'm now facing issues with my build scripts (using cake build). I get the following error:
MSBUILD : error MSB1040: ToolsVersion is not valid. The tools version "15.0" is unrecognized. Available tools versions are "Current".
Switch: 15.0

And this is how I configure the MSBuildSettings in the script:
new DotNetCoreMSBuildSettings
    {
        ToolVersion = MSBuildVersion.MSBuild15
    }

I would like to report the error and, if possible, get indications to fix it (I already tried uninstalling the preview, without success).
The only workaround at the moment is to remove the fixed ToolVersion (leaving it null), but that's not an ideal solution (I always prefer to "pin" versions to be sure that builds run in a predictable way).

You're kind of in the right place. But your issue is more with Cake-Build's way of defaulting in their base task library.
You should raise an issue over at https://github.com/cake-build/cake
As for immediate help. Cake offers property override methods for all dotnet/msbuild tasks, so you are definitely able to just pass /p:ToolsVersion="15.0" from outside which effectively does the same thing.
Use this API:https://cakebuild.net/api/Cake.Common.Tools.DotNetCore.Build/DotNetCoreBuildSettings/E83CFC4D

I split out two bugs to consider before 16.0 RTM:

#4150 -- version/numeric comparisons around MSBuildToolsVersion
#4149 -- MSBuildUserExtensionsPath

If you're interested, please give feedback on those ASAP, as the bar for changes in 16.0 is getting higher and higher.
Closing this item (the big change) as completed.


Websocket has removed

I find websocket has removed.
The project will continue to support websocket?

yes, websocket support will be added soon

websocket support has been added to the latest tag v0.0.2


(CMOR) sftof in global_mean for ocean vars

In computing global means of ocean variables for CMOR data, we should actually use the information in sftof (the fraction of a cell covered by ocean). For NEMO this is always 100%, but not necessarily so for other models which might have fractional coverage.

I had a look at this issue in devel/refactor in https://github.com/oloapinivad/ECmean4/pull/59/commits/ff5066104755144b9136b9e6375a1a76421ad615,  introducing an oceanic mask file that can be used if available.
The idea is to use it for oceanic variable if available, but it is not a mandatory requirement to run.
However, it is not possible to fully exploit this functionality since there is a bit of confusion between the "mask" (i.e. which are of the globe needs to be masked) and the "integration domain" (where to perform the integrals): the reference and climatology files use a similar key for very different goals.
For the moment I am happy with the current solution, we might want to revisit in the future, maybe starting from the yml files.