Add tagging for events

fixes #639

Codecov Report

Merging #642 (503f4af) into master (16991fc) will increase coverage by 1.79%.
The diff coverage is 79.16%.

@@             Coverage Diff              @@
##             master     #642      +/-   ##
============================================
+ Coverage     41.80%   43.60%   +1.79%
- Complexity      939      993      +54
============================================
  Files           245      245
  Lines          5054     5082      +28
  Branches        634      643       +9
============================================
+ Hits           2113     2216     +103
+ Misses         2726     2656      -70
+ Partials        215      210       -5

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/seedu/address/ui/EventCard.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...c/commands/schedulercommands/EditEventCommand.java
88.88% <100.00%> (-1.44%)
13.00 <0.00> (ø)

.../logic/parser/schedulerparsers/AddEventParser.java
100.00% <100.00%> (ø)
5.00 <3.00> (ø)

src/main/java/seedu/address/model/event/Event.java
64.86% <100.00%> (+0.97%)
13.00 <0.00> (ø)

...n/java/seedu/address/storage/JsonAdaptedEvent.java
100.00% <100.00%> (ø)
7.00 <1.00> (ø)

...a/seedu/address/model/module/grade/GradePoint.java
76.92% <0.00%> (ø)
6.00% <0.00%> (+1.00%)

...c/main/java/seedu/address/model/module/Module.java
51.72% <0.00%> (+9.48%)
22.00% <0.00%> (+2.00%)

...n/java/seedu/address/model/module/grade/Grade.java
77.77% <0.00%> (+11.11%)
6.00% <0.00%> (+2.00%)

...edu/address/model/module/grade/AssignmentName.java
80.00% <0.00%> (+20.00%)
6.00% <0.00%> (+3.00%)

... and 9 more

Continue to review full report at Codecov.

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


service-binding crd and generated secret not deleted when I disable service-binding crd in argo cd

I subscribe a credential store service in BTP platform, and deploy service instance crd and service binding crd in our k8s cluster follow the below help guide; https://help.sap.com/docs/SERVICEMANAGEMENT/09cc82baadc542a688176dce601398de/0ccebd7cec24411dacd5ad17799534e0.html
After deploy in argo CD, the resource can work well as below, and the serviceinstace and servicebinding are in the same level.

but when I delete service binding crd in argo CD, the resource is not been deleted, this abnormal result is so confused, is it right process?, the resource relation as below:

please share the binding's output after the deletion

there has no error in event logs, and this is what confused me,  below is the  live manifest of service binding after i disable it in argocd, hope it can give some clues
apiVersion: services.cloud.sap.com/v1alpha1
kind: ServiceBinding
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: >
      {"apiVersion":"services.cloud.sap.com/v1alpha1","kind":"ServiceBinding","metadata":{"annotations":{},"labels":{"argocd.argoproj.io/instance":"di-cs-meta--a5440b24"},"name":"cornerstone-btp-credstore","namespace":"dfs"},"spec":{"serviceInstanceName":"btp-credstore-instance"}}
  creationTimestamp: '2022-08-10T09:27:15Z'
  finalizers:
    - services.cloud.sap.com/sap-btp-finalizer
  generation: 1
  labels:
    argocd.argoproj.io/instance: di-cs-meta--a5440b24
  managedFields:
    - apiVersion: services.cloud.sap.com/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:annotations':
            .: {}
            'f:kubectl.kubernetes.io/last-applied-configuration': {}
          'f:labels':
            .: {}
            'f:argocd.argoproj.io/instance': {}
        'f:spec':
          .: {}
          'f:serviceInstanceName': {}
      manager: argocd-application-controller
      operation: Update
      time: '2022-08-10T09:27:15Z'
    - apiVersion: services.cloud.sap.com/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:ownerReferences':
            .: {}
            'k:{"uid":"f44ed9da-065c-42e5-a078-d75c8f638c3a"}': {}
        'f:status': {}
      manager: manager
      operation: Update
      time: '2022-08-10T09:27:15Z'
    - apiVersion: services.cloud.sap.com/v1alpha1
      fieldsType: FieldsV1
      fieldsV1:
        'f:status':
          'f:bindingID': {}
          'f:conditions': {}
          'f:instanceID': {}
          'f:observedGeneration': {}
          'f:ready': {}
      manager: manager
      operation: Update
      subresource: status
      time: '2022-08-10T09:28:47Z'
  name: cornerstone-btp-credstore
  namespace: dfs
  ownerReferences:
    - apiVersion: services.cloud.sap.com/v1alpha1
      blockOwnerDeletion: true
      controller: true
      kind: ServiceInstance
      name: btp-credstore-instance
      uid: f44ed9da-065c-42e5-a078-d75c8f638c3a
  resourceVersion: '1014093490'
  uid: bea752b2-5d7a-4198-846c-d11577b46bca
spec:
  externalName: cornerstone-btp-credstore
  secretName: cornerstone-btp-credstore
  serviceInstanceName: btp-credstore-instance
  userInfo:
    groups:
      - 'system:serviceaccounts'
      - 'system:serviceaccounts:kube-system'
      - 'system:authenticated'
    uid: f1a2392c-5ca0-45fa-841b-bfdb473276d8
    username: 'system:serviceaccount:kube-system:argocd-manager'
status:
  bindingID: c77e7cd2-00f0-4d49-9339-64e3a3e0c6ea
  conditions:
    - lastTransitionTime: '2022-08-10T09:28:47Z'
      message: ServiceBinding provisioned successfully
      observedGeneration: 1
      reason: Created
      status: 'True'
      type: Succeeded
    - lastTransitionTime: '2022-08-10T09:28:47Z'
      message: ''
      reason: Provisioned
      status: 'True'
      type: Ready
  instanceID: 8115de5a-1492-43eb-b825-257a18fc91ef
  observedGeneration: 1
  ready: 'True'


Create init.py

This allows to use the library as a module

Hello, Many thanks for this excellent code
I could read my sensor perfectly.
Could you please give an idea on how to read two sensor connected parallell?

Hello,
You need to change the sensor adress the use the following code with your address:

from mlx90614 import MLX90614
thermometer_address = 0x5a
thermometer_address1 = 0x5b
thermometer = MLX90614(thermometer_address)
thermometer1 = MLX90614(thermometer_address1)
print thermometer.get_obj_temp()
print thermometer1.get_obj_temp()

Thank You very mutch for that , I am looking for how to change MLX90614 adress, but Iam not finding, do have any suggest?

I couldn't find any code to change the sensor address in python, and I don't have this sensor anymore to test it.
If you have any arduino laying around you could change the address on an arduino.

Hello, Tiago
Many thanks to your help. I did what You have recomended and every thing works beutifully
Thank You
Yours
André.

Hello Andre, nice to hear, good luck on your project


Crossmatch different ZTF data releases

Light curve features are now being computed and ingested based on ZTF DR13. The golden dataset's classifications were done using ZTF DR5, and that release's ZTF source ids (_id column in Kowalski) are not necessarily the same as those in DR13. We will have to find or make a crossmatch between these releases if we want to use the latest features to train our model.
(Potentially a separate issue is whether the existing labels should change based on the new data. It is possible the golden classifications are of high enough confidence that the additional data will not change them.)

If the golden set classifications are high confidence, they will most likely not change. But a test at some point will be useful. That is why we carry confidances along.


chore: bdd-spring-1578770575 to 0.0.1

chore: Promote bdd-spring-1578770575 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


Migrate core package 'package-generator' into Atom repo

This issue tracks the steps necessary to migrate the package-generator package into the core atom/atom repository under the packages path:
Migration Checklist
Phase 1 - Prepare repo for migration

[ ] Merge or close existing pull requests on the atom/package-generator repository

Some guidelines for merging vs closing PRs:

Merge when the PR is small, useful, has no merge conflicts with master, and has passing tests
Close when the changes are non-trivial, the PR has conflicts with master, or there are failing tests in CI

If you close a PR, let the user know that we are currently moving the repository over to atom/atom so they should feel free to reopen the pull request there once the package code has been migrated.
Phase 2 - Migrate the package code

[ ] Create a fresh branch off master in your local clone of atom/atom with the name migrate-package-generator-package
[ ] Delete Atom's node_modules, script/node_modules, and apm/node_modules folders if they exist
[ ] Make sure Atom's package-lock.json file is unmodified, use git checkout -- package-lock.json if it isn't
[ ] Clone the atom/package-generator repo into the packages path of your local Atom repository and then delete its .git subfolder
[ ] Delete any unnecessary repo configuration files in the packages/package-generator folder like appveyor.yml, .travis.yml, ISSUE_TEMPLATE.md, and PULL_REQUEST_TEMPLATE.md
[ ] Remove any information from the package's README.md which will be inaccurate after the migration is complete (e.g. CI status badges or contribution instructions)
[ ] Open packages/package-generator/package.json and change the repository field to point to the main repo URL https://github.com/atom/atom
[ ] Open Atom's package.json file to change the following:

[ ] Update the package-generator entry in packageDependencies to reflect the local path of the package:"package-generator": "file:./packages/package-generator",

[ ] Delete the package-generator entry in the dependencies section since it may contain a hardcoded tarball link.  This will help avoid issues in the next step

[ ] Open packages/README.md and perform the following edits:

[ ] Update the second column of the package-generator row to reflect the new local path for the package:[`./package-generator`](./package-generator)

[ ] Delete the following line toward the end of the file:[package-generator]: https://github.com/atom/package-generator

[ ] Run a full Atom build using script/build and verify that there are no unexpected build errors
[ ] Commit the migrated package code and any changes to Atom's package-lock.json files to your branch using this commit message::arrow_right: Migrate core package 'package-generator' into ./packages

Phase 3 - Make sure the package works and send a PR

[ ] Launch the Atom binary in the ./out folder and manually verify that the migrated package is working without any obvious issues.  For example, if you're migrating a color theme, turn on that theme to make sure that it changes the editor colors as expected.
[ ] Open the Chrome Developer Tools console (Ctrl+Shift+I or Cmd+Option+I) and ensure that there are no errors written there.  If there are, add them to this issue and investigate.
[ ] Create a PR against atom/atom with the title "➡ Migrate core package 'package-generator' into ./packages".  For convenience, you may use the following message in your PR body:### Description of the Change

This PR migrates the core [`package-generator`](https://github.com/atom/package-generator) package into `atom/atom`.  See issue #18279 for more information.

[ ] If any CI tests fail, investigate and fix the failures until CI goes green
[ ] Once CI is clean and the PR is approved, merge it

Phase 4 - Archive the package-generator repo

[ ] Move all existing issues from the  package-generator repo to atom/atom using github-issue-mover or a script
[ ] Add a label titled packages/package-generator to the migrated issues so that they can be found easily
[ ] Edit the original package repo's README.md (don't commit directly) to point contributors to the code's new home in atom/atom.  You can use the following text:### This package is now a part of the [core Atom repository](https://github.com/atom/atom/tree/master/packages/package-generator), please direct all issues and pull requests there in the future!

---

[ ] Send a PR to the package-generator repository with the updated README.md so that watchers will be notified of the change.  You do not need to wait for reviews, it can be merged immediately.  You can use the following PR description text:As of **INSERT MIGRATION PR LINK**, the `package-generator` package is now a part of the core Atom repository. This pull request updates `README.md` to reflect that fact. We'll be archiving this repository shortly.

/cc atom/atom#18279

[ ] Archive the package repository by going to its Settings page, scroll down to the "Danger Zone" section and click "Archive this Repository"

Migration is now complete! :tada:

Having core packages in the atom repo could have several benefits. Like dependancy management for the packages. They could share dependencies such that each package would be using the same version of the dependancy.
With the current setup we don’t benefit from shared dependancies. The first benefit that comes to mind for moving the packages to the atom repo is improved dev experience.
On the other hand we also have apm link which also improves the dev experience while working on packages.
Having the core-packages migrated to the atom repo doesn’t make a huge difference.
For now I will close this issue but happy to reopen once we re-organise our repo to allow shared dependencies.


Deployment

Deployment
User Story
As a boot camp student,
I want a Prework Study Guide website,
so that I can review all the information I learned throughout Prework.
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed
WHEN I view the study guide
THEN I see a dark blue header and footer, and four boxes with a shadow
WHEN I open the console in my browser
THEN I can see the four topics I learned listed along with a suggestion on what I should study first
WHEN I visit the website using the URL
THEN I can access my website from any browser

Prework Study Guide webpage has been deployed using the GitHub web hosting service.


selectMode='multi' on only certain rows

Hi everyone!
I have a use case where I have selectMode='multi', but I want to hide the checkbox in the select column for certain rows. On select all, only the ones with checkboxes would be selected. Is that possible? If I understand correctly, multi_filtered does not support this functionality.

No, at the moment it is not possible.
I can imagine the following new setting:
rowSelectable: (row: Row) => boolean
similar to rowClassFunction. This function would produce a Boolean for each row, deciding whether the row is selectable.
Of course, the "select all" would need to only consider selectable rows.
I think it is a good idea - to prevent a performance nightmare - to require from that function that it is pure and cache the result in the row object and only invalidate the cache when the data of the row changes.

Although this feature request is ages old and there was no feedback on the proposal, I think we should finally give it a shot in v3.4.0.

That was a bit too ambitious. The problem is, that we are still carrying the technical debt, that the DataSource implements the selection logic.
That would need to be fixed, first, but this is a breaking change. So unfortunately the topic cannot be addressed before a new major release.


question: how to correctly create print helpers for '<<' explicitly removed in C++20?

Hello!
while project description states that this framework is for C++17 max, could anyone possibly help me with C++20 compatibility issue?
my problem is that in C++20 operator << for printing wide strings (std::wstring, `const wchar_t*, etc) was explicitly removed. In C++17 I could define helper template like
template<> std::ostream& operator<<(std::ostream& o, const std::wstring& what) { o << convert_to_char(what); return o; }

and it worked perfectly. In C++20 this no longer works, as this operator is explicitly deleted, so this template is not even considered. I found that I can partially solve the issue for std::wstring by defining this specialization
namespace boost {
namespace test_tools {
namespace tt_detail {
namespace impl {
template<> std::ostream& boost_test_print_type_impl::operator()(std::ostream& o, const std::wstring& what) const
{
    o << convert_to_char(what); return o;
}
} // impl
} // tt_detail
} // test_tools
} // boost

but this works only for std::wstring, not for any wide string literals in a test like
BOOST_TEST(someWideString == L"expectations");

as I found no way to match R const& r against wchar_t[12] so I can't create a specialization in similar manner.
what need to be done, so BOOST_TEST could understand wide string literals in C++20?
if you need compiler specifics: this is Xcode 15 on macOS

It turned out that I was incorrect in my analysis of the problem: it turned out that old workaround with std::ostream& operator<<(std::ostream& o, const std::wstring& what) works just fine. But with C++20 this workaround no longer works for wide-string literals like L"expectation": when C++ tries to apply td::ostream& operator<<(std::ostream& o, const wchar_t* what) it finds that it is deleted, so conversion to std::wstring is not considered. So obvious fix is to use wstring's, like
using std::string_literals;
BOOST_TEST(someWideString == L"expectations"s);

but is there a way to make BOOST_TEST to work with const wchar_t* ?

So obvious fix is to use wstring's, like
using std::string_literals;
BOOST_TEST(someWideString == L"expectations"s);

but is there a way to make BOOST_TEST to work with const wchar_t* ?

BOOST_TEST does work with const wchar_t* (not necessarily printing the string); it just doesn't work with const wchar_t[N]. BOOST_TEST has special handling for pointers to arrays of characters because pointers might be null. Arrays, on the other hand, rely on the presence of <<.
My current workaround is
BOOST_TEST(someWideString == +L"expectations");


Header: Masked Social Security Number

Example showing both an unmasked and a masked SSN with and explanation and Read.me file

Brett, I am request to have you pull two samples:  Masked SSN and a Specimen Collection Time sample.


Instantsearch.js demo tweaks

Small changes to improve readability and understandability of code.

:+1:

:+1:


ADS Delay

Description
ADS Delay is basically the amount of time it takes to aim down sight for a certain gun. If you look in a game, like COD (Modern Warfare 2019 as a good example), you see that some guns take a longer or shorter time to ADS because of their weight, whether they are lighter or heavier.
Configuration
Scope:
Scope_Delay: <integer / ticks>

Completely overlooked feature...

this would be pretty cool in the plugin

No idea when it was added, but here: https://github.com/WeaponMechanics/MechanicsMain/wiki/Scoping#shoot_delay_after_scope-integer


[B7] Auromancy (Basic Thaumaturgy)

It appears as though the third and final step of the first "Quest" for Auromancy is impossible to complete. I have crafted the "Touch Fire" Focus, however when I craft it, it comes out with 5 damage whereas the Thaumunomicom want's it to have 4.4 Damage and thus does not complete the quest.

I have the same problem on a server. One player can do it, another one can't. Even tried to do it myself by login in with his account but can't do it either

@darklex55 I actually found another issue with the same problem. Apparently it's going to be fixed in the near future. https://github.com/Azanor/thaumcraft-beta/issues/364

@Lightone Harvest Festival. Pack is Renaissance

I'm having this same issue, how do you name the research so that I can use the command to force it?


Noise in script tag

When attempting to parse all Heading tags of certain sites, there's an opening Heading tag in script data, and forceTagsClosed doesn't seem to apply.
How to avoid this H tag parsing in the script tag?
Example site: techcrunch dot com with H2 wrapped in script tags.
find('H2') for the above site example collects garbage.
Amazing script, btw! Please advise.

Hi, I am not author, just using external library "PHP Simple HTML DOM Parser" hosted on Sourceforge
With all bugs or feature requests you should go there https://sourceforge.net/projects/simplehtmldom/


RFP — jPdf Tweak

1. Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts 'RFP — ';
[x] The download URL is public and not locked behind a paywall / login.

2. Package Details

Software project URL: http://jpdftweak.sourceforge.net/;
Binary download, compact version: https://sourceforge.net/projects/jpdftweak/files/jpdftweak/jpdftweak-1.1/jpdftweak-compact-1.1.zip/download?use_mirror=netcologne&download=;
Binary download, normal version: https://sourceforge.net/projects/jpdftweak/files/jpdftweak/jpdftweak-1.1/jpdftweak-1.1.zip/download?use_mirror=netcologne&download=;
Binary download, Windows x64 version: https://sourceforge.net/projects/jpdftweak/files/jpdftweak/jpdftweak-1.1/jpdftweak-windows-x64-1.1.zip/download?use_mirror=netcologne&download=;
Binary download, Windows x86 version: https://sourceforge.net/projects/jpdftweak/files/jpdftweak/jpdftweak-1.1/jpdftweak-windows-x86-1.1.zip/download?use_mirror=netix&download=;
Software summary/short description: open source GUI for PDF editing. jPdf Tweak has many features; I use it for make the pages size standard and renumber PDF pages.

3. Notes
3.1. Dependencies
From official site:

jPDF Tweak requires Java 5 or higher.

It would be nice add Java to Chocolatey package dependencies.
3.2. Difference between versions
From official site:

There are two platform independent binary versions available, a compact one and a normal one. The compact one uses an obfuscator to make the application smaller. So, the compact one has the same features as the normal one. Only if you have problems using the compact one for a task, or if you want to report a bug, try the normal one. The normal version produces better error messages, and - of course - the obfuscator might have bugs as well. If you want to download the libraries separately, there is another version without libraries available (it won't work without libraries).

Thanks.

From official site:

jPDF Tweak requires Java 5 or higher.

It would be nice add Java to Chocolatey package dependencies.

Anyone picking this request up should test if the a java dependency is needed.
Most java applications I have tested in the past (that have been compiled for windows platforms), do not need java as a dependency.

@AdmiringWorm,
Type: Reply
1. General case

Anyone picking this request up should test if the a java dependency is needed.
Most java applications I have tested in the past (that have been compiled for windows platforms), do not need java as a dependency.

Thanks, I will remember this for the future.
2. jPdf Tweak
2.1. Summary
Maybe I don’t know something, but I don't understand, how jPdf Tweak can work without Java.
2.2. Argumentation
jPdf Tweak doesn't contain .exe files.
Files of 64-bit version (I also looked at files from another versions):
D:\SashaPrograms\jpdftweak-windows-x64-1.1>tree /F
Folder PATH listing
Volume serial number is 00000042 1835:AC7C
D:.
│   icon.ico
│   jmupdf64.dll
│   jpdftweak.bat
│   jpdftweak.jar
│   license.txt
│   README.txt
│
├───icons
│       icon128.png
│       icon16.png
│       icon256.png
│       icon32.png
│       icon48.png
│       icon64.png
│
├───lib
│       bcmail.jar
│       bcprov.jar
│       bctsp.jar
│       forms.jar
│       itext.jar
│       jgoodies-common.jar
│       JMuPdf.jar
│
└───manual
        index.html
        screenshot.png
        shot01.png
        shot02.png
        shot03.png
        shot04.png
        shot04a.png
        shot05.png
        shot06.png
        shot07.png
        shot08.png
        shot09.png
        shot10.png

jpdftweak.bat:

@java -jar jpdftweak.jar %*

I don't understand, how possible run it without Java.
Thanks.

When I said

that have been compiled for windows platforms

I assumed that the windows specific archives was compiled to a .exe file, when it isn't you of course need to have java installed.

@Kristinita What is the difference between "normal" version and "windows-x86" and "windows-x84" versions?
I have read "In addition, there are platform dependent binary versions available for Windows (x86/x64) and Linux (x86/x64); these bundle native JMuPdf libraries so that you can use the image export features out of the box." but I didn't how they can been different.
Maybe compact and normal versions need Java and windows versions doesn't need Java as dependency?

Status: Review
https://chocolatey.org/packages/jpdftweak

Status: Published
https://chocolatey.org/packages/jpdftweak
Can be closed.

Status: Published
https://chocolatey.org/packages/jpdftweak
Can be closed.


[Image Layout] How to let image height to be auto?

Hi, I get images from web and you know which are without fixed width or height.
However I want display the image with screen width and let them height auto.

Same issue, React-Native Android, I want put an unknown height Image from uri

+1

Hi there! This issue is being closed because it has been inactive for a while.
If you'd like you can create an issue on Product Pains.
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix. Thanks!


Webpack build broken (blank screen, hard error in console) for external client

Note: since the original filing I have come up with a simplified way to reproduce the problem.
Describe the bug
We rely on an external client that includes the majority of kui plugins.
In attempting to rebase our kui fork to commit 72ad63a3d, we get a broken result (browser screen is blank).
Console: Uncaught SyntaxError: Unexpected token .
Associated Source: main.02dd8eb1e816f9c8a7b4.bundle.js:408506
module.exports = ./es6/crc17_ccitt;

Also nearby are:
module.exports = ./es6/crc17_kermit;
module.exports = ./es6/crc17_modbus;
module.exports = ./es6/crc17_xmodem;
module.exports = ./es6/crc9_1wire;

I don't know if those others would be about to fail also, but I suspect so.  I notice that these five exports are explicitly mentioned in webpack.config.js but I don't know the motivation or the connection to the bug.
Steps to reproduce the behavior
Unfortunately, these steps are laborious because we rely on npm pack of the kui repo components and I can't reproduce the problem using published kui components (if I substitute @dev components, the result works).
Here is the package.json of a test that produces the problem (after building the client, including npx kui-init)
{
  "name": "test-client",
  "version": "0.0.1",
  "description": "Test External Client Support",
  "main"<EMAIL_ADDRESS>  "keywords": [],
  "author": "Joshua Auerbach",
  "license": "UNLICENSED",
  "devDependencies": {
    "@kui-shell/builder": "file:../kui-shell-builder-4.0.0.tgz",
    "@kui-shell/webpack": "file:../kui-shell-webpack-4.0.0.tgz",
    "mocha": "6.1.4",
    "@types/mocha": "5.2.7",
    "@types/node": "12.0.10",
    "electron": "5.0.6",
    "spectron": "7.0.0",
    "typescript": "3.5.2"
  },
  "dependencies": {
    "@kui-shell/core": "file:../kui-shell-core-4.0.0.tgz",
    "@kui-shell/plugin-core-support": "file:../kui-shell-plugin-core-support-4.0.0.tgz",
    "@kui-shell/plugin-openwhisk": "file:../kui-shell-plugin-openwhisk-4.0.0.tgz",
    "@kui-shell/plugin-apache-composer": "file:../kui-shell-plugin-apache-composer-4.0.0.tgz",
    "@kui-shell/plugin-bash-like": "file:../kui-shell-plugin-bash-like-4.0.0.tgz",
    "@kui-shell/plugin-editor": "file:../kui-shell-plugin-editor-4.0.0.tgz",
    "@kui-shell/plugin-grid": "file:../kui-shell-plugin-grid-4.0.0.tgz",
    "@kui-shell/plugin-k8s": "file:../kui-shell-plugin-k8s-4.0.0.tgz",
    "@kui-shell/plugin-manager": "file:../kui-shell-plugin-manager-4.0.0.tgz",
    "@kui-shell/plugin-openwhisk-editor-extensions": "file:../kui-shell-plugin-openwhisk-editor-extensions-4.0.0.tgz",
    "@kui-shell/plugin-tutorials": "file:../kui-shell-plugin-tutorials-4.0.0.tgz",
    "@kui-shell/plugin-wskflow": "file:../kui-shell-plugin-wskflow-4.0.0.tgz"
  }
}

Each of the referenced tarballs was produced from kui at the above commit via
npm pack $PACKAGES/app \
         $PACKAGES/kui-builder \
         $PACKAGES/webpack \
         $PLUGINS/plugin-apache-composer \
         $PLUGINS/plugin-core-support \
         $PLUGINS/plugin-grid \
         $PLUGINS/plugin-k8s \
         $PLUGINS/plugin-manager \
         $PLUGINS/plugin-openwhisk \
         $PLUGINS/plugin-wskflow \
         $PLUGINS/plugin-editor \
         $PLUGINS/plugin-openwhisk-editor-extensions \
         $PLUGINS/plugin-tutorials \
         $PLUGINS/plugin-bash-like \

where the symbols refer to the packages and plugins directories of a kui repo checked out at commit 72ad63a3d.
I am not necessarily expecting you to go through the full process of reproducing the error but if my exposition of the problem gives some clues to what might be wrong, I'm hoping for some help.

There is a simpler way to reproduce the problem now that we are attempting to use stable releases of kui instead building from the repo.   The following package.json is from a test external client built in (nearly) the standard way:
{
  "name": "test-client",
  "version": "0.1.19",
  "description": "Test Workbench Client",
  "main"<EMAIL_ADDRESS>  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "Joshua Auerbach",
  "license": "UNLICENSED",
  "devDependencies": {
    "@kui-shell/builder": "4.5.0",
    "@kui-shell/webpack": "4.5.0",
    "mocha": "6.1.4",
    "@types/mocha": "5.2.7",
    "@types/node": "12.0.10",
    "electron": "5.0.6",
    "spectron": "7.0.0",
    "typescript": "3.5.2"
  },
  "dependencies": {
    "@kui-shell/core": "4.5.0",
    "@kui-shell/plugin-core-support": "4.5.0",
    "@kui-shell/plugin-editor": "4.5.0",
    "marked": "^0.7.0"
  }
}

Concerning the dependencies:

the editor plugin is now required by the core
the "marked" dependency is needed in this minimal config because it is dynamically imported by the core and webpack will barf on its absence.

Non-standard aspects:

I started with the usual kui-init but found I had to delete the test directory in the sample plugin, otherwise I got an error when test support was not found in the core.

Symptom:
The same as reported originally.  It builds, but when uploaded and visited I get a blank screen with the console error as shown above.

re: the editor dependence for external clients. this should be fixed in the 5-series, which now offers a way for plugins to offer an editor API to the core.

re: the editor dependence for external clients. this should be fixed in the 5-series, which now offers a way for plugins to offer an editor API to the core.

Good to know.   Any progress on the main problem?   We are blocked from upgrading our kui dependency because of it.

this should be resolved now


We were making a bad assumption in there about the request IDs

What are you adding in this PR?
Fixup request IDs in LanguageClient. This was breaking hot reload in admin.
Before you deploy

[X] I included a patch bump changeset

Actually that doesn't quite solve our problem. Happens with the lifecycle and one worker. The initialize of the new client happens concurrently with the destroy of the other one. The new client gets the response for the shutdown request (!)


Alturos.Yolo on Windows 10

Hi,
I try to run Alturos.Yolo on

Windows 10
VS2017
Cuda V10.0 + cudnn
and get the exception  Unable to load DLL x64\yolo_cpp_dll_gpu.dll
The yolo_cpp_dll_cpu.dll is running without problems.
Does anyone know this problem? Do I need another yolo_cpp_dll_gpu.dll compiled with cuda V10.0?

Thanks a lot

I currently use cuda 9.2 you must compile self if you nedd cuda 10

Hi Tino,thanks for the fast answer.
I hope I can do it ;-)
ThanksEsther
Am Mittwoch, 14. November 2018, 16:30:33 MEZ hat Tino Hager<EMAIL_ADDRESS>Folgendes geschrieben:

I currently use cuda 9.2 you must compile self if you nedd cuda 10
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi @EstherHD
Could you please share your work for win10?
I'm using win10 too
Having problem like this

oops. Fixed by comment out this

@purnadika have you install c++ 2017 redistributable?

@purnadika I have push a new Version to nuget can you check again?

A newer version? 2017 is the latest version?

Yeah. you know the version like v2017.101 and mine is like v2017.201

On which part you found this version v2017.201 ?

that was just for illustration.
Here's screenshot of mine:

while what I have downloaded is

Can you send me the output of reg query "HKCR\Installer\Dependencies\,,amd64,14.0,bundle"

can you check this command req query "HKCR\Installer\Dependencies\VC,redist.x64,amd64,14.16,bundle"

I have push a new nuget package, i think now its works 2.2.4 (available in few minutes)
https://www.nuget.org/packages/Alturos.Yolo/2.2.4
If it works for you now, I would be happy to receive a star for the project

great! works like charm

@purnadika : I am facing same problem, I am new to this. Can you please share the steps how did you fix this?


'tilewidth' must be >= 1 and <= genome size

Dear developer,
I encountered an error while plotting data with the tool. The error message is: "[pafToBins] Binning PAF alignments, binsize=10000bpError in GenomicRanges::tileGenome(seqlengths = aln.len, tilewidth = binsize,  :
'tilewidth' must be >= 1 and <= genome size", I tried setting the binsize to 1000 and 10000, but the issue persists. Do you have any suggestions for resolving this?
Thanks in advance!
Best,
PF

Can you please share with me an example paf file that was giving the error so I can see how to fix this?

hi, thanks for your quick reply!
Somehow, it works now.
i added more broad 'perc.identity.breaks', then it worked.
but i can still show you my paf file here, just for some one has same issue like me:
`> head(paf.46.43)
A tibble: 6 × 13
q.name    q.len  q.start    q.end strand t.name    t.len  t.start    t.end n.match aln.len  mapq cg

1 chr_03 14382887   467417   523422 +      chr_03 18850220    10163    74517   48039   70432    60 201M2D266M1I16M1D187M1…
2 chr_03 14382887   696336   748339 +      chr_03 18850220   246022   301047   46797   56648    60 22M1I601M3D29M1D22M1I3…
3 chr_03 14382887  1596382  1636183 +      chr_03 18850220  1137233  1190035   34551   55352    60 387M4D46M3I227M271I433…
4 chr_03 14382887  2022169  2062106 +      chr_03 18850220  2636466  2670606   29721   42816    60 91M2I416M717D200M1D64M…
5 chr_03 14382887 10255710 10287409 +      chr_03 18850220 13525588 13563582   28839   38949    60 59M3D62M1I20M3D18M2D10…
6 chr_03 14382887 13982802 14008903 +      chr_03 18850220 18243390 18277170   24537   34153    60 108M1D289M1I356M7D282M…my command for plot isplotMiro(paf.table = paf.46.43, binsize = 10000,
perc.identity.breaks = c(70, 85, 90, 95))`.
Best, PF


"Ponor" is listed in the dropdown menu when searched.

Description : When you will type "Ponor" in the search bar you should see it in the dropdown menu correctly spelled and with locality information.
Precondition : The website is up and running

Step 1
Type "Ponor" in the search bar.
Expected results:
The dropdown is listing "Ponor" as the first location in the dropdown menu.


close problem

Problem
I have a problem,UsbDevice.close(), App crashed.  error log like this:

My Code like this:

This happens if you close the USB device twice.

thank you,I am trying...


Does it support converting NCCL to RCCL?

Does it support converting NCCL to RCCL?

Currently, it doesn't support NCCL, but it is in the plans.


Fix Content-MD5 header for s3transfer

Overview
This is a continuation of #1985 to resolve #1979. We're adding two additional tests to prevent future regression with empty bodies, and adding some more info on the underlying issue.
Bug
While the initial PR was addressing a lack of Content-MD5 headers being added for empty files going to s3, the bug is little more subtle. Currently, using the low level API for PutBucket will ensure all input, regardless of length, is transformed into a file-like object. When this is passed to our MD5 checksum function, it will always be True and get the header added correctly. These always evaluate to True because bool resolves "truthiness" to be if the file-object exists or not.
The bug enters when the higher level s3 APIs are being invoked like s3 sync in the AWS CLI. This replaces our standard file-like wrappers (StringIO, BytesIO) with s3transfer's ReadFileChunk. Due to s3transfer implementing __len__ on what would otherwise appear to be a file-like object, we now get different criteria for what makes it truthy. bool will choose __len__ > 0 as being more specific than if the file exists. That broke our previous assumptions on what would be coming through to conditionally_calculate_md5.
Outcome
We probably should make ReadFileChunk adhere closer to the file-like object spec, but at this point it would be a backwards incompatible change. I think the original proposal from @wimglenn is the safest bet to make things operate as expected.

Codecov Report

Merging #2221 (b263f6e) into develop (60d2bf7) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop    #2221      +/-   ##
===========================================
- Coverage    98.23%   98.23%   -0.01%
===========================================
  Files           58       58
  Lines        10852    10848       -4
===========================================
- Hits         10661    10657       -4
  Misses         191      191

Impacted Files
Coverage Δ

botocore/handlers.py
96.35% <ø> (-0.04%)
:arrow_down:

botocore/utils.py
97.73% <100.00%> (ø)

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 60d2bf7...b263f6e. Read the comment docs.


Suppress warning output in Get-DbaBackupHistory when using LastFull

fixes #5263

only impacts output, not functionality, so merging 👍  also

also, the failure was related


Deduplicate muxer for a given same stream.

Not sure if this causes any problems I can't think of, But it sure fixes this problem as well as the new unit test (comment out line 248 to see it fail)
This would make this PR unnecessary too.

You should not return from a constructor, creates weird edge-cases. The Protomux.from helper exists for exactly this

You should not return from a constructor, creates weird edge-cases. The Protomux.from helper exists for exactly this

Fair enough, I was trying to cover cases where someone constructs Protomux with new, like Hypercore.createProtocolStream and obsolete the PR in corestore
Fixed now.

@Nazeh we should change that to be Protomux.from, the one Hypercore one

Cool solution. In general we define the userData field so a stream can opt-in to modules doing this, vs force injecting it. Added a comment about that.


CLI outputs invalid JSON when detecting multiple targets

Steps to reproduce:

Create a folder foo.
Create foo/1.scss and foo/2.scss with #foo { color: red })
Run sass-lint -q -v -f json foo/*.

What did you expect to happen?
It to print a single array.
What actually happened?
It prints numerous arrays, resulting in invalid json if you try to parse the complete stdout.
Example:

Note: I think I found the issue in bin/sass-lint.js. I currently have a commit in my fork where I did a quick fix to get things moving for the project I'm working on.
Hope this helps, and thanks for the awesome project.  :-)

@brentlintner thanks for this. I really really don't know how this has gone under the radar for so long or how we've never noticed it! Unfortunately due to our lack of time over the last year or so this has gone unfixed too.. We are going to be bringing out a v2 very shortly, mainly to deprecate older node versions and this fix will be part of that update as im worried that with the lack of other people reporting this as an issue they've worked around it or just not noticed either..
It explains a problem we noticed in the gulp plugin though but which we didn't have time to investigate properly...

@DanPurdy no problem! Kudos on the new release as well, and thanks. :-)

:tada: This issue has been resolved in version 1.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


noted the issue still exists. Heres the test repo https://github.com/giang12/moldecormixinsbug

noted the issue still exists. Heres the test repo https://github.com/giang12/moldecormixinsbug
Originally posted by @giang12 in https://github.com/ColonelBundy/moleculer-decorators/issues/15#issuecomment-486401046

I will fix it today!


Tabs in cards not working

Tabs in cards are not working in new v.1.0.0.
I have tested on starter template.
Let me know if you need further information.
Thanks for your help.

Can you post a codepen reproducing this issue?

Sure!
https://codepen.io/jlfernandez83/pen/pVEbRY

You missed initializazion?
I added jquery and materializa css/js and it works

That's true, Michele.
I changed jquery initialization to M.AutoInit(), as jQuery is not a dependency anymore.
https://codepen.io/jlfernandez83/pen/pVEbRY
Anyway, I think it should be specified in docs how to exactly init just cards, as in other components.
http://materializecss.com/cards.html
For example, the initialization of carousel element is specified in docs to be:
var elem = document.querySelector('.carousel');   var instance = M.Carousel.init(elem, options);
Am I right? What do you, guys, think?

It works nicely, well done.

Cards do not need initialization, they don't use js unlike tabs.

M.AutoInit(); works but I personally would use the specific version for the tabs you want to init only, the generic init may interfere with others materialize components.

var elem = document.querySelector('.tabs');  var instance = M.Tabs.init(elem, {});

hello and if you want to instantiate all the elements instead of one by one, how would the code be? help, I'm new to this, in js and materializecss, thanks

  <script type="text/javascript">
    document.addEventListener('DOMContentLoaded', function() {
      var instances = M.AutoInit();
      });
  </script>

Así inicializo todos los componentes yo, espero te sirva y si estoy mal corrijanme.

Hi, I am trying to initialize all the elements using the syntax above, but it only works in firefox and not chrome. What might be causing this behavior. Kindly assist, thanks.

Thanks for your time Michele, it seems I was looking just the "cards" page ("Tabs in Cards" section) so I didn't realize I had to initialize tabs in js. That was causing the problem.
Cheers!

This is the same issue I had. Since this issue is still open, should I add the solution that @MicheleLucini provided to the docs?

var elem = document.querySelector('.tabs'); var instance = M.Tabs.init(elem, {});

thx so much!

Hi All,
Regarding the card tabs the documentation is still missing the initialization step. I wrecked my brains before I was able to find this post. However, although the mentioned initialization worked for one instant of the card with tabs, when creating another it did not work. That is when creating two identical cards with tabs, the first works ok but strangely the second does not!
Does that mean each instance require its own initialization ?!!!

Apparently each instance does need its own initialization. I was able to finally resolve my issue by applying a different id to each ul tag with class="tabs" then initialize each based on the id.
var tabElems1 = document.querySelector("#tabs1");
var tabInstances1 = M.Tabs.init(tabElems1, {});

var tabElems2 = document.querySelector("#tabs2");
var tabInstances2 = M.Tabs.init(tabElems2, {});

This is work, but the docs did not say to include this
<script>
       $(document).ready(function () {
            $('.tabs').tabs();
        });
</script>

This is work, but the docs did not say to include this
<script>
       $(document).ready(function () {
            $('.tabs').tabs();
        });
</script>

thank you @NMNaufaldo, it helpful to me

Thanks @MicheleLucini your answer helped me a lot!


"Version-6.5.2" release

Release Notes: https://x-team-internal.atlassian.net/projects/XP/versions/10139
Release branch content:

Switch RichTextEditor with InputField textarea on Notes (#565)

P.S. Do not merge until approved by product team!

Closing in favor of https://github.com/x-team/xp-ui/pull/567


#2096 backport to 0.14

Created the v0.14_release branch from the 0.14.0 tag, this MR will merge into that branch.

ugh all the CI issues apply here as well ofc :(
Probably easier to have someone else do a manual build too, its only the parser so it shouldn't be an issue.

oh stupid, without CI we won't have the release build so no binaries  (╯°□°）╯︵ ┻━┻
Guess I have to backport all CI fixes to 0.14 as well


skylib: Move non-distro targets to a separate presubmit config

As of #74 the federation references a skylib release instead of the entire repository. However, the presubmit failed (as expected) since some test targets cover files that are not part of the distribution.
The present commit moves these tests to a separate file so that they can be tested again once bazelbuild#78 is solved.
Tested: https://buildkite.com/bazel/fwes-federation-pipeline/builds/14

This PR will break CI due to the removal of test target exclusions. However, https://github.com/bazelbuild/bazel-federation/pull/74 will fix that.


[Core] Prompt for interactive authentication for all silent authentication failures

Related command
az login
Description
When WAM is enabled, AADSTS error code is no longer included in error_description property of the MSAL error (https://github.com/AzureAD/microsoft-authentication-library-for-python/issues/698). MSAL.PY also has no clear indicator for InteractionRequired (https://github.com/AzureAD/microsoft-authentication-library-for-python/issues/701).
So, we no longer detects AADSTS50076 and tell the user the error is caused by MFA. Instead, we unconditionally prompt for interactive authentication for all silent authentication failures.
Testing Guide
az login with an account that requires MFA for non-home tenants.
Output:
Silent authentication fails for tenant 54826b22-38d6-4fb2-bad9-b7b93a3e9c5a 'AzureSDKTeam': (pii). Status: Response_Status.Status_InteractionRequired, Error code:<PHONE_NUMBER>, Tag: 557973645
The following tenants require interactive authentication. Use 'az login --tenant TENANT_ID' to explicitly login to a tenant.
54826b22-38d6-4fb2-bad9-b7b93a3e9c5a 'AzureSDKTeam'

Core

Another benefit we get is that we now not only handle AADSTS50076:

AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access 'xxx'.

but also other MFA-related errors which Azure CLI currently can't handle:

AADSTS50079: Due to a configuration change made by your administrator, or because you moved to a new location, you must enroll in multi-factor authentication to access 'xxx'.

AADSTS54008: Multi-Factor authentication is required and the credential used (Certificate) is not supported as a First Factor. Contact your administrator for more information.

Azure PowerShell relies on you must use multi-factor authentication to access to detect AADSTS50076 (https://github.com/Azure/azure-powershell/pull/14977):
https://github.com/Azure/azure-powershell/blob/b15c6bb3a5457e071d1573587b35a1309f9811ca/src/Accounts/Authentication/Factories/AuthenticationFactory.cs#L189
                    //There's no official error message for requiring MFA permission, so have to compare UGLY error message
                    if (msalUiRequiredException.ErrorCode == "invalid_grant" &&
                        msalUiRequiredException.Message.Contains("you must use multi-factor authentication to access"))

There was even a discussion on relying on AADSTS50076: https://github.com/Azure/azure-powershell/pull/14977#discussion_r631660881

Related Azure PowerShell PR: https://github.com/Azure/azure-powershell/pull/24792


go-get-kubernetes.sh: make replace statement pruning optional

Not pruning is safer because it allows adding k/k to a project at a
later time. Therefore adding all replace statements is the default.
A new flag can be used to clean up if desired. It's just a cosmetic
change because unused replace statements are ignored by Go.
/assign @jsafrane
/cc @msau42

/release-note-none

It's generally discouraged to import k/k packages directly.

I know, but sometimes it cannot be avoided.
CSI driver developers who want to implement their own E2E test suite and reuse existing support code for that (k/k/test/e2e/framework, the storage test suites) have no choice, they have to import k/k. The effort to move the framework into staging has been abandoned and for the storage test suite that never has been the goal.
We don't have to make it harder by removing features that already existed.

/retest

/remove-lifecycle stale

/remove-lifecycle stale

I checked output with -p and without it, it works as described in the help text and does not make go.mod worse.
/lgtm

I tried to run the script for 1.26.0
./release-tools/go-get-kubernetes.sh -p 1.26.0-rc.0

But it failed with:
go: inconsistent vendoring in {package path}/external-attacher:
	k8s.io/api: is replaced in go.mod, but not marked as replaced in vendor/modules.txt
	k8s.io/apimachinery: is replaced in go.mod, but not marked as replaced in vendor/modules.txt
	k8s.io/client-go: is replaced in go.mod, but not marked as replaced in vendor/modules.txt
	k8s.io/component-base: is replaced in go.mod, but not marked as replaced in vendor/modules.txt
	k8s.io/csi-translation-lib: is replaced in go.mod, but not marked as replaced in vendor/modules.txt

	To ignore the vendor directory, use -mod=readonly or -mod=mod.
	To sync the vendor directory, run:
		go mod vendor

ERROR: could not obtain package list, both of these commands failed:


New Feature: optionally pass an array or string instead of mapStateToProps

Currently I am using recompose in every place where I am using connect. my mapStateToProps is essentially always:
connect(({apples, bananas, carrots, daikon}) => ({apples, bananas, carrots, daikon}))

I would like to get your thoughts on passing:
connect(["apples", "bananas", "carrots", "daikon"])

Is this an idea worth implementing?
Is there an existing way to cut this extra code out?
Am I just super off on this pattern?

You can also use the package only():
connect(obj => only(obj, 'apples bananas carrots daikon'))

I am using an even simpler way:
connect(state => state)

I was going to make the same suggestion as @meChrisReed but found this issue saying basically that it's not wanted as a core functionality react-redux.

@franciscop-invast : that's almost always a bad idea, because of performance.  Your component will now re-render every time an action is dispatched and the store is updated, rather than just when the data this component actually needs has changed.

@markerikson woah, that is awesome to know, than you! I have a fairly thin state tree (but deep) so I haven't seen any difference so far, but I'll definitely keep it into mind for the future.


Bump to Autorelease 0.3.2

Autorelease 0.3.2 was released back in August. The main improvements are in blocking Autorelease workflows from running on forks (see #1061, #1062) and in better information on the vendored files (to ensure that the status as vendored from Autorelease is more clear).

This is ready for review and comment. I will leave it open for at least 24 hours, merging no earlier than Mon 08 Nov 15:00 GMT (10:00 my local).


[Monitor OpenTelemetry] Add Winston Log Instrumentation

Packages impacted by this PR
@azure/monitor-opentelemetry
Adds support for winston log instrumentation.

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/monitor-opentelemetry


Pages don't change on windows phone

The url changes but the pages don't. I tested the kitchen sink demo

The HN demo keeps the loading icon forever

Confirmed on Nokia Lumia 635.
Hacker News indeed keeps the loading icon.
Kitchen Sink loads data and seems to change page, but it doesn't let me scroll below the initial fold.

@leeDav I'm purchasing a windows phone today to start testing it on that platform. Thanks for the bug reports.
I did just push an update 20 minutes ago to kitchen sink, but nonetheless I'm excited to be able to actually test on real hardware.

Yeah. Now the page and scroll are working, but it's very very slow :(

Does anyone happen to know what the JS implementation on Win Phone uses?  Is it effectively the same as native IE, or unique to the phone, etc.?


fix: image stub for JS

Noticed the JS-example app wasn't running. There are obviously more errors, but with this fix at least it renders some screens! 😄

Is it feasible to add test to avoid future regression.
Can you change to https://github.com/ocsigen/js_of_ocaml/blob/master/runtime/bigarray.js#L354 so event if name change it won't crash ?

Ah, thanks @lessp and @Et7f3 !
Ya, it'd be nice to even have like a selenium or healdess browser test where we could run the js build, and simplify verify no errors in console. Would really help with this class of regressions 👍


Unable to reach OpenAI

When i do a command in MC say me:
The assistant is unable to finish your request: Unable to reach OpenAI: You exceeded your current quota, please check your plan and billing details.
I used a new account with new API Key. How i can resolve this?

Idk, i have same error

You should check out if you have run out of your OpenAI account credits. Or if your account is new and you didn't get your $5 free credits, you may try to contact OpenAI at<EMAIL_ADDRESS>And if you still have some problems, this article may help: https://help.openai.com/en/articles/6891831-error-code-429-you-exceeded-your-current-quota-please-check-your-plan-and-billing-details.


Update readme to add Pallets Ecosystem notice

This commit converts the README from .rst to .md, and then adds the Pallets Community Ecosystem notice. I don't believe .rst files can show the same "Important" alert boxes and it feels correct to keep it visually consistent between projects.
I've also updated all of the references in the README from github.com/flask-admin/flask-admin to github.com/pallets-eco/flask-admin. I can add another commit that does the rest of the project's references, or I can remove that change from this PR to do it all references together in a separate PR.

Is flask-admin not active anymore?

@princerb Just transferred to the Pallets!

@princerb Just transferred to the Pallets!

I see, but I also can see the date when the last commit was made. So this repo is inactive for this too long, and 78+ open pull requests. For this reason, I am afraid I am not willing to open my pull request while I have some contribution improvements for the project.

setup.py still references README.rst for the package's long description.

@aenglander good spot - have fixed that reference (and the reference in MANIFEST.in as well)

@princerb We actually need more maintainers. Feel free to join the Pallets discord # pallets-eco channel ^^.


feat(replica): RebuildRetryCount for disconnection

Do not count the RebuildRetryCount if rebuilding reused replicas failed caused by network disconnection or node down.
Need to collect more failed reasons of rebuilding replicas.
longhorn/longhorn#1923

After some testings, both node is down or network of the node is unstable,
RebuildRetryCount that is not increased will not make the rebuilding mechanism into an infinite loop because a replica would be replenished in SettingNameReplicaReplenishmentWaitInterval seconds (default is 600 sec.) if there is another available node and failed replica on the down or unstable networking node will be deleted when reaching the volume.spec.staleReplicaTimeout (minutes)

@mantissahz Please update the test result, then we can merge this. Thanks.

Regression test for rebuilding part is here https://ci.longhorn.io/job/private/job/longhorn-tests-regression/3016
Manual tests: (use network_down.sh to simulate network unstable)

Make network down and up repeatedly on node A of replica A:
It can get ReplicaConditionReasonRebuildFailedDisconnection or NodeConditionReasonManagerPodDown failed reasons and rebuildRetryCount will not be increased
Sometimes it will get replica must be closed, cannot add in state and rebuildRetryCount will be increased.
Replica can be rebuilt normally if network is back to be stable.
A new replica will be replenished depended on replica-replenishment-wait-interval if replica A is never rebuilt completely and replica A will be deleted depended on staleReplicaTimeout

https://ci.longhorn.io/job/private/job/longhorn-tests-regression/3018
Rerun for failed case test_settings.py::test_setting_concurrent_rebuild_limit and PASSED

https://ci.longhorn.io/job/private/job/longhorn-tests-regression/3018 Rerun for failed case test_settings.py::test_setting_concurrent_rebuild_limit and PASSED

cc @longhorn/qa need to pay attention to this test to see if it's flaky.

Manual Tests just like https://github.com/longhorn/longhorn-manager/pull/1703#issuecomment-1441368785 works as expected.
And regression test for the rebuilding part is running: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/3019

@Mergifyio backport v1.4.x


[wip] Status updates

https://trello.com/c/oAaQvqQE/320-create-a-delivery-monitor-to-check-status-of-emails-sent-to-notify

Thanks @thomasleese. I've made those changes. Please could you take another look?
I've broken out the healthchecking into separate tickets:
https://trello.com/c/sehNMIbL/246-make-healthcheck-test-for-technicalfailure
https://trello.com/c/31XA1mkY/248-integrate-email-alert-api-with-notifys-callback
And I've added an integration ticket for when Notify have done their callback work:
https://trello.com/c/31XA1mkY/248-integrate-email-alert-api-with-notifys-callback
Have I missed anything you can think of? The change turned out to be quite small.

Tested on my local machine by manually creating the models then posting to the endpoint with sidekiq running. I can see the status change and a permanent_failure set the subscriber's email address to NULL and deleted its subscriptions.
$ curl -H "Content-Type: application/json" -X POST -d '{"reference":"ref-123","status":"permanent_failure"}' http://localhost:3088/status_updates


Add in hyperlinks to external resources

Hyperlink EC number to a database in per PDB Search tab.
Hyperlink RHEA reactions back to RHEA in Enzyme tab.

Added both of these enhancements in #6


assertion failed: self.idx % 2 == 0

Thanks for SIMD support for rand. See you can see here, it outperforms other mt implementations.
I am using  sfmt::thread_rng(); and  rayon parallel iterator.
During benchmark test, I see randomly it throws below error which is an asset condition. I am using mac-osx.
thread '<unnamed>' panicked at 'assertion failed: self.idx % 2 == 0', /Users/xxxx/.cargo/registry/src/github.com-1ecc6299db9ec823/sfmt-0.2.2/src/lib.rs:56:9
test prior::tests::sigma_par_rust                  ... FAILED

I think found the problem. when sfmt::thread_rng() used with rand::distributions::WeightedChoice in rayon's parallel iterator into_par_iter, it gives above error.
This is working fine when I used rand:thread_rng()
        let mut wc = WeightedChoice::new(&mut items);
        let mut v = Vec::with_capacity(prior_conf.num_data_points);
         (0..prior_conf.num_data_points)
            .into_par_iter()
            .map(|_| {

                //let mut rng = rand::thread_rng();  //this work fine
                let mut rng = sfmt::thread_rng(); //this give error
                wc.ind_sample(&mut rng) as usize
            })
            .collect_into_v(&mut v);

assertion failed: self.idx % 2 == 0

This assertion is in pop64, and it happen when you get u64 random number after a u32:
let mut rng = sfmt::SFMT::new(1234);  // seed
let r = rng.gen::<u32>();
let r = rng.gen::<u64>();

This is a limitation of the original SFMT written in C, but we can easily avoid it.
I will write a patch for this. Thanks.

Please check with new version.

It fixed the issue.  Thank you for the quick response. 👍


add APEL plugin installation and usage to documentation

This PR adds information about the installation and usage of the APEL plugin to the documentation.

Codecov Report

Merging #462 (5a9f3f7) into main (82055fb) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 5a9f3f7 differs from pull request most recent head e2b2bfc. Consider uploading reports for the commit e2b2bfc to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #462   +/-   ##
=======================================
  Coverage   67.47%   67.47%
=======================================
  Files           1        1
  Lines         372      372
  Branches       58       58
=======================================
  Hits          251      251
  Misses        121      121

Components
Coverage Δ

apel_plugin
67.47% <ø> (ø)

auditor
∅ <ø> (∅)

slurm_collector
∅ <ø> (∅)

slurm_epilog_collector
∅ <ø> (∅)

htcondor_collector
∅ <ø> (∅)

priority_plugin
∅ <ø> (∅)


amtool should display the state of an alert (active, unprocessed, inhibited, silenced)

From https://github.com/prometheus/alertmanager/issues/1248#issuecomment-386327062

adding a State column to the extended output would be cool:

# ./amtool alert query -o extended -s -a  'alertname="HighErrorRate"'
Alertname               Starts At                Summary                        State
HighErrorRate           2018-05-03 14:51:19 UTC  server is serving many errors  Silenced

Do we want to add this to the extended output or the simple output? The snippet looks like it's the simple output, but the request is for the extended output?
Perhaps it's worth doing a bit more of a deep dive around what really should go into the output? In every case I've seen the extended output is far too large to fit into any terminal anyway.
I've found in my own experience the most useful output for me is the json output. Whenever I really need information I end up just piping the output into jq for mangling anyway.

I've just copied the comment from @stuartnelson3 in the original issue but as I understand it, this was requested to be added to the extended output format.

@simonpasquier hey created a pr for both output types, simple output a lot faster sometimes but added support for both simple and extended https://github.com/prometheus/alertmanager/pull/2324


iOS: Text replacements don’t work in the editor

Issue Summary
When typing in the editor using iPad, the keyboard’s text replacements should replace :nerd_face: with 🤓, etc.
To Reproduce

Switch to the English keyboard (Settings → General → Keyboard)
Edit a post in the Ghost admin using Safari or Chrome
Type :nerd_face:

Expected: Converts into emoji
Actual: Nothing
Technical details:

Ghost Version: latest
Browser/OS: iPad Pro 11”, latest iOS, Chrome/Safari

There is no text replacement for emojis in Ghost's editor so this is expected. If you want emoji autocomplete you could add your vote to the feature on the Ideas board https://forum.ghost.org/t/emoji-autocomplete/882.


V 0.3 update

This version introduces the following features:

Automatic Gitlab DB and configuration backup to a designated cloud bucket
Capability to migrate from another Gitlab instance
Capability to supply Dockerhub credentials and run jobs with private container images
Capability to supply external DNS hostname to Gitlab instance if the managed zone exist on one of your google cloud projects
Updated README guideline and infrastructure layout image accordingly

Fixes/Changes/Security

Now using TF provider  instead of project ID where possible
Scoped the bucket admin permissions of the container image pusher only to the bucket holding the container images instead of all buckets.
Separated K8s (GKE) resources to a single file (gke.tf).  Helm resources kept in the main file.
By utilizing PDB , fixed cases when additional linux nodes were not scale down
Fixed certificate generation error, when not suppling external DNS hostname
Added the Gitlab compute service account permissions to remove its metadata values
Removed the automated Gitlab API key seeding for a better security.
Now seeding the runners registration token after the complete deployment to allow finish reconfiguration before the Gitlab runners are able to register.
Registering the Kaniko runner (container builder) specifically to work with only Scallops-recipes repo to secure unauthorized usages and possible access key theft.
Separated the windows node pool from the GKE module to reduce the time it takes to re-apply new resources to the environment (This issue made the debugging of the deployment a nightmare).

New commit added related to these comments:
https://github.com/SygniaLabs/ScallOps/commit/68b25391f48853d3f35a286fffd747d6fdf0e15d
Refer the comments threads to find specific code diffs

Need to close still the opened conversations, added one minor comment.


runCommand error: system

Hello,
I am trying to run the latest verged (Verge daemon ) on linux for a small yiimp mining pool, for blake2s verge.
In my debug.log i see messages like:
runCommand error: system(/var/stratum/blocknotify :5766 561 < blockhashhere> ) returned -1 .
When i process the command manually everything works ok.
My verge.conf is as follows:

rpcuser=myuser
rpcpassword=mypass
rpcport=5610
rpcthreads=8
rpcallowip=<IP_ADDRESS>
maxconnections=256
algo=blake
daemon=1
gen=0
alertnotify=echo %s | mail -s "Verge-blake2s alert!" info@
blocknotify=/var/stratum/blocknotify :5766 561 %s

2 questions:
Verged seems to have support for blake2s, however i cannot find it. Is algo=blake in the configuration and MAN pages to be meant as blake2s?
I Run Verged as root, so i wonder why it comes back with these run command errors?

if you can do it manually then that means the software must be doing it slightly different than you are.

Hi, have you fixed the problem?

[quote]
Hi, have you fixed the problem?
[/quote]
I wish i had ... :(  but no, it is not solved yet.
The first question is not solved. The second is not  a question but a remark, after trying i found out that the VERGd only accepts algo=blake and not algo=blake2s. .... So apparently algo=blake means blake2?

So apparently algo=blake means blake2?

Yes it does show the right difficulty, however there are more bug's to look into as my pool does find blocks, but when writing them to the chain gives me a Sign error.

I chatted with VergeDev on Discord and I was told though in conf algo=blake but when mining it has to be blake2s. Hope it helps.

@wijnandschouten im guessing you got this resolved since you pr'd your pool to the main website? feel free to make a new issue if there are any issues with verge.

Can you post your conf file plz?

This has nothing to do with Verge, but it has to do with Blocknotify / Yiimp.

rpcuser=yiimprpc
rpcpassword=e9N6hF3IwZgtYAjq4rV58g
rpcport=19090
rpcthreads=8
rpcallowip=<IP_ADDRESS>
onlynet=ipv4
algo=blake
maxconnections=12
daemon=1
gen=0
alertnotify=echo %s | mail -s "Verge alert!"<EMAIL_ADDRESS>blocknotify=blocknotify <IP_ADDRESS>:3433 1909 %s
note: I did try domain name and 192 ip as well... so it seems yiimp problem.

back to the first post, its probably related to you manually changing the rpc port in the .conf?

I also have such a problem, help me fix it!

@says112  you have to sert the correct powalgo on avian.


[SPARK-42263][CONNECT][PYTHON] Implement spark.catalog.registerFunction

What changes were proposed in this pull request?
Implement spark.catalog.registerFunction.
Why are the changes needed?
To reach parity with vanilla PySpark.
Does this PR introduce any user-facing change?
Yes. spark.catalog.registerFunction is supported, as shown below.
>>> @udf
... def f():
...   return 'hi'
...
>>> spark.catalog.registerFunction('HI', f)
<function f at 0x7fcdd8341dc0>
>>> spark.sql("SELECT HI()").collect()
[Row(HI()='hi')]

How was this patch tested?
Unit tests.

Merged to master and 3.4, thanks!


[submodule-sync] bot-submodule-sync-branch-22.08 to branch-22.08 [skip ci] [bot]

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
HEAD commit SHA: 81f30b3fc9e00990f3466a02aaba67ec0d455843, cudf commit SHA: https://github.com/rapidsai/cudf/commit/0f860ea11b35e5dc79fd0e0f6bb7bc526dce209a
This PR will be auto-merged if test passed. If failed, it will remain open until test pass or manually fix.


setting room-info and textarea-action-handler event listeners does not cause intended behavior change

Describe the bug
When @textarea-action-handler is set, custom-action-icon should be displayed but is not.
When @room-info is set, room header should be clickable but is not.
Steps to reproduce
Add a @textarea-action-handler to chat-window component, expected icon does not appear in text area.
Additional context
Code used is demo code modified for purpose, with relevant additions:
<chat-window
   ...
  @textarea-action-handler="sendLink"
>
  <template v-slot:custom-action-icon>
    <i  class="far fa-link" />
  </template>
</chat-window>

...

sendLink({ roomId }) {
  const message = {
    content: document.location.href,
    roomId: roomId
  }
  this.sendMessage(message)
}

Fixed in https://github.com/antoine92190/vue-advanced-chat/commit/c44f70c6aac819beb97f0f174e5dc1e12010e105


#1320 Added new trigger events

Closing #1320

There is a problem in the html table code:

There are three misspellings of the word "supported"


Update functions to all use POSIX syntax

I'm not a huge fan of this change, as I've made it known. However, this
is semi-recommended by the style guide we've chosen to use and is a more
common syntax.
I used the command Eriner originally posted and manually fixed some of the lines which were accidentally modified and tried to double check the rest.
Fixes #692.
CC @Eriner @sorin-ionescu

This will be going in before any other PRs which change actual shell code so we don't need to spend another year waiting on someone to re-do these changes.
I've been using this for a day with no problems, so I'll merge this soon unless anyone has problems with it.

I don't see the point of changing this? This is a zsh project and I don't see what this helps. If it were not a zsh project this could be an okay change. But in the end it really doesn't matter as long as there are no differences between defining functions the different ways...

The style guide says this:
Lower-case, with underscores to separate words. Separate libraries with ::. Parentheses are required after the function name. The keyword function is optional, but must be used consistently throughout a project.
I personally like the function keyword as it makes it easier to grep for functions and easier to see where functions are. Though in the end it's really a stylistic choice.

I honestly prefer the function x syntax... but in the mentioned issue, Sorin and Eriner both weighed in, seemingly preferring the posix style syntax. It was me and one other person preferring the function keyword.
One thing worth noting: there are currently 3 function definition syntaxes being used in prezto:
function x
function x ()
x ()

I prefer the first, the middle should never be used and the third is posix. As long as we're consistent I'm fine with either the first or last syntaxes.
Anyway, there's a ton of discussion and quoting man pages and stuff in the issue. I can drop this if you'd like to comment there... I just want to be done with this issue.

Also I'm most against this because:
Says bash on posix mode:
12. Function names must be valid shell names. That is, they may not contain characters other than letters, digits, and underscores, and may not start with a digit. Declaring a function with an invalid name causes a fatal syntax error in non-interactive shells.

We have plenty of functions which use dashes so we are already non-POSIX there. And there seems no real reason to change, though we should remove any () if we use the function keyword. Though this is all just my opinion and in the end it really doesn't matter that much...

I'm dropping this in favor of #1366


Companion mode stuck on champs select

Details
Hi guys,
Koolo work nicely overall on my side, but when i try companion mode it can't find my character.
let me know if i can give you more info
Version
v0.4.6
Logs
time=23:33:37 level=INFO msg="Waiting for character selection screen..."
time=23:34:38 level=INFO msg="Character selection screen found"
time=23:34:38 level=INFO msg="Selecting character..."
time=23:34:39 level=ERROR msg="error running supervisor Paladin: error waiting for character selection screen: character tototestte not found"

I've built from latest commit

Can you share a pic of your character select screen please @totodelee

keek, i deactivated the companion mode but it doesn't work anymore.
i prefer not share my character name.
but i was working nicely until today

Names are case sensitive so it is possible that could be an issue. But more information is needed to assist with some issues. I understand, be advised support will be more limited without some information.
There was a d2r update pushed today that caused issues.

update for the new d2r patch fixed the issue.
9457712

update for the new d2r patch fixed the issue.
9457712


Currently at 989 lines. Reduce lines while improving readability!

Remember, this isn't code golf. The goal is to make the code easier to maintain. In general that's also smaller, but smaller that's harder to maintain can't be merged.

 But once there are stable OpenCL implementations we could ditch the numpy ones, since OpenCL runs on the CPU as well?!?

I think we'll keep both, forces the Tensor class to remain good and generic. And it doesn't really hurt complexity, they are totally separate files.

Down at 941 now, even with the 40 line profiler.

At 927 without the GPU backward conv. Going to be close once we merge it. Almost feature complete!

978

ops.py Class Pad2d - line 103, # return statement can be oneline.

What lines are we counting, anything in the tindygrad folder? Any line length guidelines/style guidelines?

@big-c-note look one of PR's test checks there should be lines details

i would recommend a fastai coding style for readability and low line count.

#212 shaves off another ~55 lines

Down to 937!


SearchBar doesn't match value nested into td element

I have a td column that is composed by a div with other two span inside. But when I wrote something that would be matched in that column the table results is always empty.
Is it possible that search bar is not capable to match string inside the td element ?

@stcursi sorry for lately reply, I think I need to know some context so that I can help you, but it's better to have a minimal and simple example code on codesandbox that I can solve your problem efficiently
question:

did you use column formatter for some column?
if yes, did you enable searchFormatted?

thanks

Hi @AllenFang - I am seeing this same behavior, particularly when I use the formatter function to return a link. I am providing snippets from my code.
Note! I added a console.log to the filterValue function, and it does NOT execute when I type in to my search bar. However, if I remove the formatter, then filterValue executes as expected.
// from columns array
{
    dataField: "name",
    text: "Name",
    sort: true,
    searchable: true,
    formatter: (cell, row) => <Link to={{ pathname: `/data-catalog/${row.identifier}` }} >{props.row.name}</Link>,
    filterValue: (cell, row) => {
      console.log("is this being called?")
      return row.name
    },
},

// from my table
...
          <ToolkitProvider
              bootstrap4
              keyField={this.props.keyField}
              data={this.props.data}
              columns={this.props.columns}
              search={ { searchFormatted: true } }
            >
              {(toolkitprops) => (
                <div>
                  <SearchBar {...toolkitprops.searchProps} />
...

I implemented a workaround by including a "hidden" field that filters my name column:
{
  dataField: "searchable_name",
  hidden: true,
  searchable: true,
  filterValue: (cell, row) => {
    return row.name
  },
},


Add Validation to the Models During Construction

Administrator.php, Role,php, etc

I'm not sure this is necessary. This would be in order to prevent invalid database entity / business objects from being instantiated. Currently this is done by only instantiating them from their respective mappers, after calling a select function, so that they are directly injected with database data.


Test setting DisablePythonDependencyInstallation to true

Draft PR to verify all tests still pass :fingers_crossed:

I had initially forgotten to build the JS after the TS change :face_exhaling:

No need for this PR any longer :+1:


#9323: Introduce template for new ttnn pull requests

Related Issues
#9323
Description
This introduces a template for future pull-requests opened under ttnn. These changes are introduced to start outlining the expectations from a developer opening up a pull-request. The goal here is to create a consistent interface for opening up a pull-request and enable reviewers to better understand the changes being merged in at a high-level.
Checklist

[x] Post commit CI passes - N/A
[x] Related model testing - N/A
[x] New tests added - N/A
[x] Change is made to ttnn and not tt_lib :)

Looping in @TT-BrianLiu as well
How often do we see changes in tt-lib? Should we start enforcing static-check level gating to ensure it doesn't change?


Update committed spend chart to use details API

Update committed spend chart to use details API, but default to the POC for demos.

Codecov Report

Merging #415 (1e2a887) into main (8cdb5f0) will decrease coverage by 0.23%.
The diff coverage is 0.00%.

:exclamation: Current head 1e2a887 differs from pull request most recent head 2f39926. Consider uploading reports for the commit 2f39926 to get more accurate results

Additional details and impacted files

@@           Coverage Diff            @@
##            main    #415      +/-   ##
========================================
- Coverage   4.80%   4.57%   -0.23%
========================================
  Files         45      49       +4
  Lines       1894    1987      +93
  Branches     406     427      +21
========================================
  Hits          91      91
- Misses      1803    1896      +93

Impacted Files
Coverage Δ

src/routes/components/data-toolbar/DataToolbar.tsx
0.00% <0.00%> (ø)

src/routes/details/Details.tsx
0.00% <0.00%> (ø)

src/routes/details/DetailsFilterToolbar.tsx
0.00% <ø> (ø)

src/routes/details/DetailsHeaderToolbar.tsx
0.00% <0.00%> (ø)

src/routes/details/DetailsTable.tsx
0.00% <0.00%> (ø)

src/routes/details/DetailsTableExpand.tsx
0.00% <0.00%> (ø)

...tual-spend-breakdown/ActualSpendBreakdownChart.tsx
0.00% <0.00%> (ø)

.../committed-spend-trend-poc/CommittedSpendTrend.tsx
0.00% <0.00%> (ø)

...itted-spend-trend-poc/CommittedSpendTrendChart.tsx
0.00% <0.00%> (ø)

...d-spend-trend-poc/CommittedSpendTrendOverChart.tsx
0.00% <0.00%> (ø)

... and 3 more

Continue to review full report at Codecov.

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


response: skips lines before response line

Improve the logic for junk lines before response line, instead of treating them as body, try to peek if the next line begins with an H and may actually be the response line we were waiting for
If we do not see an H coming, we treat as if it were a HTTP/0.9 response to a HTTP1 request, that is a response without line and headers but just directly body.
for https://github.com/OISF/suricata/pull/8777
https://github.com/OISF/libhtp/pull/387 with commit message improved

@jlucovsky

Merged in #392, thanks!


Print build errors to stderr

This addresses #4451
There are some cases which needs discussion about where to prints them:

usages messages on missing CLI argument
build errors when output format is JSON

LGTM! I think the two cases you mention should also print to stderr. Why would you send them to stdout?

About the JSON formatted errors, I'm thinking about the use-case of using shell commands:
$ crystal build --format json file.cr | use_the_json_output

Once the JSON errors will be on stderr, they'll have a hard time getting the correct stream to go in the pipe to use_the_json_output program.
But maybe it's not our business, and it should stay on stderr, as most users will use their language's stdlib to spawn a process and granuraly get it's stdout/stderr programmatically.

I don't know why the build doesn't work, did I broke something?

@bew so far, so (green) good... :)

The travis build fails so often or osx, why don't we just disable it or ignore the results and use circleci only?

Rebased, osx still failing, are we waiting for #4528 to be merged? Or could this be merged soon?

Looks like GTG, merge-time?

I'm unsure to write errors to STDERR in JSON output case.
Better to choose output stream based on output format. Errors to JSON to STDOUT is ok. Isn't it?

@akzhan I'd expect to see errors on STDERR on non-success process exit...

@akzhan I believe that an error message should always go to stderr, whatever the output format is.

@Sija @bew Ok.

Looks good to me, would be nice if we could spec this behaviour but i'm not really opposed to landing this without specs.

Restarted the build (I know, I know, we'll tackle that soon :)).

@mverzilli this PR is from may so I guess it doesn't have the .travis.yml merged so that OSX is an allowed failure.

@RX14 You're right, I've rebased the branch on current master it should be good now.

I've found another place where output should go on STDERR:
diff --git a/src/spec.cr b/src/spec.cr
index 2c3c303a5..aa49cdbcf 100644
--- a/src/spec.cr
+++ b/src/spec.cr
@@ -83,8 +83,8 @@ OptionParser.parse! do |opts|
     if location =~ /\A(.+?)\:(\d+)\Z/
       Spec.add_location $1, $2.to_i
     else
-      puts "location #{location} must be file:line"
-      exit
+      STDERR.puts "location #{location} must be file:line"
+      exit 1
     end
   end
   opts.on("--junit_output OUTPUT_DIR", "generate JUnit XML output") do |output_dir|
@@ -106,7 +106,7 @@ OptionParser.parse! do |opts|
 end

 unless ARGV.empty?
-  puts "Error: unknown argument '#{ARGV.first}'"
+  STDERR.puts "Error: unknown argument '#{ARGV.first}'"
   exit 1
 end

Should I add this change in this PR ?

@bew IMHO it's an addition in line with this PR, so yes, I'd add it too.

@bew that's not actually build errors though is it? I'm fine with modifying the spec runner in this PR but the commit should be renamed to "Print build and spec errors to stderr".

Indeed it's not a build error, that's why I asked first.
I'll make another PR later today (or someone else can if he wants to!) for the spec runners, as it was not in the scope of this PR to check every possible print/puts.

@bew so, is this ready to merge?

If you all agree, yes I think so.

Great job @bew! Thank you ❤


Add support for pod metrics from all namespaces in Metrics API

We should add support for handler apis/metrics/v1alpha1/pods in https://github.com/kubernetes/heapster/blob/master/metrics/apis/metrics/handlers.go#L52

ref #1231


Need to highlight DNN incompatibility with SQL older than 2019 during cluster creation

Under the create a cluster section there needs to be a warning earlier on about using DNNs and Windows 2019. In the situation of running Win 2019 with SQL older than 2019 DNNs are not supported which causes the overall networking to not work without recreating the Cluster and AG as a VNN.
If possible we need to make this more obvious/give version specific instructions.

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

ID: ee7ac6ba-8f0a-b6d9-99f4-a335afc63b99
Version Independent ID: 2b550681-c147-281d-15be-ff701387797f
Content: Tutorial: Configure a SQL Server Always On availability group - SQL Server on Azure VM
Content Source: articles/azure-sql/virtual-machines/windows/availability-group-manually-configure-tutorial.md
Service: virtual-machines-sql
Sub-service: hadr
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@cbattlegear , Support for AG DNN listener is back ported all the way to SQL Server 2016 SP3 (https://support.microsoft.com/en-us/topic/kb4578579-improvement-availability-group-listener-without-the-load-balancer-in-sql-server-2016-2017-and-2019-81d27666-5c58-ad47-c83c-48ab7a5d959d).

Closing this Git Issue as the fix has been backported.
Thanks!
Masha from the SQL Docs team
#please-close


容器管理 - 在集群中部署第二调度器文档中配置vgpu参数建议文档中提供一些详细的步骤，而不是只写一个参数并没有截图

Describe the bug
容器管理 - 在集群中部署第二调度器文档中配置vgpu参数建议文档中提供一些详细的步骤，而不是只写一个参数并没有截图

A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '...'
Scroll down to '...'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

done:https://github.com/DaoCloud/DaoCloud-docs/pull/4010


add special '[document]' fieldset

specially handled like [all] and [docid]
depends on the document type having a configured fieldset named '[document]'
should make it possible to run vespa-visit -l '[document]' and get only the
fields declared inside the document for any and all document types.

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
@vekterli please review
@geirst please review

I am handing this over to @baldersheim as he has more context.


Don't run precmd hooks in cd widget

precmd hooks expect the Zsh Line Editor to not be active.
Running these when the ZLE is active can lead to unpredictable results.
See https://github.com/marlonrichert/zsh-autocomplete/issues/180

This reverts #1136 which fixed #915.
@aaronjensen Can you review this pull request?

@junegunn While perhaps it looks like I'm reverting #1136, this is not entirely true, because this PR does not regress #915. Rather, it changes the code to do things properly. With this PR, precmd hooks will still fire when using Altc, but now they will fire at the right time, just before the ZLE gets activated, rather than when it's already active.
You can test this in Zsh as follows:
$ precmd_test() { print fired }
$ autoload -Uz add-zsh-hook
$ add-zsh-hook precmd precmd_test

Then press Altc to change dirs. You will see that fired will get printed.

AFAICT it still works for my use case. 👍

Thanks for the clarification!

Merged, thanks!


How To Auto Restart?

Help me please

What type of auto-restart do you mean? Do you mean auto-restarting after someone reaches a certain amount of mass or auto-restarting after a certain time limit?

Duplicate.

After someone reaches a certain amount of mass

Duplicate of #447

If I put the maximum mass in 5000, and someone reaches that mass, will all players all players die?

No

And how do I make all players die?

type in killall in the console .

xD

buhh xD


IMU integration

Hello,
I'm trying to test isaac_ros_visual_slam with IMU (the one inside realsense d455 module) using realsense launch example.
I edited  realsense example like this:

Edited launch
visual_slam_node = ComposableNode(
      name='visual_slam_node',
      package='isaac_ros_visual_slam',
      plugin='isaac_ros::visual_slam::VisualSlamNode',
      parameters=[{
                  'enable_rectified_pose': True,
                  'denoise_input_images': False,
                  'rectified_images': True,
                  'enable_debug_mode': False,
                  'debug_dump_path': '/tmp/elbrus',
                  'enable_slam_visualization': True,
                  'enable_landmarks_view': True,
                  'enable_observations_view': True,
                  'map_frame': 'map',
                  'odom_frame': 'odom',
                  'base_frame': 'camera_link',
                  'enable_imu': True,
                  'input_left_camera_frame': 'camera_infra1_frame',
                  'input_right_camera_frame': 'camera_infra2_frame',
                  'input_imu_frame': 'camera_accel_frame',
                  'gravitational_force': [-0.22555294, -9.83607, 0.049]
                  }],
      remappings=[('stereo_camera/left/image', 'infra1/image_rect_raw'),
                  ('stereo_camera/left/camera_info', 'infra1/camera_info'),
                  ('stereo_camera/right/image', 'infra2/image_rect_raw'),
                  ('stereo_camera/right/camera_info', 'infra2/camera_info'),
                  ('visual_slam/imu', '/imu')]
  )

'gravitational_force': [-0.22555294, -9.83607, 0.049] -> gravitational_force was changed from default value as stated here  [-0.22555294, -9.83607, 0.049] is reading from IMU at the start of trajectory estimation

'input_imu_frame': 'camera_accel_frame' -> input_imu_frame was set to available one from tf tree following this

Visualized here

My issue:
Although integrator_states changes to 3 (at launch it as 2 and later 3) I cannot see any improvements in estimated trajectory. (IMU measurements seems to be relatively in order)
In a experiment, where I simulate lost of image (the device is without movement) estimated trajectory does drift (not small drift caused by noise integration but a big one).
Questions:
I suspect that my input_imu_frame or gravitational_force parameters are not in order, could you provide some more insight how to set these parameters?
What should I expect from IMU integration? Overall better trajectory estimation? Or IMU is used only in situations where image is invalid?
Is there a simple way how to test whether IMU integration is in order?

In order to verify the integration of IMU, you could try to "blind" the camera imagers and try small rotational changes about principal axes and see if the poses are still coming and are expected.
For the gravitational vector, it looks like it is aligned to the camera coordinate frame so the Z component of the gravitational vector should have the value 9.81

Hello, I'm trying to test isaac_ros_visual_slam with IMU (the one inside realsense d455 module) using realsense launch example.
I edited realsense example like this:
Edited launch

'gravitational_force': [-0.22555294, -9.83607, 0.049] -> gravitational_force was changed from default value as stated here  [-0.22555294, -9.83607, 0.049] is reading from IMU at the start of trajectory estimation
'input_imu_frame': 'camera_accel_frame' -> input_imu_frame was set to available one from tf tree following this

Visualized here
My issue: Although integrator_states changes to 3 (at launch it as 2 and later 3) I cannot see any improvements in estimated trajectory. (IMU measurements seems to be relatively in order)
In a experiment, where I simulate lost of image (the device is without movement) estimated trajectory does drift (not small drift caused by noise integration but a big one).
Questions: I suspect that my input_imu_frame or gravitational_force parameters are not in order, could you provide some more insight how to set these parameters?
What should I expect from IMU integration? Overall better trajectory estimation? Or IMU is used only in situations where image is invalid?
Is there a simple way how to test whether IMU integration is in order?

Hi, did you succefully set imu fusion in visual slam?
I'm also using d435i to do this, but I do not know which frame is "inpu_imu_frame", since the expected imu frame of d435i is camera_imu_optical_frame, but it doesn't show in TF trees although it does output /camera/imu topics...
any assistance or advice would be appreciated, thanks

Hi @MartinSedlacek !
I am also trying to use the D455's IMU , but I am not sure about the correct parameters values. Have you figured this out?


Title: I will add a Leetcode Formatter to the awesome chrome extenstion list.

Is your feature request related to a problem? Please describe.
No, my feature is not a request related to a problem.
Describe the solution you'd like.
This Extension is very useful for the developers who solve leetcode coding challenges, without this extension they have to write code on vs code and then paste it to the leetcode code editor. instead of that, they can use this extension to write the code beautifully formatted.
Describe alternatives you've considered.
no, I have not considered any alternative.
Add any other context or screenshots about the feature request here.

@ridsuteri kindly review this issue.

@AmolShelke2 This looks like an existing one. Did you make this one? Because right now we are just allowing custom-made extensions...

Ohh sorry I though you are accepting all extension you can close this issue.
On Sun, May 8, 2022, 11:50 AM Riddhi Suteri @.***>
wrote:

@AmolShelke2 https://github.com/AmolShelke2 This looks like an existing
one. Did you make this one? Because right now we are just allowing
custom-made extensions...
—
Reply to this email directly, view it on GitHub
https://github.com/ridsuteri/Awesome-Chrome-Extensions/issues/239#issuecomment-1120358686,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWWDINQRYXWDI3RUPGN4OG3VI5ML5ANCNFSM5VLNUDCQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


/groups/:id/monthly-top endpoint returns null for groups that don't exist

Example: wiseoldman.net/api/groups/113333/monthly-top
It should probably return "Group not found.", like a few other endpoints do.

Notes:
When removing a player from a group, is there a way to give a non valid tracked player as input? I have tried but not succeeded. Help.

This was left as it is to avoid doing one extra database fetch for endpoints that don't require it, but I agree that the fetch is worth doing in exchange for API consistency.


Unhandled Rejection (ReferenceError): bKash is not defined

This is not a valid url for bkash script, please note that in the README, we only provided a dummy URL and if you have proper bkash credentials, they should send you this URL as well.


Use rayon for indexing workers.

Codecov Report

Merging #1324 (83045b8) into main (447811c) will decrease coverage by 0.01%.
The diff coverage is 94.73%.

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

@@            Coverage Diff             @@
##             main    #1324      +/-   ##
==========================================
- Coverage   94.23%   94.22%   -0.02%
==========================================
  Files         232      232
  Lines       40850    40872      +22
==========================================
+ Hits        38496    38510      +14
- Misses       2354     2362       +8

Impacted Files
Coverage Δ

src/indexer/index_writer.rs
96.55% <94.73%> (-0.20%)
:arrow_down:

.../termdict/sstable_termdict/sstable/block_reader.rs
80.35% <0.00%> (-1.79%)
:arrow_down:

src/directory/directory.rs
94.11% <0.00%> (-1.48%)
:arrow_down:

src/query/union.rs
98.78% <0.00%> (-0.61%)
:arrow_down:

src/query/boolean_query/block_wand.rs
96.85% <0.00%> (-0.21%)
:arrow_down:

Continue to review full report at Codecov.

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


fix(ui-components): pass remaining props to UITreeDropdown

Give UITreeDropdown component all passed props, similar to other components.

@AlinaGovoruhina could you please add additional test where you pass one of property which was not available before?