Tabbed Layout forId problem

Make sure to check the demo app(s) for sample usage
Demo app works
If the demo apps cannot help and there is no issue for your problem, tell us.
I see the message on console

Please make sure forId="" resolves to a visible view, or the toolbar won't render correctly! Example:

When it does, the keyboard toolbar does not show no matter how many times I click it the triggering textfield. Then I click the Home button (Android) and click the overview button to go back to the app, then the textfield triggers the keyboardtoolbar and everything works fine!
1 out of 10 times the message does not appear and everything works fine on multiple tabs. Sometimes it only affects some of the keyboardtoolbars.
Which platform(s) does your issue occur on?

Android / Not checked iOS

Please, provide the following version numbers that your issue occurs with:

CLI: 6.0.2
Runtime(s):
"tns-android": {
"version": "6.0.0"
},
"tns-ios": {
"version": "6.0.1"
}
Plugin(s):
"dependencies": {
"@angular/animations": "8.0.0",
"@angular/common": "8.0.0",
"@angular/compiler": "8.0.0",
"@angular/core": "8.0.0",
"@angular/forms": "8.0.0",
"@angular/http": "^8.0.0-beta.10",
"@angular/platform-browser": "8.0.0",
"@angular/platform-browser-dynamic": "8.0.0",
"@angular/router": "8.0.0",
"@nstudio/nativescript-pulltorefresh": "^1.0.1",
"@types/node": "^11.13.18",
"crypto-js": "^3.1.9-1",
"email-validator": "^2.0.4",
"moment": "^2.24.0",
"nativescript-angular": "8.0.2",
"nativescript-background-http": "^3.4.1",
"nativescript-barcodescanner": "^3.2.1",
"nativescript-camera": "^4.5.0",
"nativescript-carousel": "^6.1.0",
"nativescript-contacts": "^1.6.2",
"nativescript-crossplatform-aes": "^1.0.3",
"nativescript-downloader": "^2.1.4",
"nativescript-feedback": "^1.3.10",
"nativescript-filter-select": "^1.3.0",
"nativescript-imagecropper": "^1.0.6",
"nativescript-keyboard-toolbar": "^1.0.4",
"nativescript-loading-indicator": "^2.5.2",
"nativescript-local-notifications": "^4.0.1",
"nativescript-localstorage": "^2.0.0",
"nativescript-modal-datetimepicker": "^1.2.0",
"nativescript-permissions": "^1.3.6",
"nativescript-phone": "^1.4.0",
"nativescript-ripple": "^2.2.1",
"nativescript-social-share": "^1.5.2",
"nativescript-theme-core": "~1.0.4",
"nativescript-ui-chart": "5.0.0",
"nativescript-ui-dataform": "5.0.0",
"nativescript-ui-listview": "7.0.0",
"nativescript-web-image-cache": "^5.0.0",
"reflect-metadata": "~0.1.12",
"rxjs": "~6.3.0",
"tns-core-modules": "~6.0.1",
"uglifyjs-webpack-plugin": "^2.1.3",
"webpack-bundle-analyzer": "^3.3.2",
"xmldom": "^0.1.27",
"xpath": "0.0.27",
"zone.js": "0.9.1"
},
"devDependencies": {
"@angular/compiler-cli": "8.0.0",
"@nativescript/schematics": "~0.5.0",
"@ngtools/webpack": "8.0.0",
"node-sass": "4.12.0",
"nativescript-dev-webpack": "^1.0.1",
"tns-platform-declarations": "6.0.1",
"typescript": "3.4.5"
},

Please, tell us how to recreate the issue in as much detail as possible.
I tried to recreate the issue using an empty tabbed layout and multiple keyboardtoolbars. the issue did not reoccur. I think it might be related to loading times of the tab contents.
Is there any code involved?
I used the sample code, not much of extras:
           <TextField #tfFilterTask id="tf2" row="1" col="0" style="placeholder-color: rgba(255,255,255,0.6)"
                       class="c-white m-l-5" hint="Kod veya isim..." [text]=filterTaskText
                       (textChange)="onFilterChange($event)"></TextField>

    <KeyboardToolbar2 forId="tf2" height="50">
        <GridLayout columns="auto, *,auto,auto, auto" class="c-white p-10" backgroundColor="#26252A">

        </GridLayout>
    </KeyboardToolbar2>

Thank you for this great plugin, I hope we can solve this issue as I'd really like to use it.

Hi @EddyVerbruggen ,
I think it might be related to this issue  androidTabsPosition="bottom" androidOffscreenTabLimit="0" with the tabview. When androidTabsPosition is set to bottom, androidOffscreenTabLimit="0" is ommited and tabview tries to preload the next tab. As the next tab is not in the frame, it gives this above message, and the triggering textfield does not get binded.
Would be glad if there were a workaround for this. maybe by bypassing a page id, rather than this below in nativescript-keyboard-toolbar\keyboard-toolbar.android.js line 21
 _this.thePage = frame_1.topmost().currentPage;
What do you think?

Hi @comporell, would you mind sharing a repo (or Playground) that shows the problematic behavior? I'm sure we can think of a way to fix it once the problem is clearly demonstrated.

Hi @comporell, would you mind sharing a repo (or Playground) that shows the problematic behavior? I'm sure we can think of a way to fix it once the problem is clearly demonstrated.

Dear Eddy. Playground is a pain to work with, I'm attaching an example project.
tabbedKeyboardTest.zip

Thanks for the project!
Indeed the issue was with preloading of tabs on Android. I had to add some code specific to this TabView case to make it work.

@comporell Can you give 1.1.0 a go?


[csrng/dv] Update testplan/checklist, add coverage

Updates for CSRNG V2 review.
Signed-off-by: Steve Nelson<EMAIL_ADDRESS>

@weicaiyang this PR is similar to the one you just approved for edn PR #11552. Should I remove the checklist from this one too? Then you'll approve?

@weicaiyang this PR is similar to the one you just approved for edn PR #11552. Should I remove the checklist from this one too? Then you'll approve?

yes, please split the checklist update into another PR. Then we can merge this one. Thanks

Checklist removed


backwards of autograd functions

#661 allows us to trace through torch.autograd.Function .apply using the forward, but so far we ignore the backward (and emit a warning). It would be neat to fix this and also trace the backward / use it in a grad_transform or so.

triage review:

Currently we can drop some custom autograd handling on the floor
We should do this properly but needs some proper design or discussion
Can we run these as a black box through torch instead of understanding them?
We don't run jit during backward right now... when do we want to acquire backward?

Closing this duplicate in favor of https://github.com/Lightning-AI/lightning-thunder/issues/1017.


fix: create new section for anvil apps in workspace

Description

This PR separates applications into Anvil and non-Anvil applications

Fixes #34169
Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true


⚠ Slack has degraded performance

In d89fd77, Slack (https://status.slack.com/api/v2.0.0/current) experienced degraded performance:

HTTP code: 200
Response time: 61 ms

Resolved: Slack performance has improved in 7016f97.


Refactor so that testdata samples are in their own namespace

Related to #75
This was particularly nice as we were able to move tests into their own namespace.
We may move bincapz.go to pkg/bincapz, but I'm not sure yet.

need a rebase


feature request: add support for detecting Enterprise Mode

You should be able to do something like this:
if (IE.TrueVersion < 9 && ('spellcheck' in document.createElement('textarea')) {
    // enterprise mode is on!
}

I'll look into this.


5 middleware configuration

Implementation proposal for https://github.com/biscuit-auth/biscuit-actix-middleware/issues/5.
As discussed with @divarvel, token parsing feature is no more mandatory. Consequently, this PR add following configuration:

Error handling
Token extraction
Public key selection/rotation management

At the moment of writing, the biscuit-auth dependency points to a branch of my fork. If my proposal is validated, we have to merge my branch to biscuit-auth repo, then update cargo.toml  before merging the PR.

Neat! Could the example showcase key selection as well?


Kong support

As a user I want to use Kong gateway instead of EnvoyFleet
This opens up several questions as follows:

[ ] - In this scenario should Kong be a prerequisite or should be install Kong operator when such API is created
a. we could trigger kong operator installation
b. validation webhook could prompt users to do this

[ ] how to translate x-kusk extensions into KongIngress

[ ] Kong supports mocking out of the box. We need to translate Open API examples into Kong readable configuration https://docs.konghq.com/hub/kong-inc/mocking/

Perhaps we can start with the  scenario where Kong already exists in your cluster (which to me seems more likely than that you would explicitly want to use Kong instead of Envoy) - our installer could detect this and ask if the user wants to use Kong or Envoy?

Installer option seems to be simple way to solve this. With the mutating webhook we add envoyfleet if such is missing I thought that we could also detect whether EnvoyFleet or Kong exist in the cluster and then install accordingly.
For example:
apiVersion: gateway.kusk.io/v1alpha1
kind: API
metadata:
  name: hello-world
spec:
  gateway:
    type: EnvoyFleet
    name: kusk-gateway-envoy-fleet
    namespace: kusk-system

we could detect and install such envoy fleet if not installed. Something similar could be done for Kong:
apiVersion: gateway.kusk.io/v1alpha1
kind: API
metadata:
  name: hello-world
spec:
  gateway:
    type: Kong
    name: kusk-gateway-kong
    namespace: kusk-system

This would trigger installation of Kong cluster CRD and would configure KongIngress CRD accordingly and whatnot. Or if Kong CRD is missing, therefore Kong Operator is not installed we could trigger Kong Operator installation. Perhaps such approach could be too invasive.

For now, we're not going to support other Gateway APIs, so let's open this up in the future if we see fit.


Added Errorhandler & Logger

This PR solves #8
Parent Issue : #1
Tasks Handled in this PR

[x] Created an instance from the node Error class, to create custom error objects.
[x] Marked operational and programming errors.
[x] Created an error controller function to handle errors from the custom error object.
[x] User the express "out of the box" error handler to handle global errors by passing the error controller as a middleware.
[x] Installed winston and morgan to set up proper error logging and http logs.

looks great, boss


Pod goes into CrashLoopBackoff repeatedly

Installing deis-router through the deis helm chart leaves me with deis-router continually flapping:
$ kubectl get pods
NAME                        READY     STATUS              RESTARTS   AGE
deis-builder-lknfs          0/1       CrashLoopBackOff    16         1h
deis-database-yxntz         1/1       Running             0          1h
deis-etcd-1-ekw9s           1/1       Running             0          1h
deis-etcd-1-hrqyk           1/1       Running             0          1h
deis-etcd-1-pd1mu           1/1       Running             1          1h
deis-etcd-discovery-vqlzu   1/1       Running             0          1h
deis-minio-fsmqx            0/1       RunContainerError   0          1h
deis-registry-rarvy         1/1       Running             0          1h
deis-router-2iwxb           0/1       CrashLoopBackOff    15         1h
deis-workflow-tr7eb         1/1       Running             1          1h

noticed this too, but it's intermittent between helm installs. Possibly etcd related? Although I haven't seen any consistent etcd behaviors that could cause

So far deis-router has consistently failed for me, and etcd is happy and healthy. There's no Service defined for deis-router, and the ReplicationController doesn't show any valuable info, but if anyone knows where I could get relevant failure logs, I'll post them here.

@mboersma I'll look into this.  fwiw, router doesn't use etcd at all, so the problem definitely isn't there.

The problem is here:
https://github.com/deis/router/blob/master/model/model.go#L227-L236
This is me trying to determine whether a service actually has any pods backing it ATM.  If not, router returns a 503 when requests for the corresponding app are received.
I can try to figure out why this is failing, or alternatively, we can drop this behavior and and just accept whatever happens when you route a request to a service that has nothing backing it.  I wouldn't be surprised if it gives a 503 anyway.
The only reason I was attempting this check to begin with was that v1.x was doing something similar.  It might not be strictly necessary.

@krancour I'm in favor of omitting this check and letting it go through, as pods / RCs may come and go during the lifetime of the router in the k8s world

accept whatever happens when you route a request to a service that has nothing backing it

If that's a 503 or other appropriate error, then +1 for removing our check code and letting k8s do the failing.

The router is constantly checking whether annotations have changed or if any annotated service has no endpoints.  So the fact that things can change is accounted for.
I just tested this... sort of:
[kent@mbp router]$ k exec -it deis-router-vt9u6 -- bash
bash-4.3# wget http://<IP_ADDRESS>:80
Connecting to <IP_ADDRESS>:80 (<IP_ADDRESS>:80)
wget: error getting response: Connection reset by peer

Can't say I'd be satisfied with that.  A 503 makes more sense.

Ok... testing more thoroughly... if I drop this feature of detecting when there are no backend endpoints, and the router sends traffic to the app in question, nginx returns a 502 to the end user.
@mboersma @arschles would you consider that acceptable?

ah, right. I missed that it was constantly checking. yes, a 502 is acceptable. maybe create a ticket to investigate a better solution post-alpha?

maybe create a ticket to investigate a better solution post-alpha?

If we think that returning a 502 instead of a 503 is fine, I would just leave it at that.  If we still feel we need a "better solution post-alpha," then it's probably better for me to just fix the array index out of bounds right now.

k. I don't think we necessarily need a better solution post-alpha, I assumed the code block that you linked just needed a different way to poll the k8s api though, that's why I suggested the investigatory ticket.

502 seems like an appropriate HTTP response here, so :+1:.


Generate statecode enum?

Hi,
The generated classes doesn't contains statecode enum like the early bound generator.
Is there any reason why?

Hi, there is no reason, I am working on this feature


Type still needed when using $ref inside definitions

If i want to reference another definition from inside a definition, I used to be able to have this:
"app_id": {
"$ref": "/schemata/app/definitions/identity"
}
But now prmd complains:
failed schema #/definitions/resource/dependencies/properties/definitions/additionalProperties: No subschema in "anyOf" matched.
If I add "type" then the error goes away:
"app_id": {
"type": "string",
"$ref": "/schemata/app/definitions/identity"
}
which seems a bit redundant. Shouldn't it be able to get the type from de-referencing?
Edit: Also, it now complains that "description" isn't there. I can live with that, as I would usually want to write a description locally, e.g. "id of the app associated with this user". But it should be able to pick up the description from the referenced definition

Hmm, it seems like we must have broken something here around the time of that release (which may relate to your other issue as well). I'll have to dig deeper. Do you have a smallish schemata you could share as a repro case to help me pin down the issue? Thanks!

Here is a new schema I made to show the issue. I created it by doing prmd init for 'app' and 'user', and combining. All that was added was the app_id definition and property on user.
https://gist.github.com/mcclymont/30798548c0688755ad40

Last working version for me was 0.6.2. Upgrading to 0.7.0 shows the error

Ah. I think the key difference is that in 0.6.2 when you prmd combine, it sets the top level $schema value as "http://json-schema.org/draft-04/hyper-schema" but in 0.7.0 it sets it as "http://interagent.github.io/interagent-hyper-schema".
Since I use a script that does combine, then verify, then render and it was failing on the verify step, I thought the bug was in the verify step and something to do with that had changed between 0.6.2 and 0.7.0. So it turns out that maybe my schemas weren't really meant to be verifying all along?
I am using stuff like leaving out type (because it should come from the reference), using oneOf inside of definitions etc. and that all worked before because it was only getting verified against the json-schema.org spec.
To help me understand a bit better - does (or should) the dereferencing happen before verification against the interagent schema?

I think dereferencing should probably proceed verification? I've just released 0.9.0 which has some fixes, but it didn't look like it helped against your minimal schema at least. That said, could you double check and see if it helps you out?

0.9.0 is not on rubygems.org yet, but I tried with the latest commit https://github.com/interagent/prmd/commit/8209a2a2e552466779b5825e10d542b93f11a8da and it had the same error.
We have ended up doing the following so we can build and verify our schema again:
bundle exec prmd combine --meta meta.json schemata/ | \
  sed 's,http://interagent.github.io/interagent-hyper-schema,http://json-schema.org/draft-04/hyper-schema,g' \
  > schema.json

Oops. I just pushed 0.9.0, thought the rake task I have did that automatically...
Thanks for the update. I suspect it may be that our interagent schema has some overly-strict stuff going on there (or verification is overly strict). I'll try to poke around some more, glad to hear you have a workaround in the mean time though.

Glad you have a workaround at least, I think your expectations are things we would (ideally) meet, but sounds like we aren't there presently. Would be great to fix, but I fear not something I have bandwidth for presently, certainly happy to help how I can if you want to take a stab though.


Let Approx::epsilon also take float

Description

Approx::Approx and its comparison operators can now take  float
Adding this feature to Approx::epsilon would improve consistency and code

Somehow related to #873
Extra information

Catch version: v1.9.1 (Generated: 2017-04-09 21:21:06.285364)

I spent some time thinking about this, then suddenly got really busy and couldn't respond.
The reason why this wasn't a no-brainer change was that it isn't quite so simple as to add a float overload for the function, because that would trigger compile-time error for code like Approx(2).margin(2). The solution that we are using is to add a templated overload, that uses SFINAE to only work with types that can be converted to double.
Now, for Approx::margin this isn't semantically problematic, as Approx(temperature(72)).margin(temperature(2)), makes perfect sense.  However for Approx::epsilon and the situation is not quite so clear-cut, as Approx(temperature(72)).epsilon(temperature(0.001)) does not make semantical sense.
This could be solved in two ways.

Specifically make Approx::epsilon only accept floating point types (using std::is_floating_point).
Damn the semantics, make Approx::epsilon accept anything.
Personally I like the second option better.

There is also Approx::scale, but I don't think anybody is actually using that one.

After discussion with Phil, I decided to go with option 2.


getstarted does not work for newer browser version

BigchainDB version: v1.1
Operating System: Ubuntu
Deployment Type: IPDB

network type: test
URL: https://www.bigchaindb.com/getstarted/

BigchainDB driver: no

Description
Getting started page does not work for Chrome browser versions >61.x latest browser versions does not set http_referer to bigchaindb.com as is expected by the backend server and as a result nginx refuses the request.
Steps to Reproduce
update to a chrome version > 61.x and try https://www.bigchaindb.com/getstarted/

As discussed with @jernejpregelj , we can try moving the OPTIONS request before we check for the PROXY_EXPECTED_REFERER/ORIGIN_HEADER i.e. change
      # check if the request originated from the required web page
      # use referer header.
      if ($http_referer !~ "PROXY_EXPECTED_REFERER_HEADER" ) {
        return 403 'Unknown referer';
      }

      # check if the request has the expected origin header
      if ($http_origin !~ "PROXY_EXPECTED_ORIGIN_HEADER" ) {
        return 403 'Unknown origin';
      }

      if ($request_method = 'OPTIONS') {
        add_header 'Access-Control-Allow-Origin' '*';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range,app_key,app_id';
        add_header 'Access-Control-Max-Age' 43200;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
      }

To something like this:
      if ($request_method = 'OPTIONS') {
        add_header 'Access-Control-Allow-Origin' '*';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range,app_key,app_id';
        add_header 'Access-Control-Max-Age' 43200;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
      }

      # check if the request originated from the required web page
      # use referer header.
      if ($http_referer !~ "PROXY_EXPECTED_REFERER_HEADER" ) {
        return 403 'Unknown referer';
      }

      # check if the request has the expected origin header
      if ($http_origin !~ "PROXY_EXPECTED_ORIGIN_HEADER" ) {
        return 403 'Unknown origin';
      }

@jernejpregelj @muawiakh  I think the best solution would be to set the Referrer-Policy on the client side to origin-when-cross-origin. Since that the only change is see form current workflow that the browser now just expect the client application to configure a referrer policy from one of the options available here instead of just adding the referrer by default

So, will you be taking care of it? Or reassign to @kremalicious ?

@muawiakh reassigning

@kremalicious since you were away when we created this let me know if you need to discuss it offline

@shahbazn @muawiakh Referrer-Policy cannot be set in all browsers for CORS preflight (OPTIONS) request. I think the best way is to check origin instead of referrer header or move referrer check after options.


types(runtime-core): provide valid type for default $emit

relates to https://github.com/vuejs/vue-test-utils-next/issues/144
When using ComponentPublicApi the emit type defaults to an empty object, making the $emit to be unknown type instead of the default emit function (event: string, ...args: any[]) => void

This change seems to have broken vue-class-component.
Cc: @ktsn

@sodatea Thank you :)
There's the fix: https://github.com/vuejs/vue-next/pull/1584


feat(module:table): support table expand feature

close #185
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Coverage increased (+0.09%) to 41.237% when pulling 4ab513b0fa4472c17af538202988895ed3c7146a on vthinkxie:feat-table-expandable-row into cd5b511828d4391d21953bee05e2297ae016a5e8 on NG-ZORRO:master.

Coverage increased (+0.09%) to 41.237% when pulling 4ab513b0fa4472c17af538202988895ed3c7146a on vthinkxie:feat-table-expandable-row into cd5b511828d4391d21953bee05e2297ae016a5e8 on NG-ZORRO:master.

Coverage increased (+0.09%) to 41.237% when pulling 68c5d489aea041de3a8848b41483e0f278bb1453 on vthinkxie:feat-table-expandable-row into cd5b511828d4391d21953bee05e2297ae016a5e8 on NG-ZORRO:master.


Issue in installing plugin, name not listed under plugins when starting kibana

Hi,
I've upgraded my Kibana to 8.9.2, older enhanced-table is broken.
So I'm trying to install the correct version, but failing to do so.
Steps I'm following:

systemctl stop kibana
rm -rf optimize folder
from kibana home folder: ./bin/kibana-plugin install https://github.com/fbaligand/kibana-enhanced-table/releases/download/v1.13.4/enhanced-table-1.13.4_8.9.2.zip
Installs successfully
systemctl start kibana -> enhancedTable is not listed in plugins list
Cache for forever is deleted
Hard refresh for the Kibana UI
Error as seen in screenshot

Any help is much appreciated.

Hi,
Well, I just tried to install plugin v1.14.0 on Kibana 8.9.0 (I had this Kibana version on my computer). And it works fine.
Some advices:

first, don't delete "optimize" folder. Since Kibana 7.9, it is not necessary and especially not useful. Maybe it can cause some errors.
then use the very last plugin version (v1.14.0). So I invite you to install this package:
https://github.com/fbaligand/kibana-enhanced-table/releases/download/v1.14.0/enhanced-table-1.14.0_8.9.2.zip


:bug: Fix: Procedures imports

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

#1202  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on  Graphite


Do not provide a default JMIG_DATA_URL

Originally JMIG_DATA was a URL, which I changed to also accept a local path. Now it's either JMIG_DATA_URL or JMIG_DATA, so we can't have a default URL or JMIG_DATA is never used.

Actually now that data_directory is part of the corpus model it has to be a directory so we cannot (ab)use it for the data source.


Integrate selinux file label

add method and test case to retrieve the selinux security context/label from a file by stat, for i.e.
describe file('/usr/bin/docker') do
  its(:selinux_label) { should match /docker_exec_t/ }
end

Thanks!

Released as v2.25.0.


Pull request title is always "is"

No matter if I set the PR title myself or let it be the default (which should be the update container string), the title is always "is".

I think it's likely there are missing quotes, the default does work, and see the pull requests here. Could you share your workflow file?

I just added quotes, could you look in your action and see what it's echoing for the data? Should coincide with this line:
echo "curl --user ${GITHUB_ACTOR} -X POST --data ${DATA} ${PULLS_URL}"

See https://github.com/vsoch/pull-request-action/issues/7, this has been fixed.


Only flood images if relative change in precipitation is above a certain threshold (60%)

For now, we are only going to apply the generative model to the image if the relative change in precipitation that is expected in 2050 is above 60%.

I don't think this is scientifically correct thing to do, we should discuss the idea and also, why 30% ?

Speaking with Ata, he just let me know that we're bumping this to 60% as a result of some analysis he did regarding the relative change in precipitation levels observed after recent flooding in Quebec.

Also, according to Ata, if any of the immediately adjacent grid items are above the flood threshold, flood it.

ok, cool, let's keep it 60% for now, until we get new info

From a discussion with @notoraptor about how the API and UI should handle this:


Xiaomi Mi Smart Pedestal Fan 2S issue

Xiaomi Mi Smart Pedestal Fan 2S does not work with this adapter. Adapter cannot find a device

Xiaomi Mi Smart Pedestal Fan 2S does not work with this adapter. Adapter cannot find a device

Has this issue been solved?


onSelect(Start)

Is your feature request related to a problem? Please describe.
For some applications, it would be great to have an event when the user picked the start date (single mode disabled) of a date range.
Describe the solution you'd like
An event for the selection of the start date (single mode disabled). Alternatively, the existing onSelect event is called when the start date is selected (but with end date parameter null/false) and then again when the selection of the range is completed.
Describe alternatives you've considered
I don't think there is an alternative to this. :/
Edit: It also seems that the onDayHover event doesn't fire when clicking a day element (though it is stated in documentation),
but only when also hovering the item (and moving the mouse around while over the element).

This would be very useful. I have spent a lot of time trying to use onDayHover, but it doesn't fire on click in Safari (but does in Chrome). My use case is to set a header based on whether it is the start or end date which is being selected. I also want to be able to default the end date to the start date, if only one date is selected.
I would be happy to have an option to trigger onSelect on each date selection, and then it would be up to the onSelect function to check if both dates are available.

@pgmahoney: Currently I use a workaround where the DOM element of clicked/touched day element is inspected (event listener).

This would be an excellent feature to have.
I think ideally, onSelect should return null/false/undefined/whatever when the end date has not been picked yet, have have the event fire whenever date is selected

@wakirin: 🙏

I have a case where I need to set the minDays option depending on the start date (high-season 14 days or low-season 7 days). So having the onSelect also fire when start date is selected would be nice. Or add events onSelectStart and onSelectEnd.

https://wakirin.github.io/Litepicker/docs/events#preselect
@RVXD
I think in your case is better to use https://wakirin.github.io/Litepicker/docs/options#lockdaysfilter-200

https://wakirin.github.io/Litepicker/docs/events#preselect
@RVXD
I think in your case is better to use https://wakirin.github.io/Litepicker/docs/options#lockdaysfilter-200


Type erasure

Hi, this seems a fantastic and well fleshed out library!
One concern I have is that StateConnectionViewGuard is type erasing the view hierarchy with AnyView, which is far as I understand removes the optimizations SwiftUI applies when rendering.
As this is applied on any use of connect() it basically affects the whole tree when used.

Thanks for pointing that out. That definitely needs to be changed.

This should be fixed in v0.11.1.


net::ERR_CONNECTION_RESET on windows 7

On my windows 7 x64, I got net::ERR_CONNECTION_RESET error when I want to update vscode.

VSCode Version: 1.32.3
OS Version: windows 7 x64

So I want to known which resources vscode is needed when it update ?

These are the resources: https://code.visualstudio.com/docs/setup/network#_common-hostnames


updating carousel  to auto-silde

Is your feature request related to a problem? Please describe.
The carousel implemented for the website is static
Describe the solution you'd like
I want to make it auto-sliding
Describe alternatives you've considered
Additional context

Go on,
you have one week for it.


refactor matchmaker process

This refactor attempts to split the Matchmaker process method up into smaller methods of related functionality.  My understanding of the logic is roughly:

Iterate over active items in random order
Build a Bluge search which finds all other items which match what this item is looking for
Execute the search
Skip over some Bluge results at this point

Matches itself
Matches other people already in party, etc

Each match now either becomes part of an existing combination, or the start of a new combination
This resulting combination is given a final check as follows:

Final size equals max count or this is the last iteration and the final size is > min count
Resulting final size satisfies each members desired min count

If a match has been found, the internal state is updated such that subsequent matches cannot be made against the already matched items.
Main loop continues to find/build matches for subsequent active items

This refactor is still not perfect, but it brings the main process function under 100 lines.  Note, the helper methods which operate with the lock held have the suffix LOCKED.
Whether or no we want to merge this refactor is a separate issue, it was mostly a way for me to try to test my understanding of the code.
On the topic of ensuring mutual matches, it would seem that the correct place to add this check would be in "skip over some bluge results" phase.  At this point, if we had an efficient way to check that the search hit's query also matches the outer for-loop's hit, we could detect and eliminate non-mutual matches at this phase.  And to my understanding, the rest of the logic would work correctly unchanged.
At the moment I have 2 ideas:

Run another Bluge query on the same snapshot as the original query.  Obviously this immediately raises concerns about some sort of n2 query execution, but we could do this with an additional MUST clause on the outer for-loop's _id.  This might be sufficient to keep the cost of the query down to an acceptable level.  This should be easy to prototype, but may require additional testing to validate the performance implications.
Use something like bleve sear to allow for fast single-document matches a query execution.  This might yield a leaner/faster solution, but would also involve additional effort as sear would have to be adapted to work alongside bluge.

Another unrelated observation while in this section of code: the bluge request today uses top-N with n=len(activeIndexes), which generally should be replaced with an AllMatches request.  This should work for Nakama as we process each search hit one at a time anyway, and often we may find what we're looking for early anyway.  By doing this, we would avoid the need to allocate as many large slices for the entire result set, because we process them as we go.

After discussion with @mschoch we've decided to park this until further improvements land in the matchmaker. We can revisit refactoring then. 👍


response body is nil

Hi,
Another fun one for the Net::HTTP crowd. Been seeing sporadic issues from this code in session.rb:
response = access_token_request(code)
if response.code == "200"
  token = JSON.parse(response.body)['access_token']
else
  raise RuntimeError, response.msg
end

The response.code method exists and is 200, but the response body is nil. Is there a better way to handle the underlying reason no body would be returned? It is likely the token at fault but it seems handling this is awkward as there is no mention of the source of the troubles.

Closing for now - if somehow this issue is still occurring feel free to say so here with more information.

Shopify. On the Ball. Closing issues from 2014 like there is no tomorrow.


Adds AuthorizationHelper Improvements to ConvertToBase64string method

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
Instead of using ‘ArrayPool.Shared.Rent(capacity)’ to allocate byte array temporarily, we can use a hybrid of stackalloc byte[] and ArrayPool.Shared.Rent. It avoids the overhead of allocating and deallocating the buffer.
Ask from compute team:
Need to change this method https://github.com/Azure/azure-cosmos-dotnet-v3/blob/167647588c71f2a87b193c98deb689142063f9bf/Microsoft.Azure.Cosmos/src/Authorization/AuthorizationHelper.cs#L780 SDK keeps renting byte arrays in a case where hashPayLoad is always 64 byte array (256 bit hash). We see this coming up on the AzureProfiles and could be responsible for 0.1% of the CPU utilization. Instead we should allocate on stack here.

Closing the issue for now as there is lack of clarity around the ask and still waiting on requesting team.


Terragrunt cache for providers doesn't work with nested modules

Describe the bug
We started testing https://terragrunt.gruntwork.io/docs/features/provider-cache/ and faced a problem.
Terragrunt with enable caching fails if we use "nested" configuration for modules, when one module sources another one.
For example, to create an AWS VPC we use our own local module that does some extra work and sources a module terraform-aws-modules/vpc/aws. In this case we get the next error:
INFO[0000] Terragrunt Cache server is listening on <IP_ADDRESS>:54708
INFO[0000] Start Terragrunt Cache server
╷
│ Error: Error accessing remote module registry
│
│   on main.tf line 10:
│   10: module "vpc" {
│
│ Failed to retrieve available versions for module "vpc" (main.tf:10) from
│ registry.terraform.io: host registry.terraform.io does not provide a
│ modules service.
╵

╷
│ Error: Error accessing remote module registry
│
│   on main.tf line 85:
│   85: module "vpc_gateway_endpoints" {
│
│ Failed to retrieve available versions for module "vpc_gateway_endpoints"
│ (main.tf:85) from registry.terraform.io: host registry.terraform.io does
│ not provide a modules service.
╵

If we directly call the terraform-aws-modules/vpc/aws from the terragrunt.hcl file, everything works well
$ TERRAGRUNT_PROVIDER_CACHE=1 TERRAGRUNT_PROVIDER_CACHE_DIR=/Users/nikro/.terraform.d/plugin-cache terragrunt plan                                                         <aws:md-sandbox-admin>
INFO[0000] Terragrunt Cache server is listening on <IP_ADDRESS>:57086
INFO[0000] Start Terragrunt Cache server
INFO[0000] Downloading Terraform configurations from tfr:///terraform-aws-modules/vpc/aws?version=5.7.1 into /Users/example/test-repo/....../.terragrunt-cache/QrEmt8mAQ5UY76kC5XOncjM8wYA/ThyYwttwki6d6AS3aD5OwoyqIWA
INFO[0007] Provider "registry.terraform.io/hashicorp/aws/5.45.0" is cached

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Finding hashicorp/aws versions matching ">= 5.30.0"...
- Installing hashicorp/aws v5.45.0...
- Installed hashicorp/aws v5.45.0 (unauthenticated)

Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.

To Reproduce
Steps to reproduce the behavior, code snippets and examples which can be used to reproduce the issue.
include "root" {
  path   = find_in_parent_folders()
  expose = true
}

include "env" {
  path   = find_in_parent_folders("env.hcl")
  expose = true
}

generate "providers_versions" {
  path      = "versions.tf"
  if_exists = "overwrite"
  contents  = <<EOF
terraform {
  required_version = ">= 1.7.0"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "${include.root.locals.tf_providers.aws}"
    }
  }
}
EOF
}

terraform {
  source = "${get_path_to_repo_root()}/terraform//modules/aws-vpc"
}

inputs = {
  name               = include.env.locals.name
  cidr               = include.env.locals.values.vpc_cidr
  azs                = include.env.locals.values.azs
  single_nat_gateway = include.env.locals.values.single_nat_gateway
}

terraform//modules/aws-vpc/main.tf
...
module "vpc" {
  source  = "terraform-aws-modules/vpc/aws"
  version = "5.7.1"

  name = var.name
  cidr = var.cidr

....

Expected behavior
Working terragrunt and cache
Nice to have

[ ] Terminal output
[ ] Screenshots

Versions

Terragrunt version: 0.56.5
Terraform version: 1.7.3
Environment details (Ubuntu 20.04, Windows 10, etc.): MacOS Sonoma

Additional context
Add any other context about the problem here.

I'm experiencing the same issue, I was not able to workaround it

I was able to hack in a fix and use a locally-built terragrunt to get around this issue. I doubt this is a proper fix, but maybe it'll help towards figuring out an actual solution.

Resolved in v0.57.3 release.


skip next ui workaround - world

-add missing locations related to hiding place film, allowing them to be randomized
-reworks existing locations related to hiding place film, allowing them to be randomized
-rookie's table is now able to be randomized
works on my side, but my testing was done on a older versions of the game, might want to double check at least one of those places (rookie's table is the easiest one)

Code changes look straightforward :+1:
Making a note of things I need to test with this when I can:

Server sending Rising Rookie gives the right item, since item entry mentioned that hex might not be right
Checking 1 full set of items for each of A and B, both Standard and Hardcore of one

Still planning to test this. Just need to resolve some hardware issues in the meantime first :smiley:


Fix bug #7647 in image retraining example retrain.py so that the --pr…

Fix bug #7647 in image retraining example retrain.py so that the --print_misclassified_test_images flag now works properly in Python 3.

Can one of the admins verify this patch?

Jenkins, test this please.


Support for Windows 10

Are there any plans to support Windows UWP or Windows Phone. I know, most iOS and Android users forget about but still, Windows has a notable market share.

Windows certainly has a large market share as a desktop OS! And Zulip very much supports Windows. You can get our desktop app here:
https://zulipchat.com/apps/windows

I believe Windows Phone is a very different story. Here's an obituary for it, in 2017:
https://www.vox.com/2017/7/17/15984222/microsoft-windows-phone-mobile-operating-system-android-iphone-ios
Graph from that news story:

Windows Phone was at 0.1% market share then, and Microsoft has ended support for it.
So I don't think we'll ever be interested in putting effort into supporting Windows Phone.

But Windows Phone is not Windows 10. Any Windows UWP-App runs on Windows 10. And Windows 10 is the mostly used Desktop-System worldwide. This would still increase the UX as UWP apps offer native UI.

Any Windows UWP-App runs on Windows 10. And Windows 10 is the mostly used Desktop-System worldwide. This would still increase the UX as UWP apps offer native UI.

Have you tried the Zulip Windows app?
https://zulipchat.com/apps/windows
That and the webapp are our two recommended clients for Windows -- same story as on macOS or Linux.
The Zulip mobile app has a UI optimized for mobile-size displays, with a touchscreen and no physical keyboard. The desktop app, like the webapp, has a UI optimized for laptops and desktops with a bigger screen and a real keyboard. There are a lot of UI choices that go differently for those two very different environments, so even if the app were made to run on Windows it would be quite difficult for it to beat the UX of the desktop app and webapp.

If someone is excited about making the app run with e.g. react-native-windows (TIL!) I will certainly be curious to see what they come up with :smiley:
I think most likely we would not be keen on merging a PR for it, though -- it'd have to fit in quite cleanly without requiring a lot of changes across the app, and that seems tough.


[Dont Merge] nixos-iso: Add zfs / btrfs to supportedFilesystems

Does this seem reasonable to everyone? My only worry is that zfs sometimes falls behind in supporting newer kernels which would cause the iso build to fail. It would be nice to be able to create zfs root installs and access zfs pools from the iso though.

The bug in ZFS was fixed.  Check the upstream bug.  https://github.com/zfsonlinux/zfs/issues/2368#issuecomment-45520352


Product AutoConfigurator creates config for read only properties

Describe the bug
The AutoConfigurator creates config for read only properties. From my point of view, the get-only properties should be ignored.
My product have the following properties
public double Length { get; set; }

public string LengthString => Length.ToString("F");

public double Height { get; set; }

public string HeightString => Height.ToString("F");

To Reproduce
The AutoConfigurator is creating the following config for me:
{
    "$type": "Moryx.Products.Management.GenericTypeConfiguration, Moryx.Products.Management",
    "PluginName": "GenericTypeStrategy",
    "JsonColumn": "Text8",
    "PropertyConfigs": [
        {
        "PropertyName": "Length",
        "PluginName": "FloatColumnMapper",
        "Column": "Float1"
        },
        {
        "PropertyName": "LengthString",
        "PluginName": "TextColumnMapper",
        "Column": "Text1"
        },
        {
        "PropertyName": "Height",
        "PluginName": "FloatColumnMapper",
        "Column": "Float2"
        },
        {
        "PropertyName": "HeightString",
        "PluginName": "TextColumnMapper",
        "Column": "Text2"
        }
    ],
    "TargetType": "MyProductType"
},

@Toxantron I was already on the way to fix this problem but I am not sure which is the right way:

Assign NullPropertyMapper (which would maybe work for the AutoConfigurator) but what would a developer or user of the product management do?
Ignore get-only properties in all mappers

I would prefer the latter.  Read-only properties are mostly "helpers", there is no point in the storage to consider them and once we move the endpoint out, the entire product management could ignore them.

Ignore get-only properties in all mappers


Rename documents path

This text doesn't provide which documents path. The objective of this issue is to provide a way to better show what the documents path is.
It is something like:
C:\Users\USERR\OneDrive\DOCUMENTSPATH\Paradox Interactive

It could say something like:
Can't find "Paradox Interactive" in your documents
or:
Can't find "documents/Paradox Interactive"
but if the save data isn't located in Documents this might be better:
Can't find the hoi4 save data directory

@Wolfmyths Certainly, I think the combination of the solutions is better. Like:
Can't find "Paradox Interactive" in $PATH


Implement loading and saving for floating docks

As mentioned in https://github.com/godotengine/godot/issues/57142#issuecomment-1064021752, floating docks in the editor layout were not loaded nor saved, they were always reset back to their original dock slot.
Now, they are saved in the config with the key dock_floating, here's what it looks like in a config file:
dock_floating={
"Inspector": Rect2i(2319, 47, 688, 448),
"Node": Rect2i(3012, 48, 486, 933)
}

Superseded by #62378.


Error: Invalid name: please ensure the contract and method you're calling exist! failed to decode empty bytes. if you're using jsonrpc this is likely due to jsonrpc returning 0x in case contract or method don't exist

I have a problem:
Execute the command
./target/release/mev-inspect -u http://x.x.x.x:8545
Error: Invalid name: please ensure the contract and method you're calling exist! failed to decode empty bytes. if you're using jsonrpc this is likely due to jsonrpc returning 0x in case contract or method don't exist
I need help.😢

Hey - this does not look like a valid command to me...Can you give a specific block / tx example which fail to work?

Hi. I actually ran in to the same error message. Here is what I did

setup a MEV-geth and run it locally via the following command

./build/bin/geth console --http --syncmode "light" --signer=/Users/namgun_kim/Library/Signer/clef.ipc

ran the following mev-inspect-rs command to learn more about the particular block 12544939

./target/release/mev-inspect blocks -f 12544939 -t 12544939

I highly suspect that there is something wrong with my local setup.

mev-inspect-rs works with Parity/Open Ethereum nodes, not Geth, due to usage of the tracing API!


Enable javax_net_ssl_fips with FIPS_VARIATION_PROBLEM_LIST_FILE

related: backlog/issues/1529
depends on: https://github.com/adoptium/TKG/pull/620 and https://github.com/ibmruntimes/openj9-openjdk-jdk11/pull/816

Grinder


Navbar-expand and paddings

Bootstrap v4dev
I don't know if I understood, .navbar-expand is used when you want the .navbar is always expanded?
I try this way, but when i use .navbar-expand, the paddings are removed from container and the content is larger then the other part.
https://jsbin.com/zoyuqiteri/edit?html,output

Yes, we toggle the padding and margin a bit to make the navbar behave as we want it to. As I recall there wasn't much of a way around it.

I don't know if this problem has been addressed but this happens with all other expands as well (navbar-expand-sm, navbar-expand-md, lg, etc)
In this particular case, these lines are causing this problem:
.navbar-expand > .container, .navbar-expand > .container-fluid {     padding-right: 0;     padding-left: 0; }
Which can be solved by wrapping them only in the media they should be valid
@media (max-width: 585px) {     .navbar-expand > .container,     .navbar-expand > .container-fluid {         padding-right: 0;         padding-left: 0;     } }
All other expands are fixed by including them inside this media as well.
As of now, for example, navbar-expand-md loses its .container padding from 585px to 767px screens.
This is because of this code
@media (max-width: 767px) {   .navbar-expand-md > .container,   .navbar-expand-md > .container-fluid {     padding-right: 0;     padding-left: 0;   } }
Simply by adjusting its max-width to 585 (xs screen) solves this problem.
I don't seem to understand the reason behind toggling the padding like this, as navbars are still behaving as expected after this fix. This is the reason this seems like a problem. Am I missing something? @mdo

I've noticed this same issue.
In case it's not clear what's happening, here is an screenshot of the issue happening on Bootstrap v4-alpha website.
As you can see, the container inside navbar-toggleable (or navbar-expand if you are in v4-dev),  is missing its horizontal padding, and so, the Bootstrap brand and the hamburguer menu are misaligned.

As others, I also don't understand the reason behind toggling the padding.
The issue is both present in alpha-6 release and v4-dev branch.

For anyone compiling Bootstrap from SASS sources, you can restore the horizontal padding on .navbar-expand-* elements by monkeypatching your code in a custom SASS file (imported below _navbar.scss) that generates the very same .navbar-expand-* classes, allowing those classes to have more precedence.
In your custom SASS file, you add:
// Generate series of `.navbar-expand-*` responsive classes for configuring
// where your navbar collapses.
.navbar-expand {
  @each $breakpoint in map-keys($grid-breakpoints) {
    $next: breakpoint-next($breakpoint, $grid-breakpoints);
    $infix: breakpoint-infix($next, $grid-breakpoints);

    &#{$infix} {
      @include media-breakpoint-down($breakpoint) {
        > .container,
        > .container-fluid {
          padding-right: $navbar-padding-x;
          padding-left: $navbar-padding-x;
        }
      }
    }
  }
}

As you can see, it's the very same code taken from bootstrap/scss/_navbar.css but only monkeypatching the relevant parts to restore the horizontal padding (using $navbar-padding-x variable).

This worked for .container:
.navbar-expand > .container {
	padding-right: 15px;
	padding-left: 15px;
}

@media (max-width: 575px) {
	.navbar-expand > .container {
		padding-right: 0;
		padding-left: 0;
	}
}

This worked for .container on V4 Beta 1:
.navbar-expand > .container {
	padding-right: 15px;
	padding-left: 15px;
}

/* Extra small devices (portrait phones, less than 576px) */
@media (max-width: 575px) {
	.navbar-expand > .container {
		padding-right: 0;
		padding-left: 0;
	}
}

This worked for .container on V4 Beta 1:
.navbar-expand > .container {
	padding-right: 15px;
	padding-left: 15px;
}

@media (max-width: 575px) {
	.navbar-expand > .container {
		padding-right: 0;
		padding-left: 0;
	}
}

Changing navbar-expand-md to navbar-expand-sm seems to work in my use case.

As I recall there wasn't much of a way around it.

Around what? This seems to be a bug.

Why is this closed again?
It seems only quickfixes has been suggested, and no actual solution or response to if it is going to be fixed or not.


PnR crashes if you use a capacitor and don't have a corresponding CC constraint

@Lastdayends PnR seg. faults if you don't have a CC constraint corresponding to the capacitors in the design (I guess the CC constraint causes the capacitor array to be generated---otherwise there are pins with missing components in the placer.)
We should probably explicitly check for this and assert with a decent error message. It took a while for me to figure out what was going one.

Hi Steven,
You are right. If CC constraint is missed, no common centroid capacitor
will be created, thus the pin information is empty for this common centroid
capacitor.
I will let the code print something for CC constraint missing error.
Yaguang
Steve Burns<EMAIL_ADDRESS>于 2019年7月28日周日 下午1:01写道：

@Lastdayends
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Lastdayends&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=nPuywd6RUqnxGqmKZesVUhd4KkdJyloQ9HO-xbBP3a0&s=2GAZannsl7Qn0jKi-JIPsYUvU6dxHD112XQgTSB4a-8&e=
PnR seg. faults if you don't have a CC constraint corresponding to the
capacitors in the design (I guess the CC constraint causes the capacitor
array to be generated---otherwise there are pins with missing components in
the placer.)
We should probably explicitly check for this and assert with a decent
error message. It took a while for me to figure out what was going one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ALIGN-2Danaloglayout_ALIGN-2Dpublic_issues_101-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAKIMLZWQMVR2MEQNJUXEB4TQBXNG3A5CNFSM4IHNCTEKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HB5E64A&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=nPuywd6RUqnxGqmKZesVUhd4KkdJyloQ9HO-xbBP3a0&s=oUPzYpYtFjl6BRTP_n2yHJwRHDMMKlG-e8Y1zjlvu3Y&e=,
or mute the thread
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AKIMLZUKFT5Y7HDC7X4YBELQBXNG3ANCNFSM4IHNCTEA&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=nPuywd6RUqnxGqmKZesVUhd4KkdJyloQ9HO-xbBP3a0&s=yZ-xwdXDec0oO5OI4C1HMtzaCbHQVKsspjYUIA6GPA8&e=
.

Hi Steven,
By the way, which design are you testing? (dc_dc?) Can you send me the link
of your test case? I can check your case about this CC format issue.
Yaguang
Yaguang
Yaguang Li<EMAIL_ADDRESS>于 2019年7月28日周日 下午7:06写道：

Hi Steven,
You are right. If CC constraint is missed, no common centroid capacitor
will be created, thus the pin information is empty for this common centroid
capacitor.
I will let the code print something for CC constraint missing error.
Yaguang
Steve Burns<EMAIL_ADDRESS>于 2019年7月28日周日 下午1:01写道：

@Lastdayends
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Lastdayends&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=nPuywd6RUqnxGqmKZesVUhd4KkdJyloQ9HO-xbBP3a0&s=2GAZannsl7Qn0jKi-JIPsYUvU6dxHD112XQgTSB4a-8&e=
PnR seg. faults if you don't have a CC constraint corresponding to the
capacitors in the design (I guess the CC constraint causes the capacitor
array to be generated---otherwise there are pins with missing components in
the placer.)
We should probably explicitly check for this and assert with a decent
error message. It took a while for me to figure out what was going one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ALIGN-2Danaloglayout_ALIGN-2Dpublic_issues_101-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAKIMLZWQMVR2MEQNJUXEB4TQBXNG3A5CNFSM4IHNCTEKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HB5E64A&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=nPuywd6RUqnxGqmKZesVUhd4KkdJyloQ9HO-xbBP3a0&s=oUPzYpYtFjl6BRTP_n2yHJwRHDMMKlG-e8Y1zjlvu3Y&e=,
or mute the thread
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AKIMLZUKFT5Y7HDC7X4YBELQBXNG3ANCNFSM4IHNCTEA&d=DwMCaQ&c=u6LDEWzohnDQ01ySGnxMzg&r=ZMUCBc0sWFUe5MzbQ3jL6w&m=nPuywd6RUqnxGqmKZesVUhd4KkdJyloQ9HO-xbBP3a0&s=yZ-xwdXDec0oO5OI4C1HMtzaCbHQVKsspjYUIA6GPA8&e=
.

Closing because this has been superseded by #187 . Same issue, different case


Add a parameter to limit the size of a query string

Description
fix #3546
Added a parameter to set the maximum number of characters in a query.
Default is set to 512 for the following reasons.
Because the query for this test was 395 bytes, and I thought the default of 256 byte might be too short even for a normal use case. (I'd like to hear from maintainers here)
https://github.com/quickwit-oss/quickwit/blob/main/quickwit/quickwit-jaeger/src/integration_tests.rs#L197
How was this PR tested?
add a few unit tests.
Please let us know if you feel your test case is missing :)

 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.

Default is set to 512 for the following reasons.
I'd personally go even higher with 1,000 bytes or more. Queries generated programmatically can be long.


Update Composer dependencies (2020-06-10-00-12)

Visual regression test passed!
View the visual regression test report


Exchange Online Powershell reference page link is broken/404

https://docs.microsoft.com/en-us/powershell/exchange/
Hi there,
I tried accessing the exchange online powershell reference page via different browsers, but link seems to be broken. It was working few days ago, can you please fix this ?

It works now, Closing this issue.


SQS issue with new AWS sdk

What steps will reproduce the problem?
after upgrading AWS SDK the SQS Queue TTR will received only as a string and the SQS driver in yii is sent as an integer.
What is the expected result?
Error: The provided type for MessageAttributes -> TTR -> StringValue value was integer. The modeled type is string.
Additional info
must be casting the TTR value as a string to prevent the exception in pushMessage function in yiisoft/yii2-queue/src/drivers/sqs/Queue.php or override the class and make your changed
$request = [             'QueueUrl' => $this->url,             'MessageBody' => $message,             'DelaySeconds' => $delay,             'MessageAttributes' => [                 'TTR' => [                     'DataType' => 'Number',                     'StringValue' => (string)$ttr,                 ],             ],         ];

Q
A

Yii version
2.0.49

PHP version
8.1

Operating system
ubuntu

AWS SDK
3.293.8

@mahran419 This seems to be an issue with the yii2-queue package and I think it's the same issue fixed here: https://github.com/yiisoft/yii2-queue/pull/502
Could you please try with the "dev-master" version ("yiisoft/yii2-queue": "dev-master" in your composer.json file).

@rhertogh Yes the same issue was fixed on version ("yiisoft/yii2-queue": "dev-master"
thank you @rhertogh


extensions: addition of IPython notebook preview

Adds a new previewer which renders IPython notebook files. (closes #6)

Signed-off-by: Javier Delgado<EMAIL_ADDRESS>

Merge after #14

@tiborsimko It does not have support for ROOT right now. However, it works with the file that you post on #6 (file) since the execution result is already stored in the file.

Coverage increased (+1.7%) to 93.574% when pulling 6d740418e5024e5fc58020c65ad9b75578f85a03 on JavierDelgadoFernandez:ipynb_addition into e848e04bbecb94a910b26a561988018aac475e3f on inveniosoftware:master.

Coverage increased (+1.6%) to 93.443% when pulling 6d740418e5024e5fc58020c65ad9b75578f85a03 on JavierDelgadoFernandez:ipynb_addition into e848e04bbecb94a910b26a561988018aac475e3f on inveniosoftware:master.

Coverage increased (+1.6%) to 93.443% when pulling 6d740418e5024e5fc58020c65ad9b75578f85a03 on JavierDelgadoFernandez:ipynb_addition into e848e04bbecb94a910b26a561988018aac475e3f on inveniosoftware:master.

@lnielsen Rebased and updated.

Coverage increased (+0.5%) to 92.988% when pulling 2ab92c06100def25a30d4dd13589f40aca46887f on JavierDelgadoFernandez:ipynb_addition into ea3188b332cbfd60cd98801e4a813b73d7e25ab5 on inveniosoftware:master.


Firewall rules won't apply when one of the interfaces lacks an address on failover

Important notices
[X] I have read the contributing guide lines at
[X] I have searched the existing issues and I'm convinced that mine is new.
Describe the bug
When dealing with a failover scenario in a multi-WAN setup, if the primary interface goes down (i.e. upstream outage) and its DHCP lease expires, the interface won't have an address assigned to it and any and all changes to firewall rules will fail.
The following notices will start accumulating on the top of the page:
03-12-20 12:49:29 [ There were error(s) loading the rules: /tmp/rules.debug:85: no translation address with matching address family found. - The line in question reads [85]: nat on igb2 inet proto tcp from (igb2:network) to $VPNGATE port {22} -> igb2 port 1024:65535 # vpngate/ssh ]

Some functionality (notably, policy-routed VPNs) will fail to function correctly due to the above notice during rule application.
When the DHCP lease is refreshed (i.e. service returns), everything goes back to normal. The common denominator seems to be that while the interface has an IP assigned - regardless of whether service is actually available through the circuit - everything works as intended, even during failover (thanks to info from this ticket, I applied the patch mentioned therein and that resolved other problems I was having regarding default gateways).
To Reproduce
Steps to reproduce the behavior:

Install OPNsense 20.1, apply all updates
Configure WAN1 using DHCP, set its gateway to be upstream with priority 1, and gateway monitoring using a "far" IP (i.e. <IP_ADDRESS>)
Configure WAN2 using DHCP, set its gateway to be upstream with priority 2, and gateway monitoring using a "far" IP (i.e. <IP_ADDRESS>)
Configure all other gateways set Disable Gateway Monitoring and Mark Gateway as Down
Configure GW Monitoring like described in https://docs.opnsense.org/manual/how-tos/multiwan.html
Enable gateway switching
Configure policy based routing like described in https://docs.opnsense.org/manual/how-tos/multiwan.html
Confiure an SSH port forwarding on both WAN1 and WAN2 to an internal server (named VPNGATE in our example), and use a Host Alias to refer to the server's IP.
Wait for both WAN gateways to be up and available
Verify routing over both WAN gateways
Unplug the cable for WAN1 at either end
Wait for the IP address on the WAN1 interface to be cleared out

Expected behavior
No loss of traffic routing or functionality due to failover to WAN2, ability to change or modify rules and have them take effect immediately, functionality continues upon return to service of WAN1.
Actual behavior
Some or all routing functionality is lost, rules can be changed in the UI and saved, but do not take effect immediately - the above notice is the only indication of an error.
Environment
OPNsense 20.1.2-amd64
FreeBSD 11.2-RELEASE-p17-HBSD
OpenSSL 1.1.1d 10 Sep 2019
Protectlii FW4B

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


Fix issue551

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: #551
What is the new behavior?

Other information

Codecov Report
Base: 62.00% // Head: 44.51% // Decreases project coverage by -17.49% :warning:

Coverage data is based on head (605b3cf) compared to base (136decb).
Patch coverage: 41.02% of modified lines in pull request are covered.

: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             @@
##           master     #552       +/-   ##
===========================================
- Coverage   62.00%   44.51%   -17.49%
===========================================
  Files         221      147       -74
  Lines       21466    15346     -6120
===========================================
- Hits        13309     6831     -6478
- Misses       7503     8206      +703
+ Partials      654      309      -345

Flag
Coverage Δ

1.16.x
44.14% <41.02%> (-17.41%)
:arrow_down:

1.19.x
44.56% <41.02%> (-17.29%)
:arrow_down:

1.20.x
44.58% <41.02%> (-17.23%)
:arrow_down:

integration
?

macOS-latest
44.46% <41.02%> (+0.04%)
:arrow_up:

ubuntu-latest
44.59% <41.02%> (-17.37%)
:arrow_down:

unit
44.51% <41.02%> (-0.05%)
:arrow_down:

windows-latest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

 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.


simplify check if enum is boolean

Has been tested to work localy

I don't mean to be a jerk but there is no reason to correct working code for stylistic reasons. PRs should be submitted for bugs of improvements. Your changes are both unnecessary and logically wrong. The first will cause an exception to be raised if values is None and the second is both less efficient than the previous code and also logically wrong because it doesn't do the same thing. It doesn't check if the string ends with "on" or "off". So I'm closing this PR.


[GAL-50 GAL-51 GAL-52 GAL-53] WIP Add Follow functionality

This PR adds Follow/Unfollow functionality.
Users can now follow + unfollow other users, and also see a list of followers and following.

Main new components are:
Follow Button
displays an icon depending on following state, and calls the follow/unfollow mutation. has some icon display logic depending on hover, etc.
Tooltip
replaces react-tooltip. Making our own tooltip was easier to match the spec
Follower List component
displays a user's followers and following.
Follower Count
displays a user's follower count + opens Follower List when clicked.
A  Follow "Nav Action" component
wraps all the above into an interactive component that lives in the navbar. Other Nav Actions would be additional circular buttons in the navbar.

added useFollowUser and useUnfollowUser mutation hooks

closing in favor of #787


Model Inference with Haliax?

I am trying to replicate nanoGPT with Haliax but am running into an error when trying to do inference with the model. The model expects a named array as input, but unlike during training, the vector of tokens I provide will not always fill up the entire context/block size, and so will not have the Block axis – in fact, it should probably be an unnamed array for this reason because there is no real meaningful axis to represent. But I can't pass in a normal Jax array to my Haliax model. So how should inference be done? I tried checking out the Levanter repo but was unable to determine this. Apologies if it is an elementary question.

Hi @rohan-mehta-1024 ,
That sounds like a great project! Just so we're clear, you're using Block as the name of the sequence length Axis? I still think it's meaningful to give it a name: the axis has a meaning. Also note that not all vectors that have an axis called "block" will have to have the same length for block. That said, because of the way jax works, you have to recompile every time you pass in a new length, so I'd recommend padding to some set of lengths.
I've personally not implemented inference in Haliax/Levanter yet, but I don't think there should be too many surprises.

I think this is good/reasonable. It would be good to add pad and similar (might be a decent PR...)
One could probably haliax-ify the seq/full_seq stuff, but i think it's ok
I think "Embed" is a weird choice of axis name here. ordinarily i'd expect Vocab or TokenId or something?

Ok, thanks for that confirmation. It's a little confusing but Embed and Vocab have the same size here because I'm testing things out with a bigram model before I move to the full transformer architecture. I'm kinda new to this, but would like to support this library as I think it's really cool, and so will try to submit a PR for pad / unpad functions.

closing this, just b/c there's no definition of done


Debounce Autocomplete

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[x] support request/question

Current behavior
autocomplete using an Observable sends HTTP requests as soon as user types a single character.
Expected behavior

Is there an easy way to debounce?  For example, only fire the network request after the user has stopped typing for 500ms. I see there is a minimumTextLength property.  If that works as I expect, I suppose I could only send the HTTP request after the user types at least X amount of characters.

Hi @chanm003,
can you try onTextChangeDebounce? This should work, but I haven't tried it yet with autocompleteObservable. Let me know :)

Hi @Gbuomprisco,
Worked like a charm with autCompleteObservable! I should have found that!

Awesome :)


Cant Log in (Captcha)

Describe the bug
It says my password or something is wrong but I KNOW everything is right.
Screenshots or Logs

Configuration (please complete the following information):

Browser: I think chrome?
Hosting solution [e.g. reverse proxy, HTTPS/HTTP, caching, localhost]: i think localtunnel

The error page._client.send is not a function is causing one of the stealth evasions to fail, causing the login to be detected as a bot, and to fail.
It's hard to support non-Docker deployments since there's exponentially more room for error in setup. I don't really have much more advice than to setup fresh.

Good Day, I am having the same issue on HomeAssistant Docker install, The Capptcha is saying invalid and does it over and over again.

Got the same problem as well

Me too, in one out of four accounts. The others  work.
Deployed with Docker on NAS and was working the last 1.5 years… strange!

I'm also getting this error, and am using Docker. I'm also not seeing the page._client.send is not a function error that was previously mentioned.

No longer relevant in latest version


Pricing tier doesn't match the subscription's billing model.

Unable execute: az deployment group create --resource-group hub-spoke \     --template-uri https://raw.githubusercontent.com/mspnp/samples/master/solutions/azure-hub-spoke/azuredeploy.json
I get this error message:
$ az deployment group create --resource-group hub-spoke \
    --template-uri https://raw.githubusercontent.com/mspnp/samples/master/solutions/azure-hub-spoke/azuredeploy.json
Please provide string value for 'adminUserName' (? for help): admin
Please provide securestring value for 'adminPassword' (? for help):
{"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{\r\n  \"error\": {\r\n    \"code\": \"BadRequest\",\r\n    \"message\": \"Pricing tier doesn't match the subscription's billing model. Read http://aka.ms/PricingTierWarning for more details.\",\r\n    \"target\": \"PricingTier\"\r\n  }\r\n}"}]}}

Note: I was given a ~$200 "Visual Studio Enterprise Subscription"

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

ID: 104eba32-c77e-b013-e161-ff616d16a0f7
Version Independent ID: 3bc27d0a-ef32-f5f6-4c85-fe8e2e45155e
Content: Hub-spoke network topology in Azure - Azure Reference Architectures
Content Source: docs/reference-architectures/hybrid-networking/hub-spoke.yml
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @EdPrice-MSFT
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 488992

@snodnipper We assume you are talking about the section - Deploy with VPN gateway . I think the VS enterprise subscription you have may be of old SKU when it used to have $200 allowance. I am not sure but now VS enterprise based subscription gets $150 allowance per month and many Azure services follow the newer pricing model so you may get some error like this. But we will verify this on our side and let you know further.

@snodnipper Looks like the problem is with the legacy SKU set for the log analytics workspace. I worked up a PR to fix this. Could you give it a shot?
Click this to try deploying from Azure Portal

or run the following using Azure CLI
az deployment sub create --location eastus \
    --template-uri https://raw.githubusercontent.com/PramodValavala-MSFT/samples/patch-1/solutions/azure-hub-spoke/azuredeploy.json

@PramodValavala-MSFT, thanks for that - I just ran it in my subscription and all is good now.  Thanks!


Ollama quickstart update

Description
Add OLLAMA_NUM_GPU env variables in ollama quickstart,  remove PARAMETER num_gpu 999 and "options": {"num_gpu": 999}.
We will only recommend users to set OLLAMA_NUM_GPU to run models on gpu in the future.
4. How to test?

[ ] Document test

maybe put OLLAMA_NUM_GPU setting under ### 3 Run Ollama Serve


Add compiler optimisation flags to CMake configuration

It looks like compiler optimisation flags can make a huge difference. We should consider enforcing these in the CMake configuration, if not already default. However it'll probably be a good idea to run the whole CI test suite after making changes related to this, and possibly a real-time video processing pipeline.

Closing as out of date.


[3.x] Make MessageQueue growable

Uses simple vector resizing (po2)
Uses pair of read and write buffers

3.x version of #65740
See that PR for more details.

Thanks!


add chown command for kicker

When pulling the web3 image in gitpod, the following error message will appear:

Reference solution: https://github.com/badges/shields/pull/8908


Code example in Metamask snap

To demonstrate wallet-dapp integration with Waku, let's create a metamask extension using their snap framework: https://medium.com/metamask/introducing-the-next-evolution-of-the-web3-wallet-4abdf801a4ee
The example could be an other eth-pm or maybe something more M2M like such as a notification from a contract owner (DAO) to token holder.

This is marked as closed "Done" just wondering if you could point to where the metamask snap code is ?

@reisepass this was closed as "not done" :)


Window controls and sidebar overlaid on 1.6.1

Here's what I see... so far restarting hasn't made it go away.

And then literally as I'm typing this and having left it running in the background, it sorts itself out. Weird.

Fixed in PR https://github.com/yannhodiesne/Discord-M1/pull/17#issuecomment-961148024


Investigate latency

On my machine, I was getting an estimated 250ms latency in the demo app, which is a lot of overhead for Unreal to be adding. Could be my graphics card or general system load, or system settings, but the "out of box experience" for the integration should be better.

Some latency was reduced with this issue fixed:
https://github.com/OSVR/OSVR-Unreal/issues/7
This causes some performance overhead, but apparently not as much as it did pre-4.8. The current rift plugin turns this setting off. I only see a 1-2ms difference in frame render time (according to profilegpu), but this is with a small scene.
The next biggest source of latency for me is likely to be from me running the HDK in landscape mode with my main display duplicated.
Next, @yboger suggested running context update more than once per frame, and closer to frame render time. Couldn't hurt, but I think adding render manager support w/direct mode is going to give the biggest gain.
Frame render time doesn't appear to be a significant factor in latency. I am getting consistent 4-6ms frame render times. Granted this is with a very simple scene - I could import a more complex map from the gallery for testing purposes to see for sure, but it's not a priority.

Closing this as we are doing much better with latency in the latest code (this is an old issue).


How to add user management to the UI interface

I installed the  ES7 +latest version of SkyWalking，when I launch the UI, I go directly to the page without logging in。
If I use it in the company's servers, this is generally not allowed.
So I need a solution that prevents arbitrary access from the outside world.

Please don't submit a duplicated question. We have answered many times, there is no user management. Choose proxy, such as Nginx/APISIX to do that.


Old CA certificates in AmazonLinux 2023

During minor upgrade from 2.9 to 2.10 the container base OS was silently switched from AmazonLinux 2 to AmazonLinux 2023.
Not that silent though, as CA root cert bundle in AL2023 is utterly broken.
See https://github.com/amazonlinux/amazon-linux-2023/issues/471
While I don't know why that switch of base OS happened in a minor change, it definitely might break things in deployments.

Yep, 2.10 has broken our CI/CD pipeline. Reverting to 2.9.0 fixes the issue

@TheRealBro  We are looking in to this issue and will track the upstream issue as well.
The decision to move to AL2023 was finalized for 2.10.0 release to support Node18 version based on the proposal here.
CC: @peterzhuamazon @prudhvigodithi

Understanding the need for Node 18, those big changes should end up in a major release - not in a minor version upgrade. I guess that is what SemVer defines as well. justmy2cents

@TheRealBro We were indirectly forced to migrate to Node18 since Node 16 End-of-Life Date was suddenly changed to September 11th, 2023. Having said that, OpenSearch dashboards still should support older version of node ( i.e. node 14 and node 16 by switching the node version locally) but we ship only the actively supported version in the distribution.

Hey @TheRealBro @marcin-bojar, I'm curious can you please elaborate or share the error how the application is being impacted? I assume you are using docker and the container exits ?

@xoxys do you still have the logs?

New finding ... your documentation on DockerHub became outdated as well with that change.
https://hub.docker.com/r/opensearchproject/opensearch
Note: OpenSearch images use [Amazon Linux 2](https://aws.amazon.com/amazon-linux-2/) as the base image. If you are using [Docker Desktop](https://www.docker.com/products/docker-desktop/), then we recommend configuring Docker to use a minimum of 4 GB of your system memory.

Hey @TheRealBro @marcin-bojar, I'm curious can you please elaborate or share the error how the application is being impacted? I assume you are using docker and the container exits ?

Sure. If you run OpenSearch with Certificates from an "official CA" and not self-signed PKI, than somebody might come to the idea of copying or mounting the system-provided CA file
/etc/pki/tls/certs/ca-bundle.crt

into the config directory and change the mandatory value for
plugins.security.ssl.transport.pemtrustedcas_filepath

to that file.
If you do so with AmazonLinux 2 based containers, OpenSearch starts.
If you do the same with AmazonLinux 2023 based containers, OpenSearch fails to start, as the certificate file seems to exceed some header sizes and it tries to load the "bloated" CA file with old certs from AL2023.
We saw this message in our logging after we switched to the new version of your container. Replacing the CA file with a correct one (not containing a lot of old certs) fixed the issue. But still, this is wrong having such old certs in a distro / container.
["javax.net.ssl.SSLProtocolException: The size of the handshake message (40539) exceeds the maximum allowed size (32768)"

New finding ... your documentation on DockerHub became outdated as well with that change. https://hub.docker.com/r/opensearchproject/opensearch
Note: OpenSearch images use [Amazon Linux 2](https://aws.amazon.com/amazon-linux-2/) as the base image. If you are using [Docker Desktop](https://www.docker.com/products/docker-desktop/), then we recommend configuring Docker to use a minimum of 4 GB of your system memory.

Thanks @TheRealBro , I just updated the descriptions now.

Hi @bbarani @peterzhuamazon , is there any action item from our end related to the issue.

Pending: https://github.com/amazonlinux/amazon-linux-2023/issues/471

I am closing this issue as no longer expired CA certs in AL2023, AL2 bundle cert.
Please refer the validation on https://github.com/amazonlinux/amazon-linux-2023/issues/471#issuecomment-2000257227 for AL2023, and https://github.com/amazonlinux/amazon-linux-2023/issues/471#issuecomment-2000260325 for AL2.
please feel free to reopen this issue if needed.
thanks!


Update the install-fabric script & docs

Add podman to install-fabric script
Add documentation on this script

Signed-off-by: Matthew B White<EMAIL_ADDRESS>

@hyperledger/fabric-core-maintainers could you review this please?  Thankyou

@hyperledger/fabric-core-maintainers could you take a look please...


MariaDB config file is missing

hello,
At the moment, in config/autoload (https://github.com/prooph/proophessor-do/tree/master/config/autoload) exists only a

mysql_event_store.local.php.dist
postgres_event_store.local.php.dist

but the mariadb_event_store.local.php.dist is missing
I tried these configuration:
mariadb_event_store.local.php
<?php
/**
 * This file is part of prooph/proophessor-do.
 * (c) 2014-2017 prooph software GmbH<EMAIL_ADDRESS> * (c) 2015-2017 Sascha-Oliver Prolic<EMAIL_ADDRESS> *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */

declare(strict_types=1);

namespace Prooph\ProophessorDo;

use Prooph\EventStore;

/**
 * Local configuration overrides - make your adjustments here
 */
return [
    // dependencies settings
    'dependencies' => [
        'factories' => [
            EventStore\EventStore::class => [
                EventStore\Pdo\Container\MariaDbEventStoreFactory::class,
                'default',
            ],
            EventStore\Projection\ProjectionManager::class => [
                EventStore\Pdo\Container\MariaDbProjectionManagerFactory::class,
                'default',
            ],
        ],
    ],
    // prooph settings
    'prooph' => [
        'event_store' => [
            'default' => [
                'persistence_strategy' => EventStore\Pdo\PersistenceStrategy\MariaDbSingleStreamStrategy::class,
                'connection' => 'pdo.connection',
            ]
        ],
        'pdo_connection' => [
            'default' => [
                'schema' => 'mysql',
                'host' => '<IP_ADDRESS>',
                'port' => '3306',
                'user' => 'root',
                'password' => '',
                'dbname' => 'todo',
                'charset' => 'utf8',
            ],
        ],
        'projection_manager' => [
            'default' => [
                'connection' => 'pdo.connection',
            ],
        ],
    ],
];

but I get this error message:
$ php scripts/create_event_stream.php
PHP Fatal error:  Uncaught Zend\ServiceManager\Exception\ServiceNotFoundException: Unable to resolve service "Prooph\EventStore\Pdo\PersistenceStrategy\MariaDbSingleStreamStrategy" to a factory; are you certain you provided it during configuration? in /Users/sebastianblum/PhpstormProjects/proophessor-do/vendor/zendframework/zend-servicemanager/src/ServiceManager.php:681
Stack trace:
#0 /Users/sebastianblum/PhpstormProjects/proophessor-do/vendor/zendframework/zend-servicemanager/src/ServiceManager.php(757): Zend\ServiceManager\ServiceManager->getFactory('Prooph\EventSto...')
#1 /Users/sebastianblum/PhpstormProjects/proophessor-do/vendor/zendframework/zend-servicemanager/src/ServiceManager.php(200): Zend\ServiceManager\ServiceManager->doCreate('Prooph\EventSto...')
#2 /Users/sebastianblum/PhpstormProjects/proophessor-do/vendor/prooph/pdo-event-store/src/Container/AbstractEventStoreFactory.php(83): Zend\ServiceManager\ServiceManager->get('Prooph\EventSto...')
#3 /Users/sebastianblum/PhpstormProjects/proophessor-do/vendor/proop in /Users/sebastianblum/PhpstormProjects/proophessor-do/vendor/zendframework/zend-servicemanager/src/ServiceManager.php on line 681

You have to add that class, too. I don't know which file from my head, look
into that config folder, you'll find the configs for the other
implementations as well.
On Oct 28, 2017 05:03, "Sebastian Blum"<EMAIL_ADDRESS>wrote:

hello,
At the moment, in config/autoload (https://github.com/prooph/
proophessor-do/tree/master/config/autoload) exists only a

mysql_event_store.local.php.dist
postgres_event_store.local.php.dist
but the mariadb_event_store.local.php.dist is missing

I tried these configuration:
mariadb_event_store.local.php
 * (c) 2015-2017 Sascha-Oliver Prolic  * * For the full copyright and license information, please view the LICENSE * file that was distributed with this source code. */declare(strict_types=1);namespace Prooph\ProophessorDo;use Prooph\EventStore;/** * Local configuration overrides - make your adjustments here */return [    // dependencies settings    'dependencies' => [        'factories' => [            EventStore\EventStore::class => [                EventStore\Pdo\Container\MariaDbEventStoreFactory::class,                'default',            ],            EventStore\Projection\ProjectionManager::class => [                EventStore\Pdo\Container\MariaDbProjectionManagerFactory::class,                'default',            ],        ],    ],    // prooph settings    'prooph' => [        'event_store' => [            'default' => [                'persistence_strategy' => EventStore\Pdo\PersistenceStrategy\MariaDbSingleStreamStrategy::class,                'connection' => 'pdo.connection',            ]        ],        'pdo_connection' => [            'default' => [                'schema' => 'mysql',                'host' => '<IP_ADDRESS>',                'port' => '3306',                'user' => 'root',                'password' => '',                'dbname' => 'todo',                'charset' => 'utf8',            ],        ],        'projection_manager' => [            'default' => [                'connection' => 'pdo.connection',            ],        ],    ],];

but I get this error message:

$ php scripts/create_event_stream.php
PHP Fatal error: Uncaught Zend\ServiceManager\Exception\ServiceNotFoundException:
Unable to resolve service "Prooph\EventStore\Pdo\PersistenceStrategy\MariaDbSingleStreamStrategy"
to a factory; are you certain you provided it during configuration? in
/Users/sebastianblum/PhpstormProjects/proophessor-
do/vendor/zendframework/zend-servicemanager/src/ServiceManager.php:681
Stack trace:
#0 /Users/sebastianblum/PhpstormProjects/proophessor-
do/vendor/zendframework/zend-servicemanager/src/ServiceManager.php(757):
Zend\ServiceManager\ServiceManager->getFactory('Prooph\EventSto...')
#1
/Users/sebastianblum/PhpstormProjects/proophessor-
do/vendor/zendframework/zend-servicemanager/src/ServiceManager.php(200):
Zend\ServiceManager\ServiceManager->doCreate('Prooph\EventSto...')
#2
/Users/sebastianblum/PhpstormProjects/proophessor-
do/vendor/prooph/pdo-event-store/src/Container/
AbstractEventStoreFactory.php(83): Zend\ServiceManager\
ServiceManager->get('Prooph\EventSto...')
#3  /Users/sebastianblum/
PhpstormProjects/proophessor-do/vendor/proop in /Users/sebastianblum/
PhpstormProjects/proophessor-do/vendor/zendframework/zend-
servicemanager/src/ServiceManager.php on line 681

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
, or mute the thread

.

@prolic thank you for the quick reply. I created the new config file and replaced MySQL to MariaDB.
Where do I configure the factory?


Update relevant resources to refer to Data Registry

[x] Kingfisher Collect ReadTheDocs
[ ] Data use tutorials?

@camilamila @yolile Can you check whether any of the data use tutorials ought to be updated to refer to the data registry? https://www.open-contracting.org/resources/?tab=learning-library&learning-resource-category=use

Hmm, there are some of them that are about using OCDS in a tabular format. That tabular format is the current flatten tool format. Do we want to update those resources to refer to flatterer format?

We can, but that's maybe a separate issue.
Don't our materials have a step like "get OCDS data"? In any case, getting OCDS data is necessary for any use, so we should have at least one sentence pointing people to the registry.
I thought I remembered some materials that used Kingfisher Collect directly. We should add a sentence pointing people to the registry (we can still keep the Collect content, but it's for more advanced needs).

Yes, but then the guidance uses the "flatten tool" format for exploring/using the dataset, so for example, if I'm following the guidance, download the data from the registry, and want to go to the next step in the guidance the format won't be the same as the data I downloaded. I guess we could say something about the different format in the same little box.

For the other issue about flatterer, we can add a link to the Google Doc at https://www.open-contracting.org/resources/flatten-and-unflatten-ocds-data-notebook/
Where do you want to track those issues – in the CRM or an issue-only GitHub repository?

Yes, but then the guidance uses the "flatten tool" format for exploring/using the dataset, so for example, if I'm following the guidance, download the data from the registry, and want to go to the next step in the guidance the format won't be the same as the data I downloaded. I guess we could say something about the different format in the same little box.

Aha, yes, we can make a note like:

If a publisher only offers JSON files, use the OCP Data Registry to access all OCDS datasets worldwide. The Excel files from the Data Registry may have different column names and sheet names than those in this tutorial.

I've updated all the resources now


In collection view, fix rendering of falsy field values

- Summary
Fixes #462. Logical OR was used to provide a fallback value of '' when field data cannot be found during card rendering in collection view. With boolean widgets, field values can now be falsy and this was trapping the string representation of false (and other falsy values). Rewrite to use Map API notSetValue instead.
- Test plan
All jest tests passing. Not covered in test suite.
Tested in browser using issue steps to repro.
- Description for the changelog
Boolean data field values are rendered accurately in collection view.
- A picture of a cute animal (not mandatory but encouraged)

@eamonnbell this would regress the fix provided in #419.

No worries. Seems like more general consideration of entry editing validation and tolerance for missing/null field data #464 will affect this so will hold off on a new PR until this becomes clearer.

Alrighty - closing for now, feel free to re-open if/when ready.