feat: Add OpenZiti to edgex-go

original pr here - closed mistakenly when trying to sync my main branch using github: https://github.com/edgexfoundry/edgex-go/pull/4755
This PR enables the core microservices to be built with support for OpenZiti. Without the individual changes to the files, after building docker images locally (make docker_base -> make docker) without the individual changes the ListenMode was never correctly discovered as 'zerotrust'
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.62%.  Consider uploading reports for the commit 302b7c9 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4777   +/-   ##
=======================================
  Coverage   41.62%   41.62%
=======================================
  Files         105      105
  Lines        9858     9858
=======================================
  Hits         4103     4103
  Misses       5402     5402
  Partials      353      353

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


6042 abort      python src/face_capture.py --emotion_name smile --number_of_images 100

When I run this program in my own laptop, here is a problem:
STEP 1 - generating the facial images, what I did is:

(facialemoji) (base) jishenshen@Jishenshens-MacBook-Pro facial_emotion_recognition__EMOJIFIER % python  src/face_capture.py --emotion_name smile --number_of_images 100

However, it returns:

[2020-03-11 22:38:32] [root] [INFO] (Loggers ready !)
[2020-03-11 22:38:32] [root] [DEBUG] (Emotion Map: {'smile': 0, 'kiss': 1, 'tease': 2, 'angry': 3, 'glass': 4, 'lol': 5})
[2020-03-11 22:38:32] [root] [INFO] (Loggers ready !)
[2020-03-11 22:38:32] [root] [DEBUG] (Emotion Map: {'smile': 0, 'kiss': 1, 'tease': 2, 'angry': 3, 'glass': 4, 'lol': 5})
[1]    6042 abort      python src/face_capture.py --emotion_name smile --number_of_images 100

Why this happens?
Many thanks!

Hi @Jishenshen, did you complete the step 0 mentioned in the readme file in this section?

closing due to inactivity, feel free to reopen if having issues.


support for perf-checks from different regions?

this could be one more metric in the analysis.

I'll consider your suggestion thank you very much


No autocompletion

Solution
As we are using clangd extension for vscode as a test client, the implement of client extension may alter our server's result.
The best way is create an extension for this server.
Also, we need to write test make sure everything is ok.

This bug is caused by client, close.


Added changeExt option to avoid changing file extension to .html

Added changeExt option to avoid changing file extension to .html (Advanced use cases) , changeExt defaults to true so normal cases will change ext to .html and for those who need can avoid changing extension

Nice! Could you please add a test and documentation in the readme for this?
I guess you can use the same logic as in the "should compile twig templates to html files" test but asset the file extension to be correct.


Change name to sphinx-tomyst

Change the package name from sphinxcontrib-tomyst to sphinx-tomyst

Closed by #74


GUI Corruption

Hi, Well something is not right with the GUI rendering

Environment:
Win 10 21H2
RTX 3080
Nvidia Driver Version: 511.79 DCH
Resolution: 2560*1080

Well, this is weird. I believe this is fault of java swing and/or FlatLaf. I don't think I have any way to fix this. Does this happen often? Is it fixed by closing and reopening it?

it happens always, but I found the culprit, it's the combination of GeForce experience overlay (Detects the app as a 3D game I guess) and windows dark mode, weirdly it's fine with windows light colors.
anyways it's not a big deal, thanks for replying.


Report the number of evaluated tests alongside with diagnostics

This is rebased and cleaned up of stale #75.
My motivation is simply to make it possible to use tsd with jest.
PS I couldn’t find a way to work directly on #75. New PR seemed to be the solution. If this is somehow non-nonethical or a bad practise, I am fine to close and to proceed in some other way.

Not good idea. It reports count of assertions, not count of tests (there are no tests in tsd).


Sagemaker Endpoint returning complete gibberish

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Windows
- Continue version:
- IDE version:
- Model: Sagemaker Endpoint(hosting Llama 3 8B)
- config.json:

{
  "allowAnonymousTelemetry": false,
  "models": [
    {
      "model":"anthropic.claude-3-5-sonnet-20241022-v2:0",
      "contextLength": 200000,
      "title": "Bedrock: Claude 3.5 Sonnet v2",
      "provider": "bedrock",
      "region": "us-west-2",
      "profile": "bedrock"
    },
    {
      "model": "anthropic.claude-3-haiku-20240307-v1:0",
      "contextLength": 200000,
      "title": "Bedrock: Claude 3 Haiku",
      "provider": "bedrock",
      "region": "us-west-2",
      "profile": "bedrock"
    },
    {
      "model": "amazon.titan-text-express-v1",
      "contextLength": 8000,
      "title": "Bedrock Govcloud: Titan Text Express",
      "provider": "bedrock",
      "region": "us-gov-west-1",
      "profile": "govcloud"
    },
    {
      "model": "meta.llama3-70b-instruct-v1:0",
      "contextLength": 120000,
      "title": "Bedrock Govcloud: Llama 3.0 70B Instruct",
      "provider": "bedrock",
      "region": "us-gov-west-1",
      "profile": "govcloud"
    },
    {
      "model": "anthropic.claude-3-5-sonnet-20240620-v1:0",
      "contextLength": 120000,
      "title": "Bedrock Govcloud: Claude 3.5 Sonnet",
      "provider": "bedrock",
      "region": "us-gov-west-1",
      "profile": "govcloud"
    },
    {
      "model": "AUTODETECT",
      "title": "LISA",
      "apiBase": "https://lisa.liumike.people.aws.dev/v2/serve",
      "completionOptions": {},
      "provider": "openai",
      "apiKey": "password",
      "contextLength": 28672
    },
    {
      "title": "Sagemaker-Llama2-small",
      "provider": "sagemaker",
      "model": "lmi-model-2024-12-04-18-50-43-773",
      "region": "us-west-2"
    },
   {
    "title": "Sagemaker-Llama-2-7b",
    "provider": "sagemaker",
    "model": "meta-llama-2-7b-l-20241204-162626",
    "region": "us-west-2"
  },
  {
  "title": "Sagemaker-Llama-3-8b",
  "provider": "sagemaker",
  "model": "jumpstart-dft-meta-textgeneration-l-20241204-152843",
  "region": "us-west-2"
  },
  ],
  "tabAutocompleteModel": {
    "title": "Starcoder2",
    "provider": "ollama",
    "model": "starcoder2",
    "apiBase": "http://internal-usw2-c-ollam-ZPZPsphJEnsG-1373085052.us-west-2.elb.amazonaws.com:11434"
  },
  "customCommands": [
    {
      "name": "test",
      "prompt": "{{{ input }}}\n\nWrite a comprehensive set of unit tests for the selected code. It should setup, run tests that check for correctness including important edge cases, and teardown. Ensure that the tests are complete and sophisticated. Give the tests just as chat output, don't edit any file.",
      "description": "Write unit tests for highlighted code"
    }
  ],
  "contextProviders": [
    {
      "name": "code",
      "params": {}
    },
    {
      "name": "docs",
      "params": {}
    },
    {
      "name": "diff",
      "params": {}
    },
    {
      "name": "terminal",
      "params": {}
    },
    {
      "name": "problems",
      "params": {}
    },
    {
      "name": "folder",
      "params": {}
    },
    {
      "name": "codebase",
      "params": {}
    }
  ],
  "slashCommands": [
    {
      "name": "edit",
      "description": "Edit selected code"
    },
    {
      "name": "comment",
      "description": "Write comments for the selected code"
    },
    {
      "name": "share",
      "description": "Export the current chat session to markdown"
    },
    {
      "name": "cmd",
      "description": "Generate a shell command"
    },
    {
      "name": "commit",
      "description": "Generate a git commit message"
    }
  ]
}

Description
I'm getting complete gibberish from my connection to sagemaker endpoint.

This only happens if I make the call through continue. Making the call through jupyter notebook gives me a normal response.
Here's the portion of my config file that has the endpoint model I'm testing.
{
"title": "Sagemaker-Llama-3-8b",
"provider": "sagemaker",
"model": "jumpstart-dft-meta-textgeneration-l-20241204-152843",
"region": "us-west-2"
},
To reproduce
make any input calls to sagemaker endpoint
Log output
no logs

@jeffchnn2001 is this model a fully trained-from-scratch kind of model or a fine tuned version of some open source model or what kind of output would you expect?

it's a fully trained from scratch kind of model. Deployed it through sagemaker jumpstart.

If you give the same input through CLI or other connection what result do you get?

I get a normal response when querying the endpoint from jupyter notebook.

@jeffchnn2001 I believe you could use the template  config here: https://docs.continue.dev/reference#models


Update to Godot 4.3 (TileMapLayer)

I know 4.3 isn't out yet but is there currently a way I can assign a TileMapLayer node to a generator rather than a Tilemap node? Couldn't find any info about this

That's coming as soon as 4.3 is released fully.

Thanks!
In the meantime, if anyone else looking for info land on this issue, I managed to get all demos* to work with a few changes to gaea/renderers/2D/tilemap_gaea_renderer.gd :
Changes the following lines  (currently 10, 39-40, 53, 64):
@export var tile_map: TileMap :
...
for l in range(tile_map.get_layers_count()):
	tile_map.call_thread_safe("erase_cell", l, Vector2i(x, y))
...
tile_info.tilemap_layer, tile, tile_info.source_id,
...
tile_info.tilemap_layer, terrains[tile_info],

To :
@export var tile_map: TileMapLayer :
...
#for l in range(tile_map.get_layers_count()):
	tile_map.call_thread_safe("erase_cell", Vector2i(x, y))
...
tile, tile_info.source_id,
...
terrains[tile_info],

*except for the wave_function_2D demo but even with a regular Tilemap I can't get it to work so it seems to be an issue with 4.3 and not TileMapLayer nodes


Target url never ends with a slash

i've tested the code manually, as i'm new to junit
if something goes wrong kindly ping me.
closes: #899

As mentioned inside #899 we no longer handle this at SecHub site but instead product specific.
But I will add my thoughts for future PRs.


Unable to add two PVA bot skills through bot framework composer with the option connect to a skill

Describe the bug

We are able to add a PVA bot skill in bot composer successfully. When we try add another PVA skill, the below error is thrown in bot composer.
"This operation cannot be completed. The skill is already part of the Bot Project"
Version

2.1.2
Browser

Chrome

[ ] Chrome

OS

macOS

[ ] macOS

To Reproduce
Steps to reproduce the behavior:

Go to 'Bot Framework Composer'
Click on 'Connect to a skill'
Select PVA bot manifest zip file
See error

Expected behavior

Screenshots

## Additional context

Hi @pckyn Apologies for the delay. I am investigating and will update with findings shortly.

I can confirm this behavior and reproduce. Not sure if it is expected or not.
@ceciliaavila Can you please comment or investigate further?

Hi @dmvtech, we'll add this one to our backlog, we should be tackling it next week.
Thanks!

@ceciliaavila - Thank you for the update!!
When would this fix be released? Any expected date? thanks

Hi @pckyn, I don't know the release date, maybe @tracyboehrer can help us with that.


All mass differences at -1, 0, 1

In the two-sample comparison, all mass differences seems to be collected at integer values -1, 0 and 1. Could a type error (int instead of float) have been introduced by accident?

This is fixed in the latest version.


Remove pod2daemon-flexvol and volume definition from canal manifest

What this PR does / why we need it:
This volume causes problems on CoreOS
Special notes for your reviewer:
https://github.com/projectcalico/calico/issues/2712
Does this PR introduce a user-facing change?:
removed flexvolume support from canal

/lgtm

/retest


URL encoding doesn't work with long URLs

For some reason, the URL RegEx is restricted to 512 characters, which causes issues when displaying long URLs.

Shouldn't it be 2048 characters?

Curious - are you logging URLs that big?
This was usually meant for terminals.

@m-murasovs - any comment?


Can jolokia agent filter the metrics

For security and performance( bandwidth) reasons, sometimes people may want to limit the metrics which can be list or read. I was wondering if jolokia can do it
Thanks in advance :)

Yes it can. https://jolokia.org/reference/html/security.html


count(s) and term_frequency(s)

Replace term frequency by Count and creates a new method term_frequency

@jbesomi  Can I have a review ?

@jbesomi Can I have a review ?

Seems like its failing the tests.sh. Have you downloaded the dev-dependencies and ran the tests.sh?
.....................................................................................................
======================================================================
FAIL: test_correct_index_26_term_frequency (tests.test_indexes.AbstractIndexTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/parameterized/parameterized.py", line 530, in standalone_func
    return func(*(a + p.args), **p.kwargs)
  File "/home/travis/build/jbesomi/texthero/tests/test_indexes.py", line 96, in test_correct_index
    self.assertTrue(result_s.index.equals(t_same_index.index))
AssertionError: False is not true
======================================================================
FAIL: test_incorrect_index_26_term_frequency (tests.test_indexes.AbstractIndexTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.6.7/lib/python3.6/site-packages/parameterized/parameterized.py", line 530, in standalone_func
    return func(*(a + p.args), **p.kwargs)
  File "/home/travis/build/jbesomi/texthero/tests/test_indexes.py", line 103, in test_incorrect_index
    self.assertFalse(result_s.index.equals(t_different_index.index))
AssertionError: True is not false
----------------------------------------------------------------------

Thank you, that looks a great start!
@henrifroese is working on #90, we should probably wait for his merge before we can continue with that. For a broader view, you can have a look there: #85
As you have some Javascript knowledge (and I assume also some web-development knowledge), would you be interested in helping out with #40 ? I can support you there. This is quite an interesting subject, as we will have to work with Sphinx, CSS, html and maybe even a bit of JS
Otherwise, if you are more interested in the software development, what about #65 ?

Hey @jbesomi Yes, I can work with both. Should I proceed with this PR?  I have to add just a couple of test cases to fix this.

For this PR, you will need to wait a bit. I'm making some important changes. I will let you know when is done (in an hour or so).
If you want to keep going in the meantime, may you have a look there and add ask for questions/add your opinion? #40

Hey @ishanarora04, you can keep working on it! For you to know, once you are finished, I will try to uniform all three functions so that they have all the same arguments (min_df, max_df and max_features). You probably will have to redo the work on the new version of the files, it might be just faster!

@jbesomi  Should term_frequency be part of test_indexes.py since we are generating a new series?

Hey!
Yes it should be. What do you mean by "since we are generating a mew series?"
Also, term_frequency is basically count normalized by the number of words in the document. You are doing something different right now... isn't?
term frequency formula

Hey, Can I have a review here ?

Hey @ishanarora04, thanks, amazing!
I'm out of town for the weekend, I will look into that tomorrow evening (ECT) or latest on Monday.
If you are interested in contributing more, this issue needs some help #65 👍
Thank you for your patience!

This is up for review ?

Hey @ishanarora04, thank you! 🎉
When reviewing, I noticed that the tokenize function was splitting by _ (underscore). This is clearly not what we expected. I just fixed this issue in 448d40f .
@henrifroese and @mk2510 recently made some big improvements to the documentation and the preprocessing file. You can see the main changes there: #107
If you are okay with that, I will first merge PR #107 and then will merge yours, that way we can reduce merging conflicts.
Review for now (for efficiency and to avoid do the work twice, you might want to wait that we merge #107 before doing any changes):

Congrats! That's super!
new count: you added two parameters (min_df and max_df) but you don't add and explain them in the docstring.
To return the features_names:s -- s after the semicolon

For involving you in the discussion:
Initially, preprocessing functions were receiving a Text Series and then scikit-learn default settings were used. scikit-learn by default lowercase and remove punctuation, that's why we added test such as *_punctuation_are_kept and *_not_lowercase. Now, tfidf and company receives as argument an already tokenized series. This means that unit-test are probably not strictly necessary anymore. It's up to you if you want to keep it, remove it or merge it in a single unit-test (👍 ). Independently of the decision you take, we will need to update the unit-tests in tfidf, count and term_frequency (on a separate PR)

Thanks for the review. Yes, we can wait for #107 to be merged. I will inculcate all suggestions

Incorporated the suggestions. Meanwhile, I can start working on #65

Top! 🎉
We will just wait for #107, check there are no conflicts, and finally merge! :)

Hey @ishanarora04. Thank you for your PR! Just merged 🎉 🎉

Thanks
On Wed, Jul 22, 2020 at 1:42 PM Jonathan Besomi<EMAIL_ADDRESS>wrote:

Hey @ishanarora04 https://github.com/ishanarora04. Thank you for your
PR! Just merged 🎉 🎉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jbesomi/texthero/pull/92#issuecomment-662311622, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWIJOEW5YRNOWECY6WY3FLR42NONANCNFSM4O2NCJ2A
.


Enhancing the card UI.

Is your feature request related to a problem? Please describe.
The UI of the card in the Gallery section can be customized.
Describe the solution you'd like
I would like to add separate boxes for the tags of "hot","featured","JPG,"JPEG" etc.
Describe alternatives you've considered
This will make the card look somewhat like the attached

screenshot.

I request you to assign me this issue.

@Vatsalmadhur sure go ahead, Make a pr with proper screenshot, also try to use row-gap in between lines.

Have a look at pr #61


Add task annotation to commits for published packages

This updates Porch to store the tasks for Package Revisions in commits for Published packages. Up until now, the tasks were not included in the commit generated as part of publishing a package.
This achieves this by adding the list of tasks to the commit annotation, so while it keeps the tasks, the changes caused by each task is no longer separated into separate commits. It also adds the revision of the package revision to the annotation, which allows us to only find the tasks that belong to a specific package revision. If we want to look at the tasks further back, those will be available by following the reference to the upstream package in the clone task.
This doesn't preserve the individual commits after approval, but I think we can address that separately.

🚢


Build IOS

Hi,
if I try download the packages on site:
nightlies.videolan.org/build/iOS/
after try extract the component in archive, I have a problem, the Mac no extract directory, but make an other archive, I try too with other software for archive, but the results are equal.
I have try open in windows and after send to Mac , but when I try open in Mac open alert archive damaged
can we help me?
and the libstdc++.6.0.9.tbd is deprecated, how resolve this ?

(1) you can use  dr.unarchiver
（2）remove   libstdc++.6.0.9.tbd
（3）Your Project   Build Settings --> Build Options --> Debug Information Format   set    DWARF.

i solved with extract archive with command line for the library I used libstdc++.
now I have new problem, can write here? or open new issue?

android  or  ios

android and ios.
for open wait 15sec
`
import React, {Component} from 'react';
import {Platform, StyleSheet, Text, View} from 'react-native';
import { VLCPlayer, VlCPlayerView, VlcSimplePlayer } from 'react-native-yz-vlcplayer';
import Orientation from 'react-native-orientation';
export default class App extends Component {
render() {
return (
     <VlCPlayerView
       style={{width:'100%',height: '100%'}}
       url={'rtsp://link cam here'}
       Orientation={Orientation.lockToLandscape()}
       autoplay={true}
       videoAspectRatio='16:9'
       setOption={"--no-audio"}
    setOption={"--rtsp-tcp"}
    setOption={"--network-caching=" + 150}
    setOption={"--rtsp-caching=" + 150}
    setOption={"--no-stats"}
    setOption={"--tcp-caching=" + 150}
    setOption={"--realrtsp-caching=" + 150}

       />
);

}
}
`

you  can  use  code like  it.
<VlcSimplePlayer
autoplay={true}
url='rtsp://<IP_ADDRESS>/vod/mp4://BigBuckBunny_175k.mov'
initType={2}
initOptions={[
"--no-audio",
"--rtsp-tcp",
"--network-caching=" + 150,
"--rtsp-caching=" + 150,
"--no-stats",
// setOption("--subsdec-encoding");
// setOption("--audio-time-stretch");
"--tcp-caching=" + 150,
"--realrtsp-caching=" + 150,
]}
/>

Yeah! it work! thank you so much!
i have 3 problems now, if I reload app in debug mode (IOS) the player no reload and in Xcode generate in libvlc_ArtRequest: ->  0x1006686f8 <+0>:  ldr    x0, [x0, #0x58] thread 1: EXC_BAD_ACCESS (code=1, address=0x1a246b90fe9).
and only if I click on display the video open in '16:9'.
and this:
Warning: option --rtsp-caching no longer exists.
Warning: option --tcp-caching no longer exists.
Warning: option --realrtsp-caching no longer exists.
Warning: option --rtsp-caching no longer exists.
Warning: option --tcp-caching no longer exists.
Warning: option --realrtsp-caching no longer exists.

1.I have  no  idea  to  solve it.
2.you can use ：
fullVideoAspectRatio={"16:9"}
videoAspectRatio={"16:9"}

maybe these option is  remove in this  version.

if I remove this option the player wait 15sec before load a video, with this option open immediately.

@IosSos I have the same Thread 1: EXC_BAD_ACCESS issue when set --rtsp-tcp option, did you find a solution for this ?


Install 0.36

Thanx for the excellent package. Somehow I cannot install 0.36 version. The 0.35 worked perfectly for me. According to the documentation there seems to some interesting new features in this new 0.36 version. I would definitely like to test them. After installation, I got the following error messages.  Attached, I print also my Python and OS versions.
import sys
import platform
print(sys.platform)
print(platform.version())
print(sys.version_info)
import shap
win32
10.0.19041
sys.version_info(major=3, minor=6, micro=10, releaselevel='final', serial=0)
ImportError Traceback (most recent call last) < ipython-input-1-1139cee11c9a> in < module>
4 print(platform.version())
5 print(sys.version_info)
----> 6 import shap
~\Anaconda3\lib\site-packages\shap_init_.py in < module>
10     warnings.warn("As of version 0.29.0 shap only supports Python 3 (not 2)!")
11
---> 12 from ._explanation import Explanation
13
14 # explainers
~\Anaconda3\lib\site-packages\shap_explanation.py in < module>
6 import warnings
7 import copy
----> 8 from slicer import Slicer, Alias
9 # from ._order import Order
10 from .utils._general import OpChain
ImportError: cannot import name 'Alias'
This is what happens, when I use 0.35 version, installed via conda i.e. all works. After conda install pip install does not allow me to upgrade shap.
import sys
import platform
print(sys.platform)
print(platform.version())
print(sys.version_info)
import shap
win32
10.0.19041
sys.version_info(major=3, minor=6, micro=10, releaselevel='final', serial=0)
print(shap.version)
0.35.0

This is what happens, when I use 0.35 version.
import sys
import platform
print(sys.platform)
print(platform.version())
print(sys.version_info)
import shap
win32
10.0.19041
sys.version_info(major=3, minor=6, micro=8, releaselevel='final', serial=0)
print(shap.version)
0.35.0

Thanx for the excellent package. Somehow I cannot install 0.36 version. The 0.35 worked perfectly for me. According to the documentation there seems to some interesting new features in this new 0.36 version. I would definitely like to test them. After installation, I got the following error messages. Attached, I print also my Python and OS versions.
import sys
import platform
print(sys.platform)
print(platform.version())
print(sys.version_info)
import shap
win32
10.0.19041
sys.version_info(major=3, minor=6, micro=10, releaselevel='final', serial=0)
ImportError Traceback (most recent call last) < ipython-input-1-1139cee11c9a> in < module>
4 print(platform.version())
5 print(sys.version_info)
----> 6 import shap
~\Anaconda3\lib\site-packages\shap__init__.py in < module>
10 warnings.warn("As of version 0.29.0 shap only supports Python 3 (not 2)!")
11
---> 12 from ._explanation import Explanation
13
14 # explainers
~\Anaconda3\lib\site-packages\shap_explanation.py in < module>
6 import warnings
7 import copy
----> 8 from slicer import Slicer, Alias
9 # from ._order import Order
10 from .utils._general import OpChain
ImportError: cannot import name 'Alias'
This is what happens, when I use 0.35 version, installed via conda i.e. all works. After conda install pip install does not allow me to upgrade shap.
import sys
import platform
print(sys.platform)
print(platform.version())
print(sys.version_info)
import shap
win32
10.0.19041
sys.version_info(major=3, minor=6, micro=10, releaselevel='final', serial=0)
print(shap.version)
0.35.0

Y

Accidentally closed

I will close this issue. I upgraded Python (3.85) to new environment and all started to work. So it seems that 3.6 does not work any more.


Allow another HTTP client

Hi,
Can you allow to set another HTTP Client to the library ?
You implement already PSR-7, and you just have  #to implement https://github.com/php-http/httplug for example.
Regards.

This topic has been discussed at length. https://github.com/thephpleague/oauth2-client/pull/538

@ElGigi Please see #685


How can there be fewer 'excess events' when demand is reduced?

I build 100.000 offshore wind mills

I reduce energy demand by a) cut population in half, b) demolish all old houses, and reduce new houses to 0.1 million.

I think the answer to that question is that peaks in the wind profile that earlier where counted as multiple events are now part of a longer single event.

I think the answer to that question is that peaks in the wind profile that earlier where counted as multiple events are now part of a longer single event.

I fully agree with @ChaelKruip . This is supported by the fact that the dashboard item showing the total number of excess hours does increase.
Closing this issue. Re-open if you disagree with the explanation.


How to upload music

Are there any other ways to upload music apart from youTube?

For information we forked project here https://github.com/wtfcoderz/streamlist
Feel free to follow us if you want

Okay, I'll start following that too @WTFKr0


Upgrade to MudBlazor 7.* and Extensions.MudBlazor.StaticInput 2.*

Description
This update upgrades package references to the official release version for:

MudBlazor 7.*
Extensions.MudBlazor.StaticInput 2.*

How Has This Been Tested?
TODO (This cannot be tested until after the official release.)
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

Do you think these lines are necessary?
https://github.com/MudBlazor/Templates/blob/c5294d177ab4a90a8e5fc34e8a777c061f75958e/src/MudBlazor.Templates.csproj#L50-L56
Or did they get added to the csproj by accident?
I removed them locally and built using nuke pack, and the NuGet package was the same as it was with these lines.

Do you think these lines are necessary(The question is not related to this PR)?
https://github.com/MudBlazor/Templates/blob/c5294d177ab4a90a8e5fc34e8a777c061f75958e/src/MudBlazor.Templates.csproj#L50-L56
Or did they get added to the csproj by accident? I removed them locally and built using nuke pack, and the NuGet package was the same as it was with these lines.

I think you're right, that they got added by mistake and can be removed.


Enhancement of API for weak singletons

I'd like to make a feature request for weak singletons. There are many cases in your app where you need to use a singleton, but the issue is the singleton will live on for the lifetime of the app.
Instead, I propose weak singletons. Essentially Swinject would maintain a weak reference to the class when it is resolved instead of a strong one. Anyone else who resolves the class while the first resolved instance exists will thus get that same instance. When all resolved instances are released, the singleton can then be de-initialized, since Swinject itself is not holding onto it. If someone else then resolves the class again, a new instance will be created.
Thoughts?

I've also wanted to add weak singleton feature. After #165, it looks easier to implement it.


Add performance counters in the system

Performance counter can be turned on in options or activated via plus args or env.

Added in 6b3d206.


Create setup_test_with_server hook

Add a hook to be executed before each test_with_server just after the server started.
defmodule MyApp.MyModuleTest do
  use ExUnit.Case
  import FakeServer

  def setup_test_with_server(env) do
    IO.puts "This server is running at port #{env.port}"
  end

  describe "my test describe" do
    # ...
end

I'll work on this issue.


kubectl plugin for plan execution

We'd like to be able type things like:
kubectl maestro plan show deploy --instance=kafka
And get a plan output.

Completed.


[New]: Learning Path for Hugo

Path Name
Hugo
Additional info
https://gohugo.io/

https://www.youtube.com/playlist?list=PLLAZ4kZ9dFpOnyRlyS-liKL5ReHDcj4G3

Already existing path

[X] I searched on https://paths.tinkerhub.org/ and found that the learning path doesnt exist.

I'm unable to find much resources related to hugo 😥
These are the only ones I found out

https://gohugo.io/
https://flaviocopes.com/start-blog-with-hugo/
https://www.youtube.com/playlist?list=PLLAZ4kZ9dFpOnyRlyS-liKL5ReHDcj4G3

@nikiljos what were you expecting?
what is there to learn about a template engine?
are we just stat padding the number of learning paths now?

@nikiljos what were you expecting?
what is there to learn about a template engine?
are we just stat padding the number of learning paths now?

@LunaticHacker
I wanted to learn hugo but could not find a lot of resources....
Not sure whether there is much to learn but as a beginner I personally felt I need to learn it to implement it....
There is something to learn in it right?
Open for your suggestions... Not sure if such a learning path is necessary...

@nikiljos

Not sure if such a learning path is necessary...

It is not. Hugo is dead simple all you need to do is to read the documentation, learning paths are not supposed to replace documentations for simple technologies. It should be about guiding the learner to correct resources in the correct chronology to an otherwise messy topic to learn and grasp.(thus the name)

@gautamkrishnar Maybe we could close this issue if this is an unnecessary learning path... What's your opinion

@nikiljos there are tons of learning videos on youtube. Yes, we can close this for now.


feature: allow namespace to be set in a chart

Allow namespace to be set in a chart for resources that need to be created in specific namespace

+1

@adamreese This is supported now, right?

What is the current status of this? Can I set the namespace in my chart through a value or will Tiller override this?
I tried finding some more information in the docs, but there's not much reference to namespaces in there. Nor on setting them explicitly through the chart, or how the value of .Release.Namespace is set.

The problem here comes from the way the Kubernetes library works. It requires you to give it a single namespace that it can manage. If you give it a resource with an alternate namespace, it will happily create that resource, but then subsequent queries for that object will not show the object (because it's in a namespace that differs from the one you gave it).
So essentially:

You can create resources in multiple namespaces with helm install
You cannot helm upgrade them, though (and they may not show up with helm status)

Thus, we consider these charts to be unsupported
We'd gladly take a PR that elegantly works around this limitation.

Yeah so I've been playing with this a bit. @technosophos is absolutely right. If your chart includes different objects which you want to exist in different namespaces, that isn't going to work the way you think it does.
Helm seems to have its own concept of namespace based solely on which namespace it implicitly launches on (the default) or which is explicitly passed in at runtime (this is reflected in status output and Release.Namespace built-in. It has no knowledge of manifest defined namespaces i.e. metadata.namespace so if you were to use that, helm would have no knowledge of it.
In my eyes, and how I'm (initially) using helm, a chart shouldn't contain objects which transgress multiple namespaces. Additionally, I'm defining the namespace in my values file so i can use --set to keep a more consistent workflow. In this case, I can safely continue using helm upgrade and other functions without worrying about mismatches only having to remember helm's reporting of namespace is not valid.

@InAnimaTe that is how I am doing it now as well, but from @technosophos his answer I could not really deduct if this manual overriding of the Helm Release.Namespace is actually supported or it might break at any moment.

Helm does not have it's own concept of namespace. We follow Kubernetes' conception very carefully. The problem is that Kubernetes clients connect to a specific namespace and do their operations from within that namespace. If you tell Helm that you deployed a release to namespace foo, it will connect to that namespace to learn about the release.
However, it is possible to connect to one namespace, and then deploy a resource to another namespace by overriding the contextual namespace using the metadata.namespace: field in a manifest.
kubectl explicitly disallows you from connecting to one namespace and installing into another.
Say I have a manifest that declares itself to be in the metadata.namespace: cookies. If I try to install this with kubectl pointed to a different namespace, I get this:
⇒  kubectl create --namespace default -f ./example.svc
the namespace from the provided object "cookies" does not match the namespace "default". You must pass '--namespace=cookies' to perform this operation.

For whatever reason, we never explicitly disallowed this. We just tell people not to do it. While kubectl can operate on just one object and override an unconfigured namespace, Helm doesn't have that luxury, since it is almost always dealing with more than one object (some of which are un-namespaced, like TPRs and Namespace kinds).
So what we suggest to people is to use the --namespace flag on the CLI, and use (but don't override) .Release.Namespace. The .Release.Namespace value should always contain the value that was passed as --namespace. It's possible to set the default value for --namespace by any of the way kubectl supports setting a default namespace (see kubectl config -h).
That said, you are free to use Helm other ways, provided you understand that there are some known edge cases where Helm will not be able to find certain resources because they were created in a namespace that doesn't match the one you tell Helm to use (with --namespace or through Kube config).
As far as future support goes, we are more likely to try to support multiple namespaces. We are less likely to get stricter about what we allow in charts (unless it really becomes a problem). We'd almost definitely accept a PR that allowed users to export something like HELM_NAMESPACE and have that work like using --namespace. (We already do this with --tiller-namespace and TILLER_NAMESPACE).
I know the topic is a little obscure. I hope this at least explained why Helm currently works the way it does.

@adamreese I want to close this due to inactivity and that #2060 seems to have taken over this discussion. However this issue does have a "Upcoming Major" label so wanted to double-check with you first. Can we close this one?

We can close this.

@technosophos Does helm/tiller now support to specify namespace in chart?
I have done some simple test in my local env:
env
root@llcao-master:~# kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.4", GitCommit:"d03f6421b5463042d87aa0211f116ba4848a0d0f", GitTreeState:"clean", BuildDate:"2019-01-17T13:14:09Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.4", GitCommit:"d03f6421b5463042d87aa0211f116ba4848a0d0f", GitTreeState:"clean", BuildDate:"2019-01-17T13:14:09Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

root@llcao-master:~# helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"8ddf4db6a545dc609539ad8171400f6869c61d8d", GitTreeState:"clean"}

Create nginx-chart and add resource in another namespace:
root@llcao-master:~# helm create nginx-chart
Creating nginx-chart
# Default values for nginx-chart.

root@llcao-master:~# cat > ./nginx-chart/templates/sleep.yaml <<EOF
>apiVersion: extensions/v1beta1
>kind: Deployment
>metadata:
>  name: sleep
>  {{- if .Values.sleep.anotherNamespace }}
>  namespace: {{ .Values.sleep.anotherNamespace }}
>  {{- end }}
>spec:
>  replicas: 1
>  template:
>    metadata:
>      labels:
>        app: sleep
>    spec:
>      containers:
>      - name: sleep
>        image: "{{ .Values.sleep.repository }}:{{ .Values.sleep.tag }}"
>        command: ["/bin/sleep", "3650d"]
>        imagePullPolicy: IfNotPresent
>EOF

root@llcao-master:~# cat >> ./nginx-chart/values.yaml <<EOF
>sleep:
>  anotherNamespace: istio-system
>  repository: pstauffer/curl
>  tag: v1.0.2
>EOF

Install the chart:
root@llcao-master:~# helm install ./nginx-chart --name nginx --namespace default

Check the release status:
root@llcao-master:~# helm status nginx
LAST DEPLOYED: Tue Feb 12 02:47:31 2019
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/Service
NAME               TYPE       CLUSTER-IP   EXTERNAL-IP  PORT(S)  AGE
nginx-nginx-chart  ClusterIP  <IP_ADDRESS>  <none>       80/TCP   9m

==> v1beta2/Deployment
NAME               DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
nginx-nginx-chart  1        1        1           1          9m

==> v1beta1/Deployment
sleep  1  1  1  1  9m

==> v1/Pod(related)
NAME                               READY  STATUS   RESTARTS  AGE
nginx-nginx-chart-c6c9778cc-vq5r5  1/1    Running  0         9m
sleep-789c4b4667-5q4dr             1/1    Running  0         9m

NOTES:
1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace default -l "app=nginx-chart,release=nginx" -o jsonpath="{.items[0].metadata.name}")
  echo "Visit http://<IP_ADDRESS>:8080 to use your application"
  kubectl port-forward $POD_NAME 8080:80

The status shows that the sleep resources can be listed, although it's in another namespace(istio-system), instead of chart release namespace(default)
Check the sleep deployment tag:
root@llcao-master:~# kubectl -n istio-system get deploy sleep -owide
NAME                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE    CONTAINERS                 IMAGES
sleep                    1         1         1            1           112s   sleep                      pstauffer/curl:v1.0.2

Upgrade the release with new sleep image:
root@llcao-master:~# helm upgrade nginx --set sleep.tag=v1.0.3 ./nginx-chart
Release "nginx" has been upgraded. Happy Helming!
LAST DEPLOYED: Tue Feb 12 02:43:57 2019
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1beta2/Deployment
NAME               DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE
nginx-nginx-chart  1        1        1           1          3m

==> v1beta1/Deployment
sleep  1  1  0  1  3m

==> v1/Pod(related)
NAME                               READY  STATUS       RESTARTS  AGE
nginx-nginx-chart-c6c9778cc-jmkdr  1/1    Running      0         3m
sleep-789c4b4667-z2sr6             1/1    Terminating  0         3m
sleep-85bbdf484d-jm97t             0/1    Pending      0         0s

==> v1/Service
NAME               TYPE       CLUSTER-IP    EXTERNAL-IP  PORT(S)  AGE
nginx-nginx-chart  ClusterIP  <IP_ADDRESS>  <none>       80/TCP   3m

NOTES:
1. Get the application URL by running these commands:
  export POD_NAME=$(kubectl get pods --namespace default -l "app=nginx-chart,release=nginx" -o jsonpath="{.items[0].metadata.name}")
  echo "Visit http://<IP_ADDRESS>:8080 to use your application"
  kubectl port-forward $POD_NAME 8080:80

Check if sleep image is upgraded
root@llcao-master:~# kubectl -n istio-system get deploy sleep -owide
NAME                     DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE    CONTAINERS                 IMAGES
sleep                    1         1         1            0           3m34s  sleep                     pstauffer/curl:v1.0.3

The sleep image has been upgraded from v1.0.2 to v1.0.3 successfully.
Delete the release:
root@llcao-master:~# helm delete nginx --tls --purge
root@llcao-master:~# kubectl -n istio-system get deploy sleep
Error from server (NotFound): deployments.extensions "sleep" not found

We can see that the sleep resources has also been removed after the chart is deleted.
So can we say the helm/tiller now supports specify resources in other namespace other than the .Release.Namespace?


Crash in WeakRefTracker finalizer with mono 5

From @hmflash on May 24, 2017 23:8
Mono 5 crashes during exit when the WeakRefTracker finalizer runs.  I'm not sure if this is a mono bug or an IronPython bug.  All my application does is import a module and exit.  Some modules do not exhibit this problem (time) where other modules do exhibit this problem (code xmllib). This does not reproduce on mono 4.8.  My test application is using the IronPython 2.7.7 nuget package.
My test application is:
namespace PythonTest
{
	class Program
	{
		public static void Main(string[] args)
		{
			var engine = IronPython.Hosting.Python.CreateEngine();

			// Add IronPython.StdLib to the search path
			var basePath = PlatformServices.Default.Application.ApplicationBasePath;
			var pythonPath = Path.Combine(basePath, "Python");

			var paths = engine.GetSearchPaths();
			paths.Add(pythonPath);
			engine.SetSearchPaths(paths);

			foreach (var item in args)
			{
				Console.WriteLine("Importing module {0}", item);
				engine.ImportModule(item);
			}

			Console.WriteLine("SUCCESS!");
		}
	}
}

The failing output is:
Importing module xmllib
SUCCESS!
Stacktrace:

  at <unknown> <0xffffffff>
  at (wrapper managed-to-native) System.Delegate.CreateDelegate_internal (System.Type,object,System.Reflection.MethodInfo,bool) [0x00000] in <4dc8ec68b0964e099af86e50301f5f3c>:0
  at System.Delegate.CreateDelegate (System.Type,object,System.Reflection.MethodInfo,bool,bool) [0x002f0] in <4dc8ec68b0964e099af86e50301f5f3c>:0
  at System.Delegate.CreateDelegate (System.Type,object,System.Reflection.MethodInfo) [0x00000] in <4dc8ec68b0964e099af86e50301f5f3c>:0
  at System.Reflection.Emit.DynamicMethod.CreateDelegate (System.Type,object) [0x0001a] in <4dc8ec68b0964e099af86e50301f5f3c>:0
  at System.Linq.Expressions.Compiler.LambdaCompiler.CreateDelegate () [0x00022] in <c716d84e34fc4c408a98d9a0c1024723>:0
  at System.Linq.Expressions.Compiler.LambdaCompiler.Compile (System.Linq.Expressions.LambdaExpression) [0x00013] in <c716d84e34fc4c408a98d9a0c1024723>:0
  at System.Linq.Expressions.Expression`1<TDelegate_REF>.Compile (bool) [0x00000] in <c716d84e34fc4c408a98d9a0c1024723>:0
  at System.Linq.Expressions.Expression`1<TDelegate_REF>.Compile () [0x00000] in <c716d84e34fc4c408a98d9a0c1024723>:0
  at System.Runtime.CompilerServices.CallSiteBinder.BindCore<T_REF> (System.Runtime.CompilerServices.CallSite`1<T_REF>,object[]) [0x0003b] in <c716d84e34fc4c408a98d9a0c1024723>:0
  at System.Dynamic.UpdateDelegates.UpdateAndExecute1<object, bool> (System.Runtime.CompilerServices.CallSite,object) [0x000f1] in <c716d84e34fc4c408a98d9a0c1024723>:0
  at IronPython.Runtime.Binding.PythonConversionBinder.BoolConversion (System.Runtime.CompilerServices.CallSite,object) [0x0001f] in <1304a224b80f47cdada4a1f932239862>:0
  at IronPython.Runtime.Converter.ConvertToBoolean (object) [0x00000] in <1304a224b80f47cdada4a1f932239862>:0
  at IronPython.Compiler.Ast.DynamicConvertExpression/BooleanConversionInstruction.Run (Microsoft.Scripting.Interpreter.InterpretedFrame) [0x00007] in <1304a224b80f47cdada4a1f932239862>:0
  at Microsoft.Scripting.Interpreter.Interpreter.Run (Microsoft.Scripting.Interpreter.InterpretedFrame) [0x00016] in <48823422b7404dddb2a834a9795980bd>:0
  at Microsoft.Scripting.Interpreter.LightLambda.Run3<T0_REF, T1_REF, T2_REF, TRet_REF> (T0_REF,T1_REF,T2_REF) [0x0005c] in <48823422b7404dddb2a834a9795980bd>:0
  at IronPython.Compiler.PythonCallTargets.OriginalCallTarget2 (IronPython.Runtime.PythonFunction,object,object) [0x00012] in <1304a224b80f47cdada4a1f932239862>:0
  at Microsoft.Scripting.Interpreter.FuncCallInstruction`5<T0_REF, T1_REF, T2_REF, T3_REF, TRet_REF>.Run (Microsoft.Scripting.Interpreter.InterpretedFrame) [0x00000] in <48823422b7404dddb2a834a9795980bd>:0
  at Microsoft.Scripting.Interpreter.Interpreter.Run (Microsoft.Scripting.Interpreter.InterpretedFrame) [0x00016] in <48823422b7404dddb2a834a9795980bd>:0
  at Microsoft.Scripting.Interpreter.LightLambda.Run4<T0_REF, T1_REF, T2_REF, T3_REF, TRet_REF> (T0_REF,T1_REF,T2_REF,T3_REF) [0x0006d] in <48823422b7404dddb2a834a9795980bd>:0
  at System.Dynamic.UpdateDelegates.UpdateAndExecute3<T0_REF, T1_REF, T2_REF, TRet_REF> (System.Runtime.CompilerServices.CallSite,T0_REF,T1_REF,T2_REF) [0x0011a] in <c716d84e34fc4c408a98d9a0c1024723>:0
  at IronPython.Runtime.PythonContext.CallSplat (object,object[]) [0x0001d] in <1304a224b80f47cdada4a1f932239862>:0
  at IronPython.Runtime.Operations.PythonCalls.Call (object,object[]) [0x00005] in <1304a224b80f47cdada4a1f932239862>:0
  at IronPython.Runtime.WeakRefTracker.Finalize () [0x00056] in <1304a224b80f47cdada4a1f932239862>:0
  at (wrapper runtime-invoke) object.runtime_invoke_virtual_void__this__ (object,intptr,intptr,intptr) [0x0001e] in <4dc8ec68b0964e099af86e50301f5f3c>:0

Mono information:
Mono JIT compiler version 5.0.0 (Stable <IP_ADDRESS>/9667aa6 Thu May 11 14:33:04 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  amd64
        Disabled:      none
        Misc:          softdebug
        LLVM:          supported, not enabled.
        GC:            sgen (concurrent by default)

Copied from original issue: IronLanguages/main#1657

We see the same issue. Our crash has the exact same stack trace. Both with mono 5.0.x and now mono <IP_ADDRESS> and IronPython 2.7.6, did not see it before mono 5.0 as well.

This should be fixed in Mono 5.4, see https://bugzilla.xamarin.com/show_bug.cgi?id=57301

Awesome, I'll test that change and report back. Thanks for the super quick reply.

FYI, Mono 5.4 is not a final release yet. I think the first Alpha was released at the start of August. http://www.mono-project.com/docs/about-mono/releases/5.4.0/

I'm patching the release 5.2 sources with that one line change to see if it's sufficient all alone. If so I'll let you know. It's building right now. I have to run soon though for a start of school parent/teacher meeting, but I should have a test result by tomorrow. Thanks again!

Alas, that single line change added back to 5.2 was not sufficient, perhaps more was changed that also relates. I'll try to take a look for any related changes since 5.2. I also tried building and running against the latest <IP_ADDRESS> and unfortunately my app crashes with a different issue when running an IronPython script:

Assertion at dynamic-image.c:209, condition `prev == MONO_HANDLE_RAW (obj)' not met

Stacktrace:
at  <0xffffffff>
at (wrapper managed-to-native) System.Reflection.Emit.ModuleBuilder.getToken (System.Reflection.Emit.ModuleBuilder,object,bool) [0x00022] in <6543d6bac4be4fe3b57b6ee9cddbc34d>:0
at System.Reflection.Emit.ModuleBuilder.GetToken (System.Reflection.MemberInfo,bool) [0x00061] in /home/pbi/git/mono/runtime/sources-<IP_ADDRESS>/mono-<IP_ADDRESS>/mcs/class/corlib/System.Reflection.Emit/ModuleBuilder.cs:793
at System.Reflection.Emit.ModuleBuilderTokenGenerator.GetToken (System.Reflection.MemberInfo,bool) [0x00000] in /home/pbi/git/mono/runtime/sources-<IP_ADDRESS>/mono-<IP_ADDRESS>/mcs/class/corlib/System.Reflection.Emit/ModuleBuilder.cs:1207
at System.Reflection.Emit.ILGenerator.Emit (System.Reflection.Emit.OpCode,System.Reflection.MethodInfo) [0x0004e] in /home/pbi/git/mono/runtime/sources-<IP_ADDRESS>/mono-<IP_ADDRESS>/mcs/class/corlib/System.Reflection.Emit/ILGenerator.cs:734
at System.Reflection.Emit.ILGenerator.EmitCall (System.Reflection.Emit.OpCode,System.Reflection.MethodInfo,System.Type[]) [0x00084] in /home/pbi/git/mono/runtime/sources-<IP_ADDRESS>/mono-<IP_ADDRESS>/mcs/class/corlib/System.Reflection.Emit/ILGenerator.cs:841
at Microsoft.Scripting.Generation.ILGen.EmitCall (System.Reflection.Emit.OpCode,System.Reflection.MethodInfo,System.Type[]) [0x0000a] in <493b9fd2a26745c8a6d84dd641c02e79>:0
at IronPython.Runtime.Types.NewTypeMaker.EmitBaseMethodDispatch (System.Reflection.MethodInfo,Microsoft.Scripting.Generation.ILGen) [0x0005e] in :0
...

I added the line change to the 5.2 sources and it looks like it works for this specific issue (CreateDelegate). I'm running the full test suite with the changed version to see what else falls out.

@pb-devans Can you share the script that is causing the new error?

@slide just spent some time trying to generate a minimal script that crashes on mono <IP_ADDRESS> and it turns out all I need is "import os" it looks like. Then I get that stack trace above. Ok next I'm going to double check my 5.2 patching since you seemed to get that to work.

It looks like there were some changes in dynamic-image.c that are causing that assert, I'll file an issue.

I submitted this issue https://bugzilla.xamarin.com/show_bug.cgi?id=59364

Thank you! I redid my patch on 5.2 and also confirmed that it resolved this original issue. My test before had a mistake in how I was installing. Now I have the patch applied properly and I can't reproduce the original issue either.

This should be fixed in newer Mono releases.


Do you plan to enhance it for incremental models?

we could not be sure incremental materialization strategies is working well or missing sth so thats why I am asking.

Hi,
same question. Incremental models could not be tested, is there a workaround?

+1
an dbt_unit_testing.mock_initial() section? and/or some way to mock {{ 'this' }}?

+1 on this as well

+1! I love this package! But without support for incremental models, we will not be able to test our most important models 😢

Hello everyone,
We have created a new branch proposing an implementation of "dbt-unit-testing" that supports "incremental-models".
As you will see, our solution is a bit 'intrusive', at least for those we prefer to redefine the "ref" macro instead of using "dbt_init_testing.ref" on your models. Here you'll have to use some "dbt_init_testing.xxx", as explained in the README.
We did try to find a less intrusive solution, but our attempts seemed hacky, so we decided to keep it like this.
We are eager to hear your feedback and suggestions, so please give it a try and let us know your thoughts. We hope it will save you time and prove useful.
To access this branch, you will need to change the revision of the package as follows:
packages:
  - git: "https://github.com/EqualExperts/dbt-unit-testing"
    revision: e4a93ebd08ccd388d212b1ec636da2e467db12b9

Please do not hesitate to share your feedback with us. Thank you!

Hey, the implemented PR works great. Is there anything I could help with trying to get this released?


Pin pluggy version to 1.2.0

To fix issues with build we need to pin version of pluggy to 1.2.0

Guys, I'm really not sure what I'm talking about... :sweat_smile:
But after discussions with @carlcsaposs-canonical on this particular thing, I understood that we have a solution available without any additional pinning on charms side.
We just need to use v5 for the corresponding github action.
canonical/data-platform-workflows/.github/workflows/build_charms_with_cache.yaml@v5

(Proof is on https://github.com/canonical/mongodb-k8s-operator/pull/200)

BTW that seems to be what other charms are doing as well:
https://github.com/canonical/mysql-k8s-operator/blob/main/.github/workflows/ci.yaml#L37

@juditnovak, looks like  canonical/data-platform-workflows/.github/workflows/build_charms_with_cache.yaml@v5 is not working on CI and causing  issue crashes

WOW, I'm very glad that the githb action was useful at the end :-)


fix container cpu hot add

The cpu hotplug calculation should take into account the initial vCPUs
counts otherwise we end up hotplugging more vCPUs than actual need.
Before fix:
[macbeth@runtime]$docker run --rm -it --runtime kata --cpu-period "1000" --cpu-quota "1000" busybox
/ # nproc
2

After fix:
[macbeth@runtime]$docker run --rm -it --runtime kata --cpu-period "1000" --cpu-quota "1000" busybox
/ # nproc
1

@bergwolf

Before fix:
[macbeth@runtime]$docker run --rm -it --runtime kata --cpu-period "1000" --cpu-quota "1000" busybox
/ # nproc
2

yes, you see two CPUs but the container can use only 1 cpu since it's placed inside a CPU cgroup
have you considered the k8s case where one container has a CPU constraint and other doesn't?
for example container A has a constraint of 2vCPUs and consumes 200% of CPU (2 vcpus) and container B doesn't have CPU constraint and consumes 100% of CPU (1 vcpu), since your VM only have 2 vcpus you won't be honoured the CPU constraint of the container A.
https://github.com/kata-containers/documentation/blob/master/constraints/cpu.md#container-without-cpu-constraint
currently we are leaving 1 vcpu for containers without CPU constraints and non-container processes, like systemd and kata-agent, I'd like to see how much will impact this change to HPC containers

No, if container B doesn't have CPU constraints, it consumes all the vCPUs of a guest.

Actually, that's not true
I ran next test:
# ~/cpu-test.yaml
apiVersion: v1
kind: Pod
metadata:
  name: cpu-demo
spec:
  containers:
  - name: cpu0
    image: vish/stress
    resources:
      limits:
        cpu: "3"
    args:
    - -cpus
    - "3"
  - name: cpu1
    image: vish/stress
    args:
    - -cpus
    - "3"

Container cpu0 has a constraint of 3 vcpus and will try to use 300% of CPU
Container cpu1 doesn't have a constraint and will try to use 300% of CPU
sudo -E kubectl create -f ~/cpu-test.yaml

$ ps aux | grep qemu
root     23524  380  1.0 3257828 172244 ?      Sl   17:55  26:07 /usr/bin/qemu-lite-system-x86_64 -name sandbox-e5dc98f03f26a14f3862f0357e902f911d72f7dc56cd02a28a2dd97dfdc8be64 -uuid a2a4a4ca-68dd-4274-96c2-13bf52094df8 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host,pmu=off -qmp unix:/run/vc/vm/e5dc98f03f26a14f3862f0357e902f911d72f7dc56cd02a28a2dd97dfdc8be64/qmp.sock,server,nowait -m 2048M,slots=2,maxmem=17065M -device pci-bridge,bus=pci.0,id=pci-bridge-0,chassis_nr=1,shpc=on,addr=2 -device virtio-serial-pci,disable-modern=true,id=serial0 -device virtconsole,chardev=charconsole0,id=console0 -chardev socket,id=charconsole0,path=/run/vc/vm/e5dc98f03f26a14f3862f0357e902f911d72f7dc56cd02a28a2dd97dfdc8be64/console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 -object memory-backend-file,id=mem0,mem-path=/usr/share/kata-containers/kata-containers-debug.img,size=536870912 -device virtio-scsi-pci,id=scsi0,disable-modern=true -device virtserialport,chardev=charch0,id=channel0,name=agent.channel.0 -chardev socket,id=charch0,path=/run/vc/vm/e5dc98f03f26a14f3862f0357e902f911d72f7dc56cd02a28a2dd97dfdc8be64/kata.sock,server,nowait -device virtio-9p-pci,disable-modern=true,fsdev=extra-9p-kataShared,mount_tag=kataShared -fsdev local,id=extra-9p-kataShared,path=/run/kata-containers/shared/sandboxes/e5dc98f03f26a14f3862f0357e902f911d72f7dc56cd02a28a2dd97dfdc8be64,security_model=none -netdev tap,id=network-0,vhost=on,vhostfds=3:4:5:6:7:8:9:10,fds=11:12:13:14:15:16:17:18 -device driver=virtio-net-pci,netdev=network-0,mac=56:1c:7a:60:22:88,disable-modern=true,mq=on,vectors=18 -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -kernel /usr/share/kata-containers/vmlinuz-<IP_ADDRESS>-135.container -append tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k console=hvc0 console=hvc1 iommu=off cryptomgr.notests net.ifnames=0 pci=lastbus=0 root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro rw rootfstype=ext4 debug systemd.show_status=true systemd.log_level=debug panic=1 nr_cpus=4 init=/usr/lib/systemd/systemd systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket -smp 1,cores=1,threads=1,sockets=1,maxcpus=4

using socat  and a debuggable image with top I attached to the console.sock to inspect the processes
$ sudo socat stdin,raw,echo=0,escape=0x11 unix-connect:/run/vc/vm/e5dc98f03f26a14f3862f0357e902f911d72f7dc56cd02a28a2dd97dfdc8be64/console.sock
# ps aux | grep stress
root       175  298  0.1   5828  2080 ?        Rsl  17:55  26:21 /stress -logtostderr -cpus 3
root       189 99.9  0.1   5828  2080 ?        Ssl  17:55   8:47 /stress -logtostderr -cpus 3

Container cpu0
# cat /proc/175/cgroup
10:cpuset:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
9:memory:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
8:pids:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
7:freezer:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
6:cpu,cpuacct:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
5:blkio:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
4:net_cls,net_prio:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
3:perf_event:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
2:devices:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999
1:name=systemd:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999

checking period and quota
# cat /sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999/cpu.cfs_quota_us
300000
# cat /sys/fs/cgroup/cpu,cpuacct/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-fe90c6fd297997c0fd2e599bbd0512b852fc743e89f16f8b033d46389f6e6999/cpu.cfs_period_us
100000

# top -p 175

Container cpu0 consumes ~300% of CPU
Container cpu1
# cat /proc/189/cgroup
10:cpuset:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
9:memory:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
8:pids:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
7:freezer:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
6:cpu,cpuacct:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
5:blkio:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
4:net_cls,net_prio:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
3:perf_event:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
2:devices:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79
1:name=systemd:/kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79

checking period and quota
# cat /sys/fs/cgroup/cpu,cpuacct//kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79/cpu.cfs_quota_us
-1
# cat /sys/fs/cgroup/cpu,cpuacct//kubepods/burstable/pode6830706-b134-11e8-9560-000d3afd0f0a/crio-d9e1af93270cca6d4a4182a936901475b22777e922f42f4944f9f4aba0986a79/cpu.cfs_period_us
100000

# top 189

Container cpu0 consumes ~100% of CPU
Conclusion
Containers with CPU constraints have more priority than container without constraints
the question here is how much this patch will impact the performance of containers with CPU constraints when containers without a constraints run in the same POD
IMO this patch will impact HPC containers and its performance, hence NACK and -1
cc @grahamwhaley @sboeuf

@devimc Could you check cpuset for the two container processes, as well as kata-agent?
I'm traveling and do not have access to k8s cluster right now. But AFAICT, for a container created with:
docker run --rm -it --runtime kata --cpu-period 1000 --cpu-quota 2000 ubuntu

Both kata-agent and /bin/bash container command have access to ALL three vCPUs. kata-agent is not limited by any constraints and can use as many CPU cycles at it can in scheduling, while /bin/bash is restricted by specified cpu quota.
OTOH, CPU cgroup quota does not guarantee the CPU share of the quota. It simply limit the ceiling CPU time you can use.
root@d6731e549882:/# cat /proc/cpuinfo |grep processor
processor       : 0
processor       : 1
processor       : 2

bash-4.2# ps aux|grep kata
root       120  0.2  0.8 364756  4424 ?        Ssl  08:30   0:01 /usr/bin/kata-agent
bash-4.2# cat /proc/120/cgroup |grep cpu
7:cpuset:/
2:cpu,cpuacct:/
bash-4.2# cat /sys/fs/cgroup/cpu,cpuacct/cpu.cfs_period_us
100000
bash-4.2# cat /sys/fs/cgroup/cpu,cpuacct/cpu.cfs_quota_us
-1
bash-4.2# cat /sys/fs/cgroup/cpuset/cpuset.cpus
0-2

bash-4.2# cat /proc/149/cgroup |grep cpu
6:cpu,cpuacct:/docker/a9e4f217a0cc727a5401043d23904ce38c5b99d9bb9bc26bb7f085ce01e2a692
2:cpuset:/docker/a9e4f217a0cc727a5401043d23904ce38c5b99d9bb9bc26bb7f085ce01e2a692
bash-4.2# cat /sys/fs/cgroup/cpuset/docker/a9e4f217a0cc727a5401043d23904ce38c5b99d9bb9bc26bb7f085ce01e2a692/cpuset.cpus
0-2
bash-4.2# cat /sys/fs/cgroup/cpu,cpuacct/docker/a9e4f217a0cc727a5401043d23904ce38c5b99d9bb9bc26bb7f085ce01e2a692/cpu.cfs_quota_us
2000
bash-4.2# cat /sys/fs/cgroup/cpu,cpuacct/docker/a9e4f217a0cc727a5401043d23904ce38c5b99d9bb9bc26bb7f085ce01e2a692/cpu.cfs_period_us
1000

So in your example, container cpu0 can use at most 300% vCPU time, while container cpu1 can use at most ALL (iow 400%) vCPU time. The reason you are seeing 3:1 split between them is because cpu0 process will not yield vCPU as long as it has more quota, while cpu1 process yields its vCPU when it has competition (surely it's a simplification. The scheduling is also affected by cpu.shares settings).
I'm not sure what kind of semantics we want to give to users. Maybe we should add an option to control if the initial CPU/memory should be assigned to containers with constraints.

@devimc What do you think of the idea that uses a config option to specify if the initial vCPU and memory settings in the config are shared with containers with cpu/memory constraints?

@bergwolf  cold plugged resources (mem and cpu) can be used or taking into account by containers with or without constraints , sounds good, but we should document the possible impacts.
btw once we have support for mem hotplug we should change default_memory to 128 or 256

@bergwolf @devimc What the summary on this, and what action will be taken for this PR?

@sboeuf I'll add a new cli config option to control the behavior.

@bergwolf sounds good, thanks for the feedback.
Please make sure you tag the new PR appropriately (enhancement or bug-fix) so that it gets easy to review which PR need to be backported.


bms/auth-sign-in-1318

Linked issues
closes: # (1318)
Details
Provide a list of your changes here. If you are fixing a bug, please provide steps to reproduce the bug.
Change details

Describe your changes, with screenshots and code snippets as appropriate

code snippets:
screenshots:
Attestation Checklist

[x] My code follows the style guidelines of this project

I have checked for/fixed spelling, linting, and other errors

I have commented my code for clarity

I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient)

My changes generate no new warnings

I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:

Local testing
E2E testing in Teams

New and existing unit tests pass locally with my changes

Additional information

Feel free to add other relevant information below

https://github.com/microsoft/teams-ai/issues/1318#issue-2147805974

in application.ts,  getTokenOrStartSignIn,... does deleteUserInSignInFlow and setUserInSignInFlow.
In app.py, get_token_or_sign_in_user,... does not directly do these things. Here the "insigninflow" is captured at the top. IN_SIGN_IN_KEY = "__InSignInFlow__". IN_SIGN_IN_KEY is used in the
    async def _authenticate_user(self, context: TurnContext, state):
        if self.options.auth and self._auth:
            auth_condition = (
                isinstance(self.options.auth.auto, bool) and self.options.auth.auto
            ) or (callable(self.options.auth.auto) and self.options.auth.auto(context))
            user_in_sign_in = IN_SIGN_IN_KEY in state.user
            if auth_condition or user_in_sign_in:
                key: Optional[str] = state.user.get(IN_SIGN_IN_KEY, self.options.auth.default)

                if key is not None:
                    state.user[IN_SIGN_IN_KEY] = key
                    res = await self._auth.sign_in(context, state, key=key)
                    if res.status == "complete":
                        del state.user[IN_SIGN_IN_KEY]

                    if res.status == "pending":
                        await state.save(context, self._options.storage)
                        return False

                    if res.status == "error" and res.reason != "invalid-activity":
                        del state.user[IN_SIGN_IN_KEY]
                        raise ApplicationError(f"[{res.reason}] => {res.message}")

        return True

I think the method is looking alright, but I still need to write tests @lilyydu

@BMS-geodev could you update the PR style to follow our contribution guidelines? Thanks!

@corinagum done, apologies

@lilyydu wrote 4 tests that circle around get_token_or_sign_in_user(), and added them to test_app.py
test_get_token_or_sign_in_user_token_exists
test_get_token_or_sign_in_user_no_token_sign_in_flow
test_get_token_or_sign_in_user_successful_authentication
test_get_token_or_sign_in_user_no_auth_manager


Set RequestLog#content for AnnotatedService if a pojo is requested/returned

Logging[Client|Service] can be confusing since the request/response content is sometimes logged, and sometimes not logged.
Request/Responses are logged when:

GrpcService or ThriftService is used
ContentPreviewing[Client|Service] is used

The majority of our users use AnnotatedService along with GrpcService or ThriftService.
However, when adding a Logging[Client|Service] to APIs, it may be surprising that some services log content by default while others don't.
In most cases, this isn't a big problem. However, we recently saw a case where a service handling sensitive data used AnnotatedService and intentionally didn't add a ContentPreviewing[Client|Service]. While adopting GrpcService, they found that sensitive information was being logged by default.
I believe if we just log content for AnnotatedService by default as well, users can be aware that content will be left in most cases and configure Logging[Client|Service] accordingly. As an added bonus, by leaving the POJO at RequestLog#content we may potentially also allow users to sanitize specific fields more easily.

Like gRPC, we may create an abstraction for the requests served by annotated service and set it to RequestLog.requestContent().
https://github.com/line/armeria/blob/0960d091bfc7f350c17e68f57cc627de584b9705/grpc/src/main/java/com/linecorp/armeria/internal/server/grpc/AbstractServerCall.java#L617
interface AnnotatedRequest {
   AnnotatedService service();
   List<Object> parameters();
}


Broken display of some characters.

Windows Terminal version
1.19.240130002
Windows build number
10.0.19044.0
Other Software
No response
Steps to reproduce
I use a custom prompt starship with default preset called Tokyo Night, with nerdfont called FiraCode(Mono)

Expected Behavior
No response
Actual Behavior
Custom prompt uses the semicircle symbol ""(\ue0b4) at the start of which, at certain zoom values(font size 11 for me), an extra pixel appears.

The problem appeared with the latest updates, since I have two versions of the terminal on the device, I can run them in parallel using all the same settings, and in the old version of such a problem is not observed.

Thanks for the feedback! This was recently fixed by #16729 which will ship in the next Windows Terminal version. We're still working on the fine details, but powerline glyphs will work for sure.

@lhecker ah it's been like two or three updates, and the problem's still there, even tried the pre-release version, it has this problem too. What's interesting is that when you answered me, I decided to try the pre-release version and it was already fixed there, but it looks like the problem is back (even though it never disappeared on release)

When you say "pre-release version" are you referring to the preview version? #16729 wasn't released in preview yet. You need to use our nightly builds ("canary") instead. You can find the download links here: https://github.com/microsoft/terminal/discussions/16121
(I recommend the App Installer.)

oops, I apologize, I did get the url mixed up and was checking the wrong build 😬


Release 1.0.0

Description
Release 1.0.0 when ready.

ship it
https://github.com/bmf-san/gobel-api/releases/tag/1.0.0


utf-8 exception at cue track processing

Exception at 84['utf-8' codec can't decode byte 0x91 in position 2266: invalid start byte] in parseCue


Only show tabline, disable status bar

environment

vim: 8
vim-airline: lastest
OS: windows 10
Have you reproduced with a minimal vimrc: yes

let g:airline#extensions#tabline#enabled = 1
let g:airline#extensions#tabline#tab_nr_type = 1 " tab number
let g:airline#extensions#tabline#show_tab_nr = 1
let g:airline#extensions#tabline#formatter = 'default'
let g:airline#extensions#tabline#buffer_nr_show = 1
let g:airline#extensions#tabline#fnametruncate = 16
let g:airline#extensions#tabline#fnamecollapse = 2

let mapleader = ","

let g:airline#extensions#tabline#buffer_idx_mode = 1

nmap <silent> <leader>1 <Plug>AirlineSelectTab1
nmap <silent> <leader>2 <Plug>AirlineSelectTab2
nmap <silent> <leader>3 <Plug>AirlineSelectTab3
nmap <silent> <leader>4 <Plug>AirlineSelectTab4
nmap <silent> <leader>5 <Plug>AirlineSelectTab5
nmap <silent> <leader>6 <Plug>AirlineSelectTab6
nmap <silent> <leader>7 <Plug>AirlineSelectTab7
nmap <silent> <leader>8 <Plug>AirlineSelectTab8
nmap <silent> <leader>9 <Plug>AirlineSelectTab9

What is your airline configuration: ???
if you are using terminal:
terminal: ????
$TERM variable: ???
color configuration (:set t_Co?):
if you are using Neovim:
does it happen in Vim: ???

actual behavior
Bottom status bar is always enabled and I can't find a way to hide/disable it.
expected behavior
I just want to enable tabline so I can fast switch between buffers but don't want to use status line.
Is there an option to this?

Probably set laststatus=0 will help. Closed.

set laststatus=0

correct, but note, this won't work, if you have several windows open.

Well then, do you have a workaround solution for it? maybe an option from airline is the best for users.

no, one could set the statusline to the empty string, but I am not planning to support that feature.

I'll have something to work on then :)


Support rails 6

Did you try the code with rails 6? I know test suite is outdated, but I'd like to know if this code is able to run.

Did you try the code with rails 6? I know test suite is outdated, but I'd like to know if this code is able to run.


Move cassowary into package:flutter

Cassowary doesn't have any additional dependencies and this simplifies things.
Fixes #2442

@chinmaygarde @Hixie


Error during 'azure site create [name] --git'

$ azure site create Honey-ConUHacks --git
$ cat /home/username/.azure/azure.err
2017-01-21T22:36:02.362Z:
{ Error: The server encountered an internal error. There is a bright chance that the site may be actually created.
Please execute: 'azure site list' to verify that the created site: 'undefined' appears in the list.
 If it does not appear in the list then, retry the request.

  <<< async stack >>>
  at createSite__4 (/usr/lib/node_modules/azure-cli/lib/commands/asm/websites/websitesclient.js:294:37)
  at createSite (/usr/lib/node_modules/azure-cli/lib/commands/asm/site.js:402:36)
  at __4 (/usr/lib/node_modules/azure-cli/lib/commands/asm/site.js:244:13)
  <<< raw stack >>>
    at Function.ServiceClient._normalizeError (/usr/lib/node_modules/azure-cli/node_modules/azure-common/lib/services/serviceclient.js:814:23)
    at /usr/lib/node_modules/azure-cli/node_modules/azure-common/lib/services/filters/errorhandlingfilter.js:44:29
    at Request._callback (/usr/lib/node_modules/azure-cli/node_modules/azure-common/lib/http/request-pipeline.js:109:14)
    at Request.self.callback (/usr/lib/node_modules/azure-cli/node_modules/request/request.js:187:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/usr/lib/node_modules/azure-cli/node_modules/request/request.js:1044:10)
    at emitOne (events.js:101:20)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/azure-cli/node_modules/request/request.js:965:12)
  stack: [Getter/Setter],
  code: 'InternalError',
  statusCode: 500,
  requestId: '71bdb4c9a19b37358c7e2ec371498b8f',
  __frame:
   { name: 'createSite__4',
     line: 275,
     file: '/usr/lib/node_modules/azure-cli/lib/commands/asm/websites/websitesclient.js',
     prev:
      { name: 'createSite',
        line: 382,
        file: '/usr/lib/node_modules/azure-cli/lib/commands/asm/site.js',
        prev: [Object],
        calls: 2,
        active: false,
        offset: 20,
        col: 35 },
     calls: 0,
     active: false,
     offset: 19,
     col: 36 },
  rawStack: [Getter] }
Error: The server encountered an internal error. There is a bright chance that the site may be actually created.
Please execute: 'azure site list' to verify that the created site: 'undefined' appears in the list.
 If it does not appear in the list then, retry the request.

  <<< async stack >>>
  at createSite__4 (/usr/lib/node_modules/azure-cli/lib/commands/asm/websites/websitesclient.js:294:37)
  at createSite (/usr/lib/node_modules/azure-cli/lib/commands/asm/site.js:402:36)
  at __4 (/usr/lib/node_modules/azure-cli/lib/commands/asm/site.js:244:13)
  <<< raw stack >>>
    at Function.ServiceClient._normalizeError (/usr/lib/node_modules/azure-cli/node_modules/azure-common/lib/services/serviceclient.js:814:23)
    at /usr/lib/node_modules/azure-cli/node_modules/azure-common/lib/services/filters/errorhandlingfilter.js:44:29
    at Request._callback (/usr/lib/node_modules/azure-cli/node_modules/azure-common/lib/http/request-pipeline.js:109:14)
    at Request.self.callback (/usr/lib/node_modules/azure-cli/node_modules/request/request.js:187:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/usr/lib/node_modules/azure-cli/node_modules/request/request.js:1044:10)
    at emitOne (events.js:101:20)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/usr/lib/node_modules/azure-cli/node_modules/request/request.js:965:12)

References
[1] https://conuhacks.io/

This repository is for Azure CLI 2.0. The reported issue is for the xplat CLI. Please open the issue at https://github.com/Azure/azure-xplat-cli/issues.


agnoster: speed up git prompt

Problem
On detached-refs, the git prompt is very slow because it uses a command
to output all refs, which takes 32s on the twitter internal git repo.
Solution
Use git-rev-parse instead of git-show-ref to only output the head ref.
Runtime drops to 0.03 seconds.
Note
Interestingly, git-rev-parse isn't slow without the --head arguement so
I'll probably be cooking up a patch for the git team to speed this up
eventually, but it's still pointless to sigpipe git as it walks the
filesystem.

Say, does this slowness on detached-refs also affect the upstream agnoster theme? It's using zsh's own vcs_info support instead of the external git command now.

Nope, upstream is fine.  I think vcs_info uses rev-parse correctly.  I'll close this in favor of that approach.

You might actually want to leave this open, as an interim fix. This a small change, so could be merged pretty quickly. The OMZ agnoster theme is not tightly tied to the upstream, and has diverged significantly. We're currently working on harmonizing them, but that's work-in-progress and will be a bigger change, so will take longer to get through the approval process, and there's no ETA on it.

:+1: /cc @robbyrussell


[ca] Separate server signing root CA from security config root CA

This finishes separating signing functionality from the security config that was started with https://github.com/docker/swarmkit/pull/2262.  This way, the mechanism for updating the root certs in the security config is the same for both managers and workers (via the dispatcher), which makes the root update logic a little less complex.
This also means that the CA server is more standalone, again - it performs its own watch on the store for cluster update changes.

ping @nishanttotla for review, if you have time.  :)
Also cc @jlhawn

Thanks @aaronlehmann and @diogomonica!


nanomq: 0.16.3 -> 0.18.2

Description of changes
Bump. Got tests mostly working, but not enabled by default.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 232475 run on x86_64-darwin 1

1 package built:

nanomq

Is that an approval? :)

Result of nixpkgs-review pr 232475 run on x86_64-darwin 1

1 package built:

nanomq


Allow showing profile pictures on Android

The default content security policy for CCA prevented this, so this
change overrides it.
Fixes #2017

:thumbsup: (sorry about the delay)


Network traces for training new videos

Hi Hongzimao,
I am trying to train Pensieve for another video. However, I am able to get better results than MPC for only 3G network traces. Could you please provide all traces you used for training and testing to produce the results in Pensieve paper? The sample traces you provide look like they are in 3G bandwidth range (0 to 4 mbps). When I train with LTE traces (10-20 Mbps), I am not able to get any better results.
Could you please advise?

Thanks for your interest. For LTE traces with 10-20Mbps bandwidth, you might be able to stream the video at highest bitrate all the time without rebuffering. I would check if Pensieve (and other schemes) is doing just that. Then it makes sense that there isn't any better results to get. In this case, you can try scaling down the bandwidth in the trace (make it in the same range of 3G traces), or scaling up the video bitrate (by using a different video, or simply make the video chunk larger if you only run the simulation).
Also, I would check if the LTE traces have similar size (i.e., number of traces) as the 3G traces and if they share the same kind of variations (is the LTE trace all flat in bandwidth, for example). For machine learning algorithms, it can be hard to generalize when the training dataset is small or does not contain diverse samples (making it hard to generalize to testing dataset).
Hope these help!

Does the sample traces given in the repository cover all traces you used for training? If not, where can I find the rest?

You can try downloading the raw traces from the source: https://github.com/hongzimao/pensieve/blob/master/traces/README.md

I checked this repo and the available traces here for 4g/LTE are actually the traces I was talking about. As you said, these are high bandwidth traces and there is no room to adapt since choosing the highest bitrate is possible. My question is in the original paper results, are these traces included. If so, can you please tell me the ratio of these traces.
Based on my experiments, I could only generate similar results with the traces you shared as sample traces. Are these sample traces the only ones used in pensieve paper?

I think we filtered out the high bandwidth trace from the original source. This is aligned with prior work (e.g., A Control-Theoretic Approach for Dynamic Adaptive Video Streaming over HTTP, SIGCOMM '15). What we did was documented in the our paper section 5.1:
To avoid scenarios where bitrate selection is trivial, i.e., situations where picking the maximum bitrate is always the optimal solution, or where the network cannot support any available bitrate for an extended period, we only considered original traces whose average throughput is less than 6 Mbps, and whose minimum throughput is above 0.2 Mbps.


Have tested traits provide some convenience for always testing, even if the impl didn't use_trait_tests?

There's no obvious convenient way to do this at present.
It's straightforward for #[live_prop_test] to generate wrapper functions that always apply the tests; the question is how to expose them.
One thought is:
#[live_prop_test]
trait MyTrait {
  #[live_prop_test(some test)]
  fn method();
}

// generated:
trait MyTraitAlwaysTest {
  #[live_prop_test(some test)]
  fn method();
}

#[live_prop_test(use_trait_tests)]
impl<T: MyTrait> MyTraitAlwaysTest for T {
  fn method() {T::method()}
}

(although not quite that, because we also want the always-test version to use the original histories, and not double-test if the impl DOES use_trait_tests)
The main open question is, what name to use for the always-test version? Maybe the attribute above MyTrait can specify it, as in #[live_prop_test(always_test_version = "MyTraitAlwaysTest")]? Having the methods have the same name is still awkward… Except actually, if you're trying to use the always-test version, you actually DON'T want to import the original trait, so that you don't accidentally call untested methods. It's a little awkward that the original trait is still the one you'll have to implement, so you'll always have to implement it by an explicit path rather than bringing it into scope

...and it certainly shouldn't be called "always test", since that could imply "don't throttle"


ETA on v2?

Do you have an ETA on v2? It seems that v1 will be completely abandoned... "In the next couple of months".

ETA will be this month. v1 will not be abandoned in the next couple of months. V2 will be released in the next couple of months. V1 will be supported after this release

Mmm okay great, the MoneyBird email about backward compatibility suggests otherwise.
  "

Still true. Bottom line: if you switch your MB account to V2, you'll need to switch your API too. If you stick with V1, API V1 will still work. Of course support for V1 will end someday, buth not in the next couple of months. If in doubt, please contact Moneybird

Any updates on the expected release date?

will work on this in May, expect it to be released by the end of May

@pluijm Any update for V2? :-)

Well, as you might have guessed, I haven't been able to create time to look at the update. At this moment I don't need the update myself, nor does my company. As this library is not much more than a wrapper, you could use a tool like http://phphttpclient.com/ to get the same result.
I'm sorry I can't work on it right now

No worries Sjors! I have looked at other options, seeing as v2 is a very pretty oauth2 api I looked at alternatives such as guzzle.


4.0 release

Where can I find this release ready for Jenkins as ready plugin?

i am sorry, but we do not accept pull requests to the master branch.
the plugin is available from the Jenkins plugin repository, version 4.0 was released and available
https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools

Hi there,
It was a new release today and I have tested it. It fails on publishing in the and of the process. Also the Analysis crashes in thi step with a nasty message.
The odd thing is that all is good except the last publishing step, and that the  error report says that the results.xml file is missing. I look in the folder and it seems like the result.xml file has another number/reference.
The java error message says that the file is not found. I have tested access and Java home settings.
It will be good if you are able to help.
I can send more detailed information. Please use this e-mail on reply<EMAIL_ADDRESS>Kind regards,
Arne
From: Avishai Moshka
Sent: Tuesday, October 20, 2015 5:04 PM
To: hpsa/hp-application-automation-tools-plugin
Cc: arnechristian
Subject: Re: [hp-application-automation-tools-plugin] 4.0 release (#57)
i am sorry, but we do not accept pull requests to the master branch.
the plugin is available from the Jenkins plugin repository, version 4.0 was released and available
https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools
—
Reply to this email directly or view it on GitHub.


UseRequestLocalization() call has to be placed after UseAuthentication()

I've tried to migrate a net core 2.2 web application to net core 3.0 preview 9. I'm having troubles with middleware, where HttpContext.User.Identity.IsAuthenticated always returns false even if the user is authenticated. To ensure that I do not made any mistakes during migration of our application, I even tried to set up a new 3.0 web application project and follow the instructions on this page. In the code below IsAuthenticated is always false.
How do I make this work in 3.0? I have to check authenticated user to resolve the culture based on a SQL query.
                options.RequestCultureProviders.Insert(0, new CustomRequestCultureProvider(async context =>
                {
                    var isAuthenticated = context.User.Identity.IsAuthenticated; // always false in 3.0 preview9
                    // My custom request culture logic
                    return new ProviderCultureResult("en");
                }));

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

ID: d1833676-ff1b-c587-cc9c-81afffa8ef68
Version Independent ID: ad989395-3f49-4d55-521e-cf6fe56281ee
Content: Globalization and localization in ASP.NET Core
Content Source: aspnetcore/fundamentals/localization.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@ryanbrandenburg  please review.

@jcemoller ping me if you don't get a response by end of day 9-11.

@Rick-Anderson spent the last two days trying to find any resolution to this, and I think I found one. It seems that in 3.0, the UseRequestLocalization() call has to be placed after UseAuthentication() call in Configure(). Previously, in 2.2 and also as noted in the documentation under https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization?view=aspnetcore-3.0#implement-a-strategy-to-select-the-languageculture-for-each-request, the recommendation was to place UseRequestLocalization() before UseStaticFiles() and UseAuthentication().
I have yet to find any side-effects by moving the call later in setup, but if this is the new policy it should be reflected in the docs for 3.0. Thanks.

@ryanbrandenburg please review.

@Rick-Anderson any news now for rtm?

@mkArtakMSFT please assign a reviewer.
@ryanbrandenburg  can you review - this looks short but important.

This issue was moved to aspnet/AspNetCore#14391

Seems like this is a technical problem/question rather than a docs question. I've moved it to aspnet/AspNetCore where we track that kind of thing.

@ryanbrandenburg well, could be either or.
The documentation for 2.2 (and current 3.0) states that the following is the correct way to initialize request localization;
(from https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization?view=aspnetcore-3.0#localization-middleware)
var supportedCultures = new[]
{
    new CultureInfo("en-US"),
    new CultureInfo("fr"),
};

app.UseRequestLocalization(new RequestLocalizationOptions
{
    DefaultRequestCulture = new RequestCulture("en-US"),
    // Formatting numbers, dates, etc.
    SupportedCultures = supportedCultures,
    // UI strings that we have localized.
    SupportedUICultures = supportedCultures
});

app.UseStaticFiles();
// To configure external authentication,
// see: http://go.microsoft.com/fwlink/?LinkID=532715
app.UseAuthentication();
app.UseMvcWithDefaultRoute();

This works correctly in 2.2, but not in 3.0 as I wrote above since UseRequestLocalization call must be placed after UseAuthentication.
If this is due to a bug/regression in 3.0 - it seems correct to move to https://github.com/aspnet/AspNetCore.
On the other hand, if this a new requirement to properly configure localization in 3.0 - it's a documentation issue.
Who should I ping to work this out?

UseRequestLocalization() call has to be placed after UseAuthentication()
See https://github.com/aspnet/AspNetCore/issues/14391

@hishamco please review

Sure but I like to know if it's doc or technical issue? I saw @ryanbrandenburg comment and that's why I asked the question again

@jcemoller

If this is due to a bug/regression in 3.0 - it seems correct to move to https://github.com/aspnet/AspNetCore.

Is the 3.1 behavior the same?

Thanks @ryanbrandenburg for the explanation. I think it broke for me when I reordered the middleware during migration to 3.0; changing the order of UseAuthentication made it work again.
Would there ever be a case where UseAuthentication must be placed after UseRequestLocalization? Otherwise I would suggest changing the default order in the documentation, or adding a Note section explaining that it must be changed in order to access the authenticated user. I think it is a common pattern to use the authenticated user's settings stored somewhere (like a database or other store) to set the display language.

@jcemoller , that sounds like a customer experience question that @danroth27 is better suited to handle.
Personally my vote would be no. I think there are so many possible (even likely/common) interactions between our various middle-wares that if we start documenting the ordering changes for all of them it would crowd the documentation. I DO think we could do a better job of helping people understand the middle-ware system in general and how it might affect their scenarios so they can reason about it for their unique app, but I'm not sure what specific changes that would entail.

@ryanbrandenburg I understand this from a maintenance perspective. However, the middleware order is already documented in a certain way in the mentioned page with "The localization middleware must be configured before any middleware which might check the request culture" together with a code section that made me think that UseAuthentication also had to be afterwards in the Startup.cs file. Took me some time to debug, but I learned the importance of middleware ordering the hard way.
Don't know about any specific changes but a generic note section that would say something like "depending on what you need to access in your handler - ensure the middleware is ordered correctly by following the instructions on some_other_page" would have at least given me the pointers to resolve this quicker on my own.


Undesired overflow-x scrolling for #messages div (not present in tutorial screenshots)

The CSS .message-container .name { width: 100%; padding-left: 40px; } is causing an undesired x-scroll on the messages list; due to box-sizing adding the 40px padding to the total width.
Could modify the rule above or add box-sixing: border-box.

Fixed! Thanks for the report!


process didn't exit after disconnect() and no more script running

await orbitdb.disconnect()
await ipfs.stop();

Did you find any solution to this? I stumbled upon the same problem.

Closing. version 1 does not have a disconnect function.


[type: refactor] refactor integration test for waf plugin

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #1975 (ce1bc42) into master (a064481) will decrease coverage by 0.66%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #1975      +/-   ##
============================================
- Coverage     62.59%   61.93%   -0.67%
+ Complexity     4007     3992      -15
============================================
  Files           593      593
  Lines         17295    17355      +60
  Branches       1662     1663       +1
============================================
- Hits          10825    10748      -77
- Misses         5601     5732     +131
- Partials        869      875       +6

Impacted Files
Coverage Δ

...apache/shenyu/plugin/base/cache/BaseDataCache.java
91.17% <0.00%> (-8.83%)
:arrow_down:

...apache/shenyu/web/controller/PluginController.java
5.52% <0.00%> (-2.74%)
:arrow_down:

...enyu/client/tars/TarsServiceBeanPostProcessor.java
33.82% <0.00%> (-55.89%)
:arrow_down:

...ache/shenyu/client/tars/common/dto/TarsRpcExt.java
0.00% <0.00%> (-30.77%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
64.70% <0.00%> (-29.42%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
63.10% <0.00%> (-9.71%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
56.84% <0.00%> (-6.32%)
:arrow_down:

...in/response/strategy/NettyClientMessageWriter.java
69.56% <0.00%> (-4.35%)
:arrow_down:

...henyu/plugin/httpclient/NettyHttpClientPlugin.java
58.00% <0.00%> (-2.00%)
:arrow_down:

... and 4 more

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 a064481...ce1bc42. Read the comment docs.