Support i128 and u128

These types gained Serialize and Deserialize impls in Serde 1.0.60 but still needs to be implemented in serde_json.

On version serde_json 1.0.89 this error is still showing up, "u128 is not supported"


request to add student pasta recipe

I have added  a new student pasta recipe

@MatjazSkrlec looks good. Please add instructions soon :)


Restore Ruby 3.4 compatibility in T::Props::Serializable

Followup: https://github.com/sorbet/sorbet/pull/7778
Followup: https://github.com/sorbet/sorbet/pull/7710
Exceptions are not guaranteed to have a #backtrace_locations because of Exception#set_backtrace and Kernel#raise(error, message, backtrace).
It's still prefereable to use #backtrace_location when present as it requires much less string parsing.
But if it's missing we can fallback to parse backtraces the old way, however we need to account for Ruby 3.4 newer format.
@froydnj @jez @paracycle

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_QRe33VxDQmlaPU

Sorry for the long review on this change. The script we used to test PRs against Stripe's codebase had atrophied and broken, and we had not gotten around to fixing it.
The script is fixed, I've tested these changes on Stripe's codebase, and everything looks great.
Thanks for the patience.


Calculation of thermodynamic observables

What is the expected behavior?
Introduced in https://arxiv.org/abs/2003.02303

moved to backlog and expose this only as a demo notebook.

Closing this issue in view of the merged tutorial in qiskit-tutorials. Will start a new one as long as we have an implementation that allow for larger than diatomic molecules to be supported.


Expand preferences for completions.

Since we've stopped getting new reports, I'd like to start expanding the sorts of completion logic we end up requesting to be a little bit more typical of what VS Code is requesting from us. The old crawler was using all of these options with the exception of includeCompletionsForModuleExports. Apparently that's only done randomly in the interest of not spending too much time in completions.
I don't know how much slower the new-errors runs will become as a result of this - I haven't tried running it. But we can always dial this back if we want.

First run is over at https://github.com/microsoft/TypeScript/issues/52645


Docs: Upgrade lakeFS

Document how to upgrade lakeFS in case of DB migration (lakefs migrate up)

The instructions will be part of the notes published with each release.


AMP downloading experimental PaperMC builds despite set to "Stable" release stream

Bug Report
System Information
Operating System
Ubuntu Server 22.04.4
AMP Version and Build Date
<IP_ADDRESS> - 20240502.1
AMP Release Stream
Mainline
I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms
What are you trying to do?
Update a PaperMC (Minecraft Java Edition) server while "Release Stream" is set to "Stable".
What are you expecting to happen?
That the latest stable Paper build, for the latest Minecraft version that has available stable Paper builds, is downloaded.
What is actually happening?
When the latest Paper build for the latest Minecraft version is classified as "experimental", which is often the case whenever a new Minecraft version has just been released (such as 1.20.6 as of writing this), AMP will download that build even though it is not "stable".
Reproduction
This issue can only be reproduced when the latest Paper build for the latest Minecraft version is classified as "experimental".

Create a Minecraft Java Edition instance with "After Creation" set to "Do Nothing".
Click "Manage" on the instance, go to "Configuration > Server Settings".
Change "Server Type" to "Paper".
Change "Release Stream" to "Beta" then back to "Stable" to mitigate #1091.
Start the server and observe that an experimental Paper build is being used according to https://papermc.io/downloads/paper.

The issue can be mitigated by specifying a specific Minecraft version in the settings, but if an experimental Paper build would be released for that version, AMP would update to it.
Maybe AMP needs to specify the update channel when retrieving the latest Minecraft version and Paper build https://docs.papermc.io/misc/downloads-api

Dude. You are double posting. Check your other issue. I already commented on it

Dude. You are double posting. Check your other issue. I already commented on it

These are two separate issues that has nothing to do with each other.


HCAP-244 Pass identifiers of every CFAR offers required to retrieve o…

…ffers data when pushing events

LGTM


Has this project been abandoned?

There has been a PR sitting for 4 months and no updates to issues since October of 2017.
This isn't really the place for this comment. I'm just hoping it gets noticed.

Hi @pauby ,
It is not abandoned, but spare time is limited.
Also, I tend not to look at PRs which fail the build.
Thank you for giving me a nudge, I'm gonna look into this PR.

Hi @pauby ,
Good news : the PR #15 has finally been merged.
Consequently, the issue #12  is solved and closed.
Thank you for your patience.


THEEDGE-3139 - Add new access to HMS Custom repos screen

Description
This PR is adding a new view that shows Custom repos have moved to HSM (https://www.sketch.com/s/ac25729e-df9b-4e74-a09c-badb62787d24/a/jgnqWLm#Inspect). Also is setting up the feature flag related to custom repos.
Fixes # (issue)
https://issues.redhat.com/browse/THEEDGE-3139
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[X] Documentation update
[X] Tests update

Checklist:

[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I run npm run lint:js:fix to check that my code is properly formatted

Codecov Report
Patch coverage has no change and project coverage change: -0.08 :warning:

Comparison is base (5316bd7) 29.98% compared to head (010518f) 29.90%.

:exclamation: Current head 010518f differs from pull request most recent head 3726605. Consider uploading reports for the commit 3726605 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #638      +/-   ##
==========================================
- Coverage   29.98%   29.90%   -0.08%
==========================================
  Files         126      127       +1
  Lines        2845     2852       +7
  Branches      881      885       +4
==========================================
  Hits          853      853
- Misses       1821     1828       +7
  Partials      171      171

Impacted Files
Coverage Δ

src/Routes/DeviceDetail/DeviceDetail.js
0.00% <0.00%> (ø)

src/Routes/DeviceDetail/DeviceDetailTabs.js
0.00% <ø> (ø)

src/Routes/Repositories/Repositories.js
0.00% <0.00%> (ø)

src/Routes/Repositories/RepositoryLinkAccess.js
0.00% <0.00%> (ø)

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

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


Button text FreeType-based outline out of sync if missing glyph exists

Godot version:

3.2.1.stable.official
4.0.dev.custom_build.5b4ea6529

OS/device including version: macOS 10.15.4
Issue description:
Button's text outline and the text itself go out of sync if there are characters not included in the font.
This does not happen to Label.

Steps to reproduce:
Add a button, make sure it's using a Dynamic Font and font outline is enabled. Add some characters that are not included in the font.
Minimal reproduction project:
FullwidthSpace-3.2.zip is a 3.2.1 project (the issue also exists on current master). Text contains a fullwidth space and some Chineses characters that the InputMono font does not include. The scene should look like the screenshot above.

Fixed by #44679.


Ghost Devices

Alexa keeps discovering a few devices that i only used once for testing.
Deleting them in the Alexa App doesnt work half the time and they prevent the discovery of the last device in my final Program.
At least thats what i think happens.
The weird thing is they are discovered even if my esp32 is turned off.
Maybe thats more of an Alexa problem but i dont know how to fix it.
I really enjoy the stuff that works.
Thanks for making this.
Help would be appreciated.

Hi, I can definitely reproduce this issue.
Originally I believed this issue only affected my account but it appears to be a general problem when using Espalexa.
Devices always get "discovered" after deleting, even if said device has not been online for a year.
Deleting all devices/groups/schedules from the alexa app did not help either.
I have not yet been able to conclusively determine if the ghost devices are saved in the Echo hardware or in the Amazon account and am sadly unable to share any method that permanently deletes devices.
One slightly random question - do you have a genuine Philips Hue bridge in your network and/or installed the associated Alexa skill?

Hello,
thanks for answering.
I have been able to set up the last device in my Program. It was an error in my code.
Yes i have a hue bridge in my home and the hue skill installed. But having it connected and or the skill installed seems to have no impact on the non existing yet discovered devices.
A few test have shown that the "Ghost Devices" get rediscovered only if the right Alexa Device is connected to the network.
I think its the one that was closest to the esp when i first testet the program.
 All of the rest is working brilliantly quick and reliable.
Thanks again for making this and thanks for helping a lot of not so code talented people like me! :P

I have the same issue, how do i stop this ghost devices from popping, i tried to erase flash the esp form esptool in terminal. I flashed many other project on the same esp chip but i always have this devices appearing, maybe alexa remind the mac address of the device and keep associate it to the old device names, i tried also to factory resety the alexa echo dot where those ghost devices connected forst time, but nothing changed. Myabe i have to reset the all alexa devices in my house?
I appreciate any help


HTML on content

Hi,
Can you allow HTML code on content?
Thanks

yea, I can.
if you need these changes right now, you can extend models and edit it here https://github.com/artkost/yii2-qa/blob/master/models/Question.php#L103 and here https://github.com/artkost/yii2-qa/blob/master/models/Answer.php#L103

Thanks.


Faster fuzz testing

Because the fuzz testing programs are invoke once for every single corpora file (more than 15000 today), fuzz testing is very slow.  Archiving the corpora files, and thereby reducing the number of program invokations (there are 11 such archives with this change, one for each fuzz testing program) speeds up testing dramatically [1].

[1] In my tests, the time it takes to run 99-test_fuzz.t is reduced by a factor of about 20 on an otherwise idle system.  Running several of them at once (Windows cmd, Cygwin, mingw, both 32 and 64 bit) shows even more dramatic speed increases.

I have concerns about this that were raised on the openssl-project mailing list; those should be addressed first, before this is merged.  First, why CPIO over the already-used TAR format.  And more importantly, as @vdukhovni said,we can't we just readdir() like c_rehash does?  This makes it much harder to maintain the fuzz files, or extract one to repeat a test, and so on?

Thanks for the note...  it seems I haven't received those replies...  But sure, reading the directory might work as well.
(as far as cpio vs tar, I find the cpio headers more compact and easy to handle, and quite specifically, easier to recognise with just a few bytes.  That directed my choice.  However, given the readdir idea (why didn't I think of that???), that's a moot point)

Reading a directory is "hard and nonportable", which is why we have the various crypto/LPdir_*.c implementations.  (I sort-of have a desire to have libcrypto stop knowing how to read a directory, for what it's worth.)  I am somewhat opposed to adding another place where we need to know how to read a directory if there are other alternatives, even if it is only in the test suite.

@kaduk [reading a directory is hard]
I disagree.  The code is surely simpler than reading cpio archives and, in this case, the directory reading code need not end in libcrypto, but if that code works well enough (CApath needs it after all) then
we've already solved that problem.

I think windows gets really very slow when a directory contains 15.614 files.
Is here a reason why the tar download files do not contain fuzz/corpora ?

The files need not all be in one directory.  They can be grouped into sub-directories.

@bernd-edlinger : corpora fuzzer input folders are currently far from this value of 15.614 entries, hopefully.

@kaduk [reading a directory is hard]
I disagree. The code is surely simpler than reading cpio archives and,

This exchange is quite amusing to me, considering I wrote both. I actually found the cpio reader more straightforward to write, 'cause there were very little platform dependent idiosyncrasies to deal with. Directory reading is quite a different story and presented quite a few stumbling blocks, as I recall. But then, I tried to make the directory reading much more general, while the cpio reader is fairly minimal (I cheat by not looking at all at the checksum in the crc format).
Anyway, I believe that #5776 is the winning implementation...

@bernd-edlinger

I think windows gets really very slow when a directory contains 15.614 files.

We currently have 15500+ files unevenly spread over 11 directories, so we're not even close.

Is here a reason why the tar download files do not contain fuzz/corpora ?

It was judged unnecessary, I think. Plus the test was so slow... I think...

My concern was that it would more than double the size:
; ddu -s . .git fuzz/corpora
421352	.
178112	.git
150248	fuzz/corpora
; echo<PHONE_NUMBER>12 - p 150248 - p |dc
243240
92992

I don't quit understand your calculations...  let me show another way to look at it:
: ; git checkout master
Redan på "master"
Din gren är à jour med "origin/master".
: ; du -sk fuzz/corpora/
76296	fuzz/corpora/
: ; git checkout faster-fuzz-test
Växlade till grenen "faster-fuzz-test"
: ; du -sk fuzz/corpora/
25372	fuzz/corpora/

Either way, again, #5776.  I'm closing this in that one's favor.

My point was comparing a repo to a repo+fuzz

Well, we already have the fuzz either way...


Improve Kubernetes service registry for ALS analysis

Improve Kubernetes service registry for ALS analysis
The current implementation of Envoy ALS K8S analysis is based on the hierarchy, pod -> StatefulSet -> deployment, StatefulSet, or others. It's freaky and different from the Istio Kubernetes registry. And the service name pattern changed in recent Kubernetes versions, which generates weird service names in the topology.
The new path is pod -> endpoint -> service, and we should leverage Informer API instead of raw Kubernetes API.

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #5706.
[x] Tests(E2E) are adjusted to verify the improvement.
[x] Update the CHANGES log.

FYI, @wu-sheng @hanahmily What it differs from the previous version is that the different versions of a same service are now collapsed into one service, e.g. in the previous version, reviews-v1, reviews-v2, reviews-v3 are 3 different services, but in this version, they are all collapsed into reviews, as a single service, with different version tag, (labels: version=v1, version=v2, etc.)

All review comments should be addressed, if I missed anything, please let me know


[IT-3266] Remove bastian hosts

Once we setup DB updates from github instances we will no longer need an AWS bastian host for each environment.
depends on https://github.com/Sage-Bionetworks/agora-data-manager/pull/116

Change of plans in https://github.com/Sage-Bionetworks/agora-data-manager/pull/116.  We are keeping the bastion hosts and using them as self-hosted runners.


#2862 improve seata beanPostProcessor order

Describe what this PR does / why we need it
SeataBeanPostProcessor had better has a higher init order, for fare some beans be initialized early along with some business beanPostProcessor, in that situation, this bean will not be proxyed by Seata like SeataFeignClient.
Does this pull request fix one issue?
Fixed #2862

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.李壮壮 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


feat: introduce unsealed shaped array syntax

This syntax enables an extension of the shaped array type by allowing additional values that must respect a certain type.
$mapper = (new \CuyZ\Valinor\MapperBuilder())->mapper();

// Default syntax can be used like this:
$mapper->map(
    'array{foo: string, ...array<string>}',
    [
        'foo' => 'foo',
        'bar' => 'bar', // ✅ valid additional value
    ]
);

$mapper->map(
    'array{foo: string, ...array<string>}',
    [
        'foo' => 'foo',
        'bar' => 1337, // ❌ invalid value 1337
    ]
);

// Key type can be added as well:
$mapper->map(
    'array{foo: string, ...array<int, string>}',
    [
        'foo' => 'foo',
        42 => 'bar', // ✅ valid additional key
    ]
);

$mapper->map(
    'array{foo: string, ...array<int, string>}',
    [
        'foo' => 'foo',
        'bar' => 'bar' // ❌ invalid key
    ]
);

// Advanced types can be used:
$mapper->map(
    "array{
        'en_US': non-empty-string,
        ...array<non-empty-string, non-empty-string>
    }",
    [
        'en_US' => 'Hello',
        'fr_FR' => 'Salut', // ✅ valid additional value
    ]
);

$mapper->map(
    "array{
        'en_US': non-empty-string,
        ...array<non-empty-string, non-empty-string>
    }",
    [
        'en_US' => 'Hello',
        'fr_FR' => '', // ❌ invalid value
    ]
);

// If the permissive type is enabled, the following will work:
(new \CuyZ\Valinor\MapperBuilder())
    ->allowPermissiveTypes()
    ->mapper()
    ->map(
        'array{foo: string, ...}',
        ['foo' => 'foo', 'bar' => 'bar', 42 => 1337]
    ); // ✅

Fixes #438

Hello @Ocramius, if you have some time I'd really appreciate if you could play with this and try to make it crash. 😛

@Ocramius I was actually just asking for real tests on your end, but thanks for the review it's really much appreciated. If you are done we can merge it. 😉

Nothing immediate in userland projects: I think it used to crash in a project last year, due to parsing failing

Let's go for it then! 💪


Public Release of ICM 0.2.0

What type of PR is this?

subproject management

What this PR does / why we need it:
This is the PR for the public release of ICM 0.2.0
Which issue(s) this PR fixes:
Related to https://github.com/camaraproject/IdentityAndConsentManagement/issues/146
Special notes for reviewers:
@hdamker CAMARA-AuthN-AuthZ-Concept.md is DEPRECATED and has been removed in this public release as agreed in the past. Please take a look at the CHANGELOG to see if you agree with the way I've tried to track this issue. It is a bit tricky because the document was removed, then restored in RC1, and finally removed now.
Changelog input
ICM public release 0.2.0

Additional documentation

https://wiki.camaraproject.org/display/CAM/Meta-release+Fall24

@hdamker CAMARA-AuthN-AuthZ-Concept.md is DEPRECATED and has been removed in this public release as agreed in the past. Please take a look at the CHANGELOG to see if you agree with the way I've tried to track this issue. It is a bit tricky because the document was removed, then restored in RC1, and finally removed now.

@jpengar Thanks that you remembered about this needed deletion - relevant is here that Commonalities will release the new version 0.4.0 which has no longer the link to the deprecated document. Suggestion above on your disposal.
Beyond that the PR looks good to me. Approval will come after the TSC (hopefully).

/LGTM

Approved by TSC


fix(turing,xp-management): Fix Turing and XP app labels

Motivation
This PR introduces fixes to the Turing and XP Management charts:
XP Management
The XP Management swagger docs are not functioning correctly if the full name of the XP management app does not happen to be the same as its regular name. That's because the swagger K8s service is using the full name as a label selector whereas the XP Management deployment pods are simply using a regular name as a label.
Compare:

https://github.com/caraml-dev/helm-charts/blob/main/charts/xp-management/templates/service-swagger.yaml#L18
https://github.com/caraml-dev/helm-charts/blob/main/charts/xp-management/templates/deployment.yaml#L23

This PR thus updates the selector value to use the regular name of the XP Management service.
Turing
The Turing deployment pod labels and service pod selectors are using the full name of the Turing app, which isn't in sync with the other CaraML apps like Merlin and XP where we are using the regular name of the app as part of the app label. This PR thus updates the app label of the Turing deployment pod labels and service pod selectors to make it consistent with the other CaraML apps.
Modification

charts/turing/templates/turing-deployment.yaml - Update of the Turing deployment pod label and selectors
charts/turing/templates/turing-service.yaml - Update of the Turing service pod selector
charts/xp-management/templates/service-swagger.yaml - Update of the XP swagger service pod selector

Checklist

[x] Chart version bumped
[x] README.md updated

Thanks a lot for the quick review; I just added another line to insert labels specified in .Values.deployment.labels to the deployment pod template (which is what the Turing/Merlin/MLP charts do).
Unfortunately, Turing and XP do not have a separate values block for pod labels, unlike Merlin and MLP which have pod-level labels and deployment-level labels (and even these aren't named consistently between these 2 charts). I'll leave this refactoring out for again for a separate PR. Will be merging this once the pipeline passes :)


Paragraph breaks not preserved in lingva Eng-> japanese

Hi (long time no see). I haven't been using the plugin much lately for various reasons, but started up recently. One thing hanging me up is a snag with the lingva translator. It may not be with the plugin at all, but I find that in translating english to japanese, french and portuguese (the only languages I tested), paragraph breaks are not preserved, which was slowing me down.  I don't konw if it something fixable on your end, but I thought I'd let you know. Aside from that, hope you are doing well...

Hey, I'm really sorry for the wait! I've tried fixing this a couple weeks before, but the lingva services seemed to be down. Apparently all .ml domains were taken offline, only 4 of the services still work.
Either way, I found the issue, and everything should work now, I forgot to properly encode the endline/paragraph breaks...
I'll be pushing this soon, thank you for reporting the issue! Sorry again for being so late with this, I've been getting distracted with the other plugin I've been working on 😅

Hi, that's great. No worries about the time. I am a slow burner myself, and anyway I have my implicit trust.  Are you talking about criticmarkup? Nice idea! (though I wouldn't have call to use it.)

Yep, the CriticMarkup plugin! Basically, I'm trying to squeeze Google Docs/Word's suggestion mode and comment system into Obsidian. It will be helpful for tracking changes, collaborating with people or leaving notes for yourself using pure markdown. There's still a lot of work left that needs to be done, but I'm getting closer and closer to a working product.

Closing this issue as it is shipped with update 1.4.6, thanks again for the issue report!

Great. It works.
FYI when I updated the plugin, reloading Obsidian didn't complete and I got one of those reboot or turn off community plugins messages. Eventually I had to reinstall the plugin from scratch and redo my settings, but it is working now beautifully, saving me a lot of time. Thanks!

Agh, that should never happen. Something may have gone wrong with the plugin's data when updating, though without error logs, it's hard to say. I'm sorry for that major inconvenience! Sometimes it feels like the plugin is barely held together by spit and baling wire. I'll be on the look-out for cases where this may happen.


fixed the bug by adding a cleanup function to the useEffect in LoginC…

…ontainer
Description
Clicking the back button when on the register webpage errors the entire webpage and the webpage turns white. This was due to the LoginContainer component not having a cleanup function in the useEffect hook. Therefore, I added the remove method from Okta widget to run in the cleanup function.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have removed unnecessary comments/console logs from my code
[ ] I have made corresponding changes to the documentation if necessary (optional)
[X] My changes generate no new warnings
[X] I have checked my code and corrected any misspellings
[ ] No duplicate code left within changed files
[X] Size of pull request kept to a minimum
[X] Pull request description clearly describes changes made & motivations for said changes

Good catch.


[WIP] quinn compatibility testing! DO NOT MERGE

Description

Breaking Changes

Notes & open questions

Change checklist

[ ] Self-review.
[ ] Documentation updates following the style guide, if relevant.
[ ] Tests if relevant.
[ ] All breaking changes documented.

Guess nobody is playing with this anymore.


Create stale.yml

This file enables stale bot to automatically flag stale issues and automatically close old issues. This is for #1157

That looks great!


How to change from Windows only to SQL Server and Windows authentication mode

The article shows how to change the authentication mode to Windows only - but what T-SQL command and magic value is used to change the authentication mode to "SQL Server and Windows authentication mode".
All combinations should be documented.
Thanks in advance.

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

ID: 3e9b632d-7e6d-1434-cc6b-9aa77d37f41a
Version Independent ID: 3689727c-e685-1503-fd9e-365aa15c33fa
Content: Change Server Authentication Mode - SQL Server
Content Source: docs/database-engine/configure-windows/change-server-authentication-mode.md
Product: sql
Technology: configuration
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@bdcoder2 -- thank you for your feedback.
@MikeRayMSFT -- please look into this issue #4087.

Other suggestion:

Include a list of the various registry paths for the various flavors of SQL (ie: SQLExpress)
Mention the above can be accomplished using RegEdit as well (in case access to SMSS is not available)

I guess that original doc dont speicfy T-SQL because it uses undocumented xp_regwrite* procedures.
Maybe, Product Team want not encourage users to use this procedure due to side effects that it can cause on environment.
I dont know why Microsoft not use the "sys.configurations" to store it. This would can a better place and all interfaces to change it already documented.

@bdcoder2  thanks for the submission, and writing up a way to accomplish the task. I'm reviewing your suggestion with engineering.
Your call out helps me identify that this doc could be improved to clarify what you can  & can't do with T-SQL.
After I review, we'll update.
Thanks!
Mike

@bdcoder2 thanks for the submission.
We've reviewed the article and are updating it to clarify what the different steps do. We are not explicitly describing how to use T-SQL XPs to change the authentication mode beyond what it currently describes. The manual steps described manually modify the registry. This task is very high-risk and not advised.
If you would like to submit a feature request to enable a programmatic way to change this setting, consider submitting feedback at https://aka.ms/sqlfeedback.


SendActivityAsync's overload options are painful for the most often invoked scenario

Is your feature request related to a problem? Please describe.
Arguably the most common API being invoked is going to be the   SendActivity(string, [CancellationToken]) overload. Unfortunately, as   defined, the cancellationToken is optional, but this causes it to clash with   another overload forcing you to always have to name the cancellationToken   parameter if you do want to pass it.
This is because the SendActivityAsync(string, [CancellationToken]) overload defines the CancellationToken as an optional parameter so, when you do actually want to supply it, you must explicitly name the parameter. If you don't, the compiler can't tell the difference between that overload and the other overload of SendActivityAsync(string, [string],  [string], [CancellationToken]).
This forces everyone who wants to pass the CancellationToken in to the first overload, which is the right thing to do and should be encouraged, to have to spell it out with a verbose/repetitive parameter name like so:
turnContext.SendActivityAsync("Hello world!", cancellationToken: cancellationToken);

Describe the solution you'd like
Ideally this should have been defined as only one method on ITurnContext:          SendActivityAsync(IActivity, CancellationToken);  and then everything else should have been implemented as a set of extension methods for ITurnContext enabling convivence signatures and solving this specific problem with distinct overloads with explicit, required params:

SendActivityAsync(string);
SendActivityAsync(string, CancellationToken);
SendActivityAsync(string, string, string, CancellationToken);
etc.

Additional Context
Right now I'm honestly not sure how best to resolve this without a breaking API change. 😢

Thanks for feedback on this @drub0y, we all agree that this would be better as described but it is probably not possible to correct without breaking API changes.


Clear Navigation Context on Profile Page

Clear Navigation Context on Profile Page

Add before_filter to clear the navigation context.
This fixes a bug that shows content in the header from previous page.

[#100847372]

:+1:


[ExternalNode] Create Secret for vm-agent in RBAC

Crate a separate Secret for VM Agent in RBAC file, because the Secret for a ServiceAccount is not created automatically since K8s v1.24.
Use the manually created Secret in Agent kubeconfig file.

Fix #4558
Signed-off-by: wenyingd<EMAIL_ADDRESS>

/test-vm-e2e

/skip-all
VM Agent e2e test has passed in CI setup.


Why would one prefer 'django-webpack-loader' over 'html-webpack-plugin'

I tried to see if I need to use 'django-webpack-loader' but still not convinced. Its objective is to allow use of the generated webpack bundles, but this can be achieved easily with 'html-webpack-plugin' which generates an html file with the bundle files injected in it, this html file then can be used as a django template.
The advantage of using 'html-webpack-plugin' becomes more obvious when using a pre-configured webpack ecosystem (like vue cli) where we get a ready made html file with all the needed head/body bundle tags (including prefetch/preload links ...) injected, without any need to manually select what to put in head/body.
Here is my setup (simplified):
base.html
{% block html %}
<!DOCTYPE html>
<html {% block html_tag_attributes %}{% endblock %}>
  <head>
    {% block head %}
      <meta charset="utf-8">
    {% endblock %}
  </head>

  <body {% block body_tag_attributes %}{% endblock %}>
    {% block body %}
      {% block content %}{% endblock %}
    {% endblock %}
  </body>
</html>
{% endblock %}

index.html (template used by html-webpack-plugin to generate bundles/webpack/home_page.html):
{% extends "base.html" %}
{% load static %}
{% block html %}
<!DOCTYPE html>
<html {% block html_tag_attributes %}{{ block.super }}{% endblock %}>
  <head>
    {% block head %}{{ block.super }}{% endblock %}
  </head>
  <body {% block body_tag_attributes %}{{ block.super }}{% endblock %}>
    {% block body %}{{ block.super }}{% endblock %}
  </body>
</html>
{% endblock %}

home_page.html
{% extends "bundles/webpack/home_page.html" %}
{% block content %}
  Adding content here...
{% endblock %}

I appreciate if someone can tell if there is a scenario where we can do it only with django-webpack-loader
Note: the links in the injected tags can be easily converted to django static tempate tag format, ie: 'bundles/js/main.js' ==> {% static 'bundles/js/main.js' %}
I created a minimal basic plugin to do this: https://gitlab.com/noor-projects/django-static-webpack-plugin/blob/master/index.js
@owais

I don't know what html-webpack-plugin is and don't remember using it. I wrote this to solve my own problem a few years ago. The core problem I was trying to solve was to make it easy for Django to figure out the names of bundles generated by webpack. If html-webpack-plugin solves your problem, then I don't see why you need to use django-webpack-loader at all.

Thanks for the reply, I am inquiring about django-webpack-loader because I saw it mentioned in many tutorials and it is popular, so I was wondering if it has other features that I might need in the future, then I will be adopting it from the beginning.

I did not mean in any way to undermine django-webpack-loader, and I am sorry if that was perceived.

Html-webpack-plugin is a frontend solution to the problem, this is a backend solution. I'd say this is the easier/more manageable solution between the two.

@ejez Thank you very much for sharing your configs! Would you mind sharing your Vue CLI config (vue.config.js) as well?
I'm struggling a bit to understand the html-webpack-plugin method (because I'm new to Vue and Vue CLI), but I really want to try it.
One thing I don't understand is whether I still need the Vue dev server for anything? If not, will hot module replacement work?
When I run the Vue dev server (npm run serve) from a project created via Vue CLI, it doesn't save anything to disk. One way to overcome this is to set writeToDisk to true, but I'm not sure if this is the most optimal way.
I wonder how you do it.

I've created a Django + Vue CLI demo project following @ejez's approach:
https://github.com/EugeneDae/django-vue-cli-webpack-demo
I'm not advocating against django-webpack-loader — just wanted to explore an alternative.

It's pretty interesting indeed, I've been using both solutions, and didn't
find any reason to favor one on top of another so far.

I've got some updates:

figured why I prefer django-webpack-loader over html-webpack-plugin: django-webpack-loader just saves workflow time overall, ie.: we don't have this weirdness where we edit a django base_template.html template to generate the base.html template
migrating away from webpack to snowpack and got a 3.000x productivity boost, check Django + Snowpack = djsnowpack blog post

@ejez, how would you use that approach on a MPA?

@ejez, how would you use this approach on a MPA?

might be of interest:
https://github.com/EugeneDae/django-vue-cli-webpack-demo/blob/master/README-MPA.md

@EugeneDae, thanks. I've read that :) However I'm not using vue, but a plain webpack config.


Node SSL Certificate methods missing in v10

Get|Set|Remove methods for node SSL certs are documented in API Guide 10.1 but missing in the Postman collection

@ReeseLloyd will these methods be added in next update?

This was fixed in v11.


Tensorboard icons invisible when building from source

The refresh, configure, and plot buttons (expand, log/linear) are not visible when building tensorboard from source. However, they are clickable.

Environment info
Build/execute operating System: Ubuntu 16.04
Viewing operating System: OS X 10.11.6
Viewing browsers: Chrome 52 & Safari 9.1.2
Installed from source from a recent master commit 99ce233191920fb0dde2d823cf493e28b89618c7
Bazel 0.3.0
Steps to reproduce

git clone https://github.com/tensorflow/tensorflow.git
cd tensorflow
./configure
bazel build -c opt --config=cuda //tensorflow/cc:tutorials_example_trainer
pushd tensorflow/tensorboard
npm run prepare
npm run compile
gulp regenerate
popd
bazel build -c opt --config=cuda //tensorflow/tools/pip_package:build_pip_package
bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg
pip install /tmp/tensorflow_pkg/tensorflow-0.10.0rc0-py3-none-any.whl
tensorboard

What have you tried?

Building from r0.10 branch but it doesn't work either.

Known issue. Will be fixed today at r0.10 and master.

It is fixed in master now. Thanks.

Fix will be merged into r0.10 by https://github.com/tensorflow/tensorflow/pull/4137.


Added Event model and routes

fixes #29

Description: Added Events model and routes with CRUD operations
Checklist

[x] I've followed the Contributing guidelines provided in the repository.
[x] I've made the changes that were demanded in the linked issue.
[ ] I've tested my code on a Chromium-based browser.
[ ] I've tested my code on Mozilla Firefox.
[x] My code gave a clean console on debugging. (no warnings/errors)

Testimonial

@tusharjain0022 - Review it! Then I will merge it

Everything seems good to me !! 🚀


COMP: Move ITK_DISALLOW_COPY_AND_ASSIGN calls to public section.

Move ITK_DISALLOW_COPY_AND_ASSIGN calls to public section following
the discussion in
https://discourse.itk.org/t/noncopyable
If legacy (pre-macro) copy and assing methods existed, subsitute them
for the ITK_DISALLOW_COPY_AND_ASSIGN macro.

:+1:  LGTM!

@DVigneault I do not have the rights to merge. Can you proceed, please?

Thanks @DVigneault !


no helpful message if template is missing headers

When a user uploads a template that is missing headers (in specific from the last columns) the system yields: An error occurred parsing the sample template Sample_Template.txt No columns to parse from file, which is not useful

The current error, see below, is much better. Closing for now.


Add CI tests targeting glibc=2.17

Feature request

We recently discovered a regression in NumPy's (1.26) meson-based builds under glibc=2.17 at
- https://github.com/conda-forge/numba-feedstock/pull/128#issuecomment-1795031396
Numba's own CI tests apparently didn't catch this beforehand.
Since Anaconda Distribution as well as conda-forge currenlty target glibc 2.17/CentOS 7, it'd be good to have one or more CI jobs that run under CentOS user space, e.g., via a container-based build.

Following discussion during the dev meeting, we felt that it would be difficult to resource this. However, for future releases we will be testing a build of the potential commit to tag for a release via a PR to conda-forge. This is to ensure that we catch any error that might appear in a conda-forge build prior to the release, and not after the release (as we have observed with 0.58).
See: https://github.com/numba/numba/issues/9271 and https://github.com/numba/llvmlite/issues/1008

Thanks @gmarkall, good to know this has already been considered.

it would be difficult to resource this.

Given Numba's extensive tests, it that seems understandable.

testing a build of the potential commit to tag for a release via a PR to conda-forge.

That would be a good addition, thanks!
Another suggestion would be to have otherwise too intensive additional tests (like the suggested container-based ones) on a regular schedule at off-hours.
Given Numba's development pace and release schedule, a weekly run (e.g., at night on the weekend) would make sense (a typical "nightly" run seems unnecessarily much, IMO).
The advantage of that would be that potential issues can be discovered closer in time when they are introduced and handled before entering a busy pre-release phase.

Many thanks for the suggestions!

Given Numba's extensive tests, it that seems understandable.

I was more thinking along the lines of developer time - none of us are expert enough in CI systems that we could set something like this up with ease, and feel the constant pressure from other ongoing maintenance tasks (supporting new LLVM, NumPy, CPython, CUDA versions, etc.) alongside regular feature development and issue handling / bug fixing. I think even running the suggested configuration at a reduced cadence (compared to "all PRs") would be just as much effort to set up, so we feel that checking the build will succeed on conda-forge prior to tagging releases is the most attainable improvement we can make right now.

I was more thinking along the lines of developer time

Oh, since "CI resource economy" is a thing with Numba's tests, I didn't even think about the other obvious factor :D.
Having to deal with build/test setups when there is much else to do can be quite problematic, indeed.

I think even running the suggested configuration at a reduced cadence (compared to "all PRs") would be just as much effort to set up,

Most definitely, yes.

checking the build will succeed on conda-forge prior to tagging releases is the most attainable improvement we can make right now.

Certainly!

It shouldn't be too hard to add this with minimal changes to the existing setup and (more importantly) in a way that imposes next to none additional maintenance burden.
Maybe I could at some point (might take a while...) take a look at it -- or someone else stops by with a contribution :).


dockerd shutdown-timeout option does not work as expected

Description

dockerd option shutdown-timeout does not seem to work as expected on service shutdown.
Steps to reproduce the issue:

setup systemd with a configuration that includes the --shutdown-timeout=30 option. In my case

ExecStart=/usr/bin/dockerd -D -H unix:///var/run/docker-${USER_NAME}.sock --userns-remap=default --exec-root=/var/run/docker/${USER_NAME} -g /home/${USER_NAME}/docker/ --pidfile=/var/run/docker-${USER_NAME}.pid --insecure-registry=dregistry:5000 --fixed-cidr=${DOCKER_NETWORK} --shutdown-timeout=30

Run a container which is not handling SIGTERM by default, so it always gets killed.

docker run -d -ti --name=zkui goodguide/zk-web:latest

stop docker.service measuring time statistics

time systemctl stop docker.service

real	0m11.846s
user	0m0.000s
sys	0m0.000s

Describe the results you received:
journalctl logs mention this

"start clean shutdown of all containers with a 30 seconds timeout...

but container gets stopped after 10 seconds (instead of 30).

msg="Container 23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b failed to exit within 10 seconds of signal 15 - using the force"
Apr 04 09:30:35 qa22 dockerd[28264]: time="2017-04-04T09:30:35.316828071-07:00" level=debug msg="Sending kill signal 9 to container

Apr 04 09:30:25 qa22 systemd[1]: Stopping Docker Application Container Engine...
Apr 04 09:30:25 qa22 dockerd[28264]: time="2017-04-04T09:30:25.315742282-07:00" level=info msg="Processing signal 'terminated'"
Apr 04 09:30:25 qa22 dockerd[28264]: time="2017-04-04T09:30:25.315887135-07:00" level=debug msg="start clean shutdown of all containers with a 30 seconds timeout..."
Apr 04 09:30:25 qa22 dockerd[28264]: time="2017-04-04T09:30:25.315980272-07:00" level=debug msg="stopping 23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b"
Apr 04 09:30:25 qa22 dockerd[28264]: time="2017-04-04T09:30:25.316012651-07:00" level=debug msg="Sending kill signal 15 to container 23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b"

Apr 04 09:30:35 qa22 dockerd[28264]: time="2017-04-04T09:30:35.316780128-07:00" level=info msg="Container 23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b failed to exit within 10 seconds of signal 15 - using the force"
Apr 04 09:30:35 qa22 dockerd[28264]: time="2017-04-04T09:30:35.316828071-07:00" level=debug msg="Sending kill signal 9 to container 23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b"
Apr 04 09:30:35 qa22 dockerd[28264]: time="2017-04-04T09:30:35.44054447-07:00" level=debug msg="containerd: process exited" id=23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b pid=init status=137 systemPid=3870
Apr 04 09:30:35 qa22 dockerd[28264]: time="2017-04-04T09:30:35.446673243-07:00" level=debug msg="libcontainerd: received containerd event: &types.Event{Type:\"exit\", Id:\"23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b\", Status:0x89, Pid:\"init\", Timestamp:(*timestamp.Timestamp)(0xc421372b50)}"
Apr 04 09:30:35 qa22 dockerd[28264]: time="2017-04-04T09:30:35.447517766-07:00" level=debug msg="Revoking external connectivity on endpoint zkui (5bd33a9b2b7571fbf24661ae18fdedc0f67ab412a4bd0b1604fcb1d192809441)"
Apr 04 09:30:35 qa22 dockerd[28264]: time="2017-04-04T09:30:35.623431528-07:00" level=debug msg="Releasing addresses for endpoint zkui's interface on network bridge"
Apr 04 09:30:35 qa22 dockerd[28264]: time="2017-04-04T09:30:35.623473594-07:00" level=debug msg="ReleaseAddress(LocalDefault/<IP_ADDRESS>/16/<IP_ADDRESS>/24, <IP_ADDRESS>)"
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.092134694-07:00" level=debug msg="GetMountID id: 23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b -> mountID: ecfc1dff8eae821378ed76e5e6d6813f9ee733edfe635da43e0472022b241385"
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.092170115-07:00" level=debug msg="Cleaning up old mountid ecfc1dff8eae821378ed76e5e6d6813f9ee733edfe635da43e0472022b241385: start."
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.092612747-07:00" level=debug msg="Cleaning up old mountid ecfc1dff8eae821378ed76e5e6d6813f9ee733edfe635da43e0472022b241385: done."
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.092629491-07:00" level=debug msg="container stopped 23e4f3e7529471356ae0069197e77f6939d7d8176d49422c59b9b93d3afbb63b"
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.117212427-07:00" level=debug msg="Cleaning up old mountid : start."
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.117318455-07:00" level=debug msg="Unix socket /run/docker/libnetwork/bfa6d768c2dd0afb1c12c2e69b9c0b2781361d2de54afd8a327f0e2c024b0cab.sock doesn't exist. cannot accept client connections"
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.117564226-07:00" level=debug msg="Cleaning up old mountid : done."
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.117588043-07:00" level=debug msg="Clean shutdown succeeded"
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.117850074-07:00" level=info msg="stopping containerd after receiving terminated"
Apr 04 09:30:36 qa22 dockerd[28264]: time="2017-04-04T09:30:36.411530576-07:00" level=debug msg="libcontainerd: containerd health check returned error: rpc error: code = 9 desc = grpc: the client connection is closing"
Apr 04 09:30:37 qa22 systemd[1]: Stopped Docker Application Container Engine.

container stopped
Describe the results you expected:
I was expecting command  time systemctl stop docker-litservices.service to finish after 30 seconds.
Even if I run the container with a container level timeout of 60s using docker run --stop-timeout=60, still time systemctl stop docker-litservices.service is shutting down after 60s (instead of 30s).
it seems that the container level timeout option stop-timeout, overpowers the shutdown-timeout dockerd value and the latter is not making any difference at all. Is this normal?
Which timeout is the dockerd/ --shutdown-time option is setting?
Additional information you deem important (e.g. issue happens only occasionally):
--shutdown-timeout exists in man/help page but is not documented in the documentation
[~]>dockerd --help | grep shut
      --shutdown-timeout int                  Set the default shutdown timeout (default 15)

Output of docker version:
# docker --version
Docker version 17.03.1-ce, build c6d412e

Output of docker info:
[~]>docker info
Containers: 22
 Running: 20
 Paused: 0
 Stopped: 2
Images: 6
Server Version: 17.03.1-ce
Storage Driver: aufs
 Root Dir: /home/services/docker/1083040.1083040/aufs
 Backing Filesystem: extfs
 Dirs: 143
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
 userns
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 94.6 GiB
Name: dev2
ID: J34K:LKP5:Y6A5:IWIO:KT5H:WMRH:YSZJ:6QOA:EHYP:ZLBH:XGOA:EANL
Docker Root Dir: /home/services/docker/1083040.1083040
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 135
 Goroutines: 102
 System Time: 2017-04-04T09:36:55.73437204-07:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
Experimental: false
Insecure Registries:
 dregistry:5000
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Physical debian
SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux

Shutdown timeout is the period of time that is given for the daemon to shutdown before it just proceeds with exiting. This is not related to container shutdown time.
To change a container's stop timeout, you need to set --stop-timeout.
Shutdown timeout is adjusted for the max stop-timeout of a container.

So if shutdown timeout will be the max('Shutdown timeout', max('stop-timeout')) what is its use?
If max(stop timeout) is less that shutdown timeout, all containers would be stopped before we reach shutdown timeout anyway so we wouldnt reach it.
For example if the max stop-timeout for containers is 10 seconds and shutdown-timeout for the service is 20 seconds.
If we issue a service stop, then after 10 seconds all containers will have been stopped and the service will stop at that time too. Thus, it will not reach 20 sec.
What am i missing?

@hdimitriou There's more work to do than just shutdown containers on exit.

@cpuguy83 ; --shutdown-timeout was added in https://github.com/docker/docker/pull/23036, and overrides the default 10 seconds + 5 seconds grace before SIGKILL the container; https://github.com/docker/docker/pull/22566 also adds a per-container option; if that option is set and is longer than shutdown-timeout, the shutdown-timeout is extended to be sure it's not shorter than that.
However, the daemon shutdown takes the stop-timeout into account that was set on a container, and I think this is where the mistake is; that timeout defaults to 10 seconds, so the shutdown-timeout won't be used.
ping @yongtang perhaps you can take a look if we're mis-interpreting it?

Thanks @thaJeztah I will take a look.

When stopping a container, either the user-specified (--stop-timeout) timeout is used, or if no timeout is set, the default (fixed) timeout of 10 seconds is used;
https://github.com/moby/moby/blob/930e6896685f614d8f15ed10207596b1a151cbc8/container/container.go#L462-L468
https://github.com/moby/moby/blob/930e6896685f614d8f15ed10207596b1a151cbc8/container/container.go#L54-L55
During shutdown, the longest timeout is taken; which can be either the value set on the daemon (--shutdown-timeout), or set by a container (--stop-timeout). After all containers are terminated, the daemon shuts down;
https://github.com/moby/moby/blob/147443a42665419d8b3c2047a7d345440bfb63c0/cmd/dockerd/daemon.go#L408-L429
Here's the tricky bit:

if the timeout set on the daemon is shorter than the timeout of any of the containers, the shutdown-timeout is extended to allow the container to shutdown gracefully (https://github.com/moby/moby/pull/22566)
effectively, seting the --shutdown-timeout to anything shorter than 15 seconds (default container stop-timeout + grace period) does not have any effect
setting --shutdown-timeout to anything longer than the longest --stop-timeout of a container does not do much either; containers are killed before the --shutdown-timeout expires, in which case the daemon also shuts down.

Observations

From the above, it becomes clear that the --shutdown-timeout option currently doesn't do anything.
The --stop-timeout and --shutdown-timeout options were implemented to allow stateful services/containers to be shutdown cleanly (e.g. don't kill a mysql container while it's still writing data to disk, because that may lead to data corruption).
By always accepting the longest timeout, a container started with --stop-timeout=-1 potentially prevents the daemon from shutting down; this may be a concern because the person managing the daemon has no control over this.
It's not possible to override the default stop-timeout for containers (if that's desirable), the default is fixed to 10 seconds

Possible solutions
We can remove the default value for --shutdown-timeout (e.g., set it to 0);

If no value is set for --shutdown-timeout. Containers are killed after 10 seconds by default, and the daemon shuts down after the last container was terminated. It may thus not even be needed to calculate the actual shutdown time (just wait until all containers terminated).
If a value is set for --shutdown-timeout, that value overrides the --stop-timeout for containers, which means that --shutdown-timeout=10 kills any container that did not stop after 10 seconds (including, e.g., a mysql container with a --stop-timeout=60). Allowing to override the timeout on the daemon puts the person managing the daemon back in control ().

Alternatively; use --shutdown-timeout as the default value for containers that don't specify a --stop-timeout. This makes the default configurable (item 4. on the list above), allows the timeout to be customized for stateful containers (item 2.) but doesn't solve 3.

do we need the default to be configurable? It may be best to leave this to the container configuration; the desired timeout strongly depends on the type of container (stateful, ephemeral)

Hello,
just wanted to chime in - I believe that this is a valid bug, I just have hit the same issue.
Problem 1: the documentation for "--shutdown-timeout" on https://docs.docker.com/engine/reference/commandline/dockerd/ is non-existing, leading users to believe that this indeed is the option to set the time between sig 15 and sig 9 for all containers. This should be fixed by putting the documentation @thaJeztah wrote here into the docs (and to me looks like it falls in the scope of #26828).
Problem 2: there is no way to globally set the stop timeout for all containers. This impacts people running Docker with orchestrators, frameworks or other controllers on top that do/can not issue --time when running docker stop, which in our case led to data loss multiple times as databases were not shutdown cleanly.
As for your question

do we need the default to be configurable? It may be best to leave this to the container configuration; the desired timeout strongly depends on the type of container (stateful, ephemeral)

I'd say the system operator knows what kinds of containers will be run on the machine and so should be free to set the default value to something that will work for his/her workload.


Fix incorrect "no master at ..." when running on separate host

The _is_master_alive function was only checking localhost instead of using the MASTER_HOST value, which was incorrect if running on separate hosts

(encountered when trying to docker'ify Pinball similar to #72)


Request for improvement

I need to apply an automation to vagrant for RancherOS. If you need some more material about I can send you some materials, else-way I am requiring if you have any plan for pull requests.
Thanks,
Fabrizio Torelli
(https://github.com/fabriziotorelli-wipro)

It would be helpful if you described what improvement you want. It's unclear what ST2 components you're referring to.
Pull requests are always welcome.


[ENH] Have @cython.overflow skip arithmetic on overflow

Is your feature request related to a problem? Please describe.
When using @cython.overflowcheck with tools like UBSAN you end up with failures because the arithmetic still is performed, giving you undefined results until the OverflowError gets raised
Describe the solution you'd like.
As far as I can tell Cython generates this code for multiplication overflow checking:
static CYTHON_INLINE int __Pyx_mul_const_int_checking_overflow(int a, int b, int *overflow) {
    if (b > 1) {
        *overflow |= a > __PYX_MAX(int) / b;
        *overflow |= a < __PYX_MIN(int) / b;
    } else if (b == -1) {
        *overflow |= a == __PYX_MIN(int);
    } else if (b < -1) {
        *overflow |= a > __PYX_MIN(int) / b;
        *overflow |= a < __PYX_MAX(int) / b;
    }
    return a * b;
}

Since the results of the multiplication are undefined I am guessing we could return almost anything here? Alternately we could give users a @cython.overflowcheck.return_value() decorator that specifies what value they would like back in such instances, or maybe even a new @cython.overflowcheck.fail_fast() decorator where the user can still choose to continue with the multiplication or not
Describe alternatives you've considered.
When using UBSAN you could also work with a suppression file, but I think that is harder for users to set up and properly maintain
Additional context
No response

I definitely don't think it's worth adding additional compilation options. The skipping the check part sounds reasonable to me

When you say skipping the check do you mean skipping the arithmetic?

When you say skipping the check do you mean skipping the arithmetic?

Yes - that's what I mean. Sorry for being a bit vague.

Actually I think this does already work this way, at least on platforms that have the overflow builtins looks like it is leveraging those. So probably nothing else for Cython to do - just have to wait for more compilers to support those


Migrate to Pydantic

TODO:

[ ] write unit tests to compare impls
[x] add models rebuilding at the end of models.__init__. how to determine the correct order?
[ ] migrate lexicon parsing to pydantic
[ ] fix collisions with reserved pydantic names (validate)
[x] fix parsing of records:

[x] bind _type field to understand type in Union ref
[x] implement resolving of "UnknownDict" type for records
[x] implement resolving of "UnknownDict" type did doc (fallback to DotDict)
[x] implement fallback to DotDict if the record is custom

[x] fix parsing of blob refs
[x] fix parsing of CIDs
[x] resolve lexicon refs without proxy class? instead of ResponseRef we could use resolved type directly
[ ] delete dacite package and related methods
[ ] use snake-cased fields with aliases to the original camel-cased. add backward compatibility?
[ ] backward compatibility for positions args in the model's constructor?

Dev build is available here https://github.com/MarshalX/atproto/discussions/119#discussioncomment-6830838


adding description about configuration in MVC.

#104
this pull request describe how the configuration in MVC work,following the orientation the @chkal .

Hi @Daniel-Dos,
thanks a lot for creating the PR. But I guess the section should contain a bit more about the configuration topic. I'm thinking about something like:

Explain that there are a few settings which must be supported by all implementations
Note that JAX-RS configuration is based on implementing a corresponding method in the Application subclass provided by the developer
Show a simple example for an Application subclass which configures a custom location of the view folder which is different from the default /WEB-INF/views.
Note that details about the concrete configuration options are described in the corresponding sections of the specification.

Thoughts?

Hi @chkal ,
I have a question regarding this  :

Explain that there are a few settings which must be supported by all implementations

how could you explain ?
thanks.

Beauty, I'll take a closer look at the weekend.

Hi @ivargrimstad,
I have not had time to see right yet.
Please do not make the merge yet.

thanks @ivargrimstad .

@chkal and @ivargrimstad ,
please review the commit  .
thanks.

Hi @chkal ,
please, review the new information.
thanks.


4k h265 to 720p h264

i got go2rtc installed in a container with an nvidia gpu presented.
nvidia-smi is working
image is go2rtc:master-hardware
from the same stream, i want to forward the original for record and downscaled 720p version for detect.
record is working tested via go2rtc UI and ffmpeg from a remote machine
detect stream plays tested via UI, but still shows 4k and avframe (is avframe h264?)
streams:
  # Input Stream: Original H.265 stream from the camera
  3F_Hallway_record:
    - rtsp://user:password@<IP_ADDRESS>:554/h265Preview_01_main
      # Native H.265 recording, no transcoding
      # Hardware decoding and encoding (NVIDIA)
      # Using 'copy' for both video and audio streams
    - ffmpeg:rtsp://user:password@<IP_ADDRESS>:554/h265Preview_01_main#video=copy#audio=copy

  # Transcoded H.264 for detection
  3F_Hallway_detect:
    - ffmpeg:rtsp://user:password@<IP_ADDRESS>:554/h265Preview_01_main
      # Convert to H.264, scale to 720p, limit to 15 FPS
      # Hardware-accelerated decoding and encoding
    - ffmpeg:rtsp://user:password@<IP_ADDRESS>:554/h265Preview_01_main#hwaccel=cuda#video=h264_nvenc#width=1280#height=720#fps=15#media=video

    $ ffmpeg -i rtsp://user:password@<IP_ADDRESS>:8554/3F_Hallway_detect -f null -
ffmpeg version 4.4.2-0ubuntu<IP_ADDRESS> Copyright (c) 2000-2021 the FFmpeg developers
  built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
  configuration: --prefix=/usr --extra-version=0ubuntu<IP_ADDRESS> --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  WARNING: library configuration mismatch
  avcodec     configuration: --prefix=/usr --extra-version=0ubuntu<IP_ADDRESS> --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared --enable-version3 --disable-doc --disable-programs --enable-libaribb24 --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libtesseract --enable-libvo_amrwbenc --enable-libsmbclient
  libavutil      56. 70.100 / 56. 70.100
  libavcodec     58.134.100 / 58.134.100
  libavformat    58. 76.100 / 58. 76.100
  libavdevice    58. 13.100 / 58. 13.100
  libavfilter     7.110.100 /  7.110.100
  libswscale      5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc    55.  9.100 / 55.  9.100
[rtsp @ 0x6330b8044680] method SETUP failed: 461 Unsupported transport
Input #0, rtsp, from 'rtsp://user:password@<IP_ADDRESS>:8554/3F_Hallway_detect':
  Metadata:
    title           : go2rtc/1.9.7
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Audio: aac (LC), 16000 Hz, mono, fltp
  Stream #0:1: Video: hevc (Main), yuv420p(tv), 3840x2160, 15 fps, 90k tbr, 90k tbn, 90k tbc
Stream mapping:
  Stream #0:1 -> #0:0 (hevc (native) -> wrapped_avframe (native))
  Stream #0:0 -> #0:1 (aac (native) -> pcm_s16le (native))
Press [q] to stop, [?] for help
[hevc @ 0x6330b8088dc0] Could not find ref with POC 12
Output #0, null, to 'pipe:':
  Metadata:
    title           : go2rtc/1.9.7
    encoder         : Lavf58.76.100
  Stream #0:0: Video: wrapped_avframe, yuv420p(tv, progressive), 3840x2160, q=2-31, 200 kb/s, 15 fps, 15 tbn
    Metadata:
      encoder         : Lavc58.134.100 wrapped_avframe
  Stream #0:1: Audio: pcm_s16le, 16000 Hz, mono, s16, 256 kb/s
    Metadata:
      encoder         : Lavc58.134.100 pcm_s16le
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 49 >= 49
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 65 >= 65
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 70 >= 70
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 94 >= 94
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 106 >= 106
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 109 >= 109
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 115 >= 115
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 118 >= 118
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 121 >= 121
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 125 >= 125
[null @ 0x6330b8077740] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 130 >= 130
frame=  132 fps= 17 q=-0.0 Lsize=N/A time=00:00:09.00 bitrate=N/A speed=1.18x
video:69kB audio:284kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
Exiting normally, received signal 2.

some guidance is appreciated.

You have many unsupported params for ffmpeg source. I don't know where you get them.
If you have changed default ffmpeg source params - it may broke hardware support.

after more testing you right, i definitely mixed up lots of the stuff i googled and read from reddit, frigate, and github.
i got it cleaned up now, the record stream works but the detect just shows all green
rtsp:
listen: ":8554"    # RTSP Server TCP port, default - 8554
username: "user"  # Optional, default - disabled
password: "password"   # Optional, default - disabled
default_query: "video&audio"  # Optional, default codecs filters
streams:
Input Stream: Original H.265 stream from the camera
3F_Hallway_record:
- rtsp://cam_user:cam_password@<IP_ADDRESS>:554/h265Preview_01_main
3F_Hallway_detect:
- ffmpeg:rtsp://cam_user:cam_password@<IP_ADDRESS>:554/h265Preview_01_main#video=h264#hardware#width=1280#height=720#fps=15
_record stream working as expected
_detect however is getting transcoded to h264 but has all green screen on the stream
error log:
h265Preview_01_main#video=h264#hardware#width=1280#height=720#fps=15 caller=github.com/AlexxIT/go2rtc/internal/streams/producer.go:170
ffmpeg from laptop to go2rtc
Metadata:
title           : go2rtc/1.9.7
Duration: N/A, start: 43856.377767, bitrate: N/A
Stream #0:0: Video: h264 (High), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], 24.58 fps, 24.58 tbr, 90k tbn, 49.17 tbc
Stream mapping:
Stream #0:0 -> #0:0 (h264 (native) -> wrapped_avframe (native))
Press [q] to stop, [?] for help
Output #0, null, to 'pipe:':
Metadata:
title           : go2rtc/1.9.7
encoder         : Lavf58.76.100
Stream #0:0: Video: wrapped_avframe, yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 24.58 fps, 24.58 tbn
Metadata:
encoder         : Lavc58.134.100 wrapped_avframe
am close to the h264 720p 15 fps target. perhaps you can point me to what am doing wrong.

made another tweak and the green screen cleared out and it's getting transcoded to 720p:
- ffmpeg:rtsp://cam_user:cam_password@<IP_ADDRESS>:554/h265Preview_01_main#video=h264#width=1280#height=720#fps=15
however i am uncertain if this is using the gpu to transcode.
nvidia-smi inside the go2rtc container doesn't show any ffmpeg process
nvidia-smi at the host level didn't show an another ffmpeg show up either.
what flag does one use for nvidia gpu transcode?

You definitely have some kind of hardware transcoding problem. That's why it's turned off by default. It is unpredictable in different environments.
First try hardware transcoding without resizing the picture.
PS. fps parameter is not supported. I don't know where you got it from.

hardware trancoding works with the cpu but can't seem to figure out the correct flags to get the gpu to do the work.
tried #video=264#hardware=cuda but that didn't do the trick as well so i googled and tested what i found that includes the fps lol
i found this from nvidia's docs hub:
ffmpeg -y -vsync 0 -hwaccel cuda -hwaccel_output_format cuda -i input.mp4 -c:a copy -c:v h264_nvenc -preset p6 -tune ll -b:v 5M -bufsize 5M -maxrate 10M -qmin 0 -g 250 -bf 3 -b_ref_mode middle -temporal-aq 1 -rc-lookahead 20 -i_qfactor 0.75 -b_qfactor 1.1 output.mp4
from that i gathered these flags would make sense testing:
#hwaccel=cuda#hwaccel_output_format=cuda#c:a=copy#c:v=h264_nvenc#b:v=4M
enable hardware acceleration, use cuda, copy audio, transcode video to h264, bitrate of 4Mbit... do correct me if how i converted those flags with # is wrong. am clearly over my head. lol


Property:storageFootprint

Definition

Dimension

Existing property

Existing class

Existing property identifier

Format
Numeric

Required

Repeatable
no

Constraints

Examples

Notes

Definition: Floor area taken by the collection
Example: 10 m2


docker.execute with output to terminal

I would like to get some statistics from inside my running Docker container. For this, I need to execute a command inside the Docker container.
My idea is something like that:
stats = docker.execute("<container name>", "<command>", interactive=True, tty=True)
print(stats)

But I can't get it to work.
I receive "the input device is not a TTY" if I run in pyCharm.
If I run in terminal, I got "OCI runtime exec failed: exec failed: unable to start container process: exec: "": executable file not found in $PATH: unknown"
Is that even possible?

In this situation, I don't think you want to use interactive and TTY

Yes, that was also my thought. But then following error occurs:
It returned with code 126
The content of stdout is 'OCI runtime exec failed: exec failed: unable to start container process: exec: "": executable file not found in $PATH: unknown
'
The content of stderr is ''

I think the command shoud be a list

You're right. It works with a list:
stats = docker.execute("<container name>", ["<command>"])
example: metrics = (docker.execute("busybox", ["sh", "-c", "whoami ; pwd"]))


docs: add how to use metrics doc and update base URL

Description
This PR:

Add Metrics Usage Guide docs both ZH and EN
Update base URL from https://oss.x-lab.info/open_digger/ to https://oss.open-digger.cn/
Fix sidebar i18n configs for EN site

Resolved issues
None.
Before submitting the PR, please take the following into consideration

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. If you don't have an issue, please create one.
[x] Prefix your PR title with feat: , fix: , chore: , docs:, or refactor:.
[x] The description should clearly illustrate what problems it solves.
[x] Ensure that the commit messages follow our guidelines.
[x] Resolve merge conflicts (if any).
[x] Make sure that the current branch is upto date with the main branch.

/preview

/preview


Add PersonDirectory sample code

Wondering if it will be better to name the sample as PersonDirectoryOperations or PersonDirectoryOps to be clearer?


Updated documentation covering Angular 18

Angular 17, 18+
The new documentation now covers installation on
Angular 18+ and is divided into smaller, more readable sections, making it
easier to digest than this big README. It also documents the additional
interfaces and explains how to develop custom plugins.
New documentation: https://ngx-translate.org/
In addition to that, a getting started tutorial is available here:
How to Translate Your Angular App with NGX-Translate
This Demo project
contains 3 simple example projects for Standalone components, NgModules, and
how to use the message format compiler. The branches contain the same
projects for older Angular versions.

Greetings are you part of the ngx-transalate team are you planning to take over the project from combe?

I currently have some additional privileges, such as handling tickets on the project: https://github.com/orgs/ngx-translate/people.
However, there isn't a formal "team" structure in place. We've never had meetings to discuss project direction, decision-making, or processes.
I'd like to take over the project since we have the resources to maintain ngx-translate in the long term and keep the library active. I proposed this two years ago, but the offer was declined. I tried reaching out to Olivier again last week, but I haven't received any response—neither via email nor on social media.
If I don't hear back from him soon, the only option may be to fork the project, although this seems questionable. It doesn’t make sense to essentially create a new library and start from scratch.

essentialy what we have done is when we dont hear back from the maintainter we put our our organization in front of it @windmillcode/[PACKAGE NAME] you might as well do the same . I know that you have enough resources but if there is any collaboration, promotion or help we can provide let me know

I've meanwhile forked the project:
@codeandweb/ngx-translate
@codeandweb/http-loader
The current work in progress is available as a beta version on npm.

Greetings our organization's library depends on ngx-translate would like to collaborate especially on testing issues  .Even promote by writing articles https://windmillcode.github.io/Windmillcode-Angular-CDK-Docs/
you can setup time to connect https://windmillcode.com/contact

Can you make fork public? Probably all should go migration to your new npm package and all issues will be open at that place

It's already available. I've released V16 of my fork last week. This migration guide explains how to switch to my fork and also explains the benefits of doing so:
https://ngx-translate.org/getting-started/migration-guide/

If all goes well, this should be arranged, soon see https://github.com/ngx-translate/core/issues/783#issuecomment-2440849415

Got permissions by Olivier to publish updates here...

Angular 17, 18+
The new documentation now covers installation on Angular 18+ and is divided into smaller, more readable sections, making it easier to digest than this big README. It also documents the additional interfaces and explains how to develop custom plugins.
New documentation: https://ngx-translate.org/
In addition to that, a getting started tutorial is available here: How to Translate Your Angular App with NGX-Translate
This Demo project contains 3 simple example projects for Standalone components, NgModules, and how to use the message format compiler. The branches contain the same projects for older Angular versions.

Hi @CodeAndWeb
The new documentation looks very nice and clear, thanks for your work =)
The actual README.md file will be updated as well (maybe with the content removed and a link to the new docs)
There I still can see the recommendation to the version core@15 and http-loader@8 of the libraries and there's no usage of the Standalone methods (that are already covered in the new docs)
In the Demo project pointed out in your issue above, there's no usage of the the Standalone way as well.
From my point of view, clean the readme file and just keep the right links will be better than try to keep both updated =)


Add transformer

add constrouctor ParserGeneratorOptions.fromMap so we can pass map options provenient from transformer
add PegTransformer that listen on any change of any dart file and produce parser file automatically (We should change this to listen on peg files changes instead)
add abstract_parser.dart which contains two classes AbstractParser and AbstractParserError. Those classes colud be extended by user to have autocompletion in the receiver code.

Need time for rethinking.

Please view sample code at https://github.com/luisvt/peg_transformer_sample and also review changes to readme. I think we don't need to put the entire generated code and stats

I have also added sample web code if you are interested

by the way, now transformer listen on peg files changes instead of dart files.

Thank you.
Your suggestions requires time for innovations that are not originally planned.
Currently I only have free time to correct found bugs.


Added check for meta class to set provider name

Added the ability to set the provider name via a meta subclass. If the subclass isn't available the name will be set using the standard way (cls.__name__.lower()).
Modified the test to use an alternate name to test the functionality.

@Battleroid I added it just now. :smile:

Woo!


train image

i am trying this paper in the caffe
i am using NYU2 raw depth dataset. about 12K~13K sampled depth image.
at the train task of you, did you use filtered image(cross bf or colorization) or not(raw depth image)?
colorization is good filter method but it is too slow

Hi,
The ground truth depth images used for training were actually raw depth images. Invalid pixels (where depth is zero) have been then excluded from training.

sorry, I have one more question.
'relative err : 0.129' in your paper is calcualated by only testNdx datas(hole filled) in 'nyu_depth_v2_labeled.mat'(654 Image pairs)? or All test scene Images in NYU_Depth_v2_raw dataset(about 200k image pairs)?

The error metrics are calculated over the official split of 654 images in the labeled subset of NYU (to fairly compare to prior works). In this case, we are using the depth maps which were filled-in using the colorization method and not the raw data. The errors should be lower when comparing to raw depth maps.

Hi, @seokhoonboo ! Have you successfully reimplement it in caffe? I have got some troubles, like how to set upsampling layer(since there is no direct upsampling layer like paper in caffe, instead I use deconvolution layer to replace upsampling, but it seems that the network is hard to learn anything...).

@jszhujun2010 it might be easier to implement upsampling in caffe. Training this network with deconv will be problematic. However, you might want to try not to learn the parameters of the deconv and only use it as a bilinear filter.

Thanks, @bazilas . I'll consider to write my own unsampling layer.

@jszhujun2010
https://github.com/matthieudelaro/caffeBVLCplus
this repository include unpooling layer, and i am trying by using it

Thanks, @seokhoonboo . I guess UnpoolingParameter_UnpoolMethod_MAX is what we need.

Hey, guys! I'm trying to train a model on Make3D dataset, here is details:

I resized all images to 172*230 as CNN's input(since the paper mentioned that all images are resized to 345*460 and then reduce the resolution by half), and augmented the data to 15k. I resized output data(305*55) to 172*230.

The CNN architecture is just as the paper's description except some minor changes. Since 4 upconv structure can not get 172*230, so I add another upconv layer(resulting 192*256) and a crop layer(as FCN segmentation).

I set leaning rate as 10^(-10) because larger lr will cause infinite loss. Other parameters are  exactly the same as paper.
However, there is no signal of convergence after thousands iterations. Is there anything I'm missing or wrong?

Hi! @iro-cp , I have one more question. Did you your fine-tune the whole network or just the part after the resnet?

@jszhujun2010
Regarding fine-tuning: All layers are trained for the depth estimation task, including both the core-ResNet and the upsampling part.
To answer your previous question: When you do the data augmentation you should make sure that you do not interpolate depth values that shouldn't be interpolated (for example when the ground truth depth map includes invalid pixels). In our work, all transformations are performed with nearest neighbor interpolation.
I think the lack of convergence is related to your very low learning rate. If you had to set it this low to avoid an infinite loss, you might want to make sure that there is everything is fine with your training data for example.

@iro-cp
Thanks for your reply. It's still for me to train the model, the model is even hard to overfit(using two images with batch size 2, original data without transformation).
I have forked the repository and added my caffe prototxt as well as some preprocessing scripts. You guys can check it if you are interested.
Repo is here, and caffe prototxt is in caffe folder.

Hi @jszhujun2010  Do you  train your model on NYU Depth v2  dataset successfully?

kind of... I have trained on NYU data without data agumention and the model can fit training data well(testing result not so good though, due to overfitting).

Hi @jszhujun2010  I have trained your model in the repository on NYU Depth v2 dataset, but I found the loss also can't converge. The  Loss map can be seen here.I don't why ? Is there any question?

Hi @jszhujun2010 I have trained your model in the repository on NYU Depth v2 dataset, but I found the loss also can't converge. The Loss map can be seen here.I don't why ? Is there any question?

I have modified the network and I'll update it recently.

@jszhujun2010
Thanks for your reply. I have trained your modified network on NYU Depth v2 dataset again. But I found the loss is still as shown above and can't converge.Is it normal?Is there any question?

Well, it's fine for me.

How many iterations is your setting?

@jszhujun2010
Thanks for your reply. I have set 300000 iterations on  NYU Depth v2 dataset.But the loss still can't converge.And the Loss map still didn't like the map as you show! Do you change anything of  your network?I don't why ?

What's your data? I only used 795 training images from official dataset(as a result, overfitting is quite obvious). I found that their training data is sampled from video, I'm too lazy to download that large file...
Another thing is that, I still cannot reimplement make3D dataset's experiment even in training(training loss can not decrease to ideal level). I guess there must be some trick in data preprocessing phase, but I still cannot figure it out... I think make3D is much more difficult to train because its depth range is too large for the network to learn.

looks like all problems are resolved. Please open another issue if there are open questions.

can you share the train code?

Could you share the pre-processing code to the make3d dataset? I can not find how to augment the training dataset from 343 to 15k， thank you


New version does not support devcontainer environmental variables.

So that we don't commit a redmine API key to git, it is nice to leverage the .env option when using devcontainers with docker-compose.
https://code.visualstudio.com/docs/remote/containers-advanced#_option-2-use-an-env-file
https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_variables-in-devcontainerjson
.env
REDMINE_API_KEY=4asd9na345lkjnc9d8934n5

docker-compose.vscode.yml
version: "3.7"
  services:
    gibson:
      environment:
      - REDMINE_API_KEY

.devcontainer.json
...
"dockerComposeFile": [
        "docker-compose.vscode.yml"
],
"extensions": [
	"rozpuszczalny.vscode-redmine"
],
"settings": {
	"redmine.apiKey": "${remoteEnv:REDMINE_API_KEY}",
	"redmine.identifier": "ProjectName",
	"redmine.url": "https://redmine.domain.com/"
}
"remoteEnv": {
	"REDMINE_API_KEY": "${containerEnv:REDMINE_API_KEY}"
}

Inside the container echo $REDMINE_API_KEY exports 4asd9na345lkjnc9d8934n5
Hardcoding "redmine.apiKey": "4asd9na345lkjnc9d8934n5" also works

Hi, thanks for raising this issue.
First, I'll have to dig into devcontainers, to see how it works - I never had a chance to work with devcontainers. I'll then try to see what my extension needs to cover to work with devcontainers.

Related to #29

Hi, thanks for raising this issue.
First, I'll have to dig into devcontainers, to see how it works - I never had a chance to work with devcontainers. I'll then try to see what my extension needs to cover to work with devcontainers.

Let me know if I can help.
Working Examples: https://github.com/search?q=org%3Amicrosoft+vscode-remote-try-&type=Repositories
Docs: https://code.visualstudio.com/docs/remote/containers

Hi @jonfen,
I dig it a little bit and I think using containerEnv or remoteEnv inside settings is not supported by VSCode itself. I even tried to use ${env:ENV_VARIABLE} with local workspace and that didn't work as well. I think it's related to this issue: https://github.com/microsoft/vscode/issues/2809 .
So unfortunately, I really cannot do anything to make it work the way you want to.
If you'll find any extension, which is working with referencing environment variables, please repoen this issue and link it here, so I'll dig it more :wink:


meshery: Fixed unexpected 404 while reloading adapter's page

Signed-off-by: Naveen Jain<EMAIL_ADDRESS>
Description

This PR fixes #861
Notes to reviewers:
Checklist

[x] DCO signed.
[x] Title of the PR starts with area name, e.g. meshery:, mesheryctl:, ui:.

@nveenjain this is an improvement for sure. One item to note is that when the page is refreshed, users don't always land back on the adapter that they have selected.

I strongly suspect this issue is do to out of order messages received through the go channel used by go routines to query all the adapters for their metadata. Assuming this is the case, this article might be of value -<EMAIL_ADDRESS>

https://github.com/layer5io/meshery/issues/871 opened to track this issue. Please self-assign, if interested in fixing.

@leecalcote @nveenjain Can you please me reproducing steps of the issue this PR has addresed ?
I have been trying for a while now but I didn't encountered issue #861 . Also I have already reverted this PR on my local. It would be great if you may guide me where is it giving 404 after refreshing?
I tried to refresh page http://localhost:3000/management?adapter=meshery-adapter_name:adapter_port but there was no error has stated in the issue .

@kushthedude, you bet.  I think we're talking about two items here. Repro steps for each:

Prior to the fix for https://github.com/layer5io/meshery/issues/861, it should be the case that when you nav to one of the adapter's (e.g. http://localhost:9081/management?adapter=meshery-linkerd:10001), then refresh your page, you would arrive a 404. Reminder: you may need to make build-ui, then make run-ui-dev.

Prior to PR https://github.com/layer5io/meshery/pull/872, it should be the case that while visiting a specific type of service mesh adapter (e.g. http://localhost:9081/management?adapter=meshery-linkerd:10001), when you refresh the page repeatedly, you will see different service meshes as being selected, not the selection you originally made.

@kushthedude, you bet. I think we're talking about two items here. Repro steps for each:

Prior to the fix for #861, it should be the case that when you nav to one of the adapter's (e.g. http://localhost:9081/management?adapter=meshery-linkerd:10001), then refresh your page, you would arrive a 404. Reminder: you may need to make build-ui, then make run-ui-dev.

I am able to produce the scenario before #872, but alas I am still unable to reproduce the scenario-1 which is before #861 . PS: I ran make build-ui before make run-ui-dev .

@kushthedude , it's actually working fine in development mode of ui. Hence working in 3000 port, but doesn't work after site is exported using next.

You would need to run make run-local and access the site from 9081 port...

You would need to run make run-local and access the site from 9081 port...

I think shouldn't accessing from make run-ui also throw the error. Because the behaviour which I am encountering before #862 is similar to the scenario-2 described by @leecalcote above, which makes me more curious about why there is such mis-alignment b/w ui & server rendered ui ?

Actually management.html is rendered by next js, there is no other file for management page, the server points /management?adapter=________ to management.html rendered in the out folder rendered by next. It should parse the query parameters from window location, which were ignore before #872.

@kushthedude right - make run local. My theory is that part of this misalignment is due to out of order messages received through the go channel used by go routines to query all the adapters for their metadata (adapter information being returned in different order on each page load) from the REST call. Following on this hunch, the UI should be matching on adapter name / menu item name, not an unstable array.


Add Content-Appearance header

Allows switching between the "full-width" and "fixed" page layouts.
The "fixed" layout renders the page in a narrow column. (Confluence default)
If not configured, it defaults to "full-width".

Thanks!


More flexible adapter/activity stubbing

Currently stubbing in Designer is all-or-nothing. You can only turn stubbing on/off globally. We need a more flexible approach that allows hard-wired responses only for certain adapters whether run with or without stubbing. This will work better when good data for actual calls cannot be relied on.
One option would be to invoke the self-hosted asset retrieval service (http://localhost:8080/mdw/asset/) to pull the hard-wired response that's available from the framework. In conjunction with issue #53, this would allow you to temporarily set the problem endpoint URL the asset URL. However this only works for GET. It might be worthwhile to implement a Stub REST service in the framework that can handle any request METHOD and return the desired response asset.

migrated this issue to the mdw-designer repo.
closed the issue,removed the milestone, removed the designer label , removed the project and marked as duplicate in this repo.

Reopening for SDWF.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/76 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

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

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-25-07-14-34 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-25-07-14-34

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


ER_NO_DB_ERROR

when I send too many request in front side, the knex throw ER_NO_DB_ERROR or ER_NO_SUCH_TABLE.
but the less request, it would return true reponse.
client: mysql

Could you provide more context?

In front side, I send many request at the same time.
like this;
`
for (let i = 0; i < 10; i++) {
ajax({
url: 'http://<IP_ADDRESS>:3000/api/v1/database/schema1/table1/' + i,
success: function (r) { }
});
TT.ajax({
    url:'http://<IP_ADDRESS>:3000/api/v1/database/schema2/table2/' + i,
    success: function (r) {  }
});

}
`
In the server side.
// koa // koa-router // app.js about knex init const knex =  require('knex'); let databaseConnection = knex ({     client: 'mysql',     connection: {         host: databaseConfig.host,         user: databaseConfig.user,         password: databaseConfig.password,         port: databaseConfig.port,         insecureAuth: true     }); ... // route.js router.use('/api/v1/database/:schema/:table/:id', function *(next) {     yield databaseConnection.raw('use :schema:', this.params.schema);     let r = databaseConnection(this.params.table).select().where('id', this.params.id);     this.body = r; })
so, I accept many request at the same time.
it would happen that ‘use schema1’ but ‘select * from schema2.table2 where id = ?’

Hi, Please try to drop express from your test code and provide runnable single file example how to reproduce the problem.
Also are you sure this one is doing correct query?
databaseConnection.raw('use :schema:', this.params.schema);

I'm pretty sure it sends just:
use :schema:;

to DB.
It probably should be:
databaseConnection.raw('use :schema:', this.params);

You can see what queries are sent to DB by setting DEBUG=knex:* environment variable to shell where you start your backend process.

sorry, This may be my server bug.
I would do processing in each layer of route.

the top route '/:schema' we  would do use :schema:;' and turn to the next route
the second route '/:table' we would do connection.shema.withSchema(’schema').hasTable(‘table’) to make sure table exists and turn to the next route
3 the underlying route ‘/:id’  we would get data with id.
Through debugging i found that the bug happen in the second route '/:table'. i drop connection.shema.withSchema(’schema').hasTable(‘table’) and the server work well.
at the end, sorry for my bad English.

I'll close this, since according to discussion this doesn't seem to be a bug in knex


"Add this lines to your config-node.toml" ... where?

The README says to

Add this lines to your config-node.toml

But it doesn't say what section to add it to. Should it be added to the [node] section?

this configuration is only for those who want to use their own Nano node. It is inside the "Nano" folder, inside the directory configured in the docker installation script.

Thanks. Yes, I have my own nano node and see the directory. I also figured you were referring to the config-node.toml file of the two that are in that directory.
My question though was what section of that file should it be added to. There are at least three in my file, and I'm guessing I should insert it into the first:
[node]

# Enable or disable voting. Enabling this option requires additional system resources, namely increased CPU, bandwidth and disk usage.
# type:bool
enable_voting = true

# Online weight minimum required to confirm a block.
# type:string,amount,raw
online_weight_minimum = "60000000000000000000000000000000000000"

# Percentage of votes required to confirm blocks. A value below 50 is not recommended.
# type:uint64
online_weight_quorum = 67

[node.websocket]

# WebSocket server bind address.
# type:string,ip
address = "::ffff:<IP_ADDRESS>"
# Enable or disable WebSocket server.
# type:bool
enable = true

[rpc]

# Enable or disable RPC.
# type:bool
enable = true

Correct, it's in the node section. Now I quote this detail in README.md. Thanks!
https://github.com/anarkrypto/confirmy-block/commit/2e2259230e755954f753e37abbcbf719a4f98669