Isolated case where instance is in the "list" key but its correct key is not found in the KV store

I have one isolated case where and instance ID is wrong and the instance cannot be uninstalled.

As per Lev instance is in the "list" key, but its own key is not found in the KV store
I will attempt to find reproduction steps.
Observed Steps:

Deployed latest Jira
Run /jira setup
Use Setup flow to install the intance
Run /jira list

Observed: KV store shows an error and instance ID is wrong.

@levb - could the growth spike -related changes introduce this? Dylan has the instance preserved if needed.

@catalintomai Yes, but it was likely the result of testing and failing. There are no specific steps to reproduce AFAIK.

@dipak-demansol - can you help us identify repro steps?

@DHaussermann i'm Not able to Regenerate the issue.

@DHaussermann @hanzei @mickmister I am not able to reproduce this error. From the screenshots, it is looking like a Jira cloud instance so I tried installing that both using /jira setup and /jira instance install cloud <url> and both worked fine for me. I also tried your reproduction steps which also worked fine for me.
Just on a different note, this issue is looking similar to the issue https://github.com/mattermost/mattermost-plugin-jira/issues/902 for which I have created a PR https://github.com/mattermost/mattermost-plugin-jira/pull/914. Please see whether this PR solves this issue as well.

@DHaussermann @hanzei @mickmister I am not able to reproduce this error. From the screenshots, it is looking like a Jira cloud instance so I tried installing that both using /jira setup and /jira instance install cloud <url> and both worked fine for me. I also tried your reproduction steps which also worked fine for me. Please let me know whether I should try this for jira server/datacenter as well. Just on a different note, this issue is looking similar to the issue #902 for which I have created a PR #914. Please see whether this PR solves this issue as well.

@DHaussermann @hanzei @dipak-demansol The PR #914 mentioned here was release in the last Jira plugin release. Can you please confirm if the issue was fixed with that PR? If not, please let us know your opinions on this.


Custom ACME file name

Hi @kereis
I see ur new environment custom path, but i can see to how can I adapt it to my compose:
ACME_FILE: /my/custom/path/acme_the_second.json

This is my compose now, i want use extractor for acmezerossl.json (/share/docker/traefik/conf/acmezerossl.json):
version: '3.7'
services:
certdumper:
image: tmp/traefik-cert-dumper:latest
container_name: extractor
network_mode: none
volumes:

/share/docker/traefik/conf/:/traefik:ro
/share/docker/certs/subdomain.domain.com/:/output:rw
/var/run/docker.sock:/var/run/docker.sock:ro
secrets:
pkcs12_password
environment:
DOMAIN: subdomain.domain.com
PKCS12_PASSWORD_FILE: /run/secrets/pkcs12_password
COMBINE_PKCS12: "true"
OVERRIDE_UID: 1002
OVERRIDE_GID: 1000

secrets:
pkcs12_password:
file: /share/docker/certs/extractor/PKCS12_PASSWORD
I used it with acme.json without problem but now i want for acmezerossl.json but i littte confuse with ur explanation with /my/custom/path in volumen and enviroment acme_file but I have put the path but it gives me an error or I do not understand it according to my compose :
volumes:

./traefik/acme:/my/custom/path:ro

environment:

ACME_FILE: /my/custom/path/acme_the_second.json

Hey @deejayexe,
sorry for the delayed response.
In your case, you might want to mount /share/docker/traefik/conf/:/traefik:ro with ACME_FILE=/traefik/acmezerossl.json. :)

I'm closing this issue as there has been no activity ever since. If you have any other issues, feel free to create a new one or create a discussion. :)


[Bug]: vacuum warning talks about version 0.6 instead of 0.5.6

What happened?

⚠ It looks like you upgraded from a version below 0.6 and could benefit from vacuuming your database

This should say 0.5.6 right?
https://github.com/chroma-core/chroma/blob/main/chromadb/db/impl/sqlite.py#L112
Versions
Chroma v0.5.11
Relevant log output
No response

@Benzhaomin, you are correct that the message is somewhat confusing. The thing is that this feature was meant to be released in version 0.6.0 of Chroma, but in the interim, we decided that users could benefit from WAL pruning sooner than 0.6.0 would have been released. You can safely ignore this message :)

Fixed in https://github.com/chroma-core/chroma/pull/2964


4.5 Branch: update pom version and add upgrade path from 4.5.0 to 4.5.1

Updates pom version to 4.5.1-SNAPSHOT
Adds upgrade path from 4.5.0 to 4.5.1

Build fine with all unit tests passing, upgrade runs successfully from 4.5.0.
cc @ke4qqq @runseb @daanhoogland - would be great if you can review it

@bhaisaab just a thought, but from the commit messages I can't tell the critical bug fix was applied. I think you should merge. We need the pom version switch anyway. And we need to test the release on the actual source.

@runseb the bugs were fixed on 4.5 branch so they are already in 4.5 branch. I think to create 4.5.1 RC one could simply branch off from 4.5 once these commits are merged, or do you only want to create a different branch with only the identified critical bugfixes?
These are the list of important commits IMO that went into 4.5 branch but did n't made into 4.5.0:
https://github.com/apache/cloudstack/commit/02cadc3fb3fae7f5e8c87b7fafb977fb5eeae6eb
https://github.com/apache/cloudstack/commit/f3f47f25bab8661f31e5d470995f6f24cc08310e
https://github.com/apache/cloudstack/commit/f9090eacd6432856ca7504ebdfce38d65f8d019d
https://github.com/apache/cloudstack/commit/b2b9de7fa39825e8ff111353619df4e5aece12e6
https://github.com/apache/cloudstack/commit/b879916f5c64ddbca8713852b2c0ac187e9be1ff
https://github.com/apache/cloudstack/commit/ab8f367850c7ef75e1ff851397ff7dee4b5e40ab
https://github.com/apache/cloudstack/commit/729e239a471dc9910f550e7ce0c01e29fa920381

On Mar 11, 2015, at 5:09 PM, Rohit Yadav<EMAIL_ADDRESS>wrote:

@runseb the bugs were fixed on 4.5 branch so they are already in 4.5 branch. I think to create 4.5.1 RC one could simply branch off from 4.5 once these commits are merged, or do you only want to create a different branch with only the identified critical bugfixes?
These are the list of important commits IMO that went into 4.5 branch but did n't made into 4.5.0:

So let me show my ignorance here.
4.5.0 is a tag in the 4.5 branch ? correct ?
Commits were made on top of that to fix some issues including a critical bug fix in 4.5.0 that is forcing us to release 4.5.1 quickly.
Why don't we do a linear release on the 4.5 branch ? Why do you want to branch from 4.5 ?
In the end we vote on a git hash.

02cadc3
f3f47f2
f9090ea
b2b9de7
b879916
ab8f367
729e239
�
Reply to this email directly or view it on GitHub.

@runseb So we've two options:
I merge this into 4.5 and then a 4.5.1 RC1 candidate is cut off 4.5 branch. On 4.5 branch there aren't many commits that have went into after 4.5.0 was cut/released.
Or,
I merge this into 4.5 and share only commits that need to be picked on top of 4.5.0 (tag). That is - I'll create a branch from the 4.5.0 tag and cherry-pick commits that need to go into the emergency 4.5.1 and use that for voting?
Which one do you prefer?

@runseb yes, I want a linear release too; just use latest 4.5 (after we merge this).
I'm testing it now and then merging if it passes.

Ran basic tests against KVM, they passed for merging.


Bug: Search Bar did not work with Pool Name

Describe the bug
When I searched the name of pools: TestToken, nothing shows up while there are still many pools of TestToken
To Reproduce
Steps to reproduce the behavior:

Go to https://app.poolz.finance/dashboard
Click on Search Bar
Type: TestToken
See the screen: No Pools to show

Expected behavior
All pools which have the name TestToken should appear in the search result
Screenshots

Desktop (please complete the following information):

OS: Microsoft 10
Browser Chrome
Version 87.0.4280.88

Additional context
N/A
Wallet address
0x306B769A3B4B4c2D59fC1580f581796Ed9dfDf2F

https://github.com/The-Poolz/Poolz-Back/issues/34

https://github.com/The-Poolz/Poolz-Back/issues/34


Update search-howto-index-sharepoint-online.md

Adding the use of IncludeFolder parameter for URL that includes spaces.
I have detected the use of includeFolder do not support it correctly.
I´m Microsoft Employee<EMAIL_ADDRESS>happy to understand if this change make sense or not or I'm not correctly using it.

Followed up with requester offline to provide context and will close the PR.

#please-close


ci: use action vars

What type of PR is this?

[x] Refactor

Perhaps we should move these variables to the secrets configuration in Github.

Originally posted by @junnplus in https://github.com/RedashCommunity/redash/pull/3#discussion_r1189364264
Description

How is this tested?

[x] Unit tests (pytest, jest)
[x] E2E Tests (Cypress)
[ ] Manually
[ ] N/A

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Someone can merge it test CI.

Someone can merge it test CI.

Please wait a moment, I am still configuring secrets.

Someone can merge it test CI.

Please wait a moment, I am still configuring secrets.

Ok, are you a Chinese?

Someone can merge it test CI.

Please wait a moment, I am still configuring secrets.

You can merge it by yourself.

I will first put it in vars.

Unfortunately, vars cannot be read in fork pull requests.

Ouch.  Hmmm, would it work as a secret instead of as a variable?

Ahhh, thanks.  Got it. :smile:

Sorry this PR didn't work out.  I guess it was useful for us to investigate though. :smile:


Sync eng/common directory with azure-sdk-tools for PR 2617

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/2617  See eng/common workflow

/check-enforcer override


PR #33 broke compatibility

Yeah, so Wrap() used to return *Error and now returns error. This will break a lot of people. Regardless of the merits of this change, in principal, this was a backwards-incompatible change that should not have been made. Now, your package is breaking all of my packages upon upgrade, and all of the outside projects that are consuming them, and doubtless more well beyond just my scope.
https://github.com/go-errors/errors/commit/2ae1e4450826c9fecb6d5eb82b216f93f5808770
Error output (with a replace clause in the go.mod):
../go-logging/v2/log.go:356:14: cannot use "github.com/go-errors/errors".Wrap(err, 2) (type error) as type *"github.com/go-errors/errors".Error in assignment: need type assertion
../go-logging/v2/log.go:483:20: cannot use "github.com/go-errors/errors".Wrap(err, 1) (type error) as type *"github.com/go-errors/errors".Error in return argument: need type assertion
../go-logging/v2/log.go:489:20: cannot use "github.com/go-errors/errors".Wrap(err, 1) (type error) as type *"github.com/go-errors/errors".Error in return argument: need type assertion

I would request that you revert this change, and move this feature, if still required, to the next major release in order to maintain API compatibility with all current integrations (per the Go Compatibility Promise).

Hey @dsoprea!
I'm sorry about that – I didn't consider the impact this would have on people using libraries that transitively depend on this!
(I had erroneously assumed that people would either have a version in go.mod already in which case they'd continue to see the old behaviour until they opted in to an upgrade, or they would be adding errors to their mod file for the first time in which case they'd get the better behaviour from day one. This is mostly true, but in hindsight is obviously broken if someone depends both on errors directly, and also a library that depends on errors; because they can chose to upgrade errors without the knowledge of the library author).
I'll revert for now.

As well as if other maintainers just do a general update. They're blocked from general updates because of a dependency (you) of a dependency (my logging package) of a dependency (my package that they're using) of a dependency (their package). The whole chain breaks down. In this case, he was meaning to just update my package and was updating everything, but, still, I don't like that a deeper requirements of my project, several times removed from his project, is preventing him from conducting his business.
I made the change to adopt error versus *errors.Error because I wasn't sure if you'd respond. However, because a) those values are not a completely internal semantic of go-logging (the wrapped-error values can be returned directly and captured by an external caller), and b) the loss of type-safety (because we're now often passing around error rather than *errors.Error) means that the stacktrace printouts could potentially fail if accidentally called for unwrapped errors. So, I need to very thoroughly test it and all of its integrations and add some panics where the stacktrace is expected to be available but may no longer be, and I'm not prepared to do that at this moment, especially in the context of actively failing integrations. Better to just revert (as you have already done).
Honestly, I'm not a huge fan of the above. I would strongly encourage you to push it into the next release, which I will probably never adopt. I don't have an issue with the way it was already working.
Thanks for responding/reacting so quickly.
The revert, for the record: https://github.com/go-errors/errors/commit/b28c3b08d7afb2c96fb4c9cf7d9410bb8a4088d6

Confirmed resolved.

Thanks for the reply (I also did not realize that go get -u would update transitive dependencies), and sorry again for the frustration.


Chapter 4 - df06.py faces default quota limit

In case a default project quota on GCP is still in place ("trial" account with free credit), df06.py fails due to  '--max_num_workers=10'. The default quota is 8.
To make this run, change
'--max_num_workers=10', to '--max_num_workers=8', in the df06.py.
Alternatively, change from "free trial account" - "Upgrade" in IAM - Quotas.
Documentation: https://cloud.google.com/compute/quotas

thanks, changed.


use updated envoy config

Summary
Use the updated envoy config generation to run validation.
Related issues

https://github.com/pomerium/pomerium/pull/4098

Checklist

[ ] reference any related issues
[ ] updated docs
[ ] updated unit tests
[ ] updated UPGRADING.md
[ ] add appropriate tag (improvement / bug / etc)
[x] ready for review

always serves self-signed cert for me for some reason for all ingresses. will dig in why on monday.


Breadcrumb vs Panel Padding

The breadcrumbs and panels are used on most pages and their padding is not the same leading to the Title not being aligned

the breadcrumb has a left padding of 1rem whereas the panel has 1.25rem
I think 1rem is the preferred one, the panel content has 1.25rem as well - I think all the paddings (left:right) should be the same, either 1rem or 1.25rem

I changed this and its released in v2.6.11

The header is fine now but the panel-content padding is still to big.

Sorry about the circumstances... i fixed it and released it again 👍


Update catbird to 0.19.0

Codecov Report

Merging #214 into master will increase coverage by 0.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #214      +/-   ##
==========================================
+ Coverage   97.37%   97.59%   +0.21%
==========================================
  Files          28       28
  Lines         916      916
  Branches       70       70
==========================================
+ Hits          892      894       +2
+ Misses         24       22       -2

Impacted Files
Coverage Δ

core/src/main/scala/io/iteratee/Enumeratee.scala
100% <0%> (+0.92%)
:arrow_up:

Continue to review full report at Codecov.

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


Update Workflow

Description
Adding a GitHub workflow to configure an automated process to run 3 jobs in a self-hosted runner
Validation
This CI pipeline includes a clang-format job and test using Ctest from CMAKE. Algo generates an HTML report with Code coverage using gcov and lcov

[X] test_strio_lib
[X] 100% Branches on Code Coverage

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[-] Any dependent changes have been merged and published in downstream modules

3 jobs created.


Support inherit the attributes of the old version when updating template of the service to a new version

Is your enhancement related to a problem? Please describe.
when the template of the service is updated to a new version, the attributes of the old version are replaced.
Describe the solution you'd like

Support inherit the attributes of the old version when updating template of the service to a new version;
Consider the merging of attributes and the handling of attributes for differences.

Environment

Walrus version: main 73e6ce88f4205e030d30ff4276e82d687c0ccdd0
UI version: dev-860ae96

Test Result: pass

Environment

Walrus version: main 66a2214c8ea5dfb7fd8542fecb5e87a3778fc07e
UI version: dev-4dd2e5a

Test Result:
When upgrading the template version of a resource definition, please make it able to inherit the attributes from the original template too.

Environment

Walrus version: main 4eef11db3efc80ce93bb17814e5e8fb822d75d45
UI version: dev-8ceaed8

Test Result: pass


Fix documented metrics labels to work for k8s 1.16+

This was brought up in https://github.com/kubernetes-sigs/prometheus-adapter/issues/289. The metric labels are incorrect for Kubernetes 1.16+, because the labels were removed.

Thank you for taking the time to update the examples :slightly_smiling_face: . Would you mind also updating the config generator? https://github.com/kubernetes-sigs/prometheus-adapter/blob/master/cmd/config-gen/utils/default.go
/ok-to-test

@dgrisonnet great call out, made the change

From the CI failures, it looks like some labels also need to be updated in the tests.

Perfect! Thank you @aackerman :slightly_smiling_face:
/lgtm
/approve

@dgrisonnet thank you for the feedback, it really helped.


feat: options in session.save function

I would like to be able to pass options to the session.save function.
This would be useful for making a cookie persistent by default, but can be overridden with the options. For example when a user toggle a "Remember me" checkbox.
If there already is such an option, please show me how 🙂

Also the you might want to override the TTL depending on user specifics. So agreed.


Add unit tests for unsubscribe use case

The file is in here: unsubscribe.go
Steps:

Create a file unsubscribe_test.go in the same directory
Create a mock for the repository interface. I recommend using matryer/moq for it, but suggestions are welcome
Start testing! :vertical_traffic_light:

hey, can I take this issue ?

Can i take this?


Added Categories Section

Fix for issue #3099. Added documentation for how and why to add Categories in the Code Editor for a Marketing Campaign.

Description of the change:
Reason for the change:
Link to original source:

Closes #
@ksigler7

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @rjheim,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


default-filters Hystrix fallback uri is routed all the time

spring:
cloud:
gateway:
default-filters:
- name: Hystrix
args:
name: fallbackcmd
fallbackUri: forward:/fallback
i want this Hystrix  can use to all route in gateway. but i found it work before route filter,so it always route to the forward uri  but the route is online

my pom.xml
....

org.springframework.boot
spring-boot-starter-parent
2.0.5.RELEASE

<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<java.version>1.8</java.version>
<spring-cloud.version>Finchley.SR1</spring-cloud.version>

...

org.springframework.cloud
spring-cloud-dependencies
${spring-cloud.version}
pom
import

i can't upload my demo for my company.
my conf:
spring:
  cloud:
    gateway:
      default-filters:
       - name: Hystrix
         args:
          name: fallbackcmd
          fallbackUri: forward:/fallback
       - name: RequestRateLimiter
         args:
            redis-rate-limiter.replenishRate: 10
            redis-rate-limiter.burstCapacity: 20
            key-resolver: '#{@ipKeyResolver}'
      routes:
       - id: test-server-1
         predicates:
         - Path=/test/**
         - Weight=test-server,50
         uri: http://<IP_ADDRESS>:9089
       - id: test-server-2
         predicates:
         - Path=/facebank/**
         - Weight=test-server,50
         uri: http://<IP_ADDRESS>:9088

i use Finchley.SR2 now

@xkupc there are basically two ways to work with the fallbackUri:

have the /fallback endpoint or webflux handler within your gateway app
have it in a different app and provide routing to it in your gateway setup, like so:

spring:
  cloud:
    gateway:
      routes:
      - id: ingredients
        uri: lb://ingredients
        predicates:
        - Path=//ingredients/**
        filters:
        - name: Hystrix
          args:
            name: fetchIngredients
            fallbackUri: forward:/fallback
      - id: ingredients-fallback
        uri: http://localhost:9994
        predicates:
        - Path=/fallback

In this example, there is no fallback endpoint or handler in the gateway application, however, there is one in another app, registered under http://localhost:9994.
Is this helpful? If not can you describe exactly what happens as opposed to what you expect to happen and provide a demo project that we could run locally to verify the issue?

@OlgaMaciaszek
i did it,i mean when i configure default-filters Hystrix ，all the request are route to /fallback regardless of whether the backend service is online
@RestController
public class HystrixFallbackController {
    @RequestMapping("/fallback")
    public Mono<String> fallback() {
        return Mono.just("system busy,please try later");
    }
}

@xkupc have you found out what the issue was?

Same is the case with me. I have my .yml file as following:
server:
  port: 8080

spring:
  application:
    name: gateway

  sleuth:
    sampler:
      probability: 1.0

  cloud:
    gateway:
      routes:
        - id: view_route
          uri: lb://VIEW-SERVICE
          predicates:
            - Path=/unison/view/**
          filters:
            - name: Hystrix
              args:
                name: fallbackCommand
                fallbackUri: forward:/fallback

        - id: data_route
          uri: lb://CORE-SERVICE
          predicates:
            - Path=/unison/data/**

logging:
  level:
    org.springframework: DEBUG
    org.springframework.web: ERROR

eureka:
  instance:
    prefer-ip-address: true
    lease-expiration-duration-in-seconds: 5
    lease-renewal-interval-in-seconds: 5
  client:
    fetch-registry: true
    registry-fetch-interval-seconds: 5

management:
  endpoints:
    web:
      exposure:
        include: hystrix.stream

Whenever I hit the URL http://localhost:8080/unison/view/9000041131 it gives me the fallback response regardless of the service running or not.
But when I remove the fallback filter, I can see the proper response.

@hammadnaeemhere Please provide a minimal, complete, verifiable example that reproduces the issue.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


swaggerGenerator.js is throwing error

include-all attempted to require(/home/anasuya/Documents/FrescoPlay/date-api/config/swaggergenerator.js), but an error occurred::
Details:ReferenceError: sails is not defined
at Object. (/home/anasuya/Documents/FrescoPlay/date-api/config/swaggergenerator.js:12:22)
at Module._compile (module.js:641:30)
at Object.Module._extensions..js (module.js:652:10)
at Module.load (module.js:560:32)
at tryModuleLoad (module.js:503:12)
at Function.Module._load (module.js:495:3)
at Module.require (module.js:585:17)
at require (internal/module.js:11:18)
at /home/anasuya/Documents/FrescoPlay/date-api/node_modules/include-all/lib/help-include-all-sync.js:271:33
at Array.forEach ()
at _recursivelyIncludeAll (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/include-all/lib/help-include-all-sync.js:174:11)
at includeAll (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/include-all/lib/help-include-all-sync.js:292:5)
at helpBuildDictionary (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/include-all/lib/help-build-dictionary.js:43:15)
at Function.module.exports.aggregate (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/include-all/index.js:101:10)
at Array.loadOtherConfigFiles (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/sails/lib/hooks/moduleloader/index.js:247:22)
at /home/anasuya/Documents/FrescoPlay/date-api/node_modules/sails/node_modules/async/lib/async.js:591:38
at _arrayEach (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/sails/node_modules/async/lib/async.js:85:13)
at Object.async.auto (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/sails/node_modules/async/lib/async.js:552:9)
at Hook.loadUserConfig (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/sails/lib/hooks/moduleloader/index.js:245:13)
at Hook.wrapper [as loadUserConfig] (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/@sailshq/lodash/lib/index.js:3250:19)
at Hook.loadModules (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/sails/lib/hooks/userconfig/index.js:41:27)
at Hook.wrapper [as loadModules] (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/@sailshq/lodash/lib/index.js:3250:19)

hmmm taking a look at it now

One more issue I am facing,
verbose: A socket is being allowed to connect, but the session could not be loaded.  Will create an empty, one-time session to use for the life of the socket connection.  Details:  Error: Session could not be loaded     at _createError (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/sails/lib/hooks/session/index.js:31:19)     at Immediate._onImmediate (/home/anasuya/Documents/FrescoPlay/date-api/node_modules/sails/lib/hooks/session/index.js:34:11)     at runCallback (timers.js:804:20)     at tryOnImmediate (timers.js:762:5)     at processImmediate [as _immediateCallback] (timers.js:733:5)
This error is coming ,anyways its not hampering any work,,,still ,please let me know if I need to add anymore configuration

the issue is coming in swaggerJsonPath: sails.config.appPath + "/swagger/swagger.json" this line
sails.config.appPath is throwing this error actually

that sails is undefined right ?

yes

Oh yea, check your configuration ( config/globals.js) and see if sails is true

Tried updating config/globals.js , but no luck.
created a demo repo https://github.com/anasuya1117/myToDoApp ,please have a look

Taking a look later today 👍

Seen the error, in your swaggergenerator.js you added swaggerJsonPath to usesails.config which is the default path, if you want to stick with the default path no need for adding it, remove it from your swaggergenerator.js. If you want to change the folder, then you do something like this
swaggerJsonPath: "./assets/swagger/swagger.json" --> using the absolute path relative to the project

great, It worked !!! Thanks a lot for your help.


Matlab wrapper for hopsanc

A Matlab class for interfacing with HopsanCore using the hopsanc library.
Depends on #1943.

This now depends on #1952.


Multiple front ends hosting with the same cognito same login

I created an aws amplify back end  as follows:
amplify init

amplify add auth

amplify push

amplify publish

Once this was done I created a front end and used the amplify pull command in the front end app
amplify pull --appId ************* --envName *******

I wanted to host this app so in the front end app I did
amplify init

amplify add hosting

amplify push

amplify publish

For the other front ends that i wanted to use the same backend on i created them in the same way and this works fine.
Is this the correct way to do this if so if i make changes to the cognito how would i get the updates to show on the front end?
Next when a user is logged into one how would I make is so they dont have to log into the app front ends?

Hi @robin22d, check out the docs we have for multiple frontends.

Hi yes I have had a look at the docs but I cannot see anything about hosting unless im missing something? Also do you know of any docs that would help me with when a user is logged into one how would I make is so they dont have to log into the app front ends?

Is there something not covered in the hosting section? What are you trying to accomplish?

Also do you know of any docs that would help me with when a user is logged into one how would I make is so they dont have to log into the app front ends?

I don't fully understand the question. How would the user log in before accessing the FE?

I don't fully understand the question. How would the user log in before accessing the FE?

I have two apps

app 1
app 2

The user has access to both apps and they log into app 1. Then when they go to app 2 they should already be logged in because both apps have the same back end. Its like login into gmail and then going to google docs and not having to log in again.

Is there something not covered in the hosting section? What are you trying to accomplish?

Yes I have had a look that the hosting and wanted to know if the way that im doing it is correct.

Hi @robin22d, thanks for clarifying! It sounds to me like you are looking for SSO (Single sign-on). Amplify does not currently have an out-of-the-box solution for SSO. I've marked this issue as a feature request.

Hi @robin22d, thanks for clarifying! It sounds to me like you are looking for SSO (Single sign-on). Amplify does not currently have an out-of-the-box solution for SSO. I've marked this issue as a feature request.


Put artifacts under preview other page to the right place.

Make changes to this page: https://review.docs.microsoft.com/en-us/java/api/overview/azure/other?view=azure-java-preview&branch=smoke-test

Docs Build status updates of commit e33a878:
:clock10: Full build: the average full build time is 266 min(s) 25 sec(s), this is based on the last 902 build(s) for this repository.

Docs Build status updates of commit e33a878:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

preview/docs-ref-autogen/overview/Core.yml
:x:Error

Details

preview/docs-ref-autogen/overview/Core.yml

[Error-ApplyTemplatePreprocessorError] Error transforming model "W:\oedq-o-unknown\raw-\mznwvchk.13n\rawmodel\preview\api\overview\azure\Core.raw.json" generated from "preview/docs-ref-autogen/overview/Core.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor: type is undefined

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b74edff:
:clock10: Full build: the average full build time is 266 min(s) 25 sec(s), this is based on the last 902 build(s) for this repository.

Docs Build status updates of commit b74edff:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

preview/docs-ref-autogen/overview/Core.yml
:x:Error

Details

preview/docs-ref-autogen/overview/Core.yml

[Error-ApplyTemplatePreprocessorError] Error transforming model "W:\zcxd-o-6e737481\raw-\o14caj4h.nx4\rawmodel\preview\api\overview\azure\Core.raw.json" generated from "preview/docs-ref-autogen/overview/Core.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor: type is undefined

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5a6ded1:
:clock10: Full build: the average full build time is 266 min(s) 25 sec(s), this is based on the last 902 build(s) for this repository.

Docs Build status updates of commit 5a6ded1:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

preview/docs-ref-autogen/overview/Core.yml
:x:Error

Details

preview/docs-ref-autogen/overview/Core.yml

[Error-ApplyTemplatePreprocessorError] Error transforming model "W:\cgzv-o-f2eda23e\raw-\0ohvghkh.qwi\rawmodel\preview\api\overview\azure\Core.raw.json" generated from "preview/docs-ref-autogen/overview/Core.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor: type is undefined

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 77a2039:
:clock10: Full build: the average full build time is 266 min(s) 40 sec(s), this is based on the last 903 build(s) for this repository.

Docs Build status updates of commit 77a2039:
:clock10: Full build: the average full build time is 266 min(s) 46 sec(s), this is based on the last 904 build(s) for this repository.

Docs Build status updates of commit 77a2039:
:clock10: Full build: the average full build time is 266 min(s) 46 sec(s), this is based on the last 904 build(s) for this repository.

Docs Build status updates of commit 77a2039:
:clock10: Full build: the average full build time is 266 min(s) 46 sec(s), this is based on the last 904 build(s) for this repository.

Docs Build status updates of commit 77a2039:
:clock10: Full build: the average full build time is 266 min(s) 46 sec(s), this is based on the last 904 build(s) for this repository.

Docs Build status updates of commit 77a2039:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

package.json
:white_check_mark:Succeeded

preview/docs-ref-mapping/reference-preview.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Set minimum number of cores to 1

I'm able to pass an input file with number of cores set to 0.

Fix pushed in "develop" branch. Working for me. Need a second person to check

Works, thank you.


There are several issues with docs

Describe the bug
There are several issues with docs.

ValueError spelling issue
The parameter end is not present in RandomChannelShift and RandomBrightness layer

code in the layers needed to be updated


SKCore: make . part of the extension

This is just a cleanup change to setup the extensions for other targets.
This allows for platforms to have no extensions or an extension which
may or may not include a ..

@swift-ci please test

@benlangmuir would you mind merging this please?


add drag coefficient and roughness to cache

Purpose

Cache drag coefficient and roughness as 2D fields. This is needed by the coupler.
To-do

Content

Oh this is allocating a lot...https://buildkite.com/clima/climaatmos-ci/builds/4408#0183d822-6472-4081-9183-e01830927310/140-186 @charleskawczynski is there anything I did wrong in the cache?

bors r+


Fix nil pointer for policyDef in runtime

Signed-off-by: Deepanshu Agarwal<EMAIL_ADDRESS>Description
Few Certification tests in dapr/components-contrib are failing, if somehow policyDef is nil. e.g.:
https://github.com/dapr/components-contrib/actions/runs/3872016087/jobs/6600380515#step:23:174
https://github.com/dapr/components-contrib/actions/runs/3872016087/jobs/6600381140#step:23:184
https://github.com/dapr/components-contrib/actions/runs/3872016087/jobs/6600380245#step:23:318
So, for latest dapr/dapr referred in contrib, they are failing:
https://github.com/DeepanshuA/components-contrib/actions/runs/3873108358/jobs/6602751037
This small check fixes that.
Fix verification:
https://github.com/DeepanshuA/components-contrib/actions/runs/3875970689/jobs/6609245631 (FYI: cloud parameters are not set on my env., so cloud related tests are failing, so that's not a concern).
Issue reference

Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

@DeepanshuA Please fix conflicts and fix DCO also. Rest lgtm.

Sorry the DCO issue was my fault. Fixed


Log spam with HikariPool

Our server logs are spammed with debug details from HikariPool and LuckPerms, for example:
[05:53:15] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:32] [HikariPool-1 housekeeper/DEBUG] [com.zaxxer.hikari.pool.HikariPool/sponge]: HikariPool-1 - Pool stats (total=10, active=0, idle=10, waiting=0)
[05:53:32] [Server thread/DEBUG] [FML/]: Gathering id map for writing to world save Teal
[05:53:33] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:36] [luckperms housekeeper/DEBUG] [com.zaxxer.hikari.pool.HikariPool/sponge]: luckperms - Pool stats (total=10, active=0, idle=10, waiting=0)
[05:53:39] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:44] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:47] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:48] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:49] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:51] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:55] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:57] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:53:58] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:00] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:01] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:02] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:02] [HikariPool-1 housekeeper/DEBUG] [com.zaxxer.hikari.pool.HikariPool/sponge]: HikariPool-1 - Pool stats (total=10, active=0, idle=10, waiting=0)
[05:54:03] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:06] [luckperms housekeeper/DEBUG] [com.zaxxer.hikari.pool.HikariPool/sponge]: luckperms - Pool stats (total=10, active=0, idle=10, waiting=0)
[05:54:11] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:17] [Server thread/DEBUG] [FML/]: Gathering id map for writing to world save Teal
[05:54:22] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:32] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:32] [HikariPool-1 housekeeper/DEBUG] [com.zaxxer.hikari.pool.HikariPool/sponge]: HikariPool-1 - Pool stats (total=10, active=0, idle=10, waiting=0)
[05:54:33] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:36] [luckperms housekeeper/DEBUG] [com.zaxxer.hikari.pool.HikariPool/sponge]: luckperms - Pool stats (total=10, active=0, idle=10, waiting=0)
[05:54:37] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:42] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:46] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:49] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:54:52] [Thread-26/DEBUG] [com.zaxxer.hikari.pool.PoolBase/sponge]: HikariPool-1 - Reset (autoCommit) on connection org.mariadb.jdbc.MariaDbConnection@235a74f9
[05:55:00] [Server thread/INFO] [nucleus/]: Server ran the command: /weather Teal clear

Over 3h40m of runtime (ServerStarted to ServerStopped), we've 20221 lines, including:

4674 lines about "HikariPool-1 - "
877 lines about "luckperms - Pool stats"
That's ~27% of log lines

This is with
forge-1.10.2-<IP_ADDRESS>2-universal.jar
spongeforge-1.10.2-2202-5.1.0-BETA-2020.jar
LuckPerms-Sponge-2.16.79.jar

As far as I can tell, it's not possible to set SLF4J's logging level at runtime.
You could try using these startup flags to suppress logs from "com.zaxxer.hikari".
https://stackoverflow.com/questions/14544991/how-to-configure-slf4j-simple
http://slf4j.42922.n3.nabble.com/How-to-programmatically-set-log-level-in-SLF4J-td45652.html
https://stackoverflow.com/questions/27274115/disable-hikaripool-logging
However, I've spent a good ~20 mins testing and can't get it to work for me.
Either way, this isn't really an LP issue. :/

Not sure how that would be possible in LuckPerms? I just download the Hikari jar and load it. How would the logger implementation know to read from a file in the LP jar?

In the Sponge issue I've linked, someone did it programmatically

Ok, I'll look into it.

Ah, I don't think this will work with LuckPerms. I bundle slf4j-simple, not log4j.


Duplicate results reported

Sometimes, when rolling, the roll is repeated. Usually this results in a second, different set of rolls, but occasionally will result in the same set being sent twice.
Example:

[11:56 PM]
BOT
rollem: @Hypno (Sgt. Gray),
4 ⟵ [2]1d6 + 2
7 ⟵ [5]1d6 + 2
3 ⟵ [1]1d6 + 2
3 ⟵ [1]1d6 + 2
[11:56 PM]
BOT
rollem: @Hypno (Sgt. Gray),
5 ⟵ [3]1d6 + 2
6 ⟵ [4]1d6 + 2
3 ⟵ [1]1d6 + 2
7 ⟵ [5]1d6 + 2

This was one roll - 4#1d6+2; the replies came back simultaneously (or as close to such as they looked like one response to me). Occurred on Apr 23, 2020 at 11:56PM Eastern.

Thanks for the report!
To help narrow down the search for the cause:

Does this usually happen once every now and then, happen for every roll for short time (a few minutes to an hour) and then stop, or something else?
Next time it happens can you do '@rollem stats' - this is to see if two bots are trying to respond or if it's one double-responding for some reason? It will also help me tell if one specific shard is having issues.

The rest of this comment is mostly notes for future-me.

Off the top of my head, the bits that could be breaking:

kubernetes is starting a second bot before the first has shut down, when it decides it's time to recycle the instance. could be mitigated by adding inter-bot communication bus (via redis? doesn't k8s already have something for this?)
a single bot is 'receiving' the message twice (due to a network hiccup?) - could be easily mitigated by keeping a local rolling list of recently replied post IDs and refusing to process them twice
some mystery discord.js retry logic is causing one bot to send the reply twice. it's unclear how i would avoid this if it's the case
discord itself is passing the message through twice

1 or 2 could be the cause when the replies don't match. 3 and 4 when the replies do. Barring cosmically unlikely events. Or thread concurrency shenanigans that I don't think discord.js should be doing.

It usually happens every now and then. Most of the time it's once and then stops; very rarely we've seen it double for 2-3 rolls in a row. I'll keep an eye out to do the @rollem stats

Yes, that's exactly the issue. Haven't seen it since the report I made, unfortunately (?).


automatic compile like Webforms Website

is there a possibilty to automatically rebuild the / one file on code change like ASP.NET Webforms Website?
I am thinking of typically real websites, which a small amount of logic, Admin can go to code and change a line Sourcecode in cs/vb with notepad and done.

Thanks for contacting us, @hannespreishuber.
This is not something we have support for. We do support runtime compilation for .cshtml files, but that's it.


My Morphmap is returning empty

Laravel Version: #.#.# 5.4
PHP Version: 7
Database Driver & Version:

Description:
I have a table like so:
    Schema::create('comments', function (Blueprint $table) {
        $table->increments('id');
        $table->integer('user_id');
        $table->integer('comment_id');
        $table->string('comment_type');
        $table->text('comment');
        $table->timestamps();
    });

Which is populated like so:
INSERT INTO `job`.`comments` (`id`, `user_id`, `comment_id`, `comment_type`, `comment`, `created_at`, `updated_at`) VALUES ('1', '1', '8', 'courses', 'Hello', NULL, NULL);

I have a course model like so:
<?php

namespace App\Modules\Courses\Models;

use Illuminate\Database\Eloquent\Model;
use Illuminate\Support\Facades\Auth;
use Laravelista\Comments\Comments\Traits\Comments;

class Courses extends Model
{
    use Comments;

    protected $table = 'courses';

    public function comments()
    {
        return $this->morphMany('App\Modules\Comments\Models\Comments', 'comment');
    }

which morphs my Comment model with my Morph map:
<?php

namespace App\Modules\Comments\Models;

use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\Relations\Relation;

Relation::morphMap([
	'courses' => App\Modules\Courses\Models\Courses,
]);

class Comments extends Model
{
    public function commentable()
    {
      return $this->morphTo();
    }
}

If I reference my map in my row and use courses at the type it returns empty as you can see from Tinker:

But if I use the full namespace in the comment_type in the database it works:
INSERT INTO `job`.`comments` (`id`, `user_id`, `comment_id`, `comment_type`, `comment`, `created_at`, `updated_at`) VALUES ('1', '1', '8', 'App\\Modules\\Courses\\Models\\Courses', 'Hello', NULL, NULL);

What am I doing wrong, and how can I fix this?
edit: I have also tried the suggestions of placing it inside my app service provider too, but that didn't work neither:

Steps To Reproduce:
I am using the following packages:
    Hootlex\Friendships\FriendshipsServiceProvider::class,
    Overtrue\LaravelFollow\FollowServiceProvider::class,
    Conner\Likeable\LikeableServiceProvider::class,
    Netshell\Paypal\PaypalServiceProvider::class,
    ConsoleTVs\Charts\ChartsServiceProvider::class,
    RachidLaasri\LaravelInstaller\Providers\LaravelInstallerServiceProvider::class,
    Monarobase\CountryList\CountryListServiceProvider::class,
    Rap2hpoutre\LaravelLogViewer\LaravelLogViewerServiceProvider::class,
    Yajra\Datatables\DatatablesServiceProvider::class,
    Yajra\Datatables\ButtonsServiceProvider::class,
    Caffeinated\Modules\ModulesServiceProvider::class,

LOL... I'm quitting now. Sorry guys wasn't an error. Silly me didn't realise I had to exit tinker for changes to take affect. I apoligise.


[ExtensionApp] "standalone" mode

I was looking at the extension app mechanism, and I have some thoughts for the voila use case.

Ideally, I would like to have the voila command line to become an alias on jupyter voila. A byproduct will be that we should be able to drop the VoilaConfiguration mixin used by both the tornado application and the server extension...

Now, one thing about the voila command line that we would lose, is the guarantee that other server extensions are not enabled. The reason is that we generally want voila to be used to produce standalone web app that don't allow arbitrary code execution. Enabling the lab server extension defeats the purpose, because it would provide a means to access and execute code...

So an idea would be to have a --standalone option that only enables the selected server extension and not the other ones. Then voila would make use of jupyter voila --standalone...

cc @rolweber @Zsailer @epifanio

Another option would be to have each extension app decide whether they allow other server extensions or not when they are used as the main extension point.

I thought that the selected app is responsible for enabling all extensions that should be running, besides the default stuff that comes with Jupyter Server itself. So if the Voila extension doesn't enable Lab, then Lab isn't there. Am I mistaken there?

Ideally, I would like to have the voila command line to become an alias on jupyter voila.

Just for context, what is the motivation for this?

Just for context, what is the motivation for this?

This would reduce the number of entry points and simplify the codebase (e.g. no need for a VoilaConfiguration object).

In a way, voila and lab are two perfect examples of extension apps...

In the current ExtensionApp class, VoilaConfiguration already goes away (I desperately need to add documentation to demonstrate this).
In PR #59, I added logic to handle the extension-specific config. That way, extensions writers don't need to write their own mixin classes (like VoilaConfiguration).
How does this work?

ExtensionApp creates a Configurable object to store the extension's trait
It then passes this object to tornado web-servers settings under the '<extension_name>_config' key.
If the extensions' handlers inherit the provided ExtensionHandler class, this object is accessible under the handler's self.config attribute.

I'm also fine with adding a --standalone mode.

In the current ExtensionApp class, VoilaConfiguration already goes away (I desperately need to add documentation to demonstrate this).

Yep, but I guess this requires the voila command line to be an alias on jupyter voila.

I'm also fine with adding a --standalone mode.

:+1:

Yep, but I guess this requires the voila command line to be an alias on jupyter voila.

I think you're right.
You could, instead, have a small subclass that inherits the Voila ExtensionApp, changes the standalone trait to True, set this trait's tag config=False, and add a new voila entry-point pointing to this classes launch_instance method.

Adding in #70

Closing since we added standalone mode in #76.


Configure call to webhook in Circle CI build

This variables should be added into Circle CI ENV variables:
ORGANIZATION
WEBHOOK_PROJECT
CIRCLE_TOKEN

@s0b0lev , can you mention the exact variable values that are to be added?

@s0b0lev , any updates?

@norhh I am still looking for a reason why environment variables are not injected into build. Also, I didn't find any other variables which was declared in Circle CI build env as well.

@norhh , thanks to @fgimenez , issue is within settings, which is not allowed to inject env variables on forks. So I should use mythril-classic branch, and it should work. I will close this PR and create another one.


Change default Ceph release to Quincy

My main concern here is the potential for surprise upgrades.

Do you prefer to wait until we have a zed branch?

My main concern here is the potential for surprise upgrades.

Do you prefer to wait until we have a zed branch?

Let's discuss in today's infra meeting, but that might be safer. Deployments can always make these changes in their branches.

I think we agreed to stay on pacific for now

Pacific is EOL-ish - https://github.com/ceph/ceph/blob/main/doc/releases/releases.yml

Pacific is EOL-ish - https://github.com/ceph/ceph/blob/main/doc/releases/releases.yml

Yes. I'm not saying we shouldn't update clients to Quincy, but should we make such changes on a stable branch?

In this case it probably is not problematic (you would need to run bootstrap against a running cluster to make some serious problems), but I understand where you're going - I don't know even if we should have a default in s-k-c.

In this case it probably is not problematic (you would need to run bootstrap against a running cluster to make some serious problems), but I understand where you're going - I don't know even if we should have a default in s-k-c.

If we don't have a default in s-k-c then we depend on the default in the collection, which is less visible. We do specify the container image tag in s-k-c too, which is tied to the release

So let's just assume we just update the default once, in the early stages of a branch - and that's it.

Perhaps we should better document how to change the release in SKC docs?

Is it time to close this PR @priteau @markgoddard?

Is it time to close this PR @priteau @markgoddard?

Should I target it to zed instead?

It's already done: https://github.com/stackhpc/stackhpc-kayobe-config/blob/stackhpc/zed/etc/kayobe/cephadm.yml

Not required anymore.


A few basic NewUnifier optimizations

Use more Map functionality to make some operations cheaper.
Make a fold stricter on the inside and lazier on the outside. If the lists are long, this should give better cache utilization and reduce GC time.
Avoid recursively appending to the end of a list.

Fixes #nnnn
Scope:
Estimate:

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[ ] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

/KEVM-perf-run

/KEVM-perf-run

Do you see where something could've been reordered? Because I can't find it.

/KEVM-perf-run

/KEVM-perf-run


Way to find Size Of Variables.

Please fill in this pull request template before submitting
1. This pull request resolves #44
2. Description
(Write description of your changes here)
3. Fill in checklist by marking [x]

[x] I've read the CONTRIBUTING.md
[x] I was assigned to this issue
[ ] My code is formatted using required linting
[x] I've run my code locally and checked it works

I have written the tutorial in the exact format mentioned in CONTRIBUTING.md But, I have never formatted code using the required linting, so I have no idea how to do it. I am having trouble with that.

@nisheetkaran Merging your file now! Thanks for the contribution :tada:


GET .kibana/_search?size=1 crashes

Error message is
  File "/peek/peek/es_api_spec/api_completer.py", line 74, in <listcomp>
    return [Completion(c)
  File "/python3.10/site-packages/prompt_toolkit/completion/base.py", line 59, in __init__
    self.display = to_formatted_text(display)
  File "/python3.10/site-packages/prompt_toolkit/formatted_text/base.py", line 83, in to_formatted_text
    raise ValueError(
ValueError: No formatted text. Expecting a unicode object, HTML, ANSI or a FormattedText instance. Got 0

This is no longer an issue.


Add additional doc on working with webpack and secure services

Closing per https://github.com/Esri/angular-cli-esri-map/pull/58/commits/ca65abca58d3ea06093751085c69ba2d11080b2d


Question: Which platform is used by the Run-AlValidation

From yammer threads I understood the online appsource validation is now using BC25 as the validation platform.
Running the bccontainerhelper cmdlet Run-AlValidation is still running against BC24.4
How does the Run-AlValidation determines the correct version to use?
Or can we use/choose a version?

Run-AlValidation by default validates against the latest released version.
You can specify -ValidateNextMajor if you want to validate against next major.
Default is to -validateCurrent (I think)

Understood. If this remains ruling its clear to me.


gDEBugger doesn't work on lime if DYNAMIC_OGL is defined

Recently I noticed gDEBugger stopped working, and after removing DYNAMIC_OGL, it started working again.
This suggests that gDEBugger can only hook OpenGL functions statically linked to the app, not dynamically loaded ones. Should we disable this by default, when we build lime without ANGLE?

I'm not sure if there's a way we could make it work with dynamic OpenGL?
Our problem that is if we statically link to OpenGL, this can fail on systems without OpenGL installed. Perhaps this more an issue on Linux than Windows, though

Then can we enable this only on Windows?
As of today, all windows systems comes with basic OpenGL support (opengl32.dll), so this shouldn't be a problem for Windows. Newer OpenGL functions are always dynamically loaded with wglGetProcAddress().
Even though this flag is named "DYNAMIC_OGL", functions existed in fixed-pipeline OpenGL is still dynamically linked, at least on Windows. It's implemented in opengl32.dll. Compiler automatically inserts library loading call at startup if this flag is disabled.


Istio : Authentication failure

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
Envoy proxy fails to start properly, due to missing Service account token (not found on file system)
Happens even though, some other components do have mounted SA token
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[X ] Virtual Machine
[ ] Multi Control Plane
Expected behavior
Istio-proxy is up and functioning
Steps to reproduce the bug
Install istion via helm chart
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
How was Istio installed?
Via Helm chart
Environment where the bug was observed (cloud vendor, OS, etc)
Windows, Docker for Desktop
Windows, Minikube
MacOS, Docker for Desktop
MacOS, MInikube
**Errors **
Errors in a envoy-proxy sidecar, after auto-injection to Postgres or Reddis :
2021-07-25T08:28:53.156107Z warn failed to fetch token from file: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
2021-07-25T08:28:53.156176Z info xdsproxy connected to upstream XDS server: istiod.istio-system.svc:15012
2021-07-25T08:28:53.156778Z warn xdsproxy upstream [30] terminated with unexpected error rpc error: code = Unauthenticated desc = authentication failure
2021-07-25T08:28:53.157187Z warning envoy config StreamAggregatedResources gRPC config stream closed: 16, authentication failure
2021-07-25T08:29:00.113795Z warn failed to fetch token from file: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
2021-07-25T08:29:00.113855Z info xdsproxy connected to upstream XDS server: istiod.istio-system.svc:15012
2021-07-25T08:29:00.114575Z warn xdsproxy upstream [31] terminated with unexpected error rpc error: code = Unauthenticated desc = authentication failure
2021-07-25T08:29:00.114974Z warning envoy config StreamAggregatedResources gRPC config stream closed: 16, authentication failure
2021-07-25T08:29:12.932919Z warn failed to fetch token from file: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
** Summary **
Weird part is that on Windows 3 components has these errors  : IngressGateway, Reddis and Postgres
In the MacOs, there is only Postgres having issue with readiness probe, because of the envoy-proxy that is missing mounted services account and looks like it cant pass the auth due to that

I am guessing your pod has both the disable auto mounted cert, and you installed Istio with the option to use the auto mounted cert (an insecure option that had been deprecated for 2 years+).
I would change the option on the pod, or better yet change istio to use its own token - see https://preliminary.istio.io/latest/docs/ops/best-practices/security/#configure-third-party-service-account-tokens

Heh, unfortunately, not completely the case
Using third party JWT setting
I was able to resolve the Postgres issue with the probe, by automounting the SA token from the helm chart
For ingress gateway itself, still looking into more details
For pod, I can understand why this would happen, as SA in some cases wouldn't mount
But crashing the IngressGateway pod, due to the same  error (not the pods connecting to it causing the error) is weird
Gonna look into it a bit more & will update with more details
Maybe I've missed something, will do more of my homework
Thanks, @howardjohn for responding this quickly!

If you have third-party-jwt its not supposed to even look at those files. Maybe help to post the fully ingress pod yaml and log (including first lines)

Can i disable jwt for istio?


Register simple-progs.is-cool.dev

Added simple-progs.is-cool.dev using the CLI.

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA


ManualMap 64bit crashes with std::thread used

Hey, after wasting nearly 1,5 days to narrow down the reason why manual mapping my dll in x64 crashes instantly before DLL_PROCESS_ATTACH was being called, I am now looking at an EMPTY project which crashes the moment I have a single line defined that uses std::thread in a .cpp file which is not even used anywhere.
It works all fine in 32bit manual mapping, it also works fine with native injection method even in 64bit.
It just instantly crashes with 64bit and manual mapping.
I cannot explain why it happens, but maybe you can.
Win32Project1.zip
Edit: Fun fact, I took out all std::thread calls from my main project, but libraries which the project uses still have the same std::thread implemented, it still works in x64 manual mapping... weird

I played a bit more with my project in x64 now that I can inject, it looks like exception handling is not working (it works fine in 32bit for my code), any kind of exception instantly crashes it.

Exception handling is fine, sort of. Problems begin with CRT static linkage - /MT. Some CRT functions use  RtlPcToFileHeader to get mapped image base. That function walks InvertedFunctionTable which is empty because Dynamic exception table is used instead.
I've implemented InvertedFunctionTable support for x64 (Win10 only for now) in c39fc6057a86497f1a5519c1d0fc3bdb0754e38b.

Thank you for the quick response, I'll try to compile it with /MD and see if that helps :)

I'll try to compile it with /MD and see if that helps :)
It should work with /MT too after that commit.

Btw. do you have a "donate button" somewhere ?
No. No yet at least :)

Maybe check if https://www.patreon.com/ is something for you, you can put the link on the frontpage of you repo. I would subscribe then on a monthly basis ;)
Thanks again for the super quick response and solution!


Unable to see any visualization in the UI

I think I have all the data extracted properly but I dont see any visualization in UI. Output is as follows:
Its an Ubuntu 20.04 system
export KITTI360_DATASET=/opt/datasets/kitti360/KITTI-360/
sxv1kor@BMH7160115:/opt/datasets/kitti360/KITTI-360/kitti360Scripts/kitti360scripts/viewer$ ./kitti360Viewer.py
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 568, resource id: 6295943, major code: 40 (TranslateCoords), minor code: 0
/opt/datasets/kitti360/KITTI-360/data_2d_semantics/train/2013_05_28_drive_0000_sync/instanceDict.json
Loading /opt/datasets/kitti360/KITTI-360/data_3d_bboxes/train/2013_05_28_drive_0000_sync.xml...
building                      :	 538
pole                          :	 356
traffic light                 :	 17
traffic sign                  :	 182
person                        :	 60
rider                         :	 18
car                           :	 901
truck                         :	 11
bus                           :	 1
caravan                       :	 1
trailer                       :	 25
train                         :	 0
motorcycle                    :	 22
bicycle                       :	 44
garage                        :	 288
stop                          :	 1
smallpole                     :	 94
lamp                          :	 117
trash bin                     :	 153
vending machine               :	 10
box                           :	 104
Loaded 2960 instances
Loaded 10994 boxes
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 685, resource id: 6296203, major code: 40 (TranslateCoords), minor code: 0

Hi, thank you for reporting the problem. Which PyQt version do you use?

Hi, thank you for reporting the problem. Which PyQt version do you use?

Sorry for delay in replying. The version is:        PyQt5                         5.14.1
Its installed with the command:
sudo apt-get install python3-pyqt5
Reading package lists... Done
Building dependency tree
Reading state information... Done
python3-pyqt5 is already the newest version (5.14.1+dfsg-3build1)

Hi, I have the same problem


Make the room_id optional in sync-related events

According to the spec, this field can be absent in some contextes,
notably in the responses to the /sync endpoint, where the events
appear in a context where there is no ambuity regarding which room
the event is related to.
Fixes #19 and makes ruma-client now capable of parsing /sync responses
from synapse 0.34.0

Fixed.
I also made optional some other fields that can be missing from the summarized events in an initial sync.


Split init.py into several smaller files

As suggested by philiptzou in #131 , I took the time to split the huge init.py into several smaller files.
This leaves us with 7 files and 1 folder:

parsedatetime.py
constants.py
calendar.py
context.py
context_stack.py
warns.py
init.py
locales/

I also took the freedom to rename pdtContext and pdtContextStack to Context and ContextStack, as well as moving pdt_locales/ to locales/, for naming consistency purposes.
De-splitting init.py made me add the code copied from feedburner directly into calendar.py. This also highlighted unused code that I decided to remove.
I'm merging this PR into 3.0 because of the breaking changes this includes:

pdtContext is now Context
pdtContextStack is now ContextStack
pdtLocales is now in Constants.py but exposed via init.py
Version flags are now in Calendar.py but exposed via init.py
debug flag is now both in Calendar.py and Constants.py

Have a nice weekend

This change is

I'll take a closer look later but this seems like a good direction. The inconsistencies were causing problems in naming my new test classes as well, so it would be nice to have stronger naming precedent.

This PR is really straightforward as I do not have much experience on this project, but it could be the beginning of a discussion about further splitting, by creating modules for NLP processing, or different kind of parsing.

There are a lot of failing tests here due to import issues. The tests are going to be redone, but even so can you work on getting all of the tests to pass for this PR?

Current coverage is 77.86% (diff: 74.44%)

Merging #201 into v3.0 will decrease coverage by 0.15%

@@               v3.0       #201   diff @@
==========================================
  Files            14         17     +3
  Lines          1565       1572     +7
  Methods           0          0
  Messages          0          0
  Branches        288        283     -5
==========================================
+ Hits           1221       1224     +3
- Misses          252        255     +3
- Partials         92         93     +1

Powered by Codecov. Last update e7ebb05...a1dd221

Tests are passing, just need to improve coverage.


feat(words): add Miniconda Bpearl

https://github.com/autowarefoundation/autoware.universe/pull/5570

@Shin-kyoto could you review this?

To add context:
Bpearl: https://www.robosense.ai/en/rslidar/RS-Bpearl
Miniconda: https://docs.anaconda.com/free/miniconda/index.html


Theme: Update to crate-docs-theme>=0.37.0.dev0, introducing dark mode

About
Use the new theme that introduces dark mode. Thanks, @msbt.
Preview
https://cratedb-guide--136.org.readthedocs.build/
References

https://github.com/crate/crate-docs-theme/pull/546
https://github.com/crate/crate/pull/17001

crate-docs-theme 0.37.0 has been released.


No releases available for package "pecl.php.net/xdebug"

Info:

Docker version ($ docker --version):
➜  laradock git:(master) ✗ docker --version
Docker version 17.11.0-ce, build 1caf76c
Laradock commit ($ git rev-parse HEAD):
git rev-parse HEAD
ad3698670bd31528acdf5f125b39a78c24413c0e
System info (Mac, PC, Linux):
System info disto/version:
laradock git:(master) ✗ uname -a
Linux T410 4.10.0-40-generic #44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Issue:

Expected behavior:

Reproduce:

Relevant Code:
➜  laradock git:(master) ✗ docker-compose build php-fpm
Building php-fpm
[WARNING]: Empty continuation line found in:
    RUN if [ ${INSTALL_AEROSPIKE} = true ]; then     apt-get update -yqq &&     apt-get -y install sudo wget &&     curl -L -o /tmp/aerospike-client-php.tar.gz "https://github.com/aerospike/aerospike-client-php/archive/master.tar.gz"     && mkdir -p aerospike-client-php     && tar -C aerospike-client-php -zxvf /tmp/aerospike-client-php.tar.gz --strip 1     && (         cd aerospike-client-php/src         && phpize         && ./build.sh         && make install     )     && rm /tmp/aerospike-client-php.tar.gz ;fi
[WARNING]: Empty continuation line found in:
    RUN if [ ${INSTALL_MSSQL} = true ]; then     apt-get update -yqq && apt-get install -y apt-transport-https         && curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add -         && curl https://packages.microsoft.com/config/debian/8/prod.list > /etc/apt/sources.list.d/mssql-release.list         && apt-get update -yqq         && ACCEPT_EULA=Y apt-get install -y unixodbc unixodbc-dev libgss3 odbcinst msodbcsql locales         && echo "en_US.UTF-8 UTF-8" > /etc/locale.gen && locale-gen         && pecl install pdo_sqlsrv-4.1.8preview sqlsrv-4.1.8preview         && docker-php-ext-enable pdo_sqlsrv sqlsrv ;fi
[WARNING]: Empty continuation lines will become errors in a future release.
Step 1/62 : FROM laradock/php-fpm:2.0-71
 ---> b988e8cfee9a
Step 2/62 : MAINTAINER Mahmoud Zalt<EMAIL_ADDRESS> ---> Using cache
 ---> c37f2d2748a3
Step 3/62 : ARG INSTALL_SOAP=false
 ---> Using cache
 ---> 89a3f129d81a
Step 4/62 : RUN if [ ${INSTALL_SOAP} = true ]; then     apt-get update -yqq &&     apt-get -y install libxml2-dev php-soap &&     docker-php-ext-install soap ;fi
 ---> Using cache
 ---> 0a3d73abbc29
Step 5/62 : ARG INSTALL_PGSQL=false
 ---> Using cache
 ---> 7c23ef68f03f
Step 6/62 : RUN if [ ${INSTALL_PGSQL} = true ]; then     apt-get update -yqq &&     docker-php-ext-install pgsql ;fi
 ---> Using cache
 ---> 8972ab545335
Step 7/62 : ARG INSTALL_PG_CLIENT=false
 ---> Using cache
 ---> ed5c2a953c8e
Step 8/62 : RUN if [ ${INSTALL_PG_CLIENT} = true ]; then     apt-get update -yqq &&     apt-get install -y postgresql-client ;fi
 ---> Using cache
 ---> d879be2ff15f
Step 9/62 : ARG INSTALL_XDEBUG=false
 ---> Using cache
 ---> 87d2d3363ed4
Step 10/62 : RUN if [ ${INSTALL_XDEBUG} = true ]; then     pecl install xdebug &&     docker-php-ext-enable xdebug ;fi
 ---> Running in aedde74c8087
No releases available for package "pecl.php.net/xdebug"
install failed
ERROR: Service 'php-fpm' failed to build: The command '/bin/sh -c if [ ${INSTALL_XDEBUG} = true ]; then     pecl install xdebug &&     docker-php-ext-enable xdebug ;fi' returned a non-zero code: 1

➜  laradock git:(master) ✗ docker run -it laradock/php-fpm:2.0-71  /bin/bash
root@6853ecc37e55:/var/www/html# pecl install xdebug
No releases available for package "pecl.php.net/xdebug"
install failed
root@6853ecc37e55:/var/www/html#

I got the same errors. Any solutions?
---> Running in 2c241ea48d1f
No releases available for package "pecl.php.net/xdebug"
install failed
ERROR: Service 'php-fpm' failed to build: The command '/bin/sh -c if [ ${INSTALL_XDEBUG} = true ]; then     pecl install xdebug &&     docker-php-ext-enable xdebug ;fi' returned a non-zero code: 1

update: Seems it was network issue, I could install xdebug successfully via VPN

same issue here....................

The problem occurs when behind a proxy and is solved with the following modiffications
.env
Set the http_proxy in the .env file. Do not put any quotes around it
http_proxy=http://<IP_ADDRESS>:3128

docker-compose.yml
Add an arg http_proxy in every build that needs to connect to the internet (e.g. uses apt-get, pecl ...)
Note that arg http_proxy is in lowcase in order for apt-get to understand it
without any other modifications in the Dockerfiles
    php-fpm:
      build:
        context: ./php-fpm
        args:
          - http_proxy=${http_proxy}
          - PHP_VERSION=${PHP_VERSION}

php-fpm/Dockerfile ...
In all Dockerfiles that use pecl (e.g in php-fpm, php-worker, workspace, adminer)
before the first use of pecl put the following code
RUN if [ "${http_proxy}" != "" ]; then \
    # Needed for pecl to succeed
    pear config-set http_proxy ${http_proxy} \
;fi

In some occasions. May be a permission/configuration issue with pecl. (Temporary directory not accessible for writing) As it was in my occasion.

try run with sudo.

Hi  this issue has been automatically marked as stale  because it has not had recent activity . It will be closed if no further activity occurs. Thank you for your contributions .

:cry:

#2508
current version all fine.

Same here!
I got this error after run pcel install xdebug on my machine
No releases available for package "pecl.php.net/xdebug" install failed

Same here!
I got this error after run pcel install xdebug on my machine
No releases available for package "pecl.php.net/xdebug" install failed

sudo pcel install xdebug  worked for me

sudo pcel install xdebug worked for me

Worked for me too.. so weird.

This occurs before when you update the channel, example: pecl channel-update pecl.php.net

For me it was DNS issues with docker. I resolved this by adding
{ "dns": ["<IP_ADDRESS>", "<IP_ADDRESS>"] } (or any DNS of your choice) to /etc/docker/daemon.json on the host. If the json file does not exist yet,  you can create it.

like cache issue.
need run pecl channel-update pecl.php.net
try docker-compose build --no-cache --pull php-fpm

nothing is working

anyone was able to fix this?

Doing pecl channel-update pecl.php.net as suggested by @ivanferrer solved the problem for me

pecl channel-update pecl.php.net

this worked with me as well. thanks

Doing pecl channel-update pecl.php.net as suggested by @ivanferrer solved the problem for me

It worked

To me what solved was adding DNS values to docker settings:

update the docker to latest version.

You could also add "nameserver <IP_ADDRESS>" to the "/etc/resolve.conf" file.
Lease the 'nameserver <IP_ADDRESS>" as its first nameserver; this is so the docker hostnames are resolvable.
(and this solution doesn't require a reboot; just add the line, and try)

I solved it by updating the version of redis in the dockerfile to the latest one, as it seems to me that the problem is in the pecl repository

Looks like they're aware of the issue and working on fixing it.

{ "dns": ["<IP_ADDRESS>", "<IP_ADDRESS>"] }

This worked for me after everything failed. Thanks a lot.

The problem occurs when behind a proxy and is solved with the following modiffications
.env
Set the http_proxy in the .env file. Do not put any quotes around it
http_proxy=http://<IP_ADDRESS>:3128

docker-compose.yml
Add an arg http_proxy in every build that needs to connect to the internet (e.g. uses apt-get, pecl ...) Note that arg http_proxy is in lowcase in order for apt-get to understand it without any other modifications in the Dockerfiles Edit: You have to add an https_proxy arg in all builds that use curl
    php-fpm:
      build:
        context: ./php-fpm
        args:
          - http_proxy=${http_proxy}
          - https_proxy=${http_proxy}
          - PHP_VERSION=${PHP_VERSION}

php-fpm/Dockerfile ...
In all Dockerfiles that use pecl (e.g in php-fpm, php-worker, workspace, adminer) before the first use of pecl put the following code
RUN if [ "${http_proxy}" != "" ]; then \
    # Needed for pecl to succeed
    pear config-set http_proxy ${http_proxy} \
;fi

ARG http_proxy=""
RUN if [ "${http_proxy}" != "" ]; then \
    # Needed for pecl to succeed
    pear config-set http_proxy ${http_proxy} \
;fi

change code:
pecl install xdebug-2.5.5; \

to
#      pecl install xdebug-2.5.5; \
      pecl install http://pecl.php.net/get/xdebug-2.5.5.tgz; \

It's works!!!

change code:
pecl install xdebug-2.5.5; \

to
#      pecl install xdebug-2.5.5; \
      pecl install http://pecl.php.net/get/xdebug-2.5.5.tgz; \

It's works!!!

Thanks man, this is the only solution that worked for me.


[Chore] Putting ENV file to another place

Codecov Report
Base: 99.18% // Head: 99.18% // No change to project coverage :thumbsup:

Coverage data is based on head (ced6fe6) compared to base (6fa7ace).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##               main      #28   +/-   ##
=========================================
  Coverage     99.18%   99.18%
  Complexity      224      224
=========================================
  Files            83       83
  Lines           612      612
=========================================
  Hits            607      607
  Misses            5        5

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add Hizicbold's file

created a branch, created a file and made a commit, and opened a pull request

good job


Include HTTP headers in the GET request for asset definition file

The headers:

curl -H "Accept: text/xml; charset=UTF-8" -H "IF-Modified-Since: Mon, 02 Jul 2018 13:23:00 GMT" -H "X-Client-Name: AlphaWallet" -H "X-Client-Version: 1.0.3" -H "X-Platform-Name: iOS" -H "X-Platform-Version: 11.1.2" https://repo.awallet.io/0xd8e5f58de3933e1e35f9c65eb72cb188674624f3

Accept — "text/xml; charset=UTF-8"
X-Client-Name — "AlphaWallet"
X-Client-Version — the app version number
X-Platform-Name — "iOS" or "Android"
X-Platform-Version - OS version number
and
IF-Modified-Since — timestamp the file was last saved. Only include if the file is already cached

Should also check for the HTTP status code 304 (if and when the repo supports it) which means the content is unchanged and the body will not be in the response

Let's also standardize standardise the app version number format for iOS and Android. Maybe not as far as applying https://semver.org (though would be good, but maybe later), but at least we can agree that it's in the format x.y(.z)?? e.g. 1.2, 1.2.3, 2.0 but not 1. Helps with parsing on the server side for the short term.

Fixed in PR #399


[DOCS]

Description
I want to add instructions on using Github Desktop for contributing to this repository which makes it easy as well as simple for beginners to contribute. Please assign me this issue under GSSOC'24.
Screenshots
No response

@Priyanshu2631 Thank you for providing your insight but it is not required as of now


Please elevate this note to a large warning towards the top across RBAC + Key Vault + App Service documentation

https://docs.microsoft.com/en-us/azure/key-vault/general/rbac-migration

ⓘ Note
Azure App Service certificate configuration does not support Key Vault RBAC permission model.

I have been under the assumption I was missing some key piece of the RBAC flow, because I wasn't migrating to RBAC but creating a new Key Vault with RBAC. This note isn't present anywhere in normal RBAC, Key Vault or App Service docs that I could find.

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

ID: 9fe2188c-d08d-be91-bf80-9665cac23596
Version Independent ID: e0cf82de-bdf5-97a4-f9e0-f40e8c12b064
Content: Migrate to Azure role-based access control
Content Source: articles/key-vault/general/rbac-migration.md
Service: key-vault
Sub-service: general
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@johnrom
Thanks for your feedback! We will investigate and update as appropriate.

@johnrom
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@johnrom we have added this note to our RBAC guide :
https://docs.microsoft.com/en-us/azure/key-vault/general/rbac-guide

#please-close

Thanks!


[ Bug ] Album still showing in Downloads after deleting all songs

I wanted to remove an album from my offline downloads, and couldn't find an easy way to do it except deleting every downloaded song in the album. But the album is still showing, even though it's empty. :sweat_smile:
After optimizing local storage, by deleting all downloaded albums and songs, it removed it.

yeah this is somewhat annoying. this should be a feature ("remove downloads" in album) to fix this bug lol gonna make it in 1.5


Poll a specific job number

Since this plugin always checks ${jobName}/lastBuild for the status, if another build starts before the one we triggered finishes, we'll end up polling that one for status instead. This waits 10 seconds after triggering a build, then grabs the build number of the most recent build, and polls that for status.

@cccCody Please resolve the conflicts.

Please see https://github.com/estherk0/jenkins-trigger/pull/8 first before acting on this one

#8 seems to be a better solution. I'll close this.


Release 5.0.5...5.1.0 Call to a member function process() on null

Release 5.1.0 seems to break things for us.

Call to a member function process() on null

  Type: Error
  File: Data/Temporary/Production/Cache/Code/Flow_Object_Classes/Flowpack_ElasticSe
        arch_Domain_Model_Index.php
  Line: 209

Seems DynamicIndexSettingService is not yet available during injectSettings()?
Non-breaking but IMHO the default value for CURLOPT_SSL_VERIFYHOST should be set to 2.  curl_setopt_array(): CURLOPT_SSL_VERIFYHOST no longer accepts the value 1, value 2 will be used instead (see https://www.php.net/manual/en/function.curl-setopt.php)

Same issue here with 5.1.1 when calling ./flow node:repair
./flow node:repair
Run checks for basic node integrity in the content repository

Checking for nodes with abstract or undefined node types ...
Checking for orphan nodes ...
Checking for disallowed child nodes ...
Checking for undefined properties ...
Checking for broken entity references ...
Checking for nodes with invalid dimensions ...
Checking for nodes with invalid workspace ...
Checking for nodes with inconsistent identifier ...
Checking for missing child nodes ...
 ❱ Add node dad9deb8-f493-5f14-0cc6-34c8180b8480 named "autoshortcuts" in "/sites/internezzo-site"
    applied ✔
Created 1 new child nodes
Call to a member function process() on null

  Type: Error
  File: Data/Temporary/Development/SubContextDdev/Cache/Code/Flow_Object_Classes/Fl
        owpack_ElasticSearch_Domain_Model_Index.php
  Line: 209

The commit that leads to the error seams to be b8a4f9ceee1d6ae2f44a9cf79262f68c008e5aa8.
In my opionen the problem is that when calling the getSettings() function the needed class DynamicIndexSettingService isn't injected yet.

@simonhir this is exactly the issue.  Because when Flow compiles it generates this method
    private function Flow_Proxy_injectProperties()
    {
        $this->injectSettings(\Neos\Flow\Core\Bootstrap::$staticObjectManager->get(\Neos\Flow\Configuration\ConfigurationManager::class)->getConfiguration('Settings', 'Flowpack.ElasticSearch'));
        $this->Flow_Proxy_LazyPropertyInjection('Flowpack\ElasticSearch\Service\DynamicIndexSettingService', 'Flowpack\ElasticSearch\Service\DynamicIndexSettingService', 'dynamicIndexSettingService', 'a084c9e1cc42f5f542a97a68fba74866', function() { return \Neos\Flow\Core\Bootstrap::$staticObjectManager->get('Flowpack\ElasticSearch\Service\DynamicIndexSettingService'); });
        $this->Flow_Injected_Properties = array (
  0 => 'settings',
  1 => 'dynamicIndexSettingService',
);
    }

and when
$this->injectSettings is called the $this->Flow_Proxy_LazyPropertyInjection is not called yet, thus $this->dynamicIndexSettingService is null at the moment in  protected function getSettings()

I wonder why there is not a lot of traffic about this ticket, we are hidden quite hard by this issue, every Neos and Flow installation who did a composer update in the last 2 weeks was broker afterwards, sometimes not easy to spot the problem. I assumed everybody to be affected by this bug, but maybe I am mistaken.
Anyway, if there is someone to fix it, I would appreciate and I can offer some budget for it.

The problem is that injectSettings calls getSettings() here.


First batch of translations

Translated:

404_it.json
bank-runs_it.json
bitcoin-vs-cbdc_it.json
bitcoin-vs-gold_it.json

Ok thanks for the hints! I'll prioritize those 2 files then 👍


remove id from fill() to prevent postgres error

fixes https://github.com/statamic/eloquent-driver/issues/67

@helloiamlukas can you please resolve the merge issues?

FYI currently this reverts the fix from #19. If you were to import entries, they'd lose their existing IDs.
I'll update this PR appropriately.


Update image text retrieval data preprocessing

PR types

PR changes

Description

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Use PP constants

We've noticed differences at >1e-4 between PP constants (currently implemented in CCL), CLASS constants and GSL constants. (G is one example.) We have agreed the best is to use PP constants and we need to contact the CLASS developers to ask them to incorporate these as well if possible.

I ran comparisons between the constants in CCL and some other sources. The results are attached.

I submitted a PR where Msun is fixed to be the GSL value and rho_crit is derived.

This is a great analysis, @matthewkirby. Thanks for doing this.

By the way, @matthewkirby make sure you cross-link the issue like so: #241 when you issue the PR, so it's slightly easier to locate the issue.


[RU] Add prep "[в|на]" to  parts

You should put all this similar changes in one pull-request. Moreover, I examined sentences in more details. This prep are already placed in _common.yaml, so I should to remove them from other files entirely.
  area: "[в|на] {area}"

understood, missed info regarding _common.yaml file.


Handle workspace exceptions properly in get_workspaces

Coverage increased (+0.009%) to 97.905% when pulling b54d46066d383f5d17395fd1b5ff504b5e54fdca on MrCreosote:master into a6d0ace042fcbc18980e86e726202a8349248c13 on kbaseIncubator:master.