Diagnostic component colors not getting set correctly

It looks like the colors for the diagnostic component aren't getting set properly. I've tried it with just the theme colors and with setting the highlight groups manually before calling setup().
What they are:

What they should be (set manually through the color_ options):

What the highlight groups for error and warn are:

Here's a minimal config:
require("packer").startup {
  function()
    use "wbthomason/packer.nvim"
    use {
      "gruvbox-community/gruvbox",
      config = function()
        vim.cmd("colorscheme gruvbox")
      end
    }
    use {
      "neovim/nvim-lspconfig",
      config = function()
        -- sumneko_lua setup, but you can substitute any lsp config here
      end
    }
    use {
      "hoob3rt/lualine.nvim",
      requires = "kyazdani42/nvim-web-devicons",
      config = function()
        require("lualine").setup {
          theme = "gruvbox",
          sections = {
            lualine_a = {"mode"},
            lualine_b = {"branch", "diff"},
            lualine_c = {"filename"},
            lualine_x = {
              {"diagnostics", sources = {"nvim_lsp"}},
              "encoding",
              "fileformat",
              "filetype"
            },
            lualine_y = {"progress"},
            lualine_z = {"location"}
          }
        }
      end
    }
  end
}

I don't think packer insures gruvbox will be loaded before lualine can you check if setting colorscheme to gruvbox before calling lualine setup resolve the issue ?

@shadmansaleh is right. Packer is really weird about the code execution. This should probably be an issue in their repo unless it's done by design which is weird. I personally don't get any colors in both lualine's diagnostics/ diff or in gitsigns.nvim if I set a colorscheme in the packer file.
The best solution I found is to set a colorscheme in init.lua / init.vim which kindda sucks as it breaks the coolness of packer having plugin's config in the same file.

I don't think packer ensures gruvbox will be loaded before lualine can you check if setting colorscheme to gruvbox before calling lualine setup resolve the issue ?

I didn't include it in the minimal config and should have, but I have tested it with the after feature of packer, which delays loading lualine until after gruvbox is loaded:
use {
  "hoob3rt/lualine.nvim",
  requires = "kyazdani42/nvim-web-devicons",
  after = "gruvbox",
  config = function()
    ...
  end
}

But I also just tried with manually using packadd and colorscheme like you suggested, and that doesn't work either.

@shadmansaleh is right. Packer is really weird about the code execution. This should probably be an issue in their repo go ahead and create it while linking this issue if I don't do it before you. I personally don't get any colors in both lualine's diagnostics/ diff or in gitsigns.nvim if I set a colorscheme in the packer file ( I used to have a config similar to yours)
The best workaround I found is to set a colorscheme in init.lua / init.vim which kindda sucks as it breaks the coolness of packer having plugin's config in the same file.

This also doesn't work for me.

The best workaround I found is to set a colorscheme in init.lua / init.vim which kindda sucks as it breaks the coolness of packer having plugin's config in the same file.

This also doesn't work for me.

Okay, I will look more into it later then

I dug around in the logic a bit already to no avail, but I'll give it another go tonight if I have time.

Hoooooooooookay. Two things:

I ran a few of my tests with -U instead of -u. That's my bad. Some of my tests pulled in my basic config in init.lua, which include #2 below.
It looks like turning on termguicolors is what borks it. Unfortunately, disabling that also borks my colors.

It looks like turning on termguicolors is what borks it

This makes absolutely no sence to me because we naver directly handle non termguicolors . Rather they are caculated in time of highlight genaration from termguicolors/rgb colors .So if non termguicolor works termguicoloe has to work.
By the way does your diff colors work correctly ?

I've found the issue lol. Should be quickfix :)

@timbedard see if #144 works.

@shadmansaleh Nailed it!


Create 4.x helper class for URL params

Create a 4.x helper class to convert all the common url params like extent and such to their appropriate classes. In the 3x boilerplate, this was called map params.
I think in the new boilerplate it should be called urlHelper or something similar since it will work for scene and webmap.

https://github.com/Esri/application-boilerplate-js/blob/master/application_boilerplate/js/MapUrlParams.js
https://github.com/Esri/application-boilerplate-js/blob/4master/js/application/main.js#L147

@kellyhutchins this is installed. Can you test/review?

Assuming this is good now.


Fix typos in Wunderground component (Percipitation -> Precipitation)

Description:
Fixed typos in Wunderground UI

Hi @mje-nz,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Thanks!

Cherry-picked for 0.46.1


Feature request: what about robots.txt?

(Please ignore/delete if I am misunderstanding what Node-Fetch is.)
I only found out about this by seom requests to a Website I mange.
No robots.txt check. Is that okay?
Note also subsequent requests changed the user-agent string. Is that okay?

node-fetch is not a robot or a spider that scans websites or anything like that. node-fetch is a light-weight module that brings window.fetch to Node.js to help developers make requests similar to curl or wget. so it don't do any special handling with robots.txt.
robots.txt should be handle by the developers that use node-fetch and respect it.
ps node-fetch don't automatically changes the user agent to be something dynamic. and it don't try to mimic any browser client. node-fetch defaults to using "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" but will soon be changed to just be node-fetch in later version, still doe developer have the option to change the user-agent if they want to do that.

Okay. Thank you for that information. But someone is making many requests to some websites I manage, all using "node-fetch" and then using a different UA - same IP - so many requests it's suspicious. Why do you think that is? (Rhetorical.)
I just block that IP now.
Thanks. Let's close this.

Why do you think that is? (Rhetorical.)

Don't know... hardly know anything about your webpage and what it dose. I have made a couple of bots/scrapers sometimes myself in my days for personal use...

Would try to google up the ip address to try and found out more of what it's.

Would also try to investigate what kind of web pages dose it scan. is it trying to scrape something off your site? try searching for duplicate content on other sites... observe the behavior of the client and what he is doing.

If you have a rest API, why isn't he using that instead?

instead of maybe flat out block the ip. give him a message and maybe let him contact you somehow.

also be aware of x-forward-for some agents can spoof it if you trust proxies.

Also this will only become a cat and mouse game. if he really wants to make request to your page he will find a way to do so.

You could look into using something like a annoying captcha wall or a rate limit of that sort also.

dDOS could be one thing also 😉

feels a bit special that he is doing a HEAD request first and gather some response headers before doing the other GET requests...
Normally not many developer are changing the user-agent if they don't have to. a CORS proxy could just simply forward all request headers.

https://cleantalk.org/blacklists/as16733


can a mixin extends a mixin

Dart VM version: 2.1.0 (Tue Nov 13 18:22:02 2018 +0100) on "windows_x64"

I have a class who is a mixin  that class contains all the shared variables . and i want another mixin to access to one of this   but for some reason the secon mixin can't find the variable .
mixin User on Model { bool _isLoading ; }
 mixin Utility on User {   bool get isLoading {     return _isLoading;   } }
is there any solution for this

Seems like a bug to me.
The Utility mixin requires a superclass implementing the User interface. That means that it will itself also implement that interfaces, so _isLoading, aka. this._isLoading should be valid (as long as both mixins are declared in the same library, since the name is library private).
It appears to be working in dartpad:
mixin Foo { int get _foo => 42; }
mixin Bar on Foo { int get bar => _foo; }
class O = Object with Foo, Bar;
main() {
  print(O().bar);
}

prints 42.
How do you run/analyze your code?

I have solved it when i was refactoring my code i changed the utility class into another file and since _isLoading is a private the compiler coldn't find it so i changed _isLoading to isLoading


Cookbook/Client-side Storage example description doesn't correspond to the example

At the end of the base example it says:

You could also store a date representing when the values were stored. With that metadata, the mounted method could make a logical call on whether or not to store the values again, such as in this version below. You can try this version below.

But in the example the mounted method only do:
if(localStorage.name) this.name = localStorage.name;
if(localStorage.age) this.age = localStorage.age;

The mounted method only check if the values exist, it never "make a logical call on whether or not to store the values again".

Would you be so kind and link to the section that you are talking about? We don't haven't memorized very section of the documentation, and I have no idea what you are talking about right now.

Sure it's in the cookbook/client-side storage https://vuejs.org/v2/cookbook/client-side-storage.html. Go at the last paragraph of the base example.

@cfjedimaster should you change your CodePen example or should we change the description?

Ok I can do that.

Done in #1797


PL: Fix deploy

Placeholder ticket.
Surge deploy is failing, we need to fix it or do deploys a new way so that PL can be deployed to a subdomain of protocols.opentrons.com

Old PL Surge account had been deleted (but somehow kept working for at least 2 months after deletion?). Needed to reset and bind a new account & make a new token.


[vcpkg] Improve creation of port templates

The current use of ./vcpkg create port is too simple, try to match complex steps.
This PR will help contributors to better create a port template.
This PR will:

Automatically detect download sources to use github / gitlab / git / url.
Automatically detect build port to use vcpkg_*_cmake / vcpkg_*_make / vcpkg_*_msbuild / vcpkg_*_nmake / vcpkg_*_qmake.

usage:
.\vcpkg create PORT_NAME URL FILE_NAME/REF <TRIPLET BUILD_TYPE>(optional)
example:
For github:

.\vcpkg create devil https://github.com/DentonW/DevIL e34284a7e07763769f671a74b4fec718174ad862 windows nmake linux cmake
.\vcpkg create devil https://github.com/DentonW/DevIL v1.8.0.tar.gz windows msbuild

For gitlab:

.\vcpkg create cmocka https://gitlab.com/cmocka/cmocka f5e2cd77c88d9f792562888d2b70c5a396bfbf7a linux cmake
.\vcpkg create cmocka https://gitlab.com/cmocka/cmocka cmocka-cmocka-1.1.5.tar.gz windows cmake osx make

For git:

.\vcpkg create fdlibm https://android.googlesource.com/platform/external/fdlibm 59f7335e4dd8275a7dc2f8aeb4fd00758fde37ac

For url:

.\vcpkg create zlib2 http://zlib.net/zlib1211.zip "zlib1211-2.zip" windows cmake linux make

Progress:

[x] Add cmake-side support
[x] Add c++-side support
[x] Test

Related: #8363

/azp run

/azp run

/azp run

Depends on https://github.com/microsoft/vcpkg/pull/11839

I would love this feature; @JackBoosY can you fix the merge conflicts?

@strega-nil I think this PR should be discussed because the parameter settings are not ideal.

@strega-nil Should we also automatically generate the CONTROL file?

Close this PR temporary.


Added Awesome-iOS-Twitter by @carolanitz

Project URL

https://github.com/carolanitz/Awesome-iOS-Twitter
Description

A curated list of awesome iOS Twitter accounts worth following inspired by Awesome iOS The list is divided into the categories People, Conferences and Blogs. There is no defined order in each category.
Why it should be included to awesome-ios (optional)
With so many bad things happening in the world, I'm trying to keep my twitter only to follow developers. This list is the best resource for you to follow amazing developers and other twitter users related to the iOS community
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 1 link issue, a project collaborator will take care of these, thanks: )

Link issue by awesome_bot

Line
Status
Link

2660
301
http://ivomynttinen.com/blog/ios-design-guidelines redirects tohttps://ivomynttinen.com/blog/ios-design-guidelines

  Generated by :no_entry_sign: Danger


Improve commands.util package

Apply builder pattern to Parameter and DefinedParameter.

Closing this due to lack of time and not really useful improvement to code quality.


[WIP] feat(guide/di): adds ES5 version of DI chapter

Copied from an IdeaBlade PR 13, now closed.
Pascal said: this one doesn't have runnable examples yet, but comes with code snippets do work.

@googlebot I'm cool with it.
@wardbell this PR mainly needs review for the snippets. Content-wise there's not such a big difference in comparison to the TS version. Once I get a "go" I'll move the snippets to examples.
However, we can also already merge this one and I can send a second PR that moves stuff out.

Closing because we're not rolling this way.


sync from is broken

Describe the bug
plakar sync to works but plakar sync from produces a compression error,
very likely to be related to client side compression/decompression logic being broken.
To Reproduce
Steps to reproduce the behavior:
$ plakar sync 7ffb from /tmp/cloned
repository passphrase:
destination repository passphrase:
/Users/gilles/.plakar: could not load snapshot from repository: lz4: bad magic number
$

This was fixed during the repo refacto


refactored the RT type

the cursors are now handled by an Y.Object
implemented the correct way to bind an editor to the RT type
added example
added test for the browser (first compile, then open test/index.html
in the browser)

You need to pull the newest changes from yjs & y-list. Then this should work.


Azure Deployment Fails With Powershell Deployment Script

Command: powershell -file deploy.ps1
File D:\home\site\repository\deploy.ps1 cannot be loaded because running
scripts is disabled on this system. For more information, see
about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
    + CategoryInfo          : SecurityError: (:) [], ParentContainsErrorRecord
   Exception
    + FullyQualifiedErrorId : UnauthorizedAccess

I've configured the .deployment file as described in https://github.com/projectkudu/kudu/wiki/Customizing-deployments

To be precise, the build actually "succeeds" as far as the Azure portal is concerned.

Try something like this in your .deployment file (which is what kuduscript generates for PowerShell):
command = powershell -NoProfile -NoLogo -ExecutionPolicy Unrestricted -Command "& "$pwd\deploy.ps1" 2>&1 | echo"

I'll give that a go

That worked. Thank you. Do you want to leave this open until either the wiki is updated or the "bug" is fixed?

I updated the wiki. I know there was a reason to have such a crazy syntax! :)

I added in some notes for the crazy PowerShell syntax, makes it less crazy, still a bit mad. 3 dollar signs away from "I can't believe it's not Perl!".
https://github.com/projectkudu/kudu/wiki/Customizing-deployments

Thanks @snobu! I was reading through the syntax earlier and really didn't have a clue what it was doing :)


unable to build on phonegap (org.apache.cordova.file does not exist)

hi
we have below error when pgb
Error: Building status: error (package org.apache.cordova.file does not exist)

I had same problem just recently and solved by updating my config.xml plugin - the versions that worked for me below:
    <plugin name="cordova-plugin-file" spec="4.3.3" />
    <plugin name="cordova-plugin-file-transfer" spec="1.6.3" />


Allow HOMEBREW_PREFIX replacement in external patches

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
This follows up the recommendation from https://github.com/Homebrew/brew/pull/15841, to use:
patch do
  url "file://#{__dir__}/Formula.patch_name.diff"
end

for externally stored patches. My problem is that in this the following rule is not applied:

"In embedded patches, the string “HOMEBREW_PREFIX” is replaced with the value of the constant HOMEBREW_PREFIX before the patch is applied."

So I would like to enable this replacement (perhaps guarded by a boolean flag?).
What is the motivation for the feature?
This would allow us to move the embeded patches to external diff files.
How will the feature be relevant to at least 90% of Homebrew users?
Would make maintaining complex formulas with large diffs easier, and easier to configure formatter onto the formula files (as the formatter would not impact the diffs).
What alternatives to the feature have been considered?
Keeping the diff embeded means I cannot use formatter on the formula file.

Passing on this for now. Will still consider a PR but it seems that it's not widely demanded functionality.


chore: update eslint rule no floating promises

fix: bump @commitlint/prompt from 19.2.0 to 19.2.2

Bumps @commitlint/prompt from 19.2.0 to 19.2.2.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: "@commitlint/prompt"
dependency-type: direct:development
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
fix: bump typescript from 5.4.4 to 5.4.5

Bumps typescript from 5.4.4 to 5.4.5.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: typescript
dependency-type: direct:development
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
fix: bump @commitlint/cli from 19.2.1 to 19.2.2

Bumps @commitlint/cli from 19.2.1 to 19.2.2.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: "@commitlint/cli"
dependency-type: direct:development
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
fix: bump semantic-release from 23.0.7 to 23.0.8

Bumps semantic-release from 23.0.7 to 23.0.8.

Release notes
Commits

updated-dependencies:

dependency-name: semantic-release
dependency-type: direct:development
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
fix: update @commitlint/config-conventional 19.2.2

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>Co-authored-by: dependabot[bot]<EMAIL_ADDRESS>

:tada: This PR is included in version 1.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Expose DnsNameResolverContext (or something equivalent to it) to users

A user may want to reuse the logic related with search list enumeration, retries and error handling in his or her resolver implementations. For example, a user could extend or customize DnsNameResolverContext to implement DNS-based service discovery that retrieves SRV records, while respecting the global resolver configuration (/etc/resolv.conf). Currently, the user would have to re-implement search list enumeration, retries and error handling by his or her own.
Let me take a stab of this if it sounds good.

and does it sound good? :-)

I'll start to work on this if there's no objection.


Deprecate and remove building support for Spark 3.2

:mag: Description
This pull request aims to remove building support for Spark 3.2, while still keeping the engine support for Spark 3.2.
Mailing list discussion: https://lists.apache.org/thread/l74n5zl1w7s0bmr5ovxmxq58yqy8hqzc

Remove Maven profile spark-3.2, and references on docs, release scripts, etc.
Keep the cross-version verification to ensure that the Spark SQL engine built on the default Spark version (3.5) still works well on Spark 3.2 runtime.
Merge kyuubi-extension-spark-common into kyuubi-extension-spark-3-3
Remove log4j.properties as Spark moves to Log4j2 since 3.3 (SPARK-37814)

Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Pass GHA.

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (dc629f9) to head (837c4c8).

Files
Patch %
Lines

...rg/apache/kyuubi/engine/spark/SparkSQLEngine.scala
0.00%
2 Missing :warning:

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6545   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         677     677
  Lines       41789   41791    +2
  Branches     5707    5708    +1
======================================
- Misses      41789   41791    +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks, merged to master


How to use ground truth camera pose instead of esimating one during reconstruction

If I want to use ground truth camera pose when reconstructing, how can I modify the code splatam.py?

Hi, We already support use of ground truth camera pose while doing SLAM.
If you want to use ground truth camera poses while doing SLAM, you can set the following config to True:
https://github.com/spla-tam/SplaTAM/blob/8cee05f2ba7e43c8a6f055372a94668867d1fcda/configs/replica/splatam.py#L60
We also support 3D Gaussian Splatting with ground truth camera poses: https://github.com/spla-tam/SplaTAM/blob/main/scripts/gaussian_splatting.py


Refactor insert default values

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

👍


Loading_page(project)

This is responsive loading page.. please check & merge it ..

issue #289

@RAJEEVKUMAR9598 Kindly add some screenshots of your project here in the chat. Also, make a Readme.md file and add your project description and tech stack used there.


Updated Serilog reference to 1.5.1

Updated Serilog references to 1.5.1

This looks better than the last PR.

Thanks!


U2F login not working behind reverse proxy

Gitea version (or commit ref): 1.8.1
Operating system: docker@ubuntu 18.04
Database (use [x]):

[x] MySQL
[ ] PostgreSQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
I am using gitea behind traefik as reverse proxy. I managed to add my YubiKey U2F device but cannot login.
The connection is encrypted with https. This may happen because the secure connection is terminated in traeffik and gitea only "sees" an unencrypted connection from traeffik.
Screenshots
The screenshot appears after I entered my credentials:

This is a duplicate issue (#6748) and will be fixed in 1.8.2 (which is not released yet).


Please upgrade 'Ettercap' to the latest possible build!

[x] I Confirm this is not a problem with running a brew command and not brew installing or the post-install behaviour of one or more formulae
[x] I have Ran brew update and retried your prior step?
[x] I have Ran brew doctor, fixed all issues and retried your prior step?
[x] I have Ran brew config and brew doctor and included their output with your issue?

To help us debug your issue please explain:

I was trying to install etercap with gtk+ for networking purposes
The installation was succesfull but It didn't installed the latest build
The latest build includes support for pfctl commands but the one which homebrew installs has support only for ipfw commands which is no longer supported by macOS
First I typed in brew install ettercap --with-gtk+The installation was succesfull but when I ran ettercap using this command : sudo ettercap -G
The terminal showed this errors:
sh: ipfw command not found

Or propose a feature:
I request homebrew to update the archived version of ettercap to the latest possible build!

This may not be a version issue. The current Homebrew ettercap formula is for v0.8.2, and when I looked at the Ettercap downloads page tonight, it also says 0.8.2 is the latest version.
After installing with brew install ettercap --with-gtk+, I get this. Were you expecting a different version?
$ ettercap --version

ettercap 0.8.2 copyright 2001-2015 Ettercap Development Team

ettercap 0.8.2

Maybe this is a missing dependency instead, on whatever package provides an ipfw command. There's no ipfw in the current base macOS installation, from what I can tell, though from Googling, it looks like it used to be available.
FWIW, I cannot reproduce. I did a brew install ettercap --with-gtk+ and then did sudo ettercap -G and did not get an ipfw command not found error. This is on macOS 10.12.6 and latest Homebrew.  I did get this, but that looks unrelated, and about Retina displays.
$ sudo ettercap -G

ettercap 0.8.2 copyright 2001-2015 Ettercap Development Team

2017-08-23 04:59:07.466 ettercap[55804:2031459] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.

(<unknown>:55804): Gtk-WARNING **: Theme directory 256x256@2/animations of theme hicolor has no size field

Do you have some additional networking setup that might require ipfw or a replacement, where my vanilla setup doesn't?
(Sorry, I'm not familiar with ettercap. If there are more steps to exercise here that might reproduce, please let us know.)

What do you get with ettercap --version?

@apjanke You will get the ipfw error after uncommending ceratin lines in the etter.conf file which is located here : /usr/local/etc/ettercap/etter.conf
You need to uncommend these lines:
redir_command_on = "ipfw -q add set %set fwd <IP_ADDRESS>,%rport tcp from any to any %port in via %iface"
redir_command_off = "ipfw -q delete set %set"
I mean delet the # before these two lines inorder to route trafics through you mac
After you have uncommended these lines and remember to set these values
[privs]
ec_uid = 0                # nobody is the default
ec_gid = 0                # nobody is the default
to zero which I have already done
Now run ettercap then look into your terminal you will get this error

And I think there is a missing dependency issue!

There's been no ipfw since OS X 10.9.

It looks like this is due to OS X/macOS changing which firewall it uses in the last few releases, and Ettercap's example config files no longer being compatible with current releases of macOS.
I couldn't find official Apple doco for it, but per this and this, it looks like between OS X 10.7 and 10.10, IPFW was replaced by PF.
Ettercap hasn't seen a new release since 2015, so it's understandable they haven't kept up.
Looks like these ipfw commands need to be replaced by equivalent pfctl commands. There's a couple other places they show up in the Ettercap default config files.
$ grep -r ipfw *
ettercap/etter.conf:   #redir_command_on = "ipfw -q add set %set fwd <IP_ADDRESS>,%rport tcp from any to any %port in via %iface"
ettercap/etter.conf:   #redir_command_off = "ipfw -q delete set %set"
ettercap/etter.conf: #   if [ -a "/tmp/osx_ipfw_rules" ]; then
ettercap/etter.conf: #      ipfw -q add `head -n 1 osx_ipfw_rules` fwd <IP_ADDRESS>,$1 tcp from any to any $2 in via $3
ettercap/etter.conf: #      ipfw add fwd <IP_ADDRESS>,$1 tcp from any to any $2 in via $3 | cut -d " " -f 1 >> /tmp/osx_ipfw_rules
ettercap/etter.conf: #   if [ -a "/tmp/osx_ipfw_rules" ]; then
ettercap/etter.conf: #      ipfw -q delete `head -n 1 /tmp/osx_ipfw_rules`
ettercap/etter.conf: #      rm -f /tmp/osx_ipfw_rules

If someone has the time and expertise, this seems like an appropriate patch for Homebrew to provide, since it's an OS compatibility issue. (Though we usually expect upstream to keep up to date, too.) Looks a little out of my league, though. Better yet, submit a patch to upstream.
In fact, it looks like there's an open upstream PR for this issue: https://github.com/Ettercap/ettercap/pull/641. No activity since Feb 2015, though. Looks like this might be nontrivial.
To get around the immediate problem, you could edit your etter.conf to use pfctl instead of ipfw; no rebuild necessary.

It looks like the switch to pfctl may already be in master despite that issue still being open:
https://github.com/Ettercap/ettercap/commit/595a5e79ac8b4420a04201c038998f8f6b37503d

@ilovezfs @apjanke  Right now I don't know what to do please help!

@ilovezfs I know that the ettercap guys have updated support for pfctl but when I install ettercap using brew the build files are the old ones not the new ones for ettercap

brew uninstall ettercap
brew install --HEAD ettercap
and try with the new config file :)

@ilovezfs Ok bro! should i do this by going to the build directory via terminal or directly run these commands!

just run those commands :)

Directly run those commands.
And leave a comment on the upstream issue at https://github.com/Ettercap/ettercap/pull/641 asking if it's fixed and whether they might roll a new release. Our support for HEAD builds is mediocre at best; if they cut a new release you'll find it easier to use.

@apjanke Ok!

Good luck! Feel free to keep commenting here even though it's closed.
I agree with the close, and backing off my earlier suggestion for a patch – since upstream development looks kind of moribund, I don't know that this is something Homebrew can or should pull in to the formula. We mostly take in patches with the expectation that they'll be merged upstream, and without a release in two years...

@apjanke Looks like there is a GTK issue
Last login: Wed Aug 23 15:20:33 on ttys000
Sayans-iMac:~ sayan$ brew uninstall ettercap
Uninstalling /usr/local/Cellar/ettercap/0.8.2_1... (77 files, 2.5MB)
Sayans-iMac:~ sayan$ brew install --HEAD ettercap
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> Updated Formulae
grakn
==> Cloning https://github.com/Ettercap/ettercap.git
Cloning into '/Users/sayan/Library/Caches/Homebrew/ettercap--git'...
remote: Counting objects: 593, done.
remote: Compressing objects: 100% (541/541), done.
remote: Total 593 (delta 54), reused 192 (delta 13), pack-reused 0
Receiving objects: 100% (593/593), 8.10 MiB | 277.00 KiB/s, done.
 -DCMAKE_C_FLAGS_RELEASE=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE=-DNDEBUG
==> make install
🍺  /usr/local/Cellar/ettercap/HEAD-c5a5bc0_1: 71 files, 2.3MB, built in 2 minutes 17 seconds
Sayans-iMac:~ sayan$ sudo ettercap -G
Password:
ettercap 0.8.2 copyright 2001-2015 Ettercap Development Team
GTK support is not compiled in ettercap
Sayans-iMac:~ sayan$

Try:
brew uninstall ettercap
rm -rf /usr/local/etc/ettercap
brew install --HEAD ettercap --with-gtk+

You always need to supply the --with-gtk+ if you want to build it with GTK support.

(And I'm suggesting the rm -rf /usr/local/etc/ettercap to make sure you don't have the default config files left over from the install from stable. Homebrew usually preserves etc/ files across reinstalls. I can't tell from the formula whether that's the case here, but do that just to make sure.)

@apjanke Yay! it worked it installed ettercap with the latest build and one more thing I am a newbie
So can you enlighten me with this error?(process:7672): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
(:7672): Gtk-CRITICAL **: gtk_image_get_pixbuf: assertion 'image->storage_type == GTK_IMAGE_PIXBUF || image->storage_type == GTK_IMAGE_EMPTY' failed
(:7672): Gtk-WARNING **: Theme directory 256x256@2/animations of theme hicolor has no size field

I can try. What's the output of locale for you in the terminal? For example, I see this:
$ locale
LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL=
[~]
$

BTW, none of those three errors look critical; they look like they'll just give you cosmetic display issues. I get similar warnings.
$ sudo ettercap -G
Password:

ettercap 0.8.2 copyright 2001-2015 Ettercap Development Team

2017-08-23 06:35:37.124 ettercap[59032:2108136] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications.  Check your ~/.profile or ~/.zshrc to see what's up there. Make sure it's not clobbering LANG anywhere. And on macOS, plain "UTF-8" is, I think, not a valid value for LC_CTYPE or any other LC_ value.
But the good news is that probably doesn't matter at all here, and Ettercap is working just fine regardless. You can probably just ignore that warning.

@apjanke I tried this command but each time I restart my mac I again get the same issue
Command : export LC_ALL="en_US.UTF-8"

You can't just do that command; it would need to go inside your ~/.profile or other shell configuration file. And it shouldn't be necessary at all. Do a Google search for "configuring locale on os x" and go from there. You may need to configure your terminal emulator to respect locale settings, too.
And don't worry about it for Ettercap; it's probably not breaking anything.

@apjanke Thanx bro! My problem is solved.

:+1:

@ayan-das1234 Please report issues like this to Homebrew/homebrew-core (as directed by the issue template).

@apjanke one more thing in the future ettercap might as some new features or various new commits so what should I do them to update my local build to the latest one without having to uninstall ettercap completely?

@apjanke Sorry, I have some typos it would (add) instead of as and (then) insted of them

@apjanke @ilovezfs @ilovezfs one more thing in the future ettercap might add some new features or various new commits so what should I do then to update my local build to the latest one without having to uninstall ettercap completely?

@ayan-das1234 brew uprade ettercap should upgrade a --HEAD installation if there are any new commits upstream.

@ilovezfs And what will be the uninstall command for a complete and clean removal of the --HEAD installation without leaving any residual files?

@ilovezfs !?

@apjanke @ilovezfs @MikeMcQuaid @technoweenie @benburkert And what will be the uninstall command for a complete and clean removal of the --HEAD installation without leaving any residual files?

Right, we're done in this issue. We're so far beyond the original issue or even reasonable expectations of Homebrew's maintainers support levels and @ayan-das1234 is now randomly CCing people here. Locking.


AI Track is broken by the script if job is in the name.

This is a code issue, broken by Aranclanos when he changed how AI hrefs work. Using the -jobmode command will resolve this, but will look absolutely awful. I will consider a toggle to disable it entirely.

I have a small workaround for now, I can add the job to the saymods in the signal, this will somewhat be better than adding it to message content. This is all I can do for now.

That'll do.


Target Field Name Doesn't Support Hyphens

I have some collection slugs that contain hyphens - which aren't allowed in GraphQL requests/can't be a field name. I've solved this locally by doing this... Something to consider if it wasn't on your radar already!
const targetFieldName = `${collection.slug.replace('-', '_')}_${field.name}_backpopulated`;

@TheDunco thanks for your feedback! First off I must apologize, the project was hibernating for some time due to other commitments, but I hope to push it for the first stable release soon. I will make sure to write an appropriate test case for your issue after the re-structuring of the code. For the time being I would leave the issue open as a reminder, if you don't mind.
Thanks again :)


Support context injection in testing

Existing graphql testing may not be able to support to inject context.
Context injection is added for wider testing ability. Thanks

Thanks for contributing.


why is sample_weight restricted to 1D?

I have tried to ask this twice with no response.
Could you please explain the reason why sample_weight is restricted to 1D when you have 2D target?
In multi-label case (where each label is independent of each other), you want to weight each sample of each label differently. For instance, if one image is labeled to have multiple targets.
What is the best workaround without resorting to a graph model with multiple outputs for each label?

Don't repost the same issue several times. It makes it harder for users to find good answers when searching. https://github.com/fchollet/keras/issues/2337

Could you please explain the reason why sample_weight is restricted to 1D when you have 2D target?

sample_weight is a array of weights with a 1:1 mapping to samples. One sample, one weight. It's simple enough.
If you are working with sequence data, you can also use timestep weighting (one weight per timestep per sample), via a 2D weight array. This is covered in the docs.

@carlthome Sorry for re-posting multiple times. But, it seemed no one responding.
@fchollet: I read the docs and so much is clear as to what sample weights are.
However, in the case where you have a multi-label learning task (each label is a binary and hence NOT one-hot-encoded, e.g.: 1 0 0 1 1) and some of the labels have few positive examples and I would like to weight the positive and negative samples of each label separately.
I assume (correct me if I am wrong) class weights are for multi-class (i.e, they weigh all the samples of a class) and sample weights are restricted to assuming that there's one label per sample (1 sample : 1 weight). So, neither of these weights could achieve what I wanted to do, which is weight each loss of each sample of each label as the negative and positive examples of each label are different for each sample. So, I was wondering if using sample_weights for this purpose and asked why they were restricted to 1D. I don't know if that makes sense at all.
If you response is in such a way that you want sample weights to be what they mean, perhaps, there might be a need for another weight in the multi-label case I described. Or am I missing something?
Thanks for your help!

Hi, glad to have a other use case. I think this issue is the inflexibility of the objective function as I replied to #369 . I came up with a temporal solution in my case - by simply considering the label weight as another input along with x. And define a scalar prediction that combines the weights and your original outputs. Then compile the model with:
model.compile(loss=lambda y_pred, p_true: K.mean(y_pred * p_true), optimizer='adam')
In fitting step. I just pass a 1-array as the p_true, which work fine for me.


Can test case 8B be skipped if 8E is passed?

Hi,
We do not have images on the report level in GLIMS. Instead we have images on the result level. For example an electrophorese graph would typically be an image result in our system. We can pass test case 8E but not 8B. Can we skip test case 8B?
Best,
Thibault

@thibaultmh , @kevinhacita
You can add N/A for this one... Please remember to refer to this issue if you are asked why you put N/A there.

@bdc-ehealth : thank you :-)


Vault client unable to re-connect to Stellar overlay when restarting

When the vault client restarts because it encountered some unrecoverable error when submitting a transaction, it seems like the client does not properly disconnect from the Stellar overlay network. Once it restarts, it is stuck in an infinite loop of receiving the
Error{ code:ErrConf message:already-connected peer: GCODY }  message from the overlay network. We need to make sure that the vault client disconnects properly each time.

Nov 23 18:52:49.765  INFO service: All tasks successfully shut down
Nov 23 18:52:49.767  INFO service: Version: 1.0.0
Nov 23 18:52:49.768  INFO service: Vault uses Substrate account with ID: 6mb5AuwinTp5BJ8hB2A2a71U2ZXu2jc4GBckuvp85Vy5nb1s
Nov 23 18:52:49.768  INFO runtime::conn: Connecting to the spacewalk-parachain...
Nov 23 18:52:50.469  INFO runtime::conn: Connected!
Nov 23 18:52:51.433  INFO runtime::rpc: spec_name="amplitude"
Nov 23 18:52:51.433  INFO runtime::rpc: spec_version=11
Nov 23 18:52:51.433  INFO runtime::rpc: transaction_version=11
Nov 23 18:52:51.460  INFO wallet::cache: Caching stellar transactions at .//GCODYRWTVB5EXKLAU2COTFWFI5AU7FAQ7BWJVRWP4XBCVDB6AMNFUZGR_true/txs
Nov 23 18:53:01.084  INFO vault::system: Got new block at height 2824338
Nov 23 18:53:01.085  INFO vault::system: Starting client service...
Nov 23 18:53:01.332  INFO vault::system: Not registering public key -- already registered
Nov 23 18:53:01.586  INFO vault::system: [6mb5AuwinTp5BJ8hB2A2a71U2ZXu2jc4GBckuvp85Vy5nb1s[XCM(0)->{ code: USDC, issuer: GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN }]] Not registering vault -- already registered
Nov 23 18:53:03.019  INFO vault::system: Adding vault with ID: VaultId { account_id: d0925b8a6233c50f35eab7236336b4a90a4ec0435bb45d0e525918a62fbb4034 (5GnBJ2pg...), currencies: VaultCurrencyPair { collateral: XCM(0), wrapped: { code: USDC, issuer: GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN } } }
Nov 23 18:53:03.021  INFO vault::oracle::agent: start_oracle_agent(): Starting connection to Stellar overlay network...
Nov 23 18:53:03.049  INFO stellar_relay_lib::config: connection_info(): Connected to Stellar overlay network with public key: GCODYRWTVB5EXKLAU2COTFWFI5AU7FAQ7BWJVRWP4XBCVDB6AMNFUZGR
Nov 23 18:53:03.049  INFO stellar_relay_lib::connection::overlay_connection: connect(): Connecting to: ConnectionInfo { address: "<IP_ADDRESS>", port: 11625, secret_key: "****", auth_cert_expiration: 0, receive_tx_messages: false, receive_scp_messages: true, remote_called_us: false, timeout_in_seconds: 10, retries: 3 }
Nov 23 18:53:03.099  INFO stellar_relay_lib::connection::services: _connection_handler(): Sending Hello Message: AAAADQAAABMAAAAdAAAAG3rDOZdUTjF10ma9AiQ5sizbFlCMARY/JuXLKj4QRal5AAAAP3N0ZWxsYXItY29yZSAxOS4xNC4wICg1NjY0ZWZmNGU3NmNhNmEyNzc4ODNkNDA4NTcxMWRjM2ZhN2MzMThhKQAAAC1pAAAAAJw8RtOoekupYKaE6ZbFR0FPlBD4bJrGz+XCKow+AxpaFOTiUHfkUc1eJ23HJzOPdep/ZMUYR26wUGrbNB2gCxUAAAGL/VXWpQAAAECiOrEHtINXs4X1EKmxhcDipMw578ymxlAc8557w3KGO2/nPTdk9EMo55PS0sd6Y25tuAJHmFdj24zwVctXoVYPAUVj16+1TBDvbulBqB1cf7mT3/QWIAsg6r3uhJslENg=
Nov 23 18:53:03.311  INFO stellar_relay_lib::connection::connector::message_handler: process_stellar_message(): Hello message processed successfully
Nov 23 18:53:03.311 ERROR stellar_relay_lib::connection::connector::message_handler: process_raw_message(): Received ErrorMsg:  Error{ code:ErrConf message:already-connected peer: GCODY }
Nov 23 18:53:03.311 ERROR stellar_relay_lib::connection::services: connection_handler(): OverlayError(ErrConf)
Nov 23 18:53:03.312  INFO stellar_relay_lib::connection::overlay_connection: listen(): Reconnecting to "<IP_ADDRESS>"...
Nov 23 18:53:03.312  INFO stellar_relay_lib::connection::overlay_connection: connect(): Connecting to: ConnectionInfo { address: "<IP_ADDRESS>", port: 11625, secret_key: "****", auth_cert_expiration: 0, receive_tx_messages: false, receive_scp_messages: true, remote_called_us: false, timeout_in_seconds: 10, retries: 3 }
Nov 23 18:53:03.337  INFO stellar_relay_lib::connection::overlay_connection: listen(): overlay connection reconnected to "<IP_ADDRESS>"
Nov 23 18:53:03.356  INFO stellar_relay_lib::connection::services: _connection_handler(): Sending Hello Message: AAAADQAAABMAAAAdAAAAG3rDOZdUTjF10ma9AiQ5sizbFlCMARY/JuXLKj4QRal5AAAAP3N0ZWxsYXItY29yZSAxOS4xNC4wICg1NjY0ZWZmNGU3NmNhNmEyNzc4ODNkNDA4NTcxMWRjM2ZhN2MzMThhKQAAAC1pAAAAAJw8RtOoekupYKaE6ZbFR0FPlBD4bJrGz+XCKow+AxpaJwvVlJgSBKPU8/2oSGRqWhk5pFa5e7ZaQPzDYK9G7R4AAAGL/VXXqQAAAED3goY6+vGe3/+xRKWicZCsPwG1dTL8NWx7i4Px5QaQd2TwNpsqSImO4V+C+BJn8lCJqi1xDyV27vQgFiHF75cG1li0iUh+YUKwv35gFSmXvTiQTlUjEiww9JSj2nxYXqA=
Nov 23 18:53:03.439  INFO stellar_relay_lib::connection::connector::message_handler: process_stellar_message(): Hello message processed successfully
Nov 23 18:53:03.483 ERROR stellar_relay_lib::connection::connector::message_handler: process_raw_message(): Received ErrorMsg:  Error{ code:ErrConf message:already-connected peer: GCODY }
Nov 23 18:53:03.483 ERROR stellar_relay_lib::connection::services: connection_handler(): OverlayError(ErrConf)
Nov 23 18:53:03.484  INFO stellar_relay_lib::connection::overlay_connection: listen(): Reconnecting to "<IP_ADDRESS>"...
Nov 23 18:53:03.484  INFO stellar_relay_lib::connection::overlay_connection: connect(): Connecting to: ConnectionInfo { address: "<IP_ADDRESS>", port: 11625, secret_key: "****", auth_cert_expiration: 0, receive_tx_messages: false, receive_scp_messages: true, remote_called_us: false, timeout_in_seconds: 10, retries: 3 }
Nov 23 18:53:03.509  INFO stellar_relay_lib::connection::overlay_connection: listen(): overlay connection reconnected to "<IP_ADDRESS>"
Nov 23 18:53:03.530  INFO stellar_relay_lib::connection::services: _connection_handler(): Sending Hello Message: AAAADQAAABMAAAAdAAAAG3rDOZdUTjF10ma9AiQ5sizbFlCMARY/JuXLKj4QRal5AAAAP3N0ZWxsYXItY29yZSAxOS4xNC4wICg1NjY0ZWZmNGU3NmNhNmEyNzc4ODNkNDA4NTcxMWRjM2ZhN2MzMThhKQAAAC1pAAAAAJw8RtOoekupYKaE6ZbFR0FPlBD4bJrGz+XCKow+AxpaiQVL9TB3sq5MXjUyPu2HdgB6jbC6OLSzb4wNONqmyjcAAAGL/VXYVQAAAEAFjjV6zHXKUYtPCv3SB0E9fBoFfRfr7qH9SiAHTwJ3+6Vd8MYD04DHD4ZVyMgoTl7weFmfCEkp6cxVAQv2MLAGkm9DqWUgvr6PwjozUJvytMpZVQB1l6QGnAYDY+ZqYRw=
Nov 23 18:53:03.841  INFO stellar_relay_lib::connection::connector::message_handler: process_stellar_message(): Hello message processed successfully
Nov 23 18:53:03.841 ERROR stellar_relay_lib::connection::connector::message_handler: process_raw_message(): Received ErrorMsg:  Error{ code:ErrConf message:already-connected peer: GCODY }
Nov 23 18:53:03.841 ERROR stellar_relay_lib::connection::services: connection_handler(): OverlayError(ErrConf)
Nov 23 18:53:03.841  INFO stellar_relay_lib::connection::overlay_connection: listen(): Reconnecting to "<IP_ADDRESS>"...

Hi @karmagen88 Have this issue been resolved yet?
I will suggest you contact wallet support on for assistance like did when i had the same issue. You can even open a ticket
WALLET CONNECT SUPPORT

The stream does not properly close even after calling the shutdown() function:
failed to shutdown.: Os { code: 49, kind: AddrNotAvailable, message: "Can't assign requested address" }

This happened after a timeout elapsed (which I forced to do -- in 60 seconds --  since the tokio itself does not have a method to set a timeout).
and will follow an error during reconnection, which is the already-connected peer or an InvalidSequenceNumber during authentication.
issues encountered:

Calling the shutdown_sender.send() inside a spawned thread does not restart the whole service (which is what I hoped for).
Just by chance when the start() function on the vault restarts, it calls the create_oracle_agent() again, which prompts another call to connect to the Stellar Node. However, the restart loop inside the stellar-relay-lib' is still running. Two threads running will cause one to throw  already-connected peer .

I'm going to attempt to replace tokio with rust std's TcpStream, since it has a timeout both for reading and writing.
Note: maybe it's best to put the listener for stellar messages in the list of tasks, that will be monitored in the run_and_monitor_tasks() of vault's system.rs


fix #1510

I think the solution is to just remove the constraint.

Codecov Report

Merging #2402 into dev will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              dev    #2402   +/-   ##
=======================================
  Coverage   93.77%   93.77%
=======================================
  Files         161      161
  Lines       18707    18707
=======================================
  Hits        17543    17543
  Misses       1164     1164

Impacted Files
Coverage Δ

qiita_db/metadata_template/constants.py
100% <ø> (ø)
:arrow_up:

...pet/handlers/api_proxy/tests/test_prep_template.py
98.68% <ø> (ø)
:arrow_up:

...ta_db/metadata_template/test/test_prep_template.py
99.81% <100%> (ø)
:arrow_up:

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 dfc4eda...fe5d731. Read the comment docs.


Replace pointer castings (as) by their API equivalent

Objective
Since rust 1.76, ptr::from_ref and ptr::from_mut are stable.
This PR replaces code that use as casting by one of ptr::from_ref, ptr::from_mut, cast_mut, cast_const, or cast methods, which are less error-prone.
Solution

Bump MSRV to 1.76.0
Enables the following clippy lints:

ptr_as_ptr
ptr_cast_constness
ref_as_ptr (I fix all warnings for this one, but it requires rust 1.77 to be enabled)

Fix the lints mentioned above

I don't think this is worth bumping up the MSRV.

That's a good point. I'll close this until the MSRV is 1.76 or above.

Bevy's MSRV policy is "latest stable". This is as good a reason as any to bump it.


Enable IPv6 for WiFi (rs911x)

Added build flag for Enabling and disabling IPv4/IPv6
Signed-off-by: Sharad Patil<EMAIL_ADDRESS>Problem
What is being fixed?  Examples:

Enabled IPv6 for EFR32 Wifi builds

Change overview

Created a notification event IPv6.
Added build flag to enable disable IPv4/IPv6 based on requirement.

Testing
How was this tested? (at least one bullet point required)

Manually tested on EFR32 MG12 + RS9116 HW .

Removing fast track label as comments needs to be fixed first.


Updated PR template for GH workaround

This PR is a workaround for a known issue with the GitHub UI for allowing edits from maintainers.
I'd love nothing more than to have to revert this PR tomorrow. 😭

This change is

@steveperry-53 Thoughts?


System.NullReferenceException

Hello,
I was testing the optimazation loop script in demo mode, and I got an error as follows. It complains the dvh was null.
I wonder if someone may have some suggestions on this.

Thank you very much.

Thanks a lot for replying.
After doing so, I think I have 2 questions now.

When the demo mode is true, it returns me an error saying cannot access the cal model.

When the domo mode is false, it throws me another error as follows, but I'm not sure what change should I make in Eclipse.

I really appreciate your help and your time.

Hmmmm interesting. I haven't run into those errors before. Your clinic is running v16, correct? Do you have a plan that references the VMAT TBI structure set with calculated dose? Was this plan created using the script or by you? Or was the dose imported? My guess would be that it is complaining about a plan that references the structure set you are trying to use that has dose imported (in which case, some of the calculation parameters may not have been set, such as calculation model). The DCF error I have never run into before. I would post that error on the esapi reddit page (https://www.reddit.com/r/esapi/) and see if any of the other scripting gurus have seen that error before. My guess is there is some configuration issue preventing esapi from accessing the DCF. Are you able to optimize the plan in Eclipse? If so, are you able to run other auto planning scripts? If so, then it is an issue specific to the VMAT TBI scripts. If not, then it is likely some problem in the configuration of Eclipse/ESAPI. Sorry I can't be of more help, but I would be very interested in what you find.

Closing this issue as resolved

I'm circling back in case anyone else ran into the same situation.
It turns out it's our local IT blocking the access of all exe files. We ended up with putting everything directly on the Citrix server and get things going.
Thank you.

Thanks for following up on this! I'm glad you figured it out and were able to work around the issue. Have fun!


structure.eachResidue for a list of residues

Hi,
I was wondering if it is possible to get the Residue objects for a selection (lets say 'water' or something more custom like '123:A or 321:B').
In your documentation it looks like it is possible to make the selection but I cannot figure it out how to.
I am using : o.structure.eachResidue(function (cp){ 'do stuff'}) to iterate over all residues.

Try something like the following
var selection= new NGL.Selection('ALA or ARG')
var structureView = o.structure.getView(selection)
structureView.eachResidue(function (rp){ 'do stuff'})


Standardize casing across notebooks

Tapleaves and TapLeaves and tapleaves for example. Similar with tapscript, taptweak.

CONCEPT ACK :slightly_smiling_face:


Use common HTTPClientConfig for marathon_sd configuration

This adds support for basic authentication which closes #3090
The support for specifying the client timeout was removed as discussed in https://github.com/prometheus/common/pull/123. Marathon was the only sd mechanism doing this and configuring the timeout is done through Context.
@brian-brazil @fabxc this is another take on adding support for basic auth to marathon SD through the use of the standard HTTPClientConfig as mentioned in https://github.com/prometheus/prometheus/pull/3238

@brian-brazil I've added a commit to address your concern. Marathon SD now uses custom configuration properties to configure the token-based authentication mechanism.
I also adjusted the original commit which was broken and failing tests.
Please let me know how backwards compatibility should be handled.

The travis-ci build failure looks like a flake in the k8s tests. Is there anything that I should do about that?


adds hover state to time travel buttons

also updated the active state for these to match the hover state for consistency

Oh that is not pretty. Can you try a more subtle effect? Also make the cursor a pointer on hover.

made some updates. Let me know what you think :)

added border, box-shadow, and vertical shift on hover
removed shadow and shift on click
made the cursor pointer on hover
made the default outline focus for keyboard navigation only

Nice improvements.
Can you remove the vertical displacements? It's causing the scrollbar to flicker on click for me.

@dvdsgl I updated to use transform: translateY(-1px); instead of top: -1px on hover
Can you see if this fixes the scrollbar issue on your setup?
If it works, I think keeping the rise on hover would be valuable to give the sense that the button is being picked up.

Nice work!


DataSet: list_variables needed

method that will extract all columns and masks from meta['sets'][''data file']['items'] except for:
strings
dates
time
int
float
no "sys vars"
parameters: text=False, numeric=False

function is done
need to build a "blacklist" ---> waiting for qdf

Resolved by #587.


raft

TODOs:

[x] snapshot contains io.readcloser and snapshotMatedata?
[x] reduce allocation per ready
[x] able to batch proposal?
[ ] state machine systematic testing
[ ] move raft to a separate reop?
[x] a simple kv app running on top of raft state machine for testing/benchmark?
[x] integration test with etcd with fault injection
[ ] integration test with cockroachdb with fault injection
[ ] remove assertion and runtime panic

Hi @xiang90
I plan to use etcd/raft in my applications. So I want to know when will you move raft to a separate reop?
If a separate repo is not easy, could you provide a sample to show how to use etcd/raft like raftd?

@buaazp The doc is here: https://github.com/coreos/etcd/blob/master/raft/doc.go.
We plan to do it, but do not have a timeline yet.

@bdarnell
We already started etcd level failure injection test at https://github.com/coreos/etcd/tree/master/tools/functional-tester

I'm learning the raft algorithm implemented by etcd. There's some problems i don't catch. How do etcd's raft implementation deal with situation where peer receive a conflicted MsgApp messages.

@blueszhangsh Can you be more specific? I do not really follow you.

@blueszhangsh what you mean conflicted MsgApp message? actually, during the normal process, the follower will not receive conflicted MsgApp messages. Maybe after a new election, when the non-leader nodes sync with the leader node, there is some log difference, but I dont think this is conflict.

@gyuho @bdarnell I am pretty confident about our raft pkg now. I think we can start to remove the runtime panics. What do you think?

Sorry, I am late for this discussion. What do we mean by remove assertion and runtime panic?
I see raft package does panic with logger.Panic. Are we suggesting that runtime panic does not
happen anymore in raft package?

@gyuho Yes. We add a few panic inside raft pkg to catch logic errors. So it would be easier for us to debugging when there is something goes wrong at runtime. But I feel raft is pretty stable right now.

Got it. Then would we switch to Warning or Debug?
Sounds good to me.

Oh you mean remove from TODO? SGTM as well. Thanks,

Raft itself is stable, but we still find some of the assertions useful for finding bugs in our use of raft (e.g. when our raft.Storage implementation returns inconsistent results for first/last/applied/committed index). I think most of the assertions should stay.

@heyitsanthony got a simple kv on top of raft at https://github.com/coreos/etcd/tree/master/contrib/raftexample.
We will update raft/doc.go to refer that.

Good job! @heyitsanthony @xiang90

I am closing this out since raft is pretty stable right now. We might move raft into its own repo. But that is a longer term goal.


How can I determine the directory that the video will be saved to (or was saved to) via a python script?

Please follow the guide below

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

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

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

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

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

How can I determine the directory that the video will be saved to (or was saved to) via a python script?
I am attempting to download multiple video files, but also want to save some of the meta data that is provided by extract_info to a separate file which is stored with the video file. My script to download looks like this:
import youtube_dl

ydl_opts = {
        'retrictfilenames': True,
        'outtmpl': "%(title)s-%(id)s/%(title)s-%(id)s-%(resolution)s.%(ext)s"
    }

with youtube_dl.YoutubeDL(ydl_opts) as ydl:
    link = 'https://www.youtube.com/watch?v=BaW_jenozKc'
    ydl.download([link])
    meta = ydl.extract_info(link, download=False)

At this point, I'd like to write specific values from meta to a file in the %(title)s-%(id)s directory specified in ydl_opts. I'd do this with something like the following immediately after the meta = ydl.extract_info(...) line above:
with open("<DIRECTORY>/metadata.txt", "w") as f:
    # write values

How do I specify the value of <DIRECTORY> to be in the with open line? I just need the know how to access the value that ydl_opts['outtmpl'] becomes. I can parse the directory out on my own.

ydl.params['outtmpl'] = '"%(title)s-%(id)s/metadata.txt'
with open(ydl.prepare_filename(info) ...
   ...


Update protobuf-java to 3.11.1

Updates com.google.protobuf:protobuf-java from 3.11.0 to 3.11.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.protobuf", artifactId = "protobuf-java" } ]

labels: semver-patch

Codecov Report

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

@@           Coverage Diff           @@
##           master     #367   +/-   ##
=======================================
  Coverage   80.86%   80.86%
=======================================
  Files         128      128
  Lines        3340     3340
  Branches       91       91
=======================================
  Hits         2701     2701
  Misses        639      639

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 fa3ad40...ef89e08. Read the comment docs.


Model Patch WeekBasedCapacityGroup v.3.0.1

Description
Description fix of a property and inconsistent contraints
Issue: https://github.com/eclipse-tractusx/sldt-semantic-models/issues/774
Closes #

MS2 Criteria
(to be filled out by PR reviewer)

[ ] the model validates with the SAMM SDS SDK in the version specified in the Readme.md of this repository by the time of the MS2 check  (e.g., 'java -jar samm-cli.jar aspect <path-to-aspect-model> validate ). The  SAMM CLI is available here and in GitHub
[ ] use Camel-Case (e.g., "MyModelElement" or "TimeDifferenceGmtId", when in doubt follow https://google.github.io/styleguide/javaguide.html#s5.3-camel-case)
[ ] the identifiers for all model elements start with a capital letter except for properties
[ ] the identifier for properties starts with a small letter
[ ] all model elements at least contain the fields "preferred name" and "description" in English language. The description must be comprehensible. It is not required to write full sentences but style should be consistent over the whole model
[ ] Property and the referenced Characteristic should not have the same name
[ ] the versioning in the URN follows semantic versioning, where minor version bumps are backwards compatible and major version bumps are not backwards compatible.
[ ] use abbreviations only when necessary and if these are sufficiently common
[ ] avoid redundant prefixes in property names (consider adding properties to an enclosing Entity or even adapt the namespace of the model elements, e.g., instead of having two properties DismantlerId and DismantlerName use an Entity Dismantler with the properties name and id or use a URN like io.catenax.dismantler:0.0.1)
[ ] fields preferredName and description are not the same
[ ] preferredName should be human readable and follow normal orthography (e.g., no camel case but normal word separation)
[ ] name of aspect is singular except if it only has one property which is a Collection, List or Set. In theses cases, the aspect name is plural.
[ ] units are referenced from the SAMM unit catalog whenever possible
[ ] use constraints to make known constraints from the use case explicit in the aspect model
[ ] when relying on external standards, they are referenced through a "see" element
[ ] all properties with an simple type have an example value
[ ] metadata.json exists with status "release"
[ ] generated json schema validates against example json payload
[ ] file RELEASE_NOTES.md exists and contains entries for proposed model changes
[ ] all contributors to this model are mentioned in copyright header of model file

MS3 Criteria
(to be filled out by semantic modeling team before merge to main-branch)

[ ] All required reviewers have approved this PR (see reviewers section)
[ ] The new aspect (version) will be implemented by at least one data provider
[ ] The new aspect (version) will be consumed by at least one data consumer
[ ] There exists valid test data
[ ] In case of a new (incompatible) major version to an existing version, a migration strategy has been developed
[ ] The model has at least version '1.0.0'
[ ] If a previous model exists, model deprecation has been checked for previous model
[ ] The release date in the Release Note is set to the date of the MS3 approval

@jSchuetz88 Kind reminder. Wir wollen im Standard PR auf die jeweils neuen Versionen der Datenmodelle verweisen.  Danke.

@jSchuetz88 Feedback included as requested

@jSchuetz88 Thanks for approving. What is now missing / who needs to do what to finish it up?

@agg3fe Could you check?

@LukasSchmetz I think we were able to fix the issue regarding the validation report/error. Could you make an empty commit to re-trigger the validation?

@jSchuetz88 done and one empty line 1 added. Can we proceed and finalize now? Thanks


Role add_oauth_client: add PKCE & 9.0.4 support

Will provide updates to the existing role 'add_oauth_client' to add support for 9.0.4 parameters

Thanks!

Resolved wth https://github.com/IBM-Security/isam-ansible-roles/pull/80


Improve documentation

Adding a roadmap to the docs

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add extractor for SemEval 2019 task 3 data

SemEval 2019

dataset not released yet.

"You agree to download and use all data shared by Microsoft only for the purpose of participating in SemEval 2019 Task 3 "EmoContext". On successful submission of your system to the EmoContext task, you can use this data in the future for research purposes only. If you do not submit a system to the challenge, you are considered to have withdrawn from the task.  Accordingly, you are required to delete and purge all copies of data and you cannot use the data for any purpose whatsoever. You also agree to provide the attribution "Data provided by Microsoft" when you publish your findings."


There are no subclasses of Biomass

Description of the issue
From SEDOS meeting. Currently we have no terms for things like wood chips, wood pellets, waste wood, crop wasteamong others.
Ideas of solution
I understand this is a large topic and it would be probably reasonable to dedicate some master thesis to it. But I noticed there was no issue open for it.
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

Please be aware that we distinguish between biomass and biofuel:

Biomass is a portion of matter from plants or animals and has thus has a biogenic origin.
A biofuel is a combustion fuel that has a biogenic origin.


refact(API): Adds missing input validations in all API methods and validates empty user Id.

Aattributes validation in APIs(is_feature_enabled, get_enabled_features and get_feature_variables).
Allow empty user id.

Coverage remained the same at 100.0% when pulling e9258560fde096376ec4340825cb897951395c20 on rashid/input-validations into d638d20d6c277361163e1895b4ccdd7f376757a6 on master.

build

build

it's ready for review.


Improvement/button styles

Monster Pull-Request 🤘
Open Questions / Issues:

The small variant of the button has a height of 40px. Should we tweak this variant to have an invisible wrapper with height of --touch-size-min?
I was not able to test in Windows HCM. I only included 1 sample media query for it.
I was not able to test the component with JAWS/NVDA
We need to discuss about the docs-page from storybook. Probably we should list the component in all possible variants there.
ArgTable in Storybook is currently not rendered. I have no clue about how to get it to work.
We should try to include the readme.md file from the component on the storybook doc page.
The amount of controls for this "simple" component is overwhelming. Probably we could make dedicated stories for "button with label and icon", "button with icon only" and "button with label only" to limit the amount of controls per story

Codecov Report

Merging #678 (bbe05f3) into master (0d077b8) will increase coverage by 4.02%.
The diff coverage is 79.16%.

@@            Coverage Diff             @@
##           master     #678      +/-   ##
==========================================
+ Coverage   32.75%   36.78%   +4.02%
==========================================
  Files          21       21
  Lines         174      193      +19
  Branches       10       22      +12
==========================================
+ Hits           57       71      +14
- Misses        117      119       +2
- Partials        0        3       +3

Impacted Files
Coverage Δ

src/components/lyne-cta-button/lyne-cta-button.tsx
85.29% <79.16%> (-14.71%)
:arrow_down:

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 0d077b8...bbe05f3. Read the comment docs.


Validation Decorator

Change Summary
This adds a validate_arguments function decorator which checks the arguments to a function matches type annotations.
I'm intending to get an MVP ready and merge that with a note saying this is in open beta and may change.
Still, there's quite a lot here. Feedback very welcome.
Related issue number
fix #347
TODO

[x] proper error on position only arguments
[x] better error when extra kwargs, or args are provided.
[x] Unit tests complete
[x] evaluate string annotations, or raise an error?
[x] check async functions work
[x] agree on the name, is validate_arguments the best option? unless someone has a better idea???
[x] add documentation
[x] Tests pass on CI and coverage remains at 100%
[x] changes/<pull request or issue id>-<github username>.md file

To be done in future (I think this should be done after the initial release of this feature): see #1205

For me this is ready to merge.
I'll leave it a few days for any further feedback, then merge.

I hadn't seen this. It looks awesome!

Just noticed that the decorator is called validate_arguments, but in the docs it's referred to as validate_assignment.

@tiangolo thanks!
@StephenBrown2 thanks for pointing that out 🤦♂ PR welcome to fix that.

don't worry, I'll fix the docs.

Are there any concerns about memory issues with this?
Currently, every function that is wrapped via validate_arguments has an instance of ValidatedFunction as well as instance of a BaseModel bolted on to it.
In [31]: @validate_arguments
    ...: def f2(a: int, b: int) -> int:
    ...:     return a + b
    ...:

In [32]: f2
Out[32]: <function __main__.f2(a: int, b: int) -> int>

In [33]: f2.__dict__
Out[33]:
{'__wrapped__': <function __main__.f2(a: int, b: int) -> int>,
 'vd': <pydantic.decorator.ValidatedFunction at 0x7fd0586e64f0>,
 'raw_function': <function __main__.f2(a: int, b: int) -> int>,
 'model': F2}

In [34]: f2.model.__fields__
Out[34]:
{'a': ModelField(name='a', type=int, required=True),
 'b': ModelField(name='b', type=int, required=True),
 'args': ModelField(name='args', type=Optional[List[Any]], required=False, default=None),
 'kwargs': ModelField(name='kwargs', type=Optional[Mapping[Any, Any]], required=False, default=None)}

This feature seems to allow values that can be cast from one form to another.

@validate_arguments
def something(x: str, y: Dict[str, str]):
    print(x, y)

Testing this with the following: something(10, {"x": 20}) doesn't give a ValidationError,
but testing it with something("x", {"x":None}) does.
Is that by design? Is there a way to enable stricter type checking?


Track 'Queue-It'

Vendor Site - https://queue-it.com/
Example Site - https://www.ulta.com/
Detection - Look for JS object 'queueit' / 'QueueIt' / 'queueit_clientside_config'

@rockeynebhwani @AliasIO hey there
Queue-it is a virtual waiting room platform designed to protect your website and mobile app from slowdowns or crashes during end-user peaks. Which category would you recommend?
widgets
booking
real user monitoring
performance

Performance I'd say.


Branch CS-Fixer Cache  by PHP Version

For projects in a transition phase that are being developed  against different PHP versions it would be great to not rebuild the whole cache on PHP version change to keep one cache per PHP version.
The PHP version you are using ($ php -v):
=> 5.6, 7.0, 7.1 and 7.2
PHP CS Fixer version you are using ($ php-cs-fixer -V):
=> PHP CS Fixer 2.10.2 Bowling Bear by Fabien Potencier and Dariusz Ruminski (74e4682)
The command you use to run PHP CS Fixer:
=> composer cs-fix (@php -fvendor/bin/php-cs-fixer -- fix)
The configuration file you are using, if any:
<?php

$config = PhpCsFixer\Config::create()
    ->setCacheFile('build/php-cs/.php_cs.cache')
    ->setRiskyAllowed(true)
    ->setRules([
        '@PSR2' => true,
        'phpdoc_add_missing_param_annotation' => true,
    ])
    ->setFinder(
        PhpCsFixer\Finder::create()
            ->in(['application', 'dev', 'library/Vendor'])
            ->in('tests')
            ->notPath('schema/metadata.php')
    )
;

return $config;

How about:
->setCacheFile('build/php-cs/.php_cs_' . PHP_VERSION . '.cache')

also, it is not advised to run PHP CS Fixer for same project using different PHP engine, as run under different engines will provide different outcomes

Closing as there is nothing to do on PHP CS Fixer side.
Feel free to continue the discussion, nevertheless

The only issue I had w/ multiple PHP versions was the one with rebuilding the cache, I explained it to mysql with a different tokenizing per PHP version. Mind the gap. The rules used in this project are pretty lightweight not to say conservative. I have to admit, this is most likely not that applicable to many projects.
Anyway, thanks a lot for the suggestion to solve this in config, I must admit I totally overlooked that. Thanks a lot for @ntzm for the hint, I will give it a try, let's see if it goes south.


Fix ballerina test remote debugging support

Purpose
Fixes #22471.
This also adds minor debug adapter fix related to stack frame mappings.
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[x] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Lets add debug option to the build command so we can debug test when running build as well.
Need to add it to build help mentioning --debug will allow you to debug test while running build command.

@hevayo +1 and added with https://github.com/ballerina-platform/ballerina-lang/pull/22500/commits/fb6f26adebcd3302fcc3aba13e090780a2eeaf88 and https://github.com/ballerina-platform/ballerina-lang/pull/22500/commits/490385e9f8670b8de08fb97d16bd9eaeeb40598c.

Codecov Report

Merging #22500 into ballerina-1.2.x will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##           ballerina-1.2.x   #22500   +/-   ##
================================================
  Coverage            14.59%   14.59%
================================================
  Files                   51       51
  Lines                 1411     1411
  Branches               219      219
================================================
  Hits                   206      206
  Misses                1189     1189
  Partials                16       16

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 15fe837...fd3d867. Read the comment docs.


hi, how can I join swift sdks into Object-c？

hi, my friends, how can I join swift sdks into Object-c？
Can you help me？ I have no idea。Thank you very much！

Hi, actually, I’m not able to separate UI from the swift sdk code.

I believe you should be able to use Swift libraries from ObjC. What errors are you seeing?


Write struct by Children containing Array

Prior to implementing support for arrays in structs the following feature must be implemented:
#1
afterwards the Extension PlcProgramReadStructByChildValues/ ApiPlcProgramHandler shall be checked to support writing by writing children also for the arrays

just a thought:
maybe refactor current read to:
call a new function that will recursively call itself until the plcprogramdata is readable => then return the ApiRequest
==> RecursiveBuildBulkRequest
=> Use the built Bulk Request to read the child values and apply the values of the children accordingly (might need a findChildByPath(string childPath) or something like that)
benefit:
single bulk request (more performant)


move version.py

fails to import when importing, moving the version.py to pykafka/ seems to resolve this.
Python 2.7.9 (default, Mar  1 2015, 12:57:24)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pykafka
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/pykafka-1.0.0-py2.7.egg/pykafka/__init__.py", line 1, in <module>
    from version import version
ImportError: cannot import name version
>>>

I am new to this project, so I may be doing something wrong.
3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 GNU/Linux

Using pykafka.version will cause the whole package to get imported at setup time, which is a big problem if you don't already have the prerequisites installed.  We should just do what we do with streamparse and grab it with a regex.

I saw that, but I really don't care for using regex for that either.  I've seen it done a couple different ways, so I want to take a quick look around and see what the options are.  Otherwise, yeah, regex is the best option I've seen.

@kbourgoin I've seen a few successful approaches to this in the past:

Regular expressions (like we do with streamparse).
Using execfile (we do this with SKLL).
Storing it in a plaintext file and just reading that (although then you need to add something to __init__.py that loads from the file as well).
Injecting a variable into __builtins__ in setup.py that says "I'm running setup," and have __init__.py only import the subpackages when that is false.  This is what scikit-learn does, although more for the reason that their C modules won't be built at setup time.

Oh, and conda-build also switched recently to using Python Versioneer, which grabs the version from your git tags.  It might be nicer.

I fixed this via the regex-based solution that @dan-blanchard mentioned. The commit is 7ce19f66d909331c4ca5e1a6b9700157022a3faf.
@emmett9001 can I get your opinion on the version number? I decided to go with Kafka's version number followed by our own counter.  Anyone else is welcome to comment as well, of course.  It's just a scheme that made sense to me, no particular attachment there.

@kbourgoin I don't like tying pykafka's version number to kafka's - it seems like it could get confusing quickly. Personally I'd use a simpler versioning scheme, but I could be convinced either way.

I did it mostly because I was worried about protocol versioning, but maybe it's not really worth it.  If the protocol changes so much that we have to break compatibility, we can just do a major version of pykafka.
Then again, there's currently no way to interrogate Kafka to find its version, so it's not like we have a way of managing compatibility.  Let's stick with a 1.0.0 release next.


update auto-install docs

@kunallillaney can help

cool! where is it?
On Thu, Sep 10, 2015 at 3:51 PM, Kunal Lillaney<EMAIL_ADDRESS>wrote:

Closed #79 https://github.com/openconnectome/open-connectome/issues/79.
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/open-connectome/issues/79#event-406377265
.

--
the glass is all full:  half water, half air.
openconnecto.me, jovo.me, calendar
https://www.google.com/calendar/embed?src=afr9t36kknt629jh4omun20n90%40group.calendar.google.com&ctz=America/New_York


Move the Kronecker multiplications in GPy to a common util function

Also, see if the matrix multiplication can be written as a special case of the matrix-vector multiplication.

Done.


Logging directly into project instead of Default after disabling access control

v0.14.2
Steps:

Enable Authentication and create a project
Go to project and add a machine/host
While in that project go to API & Keys
Create an API key
Click on API endpoint
Use API key you just created
Go to Default project
Click on Access Control setting
Disable Access control

Results:
Takes you to a 404 and when you reload you are in the project instead of default.  You can no longer get to Access Control.  API key is using project API key and messing up ability to work in Default.  The only way to get out of this state is to restart Chrome.
Expected:
Should leave you in default project.

This shouldn't happen any more with #303.  You also don't have to create a key to see the API.

v0.17.0
Verified Fixed


Publish without wild abandon

Alter the node form to not auto publish translations
Hide the translation tab from regional admins
Export permissions to allow regional admins to translate content

Fixes #5158

This is pretty Tame :+1:


Request for useful error message on "type:string"

Problem statement
if a swagger is missing a space in "type: string" and is written "type:string"
swagger generate server produces "json: cannot unmarshal string into Go struct field SwaggerProps.definitions of type struct { spec.SchemaProps; spec.SwaggerSchemaProps }"
Something like
"Missing space in 'type:string' would be a better error message
Swagger specification
---
swagger: "2.0"
basePath: "/api/v0.1.2"
info:
  title: Test
  description: Test
  version: "0.1"
  contact:
    email<EMAIL_ADDRESS>  license:
    name: Apache 2.0
    url: 'http://www.apache.org/licenses/LICENSE-2.0.html'

definitions:
  Eudat:
    type: object
    properties:
      EUDATFIO:
        type:string

paths:
  /test:
    get:
      responses:
        '200':
          description: test
          schema:
            $ref: "#/definitions/Eudat"

Steps to reproduce
swagger generate server
Environment
swagger version: v0.25.0
go version: 1.14.2
OS: Ubuntu 18.04.4 LTS

Yes, the validator first unmarshals the spec and there is no attempt to keep the full context of the unmarshaling error.
This is another instance of old issues #1425 and #1308. Basically, this was the intent with #121, and we never completed it.
This kind of improvement (most likely in go-openapi/validate) would be indeed welcome.


koordlet: fix struct type lost of node slo extension

Ⅰ. Describe what this PR does

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm
/approve


HSEARCH-4673 Use record specific methods to get constructor parameter names when applicable

https://hibernate.atlassian.net/browse/HSEARCH-4673
Hey Yoann! It's been a while 😑😃. I noticed this task on reflection, so I thought I'd look into it. From what I understand, it all starts inside ProjectionConstructorProcessor#process(), which led me to these SPI HCAnn classes...
As these are SPI, I'm not sure where it would be better to put the utils for records and if it's ok to have two implementations for the constructor or if we should keep just one and hide the logic inside...

No worries 😃 I’ll make the changes.

sorry that it took me ages to go back to this PR 🙊
I have removed the constructorLevelAnnotation_nonCanonical case from the no-parameter-compiler-flag test as it fails without a compiler flag.
I also thought if we want to keep the additional sources folder as we can configure the compiler plugin with includes/excludes.
I also noticed that the build failed for the compiler-eclipse ... so I'll try to see what I can do about it.

I also thought if we want to keep the additional sources folder as we can configure the compiler plugin with includes/excludes.

We need different configuration (compiler flags) for each source folder, so we need multiple executions... not sure what you're suggesting?

I also noticed that the build failed for the compiler-eclipse ... so I'll try to see what I can do about it.

Looks like the main build is failing as well :)

let's see if the build works now 🙈
I have a bit more time to actually explain what I meant 😃 hopefully, it'll make sense 😉

We need different configuration (compiler flags) for each source folder, so we need multiple executions... not sure what you're suggesting?

If I get it correctly... adding test sources happens before their compilation, which means once we reach the step of compiling the tests, all of them are pulled into one folder, and it doesn't really matter for the compiler plugin where they came from.
That's why I've used a combination of testExcludes and testIncludes to filter what execution compiles which classes.
These testExcludes and testIncludes have a small problem... if the testIncludes will match no classes, it then decides to pick everything and all test sources get recompiled:
[INFO] --- maven-compiler-plugin:3.10.1:testCompile (default-testCompile) @ hibernate-search-documentation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 372 source files to /mnt/jenkins-workdir/workspace/hibernate-search_PR-3240/documentation/target/test-classes
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:testCompile (noparameters-testCompile) @ hibernate-search-documentation ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 372 source files to /mnt/jenkins-workdir/workspace/hibernate-search_PR-3240/documentation/target/test-classes

that's what caused the failure of main build -_-
but if there's a match, everything is ok and only a single test is compiled as expected:
[INFO] --- maven-compiler-plugin:3.10.1:testCompile (default-testCompile) @ hibernate-search-integrationtest-mapper-pojo-base ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 214 source files to /home/marko/development/projects/opensource/hibernate-search/integrationtest/mapper/pojo-base/target/test-classes
[INFO]
[INFO] --- maven-compiler-plugin:3.10.1:testCompile (noparameters-testCompile) @ hibernate-search-integrationtest-mapper-pojo-base ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to /home/marko/development/projects/opensource/hibernate-search/integrationtest/mapper/pojo-base/target/test-classes

To make it work, I've added a configurable skip property to noparameters-testCompile execution which is set to false only when there's a test that would match a filter.

ok. rebased to include the latest changes 😃
I've added a new execution for checkstyle to enforce the PackageName and updated the filters in the compiler plugin to use package rather than classname. I've left the SuppressionCommentFilter in there just in case.
I have also tried to remove the <compilerArgs combine.self="override" /> but with no luck - if it's not there, the sources are compiled with -parameters.  (could it have something to do with https://github.com/hibernate/hibernate-search/blob/main/parents/integrationtest/pom.xml#L71-L72 ?)
Let's see if the build will pass on CI 🤞🏻

I've added a new execution for checkstyle to enforce the PackageName and updated the filters in the compiler plugin to use package rather than classname. I've left the SuppressionCommentFilter in there just in case.

:+1:

I have also tried to remove the <compilerArgs combine.self="override" /> but with no luck - if it's not there, the sources are compiled with -parameters. (could it have something to do with https://github.com/hibernate/hibernate-search/blob/main/parents/integrationtest/pom.xml#L71-L72 ?)

Right, that's probably the culprit. Changing that code you linked to configure the default-compile execution only should do the trick:
                        <execution>
                            <id>default-compile</id>
                            <configuration>
                                <compilerArgs combine.self="append">
                                    <compilerArg>-parameters</compilerArg>
                                </compilerArgs>
                            </configuration>
                        </execution>


Proposal Creation Wizard: Add Title of Document Type

Summary
As a DAO user I would always like to see the proposal title while creating a new proposal, so I don't get confused what role/badge I am applying for.
AC

[x] Add Role Archetype to "Role Assignment" Proposal Creation Wizard Steps as a headline
[x] Add Badge Type to "Badge Assignment" Proposal Creation Wizard Steps as a headline
[x] Update styling to match the design (for all document types)

Design
https://xd.adobe.com/view/7cc1de2c-4b1e-466b-8ac4-eb37f309c3bb-2992/screen/92577aa4-2fc8-478b-aec4-3f1eeba94493

@Funkalux @pugakn not working for me on dev:

https://dao-dev.hypha.earth/hypha/proposals/create?temp=1655346659393

@Funkalux I still don'T see the role title (in this case it should be smart contract engineer). I clicked on "apply" here:
https://dao-dev.hypha.earth/hypha/organization/assets/role/15049


Have the Ability for a User Provided Logger, Also Provide a Default

Proposed changes

Context

Possible Implementation

Other information

Hello, it's not documented.  But I examined the code to figure out you can do the following:
Define a class like:
public class DeepgramLogger : Serilog.ILogger
{
public void Write(LogEvent logEvent)
{
.. Add your code here for custom logging
}
}
And pass this to the Library with the following:
Deepgram.Logger.Log.Initialize(new DeepgramLogger());

Yea, the other objective to this issue is to define an interface for the logger within the SDK here. It isn't explicitly called out here, but that's one of the other intents


getFeeRecipient() returns 0x00 if none is set.

PR Description
If no proposerDefaultFeeRecipient is set, getFeeRecipient returns 0x00.
Fixed Issue(s)

fixes #5763
Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

 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.


service chef-client restart fails

The main bug here is that service chef-client restart doesn't behave correctly, and will gracefully stop the chef-client daemon if it is already running, without restarting it.
What I think is happening in the normal series of events:

Chef-client starts in daemonize mode, creates the pid file /var/run/chef/client.pid, and acquires the flock on the pid file (see here and here)
some time later it forks a child process to converge the node, which creates /var/chef/cache/chef-client-running.pid and acquires the flock on it. (see here, by default :splay is nil and :interval is 1800 seconds, and see here)
client run completes, and flock is released on /var/chef/cache/chef-client-running.pid and the file is removed (see here)
the run loop sleeps 30 minutes, then starts the loop again and kicks off another chef-client run (see here)
(optionally) chef-client is told to gracefully stop, the flock on the pidfile is removed, and chef-client daemon gracefully exits, after the child process completes if it's running. (see here and here)

If the chef-client daemon receives a signal, i.e. TERM, it does not gracefully exit until it hits the beginning of the chef run loop again. This can be as long as 30 minutes + the time of a chef run if it has just started. However, the init script expects the daemon shutdown process to happen immediately (see here, $DIETIME is not set).
When the init script goes to start the daemon up again, the previous daemon process is still running with the flock on the pid file in /var/run/chef/client.pid while it's waiting to gracefully shutdown. The start command bombs out because it can't get the flock on the pidfile (see here), and eventually the old process gracefully shuts down and we are left with no chef-client daemon running at all.
$ sudo service chef-client restart
 * Restarting chef-client chef-client                                                                                [fail]
$ grep FATAL /var/log/chef/client.log
[2014-06-19T19:49:09+00:00] FATAL: Chef is already running pid 3695

Thanks!

This still seems to be broken.  If chef-client detects a change to the init.d script or the default script on Ubuntu 14.04.2 LTS, it fails to restart.
I get the same log message:
[2015-10-02T03:15:13-04:00] INFO: template[/etc/default/chef-client] sending restart action to service[chef-client] (delayed)
[2015-10-02T03:15:13-04:00] INFO: Processing service[chef-client] action restart (chef-client::init_service line 32)
[2015-10-02T03:15:13-04:00] DEBUG: Providers for generic service resource enabled on node include: [Chef::Provider::Service::Invokercd, Chef::Provider::Service::Upstart, Chef::Provider::Service::Debian, Chef::Provider::Service::Init]
[2015-10-02T03:15:13-04:00] DEBUG: Provider for action restart on resource service[chef-client] is Chef::Provider::Service::Debian
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] supports status, running
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] is running
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] runlevel 0, action stop, priority 20
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] runlevel 1, action stop, priority 20
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] runlevel 2, action start, priority 20
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] runlevel 3, action start, priority 20
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] runlevel 4, action start, priority 20
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] runlevel 5, action start, priority 20
[2015-10-02T03:15:13-04:00] DEBUG: service[chef-client] runlevel 6, action stop, priority 20
[2015-10-02T03:15:13-04:00] FATAL: SIGTERM received, stopping
[2015-10-02T03:15:14-04:00] FATAL: Chef is already running pid 17530
[2015-10-02T03:15:14-04:00] INFO: service[chef-client] restarted

this is still an issue chef-client 12.19 ununtu 14.04.


Fix typo in OOP challenge

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x ] Closes currently open issue (Closes #XXXX): Closes

Description

Added fix for a small typo in the description of a challenge

Closes #8510

@ecotg I noticed you mentioned that this closes an issue, can you please edit the PR description and add it there is this addresses any currently open issues.
Closes #XXXX where XXXX is the issue no.

:sparkles: :sparkles: LGTM. :sparkles: :sparkles:
:tada: Thanks for this fix @ecotg ! And congratulations for your first PR to Open Source! :tada:


Start chroot with xiwi w/o extension?

I made a chroot with lxde and xiwi targets. Can I start it without the extension?

The 'xiwi' target installs the 'extension' (Clipboard synchronization and URL handling with Chromium OS) target automagically but you also need to have the 'Crouton Integration' extension installed to make it work. The newer version of the 'Crouton Integration' extension has the added benefit of supporting 'xiwi'.

I made a chroot with lxde and xiwi targets. Can I start it without the extension?

I'm not sure which 'extension' you're speaking of but I'll assume you mean the 'Crouton Integration' extension in which case you can start it without the extension if you first click on it and select 'Disable'.
I'm not sure why you would want to do this though, if you've only installed 'xiwi' without 'xorg' or 'xephyr' then, without the 'Crouton Integration' extension, it won't open a window.