Can't heal injured civ

I have bandages in my inventory
There is no item in the action menu to heal the man
There is no injured part on the man in the ACE heal menu

The other player in my team reported that the man was in a combat/firing stance without a gun - same clothes though. He didn't get an image.
Attached images and log. I was hosting locally.
Arma3_x64_2017-10-25_09-42-18.txt

The civs that are in a combat firing stance is I think just the result of the units items being checked and then removed via script after town clearance not an indication they are about to go rogue. I have found the medical issue can be resolved by carrying more types of bandages like quick clot, packing bandages etc, even if just to carry out treatment on these civs. Try equipping a variety of bandage and dressing types then check if it helps in this situation. There may be traces of ace advanced wounds used in this event.

Ah, I'll try with different bandages.
To be clear, the man was in the firing stance while he was prone for me. We were looking at the same man.
Because I only play with one other, we don't take a medics' slot but I will do that or even equip a medical AI next time.
Will report back

Activate the civrep debug and provide a logfile.


Aggregators for logs and Dashboards - Sample Alert for metric

Configure and document how to create an alert on a metric on ELK, so Dusk engineer can easily reproduce on future needs.

Native Alert on Elastic Stack requires Elastic Gold Subscription. https://www.elastic.co/pricing/

Implementation will use https://github.com/Yelp/elastalert


Are there Decorators to name a Method in  Resource class?

I hope the title gets the thing i want to do here.
lets say i define a custom Resorce like so
class ApiProduct(Resource):

    def get(self, id):
        product = ProductRepository.get_product_by_id(id)
        return jsonify(product)

    def undo_delete(self, id):
        ProductRepository.undo_delete_product(id)
        product =ProductRepository.get_product_by_id(id)
        if(product.Deleted == False):
            return '', 204
        return 404

and what i am looking for is more or less a way to make undo_delete available with a other name to the Request. So is there a existing decorator that does that, so undo_delete becomes a undodelete for the supported request methods?

Resource is a fancy wrapper for MethodView from Flask, so a resource is just a collection of methods that respond to HTTP verbs. You can't map the verbs to methods in any way other than naming the method post or get, etc.
Flask 2.x can sortof do this now though:
@app.delete('/foo')
def delete_foo():
    pass

ok thanks,
i can live with that, and having  methods named like some_thing is ok for me
cheers
Markus


Bash on Ubuntu on Windows - TLDR update command fails

Reproduction Rate
I could reproduce the issue each time I tried to update TLDR local database.
Steps to Reproduce

Install Windows Subsystem for Linux.
Install Ubuntu on Windows.
Run Bash on Ubuntu on Windows.
Install linuxbrew. There is installation instruction on http://linuxbrew.sh.
Install TLDR C++ client: brew update and brew install tldr.
Try to update TLDR local database: tldr --update.

Result
$ tldr --update
Error: Could Not Rename: /tmp/tldrElmG3W/tldr-master to /mnt/d/joachim/.tldrc/tldr-master/

Expected Result
Update of  TLDR local database.
Additional Information
Windows Subsystem for Linux, Bash on Ubuntu on Windows
TLDR C++ has been installed with linuxbrew
I have tried to update TLDR as superuser:
$ sudo tldr --update
[sudo] password for joachim:

There is no error message when I update TLDR as superuser but I'm still unable to print any TLDR page. Each attempt ends with This page doesn't exist yet! error message.

The rename() function does not work across file system boundaries. If your $HOME is mounted seperately OR /tmp is a tmpfs, you will see above error. This means tldr will only work successfully in trivial installations, and practically none of the modern Linux distros.
A fix would be to back up with a recursive copy-then-remove if rename() fails, or just use that in all cases.

Closing as a duplicate of the following:

https://github.com/tldr-pages/tldr-c-client/issues/95
https://github.com/tldr-pages/tldr-c-client/issues/24

Progress on this has been made by a contributor here:

https://github.com/tldr-pages/tldr-c-client/pull/100


Fix error reporting of unclosed slice interpolation

Fixes https://github.com/scalameta/scalameta/issues/2169

Error is thrown in       def curr = legacyTokens(legacyIndex)
I did not want to be too invasive, but it is actually used in multiple places, maybe better would be to check in def curr we are not outside of tokens array and throw more generic error "unclosed statement" or sth. similar?


import of module 'glog.glog.log_severity' appears within namespace 'google'

Hello All,
I am running iOS project using react-native. I have installed pods, below is my Podfile
_source 'https://github.com/CocoaPods/Specs.git'
source 'https://github.com/goinstant/pods-specs-public'
target ‘appName’ do
platform :ios, '9.0'
use_modular_headers!
pod 'GoogleSignIn'
pod 'GoogleMaps'

pod 'React', :path => './node_modules/react-native', :subspecs => [
'Core',
'RCTText',
'RCTImage',
'RCTNetwork',
'CxxBridge',
'RCTLinkingIOS',
'RCTWebSocket',
'RCTAnimation',
'DevSupport',
pod 'yoga', :path => './node_modules/react-native/ReactCommon/yoga'
post_install do |installer|
    installer.pods_project.targets.each do |target|
        phase_name = 'Headers'
        target.build_configurations.each do |config|
            config.build_settings['SWIFT_VERSION'] = '3.0'
        end
    end
end
pod 'ReactNativeLocalization", :path => './node_modules/react-native-localization'
pod 'BVLinearGradient', :path => './node_modules/react-native-linear-gradient'
pod 'DoubleConversion', :podspec => './node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
pod 'glog', :podspec => './node_modules/react-native/third-party-podspecs/glog.podspec'
pod 'Folly', :podspec => './node_modules/react-native/third-party-podspecs/Folly.podspec'

end_
So when I run my project, I get the above error. Please let me know how to fix this.

What's a pod and how is your problem related to glog?

Please then provide a minimal example allowing to reproduce the problem, without pod.

I also have the same issue.

@sergiud
As per mentioned in the docs
I added Folly in my podfile, and then this issue appeared in logging.h

I'm not familiar neither with Folly nor with pod. Please provide a reproducible standalone example showcasing the problem. Closing the issue until then,

Try to turn off module imports for this pods
pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec', :modular_headers => false
pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec', :modular_headers => false
pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec', :modular_headers => false

Is there a solution without using use_Frameworks!

@anutripa Try updating cocoapods.
I've checked this question on StackOverflow and checked my version of pods. In 1.5.3 I was still getting this error but after updating to 1.7.5 it is no longer required and you can remove use_frameworks! / use_modular_headers!
P.S. @sergiud sorry for hijacking this thread with seemingly unrelated issue. The point of failure was in the glog here where includes were inside the namespace. The swift <==> objC bridge was trying to generate "modular_headers" for that and chocked on that syntax which brought us all here. Hopefully this is not a problem any more.

This issue is still exists, why did you close it?
i can't use the RN because i receive the following error message.

OS: 10.15 Beta (19A536g)
Xcode: 11.0 beta 5 (11M382q)
Toolchain: Swift 5.1 Snapshot 2019-07-25 (a)
React-Native: 0.60.5 (glog version in podspec file is 0.3.5)

Other infos
Pod version: 1.8.0.beta.1
`
source 'https://github.com/CocoaPods/Specs.git'
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '9.0'
use_frameworks!
target 'eportrait_sdk' do
pod 'React', :path => '../../js/node_modules/react-native/'
pod 'React-Core', :path => '../../js/node_modules/react-native/React'
pod 'React-DevSupport', :path => '../../js/node_modules/react-native/React'
pod 'React-RCTText', :path => '../../js/node_modules/react-native/Libraries/Text'
pod 'React-RCTImage', :path => '../../js/node_modules/react-native/Libraries/Image'
pod 'React-RCTNetwork', :path => '../../js/node_modules/react-native/Libraries/Network'
pod 'React-RCTWebSocket', :path => '../../js/node_modules/react-native/Libraries/WebSocket'
pod 'React-RCTLinking', :path => '../../js/node_modules/react-native/Libraries/LinkingIOS'
pod 'React-RCTAnimation', :path => '../../js/node_modules/react-native/Libraries/NativeAnimation'
pod 'React-RCTBlob', :path => '../../js/node_modules/react-native/Libraries/Blob'
pod 'React-RCTLinking', :path => '../../js/node_modules/react-native/Libraries/LinkingIOS'
pod 'React-RCTActionSheet', :path => '../../js/node_modules/react-native/Libraries/ActionSheetIOS'
pod 'React-RCTSettings', :path => '../../js/node_modules/react-native/Libraries/Settings'
pod 'React-RCTVibration', :path => '../../js/node_modules/react-native/Libraries/Vibration'
pod 'React-cxxreact', :path => '../../js/node_modules/react-native/ReactCommon/cxxreact'
pod 'React-jsi', :path => '../../js/node_modules/react-native/ReactCommon/jsi'
pod 'React-jsiexecutor', :path => '../../js/node_modules/react-native/ReactCommon/jsiexecutor'
pod 'React-jsinspector', :path => '../../js/node_modules/react-native/ReactCommon/jsinspector'
pod 'DoubleConversion', :podspec => '../../js/node_modules/react-native/third-party-podspecs/DoubleConversion.podspec', :modular_headers => false
pod 'glog', :podspec => '../../js/node_modules/react-native/third-party-podspecs/glog.podspec', :modular_headers => false
pod 'Folly', :podspec => '../../js/node_modules/react-native/third-party-podspecs/Folly.podspec', :modular_headers => false
pod 'yoga', :path => '../../js/node_modules/react-native/ReactCommon/yoga'
pod 'react-native-camera', subspecs: ['RCT', 'RN'], path: '../../js/node_modules/react-native-camera'
pod 'react-native-image-picker', :path => '../../js/node_modules/react-native-image-picker'
pod 'rn-fetch-blob', :path => '../../js/node_modules/rn-fetch-blob'
pod 'react-native-image-resizer', :path => '../../js/node_modules/react-native-image-resizer'
pod 'react-native-orientation', :path => '../../js/node_modules/react-native-orientation'
pod 'RNDeviceInfo', :path => '../../js/node_modules/react-native-device-info'
pod 'RNGestureHandler', :path => '../../js/node_modules/react-native-gesture-handler'
end
`
So, i tried everything what i found on the internet, but i think these steps don't change the original problem :)

@kovacs-tamas what is your version of cocoapods?

Is the glog prepared for Clang 11.0.0? I assume the problem can be a deprecated syntax, because i haven't faced with this issue before i upgraded to Catalina beta

Add same in pod file
pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec', :modular_headers => false
pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec', :modular_headers => false
still issue

I'm locking the discussion because the issue is clearly not in glog but rather is caused by the tools being used.


components.header undocumented

Do you want to request a feature or report a bug?
question
Currently TimeGridHeader makes use of a header component that can be passed from Calendar. https://github.com/intljusticemission/react-big-calendar/blob/d2e02c4bfde41b39ea22db344cbd8b948b17fc8b/src/TimeGridHeader.js#L70
The property is however not documented. Is this indeed only an implementation detail or meant for actual usage? Currently this seems to be the only way to render a custom header for days in the week view.

It's intended for use, it's an oversight it's not documented! If your up for it, the fix is adding it to the proptype in Calendar.js

Will do. Thanks.

One question remains:
https://github.com/intljusticemission/react-big-calendar/commit/d2e02c4bfde41b39ea22db344cbd8b948b17fc8b#diff-3a1d9f7d22bf911fb6fa60b0b0daae4cL105 removed some passed props.  This could however be considered a non-breaking change since it was not documented before. Just need to know this for the relevant @types PR.

yes intentional, format and culture are long longer needed as the localizer knows them already

Well then I think only the pending PR is left. Closing here.


Question about input order.

Dear Authors:
Thank you for your excellent work！I have a question when I deal with my data. Would the outcome be affected if I input all the 'add-lines' before the 'delete-lines' without formatting the diff-lines according to the commit format in your paper?
For example:
A：[add] line1 [add] line2 [add] line3, [del] line1 [del] line2 [del] line3,
B：[add] line1 [del] line1 [add] line2 [del] line2 [add] line3 [del] line3
If I input the data in format A, would the outcome differ from format B?
I'm still relatively new to AI, so I truly appreciate your insights.

Thank you for your interest. IMHO, I see no obvious difference between the two input formats, as long as the format is consistent from the pre-training phase to the fine-tuning phase. However, actions speak louder than words. We look forward to seeing the investigation results and hope you can share them with us if you research the influence of performance based on different input formats.

So inspiring work this is. I love it veri much!


[WFCORE-114] : Get RuntimeVaultReader into WildFly Core

Moving RuntimeVaultReader from WildFly to WildFly-Core
1.x variant of #679

Linux Build 4 is now running using a merge of 75fec5ce8c0015f6315a6ec4f328d671cc3617e5

Core - Full Integration Build 5 is now running using a merge of 75fec5ce8c0015f6315a6ec4f328d671cc3617e5

Windows Build 5 is now running using a merge of 75fec5ce8c0015f6315a6ec4f328d671cc3617e5

Windows Build 5 outcome was FAILURE using a merge of 75fec5ce8c0015f6315a6ec4f328d671cc3617e5
Summary: Tests failed: 7, passed: 3094, ignored: 66 Build time: 0:21:39
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.manualmode.management.cli.CustomVaultInCLITestCase.testWrongVaultPassword: <no details avaliable>

org.jboss.as.test.manualmode.management.cli.CustomVaultInCLITestCase.testNonExistingVaultPassword: <no details avaliable>

org.jboss.as.test.manualmode.management.cli.CustomVaultInCLITestCase.testRightVaultPassword: <no details avaliable>

org.jboss.as.test.manualmode.vault.CustomVaultInModuleTestCase: <no details avaliable>

org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.testWrongVaultPassword: <no details avaliable>

org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.testRightVaultPassword: <no details avaliable>

org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase.testTrustedCLICertificate: <no details avaliable>

Linux Build 4 outcome was SUCCESS using a merge of 75fec5ce8c0015f6315a6ec4f328d671cc3617e5
Summary: Tests passed: 3101, ignored: 66 Build time: 0:23:20

Core - Full Integration Build 5 outcome was SUCCESS using a merge of 75fec5ce8c0015f6315a6ec4f328d671cc3617e5
Summary: Tests passed: 2868, ignored: 373 Build time: 0:50:23

Windows Build 6 is now running using a merge of 75fec5ce8c0015f6315a6ec4f328d671cc3617e5

Windows Build 6 outcome was SUCCESS using a merge of 75fec5ce8c0015f6315a6ec4f328d671cc3617e5
Summary: Tests passed: 3101, ignored: 66 Build time: 0:20:32

Windows Build 14 is now running using a merge of 242b11d4b31ec3ad522fb21932061e5ba7f9019d

Linux Build 14 is now running using a merge of 242b11d4b31ec3ad522fb21932061e5ba7f9019d

Core - Full Integration Build 13 is now running using a merge of 242b11d4b31ec3ad522fb21932061e5ba7f9019d

Windows Build 14 outcome was SUCCESS using a merge of 242b11d4b31ec3ad522fb21932061e5ba7f9019d
Summary: Tests passed: 3101, ignored: 66 Build time: 0:22:01

Linux Build 14 outcome was SUCCESS using a merge of 242b11d4b31ec3ad522fb21932061e5ba7f9019d
Summary: Tests passed: 3101, ignored: 66 Build time: 0:22:50

Core - Full Integration Build 13 outcome was SUCCESS using a merge of 242b11d4b31ec3ad522fb21932061e5ba7f9019d
Summary: Tests passed: 2862, ignored: 373, muted: 1 Build time: 0:51:57


I want a Plugin that provides the SysML DSL in AaC

Closes #477
Closes #549

Added schema definitions for the variety of SysML Diagram elements
Added root-types for the primary SysML diagrams

This story has been quite a learning experience for SysML. I referred to a number of sources, which I'll record here, but I found them to not be as extensive as would be helpful for this exercise. I also noted a number of behaviors in the SysML language and its constraints that we'll need to spend more time aligning this plugin with in future iterations.
A number of these schemas have 'tbd' in their fields. I'm largely blocked by some inadequacies in AaC (no union typing), and deliberation with SysML stakeholders on how to best represent SysML models in AaC (do we go back on defining all concrete diagram elements and leverage the more abstract syntax to get around some issues of multiple schema types being acceptable for a single field?).
SysML References:
SysML 1.5 Specification
SysML Explained
Overview of SysML and SysML diagrams
SysML and MBSE
3rd Party user docs for SysML 1.5
Some educational slides on SysML including examples
UML2 Specification which provides some underlying understanding to SysML, which largely extends UML2

Examples of conversion:
Source SysML model
blockDefinitionDiagram:
    name: FiringRange
    description: |
        This model provides a simple use-case example for the the BDD diagram 'FiringRange' described in figure E.22 of
            the SysML v1.6 specification, found on page 355.
    defaultNamespace: FiringRangeNamespace
---
block:
    name: FiringRangeNamespace
---
block:
    name: Cannon
---
block:
    name: Shot

Converted Core Model
model:
  name: FiringRange
  description: ''
  components: []
  behavior: []
  state: []
  sysmlElement: SysML.BlockDefinitionDiagram
---
model:
  name: FiringRangeNamespace
  description: ''
  components: []
  behavior: []
  state: []
  sysmlElement: SysML.Block
---
model:
  name: Cannon
  description: ''
  components: []
  behavior: []
  state: []
  sysmlElement: SysML.Block
---
model:
  name: Shot
  description: ''
  components: []
  behavior: []
  state: []
  sysmlElement: SysML.Block

Converted Core Model Converted Back to SysML
blockDefinitionDiagram:
  name: FiringRange
  defaultNamespace: ''
  blocks: []
---
block:
  name: FiringRangeNamespace
  values: {}
---
block:
  name: Cannon
  values: {}
---
block:
  name: Shot
  values: {}


Parser Issue Findings from Fuzzing

Prerequisites

[X] Can you reproduce the problem in a MWE?
[X] Are you running the latest version of AngleSharp?
[X] Did you check the FAQs to see if that helps you?
[X] Are you reporting to the correct repository? (there are multiple AngleSharp libraries, e.g., AngleSharp.Css for CSS support)
[X] Did you perform a search in the issues?

Description
A small input is enough to hang the HTML parser (indefinitly?).
Steps to Reproduce
var html = "
<menu><svg><template><nobr>
<nobr>";
or
var html = "
<svg><template>";
var parser = new AngleSharp.Html.Parser.HtmlParser();
parser.ParseDocument(html.ToCharArray(), 0);

Expected Behavior
Don't take that long.
Actual Behavior
Hangs for at least 10min. Did not test longer.
Possible Solution / Known Workarounds
No response

I appreciate the fuzzying there - but could you aggregate the findings?
Also better titles would help. I've changed this one to use the issue for all the findings.

If that makes it clearer and easier, of course. But I don't expect much more findings.

Found one input that still timeouts on the newest 1.1.1 release:
"

I've brought it over to a new issue for the 1.1.2. Please put all your findings in this one; the HTML snippet / input is sufficient.


shrinkwrap update for js and markdown

@kieferrm @ramya-rao-a What's up with this one? Should we merge it, close it or defer to February?

I ran the shrinkwrap tool last time and found these diffs. They were not merged, because testing was done by then and so this was pushed to Jan.
Looks like we are having the same situation again

OK, we should do this at the beginning of a milestone. Pushing this out.

I am closing this, as it is quote obsolete now


dep does not handle peer dependency correctly

What version of dep are you using (dep version)?

dep:
 version     : v0.4.1
 build date  : 2018-01-24
 git hash    : 37d9ea0a
 go version  : go1.9.1
 go compiler : gc
 platform    : linux/amd64

Gopkg.toml
[prune]
  go-tests = true
  unused-packages = true

[[constraint]]
  name = "github.com/hashicorp/consul-template"
  version = "0.19.4"

[[constraint]]
  name = "github.com/kelseyhightower/envconfig"
  version = "1.3.0"

What dep command did you run?
❯ dep ensure -add<EMAIL_ADDRESS>
Warning: Gopkg.lock is out of sync with Gopkg.toml or the project's imports.
Fetching sources...

Solving failure: No versions of github.com/hashicorp/consul-template met constraints:
        v0.19.4: Could not introduce<EMAIL_ADDRESS>as it has a dependency on github.com/hashicorp/vault with constraint ^0.8.1, which has no overlap with existing constraint ^0.9.5 from (root)
....

What did you expect to see?
I expected that dep would easily add the dependency since caret symbol means from specified version till major version.
As explained in dep docs https://golang.github.io/dep/docs/Gopkg.toml.html#version .
Specific quote:
^: major range. Eg: ^1.2.3 is equivalent to >= 1.2.3, < 2.0.0

What did you see instead?
Error message that it's unable to find a satisfiable dependency to install.

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


CTAS on Azure SQL

We're running our dbt projects agains Azure SQL database, and in order for models to work we had to modify
https://github.com/microsoft/dbt-fabric/blob/e8a59ed8a9167cc46d4a75819793aed48a9c038a/dbt/include/fabric/macros/materializations/models/table/create_table_as.sql#L27
by adding WITH (DISTRIBUTION = ROUND_ROBIN)
Not sure what the correct solution is for all favours of SQL on Azure so please advise and make necessary changes.

@ms32035 , this adapter supports only Fabric DW.
you need to dbt-synapse adapter for Azure Synapse Data Warehouse (Synapse Dedicated SQL Pool)
You need to use dbt-sqlserver for other flavors of Microsoft SQL.


Unit testing of vertical regridding code

Just making a note here that we do need to think about some unit testing for the vertical regridding code, both for MAPL3 and just so that if people do want to clean/optimize we don't break it.
I do think that we at least need to have some realistic inputs for the unit tests, if synthetic they need be somewhat realistic. The whole point of the main event in this code is given a level(s), say 1000mb, 950mb, and a variable that defines the column edge pressures interpolate another variable defined on those column edges or centers of each column level to those output levels(s).
It would be non-sense to generate say a synthetic PLE for a column that was not not monotonic increasing or decreasing set of numbers, so if you are going to generate synthetic inputs, it at least better be physically reasonable.
I would argue let's just capture several representative columns of edge pressures as inputs for a unit test and be done with it. Or write some code to generate physically reasonable synthetic pressure columns.

I'll try to dig up an old presentation where I used interpolation (1D) as an example for demonstrating test driven development.     In general, unit testing is quite friendly to this type of layer, but the interfaces may need to be modified to be more well-suited, and we may have to factor out more helper procedures than is typically the case.
The basic approach is to break the problem into 3 distinct issues:

For a given x, find the bracket that contains x
For a given x within a bracket b, compute the weight(s).

subtests should include point on each node, point in the middle, etc.

Iterate over x's

Testing the latter is a bit less valuable of course.
Now if vectorization is unfriendly to such small procedures with narrow interfaces,  you use the well-tested procedures as the "expected" result for the fully fused/integrated interfaces.   Might have to allow for roundoff depending.
The variant here is the use of a reference pressure.   That will add a bit of complexity, but I doubt it will substantially change the approach.
Synthetic values are used everywhere ...

I'll have to refresh my memory about the interface (probably needs to be trashed and cleaned up, I just pulled the code out of History and put it in a module) and what this code actually does before we go too far into how to test this or having a discussion about the details.


Update product handbook

This PR:

Cleans up some stale portions of the handbook
Adds a new "features" page to help us align on terminology around features.

@aaronsteers @seth-meltano would appreciate your review on this PR. This is to give us an initial language around Core and Cloud features. Please feel free to suggest any changes!
Note that I was heavily inspired by https://docs.getdbt.com/docs/dbt-versions/product-lifecycles


CI for publishing website from main

Description
CI to publish docs from latest main independent of releases.
Type of change

[ ] :sunflower: Feature
[ ] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Test
[x] :computer: CI/Deployment
[ ] :hamster: Trivial/Minor

Issue(s)

#

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

This can be run by using manual trigger on the Publish Docs workflow.

Closing as the CI will change now that we are merging both docs and website.
https://github.com/alcionai/corso/issues/1551


#14199: catch subprocess.CalledProcessError in get_gpus()

Description
fixes: #14199
Calling subprocess may fail with non-zero code. Catching subprocess.CalledProcessError to avoid get_gpus() crash.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[X] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[X] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[X] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@frankfliu  thanks for the contribution, could you also change here:
https://github.com/apache/incubator-mxnet/blob/master/tools/bandwidth/test_measure.py#L27
and here:
https://github.com/apache/incubator-mxnet/blob/master/benchmark/python/control_flow/rnn.py#L84
I believe that's all the usage of get_gpus()

@mxnet-label-bot add[Example, Exception Handling, pr-awaiting-review]

Couldn't we replace that with the native version? https://github.com/apache/incubator-mxnet/blob/master/src/c_api/c_api.cc#L130

Couldn't we replace that with the native version?
incubator-mxnet/src/c_api/c_api.cc
Line 130 in fdbc433
int MXGetGPUCount(int* out) {

I think we should add a new formal python API that expose MXGetGPUCount(int* out), so all examples can use it.
This PR is a quick patch for those examples.

I have a question.
Is it continuous for valid GPU ids?

Yes, the GPU ids are continuous, and start from 0.
The existing get_gpus() implementation also return a list of gpu ids as range(len(...))

@frankfliu could you re-trigger CI? This PR can be merged once CI passes.

The PR has been merged.
Thanks for your contribution!


Updated parser

now you don't need to spacing tokens

Started to check

I think you didn't code about the first whitespace in line of code.

wait a sec... you made code about that error...

@codenstory I fixed. 🎉

Thank you !


build fails if Python 3 is used to drive scons

Description
Project will not build if Python 3 is used to drive scons.
To Reproduce
python3 /usr/bin/scons
(or wherever scons is).  Fails quickly with
scons: Reading SConscript files ...
  File "/home/mats/github/one/SConstruct", line 189

    except Exception, e:

                    ^

SyntaxError: invalid syntax

Expected behavior
Build proceeds normally instead of erroring out immediately.
Details
Someone turned up on the scons freenode IRC channel concerned that Arch Linux has switched their scons to be run by Python3, and this project wouldn't build as a result.  As a contribution, have attached a patchfile here that addresses the obvious issues without breaking the ability to run through Python 2, can't really push it further since on the local system there are complaints about xmlrpc and I don't have any incentive to push through to get a full build going.  Do with it what you want!
0001-Port-build-scripts-to-Python3.patch.gz
Additional context
Add any other context about the problem here.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Thx you very much for the report and the patch. That fix the issue.


readable_time format fixed

The logic doesn't work for Python3 (need to use // (floor division) instead of / (true division) in python3).
For the sake of simplicity, I fixed it using equality operators.

good job.


Node retries not compatible with timeouts

I'm looking at integrating superagent to make a server side call to a flaky backend API.  The API either responds quickly or doesn't respond at all and needs to therefore be retried.
I'm therefore using retry(3) in combination with timeout({ deadline: 3000 }).  However the timeout is overruling the retry and throwing an Aborted error which returns a 500 error to the client. From what I can tell the following is happening when the request takes too long:

Superagent makes a get request to backend API
GET request times out so emits an abort
abort handler then rejects the request
Retry logic kicks in and decides that we should retry
Aborted error then causes 500 error to client
Backend API is then retried
If API call fails then is retried twice more otherwise finishes

Looking at the code the retry logic attempts to reset the _aborted and timedout properties, but it looks like by then it is too late as reject is called.
Is there a way I can therefore retry when the API call times out?

I've investigated a bit further and it turns out that the timeout functionality is not compatible with using the promise version of superagent i.e. using then.  When using end and wrapping the superagent call in a manual promise instead then it all works as expected and the request is retried after it times out.

I found the same problem in version 5.0.5.  Using .timeout() with .retry() worked in version 3.8.3.

The issue here is that when a timeout occurs, superagent calls req.abort(), which emits an aborted message, which is handled by rejecting the promise with err.code == ABORTED.  Only then does it try to reject with a timeout error -- but the promise has already rejected so that second error is silently ignored.

To reproduce:
const request = require('superagent');

const main = async () => {
  const req = request('http://localhost:8000');
  req.timeout(1000);
  await req.catch(err => {
    if (err.timeout) {
      console.log('got timeout');
    }
    throw err;
  });
};

main().then(console.log, console.log);

and in another terminal, run a server that will not reply.  Netcat will do:
nc -klp 8000

v5.3.0 published to npm and GitHub releases page with changelog


NCSC Vendor Security Assessment V.B.5 Unsafe functions - not used in vendor's released code

This is language independent issue. In a  nutshell UK NCSC require to have no "unsafe functions" in their code without providing a list of them. This is a prerequisite to deliver products into the UK market.
I believe that there is a high risk that misinterpretation can lead suppliers to return to "custom implementations" to avoid "unsafe functions" like what we had 20-30 years ago subsequently causing more un-tracked vulnerabilities.
The UK NCSC requires in V.B.5:

Security expectation: "There are no unsafe functions used within the vendor’s released code. Unsafe functions are those commonly associated with security vulnerabilities or those considered unsafe by industry best practice".
Why it matters: "These functions are frequently the cause of product vulnerabilities"
Evaluation, Security declaration: "The Security Declaration clearly states whether unsafe functions are used within the vendor’s code base."
Evaluation, customer or 3rd party spot checks: "Request code metrics on use of unsafe functions"

https://www.ncsc.gov.uk/files/[NCSC-Vendor-Security-Assessment.pdf](https://www.ncsc.gov.uk/files/NCSC-Vendor-Security-Assessment.pdf)

I think the link there is incorrect. The right one is this

I will see if I can find a contact point.


let directive: pass error value as context to error template when using template anchors

Problem Solved By The Feature
Currently if using template anchors the error template will receive a context $error = true.
With no context of the actual error
https://github.com/BioPhoton/rx-angular/blob/e1fe3b381d85aaf232873a6655bed08b533692d1/libs/template/src/lib/let/let.directive.ts#L334
Solution
Pass the error as the implicit context for the view:
this.templateManager.updateViewContext({        $implicit: error,        $error: true,   });

Hi @codingnuclei!
Thanks for your feedback!
The first implementation had the error as value instead of treu for $error.
What would you do with the original error?
Just try to gather more information...

For me the observable is a network request. So the errors are network errors.
It would be nice to display different errors messages based on the error... Not just "There has been an error".
Out of interest why was it changed from the original?

Hi @codingnuclei.
Can you take a look at the PR #295.
There i implemented your request is a slightly different way. Let me know what you think.

Yea that solves the issue nicely.
I like the futures of being able to access the last value too in the future. Although not required for my use case, I can definitely see other use cases that would need it!


add DTLS support, upgrade packages, remove obsolete .NET Framework

This adds DTLS support (fixes #5), including examples for both server and client. This should work with certificate-based authentification/encryption and TLS-PSK, but only TLS-PSK has been tested.
Also, some NuGet packages were upgraded and .NET Core 2.0 support was either removed (for libraries) or replaced by .NET 5.0 (for executables), as .NET Core 2.0 is no longer supported by Microsoft.

It looks good to me, I'm impressed with the readability of the implementation. It has also added doubt to some of the API design that I've provided. I'll get a version published soon and then work on implementing tests, plus certificate based connections for more more complete DTLS support.
Thank you very much!


Fix scoring DB query error

It seems it's possible for the scoring DB to have the same color code repeated in the DB, which was causing a subquery error message in the vector tile generation.

Superseded by #362


link chapter 9 inside 6 - and more cross linking in general.

### Tasks
- [x] chapter 9 (Modules Events and Functions) in 6 (metadata and module files)
- [x] other

done 4d8b667e94c993760909fdf0e7655d5c069f8aa0


Using EmojiArea with Coocon gem

First of all allow me to say, THANK YOU for this great gem. It has saved me so much time so many times. So I really appreciate your work and to make this great gem🥇 💯
In my application, I have messages & translations. Everything works fine regarding nested forms and all, but this time I need to implement EmojiArea.
This is my set up:
# _form.html.haml
= f.input :title, input_html: {class: 'emojioneArea'}
= f.input :body, input_html: {class: 'emojioneArea'}
#translations
  = f.simple_fields_for :translations do |translation|
    = render 'translation_fields', f: translation
  .link
    = link_to_add_association 'Add New', f, :translations

:javascript
  $(document).ready(function() {
    $(".emojioneArea").emojioneArea({
      emojiPlaceholder: ":smile_cat:",
      pickerPosition: "bottom",
      searchPosition: "bottom"
    });
  });

# _translation_fields.html.haml
.nested-fields
  = f.input :title input_html: {class: 'emojioneArea'}
  = f.input :body, as: :text, input_html: {class: 'emojioneArea'}
  = link_to_remove_association 'Remove', f

# MessagesController
def new
    @message.translations.build
end

This works fine for the inputs that are already added when the page is loaded (which is understandable because of $(document).ready(function()), but than new nested forms inputs doesn't get EmojiArea.
so I changed my javascript in _form.html.haml to:
:javascript
  $(document).ready(function() {
    $('#translations')
      .on('cocoon:after-insert', function() {
        $(".emojioneArea").emojioneArea({
          emojiPlaceholder: ":smile_cat:"
        });
      });
  });

Which adds the EmojiArea after a nested form is added but inputs that were added on the page load, doesn't have EmojiArea (which is again understandable because of .on('cocoon:after-insert', function() ), BUT this makes the form to behave really strange.
I wasn't sure how I could explain it so instead, I created a video/gif to give a better overview.

When I change my javascript to (below), inputs will have the EmojiArea from start but, that strange behaviour still there.
:javascript
  $(document).ready(function() {
   $(".emojioneArea").emojioneArea({
      emojiPlaceholder: ":smile_cat:",
      pickerPosition: "bottom",
      searchPosition: "bottom"
    });
    $('#translations')
      .on('cocoon:after-insert', function() {
        $(".emojioneArea").emojioneArea({
          emojiPlaceholder: ":smile_cat:"
        });
      });
  });

Any feedback and help are much appreciated and thanks in advance!

Thank you for your detailed question :clap: :clap: :+1:
Now you already do everything near perfectly, as far as cocoon is related imho. The only thing I can imagine, which could explain maybe strange behaviour, is if the emoji-picker acts strange when it is "enabled" multiple times.
So an easy fix for that would be:
:javascript
  $(document).ready(function() {
   $(".emojioneArea").emojioneArea({
      emojiPlaceholder: ":smile_cat:",
      pickerPosition: "bottom",
      searchPosition: "bottom"
    });
    $('#translations')
      .on('cocoon:after-insert', function(e, s) {
        s.find(".emojioneArea").emojioneArea({
          emojiPlaceholder: ":smile_cat:"
        });
      });
  });

This will only enable the emojioneArea inside the newly inserted nested item (after the insert).
But if this does not help, I am afraid this not an issue for the emoji-picker you are using. I have no idea what the normal behaviour is for the plugin, and  I cannot see how I can help other then start to investigate the emoji-picker plugin you are using.

 You just made my Friday :)
Thanks a lot for your help 👍


[DIR-631] utility function to call clsx and twmerge

Good job. I also added it to the ButtonBar component and added a description above twMergeClsx
I wonder if from now on, we always use this function even if we don't need the functionality of twmerge.
Can you search for import clsx from "clsx" in the entire project and replace it with our new twMergeClsx?

FYI: there is a new feature in our Github actions. We now have preview links for all pull requests and for every push to the redesign branch.
This means the latest redesign status is now always available at (it automatically updates when we merge new features into the redesign branch): https://direktiv-ui-refs-heads-feature-redesign.direktiv.dev
Also on every PR, there is a new action called Create and push PR Docker image / deploy-review-app (pull_request)  (you can see it in this PR too). When you click on Details, and then Summary at the top you see a link to a preview of this PR

👌


Build the style guide (Components: Selector)

The design team has built the Style guide, which can be found here.
This issue is a chunk of #4, ensure to check it first.

Build the Selector components similar to the design and document all classes used
Build with great focus on all states and responsiveness.

Hey @BolajiAyodeji ,
what's the difference between a Selector and a Checkbox/Radio button?

Hey @BolajiAyodeji ,
what's the difference between a Selector and a Checkbox/Radio button?

It's actually the same thing, just some border radius for the selector according to the style guide. The design team separated it so I thought to create an issue for it with level simple. Looks like the easiest ticket :sweat_smile:

Yes, I get that. I'm having a hard time figuring out the difference between what a selector does and what a Checkbox / Radio button helps us achieve? I might be overthinking it, but I'll probably pick another ticket.

I'll have to cc @perriefidelis again here so the design team can explain better.
I want to believe, the Checkbox actually allows the user to select an option, the comparison should be between the Checkbox and Radio buttons and maybe there shouldn't be a Selector component after all. I'll get back to this with more context from the design team, please feel free to pick another ticket.

Yeah, for a bit of context @perriefidelis.
Since the checkbox and radio components act as selectors for multiple and single entities respectively, I'm uncertain the value the selector component will add since both components listed above already helps us achieve this.

Sorry for the delays with this. I got word from the design team that the style guide is actually not just for the website but also for their general designs so some components are actually not meant for dev.
I'll be closing this issue for now and apologies for the confusion.


Create LICENSE

:+1: To be explicit, I'm releasing all the code I have Copyright on in this repository under the MIT License.


Add validation when git credential type does not match git URL

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
Updating to v2.2.0 caused workflows to break which contained a git checkout input artifact
What you expected to happen:
The git checkout would continue to work
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Argo version: v2.2.0
Kubernetes version : v1.10.0

Other debugging information (if applicable):

executor logs:

# init:
❯ k logs -f -c init argo-test-8zb2g-438481831
time="2018-08-30T21:00:25Z" level=info msg="Creating a docker executor"
time="2018-08-30T21:00:25Z" level=info msg="Executor (version: v2.2.0, build_date: 2018-08-30T08:52:54Z) initialized with template:\narchiveLocation: {}\ncontainer:\n  <bunch of sensitive stuff removed> \ninputs:\n  artifacts:\n  - git:\n      passwordSecret:\n        key: password\n        name: github-creds\n      repo: https://github.com/<removed>.git\n      revision: <removed>\n      sshPrivateKeySecret:\n        key: ssh-private-key\n        name: github-creds\n      usernameSecret:\n        key: username\n        name: github-creds\n    name: code\n    path: /app\nmetadata: {}\nname: build-statics\noutputs: {}\n"
time="2018-08-30T21:00:25Z" level=info msg="Start loading input artifacts..."
time="2018-08-30T21:00:25Z" level=info msg="Downloading artifact: code"
time="2018-08-30T21:00:25Z" level=info msg="Alloc=3609 TotalAlloc=9938 Sys=10086 NumGC=3 Goroutines=4"
time="2018-08-30T21:00:25Z" level=fatal msg="invalid auth method\ngithub.com/argoproj/argo/errors.Wrap\n\t/root/go/src/github.com/argoproj/argo/errors/errors.go:87\ngithub.com/argoproj/argo/errors.InternalWrapError\n\t/root/go/src/github.com/argoproj/argo/errors/errors.go:70\ngithub.com/argoproj/argo/workflow/artifacts/git.gitClone\n\t/root/go/src/github.com/argoproj/argo/workflow/artifacts/git/git.go:56\ngithub.com/argoproj/argo/workflow/artifacts/git.(*GitArtifactDriver).Load\n\t/root/go/src/github.com/argoproj/argo/workflow/artifacts/git/git.go:34\ngithub.com/argoproj/argo/workflow/executor.(*WorkflowExecutor).LoadArtifacts\n\t/root/go/src/github.com/argoproj/argo/workflow/executor/executor.go:139\ngithub.com/argoproj/argo/cmd/argoexec/commands.loadArtifacts\n\t/root/go/src/github.com/argoproj/argo/cmd/argoexec/commands/init.go:35\ngithub.com/argoproj/argo/cmd/argoexec/commands.glob..func1\n\t/root/go/src/github.com/argoproj/argo/cmd/argoexec/commands/init.go:17\ngithub.com/argoproj/argo/vendor/github.com/spf13/cobra.(*Command).execute\n\t/root/go/src/github.com/argoproj/argo/vendor/github.com/spf13/cobra/command.go:766\ngithub.com/argoproj/argo/vendor/github.com/spf13/cobra.(*Command).ExecuteC\n\t/root/go/src/github.com/argoproj/argo/vendor/github.com/spf13/cobra/command.go:852\ngithub.com/argoproj/argo/vendor/github.com/spf13/cobra.(*Command).Execute\n\t/root/go/src/github.com/argoproj/argo/vendor/github.com/spf13/cobra/command.go:800\nmain.main\n\t/root/go/src/github.com/argoproj/argo/cmd/argoexec/main.go:15\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:198\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:2361"

The conclusion (over slack) was that a sshPrivateKeySecret was supplied, even though the git URL was an http url (and not an ssh url).
We can improve the behavior to detect this, and either fail validation or fail with a better error message since the auth type needs to match the protocol.


clusters do not delete

command finishes if i delete cluster from console.
bash-3.2$ coldbrew cluster-delete demo-platespace
Determining AWS resources that need to be deleted...
  ECS Cluster: coldbrew-demo-platespace
  IAM Role for ECS Services: coldbrew-demo-platespace-ecs-service-role
  EC2 Launch Configuration for ECS Container Instances: coldbrew-demo-platespace-lc
  EC2 Auto Scaling Group for ECS Container Instances: coldbrew-demo-platespace-asg
  IAM Instance Profile for ECS Container Instances: coldbrew-demo-platespace-instance-profile
  EC2 Security Group for ECS Container Instances: coldbrew-demo-platespace-instance-sg

> Do you want to delete these resources? [y/N]: y

[*] Terminating instances in EC2 Auto Scaling Group [coldbrew-demo-platespace-asg]... (this may take long)
[-] Deleting EC2 Auto Scaling Group [coldbrew-demo-platespace-asg]... (this may take long)
[-] Deleting EC2 Launch Configuration [coldbrew-demo-platespace-lc]...
[-] Deleting IAM Instance Profile [coldbrew-demo-platespace-instance-profile]...
[-] Deleting EC2 Security Group [coldbrew-demo-platespace-instance-sg]...
[-] Deleting ECS Cluster [coldbrew-demo-platespace]...

Error: Failed to delete ECS Cluster [coldbrew-demo-platespace-ecs-service-role]: ClusterContainsServicesException: The Cluster cannot be deleted while Services are active.
	status code: 400, request id: 87dbb57b-7ba6-11e7-8f63-4549790bf4f0

Did you delete all apps (ECS services) on that cluster?

User error.  closing.


Call the correct haproxy reload handler

Tests failed because cirros url path may have changed.

The tests failed, because 1.1.x doesn't pass tests right now. However the change is pretty simple, and worked for venom patching, so merging it in.
YOLO.


Laravel Updater

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v7.25.0 branch.
Before merging, you need to:

Checkout the shift-ci-v7.25.0 branch
Review all pull request comments for additional changes
Run composer update
Test your application (no tests?)

:warning: You are running version 5.3.4 of guzzlehttp/guzzle. The latest version is 7.0.1. You should review this dependency to see if you can upgrade to the latest version.

:information_source: You are running an older version of Laravel. The latest version is 7.25.0. Run the Laravel 7.x Shift to upgrade to the latest version of Laravel.

:warning: You are running version 1.0.10 of laravel/tinker. The latest version is 2.4.1. You should review this dependency to see if you can upgrade to the latest version.

:warning: You are running version 0.14.0 of league/fractal. The latest version is 0.19.2. You should review this dependency to see if you can upgrade to the latest version.

:warning: You are running version 3.9.3 of ramsey/uuid. The latest version is 4.1.0. You should review this dependency to see if you can upgrade to the latest version.


Add support for Actions via Vue.Provide/Inject API

Register actions defined as part of the helper as app.provide functions to allow all components to call those functions.

Done as of v0.0.4


bluetooth: Add get-primary-services sample

Pending https://codereview.chromium.org/2027973002/
R=@g-ortuno @scheib @jyasskin @jeffposnick

Two thoughts:

I wonder if it would be better to have two fields: one dropdown list, like the one we use in other samples, and another text input field for custom UUIDs. Having to write 'heart_rate' every time I want to use the sample is going to be a bit annoying. Or have 'Custom UUID' as one of the options in the list and when that is selected the text input field appears. That requires more UI code, so I would be OK with just two fields.

I'm not sure how useful this will be. You basically just get whatever services you put in. A combined sample with getCharacteristics might be better?

I wonder if it would be better to have two fields: one dropdown list, like the one we use in other samples, and another text input field for custom UUIDs. Having to write 'heart_rate' every time I want to use the sample is going to be a bit annoying. Or have 'Custom UUID' as one of the options in the list and when that is selected the text input field appears. That requires more UI code, so I would be OK with just two fields.

Let's give it a try.

I'm not sure how useful this will be. You basically just get whatever services you put in. A combined sample with getCharacteristics might be better?

Indeed that was what I was afraid of... I'm afraid the combined sample will look a lot like the Get Characteristics Beginner Sample though. Let's try though.

@g-ortuno I've taken in account your feedback. WDYT?

Can you add another screenshot?

@g-ortuno, here it is:

And you can try it at https://beaufortfrancois.github.io/samples/web-bluetooth/discover-services-and-characteristics.html

@g-ortuno I've include all your feedback and it looks a lot nicer. Thanks! I'll publish it now.

It is now publicly accessible at https://googlechrome.github.io/samples/web-bluetooth/discover-services-and-characteristics.html

Thinking more about it, the refactoring doesn't handle properly the rejected promise of getCharacteristics().... I'm not sure if adding a catch  is better than returning Promise.all.

One way to solve this is to adding a catch. WDYT @g-ortuno?
I'm not a big fan of it as it now has 2 catches to handle errors when really only one is needed.
diff --git a/web-bluetooth/discover-services-and-characteristics.js b/web-bluetooth/discover-services-and-characteristics.js
index b2b1d14..9659c52 100644
--- a/web-bluetooth/discover-services-and-characteristics.js
+++ b/web-bluetooth/discover-services-and-characteristics.js
@@ -31,6 +31,9 @@ function onButtonClick() {
           log('>> Characteristic: ' + characteristic.uuid + ' ' +
               getSupportedProperties(characteristic));
         });
+      })
+      .catch(error => {
+        log('Argh! ' + error);
       });
     });
   })

Or a Promise queue like we did before:
diff --git a/web-bluetooth/discover-services-and-characteristics.js b/web-bluetooth/discover-services-and-characteristics.js
index b2b1d14..e522934 100644
--- a/web-bluetooth/discover-services-and-characteristics.js
+++ b/web-bluetooth/discover-services-and-characteristics.js
@@ -24,15 +24,17 @@ function onButtonClick() {
   })
   .then(services => {
     log('Getting Characteristics...');
+    let queue = Promise.resolve();
     services.forEach(service => {
-      service.getCharacteristics().then(characteristics => {
+      queue = queue.then(_ => service.getCharacteristics().then(characteristics => {
         log('> Service: ' + service.uuid);
         characteristics.forEach(characteristic => {
           log('>> Characteristic: ' + characteristic.uuid + ' ' +
               getSupportedProperties(characteristic));
         });
-      });
+      }));
     });
+    return queue;
   })
   .catch(error => {
     log('Argh! ' + error);

And I think I like this one better. So I'll go with it for now. Please let me know what you think.

Hi @beaufortfrancois ! i'm gettinng some trouble in getPrimaryService function. It is not retrieving anything and i don't understand why. Could you help me? Thank in advance


Exception when setting security_groups

I am setting security_groups with the following in my Vagrantfile:
config.vm.provider :aws do |aws, override|
    aws.access_key_id = <REDACTED>
    aws.secret_access_key = <REDACTED>
    aws.keypair_name = <REDACTED>

    aws.ami = "ami-7747d01e"
    aws.instance_type = 't1.micro'

    aws.security_groups = ['vagrant']

    override.ssh.username = "ubuntu"
    override.ssh.private_key_path = <REDACTED>
  end

I created the vagrant security group via the AWS web interface. I can connect without specifying a security group, but then my SSH command hangs.
Unfortunately, having the "aws.security_groups" line present causes a huge exception:
ERROR warden: Error occurred: Expected(200) <=> Actual(400 Bad Request)
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<VagrantPlugins::AWS::Action::RunInstance:0x007f29c0899270>
 INFO machine: Calling action: read_state on provider AWS (new)
 INFO runner: Running action: #<Vagrant::Action::Builder:0x007f29c04fd4b8>
 INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x007f29c0502bc0>
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ConnectAWS:0x007f29c0502b98>
 INFO connect_aws: Connecting to AWS...
 INFO warden: Calling action: #<VagrantPlugins::AWS::Action::ReadState:0x007f29c00dc0c8>
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: Expected(200) <=> Actual(400 Bad Request)
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000001249658>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Running hook: environment_unload
 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000000177b4f0>
/home/fil/.vagrant.d/gems/gems/excon-0.22.1/lib/excon/middlewares/expects.rb:10:in `response_call': Expected(200) <=> Actual(400 Bad Request) (Excon::Errors::BadRequest)
    from /home/fil/.vagrant.d/gems/gems/excon-0.22.1/lib/excon/connection.rb:355:in `response'
    from /home/fil/.vagrant.d/gems/gems/excon-0.22.1/lib/excon/connection.rb:249:in `request'
    from /home/fil/.vagrant.d/gems/gems/fog-1.10.1/lib/fog/core/connection.rb:21:in `request'
    from /home/fil/.vagrant.d/gems/gems/fog-1.10.1/lib/fog/aws/compute.rb:384:in `_request'
    from /home/fil/.vagrant.d/gems/gems/fog-1.10.1/lib/fog/aws/compute.rb:379:in `request'
    from /home/fil/.vagrant.d/gems/gems/fog-1.10.1/lib/fog/aws/requests/compute/run_instances.rb:119:in `run_instances'
    from /home/fil/.vagrant.d/gems/gems/fog-1.10.1/lib/fog/aws/models/compute/server.rb:173:in `save'
    from /home/fil/.vagrant.d/gems/gems/fog-1.10.1/lib/fog/core/collection.rb:52:in `create'
    from /home/fil/.vagrant.d/gems/gems/vagrant-aws-0.2.2/lib/vagrant-aws/action/run_instance.rb:76:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/fil/.vagrant.d/gems/gems/vagrant-aws-0.2.2/lib/vagrant-aws/action/warn_networks.rb:14:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/fil/.vagrant.d/gems/gems/vagrant-aws-0.2.2/lib/vagrant-aws/action/sync_folders.rb:21:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/provision.rb:45:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /home/fil/.vagrant.d/gems/gems/vagrant-aws-0.2.2/lib/vagrant-aws/action/connect_aws.rb:41:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/machine.rb:147:in `action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run

I'm having the same problem, Has anyone managed to solve this problem?
/Users/fabiano/.vagrant.d/gems/2.4.2/gems/excon-0.60.0/lib/excon/middlewares/expects.rb:7:in response_call': The key pair 'vagrant' does not exist (Fog::Compute::AWS::NotFound)`
PS: I have already created the "key pair" in aws with the name "vagrant"


[SPARK-24151][SQL] Case insensitive resolution of CURRENT_DATE and CURRENT_TIMESTAMP

What changes were proposed in this pull request?
SPARK-22333 introduced a regression in the resolution of CURRENT_DATE and CURRENT_TIMESTAMP. Before that ticket, these 2 functions were resolved in a case insensitive way. After, this depends on the value of spark.sql.caseSensitive.
The PR restores the previous behavior and makes their resolution case insensitive anyhow. The PR takes over #21217, therefore it closes #21217 and credit for this patch should be given to @jamesthomp.
How was this patch tested?
added UT

cc @dongjoon-hyun @HyukjinKwon @viirya

ok to test

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3152/
Test PASSed.

Merged build finished. Test PASSed.

Test build #96136 has started for PR 22440 at commit 49595c0.

Test build #96129 has started for PR 22440 at commit e207e60.

Test build #96130 has started for PR 22440 at commit 49595c0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3153/
Test PASSed.

Test build #96130 has finished for PR 22440 at commit 49595c0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96130/
Test FAILed.

Retest this please.

Thank you, @mgaido91 .

Test build #96136 has finished for PR 22440 at commit 49595c0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96136/
Test FAILed.

@mgaido91 . I know that your test code is bigger than the remaining original code in Analyzer.scala.
However, we changes our way of credits in a explicit manner. If you preserve some of @jamesthomp 's commits, he will be the original author and you will be a co-author as you requested. I prefer this way.
Otherwise, could you add an empty commit with @jamesthomp 's name and email at least? In that case, he will be co-author automatically.

Test build #96129 has finished for PR 22440 at commit e207e60.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

I see @dongjoon-hyun. Sure, sorry I wasn't aware of how this is working. Shall I create a new PR based on @jamesthomp's commits or is it enough to update this adding his commits?
Sorry for the trouble and thanks for guiding me on this.

 Then, I will try to moderate during setting the main author.

Thanks! Merged to master/2.4

Thank you for merging, @gatorsmile ! I like it.


Installation from pip is failing because of missing README.rst

Hey! Just tried to install the package from pip, and it's failing with:
 src/Bot-new   mainline  pip3 install pipeop
Collecting pipeop
  Downloading https://files.pythonhosted.org/packages/f3/71/5449fe7a4ca9ecef67bca9ceb13a163d7326fc0c325b6642694e7da5c0fc/pipeop-0.2.2.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/private/var/folders/bw/539xc4113rd4lcc56p27lq1jghmd7n/T/pip-install-ujbf0qn9/pipeop/setup.py", line 5, in <module>
        with open('README.rst', 'r') as f:
    FileNotFoundError: [Errno 2] No such file or directory: 'README.rst'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/bw/539xc4113rd4lcc56p27lq1jghmd7n/T/pip-install-ujbf0qn9/pipeop/

Tried to fix in 0.2.3 but Artifactory is caching pip and I can only download failing 0.2.2. Will try later, hopefully cache will clear.

Ok 0.2.3 isn't working either. I don't understand why it stopped working. It works when I build the distribution because the rst contents are displayed on Pypi. Any assistance with navigating the intricacies of setup.py voodoo happily accepted.

Created MANIFEST.in, didn't quite understand this previously. Hopefully fixed in 0.2.4

Ok, had to go to 0.2.5 because Pypi wouldn't update 0.2.4. Tested on a new Python container and it installed without issue.


Docker not working

When I try to run it I get this error ERROR: failed to solve: failed to parse stage name "selenium/standalone-/vscode/bin/linux-x64/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/helpers/browser.sh": invalid reference format Docker build failed.

Does this happen during docker build? It looks like your "$BROWSER" environment argument isn't set.
https://github.com/EFForg/badger-sett/blob/5837e2d080a2265c73210b2bb1764cf9f0824096/runscan.sh#L74-L75
https://github.com/EFForg/badger-sett/blob/5837e2d080a2265c73210b2bb1764cf9f0824096/Dockerfile#L4
And then Docker looks for "selenium/standalone-/..." where it should be looking for "selenium/standalone-firefox/..." or whatever .
I think our README is confusing and/or missing some information. Sorry about that!
You should be able to fix your error by prepending your runscan.sh command with BROWSER=chrome (or firefox, or edge).
You can also run crawler.py directly without Docker, you'll just have to set up your pip environment from requirements.txt and check out the Privacy Badger repository yourself and provide a bunch of arguments to crawler.py. For example:
$ ./crawler.py --num-sites 20 --browser chrome --pb-dir ../privacybadger --take-screenshots --log-stdout

Let me know if you have any questions.

That worked. Thank you!


lima blocks on second file when used with deeplima

The command below gets stuck after finishing the first file:
lima -l ud --meta udlang:eng-UD_English-EWT -p deeplima  *.txt

It does not happen with main or deepud pipelines.

The problem arise in deeplima tokenizer libs. An issue has been opened upstream:
https://github.com/aymara/lima/issues/172

Corrected upstream. It works here too.


Consider allowing Push action for branches in "Behind" state

This may be useful while splitting branches (PRs) into two (or more) by commits.

@mkondratek hmm for clarity, could you provide a specific scenario? :thinking:

scenario:

Having a branch feat_1 with two commits:

commit A (older)
commit B (newer)

For some reason (separability of changes' topics, amount of changes, risk of exponential review comment overload :Xd:, whatever) a decision to split the commits between two separate branches has been made
The user checkouts a new branch feat_2 from feat_1 (both are point to the commit B)
The user resets branch feat_1 --hard HEAD~1 in our case (or perform rebase with a drop)
feat_1 is behind and needs to be pushed

Eventually, feat_1 is to contain commit A,  and feat_2 is to contain commit B.
Is it clear now?

Hmm TBH it's a rather rare case... I don't remember when I needed to do sth like that myself (although it isn't completely foreign to me, either) :/
Note that this will most likely require an action from command line anyway (git reset as you mentioned), so the user will most likely already be prepared to issue yet another command.
I don't think we should support every possible scenario; being too inclusive might be confusing for the users and runs against the purpose of left-side bar - to suggest the most viable action for the current branch's state.

okay then, I think we can close this one


:disappointed:

You're using a really old version of rubygems, are you? :)

Fixed in 0.2.2
Also, rebased runner branch


Option to disable escaping

https://mustache.github.io/mustache.5.html

All variables are HTML escaped by default. If you want to return unescaped HTML, use the triple mustache: {{{name}}}.

Do you want this?

I do! Thanks very much! :)


Improve GitHub pack with support for managing releases and deployments (+ add action aliases)

GitHub
Status

pack extension.

Description
Add actions using the GitHub APIs directly so that it's possible to manage GitHub releases & deployments via ST2 (and via ChatOPs).
Checklist (tick everything that applies)

[X] Version bump (required for changed packs)
[X] Code linting (required, can be done after the PR checks)
[X] Tests (not required but really recommended)
[X] Add Action Alias tests
[x] Add support for connecting to GitHub.com and Enterprise at the same time.

Thanks for the review comments @Kami, these have been addressed and it's now ready to be merged if it looks ok to you too :-D

Merged into master.
Nice works and thanks! :+1:


WhereHas and has not working with Model Connection property take default connection

Laravel Version: 9.35.1
PHP Version: 8.0.3
Database Driver & Version:
Mysql 5.7.12

Description:
on server, there is 2 database running on the same rds
database 1 has a user table and user model connection name is old_database
database 2 has a corporate user and the Corporate user model connection name is mysql (default)
when I try to perform any action like whereHas or has via the corporate user to a user then laravel orm ignores connection it always take the default database connection but it is working perfectly with() method
Steps To Reproduce:
User Default table provided by laravel
corporate_users user table
CREATE TABLE corporate_users (
id bigint(20) UNSIGNED NOT NULL,
user_id bigint(20) UNSIGNED DEFAULT NULL COMMENT 'This id will be user id',
name varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
email varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
mobile_number varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
gender enum('male','female') COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'male',
created_at timestamp NULL DEFAULT NULL,
updated_at timestamp NULL DEFAULT NULL,
deleted_at timestamp NULL DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
query
CorporateUser::has('user')->count('id')
Corporate User model

User Model

relationship
public function user()
{
return $this->belongsTo(User::class, 'user_id', 'id');
}
Database config

   'mysql' => [
        'driver' => 'mysql',
        'url' => env('DATABASE_URL'),
        'host' => env('DB_HOST', '<IP_ADDRESS>'),
        'port' => env('DB_PORT', '3306'),
        'database' => env('DB_DATABASE', 'forge'),
        'username' => env('DB_USERNAME', 'forge'),
        'password' => env('DB_PASSWORD', ''),
        'unix_socket' => env('DB_SOCKET', ''),
        'charset' => 'utf8mb4',
        'collation' => 'utf8mb4_unicode_ci',
        'prefix' => '',
        'prefix_indexes' => true,
        'strict' => true,
        'engine' => null,
        'options' => extension_loaded('pdo_mysql') ? array_filter([
            PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
        ]) : [],
    ],
    'old_database' => [
        'driver' => 'mysql',
        'url' => env('OLD_DATABASE_URL'),
        'host' => env('OLD_DB_HOST', '<IP_ADDRESS>'),
        'port' => env('OLD_DB_PORT', '3306'),
        'database' => env('OLD_DB_DATABASE', 'forge'),
        'username' => env('OLD_DB_USERNAME', 'forge'),
        'password' => env('OLD_DB_PASSWORD', ''),
        'unix_socket' => env('OLD_DB_SOCKET', ''),
        'charset' => 'utf8mb4',
        'collation' => 'utf8mb4_unicode_ci',
        'prefix' => '',
        'prefix_indexes' => true,
        'strict' => true,
        'engine' => null,
        'options' => extension_loaded('pdo_mysql') ? array_filter([
            PDO::MYSQL_ATTR_SSL_CA => env('MYSQL_ATTR_SSL_CA'),
        ]) : [],
    ],

Same problem. $table is not ignored but in my case i have dynamic database name so i must use $connection.

I did few tests and $connection isnt ignored. For all whereHas $connection is set from main model
User::whereHas('Roles')->get(); For this Roles using main model $connection = User model connection.
U can work on $table variable and this will work good but if your both databases use other mysql user than this do not work.

I did few tests and $connection isnt ignored. For all whereHas $connection is set from main model User::whereHas('Roles')->get(); For this Roles using main model $connection = User model connection. U can work on $table variable and this will work good but if your both databases use other mysql user than this do not work.

I checked but if both tables are on the same DB then it's not generate any error but if one table is in another database then its generates error because it always use the parent model connection

Yes but if both tables are on same server and 1 user have access to them u can set $table like $table = 'second_db.users'; and this will work. If u have pivot table than u must set this also in relation (second parameter in belongsToMany).
If databases are on different server than RIP 💀

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

Yes but if both databases are on same server and 1 user have access to them u can set $table like $table = 'second_db.users'; and this will work. If u have pivot table than u must set this also in relation (second parameter in belongsToMany). If databases are on different server than RIP 💀

we have 4 database 2 for dev and 2 for producation

model connection is working perforate  with with or withcount it is only generating errors with has and whereHas
it taking the parent model connection value
Here is Error Reproduce here is code for Reproduce
just clone repo and make 2 database test_1 and test_2 and i also added factory as well
in index route I added code which generates errors
corporates table is on test 1 database
employees table is on test 2 database
SELECT
*
FROM
corporates
WHERE
EXISTS (
SELECT
*
FROM
employees
WHERE
corporates.id = employees.corporate_id
AND status = active
)
Steps To Reproduce with code ;
https://gitlab.com/MohinSandhi/laravel-wherehas-and-has-issue


Removes setup dependency on pytest-runner

This dependency is only useful to be able to run tests using setup.py,
which is not something that is done. This allows us to drop a dependency
and make packaging for distributions easier.
Fixes: #15

Pull Request Test Coverage Report for Build 71

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 98.503%

Totals

Change from base Build 66:
-0.4%

Covered Lines:
658

Relevant Lines:
668

💛  - Coveralls


Configuration via yml

Using ogm with dropwizard it would be great if the configuration could be done via yml.
neo4j:
driverConfiguration: (driver?)
credentials:
username: neo4j
password: neo4j
...
It seems that some default constructors and a top-down approach are missing.

Hi @danielmischler, would be cool if you can send a PR for this. It'll benefit other users using dropwizard.

We keep this in mind for a future major release. However, I'd like to see something like a general configuration api, where different systems can plug in, rather than a dedicated YAML format.


Build failure: mysql80

Steps To Reproduce
Just add mysql80 to your System
Build log
467a468
> #include_next <stdint.h>
CMake Error at /build/mysql-8.0.32/cmake/do_abi_check.cmake:121 (MESSAGE):
  ABI check found difference between
  /build/mysql-8.0.32/include/mysql/services.h.pp and
  /build/mysql-8.0.32/build/abi_check.out

make[2]: *** [CMakeFiles/abi_check.dir/build.make:70: CMakeFiles/abi_check] Error 1
make[1]: *** [CMakeFiles/Makefile2:2990: CMakeFiles/abi_check.dir/all] Error 2

Additional context
The build also failed in Hydra
https://hydra.nixos.org/build/215738828
Notify maintainers
@orivej

I've briefly looked into this and it seems that mysql configure does something strange, it preprocesses its headers that include standard C headers with gcc -nostdinc (to do an ABI check). (Another strange thing is that some of the included headers are C++ only since they do #include <cstdint>, but the compiler used is gcc, not g++, and it fails to process these headers if I remove -nostdinc from the call.)
I am not sure that I will resolve this in a timely manner, but probably this can be worked around with gcc10StdenvCompat.

probably this can be worked around with gcc10StdenvCompat

Some dependencies of mysql80, protobuf and icu, use symbols of libstdc++ from gcc 12; mysql80 fails to build with gcc10StdenvCompat or gcc11Stdenv (unless the dependencies are also built with older gcc).

My bisect hasn't quite completed yet, but it's looking like #209870 is the culprit here.

Yep, fdd49f1bcd8 from that PR is the last good commit, then there's a series of commits that fail with undefined variables, then 5f57c2e0f97 is where the build gets far enough to encounter this error.
I guess I'll add this to the project they created for follow-ups to that PR.
I'm pretty out of my depth here in terms of ideas for a fix.  I found https://bugs.mysql.com/bug.php?id=61297 which mentions running make abi_update to fix a similar issue a couple years back, but I'm not sure if that makes sense in nixpkgs or not.

This should have been resolved in staging-next, see https://hydra.nixos.org/job/nixpkgs/staging-next/mysql80.x86_64-linux.

This should have been resolved in staging-next, see https://hydra.nixos.org/job/nixpkgs/staging-next/mysql80.x86_64-linux.

If it isn't, please ping me and I will investigate this.


Setup Favicon

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


Added template properties file which states the category for this template

Sorry, but I don't understand what this is for.

In the same folder with a template file you can have a properties file which specifies various properties of the template file, for example it can specify a custom image icon to be used.
We started the work to integrate your plugin by default in an Oxygen installation.
We have an automated test on our side which states that each template file should have an associated .properties file which should at least state its type. The type of the template may be used for various filters which may be applied on the File->New dialog. For example if I want to create a new DITA resource with a specific "New Topic" action I don't want to see the file templates for creating XSL-FO files.
I added this as a push request in order to have a minimum of modifications between your framework and what will get included in Oxygen.

Does XSL-FO.properties need to be included in the Zip file for the add-on framework?

Yes Tony, it would be great if you could change the build.xml when you have the time to also include *.properties files from the templates folder.


Mock FRAM code

Description
This is necessary for testing the telemetry memory and persistent state.

Blocked by #185 and #192


Fix BlackrockIO unable to load nsX without nev

This should fix issue #480, @samuelgarcia.
I implemented the missing checks for the availability of nev files and also added a correct error message for cases when no Blackrock files could be found at all.
This works for Blackrock file versions 2.2 and 2.3, but unfortunately it seems that version 2.1 does indeed require a nev file to be loaded because scaling to Volts can only be done with dig_factor which is included in the nev file. I also added an error message for this case.
Apart from that I added a test for this in test_blackrockio that makes sure correct errors are raised in these cases.

Hello @bjoern1001001! Thanks for submitting the PR.

In the file neo/rawio/blackrockrawio.py, following are the PEP8 issues :

Line 119:77: W291 trailing whitespace
Line 285:100: E501 line too long (102 > 99 characters)
Line 355:100: E501 line too long (103 > 99 characters)
Line 362:100: E501 line too long (102 > 99 characters)
Line 1540:100: E501 line too long (117 > 99 characters)

Coverage decreased (-0.02%) to 48.774% when pulling 714b6bb6930708c8d79a8705eccd08a9b4d30215 on bjoern1001001:brio_no_nev into 6b6c7ef2d148de5431cbd8f254430251c3d34dde on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 48.774% when pulling 714b6bb6930708c8d79a8705eccd08a9b4d30215 on bjoern1001001:brio_no_nev into 6b6c7ef2d148de5431cbd8f254430251c3d34dde on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 48.774% when pulling 714b6bb6930708c8d79a8705eccd08a9b4d30215 on bjoern1001001:brio_no_nev into 6b6c7ef2d148de5431cbd8f254430251c3d34dde on NeuralEnsemble:master.

Coverage decreased (-0.02%) to 48.774% when pulling 714b6bb6930708c8d79a8705eccd08a9b4d30215 on bjoern1001001:brio_no_nev into 6b6c7ef2d148de5431cbd8f254430251c3d34dde on NeuralEnsemble:master.

@bjoern1001001: thanks for the patch I will have a look.
For the 2.1, case maybe we could force to read without nev file and in that case we would have not units (units='') and a wrning for that. It could be usefull for instance in spike sorting on theses old files where the units is not mandatory.
What do you think ?

This sounds like a good idea. The 'old' BlackrockIO had a parameter called 'scaling' where you could basically choose this. So if you agree, I would try to implement it in a more general way for all Blackrock file versions.

For the behavior I propose:

scaling=None by default
for v>=2.2 take the internal scaling and assert scaling is None, 'not used ffor version>2.1
for v==2.1:

if scaling is None raise an error
if scaling=='' or scaling=='realscaling' load data with the

For the keyword instead of scalling maybe ext_units or units_scale or signal_units would be more expressive.

In this case, it would not be necessary to even introduce such a parameter, one could just issue a warning as you first suggested.
In certain cases like this there could be advantages (e.g. memory consumption) to being able to keep original scaling and not even convert to float but rather keep the data as int. For this, an explicit scaling keyword would be necessary. The important question now is, if we want to offer the option to acces all data in the original int data type as present in the file. This would require a change in rescale_signal_raw_to_float() and the introduction of a scaling keyword, which could be called something like 'amplitude_scaling' or similar, because 'units' might be misleading because this term appears in many different places with different meanings (e.g. neo.units).

I am back.
Thank for teh code.
Finaly, I am more happy with my first comments : "with 2.1 no nev then no scaling no units".
The actual code is : "with 2.1 no nev then raise error", no ?
I think reading nsx v2.1 than lost there nev v2.1 should be able to be readable.

I agree about version 2.1. This should be possible and thus will not be able to be scaled.
I will check my code again and report back when I'm sure it does this correctly.
For the scaling parameter and thus memory usage, I will create a new issue or PR in the future.

I updated my code so it can now load any nsX file correctly without nev. For version 2.1 it now only shows a warning that raw data will be given instead of a voltage.

OK for me. I merge it.


Enable LTI for modeling, text and file upload exercises

Until now, LTI and the use of exercises in online courses was limited to programming exercises.
This PR enables LTI for online courses for modeling, text and file upload exercises.
When tutors submit an assessment for text, modeling, file upload or programming exercises, the score is immediately reported to edX. This means Artemis ignores the assessment due date in this case, because otherwise we would need to implement a scheduler to report the results to edX, which is not really necessary in my opinion, as it is rather difficult and might be error prone in case of system restarts. We could still implement something like this in the future, but for now this is not needed!
Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Server: I followed the coding and design guidelines.
[x] Client: I followed the coding and design guidelines.

Steps for Testing
Only for SEECx tutors:

Create a programming, text, modeling and file upload exercise on Artemis TS1 (make sure the course is configured as online course). Test programming exercises with automatic and manual assessment
Reference the exercises on edX in an unreleased section
Navigate from edX to Artemis (so that Artemis has a proper LTI URL for the exercise and the user), start the exercise, submit something
Assess the text/modeling/file upload/programming exercise manually on Artemis after the due date
Check that the score (set in the assessment) is successfully reported to edX and is shown on the edX page

Test Coverage
no change

Thanks for testing 👍


createTag weirdness

tons of weirdness with createTag. check this pen: http://codepen.io/Spongman/pen/zwrMKw

type 'a' into the select input box, NOTE:

a tag is created in the results list
the placeholder is changed

type an addional 'b' into the select input box (making it 'ab'), NOTE:

the tag in the results list changed (good)
the placeholder still shows 'a' (bad)

click the 'x' in the select2, NOTE:

the list didn't close (bad)
the placeholder changed to reflect the typed value (bad)

click the 'x' again, NOTE:

it still doesn't close, the original placeholder is back, and the results list says "No results found"

is it even supposed to be altering the selection here before the user actually selects the result?

So, placeholders will only work properly when you have an empty <option> element.  See https://select2.org/placeholders#text-placeholders
As for the dropdown not closing, I'm not sure what the intended behavior is, but I don't think it is supposed to close automatically when the selections are cleared.


Mlpack tutorials on NLP related projects

There are only computer vision related examples in this repo. Improve the repo by adding  examples related to NLP

@kartikdutt18  please assign me this issue . I will work on it .

Hey @Saikirannaidu225, sure! Please feel to work on this. Is there any specific model that you are planning to add (Mentioning sample dataset and model might be useful for everyone that reads this thread). Thanks for picking this up!


Support for RGB header pins on motherboard

Hi
I have this program installed and get the error Exception: No devices found
My Prism is plugged into the RGB header pins on motherboard I'm guessing this program only works if the Prism is plugged into the USB pins? are you likely to support RGB pins in future or is that a lot more complicated?

Hi,
As far as I know with RGB header connected you can only control fan color.
This a limitation of the controller firmware.
It would be difficult for me to pursue support of RGB header due to
the fact that implementation would wildly vary form motherboard to another.
Every manufacturer has different incompatible type of software to manage RGB.
There are project's out there that try to follow this direction however:
https://gitlab.com/CalcProgrammer1/OpenRGB
Hope this helps.


improve mio perf

Improve mio perf
for buf in &info.to_write {
    for elem in buf {
        data.extend_from_slice(unsafe { elem.as_slice() });
    }
}

takes a lot of time! It is implemented really poorly. Also I think it is a tick behind atm.

old code. no longer using mio


Implement Single Region Account

SEP : single-region-accounts-aka-SiRAs. This is a post GA requirement and SEP is still under review.

Moved to 2165


Retain cycle

The view controller is being retained because of MGSwipe.
Does anyone have the same problem: after one swipe, your view controller never goes to deinit?
deinit {
print ("deinit \(self)")
}
Please, can anyone help me?
MGSwipeTableCellDelegate is declared as weak, which is good. But maybe something else?
Tks!

Hey,
I just came across this retain issue in my own project and here is how I solved it.
If you implement any MGSwipeButtons with a convenience block callback, make sure you add [unowned self] in the block parameters like so:
let undo = MGSwipeButton(title: "Undo", backgroundColor: UIColor.red, callback: { unowned self -> Bool in
//your response.
return true
})
Hopefully this helps if you are still having this issue.

Hey, I also ran into a retain cycle issue while implementing MGSwipeTableCellDelegate in my project. After testing, I traced the retain cycle to the MGSwipeButton class convenience block callback which was retaining the cell responding the block.
I fixed the issue by adding [unowned self] to the block` parameter like below:
let undo = MGSwipeButton(title: "Undo", backgroundColor: .red, callback: { [unowned self] (_cell) -> Bool in             //do something with _cell             return true         })
Not sure if this was faulty logic on my part or the block callback but it worked for me.


Enable version sort in edges table

Dependent on https://github.com/nuvla/api-server/issues/746

Replaced by another ticket


New version: SlackTechnologies.Slack version 4.34.115

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@Trenly I've manually checked these hash's and seems fine. Not sure where its tripping up.

@wingetbot run

Installer https://downloads.slack-edge.com/releases/windows/4.34.115/prod/x64/slack-standalone-<IP_ADDRESS>.msi
Scan request id: 'f1a0934f-2942-4cc1-add7-2769958e9fc2'

Specified hash doesn't match.
Actual hash:   31FB7E3A47E9519829086C9063F93AB7A297FE9F5AFE965AC3B3BA5630EE88AB
Expected hash: fc417c2936b0742d751732e629dcf4423a0a0b99e7bf585a60f5701f9cde1a0a


[doc] missing word

📝 Summary

🔍 Description of Changes

📋 Checklist

[ ] I have read the contributor guidelines.
[ ] For large changes, or changes that affect the public API: this change was discussed or approved through an issue, on Discord, or the community discussions (Please provide a link if applicable).
[ ] I have added tests for the changes made.
[ ] I have run the code and verified that it works as expected.

📜 Reviewers

@akshayka OR @mscolnick

Thank you! I think you accidentally opened this PR against your fork, instead of against our repo


recent change broke additional service monitors

by not breaking out of range scope to get other variables. fixed.
What this PR does / why we need it:
recent change broke additional service monitors by not breaking out of range scope to get at the new crdApiGroup variable. This fixes that.
Which issue this PR fixes
No existing issue to my knowledge
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

@gianrubio

/lgtm


Can we use SDN's reactive mode of operation in a typical network?

Mininet uses GitHub issues for bug reports and feature requests only.
These issues can be viewed at bugs.mininet.org
If you have a question that is not a bug report or a feature request,
please use the documentation at docs.mininet.org, the FAQ
at faq.mininet.org, and the mininet-discuss mailing list.
For bug reports, please fill in the following information in detail,
and also feel free to include additional information such as debug
output from mn -v debug, etc.
--- Cut Here ---
Expected/Desired Behavior:
Actual Behavior:
Detailed Steps to Reproduce the Behavior:
Additional Information:

If you have a question that is not a bug report or a feature request,
please use the documentation at docs.mininet.org, the FAQ
at faq.mininet.org, and the mininet-discuss mailing list.


Install binutils-multiarch so that clang cross-compilation works

OK, I actually looked at both docker files, and then choose the wrong one :/

No worries at all! Sorry it's so obtuse and sorry for the gap between replies (at work atm and trying to find time to field this in between)

This was merged into master as 5a45e0ac1068b7e0d0983834c17957c939095e73


Fixed linting errors

I am not an JS expert. Maybe request a review for similar things by another JS dev for next PR :)


Prevent duplicate Zendesk ticket creation

When receiving a 409 response (conflict) from the Zendesk API, the support app keeps trying to create a ticket until the request goes through.
This change rescues the 409 response and takes no action, ignoring the ticket creation because Zendesk has already received it.
This PR also desactivates the submit button in the view after it has been pressed, to prevent duplicate requests being generated in the frontend (the below would usually be displayed for less than a second).

Another change that was considered was to store a hash of the ticket requester/contents for a few minutes in an ephemeral cache (eg redis) and drop any duplicates - however we think the two changes above are enough to solve the problem (do jump in @benilovj if you disagree).
Trello ticket

I don't think that the duplicate submission protection on the government support request forms will help here. Almost all of the duplicates originate through the public support form, which go through the feedback app. I'm not sure we'd see any benefit from having the protection there, given the low occurrence of government support request duplicate tickets.
On the broader question of "is discarding the 409 response enough?", my previous analysis suggested that it may not be enough, but we cannot be sure until we make this change. I'd suggest that we come back in a month after releasing this change and see how many duplicates there are now, and decide whether further duplicate detection is necessary. ^ @boffbowsh

Now that I've had :coffee: I understanding what Jake means. This change probably belongs more in the feedback app than in here.

Ok, thanks Jake! I didn't realise the duplicates came from the public support form. I've now removed that commit from the PR, and put some info about it in Trello here in case it can help for changes to the feedback app later.

This looks good. One final thing; we discard the exception completely silently, and there's no way to track that it's happened. Is it worth having a stats counter to track these (something like this), in case Zendesk tickets start going missing and we don't know why?

Oki doki! Adressed here.

:+1:


Removed use of deprecated ProgressEvent.position property

According to the ProgressEvent API, the XMLHttpRequest ProgressEvent.position property is now deprecated, and using it shows a warning in the Chrome console.
Is there any reason (e.g. backwards compatibility) that these references shouldn't be removed?

@zakangelle The code
progressEvent.loaded || progressEvent.position || 0

means that it should use progressEvent.loaded if available and only use progressEvent.position if it doesn't find the former. I got the same errors and looked in the code. Removing this like you have done breaks backward compatibility. However it seems that there is a case early in the call when progressEvent.loaded is undefined and it would be nice if it didn't throw this warning in those cases. But you can't just remove progressEvent.position. You need to do a proper check to figure out which one you want to use.

Thank you for the important attention and valuable feedback!

@jakutis Thanks for the quick fix, it will save us from some console pollution :)