feat(solc): emit additional raw metadata field

Motivation
Closes #1325

Solution
add an additional rawMetadata:String field to artifact output which preserves solc's metadata string

PR Checklist

[ ] Added Tests
[x] Added Documentation
[x] Updated the changelog

Is the unit test failure a flake?

forgot that solc emits empty string for metadata regardless...
improved the json_opt deserialization

The --all-features tests seem to be hanging for some reason..

this is super annoying because for some reason there are no logs available for the job...
perhaps this is due to some hanging request, but testing locally works...

@gakonst after looking at jobs that timed out,
it looks like can_stream_pending_transactions test hangs
https://github.com/gakonst/ethers-rs/runs/6801222172?check_suite_focus=true
ignored it for now until I debugged this on anvil


UVa Online Test TLE 10029 - Edit Step Ladders/main.py

Trying to find an efficient Python solution to pass UVa online test for this problem. I found your provided solution also hit "Time Limit Exceeded".

Hi
You could construct the graph for all the words in the dictionary, connecting those that are one change away from each other, then use Dijkstra to find the longest path. I think the hardest part should be to construct the graph efficiently.

Instead of using Dijkstra's algorithm, I think, your original implementation is better based on the knowledge of the final graph being a DAG. And building a graph adds extra time&space cost to solve this problem. I tried dictionary to record each input word. Every time a new word is read, the "addNewWord()" method calculates the longest edit ladder ending with this word. The time complexity of "addNewWord()" is constant for this problem (at most 2616 + 16 + 2616). So this solution is O(n) complexity. But it still fails on UVa online judge. I don't know how I can speed up this python program.
from collections import defaultdict
import sys

class EditGraph:
    alpha = 'abcdefghijklmnopqrstuvwxyz'

    def __init__(self):
        self.count = defaultdict(lambda : 0)  # Record the number of occurance
        self.ladderLen = defaultdict(lambda : 0)
        self.longest = 0

    def addNewWord(self, word):
        count = self.count[word]
        if count != 0:
            self.count[word] += 1
            self.ladderLen[word] += 1
            self.longest = max(self.longest, self.ladderLen[word])
            return
        else:
            self.count[word] = 1

        preLadder = 0
        # Edit by adding
        for pos in range(len(word)):
            for letter in self.alpha:
                add_str = word[:pos] + letter + word[pos:]
                if add_str < word:
                    preLadder = max(preLadder, self.ladderLen[add_str])
                else:
                    break

        # Edit by deleting
        for pos in range(len(word)):
            del_str = word[:pos] + word[pos+1:]
            preLadder = max(preLadder, self.ladderLen[del_str])

        # Edit by changing
        for pos in range(len(word)):
            for letter in self.alpha:
                mod_str = word[:pos] + letter + word[pos+1:]
                if mod_str < word:
                    preLadder = max(preLadder, self.ladderLen[mod_str])
                else:
                    break
        self.ladderLen[word] = max(self.ladderLen[word], preLadder + self.count[word])
        self.longest = max(self.longest, self.ladderLen[word])

if __name__ == '__main__':
    g = EditGraph()
    for word in map(str.strip, sys.stdin):
        g.addNewWord(word)
    print(g.longest)

Fixed
Changed how transformations are generated to skip the ones that aren't be in lexicographical order.


Deprecate class allocators and deallocators

delete was deprecated in 2.079.  Before the delete keyword can be removed it will be necessary to also deprecate and remove class allocators and deallocators.  They have been planned for deprecation for years; this PR finally puts the deprecation process in motion.
See https://dlang.org/deprecate.html#Class allocators and deallocators
DMD PR:  https://github.com/dlang/dmd/pull/8042

So we recently found @disable new is actually kinda cool....

So we recently found @disable new is actually kinda cool....

Please elaborate.

struct S
{
  @disable new (size_t s) { return null; }
}

void main()
{
	S* s = new S; //  Error: allocator `e.S.new` is not callable because it is annotated with @disable
}

So the application there is you can force users to go through your custom factory functions, or in the case of structs, put them on the stack (or bypass with memcpy lol).

See https://github.com/dlang/phobos/pull/6003 for an example.

I've added support for the syntax @disable new(); to the DMD PR.  You won't even need to add the useless size_t argument.  That should prevent any breaking changes.

That sounds good to me!

That sounds good to me!

Great!  If you don't mind, and truly approve of this PR, please take the explicit step of marking it "Approved".

oh lol i keep forgetting i actually have some power in this repo. I don't have such power over on the dmd side though.

I don't have such power over on the dmd side though.

I still think it's helpful to mark PRs "approved" even in repos where you may not have merge rights.  It helps to know that it was reviewed and scrutinized by anyone with D language skills, especially a veteran like yourself.

Shouldn't this PR remove or mark as deprecated the respective sections in the spec too?
e.g.
https://dlang.org/spec/class.html#allocators

Shouldn't this PR remove or mark as deprecated the respective sections in the spec too?

The spec already states the following for allocators:

Note: Class allocators are deprecated in D2.

... and the following for class deallocators

Note: Class deallocators and the delete operator are deprecated in D2

I remember a brief discussion we had with one of the other deprecations in 2.079 to leave the spec in tact until removal (See https://github.com/dlang/dlang.org/pull/1941#issuecomment-364106970) so users could still refer to it when updating their code.  Therefore, since the spec has already marked allocators and deallocators as deprecated, I think the spec should be left it as is until removal.

Ping!  DMD PR was merged.


Update to latest jclouds release 2.0.1

I shall try to run some tests against this later today

this LGTM, have deployed and tested operation of each of a number of representative entities (Riak cluster, Tomcat 8, Zookeeper ensemble) against each of a variety of clouds (AWS, Azure, Openstack (Bluebox), GCE, and Softlayer); all tests succeeded on all clouds. Will merge this.


Have Webpacker constant output a deprecation message

This change causes a deprecation message to be output anytime a method or constant under Webpacker is called.

@Judahmeek Maybe this can be done right before pushing a v8 with other breaking changes?

@justin808 If I do it right, then it won't be a breaking change.

I understand, but it will be annoying as hell when you have a dependency that is not upgrading. And maybe a breaking performance issue. @Judahmeek

To my understanding, if this PR can bring the same functionality for backward compatibility we already have, it is a much better solution. This requires removing all the existing backward compatibility layers and ensuring everything (typically backward compatibility tests) works as expected.

@ahangarha Justin is right that using relying on method_missing like this likely has high performance costs: https://www.rubyguides.com/2017/06/costs-of-metaprogramming/
And low performance is generally more annoying to debug then an uninitialized constant Webpacker error would be.

I was not expecting such a drop in performance in the case of method_missing!
Interesting!
👍🏾


[rviz_rendering] implement and document replacement for media_export

In rviz in ROS 1, a package called media_export was used in combination with the ROS_PACKAGE_PATH via the rospack C++ API to allow other packages to include resources for Ogre to be used with their rviz plugins.
That code has been commented out in the ros2 port, but we need to find a suitable alternative for ROS 2. Again, this means using ament_index in a similar way as described in https://github.com/ros2/rviz/issues/3, but instead of using it to find one package you would use it to find packages which provide media for Ogre by looking at a different ament index resource, something like rviz_ogre_media_exports or similar. For details on ament index and how it could be used to do this, see resources linked to in https://github.com/ros2/rviz/issues/3.

Let's say we have a package my_rviz_plugin which wants to add a few meshes to rviz. In principle, this means we need to call getResourceLocation(...) from the Ogre::ResourceGroupManager.
The ament_index can provide us with paths to all packages providing a resource. To add our plugin to the list, our plugin will add a file my_rviz_plugin to ament_index/resource_index/rviz_ogre_media_exports/. The real resources would be located somewhere next to the ament_index directory as specified by the ament_index documentation.
Now, we still haven't loaded the resources, we just know where they are. It seems we want to do the following: The my_rviz_plugin file contains a description containing all information of my_rviz_plugin necessary to call getResourceLocation(...) and adding the resources. Rviz can then load the resources at startup time when calling RenderSystem::setupResources().
This would require that the format of the file ament_index/resource_index/rviz_ogre_media_exports/my_rviz_plugin needs to be specified, so that the parsing functionality can be implemented. Simplest solution: The my_rviz_plugin-file contains the relative path to the resource folder. We just add every file (including subdirectories?) as a resource with location type "FileSystem" and resource group of e.g. the plugin's name.
Is this what you have in mind?

@Martin-Idel sorry for not responding, but yes this is exactly what I was thinking. We can provide a cmake macro that packages (like your my_rviz_plugin package) can use to "register a directory" with ogre via rviz.
Reference to the old code, commented out:

https://github.com/ros2/rviz/blob/ca8f42e43ba9eaa6e15434b47906d7580da1c14a/rviz_rendering/src/rviz_rendering/render_system.cpp#L333-L361

@wjwwood No problem.
I had a further look. Here is my suggestion for the interface we want to provide:

The resource type is rviz_ogre_media_exports

There are two alternatives for the macro:

The macro follows the interface in https://github.com/ament/ament_cmake/blob/master/ament_cmake_core/doc/resource_index.md word by word, i.e. we call:
register_package_resource(${PROJECT_NAME} "rviz_ogre_media_exports" CONTENT "../../../${PROJECT_NAME}/ogre_media/meshes" ...) or
the macro is tailored towards rviz: register_rviz_ogre_media_exports(${PROJECT_NAME} DIRECTORIES ../../../${PROJECT_NAME}/ogre_media/meshes)

Furthermore:

I'm inclined to let the user add a list of folders to give the user all flexibility in organising resources but simplifying loading the resource (we don't consider subdirectories)
The macro then registers the resource by adding a file to ament_indes containing the relative paths to all specified folders containing media and copies the media folders to the correct location.

I'll start working on it.


Setting TURI_NUM_GPUS=0 should disable MPS backend

This should simplify testing TensorFlow implementations on Macs (albeit slowly, with CPU-only computation)

Can you also just remove create_tf in compute_context files, which was a work around that exists in master?

Can you also just remove create_tf in compute_context files, which was a work around that's existed in master!

Good idea!

Can you also just remove create_tf in compute_context files, which was a work around that existed in master!

On closer inspection, this is still needed by DC. Since there's no MPS implementation yet, using the normal factory function will usually instantiate the MPS compute context on Macs, and attempting to produce a DC model from the MPS context will fail. (DC in particular should continue to force TF always)


Windows: Enable DPI awareness

I'm not sure if this is the best place to do this (or even the correct way to do this), but this does fix blurry fonts on Windows on displays with scaling factors higher than 100%.
Before (125% scaling factor):

After (125% scaling factor):

Hello,
Interesting. I've read more into the description of what it does and what are the possibilities, and it doesn't exactly seem it's something that this application needs, at least not in this form. Setting anything other than 0 implies the application will actually handle and scale itself based on the DPI setting. 0 means that it won't do that (the current state), so the system rescales everything automatically. A non-zero setting apparently may (unconfirmed) also cause checkboxes to shrink down in size, which would make it harder to click on them, and I guess it'd look ugly too.
The good news is that TkInter apparently has a relatively easy way to scale itself, via the scaling call: https://wiki.tcl-lang.org/page/tk+scaling  The call looks like this: root.tk.call('tk', 'scaling', 1.25), where 1.25 is the factor used to scale everything with, and root would be the main GUI window, found somewhere in the main interface creation flow in gui.py.
Refs I found, might be worth looking into:

https://stackoverflow.com/a/44422362
https://stackoverflow.com/a/74105119
https://stackoverflow.com/a/26539115
https://stackoverflow.com/a/21213145

What do you think? I guess I could get into testing all this, but I'm currently working on #586 and #590, and they're kinda more important than this. If not, I can simply test this at a later date.

Thanks for the answer. The timing of this is a bit unfortunate, though. I just lost access to the testing laptop that had a HiDPI display, so now I'll have to test this on a regular display.... :P

Setting anything other than 0 implies the application will actually handle and scale itself based on the DPI setting. 0 means that it won't do that (the current state), so the system rescales everything automatically

That's what I expected, too, but for some reason, Windows doesn't to scale the fonts automatically, so everything looks blurry. :(
I don't know Windows enough to understand why simply calling SetProcessDpiAwareness(1) is enough to make Windows scale it properly, but this approach seems quite popular. It was even recently added to Python's IDLE IDE to deal with the font scaling issue all Tkinter apps seem to suffer from on Windows.

A non-zero setting apparently may (unconfirmed) also cause checkboxes to shrink down in size, which would make it harder to click on them, and I guess it'd look ugly too.

At least that one I can confirm it doesn't happen (I'm using a 150% scaling factor now because I don't have my testing laptop anymore):

Screenshot

https://wiki.tcl-lang.org/page/tk+scaling The call looks like this: root.tk.call('tk', 'scaling', 1.25)

Maybe I'm just dumb, but that wiki page looks rather complicated. It mentions having to know the physical dimensions of the screen to calculate the DPI correctly:

If you want to set the value correctly, so that an inch or a centimeter given as a Tk distance corresponds to an inch or centimeter on the screen/panel of the monitor, you can only do this correctly when knowing the actual height or with of the screen/panel and the number of pixels in that direction

I tried a naive approach, and simply hardcoded the scaling to 2.0 (with a 150% scaling factor set on Windows):
diff --git a/main.py b/main.py
index 00d536f..a69cfab 100644
--- a/main.py
+++ b/main.py
@@ -87,6 +87,7 @@ if __name__ == "__main__":
     # NOTE: parser output is shown via message box
     # we also need a dummy invisible window for the parser
     root = tk.Tk()
+    root.tk.call("tk", "scaling", 2.0)
     root.overrideredirect(True)
     root.withdraw()
     set_root_icon(root, resource_path("icons/pickaxe.ico"))

The result does not look great (everything still looks blurry, and I had to maximize the window to fit into my non-HiDPI screen):

Screenshot

I guess I could get into testing all this, but I'm currently working on https://github.com/DevilXD/TwitchDropsMiner/issues/586 and https://github.com/DevilXD/TwitchDropsMiner/issues/590, and they're kinda more important than this. If not, I can simply test this at a later date.

It'd be great if you could. This HiDPI territory is new to me. In any case, let me know if/when you can, this is not high priority by any means.

for some reason, Windows doesn't to scale the fonts automatically, so everything looks blurry.
I don't know Windows enough to understand why simply calling SetProcessDpiAwareness(1) is enough to make Windows scale it properly

Maybe I wasn't exactly clear in my original response about this, but as far as I understand it, 1 means that no automatic scaling occurs, and that's why the fonts appear to be not blurry, while 0 makes it so that Windows scales everything, and enlarging the fonts ends up looking blurry. "Makes it work" is only partially correct in that case, as the fonts should be enlarged/scaled by the application with 1 set, to actually follow the scaling setting of the system. Otherwise, simply setting 1 makes the application look the same regardless of the scale set. The decision on whether or not this is what we want is up for debate. That's what I've meant when I said "it doesn't exactly seem it's something that this application needs, at least not in this form" - using 1 would probably fix the fonts, yes, but 1 also expects the application to do the actual scaling instead, which it doesn't do so right now.
The end result should look akin of what the https://stackoverflow.com/a/74105119 shows in it's test and pictures, with window #1 showing the 0 setting, and window #3 showing the 1 setting, after the application does the scaling properly. #2 shows that window size is also something that needs to be scaled, but that's only applicable to fixed-size windows. The miner uses a "flexbox" approach, that automatically expands the window to the size of the window's contents. If the contents are made bigger, the window should resize itself bigger accordingly.

At least that one I can confirm it doesn't happen (I'm using a 150% scaling factor now because I don't have my testing laptop anymore)

That's good then. They'll require scaling just like any other GUI element anyway though.

Maybe I'm just dumb, but that wiki page looks rather complicated. It mentions having to know the physical dimensions of the screen to calculate the DPI correctly
I tried a naive approach, and simply hardcoded the scaling to 2.0 (with a 150% scaling factor set on Windows):

As far I understand it, the description refers to HiDPI displays, and the calculations are done solely to maintain the same physical size of any graphical object (font size for ex.) between a normal and HiDPI monitor. This needs to be taken care of separately from Windows GUI scale. For a normal monitor and the Windows GUI scale only, you're supposed to the scale factor to whatever the scaling factor is currently set in Windows, so for 150% scale, the factor should be 1.5, not 2.0. Not sure where you've got the 2.0 figure from.
I'm still yet to test everything on my side, but this is more or less a backburner issue for now. I'll need to start doing tests myself to push it anywhere.


[BUG] cannot mount fsx in eks

Describe the bug
Cannot mount fsx in eks using a pvc
To Reproduce

create eks cluster [: git::https://github.com/awslabs/idf-modules.git//modules/compute/eks?ref=release/1.11.0&depth=1](path: git::https://github.com/awslabs/idf-modules.git//modules/compute/eks?ref=release/1.11.0&depth=1)
create fsx for lustre path: git::https://github.com/awslabs/idf-modules.git//modules/storage/fsx-lustre?ref=release/1.11.0&depth=1
use integration module to bind them together path: git::https://github.com/awslabs/idf-modules.git//modules/integration/fsx-lustre-on-eks?ref=95a165f483265cefa8b2b749aa129df46a1e8a24&depth=1"

This gives me the error:
Warning  FailedMount       26s (x4 over 29s)  kubelet             MountVolume.MountDevice failed for volume "integration-lustre-on-eks-fsx-pv" : kubernetes.io/csi: attacher.MountDevice failed to create newCsiDriverClient: driver name fsx.csi.aws.com not found in the list of registered CSI drivers
This didnt happen on github.com_awslabs_autonomous-driving-data-framework_release_3.1.0
Expected behavior
mounting fsx works
Screenshots
see error above after running kubectl describe pod

Actually, this was most likely error on my side


"Type ... doesn't have any fields" error on GitHub GraphQL schema.

I am using GitHub's GraphQL API. The following query worked fine with ppx_graphql (the __typename were required though) but it does not work with graphql_ppx_re:
  query issueMilestone($owner: String!, $repo: String!, $number: Int!) {
    repository(owner:$owner, name:$repo) {
      issue(number:$number) {
        id
        milestone { id }
        timelineItems(itemTypes:[CLOSED_EVENT],last:1) {
          totalCount
          nodes {
            __typename
            ... on ClosedEvent {
              closer {
                __typename
                ... on PullRequest {
                  id
                  milestone { id }
                }
                ... on Commit {
                  associatedPullRequests(first: 2) {
                    nodes {
                      id
                      milestone { id }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }

The error is:
Fatal error: exception Graphql_ppx_base__Schema.Invalid_type("Type IssueTimelineItems doesn't have any fields")

Given that it is GitHub's GraphQL schema, I am pretty confident that this is a valid schema.
Since this error looks specific to the handling of union types, I think it is the same as https://github.com/mhallin/graphql_ppx/issues/74.
Is it a bug or a known limitation? Is there a known workaround? Thanks!

When working with union types you only can query on cases and not on whole field. To adjust your example to graphql_ppx_re you only have to remove __typename from the union field. It's added behind scenes as it allows us to parse the result as one of the provided union cases and wrap it into a poly-variant.
Here is an example of a correct query:
module WorkingQuery = [%graphql
  {|
  query issueMilestone($owner: String!, $repo: String!, $number: Int!) {
    repository(owner:$owner, name:$repo) {
      issue(number:$number) {
        id
        milestone { id }
        timelineItems(itemTypes:[CLOSED_EVENT],last:1) {
          totalCount
          nodes {
            ... on ClosedEvent {
              closer {
                ... on PullRequest {
                  id
                  milestone { id }
                }
                ... on Commit {
                  associatedPullRequests(first: 2) {
                    nodes {
                      id
                      milestone { id }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
|}
];

If it doesn't solve your issue please reopen 🙂

@Zimmi48 Added it to the troubleshooting section in README: https://github.com/baransu/graphql_ppx_re#type--doesnt-have-any-fields

Thank you so much for the quick answer! If this hadn't been a migration from ppx_graphql, I would never have manually included this __typename field, and I wouldn't have had any trouble :laughing:


tilebuildoverlay sprite missing "_south" suffix

After trying to use the tile building tool an exception is thrown inside AlignTileAny.Update. Client.Services.Placement.GetDirectionalSprite(string baseSprite) is being used to get the UI sprites but the problem is the UI sprites dont have a direction. In my case the sprite that was trying to be accessed is "tilebuildoverlay_south" which should just be "tilebuildoverlay".

Should the sprite be renamed with a "_south" suffix or should I define a GetSprite function next to GetDirectionalSprite and use it instead?

I created a pull request that fixes this issue on my end.


LibWeb: Avoid crash when animating size property

Avoids falling through to the default switch case and crashing when calculating a size property that is a global keyword like inherit.
Addresses #1762

@AtkinsSJ please have another look when you get a chance.

I think https://github.com/LadybirdBrowser/ladybird/commit/5bdbc34a63d16f954fe4276fbac3af8ba68437d9 might have fixed this same issue since you opened this PR. :sweat_smile: The change looks very similar, it's just done in a different place.

Ok great! I'll close this one then. I learned a bunch digging into the CSS style application lifecycle.


Setting Launch mode to Maximized doesn't maximize

Windows Terminal version
1.14.1432.0
Windows build number
10.0.19044.0
Other Software
No response
Steps to reproduce

Set the Launch mode to Maximized.
Close Windows Terminal.
Start Windows Terminal.

Expected Behavior
The window starts in a maximized state.
Actual Behavior
The window fills the entire screen, but it isn't actually maximized, instead it's in "restored" state. Note in the screenshot below, the system menu has Restore grayed out, but Maximize is available. Likewise in the upper right, the maximize button is visible instead of the restore button.

Just a guess without any basis, but I wonder if this is related to #13158....

I'd bet on this being the same root cause as /dup #13158.


Remote validation without 'reason phrase'

I have two problems with remote validation.

When not valid You have to send 4xx status with reason phrase. My server is not allowing to send reason phrase :/
Even if I could send reason phrase - I can't use polish letters in it like "ąŁź" and so on.

Can You change api to use response's json?

Yes, this change is planned.

I also encounter this issue. @1000hz And BTW could it be possible to display some text (eventually html) on a valid response? Should I open a dedicated issue? Thanks

@kumy this is not possible now, but in the future custom validators will allow returning Promises, which means you could implement your own version of the remote validator that displays your text on success. This is a hard thing to generalize for everyone.

@1000hz When You plan to publish?

I don't know. It's been planned for a long time but other issues keep popping up that take priority. I don't have a lot of time to work on it.

sorry for bother - any news on this?? :)

@1000hz Any news?

It won't be fixed any time soon. Your best bet in the meantime is to fork and change this line:
https://github.com/1000hz/bootstrap-validator/blob/master/js/validator.js#L219 to use textStatus or something else instead of error


Add support for Snowflake database

Coverage decreased (-2.1%) to 30.483% when pulling 3305a44637392bf726e165665bb2a6b18dd5ac19 on mbobrovsky:snowflake-support into 0ae72da4357bd7627eda99602d0139faaf437d06 on snowplow:master.

Coverage decreased (-2.1%) to 30.483% when pulling 3305a44637392bf726e165665bb2a6b18dd5ac19 on mbobrovsky:snowflake-support into 0ae72da4357bd7627eda99602d0139faaf437d06 on snowplow:master.

Thanks @BenFradet - if you could action Ben's feed @mbobrovsky that would be great.

Coverage decreased (-2.1%) to 30.483% when pulling 1d01e5b1c24d7850b61630864106194742c1abd3 on mbobrovsky:snowflake-support into 0ae72da4357bd7627eda99602d0139faaf437d06 on snowplow:master.

@BenFradet am I right in thinking there are still changes for @mbobrovsky to make before you give the green tick?

@alexanderdean nope, just changed to approved

Thanks scheduling.

Hey @mbobrovsky - I started to intergrate this for UA testing before I noticed that Travis is failing:
https://travis-ci.org/snowplow/sql-runner/builds/318704666?utm_source=github_status&utm_medium=notification
The integration test suite is still using Golang 1.6 and 1.7, whereas it looks like the gosnowflake driver is only tested with 1.8 and 1.9:
https://github.com/snowflakedb/gosnowflake/blob/master/.travis.yml
You will need to update your PR so that tests pass (obviously). I've created a couple of tickets for you:

https://github.com/snowplow/sql-runner/issues/112
https://github.com/snowplow/sql-runner/issues/110

To ensure a clean git history, you must add these into your branch before the current Snowflake command.
Does that make sense? Let me know if any questions.

@alexanderdean What exactly should I do? As I undestood you commited changes on #110 , but not on #112 . Also, I can't figure out what branch is it on.
So should I just update my project to this commit with updated golang version and than add all the commits I've made before for snowflake suport?
Please, let me know what branch I should update from.

Hey @mbobrovsky:

Don't worry about my release branch, continue to work in your PR
I want to see three commits in your PR's branch, one each covering #110, #112 and #108
Travis needs to pass

Thanks!

I believe godep update -goversion is what you need as part of #112

Coverage decreased (-2.1%) to 30.483% when pulling 64243fac836b2fce43848f7fdc8da146c3d2375a on mbobrovsky:snowflake-support into 0ae72da4357bd7627eda99602d0139faaf437d06 on snowplow:master.

@mbobrovsky travis passes 👍 , could you rebase so that only 3 commits (corresponding to the 3 issues) are left:

Remove Go versions 1.6 and 1.7 from .travis.yml (closes #110)
Bump Go version to 1.9.2 (closes #112)
Add support for Snowflake database (closes #114)

Coverage decreased (-2.1%) to 30.483% when pulling 716f7b3d54a81f1da45074161c6cfc44990bb330 on mbobrovsky:snowflake-support into 0ae72da4357bd7627eda99602d0139faaf437d06 on snowplow:master.

@BenFradet Did I do right?

Rebase to only 3 commits please

Let's I create a new branch, and then create a new PR, it will be easier

Go for it, closing this one


Generator.return() doesn't account for yield or return inside finally

Currently this code passes, but the .trim() call fails at runtime because the generator actually refused the return and yielded its own value inside the finally block, causing x to be the number 2 instead of the string 'hello'.
function *foo(): Generator<number, void, void> {
  try {
    yield 1;
  } finally {
    yield 2;
  }
}

let f = foo();
f.next();
let x = f.return('hello').value;
x.trim();

TypeError: x.trim is not a function

The definition of Generator is currently:
interface Generator<+Yield,+Return,-Next> {
    @@iterator(): $Iterator<Yield,Return,Next>;
    next(value?: Next): IteratorResult<Yield,Return>;
    return<R>(value: R): { done: true, value: R };
    throw(error?: any): IteratorResult<Yield,Return>;
}

The result of return assumes that the generator doesn't refuse the return using yield or return inside a finally block, and the provided value is what is returned.
To account for a refused return, return can be changed to:
//..
    return<R>(value: R): IteratorResult<Yield,Return|R>;
//..

which accounts for all three possibilities:

The generator does a yield inside the finally block, resulting in {done: false, value: Yield}.
The generator does a return inside the finally block, resulting in {done: true, value: Return}.
The generator accepts the return and the returned value is the one provided, resulting in {done: true, value: R}.

Thanks for the report! I'll take a look...


Investigate why sim build becomes slower

          Investigate why sim build becomes slower

and decrease timeouts

Originally posted by @xxchan in https://github.com/risingwavelabs/risingwave/pull/13731#discussion_r1408997497

Can you filtered only builds on main branch and find which commit cause that?

Since main pipeline is changed, the ci stats doesn't have data for main now. https://github.com/risingwavelabs/buildkite-stats/issues/1
We can try to find the regression from buildkite API. Or git bisect

I guess so. Confirm later.

It's because in https://github.com/risingwavelabs/risingwave/pull/13392, we added --features fail/failpoints for sit, so the build cache cannot be shared

I'll disable those failpoint tests and remove --features fail/failpoints.


fix: replace console.print with console.log

Since console.print() does not exists 😄
Motivation/Description of the PR
Applicable helpers:

[ ] Webdriver

[ ] Puppeteer

[ ] Nightmare

[ ] REST

[ ] Appium

[ ] Protractor

[x] TestCafe

Description of this PR, which problem it solves

console.print() does not exists

A link to the corresponding issue (if applicable).

Type of change

[ ] Breaking changes
[ ] New functionality
[x] Bug fix
[ ] Documentation changes/updates
[ ] Hot fix
[ ] Markdown files fix - not related to source code

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[ ] Lint checking (Run npm run lint)
[ ] Local tests are passed (Run npm test)

@Atinux thanks!


Docker conatiner stuck at Tendermint

After successful docker build, starting a container gets stuck at Tendermint
I[01-20|18:22:24.960] Generated private validator                  module=main path=/tendermint/config/priv_validator.json
I[01-20|18:22:24.960] Generated node key                           module=main path=/tendermint/config/node_key.json
I[01-20|18:22:24.961] Generated genesis file                       module=main path=/tendermint/config/genesis.json
 New Monit id: f6ba29279cdc8aa8cadb7bde94777d1e
 Stored in '/root/.monit.id'
Starting Monit 5.25.1 daemon with http interface at [*]:2812
'1c0df2bd28b1' Monit 5.25.1 started
'bigchaindb' trying to restart
'bigchaindb' restart: '/root/.bigchaindb-monit/monit_script start_bigchaindb /root/.bigchaindb-monit/monit_processes/bigchaindb.pid /root/.bigchaindb-monit/logs /root/.bigchaindb-monit/logs'
'bigchaindb' process is not running
'bigchaindb' process is running with pid 36
'tendermint' start: '/root/.bigchaindb-monit/monit_script start_tendermint /root/.bigchaindb-monit/monit_processes/tendermint.pid /root/.bigchaindb-monit/logs /root/.bigchaindb-monit/logs'

Tried doing Cntrl+C, container does not exit
Tried curl -v http://bigchaindb:9984 & curl -v curl http://tendermint:26657/abci_query, no response

Hardware/Software Specs:

Running bigchainDb - [2.0 Beta 9] - 2018-11-27
MacOS Sierra v10.12.6
Docker Version 18.06.1-ce-mac73

To run BigchainDB, you also must run MongoDB and Tendermint, so we have some Docker Compose stuff to make that easy. See http://docs.bigchaindb.com/projects/contributing/en/latest/dev-setup-coding-and-contribution-process/run-node-with-docker-compose.html

@striveLogic
The current best installation options are:

a docker-all-in-one solution (installs Mongo, Tendermint, python, BigchainDB)
an ansible script that runs nodes either on one machine, or several, and connects them into a network
the manual step-by-step installation
All are available in the "Installation" section of the re-organized documentation http://docs.bigchaindb.com/en/latest/installation/index.html
The "Drivers" section describes the connectors used to send transactions to BigchainDB.


Upgrade to arduino 1.8.1 and add support for Circuit Playground.

This change does 4 things:

Add support for Circuit Playground (32u4 version)
Upgrades to Arduino IDE 1.8.1
Creates an "arduino-headless" script to make it easy to run travis tests with this code.
"Zero" boards are now called "zero-native".

Limitations:

None at the moment. With 1.8.0 the ESP8266 didn't work, not it does.

Tests:

Is passing the travis tests for all of the boards.

PS. Hi form Costa Rica :)

Typo.
Limitations:
None at the moment. With 1.8.0 the ESP8266 didn't work, **now** it does.

I did it not to leave a sneaky line pointing to my repo that could be missued by me if whoever merges doesn't spot it.
I'm actually not sure why the travis check for Adafruit is timing out. You can check the travis checks in my repo, exactly the same code I'm trying to pull-request here.
https://travis-ci.org/fede2cr/travis-ci-arduino/builds


Add UTXO and UTXOW rules for the ShelleyMA eras

This PR may be reviewed commit by commit.
It adds the overloaded rules for the new ShelleyMA (Mary and Allegra) eras.
Where necessary, changes are made to the Shelley ledger to accommodate this:

A few more functions are exported to allow defining scriptsNeeded for the new era.
The UTXOW rule in Shelley is made era-specific to allow for overloading.

A question arises as to how to share the parts of the rule which do not change between eras. The approach I have taken in this PR is to try to follow the spec. So for the UTXO rule, which defined fully in the ShelleyMA spec (with new parts highlighted), I have re-implemented the whole rule in the shelley-ma package. For the UTXOW rule, which is explained in the spec as "The witnessing rule UTXOW does not itself change, but the function validateScript, which it
calls to evaluate the scripts prescribed by scriptsNeeded, does change, including a change to the
arguments passed to it, see", we modify the existing utxoWitnessed rule to take scriptsNeeded as a parameter.

it looks good to me so far! I see all the things I was expecting: checking the interval, no minting ada, checking forge scripts and Value scripts. I see that the minUTxOValue check is using the scaledMinDeposit, which is different from appendix B of the spec, but I do think I remember us saying that we'd not add those new pparams just yet.

FYI, this looks good from the PoV of consensus. I have rebased #1944 locally on this PR and tried it with consensus (using the real eras, not just copies of Shelley!). Everything works, except for the serialisation generators that don't support a different TxBody or Script type yet, which means they can't be used for Allegra and Mary.

Looks good to me also!


Correct the version of maps-common in maps-search-rest

Packages impacted by this PR

@azure-rest/maps-search

Issues associated with this PR
Describe the problem that is addressed by this PR

The version for @azure/maps-common is incorrect. The beta.3 is the next release version, which has yet to exist.

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Parsing arguments in klog is broken

klog(LOG_INFO, "this: %d", 123); prints garbage.
Also, need to change %x modifier to print hex.

That is fixed too. But. We have another bug which creates problems with signed numbers.  Laters!


Documentation URLs direct to 404

Description
The two links I've found for the documentation https://react-native-iap.dooboolab.com/ and https://react-native-iap.hyochan.dev/ both direct to 404.
Expected Behavior
The documentation should open

It is https://react-native-iap.hyo.dev ! Sorry for inconvenience


Bug - Unable to save changes to Profile b/c Password is incorrect.

Description
While logged into the Talent Cloud site, making changes to my Twitter handle, LinkedIn URL and tagline I am unable to save as there is an error message stating that: Current password isn't correct. As I am already logged in and made no changes to my password, I don't know why or how my password could be incorrect.
Technical Info
Device: Laptop
Operating System: MacOs
Browser: Chrome, Version 79.0.3945.79 (Official Build) (64-bit)
Steps to Reproduce
Steps to reproduce the behaviour. Example:

Go to Talent Cloud
Click on About Me
Scroll down to Account Information
Fill in additional details and Save Changes

Interaction is included within the video attached.
Video
Profile.mp4.zip

[ ] Regression test written.

Password is now within settings and the issue looks to be resolved.


Codecept on ARM: How to change browser bin path

What are you trying to achieve?
Trying to run Codecept on a raspberry pi4. All with a very basic setup, no changes to default configuration.
What do you get instead?
The browser crashes on startup, which is probably because the browser codecept default downloads and uses browser that might not be compatible with the ARM versions of those browsers. I have dealt with this situation quite a bit before and wanted to know if there is any way I can point Codecept to a path for the browser that I provide. I tried with all 3 browser alternatives that were available and they were giving similar errors. Below is the error from Firefox and Chromium.
Also, can I decide on NPM install for Codecept beforehand what to install in my system. I just want to make my script work with Chromium for, downloading other browsers isn't viable.
When running with Firefox
root@mymachine:/usr/src/core/codecept# npm run codeceptjs --verbose
npm info it worked if it ends with ok
npm verb cli [
npm verb cli   '/usr/local/bin/node',
npm verb cli   '/usr/local/bin/npm',
npm verb cli   'run',
npm verb cli   'codeceptjs',
npm verb cli   '--verbose'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb run-script [ 'precodeceptjs', 'codeceptjs', 'postcodeceptjs' ]
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
><EMAIL_ADDRESS>codeceptjs /usr/src/core/codecept
> codeceptjs run --steps

CodeceptJS v3.0.2
Using test root "/usr/src/core/codecept"

Wifi connect UI automation --
  ✖ "before all" hook: codeceptjs.beforeSuite for "Testing Wifi Connect captive portal" in 748ms
Error: browserType.launch: Protocol error (Browser.enable): Target closed.
=========================== logs ===========================
<launching> /root/.cache/ms-playwright/firefox-1205/firefox/firefox -no-remote -wait-for-browser -foreground -profile /tmp/playwright_firefoxdev_profile-ijc0N
E -juggler-pipe -silent
<launched> pid=4023
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 1: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: ELF: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 2: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: @8: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 3: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: @@@@0ppp�: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 4: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: �: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 5: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 8�: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 6: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: Syntax error: word unexpected (expe
cting ")")
<process did exit: exitCode=2, signal=null>
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.

-- FAILURES:

  1) Wifi connect UI automation
       "before all" hook: codeceptjs.beforeSuite for "Testing Wifi Connect captive portal":
     browserType.launch: Protocol error (Browser.enable): Target closed.
=========================== logs ===========================
<launching> /root/.cache/ms-playwright/firefox-1205/firefox/firefox -no-remote -wait-for-browser -foreground -profile /tmp/playwright_firefoxdev_profile-ijc0N
E -juggler-pipe -silent
<launched> pid=4023
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 1: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: ELF: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 2: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: @8: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 3: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: @@@@0ppp�: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 4: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: �: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 5: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 8�: not found
[err] /root/.cache/ms-playwright/firefox-1205/firefox/firefox: 6: /root/.cache/ms-playwright/firefox-1205/firefox/firefox: Syntax error: word unexpected (expe
cting ")")
<process did exit: exitCode=2, signal=null>
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.
  browserType.launch: Protocol error (Browser.enable): Target closed.
  =========================== logs ===========================
  <launching> /root/.cache/ms-playwright/firefox-1205/firefox/firefox -no-remote -wait-for-browser -foreground -profile /tmp/playwright_firefoxdev_profile-ijc
0NE -juggler-pipe -silent

  FAIL  | 0 passed, 1 failed   // 770ms
Run with --verbose flag to see complete NodeJS stacktrace
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
npm verb lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/core/codecept/node_module
s/.bin:/root/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
npm verb lifecycle<EMAIL_ADDRESS>CWD: /usr/src/core/codecept
npm info lifecycle<EMAIL_ADDRESS>Failed to exec codeceptjs script
npm verb stack Error<EMAIL_ADDRESS>codeceptjs: `codeceptjs run --steps`
npm verb stack Exit status 1
npm verb stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
npm verb stack     at EventEmitter.emit (events.js:314:20)
npm verb stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
npm verb stack     at ChildProcess.emit (events.js:314:20)
npm verb stack     at maybeClose (internal/child_process.js:1021:16)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd /usr/src/core/codecept
npm verb Linux 4.19.118
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "codeceptjs" "--verbose"
npm verb node v12.19.0
npm verb npm  v6.14.8
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>codeceptjs: `codeceptjs run --steps`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>codeceptjs script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm verb exit [ 1, true ]
npm timing npm Completed in 4670ms

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-12-17T22_57_22_056Z-debug.log

When running with Chromium
root@ea6af1d8fbf8:/usr/src/core/codecept# npm run codeceptjs --verbose
npm info it worked if it ends with ok
npm verb cli [
npm verb cli   '/usr/local/bin/node',
npm verb cli   '/usr/local/bin/npm',
npm verb cli   'run',
npm verb cli   'codeceptjs',
npm verb cli   '--verbose'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb run-script [ 'precodeceptjs', 'codeceptjs', 'postcodeceptjs' ]
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
><EMAIL_ADDRESS>codeceptjs /usr/src/core/codecept
> codeceptjs run --steps

CodeceptJS v3.0.2
Using test root "/usr/src/core/codecept"

Wifi connect UI automation --
  ✖ "before all" hook: codeceptjs.beforeSuite for "Testing Wifi Connect captive portal" in 483ms
Error: browserType.launch: Protocol error (Browser.getVersion): Target closed.
=========================== logs ===========================
<launching> /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome --disable-background-networking --enable-features=NetworkService,NetworkServiceInPr
ocess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-com
ponent-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI,BlinkGenPropertyTre
es,ImprovedCookieControls,SameSiteByDefaultCookies,LazyFrameLoading --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disabl
e-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --pa
ssword-store=basic --use-mock-keychain --user-data-dir=/tmp/playwright_chromiumdev_profile-gZFGj7 --remote-debugging-pipe --no-sandbox --no-startup-window
<launched> pid=4132
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 1: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: ELF: not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 2: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: �Ŭ: not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 3: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: �Ŭ: not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 1: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: �
                                                                                : not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 8: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome:
                                                                                ��@���
[err] �Ŭ
[err] �Ŭ
[err] �@��
          �
           �
            �R�td���
[err] �Ŭ
[err] �Ŭ
[err] �Hl@JlP�td$w�$w�$w�,80,80Q�td���XX/lib64/ld-linux-x86-64.so.2GNU INFOCrashpad�
[err]
     NU�t�y��dBa p � �"�������9@EJOU[jp~����������
                                                  (/7?EKRYbiv��������������
[err] -39@Ghpw�������������
                           $: not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 33: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: �Hl�Hl
                                                                                ������: not fo
und
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 1: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: Syntax error: word un
expected (expecting ")")
<process did exit: exitCode=2, signal=null>
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.

-- FAILURES:

  1) Wifi connect UI automation
       "before all" hook: codeceptjs.beforeSuite for "Testing Wifi Connect captive portal":
     browserType.launch: Protocol error (Browser.getVersion): Target closed.
=========================== logs ===========================
<launching> /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome --disable-background-networking --enable-features=NetworkService,NetworkServiceInPr
ocess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-com
ponent-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI,BlinkGenPropertyTre
es,ImprovedCookieControls,SameSiteByDefaultCookies,LazyFrameLoading --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disabl
e-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --pa
ssword-store=basic --use-mock-keychain --user-data-dir=/tmp/playwright_chromiumdev_profile-gZFGj7 --remote-debugging-pipe --no-sandbox --no-startup-window
<launched> pid=4132
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 1: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: ELF: not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 2: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: �Ŭ: not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 3: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: �Ŭ: not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 1: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: �
                                                                                : not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 8: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome:
                                                                                ��@���
[err] �Ŭ
[err] �Ŭ
[err] �@��
          �
           �
            �R�td���
[err] �Ŭ
[err] �Ŭ
[err] �Hl@JlP�td$w�$w�$w�,80,80Q�td���XX/lib64/ld-linux-x86-64.so.2GNU INFOCrashpad�
[err]
     NU�t�y��dBa p � �"�������9@EJOU[jp~����������
                                                  (/7?EKRYbiv��������������
[err] -39@Ghpw�������������
                           $: not found
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 33: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: �Hl�Hl
                                                                                ������: not fo
und
[err] /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: 1: /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome: Syntax error: word un
expected (expecting ")")
<process did exit: exitCode=2, signal=null>
============================================================
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.
  browserType.launch: Protocol error (Browser.getVersion): Target closed.
  =========================== logs ===========================
  <launching> /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome --disable-background-networking --enable-features=NetworkService,NetworkServiceIn
Process --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-c
omponent-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI,BlinkGenPropertyT
rees,ImprovedCookieControls,SameSiteByDefaultCookies,LazyFrameLoading --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disa
ble-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --
password-store=basic --use-mock-keychain --user-data-dir=/tmp/playwright_chromiumdev_profile-gZFGj7 --remote-debugging-pipe --no-sandbox --no-startup-window

  FAIL  | 0 passed, 1 failed   // 504ms
Run with --verbose flag to see complete NodeJS stacktrace
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
npm verb lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/src/core/codecept/node_module
s/.bin:/root/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
npm verb lifecycle<EMAIL_ADDRESS>CWD: /usr/src/core/codecept
npm info lifecycle<EMAIL_ADDRESS>Failed to exec codeceptjs script
npm verb stack Error<EMAIL_ADDRESS>codeceptjs: `codeceptjs run --steps`
npm verb stack Exit status 1
npm verb stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
npm verb stack     at EventEmitter.emit (events.js:314:20)
npm verb stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
npm verb stack     at ChildProcess.emit (events.js:314:20)
npm verb stack     at maybeClose (internal/child_process.js:1021:16)
npm verb stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd /usr/src/core/codecept
npm verb Linux 4.19.118
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "codeceptjs" "--verbose"
npm verb node v12.19.0
npm verb npm  v6.14.8
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>codeceptjs: `codeceptjs run --steps`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>codeceptjs script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm verb exit [ 1, true ]
npm timing npm Completed in 4375ms

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-12-17T22_59_48_399Z-debug.log

Provide test source code if related

The test file is navigating to google.com, nothing special there.
Details

CodeceptJS version: 3.0.2
NodeJS Version: v12.19.0
Operating System: Debian Buster (armv7hf)
puppeteer
Configuration file:

const { setHeadlessWhen } = require('@codeceptjs/configure');

// turn on headless mode when running with HEADLESS=true environment variable
// export HEADLESS=true && npx codeceptjs run
setHeadlessWhen(process.env.HEADLESS);

exports.config = {
  tests: 'src/*_test.js',
  output: './output',
  helpers: {
    Playwright: {
      url: 'http://localhost',
      show: true,
      browser: 'firefox'
    }
  },
  include: {
    I: './steps_file.js'
  },
  bootstrap: null,
  mocha: {},
  name: 'codecept',
  plugins: {
	retryFailedStep: {
		enabled: true
	},
    pauseOnFail: {},
    retryFailedStep: {
      enabled: true
    },
    tryTo: {
      enabled: true
    },
    screenshotOnFail: {
      enabled: true
    }
  }
}

What version of playwright do you use?

@elukoyanov I am using 1.7.0
Couple of strategies I have explored/yet to explore. What do you think would have the best chance?

Set manualStart=true and write a codecept helper to make sure the right browser is started (Playwright wouldn't like that probably because they are downloading binaries of chromium, rather than debian ARM package of Chromium)
Use the right executable as playwright maintainers mention here https://github.com/microsoft/playwright/issues/2834
Replace the chromium-browser that playwright downloads with the latest chromium Linux_ARM_cross_compile using the build script they provide here

I am going with the 3rd approach.
They also had this issue https://github.com/microsoft/playwright/issues/1243

We tried all 3 ways, can you confirm that there are just 3 objects available for use inside the Playwright API with this I.usePlaywrightTo command.
I.usePlaywrightTo('emulate offline mode', async ({ browser, context, page }) => {
  // use browser, page, context objects inside this function
  await context.setOffline(true);
});

There seems to be no way to access, browsertype.executablePath() API of playwright using codecept.

@elukoyanov Any ideas here? I be to happy to try more things if you can suggest.

@elukoyanov Any ideas here? I be to happy to try more things if you can suggest.

Hey @vipulgupta2048, not sure this is still relevant, as the question is a year old, but I'm posting anyways in case it helps someone. We're also running CodeceptJS on a raspberry pi 4 and I remember struggling with an incorrect path to the browser binary, as well. We ended up just symlinking to the binary that it wanted. This is our Dockerfile:
FROM node:14

LABEL maintainer="Hanna Becker" \
      description="Cosonify CI image" \
      version="0.1.0"

RUN apt-get update && apt-get upgrade -y
RUN apt-get install chromium chromium-l10n awscli -y
RUN ln -s /usr/bin/chromium /usr/bin/chromium-browser    # <-- symlinking to working Chromium binary
[...]

Having said that, it was about half a year ago that we struggled with this, so things may have been fixed by now.

@hanna-becker Thanks for reaching out, I appreciate you mentioning the solution on the thread to help others. Symlinking the binary is a great solution, especially when you start using node-alpine where the location of the chromium binary is different than on ubuntu. We use that as a solution in several places when using puppeteer, especially when building cross-platform applications: https://github.com/balena-io-playground/meetbot/blob/fd6c4619e63210f84bb710d9afea2f6bc370af12/src/browser.ts#L27-L31
This however doesn't help our usecase where path to binaries were pre-determined by the framework (Playwright) and couldn't be changed. Playwright has since changed and works like a charm.


adding keyboards that aren't available at qmk configurator?

Is it possible to add support for keyboards that aren't currently available on the qmk configurator, e.g. smores' clog (https://www.smoresboards.com/product/clog https://github.com/smores56/zmk-config-clog)?

I use qmk configurator to fetch the keyboard layout, that way I don't have to manually create the layout of each keyboard.
See for example this one:

JSON Layout
https://keyboards.qmk.fm/v1/keyboards/basketweave/info.json
{
  "last_updated": "2022-03-26 01:07:21 GMT",
  "keyboards": {
    "basketweave": {
      "keyboard_name": "Basketweave",
      "keyboard_folder": "basketweave",
      "keymaps": {},
      "layouts": {
        "LAYOUT_default": {
          "layout": [
            {
              "x": 0,
              "y": 0,
              "w": 1,
              "label": "Esc",
              "matrix": [
                0,
                0
              ]
            },
            {
              "x": 1.5,
              "y": 0,
              "w": 1,
              "label": "~",
              "matrix": [
                0,
                1
              ]
            },
            {
              "x": 2.5,
              "y": 0,
              "w": 1,
              "label": "!",
              "matrix": [
                0,
                2
              ]
            },
            {
              "x": 3.5,
              "y": 0,
              "w": 1,
              "label": "@",
              "matrix": [
                0,
                3
              ]
            },
            {
              "x": 4.5,
              "y": 0,
              "w": 1,
              "label": "#",
              "matrix": [
                0,
                4
              ]
            },
            {
              "x": 5.5,
              "y": 0,
              "w": 1,
              "label": "$",
              "matrix": [
                0,
                5
              ]
            },
            {
              "x": 6.5,
              "y": 0,
              "w": 1,
              "label": "%",
              "matrix": [
                0,
                6
              ]
            },
            {
              "x": 7.5,
              "y": 0,
              "w": 1,
              "label": "^",
              "matrix": [
                0,
                7
              ]
            },
            {
              "x": 10.5,
              "y": 0,
              "w": 1,
              "label": "&",
              "matrix": [
                0,
                8
              ]
            },
            {
              "x": 11.5,
              "y": 0,
              "w": 1,
              "label": "*",
              "matrix": [
                0,
                9
              ]
            },
            {
              "x": 12.5,
              "y": 0,
              "w": 1,
              "label": "(",
              "matrix": [
                0,
                10
              ]
            },
            {
              "x": 13.5,
              "y": 0,
              "w": 1,
              "label": ")",
              "matrix": [
                0,
                11
              ]
            },
            {
              "x": 14.5,
              "y": 0,
              "w": 1,
              "label": "_",
              "matrix": [
                0,
                12
              ]
            },
            {
              "x": 15.5,
              "y": 0,
              "w": 1,
              "label": "+",
              "matrix": [
                0,
                13
              ]
            },
            {
              "x": 16.5,
              "y": 0,
              "w": 2,
              "label": "Backspace",
              "matrix": [
                0,
                14
              ]
            },
            {
              "x": 0,
              "y": 1,
              "w": 1,
              "label": "Insert",
              "matrix": [
                1,
                0
              ]
            },
            {
              "x": 1.5,
              "y": 1,
              "w": 1.5,
              "label": "Tab",
              "matrix": [
                1,
                1
              ]
            },
            {
              "x": 3,
              "y": 1,
              "w": 1,
              "label": "Q",
              "matrix": [
                1,
                2
              ]
            },
            {
              "x": 4,
              "y": 1,
              "w": 1,
              "label": "W",
              "matrix": [
                1,
                3
              ]
            },
            {
              "x": 5,
              "y": 1,
              "w": 1,
              "label": "E",
              "matrix": [
                1,
                4
              ]
            },
            {
              "x": 6,
              "y": 1,
              "w": 1,
              "label": "R",
              "matrix": [
                1,
                5
              ]
            },
            {
              "x": 7,
              "y": 1,
              "w": 1,
              "label": "T",
              "matrix": [
                1,
                6
              ]
            },
            {
              "x": 10,
              "y": 1,
              "w": 1,
              "label": "Y",
              "matrix": [
                1,
                7
              ]
            },
            {
              "x": 11,
              "y": 1,
              "w": 1,
              "label": "U",
              "matrix": [
                1,
                8
              ]
            },
            {
              "x": 12,
              "y": 1,
              "w": 1,
              "label": "I",
              "matrix": [
                1,
                9
              ]
            },
            {
              "x": 13,
              "y": 1,
              "w": 1,
              "label": "O",
              "matrix": [
                1,
                10
              ]
            },
            {
              "x": 14,
              "y": 1,
              "w": 1,
              "label": "P",
              "matrix": [
                1,
                11
              ]
            },
            {
              "x": 15,
              "y": 1,
              "w": 1,
              "label": "{",
              "matrix": [
                1,
                12
              ]
            },
            {
              "x": 16,
              "y": 1,
              "w": 1,
              "label": "}",
              "matrix": [
                1,
                13
              ]
            },
            {
              "x": 17,
              "y": 1,
              "w": 1.5,
              "label": "|",
              "matrix": [
                1,
                14
              ]
            },
            {
              "x": 19,
              "y": 0.5,
              "w": 1,
              "label": "Mute",
              "matrix": [
                4,
                14
              ]
            },
            {
              "x": 0,
              "y": 2,
              "w": 1,
              "label": "Delete",
              "matrix": [
                2,
                0
              ]
            },
            {
              "x": 1.5,
              "y": 2,
              "w": 1.75,
              "label": "Caps Lock",
              "matrix": [
                2,
                1
              ]
            },
            {
              "x": 3.25,
              "y": 2,
              "w": 1,
              "label": "A",
              "matrix": [
                2,
                2
              ]
            },
            {
              "x": 4.25,
              "y": 2,
              "w": 1,
              "label": "S",
              "matrix": [
                2,
                3
              ]
            },
            {
              "x": 5.25,
              "y": 2,
              "w": 1,
              "label": "D",
              "matrix": [
                2,
                4
              ]
            },
            {
              "x": 6.25,
              "y": 2,
              "w": 1,
              "label": "F",
              "matrix": [
                2,
                5
              ]
            },
            {
              "x": 7.25,
              "y": 2,
              "w": 1,
              "label": "G",
              "matrix": [
                2,
                6
              ]
            },
            {
              "x": 10.25,
              "y": 2,
              "w": 1,
              "label": "H",
              "matrix": [
                2,
                7
              ]
            },
            {
              "x": 11.25,
              "y": 2,
              "w": 1,
              "label": "J",
              "matrix": [
                2,
                8
              ]
            },
            {
              "x": 12.25,
              "y": 2,
              "w": 1,
              "label": "K",
              "matrix": [
                2,
                9
              ]
            },
            {
              "x": 13.25,
              "y": 2,
              "w": 1,
              "label": "L",
              "matrix": [
                2,
                10
              ]
            },
            {
              "x": 14.25,
              "y": 2,
              "w": 1,
              "label": ":",
              "matrix": [
                2,
                11
              ]
            },
            {
              "x": 15.25,
              "y": 2,
              "w": 1,
              "label": "\"",
              "matrix": [
                2,
                12
              ]
            },
            {
              "x": 16.25,
              "y": 2,
              "w": 2.25,
              "label": "Enter",
              "matrix": [
                2,
                13
              ]
            },
            {
              "x": 1.5,
              "y": 3,
              "w": 2.25,
              "label": "Shift",
              "matrix": [
                3,
                1
              ]
            },
            {
              "x": 3.75,
              "y": 3,
              "w": 1,
              "label": "Z",
              "matrix": [
                3,
                2
              ]
            },
            {
              "x": 4.75,
              "y": 3,
              "w": 1,
              "label": "X",
              "matrix": [
                3,
                3
              ]
            },
            {
              "x": 5.75,
              "y": 3,
              "w": 1,
              "label": "C",
              "matrix": [
                3,
                4
              ]
            },
            {
              "x": 6.75,
              "y": 3,
              "w": 1,
              "label": "V",
              "matrix": [
                3,
                5
              ]
            },
            {
              "x": 7.75,
              "y": 3,
              "w": 1,
              "label": "B",
              "matrix": [
                3,
                6
              ]
            },
            {
              "x": 9.75,
              "y": 3,
              "w": 1,
              "label": "B",
              "matrix": [
                3,
                7
              ]
            },
            {
              "x": 10.75,
              "y": 3,
              "w": 1,
              "label": "N",
              "matrix": [
                3,
                8
              ]
            },
            {
              "x": 11.75,
              "y": 3,
              "w": 1,
              "label": "M",
              "matrix": [
                3,
                9
              ]
            },
            {
              "x": 12.75,
              "y": 3,
              "w": 1,
              "label": "<",
              "matrix": [
                3,
                10
              ]
            },
            {
              "x": 13.75,
              "y": 3,
              "w": 1,
              "label": ">",
              "matrix": [
                3,
                11
              ]
            },
            {
              "x": 14.75,
              "y": 3,
              "w": 1,
              "label": "?",
              "matrix": [
                3,
                12
              ]
            },
            {
              "x": 15.75,
              "y": 3,
              "w": 1.75,
              "label": "Shift",
              "matrix": [
                3,
                13
              ]
            },
            {
              "x": 17.75,
              "y": 3.25,
              "w": 1,
              "label": "Up",
              "matrix": [
                2,
                14
              ]
            },
            {
              "x": 1.5,
              "y": 4,
              "w": 1.5,
              "label": "Ctrl",
              "matrix": [
                4,
                1
              ]
            },
            {
              "x": 4.5,
              "y": 4,
              "w": 1.5,
              "label": "Alt",
              "matrix": [
                4,
                2
              ]
            },
            {
              "x": 6,
              "y": 4,
              "w": 2,
              "label": "Space",
              "matrix": [
                4,
                4
              ]
            },
            {
              "x": 8,
              "y": 4,
              "w": 1,
              "label": "Fn",
              "matrix": [
                4,
                6
              ]
            },
            {
              "x": 9.75,
              "y": 4,
              "w": 2.75,
              "label": "Space",
              "matrix": [
                4,
                8
              ]
            },
            {
              "x": 12.5,
              "y": 4,
              "w": 1.5,
              "label": "Alt",
              "matrix": [
                4,
                10
              ]
            },
            {
              "x": 15,
              "y": 4,
              "w": 1.5,
              "label": "Ctrl",
              "matrix": [
                4,
                11
              ]
            },
            {
              "x": 16.75,
              "y": 4.25,
              "w": 1,
              "label": "Left",
              "matrix": [
                4,
                12
              ]
            },
            {
              "x": 17.75,
              "y": 4.25,
              "w": 1,
              "label": "Down",
              "matrix": [
                4,
                13
              ]
            },
            {
              "x": 18.75,
              "y": 4.25,
              "w": 1,
              "label": "Right",
              "matrix": [
                3,
                14
              ]
            }
          ],
          "filename": "keyboards/basketweave/basketweave.h",
          "c_macro": true
        }
      }
    }
  }
}

Should be possible to define a custom layout following that format and pass it as an argument to the program, if anyone is willing to write that file manually I can add that method.
This is the repository holding all the keyboards available: https://github.com/qmk/qmk_keyboards It hasn't been updated in a year, maybe is worth to open an issue to qmk to see if they can update it.

Sure, if it's easy for you to add that method, that might be the easiest thing to do in the short term, and would be very much appreciated. It's probably not going to be feasible to try to upstream every custom board out there to qmk_keyboards

OK, I'm adding a template system to create the custom layouts so it's a bit easier.
This is the template for smore's clog:
keyboard:
  name: The Clog
  mirror: true
  columns:
    - keys: 1
      step: 3
    - keys: 2
      step: 2.5
    - keys: 3
      step: 0.5
    - keys: 3
    - keys: 3
      step: 0.5
    - keys: 4
      step: 0.5
  keys:
    - column: 6
      row: 2
      step: 0.9
      h: 1.7

This is the result of running zmk-viewer generate clog --template theClog.yaml:

I also discovered some bugs in my code parsing clog's keymap file, I'm working on it, this should be the end result:
zmk-viewer generate clog --template theClog.yaml -f clog.keymap

I'll try to release a new version soon with the changes

thanks!!
Does your app show combos on the keymap too?

Not yet, I have to think of a way to represent them. I had thought about coloring the keys, but they can be repeated in different combos so I discarded it.
Maybe the easiest way is to generate an extra image that has all the combos in a list.

I think it'd be better to have it as an overlay if possible. What about representing a combo by coloring (or using dots or dashes) the outline / boundary around the keys? That way you can represent combos with overlapping keys as stacked boundaries / outlines.

Might want to take a look at Ergogen too: they have a similar parametric description of a keyboard.


Is there a way to set network proxy for vcpkg？

Hi @Adam74211,
Assuming you're talking about during the builds of libraries themselves, we currently use CMake to perform the downloads (which uses Curl underneath). Curl can be configured with the HTTP_PROXY and HTTPS_PROXY environment variables such as given by [1].
[1] https://stackoverflow.com/questions/9445489/performing-http-requests-with-curl-using-proxy


Add a binary shim to avoid macOS Cython errors (and likely others)

This closes #64, hopefully. As documented in the PR comments, on macOS we can't just symlink or make a wrapper script to the cross-python launcher because then the resulting python can't be used in the shebang line of other scripts. It has to be a binary. So, I wrote a little Rust program that has the same effect. Took several tries to get it to work right in the face of how the prefix-rewriting is handled, but I can confirm that it helps get conda-forge/tensorflow-feedstock#286 past the initial build issues.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [23]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@ngam OK, done.

The artefacts get uploaded correctly, and are listed and selectable, but downloading fails - never seen that before
@conda-forge-admin, please rerender

@conda-forge-admin, please restart ci

Still not working. Looks like an azure issue TBH, because the artefacts get uploaded correctly...

@isuruf What do you think of this PR, modulo the Azure artifacts issues?

I can't tell if I'm hitting this error or something else with f2py, but I think it's important to get this merged.  What's the current status?

I'm supportive of this PR, but I'm not really comfortable with using rust for this and introducing a heavy dependency like rust early in the stack.

Personally, I want to avoid writing new C/C++ as much as I possibly can, and want to push towards a world where we use Rust for these kinds of systems-level tasks as much as possible. I also expect that we'll be seeing Rust more and more early in the dependency stack (Rust in the Linux kernel, etc.), and think that with the general shift in that direction, issues with bootstrapping are unlikely to arise.
That being said, it's clearly true that in practice the C/C++ toolchain is more "foundational" than Rust right now, and the binary tool here could definitely be done in C. I would rather not rewrite it in C without a specific reason requiring that, but that's a matter of my preferences rather than a technical argument.

The issue is that my rust knowledge is rusty (:smile:) and I don't want to take on the burden of maintaining a rust code base whereas I feel comfortable with C/C++.

I can definitely say that I'll be happy to help work through any issues that may arise, although this program is simple enough that I certainly hope that won't need much in the way of maintenance. Anything else I can do that will help you feel better about the maintenance burden?

Superseded by #66!


Add explanation in storage-files-file-share-management-concepts.md

https://learn.microsoft.com/en-us/azure/storage/files/files-nfs-protocol#performance

@khdownie
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


build errrors

[Enter feedback here]
I tried to build the project and deploy to hololens 2 but I got 16 error such as:
How can I deal with these errors?
Reference rewriter: Error: type System.Web.HttpUtility doesn't exist in target framework. It is referenced from RestSharp.dll at System.String RestSharp.Extensions.StringExtensions::UrlDecode(System.String).
UnityEngine.Debug:LogError(Object)
PostProcessWinRT:RunReferenceRewriter() (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessWinRT.cs:1219)
PostProcessWinRT:Process() (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessWinRT.cs:209)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
Reference rewriter: Error: method System.String System.Web.HttpUtility::UrlEncode(System.String,System.Text.Encoding) doesn't exist in target framework. It is referenced from RestSharp.dll at System.String RestSharp.Extensions.StringExtensions::UrlEncode(System.String,System.Text.Encoding).
UnityEngine.Debug:LogError(Object)
PostProcessWinRT:RunReferenceRewriter() (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessWinRT.cs:1219)
PostProcessWinRT:Process() (at C:/buildslave/unity/build/PlatformDependent/MetroPlayer/Extensions/Managed/PostProcessWinRT.cs:209)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

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

ID: 97b7f65b-2300-1e88-3072-5ecc28e5a8e5
Version Independent ID: 2089610b-9581-ea9b-11c5-7be97e53c584
Content: Getting started with Azure Spatial Anchors - Mixed Reality
Content Source: mixed-reality-docs/mr-dev-docs/develop/unity/tutorials/mr-learning-asa-02.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @jessemcculloch
Microsoft Alias: jemccull

Thanks for the response. Since there are multiple tutorials i want to make sure I'm looking at the correct one. Can you link me to the page of the tutorial you followed

https://docs.microsoft.com/en-us/windows/mixed-reality/develop/unity/tutorials/mr-learning-asa-02
čt 11. 3. 2021 v 15:51 odesílatel pamistel @.***>
napsal:

Thanks for the response. Since there are multiple tutorials i want to make
sure I'm looking at the correct one. Can you link me to the page of the
tutorial you followed
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/mixed-reality/issues/231#issuecomment-796792403,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE5QM5THVK25DC4BM7J5DRLTDDKHTANCNFSM4Y6BH25Q
.

Hi @loleklel
Thank you for the clarification. This tutorial is from the MRTK team. We will reach out and ask them to update it.
In the meantime, could I ask you to try the tutorial  from the ASA Documentation

Please file a support request to follow up, thanks!


Fix missing visualization preview in CB

Pull Request Description
Closes #5639
This PR fixes a regression introduced in #4120, due to which new nodes that were being edited had an empty visualization preview. Now newly created visualization containers do get a default visualization set even before the visualization's input type is set.
https://user-images.githubusercontent.com/117099775/221256294-c87a50da-c8b0-4f00-bf84-f5ae551fca72.mp4
Important Notes

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the
Scala,
Java,
and
Rust
style guides.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed: Enso GUI was tested when built using BOTH
./run ide build and ./run ide watch.

@farmaazon
I checked this PR. Preview visualization is visible now, though its behavior is a bit weird.

I pressed enter, then edited the node by adding argument – it showed panic expected arg1 to be Function but got Function, which is a bit shizophrenic.
I pressed tab and tried typing different arguments. The value in the preview did not change, even after some waiting. Moreover, some values produced the same panic, even though others didn't.

https://user-images.githubusercontent.com/6566674/221581814-c24dab09-3e61-407f-9cce-9b975465e5ff.mp4
This PR is not the cause though, as it happens on develop as well (except it does not show preview on develop).
The reason for such behavior is in our searcher implementation:

We replace the expression with suggestion preview, and sometimes it is left in the code even though the the CB does not have any entries visible. Moreover, the previewed suggestion can be different at different times (perhaps it is caused by different ordering of filtered results when your enter different numbers). Otherwise the preview always shows the default value of index 0, and you can't see a preview of a different index.

QA: accepted, given the said issues are also reproducible on develop.


maps only ?

Browsing through this library, I am slightly confused (doesn't take much) - is this a sidebar for any js app, or is it for maps only ? Is the maps-specific css just so that it can blend in better ?
Also, can panels appear stacked (like a toolbox) rather than tabbed (ie one at a time)
Finally - has anyone got / done / know of a material-theme for the sidebar ?
thanks

is this a sidebar for any js app, or is it for maps only ?

it was written primarily for maps, but in theory you could also use it in a more generic way

Is the maps-specific css just so that it can blend in better ?

yes

can panels appear stacked (like a toolbox) rather than tabbed (ie one at a time)

no, that functionality is not implemented

has anyone got / done / know of a material-theme for the sidebar ?

I don't know of any such theme, but it should be relatively easy to implement using the SASS files


fix new cpu regex

i think this should work

i think this should work

i forgot new commits would be added to the PR

i forgot new commits would be added to the PR


Does not work <com.jmedeisis.draglinearlayout.DragLinearLayout in activty_layout.xml lit red

I added a dependency in gradle but it doesn't help, I spent a few days trying to solve it but it doesn't work for me

I have encountered the same problem.
Running on:
AndroidStudio version: 2021.3
Kotlin plugin version: 213-1.7.20-release-for-android-studio-AS6777.52
Have you solved it in the meantime?

I never found a solution on the new version of android studio

Try to add jcenter() to repositories in Gradle

Try to add jcenter() to repositories in Gradle
Please update library with latest SDK and Gradle plugin
The RepositoryHandler.jcenter() method has been deprecated. This is scheduled to be removed in Gradle 8.0. JFrog announced JCenter's sunset in February 2021. Use mavenCentral() instead. Consult the upgrading guide for further information: https://docs.gradle.org/7.5/userguide/upgrading_version_6.html#jcenter_deprecation


Learn method

The learn method randomly samples n (default value = 100) samples from the memory and uses this minibatch to update the weights.

NOTE:
There is learning in every iteration once the memory has more than n samples

closed by d94c8281261b235b4214b18f203bacbf286fb7ce


Added a functionality for skip and rewind of the video

This is one of the enhancement mentioned in the issues and which is needed for most of the developers.

What is going on ? I've been waiting for this commit to  come live ..... Please ask author to merge....

Hello @Ishu1998  i think the maintainer is in currently active.
but you can use this pull request by adding
"react-native-af-player": "https://github.com/uday5162/react-native-af-video-player"
in your package.json and then npm install

Please update your dependencies to latest version