Error showing the sliders in production

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/s/react-swiper-navigation-forked-59kqt?file=/src/components/Carousel.jsx
Bug description
When I in dev environment, the slider work at 100% but when I make the deploy to github page the slider not work properly.
I let the link where is the deploy InSight1910.github.io .
Expected Behavior
The swiper is showing all slider, what it produces a horizontal scroll.
Actual Behavior
I hope to show a slide and the horizontal scrolling disappears
Swiper version
6.8.1
Platform/Target and Browser Versions
Windows: Edge and Android: Firefox,
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

I clearly see working Swiper on your link
https://user-images.githubusercontent.com/999588/129164709-59a91e89-90ff-496a-a8d4-953ab8a8d55c.mov

Sorry, my bad but the problem is in the resolution of the mobiles, I am very sorry for not specifying that


Python: Making SKFunction.RunThread an outer class

Motivation and Context

It's better to avoid nested classes in Python, so in SKFunction, I move RunThread out of the class. RunThread is needed because we need to wait for the result of an async function that's being run in an existing event loop, and subclassing Thread seems to be the best way to do that.
This also adds python-test.yml to the github workflows.
Description

Move RunThread out of SKFunction since flat hierarchy is more desirable than nested hierarchy in python.
Tried using a local method instead, but to no avail

I had to invoke _invoke_semantic_async with await or async.run, but that could only be done within a Thread because the jupyter notebook spawns an event loop. To wait for the result, you need to use join() but it doesn't return the result, so the local method needed an output parameter that I could mutate. That is, I passed in a list and modified the list inside the method I pass into the Thread. I didn't like that
I tried creating a task inside the existing event loop but couldn't wait for the result without a callback

Ran tests, pre-commit hooks, and notebooks

For python-test.yml:

In this PR, the checks were run because python files were changed.
In this test PR: https://github.com/mkarle/semantic-kernel/pull/2, the python tests were skipped because files in the python directory were not changed.

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

could we simplify further, avoiding the class?
def runThread(code):
    x = threading.Thread(target=code)
    x.start
    x.join
    return x.result

if loop and loop.is_running():
    if self.is_semantic:
        return runThread(self._invoke_semantic_async(context, settings))
    else:
        return runThread(self._invoke_semantic_async(context))
else:
    if self.is_semantic:
        return asyncio.run(self._invoke_semantic_async(context, settings))

Unfortunately, that won't work.
With x = threading.Thread(target=self._invoke_semantic_async), the async function will never be awaited.
But Thread doesn't have a result property, so even with x = threading.Thread(target=asyncio.run, args=(self._invoke_semantic_async,)), we can't get the result.
This works though. You can pass in a list that you modify.
def runCode(code, result):
       result.append(asyncio.run(code)
def runThread(code):
       result = []
       thread = threading.Thread(runThread(code, result))
       thread.start()
       thread.join()
       return result[0]

if loop and loop.is_running():
    if self.is_semantic:
       return runThread(self._invoke_semantic_async(context, settings)

Do you like that better?

@mkarle yes that looks better, using methods and not having an extra class is nicer.
nitpicking, is it possible to write thread.start().join() or somehow combine the 2 lines?
anyhow, pls make this change, love it!

start and join both return None, so I don't think I can combine those lines


browser reload doesn't seem to work

the package doesn't seem to be working at all for me. when I change a file the console says file "reloaded" but the browser never refreshes. I have the livereload browser extension enabled, and have also tried manually adding the js snippet to the html. Am I missing a step?
I'm running Laravel 5.2, laravel-elixir 5.0, and laravel-elixir-livereload 1.1.5

What does your gulpfile look like?
Is it related to the CSS live loading? If it is just a CSS change it
shouldn't reload, the changes should just happen.
On Fri, Feb 19, 2016, 5:37 PM Ammon Casey<EMAIL_ADDRESS>wrote:

the package doesn't seem to be working at form me. when I change a file
the console says file "reloaded" but the browser never refreshes. I have
the livereload browser extension enable, and have also tried manually
adding the js snippet to the html. Am I missing a step?
I'm running Laravel 5.2, laravel-elixir 5.0, and laravel-elixir-livereload
1.1.5
—
Reply to this email directly or view it on GitHub
https://github.com/EHLOVader/laravel-elixir-livereload/issues/17.

OH it is related to the fixes applied for #16.
Pin your dependencies to 1.1.4 instead.
The only change in 1.1.5 was bumping dep to v5.0 on elixir. Although a new version of elixir was released, it hasn't been released in the Laravel package.
I will work on a solution for that.


feat(observability): use envconfig to manage configuration for the observability exporter

Switches the observability exporter configuration to use envconfig
Adds an interface for ObservabilityExporter with a single GenericExporter implementation
Adds a configuration option to the OCAGENT exporter to set the exporter endpoint and control insecure ssl.
Completed a "todo" in the code to make the sample probability rate configurable.
Added a NOOP observability exporter to aid the testing in setup package.

I started this PR by simply adding the single configuration option to set the exporter endpoint, then things kinda spiraled out of control from there. I wanted to keep it simple, but as I dug in to make things configurable, it started to make sense to treat the observability exporter similarly to other providers and interface it out. Happy to hear suggestions on how this could be improved.

/ok-to-test


Sorts ñ among n, rather than after

Tidy now sorts:
 ancla
 andar
 andén
 añejo
 anemia
 ángulo
 anillo

When I think ñ should be read as a separate character that follows 'n' in the alphabet:
 anual
 anular
 anuncio
 añadir
 añejo
 año
 apagar

Working on this in #29. Unfortunately, user will have to specify  locale of "es-ES" for this sorting to work properly.

#29 has now been merged, adding locale support.
To sort Spanish words correctly, users will need to run something like tidy --locale es-ES -o sorted.txt spanish_words.txt, though they likely should also normalize the Unicode: tidy --locale es-ES -k nfc -o sorted.txt spanish_words.txt


Removing FStar.WellFounded.axiom1

See issue #2069
This fix enhances the SMT encoding of inductives to include an additional property on f x << D f for data constructors D of an inductive t whose argument include a ghost or total function returning a t.
All prior uses of the axiom have been removed in the F* tree.
See tests/micro-benchmarks/TestWellFoundedRecursion.fst for several small examples.

Thanks Nik! The changes look quite clean to me, left some comments, but otherwise good to go! Very happy to see all this simplified.

Thanks Nik! The changes look quite clean to me, left some comments, but otherwise good to go! Very happy to see all this simplified.


Feature request: API method to delete a sticker set

The only way to delete a sticker pack as of now is to use @Stickers bot.
Also would be nice to have an API method to rename sticker set.

As far as I remember, removing all stickers from a pack will effectively delete the pack itself

@RememberTheAir no it will not


Typo in the documentation

On this page, the access token's description has two r's in Salesforce:
...
  accessToken : '<your Salesforrce OAuth2 access token is here>',
...

Actually, I am having a hard time reading documentation. (No. I am not meaning two r in Salesforce)
The main example mentioned in https://jsforce.github.io/ for Web-browser itself does not work properly. It leads to INVALID_SESSION_ID. There are no complete examples. Documentation mentioned in https://jsforce.github.io/document/ refers to Node only. So, I really do not know how I can use this in my web-browser.

@CognitiveClouds-Prasad Your issue is entirely different from issue #843. Please open a new one.

Hello Tim, I have to stop now I have a family issue and cannot continue right now
Thanks for all your assistance, too much going on right now.
Mamie
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Tim Mendez<EMAIL_ADDRESS>Sent: Wednesday, April 24, 2019 12:09:18 PM
To: jsforce/jsforce
Cc: Subscribed
Subject: Re: [jsforce/jsforce] Typo in the documentation (#843)
@CognitiveClouds-Prasadhttps://github.com/CognitiveClouds-Prasad Your issue is entirely different from issue #843https://github.com/jsforce/jsforce/issues/843. Please open a new one.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jsforce/jsforce/issues/843#issuecomment-486336624, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCLYORF3BRD6CL66PFYQP3PSCH35ANCNFSM4GIHFWPQ.

Hello, I have to stop now I have some family issue and cannot continue
Right now. Thanks for all your assistance
Mamie
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: CognitiveClouds-Prasad<EMAIL_ADDRESS>Sent: Wednesday, April 24, 2019 1:17:55 AM
To: jsforce/jsforce
Cc: Subscribed
Subject: Re: [jsforce/jsforce] Typo in the documentation (#843)
Actually, I am having a hard time reading documentation. (No. I am not meaning two r in Salesforce)
The main example mentioned in https://jsforce.github.io/ for Web-browser itself does not work properly. It leads to INVALID_SESSION_ID. There are no complete examples. Documentation mentioned in https://jsforce.github.io/document/ refers to Node only. So, I really do not know how I can use this in my web-browser.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jsforce/jsforce/issues/843#issuecomment-486083728, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKCLYOSXNS3UISCBI7HX7T3PR73RHANCNFSM4GIHFWPQ.

PR is here: https://github.com/jsforce/jsforce-website/pull/14

ref: https://github.com/jsforce/jsforce-website/pull/14#issuecomment-2192549145


Feat: add custom Router & useGoBack

Adding useSmartNavigate hook and SmartNavigateLink component, for manage smart navigation with automatic complete of state, thats permits to make smart goBack easily
⚠ This feature need an update of "@testing-library/user-event" version from 13.5.0 to 14.2.0. It was not use in project until now, so that should not cause problem

[x] Custom Router with state injection
[x] Hook useGoBack
[x] Storybook
[x] Use useGoBack in the app

Sonar detects 1 code smell for an unnecessary assertion because that doesn't change type, but if I don't do it there is a typescript error. Because default type is unknown, not any

Related to react-router-dom that we do not use anymore, I'm closing this PR.


shareviewcontroller.h not found.

plugin is installed. when we go to build in xcode we get the error message shareviewcontroller.h not found. any tips and tricks would be appreciated.

I'm having the same problem – did you have any luck with this?


Return volume UUID in the listRouters and listSystemVms APIs

Description
This PR extends the listRouters and listSystemVms APIs to make them return the VM's root volume ID. So that in the future the UI may be extended to use the findStoragePoolsForMigration to migrate VRs and System VMs.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[X] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
This was tested in a local lab, by calling the APIs through Cloudmonkey and checking if the VM's root volume ID was being correctly returned.
Some unit tests were also added.

@JoaoJandre in itself the code looks good but I have a problem with the design; a join dao is supposed to get data from a view and not to manippulate or augment it. This is more in place in the service serving the API command. What made you decide to implement it like this? (in the ..JoinDaoImpl classes)

@JoaoJandre in itself the code looks good but I have a problem with the design; a join dao is supposed to get data from a view and not to manippulate or augment it. This is more in place in the service serving the API command. What made you decide to implement it like this? (in the ..JoinDaoImpl classes)

@DaanHoogland the response is already being built in the DomainRouterJoinDaoImpl, and there are already other similar procedures being made in the same method, such as retrieving the podname (lines 137 through 139).
I understand that ideally this should be done elsewhere, but in that case this whole response builder method would have to be refactored, which would be out of scope of this PR.

@JoaoJandre, can you take a look at the Travis errors?
@blueorangutan package

@GutoVeronezi a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@JoaoJandre why not instead allow listing volumes for routers and system VMs for admin?

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 4151

@JoaoJandre why not instead allow listing volumes for routers and system VMs for admin?

I'm sorry @shwstppr , I didn't understand your suggestion. Could you please elaborate?

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6685 (SL-JID-2341)

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@JoaoJandre why not instead allow listing volumes for routers and system VMs for admin?

I'm sorry @shwstppr , I didn't understand your suggestion. Could you please elaborate?

@JoaoJandre I meant why not allow listVolumes API to list router and systemvm volumes with a new param systemvmid or something. Because with the current approach today we need volume's uuid, then we may need to add volume name or something to show in UI, then volume's current storage pool to assist migration in UI

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6685 (SL-JID-2349)

I was looking through the open PRs and found PR #6491, which already implements what you suggested. With PR #6491 a ROOT admin will be able to list system VM volumes by passing the parameter listall as true. Therefore, there is no need for my PR anymore.
@shwstppr, when thinking about your suggestion another idea came to me; as system VM volumes will be listed via API listVolumes, why not handle system VMs in listVirtualMachines? This way, we could make listVirtualMachines a complete API, handling all types of VMs, and listRouters and listSystemVms would not be necessary anymore.


Addressing hardware checklist critical feedback

@ugurtigli noted that we're getting a lot of repeated requests during inbounds on sizing VMs specifically.
Our baremetal and K8s checklists are slightly generic to this and imply a baseline that may be uncommon within a virtualized context
This attempts to bring together a slightly wider band while emphasizing that our high-watermark is intended for high performance, while the low watermark is a bare minimum.
Staged:

http://<IP_ADDRESS>:9000/staging/VM_PROVISIONING_GUIDANCE/linux/operations/checklists/hardware.html
http://<IP_ADDRESS>:9000/staging/VM_PROVISIONING_GUIDANCE/k8s/operations/checklists/hardware.html

@harshavardhana @eco-minio any concerns before I merge after addressing final feedback?


[Log-analytics] Missing Readme Headers

As part of readme verification, we would want all headers to have required sections. The package operationalinsights/loganalytics is missing the following sections:
Azure .+ client library for JS
^Getting started$
^Key concepts$
^Examples$
^Troubleshooting$
^Next steps$
^Contributing$
Refer issue : #1583
The packages should have following headers:
Azure .+ client library for JS
^Getting started$
^Key concepts$
^Examples$
^Troubleshooting$
^Next steps$
^Contributing$

This is a purely auto generated package and should be exempted from our readme checks. When the code gen gets updated and the package regenerated based on service team's request, it will get the new readme. Can we close this issue?


Suggestion: ability to hide mining/smelters by default

The production overview, especially with the bobs recipes, gets crowded with miners.
Most people don't source raw ore for recipes but only plates.
Suggestion is to hide the rows w/ miners and maybe even smelters from the view by default.

Would be nice to have. A filter to hide or groups things together would be nice to have. I would prefer the default vie to show everything tho.


Fix the date on migration screen

Remove "H:mm" in Date modified and Date created fields

checked

checked


Multiplexing closes connection on auth failed

Description
I'm using the same WS connection to connect to multiple documents.
For document A, I don't have access (I provide an invalid token)
For document B, I do have access.
As soon as I connect to document A, the websocket connection is closed.
Expected behavior
In a multiplexing environment where auth is document based, I'd expect the architecture to be completely independent. Anything I do with document A should be unrelated to what I do with document B and vice versa

Is there any progress on the issue? @janthurau

not yet - this was expected behavior for the multiplexing release. It definitely makes sense to change this though - we're always open for contributions :)


Initial tests for serializers

Codecov Report

Merging #12 (b3c27e3) into master (f7da903) will decrease coverage by 2.22%.
The diff coverage is 87.95%.

:exclamation: Current head b3c27e3 differs from pull request most recent head 4cada6f. Consider uploading reports for the commit 4cada6f to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   61.84%   59.62%   -2.22%
==========================================
  Files           4       11       +7
  Lines         152      592     +440
==========================================
+ Hits           94      353     +259
- Misses         58      229     +171
- Partials        0       10      +10

Impacted Files
Coverage Δ

pkg/types/mapper.go
51.08% <0.00%> (ø)

pkg/serializers/model.go
92.39% <77.77%> (ø)

pkg/detectors/attributes.go
93.61% <93.61%> (ø)

pkg/detectors/adapters.go
100.00% <100.00%> (ø)

pkg/detectors/detectors.go
52.38% <100.00%> (ø)

... and 2 files with indirect coverage changes


Allow cluster wide scan with not fully covered cluster

This pull request includes several changes aimed at improving the handling of cluster-wide SCAN operations in the glide-core/redis-rs/redis library. The changes focus on adding support for non-covered slots, refining documentation, and updating error messages.
Enhancements to Cluster-wide SCAN Operations:

Added a boolean flag allow_non_covered_slots to the cluster_scan and cluster_scan_with_pattern methods to allow missing slots in the cluster. Updated relevant method signatures and documentation accordingly. [1] [2]
Introduced a new constant NO_ADDRESSES_FOUND to signal when no responsive slot addresses are found during scanning.
Updated ClusterScanArgs and ScanState structs to include the allow_non_covered_slots flag. [1] [2]
Modified ScanState methods to handle the new allow_non_covered_slots flag and appropriately manage scan states when no addresses are found. [1] [2]

Documentation Improvements:

Updated comments and documentation to use the term "cluster" instead of "Redis cluster" for consistency. [1] [2] [3]
Refined descriptions for the ObjectType enum to clarify data types.

Error Message Updates:

Revised error messages to use "cluster" instead of "redis_cluster" for clarity. [1] [2]

Issue link
This Pull Request is linked to issue #2436
Checklist
Before submitting the PR make sure the following are checked:

[x] This Pull Request is related to one issue.
[x] Commit message has a detailed description of what changed and why.
[x] Tests are added or updated.
[ ] CHANGELOG.md and documentation files are updated.
[x] Destination branch is correct - main or release
[x] Commits will be squashed upon merging.

I propose to split into multipe PRs - for core and per-client changes to avoid troubles like we had with another feature

I propose to split into multipe PRs - for core and per-client changes to avoid troubles like we had with another feature

Will do core+python for full integration prof, will move node to another.


eigenstrat2vcf.py error

Hi,
I am trying to use your script eigenstrat2vcf.py however I am receiving the error:
Traceback (most recent call last):
File "/bin/mathii_gdc/gdc/eigenstrat2vcf.py", line 67, in
main(options)
File "/bin/mathii_gdc/gdc/eigenstrat2vcf.py", line 56, in main
for i,d in enumerate(data):
TypeError: iter() returned non-iterator of type 'unpacked_data'
And I am using the commands:
python3 -u /bin/mathii_gdc/gdc/eigenstrat2vcf.py -r v44.3_HO_public -i v44.3_HO_public.ind -p v44.3_HO_public_populations -s v44.3_HO_public.snp
I wondered if maybe I am using the incorrect version of Python (3.8.6) and the script is written for an earlier version or perhaps I am using the wrong syntax? I tried with python 2.7.12 but that failed too. Any help to correct this matter would be much appreciated.
Best wishes,
Dean

Yes, sorry you definitely need python 2. Are you getting the same error with python 2.7?

Hi, actually I get the header of the VCF written to standard output but nothing else.
##fileformat=VCFv4.0
##source=eigenstrat2vcf.py
##FORMAT=<ID=GT,Number=1,Type=String,Description="Genotype">
#CHROM  POS     ID      REF     ALT     QUAL

Yes. Ok, so the -i option should be a list of individual IDs that you want to include (not the .ind file) and the -s option should be a list of snp IDs that you want to include (not the snp file). Your population file is correct. The script asssumes that the .geno, .ind and .snp files all have the same root (which you specified with -r). Assuming that you want to include all individuals (in the specified populations) and all snps, then you don't need the -i and -s options.
So I think that:
python2 /bin/mathii_gdc/gdc/eigenstrat2vcf.py -r v44.3_HO_public -p v44.3_HO_public_populations
should do what you want. If you want to further restrict the individuals or snps in your output then you could include the -I or -s options. These options are not heavily tested so please let me know if you see something weird in the output.


Add Top Peers to Player Overview

Added Top Peers to Player Overview and refactored playerPeersColumns.
Resolves issue #429

Anything we're waiting on to merge this, or can I go ahead and merge and close this out?

Looks fine to me.  Up to you if you want to get additional reviews


Adding Unit Tests for Project Functions

I have implemented the following changes as part of this pull request:

[x] Introduced unit tests for the project functions to ensure code reliability and maintainability.
[x] Implemented pair-programming for this task. Kindly decide whose project we should use for testing.
[x] Incorporated the Jest framework for writing the unit tests.
[x] Reviewed each function to determine if it is a pure function. For the functions that manipulate localStorage and the DOM, I have added appropriate mocks.
[x] Created mocks for the storage object to emulate localStorage operations (required only for jest < 24.x; newer versions automatically mock localStorage).
[x] Mocked the HTML to verify the addition and deletion of exactly one  element from the DOM when invoking the add/delete functions.
[x] Grouped the tests using the describe() method to enhance test organization and readability.

Please review the changes and consider approval for me to continue the next part. Thank you!
Best regards,
Zafron. 😺

@emmiiorji Thanks a lot for your review. 👍 😄


python311Packages.pysignalclirestapi: 0.3.18 -> 0.3.21

Description of changes
Diff: https://github.com/bbernhard/pysignalclirestapi/compare/0.3.18...0.3.21
Changelog: https://github.com/bbernhard/pysignalclirestapi/releases/tag/0.3.21

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

5 packages built:

home-assistant-component-tests.signal_messenger
python310Packages.pysignalclirestapi
python310Packages.pysignalclirestapi.dist
python311Packages.pysignalclirestapi
python311Packages.pysignalclirestapi.dist


fix: completion item documentation

Types

[x] 🐛 Bug Fixes

Background or solution
Changelog
修复在没有 resolveCompletionItem 的情况下补全列表的 documentation 丢失的问题

Codecov Report

Merging #284 (b67e4d5) into main (eea3af4) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #284   +/-   ##
=======================================
  Coverage   59.31%   59.32%
=======================================
  Files        1182     1182
  Lines       72674    72675    +1
  Branches    15061    15061
=======================================
+ Hits        43110    43111    +1
  Misses      26941    26941
  Partials     2623     2623

Impacted Files
Coverage Δ

...nsion/src/hosted/api/vscode/language/completion.ts
47.72% <100.00%> (+0.39%)
:arrow_up:

Continue to review full report at Codecov.

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


Backstage not rendering  element in Docs

We're using techdocs-cli to build our .md documentation files and publishing to S3. When viewing the Documentation locally using the spotify/techdocs Docker image our  renders. When we view our docs through a deployed Backstage instance though, the  does not render.
I've been looking into this and I believe it may have something to do with Shadow DOM. We have https://lucid.app as an allowed frame-ancestor in our Backstage app-config.yaml Content Security Policy, and I'm not 100% if that is passed to the Shadow DOM of our built documentation, or if it even needs to be passed?
Expected Behavior

When viewing documentation in Backstage, an embedded Lucid Chart  should render if it is allowed by the CSP.

Current Behavior

When viewing our documentation in Backstage if we inspect element on the Shadow DOM, our
 is present, but the  is missing. We've verified in our S3 and the  is present in the index.html of our built documentation, but for some reason is getting stripped or cut out once it is in Backstage.

Steps to Reproduce

Write some .md file that has an html block similar to the  example above.
View that documentation locally through the spotify/techdocs Docker image
View the same documentation in Backstage (once docs have been built as html, and being pulled in as a Shadow DOM)

Context

Some of our teams have some complex Lucid Charts explaining their processes, infrastructure, etc. We would like to allow them to use Lucid's embeddable  code for their documentation in Backstage.
Your Environment

Backend Backstage Dockerfile Base: node:14-buster-slim
Edit: We are using release-2021-10-13
OS:   Darwin 20.6.0 - darwin/x64
node: v14.8.0
yarn: 1.22.4
cli:  0.7.15 (installed)
Browser: Latest Chrome

Building on ^
Yes I feel like having a way to configure what tags to allow, with the default to not support iframes but possibility to change that could be a path moving forward. And with recommendations why not to support certain tags maybe?

hi @iamEAP , how are you? i saw the issue was put in TODO does it mean you guys will be working on it soon or is it something we can suddenly collaborate on?

We could be a lot better about our project board 😅
In this case, just to note that it's something we are actively thinking about on the team and will likely address soon (or, if you're interested in collaborating/contributing--we have time allotted to discuss/etc)

@iamEAP we are interested in contributing. Do you already have any suggestions?

@dnsaoki2 I'd say @emmaindal's recommendation above would be a great place to start.
Likely introducing a new config key in techdocs whose value is an array of strings representing extra tags to allow? And then modifying the sanitizer Emma linked to use that config.

@dnsaoki2 it would be awesome if you can help, do you want me to assign you to this issue?

@emmaindal yes, please :smile:

closed by #8237


question: how does amqp10 handle proxy?

Hi,
Could someone please explain how the amqp10 handled the proxy situation for apps using amq10 running behind a firewall?
I am interested in any additional proxy configuration needed for amqp10 to work.  Or if it handled automatically and transparent for the app.
Thanks,

Hey, sorry for the slow response. We haven't implemented any sort of proxying functionality for our client - it's a strict AMQP 1.0 client, speaking on 5672/5671 (non-secure/secure).
I'm assuming you mean tunneling to your AMQP server over HTTP/HTTPS standard 80/443 ports, yes? I came at this library initially to use with Azure Service Bus, which doesn't support HTTPS proxying, and my colleague on the library doesn't need it for his clients, so we've never looked into it.
All that said, we're relying on standard Node.js-based TCP/SSL semantics for network connections, so if it's a relatively simple matter of setting up an HTTPS-based connection and then driving AMQP binary traffic over it, it should be possible. I'll mark this as an enhancement request and take a look at what would be required.


[strawberry.ext.mypy_plugin] Fix import error for users who don't use pydantic

This should fix import error in strawberry.ext.mypy_plugin for users who don't use pydantic introduced in latest version. Hopefully the new location of the import is fine.
Error importing plugin "strawberry.ext.mypy_plugin": No module named 'pydantic'

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to David Němec for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)


Add link option to editor toolbar

It would be nice to include an 'add link' option in the toolbar editor.

I'd like to give this a go.

It's all yours @MSoup 😃

Posting an update - I got the link (and image upload) option into the toolbar following the quilt module documentation, but the pop up UI isn't playing well with our current site set up. I'll need some time to figure out how to figure this out before submitting this.

Update2: Finished feature and fixed UI bug. I have no idea how to make the pull request though and googling isn't helping me right now. Maybe I will figure it out soon but I am getting permission denied even if I make a new branch and try to push it.

Thanks for the updates - great job!
Hopefully you'll get things working now per our discussion on Discord.

Closed by #36


Missing declared license

Type: Missing
Summary:
Missing declared license
Details:
Missing license
Resolution:
https://github.com/visionmedia/debug/blob/1.0.3/Readme.md#license
Affected definitions:

debug 1.0.3

@geneh - can you please resolve the conflicts?  Thanks!

Done!


Have an option to set the cwd

See https://github.com/jerrysu/gulp-rsync for "inspiration".
Basically you want to be able to call rsync from an arbitrary location, but tell it to use another location as its "root".

I feel like this is not a responsibility of the library and should be done from outside the library by passing in absolute paths.


Unexpected exception after cuda error

Expected Behavior
dlib.cnn_face_detection_model_v1 should be stateless and its result should not depend on previous calls.
Current Behavior
When using dlib.cnn_face_detection_model_v1 from python bindings it is possible to get an unexpected exception.
I wrote a simple example using face_recognition module from https://github.com/ageitgey/face_recognition. (However I can reproduce it with c++ using dlib directly).
When dlib.cnn_face_detection_model_v1 throws an exception due to too much memory allocation, second usage of this method will always throw. No matter the arguments.
See the example code:
from PIL import Image
import face_recognition

image = face_recognition.load_image_file("image.jpg")

# First execution with upsamples == 0, we do not expect error
try:
    face_locations = face_recognition.face_locations(image, number_of_times_to_upsample=0, model="cnn")
except:
    print("error")
else:
    print("no error")

# Second execution with upsamples == 1, error may occur when too much memory is to be allocated
try:
    face_locations = face_recognition.face_locations(image, number_of_times_to_upsample=1, model="cnn")
except:
    print("error")
else:
    print("no error")

# Third execution with upsamples == 0, we do not expect error
try:
    face_locations = face_recognition.face_locations(image, number_of_times_to_upsample=0, model="cnn")
except:
    print("error")
else:
    print("no error")

# Fourth execution with upsamples == 0, we do not expect error
try:
    face_locations = face_recognition.face_locations(image, number_of_times_to_upsample=0, model="cnn")
except:
    print("error")
else:
    print("no error")

Image used in this code was downloaded from https://thispersondoesnotexist.com/
First call to face_locations returns one face.
Second call fails on my PC due to cuda memory allocation error:
  File "/usr/lib/python3.8/site-packages/face_recognition/api.py", line 100, in _raw_face_locations
    return cnn_face_detector(img, number_of_times_to_upsample)
RuntimeError: Error while calling cudaMalloc(&data, n) in file /home/michal/.cache/yay/python-dlib-cuda/src/dlib-19.19/dlib/cuda/cuda_data_ptr.cpp:58. code: 2, reason: out of memory

This is fine, I can catch this exception.
However next call, which is exactly the same as first one fails too:
  File "/usr/lib/python3.8/site-packages/face_recognition/api.py", line 100, in _raw_face_locations
    return cnn_face_detector(img, number_of_times_to_upsample)
RuntimeError: Error while calling cudaGetLastError() in file /home/michal/.cache/yay/python-dlib-cuda/src/dlib-19.19/dlib/cuda/gpu_data.cpp:114. code: 2, reason: out of memory

My program output:
no error
error
error
no error
Expected output would be:
no error
error
no error
no error
Steps to Reproduce
call dlib.cnn_face_detection_model_v1(image, upsample) with a big image or use big value for upsample argument and catch cuda exception.
call dlib.cnn_face_detection_model_v1(image, upsample) with normal image and get an unexpected exception.

Version: 19.19
Where did you get dlib: Arch AUR repo
Platform:  64 bit Arch Linux:
LSB Version:    1.4
Distributor ID: Arch
Description:    Arch Linux
Release:        rolling
Codename:       n/a
Compiler: gcc (GCC) 9.2.0

Calling clean() does not help. Even destroying dlib objects does not help (all GPU RAM is restored).

Well, clean() is alling cudaFree().  There isn't anything more I could do.  This is a limitation of the CUDA runtime on your platform.  Like in general, I wouldn't expect the CUDA runtime to necessarily be in a great state once an OOM error happens.  Which is another reason why you should structure your application/software/workflow or whatever you have control of to avoid them.


Add Support for Kubernetes Clusters Data Ingestion

Add kubernetes intel module to fetch k8 data.
Add cypher ingestion queries to sync k8 namespaces, pods and services.
Add cleanup queries for kubernetes.
Add ability to iterate through multiple k8 contexts, if provided in kubeconfig.

Looks good. Waiting for @achantavy to take a quick look where I mentioned him :)

Wondering if we're still waiting or do I need to do something from my side?

Looks good. Waiting for @achantavy to take a quick look where I mentioned him :)

Wondering if we're still waiting or do I need to do something from my side?

No, nothing from your end for now. Once Alex reviews those few bits, he'll let you know of any changes.

Hey, sorry for my lateness on this - my workload has been very heavy recently - I'll try to review soon but don't wait on me to approve and merge if you all think the code is good. cc: @marco-lancini can you do a quick pass too?


<EMAIL_ADDRESS>- node 14+, update deps/copyright …

… close #106, close #112

Coverage remained the same at 98.02% when pulling 42122cd695d35458392723ba5e52ae856dd3b09b on rc-0.18.0 into 821b71ae45dfbe29287326571ebe39a862c23860 on master.

Coverage remained the same at 98.02% when pulling 42122cd695d35458392723ba5e52ae856dd3b09b on rc-0.18.0 into 821b71ae45dfbe29287326571ebe39a862c23860 on master.


Model repositories on Hugging Face

Hello 👋
It would be great to have the weights on Hugging Face Hub with a model card that has a note on how to use the model. Drive or GitHub aren't the best place to share weights, so I was wondering if you'd be down. Moreover, you could host a demo built with Gradio on Hugging Face Spaces as well (I can help you out if you need it!)
Would you be interested?

Hi,
Thanks for reaching out. Both sounds great! Please let me know what I should do to move the model on Hugging Face Hub with a model card. Also, if you could help me with the Gradio by sending any pointers, that would be great.
Thanks!

Hiya, thanks a lot for the response!
You can extend your main model class like this. This is a mixin to load the model from a repository (in the same PR you can see how to load a model once it's in a repository as well). The repository will be under your namespace.
The repository can be created and files can be uploaded as shown here. This might seem a lot but overall this would take 5 mins.
Easiest way to create a Space is through Gradio Inferface. You can create an Interface as shown here. Once you build the interface, you can host it as shown here.
A bit of a not so relevant note: I saw you are having all the other models in your repository like OpenAI CLIP. This model exists under transformers as well, and I think it would greatly simplify your codebase and make your life easier to use it from transformers like in here.


[Wiki] Broken link in "Basics: Sources" article

While reading through the page [1] I found the text "supported digital resources" pointing to a non-existing wiki page [2]
[1] https://github.com/KnowledgeCanvas/knowledge/wiki/Basics:-Sources
[2] https://github.com/KnowledgeCanvas/knowledge/wiki/Supported-Import-Types

Fixed. Good catch, and thanks for pointing it out!
The "Supported Import Types" page was removed intentionally, I just forgot to remove any links pointing to it. To be revisited once the feature set is built out more.


Problem with formtools wizard when registrating services

Environment

Python version: 3.7.9
MrMap version: pre 1.0

Steps to Reproduce

Install from scratch
Try to register a service with different browser language settings
Go to the second form page

Expected Behavior
The second form page should be shown - service versions, authentication info, ...
Observed Behavior
AttributeError at /resource/add
'NoneType' object has no attribute 'get'
http 500 error - the variable from post request is not evaluated, independent from session storage (db or file)

Done ;-)

hilarious.. this would mean, that we got maybe problem in other wizards too. How did you test it ?


chore(release): 29.2.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.13%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4763

Relevant Lines:
4886

💛  - Coveralls


Document how to clean the bucket

Resolves #648
Issue #, if available:
#648
Description of changes:
Added an example script to show how to clean the bucket.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@Amri91 Thanks for submitting this. We are currently moving our docs out of this repo and instead will be located here. Can you send this PR to that repo instead so we have everything in on place? This is the file it should be added too.

Closing this here since the PR was submitted to the docs repo


Issue with bonding (active-backup mode)

I am deploying 25 pods with bonded SRIOV VFs, in active-backup mode. At least one of the pods goes into a state, where the Pod is not receiving any traffic from other Pods deployed on the same physical node.
The issue is seen only when the following things happen:

Instead of eth1, eth2 becomes the active interface
Bond0 MAC address is set to eth1 MAC address

[root@test1-pktgen-22 /]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet <IP_ADDRESS>/8 scope host lo
valid_lft forever preferred_lft forever
2: tunl0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
link/ipip <IP_ADDRESS> brd <IP_ADDRESS>
4: eth0@if598: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1480 qdisc noqueue state UP group default
link/ether f2:cb:cf:b2:3e:6d brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet <IP_ADDRESS>/32 scope global eth0
valid_lft forever preferred_lft forever
5: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP group default qlen 1000
link/ether fa:41:ef:aa:5e:4c brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 scope global bond0
valid_lft forever preferred_lft forever
23: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP group default qlen 1000
link/ether fa:41:ef:aa:5e:4c brd ff:ff:ff:ff:ff:ff
151: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP group default qlen 1000
link/ether fa:41:ef:aa:5e:4c brd ff:ff:ff:ff:ff:ff
[root@test1-pktgen-22 /]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth2
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth1
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: fa:41:ef:aa:5e:4c
Slave queue ID: 0
Slave Interface: eth2
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: a2:98:78:e0:01:4e
Slave queue ID: 0
[root@cscale-82-73 ~]# echo "$out" | egrep "test1-pktgen-22|test1-pktgen-18|test1-pktgen-21"
test1-pktgen-18   2/2     Running   0          10m   <IP_ADDRESS>   qct-03
test1-pktgen-21   2/2     Running   0          10m   <IP_ADDRESS>   qct-05
test1-pktgen-22   2/2     Running   0          10m   <IP_ADDRESS>    qct-05
Issue in action
Pod with issue - test1-pktgen-22 on Host qct-05
Ping to Pod on the same host fails
[root@test1-pktgen-22 /]# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
From <IP_ADDRESS> icmp_seq=1 Destination Host Unreachable
Ping to Pod on a different host works fine
[root@test1-pktgen-22 /]# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.150 ms
If I bring down the eth2 interface, which changes the primary slave for the bond0 to eth1, then everything works fine
[root@test1-pktgen-22 /]# ip link set down dev eth2
[root@test1-pktgen-22 /]# ip link set up dev eth2
[root@test1-pktgen-22 /]# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.275 ms
If I disable eth1 and enable it again, the primary slave of the bond0 interface would have changed to eth2 and then things don't work again
[root@test1-pktgen-22 /]# ip link set down dev eth1
[root@test1-pktgen-22 /]# ip link set up dev eth1
[root@test1-pktgen-22 /]# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
For "active-backup" mode, as far as I know, there is no need for any upstream switch configuration since the switch would only see one MAC address which is picked by the Bond interface. Seems like something is not getting set up properly.
Network Attachments
[root@cscale-82-73 ~]# kubectl get net-attach-def -n t001-u000003 test1-pktgen-22-bond0  test1-pktgen-22-net1-0 test1-pktgen-22-net1-1 -o yaml
apiVersion: v1
items:

apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
creationTimestamp: "2020-04-30T22:28:34Z"
generation: 1
name: test1-pktgen-22-bond0
namespace: t001-u000003
resourceVersion: "370830"
selfLink: /apis/k8s.cni.cncf.io/v1/namespaces/t001-u000003/network-attachment-definitions/test1-pktgen-22-bond0
uid: 9ae2acf9-e2bd-4eb2-af0d-c02d93e4729d
spec:
config: '{ "cniVersion": "0.3.1", "name": "bond-net", "plugins": [ { "type": "bond",
"mode": "active-backup", "linksInContainer": true, "miimon": "100", "links":
[{"name": "eth1"}, {"name": "eth2"}], "ipam": { "type": "robin-ipam" } }, {
"type": "tuning", "mtu": 9000, "sysctl": { "net.ipv6.conf.all.accept_ra": "0",
"net.ipv6.conf.default.accept_ra": "0", "net.ipv6.conf.bond0.accept_ra": "0"
} } ] }'
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
annotations:
k8s.v1.cni.cncf.io/resourceName: intel.com/enp59s0f0_iavf
creationTimestamp: "2020-04-30T22:28:26Z"
generation: 1
name: test1-pktgen-22-net1-0
namespace: t001-u000003
resourceVersion: "370733"
selfLink: /apis/k8s.cni.cncf.io/v1/namespaces/t001-u000003/network-attachment-definitions/test1-pktgen-22-net1-0
uid: cb21d2cd-4c5f-4e2d-80b2-64c0932cf87e
spec:
config: '{ "cniVersion": "0.3.1", "name": "sriov-network", "plugins": [ { "vlan":
20, "spoofchk": "off", "type": "sriov" }, { "type": "tuning", "mtu": 9000, "sysctl":
{ "net.ipv6.conf.all.accept_ra": "0", "net.ipv6.conf.default.accept_ra": "0",
"net.ipv6.conf.eth1.accept_ra": "0" } } ] }'
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
annotations:
k8s.v1.cni.cncf.io/resourceName: intel.com/enp59s0f1_iavf
creationTimestamp: "2020-04-30T22:28:31Z"
generation: 1
name: test1-pktgen-22-net1-1
namespace: t001-u000003
resourceVersion: "370784"
selfLink: /apis/k8s.cni.cncf.io/v1/namespaces/t001-u000003/network-attachment-definitions/test1-pktgen-22-net1-1
uid: a95b01f2-ea5f-4d37-b4af-5f60de85a050
spec:
config: '{ "cniVersion": "0.3.1", "name": "sriov-network", "plugins": [ { "vlan":
20, "spoofchk": "off", "type": "sriov" }, { "type": "tuning", "mtu": 9000, "sysctl":
{ "net.ipv6.conf.all.accept_ra": "0", "net.ipv6.conf.default.accept_ra": "0",
"net.ipv6.conf.eth2.accept_ra": "0" } } ] }'
kind: List
metadata:
resourceVersion: ""
selfLink: ""

Multus: v3.4.1
Kubernetes: 1.16.3
SRIOV: Latest Version
Bond CNI: Latest Version

Is there any logs output to dmesg when this happens? Also - since this is repeatedly coming up - is this always related to the same PF or the same VF ? Are all of the VFs configured the same?
Is VF trust set to on? I don't see that in the sriov-cni spec you've posted here.

Yes, trust is not set. I read that only spoofchk should be turned off for bonding to work. I have seen this across different nodes and PFs. I am able to reproduce this issue consistently even with a couple of pods.
All the bond interfaces created set the effective MAC to that of the port eth1 and the active slave is eth1. When I deployed 50 pods, some of them have the eth2 as the active slave. All such pods have issues.
I don't see any obvious errors reported in the dmesg. To reproduce the issue, I just brought eth1/eth2 up and down a couple of times and then I can't ping. Can only ping, if I brought one of the interfaces down.
[root@qct-03 ~]# dmesg -w
[41309.736343] nf_conntrack: falling back to vmalloc.
[41309.739458] nf_conntrack: falling back to vmalloc.
[41309.758780] nf_conntrack: falling back to vmalloc.
[41309.763097] nf_conntrack: falling back to vmalloc.
[41310.925618] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[41310.927515] IPv6: ADDRCONF(NETDEV_UP): cali69bcf3d944e: link is not ready
[41310.927531] IPv6: ADDRCONF(NETDEV_CHANGE): cali69bcf3d944e: link becomes ready
[41310.927951] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[41310.985869] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[41311.007250] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[41311.073085] i40e 0000:3b:00.0: Setting VLAN 20, QOS 0x0 on VF 59
[41311.135219] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[41311.141854] i40e 0000:3b:00.0: Setting VLAN 20, QOS 0x0 on VF 44
[41311.183813] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[41311.194453] iavf 0000:3b:09.3 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41311.195223] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[41311.199527] i40e 0000:3b:00.1: Setting VLAN 20, QOS 0x0 on VF 58
[41311.206330] i40e 0000:3b:00.1: Setting VLAN 20, QOS 0x0 on VF 63
[41311.243514] iavf 0000:3b:07.4 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41311.261647] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[41311.287132] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[41311.301801] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[41311.313353] iavf 0000:3b:11.7 eth2: changing MTU from 1500 to 9000
[41311.382013] iavf 0000:3b:09.3 eth1: changing MTU from 9000 to 1500
[41311.406510] iavf 0000:3b:11.2 eth2: NIC Link is Up Speed is 10 Gbps Full Duplex
[41311.476015] iavf 0000:3b:11.7 eth2: NIC Link is Up Speed is 10 Gbps Full Duplex
[41311.494989] iavf 0000:3b:09.3 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41311.496173] bond0: Enslaving eth1 as a backup interface with a down link
[41311.497772] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[41311.568483] iavf 0000:3b:11.2 eth2: changing MTU from 9000 to 1500
[41311.682072] iavf 0000:3b:11.2 eth2: NIC Link is Up Speed is 10 Gbps Full Duplex
[41311.683144] bond0: Enslaving eth2 as a backup interface with a down link
[41311.743772] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[41311.747372] iavf 0000:3b:07.4 eth1: changing MTU from 9000 to 1500
[41311.861138] iavf 0000:3b:07.4 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41311.862475] bond0: Enslaving eth1 as a backup interface with a down link
[41311.924068] iavf 0000:3b:11.7 eth2: changing MTU from 9000 to 1500
[41312.037933] iavf 0000:3b:11.7 eth2: NIC Link is Up Speed is 10 Gbps Full Duplex
[41312.038826] bond0: Enslaving eth2 as a backup interface with a down link
[41312.303531] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[41312.314580] iavf 0000:3b:09.3 eth1: changing MTU from 1500 to 9000
[41312.315090] iavf 0000:3b:11.2 eth2: changing MTU from 1500 to 9000
[41312.333539] bond0: link status definitely up for interface eth1, 10000 Mbps full duplex
[41312.333547] bond0: making interface eth1 the new active one
[41312.334118] bond0: first active interface up!
[41312.334485] bond0: link status definitely up for interface eth2, 10000 Mbps full duplex
[41312.334558] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[41312.431295] iavf 0000:3b:09.3 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41312.431348] iavf 0000:3b:11.2 eth2: NIC Link is Up Speed is 10 Gbps Full Duplex
[41312.434610] bond0: link status definitely down for interface eth1, disabling it
[41312.434622] bond0: now running without any active interface!
[41312.434845] bond0: link status definitely down for interface eth2, disabling it
[41312.562576] bond0: link status definitely up for interface eth1, 10000 Mbps full duplex
[41312.562584] bond0: making interface eth1 the new active one
[41312.563295] bond0: first active interface up!
[41312.563591] bond0: link status definitely up for interface eth2, 10000 Mbps full duplex
[41312.600694] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
[41312.602509] bond0: link status definitely up for interface eth1, 10000 Mbps full duplex
[41312.602516] bond0: making interface eth1 the new active one
[41312.603020] bond0: first active interface up!
[41312.603371] bond0: link status definitely up for interface eth2, 10000 Mbps full duplex
[41312.603667] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[41312.609301] iavf 0000:3b:07.4 eth1: changing MTU from 1500 to 9000
[41312.609814] iavf 0000:3b:11.7 eth2: changing MTU from 1500 to 9000
[41312.725944] iavf 0000:3b:11.7 eth2: NIC Link is Up Speed is 10 Gbps Full Duplex
[41312.725996] iavf 0000:3b:07.4 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41312.803789] bond0: link status definitely down for interface eth1, disabling it
[41312.803806] bond0: now running without any active interface!
[41312.804086] bond0: link status definitely down for interface eth2, disabling it
[41312.903499] bond0: link status definitely up for interface eth1, 10000 Mbps full duplex
[41312.903507] bond0: making interface eth1 the new active one
[41312.904015] bond0: first active interface up!
[41312.904347] bond0: link status definitely up for interface eth2, 10000 Mbps full duplex
[41786.216958] i40e 0000:3b:00.0 enp59s0f0: NIC Link is Down
[41786.223141] iavf 0000:3b:07.4 eth1: NIC Link is Down
[41786.224719] iavf 0000:3b:09.3 eth1: NIC Link is Down
[41786.252830] bond0: link status definitely down for interface eth1, disabling it
[41786.252839] bond0: making interface eth2 the new active one
[41786.288836] bond0: link status definitely down for interface eth1, disabling it
[41786.288845] bond0: making interface eth2 the new active one
[41836.921209] i40e 0000:3b:00.0 enp59s0f0: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: None
[41836.925907] iavf 0000:3b:07.4 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41836.927486] iavf 0000:3b:09.3 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41836.966335] bond0: link status definitely up for interface eth1, 10000 Mbps full duplex
[41836.987309] bond0: link status definitely up for interface eth1, 10000 Mbps full duplex
[41884.364178] bond0: link status definitely down for interface eth1, disabling it
[41886.664251] bond0: link status definitely down for interface eth2, disabling it
[41886.664266] bond0: now running without any active interface!
[41889.903723] iavf 0000:3b:09.3 eth1: NIC Link is Up Speed is 10 Gbps Full Duplex
[41889.974789] bond0: link status definitely up for interface eth1, 10000 Mbps full duplex
[41889.974797] bond0: making interface eth1 the new active one
[41889.975299] bond0: first active interface up!
[

@svallala on the switch can you change the MTU within the Jumbo frame range i.e. between 1000 bytes to 1500 bytes and let us know if the issue happens. What is the MTU of the NIC - PF and the related VFs set to ?

We have tried 9000 and 1500 and hitting the same issue. VFs are set to the default 1500.

@svallala we don't have Switch to reproduce this issue can you please see if you can reproduce this issue with connecting to another host rather than switch.

@svallala could you look at the solution posted in #14 and see if that solves your problem? The solution leverages PR #15  which adds the failOverMac option in the bond network attachment definition.

@killianmuldoon took your fix and it works well. Thanks

@svallala - glad to hear it. Hopefully this change will be merged in in the next few days.


snowflake_share incorreclty handles 'ALL ACCOUNTS IN DATA EXCHANGE' shares

Provider Version: 0.47.0
Terraform Version: 1.3.2
Describe the bug: Create a share object and attach it to a public listing. At this point, SHOW SHARES LIKE 'MY_SHARE' will return 'ALL ACCOUNTS IN DATA EXCHANGE' in the to column of the result set.
But now the snowflake_share resource will always appear to need updating:
  # snowflake_share.my_share will be updated in-place
  ~ resource "snowflake_share" "my_share" {
      ~ accounts = [
          - "'ALL ACCOUNTS IN DATA EXCHANGE'",
        ]
        id       = "MY_SHARE"
        name     = "MY_SHARE"
    }

If I set accounts = ['ALL ACCOUNTS IN DATA EXCHANGE'] in my terraform code, that then just leads to the error Error: account locators are not allowed - please use 'organization_name.account_name
Workaround: Adding a lifecycle { ignore_changes = [accounts] } to the resource stops it from trying to update the share.

I'm getting the same issue as well.
I've already created this resource and it worked well, but now it breaks and I can't deploy any updates
resource "snowflake_share" "my_share" {     name       = "MY_FREE_LISTING"     accounts = [ "ALL ACCOUNTS IN DATA EXCHANGE"] }
And I get the following error
│ Error: account locators are not allowed - please use 'organization_name.account_name │ │   with module.free_listing.snowflake_share.my_share, │   on ../modules/free-listing/[shares.tf](http://shares.tf/) line 6, in resource "snowflake_share" "my_share": │    6:   accounts = ["ALL ACCOUNTS IN DATA EXCHANGE"]


add custom icons to 'add' menu (latest icons)

Here is the sketch with the latest icons
you will have to re-download, they are brand new as of creating this issue:
https://zpl.io/aXYMxGM

@csherron any way you can make these icons the same dimensions? They are all different sizes and its difficult to line up.

ok can i add whitespace to them? if they're technically not all the same size?

Yep, that will work!

https://zpl.io/aXYMxGM


Use of outdated VK enums

https://github.com/GPUOpen-Tools/radeon_gpu_analyzer/blob/44168d942966ff10e446b00b53574e96e605356f/RadeonGPUAnalyzerGUI/Src/rgPipelineStateModelVulkan.cpp#L677-L678
https://github.com/GPUOpen-Tools/radeon_gpu_analyzer/blob/44168d942966ff10e446b00b53574e96e605356f/RadeonGPUAnalyzerGUI/Src/rgPipelineStateModelVulkan.cpp#L651
VK_ACCESS_COMMAND_PROCESS_READ_BIT_NVX, VK_ACCESS_COMMAND_PROCESS_WRITE_BIT_NVX and VK_PIPELINE_STAGE_COMMAND_PROCESS_BIT_NVX were removed in 1.2.135 (https://github.com/KhronosGroup/Vulkan-Headers/commit/26341b4bf0bfe481de1acb7020cb09ddb24e6225) but persist here.

Hi janisozaur,
A fix for this issue was pushed today. Thank you for reporting this.


zoom-us segfaults at startup

Issue description
zoom-us segfaults at startup, in NixOS. I'd like to undertstand how I could debug this further.
Steps to reproduce
Add the zoom-us package in your /etc/nixos/configuration.nix and:
$ zoom-us
zoom started.
[1]    16172 segmentation fault  zoom-us

Technical details
Output of nix-shell -p nix-info --run "nix-info -m":
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.30, NixOS, 19.09pre177651.aeb464dfd37 (Loris)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2.2`
 - channels(carlo): `""`
 - channels(root): `"nixos-19.09pre177651.aeb464dfd37"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

pinging @flokli to continue the discussion ^

It's useful to get the version of zoom-us you are using. You can get the drv like this:
$ nix-store -qd $(command -v zoom-us)
/nix/store/f4fixp5ylql7fff0w7nyyr2wnqdl75rf-zoom-us-2.7.162522.0121.drv

Also uploading the core file is always helpful (core.*).

@matthewbauer thanks, here's the version of zoom-us:
$ nix-store -qd $(command -v zoom-us)
/nix/store/dnjl9vhal6sxi09l3464angvcjhw0a0i-zoom-us-2.8.183302.0415.drv

But I wouldn't know what the core file is or how to get it!

Here's an useful trace, thanks to @matthewbauer:
$ (cd $(dirname $(readlink -f $(command -v zoom-us)))/.. && nix run nixpkgs.gdb -c gdb ./share/zoom-us/zoom)
GNU gdb (GDB) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./share/zoom-us/zoom...
warning: Loadable section ".dynstr" outside of ELF segments
(no debugging symbols found)...done.
(gdb) run
Starting program: /nix/store/hbjs5m97ppp2ddsqfz6lx28r2glcm7bv-zoom-us-2.8.183302.0415/share/zoom-us/zoom
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/nix/store/681354n3k44r8z90m35hm8945vsp95h1-glibc-2.27/lib/libthread_db.so.1".
warning: File "/nix/store/k4v41as11lyg5rbm80vdxwmbqnbc3a3r-gcc-7.4.0-lib/lib/libstdc++.so.6.0.24-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
	add-auto-load-safe-path /nix/store/k4v41as11lyg5rbm80vdxwmbqnbc3a3r-gcc-7.4.0-lib/lib/libstdc++.so.6.0.24-gdb.py
line to your configuration file "/home/carlo/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/home/carlo/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"
[Detaching after fork from child process 30483]
zoom started.
[New Thread 0x7fffdf9f3700 (LWP 30484)]

Thread 1 "zoom" received signal SIGSEGV, Segmentation fault.
0x00007fffe0f0e4d8 in ?? ()
   from /nix/store/jj2wmjrm1jq2kqyrc2qwmp3zpflmx5x0-qtbase-5.9.3-bin/lib/qt-5.9/plugins/platforms/../../../../../3f7m3k4f12a9bacacgzjq3szsfrpi2zl-qtbase-5.9.3/lib/libQt5XcbQpa.so.5

So it seems that the problem is correlated with the libQt5 library

This might be yet another invocation of https://github.com/NixOS/nixpkgs/issues/37864.
Could you try the workarounds described in https://github.com/NixOS/nixpkgs/issues/38139?

This is a test meant to check whether my environment variables were the problem here:
nix run --ignore-environment -k DISPLAY -k XDG_RUNTIME_DIR -k XAUTHORITY -k LD_LIBRARY_PATH -f channel:nixpkgs-unstable zoom-us -c zoom-us

the --ignore-environment tells nix to ignore all my environment variables, while keeping only the one designated with the -k option, the -f flag specifies the channel, and -c the command that we invoke (the -c flag can be chained).
This command worked for me, so actually the problem was something in my environment variables.
I'll see if the problem is the same you mentioned in your comment, @flokli, but I don't think I'll try the suggested workaround (removing my ~/.nix-profile and ~/.nix-defexpr folder) because the above command a better solution.
Thanks for the help @matthewbauer and @flokli

Ok, closing then.

Let's keep it open. I still want to track down what is causing this.

You can try env QT_PLUGIN_PATH= result/bin/zoom-us to see if it is the same issue.

I'm trying with the latest unstable after the previous version from 18.09 stopped working (due to zoom's server changes), and I'm running into the same problem with a segfault.
Trying the 'nix run' command it takes forever to go through the fixupPhase (100% CPU utilzation), but Zoom works this way. I'm wondering if this would work if I updated my whole system to 19.03...
Running with only a PATH, XAUTHORITY, DISPLAY, and XDG_RUNTIME_DIR (env -i PATH=... zoom-us) fails with the same segfault.
I'm trying to use strace, but I suspect that strace somehow doesn't track children for this process, as the last few thousand syscalls are getpid...

I think this Qt version mismatch bug should no longer happen because of new Qt infra.

Uhm, I think it was really too fast to close this issue. The problem is still there. But anyway, let's consider this to be a duplicate of https://github.com/NixOS/nixpkgs/issues/74273


Locust can't seem to process custom SQLAlchemy ChoiceType?

Describe the bug
I have a model that uses ChoiceType like an enum for my API. When I try to import this model into my locustfile.py, i get errors like this:
from sqlalchemy_utils import ChoiceType
  File "/Users/theo/.local/share/virtualenvs/optis2-data-service-iqC41Vso/lib/python3.9/site-packages/sqlalchemy_utils/__init__.py", line 59, in <module>
    from .types import (  # noqa
  File "/Users/theo/.local/share/virtualenvs/optis2-data-service-iqC41Vso/lib/python3.9/site-packages/sqlalchemy_utils/types/__init__.py", line 42, in <module>
    from .uuid import UUIDType  # noqa
  File "/Users/theo/.local/share/virtualenvs/optis2-data-service-iqC41Vso/lib/python3.9/site-packages/sqlalchemy_utils/types/uuid.py", line 8, in <module>
    sqlalchemy_version = tuple([int(v) for v in __version__.split(".")])
  File "/Users/theo/.local/share/virtualenvs/optis2-data-service-iqC41Vso/lib/python3.9/site-packages/sqlalchemy_utils/types/uuid.py", line 8, in <listcomp>
    sqlalchemy_version = tuple([int(v) for v in __version__.split(".")])
ValueError: invalid literal for int() with base 10: '0b2'

If I remove any imports that involve this ChoiceType enum, locust seems to run fine. Most importantly I want to be able to import a pydantic schema that uses this type, so I can provide the endpoint I'm load testing with a proper object.
Is there anything I can do to support this?

I dont think think this has anything to do with locust, you’re better off asking in some SQLAlchemy forum.


docs-bug(Input): email examples don't use email type

Documentation Feedback
The examples for email input don't use the input type of email. There's a real opportunity to improve the user experiences of those who tend to copy and paste a lot of code from these examples. Would you add type="email" to the <input> field in those examples, both in the overview and in the examples pages?
If using type="email" causes problems, at least please provide at least one code example, or calling out why it doesn't play well with Material Angular.
Affected documentation pages:

https://material.angular.io/components/input/examples
https://material.angular.io/components/input/overview

Impact: Our documentation often refers back to the documentation on this site, however, now we have to include these caveats and instructions on the email forms in order to get the correct keyboard to appear on mobile devices.

@jelbourn , can I take this up?
Do we need to change the input type for all emails?

please consider a P4 - this is a small change with big impact, as it reminds developers to use the right type in order to bring up the relevant keyboards on mobile, improving user experience.

@walvekarnikhil feel free to send a PR


GitPython on OSX 10.7 and Python 2.7 Bug

Not sure what's causing this, but help would be appreciated :)
Exception TypeError: "'NoneType' object is not callable" in <bound method WindowCursor.__del__ of <smmap.mman.WindowCursor object at 0x101547f18>> ignored

I'd really love to see this fixed as soon as possible. I'll pay you money.

I must apologize for being so slow with this, but my life kept me on the edge and made it hard to get started on non-commercial projects again. However, money is not the issue here.
Would it help you if I just merged your fix in ? I wouldn't want to release it though as I intend to get rid of the getrefcount() calls alltogether.
Tomorrow I will move into another office, which keeps the commercial work, so I can, should and must continue on working on my opensource projects - plenty of issues piled up in the past months.

could you merge my fix and state in the commit messages that it is only a temporary fix, until you can refactor and fix things the way you envision?  it would be nice to have a version of smmap out on pypi which didn't raise exceptions, even if the fix is just a temporary hack. the proper solution -- your re-write of things -- could be in a following major release version.

@Autoplectic +100.


NSNumber caused a problem in Linux

In Linux:
let value: Int = 1
print(value as? NSNumber) // It will print nil
but:
let value: Int = 1
print(NSNumber.init(value)) //It will print 1
In SwiftyJSON, the setter of var "object" use "object as? NSNumber" whitch will return nil even the "object" is "Int" caused some problems.

Apple's documentation says:

Swift bridges between the NSNumber class and Swift numeric types, including Int, Double, and Bool.
You can create an NSNumber object by casting a Swift number value using the as operator.

Assuming this is still true (the NSNumber should be NSNumber(value: value) in Swift 3, no?), this looks like a bug in Foundation on Linux.

I am going to close this now. FYI, Swift 4.0 has brought the NSNumber casting, you can checkout the in-process #943 to figure out the test cases about NSNumber.
See https://github.com/apple/swift-evolution/blob/master/proposals/0170-nsnumber_bridge.md
Note:

Considerations for Linux platforms
We do not have bridging on Linux so the as? cast is less important; but if it were to have bridging this would be the desired functionality.


Update Symonfy components to 2.6.6

This fixes a bug in the repeated form element where from 2.6.0 to 2.6.4,
it didn't actually work when the data submitted in the two elements did
not match.

This fixes a bug in the repeated form element where from 2.6.0 to 2.6.4, it didn't actually work when the data submitted in the two elements did not match.
This is the bug: https://github.com/symfony/symfony/issues/12792
This is the fix: https://github.com/symfony/symfony/pull/13198


A question regarding properties of installation object

Description
Hello! I am building an app that would send out notifications of my service to the slack channel that it is installed.
While building my own bot, I was just wondering the differences among object properties I get when a user installs my App. I want to be sure which data I need to save for my App to function correctly.
{
   "team":{
      "id":"valeus123123",
      "name":"valeus123123"
   },
   "appId":"valeus123123",
   "tokenType":"bot",
   "user":{
      "id":"valeus123123"
   },
   "incomingWebhook":{
      "configurationUrl":"valeus123123",
      "url":"valeus123123",
      "channelId":"valeus123123",
      "channel":"#valeus123123"
   },
   "bot":{
      "scopes":[
         "Array"
      ],
      "id":"valeus123123",
      "userId":"valeus123123",
      "token":"valeus123123"
   },
   "isEnterpriseInstall":false,
   "authVersion":"v2"
}

So, my questions are :

What's the difference between bot.userId and bot.id? I understand that every bot has a bot.id, then what's the use of bot.userId?
Does each workspace have a different bot.token value?? From my understanding, A bot.token is used for the bot actions such as posting a message. Is this correct?
Is user.id an id of a user who installed my APP?
What is appId and when would you use appId? I can't seem to find a situation where I would be needed of an appId value

What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[ x ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[ x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[ x ] I've read and agree to the Code of Conduct.
[ x ] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

Hi @esphoenixc, thanks for submitting a few questions here!

What's the difference between bot.userId and bot.id? I understand that every bot has a bot.id, then what's the use of bot.userId?

bot.userId is the user ID of the bot user that your app has in a workspace. bot.id might be a bit confusing but you can look up the bot user's metadata with the bot.id (as bot_id) by calling bots.info API. To identify a bot user or your app's bot user, either can be used for it. One thing to be noted is that, since bolt-js expects the botId exists in an authorize function response, we highly recommend storing both bot.userId and bot.id in your database tables.

Does each workspace have a different bot.token value?? From my understanding, A bot.token is used for the bot actions such as posting a message. Is this correct?

Yes, it does. If your app can be installed into multiple workspaces, each workspace should have a different bot/user tokens.

Is user.id an id of a user who installed my APP?

Yes, it is.

What is appId and when would you use appId? I can't seem to find a situation where I would be needed of an appId value

The app_id (it can be referred as api_app_id in some payloads) is the identifier of your app. You can access your app's configuration page at https://api.slack.com/apps/{app_id}. If you manage only one app and you don't share a database table among multiple Slack apps, perhaps you won't use this ID in your app code.
Is everything clear? If yes, would you mind closing this issue?

Thank you. I will look more into the bot userId and bot.id.

Sorry for asking a queestion after closing it, but I just have a quick question of my understanding of the meaning of a bot user.
So my understanding is that bot.userId is the id of bot users that my App has in a workspace, which means it is the id of the user that is using my App in a workspace? if yes, then what's the difference between bot.userId and user.id which the user.id is the id of the user who installs my App in a workspace. if no, then bot user meaning bot as a user just like any other human slack users in a workspace?

which means it is the id of the user that is using my App in a workspace?

No, it isn't. The user ID is the bot user's ID.

if no, then bot user meaning bot as a user just like any other human slack users in a workspace?

Yes, this is the correct understanding.


osx install

I tried on OSX and none of the widgets rendered:

(reactopya) Bens-MBP-2:reactopya_gallery bendichter$ yarn electron-dev
yarn run v1.17.3
$ concurrently --kill-others "yarn dev" "sleep 2 && cd electron && yarn start"
$ echo "starting development server" && webpack-dev-server --hot
[0] starting development server
[0] ℹ ｢wds｣: Project is running at http://localhost:5050/
[0] ℹ ｢wds｣: webpack output is served from /
[0] ℹ ｢wds｣: Content not from webpack is served from dist
$ electron src
[0] ℹ ｢wdm｣: wait until bundle finished: /?path=sha1dir://fb52d510d2543634e247e0d2d1d4390be9ed9e20.synth_magland/datasets_noise10_K10_C4/001_synth
[0] ℹ ｢wdm｣: Hash: eed0b72db19e1b12e2f2
[0] Version: webpack 4.39.1
[0] Child
[0]     Hash: eed0b72db19e1b12e2f2
[0]     Time: 4848ms
[0]     Built at: 08/06/2019 12:42:22 PM
[0]                    Asset       Size   Chunks             Chunk Names
[0]               index.html  976 bytes           [emitted]
[0]             reactopya.js    151 KiB     main  [emitted]  main
[0]     vendors.reactopya.js   11.9 MiB  vendors  [emitted]  vendors
[0]     Entrypoint main = vendors.reactopya.js reactopya.js
[0]     [0] multi (webpack)-dev-server/client?http://localhost:5050 (webpack)/hot/dev-server.js ./src/index.js 52 bytes {main} [built]
[0]<EMAIL_ADDRESS>1.33 KiB {vendors} [built]
[0]     [./node_modules/react-hot-loader/index.js] 1.24 KiB {vendors} [built]
[0]     [./node_modules/react/index.js] 190 bytes {vendors} [built]
[0]     [./node_modules/strip-ansi/index.js] 161 bytes {vendors} [built]
[0]     [./node_modules/webpack-dev-server/client/index.js?http://localhost:5050] (webpack)-dev-server/client?http://localhost:5050 4.29 KiB {vendors} [built]
[0]     [./node_modules/webpack-dev-server/client/overlay.js] (webpack)-dev-server/client/overlay.js 3.51 KiB {vendors} [built]
[0]     [./node_modules/webpack-dev-server/client/socket.js] (webpack)-dev-server/client/socket.js 1.53 KiB {vendors} [built]
[0]     [./node_modules/webpack-dev-server/client/utils/createSocketUrl.js] (webpack)-dev-server/client/utils/createSocketUrl.js 2.77 KiB {vendors} [built]
[0]     [./node_modules/webpack-dev-server/client/utils/log.js] (webpack)-dev-server/client/utils/log.js 964 bytes {vendors} [built]
[0]     [./node_modules/webpack-dev-server/client/utils/reloadApp.js] (webpack)-dev-server/client/utils/reloadApp.js 1.63 KiB {vendors} [built]
[0]     [./node_modules/webpack-dev-server/client/utils/sendMessage.js] (webpack)-dev-server/client/utils/sendMessage.js 402 bytes {vendors} [built]
[0]     [./node_modules/webpack/buildin/harmony-module.js] (webpack)/buildin/harmony-module.js 573 bytes {vendors} [built]
[0]     [./node_modules/webpack/hot/dev-server.js] (webpack)/hot/dev-server.js 1.59 KiB {vendors} [built]
[0]     [./src/index.js] 1.34 KiB {main} [built]
[0]         + 527 hidden modules
[0]     Child html-webpack-plugin for "index.html":
[0]          1 asset
[0]         Entrypoint undefined = index.html
[0]         [./node_modules/html-webpack-plugin/lib/loader.js!./src/index_template.html] 1.1 KiB {0} [built]
[0]         [./node_modules/lodash/lodash.js] 528 KiB {0} [built]
[0]         [./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 472 bytes {0} [built]
[0]         [./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 497 bytes {0} [built]
[0] ℹ ｢wdm｣: Compiled successfully.
[1] sleep 2 && cd electron && yarn start exited with code 0
--> Sending SIGTERM to other processes..
[0] yarn dev exited with code 1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Could you look in the console of the electron browser (devtools)? On Linux that is done via Ctrl+Shift+I.

recent call last):
  File "/var/folders/cg/mhhypnc14wn9kz5ydllymyc00000gp/T/tmp-reactopya-jhNm6x/entry.py", line 1, in <module>
    from reactopya_gallery import NWBView as Component
  File "/Users/bendichter/dev/reactopya_gallery/reactopya_gallery/__init__.py", line 1, in <module>
    from .PlotlyExample import PlotlyExample
  File "/Users/bendichter/dev/reactopya_gallery/reactopya_gallery/PlotlyExample/__init__.py", line 1, in <module>
    from .PlotlyExample import PlotlyExample
  File "/Users/bendichter/dev/reactopya_gallery/reactopya_gallery/PlotlyExample/PlotlyExample.py", line 1, in <module>
    from reactopya import Component
  File "/Users/bendichter/dev/reactopya_gallery/reactopya/reactopya/__init__.py", line 1, in <module>
    from .component import Component
  File "/Users/bendichter/dev/reactopya_gallery/reactopya/reactopya/component.py", line 7, in <module>
    import numpy as np
ModuleNotFoundError: No module named 'numpy'

haha that'll do it.

Yeah, I guess I need to update setup.py to include the pip dependencies. Although I know sometimes numpy is expected to be installed separately (for certain reasons).
I've tested exclusively on Linux. So I will not be surprised if some of the widgets don't work. But I am guessing the minimal plotly one should work.


Form_helper

Form helper revisited.

There is one issue with this helper:  For the HTML5 output element we would need a class instead of a helper. This is the code to be generated:
`
0

100 +

`
We have to pass the "oninput" attr to form_open() function.

We have this:
HTML5 input types:
color
date
datetime
datetime-local
email
month
number
range
search
tel
time
url
week

HTML5 input attributes:
autocomplete
autofocus
form
formaction
formenctype
formmethod
formnovalidate
formtarget
height and width
list
min and max
multiple
pattern (regexp)
placeholder
required
step

And almost all of them can be passed as attributes to form_input() as $data or $extra. A few attributes don't go as a key = value pair, e.g. "disabled" and "readonly".
So ¿?

And almost all of them can be passed as attributes to form_input() as $data or $extra. A few attributes don't go as a key = value pair, e.g. "disabled" and "readonly".

So which of them are we gonna put in?.

Ideally all of the input types should be included. Another option, and a simpler and more future-proof version, would be to adjust the form_input() method to allow you to specify the type.
As for the attributes, allow them all. No sense restricting. I'm not sure if it would be best to do special checks here, or modify stringify_attributes to check for numeric $keys and create them as single. I think the only place that method is used currently is a couple of methods in the url helper, which would face the same issue, so it's probably safe to do that.

Updated and merged in #298


Release to Maven Central?

Are there any plans to release the artifacts to Maven Central? That would make it more straightforward to integrate the library in other projects.

Hmm, had no plans to do that, but it would be indeed helpful. I will try to handle this in the next days. Thanks for the pointer.

Thanks!

Any updates?  I still don't see it

We separated the ModifiableVariable Module and released it to Maven central. The rest of TLS-Attacker will probably follow soon with the release of TLS-Attacker 2.0.

ok it took us a bit longer than expected :)
https://mvnrepository.com/artifact/de.rub.nds.tlsattacker


Fixed terms boosting in multifield query

Provided fixes for prefix terms, wildcard terms, fuzzy and range terms boosting when parsing a multifield query.
Specific test cases were added in method TestBoostsSimple of TestMultiFieldQueryParser class.

Hi, thanks, but we are not maintaining 3.0.3 anymore at this point, all resources are geared towards the 4.8.0 release and you are welcome to try it out myget.org/gallery/lucene-net

Hi, ok it's clear.
Anyway 3.0.3 branch is very largely used and referenced by other popular libraries (eg. NHibernate.Search), and things take always too time to move forwards...
I'll keep the fork on my github and surely I'll keep on my eyes on new branch.
Have a good work on it!
Thanks!
Emanuele


Not Collecting Data

After installing this template, inserting my computers IP address in to the "Agent Interface" I am not collecting any data and getting en error in "ZBX" that looks like this; Get value from agent failed: cannot connect to [[XXX.XXX.X.XX]:10050]: [111] Connection refused.
Is there a fix to this?
Thanks in Advanced.

Sadly, I do not work with this any longer but maybe someone from the hacktoberfest community knows about that. I will add the label.


Make finaldata.csv chronological

This is somewhat minor since a user will mostly likely open up a csv in excel and have the capability to sort things, however I think another small detail we can add is sorting the data such that the result in finaldata.csv is chronological.
There are a couple of different approaches one could take. One could sort the entries in org_data such that the entries are later written to the csv in order. One could also add some code write_org_data in order to take care of the sorting during the writing phase. Experiment and see which is more elegant.
Make sure to leave a comment if you're going to start working on this so that we can coordinate work!

^This photo is from my most recent running of propublica.py, on 8/4. I noticed that you added some code that got things much closer to chronologically organized. Thank you! We should figure out why these sorts of edge cases still occur and get that solved.


LIBHYDRA-280. Implement STOMP listener as a separate rake task.

https://issues.umd.edu/browse/LIBHYDRA-280

Wrong target branch.


changed metric value to u64

changed type of metric to u64

merging this as a review is not required for the quick fix of the data type.


Add the swapMemorySupport requirement to OOM tests

Add the swapMemorySupport requirement to all tests related to the OOM killer.  The --memory option has the subtle side effect of defaulting --memory-swap to double the value of --memory.  The OOM killer doesn't kick in until the container exhausts memory+swap, and so without the memory swap cgroup the tests will timeout due to swap being effectively unlimited.
Document the default behavior of --memory-swap in the docker run man page.
Signed-off-by: Sean Christopherson<EMAIL_ADDRESS>Related to #17215 and #20627.

Seems good to me.

LGTM

Ok, it has LGTM from @thaJeztah - I'm merging.


Clarify the process of setting up a new working group under ORAS

We need a clarification of the process for creation of a working group under ORAS. The GOVERNANCE.md specifies how maintainers are added but it doesn't specify how subprojects (WGs/repos) are created. We need to have the following answered:

How a proposal for WG should be submitted?
How is the proposal accepted? Who needs to approve the proposal to be accepted? Project maintainers? How many votes? Or just community? How many votes?
What is the criteria for approval of a WG? Does this fit into the project chapter?
What is required for the WG? New repo?
How are maintainers for the  WG (and new repo) selected?
What happens if maintainers in the WG do not participate in the WG? How maintainers are removed from the WG?

There may be others but let's have the discussion in this issue.

minor nit, you're mixing "working group" and "sub-project" terminology. Can we consolidate on "sub-project" as the term?

Thanks, @toddysm
The existing GOVERNANCE: ORAS Org Owners covers who is responsible for adding new sub-projects:

Deciding what subprojects are part of the ORAS project
Deciding on the creation of new subprojects

I've added #36 to clarify the existing sub-projects, which is needed regardless. See issue #23
If we agree to merge that file, we can then define the process to add sub-projects to be opening a PR to that file, asking the ORG maintainers to approve.
There's yet another step which defines how the sub-project maintainers.
This following entry suggest ORAS org owners would approve sub-project maintainer changes. Although we should add text to be more explicit.

When a subproject has no owners the ORAS org owners become responsible for it and may archive the subproject or find new owners

I may need some clarification about what the definition of a subproject is. It may be matter of semantics but for me the output from the workgroup may (or may not) result in sub-project(s) work. My understanding of the purpose of the WG is to investigate the space and specify what needs to be done. While sub-project for me is the place where the "what needs to be done" is done - either a spec or code :) This may be done in the existing sub-projects like the ORAS CLI and the Distribution on in a completely new one if that is needed.
Also, the GOVERNANCE document specifies that the sub-project (not the WG:)) needs to fit into the Vision of ORAS. An outcome from the WG group may be that this something does not fit in the Vision of the project. I looked around and couldn't find a Vision document (the question I brought up in the meeting yesterday although I used the term Charter).
There is still open the question of how the maintainers for the subproject (or WG) are selected. This seems unclear to me from the governance point of view. Also, bearing in mind that for the current proposal none of the folks interested (except you) have any formal role in the ORAS project.
Just some of the questions popping in my mind while thinking about this.

I would propose the following as a process to create a working group under the ORAS project:

Purpose of an ORAS Working Group
ORAS may establish one or more working groups (each, an “ORAS Working Group”) to experiment, validate, and define new capabilities of specifications. Each ORAS Working Group shall have a defined scope of the ORAS Working Group's intended activities and goals. The end result of the ORAS Working Group's work product shall be either:

an update to an existing specification (for example, adding support for a new set of features);
a new specification (for example, creating an specification for a new topical area); or
a new ORAS sub-project other than a specification (for example, creating a reference implementation of an specification).

Any participant in the ORAS technical community may propose a working group to the maintainers. Participants can become maintainers of the Working Group. The maintainers shall maintain a public list of the information required to be included in a working group proposal.
Required information for ORAS Working Group Proposals
ORAS Working Group proposals should contain the following information:

a clearly defined objective and scope of what the working groups aims to accomplish
a list of owners who have agreed to participate in the working group, review progress, report progress back to the ORAS community, and present the results to the maintainers once the working group has completed its objectives
a list of ORAS Projects, non-ORAS projects, or organizations sponsoring the working group and participating in the implementation and use case validation of the work done by the group
a set of project rules which govern how contributions to the working group will be handled and decisions will be made
a working agreement for making progress, which may include weekly meetings, dedicated channels for discussions, or a shared repository
a request for ORAS resources, which may include recurring meetings in the ORAS calendar, ORAS hosted repository, or topic specific communication channels
a name of the working group
Note: It is recommended that the working group is clearly differentiated from the sub-projects by using "Working Group" in the name and wg- prefix for the designated repository if such is required

Proposal for an ORAS Working Group should be submitted as an issue with all the information above.
Requirements for maintainers approval of the working group
ORAS maintainers should review the proposal for a working group and vote for its creation. Working groups can be approved with a super-majority of the maintainer votes. Once the approval is complete, maintainers will provide the requested resources to the working group participants.
Required information for maintainers approval of the working group outcome
When an ORAS Working Group determines that it has completed its initial work and is prepared to request maintainers approval for the outputs as a specification or a sub-project for ORAS, the ORAS Working Group owners will present to the maintainers the following:

the recommended next steps, draft specification, or project content
the validation work which demonstrates real world usability
the set of maintainers who have agreed to carry the work forward

There is no requirement that owners or contributors to the ORAS Working Group will continue to be maintainers for an approved specification or other ORAS sub-project after maintainers approval and release. However, the maintainers will consider it a requirement that any approved specification or other ORAS sub-project has a dedicated and active group of maintainers to continue the work.

I would be happy to submit a PR to add to the governance if the maintainers are in a agreement.
@sajayantony, @shizhMSFT, @SteveLasker, @deitch, @jdolitsky

Thanks @toddysm. I'm in support of documenting this and would welcome a PR. This also helps WG maintainers exit once the proposal is done. Enables a good timeboxed focused effort and an opportunity to include more experts from the community.
I would also like to highlight the challenges that the OCI working group had and even though the full recommendation was not accepted it did land major portions of it. It enabled a lot of members to show up and bring in participation from the community on the specific topic rather than the issues of the whole project that might not apply to WG use cases.
+1 on seeing this governance proposal on ORAS.

LGTM. I'm glad to see new working groups to experiment and explore new areas for oras.

Adding two new org owners @TerryHowe @sabre1041. Do you have any comments about @toddysm's proposal?

LGTM, do you want to make a PR out of this?


Implement certificate based auth for service principal tokens

This PR enables the use of certificates to retrieve a service principal auth token.
It replaces clientSecret on SPT with a field secret which is a struct implementing ServicePrincipalSecret. In Refresh(), rather than just adding the "client_secret" to the form, we call ServicePrincipalSecret's SetAuthValues to modify the form as needed.
ServicePrincipalTokenSecret will add client_secret to the request.
ServicePrincipalCertSecret will add client_assertion and client_assertion_type to the request.
It does introduce two new dependencies to go-autorest:

github.com/dgrijalva/jwt-go
golang.org/x/crypto/pkcs12 (the one Paul just pushed back into x/crypto)

It could be possible to avoid those by:

Reimplementing the few things needed from jwt-go.
Requiring the user to specify a PKCS#1-formatted or PKCS#8-formatted certificate instead of a PKCS#12 certificate. But, most Microsoft stuff seems to prefer PKCS#12 (most relevantly, Azure KeyVault).

I've tested this manually, and also included an example in the PR that starts from scratch and results in listing the subscription's resource groups, after retrieving an OAuth token via JWT signed with the cert's private key.

Looks good to me with one tiny addition: Could you please update the semantic version in the version.go file? I believe this bumps us to 1.0.2. With that I'll gladly accept!

Should it be 1.1.0? Assuming semver, this is a backward-compatible feature addition, rather than just a bugfix. http://semver.org/

I squashed it all and bumped the version to 1.1.0 per semver.


Fixed slides and made the build work

The build was throwing an error when I ran scripts/localbuild.sh so I fixed that and modfiied the formatting of a few slides.

@dspt @lucywyman thoughts?

:+1:

+1