[new plugin] remove-xlink-ns

Ref https://github.com/svg/svgo/pull/1508
The new plugin removes xmlns:xlink from  and replaces xlink:href
with href attribute.
xlink namespace is obsolete in SVG 2. Href attribute is recommended
replacement to xlink:href.
This plugin will be enabled by default in SVGO 3.
See https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/href
cc @devongovett

I took over this PR and implemented the plugin. It ended up being a bit more complicated, though! ^-^'
I did temporarily set removeXlink as a default plugin and can confirm regression tests 100% pass. 🎉
Differences:

This migrates the whole XLink namespace rather than just the xlink:href attribute. For example, xlink:show and xlink:title too.
This checks if the XLink namespace was added with other prefixes at some point in the document.

I took the equivalent SVG 2 syntax from MDN.

xlink:href → href
xlink:show → target (new → _blank, replace → _self)
xlink:title → <title> in the child node


add in slides for node school and hardware days

These are the slides for the first two events, hoping to put up
the slides for the language hackday when they're ready.

I'm assuming this will work fine on netlify...


vk.com  does not load

does not load https://vk.com/videos-33919455?section=album_43941159&z=video-33919455_161658117%2Fclub33919455
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', '--username', '', '--password', '', 'https://vk.com/videos-33919455?section=album_43941159']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2014.08.05
[debug] Python version 2.6.6 - Linux-2.6.32-431.17.1.el6.x86_64-x86_64-with-centos-6.5-Final
[debug] Proxy map: {}
[vk.com] Logging in as<PHONE_NUMBER>36
[vk.com] s-33919455: Downloading webpage
ERROR: Unable to extract vars; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 516, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 170, in extract
return self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/vk.py", line 159, in _real_extract
data_json = self._search_regex(r'var vars = ({.*?});', info_page, 'vars')
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 391, in _search_regex
raise RegexNotFoundError(u'Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract vars; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.

Works fine with the current master.
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'http://vk.com/video-59835603_169687332', u'--verbose', u'--skip-download']
[debug] Encodings: locale UTF-8, fs UTF-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2018.09.26
[debug] Git HEAD: 66d106f27
[debug] Python version 2.7.15rc1 (CPython) - Linux-4.15.0-34-generic-x86_64-with-Ubuntu-18.04-bionic
[debug] exe versions: ffmpeg 3.4.4-0ubuntu<IP_ADDRESS>, ffprobe 3.4.4-0ubuntu<IP_ADDRESS>, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[vk] -59835603_169687332: Downloading webpage
[debug] Default format spec: bestvideo+bestaudio/best```

I think we can close this.


Existing bintray maven repo link invalid

The existing url returns a bad gateway error. Is there an alternative source for the package?

I don't know, sorry.


RTT and readPixel sync

Hi,
I am trying to perform a render in a texture and then reading back texture pixels. The RTT part seems OK but i suspect a synchronization issue.
I probably do anything wrong but i do not find anything clear about it in doc or examples.
I first create a texture :
m_textureHandle =	bgfx::createTexture2D(a_width, a_height, a_mipmapCount, format, flags, NULL);

What flags are needed for RTT and ReadPixel ? I see flags like BGFX_TEXTURE_RT and BGFX_TEXTURE_READ_BACK but i did not find their documentation.

Then i create a FBO :
bgfx::TextureHandle textureHandles[1];
textureHandles[0].idx = m_textureHandle;

m_FBOHandle = bgfx::createFrameBuffer(1, textureHandles, false);

Does this allocation on the stack of textureHandles array work or do i need to allocate it on the heap ?

Then i render anything in my FBO
bgfx::setViewFrameBuffer(m_viewUId, m_FBOHandle);
// some other view config and submits on m_viewUId
bgfx::frame();

And finally, i read back texture pixels.
// Allocation of std::uint8_t * pixelBuffer with good size
bgfx::readTexture(m_textureHandle, pixelBuffer);
// Stuff to write on disk .png image

I obtain images on disk partially filled, or a crash.

Does the readTexture() call is executed after the end of the render and is it blocking ?

A hint would be welcome :)
Thanks,
Harold

Hi again,
After further analysis, my issue comes from readTexture()  call generate à command treated asychronously, ans therefore is not blocking as i first expected.
Is there à way to know when thé readTexture command have been executed ?
Maybe using releaseFn passed to bgfx via makeRef ? Sadly readTexture() des not take a bgfx Memory as parameter.
Regards,
Harold

I'll add some mechanism to inform about availability of result. It's guaranteed to be returned after two calls of bgfx::frame.

I'll also update docs to clarify that it's asynchronous call.

Hi,
In a more general way, IMO it could be great to be able to register a callback called when all commands of a bgfx::frame call were executed.
This should avoid cases where we have to call 2 bgfx::frame where only one is really needed when WE need kind of synchronicity.
Regards,
Harold

Frame number is intended for this use: https://bkaradzic.github.io/bgfx/bgfx.html#_CPPv2N4bgfx5frameEb
It's equivalent of callback you're talking about. You can implement callback when current frame reaches texture read frame + 2.

Sure, but waiting 2 bgfx::frame / looking to frame number is not very convenient with my use case because i am doing "one shot render".
I have a permanent GL context alive on a server, when i receive an  event from sockets, i want to submit things, call one bgfx::frame, rendering things in à texture, then call bgfx::readTexture, wait for result and send back rendered image to client.
In this case, a callback without any extra bgfx::frame call could simplify a lot the results management.
Regards,
Harold

But you then have simple case, just call bgfx::frame twice after bgfx::readTexture and return the result. That would be equivalent of immediate mode.

Updated: https://bkaradzic.github.io/bgfx/bgfx.html#_CPPv2N4bgfx11readTextureE13TextureHandlePv

Hi,
You are right, in this case calling twice bgfx::frame after my bgfx::readTexture can make thé job.
What worries me with calling extra bgfx::frame is about vsync.
I have another use case which is in real-time context, where i have to do a render in texture, read pixels as image, perform treatment over the image and finally render things in usual windows backbuffer, at 60 FPS.
Does calling twice bgfx::frame to get texture pixels will divide my final FPS by 3 with vsync activated as it will wait for screen sync at each bgfx::frame call ? :-/
Regards,
Harold

Yeah calling it multiple times is not for renderers where you need interactivity. You can disable v-sync for your server renderer app.
You can wrap bgfx::readTexture inside your app to be deferred until frame where it's available, and execute call back. Code is quite trivial to add something like this.
void yourReadTexture(bgfx::TextureHandle _handle, void* _data, YourCallbackFn _callback)
{
    uint32_t frame = bgfx::readTexture(_handle, _data);
    s_frameArray.push_back(FrameArray{frame, _callback, _handle, _data});
}

uint32_t frame = bgfx::frame();
for each s_frameArray where FrameArray.m_frame < frame execute callback


[CNCF] Understand the services available for your project at CNCF

Parts of the CNCF onboarding issue tracked by this issue
This is the list of all bullet points from the [CNCF onboarding issue](https://github.com/cncf/toc/issues/798) that this issue will track:

[ ] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/

Yes. I understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/


Build with gmake < 4 broken: missing separator

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.05.01. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.05.01

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

When buliding under openSUSE 13.1 with (GNU) make-3.82, or SLES 11 with GNU make-3.81, the build fails:
[   33s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/youtube-dl-2016.05.01-112.1.x86_64
[   33s] + cd youtube-dl
[   33s] + perl -i -pe '
[   33s]         s{^PREFIX\ \?=\ /usr/local}{PREFIX ?= /usr};
[   33s]         s{^BINDIR\ \?=\ \$\(PREFIX\)/bin}{BINDIR\ \?=\ /usr/bin};
[   33s]         s{^MANDIR\ \?=\ \$\(PREFIX\)/man}{MANDIR\ \?=\ /usr/share/man};
[   33s]         s{^SHAREDIR\ \?=\ \$\(PREFIX\)/share}{SHAREDIR\ \?=\ /usr/share};' Makefile
[   33s] + exit 0
[   33s] Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.3EufIx
[   33s] + umask 022
[   33s] + cd /home/abuild/rpmbuild/BUILD
[   33s] + cd youtube-dl
[   33s] + make DESTDIR=/home/abuild/rpmbuild/BUILDROOT/youtube-dl-2016.05.01-112.1.x86_64 install
[   33s] Makefile:15: *** missing separator.  Stop.

It appears that the variable != value syntax as introduced by commit 3ff63fb3657fee9e0c2df9d5bb96ae5827f257cc is not supported with make 3.x, but only 4.0 and up.

I don't know of other way to make it compatible with BSD make, so we'll have to think something. Note that gmake 4.0 was released in 2013, so it's not something really new.

The following syntax:
SYSCONFDIR = $(shell if [ $(PREFIX) = /usr -o $(PREFIX) = /usr/local ]; then echo /etc; else echo $(PREFIX)/etc; fi)

Works on GNU make 4.1, too. Does it work on GNU make 3.81 and/or BSD make?

No, $(shell ...) is only available in GNU make.
I can be changed to
SYSCONFDIR = $$(if [ $(PREFIX) = /usr -o $(PREFIX) = /usr/local ]; then echo /etc; else echo $(PREFIX)/etc; fi)

but that means it gets executed each time you write $(SYSCONFDIR).

but that means it gets executed each time you write $(SYSCONFDIR).

If we want to support GNU make 3.x as well as BSD make it's inevitable. And it seems harmless to youtube-dl as the Makefile is quite small.

@jengelh it should just work, but could you check if it works with this change in GNU make 3.x?

@bdeyal Could you change the offending line:
SYSCONFDIR != if [ $(PREFIX) = /usr -o $(PREFIX) = /usr/local ]; then echo /etc; else echo $(PREFIX)/etc; fi

To the new syntax proposed in https://github.com/rg3/youtube-dl/issues/9387#issuecomment-216954854 and check whether the old make on CentOS works or not?

Works OK.
I use master with  git hash 0a33bb2cb2ca401ffe88e520d7bbd7482d976cbc
changes 2 locations. First is the line you gave above (line 15) and second at line 93:
_EXTRACTOR_FILES = $$(find youtube_dl/extractor -iname '*.py' -and -not -iname 'lazy_extractors.py')
I tested a single download, works OK.

Thanks. I'll check the changes on BSD make before commiting.

After the change It works fine with NetBSD make too (called bmake in Fedora)
No difference compared to GNU make.

Oh thanks! Which Fedora version did you test with? And which version of make does CentOS comes with, 3.81 or 3.82?

CentOS 7.2 comes with make 3.82
NetBSD bmake was built on CentOS from a Fedora 24 source rpm. Tested on CentOS, not Fedora.
Took the source rpm from here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=716769

Thanks for helping on tests. Fixed.

 Sorry for not having checked everything well.

Then I don't think it can be made to support both old gmake versions and bmake. I don't mind dropping support for bmake, I just thought it would be nice to have it.

OK. Dropped BSD make support as installing gmake on *BSD systems seems quite easy.


Update bitsong to 0.14.0

proposal: https://www.mintscan.io/bitsong/proposals/16
block: 10,055,000
est time: February 17th, 2023 at 16:30:00 UTC

Both bitsong and cosmoshub have now been updated via other PRs.


Generic type constraint not working with map operator

I've admittedly not looked deeply into lightweight generics in Objective-C, but I'm seeing an issue when changing type in a signal chain using the map operator.

ReactiveObjC expects the output type of the original signal rather than the mapped one, and due to the presence of the generic refuses to allow type coercion. The following results in a build error:

My thought is this may be related to #34 as instancetype is picking up on the generic Signal, and that generic isn't updated with map.

@altyus Thanks for the issue report and sorry for the inconvenience. The transition to lightweight generics is just about finished. This should be fixed in #39.

As a temporary fix, I'd suggest either reverting to ReactiveObjC 1.x or casting the rac_addObserverForName:object: call to RACSignal<id> *.

I went with the id, just making sure I wasn't missing something.  Cheers


Failed to load https://api.twitter.com/1.1/statuse

Ripme version: 1.7.95
Java version:  Version 8 update 241
Operating system:  windowns

Exact URL you were trying to rip when the problem occurred: https://twitter.com/xxx
Please include any additional information about how to reproduce the problem:

Expected Behavior
Should rip all the images and videos' including all RT's etc
Actual Behavior
Got this error below. I keep getting this error everyday
Failed to load https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=xxx&include_entities=true&exclude_replies=true&trim_user=true&count=200&tweet_mode=extended: Status Code 401. You might be able to circumvent this error by setting cookies for this domain

This is a big one. I can't get it to work either.

please provide example screen_name

I don't think that a screen name is needed; I'm seeing this issue as well, and it is highly sporadic and not related to particular accounts. I will sometimes have this 10 times in succession, and on the 11th it will work; it seems to vary wildly. I can only guess it may be related to the availability of the Twitter API, or to what was done from my IP before, I don't know.
It usually happens on the initial connection for a newly added account, not once ripping has commenced - maybe some kind of retry with a timed backoff might help, it's hard to say.

Maybe because you're trying to download from protected account?

Maybe because you're trying to download from protected account?

No, it is public account


Import error

Hello,
I'm loving your product and would like to use it. However using the following Python and builtwith version:
Name                    Version                   Build
builtwith                 1.3.3                    pypi_0
python                    3.7.3                h8c8aaf0_0
However, trying to import the BuiltWith class fails with the following error:
ImportError: cannot import name 'BuiltWith' from 'builtwith'
Do you have an idea whats wrong?

Sorry about that. It probably doesn't work with Python 3. I haven't used this in quite a while.

Similar issue here when following the README;

Also on python3. Python 2 is end of life so not sure why you wouldn't use 3?

> ImportError: cannot import name 'BuiltWith' from partially initialized module 'builtwith' (most likely due to a circular import) (builtwith.py)
> ```

Works for me:

% python3 -m virtualenv venv
% source venv/bin/activate
(venv) % pip install python-builtwith
(venv) % python
Python 3.7.3 (default, Mar  6 2020, 22:34:30)
[Clang 11.0.3 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

from builtwith import BuiltWith
bw = BuiltWith(key='example')
bw.lookup('example.com')
...

> Also on python3. Python 2 is end of life so not sure why you wouldn't use 3?

Because I wrote it seven years ago.


Starting webcamera in docker container on windows host through pipeline

Hello,
Currently the pipeline takes the input as a video from the sample videos. To add to it, I am trying to get the input as live video through my webcamera.  ERROR: Pipeline doesn't want to pause. ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: This isn't a device '/dev/video0'. Additional debug info: ../sys/v4l2/v4l2_calls.c(616): gst_v4l2_open (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: system error: Resource temporarily unavailable Setting pipeline to NULL ... Freeing pipeline ...
How can I set my input parameter to be webcamera?

@MauryaShraddha
Mounting a webcamera into a Linux Docker container on Windows is not directly supported by Docker for Windows so unfortunately there is no simple way to enable your use case. Two options remain to support this:

Creating a Virtual Machine (Virtual Box or other), exposing the webcamera to that virtual machine, and then either installing openvino DL Streamer directly or using docker within that virtual machine.

Converting your webcamera to an IP camera and streaming over the network to your docker container

In general DLStreamer doesn't support Windows directly and these techniques are only to enable early development / prototyping on Windows.
OpenVINO on the other hand in general does support Windows and some of the other non DL Streamer based tutorials can be made to work with web cameras via opencv.

@nnshah1 Thank you. I will try to work on this and check if any simple way can be made to resolve this.

@MauryaShraddha - One of my colleagues may have a solution - I will also check if we can provide some simple instructions via virtual box

@nnshah1 Thank you so much. This means a lot and is really helpful. I will keep working on this and let you know if I get a breakthrough.

No problem, adding @tobiasmo1, as he may be able to help.

@MauryaShraddha - With VirtualBox set up to run a Ubuntu 18.04 VM, it is reasonably straightforward to configure a pipeline to access your host's webcam.  You will need to add an Ubuntu .iso as a disk, install GuestAdditions with sufficient disk space (recommend dynamic 50GB). Install latest docker on that Guest host and then with the VM powered off, you'll select the camera from the VM's (Settings -> USB) dropdown - which reserves the camera on behalf of the VM (prevents Windows from locking it).
I recommend then confirming /dev/video0 is available to the VM by installing Cheese:
$ sudo apt-get install cheese
$ cheese
Once that is verified, the webcam will be accessible as /dev/video0 in the DL Streamer docker container.


Not supported on ios 12

Please take a look at this problem.
SyntaxError is reported in this version of ios 12.5.7. It is located that the plugin is reported. I guess it is a compatibility issue. Please see how to deal with it. Thank you very much.

Please ignore the issue. It’s this window.xxx variable that has no value.


Add option to server to get TLS ConnectionState for connections

This is one way of doing it, another would be to stash the tls.ConnectionState in the WebSocket and add an accessor.

I honestly like the second idea better, because it allows to access everything in the same callback. The information can easily be passed all the way to the application. It would be a breaking change in the interface though, so up for debate. Btw I'm currently working on some improvements in the websocket package, so I could add your suggestion there directly in that case.

So to be clear, adding it to ws.Channel? I actually like that option better as well.

So to be clear, adding it to ws.Channel? I actually like that option better as well.

Yes, that's right

Changes look good. The TLS field are not exposed yet to the callback in the ocpp1.6/2.0 package (only the client ID being passed there). I can take care of it in a follow-up PR, if you want.

Good point! I can do the PR now, I'll pass the ws.Channel to all the Server handlers.

Good point! I can do the PR now, I'll pass the ws.Channel to all the Server handlers.

I merged this PR in the meantime.
It's gonna be quite a few changes, since you'll need to change the callback's signature, so I thought it would be best to keep it separate.


nuxt-bridge Uncaught ReferenceError: webpackHotUpdate is not defined

Environment

Operating System: Darwin
Node Version:     v16.15.0
Nuxt Version:     2.16.0-27616340.013f051b
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      srcDir, ssr, dev, alias, image, generate, head, typescript, publicRuntimeConfig, privateRuntimeConfig, css, loading, loadingIndicator, plugins, components, buildModules, modules, apollo, proxy, axios, vuetify, build, serverHandlers, devServerHandlers, bridge
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Reproduction

Describe the bug
From time to time, I get this warning in my console after page refresh.
Additional context
No response
Logs
No response

Did you see https://github.com/nuxt/bridge/issues/43?

@dargmuesli  thank you for the reply. Let me try some solutions provided there and get back to you.

What did you find out?

Hello @dargmuesli sorry wasn't able to get back to you.
I don't see the error now
    bridge: {
        nitro: false,
        autoImports: true,
    },

Because i turned off nitro.
Issue might be related to vite

If the error is gone, feel free to close this issue.

@dargmuesli It is not yet resolved, i believe.
The link you sent me referenced doing this

Which kinda removes the error but I believe it is just a work around.

Correct. But that's why #43 is still open. Can we close this issue to not have duplicates?

no worries @dargmuesli ,
By the way #43  says error during extractCSS.
Mine errors even without extractCSS


Add integration tests for C# and proxy

What does this PR do?
Add integration tests for:

Functions instrumented with the .NET tracer using the lifecycle API
Functions instrumented with the experimental proxy

Skip the integration tests for timeouts. We are seeing flaky behavior around tagging cold_starts after a timeout (sometimes true, sometimes false) that makes these tests unreliable for now.
Additional Notes

Also makes DD_TAGS and DD_EXTRA_TAGS consistent across all integration tests

Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[x] The appropriate team/.. label has been applied, if known.
[x] A release note has been added or the changelog/no-changelog label has been applied.

🎉  LGTM! I only left one small nit


prepare sdk for fuel-core upgrade

I am preparing our SDK for the upcoming release of fuel-core and I will use this PR for feedback on some breaking changes.
fuel-core split up ConsesnsusParameters into smaller parameters and one is called TxParameters. In the SDK we already have a type called TxParameters. For now, I import the ConsesnsuParameters one as FuelTxParameters. What do you think about this ?
Please have a look at the other changes to:

get_message_proof not uses Nonce instead of the message_id
predicates do not use ChainId for address calculation
manual_blocks_enabled is replaced with debug in local chain config
fee_checked_from_tx uses FeeParameters

Checklist

[x] I have updated the documentation.
[x] I have added necessary labels.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.

closed in favor of: https://github.com/FuelLabs/fuels-rs/pull/1200


--single-instance not working properly

Homework

[x] I looked at nativefier --help and https://github.com/nativefier/nativefier/blob/master/docs/api.md
[x] I searched existing issues, open & closed. Yes, my bug is new.
[x] I'm using the latest version available at https://github.com/nativefier/nativefier/releases

Bug description
When I build an app using the --single-instance flag, it starts another instance when I click in a link with target="_blank" inside the application directing to the same URL as the application.
Steps to reproduce
When i start an application using a domain like "example.com", using the --single-instance flag, every time I click in a link like: Test it will start another instance of the application.
nativefier https://example.com/ --platform windows --min-width 800 --min-height 600 --maximize --hide-window-frame --disable-dev-tools --single-instance --tray --file-download-options "{\"saveAs\": false, \"directory\": \"C:\/Downloads\/123\"}" --background-color #EEEEEE

Expected behavior
I expected the application to open the link in a browser, the same way other URLs do. I believe that if someone needs this behavior, it shouldn't use the "--single-instance" flag...
Actual behavior
When I click the link it starts another instance for the application.
Context

Nativefier: 42.2.1
Node.js: 14.15.4
Npm: 6.14.10
OS: Using both Windows and MacOS

This is intended. --single-instance prevents launching the application multiple times. Having multiple windows/browser views open is still the same instance/process.
I am not sure how to get around that with the current APIs if it is on the same domain. I would think a new option --single-window might be what you are looking for but that doesn't exist yet.

@mlscherer it seems to me what you are expecting here is less 'single instance' (of a running application) and more 'single window'. Would you agree?

Closing this for now. Will reopen if we can get a clarification on the desired behavior.


Adding a threadpool starvation tutorial

https://github.com/dotnet/diagnostics/issues/2907
This depends on the updated sample code in https://github.com/dotnet/samples/pull/5113

cc @dotnet/dotnet-diag

Unrelated: Does dotnet stacks report group similar stacks together? That would make it a bit more usable in these cases, sorta like paralell stacks.

Unrelated: Does dotnet stacks report group similar stacks together? That would make it a bit more usable in these cases, sorta like paralell stacks.

No, not yet, but let's workshop this idea in the diagnostics repo. I like the idea of having varying ways of presenting stacks quickly at the commandline.

@IEvangelist - thanks for the review! When you could please take another look and see if we've got everything in good shape.
I don't have commit rights but I am happy to have you merge it if its ready.


tests: arm_zero_latency_irqs: Allow for platform specified IRQ

On the CC3220SF platform the assumption that all IRQ numbers are valid
from 0..CONFIG_NUM_IRQS isn't true.  As such when the code that tries to
find a free IRQ grabs one, it will get an IRQ number that is associated
with a non-existent IRQ.  And thus the test fails since the IRQ handler
will never got called.
To workaround this, allow platforms to specify the IRQ number to test on
if the logic for finding an IRQ isn't valid for that platform.
Fixes #18593
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Feel free to close this if you've got a better solution.


fix tsconfig preventing emitting commonjs bundles

I noticed that the published package<EMAIL_ADDRESS>does not publish any commonjs bundle, which caused some issues importing theses packages into a nodejs application.
Looking deeper into it I noticed that the tsconfig file for these two packages have an override to emit esnext style modules instead of commonjs, which means npm run build:commonjsand npm run build:esnextwill end up emitting the same bundle,
reming this override will no emit commonjs style bundles in the distfolder and esnext style bundles in the libfolder.
It would be great if a release for this packages could be made, to make them usable in node.
@SamBroner @DLehenbauer

fwiw this change is covered in #6197 as well if you don't want to make it explicitly here

#6197 is merged so this fix should be made already. @karlbom I'll publish new pre-release versions of the packages and post the versions here.

@tylerbutler marvellous, thank you!

@karlbom packages >=0.40.0-25719 should include the fix. Sorry for the delay on the publishing.


Adam optimiser not following Pytorch conventions

Both BertAdam and OpenAIAdam don't follow the pytroch convetion to define the betas parameter for  Adam Optimisers as a tuple, but instead has parameters b1 and b2.
Pytorch based libraries like fastai expect the optimizer betas to be a tuple.
Any reason b1/2 is used instead of a tuple? Would be great to change so the optimisers can integrate with other pytorch libraries.

We could update that indeed, that's just a relic of the Tensorflow conversion.
Do you want to submit a PR? Otherwise I'll do it when I work on the next release.


[UPSTREAM] Update ApiGroups for ocp 4.9 (#147)

(cherry picked from commit 53066598d02267335e709f217b6162da1ddd9ff1)

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] For commits that came from upstream, [UPSTREAM] has been prepended to the commit message
[x] JIRA link(s): https://issues.redhat.com/browse/RHODS-2168
[x] The Jira story is acked
[ ] An entry has been added to the latest build document in Build Announcements Folder.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious)

Testing Steps:

Create osd cluster
Deploy custom operator deployment using instructions given here: https://docs.google.com/document/d/1Ga0khZqr-jGpi5ExPJ0Cz8RawI0INc0UGI6Q2O3fTJc/edit#heading=h.oa055wper42n
Check operator logs for errors


Starting ml backends shows 404

Describe the bug
The ml backends are getting initialized
successfully with the command
label-studio-ml init my_ml_backend --script label_studio/ml/examples/simple_text_classifier.py and generating output
Congratulations! ML Backend has been successfully initialized in ./my_ml_backend
but after doing label-studio-ml start my_ml_backend at localhost:9090 I am getting "GET / HTTP/1.1" 404 and in the browser also I am seeing The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
I have tried the same thing in the docker container made by this Dockerfile  image as well, but I am getting exactly the same error.
To Reproduce
Steps to reproduce the behavior:
Run: label-studio-ml init my_ml_backend --script label_studio/ml/examples/dummy_model.py
Expected behavior
The model page should open
Screenshots

Environment (please complete the following information):

OS: Ubuntu
Label Studio Version [v0.9.1.post1, 0 .8.2]

Additional context
I was trying to build a custom ml backend when I first this issue, but when I tried with the other ml backend examples given in the repo (huggingface, demo_model.py) I experienced the same thing any suggestion to help me debug this would be extremely helpful, I thought this is some compatibility issue but I ran the same thing in docker and it is still the same

@nishchay47b ML backend server doesn't have an index / page. Are you able to add ML backend to LS instance via Model page?

Sorry I misunderstood the model page as backend server page only, it is working at <IP_ADDRESS>:8080/model. Thank you for the response, closing this issue.


Data Gaps while Querying Aggregated Metrics via Thanos Queriers

Thanos, Prometheus and Golang version used:
v0.20.0

Object Storage Provider:
AWS S3
What happened:
In out setup, different local prometheus send metrics to Thanos using remote write. Some aggreagated queries are working perfectly fine and for some others we are seeing gaps. Also, for the queries that are showing gaps, we are seeing raw(un-aggregated) metrics and when a time window aggreagation operation is applied we are seeing gaps.
For example -
Query with no data gap -
prometheus_tsdb_head_series{pod=~"prometheus-k8s-.*",datacenter="NP-SJC6B-DC"}
Query with data gaps( with time window aggregation) - avg_over_time(prometheus_tsdb_head_series{pod=~"prometheusk8s-.*",datacenter="NP-SJC6B-DC"}[5m])
If time window is increased from [5m] to [1h] - avg_over_time(prometheus_tsdb_head_series{pod=~"prometheus-k8s-.*",datacenter="NP-SJC6B-DC"}[1h]) , data gaps are not there as all the data points are averaged for 1h time window.
We have max_source_resolution=1h set for all the queries in the Queriers UI, as auto downsampling is showing some data gaps. max_source_resolution=1h shouldn't effect querying last hour data, but setting auto downsampling or only raw data is resulting in more data gaps.
We are seeing same data gaps for the above if query time range is increased from 1h to 12h or 1 day.
since all un-aggregated metric data is there for the above example query, believe the issue is happening at the query layer. The following is the queriers config we are using -
- name: thanos-query
        image: quay.io/thanos/thanos:v0.20.0
        args:
        - query
        - --debug.name=query
        - --log.level=debug
        - --query.replica-label=prometheus_replica
        - --query.replica-label=replica
        - --query.auto-downsampling
        - --query.partial-response
        - --store=dnssrv+thanos-store-time-0-shard-0-grpc.thanos-prod.svc.cluster.local
        - --store=dnssrv+thanos-store-time-0-shard-1-grpc.thanos-prod.svc.cluster.local
        - --store=dnssrv+thanos-store-time-0-shard-2-grpc.thanos-prod.svc.cluster.local
        - --store=dnssrv+thanos-store-time-1-shard-0-grpc.thanos-prod.svc.cluster.local
        - --store=dnssrv+thanos-store-time-1-shard-1-grpc.thanos-prod.svc.cluster.local
        - --store=dnssrv+thanos-store-time-1-shard-2-grpc.thanos-prod.svc.cluster.local
        - --store=dns+thanos-receive-grpc.thanos-prod.svc.cluster.local:10901
        - --tracing.config-file=/etc/tracing/tracing-config.yaml
        - --query.timeout=5m
        - --query.lookback-delta=15m

Disabling query.auto-downsampling in above config didn't make a difference.
attaching example querier charts. These charts are at the Querier layer, not at Cache Frontend.

What you expected to happen:
There shouldn't be any data gaps while aggregating for all the queries.
Thank you for the help.

This may not be relevant, as we not missing data while remote writing to Thanos. But, just wanted to mention that we are not using any hashring for the receivers. Ingestion flow is like the following
Local Prometheus -> Remote Write -> AWS Network Load Balancer -> Thanos Receiver Replicas(Not part of any Hashring)
Receiver config is
        - receive
        - --tsdb.path=/var/thanos/receive
        - --debug.name=receive
        - --log.level=debug
        - --grpc-address=<IP_ADDRESS>:10901
        - --http-address=<IP_ADDRESS>:10902
        - --remote-write.server-tls-cert=/etc/cert/servercert-config.yaml
        - --remote-write.server-tls-key=/etc/certkey/servercertkey-config.yaml
        - --remote-write.server-tls-client-ca=/etc/certca/servercertca-config.yaml
        - --label=replica="$(NAME)"
        - --label=receive="true"
        - --remote-write.address=<IP_ADDRESS>:19291
        - --tsdb.retention=6h
        - --tsdb.min-block-duration=2h
        - --tsdb.max-block-duration=2h
        - --receive.default-tenant-id=NGN2
        - --receive.replication-factor=1
        - --objstore.config-file=/etc/config/object-store-config.yaml
        - --tracing.config-file=/etc/tracing/tracing-config.yaml

would the above ingestion setup cause any data gaps issues while Querying?
Any inputs will be much appreciated :)

Hi @bwplotka @squat any pointers on why these data gaps are happening? Very much appreciate your help.

Thank you for the inputs @wiardvanrij.
Graphs don't have any gaps if we directly query local prometheus and we don't see any data missing when local prometheus writes to Thanos receivers. Think the issue is happening at the Thanos Queriers and we are not seeing data gaps for every graph, some are perfectly fine.
For the same time period, below shows that we are able to query raw metrics(Pic 1), but when the aggregation happens data is missing(Pic 2)

After adding Receiver Hashring, we are not seeing any data gaps in the dashboards. Closing this!


Add qemu-image option lazy_refcounts=on for virt-sparsify

We need to update the virt-sparsify command since it is causing issue for created disk images on the hyperkit. In 4.1.6 tag we didn't used virt-sparsify and it was working without any issue for stop => start but 4.1.9 is not working. Looking closer looks like if we are using the virt-sparsify without qemu-img options lazy_refcounts then after stop the VM the disk image no longer a qcow2 and it failed to boot.
From cache when we fresh create it have qcow2 so that works but stop=>start not works.
$ file ~/.crc/cache/crc_hyperkit_4.1.11/crc.qcow2
/Users/prkumar/.crc/cache/crc_hyperkit_4.1.11/crc.qcow2: QEMU QCOW Image (v3),<PHONE_NUMBER>4 bytes

After stop and start.
$ sudo file /Users/prkumar/.crc/machines/crc/crc.disk
/Users/prkumar/.crc/machines/crc/crc.disk: data

$ sudo hyperkit -A -u -F /Users/prkumar/.crc/machines/crc/hyperkit.pid -c 4 -m 8192M -s 0:0,hostbridge -s 31,lpc -s 1:0,virtio-net -U d1e0b3fa-c6e7-11e9-a9d2-f2189899ab08 -s 2:0,virtio-blk,file:///Users/prkumar/.crc/machines/crc/crc.qcow2,format=qcow -s 3,virtio-rnd -l com1,autopty=/Users/prkumar/.crc/machines/crc/tty,log=/Users/prkumar/.crc/machines/crc/console-ring -f kexec,/Users/prkumar/.crc/cache/crc_hyperkit_4.1.11/vmlinuz-4.18.0-80.7.2.el8_0.x86_64,/Users/prkumar/.crc/cache/crc_hyperkit_4.1.11/initramfs-4.18.0-80.7.2.el8_0.x86_64.img,earlyprintk=serial BOOT_IMAGE=/ostree/rhcos-e1b8fa18a8f068bad264a0043d69d8f6d39265d77ab9857d142ab8c65a5ad219/vmlinuz-4.18.0-80.7.2.el8_0.x86_64 console=tty0 console=ttyS0,115200n8 rootflags=defaults,prjquota rw root=UUID=a8fbdcb1-63ea-421e-8f6f-dac9cbbcc822 ostree=/ostree/boot.0/rhcos/e1b8fa18a8f068bad264a0043d69d8f6d39265d77ab9857d142ab8c65a5ad219/0 coreos.oem.id=qemu ignition.platform.id=qemu
mirage_block_open: block_config = file:///Users/prkumar/.crc/machines/crc/crc.qcow2 and qcow_config = None and stats_config = None
hyperkit: [ERROR] Mirage block device raised exception: (Failure "Expected magic: got 2c")
Mirage-block error: Block device is disconnected
Could not open mirage-block device: Invalid argument
Could not open backing file: Invalid argument

Fix by #85


Reduce use of PortUtil

Describe the issue
I would like the HAPI FHIR tests to be more stable, and to behave reasonably when run concurrently.
Reading the Javadoc of PortUtil, it is very surprising to me that using new ServerSocket(0) is not good enough to find a free port. The doc mentions that allocating a free port can sometimes fail, but I haven't seen or heard of this problem on other projects, and e.g. the Linux bind() docs don't mention it as a possibility (http://man7.org/linux/man-pages/man2/bind.2.html). The only case where allocating a free port should fail, is if all ephemeral ports are busy. If this happens, PortUtil won't help either.
I think it would be better to simply ensure that we can pass 0 into any server we need to start during a test, and then provide a method on that server to get the currently bound port. This method has been used on other projects (e.g. Apache Storm), and seems to have eliminated port collisions for tests there, without having the resource leak drawback (and extra code maintenance) that PortUtil has.
I've updated a few tests to demonstrate how I would prefer the port allocation to work, see https://github.com/jamesagnew/hapi-fhir/compare/master...srdo:reduce-portutil-use?expand=1. I'm happy to make this change to the remaining tests, but if the idea is rejected up front, I'd prefer not to do unnecessary work.
The only valid use of PortUtil that I can see is for tests that want to get an unused port to check client behavior when connecting to an unbound port.

Hi @srdo - The issue isn't that allocating a port will fail, it's that under heavy multithreading it appears that two concurrent calls to new ServerSocket(0) happening in separate processes can sometimes return the same port (which means that one is going to fail eventually). At least on Linux this seems to be the case. All of the logic in PortUtil is there in order to avoid that.
I like your idea if it consistently works, although I would speculate that ultimately it will result in concurrent calls to new ServerSocket(0) so it would result in the same kinds of failures.
Note that this issue never happens when running the tests from an IDE since it (at least IntelliJ) doesn't run tests concurrently. It does happen often enough though on both my Ubuntu workstation as well as the Travis CI server.

@jamesagnew Thanks for elaborating. I couldn't get the concurrency issue to happen on Windows by running a good number of threads all opening and closing ServerSockets on port 0, but maybe it only happens on Linux or when the processes requesting ports are different.
I'll set up a Linux box and see if I can get it to happen for me. If not I'll try updating HAPI FHIR to use the pattern I mentioned, and will try running the tests a good number of times on Linux to see if it fails.
Just to make sure, when you've seen the issue happen, the failing code has been doing something like
ServerSocket socket = new ServerSocket(0);
//Use socket

and nothing like
ServerSocket socket = new ServerSocket(0);
int freePort = socket.getPort();
Server server = new Server(freePort);

right?

I'm not clear on the distinction there... We only ever use PortUtil to find a free port so we can open a server on it, what else could we use the port for?

Sorry, I should have been more clear. What I meant was, before you had PortUtil, when you were seeing these port collisions, were you opening a socket with new ServerSocket(0) and then using the socket directly (the first bit of code I posted), or were you opening a new socket with new ServerSocket(0), getting the port, closing the socket and then opening something else using that port (the second bit of code)?
The reason I'm asking is that the second pattern is pretty common, and is also thread unsafe, as the port you get from new ServerSocket(0) is only reserved as long as the socket is open.
Basically I'm asking whether before PortUtil was added you were doing
Server server = new Server(0);

and that was throwing address in use exceptions, or whether you were doing
ServerSocket socket = new ServerSocket(0);
int freePort = socket.getPort();
socket.close();
Server server = new Server(freePort);

ah ok, we've only ever had portutil... it's gotten more fancy over time (which has dramatically cut down on the bind errors) but we've always followed the pattern like the second thing you listed above.
Worth noting though, it really looks more like:
ServerSocket socket = new ServerSocket(0);
int freePort = socket.getPort();
log.info("Obtained the free port: " + freePort);
socket.close();
Server server = new Server(freePort);

And looking at the logs you can directly see two JVMs logging the same port at the same millisecond. That seems to be the fundamental problem.

Ok, then I feel more at ease. In the code you posted it is possible that thread A logs and closes the socket, and then thread B gets a socket with the same port. I think it's worth trying the "open-server-and-read-port" pattern. Will start working on it, will open a PR when it looks stable.


Rework References

Remove references.lua and refactor with existing script-extender functionality

Fixed in https://github.com/Shresht7/Stats-Configurator/commit/3e4db5141f247154ebb330915836bba9f61ac8de

Fixed in https://github.com/Shresht7/Stats-Configurator/commit/3e4db5141f247154ebb330915836bba9f61ac8de


Updated hip_blas header of hcc path

This commit incorporates few additional APIs and prototype changes on HCC path of hip_blas headers.
Inorder to avoid conflict with the installed header's via hcblas, I am attempting to update the hip_blas hosted under hip as well

No longer required to merge this since hip_blas headers have moved to the hcblas repo.


[Bug] The 'Tracking error occured' message displayed at successful auto-annotations at use tracker function.

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour
Objects were selected and error message does not display.
Current Behaviour
Objects were select and error 'Tracking error occuruced, Error: Frame 10 does not exist in the job' message display.
Possible Solution
Fix the bug.
Steps to Reproduce (for bugs)

Create task with 10 images (0-9 frames).
Install 'pth-foolwood-siammask' function (type is tracker).
Run auto-annotations for all frames.
 No
Operating System and version (e.g. Linux, Windows, MacOS): Ubuntu 20.04
Code example or link to GitHub repo or gist to reproduce problem:
Other diagnostic information / logs:
Logs from `cvat` container

Next steps
You may join our Gitter channel for community support.

@ActiveChooN Could you please look at the issue till the next release (February 28)?

@bsekachev, sure


Make Terragrunt recover from missing module and provider error

This change enables Terragrunt to detect errors that otherwise required the user to run "terraform init" and attempt a recovery by running Terraform automatically.
When a Terraform module or provider version changes or when a module or provider is missing and Terragrunt is invoked with an action other than "init" (e.g., plan, apply, etc.), then the Terraform run that has been started by Terragrunt will terminate with an error asking the user to run "terraform init" to reinitialize to fetch the missing runtime dependencies.
Terragrunt should detect these type of missing module and provider errors and automatically re-run "terraform init" to resolve them and retry the previous command automatically.
Signed-off-by: Krzysztof Wilczyński<EMAIL_ADDRESS>

hahah, lol, race condition with Yori and Jim detected.

Hi @brikis98, thank you for the review thus far! Much appreciated.
There is another use-case I need to test this solution against - a more complex structure with nested sub-directories (when someone has complex infrastructure and their topology contains of a lot of different states being managed). Why? Because I need to verify how passing the terragruntOptions.TerragruntConfigPath to terragruntOptions.Clone() will influence execution in a more complex scenario.

Rebased against master.

Rebased against master.

Hi @yorinasub17, is there anything here left to be done?

Hi @yorinasub17 and @brikis98,
It appears that either Terraform release 0.13+ has a potential problem or the behaviour has changed at some point as per:
$ cat > main.tf
provider "null" {
    version = "2.1.1"
}
^D
$ terraform init

Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/null versions matching "2.1.1"...
- Installing hashicorp/null v2.1.1...
- Installed hashicorp/null v2.1.1 (signed by HashiCorp)

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

$ cat > main.tf
provider "null" {
    version = "9.9.9"
}
^D

$ terraform apply -auto-approve
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

$ terraform -version
Terraform v0.13.0
+ provider registry.terraform.io/hashicorp/null v2.1.1

This is not quite what I would expect, and it breaks integration test, sadly.

Weird. That sounds like a bug.  Perhaps file one in the Terraform repo?
Also, for the integration test, what about switching the source URL of a module instead of the provider version?

Hey, I'm having this issue with updating to terraform 0.13. I'm just going into all my subdirectories with terragrunt.hcl files and re-init'ing them, which seems to work, albeit a bit time consuming. Having a init-all --force command that I can run from my root directory that would force a re-init would be useful.


GRU layer fails on single GPU when using MirroredStrategy

System information

Have I written custom code: yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): windows and linux
TensorFlow installed from: binary
TensorFlow version: 2.0
Python version: 3.7

Describe the current behavior
Using single GPU and tf.keras.layers.GRU layer and model.fit with MirroredStrategy fails on error
Invalid argument:  var and delta do not have the same shape
tf.keras.layers.LSTM works fine on one GPU.
On machine with more GPU, the GRU layers works fine.
I know it does not make much sense to run Mirrored Strategy on only one GPU but it is good for testing your code before uploading it to multi gpu machine.
It works in TF 1.5.
Code to reproduce the issue
On Google Colab, use GPU runtime and run this code
%tensorflow_version 2.x
# %tensorflow_version 1.x <- here it works

import tensorflow as tf

print(f'TensorFlow ver. {tf.__version__}')
print(f"Num GPUs Available: {len(tf.config.experimental.list_physical_devices('GPU'))}")

ds = tf.data.Dataset.from_tensor_slices({
  'input': tf.zeros([64, 4]),
  'target': tf.zeros([64, 5])
})
ds = ds.batch(3)

strategy = tf.distribute.MirroredStrategy()

with strategy.scope():

  p_input = tf.keras.Input(shape=[4], name='input')
  p_target = tf.keras.Input(shape=[5], name='target')

  # gru = tf.keras.layers.LSTM(8) # <- this works
  gru = tf.keras.layers.GRU(8)

  x = p_input
  x = tf.expand_dims(x, axis=-1)
  x = gru(x)
  x = tf.keras.layers.Dense(5, activation='tanh')(x)

  model = tf.keras.Model([p_input, p_target], x)
  model.add_loss(tf.keras.losses.MSE(p_target, x))

  model.compile(optimizer=tf.keras.optimizers.SGD())
  model.fit(ds)

Other info / logs
TensorFlow ver. 2.0.0
Num GPUs Available: 1
WARNING:tensorflow:Output dense_9 missing from loss dictionary. We assume this was done on purpose. The fit and evaluate APIs will not be expecting any data to be passed to dense_9.
      1/Unknown - 3s 3s/step
---------------------------------------------------------------------------
InvalidArgumentError                      Traceback (most recent call last)
<ipython-input-10-e5114f02da9a> in <module>()
     32
     33   model.compile(optimizer=tf.keras.optimizers.SGD())
---> 34   model.fit(ds)

11 frames
/usr/local/lib/python3.6/dist-packages/six.py in raise_from(value, from_value)

InvalidArgumentError: 2 root error(s) found.
  (0) Invalid argument:  var and delta do not have the same shape[8,24] [2,24]
	 [[node SGD/SGD/update_1/update_0/ResourceApplyGradientDescent (defined at /tensorflow-2.0.0/python3.6/tensorflow_core/python/framework/ops.py:1751) ]]
  (1) Invalid argument:  var and delta do not have the same shape[8,24] [2,24]
	 [[node SGD/SGD/update_1/update_0/ResourceApplyGradientDescent (defined at /tensorflow-2.0.0/python3.6/tensorflow_core/python/framework/ops.py:1751) ]]
	 [[ArithmeticOptimizer/ReorderCastLikeAndValuePreserving_int64_Cast_3/_18]]
0 successful operations.
0 derived errors ignored. [Op:__inference_distributed_function_24603]

Function call stack:
distributed_function -> distributed_function

I could reproduce the issue. Here is the gist. Thanks!

Thanks for reporting the issue. We also found a similar issue internally, it is caused by the graph rewrite between cpu kernel and gpu kernel.
For now, if you want to walk around the issue with some performance loss, you can add "gru.could_use_cudnn = False" to disable the cudnn path, which will allow the model to run, but just not use the fused cudnn GRU kernel.
We will fix the graph rewrite in future release.

@reedwm

Thanks for the workaround.
Question:
Considering the fact that it does work on multiple gpu, does it mean that the cuDNN path is not used  when more than one gpu is used?

In the colab, TF 2.0 is still being used instead of the nightly, despite installing tf-nightly-gpu. I am not familiar with colab so I am not sure why this is happening. The colab prints the version is 2.0.0, but the nightly version will look similar to to 2.1.0-dev20191023. I confirmed the issue does not occur in the TF nightlies by running outside colab.
The fix will be in TF 2.1, so you might want to just wait until that is out. Closing this issue since this is fixed in the nightlies.

Considering the fact that it does work on multiple gpu, does it mean that the cuDNN path is not used when more than one gpu is used?

I am not sure, but since this will be fixed in 2.1, I do not think it's worth investigating.


added proxy as request options

Allow to send request options such as proxy and timeout from api

@chiragkatare can you please resolve this conflict


Gift : Insufficient balance

Please check below screen recording
https://github.com/bithyve/bitcointribe/assets/107177634/eae1f6cd-fd13-4878-8dc9-51024c0b4418

Verified this issue on Tribe app v 2.3.0(619)


ConditionalPathPoint's sometimes don't visualize correctly

Using this model: model_vas_conditionalpathpoints.zip

(to see issues more easily): Show only knee_ext_r muscle group, hide body patella_r

At default pose, 3 vasti muscles have a kink in them, but ConditionalPathPoint should not be engaged until deep knee flexion

Change knee flexion coordinate to >90 deg. One of the path points sticks out very far

Returning the knee flexion to < 90 deg (either by using the slider or setting the coordinates back to Default state) does not undo the stray path point

Note: Another gait model with ConditionalPathPoints in vas, rec_fem, and iliopsoas seems to visualize OK (see OpenSim/Examples/Moco/example2DWalking/2D_gait.osim)
@aymanhab

I am seeing a different but potentially related issue where consecutive ConditionalPathPoints do not visualize correctly when some of them are inactive.
This issue can be reproduced in OpenSim 4.3 using the model BothLegs.osim from Applications\Analyze\test in OpenSim Core.
Here the right knee is flexed to -108 degrees, with only the right VASLAT shown for clarity. In this screenshot, the ConditionalPathPoint VASLAT-P3 is activated but VASLAT-P4 is not, and two separate lines are being drawn for the muscle.

Increasing flexion to -110 degrees activates VASLAT-P4 and the muscle is drawn correctly.

For the record, this is not an issue with conditional path points but interaction between conditionalpathpoints and wrapping. In fact if you delete the wrapping on the wrapping tab, the conditional path points acts exactly as expected. Not to justify the bug but for testing when a fix is ready.

@nathantpickle Once the build artifact is ready you can give it a spin and let me know if you encounter other issues

@carmichaelong maybe you can test this as another pair of 👀 if @nathantpickle didn't get to it

Apologies for the delay, @aymanhab - I just tested this and it looks good to me. Thanks!


contains only does not seem to work for primitive array

this should not pass, but does:
* def actual = [1, 2, 3]
* def expected = [2, 2, 3]
* match actual contains only expected

interestingly the reverse fails as expected:
* def actual = [1, 2, 3]
* def expected = [2, 2, 3]
* match expected contains only actual

for those wanting to fix this, the logic is in MatchOperation, should be easy and fun: https://github.com/karatelabs/karate/blob/v1.2.0.RC1/karate-core/src/main/java/com/intuit/karate/MatchOperation.java#L525

@ptrthomas I can pick this up

@Nishant-sehgal thanks, all yours 👍

this should not pass, but does:
* def actual = [1, 2, 3]
* def expected = [2, 2, 3]
* match actual contains only expected

interestingly the reverse fails as expected:
* def actual = [1, 2, 3]
* def expected = [2, 2, 3]
* match expected contains only actual

for those wanting to fix this, the logic is in MatchOperation, should be easy and fun: https://github.com/karatelabs/karate/blob/v1.2.0.RC1/karate-core/src/main/java/com/intuit/karate/MatchOperation.java#L525

I think it is correct only right?
Case 1:
Array1 has 3 different elements -> 1,2,3 and Array2 has 2 different elements (2 being repeated twice and 3).
So, Array 1 has all the unique elements present in Array2 so it is getting passed.
Case 2:
Fails as expected because 1 is present in Array2 and not in Array1.
Is something there that I might be missing? @ptrthomas

@jatin14493 I agree this is confusing. the original intent of contains only is to do an array equality check ignoring order.
but the docs currently say:

all elements are present but in any order

anyway, I'll wait for @Nishant-sehgal to complete analysis - and I personally feel we should check that all elements on the RHS are "accounted for"

https://github.com/karatelabs/karate#match-contains-only
As per the documentation, it checks if the second array has all its' elements being contained in the first array.
`* def data = { foo: [1, 2, 3] }

match data.foo contains 1
match data.foo contains [2]
match data.foo contains [3, 2]
match data.foo contains only [3, 2, 1]
match data.foo contains only [2, 3, 1]`

All these are succeeding as data.foo is the superset of all the elements of the example sub-arrays.
contains only additionally checks that size should be same and contains condition. :)
@ptrthomas Are you suggesting, contains only should be something like match 2 arrays even when the elements are un-ordered?

Are you suggesting, contains only should be something like match 2 arrays even when the elements are un-ordered?

yes. to be honest this was the original "use case" for contains only in the first place

It is indeed interesting to add support for this.
Problem statement is like: You are given 2 unsorted arrays and duplicates are allowed we need to check if they have the same element.
Have thought of 3 approaches will share the analysis soon.Just verifying few things before proposing a solution.

https://github.com/karatelabs/karate/pull/1798


Cherry picks from 4.2

Fixes for bad relocation generated error.
rdar://39221794

@swift-ci Please test macos

Build failed
Swift Test OS X Platform
Git Sha - 8762609f9de510e50446a8fdd37931fcb885a9be

Failed with unrelated:
/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-4.2-branch-03-26-2018/swiftpm/Sources/Basic/ByteString.swift:24:15: error: type 'ByteString' does not conform to protocol 'Hashable' public struct ByteString: ExpressibleByArrayLiteral, Hashable {               ^ Swift.Hashable:2:16: note: protocol requires property 'hashValue' with type 'Int'; do you want to add a stub?     public var hashValue: Int { get }                ^ --- bootstrap: error: build failed with exit status 1


Define a new type for derived DescriptorPublicKeys

After a brief chat on IRC and in PR #339, here's a quick draft for a new type specific to derived DescriptorPublicKeys.
This is the same design we use in BDK, where we wrap a normal DescriptorPublicKey and a secp context in a new struct. This has the drawback that the struct carries a lifetime and generic for the ctx, but I couldn't think of any other way to get this to work unless we drop the implementation of ToPublicKey for DerivedDescriptorKey which in my opinion can be very useful.

ToPublicKey for DerivedDescriptorKey which in my opinion can be very useful.

Indeed this is super useful. After we have private key derivations, we can add support for this. But for now, this would have to do.
Also, creating new verification contexts is now cheap(not exactly free still takes 50 micros seconds) as these contexts are now static in the underlying secp library. We are waiting on some cleanups from upstream secp after which creating verification contexts would be free!

Addressed most comments

Needs rebase, and does not compile currently I think because of rust-bitcoin updates. but ACK  e619be4efbca61ea7703b4ecec54f34df1bacfd8 -- this is much smaller/cleaner than I feared.

Rebased and fixed everything!

Rebased and fixed your last nit!


[TASK] Validator Class custom input

Issue Description
Is your feature request related to a problem? Please describe.
The dispatcher manager validators needs to allow for the deployment of validator-specific input XML blocks.
The code should allow for any derived validator to, optionally, define its own input specifications (e.g. options, settings, etc.)
Describe the solution you'd like
Activate the INPUT DATA reader within the validator class
Describe alternatives you've considered
hardcoded values (not optimal)

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Closure checklist passed...
Closure approved via #36


remote return false, but form.valid() return true(expect return false)

when the form field has value and the remote ajax(jsonp) request return false, invoke the $form.valid() return true(expect return false)
here is the example  http://jsbin.com/eresut/22/watch

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


Widget for backers (excluding organizations) does not seem to work embedded on website

Describe the bug
It’s not possible to get the widget for individual backers (excluding sponsors) to work.
To Reproduce
Steps to reproduce the behavior:

Go to the "Export" page on your organization https://opencollective.com/opensourcedesign/edit/export
Check the "Financial contributors widget" section
Notice there’s a lot of casino sponsors
Decide you want a widget with just the "real" people

Expected behavior
It would be cool if there would be a widget with just the actual backers, excluding organizations – which we already list separately.
Screenshots
The widget which is offered is this one:

The one we would like is this we use on GitHub since some time:

But when we use it on the website (testing locally) it doesn’t seem to work. Is this widget link supported at all?
https://opencollective.com/opensourcedesign/backers.svg?width=600
Desktop:

OS: Ubuntu 20.04
Browser: Firefox
Version: 84.0.1

Oh wow, just managed to make it work – the fix is to use
<object type="image/svg+xml" data="https://opencollective.com/opensourcedesign/backer.svg?avatarHeight=50&width=400"></object>
It is necessary to remove the id="lastOne" from the object to fix it.

Oh wow, just managed to make it work – the fix is to use
<object type="image/svg+xml" data="https://opencollective.com/opensourcedesign/backer.svg?avatarHeight=50&width=400"></object>
It is necessary to remove the id="lastOne" from the object to fix it.


”More Actions”-button (The 3 dots)

I use the button next to 0 on the magic remote, 3 dots on it, to turn on and off my receiver. In the manual this button seems to be named ”More Actions”. I cant for the life of me figure out how to map this button in my config.
For the record, the receiver is old, no hdmi, using optical, and does not want to be powered on/off with the magic remote (volume works fine).

Sorry, i also do not know what the ID of that button is. This is basically try and error till something works. Maybe there is someway a way to intercept that to find it out more easier but i do not know any other´method...

Ah alright. I did find an ipk on lg dev page that tells you the number of the button, but not the name Unfortionally

Maybe it is not possible to trigger that button using the webos API, and this is only available with the remote?

I contacted LG in an attempt to find out. They said that they could not disclose what API Command this button sends. I read that as it is doable with API, but they dont want to Tell me what the Command is.

In that you would need to somehow find another way to get the correct button ID. You could continue to try out different names or do some sniffing.

Would you need the acctual name of it, or would the number work aswell? If numbers work I could basicly just do buttons for every number to 250 or whatever and Try them all.

This needs to be an ID as far as i know.


Add shields.io badges

Add some useful badges from shields.io

Changes Unknown when pulling 1e788d2d959969e9497c0ca6941dbda9c1f7042a on shields into ** on master**.

Changes Unknown when pulling 1e788d2d959969e9497c0ca6941dbda9c1f7042a on shields into ** on master**.

Changes Unknown when pulling 5fc66f8bbc8a8ed3567adf5fcc3a93d78f9dd282 on shields into ** on master**.

@alvarolopez can you rebase this PR?

Jenkins, test this please!

approved

ok to test.

Add @gwarf to whitelist.

Jenkins, test this please!

Once again, test this please!

I cannot update anymore this PR, can we close it, delete the shields branch and focus on https://github.com/EGI-Foundation/cloud-info-provider/pull/97 ?


Add ST's m24c01/02 devices + Impl embedded_storage traits

In this PR, I have done three things:
First, I have changed the SlaveAddr::devaddr method a little bit and added quite some documentation. When I started looking into this package, it took me a little bit to unravel what this method does and especially why it does so. In case you are happier with the old code, that is fine. But at least (memory_address & !(1 << address_bits)) >> shift can be replaced by the equivalent and simpler memory_address >> shift. And I would like to keep the comments because they would have helped me a lot in understanding why data address and device address bits are mixed combined like that (I am working with an M24C02 which does not do so).
Second, I have added ST's m24c01/02 devices. They differ from at24x01/02 in using 16 byte pages instead of 8 byte pages. To distinguish those, I have called the constructor methods new_m24x01. The generating macro currently requires $dev and $part for the doc string which is constructed as "Create a new instance of a M24C01 device (e.g. M24C01)". This reads a little bit weird compared to the previous doc strings, e.g. "Create a new instance of a 24x16 device (e.g. AT24C16)" but I do not know if there are other devices which are compatible with the M24C01/02 ones. So, I would personally just accept that.
Third and finally, I have implemented the embedded_hal traits ReadStorage and Storage which allow to access the whole memory range without taking care of pages when writing. To handle the required delay between subsequent write operations, I needed to add an embedded_hal::timer::CountDown dependency. To keep this out of the low-level eeprom driver, I have created another type Storage which combines the driver and the CountDown. Like this, the users can decide if they want to use the low-level interface and handle the overhead themselves or if they prefer the overhead of supplying a CountDown.

Coverage decreased (-7.8%) to 90.837% when pulling<PHONE_NUMBER>b2287c377eb23c01470138f398f462 on DrTobe:embedded-storage into d9674f874a509d878759c80b78170c0f5ee9e4ba on eldruin:master.

So the 1.31 builds fail because embedded-storage 0.2.0 uses the slice.fill method introduced in 1.50. Downgrading to embedded-storage 0.1.0 seems to work but I would rather like not to do so. What do you think about it?

Most is done.

About the CountDown timer ...

In the beginning, I tried to come away without a timer dependency by using the polling method but that does not work either. When using the polling method, you assume that the reason for not being able to access the device is that the device is still busy and will be available eventually. In the worst case scenario, something might break in between and you end up in an infinite loop. One could come up with the idea to limit the number of retries but that is just a bad way to implement a timeout. So the only proper way to implement the polling method is to start some kind of timer and report failure as soon as it times out. So as far as I can tell, a timer is definitely required to implement embedded_storage::Storage here. I did not want to impose this requirement on all users, so I created the Storage struct which allows the users to opt-in. If the CountDown timer is actually removed from embedded-hal, it can be replaced with something else. But currently, using it seems to be the most intuitive way in embedded Rust world.

Furthermore, the embedded-storage traits do not specify that the operation must have been completed in the hardware before returning. I understand it would make a lot of sense, but busywaiting is generally a hard sell in embedded.

That is right but we definitely need to wait (or poll) when writing over page boundaries. We could remove the last delay but this would require us to remember that we have already written before (apparently, this does not seem to be so hard, I will give it a try). So I did it like that to keep the code simple and because I assumed that users would know that writing to eeprom can take some time so they should be prepared anyways.

It took me a while to review the new devaddr implementation since there was an extra zeroing of the (address_bits+1)th bit

And I was confused why only the (address_bits+1)th bit was zeroed and not all (address_bits+n)th (n positive) bits. In the current implementation we rely on some guarantees from the caller but this seems to be ok because the method is not public.

In this case, would it be possible to use a DelayUs instead of a CountDown? It should be the same but that one will make it to embedded-hal 1.0.

If we stick to the delay-approach, we will definitely do so but ...

We could remove the last delay but this would require us to remember that we have already written before (apparently, this does not seem to be so hard, I will give it a try).

I have implemented the alternative: We start the CountDown after writing and wait before each i2c access. This already speeds up many accesses (which do not cross page boundaries) but it has two downsides:

This can not be done with a DelayUs
We can not guarantee that the user does not access the eeprom too early with the low-level methods. But this could be documented (as you suggested in the beginning) so it should be fine. Furthermore, most users will probably only be using the one or the other interface to the eeprom.

So if getting rid of the CountDown is more important to you than this 5 ms speedup, I am fine with reverting the last commit.

Would you have interest in having a try at implementing this by converting the page size Eeprom24x parameter into a const parameter and using that instead of this trait?

I have thought about that possibility, too, but I am not sure about how much time it would take me. For the project my team is currently working on, the current implementation already does what we need and we are in quite a tight schedule at the moment. So I would prefer finalizing this as is and open up follow-up issues which cover the polling method and const generics.

re. CountDown start/wait reorder:
That is an interesting optimization. However, it has pretty hard downsides as it stands:

The behavior of calling CountDown::wait() before CountDown::start() is unspecified. So calling write could immediately panic, deadlock, or do nothing depending on the CountDown implementation.
The CountDown object must be in a correct state before calling. e.g. If a user reuses a CountDown which has been used to wait before, the behavior of calling wait again is again unspecified (implementors are advised to panic). This cannot be mitigated by canceling the CountDown before the bytes loop because this takes us back to 1.

It is possible to avoid the final 5ms wait when using DelayUs by having the delay call at the end of the loop and checking if there will be another loop iteration before actually calling delay_ms. An advantage would be the consistency with the rest of the library. A downside is that the user might forget to wait before the next call.
re. const generics. That is fine for me for now, it would only improve the library design. In that case, can you seal the PageWrite trait and write in its documentation that is only for internal use?

It looks like this works but I do not know why:

CountDown::wait returns nb::Result<(), Void>, why can we just change/ignore that?
On my system, I can not build anymore for the no-std targets like thumbv7em-none-eabihf because the void dependency is still there via linux-embedded-hal which requests it with the default features (i.e. std)

Ah, sorry about that. I forgot we used void in e-h 0.2.
It fails on CI here as it should. Could you just revert the last commit? I will merge this then.

I have published this in version 0.5.0.
For the record, I dabbled with converting the page size and address size parameters into const. This did not lead to a simplification of the library and is not worth pursuing because of two reasons: the address size parameter is used to control whether the chips have a write_page method (24x00 does not) and also it is not possible to perform basic mathematical operations with these parameters.
In the end parameters would need to be added without a tangible benefit and the design would actually be more complicated.


No response during register MC in my mobile app: Use Mobile Services to Create UI

Tutorial URL: https://developers.sap.com/tutorials/cp-apim-sales-tracker-create-ui.html
Please specify the step you are referring to Step 3: Scan QR code
In this step, I have the Registration(Android) address: https://mobilecards/configure?serverURL=https://hcpms-i312717trial.hanatrial.ondemand.com&oauthClientId=b9d68bee-2741-4029-a6a5-3fc29a03e1f2
Then I open the Mobile Cards in my mobile, But after I pasted the above address and agree with the agreement, sometimes later, back to the initial screen, can not register.

You have to subscribe with your ID. Are you doing that

Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


[Workers] non-reference wrangler commands need 'npx' in front of them

PCX-9321
As per guidance to install locally, all commands other than reference commands (like /workers/wrangler/commands/) need npxin front of them or they will not function.

As per guidance to install locally, all commands other than reference commands (like /workers/wrangler/commands/) need npx in front of them or they will not function.

Support this change, but just to spell this out (for myself as much as anyone else) to make sure we have a shared understanding of rationale:
Without npx: The globally installed version of wrangler will be used, if present.
With npx: The locally installed version of wrangler will be used, if present (ex: my project has wrangler 3.1.0 in its package.json). If wrangler is not installed locally, the latest version of wrangler will be installed (to the npm cache dir) and used.
So if you're to follow our docs today by the book, it's true that without npx in front, wrangler can't be found, since it's not installed globally and running without npx won't pick up a locally installed version.
Our docs currently do not instruct people to install wrangler globally:
https://developers.cloudflare.com/workers/wrangler/install-and-update/
But I wonder if it's worth elevating this note in some way as a "Always use npx — here's why:" kind of section that explains ^ the above.

Running npx wrangler will use the latest version of Wrangler except when there is already a Wrangler version installed in the current folder. In this case, it will use the locally installed version instead.

Also wonder if we should be louder about suggesting that people always use npx on the reference commands page itself? (https://developers.cloudflare.com/workers/wrangler/commands/)

As per guidance to install locally, all commands other than reference commands (like /workers/wrangler/commands/) need npx in front of them or they will not function.

Support this change, but just to spell this out (for myself as much as anyone else) to make sure we have a shared understanding of rationale:

Without npx: The globally installed version of wrangler will be used, if present.
With npx: The locally installed version of wrangler will be used, if present (ex: my project has wrangler 3.1.0 in its package.json). If wrangler is not installed locally, the latest version of wrangler will be installed (to the npm cache dir) and used.

So if you're to follow our docs today by the book, it's true that without npx in front, wrangler can't be found, since it's not installed globally and running without npx won't pick up a locally installed version.
Our docs currently do not instruct people to install wrangler globally:
https://developers.cloudflare.com/workers/wrangler/install-and-update/
But I wonder if it's worth elevating this note in some way as a "Always use npx — here's why:" kind of section that explains ^ the above.

Running npx wrangler will use the latest version of Wrangler except when there is already a Wrangler version installed in the current folder. In this case, it will use the locally installed version instead.

Aimed to address this point in https://developers.cloudflare.com/workers/wrangler/commands/#background without getting into the details of the "we once supported global install in 2021, now we do not in 2023" background story. And also made it clear that this is a reference page and how to run each command with the desired package manager in background, with clear instructions to install locally in install and update page.

Also wonder if we should be louder about suggesting that people always use npx on the reference commands page itself? (https://developers.cloudflare.com/workers/wrangler/commands/)

I'll add a linkout to the background on package managers in install and update page to make it more discoverable and clear that with local install you need to run commands in the way described in the Commands page.


chore: update ex_aws to the latest version.

This change simply updates this repository to the latest version of ex_aws. This allows downstream projects to use the latest 2.2.x releases.

Thanks @jonathanhood


Provide better error message when profile.release.strip = "symbols"

The Problem
If you have profile.release.strip = "symbols" in your Cargo.toml (a common binary size optimization) then iai-callgrind will attempt your benchmarks as normal, only erroring on parsing the callgrind output with a cryptic error message:
my_benchmark::bench_fibonacci_group::bench_fibonacci short:10
iai_callgrind_runner: Error: Error parsing file '/home/rene/Documents/Java/callgrind/callgrind-test/target/iai/callgrind-test/my_benchmark/bench_fibonacci_group/bench_fibonacci.short/callgrind.bench_fibonacci.short.out': Sentinel 'iai_callgrind::bench::' not found
error: bench failed, to rerun pass `--bench my_benchmark`

Caused by:
  process didn't exit successfully: `/home/rene/Documents/Java/callgrind/callgrind-test/target/release/deps/my_benchmark-14c0441f599a108e --bench` (exit status: 1)

The contents of callgrind.bench_fibonacci.short.out:
# callgrind format
version: 1
creator: callgrind-3.22.0
pid: 15487
cmd:  /home/rene/Documents/Java/callgrind/callgrind-test/target/release/deps/my_benchmark-14c0441f599a108e --iai-run bench_fibonacci_group 0 0 my_benchmark::bench_fibonacci_group::bench_fibonacci
part: 1

desc: I1 cache: 32768 B, 64 B, 8-way associative
desc: D1 cache: 32768 B, 64 B, 8-way associative
desc: LL cache: 8388608 B, 64 B, 16-way associative

desc: Timerange: Basic block 0 - 71579
desc: Trigger: Program termination

positions: line
events: Ir Dr Dw I1mr D1mr D1mw ILmr DLmr DLmw
summary: 0

totals: 0

I am unfamiliar with this packages internals but from my understanding callgrind puts a debug symbol in its output which iai looks for. However, if those Debug symbols are stripped then it is not present in the output -> Error.
The Fix
A simple fix for the user is to add profile.bench.strip = "none" which will override the release symbol stripping. However, this fix is not apparent at all from the current iai-callgrind error message.
TL;DR
if this happens, catch it and print out "make sure you addprofile.bench.strip = "none""
I'd be happy to implement and make an MR if this sounds okay.

Thanks for reporting this.
Yeah, this error message should be improved. If you want to start a pr, go ahead. This cargo setting also needs to be documented in the README. Maybe together with debug = true.

I updated the README and the error message. I hope it's clearer now.


export too?

Can you reverse theprocess to export an actor to a statblock, or even a csv?? Id pay $100 for that at the actor level or a compendium of actor entries. Lmk

Do you mean just have it spit out a plain text statblock from the actor? Nothing fancy? And are you talking about NPC/monster statblocks, or player characters?

I'm not sure exactly what you're looking for. If you can give me more details I'll reopen this, but I'm closing it for now.

Hiya James,The plain WotC monster/NPC statblock format. Something you could tweak and reupload if you wanted (using your tool, of course!)I dont know what the PC format would look like. Not sure anyone would use it unless it merged or was formatted into a character sheet. I just homebrew a ton of monsters to keep my players guessing and find that the FVTT is magical for tweaking stats and dropping spells and abilities together.>

It sounds like you want to export statblocks for monsters that only exist in Foundry? That you don't already have the text statblock for? If that's the case, I think that might infringe on their license and I wouldn't want this module to get banned or anything.

lol. This request was so long ago that I completely forgot about it. Since
existing monster statblocks already exist, there's no need for an export of
them. FVTT has the unique ability to build statblocks and create your own
NPCs. It is those that would be great to export. A disclaimer should be
good since most anything risks violation of WoTC/Hasbro's hold on stuff.
Even the statblock format itself.
On Tue, Oct 11, 2022 at 10:34 PM James Haywood @.***>
wrote:

Hiya James,The plain WotC monster/NPC statblock format. Something you
could tweak and reupload if you wanted (using your tool, of course!)I dont
know what the PC format would look like. Not sure anyone would use it
unless it merged or was formatted into a character sheet. I just homebrew a
ton of monsters to keep my players guessing and find that the FVTT is
magical for tweaking stats and dropping spells and abilities together.>
It sounds like you want to export statblocks for monsters that only exist
in Foundry? That you don't already have the text statblock for? If that's
the case, I think that might infringe on their license and I wouldn't want
this module to get banned or anything.
—
Reply to this email directly, view it on GitHub
https://github.com/jbhaywood/5e-statblock-importer/issues/29#issuecomment-1275537144,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXGPHCLR7UF3NIBZDCH7Z5DWCYWS7ANCNFSM5Z22642A
.
You are receiving this because you authored the thread.Message ID:
@.***>


Update for the Winget command

Seems like the command for Winget has changed slightly

@fskelly : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Linking issue is #13579

#label:"aq-pr-triaged"


Clusterfile API upgrade.

We need to encapsulate access to the *v1.Cluster data.
For example, get  master IPList:
Now we directly access the cluster.spec.master.IPlist
but if we upgrade the cluster struct
we need to update a lot of codes.
So provide a function to get it is more Reasonable.
func (c *v1.Cluster)GetMasterIPList()([]string error){
     return cluster.spec.master.IPList
}

New Clusterfile spec suggestion:

support different hosts using different ssh config.
support different master or nodes flavor
Stripping Application Configuration, like calico network config. Using AppConfig and plugin to handle those configurations.

apiVersion: sealer.aliyun.com/v1alpha2
kind: Cluster
metadata:
  name: my-cluster
spec:
  image: kubernetes:v1.19.9
  provider: BAREMETAL
  ENV: key=value
  ssh:
    # SSH login password, if you use the key to log in, you don’t need to set it
    passwd:
    ## The absolute path of the ssh private key file, for example /root/.ssh/id_rsa
    pk: xxx
    #  The password of the ssh private key file, if there is none, set it to ""
    pkPasswd: xxx
    # ssh login user
    user: root
    hosts:
    - name: master0
       role: master
       ip: <IP_ADDRESS>
       ssh:
          passwd: xxxx # overwrite the spec.ssh.passwd
    - name: node0
       role: node
       ip: <IP_ADDRESS>
---
apiVersion: sealer.aliyun.com/v1alpha1
kind: AppConfig
metadata:
  name: calico-config
spec:
  data: |
    # in use NIC name
    interface: eth0
    # Network plug-in name
    cniName: calico
    podCIDR: <IP_ADDRESS>/10
    svcCIDR: <IP_ADDRESS>/22
    withoutCNI: false


model-editor crash on exit

Every time in OS X, sometimes in Linux.

Must be fixed as of 3d8995d14764021969070477989f5aac9ab01ded. Some GL objects were been deleted from non-dispatch thread.


/pref, /ingest endpoints instantiated on every request and open new Kafka producer each time

This ends up maxing out the number of concurrent Kafka connections under load. @Singleton in JAX-RS should solve it.

I am not sure this was the problem, but this is a good idea anyway, and is done.

I actually faced that issue and bumped up max number of connections on the Kafka brokers to solve it.
Sounds good anyway.

Yeah I also increased the number of connections to resolve it, but I don't like the solution.
I think we need to use the async producer to send messages in batch. That works well locally; haven't tested it on the cluster yet. It revealed another small bug in how TopicProducer is handled that I'm also addressing now.
Will post more when I have some info that it works, but am reopening in the meantime.


Update 7.unwind.md

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ImageNet val 50 classes

Dear Junnan,
I'm from NUS SoC and I want to follow this work. Can you provide synsets.txt for selection of ImageNet val 50 classes (as I saw in another issue)? Or can you provide a snippet to choose them? I'd appreciate that very much.

Hi,
You should be able to find it from webvision dataset: https://data.vision.ee.ethz.ch/cvl/webvision/download.html
just download "Training & Validation Labels (183 MB)"

Thanks.


Keywords Insert Text adds 2 spaces instead of 1

As title says, I don't know why but it adds 2 spaces instead of 1. It is really cool setting and I love it, but I can't use it, because I manually need to delete 1 space...
And, it happens not always, for e.g. in Untitled file it always uses 1 space.
Steps to reproduce:

Create file a.ts
Reload window
Trigger suggest widget and select const
Press Tab and you will see 2 or more spaces instead of 1

What is also weird that it happens for few times and it starts to work normal again, as mentioned it might be harder to repro, but it is possible especially after reloading VS Code window.

I cannot reproduce at all, but in theory TypeScript can cache incomplete lists. Can you try installing from https://github.com/zardoy/typescript-vscode-plugins/actions/runs/5525742725 ?


Focus editor for tab after dragged over for 1500 millis

This PR implements #148664
This PR fulfills the requirements, but I think it could be better.
Perhaps we need a setting to indicate if this feature should be active
and also how long the delay should be before we focus the other editor?

I pushed a small 💄 and think the code is generally OK to ship like this but I do agree:

do we need a setting?
what should be the default timeout to open the editor?

Some pointers:

macOS has an accessibility feature called "Spring loading delay" (System Preferences, Accessibility, Pointer Control) that enables/disables this for the macOS dock and allows to adjust the delay with a slider
our very own activity bar has a hardcoded delay of 800ms to open the view that is dragged over via DelayedDragHandler

My first thought was to align activity bar and tabs to be 800ms, but then I feel maybe users are getting frustrated that the active editor changes so quickly when you drag and drop over tabs?
@mjbvz thoughts on this?

I think 800 is fine. Comparing the two..
800ms
https://user-images.githubusercontent.com/25163139/171225581-446c3fec-5b52-4240-885a-2973fe8e6ced.mp4
1500ms
https://user-images.githubusercontent.com/25163139/171225618-23497d70-57ce-4647-844f-77d9c0a24d74.mp4
It might make sense to consider this a setting that applies to these situations globally at some point so users can tune it. Kind of like the macOS example @bpasero mentioned. Rather than having a specific setting for each one, that is.