Could not resolve all dependencies for configuration ':react-native-video:_debugPublishCopy'

Current behavior
Describe what happens when you encounter this issue.
I installed the plugin and linked it too.
but when i run the command react-native run-android
i get this error

What went wrong:
A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugApk'.
A problem occurred configuring project ':react-native-video'.
Could not resolve all dependencies for configuration ':react-native-video:_debugPublishCopy'.
Could not find com.android.support:support-annotations:27.0.0.
Searched in the following locations:
file:/home/rahul/Desktop/androidSetting/extras/android/m2repository/com/android/support/support-annotations/27.0.0/support-annotations-27.0.0.pom
file:/home/rahul/Desktop/androidSetting/extras/android/m2repository/com/android/support/support-annotations/27.0.0/support-annotations-27.0.0.jar
file:/home/rahul/Desktop/androidApp/research/video_streaming_app/android/sdk-manager/com/android/support/support-annotations/27.0.0/support-annotations-27.0.0.jar
Required by:
video_streaming_app:react-native-video:unspecified > com.google.android.exoplayer:extension-okhttp:2.7.3
video_streaming_app:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-core:2.7.3
video_streaming_app:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-dash:2.7.3
video_streaming_app:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-hls:2.7.3
video_streaming_app:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-smoothstreaming:2.7.3
video_streaming_app:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-ui:2.7.3

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

BUILD FAILED
Total time: 46.139 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/getting-started.html
Reproduction steps
A 1, 2, 3, etc. list of what's needed to see the issue happen.
Expected behavior
it should run without any problem
Platform
Which player are you experiencing the problem on:

iOS
Android ExoPlayer
Android MediaPlayer
Windows UWP
Windows WPF

Video sample
If possible, include a link to the video that has the problem that can be streamed or downloaded from.

+1

me too.

Looks like this is related to inheriting the SDK versions from #999. It's causing it to look for the SDK 27 support libraries.
Is it possible to attach the build.gradle from your app (app/build.gradle)? It is supposed to use the versions of the SDK and support libraries you already have, and I want to check if the issue is configuration dependent.
I'll do my best to get this sorted out today.

Ok, issue is that the inheritance didn't work the way I expect. You have to define the variables in a separate file rather than automatically figuring it out using the app/build.gradle. Looks like I will need to revert this PR. Checking to see if there is some way to get this to work real quick.

put maven {   url "https://maven.google.com" }
in your /android/build.gradle
or
Reinstall Android Support Repository from Android Studio

@blok-0 Thanks for pointing that out. I'll see about adding that to the docs.

@cobarx Thanks!
Could not find com.android.support:support-annotations:27.0.0.  -> is the problem
This post help me

I followed all steps, but inevitably I'm still getting:
File C:\Users\Mateusz\.android\repositories.cfg could not be loaded.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugApk'.
   > A problem occurred configuring project ':react-native-video'.
      > Could not resolve all dependencies for configuration ':react-native-video:_debugPublishCopy'.
         > Could not find com.android.support:support-annotations:27.0.0.
           Searched in the following locations:
               file:/C:/Users/Mateusz/AppData/Local/Android/Sdk/extras/android/m2repository/com/android/support/support-annotations/27.0.0/support-annotations-27.0.0.pom
               file:/C:/Users/Mateusz/AppData/Local/Android/Sdk/extras/android/m2repository/com/android/support/support-annotations/27.0.0/support-annotations-27.0.0.jar
               file:/C:/Projects/react-native-starter-master/android/sdk-manager/com/android/support/support-annotations/27.0.0/support-annotations-27.0.0.jar
           Required by:
               Starter:react-native-video:unspecified > com.google.android.exoplayer:extension-okhttp:2.7.3
               Starter:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-core:2.7.3
               Starter:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-dash:2.7.3
               Starter:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-hls:2.7.3
               Starter:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-smoothstreaming:2.7.3
               Starter:react-native-video:unspecified > com.google.android.exoplayer:exoplayer:2.7.3 > com.google.android.exoplayer:exoplayer-ui:2.7.3

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

BUILD FAILED

Total time: 12.725 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/getting-started.html

thanks @mmsmsy your solution its fine for me

me to 🥇

Hi, I am trying like above but still getting this error:
Could not resolve all files for configuration ':app:debugRuntimeClasspath'.

Could not find com.google.android.exoplayer:exoplayer-core:2.9.1.

Here is my android build.gradle code:
`allprojects {
repositories {
mavenLocal()
google()
jcenter()
maven {
url "https://maven.google.com"
}
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
}

}`
Any suggestion ?

This issue is resurfacing now.

@ziyoshams
 maven { url "https://google.bintray.com/exoplayer" } <----- add this line

I replaced node_modules->react-native-video ->android_exoplayer->build.gradle line 32 with this line:
   implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
I hope this help you.

The fix for me was to remove this 'dependency' at react-native.config.js:
dependencies: {
    'react-native-video': {
      platforms: {
        android: { sourceDir: '../node_modules/react-native-video/android-exoplayer' },
      },
    },
  },


General UI improvements and operator tooltips

This is nice.
Only thing about flags, I think the 2 sections they should be stack vertically imo.
This is a bit hard to read flags until you resize the entire editor


del request/response-all-of-modified

Codecov Report

Merging #422 (e8939e4) into main (569be56) will decrease coverage by 0.02%.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##             main     #422      +/-   ##
==========================================
- Coverage   82.76%   82.75%   -0.02%
==========================================
  Files         211      210       -1
  Lines       12336    12232     -104
==========================================
- Hits        10210    10122      -88
+ Misses       1758     1744      -14
+ Partials      368      366       -2

Flag
Coverage Δ

unittests
82.75% <ø> (-0.02%)
:arrow_down:

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

Files
Coverage Δ

checker/rules.go
100.00% <ø> (ø)

:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


Fixed #40: NPE in MockNakadiPublishingClient

Fixed #40: NPE in MockNakadiPublishingClient

:+1:

:+1:


Decouple hook and route dependency for execute module

/run ci

Pull Request Test Coverage Report for Build 1073

16 of 17 (94.12%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 68.023%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/execute/callback/ProxySQLExecuteCallback.java
0
1
0.0%

Totals

Change from base Build 590:
0.006%

Covered Lines:
11415

Relevant Lines:
16781

💛  - Coveralls


Don't use metric_relabel_rules

They don't capture automatic metrics (up, scrape_duration_time, etc.).
As a result, we can't create custom monitors on any of these metrics -
as they don't get es_monitor_type.
We are using metric_relabel_rules as a way to avoid labeling automatic
metrics in some cases (cadvisor/kube_state_metrics), so I've kept these
in place. However, I think it might be better if we just fixed the rules
to handle automatic metrics as it's not obvious. For now I've added a
comment.
For https://github.com/lightbend/es-backend/issues/408

This also illustrates the big gap we have in our testing. We don't test or verify any of our monitors work correctly. Regressions are basically impossible to avoid in this scenario. We should start working on that asap post-1.0.

https://github.com/lightbend/es-backend/issues/271
https://github.com/lightbend/es-backend/issues/286 is a start

I'll think if there's a way we can add this to the smoke tests. Bash is unpleasant though for this kind of more complex testing.

I don't see how this could work, as you need to determine the workload first. monitor type has to come last

the "why use one or the other" is explained here https://www.robustperception.io/relabel_configs-vs-metric_relabel_configs

monitor type has to come last

Ah whoops - yes, I need to fix this for the cadvisor and kube-state-metrics relabeling. That's a pain because they don't currently work with automatic metrics (up, scrape_duration_time, etc.) as-is.

the "why use one or the other" is explained here

Yep, I understand the difference I believe. It's why it's broken for the automatic metrics. It's not super clear to me though why we put them in metric_relabel_config in the first place though. My reverse engineering of it is: so it skips the automatic metrics when extracting the workload in cadvisor/kube-state-metrics relabeling.

I think we have two different usecases:

Pod/service scrapes. Here it makes sense to define es_workload and es_monitor_type in normal relabel rules, since it's prescrape and based on the target info.
cadvisor (kubelet)/kube-state-metrics. The labels come from the /metrics page itself, so we need to handle it in metric_relabel_config.

I fixed it for (1), but inadvertently broke it for (2). So I need to handle case (2).

Okay I fixed the kube-state-metrics. The pod and service rules should be good as is.

Please have another look @dbrinegar.

Yeah we really do need a test for this, and the other monitor bugs we've been finding.
I'm really hesitant to expand the smoketests significantly though - I'm worried about the maintainability of a large bash smoke test suite, especially as we add more complexity.

Going to merge then work on a test.


A Parameter Is Missing in SunrgbdDetectionVotesDataset

Hello.
There may be some mistakes in the initial function of the class SunrgbdDetectionVotesDataset.
You use the test_transductive parameter in eval.py.
https://github.com/Na-Z/sess/blob/653c90df4b39ee550f3e1ae98142e9245a81537e/eval.py#L97-L100
But there is no such parameter in the class SunrgbdDetectionVotesDataset.
https://github.com/Na-Z/sess/blob/653c90df4b39ee550f3e1ae98142e9245a81537e/sunrgbd/sunrgbd_detection_dataset.py#L42-L45
Hope you can fix this issue as soon.
Thanks.

Thanks for pointing out the issue. I have fixed it, please refer to the latest version.


Tables runs first before Inline processor

I made internal page link extention for my site.
syntax looks like this
[[link_name | anchor title]]

It runs well with python-markdown 2.0.3. but in 2.1.1 when i made multiple page link with list, it is converted to table.
for example,

[[link1 | test 1]]
[[link2 | test 2]]

converted to tables not page link.
I thought it was because of OrderedDict, thus i changed extention register code with '_begin'. but it doesn't affect anything.

Yes, block level processors all run before any inline patterns run. That is by design. If you want to introduce a new inline syntax, then you need to make sure it does not conflict with an existing block level syntax. You have a few options:

Alter you syntax so it doesn't look like a table to the parser.
Not use the table extension with your extension.
Fork the table extension and rewrite it so it doesn't conflict.

But there's nothing for me to fix here. I'm closing this wontfix.


Proposal: 'Restrict further searches to this collection' checkbox

Originally on 2011-01-19
(Quoted verbatim from a mail I wrote to the -users list 9 jan 2009)
Hi all,
I have been thinking on a search option, easy to implement, that could benefit a lot current Invenio sites.
As you know, you can start searching an Invenio site at any collection, and the first search is effectively restricted to this collection.  But as soon as you start clicking hyperlinks, the searches are no longer restricted to this original collection.  The current software allows, of course, to restrict afterwards those searches to any collection via the pulldown menu of the list of all collections, but in many installations this list is quite long, and not practical to do more than once or twice.  Adding a '&c=mycollection' to the url is sometimes faster, but we cannot expect to do that to everybody.  And indeed, there are cases that creating such an isolated view of the site is useful and desirable.
The solution I've come up with is to add a checkbox next to the search field with the text Restrict further searches to this collection or similar.  If checked the collection name would be 'sticky' until unchecked again.
I think that it would be relatively easy to implement.  Unfortunately, I cannot do much of it now, except of asking your opinion about it.
What do you think?
Thanks,
Ferran

p=of&c=mycollection will be translated to p=of collection:"mycollection" in 2.1

Collection facets with checkboxes has been added to master (2.2+).


calculate of social_work

Hi.
I have a question about the calculation of social_work.
I think the social_work used to calculate the cost of the generated trajectory candidates is calculated from the social_force and obstacle_force  that calculated in sfm.hpp.
Also, as far as I can see in the program, I think social_force is calculated from the distance between the robot and the pedestrian, but at what timing is this distance?
In other words, the trajectory has a certain length, but I couldn't understand whether it is the distance at the end of the trajectory, the beginning of the trajectory, or a certain point in the middle of the trajectory when I read the program.

Hello,
your question is clearly answered in Line 598 of sfw_planner.cpp.
As you can see, the social work is computed and added for each time step of the trajectory evaluated.
So, please, try to take a look to the code carefully before asking this kind of questions.
Beyond that, I must say that this package is intended for people with knowledge of programming, ROS and its navigation stack. Moreover, Github issues is a tool for tracking the development of the code, indicating possible bugs and next steps in the development. So, this is not the most appropriate place for introductory explanations and guides. The required information is included in the readme page and the code itself.

Thank you.


Error when install jake

I followed the command line at npmjs.org to install the npm, seems that no error and it's installed correctly.
But when I use it install "jake":
sudo npm install -g jake
A window is poped out with these info:
Chris Rorden's NPM  :: April 13 2011 (Debian) CacheMB = 512; Threads used = 8
After I close the window, the error info are printed out in my terminal:
=====================================================
[CRITICAL] os_pager_hide: assertion `OS_IS_PAGER (pager)' failed
(npm:21939): Gtk-CRITICAL **: IA__gtk_widget_hide: assertion GTK_IS_WIDGET (widget)' failed [CRITICAL] os_pager_set_parent: assertion OS_IS_PAGER (pager)' failed
[CRITICAL] os_pager_hide: assertion `OS_IS_PAGER (pager)' failed
if I use "npm config set unsafe-perm true", my installation won't be blocked by those errors and jake is installed.
Is that normal?

You've installed NPM, not npm.  Maybe you followed the instructions that apt-get told you when you typed npm and it wasn't installed?
Do this:
sudo apt-get remove npm
curl http://npmjs.org/install.sh | sh

and then it should work.
See also: http://npmjs.org/doc/faq.html#If-npm-is-an-acronym-why-is-it-never-capitalized


crosscompiling arm yields 'conditional "X86SIMD" was never defined' during configure

Log:
https://travis-ci.org/voidlinux/void-packages/jobs/128457487#L756
2.0.4 builds fine.

Should be fixed now. Reopen if not.

thanks. i'll have a look soon.


Request: more optimized model which can run into low vram gpus

Peace, thanks a lot for your amazing talented work, i was really waiting for this, i hope you add more optimized model which can run into low vram gpus like 8 GiB GPUS 🤞🤞🤞🤞🤞

Thanks. Unfortunately, even our lightest 320x512 resolution/16 frames model will require 11 GB of GPU memory. We will work on optimizing it for GPU efficiency.


Videos / Iframe

I'm aware that xZoom is for zooming into images, but is possible to use xZoom to pull in a video source and display it in the main image section? I'm currently using the gallery and when selecting a gallery thumb nail image I want to pull video which I can play (not zoom of course).

This is just an idea above, but if it isn't possible, please feel free to just close this issue.

I think it is probably possible, but not easy task and cool idea to add video support as native option in the future releases.
I'll try to find a work around with xZoom API to implement video. Will let you know a little later.

Great, thank you. Yeah I think if it had native video support such as youtube videos as well as HTML5 videos, that would be a really neat feature to include. I'm using Fancybox so I'm thinking maybe I can't play a video through the main image source, instead use a preview image of some sort in the main image source area and then open the video in Fancybox maybe? But I'd rather have the user not play it through Fancybox if I can help it.

I was able to use title/caption functionality of xZoom to output video on the page with xZoom. Or another words, title/caption container comes on top of zoomed window inside it and has it's own css class by the way( so you can style it as you wish ) and as title/caption you can use any text or html. So i thought why not to use html code of video then. The only thing left now is to setup proper mouse leave event so to make it close zoom if there is not a video while with video case need to think how would be better to open zoom-video window and close.
(function ($) {
    $(document).ready(function() {
        var xzoom = $('.xzoom, .xzoom-gallery').xzoom({position: "inside", title: true});
        xzoom.eventleave = function(element) {
          //For video we don't need to close on mouse leave, so overwrited this
          console.log('Zoom Close');
        }
    });
})(jQuery);

        <img class="xzoom-gallery" src="low-image.jpg" xpreview="preview-image.jpg" xtitle=''/>

Awesome, that's a nice idea and it works pretty well, the concept is there. But yes if it isn't a video it doesn't close properly. I feel like it's almost there though, needs maybe a type of condition to pick up if it's a video or not (easier said than done though).

Ok, lets say the video will be always the last one in the list. Then we can use the next JS code to determine - are we on the last element right now and not close zoom on mouseleave. In all other cases zoom will be closed:
(function ($) {
    $(document).ready(function() {
        var xzoom = $('.xzoom, .xzoom-gallery').xzoom({position: "inside", title: true});
        var L = $('.xzoom-gallery').length;

        xzoom.eventleave = function(element) {
            //Don't close only on last element
            var index = xzoom.gallery().index;

            if (index < L - 1) element.xon('mouseleave', function(event){
                xzoom.closezoom(event);
            });
        }
    });
})(jQuery);

In case on other than last position for the video we can use index and create condition when to close or not like this example.

This is great thank you, I'm sure this is going to be really handy for someone wanting use videos like myself. The only problem is what if there was more than one video? I'm pulling in images and videos from a database, some of the web pages that are using xZoom will have images and videos and some wont so I have different video conditions I guess. (Sorry I don't think I mentioned this in my last couple of messages.)

In this case, I think we can check does the xtitle attribute of current element have "<iframe" string pattern and then decide to close or not xZoom:
(function ($) {
    $(document).ready(function() {
        var xzoom = $('.xzoom, .xzoom-gallery').xzoom({position: "inside", title: true});

        xzoom.eventleave = function(element) {
            //Don't close if video
            var index = xzoom.gallery().index;
            var title = $('.xzoom-gallery').eq(index).attr('xtitle');
            if (!title || title.indexOf('<iframe') == -1) element.xon('mouseleave', function(event){
                xzoom.closezoom(event);
            });
        }
    });
})(jQuery);

Ah nice, but I can't seem to get this to work, when my mouse is off the video disappears.

            <img class="xzoom-gallery" width="80" src="images/gallery/preview/04_g_car.jpg" title=''/>
            <img class="xzoom-gallery" width="80" src="images/gallery/preview/04_g_car.jpg" title=''/>

(function ($) {
    $(document).ready(function() {
        var xzoom = $('.xzoom, .xzoom-gallery').xzoom({position: "inside", title: true});

        xzoom.eventleave = function(element) {
            //Don't close if video
            var index = xzoom.gallery().index;
            var title = $('.xzoom-gallery').eq(index).attr('xtitle');
            if (!title || title.indexOf('<iframe') == -1) element.xon('mouseleave', function(event){
                xzoom.closezoom(event);
            });
        }
    });
})(jQuery);

Above is all my script, that I used to test it.

Ah, looks like instead of xtitle you are using regular title attribute. In this case JS part must be:
(function ($) {
    $(document).ready(function() {
        var xzoom = $('.xzoom, .xzoom-gallery').xzoom({position: "inside", title: true});

        xzoom.eventleave = function(element) {
            //Don't close if video
            var index = xzoom.gallery().index;
            var title = $('.xzoom-gallery').eq(index).attr('title');
            if (!title || title.indexOf('<iframe') == -1) element.xon('mouseleave', function(event){
                xzoom.closezoom(event);
            });
        }
    });
})(jQuery);

The reason why there is exist xtitle is only when user don't want to popup text on mouse hover on the image as regular title do, but still wants to show the caption when zoom is opened.

Doh! That's me switching computers and projects. Having xtitle makes total sense.
PERFECT!!! Thank you for your time and help, this is what I'm after.

I am unable to get the same thing done with this shared code. Could you please guide me

Probably i should add this as an example to https://github.com/payalord/xzoom-sandbox later today.


Footer extends past page on small screens

The footer will extend to the right of the viewport on a small screen, creating a scroll bar. The icons are displayed over a blank background.
This can probably be fixed by enabling wrapping in the flex container but will need to replace the current spacing hack with a better method

Taken care of in layout-style branch

Merged in #115


The rest of the endpoints

This PR sets up the rest of the endpoints.
Things to note:

BlockgroupsEl, and Neighborhoods both don't exist as tables yet and,
Zoning looked strange once setup at /zoning

@hassanshamim do you have an idea why this is failing?

Embarrassingly I think I have a pretty good idea - looks like I failed in my promise to setup the appropriate env vars in Travis, so the Test.sh script didn’t have a value for DOCKER_SERVICE.
(FYI, in case you hadn’t looked, check the Travis build linked above/below - or here - around lines 848-879 of the job log. That output reads to me like the script failed to execute.
I’m in a cab, heading to hotel. I’ll get in and setup the env vars (including the AWS creds that will later be needed in the Travis job to upload the tested container to AWS) once I hit the hotel.

Well gents, there's a problem I don't know how to solve: even with all the correct env vars setup in Travis, the test.sh script bails with this error:
Using existing test database for alias 'default'...
Got an error creating the test database: permission denied to create database

Now, the creds we use for each of the databases are privileged for the database associated with the project, but the creds do not have permission to create arbitrary databases.  We've run into this with one of the other projects - @nam20485, was that with yours?  I don't recall what the current workaround is for that - we'd discussed a couple of scenarios, but I've lost track of where we landed on that.

Using existing test database for alias 'default'...
Got an error creating the test database: permission denied to create database

@MikeTheCanuck This is not a problem, it is actually expected with the current code.
What you are running still has the old unit testing command that requires write access to the DB. @BrianHGrant has found a better solution and created an issue to explain it here: hackoregon/backend-examplar-2018/issues/82
I also have implemented his suggested pattern in hackoregon/disaster-resilience-backend. It seems to work well:

It runs the 4 example unit tests I have in my project without requiring any modification to my existing unit tests or structure. (This probably means that we can drop it in to the other existing backend repos and it will automagically work with any unit test cases or structure already present)

It does not require write access, so it will effectively test the Django app and API endpoints against a DB connection that offers only read-only access. (I have implemented it and tested it on: https://travis-ci.org/hackoregon/disaster-resilience-backend/builds/380495740, where it connects to the new disaster-resilience DB instance you created for me that allows only read-only access) You can see the log of it completing successfully in the travis project)

Given our current lack of a suitable unit testing solution, I think that we should discuss whether we all can agree on going with this solution, or why not, and if so, create a PR against hackoregon/backend-examplar so we can include it.


load wasm that build with golang

Thanks for the bug report!
Describe the bug
when I build wasm with go and wasm.NewInstance from the wasm bin, error result with:
Failed to compile the module.

A clear and concise description of what the bug is.
Steps to reproduce

build wasm with go
GOARCH=wasm GOOS=js go build -o wa.wasm wa.go
cat wa.go:

package main

//export Sum
func Sum(x, y int) int {
	return x + y
}

func main() {
}

build go program
go build main.go
cat main.go:

package main

import (
	"fmt"
	wasm "github.com/wasmerio/go-ext-wasm/wasmer"
)

func main() {
	bytes, err := wasm.ReadBytes("wa.wasm");
	if err != nil{
		fmt.Println(err);
		return
	}
	inst, err := wasm.NewInstance(bytes);
	if err != nil{
		fmt.Println(err);
		return
	}
	defer inst.Close();

	sum := inst.Exports["sum"]

	result, err := sum(5,37);
	if err != nil{
		fmt.Println(err);
		return;
	}
	fmt.Println(result);
}

Run

./main

See error
Failed to compile the module.

This is likely to be happening because some of the required imports are not present.
We probably need to improve the error message to show the detailed error.

Thanks for the bug report!
Error messages are already better in the next runtime release, see https://github.com/wasmerio/wasmer/pull/467/files.
However, maybe you can find a better definition with wasm.GetLastError. I tried with the following code:
package main

import (
	"fmt"
	wasm "github.com/wasmerio/go-ext-wasm/wasmer"
)

func main() {
	bytes, err := wasm.ReadBytes("wa.wasm")

	if err != nil {
		fmt.Println(err)
		return
	}

	inst, err := wasm.NewInstance(bytes)

	if err != nil {
		fmt.Println(err)
		fmt.Println(wasm.GetLastError())
		return
	}

	defer inst.Close()
}

Then I run it with go run main.go and got:
Failed to compile the module.
7 link errors: (1 of 7)
Import not found, namespace: go, name: runtime.wasmExit (2 of 7)
Import not found, namespace: go, name: runtime.wasmWrite (3 of 7)
Import not found, namespace: go, name: runtime.nanotime (4 of 7)
Import not found, namespace: go, name: runtime.walltime (5 of 7)
Import not found, namespace: go, name: runtime.scheduleTimeoutEvent (6 of 7)
Import not found, namespace: go, name: runtime.clearTimeoutEvent (7 of 7)
Import not found, namespace: go, name: runtime.getRandomData <nil>

I suggest to use NewInstanceWithImports but imported function are declared in the  env namespace, not in the go namespace. That's a missing feature currently.

See #29 to see how to import functions in multiple namespaces.

Hi @Hywan can you provide a quick example how to import functions into multiple namespaces?
Like the parent, I tried running a go-compiled "hello world" wasm, and I get the following:
instance  Failed to compile the module. 18 link errors: (1 of 18) Import not found, namespace: go, name: debug (2 of 18) Import not found, namespace: go, name: runtime.wasmExit (3 of 18) Import not found, namespace: go, name: runtime.wasmWrite (4 of 18) Import not found, namespace: go, name: runtime.nanotime (5 of 18) Import not found, namespace: go, name: runtime.walltime (6 of 18) Import not found, namespace: go, name: runtime.scheduleTimeoutEvent (7 of 18) Import not found, namespace: go, name: runtime.clearTimeoutEvent (8 of 18) Import not found, namespace: go, name: runtime.getRandomData (9 of 18) Import not found, namespace: go, name: syscall/js.stringVal (10 of 18) Import not found, namespace: go, name: syscall/js.valueGet (11 of 18) Import not found, namespace: go, name: syscall/js.valueSet (12 of 18) Import not found, namespace: go, name: syscall/js.valueIndex (13 of 18) Import not found, namespace: go, name: syscall/js.valueSetIndex (14 of 18) Import not found, namespace: go, name: syscall/js.valueCall (15 of 18) Import not found, namespace: go, name: syscall/js.valueNew (16 of 18) Import not found, namespace: go, name: syscall/js.valueLength (17 of 18) Import not found, namespace: go, name: syscall/js.valuePrepareString (18 of 18) Import not found, namespace: go, name: syscall/js.valueLoadString <nil>
Any help would be appreciated.

when I run the exmple, error result with:
$./main
Failed to instantiate the module:
    error instantiating
 <nil>

please, how to run the example successfully?

You can check https://github.com/wasmerio/go-ext-wasm/blob/722faa9f1b902d404e87c40ea2bb6bdd5e228a51/wasmer/test/imports.go#L36-L52.
Basically, it looks like:
imports, _ :=
	wasm.NewImports().
		Namespace("env1").
			Append("f", f, C.f).
			Append("g", g, C.g).
		Namespace("env2").
			Append("h", h, C.h)

instance, _ := wasm.NewInstanceWithImports(wasm_bytes, imports)
…

Does it help?

is it not possible for wasmer to parse out the imports when it reads the bytes and creates the instance? our nodejs version is able to load our wasm bytes just fine..

It is possible to read the imports and exports from the module. Check the Module structure:
type Module struct {
    Exports []ExportDescriptor
    Imports []ImportDescriptor
}

Hello, I am new to wasm and just trying out wasmer go-ext-wasm. Getting the same one
            8 link errors: (1 of 8) Import not found, namespace: go, name: debug (2 of 8) Import not found, namespace: go, name: runtime.wasmExit (3 of 8) Import not found, namespace: go, name: runtime.wasmWrite (4 of 8) Import not found, namespace: go, name: runtime.nanotime (5 of 8) Import not found, namespace: go, name: runtime.walltime (6 of 8) Import not found, namespace: go, name: runtime.scheduleTimeoutEvent (7 of 8) Import not found, namespace: go, name: runtime.clearTimeoutEvent (8 of 8) Import not found, namespace: go, name: runtime.getRandomData
And I see that the issue is closed with that example:
imports, _ :=
	wasm.NewImports().
		Namespace("env1").
			Append("f", f, C.f).
			Append("g", g, C.g).
		Namespace("env2").
			Append("h", h, C.h)

instance, _ := wasm.NewInstanceWithImports(wasm_bytes, imports)

But I am still not sure how does this help? What are these and where they are coming from?
Namespace("env1").
			Append("f", f, C.f).
			Append("g", g, C.g).
		Namespace("env2").
			Append("h", h, C.h)

Is there anything specific that we need to do before running Go? Tried tinygo and go, both have slightly different errors :|

The Go compiler emits a WebAssembly module with specific host functions (imports). It is very JavaScript centric.
The TinyGo compiler emits a WebAssembly module that works for JS but also other hosts, like a server.
See #95, which is likely to help.
One question though: What's your usecase to compile Go to Wasm, to then run it in Go?

Currently writing a side project for my other side project (https://webhookrelay.com/) that will allow users to upload their wasm code snippets to modify webhooks before they are forwarded to their final destination. Initially started just with Lua but wasm seems so much more interesting, therefore after some time I decided to try out wasmer :)
For example to modify webhook method when it comes as a PUT request to POST:
extern "C" {
    fn ext_set_request_method(ptr: *const u8, len: usize);
}

#[no_mangle]
pub extern fn handleRequest(_ptr: i32, _len: i32) {

    let method = "POST";
    unsafe {
        ext_set_request_method(method.as_ptr(), method.len());
    }
}

As a Go developer myself I would prefer using Go, although Rust is also fun, not sure about other people though :)

@Hywan Hello! So if I understand correctly there's no way to import a .wasm file that was compiled from Go. Is that right?

@danlaine It is possible, but it requires some jugglery. Take a look at https://github.com/wasmerio/go-ext-wasm/pull/95 for an attempt to simplify this.


Read MOSMIX/SYNOP station names from Stationslexikon

i.e. JSON response for station "dwd_station_id": "00379"
"station_name": "BERKA, BAD (FLUGPLAT"

please not this effort ;-) i thought it was an error in the translation of the MOSMIX data


Update docs pipeline

Overview
Updates the docs binary pipeline to clean the checkout folder on every run. In tests, this appears to have mitigated our previous failures.

/azp run


Slate Analytics 404

This repo is currently on low maintenance. See README for details
Problem
Shopify's Slate Analytics has been disabled/broken/shut down which causes recurring 404s when using Slate.
Replication steps

Install Slate v1 or use an existing Slate v1 project

If not using an existing project create a new project

Run watch or start

✔  Compiled successfully in 1.259s!
(node:50840) UnhandledPromiseRejectionWarning: Error: Request failed with status code 404
    at createError (/Users/username/slatedirectory/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/Users/username/slatedirectory/node_modules/axios/lib/core/settle.js:18:12)
    at IncomingMessage.handleStreamEnd (/Users/username/slatedirectory/node_modules/axios/lib/adapters/http.js:202:11)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1064:12)
    at _combinedTickCallback (internal/process/next_tick.js:139:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)
(node:50840) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)

★  You are editing files in theme 123456789 on the following store:

      https://myshopifystore.myshopify.com?preview_theme_id=123456789

More Information
Because the analytics service has been disabled/broken/shut down, the 404 can be patched by disabling the Axios post in<EMAIL_ADDRESS>As always this patch will only last until you install a project dependency or update project dependencies.

Thanks @curiouscrusher
@t-kelly What's the word here? Noticed this issue starting this morning. Will there be a patch provided?

The internal Kafka service I was using for Slate analytics has been shut down. Will open a PR to remove this and the consent form that users agree to when installing Slate.
These analytics have been really helpful, showing 2500+ weekly active users running Slate. This ultimately helps add fuel to fire of getting Slate/developer tooling prioritized. Thanks all!

Great to hear there's some solid numbers behind Slate usage, thanks for the insight there @t-kelly!
Looking forward to the patch and hopefully increased project priority 🤞

In the meantime you can silence these errors by updating your<EMAIL_ADDRESS>file to suppress errors on line 95:
return axios('https://v.shopify.com/slate/track', axiosConfig).catch(() => {});

In the meantime you can silence these errors by updating your<EMAIL_ADDRESS>file to suppress errors on line 95:
return axios('https://v.shopify.com/slate/track', axiosConfig).catch(() => {});

Similarly useful fix;
return new Promise(resolve => resolve(true));

@t-kelly If you have a chance to look at #1078 it may be a quick win to clear up the 404 issues.

I suspect due to Slate's end of support, folks will be experiencing the same error above. Commenting the following line of code from<EMAIL_ADDRESS>return axios('https://v.shopify.com/slate/track', axiosConfig);

In case this is of any use to people, I solved this issue by creating a script that I run on "postinstall" in my node_modules.
#!/bin/bash

function clear-slate-analytics() {
  rm<EMAIL_ADDRESS>  touch<EMAIL_ADDRESS>  echo "async function init(){}function event(n,t){}module.exports={init:init,event:event};" >><EMAIL_ADDRESS>}

clear-slate-analytics

That last line just replaces all the functions with a no-op.

Hey i cant find @shopify in my node_modules can anyone help?

@rafaelfranca what does ls node_modules/@shopify output?
If nothing than it’s most likely you aren’t using a recent version of Slate (before deprecation).

I created a fork for slate-tools with this error fixed. If you wanna use it do this:
yarn add peanut-butter-co/slate-tools#1.0.0-beta.20


CollapsingHeaderWithScrolldemo doesn't work in 0.45.1

Trying out CollapsingHeaderWithScroll demo, but it just doesn't work in Android with RN 0.45.1. All of the elements are rendered correctly, but the header doesn't collapse.
Any ideas?

Same problem.

Same issue, not working: header do not collapse
react-native: "0.48.4"

I am closing the issue as a part of an effort to cleanup and revive the project. If this issue persists after v1.0.0, you are more than welcome to reintroduce the issue.
Thanks for your contribution.


Linking a phone number with extension in Android is not working.

Linking a phone number without an extension works without any issues.
However, when an extension is added, it is not showing up in the Android Phone app. It only shows phone number only. For example, the following code will open a phone app with only 1<PHONE_NUMBER>.
Linking.openURL('tel:12345678900,1111')
Is it an Android bug? Can this be fixed in React Native?
Thanks.

This is not a react-native bug. You can't use , or p in Android Dial Intent URI. Look at this, maybe you will find a workaround.

@facebook-github-bot answered


Add support for only-one-when step check, issue #255

Add tests and supporting feature files
Add only-one-when.js to implement feature
Add entry to README

Split from #254 / #307

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 97.071%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
776

Relevant Lines:
789

💛  - Coveralls

Do we know when/how this setting will be deployed to npmjs?


Fix typo

:+1: Thank yoooou! ;)
Seriously, thanks for the PR! I'll merge this later unless someone beats me to it. (gotta leave right now and I tend to wait for the travis thumbs up even though this case is trivial)


[BUG]Write out file will not success and no error throwed (because the tmp file name is too long)

I've found this BUG under Windows 7 64bit, stripping out the raw shell command (manual piece together):
phantomjs "E:\\Program Files (x86)\\nodejs\\node_modules\\manet\\src\\scripts\\screenshot.js" "eyJ1cmwiOiJodHRwOi8vengyNTBsb2NhbC5jb206MzAwMC9tYWdpY3Blbi9hcHAvIy9tYWluL2luZGV4P2l0ZW1MYXlJZD0zJnNuYXBzaG90PTEmX19hPTk2QjcxRDkyOEJFRTM4NkUxMTA2MjFCRUIzN0RGRkYyIiwiZm9ybWF0IjoicG5nIiwid2lkdGgiOjE5MjAsImhlaWdodCI6MTA4MCwic2VsZWN0b3IiOiIjbWFpbi1hcmVhIn0=" "C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\yJ1cmwiOiJodHRwOi8vengyNTBsb2NhbC5jb206MzAwMC9tYWdpY3Blbi9hcHAvIy9tYWluL2luZGV4P2l0ZW1MYXlJZD0zJnNuYXBzaG90PTEmX19hPTk2QjcxRDkyOEJFRTM4NkUxMTA2MjFCRUIzN0RGRkYyIiwiZm9ybWF0IjoicG5nIiwid2lkdGgiOjE5MjAsImhlaWdodCI6MTA4MCwic2VsZWN0b3IiOiIjbWFpbi1hcmVhIn0=.png"

this command will run successfully with no extra exceptions, but the temp file will not be writed, so when visit manet, manet will send 404.
searched, linux && windows both have the file name length limiting, so we should keep the temp file name's length, and add a prefix word + a random word + timestamp is well.
at manet/src/capture.js Line 18, i modified:
function outputFile(options, conf, base64) {
    var format = options.format || DEF_FORMAT;
	//zcs=>The base64's length is too long for a file name, so we should fix the length
	var filename = 'manettemp_' + (base64 + '').substr(-20) + '_' + Date.now() + '_' + Math.floor(Math.random() * (999999 - 100000) + 100000);
	//<=zcs
    // return conf.storage + path.sep + base64 + '.' + format; //zcs=old line
	return conf.storage + path.sep + filename + '.' + format;
}

Has anyone done any work with this? Just hit same problem, and it's a show stopper for using Manet with our app - which is sad because this is otherwise a GREAT app. Found this: https://github.com/dbushell/grunt-svg2png/issues/17 - https://github.com/dbushell/grunt-svg2png/pull/25 , not sure if helpful?

@sgates as I mentioned above, u could rename the file name in your way as a temporary solution for the problem

@ppoo24 yeah, I think I'm going to go ahead and do that. Tried with a simple MD5, I think it'll work for me. Not too worried about Manet caching since I will be caching myself and only using Manet for fresh pulls. Thanks for the advice!

I ran into this issue on Linux as well. Rather than MD5 (due to collisions) or Base64 (due to length), would UUID v4 be a better option? They're more unique than MD5, shorter than Base64, and have a collision probability of ~50% if one billion of them were created every second for 100 years which would surely be unique enough for cache purposes I would think. There's a Node library for generating them.

There's always SHA-1 or SHA-2. SHA-1 hasn't had any collisions yet as far as I can tell.

Fixed here: https://github.com/vbauer/manet/pull/39
Solution with database could be implemented a little bit later.


Support Laravel 5.2

Laravel 5.1 deprecated using bindShared and 5.2 removed it completely, because of this a package update to cocur/slugify is needed to at least 1.4. orchestra/testbench 3.0 only supports Laravel 5.0.* so that requires an update as well.
Illuminate\Foundation\Composer has been moved to Illuminate\Support\Composer

The failed test is because of PHP 5.4 which isn't supported by Laravel 5.2 so the change in the Composer class location throws an error.
@cviebrock would you be okay with me updating composer and travis to remove PHP 5.4?

Dropping PHP 5.4 would also mean increasing the minimum Laravel version to 5.1 (which requires PHP 5.5.9 or above).

Actually, it's going to increase Laravel to 5.2 anyway isn't it, because it requires the Composer class in that location. Duh.

@EspadaV8 I saw this commit from another repo:
https://github.com/laracasts/Laravel-5-Generators-Extended/pull/83/files
That would (allegedly, since I haven't tested it) make it work on both 5.1 and 5.2 (including the things you proposed)

That requires use of the global app function. Does this package mind requiring that? It would also be possible to inject the Container class and use that to resolve the Composer class instead of using the global function,

@EspadaV8 agreed! Let the what @cviebrock thinks :santa:

Just had a look at the support report and it doesn't contain the Container class so either was the package would need to be updated with (I'm guessing) foundation added as a requirement. (on my mobile so can't check easily).
I would probably recommend tagging a final 0.1x release and then release a new 0.2x for L5.2 and up.

Hmm, okay, so the Container can't be injected because Commands don't get passed through the IoC and only SluggableMigrationCreator and an instance of Composer get passed in.
Using app()['composer'] works, but I'm not a great fan of using the global function.
What can be done though, is to remove the second parameter from the constructor and then use func_get_arg(1) to get the composer instance. I'm still not a great fan of this approach either.

@EspadaV8 So should we change the namespace on a new release or using func_get_arg?

This PR looks good, but probably warrants a version bump.  Let me take a look it all more closely in the next few days.
I wanted to do a major refactor of things for the next version, but I might not get to that in time, and I don't want to make things unusable for Laravel 5.2 users.

We should have a branch for 5.2 or using IoC for resolving Composer so that it can be compatible with 5.*

So, I think there are now several items that need resolving for 5.2 compatibility.
First is the composer issue.  Is there an injection we could make for Composer that works in 5.1 and 5.2? If so, let's use that.  If not, I'd almost be tempted to just entirely remove the use of composer in that class, and not do the ->dumpAutoloads(), rather than come up with version-specific workarounds.
Second issue is the bindShared vs singleton. If we can just upgrade cocur/slugify to 1.4, then that's fine with me.
Finally, updating workbench and travis to support 5.2.  It doesn't look like we can do this and make things compatible with 5.2 and earlier 5.* versions, does it?  So, probably a new branch (and major version bump) are going to be needed anyway.
Sometime this holidays, I'll deal with it.  :)

Try the 3.1.4 release.
I removed the composer reference to make it compatible with Laravel 5.2, and fixed composer.json so that it should work with all 5.x versions.

Como puedo desinstalar la version mas reciente de Sluggable para instalar la version 3.1.4

Don't use 3.1.4. Use 4.0.1 now.


"Disable Telemetry" Tweak Causes Crashes with Full-screen Applications

After rebooting to apply "Disable Telemetry" tweak, full screen applications (games) will misbehave. The FS app will repeatedly "flicker" causing the desktop to momentarily become visible. In a multi-monitor setup you can see the app's taskbar icon shift to the end as if it were the last app started, even if it wasn't (the icon shifts as if the app were momentarily closed then rapidly restarted. It will continue doing this sliding motion concurrent with the "flickers"). ALT-TAB'ing out of the app will cause it to freeze and crash.
I have experienced the issue with:
Steam Big-Picture
Sekiro (No flicker, ALT-TAB crash only)
Honkai 3rd Impact
Genshin Impact
Disabling Telemetry successfully reduces process count significantly and can be reversed by system restore. Bloated processes and FS app functionality restored upon system restore.
Only Telemetry Tweak caused instability from "Desktop" selection in Tweaks section.
Video of the Flickering:
https://www.youtube.com/watch?v=coqkDNgc0NM

I wanted to investigate more because i have the same issue and wanted to see if the cause were other options as well. It happened after ive applyed "Disable Telemetry". For me it happens in desktop as you can see: random flickers, refresh, lost mouse contact of windows, unable to open random apps/games who are in taskbar or with alt+tab and generally some weird behavior. It also happens in safemode. For me using the "Undo al Tweaks" didnt fix the isue.

It happens the same to me, I run desktop predefined tweaks and now I can not alt tab in full screen games like valorant or trackmania. Restore windows to an older point not fix the problem. Help :(

Btw, can we have some temporary or hot fixes for this like some registry keys, services we can edit/enable?

I had to manually create a system restore point prior to performing the tweak to undo it. Using the undo tweaks option didn't fix the problem. You'll likely have to do a fresh install of windows if you didn't create your own restore point.

You'll likely have to do a fresh install of windows if you didn't create your own restore point.

Not for me. Restore to a very old point not fix me the problem.

Fixed the issue on my computer. Edited top post. Please try and post results.

@JustTakingNotes Thank you very much! for me worked with just "Use REGEDIT and navigate to: "HKCU:\Control Panel\Desktop" and delete the DWORD "HungAppTimeout"
Then Restart. This should fix flickers and fullscreen crashes."
All seems to work well so far. Well see how it goes. Again TY! (didn't really wanted to reainstall windows)

ionascugabriel
lost mouse contact of windows

Another command in the telemetry tweaks was:
Set-ItemProperty -Path "HKCU:\Control Panel\Mouse" -Name "MouseHoverTime" -Type DWord -Value 10
If my solution above doesn't fix your mouse issue try restoring it to the default value of 400.

For now is working fine event with DWord -Value 10 but well remember this. TY.

@JustTakingNotes Thank youuuuuuu

Thanks for posting this all. Posting a fix in the official script right now.

Merged the following powershell command to fix this. Just rerunning the tweaks OR undo all will fix the issue. Commit: b3daa2f32ca4da7f2c46691970ccc3ce328c1455
Or just type this in powershell Remove-ItemProperty -Path "HKCU:\Control Panel\Desktop" -Name "HungAppTimeout" -ErrorAction SilentlyContinue


How to change openai in panel?

Hi.
How to change openai in panel and multi api openai.
thanks.

what's the meaning of "change openai" ?

Plz provide more info.


Look into ZenHub

ZenHub seems to supercharge some standard GitHub project management. We should look into it and decide if we want to use it or not.
https://blog.zenhub.com/github-issue-dependencies/

Closing in favor of Jira


Correct duplicate understat IDs

mandyville=# select count(understat_id) from players where understat_id is not null;
 count
-------
  3164
(1 row)

mandyville=# select count(distinct understat_id) from players where understat_id is not null;
 count
-------
  3063
(1 row)

Around 100 understat IDs (3%) are duplicated in the data set. e.g. is https://understat.com/player/1521 Gabriel Boschilia or Zé Gabriel? Or neither?! (it's actually Gabriel Barbosa who's not even in the dataset).
The understat ID code needs refining to avoid this, and we need a method for fixing the incorrect ones.

We should also add a unique constraint to understat and football-data IDs in the players table.

There's an issue with non-ascii characters incorrectly matching as well, it seems:
mandyville=# select first_name, last_name from players where understat_id = 71;
 first_name |  last_name
------------+--------------
 Berkay     | Özcan
 Nicolás    | González
 Santiago   | Ascacíbar
 Emiliano   | Insúa
 Timo       | Baumgartl
 Philipp    | Förster
 Mario      | Gómez García

Timo Baumgartl is the correct player here.

Once this is fixed, we should add a unique constraint to the understat_id column to prevent this from reoccurring.

I've now manually corrected all the duplicate IDs.


Add sidecar egress hosts conflict warnings

For https://github.com/istio/istio/pull/33766#issuecomment-872667419

LGTM. Will leave it for others to review

Making previously valid configurations invalid is a breaking API change. At most we can warn.

@howardjohn  Is this an indication that we only need to print the logs?

Add a warning, and add a TODO maybe in 1.12 we can make it this way.
FYI: WrapWarning

Add a warning, and add a TODO maybe in 1.12 we can make it this way.
FYI: WrapWarning

Thanks for your suggestions, I did it.

Add a warning, and add a TODO maybe in 1.12 we can make it this way.

We can never make it this way without it being a breaking API change. To do this it would require a new ApiVersion

@howardjohn https://kubernetes.io/docs/reference/using-api/deprecation-policy/

Yes, I would think this violates "Rule #1: API elements may only be removed
by incrementing the version of the API group"
Removing an element (either key or legal value) and making it invalid are
effectively the same?
On Mon, Jul 12, 2021, 9:14 PM Zhonghu Xu @.***> wrote:

@howardjohn https://github.com/howardjohn
https://kubernetes.io/docs/reference/using-api/deprecation-policy/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/33786#issuecomment-878763514, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXK6GTVHZXOYMYTE4BDTXO4S3ANCNFSM47V4SROQ
.

@howardjohn  I see the same action is allowed in Kubernetes: https://github.com/kubernetes/kubernetes/pull/103245.

Looks like that may be for an alpha feature flag protected field?
On Thu, Jul 15, 2021 at 3:41 AM Kebe @.***> wrote:

@howardjohn https://github.com/howardjohn I see the same action is
allowed in Kubernetes: kubernetes/kubernetes#103245
https://github.com/kubernetes/kubernetes/pull/103245.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/33786#issuecomment-880590215, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJYF6EITF27N7UJ7SDTX23LZANCNFSM47V4SROQ
.

Looks like that may be for an alpha feature flag protected field?

Yes, but this one does not affect the API and resources, it is only print some warnings in pilot, I can not do this also?

Looks like that may be for an alpha feature flag protected field?

Yes, but this one does not affect the API and resources, it is only print some warnings in pilot, can we not do this either?

LGTM, it only add some warning in validation, does not break any old configs

Sorry I either misread it or didn't look at the update - adding a warning is good, just not error


Faster precision recall

This one possible improvement for #29.
Basically, in sklearn.metrics.classifications, both precision_score and recall_score are using precision_recall_fscore_support. This mean the function was used twice for the same result in
https://github.com/emanjavacas/pie/blob/9fa672c04659b2c2219cb704027f48ba703c28b7/pie/models/scorer.py#L37-L38
PS: I added a change to the cli for evaluation because it was boring me to death to have to deal with this copy past everytime. Now pie eval loads path from --settings when none others are provided.

This will not completely fix #29, but is one good step.

I just removed a secondary loop as well. In the case of the Latin corpora, this would re-iterate over 200k tokens :)

I just spotted another places for improvement...

So, Scorer().get_scores() can be called in the following places:
In Scorer.print_summary  :
https://github.com/emanjavacas/pie/blob/9fa672c04659b2c2219cb704027f48ba703c28b7/pie/models/scorer.py#L262
Scorer.print_summary itself is called in trainer.run_check()  https://github.com/emanjavacas/pie/blob/9fa672c04659b2c2219cb704027f48ba703c28b7/pie/trainer.py#L267
But in the same function, 10 lines later, we also got get_scores() called https://github.com/emanjavacas/pie/blob/9fa672c04659b2c2219cb704027f48ba703c28b7/pie/trainer.py#L272
This mean get_score is actually called twice per Trainer.run_check() per task.

@emanjavacas We could use a multiprocess.Pool here as well,  such as
            pool = multiprocessing.Pool(int(len(self.tasks) / 2))
            # Dict are now ordered, so we should not worry about it
            stored_scores = zip(summary.keys(), pool.map(lambda x: x.get_scores(), summary.values()))

But it can be another discussion.

Is this ready to merge?

This is, multiprocessing will come later :)

Alright. Thanks!


Noise black bars missing

Thanks for the tool it is very handy :)
I'm wondering if the black bars for the noise can be added: http://www.etrma.org/uploads/images/Tyres/Tyre labelling information.jpg

Sorry for the late response. I will add them :)

Yep, this would be nice to have. Building a tire website and your script will come in handy. Only problem is responsiveness, but oh well.


Date().toISO([.withoutTZSeparators]) empty string

If I use this method Date().toISO([.withoutTZSeparators]) I get no result.
If I use this method Date().toISO() the string is corrected

Thanks for the report, the problem happens because withoutTZSeparators does not work if not paired with withInternetDateTimeExtended.
It was fixed.
Now this is the result of both calls:
Date().toISO([.withoutTZSeparators]) // 2019-04-16T16:28:06.049+0000
Date().toISO() // 2019-04-16T16:28:06Z


User method to set the MongoDB url to be used

I think there should be a method that the user can use to set the mongodb url to be used. Currently, one has to set the RADICAL_PILOT_DBURL env variable.

Good point.
Can you coordinate with Antons and Giannis, implement and document this?
I think I would be in favor of adding an optional parameter to the ClusterEnvironment. If it's not set, then RADICAL_PILOT_DBURL is used. If that's not set either, an exception is thrown.

Just to make sure.. we require an additional function to set the DB Url as opposed to another parameter in the SingleClusterEnvironment class (?).

I think an additional (optional) parameter would be better.

added 'database_url' parameter in single cluster class: https://github.com/radical-cybertools/radical.ensemblemd/blob/devel/src/radical/ensemblemd/single_cluster_environment.py#L46. If not specified, defaults to environment variable RADICAL_PILOT_DBURL.


Modal ok/cancel button

In the example: https://oruga.io/components/modal.html
ModalForm import the _modal-form-async.vue file.
Where can I find the code of this file?
I don't know how return ok/cancel event.
Thanks a lot!

https://github.com/oruga-ui/oruga/blob/develop/packages/docs-next/.vitepress/theme/examples/modal/_modal-form-async.vue


Fix image link in initialize job step

Description
Recently, macos tag name was changed from macos-10.15 to macOS-10.15. need to fix the content of image file accordingly.
Also put the same file to MacOS 10.13, MacOS 10.14 because now we have all readme files in virtual-environments repository
Related issue: https://github.com/actions/virtual-environments/issues/1992
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos1013, macos1014, macos1015, macos110


Map external tracker item states to ALM work item states

Currently these are supported states in the ALM:
[ "new", "in progress", "resolved", "closed" ]

When importing external tracker items into ALM, it should be possible to map the states of the remote tracker item into ALM native items.

I think this ticket has more scope than written.
We are considering only "states" of the items but along with that mapping layer should handle which item will be treated as story or bug or something else in ALM system.
Like this, mapping layer should translate all transportable attributes of external item into ALM item.

We will have to map the states in JIRA and bugzilla to the ALM states. Note that in JIRA, users can create custom workflows that can include customer states. Will we commit to supporting only the JIRA "classic" workflow?

@pranavgore09 This issue is more about the external to ALM mapping of states, as what github has as 'open' then what it will be mapped into our workitem.

Keep in mind the ALM doesn't support any specific state per say. It supports all and any. This is a mapping from one unknown to another unknown. (unknown as in not hard-coded/predefined)

@aslakknutsen For this sprint, should we keep mapping in the code or should it be placed in database?

This is how we currently maintain the mappings:
https://github.com/almighty/almighty-core/blob/master/remoteworkitem/remoteworkitem.go#L40

@Ritsyy Mapping in code is fine for now.

@aslakknutsen When you mention 'unknown to another unknown', will Admin decide this mapping while creation of WIT(in future) ? just curious to know how we can support this model of any and all.

@pranavgore09 (future) We need some UI that allow the user to create the mappings in the future.

Just dropping a note in here: did anyone look at TaskMapper? It's basically a dead project now, but it did support mapping of values from various trackers to one another. You could derive some inspiration from it, for your future work, especially around the provider-per-tracker concept.

@VineetReynolds As far as I can tell, TaskMapper is essentially a 'how do I get a Map a data from Provider X'. Any form of mapping between Provider X and Y is left up to the user. That's the part we're looking at. Getting the data is the easy.


Debug adapter process has terminated unexpectedly

Issue Type: Bug
i can not debug JS on vs code
this is msg : Debug adapter process has terminated unexpectedly
thanks for help
VS Code version: Code 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1, 2018-03-14T14:46:47.128Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz (4 x 1596)

Memory (System)
3.91GB (1.01GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

vscode-html-css
ecm
0.2.0

PowerShell
ms-
1.6.0

debugger-for-chrome
msj
4.2.1

JavaScriptSnippets
xab
1.5.0

Reproduces only with extensions

The same issue. No logs, no debug info. WHere I can find it?

react-native run-ios
runs Ok
...
** BUILD SUCCEEDED **

System info:

CPUs
Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.26GB free)

Process Argv
/Applications/Visual Studio Code.app/Contents/MacOS/Electron -psn_0_65552

Screen Reader
no

VM
0%

debugger-for-chrome
msj
4.2.1

vscode-react-native
vsm
0.6.5

I am getting the same issue and I think it is due to the debugger-for-chrome 4.2.1.
4.2.0 is still installed in my extensions folder. When I remove 4.2.1, the debugging works again.

@kimkimson @topchyalexey are you debugging Chrome or Node?

I'm debugging JavaScript with vscode. I dont understand what going on here
now. Help me, please.
Vào Th 7, 17 thg 3, 2018 lúc 01:27 Rob Lourens<EMAIL_ADDRESS>đã viết:

@kimkimson https://github.com/kimkimson @topchyalexey
https://github.com/topchyalexey are you debugging Chrome or Node?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/45938#issuecomment-373803980,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYurVf058h320QOfOHly4dd25EL3-2qdks5tfAP_gaJpZM4StK-p
.

Could you post your launch config (from the launch.json file)?

{
"version": "0.2.0",
"configurations": [
{
"name": "Debug iOS",
"program": "${workspaceRoot}/.vscode/launchReactNative.js",
"type": "reactnative",
"request": "launch",
"platform": "ios",
"target": "iPad Air",
"sourceMaps": true,
"outDir": "${workspaceRoot}/.vscode/.react"
},
]

}

Please file an issue on the React native extension repo

this is launch.json file
this is notification
help me. plese
2018-03-17 22:27 GMT+07:00 Rob Lourens<EMAIL_ADDRESS>
Please file an issue on the React native extension repo
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/45938#issuecomment-373928519,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYurVaYSLy9HHHwj6ob7fstUOKTJlNG6ks5tfStdgaJpZM4StK-p
.

@kimkimson I was also facing the issue and it is now fixed, if you update the React Native Tools extension everything should work fine.

@Paari that extension isn't included in the OP so I think @kimkimson has a different issue.
@kimkimson please post your launch.json file here.

@roblourens @weinand I'm seeing this on the C++ extension too. I've had to reinstall the extension to get the error to go away. I don't know what would be causing it but I also have an end-user complaining about it:
https://github.com/Microsoft/vscode-cpptools/issues/1719
@wardengnaw

These issues could also be from corrupt extension installs like in https://github.com/Microsoft/vscode/issues/43813

I'm getting this for a .py program.

@lindapescatore then please file this issue against the Python debugger extension. This Issue is about JS.

Is this still an issue? There's a confusing mix of messages here. Haven't had a report in awhile, so closing.


404 at /Machine/%EF%BC%89%E3%80%82

I found a broken link : https://docs.docker.com/Machine/）。
I arrived on this page through: https://ask.csdn.net/questions/384324

Thanks for reporting; I suspect someone posted a wrong URL on that website, which is not something we can fix in our docs.
Note that Docker Machine has been deprecated and is no longer maintained. If you want to install docker on Mac or Windows, we recommend installing Docker Desktop
I'll close this ticket because of the above, but feel free to continue the conversation


⚠ Bofrost.nl has degraded performance

In bc2aa7a, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1065 ms

Resolved: Bofrost.nl performance has improved in 8eea07b.


Question out of curiosity regarding Vagrantfile's hash rocket

Dear contributors,
Could you please explain why you provide arguments to node.vm.provision sometimes like type: "shell" and sometimes like :type => "shell"? Does it has different outcome on the way provisioning scripts are being executed?
        node.vm.provision "setup-dns", type: "shell", :path => "ubuntu/update-dns.sh"
        node.vm.provision "install-docker", type: "shell", :path => "ubuntu/install-docker-2.sh"
        node.vm.provision "allow-bridge-nf-traffic", :type => "shell", :path => "ubuntu/allow-bridge-nf-traffic.sh"
        node.vm.provision "file", source: "./ubuntu/cert_verify.sh", destination: "$HOME/"

Thank you in advance! I'm just curios 😅

Hi @DmitryMihailov
TBH I'm not sure, not being an expert in Ruby.  As far as I know, they're different syntaxes for the same thing: named parameters.


Chat image attachment flickers when removing/adding attachments and sometimes when responses are being streamed in

If it's fully rendered we shouldn't regenerate all the HTML, I'm guessing that's what's happening.
Repro:

Attach an image file to chat
Attach a file via drag and drop, 🐛 notice the image attachment thumbnail flickers

this is because the logic for attachContext is getting called a lot (which regenerates attachments in general. note that this happens when the chat stream is going as well). maybe taking a look at how we can not call it after it's initial attachment

@Tyriar I'm not seeing this anymore (i believe it was fixed with some attachContext rendering cleanup). I'll for now but let me know if you still see this 👍🏻


Cannot use eject key on logitech keyboard anymore

I installed powerkey and it works great.  The only problem I am running into now is that my eject key no longer ejects discs.  I have to now manually drag my discs to the trash for ejection.  Please help.

Hi, can you post a picture or the model name of your Logitech keyboard?
Thanks.

@stabbey it looks as if email attachments are not being added to the ticket, can you send the Model Name? Or attach your photo via the web interface.


[SPARK-47793][TEST][FOLLOWUP] Fix flaky test for Python data source exactly once.

What changes were proposed in this pull request?
Fix the flakiness in python streaming source exactly once test. The last executed batch may not be recorded in query progress, which cause the expected rows doesn't match. This fix takes the uncompleted batch into account and relax the condition
Why are the changes needed?
Fix flaky test.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Test change.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @HeartSaVioR and @allisonwang-db from #45977

Could you do the final review and sign-off, please, @HyukjinKwon ?

Let me bring this first for further monitoring. Thank you, @chaoqin-li1123 and @allisonwang-db .
Merged to master.


Propagate font sizes to ZedGraph axis

There is currently no way to propagate the font information from a TableLayoutPanel to child ZedGraph plots. This is especially important when trying to scale small plots in large TableLayoutPanels.

Duplicate of #24


Proposal to move types and errors files to dedicated folders

This design doc proposes moving types and errors files out of */libraries/ and */lib/ files and into dedicated folders named */types/ and */errors/.
Issues:

https://github.com/ethereum-optimism/optimism/issues/12642
https://github.com/ethereum-optimism/optimism/issues/12645

Here's a recap and conclusion of the discussion between @smartcontracts, @ControlCplusControlV and I on discord

Error Files: We agreed to remove error files altogether, embedding errors directly in contracts and possibly following #143 if the proposal is accepted. This has the advantage of also simplifying imports.
Type Files: For now, types files will remain as is, until the discussion for moving dispute/cannon folders into the L1 folder commences. #Issue

Discussed in #150. Conclusion was

For errors: it will follow #143
For types: it will remain as is (for now)


GetProcessorFromBuiltinColorSpace with "noop" transform does not result in isNoOp() returning true

Tested using the ocio://default config, using OCIO v2.2.1
auto config = OCIO::Config::CreateFromFile("ocio://default");
auto proc = OCIO::Config::GetProcessorFromBuiltinColorSpace("ACEScg", config, "ACEScg");
bool noop = proc->isNoOp();
assert(noop);

When generating the shader text it is quite clearly a noop.
For my use case I kind of want to rely on this specific case returning a noop processor (more specifically when using the OCIO::ROLE_SCENE_LINEAR role) as an optimization.

@SRHMorris , that's because the Processor has not been optimized, it is just the concatenation of the to-reference and from-reference transforms.  If you were processing pixels, you would generate a CPUProcessor or GPUProcessor from the Processor and that would optimize it.  But if you just want to run the optimizer without processing pixels, you may use the getOptimizedProcessor method.  Calling isNoOp on the result of that would be a no-op, in your case.

@doug-walker thanks for your help, that does seem work so I'll close this issue.


[eng/common] Update-DocsMsMetadata.ps1 can fail the build on invalid packages

This PR adds the ability to fail nightly docs builds if validation fails. This capability is not active in this PR as these need to be individually wired up in docindex.yml
Example builds:

.NET

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2928742&view=results
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2928743&view=results

JS

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2928744&view=results
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2928746&view=results

Python

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2928748&view=results
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2928751&view=results

Java

Example build showing expected failure when wired up -- https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2928681&view=logs&s=cc1c0c38-0f79-5da2-c09f-847e3abdf9ce&j=bd8e6c55-eb1f-54f4-a38a-6cffe78ea5a1

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

Partial: https://github.com/Azure/azure-sdk-tools/issues/6463

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow


Logging inside a TransactionScope

I've got some code where I'm trying to write to a database log within a TransactionScope, then the transaction is being rolled back, which rolls back the write to the log.
On September 19, 2014, there was a commit that should have fixed that (https://github.com/NLog/NLog/commit/1c85dbd8c7bac7ab0194808f3e251967b1a7301a), but it wasn't included in the 3.2 release. Does anyone know why?

it's indeed missing in 3.2.0, but it's in in the master.
Dunno what happened.


Appstudio update test-component-pac-krux

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-krux-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
33 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
30 seconds
sanity-inspect-image

✅ Succeeded
30 seconds
deprecated-base-image-check

✅ Succeeded
4 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
39 seconds
sbom-json-check

✅ Succeeded
12 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
sanity-label-check

✅ Succeeded
7 seconds
show-summary

Pipelines as Code CI/test-component-pac-krux-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
33 seconds
clone-repository

✅ Succeeded
2 minutes
build-container

✅ Succeeded
30 seconds
sanity-inspect-image

✅ Succeeded
30 seconds
deprecated-base-image-check

✅ Succeeded
4 minutes
clair-scan

✅ Succeeded
39 seconds
sbom-json-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
8 seconds
sanity-label-check

✅ Succeeded
12 seconds
sanity-optional-label-check

✅ Succeeded
7 seconds
show-summary

Pipelines as Code CI/test-component-pac-krux-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
10 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
34 seconds
build-container

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
19 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
14 seconds
sanity-inspect-image

✅ Succeeded
15 seconds
sbom-json-check

✅ Succeeded
11 seconds
sanity-optional-label-check

✅ Succeeded
12 seconds
sanity-label-check

✅ Succeeded
7 seconds
show-summary


ci-check script is rather slow

The script ci-check which in turn calls some other scripts runs for every exercise that was changed in a PR. That means e.g. for PRs that include some files being synced for all exercises, the script runs for all exercises. As far as I could see, this consistently takes 10-15min when run as part of the GitHub Actions.
Examples:

https://github.com/exercism/javascript/runs/4600717991?check_suite_focus=true
https://github.com/exercism/javascript/runs/4679060545?check_suite_focus=true

This is a bit annoying when a maintainer wants to get something done quickly so maybe someone has an idea what could be done to improve the performance.

No longer slow!


Different Learned Equation with Different Numpy Array Shape

Over the past week and a half I have been exploring some use cases of the DSO library with some research that I am doing and have noticed some odd/unexpected behavior through the explorative examples I have come up with. The odd/unexpected behavior that I wanted to ask about is how, when using the sklearn interface, the learned equation from a DSO run with the same config file training points X , and test/fit points y differs when y is  defined as a one dimensional Numpy array - i.e Numpy array shape given as (N,) where  N is the number of points - versus when  when y is  defined as a two dimensional one column Numpy array - i.e  Numpy array shape given as (N,1).  To demonstrate what I am saying, when running the below python code
import numpy as np
from dso import DeepSymbolicRegressor
def main():
    np.random.seed(2)
    num_pnts = 50
    a, b = -2, 2    # used to change the random points from [0, 1) to [a, b)
    X = b*np.random.random((num_pnts,1))+a
    y = X[:,0:1]
    # y =X[:,0]
    config_file = "TestConfig.json"
    model = DeepSymbolicRegressor(config_file)
    model.fit(X, y)
    print(model.program_.pretty())
if __name__ == '__main__':
    main()

where the TestConfig.json file is the first noted json file below, the resulting learned equation is $\frac{1}{\cos{e}}$ however by just changing the line y = X[:,0:1]  to y = X[:,0] the learned equation is $x~1$ which is the correct equation. So I wanted to ask if the library authors knew about this or not and in the latter case if the simple fix to this odd/unexpected behavior would be to check that the array y is defined as a one dimensional array and if not copy and reshape it to be one (for example in the fit function of the DeepSymbolicRegressor class found in the sklean.py file).
Another thing that I would add to this is that this behavior also results in a run time error being thrown when the function set parameter within the config Json file contains the "poly" argument. Specifically, if the below code is run with second JSON file,
import numpy as np
from dso import DeepSymbolicRegressor
def main():
    np.random.seed(2)
    num_pnts = 50
    a, b = -2, 2    # used to change the random points from [0, 1) to [a, b)
    X = b*np.random.random((num_pnts,1))+a
    y = X[:,0:1]
    # y =X[:,0]
    config_file = "TestConfig.json"
    model = DeepSymbolicRegressor(config_file)
    model.fit(X, y)
    print(model.program_.pretty())
if __name__ == '__main__':
    main()

it results in ValueError with with the whole error message being the following:

Traceback (most recent call last):
File "DSOtesting1.py", line 78, in
main()
File "DSOtesting1.py", line 66, in main
model.fit(X, y)
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\task\regression\sklearn.py", line 39, in fit
train_result = self.train()
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\core.py", line 114, in train
result = self.train_one_step()
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\core.py", line 95, in train_one_step
self.trainer.run_one_step(override)
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\train.py", line 291, in run_one_step
r = np.array([p.r for p in programs])
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\train.py", line 291, in
r = np.array([p.r for p in programs])
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\utils.py", line 112, in get
value = self.getter(obj)
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\program.py", line 452, in r
return self.task.reward_function(self)
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\task\regression\regression.py", line 194, in reward_function
p.traversal[p.poly_pos] = self.poly_optimizer.fit(self.X_train, poly_data_y)
File "c:\users\urzua\desktop\my shit\uci and sdsu stuff\research_work\pytorchtests\deep-symbolic-optimization-master\dso\dso\task\regression\polyfit.py", line 461, in fit
return Polynomial(list(compress(pod.all_exponents, mask)), self.regressor.coef_[mask])
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

Having looked a bit into why this problem happens, it appears to have something to do with how the library is determining the coefficients for the polynomial terms as the mask array in line 461 of the polyfit.py file is a three dimensional array and not a 1 dimensional array and so the list(compress(pod.all_exponents, mask) bit of the code throws the error. However again when running the above Python code with   y =X[:,0] instead of  y =X[:,0:1], no error is thrown and the correct function is learned $y=x~1$. I though I would also mention this behavior that I notice there since it seems to be related to the first behavior I noticed and was curious about with y not being defined as a one dimensional Numpy array.
I hope that I have given sufficient information to reproduce the behavior that I have noticed and explained it in enough detail but should there be any further bits of information that I need to give and clarify, please let me know and I will get back on that as quickly as I can.

Yes, y should always be one-dimensional. If it's 2D (even with a single column, as in your example), the symbolic operators are likely doing something you don't expect.
I agree it would be better to raise a ValueError or similar if y.ndim != 1. Would be happy to take a PR for this behavior.

Hi and thank you very much for the quick response here.
Glad I could be of some help in bringing the behavior with the poly token to your attention. On the PR for this behavior, I am do not happen to use GitHub all that often so do not exactly know how to properly issue pull requests and then merger my edits back with the library but I will do my best. I do have one question though, aside from in the fit function of the the DeepSymbolicRegressor class found in the sklean.py file, is there would there be any other place to check that either y.ndim!=1 or to raise a Value Error? I have only been doing my exploratory examples using the sklearn interface but know that the pair (X, y) can be given in the config file through some way and so I assume that checking the number of dimensions of y would probably be needed somewhere else as well correct?
That all being said I will make a pull request, make the edit mentioned about and look for anywhere else that the library may need a similar edit. For any further questions I have on the library I will either make a new issue or email you directly since I have some questions regarding the creation of new function/tokens (derivative related).

The sklearn interface is just a thin wrapper to the DeepSymbolicOptimizer object tied to the regression task. So yes, it would make more sense to do in the base object, or more specifically the RegressionTask.
Might need to be done in 2 places. First checking the training data shape, which can be done in RegressionTask I think.
The second would be for eval. Since the base DSO object doesn’t do prediction, might need to that in the Sklearn interface.

Got it and I will take a look into all those places that you mentioned and make the edits I see fit and then after doing some test runs issue the PR.
Again should I need to get some clarification or ask anything else I will make sure to do so here or through direct email.


Error handling: clear selection/prompt user for action when select operation fails

If the number of features selected is large, sometimes the operation fails. Nothing indicates this failure to the user.

Test App: https://sg-em-devext.mapsdevext.arcgis.com/apps/instant/notification/index.html?appid=2e420c6f669b464993645f8b698d5b46
Test Map: https://sg-em-devext.mapsdevext.arcgis.com/apps/mapviewer/index.html?webmap=5e0382dfb72f4849879889a14d7624b5
To repro

Try to select all the features

@jmhauck here is a map for you to reproduce this scenario https://arcgis4localgov2.maps.arcgis.com/apps/mapviewer/index.html?webmap=71f6e9122bbd45cfbeddd4fcf7c749a4


Modbus over RS485 - queue build up

I'm submitting a ...

(x ) unexpected behavior

Current behavior

The modbus rtu queue keeps building up messages one after another and the poll rate is really slow.
Expected behavior

The queue should be emptied faster than it's being filled.
Minimal reproduction of the problem with instructions

I am using this example flow to pull data from SDM120 using RS485 to TTL adapter, I've also tried using USB to RS485 adapter with the same result. What happens is the queue object is showing increasing number of items and the flow is very slow. When I click on any of the modbus read nodes the queue seems to start moving for a short period. Illustration below:

The serial port queue delay is 100ms.

( x) I am using just the Node-RED package and got modbus-serial package installed with it

Device : Raspberry Pi Zero W

( x) Raspbian GNU/Linux 10 (buster)

node-red-contrib-modbus version: v5.2.0

Node: (min. 10.x)
node --version = v10.18.0

Posting here because I think it's related to the upgrade and to this issue. I'm having that strange behavior after upgrade from 4.1.3, the queue keeps growing and if I try to emtpy with msg.resetQueue = true I get TypeError: a.initQueue is not a function. I haven't change anything in what it was a already working Node Red project with 4.1.3.
Device : BeagleBone Black with Debian GNU/Linux 10 (buster)
Node-RED v1.0.2
node-red-contrib-modbus version: v5.2.0
node --version = v10.15.2

@gugani if it is a major update from 4 to, then it has breaking-changes. Please, try the best way for major releases: uninstall the old version (or now your upgraded package) of Modbus before and install it again and after that export all the Modbus containing flows and import them again - deploy it. Not all nodes are backwards compatible on major releases and sometimes they have to be deleted and add again. From 4 to 5 it is also a breaking-change in the config node because it gots a new queue handling.

Thanks @biancode, I made a clean install, I imported the previously exported nodes  and everything is working in 1.0.2. Now updating to the tested version 1.0.3. Thanks!!

Hi, I have to add that communications are working, but the msg.resetQueue = true throws an TypeError: a.initQueue is not a function I open a new issue to avoid meshing more this thread.


Publicly Expose pdf viewer

Attach (recommended) or Link to PDF file here:
Would is be possible to expose pdf viewer as a public API?
Right now I must import as:
import { EventBus, NullL10n, PDFLinkService, PDFViewer } from 'pdfjs-dist/web/pdf_viewer';

is there any reason this is not currently exposed?

When opening an issue, please provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md since as-is this unfortunately lacks enough detail to understand exactly what you're actually asking for!

Would is be possible to expose pdf viewer as a public API?
Right now I must import as:
[...]

It's not entirely clear what this actually means, since it's being exposed as-is (otherwise you'd not be able to import it as shown)?

is there any reason this is not currently exposed?

What's not being exposed, since you've not explained what's "wrong" with the current situation or what you'd like to see instead?


Performance Enhancements in MySQL Database Management

Performance Improvements from Code Changes

Better Connection Handling:

Enhanced error handling in the getConnection() method helps quickly identify connection issues, reducing downtime and improving reliability.

Default Values:

Using sensible default values for connection pool settings prevents misconfigurations, ensuring smooth operation even if specific settings are missing.

Updated Driver:

Switching to com.mysql.cj.jdbc.Driver ensures compatibility with the latest MySQL features, leading to faster query execution and reduced latency.

JDBC URL Parameters:

Adding parameters like ?useSSL=false&serverTimezone=UTC avoids warnings and stabilizes connections, enhancing reliability.

Safe Resource Management:

Checking for null before closing dataSource prevents errors and resource leaks, maintaining application performance over time.

Overall Impact
These changes should result in:

Reduced Latency: Faster query execution.
Increased Throughput: Better handling of multiple requests.
Improved Resource Use: Less chance of overloading the database.

Overall, expect a more stable and responsive application with better performance metrics!

You can test at your home that there was a momentary spike in MSPT earlier while receiving the reward