A question about the evaluation code

Hello,
Thank you for sharing the code for this great project!
I have a question about the ROI experiment.
In "scripts/evaluate_changes_clevr.py" and "scripts/evaluate_reconstruction.py",  https://github.com/he-dhamo/simsg/blob/31df608cd04facb2b8b546cc6f53d84716117bdf/scripts/evaluate_changes_clevr.py#L413
https://github.com/he-dhamo/simsg/blob/31df608cd04facb2b8b546cc6f53d84716117bdf/scripts/evaluate_reconstruction.py#L236
it seems that ROI focuses on the first object (s==0). From my understanding, ROI should focus on the modified object (corresponds to "new_ids" in the code). Is this for any other specific purpose or did I miss something in the code?
Thank you very much for you time!

Thank you for noticing and mentioning the issue. We fixed the code in evaluate_changes_clevr.py and changed "s" to "subject_node". However, the similar code in evaluate_reconstruction is correct since imgs.shape[0] corresponds to the objects in the scene and not the batch number after applying the process_batch function.


*: fix multiple unit test errors in local environments

Signed-off-by: Yilin Chen<EMAIL_ADDRESS>
What is changed and how it works?

Issue Number: Close #12390
What's Changed:

1. Relax the IO load info assertion from "assert_eq" to assert "starts with".
So the test won't fail on Linux 4.19+ because of the extra fields.

2. Enable the `testexport` feature of `api_version` in the `dev-dependencies`
of `tikv`. Then, it is not necessary to specify the `testexport` feature manually
to compile tikv tests.

3.  For `plugin_registry` tests, search the dynamic library under the same
directory with the test binary. This avoids failures when people are running the
tests not under the cargo root or the default target directory path is changed.

Check List
Tests

Unit test
Manual test (add detailed scripts or steps below)

Release note
None

/merge

/test


Add RF 3.2 parser features to syntax highlighting

I've barely dug into the RF 3.2 CHANGELOG for new syntax features, but it's probably worth revisiting at this point. For example, I noted that ${{ any.old.python() }} is a (terrifying) thing.

This is now generally available (along with IF from https://github.com/MarketSquare/jupyterlab_robotmode)!

That reminds me that I should make a release. The master works with RF 4.0.x already.

Also, how you been?!

Aside from slowly getting crazy by working at "safe shared home office" for the last 14 months, been working a lot around Camunda for orchestrating both humans and robots.

Low code process digitizing platform (still WIP): http://datakurre.pandala.org/2020/05/vasara-bpm-open-source-mashup/
Helping users through complex epics with Camunda: http://datakurre.pandala.org/2021/03/implementing-user-epics-bpmn-plone-volto/
Automating Camunda tasks with Robot Framework: https://gitlab.com/atsoukka/robot-rpa-playground/
Building a FaaS for that: http://datakurre.pandala.org/2021/04/camunda-nomad-robotframework-rpa/

How are you? Just yesterday shared one more time your old RF Blocky demo.

orchestrating both humans and robots.

Those look rad. I see a lot of benefit to science in having solid open-source, on-prem tooling. It's cool you've been working with hasura... i'd love to get a chance to work with that stack. In a JupyterHub setting, I could see hasura as the "heavy duty" OLTP side of the house for an organization's bespoke domain data, and use the schema federation stuff (available from a few GraphQL servers) to tie in other related resources: e.g. available packages from your package repository, meetings in your calendar, datasets in your data catalog, runs of your pipelines. I'm really interested in dagster, and have done a few small, stumbling steps towards integrating that into a hub, with this binder.
Regarding "orchestrating people": we've all had to deal more with telepresence, and we've been working on jupyter-videochat, currently only backed by Jitsi. I'm hoping to start (ab)using their XMPP bus to build some pretty things, starting with polls, but working up to breakout rooms, drawio, etc. and integrating them into computable artifacts.
On the diagram front: your stack looks really nice, and you didn't have to do too much of it, which is a big win. I'm always stuck having to either do stuff that diagram packages don't know, or don't scale, or whatever.
Just a couple weeks ago dropped a lab-3 compatible version of ipydrawio which ships with pretty rich pictures (not so much models) which include some of the glyphs needed there. It's the first thing i've done that (almost) correctly abstracted out the model from the Big Three renderers in lab (MIME, Jupyter Widget, Document). We've also been working on ipyelk which has the best open source layout engine out there.

tried xeus-robot

I see some lovely things happening there, but yeah, I like the toys we have over here.

playground demo

As you mention playgrounds... we've been hustling on jupyterlite to reboot what was started on jyve and a few other places: a purely client-side implementation of lab and all the relevant server pieces. Given that robot is still blissfully low-dependency, and something like IPython/xeus will eventually be part of that stack, i would not rule out our ability to deliver a working robot kernel playground served from the browser, the diagram stuff, video chat, etc. It'll come.

your old RF Blocky demo.

Aw, man, they've done so much cool stuff with that since I worked with it last. I need to warm jupyterlab-outsurce back up for lab 3. Now that I've paid the price on really groking custom comms (the underbelly of jupyter widgets) and the split renderers on drawio, I could see using the new libdoc JSON (or LSP, or something) to build really nice blocks automatically at runtime. Or maybe it's not blockly at all, but drawio, which would provide the right UI and data format.

As always, I am speechless about all the progress happening around Jupyter... :see_no_evil:

It's definitely going... places.
In today's community call (should be up on YouTube soon), there were demos
of jupyterlite (kernels in the browser... Yes, robot works) and nbterm
(notebooks in the terminal).
The real challenge is in creating and maintaining community-driven
protocols and formats that ensure all this stuff works together today and
for the foreseeable future, while still allowing for innovation!


AC accessory from homekit when not reachable

Observation
When the AC unit is not reachable over the API, the accessory disappears from the homekit UI as well as homebridge. The AC unit becomes non-reachable when someone cuts power to the AC unit OR when fairly intermittantly, LG is updating the APIs at their backend (where in there is a notification available in the LG app that the user will not be able to control the unit from within the app)
I cut power to the Ac unit and restarted homebridge. Here is what the log says:
[4/29/2021, 11:29:20 AM] [LgThinqAirConditioner] Discover found 1 total devices
[4/29/2021, 11:29:20 AM] [LgThinqAirConditioner] Registering new accessory: Bedroom 2 AC
[4/29/2021, 11:29:20 AM] [LgThinqAirConditioner] TargetHeaterCoolerStateCharacteristic: Warning: Your model may support a "drying" or "dehumidification" mode. This is NOT natively supported by Homekit, and using it may show errors in Homebridge or cause temporary instability.
[Bedroom 2 AC@@Filter Change Indication] Characteristic not in required or optional characteristic section for service HeaterCooler. Adding anyway.
[Bedroom 2 AC@@Filter Life Level] Characteristic not in required or optional characteristic section for service HeaterCooler. Adding anyway.
[4/29/2021, 11:29:20 AM] [LgThinqAirConditioner] Starting refresh interval (set to 0.11 minutes)
[4/29/2021, 11:29:20 AM] [LgThinqAirConditioner] Removing offline device from HomeKit. If you need this device again, please restart Homebridge.
[Bedroom 2 AC@@Filter Life Level] characteristic value expected valid finite number and received "NaN" (number)
[4/29/2021, 11:29:21 AM] [LgThinqAirConditioner] Error renewing monitor Error: Request failed with status code 400

Workaround
To restart homebrighe each time this happens
Expected behaviour
Ability to persist the accessory, mark it as "unreachable" whenever one or more API calls fail.

Same experience. i went back to 1.13.3 to resolve sudden disappearance

I have same problem. 1.3.3 don’t solve this issue

This is a real annoyance. In my case it's simply the unreliability of LG's servers causing devices to be unresponsive. Having to re-configure room assignments and such in HomeKit every time I restart Homebridge and the AC units come back as new devices is a pain.

Hi all -- this has been fixed in the next release. Offline accessories will only be removed if explicitly asked to in the plugin configuration. Thanks for your patience!


The ability to filter tests results based on the whether the test was an OTC or at home test

Is your feature request related to a problem? Please describe.
As part of the onboarding of OTC and at home tests from the new Waters sender, state may or may not want to receive these types of tests in their primary feed. And they may change their mind.
Describe the solution you'd like

The ability for each state to specify the types of test results they want
The ability for each state to setup a secondary feed
Must be a setting
Must be consistent with FDA test authorization guidelines

Describe alternatives you've considered
Additional context
This is part of wider discussion how to handle the new Waters test data

I'd like to be able to add isNotOTC() as part of our default qualityFilter (the default quality filter is currently hardcoded near the bottom of JurisdictionalFilters.kt).     Then, if a state wishes to receive a second "feed" with everything else, we can set up a second receiver that has the reverseTheQualityFilter flag set to true.   So, for that use case, the isNotOTC() juris filter is the most useful function.
For the use case where a state wants three feeds (case quality, otc, everything else), the isOTC() juris filter is needed.  In combination with some other cleverness with qualityFilters and juris Filters, three feeds can be created.
Lastly, I think there will definitely be states who want an isOTC column in their data - this would allow us to send a single file, and states can filter.   This would require an isOTC mapper that can create a YES/NO column, or something like that.
Note:   The validation checking on the LIVD values is mediocre right now, and needs to be improved (see Giang's test results here:  https://usds.slack.com/archives/C01SK0KGVGW/p1621977249051400) which means, at least for now, we need to deal with the case where the data is erroneous, and we can't use the LIVD table to determine OTCness.    Will need to decide if we default to OTC or not OTC.   I suggest not OTC, and lean on the other checks in the qualityFilter to throw out data that is missing key info.
Note 2:  There are remaining issues with the default quality filter as well:  1) its hardcoded, and 2) There needs to be a way to set it at the organizational level, so it can be re-used and extended (or reversed!) by individual receivers.    Neither of those features is done.


Please add colab OR HF demo

need this demo page to check the example script

we are constructing hugging face demo, we will inform you as the demo is finshied :)


Update ddv4-ddsv4-series.md

Added They also support Intel® Deep Learning Boost.

@Styli365 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


SIAM style manual updated regarding font of algorithm title.

Can be any font, and the SIAM style manual will be updated. Do include instructions in the appendix about how to make the font be small caps.

Added appendix in the documentation to explain how to change the font to small caps.

Kelly Thomas confirmed on 12/9/15 that this had been added to the SIAM style manual as discussed.


Can it support loading the corresponding database in the editor (not at runtime)?

Can it support loading the corresponding database in the editor (not at runtime)? My specific case is that I want to support changing the currently effective language in real-time by modifying the passed-in index on the inspect panel during the editor period. However, I found that if KnotLocalization.Manager.Languages is empty if it's not during runtime

This way, I don't have to run the program every time, then click to switch languages, and then jump to the corresponding scene to see the effect of the switch. Instead, I can directly modify it on the inspect panel without running the program.

In runtime, components gets localized values from Manager class. It is is initialzied only in Runtime/Play Mode because it compounds raw data and might perform async operations. So it would be tricky to initialize it in Edit time every time you made a change in your Database.
/// <summary>
/// A shortcut for <see cref="IKnotManager.GetTextValue"/>. Returns text assigned to <paramref name="key"/> from <see cref="Manager"/>
/// </summary>
public static string GetText(string key) => Manager.GetTextValue(key)?.Value;

For example, the following code is used by Localized Components in runtime:
//This code will return empty string or fallback value in Edit time
KnotLocalization.GetText("key");

But you can access Database data from both Edit and Play Mode times. For example:
foreach (var databaseLanguage in KnotLocalization.ProjectSettings.DefaultDatabase.Languages)
    Debug.Log(databaseLanguage.CultureName);

That's really a pity. If there was a way to support editing to display data such as Lean Localization https://assetstore.unity.com/packages/tools/localization/lean-localization-28504  , then it would be the perfect solution

If I understand you correctly, you would like to see the the actual text behind selected key right on the text component in Edit time?
If that so, I don't think it is good idea to modify the targets of localized component without user permission in Edit time. Doing this from code automatically there might be performance issues, unwanted component modifications & prefab overrides.
If you want to see how your text for the specific languages will look on your component you can always copy-paste it from Database Editor.

Yes, I want to be able to view the actual values of the corresponding language while in edit mode and be able to switch languages. If I need to copy from the database, then I have to do it manually one by one, which takes time.

Agreed. The workaround I see is to add context-menu or button that applies the text from specific language immediatly in Edit time. Will add it to my todo-list. Thank you.

By the way, I have two usage-related questions.

Do you know how to localize an item database? For example, item names and descriptions. Currently, I am storing item data using a ScriptableObject. Do I need to add all items to the localization database and then use the getText method to retrieve the corresponding values? This seems like a lot of work, and if I delete or modify my item ScriptableObject file, it could lead to inconsistencies with the data in the localization database.
How can I better manage a growing localization database?


Add Pub/Sub subscriber role to Slurm compute node

Adding this role will eliminate "ERROR: Cannot update and notify jobs with API failures" messages in /var/log/slurm/resume.log.
Submission Checklist
Please take the following actions before submitting this pull request.

Fork your PR branch from the Toolkit "develop" branch (not main)
Test all changes with pre-commit in a local branch #
Confirm that "make tests" passes all tests
Add or modify unit tests to cover code changes
Ensure that unit test coverage remains above 80%
Update all applicable documentation
Follow Cloud HPC Toolkit Contribution guidelines #

I was wrong about mechanism by which this error occurs. We should discuss with SchedMD team whther this should be logged with "ERROR" or "WARNING" as the code outwardly appears to suggest that this ERROR should go away as soon as the script is able to read the resume.log file. Since this script itself is creating the resume.log file, it may be a "first execution" error that is either safe to ignore or able to be worked around by flushing data in earlier writes.


activate SCM publish to /httpcomponents-client-5.0.x/doc/

you can either put that as a branch to do tests, either directly in master given it's not a revolution
@michael-o

@hboutemy Could you please re-spit this PR?

@hboutemy Could you please re-spit this PR?

done
with this branch, you can/should
mvn clean site site:stage
mvn scm-publish:publish-scm

and look at the result at https://hc.apache.org/httpcomponents-client-5.0.x/doc/

done
with this branch, you can/should
mvn clean site site:stage
mvn scm-publish:publish-scm

and look at the result at https://hc.apache.org/httpcomponents-client-5.0.x/doc/

Thank you, @hboutemy. What is the plan now? Are we supposed to publish versioned reports to https://hc.apache.org/httpcomponents--/doc/ and then reference them from the main website project as URLs?

Thank you, @hboutemy. What is the plan now? Are we supposed to publish versioned reports to https://hc.apache.org/httpcomponents--/doc/ and then reference them from the main website project as URLs?

for now deploy the current SNAPSHOT, test, see the result, discuss before deciding

for now deploy the current SNAPSHOT, test, see the result, discuss before deciding

@hboutemy Could you please make the same changes to httpcore, as it is more likely to have a release soon?

@hboutemy Could you please make the same changes to httpcore, as it is more likely to have a release soon?

please publish to https://hc.apache.org/httpcomponents-client-5.0.x/doc/ and review before we test somewhere else
and I'm sure there will be improvements to discuss before talking about release (which means: content of the release will never change)

please publish to https://hc.apache.org/httpcomponents-client-5.0.x/doc/ and review before we test somewhere else
and I'm sure there will be improvements to discuss before talking about release (which means: content of the release will never change)

@hboutemy  I reviewed the staged site and it looked OK to me. I do not see any need for further improvements as far as content is concerned but admittedly I only care about javadocs and clirr (JCmpApi) reports.

@hboutemy  I reviewed the staged site and it looked OK to me. I do not see any need for further improvements as far as content is concerned but admittedly I only care about javadocs and clirr (JCmpApi) reports.

I suppose the whole team is interested
there is the discussion about unversioned vs versioned
there is more than javadoc and clirr

I suppose the whole team is interested
there is the discussion about unversioned vs versioned
there is more than javadoc and clirr


[DOR-47] Serve IIIF manifest from Rosetta

Ticket URL: https://national-archives.atlassian.net/browse/DOR-47
About these changes

Add an API call to the new IIIF manifest endpoint.
The prefix varies to the existing API endpoint, so had to add a new environment variable: _CLIENT_IIIF_MANIFEST_BASE_URL.
Add a fetch call at the record detail view to determine if the record has IIIF manifest generated. This is a bit inefficient as we have to make a request even if the record has no IIIF manifest (Raised https://national-archives.atlassian.net/browse/DOR-53 to address it).
~Add a new view at /catalogue/id/<IAID>/iiif-manifest/ to serve the manifests to the IIIF viewer JavaScript front-end.~
Decided against implementing the proxy view. Sounds like a counterintuitive idea at the moment. The manifest can link out to a lot of different resources that the viewer may want to call itself. Proxying the view, would mean having to proxy all other resources and that would require implementing quite a complicated router. It feels like this complexity shouldn't belong in the Django web application.

How to check these changes
View record detail page locally, e.g. http://localhost:8000/catalogue/id/C4700551/
Before assigning to reviewer, please make sure you have

[x] Checked things thoroughly before handing over to reviewer
[x] Checked PR title starts with ticket number as per project conventions to help us keep track of changes
[x] Ensured that PR includes only commits relevant to the ticket
[ ] Waited for all CI jobs to pass before requesting a review
[ ] Added/updated tests and documentation where relevant

Merging PR guidance
Follow docs\developer-guide\contributing.md
Deployment guidance
Follow docs\infra\environments.md

@jamesbiggs Sorry to be asking you to review this multiple times. I made an update to the code:

Only fetching IIIF manifest for the digitised records.
Only fetching IIIF manifest for templates that have the IIIF viewer.
Added tests for the records client in this PR.
Added additional tests for the record detail view in #1558. Can't do this as part of this as the unit testing for Rosetta is not working so I can't verify my tests are correct.


Add licenses

Additional choices for file licenses

Creative Commons SA was meant to be http://creativecommons.org/licenses/by-nc-sa/4.0/ which means I didn't appropriately label that. There are a number of very different CC licenses that people might like the option of. I think some way of describing them each elegantly might be a good idea too. I'll re-do this with your comments in mind.

Replaced by https://github.com/lbryio/spee.ch/pull/101


Add IHttpMediatorProxy

The majority of callers aren't concerned with the underlying mediator messaging mechanism. However, some need access to the raw HTTP message, such as for HTTP status codes.
An IHttpMediatorProxy should be added which provides the usual IMediatorProxy functionality, but also provides access to the HttpResponseMessage (and HttpRequestMessage?). This comes with the caveat that this is only implemented by HTTP-based mediator proxies.

New API surface:

IHttpMediatorProxy
HttpMediatorResult
HttpMediatorResponseBehaviour


Feature Request: Add CLI flag to read install/upgrade values from existing ConfigMap

It would be quite useful if it was possible to install/upgrade a helm chart and pass values to the chart that are persisted in another ConfigMap already existing in the cluster.  Here's a hypothetical UX to demonstrate:
% kubectl create configmap mychart-settings --from-literal=global.foo=bar --from-literal=dosomething=true
% helm install --values-configmap=mychart-settings mychart --generate-name

This allows a cluster (or namespace) to be "self describing" for a given chart.
This would enable use cases where environment specific settings can be persisted in a commonly named ConfigMap so charts can be installed across different environments and get their specializations from the cluster itself.

This seems like a subset of the behaviour of https://github.com/fluxcd/helm-controller and its stand-alone predecessor, https://github.com/fluxcd/helm-operator.
See spec.valuesFrom from Helm Controller to get a sense of what a ConfigMap or Secret used in this way might look like, and some interesting interaction possibilities, e.g. targetPath.
(For this use-case, I'd probably try to use helm-controller anyway, but if Helm supported something like this natively, then perhaps helm-controller could use it)


[AMORO-2009]: Add aws/s3/hadoop-aws and iceberg-aws as default dependenies.

Why are the changes needed?
Close #2009.
Brief change log

Add iceberg-aws as default dependenies for all module
Add hadoop-aws, awssdk to AMS module depndenies.

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[X] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? ( no)

Works in locally and minio standalone cluster.


Marking PlutusTx.Builtins.Internal -O is overkill

Currently,
-- This ensures that we don't put *anything* about these functions into the interface
-- file, otherwise GHC can be clever about the ones that are always error, even though
-- they're NOINLINE!
{-# OPTIONS_GHC -O0 #-}

Now I don't know what the problem is with GHC being clever like that (that should be documented!), but this is overkill regardless. As far as I can tell, the only thing that's always error is error :: BuiltinUnit -> a. Everything else in the module should ideally be analyzed properly. I think the right thing is to just tell GHC exactly what we mean.
error :: BuiltinUnit -> a
error (BuiltinUnit ()) = GHC.Exts.lazy (mustBeReplaced "error")

Note: in combination with #4193, we'll then want to use lazy in the BuiltinByteString functions so GHC sees those as strict in their BuiltinByteString arguments but not in the underlying ByteStrings.

Yes, it's a blunt hammer, but it works. What we really want is https://github.com/ghc-proposals/ghc-proposals/pull/415 (for essentially the same reason as the Clash folks want it).

Yes, it's a blunt hammer, but it works.

Given this, I'm marking this issue with "Low priority".


Devel merge

At this point the simulation is working in python

It was originated from the branch devel. I will make a pull request from the branch main


Screenreader activation status is not captured when application starts after the client

Extracted from https://github.com/microsoft/vscode/issues/167627#issuecomment-1407000299
Steps to Reproduce:

Enable Voice Over
Start VSCode Insiders
Application has correctly entered a11y mode, since Voice Over is able to read the contents
Status bar does not reflect the a11y mode

Version: 1.75.0-insider (Universal)
Commit: da0309f2514ac22ac82dcd080cfc764fe2a1f434
Date: 2023-01-27T14:19:56.997Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 22.2.0
Sandboxed: Yes

The problem here is that we register the listener to receive a11y event from the runtime here but in this particular scenario the event is emitted before the ready event hence we miss the signal.
@bpasero need to pick your mind here, I would like to move this event handler to main.js file before the ready event. What is the best way to update editor.accessibilitySupport configuration at this stage ?

I think a hack like this:
https://github.com/microsoft/vscode/blob/b69204b36a2ca3eb4a0ad9cfaa6dd101ca96d4ae/src/main.js#L465
https://github.com/microsoft/vscode/blob/b69204b36a2ca3eb4a0ad9cfaa6dd101ca96d4ae/src/vs/code/electron-main/app.ts#L1128
Because there is no way to talk to windows so early.
I think we can also set this early when creating the window in case the event is sent even before we open the first window:
https://github.com/microsoft/vscode/blob/b69204b36a2ca3eb4a0ad9cfaa6dd101ca96d4ae/src/vs/platform/windows/electron-main/windowImpl.ts#L1086

Thanks @bpasero , moving the a11y support configuration to https://github.com/microsoft/vscode/blob/3ec25a9fbb92d89e388c151ed56b4cca643b1cc7/src/vs/platform/windows/electron-main/windowImpl.ts#L1014-L1059 can cover both the reload as well as early trigger scenario since they are calculated for each window load operation.
However, even with the above change both https://github.com/microsoft/vscode/issues/172688 and this issue suffer from the same root cause, i-e NativeAccessibilityService is initialized earlier than AccessibilityStatus causing the observer to miss the initial _onDidChangeScreenReaderOptimized event.

@deepak1556 did you make the change that you describe above or shall I?
and @bpasero is there any way to change this?

NativeAccessibilityService is initialized earlier than AccessibilityStatus causing the observer to miss the initial _onDidChangeScreenReaderOptimized event.

@meganrogge I haven't made any changes, please feel free to make the configuration changes as well as part of the fix.

Maybe I am missing something, but why can the NativeAccessibilityService not cache the state of accessibility and then allow AccessibilityStatus to ask for it instead of relying on an event that has already fired?

Maybe I am missing something, but why can the NativeAccessibilityService not cache the state of accessibility and then allow AccessibilityStatus to ask for it instead of relying on an event that has already fired?

I think this would work. The scenario described here as well as in https://github.com/microsoft/vscode/issues/172688 are when the event has already fired when initializing the workbench, in those cases querying the status from the AccessibilityService after construction should do the trick. For other normal execution cases, the event will be a reliable indicator.


Fix the conditional expression.

realloc return is pointer. is not same 0 as a NULL....I mean style.

This particular code was not written by us.  I'd prefer to keep it in its original form (especially if it's just a style thing).


Update picgo.json

Closes #XXXX

Relates to #XXXX

[ ] I have read the Contributing Guide.

/verify

/verify


API status for pods is flaky

I have a cluster with ~130 pods.  Running back-to-back 'get pods' shows me wildly different understandings of their state, even though I can tell from docker that they have not crashed or anything.
thockin@freakshow kubernetes master /$ ./cluster/kubectl.sh get pods -l app=hostnames | awk '{print $(NF)}' | sort | uniq -c
Running: ./cluster/../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get pods -l app=hostnames
127 Running
1 STATUS
6 Unknown
thockin@freakshow kubernetes master /$ ./cluster/kubectl.sh get pods -l app=hostnames | awk '{print $(NF)}' | sort | uniq -c
Running: ./cluster/../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl get pods -l app=hostnames
82 Running
1 STATUS
51 Unknown
Nothing changed in between these calls.

cc @davidopp @dchen1107
I blame the pod cache.

@brendandburns has recently changed pod cache?
FWIW, I also observed this behavior: 19 pods Running in one call and all Unknown in the next.

Yes, I think @brendandburns's PR on pod cache #4169 should fix the problem reported here. Also it should fix the issue reported by @satnam6502 about adds-on services. I have a pending PR #4194 to have kubelet deciding on PodStatus too.

Could this have caused #3950?

@yujuhong I don't see how. I'll comment on that issue.

@yujuhong, I don't think this could be the cause of that one.

I don't think @brendandburns's PR on pod cache #4169 will fix this.  That one clears the node status.  This issue is with pod going from Running to Unknown even when nodes keep running just fine.

Totally consistent observation based on my personal experience. I just
assumed we were shooting for some kind of Hesinberg Uncertainty Principle.
S
On Thu, Feb 5, 2015 at 2:11 PM, Tim Hockin<EMAIL_ADDRESS>wrote:

I have a cluster with ~130 pods. Running back-to-back 'get pods' shows me
wildly different understandings of their state, even though I can tell from
docker that they have not crashed or anything.
thockin@freakshow kubernetes master /$ ./cluster/kubectl.sh get pods -l
app=hostnames | awk '{print $(NF)}' | sort | uniq -c
Running:
./cluster/../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl
get pods -l app=hostnames
127 Running
1 STATUS
6 Unknown
thockin@freakshow kubernetes master /$ ./cluster/kubectl.sh get pods -l
app=hostnames | awk '{print $(NF)}' | sort | uniq -c
Running:
./cluster/../cluster/gce/../../_output/dockerized/bin/linux/amd64/kubectl
get pods -l app=hostnames
82 Running
1 STATUS
51 Unknown
Nothing changed in between these calls.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4188.

Agree with @alex-mohr, #4169 clears node status only.  One possibility is that we hit transient network problem in between the calls that fails health check, so controller set node condition to not reachable, hence unknown pods.  I'll make this more robust anyway.  Other than that, it's hard to think of a reason that node status results in the flakiness.

In the absence of node information, the pod status defaults to Unknown.
Maybe there's another source of this specific problem, but the pod cache is a source of continuous problems, partly because it's not just a cache, but is implementing or duplicating a significant chunk of system logic in a half-baked manner. My goal is to eliminate it -- see #2726. Short of that, we need to at least implement #1366, eliminate nodes from the pod cache, and implement a real node cache.

I can look into this. Repro info from Tim, who said he was running on a one-node cluster but has seen the problem with multi-node clusters also:
./cluster/kubectl.sh run-container hostnames --image=kubernetes/serve_hostname --replicas=1 --port=9376 --labels=app=hostnames
./cluster/kubectl.sh expose hostnames --port=80 --container-port=9376 --selector="app=hostnames"
./cluster/kubectl.sh resize --replicas=150 rc hostnames
but I had to hack the node a bit to make it get past 100
on the node:
sysctl -w fs.inotify.max_user_instances=8192
echo "DOCKER_NOFILE=1000000" >> /etc/default/docker; /etc/init.d/docker restart (fails sometimes, dunno why)

I can verify that the situation is rather bad. Lots of fluctuation in the numbers of Pending, Running, and Unknown. serve_hostname containers on the node are exiting; I'm not sure why, or if the pod itself is terminating or just the container. Lots of the following in the log (not sure what this means yet):
Sat, 07 Feb 2015 00:06:22 +0000   hostnames-ecd2r                                    Pod                                                          failedScheduling    {scheduler }                                                 Binding rejected: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]

The pause container is also exiting, so I'm guessing that means the whole pod is exiting, not just serve_hostname...

Ugh, there is an etcd size limit you might be hitting too, I forgot.  If
you are seeing the fluctuations, maybe you got far enough, though.
On Feb 6, 2015 5:13 PM, "David Oppenheimer"<EMAIL_ADDRESS>wrote:

The pause container is also exiting, so I'm guessing that means the whole
pod is exiting, not just serve_hostname...
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4188#issuecomment-73341872
.

Just a few more observations:
This is reproducible (and a little less chaotic) with one node and 100 pods (but not with 50 pods, so it's definitely load-dependent). You can get to 100 Running pods (0 Pending or Unknown), and then a minute later a dozen or so will become Unknown, and then later go back to Running, etc. As mentioned earlier, the containers continue running on the node all this time (sudo docker ps|grep serve_hostname | wc -l), so it is definitely some kind of reporting problem.
As an aside, it looks like there is some kind of race condition with IP address allocation, as during startup (but not at steady state) a number of pods exit with the following in their log (sudo docker logs xxx):
listen tcp :9376: bind: address already in use
They do restart OK (I'm not sure if this is being restarted locally on the node or making a round-trip back to the scheduler).

Almost certainly the restart is just kubelet retrying after some time.
On Feb 8, 2015 2:57 PM, "David Oppenheimer"<EMAIL_ADDRESS>wrote:

Just a few more observations:
This is reproducible (and a little less chaotic) with one node and 100
pods (but not with 50 pods, so it's definitely load-dependent). You can get
to 100 Running pods (0 Pending or Unknown), and then a minute later a dozen
or so will become Unknown, and then later go back to Running, etc. As
mentioned earlier, the containers continue running on the node all this
time (sudo docker ps|grep serve_hostname | wc -l), so it is definitely some
kind of reporting problem.
As an aside, it looks like there is some kind of race condition with IP
address allocation, as during startup (but not at steady state) a number of
pods exit with the following in their log (sudo docker logs xxx):
listen tcp :9376: bind: address already in use
They do restart OK (I'm not sure if this is being restarted locally on the
node or making a round-trip back to the scheduler).
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4188#issuecomment-73437755
.

I found that if I comment out the line with the arrow next to it (see below) in pod_cache.cc, the Pods stop oscillating between Running and Unknown. Commenting out this line changes the logic from "if get an error from Kubelet, change pod status to Unknown" to "if get an error from Kubelet, keep pod status unchanged."
result, err := p.containerInfo.GetPodStatus(pod.Status.Host, pod.Namespace, pod.Name)
newStatus.HostIP = nodeStatus.HostIP

if err != nil {
	newStatus.Phase = api.PodUnknown  <<<------------------------
} else {

I saw in the master logs intermittent errors of this form, which was causing the pods to flip back to Unknown:
E0209 04:19:17.155149    4996 pod_cache.go:270] Error getting info for pod default/hostnames-v5drx: kubelet "kubernetes-minion-1.c.striped-torus-760.internal" server responded with HTTP error code 500 for pod default/hostnames-v5drx
This seems to correspond to lines like this in the kubelet logs:
I0209 06:38:11.104796    4704 server.go:351] GET /stats/default/hostnames-gfw5j/2bb979c5-b026-11e4-a070-42010af0f256/hostnames?num_stats=33: (218.857218ms) 500
goroutine 730 [running]:
[ ... stack trace, but they're not always the same; I'll dig into this some more, the default stack trace depth wasn't going back past the various functions that just serve up the error ... ]
However, pods still flip between Running and Pending, even though no containers are exiting on the minion, so there's another problem here too.

Thanks for investigating this!  Pods really shouldn't flip between
Running and Pending, as I believe that the only way that they go Pending
is if Pod.Status.Host is empty, and this really shouldn't happen post
scheduling, unless we are somehow dropping information.  Maybe we need to
make sure that we don't wipe out status on the error case?
--brendan
On Sun, Feb 8, 2015 at 11:53 PM, David Oppenheimer<EMAIL_ADDRESS>
wrote:

I found that if I comment out the line with the arrow next to it (see
below) in pod_cache.cc, the Pods stop oscillating between Running and
Unknown. Commenting out this line changes the logic from "if get an error
from Kubelet, change pod status to Unknown" to "if get an error from
Kubelet, keep pod status unchanged."
result, err := p.containerInfo.GetPodStatus(pod.Status.Host, pod.Namespace, pod.Name)
newStatus.HostIP = nodeStatus.HostIP
if err != nil {
newStatus.Phase = api.PodUnknown  <<<------------------------
} else {
I saw in the master logs intermittent errors of this form, which was
causing the pods to flip back to Unknown:
E0209 04:19:17.155149 4996 pod_cache.go:270] Error getting info for pod
default/hostnames-v5drx: kubelet
"kubernetes-minion-1.c.striped-torus-760.internal" server responded with
HTTP error code 500 for pod default/hostnames-v5drx
This seems to correspond to lines like this in the kubelet logs:
I0209 06:38:11.104796 4704 server.go:351] GET
/stats/default/hostnames-gfw5j/2bb979c5-b026-11e4-a070-42010af0f256/hostnames?num_stats=33:
(218.857218ms) 500
goroutine 730 [running]:
[ ... stack trace, but they're not always the same; I'll dig into this
some more, the default stack trace depth wasn't going back past the various
functions that just serve up the error ... ]
However, pods still flip between Running and Pending, even though no
containers are exiting on the minion, so there's another problem here too.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4188#issuecomment-73469290
.

I also investigated the same issue last Friday. I observed exact the same as what @davidopp described above, except the related kubelet log should be:
E0209 13:03:04.032711    5035 kubelet.go:1038] Unable to get pod with name "hostnames-zt4ct.default.api" and uid "9e39ef09-ae57-11e4-bdee-42010af0483b" info, health checks may be invalid
I0209 13:30:23.205974    5035 server.go:351] GET /api/v1beta1/podInfo?podID=hostnames-zt4ct&podNamespace=default: (346.387µs) 500

Meanwhile, I observed master is trying to query pod / and failed all the time:
E0209 23:00:13.286561    4961 pod_cache.go:255] Error getting info for pod /: kubelet "kubernetes-minion-1.c.golden-system-455.internal" server responded with HTTP error code 400 for pod /

Talked to @davidopp offline, he is going to look into why running pods go back to Pending; meanwhile, I am going to figure out Unknown cases here.

That would be great. It is very hard for me to make sense of any of the scalability experiments that I am doing while the pod status is in hysteresis.

Just to summarize:
(1) the Running<->Unknown flapping is caused by the line of code I mentioned earlier;
(2) the reason that line of code is being hit on the master is due to two errors on the kubelet (the one I identified earlier was wrong; Dawn found these):
I0209 06:42:09.303799    4704 server.go:351] GET /api/v1beta1/podInfo?podID=hostnames-v5drx&podNamespace=default: (8.82543048s) 500
E0209 04:34:13.188758    4996 pod_cache.go:270] Error getting info for pod default/hostnames-2y8ny: kubelet "kubernetes-minion-1.c.striped-torus-760.internal" server responded with HTTP error code 500 for pod default/hostnames-2y8ny
(3) we don't yet know the cause of the Running<->Pending flapping; I'm going to look into that now

(and Dawn is looking into why we're hitting those two errors on Kubelet)

Are we serving requests concurrently in Kubelet? (Is it possible not to when using go's servemux?) I don't see any locking around the pod map accesses.

This was marked for the fixit but Dawn and I are working on it. Assigned to myself.

I am also investing time writing code to try and report what is going on
with unstable cluster status. It would be good to know what you and Dawn
are doing in case I am wasting my time. Thanks.
On Tue, Feb 10, 2015 at 5:13 PM, David Oppenheimer<EMAIL_ADDRESS>
wrote:

This was marked for the fixit but Dawn and I are working on it. Assigned
to myself.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4188#issuecomment-73818573
.

This particular problem is easily reproduced manually using the instructions Tim listed, so I'm not sure it's necessary to write anything sophisticated to drive the cluster into this state.
Anyway, maybe give me and Dawn a couple of days and if we can't figure this out by then we can call in the cavalry.

Am I wrong, or are these instructions also within bounds of an e2e test? Just because our existing e2es only do one or two things doesn't mean we can't do more within O(minutes), assuming you're dealing with the same image.

The "flips back to pending" problem appears to be because updatePodStatus() writes to the cache but not back to the Pod's status. computePodStatus() initializes newStatus based on pod.Status, not based on the cached value of status. This second behavior seems wrong in light of the first behavior. However, I believe this only causes a problem in combination with my fix described earlier, which as a result doesn't actually do what I described (it doesn't "keep the status as-is" but rather copies it out of the pod's status; to "keep the status as-is" it should be copying it out of the cache). I can see if this fixes things.
(We also should fix the root cause stuff on the node side, which Dawn is working on.)

Assign the issue to me ...
I didn't see the flips between Pending and Running anymore. Don't know why. I consistently see flips between Unknown and Running on those heavily loaded nodes. The root issue is once a while docker inspect API call returns us EAGAIN. Please note that on my test nodes, I already increase NOFILE limit for docker daemon process.
I0211 18:44:31.732281   27704 kubelet.go:1559] Query docker container info failed with error: dial unix /var/run/docker.sock: resource temporarily unavailable
I0211 18:44:31.732359   27704 server.go:351] GET /api/v1beta1/podInfo?podID=hostnames-bxfcy&podNamespace=default: (3.832648315s) 500

The proposed solution is that kubelet deals with all errors internally except EAGAIN one. In this case, computePodStatus logic in pod_cache does nothing when p.containerInfo.GetPodStatus returns an error. Working on a PR to fix this.

Dawn, my suggestion is that computePodStatus() should return the cached value whenever it gets an error from Kubelet. I can implement this if you want.

@davidopp , why shouldn't updatePodStatus simply write through to the pod's status? I'd think either we always read the cached value first, or we always write through to the pod and read from there. Only reading the cached value upon an error seems counter-intuitive to me...

@davidopp why do you computePodStatus returns a cached value here? The only place calls computePodStatus is updatePodStatus, which triggered by two operations: 1) periodically update all containers 2) the client asks for PodStatus, and there is no cached one, instead calling computePodStatus to retrieve one. I think a cleaner way is

Kubelet handles all the errors except this transient one. Of course, we need to make sure docker is auto-restart and there is no too many open files error on node side too. But they are separate issues and should be handled by node side through script or configure etc.

Now back to master side, if node status is ok, kubelet should return something; if there is an error from kubelet, it should be transient; and if there is a cached one, simply return cached one upon request; if no cached one, it should be generated by computePodStatus in next round.

I have one working PR to avoid the flips between Running and Unknown, but with increasing number of Pending from node side caused by docker failure. Still investigating it...

@dchen1107 I didn't understand "if there is an error from kubelet, it should be transient; and if there is a cached one, simply return cached one upon request; if no cached one, it should be generated by computePodStatus in next round." If you're talking about the caching in the podCache on the master, then what you wrote is exactly what I was suggesting. (If you're talking about some kind of caching on the Kubelet, then that's different, because I am not aware of  cache for status on the Kubelet.)
@yujuhong I think always writing back to the pod's status might be fine but I don't know why the podCache was designed the way it was, so I didn't want to change that without asking Daniel first (I think he's the one who created it). I wasn't suggesting to only read the cached value upon an error; I meant always read the cached value under all circumstances.

@dchen1107 and @davidopp, here is my understanding. Correct me if I am wrong.
UpdateAllContainers periodically updates all containers, but it gets the initial pods from etcd through this line pods, err := p.pods.ListPods(ctx, labels.Everything()) .

For each pod from pods,  UpdateAllContainers calls updatePodStatus
updatePodStatus passes pod to computePodStatus.
computePodStatus computes and returns a new status. Note that the status is computed based on pod, i.e., the information in etcd.
updatePodStatus updates the pod cache with the new status. Note that the new status is not written to etcd.

If you repeat the same steps again, you will start with the stale pod status in the etcd because updatePodStatus does not check the cached value.

I have tested #4376 since last night. The flaps between Running, Pending and Unknown are gone for about 10 hour running 300 pods on 4 nodes except two scenario:

etcd issue:
cat kube-apiserver.log | grep "status to unknown"

I0212 20:18:30.119078   31254 pod_cache.go:175] node doesn't exist: 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0] , setting pod hostnames-yuy8d status to unknown
...
This happens a couple of times last 10 hours. We need to figure out why.

NodeStatus becomes UNREADY. It happens once last 10 hours, and pods status on that node become Unknown which is expected. I didn't figure out why NodeStatus was UNREADY then, but I heard there is a network earlier this morning.

@dchen1107 up to you whether to reopen this issue or file new ones for new issues.

@dchen1107 I've also seen the "All the given peers are not reachable" message (see my second entry in this issue). I think that was what @thockin was referring to when he said "there is an etcd size limit you might be hitting too" but I may be mis-interpreting.

That error is the etcd client's catch-all for "something went wrong" - it's
actually really bad that it obscures errors.
On Thu, Feb 12, 2015 at 9:32 PM, David Oppenheimer<EMAIL_ADDRESS>
wrote:

@dchen1107 https://github.com/dchen1107 I've also seen the "All the
given peers are not reachable" message (see my second entry in this issue).
I think that was what @thockin https://github.com/thockin was
referring to when he said "there is an etcd size limit you might be hitting
too" but I may be mis-interpreting.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4188#issuecomment-74207450
.

https://github.com/coreos/go-etcd/issues/185
On Fri, Feb 13, 2015 at 9:32 AM, Tim Hockin<EMAIL_ADDRESS>wrote:

That error is the etcd client's catch-all for "something went wrong" -
it's actually really bad that it obscures errors.
On Thu, Feb 12, 2015 at 9:32 PM, David Oppenheimer <
<EMAIL_ADDRESS>wrote:

@dchen1107 https://github.com/dchen1107 I've also seen the "All the
given peers are not reachable" message (see my second entry in this issue).
I think that was what @thockin https://github.com/thockin was
referring to when he said "there is an etcd size limit you might be hitting
too" but I may be mis-interpreting.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4188#issuecomment-74207450
.

@davidopp and @thockin Yes, that error message is cache-all error message, which need to investigation. In my particular case, it shouldn't be etcd size limits at all since we have that cluster built and upgraded more tha


Feature/89 170 performance improvments

I was thinking about adding more performance improvements to this, but I decided that this was a good enough starting point. I want to see how long it takes to generate all of these indexes.
Related Issues:

EQ-89
EQ-170

Main Changes:

Added indexes to any columns we plan to query against.
Switched from using distinct queries to using recursive queries. This improves performance by emulating a loose scan index (currently not supported by postgres).
Removed the assessmentUnitStatus field from tmdl, because this field is not in our tmdl table.
Updated how our counts work. Apparently it is faster to do count(*) than it is to do count(primary_key_column).

Steps To Test:

Add CREATE_INDEXES_AFTER_DATA=true to your etl/.env.local file
Run npm run etl_database
Verify the indexes were added
Verify the app runs

TODO:

[ ] Test the index creation in cloud.gov
[ ] Get some index creation timing information from the logs
[ ] Do some testing to see if there are indexes we can delete
[ ] Further tune performance of commonly run queries (could involve creating materialized views)

@maxdiebold-erg
I skipped some of those indexes on purpose, because we don't have any UI elements for filtering on some of these fields. It is technically possible for people to still query against these fields by hitting the API directly. The idea for omitting some of these indexes is to save on disc space for indexes that are likely to never be used. Some of the indexes that I added may be overkill and we may need to remove some of these in the future.
I see that the ones you mentioned above were missing because of configuration issues, so I'll go ahead and add in all of the indexes you mentioned above.
Here are some responses to your questions/thoughts above

I noticed that we're indexing some of the columns with list values, like delisted, inindiancountry, confirmed, includeinmeasure, pollutantindicator, usesupport, and vision303dpriority, but not cwa303dpriorityranking or organizationtype. Was this a design choice?
This was done on purpose, to save on disc space for fields that are likely to never be queried against.

I also noticed that every index includes NULLS LAST, but I don't think this will cause a decrease in performance.
Postgres gives you an option to either do NULLS LAST or NULLS FIRST. In our case we are never going to be querying for nulls, so we should get a little performance boost by putting the nulls at the end.

Since reportingcycle is required in our queries, we might benefit from creating composite indices with reportingcycle as the major column.
I considered doing composite indexes, but the extra disc space isn't really worth it. Postgres can utilize multiple indexes in a single query plan. I didn't see much of a performance gain when compairing composite indexes vs having postgres use multiple indexes.

Should the TMDL profile have the "State" filter? I noticed it isn't there.

@cschwinderg That makes sense. For the NULLS LAST point, I realize the benefit, I just meant it's being included on non-nullable fields, but still shouldn't hurt.
It looks like "State" is in the TMDL table, I'll go ahead and add that to the filters.


Feat: Base interface & documentation

Issue being fixed or implemented
This PR brings discussion around the basis of the interface we want for DashJS.
Right now, specification of DashJS is to have an abstraction around Wallet-lib, DPP and DAPI-Client, in order to allow users to just care about instantiating DashJS.SDK and being able to fetchDocuments easily as well as publishDocuments.
This will be probably done with a wrapper around those dependencies and re-implementing them here (excluding contractId when we can).
What was done

Basic TS structure + tests
Basic SDK interface + Platform + Wallet/Account access.
SDK.getDAPIInstance()
SDK.addSchema()
SDK.getSchemas()
Feat : Platform.documents.fetch (by dot-notation locator - abstracting contract id)
Feat : Platform.documents.create
Chore : Placeholder for platform.(documents|contracts|identities)
Advanced documentation + it's content (docsify with search)

@davidka Any thoughts about this one and structure / interface ?
Would you put a review on it ?
We would put new feature as additional PR, however if the structure is not fine, let's change it as soon as we can :)

@Alex-Werner I can't run the tests. Does it work for you?

I can't build the project because of some inconsistences with wallet-lib.

src/DashJS/SDK/SDK.spec.ts:20:23 - error TS2339: Property 'offlineMode' does not exist on type 'Wallet'.

20     expect(sdk.wallet.offlineMode).to.be.equal(true)
                         ~~~~~~~~~~~

src/DashJS/SDK/SDK.spec.ts:24:23 - error TS2339: Property 'offlineMode' does not exist on type 'Wallet'.

24     expect(sdk.wallet.offlineMode).to.be.equal(false)
                         ~~~~~~~~~~~

src/DashJS/SDK/SDK.ts:35:34 - error TS2345: Argument of type '{ offlineMode: boolean; } | { offlineMode: boolean; schema?: object | undefined; network?: "livenet" | "testnet" | undefined; mnemonic?: string | Mnemonic<object> | undefined; }' is not assignable to parameter of type 'Options | undefined'.
  Type '{ offlineMode: boolean; schema?: object | undefined; network?: "livenet" | "testnet" | undefined; mnemonic?: string | Mnemonic<object> | undefined; }' is not assignable to type 'Options'.
    Types of property 'mnemonic' are incompatible.
      Type 'string | Mnemonic<object> | undefined' is not assignable to type 'Mnemonic<object> | undefined'.
        Type 'string' is not assignable to type 'Mnemonic<object> | undefined'.

35         this.wallet = new Wallet({...opts, offlineMode: !(opts && opts.mnemonic)});
                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You told me to use this branch docs/typescript but it does not seem to work

Interestingly, this is the second time that we have un-sync issue on our TS compiler.
It is possible that you have a globally installed old version or something similar ?

This is as far as I could get with the current state of DPNS and DAPI-Client.
I think this is a good implementation that does provide a nice solution (dot location) for abstracting schema with no limitation.
I'm also fan of the doc, if I get any approval of this PR from @dashevo/backend we will be able to put it on a pages.github.com =D

@Cofresi @thephez Thank you for your reviews, all your proposed changed has been applied (except Cofresi, I switch from pay-to to Pay-to for sake of a new sentence having an UpperCase.


[Enhancement]: Allow configuration of what files are copied into the container for docker compose

Module
Core
Proposal
The current docker compose support copies all files that are in the directory of the docker compose file into the container that runs the docker compose. This leads to Out Of Memory exceptions in case there are a lot of files in that directory (or subdirectories).
I would like to make it possible to restrict the files that are copied via an inclusion mechanism. I will open a PR with a possible implementation which we then further can discuss.

Just a question: is there a reason, why all files of the folder where the compse file is located in, have to be copied?


Johnson's Algorithm in C, C++, Java and Python

Feature = Johnson's Algorithm

Johnson's algorithm is capable of finding the shortest paths between all pairs of vertices, even in the presence of negative edge weights.
It uses the Bellman-Ford algorithm to handle negative edge weights and identify negative cycles
By transforming the graph and modifying the edge weights, it ensures that Dijkstra's algorithm can be applied effectively.

Appraoch :
1.Graph Transformation:

Add a new vertex to the graph and connect it to all existing vertices with zero-weight edges.
Assign zero weights to these new edges.

Bellman-Ford Algorithm:

Use the Bellman-Ford algorithm to calculate the shortest distances from the newly added vertex to all other vertices in the graph.
If a negative cycle is detected during this step, terminate the algorithm as it indicates that the graph contains no shortest paths.

Graph Modification:

Modify the weights of the original graph based on the results of the Bellman-Ford algorithm.
For each edge (u, v) in the graph, update its weight as the sum of its original weight and the distance from the newly added vertex to u minus the distance from the newly added vertex to v.

Dijkstra's Algorithm (Multiple Times):

Apply Dijkstra's algorithm to each vertex in the modified graph to find the shortest paths from that vertex to all other vertices.
This step is performed multiple times, once for each vertex in the graph.

Additional context

@Kumar-laxmi I would like to work on this issue. Please assign it to me

@Kumar-laxmi  kindly assign this to me under SSOC'23. I'm ready to contribute in all 4 languages

@Kumar-laxmi Kindly assign this issue to me. I would like to work on this issue under SSOC'23.

Assigned!
@Shankhadweep : C, C++, Python and Java

@Kumar-laxmi Please assign this issue to me I would like to work on it.
Thank you!

Assigned!
@tarunvyshnav777 : C, C++, Java & Python

if any one is not doing these algo let me know i would like to work on this @Kumar-laxmi  assign it to me
thank you

I'm working on it. By the end of today, I will my pr


List.length and LazyList.length don't work

List.length and LazyList.length always return 0 with their current tail-recursive implementation.
I think they need to be implemented similarly to in LinearSeqOptimized in 2.12. I don't know if there should be a similar trait in the strawman from which both List and LazyList should inherit.

Thanks for reporting this!


cannot connect via Thunderbolt 3

Describe the bug
I am connecting via a Thunderbolt 3 cable but cannot use the k4aviewer to access the images. The camera is still recognised by lsusb and can be used as a regular webcam (guvcview and cheese show the colour images).
To Reproduce

Connect the Azure Kinect via a Thunderbolt 3 cable, e.g. I am using this: https://www.amazon.co.uk/Belkin-Thunderbolt-USB-C-Certified-40Gbps/dp/B072KPBKS3
start k4aviewer
see error

Expected behavior
k4viewer should read colour and depth images.
Logs
when using k4aviewer:
libusb: error [submit_bulk_transfer] submiturb failed error -1 errno=2
[2021-07-19 15:43:22.700] [error] [t=15412] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/usbcommand/usbcommand.c (748): usb_cmd_io(). Error calling libusb_bulk_transfer for initial tx, result:LIBUSB_ERROR_IO
[2021-07-19 15:43:22.700] [error] [t=15412] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/usbcommand/usbcommand.c (805): usb_cmd_io(usbcmd_handle, cmd, p_cmd_data, cmd_data_size, p_data, data_size, NULL, 0, bytes_read, &cmd_status) returned failure in usb_cmd_read()
[2021-07-19 15:43:22.700] [error] [t=15412] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/depth_mcu/depth_mcu.c (126): usb_cmd_read(depthmcu->usb_cmd, DEV_CMD_DEPTH_READ_PRODUCT_SN, NULL, 0, (uint8_t *)temp_serial_number, sizeof(temp_serial_number) - 1 , &bytes_read) returned failure in depthmcu_get_serialnum()
[2021-07-19 15:43:22.700] [error] [t=15412] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/sdk/k4a.c (144): depthmcu_get_serialnum(device->depthmcu, serial_number, &serial_number_size) != K4A_BUFFER_RESULT_SUCCEEDED returned failure in k4a_device_open()

when using AzureKinectFirmwareTool -q:
 == Azure Kinect DK Firmware Tool ==
libusb: error [submit_bulk_transfer] submiturb failed error -1 errno=2
[2021-07-19 15:43:35.414] [error] [t=15446] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/usbcommand/usbcommand.c (748): usb_cmd_io(). Error calling libusb_bulk_transfer for initial tx, result:LIBUSB_ERROR_IO
[2021-07-19 15:43:35.414] [error] [t=15446] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/usbcommand/usbcommand.c (805): usb_cmd_io(usbcmd_handle, cmd, p_cmd_data, cmd_data_size, p_data, data_size, NULL, 0, bytes_read, &cmd_status) returned failure in usb_cmd_read()
[2021-07-19 15:43:35.414] [error] [t=15446] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/depth_mcu/depth_mcu.c (126): usb_cmd_read(depthmcu->usb_cmd, DEV_CMD_DEPTH_READ_PRODUCT_SN, NULL, 0, (uint8_t *)temp_serial_number, sizeof(temp_serial_number) - 1 , &bytes_read) returned failure in depthmcu_get_serialnum()
[2021-07-19 15:43:35.414] [error] [t=15446] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/firmware/firmware.c (486): firmware_get_serial_number(). Failed to get serial number length

[2021-07-19 15:43:35.486] [error] [t=15446] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/usbcommand/usbcommand.c (30): TraceLibUsbError(). /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/usbcommand/usbcommand.c (453): libusb_claim_interface(usbcmd->libusb, usbcmd->interface) returned LIBUSB_ERROR_NOT_FOUND in usb_cmd_create
[2021-07-19 15:43:35.486] [error] [t=15446] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/usbcommand/usbcommand.c (30): TraceLibUsbError(). /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/usbcommand/usbcommand.c (495): libusb_release_interface(usbcmd->libusb, usbcmd->interface) returned LIBUSB_ERROR_NOT_FOUND in usb_cmd_destroy
[2021-07-19 15:43:35.486] [error] [t=15446] /__w/1/s/extern/Azure-Kinect-Sensor-SDK/src/color_mcu/color_mcu.c (74): usb_cmd_create(USB_DEVICE_COLOR_IMU_PROCESSOR, device_index, NULL, &colormcu->usb_cmd) returned failure in colormcu_create_by_index()
ERROR: Unable to find a device

Desktop (please complete the following information):
This happens on Ubuntu 20.04 and Windows 10.
Firmware version:
  RGB camera firmware:      1.6.110
  Depth camera firmware:    1.6.79
  Depth config file:        6109.7
  Audio firmware:           1.6.14
  Build Config:             Production
  Certificate Type:         Microsoft

Additional context
I used the same cable to connect an Intel RealSense to an Android phone and that worked without issues.

It is compatible with USB 2 because it is an active cable of Thunderbolt 3. It is not compatible with USB 3.
Therefore, it cable can not be use with Azure Kinect.
https://www.belkin.com/us/cables/data/thunderbolt-3-cable-usb-c-to-usb-c-100w-6-5ft-2m/p/p-f2cd085/

@UnaNancyOwen Thank you very much for pointing this out. The bandwidth of Thunderbolt 3 should be more than enough for USB 3 - So I thought that if Thunderbolt supports USB, it would support USB 3.
I think it would be very helpful to note in the documentation that Thunderbolt 3 cables are not supported.

By the way, the passive-cables of Thunderbolt 3 are compatible with USB 3. It should be available for Azure Kinect. :)

Also not all USB-C cables will work. There are two types of cable circulating - power only and data+power. You need a data+power USB-C cable. Unfortunately there is no easy way of determining which cable you have (except for trying it). The industry chose not to mark the cables differently.

Thanks a lot, I changed to another cable and it works!


SHA 256 mismatch when installing dbeaver using Homebrew

Description
Same issue as reported in https://github.com/dbeaver/dbeaver/issues/15054 :)
DBeaver Version
22.3.0 (I think)
Operating System
macOS 13.0.1
Database and driver
No response
Steps to reproduce
brew install --cask dbeaver-community
josh@Joshs-MacBook-Pro Movies % brew install --cask dbeaverlite
==> Downloading https://dbeaver.com/downloads-lite/22.3.0/dbeaver-le-22.3.0-macos-aarch64.dmg
==> Downloading from https://download.dbeaver.com/lite/22.3.0/dbeaver-le-22.3.0-macos-aarch64
######################################################################## 100.0%
Error: SHA256 mismatch
Expected: 699581de35f6ae2626f6f6a9c9b2b2ca3a4e6d7e9db4df0a9b577d67e23dd747
  Actual: ad0232cf395d47adefbb964af1f4c296a5c80ac21b4a6b4c327fa1681c2bda13
    File: /Users/josh/Library/Caches/Homebrew/downloads/09f4bc64bf1ba8d34124265611b9f7845998cd051ea922c1909fc2483cf88594--dbeaver-le-22.3.0-macos-aarch64.dmg
To retry an incomplete download, remove the file above.

Additional context
Tried updating brew using the following commands:
brew upgrade
brew update-reset
brew cleanup && brew update

Unfortunately, we had to rerelease this version. You can install it with --force argument.


file watcher does not work on mounted docker volumes

This isn't a bug in elm-live, rather an unfortunate side effect of how docker works.
However I'm hoping there is an option to use polling for file watching that could be implemented quickly just by adding a command line option along the lines of nodemon: https://www.npmjs.com/package/nodemon#application-isnt-restarting

I finally had some time to look at this and found two things: it was as easy to fix as I hoped it would be; and my original problem was me writing the wrong paths. Docker works fine with file watching.
Regardless the option to use polling might be useful for someone else and here is a pull request. #249

I finally had some time to look at this and found two things: it was as easy to fix as I hoped it would be; and my original problem was me writing the wrong paths. Docker works fine with file watching.
Regardless the option to use polling might be useful for someone else and here is a pull request. #249

I think I will leave this until someone else has this issue. It is intended to only be a development tool locally and want to keep features and flags from bloat unless there are a large number of necessary use cases.


Updates for TLSv1.3 draft 26

travis thinks there are memory leaks, at least (I didn't look at all failures)

Fixup commit pushed addressing the travis/appveyor failures. @richsalz please reconfirm?

Reconfirmed once the CI's pass.

Pushed. Thanks!


TypeError: next is not a function

Hi, I'm trying to add persistState , but it's giving me this error:
TypeError: next is not a function
(anonymous function)
C:/Git-Projects/reacttr/node_modules/redux-localstorage/lib/persistState.js:70
  67 |   console.warn('Failed to retrieve initialize state from localStorage:', e);
  68 | }
  69 |
> 70 | var store = next(reducer, finalInitialState, enhancer);
  71 | var slicerFn = slicer(paths);
  72 |
  73 | store.subscribe(function () {
View compiled

Here's my store.js file:
import {applyMiddleware, createStore} from 'redux';
import {composeWithDevTools} from 'redux-devtools-extension';
import ReduxLogger from 'redux-logger';
import thunk from 'redux-thunk';
import promise from 'redux-promise-middleware';
import reducer from '../reducers';
import persistState from 'redux-localstorage';

const middleware = applyMiddleware(persistState(), promise(), thunk, ReduxLogger);

const initialState = {
};

function getHeaderTooltip(headerName) {
  return "sum(" + headerName.toString() + ")";
}

export default createStore(reducer, initialState, composeWithDevTools(middleware));

I've figure out how to use it. This error happens, when we try to add redux-localstorage to applyMiddleware function, like this:
const middlewares = applyMiddleware(
  thunkMiddleware,
  persistState(['cart'])
);

createStore accepts as a second parameter middlewares or an enhancer.
Then, your code would be something like this:
import { combineReducers, createStore, applyMiddleware, compose } from 'redux';

const reducers = combineReducers({
  cart: cartReducer
});

const middlewares = applyMiddleware(
  thunkMiddleware
);

const configureStore =
  createStore(
    reducers,
    compose(
      middlewares,
      persistState(['cart'])
    )
  );

Pretty simple. I hope I still may help someone.
This issue can be closed.


User Story: Package authors can multi-target between runtime identifiers (RID)

Spec TBD

Currently multitargeting is supported via TargetFrameworks but not really for multiple RID's. In our own build, we have to do custom build gymnastics to achieve this.

The libraries team part here is representing our needs as we'd like to move over to this supported mechanism once it exists.

I think that adding a new first class concept to MSBuild, that of arbitrary build dimensions, would solve these 'we want to add yet another dimension' types of issues once and for all. A build dimension could be defined as a key value map: {foo:"bar", zoo:"roo"} {TargetFramework:"net472", RuntimeId:"win", Configuration="Debug", Architecture="x64"}. In MSBuild they could be expressed via regular items, or we could introduce new MSBuild expressions with well defined semantics. The engine could know about them to make it easier to specify multitargeting and whatnot. We could also borrow BuildXL's design of build dimensions

We should get an engineering owner assigned to this, like every P0 story. It can always change later. Is that you @marcpopMSFT or someone on your team?

My understanding is that the largest set of the work for this would be from NuGet so @aortiz-msft would probably be the M1 owner.

@aortiz-msft thoughts?

I think for this a decent amount of work needs to be done by MSBuild, NuGet and the SDK.

Yes, we discussed this in our Monday meeting last week, and this is not something we think we can deliver in NET 6.0. However, let's understand the customer feedback around this and start validating the problem and solution hypotheses.

As a head's up, the Extras supports this for the inner compile loop and building nuget packages:
https://github.com/novotnyllc/MSBuildSdkExtras#creating-per-runtimeidentifier-packages
It doesn't likely handle P2P references in an intelligent way.

I'm looking for a way to have multitargeting for different RIDs from a single class library project - including using the RID as a compile-time condition in the .csproj to reference RID-specific dependencies, like it is possible with TFMs now. This would not only enable building the correct binaries, but it would also allow for using the correct code at compile-time using #if rather than using runtime-checks like OperatingSystem.IsLinux().
My usecase would be to create a single NuGet package (class library) that has a windows-specific and a linux-specific implementation, which could be referenced through a common API surface in a consuming head project (abstracting away the platform differences). Depending on the publishing RID of the consuming head project, the nuget package for windows or linux would be restored. By using the RID as a condition in the .csproj file, additional platform-specific dependencies could be added.
Since there is no linux-specific TFM, I cannot multitarget a project in the usual way now.
See also https://github.com/dotnet/sdk/issues/27061
@terrajobst is this still targeted for the 7.x timeframe?

CC @baronfel for visibility. This is not in plans for a 7.0 release. A feature being discussed that might help here is TFM aliasing which would allow aliases to include the RID but that isn't officially planned yet.

Bulk closing .NET 6 epics and user stories. If you think this issue was closed in error, please reopen the issue and update it accordingly.

Please reopen this

Is this in the plan? This situation make me crazy.

@marcpopMSFT @baronfel @terrajobst please check if this should be reopened and if so, what release are we targeting this?

This should not be reopened as we are not planning on adding direct support for multi-targeting of RIDs. However, the nuget team is exploring TFM aliasing which would enable a form of this. The idea would be to enable the existing TFM multi-targeting to allow for RID information. It's still in design but potentially it'll end up with customers being able to multi-target "net8.0/win-x64;net8.0/win-arm64" (or something like that). We'd likely need some known aliases built into the SDK that set the RID when used but nuget would recognize those as two targets and allow restoring each separately. Customers could expand the aliasing beyond what's built in to support other scenarios we haven't thought of.
https://github.com/NuGet/Home/pull/12124


Update DeveloperGuide

This pull request includes updates to the DeveloperGuide such as the target user profile, value proposition, non-functional requirements (NFR), and the glossary. These updates provide clearer definitions and expectations for the application's use and development.

LGTM


useless 2FA

[Enter feedback here]
I was looking for information on how to disable 2FA for a shared account in O365 and it brought me to this page which is utterly useless. I don't know who thought forcing this would be a good idea, but not having information on how to turn on or off the settings is ridiculous and shows just how out of touch M$ is with their users.
I really don't think my writing anything here will change anything since whoever reads this will probably delete it immediately, but know this, another person in the world hates you for not doing your job right in the first place. Give us documentation the is actually up to date, and stop making changes without notice.
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?
Why won't this actually submit?

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

ID: 1a7c4c1e-fdcf-6a03-4fcc-ee6ea17c2583
Version Independent ID: effddaed-505b-6402-c296-03cd5f299994
Content: Manage privacy and security settings - Power Platform
Content Source: power-platform/admin/settings-privacy-security.md
Service: power-platform
Sub-service: admin
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @Sturmey66. This issue has been assigned to the doc author for review.


SSL: CERTIFICATE_VERIFY_FAILED

Hi everyone and thanks in advance for any help you can give me.
Launching 'pipreqs . ' I get the following error:
WARNING: Import named "cx_Oracle" not found locally. Trying to resolve it at the PyPI server.
Traceback (most recent call last):
File "C:\Python311\Lib\site-packages\urllib3\connectionpool.py", line 467, in _make_request
self._validate_conn(conn)
File "C:\Python311\Lib\site-packages\urllib3\connectionpool.py", line 1092, in _validate_conn
conn.connect()
File "C:\Python311\Lib\site-packages\urllib3\connection.py", line 642, in connect
sock_and_verified = _ssl_wrap_socket_and_match_hostname(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\urllib3\connection.py", line 783, in ssl_wrap_socket_and_match_hostname
ssl_sock = ssl_wrap_socket(
^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\urllib3\util\ssl.py", line 469, in ssl_wrap_socket
ssl_sock = ssl_wrap_socket_impl(sock, context, tls_in_tls, server_hostname)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\urllib3\util\ssl.py", line 513, in _ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\ssl.py", line 517, in wrap_socket
return self.sslsocket_class._create(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\ssl.py", line 1075, in _create
self.do_handshake()
File "C:\Python311\Lib\ssl.py", line 1346, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate signature failure (_ssl.c:1002)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Python311\Lib\site-packages\urllib3\connectionpool.py", line 790, in urlopen
response = self._make_request(
^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\urllib3\connectionpool.py", line 491, in _make_request
raise new_e
urllib3.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate signature failure (_ssl.c:1002)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Python311\Lib\site-packages\requests\adapters.py", line 486, in send
resp = conn.urlopen(
^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\urllib3\connectionpool.py", line 844, in urlopen
retries = retries.increment(
^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\urllib3\util\retry.py", line 515, in increment
raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded with url: /pypi/cx_Oracle/json (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate signature failure (_ssl.c:1002)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in run_code
File "C:\Python311\Scripts\pipreqs.exe_main.py", line 7, in
File "C:\Python311\Lib\site-packages\pipreqs\pipreqs.py", line 528, in main
init(args)
File "C:\Python311\Lib\site-packages\pipreqs\pipreqs.py", line 490, in init
imports = local + get_imports_info(difference,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\pipreqs\pipreqs.py", line 184, in get_imports_info
response = requests.get(
^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\requests\api.py", line 73, in get
return request("get", url, params=params, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\requests\api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\requests\sessions.py", line 589, in request
resp = self.send(prep, **send_kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\requests\sessions.py", line 703, in send
r = adapter.send(request, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python311\Lib\site-packages\requests\adapters.py", line 517, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded with url: /pypi/cx_Oracle/json (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate signature failure (_ssl.c:1002)')))
I have already tried searching the Internet and I can say with certainty that I do not use proxies, I can connect to the pypi.python.org and pypi.org sites from both browser and shell.
I added the crt of the pypi.python.org site to my pem file.
I don't know what to do anymore.
Tnx

anyone who has had and solved the same problem as me?

Hi @momift
u get this on company network?
Same here, I believe this is to the common mitm attacks companies like to do with breaking the SSL encryption and signing with a company certificate afterwards...

Using pip I can set trusted-host in ~/.pip/pip.conf or use --trusted-host argument. Can we add same option to the pipreqs?

Also facing the same issue behind a company network.


OpenRefine 3.2 does not start on macOS Mojave

Describe the bug
OpenRefine 3.2 does not start on macOS Mojave
To Reproduce

Download image and install; or install through homebrew.
Start OpenRefine

Current Results
"Butterfly is still initializing..." message received in the browser windows.
Expected behavior
OpenRefine starting page
Desktop (please complete the following information):

OS: macOS Mojave 10.14.6
Browser Version: Chrome Version 76.0.3809.100
JRE or JDK Version: JRE 1.7.0_79-b15

OpenRefine (please complete the following information):

Version: OpenRefine 3.2 for Mac

@iabaro thanks for this report.
If you have installed any extension, can you remove them and try again?

I tried that before going back to 3.1.
Thanks.

Any movement on this? Or shall I just revert back to an older version?

@kirschbombe have you tried 3.3 beta too?

@wetneb - I have not! But I'll give it a shot :) I reverted back to 3.1 for now.

@wetneb - I have not! But I'll give it a shot :) I reverted back to 3.1 for now.

@Kirschbombe : have you tried v3.3?

Since the v3.3 release has obsoleted v3.2, I'm closing this.


Remove erroneous v2.5.2 CSV from 2.6.0 directories

It was manual. It happened when we copied the 2.5.2 dir into 2.6.0 in https://github.com/maistra/istio-operator/pull/1782/commits/50c4306eba306f57bacd16e79763cd2869ee934a.


[Test][CI] ROCm4.3 COMGR '__clang_hip_runtime_wrapper.h' file not found

[Target]
Together with #1089, MIOpen CI needs to be upgraded to ROCm 4.3
[Symptom]
"Fp32 Hip Debug COMGR" stage has failed with

[2021-08-20T23:17:41.443Z] MIOpen(HIP): Warning [BuildHip] :1:10: fatal error: '__clang_hip_runtime_wrapper.h' file not found
[2021-08-20T23:17:41.443Z] #include "__clang_hip_runtime_wrapper.h"
[2021-08-20T23:17:41.443Z]          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Failed tests:

[2021-08-20T23:17:44.762Z] The following tests FAILED:
[2021-08-20T23:17:44.762Z] 	 19 - test_find_db (Failed)
[2021-08-20T23:17:44.762Z] 	 21 - test_gpu_reference_kernel (Failed)
[2021-08-20T23:17:44.762Z] 	 24 - test_handle_test (Failed)
[2021-08-20T23:17:44.762Z] 	 39 - test_reduce_test (Failed)
[2021-08-20T23:17:44.762Z] 	 66 - test_conv_igemm_dynamic_small (Failed)

[related]
https://github.com/cupy/cupy/issues/5592
https://ontrack-internal.amd.com/browse/SWDEV-290754
Having LLVM_PATH set in environment seems to have NOT resolved the issue

Correction: having correct LLVM PATH has resolved the issue.
reduce heat (urgency level) to wait for SWDEV-290754

SWDEV-290754 implemented and issue no longer found
MIOpen CI has upgraded to ROCm 4.3.1


Tiling Sprite Doesn't work when using local files not from a CDN

worked for <sprite/>, but not this.
<template>
    <tiling-sprite
<EMAIL_ADDRESS>      :anchor="0.5"
      :x="120"
      :y="120"
    />
</template>

however, using a CDN it renders fine.
<template>
    <tiling-sprite
    texture="https://pixijs.com/assets/p2.jpeg"
      :anchor="0.5"
      :x="120"
      :y="120"
    />
</template>

here is the log i would get on render
error.log
this could be me being stupid, or something else. anything's appreciated. Thanks!

Nevermind, It needs to be in the public folder. can't belive it took me 4 hours to figure that out.
TLDR; you cant get from assets folder but public is fine.

however, debug messages would still be appreciated :)


Disable the searchBar animation when presenting the search controller

I would like to disable the animation when presenting the search controller
https://www.mediafire.com/?xz757n3fyjd600r
I am using Xcode 7.3.1 and the iPhone 6 simulator

Then just present it without animation: present(controller, animated: false, completion: nil)


01bsp_lighthouse example never performs onboard lsfr count computation

Right before calling the function db_lh2_process_location(), db_lh2_stop() is called.
if (_lh2.state == DB_LH2_RAW_DATA_READY) {
    // Stop the LH2 internal engine before doing other computations/sending radio packets, etc
    db_lh2_stop(&_lh2);

    if (DB2_LH2_FULL_COMPUTATION) {
        // the location function has to be running all the time
        db_lh2_process_location(&_lh2);
    }

The STOP function changes the internal state of the LH2 engine to  DB_LH2_4_IDLE, and the process_location function immediately checks that the state is DB_LH2_4_RAW_DATA_READY
void db_lh2_4_process_location(db_lh2_4_t *lh2) {
    if (lh2->state != DB_LH2_4_RAW_DATA_READY) {
        return;
    }

Thus, in the example code, the process_location function is never executed.

Fixed by #273


SPIFFE OIDC Discovery Provider Rework

Partially fixes: https://github.com/spiffe/helm-charts-hardened/issues/151

ACME support is still not working.

[ ] - Passthrough support on spiffe-oidc-discovery-provider
[ ] - mount bundle on tests and use it to validate certs

[ ] - Switch to a released image

I tested this PR on Openshift and it seems to work with the secure connection as default:
helm-charts-hardened$curl https://oidc-discovery.XXXX.us-east.containers.appdomain.cloud/keys
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
helm-charts-hardened$curl -k  https://oidc-discovery.XXXX.us-east.containers.appdomain.cloud/keys
{
  "keys": [
    {
      "kty": "RSA",
      "kid": "XXXXX",
      "alg": "RS256",
      "n": "XXXX",
      "e": "AQAB"
    },


'stat' format sequences shouldn't be put in brackets

'stat' format sequences are wrongly put in brackets that causes their incorrect evaluation:
before spec-cleaner:
echo `stat --format="%y" ~`
output:
2015-05-04 10:38:50.031128333 +0200

after spec-cleaner:
echo `stat --format="%{y}" ~`
output:
?y}

You should properly escape your input ('%%y' is proper way) or do you expect to have %y macro?

As Tomas said. You actually have to use %%y otherwise if you define bit up something like:
%define y "fuuuuu"
it would get expanded in your date call. So the echo line should be "--format="%%y"".


I need to do copy-paste operation JsTree?

I'm implementing a tree using jstree,i need to do copy-paste operation.But i'm not able to copy a node (parent with children) and paste it to one of its child node.I'm trying it using jsTree-context-menu plugin?Copy and paste are done, but its contents are not copied!?
requirement

Node 1

Node 2
Node 3

Node 4

Assume this is my tree.I need to copy() Node 1 and need to paste under Node 2.I'm trying it using jstree-context-menu plugin and find its not working at all.
So my Result Must Be With content but content is not available.

Node 1
Node 2

Node 1      <-----Pasted item

Node 2
Node 3

Node 3
Node 4

This code for copy :
var inst = $.jstree.reference(data.reference),
    obj = inst.get_node(data.reference);
if (inst.is_selected(obj)) {
    inst.copy(inst.get_top_selected());
}

This code for paste :
var inst = $.jstree.reference(data.reference),
 obj = inst.get_node(data.reference);
 inst.paste(obj,'last');

Guide me.
Thanks in advance!

It is not possible to copy a node inside itself, as most of the time that will cause an endless loop.

The question was corrected.
Copy is done and the paste is done, but the content is not in the pasted nodes.

The answer is still the same - it is not possible to copy a node inside itself

Can you give me an example to work on a copy?

#I,m also implementing a tree using jstree ,i need to do copy-paste operation.But i'm not able to copy a node (parent with children) and paste it to some other node. Copy and paste operation are going smooth. but when i save the tree it doesn't updates the UI like this
Initial Structure

NFR (Parent)

Logging (child of NFR)
Tracing (child of NFR)

Project Vision Statement
Assume this is my tree.I need to copy() NFR along with its child nodes  and need to paste under Project Vision Statement.
After copy and paste it shows the changes like this
NFR (Parent)

Logging (child of NFR)
Tracing (child of NFR)

Project Vision Statement

NFR
-Logging

Project Vision Statement
Buyt when i save the tree and again re open it, the rendered tree body appears like this

NFR (Parent)

Logging (child of NFR)
Tracing (child of NFR)

Project Vision Statement

NFR
How do i let the child nodes of NFR to be rendered alongside with NFR?


bug:

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.0
Operating system/version
linux/manjaro
Describe the bug
When updating the plugins, the last couple 1-x run into a timeout. It is not always the same plugins, so after a couple of runs the plugins are updated completely but it is annoying
I am not sure that the root cause of this bug is lazy but i want to see if anybody else has the same issue because i'm out of ideas what else to debug on my system.
See screenshots:

Steps To Reproduce

start lazy
update with U
wait for timouts

Expected Behavior
I expect the plugin update not to run into a timout
Repro
No response

your internet connection is the root cause, or at least your computer. Check the docs and set a lower concurrency

my internet connection is fine + i already reduced the concurrency still happens

Then set config.git.timeout = false to disable the timeout

On my laptop, checking/updating takes less than 3 seconds for over 100 plugins. If you're experiencing way longer timings, then something is wrong with your internet / your router / or your computer settings

yes that's the same here only the last 1..X get stuck
i already tried to play around with git configs but with no success


Add post deletion hook to helm chart

Create a post deletion hook to delete alb-ingress-controller and external-dns which are two service accounts that are created outside of the namespace
Possible Issue: Since alb-ingress- controller and external-dns are part of the helm chart, this may require refactorization when adding 2 or 3 additional domains.

@Abhi94N from our latest conversation it seems that the alb_ingress_controller only supports one ingress object and therefore cannot handle multiple sub-domains with the same ALB. We, therefore, need to consider the alternatives we looked into yesterday, such as the NLB / ngnix combo, etc.
The other option is to not mess with sub-domains that reflect different namespaces but rather use a path-based routing mechanism with the same domain.

Closing, as these artifacts are only created if the user enables these values with helm conditionals.


Disable default Seccomp profile with privileged containers

The OCI runtime-tools generator includes a default seccomp spec we were not accounting for. Clear it for privileged containers to make sure we don't leak Seccomp into a privileged container.

LGTM and very nicely found @mheon

LGTM   podman running container buildah with bud now works!

As soon as we get the first podman out of fedora updates we should create a new one with this fix, for @ipbabble demo.