Adding Microsoft SECURITY.MD#2
Merged
timenick merged 1 commit intoFeb 27, 2026
Merged
Conversation
timenick
deleted the
users/GitHubPolicyService/6eb8e284-81b0-4daf-a82d-73989620f602
branch
This was referenced Mar 31, 2026
This was referenced May 8, 2026
This was referenced Jun 17, 2026
DingmaomaoBJTU
pushed a commit
that referenced
this pull request
Jun 22, 2026
…sampling, promote_findings) Aligns the autoconfig POC code with docs/self-evolution-design.html section 4. Implements the components still marked TODO; champion-config, arch pruning (build_insight) and the feature-gaps log were already done. bench_utils.py (Fix #1/#2/#5): - run_perf_session: atomic single-session perf primitive - paired_ab_bench / adaptive_paired_ab_bench: interleaved baseline-vs-hypothesis A/B so DVFS drift cancels in the within-pair ratio; adaptive variant samples until the 95% CI is decisive (KEEP/DISCARD band) or MAX_PAIRS, returns verdict + CI - thermal_classify: COOL/WARM/HOT_RUN from a cold reference latency - session_cv: shared between-session noise-floor helper promote_findings.py (Fix #4, NEW): reads catalog-*-sweep/*/results.json, applies the L1->L4 confidence ladder (L2 = effect-size gate, L3 = >=2 models/arch, L4 = >=3 arch classes), writes ep_knowledge/_auto_promoted.json as a draft sink that never clobbers curated KB. Tolerant of both QNN (full.p50s_ms) and GPU/CPU (full_p50s_ms) schemas. catalog_qnn_sweep.py (Fix #1 wiring): opt-in --paired-ab flag (default off) that runs adaptive paired A/B per hypothesis against the baseline ONNX and records verdict + CI; sequential Phase B remains the default path. README: document the self-evolution tooling and refresh the directory layout.
DingmaomaoBJTU
pushed a commit
that referenced
this pull request
Jun 26, 2026
…gistry, non-mutating model_type override - registry: replace decorator/register API with a plain QUANT_FINALIZERS dict; get_quant_finalizer lazily imports + instantiates (review #1). - quantizer: resolve+apply the model-type-specific quant policy inside quantize_onnx from config.model_type, a single seam shared by all callers; drop the duplicated dispatch blocks in commands/build.py and build/hf.py (review #2). - loader: thread an explicit model_type as model_type_override through resolve_task instead of mutating hf_config.model_type, so exporters/patchers keep the architecture's native type while the loader config surfaces the build variant (review #4).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please accept this contribution adding the standard Microsoft SECURITY.MD 🔒 file to help the community understand the security policy and how to safely report security issues. GitHub uses the presence of this file to light-up security reminders and a link to the file. This pull request commits the latest official SECURITY.MD file from https://github.com/microsoft/repo-templates/blob/main/shared/SECURITY.md.
Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.