Fix for missing destination file in Copy

In the Copy task, do not copy when the source and destination paths are the same (canonicalized) to avoid deleting the destination file when a copy-on-self is happening

An internal repo is hitting a problem with the 1.0.282 logic that added in the off-by-default "delete before copy" logic gated in regular MSBuild Copy by feature flag check if (ChangeWaves.AreFeaturesEnabled(ChangeWaves.Wave17_8). @KirillOsenkov FYI as you had filed an item against this Copy task to align with MSBuild logic, which I assume no one in the internal repo has tried yet. Also @AndyGerlicher @jeffkl FYI

Still an open TODO in the new logic related to true paths and symlinked/junctioned dirs. I don't have a good solution for this yet. An alternative to this change is to revert the destination delete logic back to before the feature flag was added in MSBuild Copy. In the interim getting this change in and a new package spun up will help with migrating the repo I'm focused on.

Just to clarify - if the MSBuild Copy feature flag that deletes files before copying is turned on, any repo that has a copy-on-self like this large repo does will end up deleting the source file and failing. Some sort of fix similar to this - or not activating the feature flag - will be needed to avoid this problem.
The CoW Copy code, though derived from MSBuild's Copy, has the disadvantage that File.Copy will silently ignore copy-onto-self cases, both at the path level and via directory symlinks/junctions. The CoW code hence has a problem in that it has to replicate similar checks without relying on checks in the Win32 subsystem that check for the same file via comparing at the file handle level.

Proceeding to commit and publish new packages to unblock testing.

We have been using 1.0.282 from the day it shipped and we haven't noticed anything wrong. @inthemedium to confirm.
The changes you made today don't look breaking to us. Did you expect us to be impacted in any way?

Yes there is a problem there. Working on a minimal repro of the various cases then will fix a bug and link it here.


Cowboy Logo

New logo for your consideration.

Thanks for the proposal. I don't think the logo matters that much so I rather put a personal touch there, instead of having a basho-look-alike Cowboy. But feel free to use it.

That makes sense @essen, thanks for considering it.
Never seen Basho btw :smiley: thank you.

@dikaio do you mind if I use it for a blog post?

I like it the logo :+1:

@unbalancedparentheses use away Fredirico! Here's a zip file with all the different formats (eps, svg, png) just in case you didn't wan't to use svg.
Thanks @bfrog!

Was trying to not polite the cowboy list, but couldn’t find a direct email for you and you are DND on Slack, so my my Slack post below…
Just to say, I saw your logo PR for Cowboy and absolutely love it!
Would you mind if we use it as a favicon.ico on an (Erlang) project we are doing at the moment that serves content with Cowboy?
Nice work!
Adrian

Dr Adrian Roe
Director

On 4 Mar 2016, at 16:54, Don Dikaio<EMAIL_ADDRESS>wrote:
@unbalancedparentheses https://github.com/unbalancedparentheses use away Fredirico! Here's a zip file https://s3.amazonaws.com/dikaio/cowboy-archive.zip with all the different formats (eps, svg, png) just in case you didn't wan't to use svg.
Thanks @bfrog https://github.com/bfrog!
—
Reply to this email directly or view it on GitHub https://github.com/ninenines/cowboy/pull/954#issuecomment-192355678.

Reopening to give visibility if other people want to use it.

Hey @adrianroe thank you! I did see that come in I failed to log into slack right but yes please use away, will be nice to see how you're able to get that to work with 16x16 :+1:
Thanks @essen

@essen I know you don't generally reach out to people for donations but maybe consider uploading to sticker mule and allowing people to throw on their laptop where proceeds could go back to the cowboy project. Just a thought!

I'm not against it but when I have the choice between writing code and doing this I too often choose to write code. Right now my only priority should be getting Cowboy 2 into shape. Maybe when we get closer to release.

Agreed, looking forward to Cowboy 2 most definitely!

Awesome work @dikaio. I like it. But it should definitely be smaller in the README i think ;)

@philipgiuliani Agreed

Closing for good this time. Cleaning up tickets. Thanks for the suggestion!


CIGIN_V2 data loader

Please provide the data loader code for the MNSolv Dataset. I would like to try out the results reported in your paper. Thanks.

Closing the issue due to lack of response in two weeks.


Connection Resume

Ability to pass in a list of connection specs would be an extra bonus

This has been implemented in the Gnat.ConnectionSupervisor


Add capability to specify a fallback text

The fallback text is used in the response on request sources that don't support rich messages

Thank you


Remove lane-related information in Map class, optimize configs

What changes do you make in this PR?

Please describe why you create this PR

Checklist

[ ] I have merged the latest main branch into current branch.
[ ] I have run bash scripts/format.sh before merging.
Please use "squash and merge" mode.

@lqy0057 I am not satisfied with this PR. Do you think we need to introduce varying lane width / num in each block? Do we have strong capacity to deal with the difference between the lane widths of the first block and next block? If so, then I will add this function, otherwise, just treat this PR provides the randomness on the lane width in map-level.

@Edwardhk This PR does not cover the functionality of applying different lane width/num in different block. We wish that should be done, but unfortunately many modifications should be done. We should further doing this in future PRs/issues!


[AMORO-1996] Fix iceberg format on hdfs not support kerberos

Why are the changes needed?

Close https://github.com/NetEase/amoro/issues/1996.
Brief change log

Wrapping the object returned by IcebergTableUtil.newIcebergFileIo method with ArcticFileIOs.buildAdaptIcebergFileIO.

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (no)

I think the Wrapper operation is better implemented inside the com.netease.arctic.server.utils.IcebergTableUtil.newIcebergFileIo(CatalogMeta) method.

good idea.

Github CI failed for checkstyle reason.
Could you please run mvn validate and fix the checkstyle problem?

Please fix the code checkstyle problems. and test mvn validate before push.

done.


Package depends on vulnerable versions of underscore

Hi,
I got message with npm audit that:
@silvermine/videojs-quality-selector *
Depends on vulnerable versions of underscore
node_modules/@silvermine/videojs-quality-selector
Can you bump up dependency underscore to to 1.12.1 or higher, which is unaffected by the vulnerability .
Thank you in advance.

See #73

Fixed in +<EMAIL_ADDRESS>


[release] Initiate 7.7 branch

This commit initiates the 7.7 branch which will be dedicated to the 7.7.x releases for the Helm Charts. It will allow to:

test this branch with the daily Stack Docker images 7.7.0-SNAPSHOT via dedicated Jenkins jobs
test the staging 7.7.x Docker images before a release

The files related to the 6.x versions are removed from this branch.
The CHANGELOG file is also removed, the intent is to have a unique file for dealing with the changelogs on master.
The doc still needs to be updated to introduce this new workflow.

jenkins test this please


Question: how to dispose textures cleanly on unmount

Howdy - I'm one of the authors of regl-worldview.  First of all, thanks for regl...it's great!
I have a question...in our app we have a "map" similar to google maps consisting of a grid of tiles, each w/ an image as a texture.  When the user pans the scene we call texture.destroy() on any of the tiles which are too far from the viewport, within the individual tile's componentWillUnmount callback.  This works great...until the entire <Worldview /> component unmounts.  At that point we call regl.destroy() within the <Worldview />'s componentWillUnmount callback....immediately after this react calls the tiles unmount and we call texture.destroy() on each of the textures from within each tile...but since regl has already cleaned up itself & everything it's managing (including the textures) we get a console.error saying "must not double-destroy texture".  In some apps, we unmount and remount <Worldview /> somewhat regularly based on where the user is at in the app.  This causes a lot of console.error spamming and floods our monitoring tools w/ error messages.
I put a try/catch around the call to texture.destroy() in an effort to suppress this error but regl has console.error hard-coded into the check function's path.
Would you be interested in a PR to remove the hard-coded console.error and just rely on the throw statement immediately below it?
If not...we were thinking of wrapping the call to regl.destroy() in a requestAnimationFrame within the componentWillUnmount of <Worldview /> which would give children (and grandchildren, etc) time to do any cleanup while they unmount before we destroy regl itself.  I'm a bit concerned about doing that though because if we call regl.destroy() in an animation frame callback after <Worldview /> unmounts the canvas element will already be unmounted by react & I don't want to get into a weird state of leaking GPU memory or something by regl not being able to fully dispose the canvas context since the canvas is already removed by the browser.  Is it safe to call regl.destroy in an animation frame after the canvas element has been unmounted by react?

Thanks for the detailed description! That seems like a completely valid issue, but just for the sake of argument, is there a reasonable way that you might be able to track destruction of regl on the application side? If you could set regl._destroyed = true, might you be able to check if regl is destroyed when calling texture.destroy() (presuming access to the regl instance where the texture is destroyed, of course)?
My second thought is way grosser… no further comment necessary here, I think :)
function doItQuietly (action) {
  var tmp = window.console.error;
  window.console.error = function () {}
  action();
  window.console.error = tmp;
}
doItQuietly(texture.destroy);

Beyond that, it does seem reasonable to me to rely on throwing rather than forcing things into the console and throwing. My only hesitation is that it's a pretty central error handler so that it might have an effect on things like the readability of glsl errors or something. Without exhaustive investigation it does seem reasonable to consider, though it's at the very least easiest if there's a workaround.

I understand - I'm hesitant to change regl as well.  So, just wanted to open up w/ a question.  I was also thinking of possibly switching on a flag in our react context to say regl has been torn down.  It's a bit more work but it's the cleanest approach.  Haha your "gross" approach was the quick fix we already implemented. 😋
One other option would be to put a flag onto the regl.texture instance itself like texture.destroyed or texture.isDestroyed or set the texture.destroy() function to a noop when regl calls destroyTextures().  I looked at just checking if (texture._texture) { texture.destroy() } but don't like relying on "private" internals of libraries as it's not stable.
I think I'll look at addin a flag to our context for now & thread it down into the map tiles and check it there.  Thanks for your thoughts!
Please feel free to close this as we can work around it in our app, but wanted to share w/ you to bring it to your attention and see if we were missing anything.  Thanks again. 😄

Just my two cents, you could also simply mock the error method temporarily ;)

yeah that's what I ended up doing. Just monkey-patched over it during dispose.


Typo in tor.install.sh

Line 186:
sudo chmod -v 755 "${tor_conf_dir}""${tor_conf_dir}"/torrc.d
should be
sudo chmod -v 755 "${tor_conf_dir}" "${tor_conf_dir}"/torrc.d
(added space between variables)
I think this is a typo but I'm not sure.

@adevoss thanks for giving this a review. 👀 @nyxnor

comitted fix to dev branch

tests looking good thru the RC2 testing. Closing for v1.7.2 release.


Fix godot_js_wrapper_create_cb regression

Fix a regression caused by #81105.
Currently, calling GodotJSWrapper.MyProxy(args) without the new keyword returns undefined, which make the following calls fail.
This PR adds the missing new keyword to the expression.
Fixes #82734

Thank you for your dedication to fix my mistake 😭

Thanks!

Cherry-picked for 4.1.3.


Explicit type declarations is not handled!

Since PHP 7.4 type declarations were introduced.
But php-avro-schema-generator does not look in it.
Steps to reproduce:
// in ../DAO/DemoNotification.php
class DemoNotification {
    private string $content;

    public function __construct(string $content) {
        $this->content = $content;
    }

    public function getContent(): string {
        return $this->content;
    }
}

$data = new DemoNotification("Hello");
$registry = (new ClassRegistry())
    ->addClassDirectory(__DIR__ . '/../DAO')
    ->load();
$generator = new SchemaGenerator($registry, '');
$schemas = $generator->generate();
echo(current($schemas)); // Out: {"type":"record","name":"DemoNotification","namespace":"App.DAO","fields":[{"name":"content","type":""}]}

Actual behavior
Despite explicit type declaration:
private string $content;

Script outputs:
{"type":"record","name":"DemoNotification","namespace":"App.DAO","fields":[{"name":"content","type":""}]}

Expected behavior
{"type":"record","name":"DemoNotification","namespace":"App.DAO","fields":[{"name":"content","type":"string"}]}

Heya, thanks for the report. Absolutely correct, i'll look into it :v:

@nick-zh, please review pull-request addressing that issue https://github.com/php-kafka/php-avro-schema-generator/pull/25

Many thanks, i left some comments and also opened #26 for the next major, since i never liked that class to begin with :smile:

Thank you very much! Could you please release a new version to do not hack that in my application?

Sure thing, i am on it, i need to fix the stan error, so i already merged your changes :v:


Referenced token value is a CSS variable instead of a HEX color

Bug report
Describe the bug
Not sure if it is a bug or a feature request, but when you have some colors token and you create another one from it, e.g. as an alias, it's value is not a hex color but a css variable.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
codesandbox: https://codesandbox.io/s/stitches-react-chueg?file=/src/stitches.config.ts

Go to stitches.config.ts
Check colors.greenMain and colors.success -> success is an alias from colors.greenMain
Scroll down to bottom of the file, there is a console.log with the values from theme.colors[token].value
See there is a  value #33d718 for greenMain, but var(--colors-greenMain) for success

Expected behavior
I would expect that colors.success is also a hex color, because otherwise it's not possible to make other computations for example adding transparency or mixing with other colors, like using tint or shade functions from polished library
Screenshots

System information

OS: macOS Monterey 12.2
Browser (if applies) Brave 1.34.81
Version of Stitches: 1.2.6

This is precisely what I was looking for!
Here's what I ended up with
  // Component/styles.ts

  export const expContainer = css({
    [`.${themes.light} &`]: {
      bg: opacify(0.35, themes.light.colors.sectionExpCardBg.value),  // not intended
    },

    [`.${themes.blackAndWhite} &`]: {
      bg: opacify(0.35, theme.colors.whiteA11.value),  // not intended
    },

    [`.${themes.dark} &`]: {
      bg: opacify(0.2, theme.colors.blackA11.value),
    },
  }

Ideally I was looking for something like
// Component/index.tsx
import { opacify } from 'polished'

import useSelectedTheme from 'src/hooks/useSelectedTheme'
import { themes } from 'src/shared/theme'
import * as stl from './styles'

export default React.forwardRef<HTMLDivElement, Props>(
  ({ data, prevBtn, nextBtn, ...props }: Props, ref) => {
    const [selectedTheme] = useSelectedTheme()
    const bg = opacify(0.35, themes[selectedTheme].colors.sectionExpCardBg.value)  // here the value should be an rgba color
    // ...

          <div
            className={stl.expContainer({
              css: { $$bg: bg },
            })}
          >

and then
// Component/styles.ts

export const expContainer = css({
  bg: '$$bg',
}

Is there a way to get the final color? 🤔

I find const assertion to be the cleanest solution for the time being.
import { createStitches } from "@stitches/react";

const colors = {
  aquamarine: "#7ee7c6",
  black: "#000000",
  gainsboro: "#dfdfdf",
  mint: "#80e6c8",
  pink: "#ff70c2",
  platinum: "#ebebeb",
  purple: "#a47be8",
  red: "#ff705c",
  white: "#ffffff",
} as const;

export const { config, css, getCssText, globalCss, styled, theme } =
  createStitches({
    theme: {
      colors: {
        ...colors,

        background: colors.white,
        error: colors.red,
        text: colors.black,
      },
    },
  });

console.log(theme.colors.error.value); // #ff705c


Use clulab artifactory & jenkins

Cleaner. Thanks!

This is a test to see whether Jenkins (jenkins.clulab.org) picks this up and can test.  It already deployed fine to artifactory.clulab.org.


hostap: add SAE_PWE_EARLY_EXIT Kconfig

In order to mitigate side channel attacks, even if the PWE is found the WPA
supplicant goes through full iterations, but in some low-resource systems
this can be intensive, so, add an option to exit early.
Note that this is highly insecure and shouldn't be used in production

@gangli02 The PR #76918 will have a manifest update that includes your hostap changes from https://github.com/zephyrproject-rtos/hostap/pull/25. This means that you can remove the manifest changes from this PR. Could you update the PR and re-submit.


Wiki: add link from ng serve page to proxy-config page

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ x ] documentation change (github wiki)

Since I can't do a pull request regarding the wiki...
This page https://github.com/angular/angular-cli/wiki/serve should include information about the option --proxy-config documented here: https://github.com/angular/angular-cli/blob/master/docs/documentation/stories/proxy.md

We actually have all the wiki pages in the repo proper!
https://github.com/angular/angular-cli/blob/master/docs/documentation/serve.md
Would you be available to make a PR there?

done!  https://github.com/angular/angular-cli/compare/master...culli:patch-1

Closed via https://github.com/angular/angular-cli/pull/7390

Thanks for fixing this 👍


Cannot create a default language when starting with new database

Issue summary
I cannot save a language as a default language in wagtail cms when I don't already have a language saved.
How to reproduce?
Create new database and try to save a new language as default.

Fixed in #14


Add parameters to ColumnLayout SCSS mixing

Make it possible to define spacing of columnlayout with mixin parameters

Added to 0.1.5


Why DigestListAck messages, but no IdleTimeoutNotificationAck message?

There is likely an obvious answer to this question that will occur to me shortly after submitting this issue, but I will ask it anyway.

I don't think there is an obvious answer. It pretty much comes from how I conceptualize these 2 functionalities.

In the case of idle timeout, losing a notification is not a big deal. Another one will be generated when the entry expires "again" (i.e. after another timeout interval). The action that the client is likely to take is remove the entry, which essentially stops the idle timeout notifications for that entry.
The case of digest is more subtle in my option. We need to worry about not flooding the client with many duplicate notifications, which we do by mandating a cache (either in hardware or software) on the target. This cache needs to be cleared, and even though we have an ack timeout mechanism, I believe an active notification from the client is best to indicate "I have processed the digest message, clear the cache now". The ack timeout provision is just in case the ack from the client is lost. The action from the client is generally less straightforward in the digest case. One can assume that the action will be to populate a table in such a way that the P4 datapath will stop generating similar digests. If we make that assumption, then we could just get away with the ack timeout to clear the cache. But I like the active ack better.

Thanks for the detailed answer.  I didn't have any strong suspicion that there was anything wrong here -- just a minor wondering whether there was something missing here, but I still don't see anything wrong with the current design.  Closing this issue.


Prevent stats update if the deltas are empty

An attempt at addressing #617 . This does not increase update frequency, but prevents the deltas from being 0 till stats are available.
(Have verified via logging that the updated stats have change in values. But, still seeing zeros in list-nodes. Actually, I have never seen non-zeros there, my redis based set up for local dev is missing something)

An attempt at addressing #617 . This does not increase update frequency, but prevents the deltas from being 0 till stats are available.
(Have verified via logging that the updated stats have change in values. But, still seeing zeros in list-nodes. Actually, I have never seen non-zeros there, my redis based set up for local dev is missing something)

try running the command with:
livekit-server --config config.yaml list-nodes

That's what I was missing. Thank you @davidzhao . It works now. It updates every 10 seconds and  in between pulls show the previous numbers.


Provide more control over server writing and make UDP support extendable

This replaces the much more complicated interface proposed in #918 (see https://github.com/miekg/dns/pull/918#issuecomment-470321738) with a different approach that should allow all the same control over the server.
Note: This is still lacking tests and so isn't ready to merge yet.
Closes #918
/cc @jrajahalme

I don't like it, the old way looks way more saner and we're catering/changing this code for a very specific use-case.
We also have the incredible awfully named Decorators in here as well.

A proper(er?) way to sidestep this all is, I think, to copy the http.RoundTripper interface and add a default one in the lib

@miekg Could you elaborate on that idea?

oh fuck, this is server side, I was thinking client. Maybe something like http.Transport makes sense for a server as well?

@miekg In the meanwhile I've tried to cope with the existing level of UDP support by limiting the Cilium policy language to only allow proxying for UDP on port 53 (see https://github.com/cilium/cilium/pull/7566). This should be no big deal as everyone is using DNS on it's standard port. For this to work with TPROXY without any DNS proxy changes the DNS proxy has to bind to port 53, but this interferes with any DNS server running on the same host, so coping with this would be too much of a restriction on the Cilium deployment.
The reason why the proxy has to bind to port 53 is that the UDP response is sent using the the listener socket, so the source port on the responses is going to be the same as the bound port for receiving. While TPROXY would allow the proxy receiving packets sent on port 53 to any arbitrary port (say, 5353), the responses will have the source port of the actual socket (here 5353).
The reason we want to move to TPROXY is that it allows the Cilium datapath to be significantly simplified and that there is some inherent raciness in iptables REDIRECT method (see https://www.kernel.org/doc/Documentation/networking/tproxy.txt). For TCP TPROXY is very easy and requires no changes in the proxy. Unfortunately, due to UDP being connectionless, some new oob/control data has to be dealt with in both reception and sending.
The approach I proposed in #918 may not be perfect, but it is an straightforward extension of the structures you already have for UDP transport; the only real change is the use of Go interfaces instead of structs to allow for extension on the library user side. I've run this code in testing for more than a month now, and have been happy with the results.
Would it be too much to ask to have another look at #918, now that we know the alternatives are not particularly beautiful either? When I researched this I found other people have asked for something similar in the past, so hopefully Cilium is not the only project that would benefit from this.
In the first round of review, dealing with the buffer pooling was an eyesore, and I'd be more than happy to amend it to any direction you may wish.

@tmthrgd @miekg FYI, I posted just posted #955, a cleaned up and rebased version of the UDP extensibiilty PR. Moving the pooling away from server.go made it quite a bit cleaner. I also renamed and restructured the interfaces/methods in udp.go according to the feedback you provided on the original PR. I hope you'll take a fresh look, and maybe start by checking out the diffs on server.go, as I was quite happy how it turned out :-)

I’m going to close this PR for now and propose changing the Writer interface to be this PRs ConnWriter whenever a plan emerges for a v2 of this library. Otherwise, I don’t see this being merged at present.

[ Quoting<EMAIL_ADDRESS>in "Re: [miekg/dns] Provide more contro..." ]

Closed #949.

So I don't think I want to see this extensible.
I addedd a thing for a company at some point in time: 'Server.Unsafe', because
they (and only they) needed it. It stayed in the lib for 4 years, after which I
reached out if they still needed that. 1) They didn't know it was there 2) they
hadn't used it for years - if ever. No one else needed or wanted this.
I'm not going to repeat that mistake. This falls squarly in the same boat. This
PR is small enough to be applied in your private fork for the time being.
This is a generic DNS library. Iff someone else has the same problem in the next
few years we can discuss this again, for now I don't see what we need add code
to make this possible.
/Miek
--
Miek Gieben


Support for topics wildcards

Hi, since multiple topics are supported, it would be useful to support wildcards in "topics" as well.

Perhaps it's already supported? https://issues.apache.org/jira/browse/KAFKA-3073

@nazr you should be able to specify a regexp for the topics property in the sink configuration. this then causes connect to subscribe to all of them. what's important to keep in mind is that if you happen to need e.g. individually different settings on topic level you should configure the topic specific overrides accordingly. another option would be e.g. to use the empty string for mongodb.collection= which would then fallback to the original kafka topic name to be used as the mongodb collection name. let me know if it works for you as expected.

thanks for the reply! Our requirement is to sink all the topic that match a wildcard definition to a single collection. It sounds like the collection name will be different though, so it won't work?
The list of topics is not known (hence wildcards), so can't configure it on per topic basis.

you can configure the connector so that it reads multiple kafka topics and sinks them into the same mongodb collection. in fact this behaviour was there from the very beginning where it wasn't possible to specify topic/collection specific configuration options. just try to put your regexp for the topics property and then set the mongodb.collection property to a name of your choice for the sink collection which should receive all records regardless of which topic it originates from. beware that this is typically not recommended in case the structure of the documents is vastly different :)

Thanks! it does work with latest version of everything. It's worth noting that it'll only pick up existing topics at the time the connector is created. Any new topics, even if they match the wildcard definition wouldn't be processed.

Glad to hear it works for you as expected. Your observation - namely that the connector only picks up topics that exist at creation time - is the current behaviour of the kafka connect itself. The topic subscription happens at framework level. Thus it has nothing to do with my sink connector implementation. I you think connect should periodically check for new matching topics to subscribe to after creation of the connector you may file a feature request for kafka connect anytime.
I suggest to close this issue now. THX again for reaching out!


Documentaton Is Extremely Murky and Unhelpful

PHP-Whois version:
4.1.10
PHP version:
8.2.6
Problem:
Documentation Is Extremely Murky and Unhelpful
Problem Description:
The Documentation is  extremely murky and extremely unhelpful to those with little to no knowledge / experience with respect to writing code,  or using an API.  This often results in choosing to use another solution which is straight forward in the documentation and includes step by step examples to cover both correct installation and correct usage.
How to reproduce the problem:
Not Applicable. The problem is self-explanatory.
Possible Solution to the problem:
The developer should rewrite the documentation to supply step by step examples suitable for those
with little to no coding experience. Developers need to remember that not everyone has the same level of experience with respect to coding, and open source projects need to be usable by everyone regardless of their experience.
Additional context of the problem
The context of this problem involves those persons whom are newer to programming in general and/or newer to the
PHP language.  Developers should Always Remember that not everyone is as experienced as them, and should keep that
fact in mind when writing open source code and documentation, as to make their projects easily usable where the rubber
meets the road.

Please submit the correct documentation in your opinion for public review.


Document Transmit.source

@thomaseizinger do you agree with this documentation?

@thomaseizinger Thanks! You're totally right making this more about from the user's perspective.
I've incorporated your suggestions into mine, but sticking with source for now.

Reads great, a big improvement! :)


Automated cherry pick of #1979: fix server purge

Cherry pick of #1979 on release/2.10.0.
#1979: fix server purge

/lgtm
/approve


Moving the finished note to something other than _posts

Is your feature request related to a problem? Please describe.
My personal website doesn't just have posts, but also projects, news, pages etc. This means I need to move the generated markdown file to the right folder
Describe the solution you'd like
Ideally, my "ready" folder would have subfolders "_post" or "_projects", matching those of my jekyll website. The notes put in those folders would be moved to the corresponding folder (if it exists) in the jekyll project.
A less flexible option would be to make the output folder a plugin option.

I really liked the idea. I was looking at the project's issues and came across this feature request. I also need something like this and would be willing to implement it, of course, with the proper authorization from the repository maintainers. @songkg7 I would be happy to implement this. 😁


Error when "XDG_DATA_DIRS" env variable is not defined

When "XDG_DATA_DIRS" env variable isn't defined the app crashes with this,
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string: construction from null is not valid
zsh: IOT instruction (core dumped)  npm run demo

I am using Manjaro linux with KDE desktop environment and have no idea what it does or why its not defined. You can try unsetting the variable to reproduce this issue. I think some error checking should be added with helpful err msg if the env variable is really required for the package.
https://github.com/paymoapp/node-active-window/blob/8a3b065a0f9e97222c6cd77746e64c18de0a9083/module/linux/src/ActiveWindow.cpp#L60
https://github.com/paymoapp/node-active-window/blob/8a3b065a0f9e97222c6cd77746e64c18de0a9083/module/linux/src/ActiveWindow.cpp#L418
I cant code C++ 😅😅, so leaving this issue

Hello!
Thanks for reporting the issue!
The variable itself is not really required. It is used to fetch high resolution png icons for the applications.
The process is the following:

get the desktop entries
find the icon paths for each application entry

As a fallback we use the _NET_WM_ICON xprop, which is suitable in most of the cases, but it's not high res.
I've assumed that XDG_DATA_DIRS is set on every desktop env (it's the directory where the desktop entries and the icons should be stored), but it seems like it's not. :)
I will add a check that the env var is set, if not, it will fall back to _NET_WM_ICON.

Fixed in 42d165567ec84304ac495e7c798d52085dad2a53
A build is on it's way!


Implement Profile Components.

Long story short

This will change the behavior of fetch_profile method which used to take no components and return a Profile class only
which limits the user to pass multiple components and return them at once. Which why this PR will fix this problem by returning a components.Component object includes the *components the user passes to the request.
Checks

[x] I have run nox tests and all pipelines have passed.
[ ] I have wriiten tests according to the code i added, modified or deleted.

Related issues
#48

Instead of naming the component attribs get_xxx it should only be xxx, i.e., get_profile -> profile


Support TexInfo

Example file:

https://github.com/ruby-debug/ruby-debug-ide/blob/master/doc/protocol-spec.texi
https://github.com/rmloveland/scsh-manual-texinfo/blob/master/scsh.texi

Official website for GNU Texinfo: https://www.gnu.org/software/texinfo/

Thanks for freand sheep
On Tue, Apr 2, 2019 at 9:58 AM Franklin Yu<EMAIL_ADDRESS>wrote:

Example file:
https://github.com/ruby-debug/ruby-debug-ide/blob/master/doc/protocol-spec.texi
Official website for GNU Texinfo: https://www.gnu.org/software/texinfo/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/linguist/issues/4479, or mute the thread
https://github.com/notifications/unsubscribe-auth/AuyF4oPpOqrXW8H8QF0uyypgYsPL4xodks5vcuqOgaJpZM4cXLCW
.

We can register it as a language on GitHub, but there won't be syntax highlighting as every TexInfo grammar out there is GPL-licensed 👎 (I've searched before).
I've been tempted to write one in the past, but I'm not familiar with the format, sadly.

Hello
Thanks to all the friends
I'm not familiar with this language too.
With the information I got, I think Instagram uses this language
Thank you
On Tue, Apr 2, 2019 at 11:55 AM John Gardner<EMAIL_ADDRESS>wrote:

We can register it as a language on GitHub, but there won't be syntax
highlighting as every TexInfo grammar out there is GPL-licensed 👎 (I've
searched before).
I've been tempted to write one in the past, but I'm not familiar with the
format, sadly.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/github/linguist/issues/4479#issuecomment-478877000,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AuyF4odDZslIt8LOUARJyZl5mz4R2aufks5vcwXUgaJpZM4cXLCW
.

Another example: https://github.com/westes/flex/blob/master/doc/flex.texi

I've written an original (non-copylefted) grammar that will fix this. See #4589.


Add the ability to see the current platinum price of a reward

Don't know if this works with other languages as well though, would be nice if someone could test that. Also some items don't work because warframe.market has a few typos in their item names :).

Merged with #9. I ended up doing a bunch of refactoring on it, and fixing some bugs with some of the items (Kavasa items, Paris Prime items, Lex Prime Reciever).

See release v0.8


Fix race for out-of-order webhooks.

It is possible that the opened action may not be the first webhook actually
received for a PR. If this should occur, users would see the CLA check for a PR
appear to hang until a new commit is pushed to the PR.
This change breaks the filtering and handling of a request into two
separately-exported functions, accepts and handle. Only acceptable
requests will be enqueued for debouncing. As a convenience to operators, the
no-op case will result in a 204 response code. I have confirmed that GitHub
treats a 204 as a successful response code in a private instance of CLA
checker.
Fixes #545

 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.


Improve double spend error strings.

The mempool's MaybeAcceptTransaction methods have also been modified
to return a slice of transaction hashes referenced by the transaction
inputs which are unknown (totally spent or never seen).  While this is
currently used to include the first hash in a ProcessTransaction error
message if inserting orphans is not allowed, it may also be used in
the future to request orphan transactions from peers.

Bumped the maximum allowed rune length of logged reject messages to 250, as the longer error strings introduced by this PR exceed the previous max of 200.

This also appears to change the orphan handling without mentioning it in the commit message.

As discussed on IRC, please split the behavior change to another pull request  The error string changes are uncontroversial and can go in quickly, but we'll need to test the orphan changes thoroughly and examine all the implications of the behavior change.

Orphan eviction behavior should be exactly the same as on master now, but I added plenty of comments explaining why I think master is iffy and how I think it should be done.  Will submit another PR with those changes for review separately.

OK.  We'll want to address the comments regarding orphan behavior separately.


Added more tips to for iOS

Hi @undernewmanagement, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Support inline role definition in AuthorizationPolicy

Support inline role definition in AuthorizationPolicy.
Add a check in applying time to make sure at least one of roleRef or actions exists in an AuthorizationPolicy.
Add unit tests for ValidateAuthorizationPolicy()
Replace an existing ServiceRole in a RBAC v2 unit test with inline role def.
For #12394

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: pitlv2109
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pitlv2109: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
8281cbb586f204f0db795de19f60ac4193fb24cf
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
8281cbb586f204f0db795de19f60ac4193fb24cf
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
8281cbb586f204f0db795de19f60ac4193fb24cf
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
8281cbb586f204f0db795de19f60ac4193fb24cf
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
8281cbb586f204f0db795de19f60ac4193fb24cf
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
8281cbb586f204f0db795de19f60ac4193fb24cf
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Will add e2e tests for inline role def once #12814 is merged.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
8281cbb586f204f0db795de19f60ac4193fb24cf
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
cd8499651c7d0fdc61b99d3c8473d81e25a57981
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: pitlv2109, yangminzhu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: diemtvu, pitlv2109, yangminzhu
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [diemtvu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

prow/e2e-dashboard.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

prow/e2e-dashboard.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

prow/e2e-dashboard.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-k8s-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-k8s-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-k8s-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-k8s-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-dashboard.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-k8s-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-mixer-no_auth.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test e2e-mixer-no_auth

prow/e2e_pilotv2_auth_sds.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

/retest

@utka prow tests are still not running when using /retest :(. Is a fix coming? I will start individual tests  for this PR.

/test e2e-dashboard
/test istio-pilot-e2e-envoyv2-v1alpha3
/test e2e-bookInfoTests-envoyv2-v1alpha3
/test e2e-mixer-no_auth
/test istio_auth_sds_e2e

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-unit-tests

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

@pitlv2109: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
cb0053537588940186692eb49afdb22eb3a95b56
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[AutoPR cognitiveservices/resource-manager] Add Python CS ARM conf

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2766

(message created by the CI based on PR content)

Codecov Report

Merging #2297 into restapi_auto_cognitiveservices/resource-manager will not change coverage.
The diff coverage is n/a.

@@                               Coverage Diff                                @@
##           restapi_auto_cognitiveservices/resource-manager    #2297   +/-   ##
================================================================================
  Coverage                                            52.76%   52.76%
================================================================================
  Files                                                 5627     5627
  Lines                                               133882   133882
================================================================================
  Hits                                                 70637    70637
  Misses                                               63245    63245

Continue to review full report at Codecov.

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

Will regenerate from service PR


fix: edge cases in vercel serverless function

Fixes: https://github.com/dai-shi/waku/issues/253

I think we need a better logic of fallback. I will fix this in another way


cols

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>

@nirshemesh , please elaborate the issue.

Hi Intel,
My goal is to have accurate point cloud from up to meter of a small object (333[cm])
While working with the most updated FW and SDK (for D415). I found the following disturbing issue although the camera is calibrated according to the user guide:

Using point cloud example in Matlab - the point cloud is very noisy and not accurate experiencing "breathing" effect over time.
The depth is also noisy - so I used temporal averaging per depth per pixel and I achieved "stability" but while doing so on the point cloud map - I found it still noisy.
can you suggest on a filter solution + example from point_cloud.m file how to apply it so it will be accurate ? Or other solution to overcome this need ?

Thanks
Nir

https://dev.intelrealsense.com/docs/tuning-depth-cameras-for-best-performance

Done that already,
Looks like the dynamic calibration tools doesnt progress (% value stays on 0).
I tried both Letter page and Mobile phone as a target pattern - with no success (I checked the dimensions as requested).
I follow the instruction on the link above and still - breathing pointcloud achieved (Matlab example).
I"m using D415 with the most updated SW & FW.
Last - I dont have a specific Matlab example for pointcloud that contain temporal filter in it - maybe that should help ?
Distance to the wall (80[cm]) and the target around 60[cm].
Will be glade to have your solution
Thanks
-Nir

@nirshemesh Sorry for late response. Would like to know if you still have issue. For dynamic calibration, what OS did you try the tool? Ubuntu or Windows?

Yes, I still have the issue. I"m using Windows 10. in addition all the calibration guides I"ve used doesnt solve the problem of "breathing" point cloud - its not stable at all. your help is appreciated.
Nir

@Nir Could you please provide some snapshots of the point cloud you see the issue?  And what's your SDK and FW version now? Thanks!

@Nir Could you provide more details about the issue so that we can continue to look into it? Thanks!

The FW version is <IP_ADDRESS> (D415) SDK version is 2.0. (Windows 10).
The average temporal error of the point cloud of a flat wall located around 80 [cm] from the camera is around 8[mm]. I want to understand if this is the accuracy I should expect from this model ?
My need to have accuracy of around 1mm...
As i said the pointcloud is "breathing" overtime (temporal),
Thanks
Nir

@nirshemesh According to section 4.7 in the datasheet https://www.intelrealsense.com/wp-content/uploads/2019/10/Intel-RealSense-D400-Series-Datasheet-Oct-2019.pdf , the temporal noise is ≤ 1% for D400 cameras(up to 2 Meters and 80% FOV). You can refer to https://dev.intelrealsense.com/docs/depth-post-processing and try post-processing to see if it helps. Thanks!

@nirshemesh Any other questions about this ticket? Looking forward to your update. Thanks!

@nirshemesh  Could you please update? Thanks!

@nirshemesh Sorry that we didn't get your feedback for several weeks. Will close the ticket at this point. Please create another one if you still have issues or questions. Thanks!


Command line handling does not produce error

We have decided a while back that we will not report unknown command line options for applications which use hpx_main.hpp (i.e. which emulate main()). The rationale was that those applications may want to do their own command line handling and reporting unknown options would be undesireable.
Now, as it turns out this has a downside. As described in a question on stackoverflow (http://stackoverflow.com/questions/35367816/hpx-minimal-two-node-example-set-up) a user was not able to make an HPX application work because of a typo in one of the command line options. The user wrote --hpx.hpx instead of --hpx:hpx. The application was hello_world which relies on emulating main().
If HPX was reporting this as an error the user would have had a lot less problems in the first place.
It is unclear at this point how this could be resolved. Some heuristic might help.

Would it be feasible to parse the options and print out a warning that "the following options were not recognized by hpx" - if the user sees on with hpx.blah in it, they'll probably realize something went wrong.
adding the option hpx:no-option-warn, would suppress it (or something similar)

@biddisco I think I found a reasonable solution - see #1998.


Spinner not showing

I'm trying to implement your component but I'm not getting the spinner to show during progress. The disabling of the button works fine. Any ideas on what I;m missing or what I should look for?

Did you include some css for the spinners? It's not included per default.

Yeah, i added this:
.btn-spinner:not(:required) {
margin-left: -22px;
opacity: 0;
transition: 0.4s margin ease-out, 0.2s opacity ease-out; }
.is-loading .btn-spinner {
transition: 0.2s margin ease-in, 0.4s opacity ease-in;
margin-left: 5px;
opacity: 1; }
.btn {
text-align: left; }

Try including all of this: https://github.com/johannesjo/angular-promise-buttons/blob/master/src/styles/_default-button.scss
Seems to be an styling issue to me.

Got it sorted, thanks; It was a styling issue.


vsphere: Can we remove the completed 7/12 VMware testing environment?

Follow-up ticket from https://github.com/crosscloudci/cross-cloud/issues/161#issuecomment-405323205:
The AWS LBs for the orphaned environments were created on 7/12, four days ago.
The following environments are still online and were not destroyed properly:

pd21943
pd21944

@akutz,
Yes, greenlight on vmware destroying these environments

Hi @lixuna,
Grazzie!
pd21943
$ docker run \
>   --rm \
>   --dns <IP_ADDRESS> --dns <IP_ADDRESS> \
>   -v $(pwd)/data:/cncf/data \
>   -e VSPHERE_SERVER=$VSPHERE_SERVER \
>   -e VSPHERE_USER=$VSPHERE_USER \
>   -e VSPHERE_PASSWORD=$VSPHERE_PASSWORD \
>   -e VSPHERE_AWS_ACCESS_KEY_ID=$VSPHERE_AWS_ACCESS_KEY_ID \
>   -e VSPHERE_AWS_SECRET_ACCESS_KEY=$VSPHERE_AWS_SECRET_ACCESS_KEY \
>   -e VSPHERE_AWS_REGION=$VSPHERE_AWS_REGION \
>   -e CLOUD=vsphere \
>   -e BACKEND=file \
>   -e NAME=pd21943 \
>   -e COMMAND=destroy \
>   -e VSPHERE_DESTROY_FORCE=true \
>   -ti provisioning
# deleting DNS entries for master node(s)
  - pd21943-master-1.pd21943.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-1","modifiedIndex":25468,"createdIndex":24393},"prevNode":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-1","value":"{\"host\":\"<IP_ADDRESS>\"}","modifiedIndex":24393,"createdIndex":24393}}
  - pd21943-master-2.pd21943.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-2","modifiedIndex":25469,"createdIndex":24394},"prevNode":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-2","value":"{\"host\":\"<IP_ADDRESS>\"}","modifiedIndex":24394,"createdIndex":24394}}
  - pd21943-master-3.pd21943.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-3","modifiedIndex":25470,"createdIndex":24392},"prevNode":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-3","value":"{\"host\":\"<IP_ADDRESS>\"}","modifiedIndex":24392,"createdIndex":24392}}

# deleting DNS entries for worker node(s)
  - pd21943-master-1.pd21943.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21943/pd21943-worker-1","modifiedIndex":25471,"createdIndex":24391},"prevNode":{"key":"/skydns/local/vsphere/pd21943/pd21943-worker-1","value":"{\"host\":\"<IP_ADDRESS>\"}","modifiedIndex":24391,"createdIndex":24391}}

# deleting AWS load balancer(s)
  - arn:aws:elasticloadbalancing:us-west-2:571501312763:loadbalancer/net/xapi-20180712204306658100000002/748b108df78b7054

# waiting for deletion of AWS load balancer(s)

# deleting AWS load balancer target group(s)
  - arn:aws:elasticloadbalancing:us-west-2:571501312763:targetgroup/xapi-20180712204304878800000001/249022a72adda676

# deleting AWS elastic IP address(es)
  - eipalloc-04448dfd1687e73ca ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...

# deleting vSphere VM(s)
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943/pd21943-master-1
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943/pd21943-master-2
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943/pd21943-master-3
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943/pd21943-worker-1

# deleting vSphere folder(s)
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943

# deleting vSphere resource pool(s)
  - /SDDC-Datacenter/host/Cluster-1/Resources/Compute-ResourcePool/CNCF Cross-Cloud/pd21943

# deleting Terraform state

real	2m39.319s
user	0m16.580s
sys	0m2.190s

pd21944
$ docker run \
>   --rm \
>   --dns <IP_ADDRESS> --dns <IP_ADDRESS> \
>   -v $(pwd)/data:/cncf/data \
>   -e VSPHERE_SERVER=$VSPHERE_SERVER \
>   -e VSPHERE_USER=$VSPHERE_USER \
>   -e VSPHERE_PASSWORD=$VSPHERE_PASSWORD \
>   -e VSPHERE_AWS_ACCESS_KEY_ID=$VSPHERE_AWS_ACCESS_KEY_ID \
>   -e VSPHERE_AWS_SECRET_ACCESS_KEY=$VSPHERE_AWS_SECRET_ACCESS_KEY \
>   -e VSPHERE_AWS_REGION=$VSPHERE_AWS_REGION \
>   -e CLOUD=vsphere \
>   -e BACKEND=file \
>   -e NAME=pd21944 \
>   -e COMMAND=destroy \
>   -e VSPHERE_DESTROY_FORCE=true \
>   -ti provisioning
# deleting DNS entries for master node(s)
  - pd21944-master-1.pd21944.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-1","modifiedIndex":25472,"createdIndex":24430},"prevNode":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-1","value":"{\"host\":\"<IP_ADDRESS>\"}","modifiedIndex":24430,"createdIndex":24430}}
  - pd21944-master-2.pd21944.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-2","modifiedIndex":25473,"createdIndex":24432},"prevNode":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-2","value":"{\"host\":\"<IP_ADDRESS>\"}","modifiedIndex":24432,"createdIndex":24432}}
  - pd21944-master-3.pd21944.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-3","modifiedIndex":25474,"createdIndex":24431},"prevNode":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-3","value":"{\"host\":\"<IP_ADDRESS>\"}","modifiedIndex":24431,"createdIndex":24431}}

# deleting DNS entries for worker node(s)
  - pd21944-master-1.pd21944.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21944/pd21944-worker-1","modifiedIndex":25475,"createdIndex":24429},"prevNode":{"key":"/skydns/local/vsphere/pd21944/pd21944-worker-1","value":"{\"host\":\"<IP_ADDRESS>\"}","modifiedIndex":24429,"createdIndex":24429}}

# deleting AWS load balancer(s)
  - arn:aws:elasticloadbalancing:us-west-2:571501312763:loadbalancer/net/xapi-20180712204423284700000002/0f31cb7bb30b2d35

# waiting for deletion of AWS load balancer(s)

# deleting AWS load balancer target group(s)
  - arn:aws:elasticloadbalancing:us-west-2:571501312763:targetgroup/xapi-20180712204421432200000001/6cdd67ac5ae591c0

# deleting AWS elastic IP address(es)
  - eipalloc-02a87e539046d61af ... ... ... ... ... ... ... ... ...

# deleting vSphere VM(s)
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944/pd21944-master-2
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944/pd21944-worker-1
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944/pd21944-master-1
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944/pd21944-master-3

# deleting vSphere folder(s)
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944

# deleting vSphere resource pool(s)
  - /SDDC-Datacenter/host/Cluster-1/Resources/Compute-ResourcePool/CNCF Cross-Cloud/pd21944

# deleting Terraform state

real	1m10.669s
user	0m7.330s
sys	0m1.150s

Hi @lixuna,
From my perspective this issue can be closed. However, the S3 buckets with the TF state may still need to be cleaned up. I imagine there's an auto-expiring lease on those, so it may not be an issue.


Installation of langchain on miniconda with the conda install langchain -c conda-forge fails

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
conda install langchain -c conda-forge
Error Message and Stack Trace (if applicable)
Collecting package metadata: done
Solving environment: failed
PackagesNotFoundError: The following packages are not available from current channels:

langchain

Current channels:

https://conda.anaconda.org/conda-forge/linux-64
https://conda.anaconda.org/conda-forge/noarch
https://repo.anaconda.com/pkgs/main/linux-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/free/linux-64
https://repo.anaconda.com/pkgs/free/noarch
https://repo.anaconda.com/pkgs/r/linux-64
https://repo.anaconda.com/pkgs/r/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org

and use the search bar at the top of the page.
Description
Installation problem
System Info
pip freeze | grep langchain as expected none
Python 3.7.3
miniconda on linux

Python 3.7.3 is no longer supported. Please upgrade to a more recent version of python.

Closing as likely not an issue. Feel free to re-open if unable to install with newer version of python


⚠ RPC server - Harmony has degraded performance

In adee809, RPC server - Harmony ($HARMONY_RPC_URL) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: RPC server - Harmony performance has improved in b55d29e.


feat: test cases for the Tab component

This is a good start.  I would like the following added:

Do the selector fix outlined above.
I would also like to add in the unit test that the active tab always has aria-selected="true".
Ensure the DOM has the right structure.  Take a look at the code walk-through on the Enable Tabs page.  Steps #5-#9 in that walk-through will tell you what you should test for. (I should have outlined that to you before starting work that you should go through the code walk-throughs).

Let me know when this is done and I'll approve (I do want to run on my local to double check when I am done, but it looks like it works as it should.

@zoltan-dulac Feedback has been incorporated, please validate.

Hi Mahesh! Good job so far.  Just want a few more changes.  After those are done, I think we can merge.


Scrollspy component js error issue

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
scrollspy component javascript error.

Reduced test cases
we should check the find result first, if found then add the CSS class.
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.1.3

No live example, not using latest version—please open a new issue once done.


Add tests for unix timestamp

@sylvestre

Could you please run rustfmt? Merci

@sylvestre done.

@tertsdiepraam i can put this in my other pr and close this, i think this might be better?


Override Dispatch training with customer provided training

Is your feature request related to a problem? Please describe.
When a user trains in utterances to skill bots or QnA Maker, many times the dispatcher guesses wrong at the correct path to dispatch the utterance.  In this case, the user has to go to LUIS and train the dispatcher to the correct way to route, however this is lost every time the dispatcher is updated.
Example: Trained QnA Maker to know "What kind of tires does my car use?" however, dispatcher thinks I want new tires and routes to Schedule service to get new tires...
Describe the solution you'd like
The dispatcher should update with the changes that has been provided by the user for additional top-level intent training to be kept when the dispatch refresh runs again.
Describe alternatives you've considered
We have discussed making another command that has an input file that could be loaded into training post running the dispatch refresh.

@tsuwandy Would appreciate your thoughts on this requirement. Effectively if there is "nudging" required for certain utterances to help the dispatcher better route how can we provide this to dispatch on refresh operations to apply each time and not use. Whilst edge scenarios can be be added to the respective luis models or qna I think an "alteration" file step could still be required.

@Dewain27 and @darrenj , this is already possible today.  Provide the utterances to override in a file (one per line), add this to Dispatch with the same intent name as the QnAMaker, is “add -t file -f {filePath} -intentName q_{QnAMakerName}”.
This will persist over refresh, and there is no need to have to go to luis to update.
Could you please share your dispatch sources with me so we could analyze why Dispatch couldn’t dispatch correctly without overrides?  Thanks!!


eigenpy: 3.0.0 -> 3.1.0

Description of changes
Hi,
This update

eigenpy to v3.1.0, ref. https://github.com/stack-of-tasks/eigenpy/releases/tag/v3.1.0 for changelog
example-robot-data to v4.0.8, ref. https://github.com/Gepetto/example-robot-data/releases/tag/v4.0.8 for changelog
crocoddyl to v2.0.1, ref https://github.com/loco-3d/crocoddyl/releases/tag/v2.0.1 for changelog

while here:

use finalAttrs instead of rec
add check & python import check
add myself in maintainers (not sure how this should be done, but I'd like to get tagged if there is any issue on those packages, as I'm their upstream maintainer ;) )

This is on staging, because this needs #242877 to get tests working on python 3.11.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I also added scipy in crocoddyl's checkInput

Result of nixpkgs-review pr 244184 run on x86_64-linux 1

12 packages built:

crocoddyl
example-robot-data
python310Packages.crocoddyl
python310Packages.eigenpy
python310Packages.example-robot-data
python310Packages.hpp-fcl
python310Packages.pinocchio
python311Packages.crocoddyl
python311Packages.eigenpy
python311Packages.example-robot-data
python311Packages.hpp-fcl
python311Packages.pinocchio


Keys 1 and 2 non functional in our plugin

🐛 Bug Report
We developed the Svetlana plugin https://pypi.org/project/napari-svetlana/.
It was working like a charm, but it now seems that the keys 1 and 2 are used as shortcuts and our plugin doesn't work anymore.
To reassign the keys, we used viewer.bind_key("1", overwrite = True), which we supposed overwrites the shortcut for 1 and 2.
Now, 2 is used to have small squares appearing. 1 is doing nothing visible.
Can anyone help ?
💡 Steps to Reproduce
Install Svetlana,
Type 1 and 2 in annotation mode
💡 Expected Behavior
Choose label 1 and label 2
🌎 Environment
napari: 0.4.18
Platform: Linux-6.2.0-36-generic-x86_64-with-glibc2.35
System: Ubuntu 22.04.3 LTS
Python: 3.10.10 | packaged by conda-forge | (main, Mar 24 2023, 20:08:06) [GCC 11.3.0]
Qt: 5.14.2
PyQt5: 5.14.2
NumPy: 1.24.4
SciPy: 1.11.3
Dask: 2023.11.0
VisPy: 0.12.2
magicgui: 0.8.0
superqt: 0.6.1
in-n-out: 0.1.9
app-model: 0.2.2
npe2: 0.7.3
OpenGL:

GL version:  4.6.0 NVIDIA 470.223.02
MAX_TEXTURE_SIZE: 32768

Screens:

screen 1: resolution 1920x1200, scale 1.0

Settings path:

/home/clement/.config/napari/mambaforge_0afcfc590f1d47f8545815636cc1a9dcb5d72f78/settings.yaml
Plugins:
napari: 0.4.18 (77 contributions)
napari-console: 0.0.9 (0 contributions)
napari-svetlana: 0.3.0 (10 contributions)
napari-svg: 0.1.10 (2 contributions)

💡 Additional Context
No response

Thanks for reporting, this seems like the same issue as:
https://github.com/napari/napari/issues/2799
See my test here:
https://github.com/napari/napari/issues/2799#issuecomment-1807168738
It appears that napari keybinds set in Preferences cannot be overwritten.
It does not appear this is plugin specific.
Can you confirm that in your case you have a labels or shapes layer selected? and that the tools do change? Labels 1 = Eraser, 2 = Brush; Shapes 1 = remove vertex, 2 add vertex

Hi,
Actually no. The layer is an image layer. 1 seems to do nothing, and 2 shows little squares on the image corners, which enable to resize it. A few months ago all keys from 1 to 9 worked for our plugin because we had overwritten it. It does not work anymore for 1 and 2 but keeps working for the others. I suppose it comes from an addition of features on 1 and 2 which did not exist before?

The plugin works in 0.4.17 but not in 0.4.18 anymore. It seems that something went wrong with these keys.

Ah, image layer. Well that one also has keybinds in the Preferences > Shortcuts > Image layer:

So 1 does nothing because it's activating Pan/Zoom and 2 is activating the transform.
And this was added in 0.4.18, so it does appear to be a manifestation of the same issue: keybinds set via viewer.bind_key are ignored if the keybind is set via Preferences > Shortcuts
You can test by unbinding 1 and 2 in the Preferences.

Thanks a lot for your help. We have a tutorial tomorrow and we will tell the participants to remove the shortcuts 1 and 2. However, on the long run, it seems like a shame that you cannot overwrite those shortcuts.

Swinging back to this, using viewer.bind_key pre-existing keybinds cannot be over-written.
But layer-specific ones do appear to work. So either import e.g. Image and do
Image.bind_key
or grab a handle for the layer you want (my_layer = viewer.layers['my layer']) and use:
my_layer.bind_key


Changing the name of a repository creates a new repository and delete the old one

When changing the name of a repository, a new repository is created and the old one is deleted.
The expectation would be that only the name changes, while keeping its content.
Note that the "id" of the ressource remain the same.
Code:
new CfnRepository(this, `GithubRepositoryTestFromCdk`, {
    name: 'test-from-cdk-rename, // Changing this value
    organization: orgName,
  });

The CDK diff output also suggest that only the name of the repository would change and there's no indication of replacement.
[~] GitHub::Repositories::Repository GithubRepositorytest-with-cdk GithubRepositorytestwithcdk
 └─ [~] Name
     ├─ [-] test-from-cdk
     └─ [+] test-from-cdk-rename

@GrumpyDevOps thanks for bringing this to our attention. Will look into this with the team.

No further details needed at this time. I'll let you know if things change. On early inspection, changing the name should not be replacing the resource and we're looking into fixing this.

@GrumpyDevOps yes! Planning to publish this with a batch of other 3rd party resource updates in the coming weeks.


[pt run] style scroll bars in results

in wpf branch, get scroll bars to be stylized

was merged in with #4343

Fixed in 0.19.0, please visit https://github.com/microsoft/PowerToys/releases/ for the latest release


Improve replay from captured metadata files

Replay using recorded metadata could go one of two ways:

"Touchless" replay asks the user after parsing for appropriate data inputs, and then runs the replay with them.
"Hands on" writes a script (like we do now), but incorporates the captured metadata files by dumping them, and then loading them appropriately from their dumped location on disk.

If we decide to build a "touchless" replay that uses recorded metadata, init_md_from_recorded_md needn't render anything, but needs to load properly.
If we go "hands on", we're going to need to render the Python API to insert an actual filepath, rather than producing some comment. This is probably easiest to handle with another variant driver.

Touchless replay is still a desirable target - I've opened a separate issue for it at #98


jupyter-scala with Spark does not see imports

I am running jupyter notebook on the machine where is available configured spark distribution with spark-submit , spark-defaults etc. I have running Python and R kernels but I have issues with jupyter-scala. I try to run the following code inside the notebook;
import org.apache.spark.SparkConf
import org.apache.spark.SparkContext
import org.apache.spark.SparkContext._
import com.datastax.spark.connector._

val conf = new SparkConf(true)
val sc = new SparkContext("spark://<IP_ADDRESS>:7077", "test", conf)

but it seems the jars are not visible by it
Main.scala:29: object datastax is not a member of package com
 ; import org.apache.spark.SparkConf ; import org.apache.spark.SparkContext ; import com.datastax.spark.connector._ ; val conf = { () =>
                                                                                ^
Main.scala:29: object apache is not a member of package org
 ; import org.apache.spark.SparkConf ; import org.apache.spark.SparkContext ; import com.datastax.spark.connector._ ; val conf = { () =>
              ^
Main.scala:30: not found: type SparkConf
new SparkConf(true)
    ^
Main.scala:29: object apache is not a member of package org
 ; import org.apache.spark.SparkConf ; import org.apache.spark.SparkContext ; import com.datastax.spark.connector._ ; val conf = { () =>
                                                  ^
Main.scala:33: not found: type SparkContext
new SparkContext("spark://<IP_ADDRESS>:7077", "test", conf)
    ^

I have tried to add before it
classpath.addPath("/var/lib/spark/lib/spark-assembly-1.6.0-hadoop2.6.0.jar")
classpath.add("datastax" % "spark-cassandra-connector" % "1.6.0-M1-s_2.11")

but nothing changes.
I am running jupyter-scala from https://git.io/vzhRi .

This is how I went about solving the issue I had (similar to you)
Installed Jupyter Toree from here: https://github.com/apache/incubator-toree

@drizham thx, but unfortunatelly toree supports only scala 2.10?

@mmatloka @drizham Sorry, I've been kind of lacking time recently for jupyter-scala (although I and colleagues are using it quite a lot at my $$ job).
This notebook illustrates how I usually use it to run things with Spark on a YARN cluster. I intend to make the doc better after the final release fo coursier, that jupyter-scala uses extensively.

Also, you should follow the updated README to install it.

I run into the same issue with Spark 2.3 and Scala 2.11. I used https://github.com/jupyter-scala/jupyter-scala to integrate with jupyter. What is the Toree agnostic way to integrate Spark+Scala and Jupyter?


Update headers to support RN >= 0.40

Please merge this

Please merge this ASAP please

I can confirm that yarn add holmesal/react-native-ios-notification-actions#17/head is compatbile with react-native version 0.44.0. Great PR.

Thanks! Sorry for the delay, I'm not actively maintaining this repo and will add a notice to the README


build(deps): bump log4js from 6.2.1 to 6.3.0

closes: #2346

@kmdrGroch please don't forget about https://github.com/log4js-node/log4js-node/issues/1037
This was the reason for me not to migrate earlier. If I recall correctly, the Linux pipelines will fail.

@kmdrGroch please don't forget about log4js-node/log4js-node#1037
This was the reason for me not to migrate earlier. If I recall correctly, the Linux pipelines will fail.

that is indeed strange :/ I didn't know there was such an issue out there

Yeah, we'll need to investigate. We're probably doing something undocumented that isn't supported anymore. For example, we're calling log4js.configure multiple times, that's probably shady territory.
The log4js configuration was complicated because of the old ConfigEditor plugins. They had the ability to change the logLevel. This is why we choose to call log4js.configure a second time after loading them. Since those plugins are no longer supported (I love v4 🎉), we might be able to simplify the log4js configuration.

Yeah, we'll need to investigate. We're probably doing something undocumented that isn't supported anymore. For example, we're calling log4js.configure multiple times, that's probably shady territory.
The log4js configuration was complicated because of the old ConfigEditor plugins. They had the ability to change the logLevel. This is why we choose to call log4js.configure a second time after loading them. Since those plugins are no longer supported (I love v4 🎉), we might be able to simplify the log4js configuration.


feat(collection): show department on table

Great job! We just need a couple of improvements, and we're good to go 👍🏽

Just remove the column when the user is on any department (basically is available on the /cat and /src)
Make department cliccable. If the user clicks on the name, it will be taken to the department page


Re-enable Travis CI builds for this repository?

They were working back in December when I submitted #415 and that build passed.  Now we have no way of knowing if changes are of any quality?

This is fixed now thanks to @kevin1024 !


Table Page Should Display Table Name

Is your feature request related to a problem? Please describe.
When navigating from the "Tables" page to a specific "Table page, the human-readable name is not displayed anywhere. When multiple tabs are open for multiple tables it's easy to lose track of which table id maps to which table name.
Describe the solution you'd like
The "Table" page should display the table name. I would not be upset if the table id was also displayed in parenthesis. For example "TableName (table_id)"
Describe alternatives you've considered
I briefly considered memorizing the mapping of table name to table id but ultimately decided against it.
Additional context
N/A

I briefly considered memorizing the mapping of table name to table id but ultimately decided against it.

:rofl:


robot not generate log.html and report.html when exception raised by python lib

During running test case, when test case failed with exception error raising by the python lib, the robot seems terminated by itself.
Here is the partial error message shown in console log:
[ ERROR ] Initializing library 'Redfish' with arguments [ https://<IP_ADDRESS>:443 | root | 0penBmc ] failed: RetriesExhaustedError
Traceback (most recent call last):
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
OSError: [Errno 113] No route to host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 703, in urlopen
    httplib_response = self._make_request(
                       ^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 386, in _make_request
    self._validate_conn(conn)
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn
    conn.connect()
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/connection.py", line 363, in connect
    self.sock = conn = self._new_conn()
                       ^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/connection.py", line 186, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x708e8914be10>: Failed to establish a new connection: [Errno 113] No route to host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/vscode/.local/lib/python3.11/site-packages/requests/adapters.py", line 667, in send
    resp = conn.urlopen(
           ^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 787, in urlopen
    retries = retries.increment(
              ^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Max retries exceeded with url: /redfish/v1/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x708e8914be10>: Failed to establish a new connection: [Errno 113] No route to host'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/vscode/.local/lib/python3.11/site-packages/redfish/rest/v1.py", line 915, in _rest_request
    resp = self._session.request(method.upper(), "{}{}".format(self.__base_url, reqpath), data=body,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/requests/adapters.py", line 700, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Max retries exceeded with url: /redfish/v1/ (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x708e8914be10>: Failed to establish a new connection: [Errno 113] No route to host'))

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/workspace/lib/bmc_redfish.py", line 50, in __init__
    super(bmc_redfish, self).__init__(*args, **kwargs)
  File "/home/vscode/.local/lib/python3.11/site-packages/redfish/rest/v1.py", line 1080, in __init__
    super(HttpClient, self).__init__(base_url, username=username,
  File "/home/vscode/.local/lib/python3.11/site-packages/redfish/rest/v1.py", line 505, in __init__
    self.get_root_object()
  File "/home/vscode/.local/lib/python3.11/site-packages/redfish/rest/v1.py", line 597, in get_root_object
    raise excp
  File "/home/vscode/.local/lib/python3.11/site-packages/redfish/rest/v1.py", line 595, in get_root_object
    resp = self.get(self.default_prefix)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/lib/redfish_plus.py", line 133, in get
    return self.rest_request(super(redfish_plus, self).get, *args,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/lib/redfish_plus.py", line 123, in rest_request
    response = func(*args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/redfish/rest/v1.py", line 633, in get
    return self._rest_request(path, method='GET', args=args,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/redfish/rest/v1.py", line 1118, in _rest_request
    return super(HttpClient, self)._rest_request(path=path, method=method,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vscode/.local/lib/python3.11/site-packages/redfish/rest/v1.py", line 959, in _rest_request
    raise RetriesExhaustedError() from cause_exception
redfish.rest.v1.RetriesExhaustedError

Try --help for usage information.

This error indicate that the redfish python lib encounter some network issue, it retries many times and raise exception.
I also try to regenerate report.html by execute rebot output.xml, but it says:
[ ERROR ] Reading XML source 'output.xml' failed: Incompatible child element 'errors' for 'suite'.

Try --help for usage information.

Here is the output.xml:
output (複製).zip

For some reason the whole execution crashes when initializing the library as part of the importing process fails. This shouldn't happen, we have tests for handling errors like this so that execution can continue normally. I also tested this separately with a simple library that has a failing __init__. I even tried raising redfish.rest.v1.RetriesExhaustedError to see is that exception somehow special, but also that was handled fine.
Can you provide a simple example I could use to reproduce this? Also, what Robot Framework version did you use?


If no explicit credentials are provided, use either environment variables, local .aws/credentials profile or IAM role

Feature description
IIRC most if not all of that is already supported by the DefaultCredentialsProvider, but worth cross-checking and documenting

We already use the DefaultCredentialsProvider  that is documented to use the following:

Java System Properties - {@code aws.accessKeyId} and {@code aws.secretAccessKey}

Environment Variables - {@code AWS_ACCESS_KEY_ID} and {@code AWS_SECRET_ACCESS_KEY}

Web Identity Token credentials from system properties or environment variables

Credential profiles file at the default location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI

Credentials delivered through the Amazon EC2 container service if AWS_CONTAINER_CREDENTIALS_RELATIVE_URI" environment

variable is set and security manager has permission to access the variable,

Instance profile credentials delivered through the Amazon EC2 metadata service

All task properties that allow configuring credentials have this description:
"If no connection is defined, we will use the `DefaultCredentialsProvider` to fetch the value."

What I can do is to change it to link to this page of the AWS documentation instead:
https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials-chain.html
I can also add a global guide in the plugin to better explain how to authenticate as we have for the GCP plugin.

In fact there is already a documentation at the root, I'll improve it.


"Uncaught TypeError: Failed to execute 'connect' on 'AudioNode': No function was found that matched the signature provided." starting in 13.7 (maybe 13.6)

I'm afraid I don't have time to whittle this down to a minimal example that reproduces the problem right now, but perhaps this info will be sufficient to identify the problem and I don't want to lose the detail I do have so far. I'll follow up with more details as I can.
I'm using Tone.js (and in particular, Tone.js's OfflineAudioContext) together with webaudio-tinysynth to synthesize music.  This is running within an Electron application.
My program works correctly with Tone 13.5.0, but when I upgrade to 13.7 I consistently get this error:
Uncaught TypeError: Failed to execute 'connect' on 'AudioNode': No function was found that matched the signature provided.

I have confirmed that swapping between Tone 13.5.0 and Tone 13.7.1 will consistently make the program work or not work (respectively).
The specific line on which the error occurs is Line 1293 in webaudio-tinysynth.js.  In my case that works out to something like this:
DynamicsCompressorNode.connect(OfflineAudioContext)

(where DynamicsCompressorNode is a instance of Chrome's implementation of the WebAudio DynamicsCompressorNode and OfflineAudioContext is an instance of Tone's OfflineAudioContext) as a result of calling:
tinysynth.setAudioContext(Tone.context, Tone.Master)

from within a Tone.Offline context.
For what it is worth I don't think there is anything special about that particular pairing, I seem to get the same error with any AudioNode.connect(OfflineAudioContext).
The only info I can find from googling that error message suggests that it is triggered by setting a NaN-valued or Infinity-value AudioParam, but after trying to hunt that down for a long time I'm not sure that's actually the problem I'm running into.

I've made these changes over the past couple of days which i think is what's causing your issue. Unfortunately, this is the new intended behavior and not a bug and will take a slight refactor to your code to upgrade to the latest version.
AudioNode.prototype.connect/disconnect used to be overwritten with a method which would accept Tone.js nodes in addition to native Web Audio Nodes. I think it's pretty well agreed upon that it's not great to modify built-in classes or methods, and as the library is more widely used, the potential for this causing issues in other people's code and libraries increases. With some encouragement from @chrisguttandin, I've decided that it's best to move away from overwriting any native methods.
There are two ways to fix this issue, either replace instances where you're connecting native nodes to Tone.js nodes with Tone.connect(srcNode, dstNode, [inputNum=0], [outputNum=0]). Or as a stop-gap, you can overwrite the native AudioNode.prototype.connect yourself to go back to the previous behavior:
const nativeConnect = AudioNode.prototype.connect
AudioNode.prototype.connect = function(dstNode, inputNum, outputNum){
  if (dstNode instanceof Tone){
    Tone.connect(this, dstNode, inputNum, outputNum)
  } else {
    nativeConnect.call(this, dstNode, inputNum, outputNum)
  }
}

I haven't tested this code, but it's pretty similar to what was in there before.

Thanks @tambien
Just to make sure I understand you correctly, by this:

replace instances where you're connecting native nodes to Tone.js nodes with Tone.connect(srcNode, dstNode, [inputNum=0], [outputNum=0])

You mean that if I start with this:
srcNode.connect( dstNode, [inputNum=0], [outputNum=0] )

it should change to this:
Tone.connect(srcNode, dstNode, [inputNum=0], [outputNum=0])

(which is your original example).
Right?

that should do it. all Tone.connect does is grabs the correct input from Tone.js which encodes it's inputs a little differently than Web Audio. Since they're all abstractions, each class has an 'input' and 'output' node. Tone.connect looks for that input node so that it could connect to it.

@tambien This solution doesn't seem to work when using React/Typescript:
I'm getting following error:
Unhandled Rejection (TypeError): AudioNode.connect: Argument 1 does not implement interface AudioNode
I'm passing streams with WebRTC, so the getUserMedia in my code is just an example. Outside of React/TS this works just fine following your solution.
Here's a link to the full gist.
Thanks in advance!

	//Tone Audio Node
	const toneGain = useMemo(() => new Tone.Gain), [])

	useEffect(() => {
		//Set Tone Context to AudioContext
		Tone.setContext(ac)

		//Connect Tone Vol Node to Destination
		Tone.connect(toneGain, Tone.context.destination)
	}, [toneGain])

	const connectStream = useCallback(
		(stream: MediaStream) => {
			//create media stream source
			const src: MediaStreamAudioSourceNode = ac.createMediaStreamSource(stream)
			//connect the source to Tone Volume Node
			Tone.connect(src, toneGain, 0, 0)
		},
		[toneGain]
	)

	const initUserMedia = useCallback(async () => {
		const stream: MediaStream = await navigator.mediaDevices.getUserMedia({
			audio: true,
		})
		connectStream(stream)
	}, [connectStream])

After you set a new context, Tone.context is still referring to the old one. (This has been since version 14.x). Try Tone.getContext().destination instead when connecting nodes.

That solved the issue! Thanks :)


CCU-194: Per-client mutes for Dolby Voice Server

@matthiasha Be careful, your MR is for master ⚠ the feature should be merged into develop first

This PR was based on the wrong branch, please ignore. It was replaced by #111


implement applicationShouldTerminateAfterLastWindowClosed

Hello! This api you've designed looks very good!
This app delegate method was missing from a simple one window app I was trying out.

Ah, cool! I think I skipped this one as I think it's  not how a good macOS app should act, but... I think you're right and it should be supported, some apps definitely need it.
Thanks for the pull request! Merging. :)