Issue in Xcode 8

Hello! Today I ran in an issue using XCTest-Gherkin with Xcode 8. I can successfully use it and run the tests, until at the end of the run, Xcode crashes and it says:

DVTAssertions: ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-11246/IDEFoundation/Testing/IDETestRunSession.m:399
Details:  Unexpected test identifier SomethingSomething/testRunNativeTests() (expected (null)).

So XCTest does not seem to like this testRunNativeTests method which dynamically creates the other tests. I have tried removing the subclassing of NativeTestCase and setting the path directly within testRunNativeTests but it gave the same crash. Any ideas what to do or how to fix this?
Update: I just checked out the latest source from github XCTest-Gherkin and you can reproduce the issue there yourself. Steps:

open the file XCTest-Gherkin.xcworkspace
hit Command + U
See Xcode 8 crash

However, if you only run the tests that have Gherkin specified in Swift syntax, then Xcode does not crash. So the issue seem purely to be with the NativeTestCase class

Hi - I'm working on this as we speak, but to be honest am not 100% sure why it's happening, and nothing I've tried so far has had any effect.
I've narrowed it down to running test cases from within another test case, but need to spend more time investigating.

I'm also looking into this but no luck so far.
Any progress on your side?

Nothing from me, but there's a PR that fixes it here: https://github.com/net-a-porter-mobile/XCTest-Gherkin/pull/45#pullrequestreview-416422 from @Rabursky - all it needs is the CI to pass and it looks good to go. And that's just a .travis configuration issue; the tests all pass locally :)

@smaljaar Hi - can you confirm that the latest release of this fixes your problem, and then I can mark this issue as closed. Thanks!

@nap-sam-dean yes the latest release fixes it!

Fantastic news :)


Support for customized pool fees

Many pools have specifically negotiated fees for larger delegators. Add support to provide key-specific fees to override the pool default. The override rate would be applied specifically to payouts for that address
Add another configuration file (perhaps .negotiatedFees) to provide public key and override rate in decimal:
B62qkBqSkXgkirtU3n8HJ9YgwHh3vUD6kGJ5ZRkQYGNPeL5xYL2tL1L|0.012573
Anticipate other fee structures / special deals in the future - extracting fee calculation to make it pluggable is a good idea. That would allow forks to do other things like first block is free, or first epoch free for new delegators, or ... etc.

Love the idea! Will be really useful for our TowerStake pool.
Being able to offer different fees for 1st epoch would be awesome.


Multiple Go API endpoints don't return "joined" fields on PUT/POST

This is a regression from the Perl API, where keys like parentCachegroupName are returned with the name of the cachegroup rather than null. This requires following up INSERT or UPDATE SQL statements with a SELECT that returns the proper fields. This is essentially what the Perl API did through the DBIx ORM for these endpoints, but currently these APIs don't follow up with a SELECT to return the same data as the Perl API and return a null value in the response:

POST, PUT /api/1.1/cachegroups

parentCachegroupName, secondaryParentCachegroupName, typeName

POST, PUT /api/1.1/asns

cachegroup

POST, PUT /api/1.3/deliveryservices

cdnName, profileName, profileDescription

POST, PUT /api/1.1/regions

divisionName

POST, PUT /api/1.1/phys_locations

region

POST, PUT /api/1.1/servers

cachegroup, cdnName, physLocation, profile, profileDesc, status, type

POST, PUT /api/1.1/tenants

parentName

Example PUT /cachegroups/{id} response from traffic_ops_golang:
{
    "alerts": [
        {
            "level": "success",
            "text": "cachegroup was updated."
        }
    ],
    "response": {
        "fallbackToClosest": null,
        "id": 531,
        "lastUpdated": "2018-07-02 17:07:59+00",
        "latitude": 39.739167,
        "longitude": -104.984722,
        "name": "rawl-cg",
        "parentCachegroupId": 3,
        "parentCachegroupName": null,
        "secondaryParentCachegroupId": null,
        "secondaryParentCachegroupName": null,
        "shortName": "rawl-cg",
        "typeId": 6,
        "typeName": null
    }
}

Example PUT /cachegroups/{id} response from Perl TO with the same request payload:
{
    "alerts": [
        {
            "level": "success",
            "text": "Cachegroup update was successful."
        }
    ],
    "response": {
        "fallbackToClosest": 1,
        "id": 532,
        "lastUpdated": "2018-07-02 21:42:40.062963+00",
        "latitude": 39.739167,
        "longitude": -104.984722,
        "name": "rawl-cg",
        "parentCachegroupId": 3,
        "parentCachegroupName": "mid-west",
        "secondaryParentCachegroupId": null,
        "secondaryParentCachegroupName": null,
        "shortName": "rawl-cg",
        "typeId": 6,
        "typeName": "EDGE_LOC"
    }
}

Notice how the Perl API returns all the fooName fields whereas the Go API returns null.

@DylanVolz is working on this

FYI The same issue exists for profileparameters
{
  "alerts": [
    {
      "text": "profileParameter was created.",
      "level": "success"
    }
  ],
  "response": {
    "lastUpdated": null,
    "profile": null,
    "profileId": 1,
    "parameter": null,
    "parameterId": 4
  }
}

The same issue exists for profileparameters

I believe this is a problem for all endpoints using the "CRUDer" framework and "Generic" funcs (and possibly more).
For the CRUDer/Generic endpoints, we should be able to fix it in all of them at once, by

changing the Generic funcs to expect queries to return the whole object
using sqlx.StructScan to read the result of the insert/update
changing each endpoint's queries to return the values in a RETURNING clause.

for objects with values in other tables, RETURNING can only return columns in the inserted table - this can be worked around by wrapping the INSERT/UPDATE in a WITH statement.

for objects with values in other tables, RETURNING can only return columns in the inserted table

In some cases you can also do a subquery.
Hm.. I'll try some stuff

Since this was a regression from TO API 1.x, and TO API 1.x no longer exists, I'm closing this out. Newer API versions that don't return "joined" fields on PUT/POST are now just how those versions work. However, I do think we should consider adhering to returning "joined" fields for PUT/POST requests as an API guideline.

fwiw, that is in the API guideline, it's just not one that's actually followed in practice


Submit cannot be triggered twice after upload manually

Element UI version
2.10.0
OS/Browsers version
chrome  79.0.3945.117
Vue version
2.5.17
Reproduction Link
https://jsfiddle.net/mmx38qxw/
Steps to reproduce
upload 手动上传之后无法二次触发submit
What is Expected?
希望可以直接再次提交
What is actually happening?
upload 手动上传之后, 接口返回失败，此时再次点击上传无法二次触发submit。除非手动移除文件再上传

同样的问题

同样的问题

still seeing this.

for those who run into this, this can be hacked by setting the following properties on the file:
  file.status = "ready"
  file.percentage = 0


Type fix for application statements/execution_file

This is a great package for building CLI tools!
But, I have received this error when building an application  (on Julia 1.6.1):
┌ Info: application options:
│   options.application =
│    ComoniconOptions.Application(;
│        filter_stdlibs = false,
│        precompile = ComoniconOptions.Precompile(;
│            execution_file = ["test/runtest.jl"],
│        ),
└    )
ERROR: LoadError: TypeError: in keyword argument precompile_statements_file, expected Union{String, Vector{String}}, got a value of type Vector{Union{Nothing, String}}
Stacktrace:
 [1] build_application(m::Module, options::ComoniconOptions.Comonicon)
   @ ComoniconBuilder ~/.julia/packages/ComoniconBuilder/I9tvS/src/build.jl:59
 [2] install(m::Module, options::ComoniconOptions.Comonicon)
   @ ComoniconBuilder ~/.julia/packages/ComoniconBuilder/I9tvS/src/install.jl:66
 [3] #install#1

I think the problem is that the following lines:
https://github.com/comonicon/ComoniconBuilder.jl/blob/22e532e4636d2ac520633cef03634a7b33dff3d9/src/build.jl#L56-L58
results an Array that can contain nothing. The nothing element should be filtered out instead. It works about replacing them with:
The change in this PR should make sure the type is Vector{String} instead of Vector{Union{Nothing, String}} in the same way it is for the system image function.
One more thing, if any of the files listed is missing the error would be raised inside the array comprehension.
Perhaps it is better to explicitly check for the existence of nothing and warn its implication (e.g. one of the files do not exist) to the user?

thanks! good catch, I think it should instead return a String[] if no file is specified instead of adding type assertions? we don't have any type inference problem here

I see, then it is probably better to do array comprehension directly with String[] so the type is always Vector{String}.

thanks! could you also put a test case for this?

just realize github has this annoying CI approve thing, great job! let's just wait for CI to pass!

seems there is an issue while building the sysimg and app against the latest nightly build?  @Roger-luo Maybe the build test should be limited to the latest release for now?

Yeah let's ignore the nightly for now

LGTM thanks

No problem!
Seems that the CI still shows the failed state - I was not able to get my head around GitHub action 😂 I will leave that to you 😏
Maybe worth making a bug fix release?


Shaping/Chaining DSL

Take inspiration from gatling
keywords
stack
launch
waitfor(timespan | event)
delete

eg.
flight = stackflight
  .stack('./vpc.cfn.yaml')
  .launch(count=2, strategy='parallel', capabilities='IAM_ROLE')
  .waitForAllStacksComplete()
  .delete()
flight.engage()

# this would delete stacks as soon as they completed.
flight = stackflight
  .stack('./vpc.cfn.yaml')
  .launch(count=2, strategy='parallel', capabilities='IAM_ROLE')
  .delete()
flight.engage()

A next level feature would be something like;
event = stackflight.event() # define some sort of event, e.g. EC2 attains running status

flight = stackflight
  .stack('./vpc.cfn.yaml')
  .launch(count=2, strategy='parallel', capabilities='IAM_ROLE')
  .waitForEvent(event)
  .delete()
flight.engage()


vpn-seed-server pods fail to start in a local garden kind cluster

/area dev-productivity
/area testing
/kind bug
What happened:
Tried to setup a local garden cluster following the instructions here.

Gardener components successfully started
Gardenlet successfully bootstrapped the seed
Shoot cluster creation failed reconciliation and was always stuck at 80%. On closer inspection 2 of the pods never came up.

machine-shoot--local--local-local
vpn-seed-server

What you expected to happen:
Shoot cluster should have been successfully reconciled and started.

Question: Is https://github.com/gardener/vpn2 built for ARM64?

How to reproduce it (as minimally and precisely as possible):
Just run the gardener local setup using the instructions at  and run this on the latest macbook with GOARCH = arm64.
Anything else we need to know?:
Controller registrations were properly setup
k get controllerregistration
NAME                RESOURCES                                                                                AGE
networking-calico   Network/calico                                                                                42m
provider-local      BackupBucket/local, BackupEntry/local, DNSProvider/local,

ControllerInstallations are fine as well
k get controllerinstallations
NAME                      REGISTRATION        SEED    VALID   INSTALLED   HEALTHY   AGE
networking-calico-xwsnk   networking-calico   local   True    True        True      42m
provider-local-x2k2t      provider-local      local   True    True        True      42m

Pod status in shoot namespace:
kubectl get po -n shoot--local--local
NAME                                            READY   STATUS             RESTARTS   AGE
etcd-events-0                                   2/2     Running            0          10h
etcd-main-0                                     2/2     Running            0          10h
gardener-resource-manager-6d8b4c8c5f-4jp8h      1/1     Running            0          10h
gardener-resource-manager-6d8b4c8c5f-cs68j      1/1     Running            0          10h
gardener-resource-manager-6d8b4c8c5f-rggch      1/1     Running            0          10h
grafana-operators-5b6f77f499-x5nhk              1/1     Running            0          10h
grafana-users-c445495fc-h59hj                   1/1     Running            0          10h
kube-apiserver-768c8f7779-5sx2z                 2/2     Running            0          10h
kube-controller-manager-7758c4b9fc-78442        1/1     Running            0          10h
kube-scheduler-7f7d5bdb8d-xvd59                 1/1     Running            0          10h
machine-controller-manager-6d7f6ff797-5wllt     2/2     Running            0          10h
machine-shoot--local--local-local-58d9b-5vklt   0/1     Running            0          16m
vpn-seed-server-7c9888fd69-8zlbk                1/2     CrashLoopBackOff   126        10h

Logs from vpn-seed-server-7c9888fd69-8zlbk => container vpn-seed-server
2022-04-21 03:30:36 WARNING: --topology net30 support for server configs with IPv4 pools will be removed in a future release. Please migrate to --topology subnet as soon as possible.
2022-04-21 03:30:36 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.
2022-04-21 03:30:36 WARNING: file '/srv/secrets/vpn-server/tls.key' is group or others accessible
2022-04-21 03:30:36 OpenVPN 2.5.2 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on May  4 2021
2022-04-21 03:30:36 library versions: OpenSSL 1.1.1k  25 Mar 2021, LZO 2.10
2022-04-21 03:30:36 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2022-04-21 03:30:36 TUN/TAP device tun0 opened
2022-04-21 03:30:36 /sbin/ip link set dev tun0 up mtu 1500
2022-04-21 03:30:36 /sbin/ip link set dev tun0 up
2022-04-21 03:30:36 /sbin/ip addr add dev tun0 local <IP_ADDRESS> peer <IP_ADDRESS>
iptables v1.8.6 (legacy): can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.8.6 (legacy): can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
2022-04-21 03:30:36 /firewall.sh on tun0 1500 1623 <IP_ADDRESS> <IP_ADDRESS> init
2022-04-21 03:30:36 WARNING: Failed running command (--up/--down): external program exited with error status: 3
2022-04-21 03:30:36 Exiting due to fatal error

Environment:
GOOS = darwin
GOARCH = arm64
MacOs version: Monterey 12.3.1

Gardener version:
Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.5", GitCommit:"c285e781331a3785a7f436042c65c5641ce8a9e9", GitTreeState:"clean", BuildDate:"2022-03-16T15:51:05Z", GoVersion:"go1.17.8", Compiler:"gc", Platform:"darwin/arm64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-06-22T04:50:02Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/arm64"}
WARNING: version difference between client (1.23) and server (1.21) exceeds the supported minor version skew of +/-1
Cloud provider or hardware configuration:
Others:

I resolved the issue w.r.t vpn-seed-server not coming up.
I changed the Dockerfile in https://github.com/gardener/vpn2 to the following seed-server/Dockerfile
FROM alpine:3.15.4

RUN apk add --update bash curl openvpn bc iptables && \
    rm -rf /var/cache/apk/*

ADD seed-server/network-connection.sh seed-server/openvpn.config.template seed-server/firewall.sh /

RUN mkdir /client-config-dir
ADD seed-server/vpn-shoot-client.template /client-config-dir

EXPOSE 1194

# We use "exec" and "trap 'exit' TERM" in the bash script, otherwise,
# the script won't recieve and react to SIGTERM
CMD exec /network-connection.sh

With the above change i was able to start the vpn-seed-server. I still have a pending issue w.r.t machine pod not starting up. Will try and gather additional journalctl logs

Thanks to @rfranzke after changing the version of kubernetes to 1.23.6 in example/provider-local/shoot.yaml and adding 1.23.6 version to the list of versions in example/provider-local/base/cloudprofile.yaml the machine pod finally comes up. It takes a total of 35m for the machine pod to come up + shoot reconciliation to finish.

For vpn changes submitted PR https://github.com/gardener/vpn2/pull/11
I am not sure if there is a PR required to also add 1.23.6 to the list of supported kubernetes versions in cloudprofile.yaml and also change the kubernetes version in shoot.yaml
if it is required then let me know and i will raise a separate PR.


Numpy 1.16 support for future read_hdf

Due to this issue (https://github.com/PyTables/PyTables/issues/717) it seems that, at least on my host machine, the latest version of numpy is needed to store and play with large datasets using hdf5. Naturally, I would love to use modin (ray) for these purposes and but realized that modin runs with numpy<=1.15.
I downloaded the source of Ray from github to test to see if numpy 1.15+ was supported and it seems that tests were failing for numpy 1.16.1. I was curious if modin planned to support higher versions of numpy in the near term as would be required to interplay with py tables.

Hi @adithyabsk, thanks for posting this!
We do plan to update this dependency in the near-term, but there are some minor changes needed internally to Modin. Ideally this will happen early-mid March. We have other robustness issues higher on the backlog, so for now I will add this to the Help Wanted queue until we are ready to start it in case anyone is interested in picking this up.

Hi @adithyabsk, sorry for the delay!
I'm looking into updating numpy to 1.16 and hopefully should have it merged into master by the end of the week. Once it gets merged, you can install from master using pip install git+https://github.com/modin-project/modin.


Allow RSA signature operations with RSA_NO_PADDING

When no md is set, the raw operations should be allowed.
Fixes #16056

This should probably have a test case...

Good point. I'll add one.

Test added. Please re-approve.

The bug also had this in it:
'The documentation inaccurately states that EVP_PKEY_verify replaces RSA_public_decrypt, but EVP_PKEY_verify_recover is actually needed instead.'

@slontis thanks for catching this. I've completely overlooked that part.

Doc fix pushed

This pull request is ready to merge

Merged. Thank you for the reviews.


Issue 91 : Added note to avoid issues related to keycloak

Added this note to kata, ensuring this problem can be averted.

I'm looking at another option here that avoids having to modify /etc/hosts. Its possible to configure the keycloak hostname to localhost or another configurable host when this is hosted somewhere.

I would love to not have to modify /etc/hosts, that was really hacky feeling.  It would be different if we had nice urls like keycloak.chorus.dev and solr.chorus.dev and smui.chorus.dev ;-)
I'm just waiting for the flood of "I don't have permission to edit my hosts file" tickets!

I was hoping to get some clue here : https://keycloak.discourse.group/t/keycloack-standalone-works-fine-on-terminal-but-on-ip-8080-i-get-this-site-can-t-be-reached/7100/12
but noticed you already had sslrequired = none , not sure what else could we do ? or tunnel the way its suggested on the thread above?


Ftp.raw question

Hello everyone,
I'm getting a lot of messages in my log following this:
Ftp.raw[pass](args): Use Ftp.raw('pass args') instead.
Ftp.raw[feat](args): Use Ftp.raw('feat args') instead.
Ftp.raw[syst](args): Use Ftp.raw('syst args') instead.
Ftp.raw[type](args): Use Ftp.raw('type args') instead.
Ftp.raw[user](args): Use Ftp.raw('user args') instead.
Ftp.raw[quit](args): Use Ftp.raw('quit args') instead.

I have no clue why they're showing up, but it's quite annoying. I'm not using debugMode so I'm not sure why this is happening. am I doing something wrong? I'm not using any raw functions except for quit, by using ftp.raw.quit();
Edit: This issue seems to only happen since the new 1.5.5 version. I went back to the version I started developing on, 1.5.3 and that one seems to work fine.

I'm seeing this, too, when I got the 1.5.5 version from a straight "npm install".  I backed up to<EMAIL_ADDRESS>and no longer see these warnings on every action.

See this commit, and then the PR to fix #209

This problem still exists since npm version of<EMAIL_ADDRESS>is different from the one in this repository.


Canadian numbers recognized as US if prefixed by country code

Canada and the US share a country code (+1). The library handles the distinction if a number is prefixed with a +1 or no country code at all, but fails if numbers are prefixed with a 1.
Steps to reproduce:

Navigate to http://jackocnr.com/intl-tel-input.html
Select Canada from the country dropdown.
Type "1647" into the text field.
The country dropdown will change to the United States.

In contrast, libphonenumber demos seem to yield the correct results. E.g.:

Navigate to http://libphonenumber.googlecode.com/svn/trunk/javascript/i18n/phonenumbers/demo-compiled.html
Enter the phone number "1647*******".
Enter the default country "US".
Click Submit.

The validation results show "Phone Number region: CA"

Hmm good spot. I wasn't aware that you would dial the 1 without the plus, but I have just confirmed that with my American colleague! I will fix this when I have time. I'm also open to pull requests if you're in a hurry!

Fixed in v5.0.3

Awesome - thanks!
On Fri, Jan 30, 2015 at 4:28 PM, jackocnr<EMAIL_ADDRESS>wrote:

Fixed in v5.0.3
—
Reply to this email directly or view it on GitHub
https://github.com/Bluefieldscom/intl-tel-input/issues/143#issuecomment-72273270
.


Crashing on collectionview layout change with core data

Using reloaddata and invalidatelayout but crashes when I delete data. Adding data does not crash but collectionview does not update. Is there something I’m missing?

Here is my error.
Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'UICollectionView received layout attributes for a cell with an index path that does not exist: <NSIndexPath: 0x60000289dda0> {length = 2, path = 0 - 4}'
*** First throw call stack:


azure/logging kit module should name and place logging subscription into hierarchy

This is implemented by now, see https://github.com/meshcloud/collie-hub/blob/main/kit/azure/logging/main.tf#L6


[IOS] Crash: SIGABRT_Flutter_fml::MessageLoopTaskQueues::GetInstance()

环境如下
translated using Google translate
The environment is as follows
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.8.0, on macOS 12.1 21C52 darwin-x64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] VS Code (version 1.27.2)
[✓] Connected device (3 available)

• No issues found!

$ flutter doctor -v
[✓] Flutter (Channel stable, 2.8.0, on macOS 12.1 21C52 darwin-x64, locale zh-Hans-CN)
    • Flutter version 2.8.0 at /Users/andy/fvm/versions/2.8.0
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision cf44000065 (9 weeks ago), 2021-12-08 14:06:50 -0800
    • Engine revision 40a99c5951
    • Dart version 2.15.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/andy/Library/Android/sdk
    • Platform android-31, build-tools 30.0.3
    • ANDROID_HOME = /Users/andy/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.27.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.21.1

[✓] Connected device (3 available)
    • iPhone 12 mini (mobile) • 00008104-0011152E04A1401E • ios            • iOS 14.2 18B92
    • macOS (desktop)                     • macos                     • darwin-x64     • macOS 12.1 21C52 darwin-x64
    • Chrome (web)                        • chrome                    • web-javascript • Google Chrome 78.0.3895.5 dev

• No issues found!

堆栈信息
translated using Google translate
stack info
Case 1
Thread 17 name:  dart:io EventHandler
Thread 17 Crashed:
0    libsystem_kernel.dylib          0x1b8e0e964 0x1b8e07000 + 31076
1    libsystem_c.dylib               0x18c6aaf50 0x18c68b000 + 130896
2    libc++abi.dylib                 0x19a181bc4 0x19a16e000 + 80836
3    libc++abi.dylib                 0x19a172fc0 0x19a16e000 + 20416
4    libobjc.A.dylib                 0x19a07fe44 0x19a064000 + 114244
5    libc++abi.dylib                 0x19a180f58 0x19a16e000 + 77656
6    libc++abi.dylib                 0x19a183c5c 0x19a16e000 + 89180
7    libc++abi.dylib                 0x19a183c08 0x19a16e000 + 89096
8    libc++.1.dylib                  0x19a1206bc 0x19a10a000 + 91836
9    libc++.1.dylib                  0x19a115cbc 0x19a10a000 + 48316
10   Flutter                          fml::MessageLoopTaskQueues::GetInstance()	(in Flutter)	(mutex:182)	12
11   Flutter                          __ZNSt3__110__function6__funcIZN7flutter11DartIsolate28SetMessageHandlingTaskRunnerEN3fml6RefPtrINS4_10TaskRunnerEEEE3	(in Flutter)	(dart_isolate.cc:121)	8
12   Flutter                          tonic::DartMessageHandler::MessageNotifyCallback(_Dart_Isolate*)	(in Flutter)	(functional:1831)	16
13   Flutter                          dart::PortMap::PostMessage(std::__1::unique_ptr<dart::Message, std::__1::default_delete<dart::Message> >, bool)	(in Flutter)	(port.cc:2620)	12
14   Flutter                          dart::PostCObjectHelper(long long, _Dart_CObject*)	(in Flutter)	(native_api_impl.cc:2620)	8
15   Flutter                          dart::bin::EventHandlerImplementation::EventHandlerEntry(unsigned long)	(in Flutter)	(native_api_impl.cc:0)	12
16   Flutter                          dart::bin::ThreadStart(void*)	(in Flutter)	(thread_macos.cc:89)	8
17   libsystem_pthread.dylib         0x1f22ae9a4 0x1f22ad000 + 6564

Case 2
Thread 18 name:  dart:io EventHandler
Thread 18 Crashed:
0    libsystem_kernel.dylib          0x1bc1579e8 0x1bc151000 + 27112
1    libsystem_c.dylib               0x18c5ce0b4 0x18c5af000 + 127156
2    libc++abi.dylib                 0x19952fe1c 0x19951d000 + 77340
3    libc++abi.dylib                 0x199521bd4 0x19951d000 + 19412
4    libobjc.A.dylib                 0x199440028 0x199426000 + 106536
5    libc++abi.dylib                 0x19952f2cc 0x19951d000 + 74444
6    libc++abi.dylib                 0x199531bd0 0x19951d000 + 84944
7    libc++abi.dylib                 0x199531b90 0x19951d000 + 84880
8    libc++.1.dylib                  0x1994d8e00 0x1994c4000 + 85504
9    libc++.1.dylib                  0x1994ceeb0 0x1994c4000 + 44720
10   Flutter                          fml::MessageLoopTaskQueues::GetInstance()	(in Flutter)	(mutex:182)	12
11   Flutter                          __ZNSt3__110__function6__funcIZN7flutter11DartIsolate28SetMessageHandlingTaskRunnerEN3fml6RefPtrINS4_10TaskRunnerEEEE3	(in Flutter)	(dart_isolate.cc:121)	8
12   Flutter                          tonic::DartMessageHandler::MessageNotifyCallback(_Dart_Isolate*)	(in Flutter)	(functional:1831)	16
13   Flutter                          dart::PortMap::PostMessage(std::__1::unique_ptr<dart::Message, std::__1::default_delete<dart::Message> >, bool)	(in Flutter)	(port.cc:2620)	12
14   Flutter                          dart::PostCObjectHelper(long long, _Dart_CObject*)	(in Flutter)	(native_api_impl.cc:2620)	8
15   Flutter                          dart::bin::EventHandlerImplementation::EventHandlerEntry(unsigned long)	(in Flutter)	(native_api_impl.cc:73)	12
16   Flutter                          dart::bin::ThreadStart(void*)	(in Flutter)	(thread_macos.cc:89)	8
17   libsystem_pthread.dylib         0x1dc5e43a4 0x1dc5de000 + 25508

and more ...
复现步骤

iOS 设备 && Flutter 2.8.0
目前仅在生产环境中 有收集到crash信息，但没有已知的复现步骤，且无法提供示例代码

影响范围
translated using Google translate
steps to reproduce

iOS devices && Flutter 2.8.0
Currently only crash information is collected in the production environment, but there are no known reproduction steps, and sample code cannot be provided

Sphere of influence

@flutter-symbolizer-bot https://github.com/flutter/flutter/issues/98022#issue-1127117326 force flutter#v2.8.0 ios release arm64

Labeling this issue for further investigation from the team.
could be related to https://github.com/flutter/flutter/issues/98016

感谢回复，几个完整的崩溃日志见附件：
Hi @maheshmnj , thanks to the reply, a few full crash logs see attachments:
case_1_stack.txt
case_2_stack.txt
case_3_stack.txt
case_4_stack.txt

This looks like an issue where the engine has not been fully torn down before the process has been terminated. That is, the process crashed while exiting. The solution is to shut down the engine cleanly before exiting the process. We've seen this in cases where the a native exit could be called for instance. In the attached backtraces, there are references to FrontBoardServices and UIApplication termination as well. The engine does try to shut down gracefully in case of UIApplication termination notifications but if an exit happens in native code, there is nothing the engine can do.
cc @zoeyfan


Add package javadoc

Since yarn javadocs is now published (https://maven.fabricmc.net/docs/yarn-21w05b+build.11/), it would be cool to have package info Javadocs.

Someone finally found the links! :smile:
Given how yarn works, I guess we might make actual package-info.java files for the docs.
In addition, it would be cool to think about generating an overview-summary.html as well from some html description. I've thought about using pandoc (we can install that on github actions) to convert readme to an html for javadoc tool to use.

The tooling and mapping formats don't support packages yet.

Yeah, package docs will only be included in the generated jd jar (like how mappingpoet inserts block tags for mappings in the fake source generated) and stored in yarn for now in a different format (I plan to use actual package-info.java files). The package docs will only be in the javadoc jars (and online views), but that should suffice for many purposes (at least for now)

Now we have constant source set and javadocs. Would not be too hard to introduce a new package doc source set, which would function similarly to constants sources, and possibly have package docs distributed in extra files like the unpick definitions or with the constants jar.


Unset leaves AWS_DEFAULT_REGION set

Ran into this while updating my zsh shell prompt.  Not necessarily a big deal, but its not doing what it says on the box.
assume Version: 0.19.0
From the help command:
   --unset, --un      Unset all environment variables configured by Assume (default: false)

My prompts with an awk showing environment variables:

a fresh terminal

➜  ~ env | awk -F'=' '/AWS/ {print $1}'
➜  ~

after running assume

➜  ~ env | awk -F'=' '/AWS/ {print $1}'                    aws:prod-0:us-west-2
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_SESSION_TOKEN
AWS_PROFILE
AWS_REGION
AWS_DEFAULT_REGION
AWS_SESSION_EXPIRATION
AWS_CREDENTIAL_EXPIRATION
➜  ~                                                       aws:prod-0:us-west-2

after running assume --unset

➜  ~ env | awk -F'=' '/AWS/ {print $1}'                               us-west-2
AWS_DEFAULT_REGION
➜  ~                                                                  us-west-2

Thank you for raising this @greg-swift-yohana. This should be fixed in the next release!


Add an option for strict route checking

Description
When you type a route that doesn't exist it doesn't throw any errors nor warnings in any environment. Not even in runtime when the route is accessed.
I use php artisan ziggy:generate --types-only each time the routes are updated in the backend (automatically, using a watcher).
My environment: Laravel 11, PHP 8.3, Breeze Inertia Vue template, added Typescript, declared ziggy's global route
Example:
A vue page component:
<Link :href="route('invalid.route')"> <!-- No error by Typescript, nor in browser, nor in runtime (console), even though the route auto-complete works  -->
Dashboard
</Link>

When the page with this invalid link is requested (not even the route itself), the user only sees a blank white page with zero errors, not even in the Browser console nor in the Networking tab. The PHP logs emit no errors as well. I think it's critical to at least inform consumers about this potential debugging nightmare.
Suggestion
I suggest providing an option that makes Typescript yell at you when the string in the route function isn't declared by the ziggy.d.ts file. It can be named strictRoutes of type boolean for example.
Alternatives
Enforce a mechanism that makes the server throw an error to the user and logging it. Or update the Breeze Inertia template to have this error handling built-in. Or at least write in the README how to set error handling up manually (be it typescript or PHP runtime)

Calling route('invalid.route') should definitely error and you should see it in the browser console. Is that exactly the code in your app? What page is it on in the Inertia template? Do you have anything like Sentry set up that might be swallowing errors? Are you having this issue in development mode or with a full Vite build, or both?
Making route() stricter about the route names passed into it is something I'm totally open to.

Calling route('invalid.route') should definitely error and you should see it in the browser console. Is that exactly the code in your app? What page is it on in the Inertia template? Do you have anything like Sentry set up that might be swallowing errors? Are you having this issue in development mode or with a full Vite build, or both?
Making route() stricter about the route names passed into it is something I'm totally open to.

Oof, I was either extremely inattentive or it for some reason didn't show up in the browser console at the time I checked. It does indeed show up in the browser console now that I check again. Sorry for misinforming on that part.
Question, is it possible to have it check all the route calls at build-time? Either way, I guess the simplest solution would be to provide an option to show the error in development time: optional Typescript error/warning.
If this solution is chosen, then the next natural question would be - where to put the option? In what configuration file? If I am not mistaken, the ziggy.js file is not made for that. I guess it'd be put as into some kind of an options param while calling app.use(ZiggyVue({strictRoutes: true})), making ZiggyVue callable, right?


Change existing symbol_namespace::iterate to return all data instead of invoking a callback

This API was never used anywhere and required some face-lifting after being half-way abandoned. It is now needed on one of our projects.

@sithhell could we go ahead with this, please?

In principle the code is ok. After thinking a while about it, I'm sceptical about scalability since all symbols are now collected into a single place. This sounds like quite some overhead for just iterating the registered names.

Well, if you need all symbols in one place you should collect them there, no?

When looking at the use case in phylanx, I think this might be solved more efficiently by calculating the symbolic names from the ast, and use those to resolve the gids. This has the additional advantage that the number of localities to broadcast to is reduced.

Could you elaborate? I don't think I understand what you're after.

In principle the code is ok. After thinking a while about it, I'm sceptical about scalability since all symbols are now collected into a single place. This sounds like quite some overhead for just iterating the registered names.

Well, if you need all symbols in one place you should collect them there, no?

Sure, what I am questioning though is if you really need all in one place.

When looking at the use case in phylanx, I think this might be solved more efficiently by calculating the symbolic names from the ast, and use those to resolve the gids. This has the additional advantage that the number of localities to broadcast to is reduced.

Could you elaborate? I don't think I understand what you're after.

The parser is creating the AST nodes with specific names which are then registered in the symbolic namespace. Giving that you have the AST, it should be trivial to extract the names of the different nodes by a simple tree traversal. Once you have a list of the names, you can calculate which service instance is responsible for the each name and send out bulk requests to only those instances of the symbolic namespace server to resolve the GID. That is, you shouldn't need the symbolic namespace service to get all names associated with the AST.

I'm still skeptical though if this is really a better approach than the callback based solution.

I'd be happy to add back the old callback-based solution as an alternate API. For my use case it would be much more expensive at runtime to use the old API, however.


Add new LLM models？

Which models are currently supported for deployment? Or how can other models be deployed through this project?

You may refer to https://github.com/mlc-ai/mlc-llm/blob/main/mlc_llm/utils.py#L74-L86 for supported model prefixes.


parser: add auto_random table option support

What problem does this PR solve?
supply a way to rebase auto_random from outside —— by auto_random table option
What is changed and how it works?
support auto_random table option support
Check List
Tests

Unit test
Integration test

Code changes

add auto_random to table option

Side effects

Breaking backward compatibility
(we will add it into the comment feature ID management)

Related changes

Need to update the documentation

Is it possible that there are more than one columns declared as auto random? @AilinKid

Is it possible that there are more than one column declared as auto random? @AilinKid

No, only one specially with primary key


Fix warning import in Iaso from typescript

Test for me and it works in Iaso, but it should be tested with the other project using bluesquare-components.
Also there are still some case where I doesn't work in Iaso, from what I gatherd is when we do the import {*} from ... in index.ts , probably we can remove theses cases?

Doesn't work with named imports. Also, it seems using unnamed imports would require to use a format like import lib from 'bluesquare-components then call eg lib.commonStyles.
or maybe I missed something. Anyway, I'd rather we keep using named imports

Ignore above review, config error on my part


Official ducumented support for ajax/XHR/fetch requests

I just got into vue 2.0 and loving it!
However, when I wanted to do a simple ajax request things kind of stopped...
I ducked "vue 2.0 ajax request" and got a lot of different results, non which were official.
The most used lib and obvious choise seems to be vue-resource, but there were reports about people not getting in to work etc..
Another "issue" with vue-resource is the "non ES6" promise API, no .catch!
Also it doesn't seem to support the new fetch API.
..I guess these are issues for vue-resource, but I mention them here because that project looks official.
So, my request would be that the official vue 2.0 docs include an example of how to best do an ajax call, so newcomers don't have to spend an hour searching for the best practice on how to do this. I would recon most apps out there use ajax-request, so I think this should be in the docs.
Thanks for a great alternative to react!

Hi, thanks for filling this issue.

so newcomers don't have to spend an hour searching for the best practice

Best practice: use whatever Ajax/http lib that suits your need, for example, fetch/axios etc or even jquery, and they will do just fine.
The Ajax/http layer should be framework-agnostic, and in fact react doesn't have official http lib either. It is unfortunate that some frameworks like angular/ember left people with the impression that http libs should be bundled with frameworks, and the truth is no, just use whatever you like.

And some quick sidenote:

Another "issue" with vue-resource is the "non ES6" promise API, no .catch!

[Really?](Another "issue" with vue-resource is the "non ES6" promise API, no .catch!)

Also it doesn't seem to support the new fetch API.

There's fetch for that.

..I guess these are issues for vue-resource, but I mention them here because that project looks official.

Yeah, vue-resource has some open issues atm, but like vuex, vue-router, vue-validator and other supporting libs we provide, you are free to use them, or use alternatives. There's no lock-in for you, and for many people ans situations, other libs may be better suited than the ones we maintain.

I found superagent, qwest, reqwest and a bunch of others, but yea, which is "best" etc..

A universal way of deciding which lib is better is by comparing their github stars/issues count and npm downlods. ;)

And if you aske 3 of our team members which they prefer, you would get three different replies minimum :D

@fractalf Use Fetch with fetchival 😉

best-superlative is subjective and always misused in my opinion. Using best makes comparisons feeling like competition.

"The Ajax/http layer should be framework-agnostic"
Why?
Ajax is an extremely important part of the web these days and you're basically saying "users should find their own way of making our framework work do Ajax".
The whole point of using a framework is so I don't have to figure things out for myself. If I know how to do Ajax, and DOM manipulations etc then why would I use a framework in the first place?

Ajax is an extremely important part of the web these days and you're basically saying "users should find their own way of making our framework work do Ajax".

Not really. What we are saying is:

Vue is a view-layer library, not a complete framework
Vue plays nicely with pretty much any AJAX solution out there (axious, superagent, vue-resource, $.ajax...) and integrting them with Vue works pracitcally the ame for all of them: import them into your app and use them as per their README.

We don't see the advantage in importing a Vue-specific AJAX solution - which for many people would be a new API to learn - if the only additional value it offers is that you don't have to install and import it.
In fact, we retired vue-resource for exactly this reason: it offered very littel benefit over using something more mature like $ajax, axios or superagent.
Also, it's about what people need:

People prefer different solutions, so we don'T want to force one solution on them
People might not need a general-purpose AJAX lib if they use a Framework or technology that has its own client-side libarary, for example Meteor, FeathersJS, ApolloJS ...

In those situations, it would be unnessessary bloat to have to include Vue's AJAX implementation into your final bundle, because your don't need it.

"Vue is a view-layer library, not a complete framework"
In that case it makes perfect sense. Thanks for the followup!


move travis patch to tests

Motivation
I just noticed we added this patch for travis so it won't die on timeout. I felt irritated that it was in our main command file node.go. since this is relevant to tests I moved it to work in app_test.go.

bors merge


Setup failed - Home Assistant Core 2024.9.0

ImportError: cannot import name 'DATA_TYPES' from 'zigpy.zcl.foundation' (/usr/local/lib/python3.12/site-packages/zigpy/zcl/foundation.py)

#1434

why raising a dubbed issue ?
https://github.com/AlexxIT/XiaomiGateway3/issues/1434

Sorry, my fault...

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v4.0.6


Add ListenAddress Option to restrict serving

Many applications allow you to restrict the listenaddress to a specific string, i.e. localhost, mydomain.com, <IP_ADDRESS>, etc. This lets you listen on only one interface, only respond to requests coming from a specific domain, etc. and it is very helpful. For example, it would be supremely useful for #306 , as it would let you run it securely on the host.
If this option is already available, then perhaps this issue is related to #218 , and the variable name just needs to be documented. However, I dug through the code looking for it, and looking at these lines here it seems monitoror does autodetection to listen on all interfaces.
Would you be willing to make that the default behavior, and allow users to override it in the .env to restrict the listening address?

+1

Hello!
It is not possible at the moment, but it seems interesting and very easy to set up.
I will add this soon ^^


hertzbeat keyword bug when using TDengine query.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
使用TDengine查询未处理关键字问题。

Expected Behavior
增加对关键字的处理。
Steps To Reproduce
No response
Environment
HertzBeat version(s):1.3

Debug logs

Anything else?
No response

已解决

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

solved


⚠ Bofrost.at has degraded performance

In 455eb8a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1332 ms

Resolved: Bofrost.at performance has improved in f34a5eb after 6 minutes.


Print notification when LXRHash file is being calculated

Right now the console is just blank for 10+ minutes with no output while the hash file is being generated. We can either turn LXRHash's verbose option on, or at least print out console output letting people know when it starts and when it ends

Agree, this is a bit obnoxious.

this has been implemented

Can probably be refined later


feature: add threshold to slide navigation

:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Issue#13 - Defaulting to latest version of push-jobs client

See https://github.com/chef-cookbooks/delivery-base/issues/13

@g0atcheez Thank you for your PR. Currently Workflow (Delivery) is not compatible with push-jobs 2.x

PJ client 2.x is compatible. PJ server 2.x is not.

Thanks for the clarification guys. I got with my Success Engineer and he was able to explain the situation to me. I'll go ahead and close the PR and issue for now and override the version I want to install.


Cannot find a way to get a reference to the Container object with React

Which version are you using?
1.18.11
Is the latest version affected?

[X] Yes
[ ] No

Which library are you using?

[ ] Vanilla JS (tsparticles)
[X] React (react-tsparticles)
[ ] Vue.js 2.x (particles.vue)
[ ] Vue.js 3.x (particles.vue3)
[ ] Angular (ng-particles)
[ ] Svelte (svelte-particles)
[ ] Preact (preact-particles)
[ ] Inferno (inferno-particles)
[ ] jQuery (jquery-particles)

I did not find in the documentation a way to get a reference to the Particles instance, in order to call its methods (play, refresh and so on). Can you give an example?

Hi @monteiz
Actually, there is a container property in the <Particles /> tag which is a React ref property.
You can see a sample here:
https://codesandbox.io/s/compassionate-mcnulty-ocu3r?file=/src/App.js
The useEffect retrieves the object after the loading and logs it in the console just to show that the object is the right one

That did the job, thank you so much.
I needed that because using SSR, the initial canvas size is [0,0].
I have to set the correct canvas size after the first render:
	useEffect(() => {
		if (containerRef && containerRef.current) {
			setTimeout(() => {
				containerRef.current.canvas.width = window.innerWidth;
				containerRef.current.canvas.height = window.innerHeight;
				containerRef.current.refresh();
			}, 1000);
		}
	}, []);


cf push app status info stack lists "unknown"

Command
When I push an app to CF I get this output at the bottom after the app starts.
requested state: started
instances: 1/1
usage: 256M x 1 instances
urls: sinatra-test-dan.cfapps.io
last uploaded: Wed Mar 16 14:54:50 UTC 2016
stack: unknown
buildpack: https://github.com/cloudfoundry/ruby-buildpack#v1.6.5

     state     since                    cpu    memory        disk          details
#0   running   2016-03-16 10:55:12 AM   0.1%   21M of 256M   68.3M of 1G

The stack always lists "unknown.  This only happens with cf push.  The output of cf app shows the stack just fine.
CLI Version

cf version 6.16.1+924508c-2016-02-26
cf v231
diego 0.1454.0
garden 0.333.0

I didn't test, but it's reported that this worked consistently on v6.14.
http://cf-dev.70369.x6.nabble.com/cf-dev-cf-push-stack-unknown-tp4206p4208.html
CF Trace
REQUEST: [2016-03-17T22:43:00-04:00]
GET /v2/apps/11ff47a3-8e32-4c74-a7b0-85b61b87e00b/summary HTTP/1.1
Host: api.run.pivotal.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.16.1+924508c / darwin

RESPONSE: [2016-03-17T22:43:00-04:00]
HTTP/1.1 200 OK
Content-Length: 2318
Connection: keep-alive
Content-Type: application/json;charset=utf-8
Date: Fri, 18 Mar 2016 02:43:00 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: e16da7d1-398d-4cd4-5723-a7bf80ccaa75
X-Vcap-Request-Id: 02faa379-502c-4dc2-5a00-0634efd491f8::d6c4fd4e-5db0-4428-a1e7-60f5dcdd8ac4

{"guid":"11ff47a3-8e32-4c74-a7b0-85b61b87e00b","name":"spring-music","routes":[{"guid":"f461c41a-2f57-439c-9b10-a142ec55cde1","host":"spring-music-dan","path":"","domain":{"guid":"fb6bd89f-2ed9-49d4-9ad1-97951a573135","name":"cfapps.io"}}],"running_instances":1,"services":[],"available_domains":[{"guid":"d576a360-a8f8-4aba-b15e-5b4787183784","name":"running-on-pws.com","owning_organization_guid":"639f74aa-5d97-4a47-a6b3-e9c2613729d8"},{"guid":"17d8c2dd-ee98-4ebd-b511-34c4b93d4ec0","name":"xxxxxx.com","owning_organization_guid":"639f74aa-5d97-4a47-a6b3-e9c2613729d8"},{"guid":"fb6bd89f-2ed9-49d4-9ad1-97951a573135","name":"cfapps.io","router_group_guid":null,"router_group_types":null}],"production":false,"space_guid":"10180e2b-33b9-44ee-9f8f-da96da17ac1a","stack_guid":"86205f38-84fc-4bc2-b2b8-af7f55669f04","buildpack":null,"detected_buildpack":"java-buildpack=v3.6-https://github.com/cloudfoundry/java-buildpack.git#5194155 open-jdk-like-jre=1.8.0_73 open-jdk-like-memory-calculator=2.0.1_RELEASE spring-auto-reconfiguration=1.10.0_RELEASE tomcat-access-logging-support=2.5.0_RELEASE tomcat-instan...","environment_json":{"JBP_CONFIG_OPEN_JDK_JRE":"[memory_calculator: {memory_sizes: {stack: 228k}}]"},"memory":512,"instances":1,"disk_quota":1024,"state":"STARTED","version":"d8057180-78ee-419c-85fb-a6876009267e","command":null,"console":false,"debug":null,"staging_task_id":"9734962bbd7e412d8f31e3d89e66d3db","package_state":"STAGED","health_check_type":"port","health_check_timeout":null,"staging_failed_reason":null,"staging_failed_description":null,"diego":true,"docker_image":null,"package_updated_at":"2016-03-18T02:42:15Z","detected_start_command":"CALCULATED_MEMORY=$($PWD/.java-buildpack/open_jdk_jre/bin/java-buildpack-memory-calculator-2.0.1_RELEASE -memorySizes=metaspace:64m..,stack:228k -memoryWeights=heap:75,metaspace:10,native:10,stack:5 -memoryInitials=heap:100%,metaspace:100% -totMemory=$MEMORY_LIMIT) &&  JAVA_HOME=$PWD/.java-buildpack/open_jdk_jre JAVA_OPTS=\"-Djava.io.tmpdir=$TMPDIR -XX:OnOutOfMemoryError=$PWD/.java-buildpack/open_jdk_jre/bin/killjava.sh $CALCULATED_MEMORY -Daccess.logging.enabled=false -Dhttp.port=$PORT\" exec $PWD/.java-buildpack/tomcat/bin/catalina.sh run","enable_ssh":true,"docker_credentials_json":{"redacted_message":"[PRIVATE DATA HIDDEN]"},"ports":[8080]}

REQUEST: [2016-03-17T22:43:00-04:00]
GET /v2/apps/11ff47a3-8e32-4c74-a7b0-85b61b87e00b/instances HTTP/1.1
Host: api.run.pivotal.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.16.1+924508c / darwin

RESPONSE: [2016-03-17T22:43:00-04:00]
HTTP/1.1 200 OK
Content-Length: 55
Connection: keep-alive
Content-Type: application/json;charset=utf-8
Date: Fri, 18 Mar 2016 02:43:00 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: edf7e334-1cf9-4265-7c96-84ab87bbd845
X-Vcap-Request-Id: 78f9f0a2-7096-42fe-5f9e-7fa308e7f102::db55594b-5126-4434-a3a6-de9cfe2b0dc1

{"0":{"state":"RUNNING","uptime":1,"since":1458268979}}

REQUEST: [2016-03-17T22:43:00-04:00]
GET /v2/apps/11ff47a3-8e32-4c74-a7b0-85b61b87e00b/stats HTTP/1.1
Host: api.run.pivotal.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.16.1+924508c / darwin

RESPONSE: [2016-03-17T22:43:00-04:00]
HTTP/1.1 200 OK
Content-Length: 273
Connection: keep-alive
Content-Type: application/json;charset=utf-8
Date: Fri, 18 Mar 2016 02:43:00 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 2c9a2591-8b83-485e-4967-73fbb181826f
X-Vcap-Request-Id: 2b97602f-4582-4b55-5b71-8dd20f3f3efe::514a4e89-477e-48b5-b98b-3ad6efbb66df

{"0":{"state":"RUNNING","stats":{"name":"spring-music","uris":["spring-music-dan.cfapps.io"],"host":"<IP_ADDRESS>","port":64283,"uptime":1,"mem_quota":536870912,"disk_quota":1073741824,"fds_quota":16384,"usage":{"time":"2016-03-18 02:43:00 UTC","cpu":0,"mem":0,"disk":0}}}}
OK

requested state: started
instances: 1/1
usage: 512M x 1 instances
urls: spring-music-dan.cfapps.io
last uploaded: Fri Mar 18 02:42:15 UTC 2016
stack: unknown
buildpack: java-buildpack=v3.6-https://github.com/cloudfoundry/java-buildpack.git#5194155 open-jdk-like-jre=1.8.0_73 open-jdk-like-memory-calculator=2.0.1_RELEASE spring-auto-reconfiguration=1.10.0_RELEASE tomcat-access-logging-support=2.5.0_RELEASE tomcat-instan...

     state     since                    cpu    memory      disk      details
#0   running   2016-03-17 10:42:59 PM   0.0%   0 of 512M   0 of 1G

Platform Details
Mac OS 10.11.3
Shell
iTerm

Thanks Dan, we'll investigate.

This has now been fixed in cf CLI 6.21.0. Thanks again for taking the time to report it.
https://github.com/cloudfoundry/cli#downloads


Allow overriding encrypted properties with unencrypted properties

Since the decrypted property source is taking precedence over all other property sources, it would not allow encrypted properties to be overridden by unencrypted properties. This commit removes the decrypted property from the overrides if it gets overridden by an unencrypted property.

I think this is OK but would like to know what @dsyer thinks.
Also if you would like this in Finchley, you will need to submit the PR against the 2.0.x branch.

I can't think of a reason not to do this, as long as the tests all pass.

@ryanjbaxter, Do I create a separate PR for Finchley or just change the base of this PR?

Alright, I've created PR #459 based on the 2.0.x branch.
Thanks!


[Bug] sdk.devices.get_settings fails if there is a single locked destination

Description
when running sdk.devices.get_settings(), I encountered a stacktrace thrown by ../py42/clients/settings/device_settings.py, line 357.
Steps to Reproduce

Create a device in Code42.
Assign the device a single, locked, destination
Attempt to retrieve the device's settings using py42

Expected Behavior
The settings data retrieves and parses correctly.
Actual Behavior
My device has this destinations object in its settings JSON:
              "destinations": {
                "@locked": "true",
                "destination": {
                  "@id": "632540230984925185",
                  "@locked": "true"
                }

py42 is attempting to process it like this:
for d in self.data[u"destinations"]:
            guid = d[u"@id"]
            dest_name = self._manager.available_destinations[guid]
            if u"@locked" in d:
                dest_name = dest_name + u" <LOCKED>"
            destination_dict[guid] = dest_name

This throws a stack trace because d[u"@id"] does not exist; since self.data[u"destinations"] is a dict and not a list.
Basic Information

py42 version: 1.10.0
python version: 3.7.4
operating system: Mac OS 10.15.7

So it looks like this happens because the device is on legal hold, as you can't actually lock "destinations" overall in the backup config (or org device defaults) settings. You can lock individual destinations, but here the lock is on all destinations.


[Bug] after running npm run build, on the index.html file under the build folder shows blank screen

Version
1.0.0
Reproduction link
https://github.com/gregmoncayo/React/tree/master/WebSite
Operating System
Mac OS
Device
Macbook air
Browser & Version
Google chrome 79.0
Steps to reproduce

In the json file, removed homepage: "https://www.creative-tim/etc" to homepage: ".",
Open terminal and npm run build
Open build folder and open index.html file
See blank screen and when inspect on google chrome console see two red errors:

DOMException: Failed to execute 'replaceState' on 'History': A history state object with URL 'file:///admin/index' cannot be created in a document with origin 'null' and URL
-Uncaught DOMException: Failed to execute 'replaceState' on 'History': A history state object with URL 'file:///admin/index' cannot be created in a document with origin 'null' and URL

What is expected?
Expected it to run normally as if I npm run serve
What is actually happening?
blank white screen with console log errors in google chrome

Solution
I believe something is wrong in my json file when trying to build it, I just don't know what.
Additional comments

Hello there, @gregmoncayo ,
Please delete the homepage prop altogether.
Also, the correct way to open the build folder is to run the serve -s build command.
Best,
Manu

Hello there, @gregmoncayo ,
Please delete the homepage prop altogether.
Also, the correct way to open the build folder is to run the serve -s build command.
Best,
Manu

this worked for me. Thanks!

Same issue... still not working for me.
I saw that there is one css that failed to downloaD from cdn

Hello there, @shachardevops ,
Please make a video with the following:

Download the product
Unzip the product
Open terminal and cd into the project
Run node -v
Run npm -v
Run npm install
Open package.json
Delete the homepage prop
Save changes (showcase this)
Run npm run build
Run serve -s build
Open browser
Navigate to http://localhost:5000
Showcase the errors that you get (the errors could be shown in the console of the browser, so be sure to use a browser that has a console)

Best,
Manu

thanks.
I removed the homepage prop from package.json and its working well.
my problem was i deleted the homepage prop from the bower.json

I am testing on how to deploy react applications and when I try to deploy it in AWS using Amplify, I received this error.

This my build. I have also just left it as:

npm i
npm run build
Have also used:
npm i
serve -s build

Is there a certain way you recommend deploying it?

Hello there, @gregmoncayo ,
Unfortunately, we do not have any experience with AWS, and don't know how to guide you.
To deploy any of our React products, since they are create-react-app based, it should be as simple as the following tutorials:

https://aws.amazon.com/getting-started/tutorials/deploy-react-app-cicd-amplify/
https://medium.com/dailyjs/a-guide-to-deploying-your-react-app-with-aws-s3-including-https-a-custom-domain-a-cdn-and-58245251f081

If you are still having errors, maybe the issue comes from the homepage prop, which is set to point to the live preview of this product, and maybe you need to provide a homepage prop for your own domain, or you have to delete the homepage prop altogether.
Read more about homepage prop and deployment on the official ReactJS docs:

https://create-react-app.dev/docs/deployment/
https://create-react-app.dev/docs/deployment/#aws-amplify
https://create-react-app.dev/docs/deployment/#step-1-add-homepage-to-packagejson

Let me know if that helped.
Best,
Manu


Add support for Geometry API

Geocoding could be an extension but most likely won't be a part of the actual add-on ever.


jira-export- not able to fetch the project name, even if it exist

Command: jira-export -u user.name -p XXXXX --url jiraURL --config config-scrum.json --force
Error:
Jira Exporter v3.0.364
Copyright (c) Solidify
[I][19:53:47] Connecting to Jira...
[I][19:53:47] Retrieving Jira fields...
[I][19:53:47] Retrieving Jira link types...
[E][19:53:48] Failed to get item count using query: 'project = project1 ORDER BY Rank ASC'
[System.AggregateException] System.AggregateException: One or more errors occurred. ---> System.InvalidOperationException: Response Status Code: 400. Response Content: {"errorMessages":["The value 'project1' does not exist for the field 'project'.","Not able to sort using field 'Rank'."],"warningMessages":[]}
at Atlassian.Jira.Remote.JiraRestClient.GetValidJsonFromResponse(IRestRequest request, IRestResponse response)
at Atlassian.Jira.Remote.JiraRestClient.d__11.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)    at System.Threading.Tasks.Task1.get_Result()
at JiraExport.JiraProvider.GetItemCount(String jql)

I tried with username = email address, password = API Token but it didnt work for me. Same JQL query is working in jira. Can you please help with this asap

Would it be possible for you to try the following as a workaround?

Try another project
Or steal the api token of another user with higher permissions and try again. The other user can revoke their token after the experiment.

I have tried multiple users, with multiple projects still getting the same error

Ok! Would it be possible to set up the same query in cUrl, Postman or a similar software?
Here is the query:
https://jira.xxx.com/rest/api/3/search?jql=project=PROJECTKEY

Authorization: Basic {base64EncodedCredentials}

Replace {base64EncodedCredentials} with a base64-encoded string in the format username:api_token

I am using command prompt, i tried with the above also, please help me with this command
jira-export -u<EMAIL_ADDRESS>-p api --url https://abhilashadxxxxxxxx.atlassian.net/--config Samples\config-scrum.json --force

I'm not sure then, other than all of the answers I have suggested, among which one or another have seemed to work for most people so far.
Would it be possible to get help from the Atlassian Support maybe?


Buxdpi

@khasansayliev lib/domains/uz/buxdpi.uz: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.


Try dbt-core#7368

Run CI with updated dependency pins

Tests are failing in a way that seems legitimately related to these changes. I don't have a chance to dig in right now, but it will take some digging.

@jtcohen6, do you still need this branch? Or can we delete it?

Deleted!


UI glitch: recipient address field is smaller then the address

The Issue
The "Recipient Address" field in the wallet is not long enough for certain addresses and it cuts off a small part of a beginning or end character. It could lead to confusion and wrong entry of the address.
Steps to reproduce

Just paste "bGSAgQZDvpLwQaVHuyVn1PUmR8HKwt9huB" in the recipient address field

Expected behaviour
The text field should show the entire address clearly.
Actual behaviour
It looks like the recipient address field is not long enough for certain addresses.
System Configuration

LBRY Daemon version: 0.18.0
LBRY App version: 0.19.4
LBRY Installation ID: 7tYN144rHXrspzJG9xLP28fi1JztXnbpKro6DBJEQyzBmXTyDgqRLfYsUvHYFVmMe2
Operating system: Win 10

Anything Else
I've tried to fix this by locally editing the app.asar file and increasing the field size from 60 to various sizes but with no success.
Screenshots

this is fixed in the redesign, @LavRadis please confirm/reopen.


Add Projects and links to docs

To make it easier to find tickets to work on, let's create projects for each major area of expertise
Here is an example board for Ruby on Rails issues
Here's what's needed to consider this ticket complete:

[ ] Identify the major areas of expertise (let's discuss this and signal agreement in comments below)
[ ] Create boards and add relevant issues
[ ] Add links to boards in the contributing guidlines

Areas of Expertise I can think of

Ruby on Rails
Cartography/Map tech
JavaScript
Docker
Linux - things like NGINX setting up computers for the field

@kalimar Do we still want to use the Projects or have we switched over to Trello fully? Is there a benefit in having both?

I would suggest we keep using Projects to group together related issues. I just updated the bug squashing Project to be able to link to all of the bug tickets in the Wiki Roadmap.
cc @FeminismIsAwesome


feature/issue 1587 increase max dropped gradients

Summary:
Sets the max number to be 5*grad_samples—the intuition being that we allow 5 dropped gradients per grad_sample, and so that it still scales with the size of the mini batch.
Intended Effect:
Allows dropped gradients by default; prior to this with grad_samples=1 (default) no dropped gradients are allowed.
How to Verify:
Run any model that ends up dropping a gradient with the default argument (grad_samples=1), c.f., unit test gradient_warn_test.cpp.
Side Effects:
None
Documentation:
None
Reviewer Suggestions:
None

this is a good catch and a straightforward change.


No length on password

Hey when I try to set the password while creating account I noticed that you haven't kept any password limit.
You need to decrease password length :There are two reasons for limiting the password size. For one, hashing a large amount of data can cause significant resource consumption on behalf of the server and would be an easy target for Denial Of Service attack.
Normally all sites have a password minimum to maximum length like 72 characters limit or 48 limit to prevent Denial Of Service attack. in my sql but in weblate registration page there are no limitation. Let me know if you need any more details.
This is typically not DoS, but a vulnerability which may lead to DoS attack.
Please assign me this issue under GSSoC'23!

This issue has been inactive for a long time
I would like to work on this issue
Please assign


[openstack_controller] Adding retry logic on expensive api calls

What does this PR do?
Adding a retry logic around paginated API calls flavors/detail and servers/detail
The latter being pretty expensive in general.
The retry logic will retry the paginated call 3 times before to start the backoff logic.
Every time a retry is performed, the limit param is being divided by 2.
Motivation
Make the integration more stable when some API calls fail.
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
[ ] If PR adds a configuration option, it has been added to the configuration file.

Additional Notes
Anything else we should know when reviewing?

Codecov Report

Merging #2755 into master will increase coverage by 3.13%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2755      +/-   ##
==========================================
+ Coverage   84.71%   87.85%   +3.13%
==========================================
  Files         657       15     -642
  Lines       37391     1746   -35645
  Branches     4488      140    -4348
==========================================
- Hits        31677     1534   -30143
+ Misses       4398      174    -4224
+ Partials     1316       38    -1278


Update dev dependency versions

It seems that Mucuchies does not build cleanly now, possibly due to a change in the grunt-ember-templates dependency. When I do a fresh clone of the project and try to npm install it, the following warning appears:
npm WARN EPEERINVALID<EMAIL_ADDRESS>requires a peer of ember-template-compiler@>=1 <2 but none was installed.

If I ignore the warning and try to build the dashboard anyway, grunt presents me with the following error:
Loading "ember_templates.js" tasks...ERROR
>> Error: Cannot find module 'ember-template-compiler'
Warning: Task "emberTemplates" not found. Use --force to continue.

Aborted due to warnings.

This PR updates all the dev dependencies, with which the project build stops yielding warnings. I updated the Handlebars client-side dependency in order to match the one used by grunt, but that was not strictly necessary as the Handlebars version set in this PR is compatible with the old one.

LGTM!


[Feature Request]: CC:Tweaked compatibility

Is your feature request related to a problem?
It would be great if it is possible to read (energy-)values of blocks created with this mod.
Solution(s)
Make things appear as computercraft peripherals.
Describe alternatives you've considered
No response
Mod Version
the newest version
Mod Loader Version
1.20.1-?
Mod Loader
Fabric
Additional context
I dont know if this needs to be done on this mod (I know this is a libary mod) or on mods that use this mod.

Im a little confused, does CC tweaked have something in it that allows it to read energy levels on a block? Botarium's purpose is to create a multiplatform energy container that can then be registered to the respective mod loaders for mod compatibility. It should automatically be compatible with CC: Tweaked if they read the energy capability on a block.

I have to test it. It should have some comptatibility with energy containers, but I think it needs to be activated somehow.

I see. I took a look at their repository, CC: Tweaked is a multiplatform mod. If they have a system for registering it, it should already be available to mods trying to be multiplatform and mod authors who want this can import CC: Tweaked directly without issue. If theres anything Botarium is doing that specifically makes it incompatible with CC: Tweaked let me know, but otherwise I don't really see what Botarium needs to do here to make it more compatible

Ok. Thank you.


Pre-push stages

Do
The pull request add two new properties to the app.manifest.

tests:

Representation:
 {
  /* ... your stuff */
  "tests": [
    {
       "name": "unit-tests",
       "cmd": "npm run tests"
    }
  ]
  /* ... your other stuff */
 }

The property "tests" is an array of Stage. Each Stage must be independent. The stage are ran in parallel before "zappification" of the widget.
If one fail it kills the command executed (push, watch ...)
TO-THINK maybe a --no-verify flag ?

build:

Representation:
 {
  /* ... your stuff */
  "build": [
    {
       "name": "unit-tests",
       "cmd": "npm run tests"
    }
  ]
  /* ... your other stuff */
 }

Such as the tests, the build is an array of independent stages. They are ran at the same time.
TO-THINK How to manage the generated bundle? Maybe defining an entry point

The build seems to fail because I am using a fork of the repository.

I close this PR and open another one from the origin instead of my fork


Issue closed without discussion in violation of code of conduct

Bug Description
I tried to open an issue about a high-level problem with this project's architecture, and it was closed in an apparent violation of the standards this project strives for in its own code of conduct.
Reproduction Steps

Try to ask a hard question in a computer science crowd
Notice that it's swept under the rug early monday morning by an engineer who doesn't appear qualified to address ethical or organizational issues

Platform and Hardware

Github issues
Community of humans
Institutional hubris

Additional Context
https://github.com/facebookresearch/flashlight/issues/375

Hi @scanlime. We certainly support your right to any particular viewpoints. On GitHub, however, the Flashlight project should be utilized for project-specific feedback, improvement suggestions and/or problems you are having with the project itself -- we really appreciate the feedback and discussions from the community and respond to anything actionable. We will continue to close out issues that are not project-specific and feel doing so does not violate our own code of conduct.


Make ‘renderMustache’ throw exceptions on missing values

Addresses #16.

Coverage decreased (-1.4%) to 83.254% when pulling 952e4a90c1f49b719d2fa5b0c2a7912a1a11bb40 on make-missing-values-throw-exceptions into 3dbdc0e2232575aa1caf83161291141f15f41ce2 on master.


RTL Support

Thanks for the source code
How we can help support this to make it RTL and readable for Arabic in Multi language?

we will have to try that http://blog.ionicframework.com/ionic-and-rtl/
I am adding this to the list for v3


Call timer

First of all: thank you very-very-very much for your work.
I need to start timer, when call is answered. Trying to listen events:
From console:
callStateRinging data {call_sid: "CA79da86a73d9d7ae501f729066ce4b"}
connectionDidConnect data {call_state: "CONNECTED", call_sid: "CA79da86a73d9d7ae501f729066ce4b"}
"callStateRinging" event returns only call_sid.
connectionDidConnect returns "connected" always. Docs says that we can get "call_state: 'CONNECTED' | 'ACCEPTED' | 'CONNECTING' | 'RINGING' | 'DISCONNECTED' | 'CANCELLED'".
So, how can i get it ('accepted' call_state)? Thanks)

If my memory serves me well I asked this very same question to Twilio a couple of years ago. Try search here: https://github.com/twilio/voice-quickstart-android/issues?q=
Maybe, it will be possible with SDK v5. If you find the way please let me know and I can think about the implementation.

If my memory serves me well I asked this very same question to Twilio a couple of years ago. Try search here: https://github.com/twilio/voice-quickstart-android/issues?q=
Maybe, it will be possible with SDK v5. If you find the way please let me know and I can think about the implementation.

Hi @Serge-purr To add to @fabriziomoscon's answer, in essence this means that the current lib does not support this behavior. Workarounds would be connecting to Twilio to get the call state when you receive an event. Not ideal, but until the new SDKs are integrated with this lib you will only be able to get connected

@SergeM55 Did you resolved this issue?


Fix Passive TTL on files does not take effect #13411

Fix Passive TTL on files does not take effect #13411.
When client exec stat/list/read operations first time, make sure alluxio.user.file.create.ttl and alluxio.user.file.create.ttl.action options from client take effect.

alluxio-bot, check this please

@LuQQiu @ggezer please, review

Codecov Report

Merging #13412 (1effc09) into master (92653af) will decrease coverage by 26.43%.
The diff coverage is 0.00%.

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


Nuxt.js

Any idea how to use this on nuxt? I cannot find a working guide. Thank you!

You need to define it as a plugin. Please check the following link. https://nuxtjs.org/guide/plugins/

I tried using it as a plugin.
This is what I did:

Yarn add vue-underscore

nuxt.config.js:
plugins: [
{ src: '~/plugins/underscore', ssr: false },
]

create a new file /plugins/underscore.js
import Vue from 'vue'
import { _ } from 'vue-underscore'
Vue.use(_)

in my pages/index.js
import { _ } from 'vue-underscore'
let testArr = [{ id: 1}, { id: 2 }]
let foundInfo = .findWhere(testArr, { id: 1 })
let foundInfo = this.$.findWhere(testArr, { id: 1 })
export default {
data: {
return {
foundInfo
}
}
}

Call {{ foundData }} (or console.log(foundData))

Didn't work both using _ and this.$_
Cannot use import statement outside a module

For the 3rd step do it like below code
`
import Vue from 'vue';
import underscore from 'vue-underscore';
Vue.use(underscore);
`

@anantonton Also I changed readme file to solve misunderstanding.


Segfault on committing group with "empty" isosurface geometry

In the (reduced) test case below I'm setting up an isosurface geometry with the intent of later on linking up the actual volume and setting isosurface values to use. The commit on group triggers a segfault, in what looks to be the geometry generation of the isosurface at the Embree level. This is with the devel branch, btw
When I add a ospCommit(geometry) directly after the ospNewGeometry no segfault occurs at that point, it sill happens at the commit of group. So I assume it is allowed to commit an "underspecified" isosurface geometry and not have it do anything until enough parameters are set and then commit once that point is reached.
$ cat t_empty_geometry_segfault.c
#include "ospray/ospray.h"

int
main(int argc, const char **argv)
{
    OSPError init_error = ospInit(&argc, argv);
    if (init_error != OSP_NO_ERROR)
        return init_error;

    OSPGeometry geometry = ospNewGeometry("isosurfaces");
    OSPGeometricModel gmodel = ospNewGeometricModel(geometry);
    OSPData data = ospNewData(1, OSP_OBJECT, &gmodel, 0);
    OSPGroup group = ospNewGroup();
    ospSetObject(group, "geometry", data);
    ospCommit(group);
}

$ gcc -g -o t_empty_geometry_segfault -I $HOME/software/ospray-superbuild-git/ospray/include/ t_empty_geometry_segfault.c -L $HOME/software/ospray-superbuild-git/ospray/lib64/ -lospray

$ gdb ./t_empty_geometry_segfault
GNU gdb (GDB) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./t_empty_geometry_segfault...
(gdb) run
Starting program: /home/melis/concepts/blender-ospray-engine/tests/t_empty_geometry_segfault
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7058176 in ospray::Isosurfaces::createEmbreeGeometry() () from /home/melis/software/ospray-superbuild-git/ospray/lib64/libospray_module_ispc.so
(gdb) bt
#0  0x00007ffff7058176 in ospray::Isosurfaces::createEmbreeGeometry() () from /home/melis/software/ospray-superbuild-git/ospray/lib64/libospray_module_ispc.so
#1  0x00007ffff70348fc in ospray::Group::commit() () from /home/melis/software/ospray-superbuild-git/ospray/lib64/libospray_module_ispc.so
#2  0x00007ffff7faa00f in ospCommit () from /home/melis/software/ospray-superbuild-git/ospray/lib64/libospray.so.1
#3  0x0000555555555258 in main (argc=1, argv=0x7fffffffe348) at t_empty_geometry_segfault.c:15

This really should be a error that Isosurfaces::commit() doesn't throw. I'll get this fix into release-2.0.x ASAP...thanks!

This now throws an error on commit of the isosurface geometry in c93f87e7.


Optional treating of multiple comments as an array rather than concatenating

Current Behaviour
Currently, multiple comments on the same move get concatenated together. This has the unfortunate effect of losing some data integrity.
Annoyingly, like most things PGN related, there is no standard way to handle this. The specification doesn't mention multiple comments, and both Chess.com and LiChess do things differently.
Take the following PGN:
1. e4 e5 {Comment One} {Comment Two} 2. Nf3 *
And then compare this imported into LiChess and Chess.com respectively:

When you then export the PGN again, LiChess keeps the comments separate, but exporting from Chess.com merge them
1. e4 e5 {Comment One Comment Two} 2. Nf3 *
The Chess.com behaviour is the same as the current pgn-parser behaviour:

Proposed Behaviour
Introduce another config setting value:
type PgnOptions = {
    startRule: StartRule;
    comments?: 'merged' | 'separate'
    fen?: string;
};

If it's not provided, it will default to the existing "merged" behaviour. This makes the feature "opt in" and prevents the change from breaking existing projects.
The current comment types would change from
type PgnMove = {
    ...
    commentDiag: GameComment;
    commentMove?: string;
    commentAfter?: string;
}

to
type PgnMove = {
    ...
    commentDiag: GameComment ? GameComment[];
    commentMove?: string ? string[];
    commentAfter?: string ? string [];
}

I am happy to create a PR and implement this functionality myself, however I wanted to raise it as a discussion first before getting started on it.

Thank you a lot for raising that issue. I have seen that in the past as well, and decided (at that time) to follow the spec, which means, merge comments then. But I have seen usages in Lichess (mostly) that worked quite well:

Having a study for multiple people, and not merging comments allows different comments (by different people) in the same context.
At the end, it should read like many paragraphs. So by using different comments then, you are able to view them as paragraphs of text (not one string without any format).

The GameComment in that context is different (in my opinion), and not so easy to multiply. It contains besides the comment (text) itself comment elements like circles, arrows, timing information, ... The trick here was to have one place to store things before any move is done. But this can be defined somehow ....
If you have the time to create a PR, that would be nice, I have too many open points in other chess related projects (where I am more interested in, to be fair).


fix init bugs

Overview
closes #19
Notes

added a function to remove added pre-script from Git pre-commit script

Codecov Report

Merging #20 (03f1285) into main (410fb81) will decrease coverage by 4.34%.
The diff coverage is 62.74%.

@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
- Coverage   77.67%   73.33%   -4.35%
==========================================
  Files           3        3
  Lines         112      150      +38
==========================================
+ Hits           87      110      +23
- Misses         15       24       +9
- Partials       10       16       +6

Impacted Files
Coverage Δ

cli.go
70.12% <62.74%> (-9.36%)
:arrow_down:

Continue to review full report at Codecov.

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

This PR decreases whole coverages +1.26%.
Thus, this error message from codecov/patch can be ignored.
ref: https://github.com/task4233/dl/pull/20#issuecomment-1072955554


Support for Unity 2017.3

There are a lot of warnings right now:
warning CS0618: `UnityEditor.BuildTarget.StandaloneOSXIntel' is obsolete: `StandaloneOSXIntel has been removed in 2017.3'
warning CS0618: `UnityEditor.BuildTarget.StandaloneOSXIntel64' is obsolete: `StandaloneOSXIntel64 has been removed in 2017.3'

etc.

I haven't had an opportunity to download and take a look at 2017.3, but I'll address these as soon as I can.

Closed by f2472758acba5d59b4ac81088b4cca529670b8b4


Various Potential Bugs in Container Pool and Container Proxy

I've found what I believe are some potential cases and would like some confirmation that I'm in the right direction with these bugs before I start trying to remediate them. Would like to hear people's opinions on if any of these seem like they might actually be the case. These are just a few things I found after looking at these two files for a couple hours. If a lot of them are, we may want to audit the Container Pool and Container Proxy for edge cases as the logic in these FSM's and FSM management have gotten quite complex. This investigation was brought forth by the bug I opened earlier today about the healthcheck protocol and building healthcheck lag in the invoker topics.

On the failure of a cold start in the Container Proxy, we attempt to go to state Removing. I believe this results in the FSM from never being stopped as once in state Removing no new messages will be sent to it. The message that ultimately is sent to stop the FSM is sent from within the destroyContainer function and that will never be called in this case if concurrency is not used and there's only one activation in the proxy. This is the line that was added recently to move to that state on this failure:

https://github.com/apache/openwhisk/commit/4956362f8f9feb217d3c96feb644cdb2ffb7ee6c#diff-4b149cfaa5f4b88c5fe7d5fd798d4ff12ab655c7d4e4fccb47072b7763800a05R502

When the container pool is completely busy, it now relies on an event to hit that calls processBufferOrFeed to attempt to execute a new Run message. I'm afraid that this is error prone to dead locks even though not re-calling Run with the head of the buffer at the end of trying to schedule that message in the ContainerPool frees up CPU cycles. I haven't been able to pinpoint anything yet that would lead to a deadlock, but we are seeing behavior in our invokers where it appears that a deadlock is happening on loaded invokers rarely.

https://github.com/apache/openwhisk/commit/a7482ca22694eee9b578c1003cd2c847953273e8#diff-907fea4f2800af33d571845b19ddc9a24a44d481994305f344c23d33310d471aL205

We are seeing lots of error logs of  unhandled event Remove in state Removing. This happens when the Container Pool sends a Remove message to the ContainerProxy when it's already in the Removing state in the fsm. My belief is that this is happening when the invoker is loaded and when some containers are failing it moves to removing early; and the container pool subsequently tries to remove the container to force a container recreation for a new action. This is probably fairly innocuous, but should be handled.

The Removing state used to stop the fsm if it received any failure message while in the state. The destroyContainer function forwards the ContainerRemoved message when all futured operations related to destroying the container completes which Removing receives and stops the fsm. On the unhappy case if something fails in destroyContainer, removing will no longer stop the fsm.

https://github.com/apache/openwhisk/commit/d4f9e8abf6739bd6ee48d64f567f93a90ef91daf#diff-4b149cfaa5f4b88c5fe7d5fd798d4ff12ab655c7d4e4fccb47072b7763800a05L541

This seems over eager to be calling processBufferOrFeed. Previously it would just try to dequeue the next item in the buffer, but by calling processBufferOrFeed you may be pulling from the message feed too soon since the buffer could now be empty:

https://github.com/apache/openwhisk/commit/a7482ca22694eee9b578c1003cd2c847953273e8#diff-907fea4f2800af33d571845b19ddc9a24a44d481994305f344c23d33310d471aR183

IMHO,

It looks like a bug to me.
I think it is supposed to see if activeCount is 0 and terminate the container if it is 0 like this.
https://github.com/apache/openwhisk/blob/master/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala#L485

processBufferOrFeed.

Since I haven't visited the code as we no longer use them I looked into it.
But not quite sure what is wrong for now.

Yes that log clearly denotes we need to add more cases in the Removing state.

That looks reasonable to me.
In case of any failures, it should be piped to the Removing state and handled there.

In the following codes,
    val unpause = stateName match {
      case Paused => container.resume()(TransactionId.invokerNanny)
      case _      => Future.successful(())
    }

    unpause
      .flatMap(_ => container.destroy()(TransactionId.invokerNanny))
      .flatMap(_ => abortProcess)
      .map(_ => ContainerRemoved(replacePrewarm))
      .pipeTo(self)

container.destory() is suspicious as container.resume() always return Future.successful({}).

Eagerly pulling a message.
Are you concerning about the message loss by pulling it too eagerly and keep it in memory?
Or are there any other downsides from eagerly pulling it?

I believe @tysonnorris has better understanding on those codes.

IMHO,

It looks like a bug to me.
I think it is supposed to see if activeCount is 0 and terminate the container if it is 0 like this.
https://github.com/apache/openwhisk/blob/master/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala#L485

processBufferOrFeed.

Since I haven't visited the code as we no longer use them I looked into it.
But not quite sure what is wrong for now.

Yes that log clearly denotes we need to add more cases in the Removing state.

That looks reasonable to me.
In case of any failures, it should be piped to the Removing state and handled there.

In the following codes,
    val unpause = stateName match {
      case Paused => container.resume()(TransactionId.invokerNanny)
      case _      => Future.successful(())
    }

    unpause
      .flatMap(_ => container.destroy()(TransactionId.invokerNanny))
      .flatMap(_ => abortProcess)
      .map(_ => ContainerRemoved(replacePrewarm))
      .pipeTo(self)

container.destory() is suspicious as container.resume() always return Future.successful({}).

Eagerly pulling a message.
Are you concerning about the message loss by pulling it too eagerly and keep it in memory?
Or are there any other downsides from eagerly pulling it?

I believe @tysonnorris has better understanding on those codes.

I agree that was my conclusion on what was meant to be included there.
Are you saying we should add back the processBufferOrFeed there? If so I think I agree.
The issue in my opinion is that the cases that are handled by the Removing state have changed so it's not a catch all for all future failures in the commit I linked for this one. If that container.destroy() fails, it will pipe the failure to Removing but only a failure when the container is WarmedData is caught.

I'm also a little concerned that we give up so easily on attempting to destroy the container. If that container.destroy() call fails, we cease tracking of the container immediately. I'm not sure if there's a more graceful or more guaranteed way of handling this other than coding in retries.

I agree this isn't a major concern. My only concern was it pulling extra things into memory too early, but not too big of a deal.

Thanks for taking the time to sanity check all of these for me. At the very least we should fix 1. asap. If I find any other logic that I question in the container management logic I'll be sure to add again to get some other opinions.
You're no longer using the container proxy / pool, is that because of the new scheduler? Will that be a part of the scheduler change?

I agree that was my conclusion on what was meant to be included there.
Are you saying we should add back the processBufferOrFeed there? If so I think I agree.
The issue in my opinion is that the cases that are handled by the Removing state have changed so it's not a catch all for all future failures in the commit I linked for this one. If that container.destroy() fails, it will pipe the failure to Removing but only a failure when the container is WarmedData is caught.

I'm also a little concerned that we give up so easily on attempting to destroy the container. If that container.destroy() call fails, we cease tracking of the container immediately. I'm not sure if there's a more graceful or more guaranteed way of handling this other than coding in retries.

I agree this isn't a major concern. My only concern was it pulling extra things into memory too early, but not too big of a deal.

Thanks for taking the time to sanity check all of these for me. At the very least we should fix 1. asap. If I find any other logic that I question in the container management logic I'll be sure to add again to get some other opinions.
You're no longer using the container proxy / pool, is that because of the new scheduler? Will that be a part of the scheduler change?

Yes, we are using another version of container pool / proxy which are aligned with the scheduler and are part of the scheduler contribution.

Yes, we are using another version of container pool / proxy which are aligned with the scheduler and are part of the scheduler contribution.


Updating validation when creating or editing a provider's endpoint.

Description
A regression was created when introducing multiple provider endpoints to the providers API.
The function for updating authentications did not re-authenticate when changing
an endpoint or an authentication. This commit updates the authentication in this cases.
Issue
https://github.com/ManageIQ/manageiq/issues/7256

@miq-bot add_label providers/containers, api
@simon3z @dkorn @abellotti please review

LGTM :+1:

@abellotti @imtayadeway please review

@simon3z @abellotti :+1: :+1: about the missing tests
While writing the tests I found the real problem.
It was not in the API, but in the ext_management_system model. The model schedule a new authentication refresh when credentials change, but in our case it did it for :default instead of :bearer.
@kbrock please review

it's no an API thing now is a core thing :-)
@miq-bot add_label core
@miq-bot remove_label api
cc @abellotti @kbrock

:+1: cc @chessbyte ready for merge

I'm 👍 with this.

The fix looks good.....I'm just wondering if a) The problem was in the model, and b) The tests aren't concerned with the response from the API, that a model spec would be more appropriate?

To follow up on @imtayadeway there are [examples] in the tests for testing that method.
If you are testing a particular method, please use a describe at the top level with your method under test
e.g.:
describe VmOrTemplate do
  describe "#connection_configuration_by_role" do
    # context if you need
    it "works with no parameters" do
      # ...
    end
  end
end

@kbrock @implowry Thanks :+1:

Added a spec to test how connection_configuration_by_role behaves when role is missing.
Did not remove the tests on the api because the bug/issue was reported on the API [1].

[1] To make this bug happen you need to call the function with missing authentication role. Currently this is the case only in the api's edit action (authentication objects do not have role fields), so the bug of wrongly guessing what is the authentication authtype based on the endpoint role is linked to the api.
@kbrock I used context,  because all the tests around do so, I do not know if to describe here ?

Did not remove the tests on the api because the bug/issue was reported on the API [1].

@yaacov that's fine - I just generally prefer to test only things in the response in request specs, and leave the nitty-gritty things up to lower level tests if t heir behavior never bubbles up to the user in the response

@kbrock please re-review

:+1: LGTM - Mr. @abellotti you have the floor

Thanks @kbrock


Uses the wallet instead of credit cards for checkout on subscription …

…orders.

Intended to address https://github.com/solidusio-contrib/solidus_subscriptions/issues/32/
Would like feedback on two things

Older versions of solidus. Not sure how far back the wallet implementation goes
default_wallet_payment_source changes the behavior here from picking the last default card to the first default card. Hypothetically a user should have only one default payment source, so I'm not sure if that's a concern or not.

Not clear why the build failed. All runs seemed to have 0 failures.