Does loggingServiceV2Client.ALL_SCOPES need cloud-platform scope?

I am a bit surprised by all the scopes that @google-cloud/logging requests by default:
/**
 * The scopes needed to make gRPC calls to all of the methods defined in
 * this service.
 */
var ALL_SCOPES = [
  'https://www.googleapis.com/auth/cloud-platform',
  'https://www.googleapis.com/auth/cloud-platform.read-only',
  'https://www.googleapis.com/auth/logging.admin',
  'https://www.googleapis.com/auth/logging.read',
  'https://www.googleapis.com/auth/logging.write'
];

Are these all – and specifically cloud-platform – necessary? @lukesneeringer @jmuk.

These are from the service configuration yaml file in https://github.com/googleapis/googleapis/blob/master/google/logging/logging.yaml
I am not sure about the choice of the scopes, we simply make the union of the all scopes of the rules.

I am not the authority on this, but my expectation would be that the following implies that either cloud-platform or logging.admin scopes would work for the specified RPCs.
      canonical_scopes: |-
        https://www.googleapis.com/auth/logging.admin,
        https://www.googleapis.com/auth/cloud-platform

/cc @munangst: can you confirm?

To be clear, cloud-platform appears on all three rules, so it needs to be eliminated from all of them if you want. Also please keep in mind that this configuration comes from our internal repository. You need to modify there.
Reviewing them, it's indeed weird to me too; for example, the second section (mostly for retrieving data) has both cloud-platform.read-only and cloud-platform. I don't know why.

@ofrobots Yes, you are correct, an OAuth token with any of the entries in the canonical_scopes list will be accepted. You can see this in the documentation for google.api.OAuthRequirements, which is the message used for this config.
The reason that some API methods accept multiple scopes is to allow different types of OAuth token to access that method. For instance, typically a read-only method like ListLogEntries would accept either cloud-platform.read-only or cloud-platform. A developer who wants the user to authorize access to both read-only and read-write methods would only have to request the cloud-platform scope, while a developer who only wants to authorize read-only methods would request cloud-platform.read-only. Likewise, the logging.* scopes are concentric, so logging.admin allows the admin actions as well as write and read actions.
(Note also that using scopes for access control is not recommended; Cloud IAM provides much finer-grained control over the set of operations a user or service account is allowed to perform. In most cases it's simplest to have the client request the cloud-platform or cloud-platform.read-only scope and rely on IAM roles to limit what the user can do.)

Yes, this would the library for logging, rather than end user applications – so we should be requesting minimal scopes to avoid misuse of privileges.
@jmuk, @lukesneeringer converting this to a bug. Does it belong google-gax repo?

Here's the part of the codegen to choose the list of the default scopes (https://github.com/googleapis/toolkit/blob/master/src/main/java/com/google/api/codegen/config/ServiceConfig.java#L48):

Scopes form a union and the union is used for down-scoping, so adding more scopes that
are subsets of the others already in the union essentially has no effect.
We are doing this for implementation simplicity so we don't have to compute which scopes
are subsets of the others.

So that's actually an intended behavior for "implementation simplicity" (also this is a common part of the codegen, any languages are affected). However, I don't think this causes problems so far. I mean, I agree that it's better to minimize the coverage of the scopes, but so far I'm not sure how this can be misused.
I'll open an internal discussion to gather more insights.

@jmuk @lukesneeringer @ofrobots what should we do here?

@jmuk What was the conclusion from the internal discussion?

Not much voice, as far as I remember.
However, considering that this would not lead to any misuses of the scopes and mostly our client use JWT which does not use scopes actually, I think it's okay to close this issue now without doing anything. @anthmgoogle FYI.

I am no longer on the team


URLs expire

I'm using S3 to server my static files. I'm currently running version 2.48 of boto.
When I upload images into the summernote widget, the images appear, but the URLs that represent the images expire after 1 hour. None of any of the other images that I upload to my site, which are served via AWS S3, have this problem.
Do you know what might be the cause of these expiring URLs and how I can fix it?
Thanks!

This problem might be caused by django storage extensions. Please refer the document of extensions for setting expiration of stored objects.
XRef: https://stackoverflow.com/questions/47774081/set-never-expire-on-amazon-s3-object


Warn about potential crash in "Getting Started"

Same changes as  #1479 but updated for the new docs format.

@austinried this lgtm. My only other thought is that technically this applies to 2.1 too which would be updated in the versioned_docs folder.Would you be able to do that too?

@jspizziri no problem, just pushed that change.


Add linting job for markdown files

Looking over #541 I noticed a handful of issues that would have been caught by https://github.com/markdownlint/markdownlint
I think we are at the point that we should step quality checks here as well.
Similar to #479 and #577  this job should only run if .md files are changed

Quickly looking I found https://github.com/actionshub/markdownlint
and I also noticed https://github.com/gaurav-nelson/github-action-markdown-link-check which might be fun to toss in

@VitaliyaIoffe Would this be something you might be interested in helping with?

@prince-chrismc yeap, please, assign this ticket to me


How to set batchsize?

Why i can't find batchsize?
Now training is slow,i want to improve it.

Thanks!


Add react-bootstrap-components

https://github.com/Hermanya/awesome-react-bootstrap-components
** While using react-bootstrap I found that many useful components are never merged into the library. This list brings more visibility for what react components are available for the most popular frontend library.  **
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

@aschrijver I believe my format works better for visual awesome lists.

@Hermanya We allow exceptions when it makes sense. In your case it does, but I'm still going to decline this as your list doesn't have much content. Happy to reconsider in the future when you add more content to the list though :)


Move device tree and defconfig from meta-xt-rcar to the product layer.

I have tested compilability of this PR and it's pair https://github.com/xen-troops/meta-xt-prod-devel-rcar/pull/24 - no issues detected during build.
Seems OK.

Acked-by: Ruslan Shymkevych<EMAIL_ADDRESS>


Object Detection Submission

I submitted my results to the evaluation server(https://bdd-data.berkeley.edu/portal.html#submission) but got 'processing undefined'. Do I make any mistakes or is the evaluation server still working?
I think I follow the detection evaluation format like this.
[
   {
      "name": str,
      "timestamp": 1000,
      "category": str,
      "bbox": [x1, y1, x2, y2],
      "score": float
   }
]

However, I always get this response.

Hi, did you figure it out?


Switch update strategy for project status

How to categorize this PR?

/area quality
/kind bug
Which issue(s) this PR fixes:
Fixes #5192
Special notes for your reviewer:
CC - @ialidzhikov
Release note:

NONE

/invite @timebertt @BeckerMax
/cla

I see c.Status().Patch() is being used in bunch of places in gardener/gardener. To me this PR does not provide any useful information/explanation why exactly this status patch does not work but all of the others work.

Same for me. I'm not sure, if I understand, how the change fixes the linked issue.

The issue seems to be the same as 2nd point mentioned here  #5295 (comment).
In the project controller also there are consecutive updates https://github.com/gardener/gardener/blob/31b8385f6fbae62af46e18f9c55a6e7624cec16e/pkg/controllermanager/controller/project/project_control_reconcile.go#L107-L151

I see c.Status().Patch() is being used in bunch of places in gardener/gardener. To me this PR does not provide any useful information/explanation why exactly this status patch does not work but all of the others work.

The issue seems to be the same as 2nd point mentioned here  #5295 (comment).
In the project controller also there are consecutive updates https://github.com/gardener/gardener/blob/31b8385f6fbae62af46e18f9c55a6e7624cec16e/pkg/controllermanager/controller/project/project_control_reconcile.go#L107-L151

/retest

We updated our findings in the issue https://github.com/gardener/gardener/issues/5192#issuecomment-1024129825 based on that @acumino will work on an updated PR

/invite @rfranzke @BeckerMax

/title Add keep-after-project-deletion annotation to project namespace only if the namespace creation is triggered by the project

/assign


java.lang.IllegalArgumentException: The given string value: {"uuid": ".........l} cannot be transformed to Json object

@vladmihalcea , I'm using com.vladmihalcea version 4.3 for saving several JSONs objects in my PostgreSQL database
data saving part is working as expected but there is an issue when deserializing particular rows.
//1st object

@TypeDefs({
		@TypeDef(name = "jsonb", typeClass = JsonBinaryType.class)
})
@AutoScaleFactor
@Entity
@Table(name = "TESTEXECUTIONPLAN")
public class TestExecutionPlanBO extends BusinessObjectImpl {
	private static final long serialVersionUID = -6454L;
	@Id
	private String testPlanID;
	private String testPlanName;
	private int testCasesCount;
    ......
       @Type(type = "jsonb")
       @Column(columnDefinition = "json")
	private JobVO jobVoJson;

//2nd object
@TypeDefs({
		@TypeDef(name = "jsonb", typeClass = JsonBinaryType.class)
})

@TrustedBO
@Entity
@Table(name = "EXECUTIONREQUESTS")
public class ExecutionRequest extends BusinessObjectImpl{

	private static final long serialVersionUID = -517242L;
	@Id
	private String uuId;
	private String orderId;
	........

	@Type(type = "jsonb")
	@Column(columnDefinition = "json")
	private ExecutionRequestVO executionRequest;
}

When listing both tables 1st table is working fine. When retrieving the second it gives the above error.
The issue is inside JsonTypeDescriptor.java
`
  private static Class<?> jsonObjectClass;

    @Override
    public void setParameterValues(Properties parameters) {
        jsonObjectClass = ( (ParameterType) parameters.get( PARAMETER_TYPE ) )
                .getReturnedClass();

    }

jsonObjectClass variable is not changing when it comes to the second table. both times it trying to deserialize by using same object class(JobVO). the second time it should be ExecutionRequestVO
What am I suppose to do to fix the issue
Hibernate version - 4.3.0.Final
PostgresSQL version - 42.1.3.jre7
com.vladmihalcea - 2.4.0

Try to replicate the issue with a test case. Once you could replicated it, send me a Pull Request so I could take a look on it.

Closed because no replicating test case was sent.


Relabel term [pulmonary fibrosis and/or bone marrow failure, telomere-related, 5 to ZCCHC8-related teleomere biology disorder]

Mondo term (ID and Label): MONDO:0032865, pulmonary fibrosis and/or bone marrow failure, telomere-related, 5
Suggested new label: ZCCHC8-related teleomere biology disorder
Your nano-attribution (ORCID) https://orcid.org/0009-0007-1636-9645
Optional: This request comes from the ClinGen Interstitial Lung Disease Gene Curation Expert Panel whom upon reviewing the curation of the ZCCHC8 and this disease entity found that a relabeled term was needed to encapsulate the phenotypes that may be recovered in future studies of this gene outside of IPF and bone marrow failure.

I added this disease name as a synonym with the tag "ClinGen label"

To be done via BioPortal KGCL.
@cmungall

Hello, I need to request an update here to correct the spelling. I incorrectly submitted it as "ZCCHC8-related teleomere biology disorder" when it should be "ZCCHC8-related telomere biology disorder". Please let me know if this can be updated before the 2024-05 Mondo Release, thank you! @sabrinatoro

Already fixed: https://github.com/monarch-initiative/mondo/pull/7757


Make Badge clickable

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.
👷♀Want to work on it

A screenshot of the github project with a topic "Make Badge clickable" isn't helpful or descriptive, especially as the text above the desktop screenshot isn't filled out.
You might want to add in the actual details before the bug report is closed without consideration.


Feature/tdslider 新增文本换行功能

🤔 这个 PR 的性质是？

[ ] 日常 bug 修复
[ ] 新特性提交
[ ] 文档改进
[ ] 演示代码改进
[ ] 组件样式/交互改进
[ ] CI/CD 改进
[ ] 重构
[ ] 代码风格优化
[ ] 测试用例
[ ] 分支合并
[ ] 其他

🔗 相关 Issue

https://github.com/Tencent/tdesign-flutter/issues/326
💡 需求背景和解决方案

📝 更新日志

fix(组件名称): 处理问题或特性描述 ...

[ ] 本条 PR 不需要纳入 Changelog

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[ ] 文档已补充或无须补充
[ ] 代码演示已提供或无须提供
[ ] Changelog 已提供或无须提供

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 4 committers have signed the CLA.:white_check_mark: shinyina:white_check_mark: Luozf12345:white_check_mark: Limpid-8818:x: v_szheshiv_szheshi 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.


Consider making a recommendation on how mismatched ELF attributes are handled by a linker/loader

Currently the spec says "Attributes are used to record information about an object file/binary that a linker or runtime loader
needs to check compatibility.". You might reasonably wonder what compability checks you should be performing. Therefore, I suggest the specification either:

Makes it explicit that the behaviour of compatibility checks are out of scope of this document (i.e. it takes no position on under what circumstances a warning should be emitted vs a failure to link)
Make a recommendation. e.g. recommending a warning but continuing to link by default.

I think @compnerd mentioned some issue related to this about linking in ELF files with no .text section (please correct me here / help link to the relevant issue).

Yes, this is effectively the issue.  https://reviews.llvm.org/D106378 was the associated LLVM review.

Looking again, the current text " Different architectures will be integrated into a superset when object files are merged." seems to imply that linkers should accept object files with mismatched attributes, as long as an ISA superset can be formed (i.e. the strings aren't fundamentally incompatible).

All attributes has explicitly specify the merge rule now, but apparently Tag_RISCV_arch need further clarification since we have incompatible extensions e.g. zfinx and f
For ELF flags, psABI don't have any merge rule yet, we need more clarification about that.


[1.76.1] Git decorations not shown in 1.76.1

Type: Bug
Open changed file in 1.76.0. Observe decorations existing on the gutter.
Upgrade to 1.76.1. Decorations gone in the same workspace, with the same file(s) opened. Or not gone. The behavior of 1.76.1 is erratic. Same types of files could show decorations or not.

Git is git-for-windows force configured in settings, picked proper.
2023-03-10 13:40:43.472 [info] Log level: Info
2023-03-10 13:40:43.473 [info] Validating found git in: "C:\Programs\Git\bin\git.exe"
2023-03-10 13:40:44.743 [info] Using git "2.37.2.windows.2" from "C:\Programs\Git\bin\git.exe"
2023-03-10 13:40:46.389 [info] > git rev-parse --show-toplevel [1581ms]
2023-03-10 13:40:47.468 [info] > git rev-parse --git-dir --git-common-dir [915ms]
2023-03-10 13:40:47.475 [info] Open repository: <project>
2023-03-10 13:40:48.520 [info] > git config --get commit.template [969ms]
2023-03-10 13:40:48.520 [info] > git rev-parse --show-toplevel [1002ms]
2023-03-10 13:40:48.875 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/DEVSTR-580 refs/remotes/DEVSTR-580 [1313ms]
2023-03-10 13:40:49.837 [info] > git rev-parse --show-toplevel [1228ms]
2023-03-10 13:40:49.965 [info] > git check-ignore -v -z --stdin [1275ms]
2023-03-10 13:40:50.474 [info] > git status -z -uall [1584ms]
2023-03-10 13:40:51.650 [info] > git rev-parse --show-toplevel [1688ms]
2023-03-10 13:40:52.217 [info] > git config --get commit.template [1666ms]
2023-03-10 13:40:52.305 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) refs/heads/DEVSTR-580 refs/remotes/DEVSTR-580 [1598ms]
2023-03-10 13:40:52.319 [info] > git rev-parse --show-toplevel [569ms]
2023-03-10 13:40:52.386 [info] > git check-ignore -v -z --stdin [603ms]
2023-03-10 13:40:52.906 [info] > git rev-parse --show-toplevel [575ms]
2023-03-10 13:40:53.351 [info] > git status -z -uall [1033ms]
2023-03-10 13:40:53.418 [info] > git rev-parse --show-toplevel [483ms]
2023-03-10 13:40:53.968 [info] > git rev-parse --show-toplevel [514ms]
2023-03-10 13:40:54.770 [info] > git rev-parse --show-toplevel [744ms]
2023-03-10 13:40:55.125 [info] > git rev-parse --show-toplevel [302ms]
2023-03-10 13:40:55.302 [info] > git rev-parse --show-toplevel [160ms]
2023-03-10 13:40:55.420 [info] > git rev-parse --show-toplevel [104ms]
2023-03-10 13:40:55.626 [info] > git rev-parse --show-toplevel [193ms]
2023-03-10 13:40:56.033 [info] > git show --textconv :app/admin/admin_cp.js [366ms]
2023-03-10 13:40:56.121 [info] > git ls-files --stage -- <project>:app\admin\admin_cp.js [431ms]
2023-03-10 13:40:56.400 [info] > git cat-file -s 7dd000c11366e6131ef18cefdf2b9022248522ee [260ms]

VS Code version: Code 1.76.1 (5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-8145U CPU @ 2.10GHz (4 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.86GB (0.65GB free)

Process Argv
--folder-uri file:///d%3A/Profiles/anrdaemon/Documents/hk/invapi-php

Screen Reader
no

VM
0%

Extensions (30)

Extension
Author (truncated)
Version

vscode-json
and
1.5.2

vscode-intelephense-client
bme
1.9.5

vscode-eslint
dba
2.4.0

diff
dup
0.0.1

gitlens
eam
13.3.2

vscode-html-css
ecm
1.13.1

EditorConfig
Edi
0.16.4

vscode-firefox-debug
fir
2.9.8

todo-tree
Gru
0.0.224

better-shellscript-syntax
jef
1.4.5

bash-ide-vscode
mad
1.35.0

jupyter
ms-
2023.2.1200692131

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

remote-ssh
ms-
0.98.0

remote-ssh-edit
ms-
0.84.0

hexeditor
ms-
1.9.11

remote-explorer
ms-
0.2.0

sqltools
mtx
0.27.1

sqltools-driver-mysql
mtx
0.5.1

sqltools-driver-pg
mtx
0.5.1

sqltools-driver-sqlite
mtx
0.5.0

php-docblocker
nei
2.7.0

tcl
ras
0.1.0

LiveServer
rit
5.7.9

html-to-css-autocompletion
sol
1.1.2

branch-in-window-title
wis
0.1.4

php-debug
xde
1.32.0

Can confirm as well. No more git changes are being displayed for the currently opened files. Changes are now only visible in the Source Control Panel.
Version: 1.77.0-insider (user setup)
Commit: b60db78000bfa99d1b290194ed4651c4ceef02cc
Date: 2023-03-10T05:24:23.805Z (7 hrs ago)
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: Yes

Please use the Start Extension Bisect command to check whether any of your extensions is causing this.

Didn't do anything for me, in the first step (all extentions disabled?) I still could not see any git decorations.
Is there maybe a connection to https://github.com/microsoft/vscode/issues/176738 ?

pinging @alexr00

Same issue here. Tested on local repos (not symlinked or anything fancy), deactivated all 3rd party extensions but still no gutter decoration at all. Uninstalled VSCode, reinstalled latest (1.76.1), checked again, but same issue.
Rollback to 1.75.1 worked for me, but didn't test rollback to any earlier 1.76.x

I am experiencing the same issue (on 1.76.1), but only for my current repository. I tried opening an older repo and saw git decorations, but going back to the project I'm working on, I don't see any. I've tried disabling and re-enabling the built-in git extension as well as git lens, restarting my pc, and deleting/re-cloning the repo.

I am not using a multi-root workspace and I have this problem.

same issue as well.
same repo, same directory, some file change will have the highlight, but some is not.

I am not using a multi-root workspace and I have this problem.

I have a feeling this is not related to multi-root workspace at all.

I rolled back to 1.76.0 and cancel the auto update. Then the git decorations are shown.
You can download the older version in this link:
https://code.visualstudio.com/docs/supporting/faq#_previous-release-versions

For me it is not working under Windows and works fine under WSL.

Related Stack Overflow question: Why aren't SCM diff decorations showing in the gutter in VS Code 1.76.1?

To be absolutely precise, even ongoing editing decorations aren't shown, even though the file is clearly under VCS control as shown on the SCM sidebar.

FWIW: I have the same issue, but with inconsistent behavior: There are files that don't show the decorations and some that do. Same file type in both cases. Could not determine any pattern yet that would explain which files work and which don't.
Version: 1.76.1 (system setup)
Commit: 5e805b79fcb6ba4c2d23712967df89a089da575b
Date: 2023-03-08T16:32:00.131Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

Possible pattern: In the repo I'm working in, I only have the problem with files that were added to the repo very recently (e.g., since Sunday). Is this affecting all files added after installing the latest vscode release? Maybe some caching issue?

Duplicate of #176738, which has a fixed merged for it.
Folks who are seeing this issue: Could you please install the latest insiders build and confirm that you no longer see the issues there?

I can confirm it is not fixed for me:

@KristofStroobants, it looks like you don't have any local changes. This issue is about these git gutter decorations:

@KristofStroobants, it looks like you don't have any local changes. This issue is about these git gutter decorations:

But shouldn't is also show the remote changes?

@KristofStroobants isn't this feature based on the results of git diff? git diff doesn't show "behind" / upstream changes unless you tell it to (if I understand correctly).

Yup gutter does not show up on me as well,, this makes hard to check changes in my file.. I hope they fix it on next update.

@alexr00 Is there any way to fix this without having to install Insiders? Or: When is an update in the official stream to be expected?

Insiders builds are installed separately, and using different configuration directory. So you could always install Insiders build and check without affecting your "production" setup.

Thanks for the heads-up, @AnrDaemon!
@alexr00 In Insiders, I see the Git decorations.

Stable update is planned for today.

Same here, it's been a week.
Finally fix it until now

Same here, it's been a week.
Finally fix it until now

So have you updated to 1.76.2?

was updated to 1.76.2, gutter started showing

Man this problem was driving me CRAZY on 1.76.1. Didn't realize it was a recent bug causing it and thought it was some obscure issue with my VS Code or Git configuration or even a recent Windows 11 update (then it happened on my Linux PC too lol). Tried every possible tip I could on the internet and nothing helped.
But I just now got prompted to update, now on 1.76.2 and git changes are BACK!

I hope you learned a lesson to never let your software autoupdate?
At the very least you will know that update had happened and any change in behavior is likely caused by it.

Same here, it's been a week.
Finally fix it until now

So have you updated to 1.76.2?

yes sir


test suite is failing on AWS083

Describe the bug
Testsuite is failing using go version go1.16.4 linux/amd64
$ go test -run "TestExampleCode/Check_'bad'_example_code_for_AWS083" -v ./internal/app/tfsec/...
?       github.com/tfsec/tfsec/internal/app/tfsec/security      [no test files]
=== RUN   TestExampleCode
=== RUN   TestExampleCode/Check_'bad'_example_code_for_AWS083
    setup_test.go:99:
                Error Trace:    setup_test.go:99
                                                        example_code_test.go:55
                Error:          Should be true
                Test:           TestExampleCode/Check_'bad'_example_code_for_AWS083
                Messages:       result with code 'AWS083' was not found but should have been
--- FAIL: TestExampleCode (0.01s)
    --- FAIL: TestExampleCode/Check_'bad'_example_code_for_AWS083 (0.00s)
FAIL
FAIL    github.com/tfsec/tfsec/internal/app/tfsec/test  0.012s

To Reproduce
make test

Well, I can reproduce it on a Linux machine. Interestingly MacOS and Windows both build fine with 1.16.4

resolved, missing body in AWS083


Charset problem when playing buffer

When I upgraded ZNC from 1.6.5 to 1.7.0, strange thing starts to happen. When I connected to my ZNC with AdiIRC, the buffer is garbled, looking like UTF-8 text interpreted as UTF-7. Real-time chat, query, backlog module, etc. seems like working as expected. Of course my server and client set to use only UTF-8 to communicate.
I'm not sure which one is to blame, but this problem disappears when I downgrade ZNC to 1.6.5. So it was my first choice to report this problem here.

Show exact output of znc --version. What modules are loaded? What encodings did you select for user and network in ZNC?

I've compiled znc from tarball, on my Raspberry Pi running Debian buster. The output of $ znc --version is:
ZNC 1.7.0 - https://znc.in
IPv6: yes, SSL: yes, DNS: threads, charset: yes, i18n: no, build: autoconf

Part of my znc.conf follows:
AnonIPLimit = 5
AuthOnlyViaModule = false
ConfigWriteDelay = 0
ConnectDelay = 5
HideVersion = true
LoadModule = webadmin
LoadModule = adminlog
LoadModule = backlog
LoadModule = modpython
LoadModule = weblog
LoadModule = block_motd
MaxBufferSize = 500
ProtectWebSessions = false
SSLCertFile = /home/znc/.znc/znc.pem
SSLDHParamFile = /home/znc/.znc/znc.pem
SSLKeyFile = /home/znc/.znc/znc.pem
ServerThrottle = 30
Skin = _default_
StatusPrefix = *
Version = 1.7.0

<Listener listener0>
        AllowIRC = true
        AllowWeb = false
        IPv4 = true
        IPv6 = false
        Port = 6667
        SSL = true
        URIPrefix = /
</Listener>

<Listener listener1>
        AllowIRC = false
        AllowWeb = true
        IPv4 = true
        IPv6 = false
        Port = 8082
        SSL = true
        URIPrefix = /
</Listener>

<User irtc1015>
        Admin = true
        Allow = *
        AltNick = I110_Gyeyang_
        AppendTimestamp = false
        AuthOnlyViaModule = false
        AutoClearChanBuffer = true
        AutoClearQueryBuffer = true
        ChanBufferSize = 100
        ClientEncoding = utf-8
        DenyLoadMod = false
        DenySetBindHost = false
        Ident = IRTC1015
        JoinTries = 10
        LoadModule = log
        LoadModule = alias
        LoadModule = controlpanel
        MaxJoins = 5
        MaxNetworks = 5
        MaxQueryBuffers = 0
        MultiClients = true
        Nick = I110_Gyeyang
        NoTrafficTimeout = 180
        PrependTimestamp = true
        QueryBufferSize = 50
        QuitMsg = Disconnecting
        RealName = IRTC1015 aka I110_Gyeyang, powered by ZNC
        TimestampFormat = [%H:%M:%S]

        <Network default>
                Encoding = UTF-8
                FloodBurst = 4
                FloodRate = -1.00
                IRCConnectEnabled = true
                JoinDelay = 2
                LoadModule = sasl
                LoadModule = push
                LoadModule = keepnick
                LoadModule = kickrejoin
                LoadModule = simple_away
                LoadModule = route_replies
                LoadModule = autoattach
                LoadModule = stickychan
                LoadModule = watch
                QuitMsg = Shutting Down...
                Server = chat.freenode.net +6697
                TrustAllCerts = false
                TrustPKI = true
        </Network>
</User>

This is a screenshot from my PC running AdiIRC. The texts in quotes are intended to be exactly same, saying "안녕하세요", whitten in Korean alphabet.

How did you detect this as UTF-7?
Does znc -D show anything interesting during playback or before?

Nothing but bunch of PRIVMSGs. Strangely, other clients(I've tried HexChat and AndroIRC) don't seem to have charset problem with buffer. As far as I can see from the console, the buffer data itself seems to be correct UTF-8.
I've tried saving bunch of text as UTF-8 file and opening it as UTF-7. I got similar result with one from AdiIRC; for example, "안녕하세요"  becomes "ìëíì¸ì", just like you can see from the screenshot.
So it can be a bug of only AdiIRC, not of ZNC. What I want to know is what makes AdiIRC behave like that, as it never happened before I installed ZNC 1.7.0.

No idea... Try to use wireshark or tcpdump to see what encoding it sends during buffer playback.

Aargh, Wireshark gave me answer...
Packet from 1.7.0 have "batch" in message(which doesn't appear in one from old version...it's IRCv3 implementation, right?). This is something changed in 1.7.0, and which I wanted to know. IT was something that AdiIRC handles wrong. To tell the truth, the bug seems to be already fixed in beta version of AdiIRC(which I never tried).
I'm sorry for making you spend some time for me.

How does batch cause UTF-7 though?
"batch" is implemented now, but it's not sent unless client requests it...
which it does.
2018-05-08 19:07 GMT+01:00 IRTC1015<EMAIL_ADDRESS>
Aargh, Wireshark gave me answer...
Packet from 1.7.0 have "batch" in message(which doesn't appear in one from
old version...it's IRCv3 implementation, right?). This is something changed
in 1.7.0, and which I wanted to know. IT was something that AdiIRC handles
wrong. To tell the truth, the bug seems to be already fixed in beta version
of AdiIRC(which I never tried).
I'm sorry for making you spend some time for me.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/znc/znc/issues/1526#issuecomment-387491564, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAT15CP4Fx7kF1B-e4Gl07ah1QW8KsNvks5twd7WgaJpZM4Tz5E-
.

I have no idea. They just marked it as resolved without further explanation. Who on earth uses UTF-7 anyway?

Well, good that it's resolved.
Btw, batch would be visible in znc -D too.


Error using an image which already exists in another storage driver

My docker installation has the image ubuntu already installed on the devicemapper driver.
If I restart my docker daemon with the aufs daemon, I get an error when using the ubuntu image:
# docker run ubuntu echo hello
2013/11/28 22:58:20 Error: create: Unable to mount using aufs invalid argument
# dmesg | tail -n 1
[246620.657816] aufs opt_add:714:docker[28297]: lookup failed /var/lib/docker/aufs/diff/8dbd9e392a964056420e5d58ca5cc376ef18e2de93b5cc90e868a1bbc8318c1c (-2)
#

I verified this with multiple images, not just ubuntu. If the image exists on the other driver, it fails. If it doesn't exist on the other driver, it works.

I'm not sure I see the point of the issue right now?
Is this issue specifically that docker won't pull ubuntu if it's loaded from a previously run graph driver or is there something deeper here?
If so it seems like that is no longer an issue.

I think we can close this one now. You will not get an error anymore because the image tags are stored in driver specific files.


show application trait status

example:

I was working on it but not able to continue it due to some personal reasons. You can take over if you would like to. You can refer this PR #449 if you want to.


Custom x86 backend resource usage for very large programs

When compiling/encoding very large programs with the custom x86 backend (in hobbes/mc), we use more memory than necessary by storing liveness at each program point.  Instead, we should store liveness just at join points in the control flow graph and interpolate within basic blocks.
Also for very large programs, where variable counts exceed int32 representation in the interference bit matrix, we need to raise an error on truncation rather than silently truncating (and losing interference information).  Also to allow such programs to be compiled, we should widen the var set index type to 64 bits.
These issues are both fixed by this PR: https://github.com/Morgan-Stanley/hobbes/pull/306

For some reason, I can't assign this to myself, but I did resolve it in that PR.
This isn't a new feature, but addresses some scaling issues encountered with very large programs sent through this alternative backend.

Perhaps it's due to the 'Triage' role, please have another try.

I'm not sure why it is, when I click on "Assignees" it opens a dropdown window with a circular "loading" indicator that never changes.  It doesn't tell me I can't do it, it just appears to get stuck.
Weird.


Certificate errors on sites with IP SSL

I'm getting "remote certificate" errors when using the SDK against sites with IP-based SSL certificates set up. I'm guessing this is an issue with the server-side code? Is it a known issue, and if so is there any timeline for a fix?

Hi @markcowl ,
This issue seems related to my question so I'll ask here instead of opening a new thread if you don't mind.
I've been reading up on [certificate pinning].(https://www.owasp.org/index.php/Certificate_and_Public_Key_Pinning) As I'm working on a project which involves Azure blob storage, I was wondering what was the validation process for certificates in the azure sdk.
I assume from your comment above that the mechanism for a client using the azure sdk is the same as the browser uses when deciding on a certificate.
However how should the client respond if there's a MITM attack proxying the azure blob storage?
Would it fail?


Move image pushing into CircleCI

What this PR does / why we need it:

Moves/updates the travis deploy script to work on circleCI.
Added DOCKERHUB_TOKEN via web UI to circleCI
runs publishing of images on master branch and on tags like v.*
minor change to naming to clarify job purposes

Which issue(s) this PR fixes
Ref: #926
Special notes for your reviewer:
I tried to use circleCI on my own repo to show this behavior to some extent. You can see here: https://circleci.com/workflow-run/9fdeb6cc-04ae-4e11-9173-bc2f06c14f40 that the publishing waits for the tests to pass. In addition, you can see https://circleci.com/workflow-run/9a9a49a3-5279-40ab-8638-9803a92063e1 doesn't show that the publishing would have occurred at all since it wasn't on the master branch.
Release note:
NONE

Codecov Report

Merging #945 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #945   +/-   ##
=======================================
  Coverage   47.78%   47.78%
=======================================
  Files          76       76
  Lines        5226     5226
=======================================
  Hits         2497     2497
  Misses       2573     2573
  Partials      156      156

Continue to review full report at Codecov.

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


Support multiple aws profiles/accounts

I'm working with a team that has multiple aws accounts.  It would be cool to not need the AWS_PROFILE environment variable.  Instead, something like:
ec2_instance { 'foo':
  profile => 'account1'
}

that would use the different entries in ~/.aws/credentials.  The upside would be I could run puppet apply across multiple manifests across multiple accounts.  I don't think I can do that with the existing setup.  Thoughts?

I would second this. I work across a number of AWS accounts. This would allow me to have a central repository for all IaaS configs. Using CF and Jenkins to do it right now, but supporting profiles in this module would be great.

Hi @benpillet. That's potentially a good idea. I don't think we'll be adding this immediately unfortunately due to other priorities but I'll leave this issue open as a reminder, or in case someone else has time and would like to submit a PR.

+1

@garethr any update here? I got another customer with the same request to support multiple aws profiles/accounts

+1

+1

+1

+1


Advanced search features

List of features to add to advanced search query builder:

Metadata List

[x] Format properties
[x] Update descriptions where computational tool and dataset have overlap.
[x] Remove properties that we don't want to include.
[x] Searchbar for metadata fields
[x] Add metadata description for each item (where available)
[x] clear fields on submit/reset

Input

[x] Custom input based on field type
[x] Add phrase suggester
[x] Remove predictive search for "all fields" - slow.
[x] Add stronger debounce for "all fields"
[x] Idea: Change "starts and ends with" to "contains"
[ ] Add validation to input

[ ] For multiple terms: "Did you mean to exact match these terms?"

[x] Enable exact and wildcard searches
[x] "Field exists" queries
[x] clear fields on submit/reset

Drag and drop

[x] Thicker color strip
[x] Add type of search to tags. (i.e. wrap term in quotes for exact, use asterisks for wildcard) and add descriptor to tag above or  below field ("exact", "contains", etc)
[x] Bold field in "Must contain [field] field"

Other

[x] Make rawquery section area more obvious ( toggle should say "view", "hide" and should share background with rawquery to make associtation more obvious).
[x] Allow user to edit the raw query
[x] Add validation for raw query editing
[x] Display results count

The validation for input feature will be excluded until after UX test confirms that this feature will help more than it will harm


Remove the .0 suffix when encoding whole-value reals.

This was a behavioral change in PropertyListEncoder when switching from the ObjC/C property list format to the new Swift one.

@swift-ci test

Oops, @iCharlesHu posted this as #718


Add missing note to get-teamChannel

Get-TeamChannel was missing the note for PS INT gallery, I'm adding it to the docs as there is extra functionality for the Graph /beta endpoint in get-teamChannel

Docs Build status updates of commit 80cd416:
:clock10: Full build: the average full build time is 12 min(s) 8 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 80cd416:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-TeamChannel.md
:white_check_mark:Succeeded
View (teams-ps)

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.

Docs Build status updates of commit 82c5a23:
:clock10: Full build: the average full build time is 12 min(s) 8 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 82c5a23:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-TeamChannel.md
:white_check_mark:Succeeded
View (teams-ps)

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.


happy not recognizing detached mode for operations

We need happy to recognize that the GHA's are running in detached mode, specifically for the rdev-delete-for-pr workflow, which needs to be able to delete even in cases of a stack being in an error state. Updating to 0.110.1 will solve this.
https://chanzuckerbergteam.slack.com/archives/C01C310V70X/p1696544208421629

Going to attempt an omnibus update of happy across all GHAs

Appears to have worked just fine


Fixes #465 by explicitly trimming STL vector size (some ROOT files have unused/padding/junk in each event after the vector's serialized data).

@tamasgal This should fix your issue. As described here, the STL vector includes information about its length that we had been ignoring because ROOT also gives the position of the start of each event, so normally the STL vector size is redundant. But you've found a case where there's unused bytes/padding/junk written to the file after the STL vector itself, making the STL vector size not redundant.
Now uproot.asjagged has an additional parameter (sizeat) for the byte position of an integer that specifies each jagged subarray's size and STL vectors set that parameter. (Other jagged arrays do not because they don't have that information.) In most cases, it's still redundant, so we check that it agrees with the sizes inferred from the ROOT event starts and only trim the data if they disagree.

Oh, I forgot to say: please stress-test this. Thanks!

Thanks Jim! I'd like to add tests if it's ok...

I'm afraid it's going deeper in the rabbit hole...
The fix now nicely cuts off the uninitialised values, but the shape is still not right.
In [4]: import uproot

In [5]: f = uproot.open("usr-nested.root")

In [6]: f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array()
Out[6]: <ObjectArray [[b'bx', b'by', b'ichan', b'cc'] [b'bx', b'by', b'ichan', b'cc'] [b'bx', b'by', b'ichan', b'cc'] ... [b'bx', b'by', b'ichan', b'cc'] [b'bx', b'by', b'ichan', b'cc'] [b'bx', b'by', b'ichan', b'cc']] at 0x000119099c10>

In [7]: f['E']['Evt']['mc_trks']['mc_trks.usr'].array()[0]
Out[7]: array([0.048692, 0.058846, 3.      , 2.      ])

In this case, the [0]-th entry of both usr_names and usr should contain the same number of sub-arrays as any other attribute in mc_trks, like mc_trks.pos.x:
In [11]: f['E']['Evt']['mc_trks']['mc_trks.pos.x'].array()[0]
Out[11]:
array([32.263, 32.263, 32.263, 32.263, 32.263, 32.263, 32.263, 32.263,
       32.263, 32.263, 32.263, 32.263, 32.263, 32.263, 32.263, 32.263,
       32.263, 32.263, 32.263, 32.263, 32.263])

So the correct output output of f['E']['Evt']['mc_trks']['mc_trks.usr'].array()[0] would be 21 sub-items:
>>> f['E']['Evt']['mc_trks']['mc_trks.usr'].array()[0]
array([0.048692, 0.058846, 3.      , 2.      ] [63.2413] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []))

and the f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array()[0] also a nested list of:
>>> f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array()[0]
[[b'bx', b'by', b'ichan', b'cc'], ['energy_lost_in_can'], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], []]

At least in the usr_names field I see the energy_lost_in_can using uproot.debug:
In [15]: f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array(uproot.asdebug)[0]
Out[15]:
array([ 64,   0,   0, 120,   0,   9,   0,   0,   0,   4,   2,  98, 120,
         2,  98, 121,   5, 105,  99, 104,  97, 110,   2,  99,  99,   0,
         0,   0,   1,  18, 101, 110, 101, 114, 103, 121,  95, 108, 111,
       115, 116,  95, 105, 110,  95,  99,  97, 110,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0], dtype=uint8)

In [16]: f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array(uproot.asdebug)[0].tostring()
Out[16]: b'@\x00\x00x\x00\t\x00\x00\x00\x04\x02bx\x02by\x05ichan\x02cc\x00\x00\x00\x01\x12energy_lost_in_can\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'

Since we expect 19 missing entries (0 length strings) after energy_lost_in_can and the scheme is always [length][string], it seems that 4 bytes are used to decode an empty string. Maybe it's just padding? So the first byte is \x00 and the the remaining \x00\x00\x00 are for the padding. The trailing \x00 in the usr_names field are at least exactly 76 bytes, which is divisible by 19 yielding 4 😉
In [20]: b = b"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\
    ...: x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
    ...: \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x0
    ...: 0\x00\x00\x00\x00\x00\x00\x00\x00\x00"

In [21]: len(b)
Out[21]: 76

In [22]: len(b)/19
Out[22]: 4.0

One question is, how to interpret this as a nested list?

Btw. another similar structure is the trks.fitinf attribute of the Trk class (which also derives from AAObject) and is a list of lists. That one is parsed perfectly fine in uproot.
This is from the same file, which contains 636 tracks in the first event and therefore 636 sub-arrays in the fitinf attribute:
[ins] In [7]: import uproot

[ins] In [8]: f = uproot.open("usr-nested.root")

[ins] In [9]: f['E']['Evt']['trks']['trks.fitinf'].array()[0][:2]
Out[9]:
[[0.048538346479761546,
  0.03306135757929911,
  -38.38983929899999,
  17.0,
  0.0,
  0.0,
  2.1429282348347063,
  62.0,
  4.954644469809049,
  4.954644469809049,
  6.779622631909124],
 [0.036081671195352216,
  0.025045466802941046,
  -32.477731698672045,
  17.0,
  0.0,
  0.0,
  3.266832183594016,
  12.0,
  8.289712676040777,
  8.289712676040777,
  15.719224788428178]]

[ins] In [11]: len(f['E']['Evt']['trks']['trks.fitinf'].array()[0])
Out[11]: 636

Well, I don't see anything in the C structs or the ROOT metadata that suggest that f['E']['Evt']['mc_trks']['mc_trks.usr'] ought to be nested (more than a single jagged array across events; i.e. a single 1-D array in each event).
But also, the two branches you're looking at have the same jagged structure (correcting for the ObjectArray with an awkward.fromiter):
>>> mc_trks_usr_names = awkward.fromiter(f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array())
>>> mc_trks_usr = f['E']['Evt']['mc_trks']['mc_trks.usr'].array()
>>> numpy.array_equal(mc_trks_usr_names.counts, mc_trks_usr.counts)
True

As a demonstration of this, we can match a string name to each numerical value—they're one-to-one:
>>> named_pairs = awkward.JaggedArray.zip(mc_trks_usr_names, mc_trks_usr)
>>> named_pairs
<JaggedArray [[(b'bx', 0.048692) (b'by', 0.058846) (b'ichan', 3.0) (b'cc', 2.0)] [(b'bx', 0.146713) (b'by', 0.400233) (b'ichan', 3.0) (b'cc', 2.0)] [(b'bx', 0.134258) (b'by', 0.077309) (b'ichan', 3.0) (b'cc', 2.0)] ... [(b'bx', 0.0) (b'by', 0.0) (b'ichan', 5.284424934e-315) (b'cc', 1.3742287462714573e-122)] [(b'bx', 5.304989477e-315) (b'by', 5e-324) (b'ichan', 175.476) (b'cc', 0.384255)] [(b'bx', 3.0) (b'by', 2.0) (b'ichan', 2.655811498e-314) (b'cc', -2.0868684099274518e-254)]] at 0x7f15ee0ad850>

This is very weird 😕 The data is definitely nested.
I was always confused about this . (dot) in the branch name, which might be used as a hint that something is nested? At least I only see this . in branch names for the "children" of the Evt class (branch).
What do you think?

Btw. another similar structure is the trks.fitinf attribute of the Trk class (which also derives from AAObject) and is a list of lists. That one is parsed perfectly fine in uproot.

The surprising thing is that ROOT is not trimming the serialized std::vector before writing it. The std::vector is valid, it says what its length is, and we know where each event starts. It's possible that this is not considered a bug—maybe it's faster or parallelized writing at the expense of larger files. It's even possible that ROOT developers don't know this is happening, since these files would read back correctly in ROOT (assuming ROOT looks at the std::vector header to deserialize it, which is almost certain). The only symptom would be that the files are a little larger.
It showed up as a bug in uproot because I made a strong assumption that the serialized std::vectors would entirely fill the basket. This PR weakens that assumption and introduces an additional check. (The std::vector size and the ROOT event positions appeared to be redundant information, and if they differ, which one is correct? From your example, it turns out that the std::vector size is the one that's correct.)
The fact that it's never come up before suggests that this is a rare feature-or-bug. Therefore, the fact that it happens in some branches and not others is also not too surprising.

I see.. what do you suggest? How do we proceed? Should I I fix this upstream and write an own method to parse the usr_names and derive the sub-structure of the corresponding usr from that information or should this be treated in uproot?

This is very weird  The data is definitely nested.
I was always confused about this . (dot) in the branch name, which might be used as a hint that something is nested? At least I only see this . in branch names for the "children" of the Evt class (branch).
What do you think?
Edit, I mean that it's ['mc_trks']['mc_trks.usr'] and not ['mc_trks']['usr']

After it's been written to the file, the dots in the branch names are just a naming convention. When I say I see no evidence that they should be nested, I mean that they're not variable length of variable length objects (only one level of "variable length").
Nesting of same length or fixed-length objects is a matter of convention, whether you consider record_x, record_y, record_z to be three arrays or records to be an array of containers of three fields is a matter of how you interpret the dot:
>>> record_x = numpy.arange(10) + 0.1
>>> record_y = numpy.arange(10) + 0.2
>>> record_z = numpy.arange(10) + 0.3
>>> records = awkward.Table({"x": record_x, "y": record_y, "z": record_z})
>>> records.tolist()
[{'x': 0.1, 'y': 0.2, 'z': 0.3}, {'x': 1.1, 'y': 1.2, 'z': 1.3}, {'x': 2.1, 'y': 2.2, 'z': 2.3}, {'x': 3.1, 'y': 3.2, 'z': 3.3}, {'x': 4.1, 'y': 4.2, 'z': 4.3}, {'x': 5.1, 'y': 5.2, 'z': 5.3}, {'x': 6.1, 'y': 6.2, 'z': 6.3}, {'x': 7.1, 'y': 7.2, 'z': 7.3}, {'x': 8.1, 'y': 8.2, 'z': 8.3}, {'x': 9.1, 'y': 9.2, 'z': 9.3}]
>>> records.x
array([0.1, 1.1, 2.1, 3.1, 4.1, 5.1, 6.1, 7.1, 8.1, 9.1])
>>> records.y
array([0.2, 1.2, 2.2, 3.2, 4.2, 5.2, 6.2, 7.2, 8.2, 9.2])
>>> records.z
array([0.3, 1.3, 2.3, 3.3, 4.3, 5.3, 6.3, 7.3, 8.3, 9.3])
>>> records_x
>>> record_x
array([0.1, 1.1, 2.1, 3.1, 4.1, 5.1, 6.1, 7.1, 8.1, 9.1])
>>> record_y
array([0.2, 1.2, 2.2, 3.2, 4.2, 5.2, 6.2, 7.2, 8.2, 9.2])
>>> record_z
array([0.3, 1.3, 2.3, 3.3, 4.3, 5.3, 6.3, 7.3, 8.3, 9.3])

Uproot reads branches as completely separate objects. If they're supposed to be in a hierarchy of nested fixed-size objects (like the record above, which has the same fixed size for x, y, and z), then you can put them together into a Table (or in Awkward 1, a RecordArray).
If the inner data have variable sizes, then that's a problem you need Uproot to resolve. Fixed-size things are so fluidly combinable and separable that maybe that shouldn't be a rigid concept anymore, but variable-sized nesting is an irreducible thing.
Have we been talking past each other on the use of the word "nested"?

I see.. what do you suggest? How do we proceed? Should I I fix this upstream and write an own method to parse the usr_names and derive the sub-structure of the corresponding usr from that information or should this be treated in uproot?

Other than the wrong std::vector deserialization, which is fixed by this PR, what needs to be fixed?

OK, maybe we are talking past each other regarding the nested thing ;)

Other than the wrong std::vector deserialization, which is fixed by this PR, what needs to be fixed?

The problem is that only the first element of the list of lists is fixed now. But it's still top level.
In fact, the usr and usr_names are variable length lists with lists in them.
Let me try to summarise better. The following array gives the number of tracks in each event (it's a bit unusual that this branch lists numbers, but we got used to it):
In [5]: f['E']['Evt']['mc_trks'].array()
Out[5]:
array([21, 13,  2, 18,  5, 10,  2, 10, 13, 16, 19, 14, 17,  8,  2, 10,  2,
        2,  2,  2,  2, 11, 13,  2, 14, 14, 16, 12, 12, 14,  2, 12,  2, 21,
        2,  2, 18,  2,  2,  2,  2, 11, 11,  2, 16,  2, 13, 13,  2, 14,  7,
        2,  2, 12, 10, 10,  2,  9,  2, 10,  2, 12, 10,  2,  2, 16, 12,  2,
        2, 21,  9,  2, 21, 10, 17, 11, 10, 10,  2, 13,  9,  2, 10, 15, 14,
        2, 19,  2, 10, 22,  2,  2, 12, 15,  2,  2, 11, 11, 15, 12, 10,  2,
       18, 10, 13, 19, 16,  2, 19,  2, 10, 19,  9, 17,  2,  2,  2, 16,  2,
       15,  2, 16,  2,  2,  2, 26,  2,  2,  2, 13, 15, 17,  2,  2,  2,  2,
       18, 10,  8,  2, 22, 10,  2,  2,  2,  2,  9, 10, 14,  2,  2, 14,  2,
        2, 15,  2,  2,  9, 12, 16, 17,  2, 18, 21, 17,  2,  2, 12,  2, 13,
       15,  9,  2,  2,  2, 20,  2,  2, 21, 20, 14,  8, 15,  2, 16,  2, 26,
       17,  2,  2,  2,  2,  2,  2,  2, 11,  2,  2,  2,  2,  2,  2,  2,  8,
       14,  2, 14, 10,  2,  2,  2,  2,  8,  2, 17,  2, 19,  2,  2,  2,  2,
       11,  2,  2, 15,  2,  2,  2,  2, 16, 22,  2,  2, 15,  2,  2, 19, 11,
        2,  2,  2,  2, 11, 18, 21,  2,  2,  2,  2,  2,  2, 23,  2,  2,  2,
        2,  2,  2,  2,  2, 17, 16,  2, 11,  2,  2,  2,  2, 12, 40,  2,  2,
        2,  2, 18,  2,  2, 15,  2, 22,  2, 26,  2,  2,  2, 25,  2, 18,  2,
        2, 22,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,  2,
        2], dtype=int32)

Here you see that the first event has 21 tracks, the second 13 and so on.
Now, each attribute of this mc_trks needs to be 21 long in the first event, 13 in the second and so on. For usr and usr_names these entries needs to be lists-of-lists (what I call nested lists)
Before the fix, the first entry (for the first event) had a length of 15, which seemed kind of random (instead of 21) and it was a flat list of values. The first 4 entries were in fact values, which one would expect in the first array of the entry ([0][0]).
After the fix, the length is OK, but it's still not nested and is missing the remaining 20 elements (as sub arrays):
In [6]: f['E']['Evt']['mc_trks']['mc_trks.usr'].array()[0]
Out[6]: array([0.048692, 0.058846, 3.      , 2.      ])

In [7]: f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array()[0]
Out[7]: [b'bx', b'by', b'ichan', b'cc']

The expected output is the following:
>>> f['E']['Evt']['mc_trks']['mc_trks.usr'].array()[0]
array([0.048692, 0.058846, 3.      , 2.      ] [63.2413] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []))

>>> f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array()[0]
[[b'bx', b'by', b'ichan', b'cc'], ['energy_lost_in_can'], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], []]

Each containing 21 sub-arrays for the first event.
Especially the last expected output is kind of easy to check, since the energy_lost_in_can value is not showing up. However, in the debug output you can see it (notice in Out[16]):
In [15]: f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array(uproot.asdebug)[0]
Out[15]:
array([ 64,   0,   0, 120,   0,   9,   0,   0,   0,   4,   2,  98, 120,
         2,  98, 121,   5, 105,  99, 104,  97, 110,   2,  99,  99,   0,
         0,   0,   1,  18, 101, 110, 101, 114, 103, 121,  95, 108, 111,
       115, 116,  95, 105, 110,  95,  99,  97, 110,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
         0,   0,   0,   0,   0,   0,   0], dtype=uint8)

In [16]: f['E']['Evt']['mc_trks']['mc_trks.usr_names'].array(uproot.asdebug)[0].tostring()
Out[16]: b'@\x00\x00x\x00\t\x00\x00\x00\x04\x02bx\x02by\x05ichan\x02cc\x00\x00\x00\x01\x12energy_lost_in_can\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'

Oh, then I have again misunderstood your intent! Instead of
>>> f['E']['Evt']['mc_trks']['mc_trks.usr'].interpretation
asjagged(asdtype('>f8'), 10, 6)
>>> f['E']['Evt']['mc_trks']['mc_trks.usr_names'].interpretation
asgenobj(STLVector(STLString()))

you want the interpretation to be
>>> branch = f['E']['Evt']['mc_trks']['mc_trks.usr']
>>> branch.array(uproot.asgenobj(uproot.SimpleArray(uproot.STLVector(uproot.asdtype(">f8"))), branch._context, 6))[0]
[[0.048692, 0.058846, 3.0, 2.0], [63.2413], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], []]
>>> branch = f['E']['Evt']['mc_trks']['mc_trks.usr_names']
>>> branch.array(uproot.asgenobj(uproot.SimpleArray(uproot.STLVector(uproot.STLString())), branch._context, 6))[0]
[[b'bx', b'by', b'ichan', b'cc'], [b'energy_lost_in_can'], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], []]

so the stuff after the first vector is not "random junk" or "padding" or anything—you were looking for more data. In that case, this PR is entirely mistaken and I'll be closing it, rather than merging it. If the above is right, then your real problem is why the interpretation thought it was singly jagged when it's doubly jagged.
However, when I'm looking a the C++ snippets you've given me, I would also assume that they're supposed to be singly jagged. As I understood it, you have an Evt struct that contains one std::vector: singly jagged. Where is the std::vector inside an std::vector?

Yes! Sorry that might be due to my bad vocabulary. Indeed I meant double jagged ;)
OK, so yes, indeed the C++ implementation is confusing.
The superclass for every class is basically this (the AAObject):
struct AAObject : public TObject
{
  std::vector<double>      usr;              ///< user data
  std::vector<std::string> usr_names;        ///< user keys
...
...

  TObject* any;                              ///< Pointer to "any" user data.

  ClassDef(AAObject, 6)
};

And then we have Trk and Hit etc. like this:
struct Trk: public AAObject
{
  int    id;                          ///< track identifier
  Vec    pos;                         ///< postion of the track at time t
  Vec    dir;                         ///< track direction
  double t;                           ///< track time (when the particle is at pos )
  double E;                           ///< Energy (either MC truth or reconstructed)

  double len;                         ///< length, if applicable
  double lik;                         ///< likelihood or lambda value (for aafit, lambda)
  int    type;                        ///< MC: particle type in PDG encoding.
  int               rec_type;         ///< identifyer for the overall fitting algorithm/chain/strategy
  std::vector<int>  rec_stages;       ///< list of identifyers of succesfull fitting stages resulting in this track

  int status;                         ///< MC status code
  int mother_id;                      ///< MC id of the parent particle

  std::vector<double> fitinf;         ///< place to store additional fit info, for jgandalf, see JFitParameters.hh
  std::vector<int>    hit_ids;        ///< list of associated hit-ids (corresponds to Hit::id).
  std::vector<double> error_matrix;   ///< (5x5) error covariance matrix (stored as linear vector)
  std::string    comment;             ///< use as you like
...
...

And finally the Evt class which stores std::vectors of these Trk and Hit instances:
struct Evt: public AAObject
{
  int id;                       ///< offline event identifier
  int det_id;                   ///< detector identifier from DAQ
  int mc_id;                    ///< identifier of the MC event (as found in ascii or antcc file).

  int run_id;                   ///< DAQ run identifier
  int mc_run_id;                ///< MC  run identifier

  int frame_index;              ///< from the raw data
  ULong64_t trigger_mask;       ///< trigger mask from raw data (i.e. the trigger bits)
  ULong64_t trigger_counter;    ///< trigger counter
  unsigned int overlays;        ///< number of overlaying triggered events
  TTimeStamp t;                 ///< UTC time of the start of the timeslice the event came from

  //hits and tracks
  std::vector<Hit> hits;        ///< list of hits
  std::vector<Trk> trks;        ///< list of reconstructed tracks (can be several because of prefits,showers, etc).
...

I see, so the Evt has a std::vector of Trk and each Trk has a std::vector of usr and usr_names. That's where the two std::vectors come in.
I'm closing this PR because it is a wrong fix: the problem is not that there are any "junk bytes" after the single serialized std::vector, it's that there's supposed to be a SimpleArray of STLVector in the interpretation. The error is in TTree::_attachstreamers (maybe we descended the streamers incorrectly and assigned the wrong level node?) or the error is in uproot.interp.auto.interpret (the massive function that assigns interpretations from what metadata it finds).


Yatin: Watch papislot.com

Yatin requests the watch of the watch_keyword papislot\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

papislot\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


preventDefault on enter key press, fixes #113

What changed?

adding a check when the user presses a key that equals the enter keyCode of 13. If enter is pressed prevent the default response (of submitting the form via HTTP) and running our own _this.submitForm() function. #113

Nice work.  Looks simple enough to me. I'll merge as soon as this is no longer in progress.

Stupid waffle.io always adding those tags. I'm going to remove it from my waffle and hopefully they don't get automatically added anymore. This is ready to merge!

Although, it probably needs a test...

Yeah, it would be best practice to start requiring tests accompanying almost any PR.  Your call if you want to skip tests or not @svmatthews

Aye - I'll write a test. Does it make sense to have this merging into your refactor?

@alukach mind if we merge this and I'll make Forms.js tests a different PR?

Works for me!


Does not need to be Teams Service admin to archive or restore a team

Apparently the features have changed and this page is outdated:
"Archive a team
Follow these steps to archive a team. You must be a Teams service admin to make these changes. See Use Teams administrator roles to manage Teams to read about getting admin roles and permissions."
It is enough to be a team owner to be able to archive a team or restore and archived team.

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

ID: 5bf689b7-a7c1-121f-578e-029e8a89c4f0
Version Independent ID: 7e6b449e-bd77-2fc4-2c3d-1f2e364e1b76
Content: Archive or delete a team in Microsoft Teams - Microsoft Teams
Content Source: Teams/archive-or-delete-a-team.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

Hello @anttikivivallisovelto How are you?
Please take into account that these instructions are to be run from the Teams admin center, so the TAC permissions are the ones specified.
Hope this clarifies it for you.
Thanks


refactor: move dropdown logic into component

This PR intends to refactor the Dropdown component logic and unify them into a single component.
What's changed

Create a new Dropdown component.
Update .gitignore to allow for the Dropdown component to be placed in ui/src/components/ui
Move ControlPanel components to use the new Dropdown component.

Banger! 🔥 Merging this now! 🙌


added code snippets to README.md

never really used GitHub before for collaboration before so please let me know if I am doing anything terribly uncouth


consumers of the SDK should be given power to throttle incoming messages

Invoker does not have to execute in goroutine.
This way the users of the library can add in any kind of throttle that they want to put in place

This PR does not add throttle control to the integrator, it adds it to the invoked connection downstream. Downstream connections can hold open and the throughput of the SDK will be limited by threads I think.

@n3wscott : Thanks you are right, This might not be the way to solve my problem.
here is what I did instead,
func (s *Subscriber) start(ctx context.Context) error {
	consumer, _ := kafka_sarama.NewConsumer("localhost:9092", sarama.NewConfig(), "some_group_id", "some_topic")
	defer consumer.Close(context.Background())
	g, ctx := errgroup.WithContext(ctx)

	g.Go(func() error {
		return s.recieveMessageAndProcess(ctx, consumer)
	})
	g.Go(func() error {
		return consumer.OpenInbound(ctx)
	})
	return g.Wait()
}

func (s *Subscriber) recieveMessageAndProcess(ctx context.Context, consumer *kafka_sarama.Consumer) error {
	wg := &sync.WaitGroup{}
	throttle := make(chan struct{}, runtime.NumCPU())
	defer close(throttle)
	defer wg.Wait()
	select {
	case <-ctx.Done():
		return ctx.Err()
	default:
		for {
			msg, err := consumer.Receive(ctx)
			if err != nil {
				return fmt.Errorf("error receiving message: %w", err)
			}
			throttle <- struct{}{}
			wg.Add(1)
			go func(m binding.Message) {
				defer wg.Done()
				err = myLongRunningProcess(m)
				<-throttle
				if err == nil {
					_ = m.Finish(protocol.NewReceipt(true, "processed at %d", time.Now().Unix()))
					return
				}
				_ = m.Finish(protocol.NewReceipt(false, "error processing the message: %w", err))
			}(msg)
		}
	}
}

Looks like this solution is working at the moment, so will close this PR.
Thanks again 😅


Add Block Explorer API URI to ChainInfo

The clients fetch the contract ABIs using the /api endpoints provided by the block explorer of each chain.
This information should be returned by the CGW in the /chains payload (this is going to be provided by the safe-config-service)
GET /api/v1/chains

[
  {
    "chainId": <string>,
    "chainName": <string>,
    "blockExplorerApiUri": <string> // new field
  }
]

Open Questions

Can blockExplorerApiUri be nullable?

cc/ @gnosis/safe-web @gnosis/safe-services

After aligning with @gnosis/safe-web we have decided to follow the template solution that we already had with blockExplorerUriTemplate. This would allow us to adapt more dynamically to different block explorers that might have a different path/query parameters for the same data.
The new template will have the following fields:

module (eg.: contract)
action (eg.: getAbi)
address (Ethereum address used for action – if needed)

GET /api/v1/chains

[
  {
    "chainId": <string>,
    "chainName": <string>,
    "blockExplorerUriTemplate": {
        "address": "https://etherscan.io/address/{{address}}", // example
        "txHash": "https://etherscan.io/tx/{{txHash}}" // example
        "api": "https://api.etherscan.io/api/?module={{module}}&action={{action}}&address={{address}}" // new field example
      },
  }
]


Sign-in button in status bar

To better promote the SSO feature and make it more accessible, we talked about adding a button/indicator to the navigation bar at the bottom.
I imagine a button with the Red Hat logo and specific text that on click fires the sign-in process.  It should also indicate whether the user is signed in or not.

@slemeur does that reflect what you had in mind?

It looks like https://github.com/containers/podman-desktop/issues/6297 was opened to track this.

Being worked on in https://github.com/containers/podman-desktop/pull/6446

I have an icon on status bar

@benoitf How do I make it red?

It's not possible to pickup colors for status bar elements
It is to avoid Christmas tree effect

@benoitf  @vrothberg Then we cannot use White Hat with Black stripe icon. It seems according to https://brand.redhat.com it can be: Red/White, Red/black or Black/white only. There is no White/black colored icon.

We still allow colors on the action bar (openshift icon is red)

What is there is limited number of colors: red, green and yellow?

How about displaying a green check mark ✅ next to the logo when being signed in?

See previous comment - it's intentionally not possible today. Statusbar is kept to muted colors to avoid distraction (and as a user, I really wouldn't like either of these last two suggestions).

See previous comment - it's intentionally not possible today. Statusbar is kept to muted colors to avoid distraction (and as a user, I really wouldn't like either of these last two suggestions).

I am still confused, why text editor colored like Christmas tree is fine, but status bar colored the same way is not ;)
But, I am going to use muted color hat for now.


Document Docker Desktop alternatives for contributors

Signed-off-by: Antonin Bas<EMAIL_ADDRESS>

Codecov Report

Merging #3218 (ac3404f) into main (ccd0150) will decrease coverage by 7.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3218      +/-   ##
==========================================
- Coverage   41.19%   34.08%   -7.11%
==========================================
  Files         196      131      -65
  Lines       23660    15581    -8079
==========================================
- Hits         9746     5311    -4435
+ Misses      12914     9785    -3129
+ Partials     1000      485     -515

Flag
Coverage Δ

integration-tests
34.08% <ø> (?)

unit-tests
?

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

Impacted Files
Coverage Δ

pkg/ovs/ovsconfig/default.go

pkg/flowaggregator/certificate.go

pkg/agent/cniserver/pod_configuration_linux.go

...gent/controller/noderoute/node_route_controller.go

pkg/agent/cniserver/server.go

...kg/agent/controller/networkpolicy/audit_logging.go

...agent/controller/traceflow/traceflow_controller.go

pkg/agent/controller/networkpolicy/reconciler.go

pkg/antctl/command_message.go

pkg/ipam/ipallocator/allocator.go

... and 317 more

/skip-all


Add support for Hbm/Hbm2 memory device types

Fix https://github.com/jcreekmore/dmidecode/issues/29

This one is clean now, showing 1 commit.

This is now conflicting with the previous PR I merged. If you can rebase and fix that up, you will be golden.

thanks for the quick response, merge conflict resolved.

When you get a chance if you could issue a new release version with the latest additions, that'd be perfect.

When you get a chance if you could issue a new release version with the latest additions, that'd be perfect.

That is going to have to wait until Monday. I'm away from the computer that has my keys on it until then (the GitHub app works great on mobile, but I don't have a good workflow for cargo releases on mobile yet). I will make a note to do it when I get home, though.

@ldfsilva I released 0.7.5 a few minutes ago.

That's great, thank you @jcreekmore


clone bureau, but without nvm info

I like the bureau theme, but don't use node, so I cloned the theme and removed nvm info.

I would close this one as #5143 is a better solution


Dep upgrades 2024 11 19

Hi @drdalessandro  - thanks for submitting.  We usually run this process every Monday.  Was there a dependency that you need upgraded?


suggestion

have a way to add newer texconv  formats

Hello, which formats are you refering to, DXGI?

the newest version of texconv now supports dtx 5 rxgb because of me lol

https://github.com/bj-rn/texconvgui/releases/tag/2.0.0


table header and body different widths

in the auto-arima.bkr tutorial, the 1st cell comes out wrong:

cannot reproduce


Inference on different dataset

Hi, I would like to use FRNet on the UTCampus dataset, however, I don't get the expected results. The code runs without any issues, but the results are terrible, see below. I use the provided config and checkpoints files corresponding to the KITTI dataset within the mmdetection3D framework.
In my opinion, the poor results can be caused by the difference in LiDAR sensors, the setup of the config files, or incompatibility in general. I already tried a couple of things in order to solve the issue, unfortunately, they all didn't work:

Tried the checkpoint and config file corresponding to the nuScenes dataset
Changed the fov_up and fov_down in both config files
Downsampled my point cloud to better match the resolution of KITTI and nuScenes

I hope that I gave you enough information, otherwise feel free to ask.
Kind regards,
Guido

Hi @guidodumont, can you show some examples of projecting your LiDAR point clouds to range view using the FOVs you tried? We cannot make a comment on your scenario until getting more information about your dataset. Thanks

Sorry for the late response. The cause of the problem is probably the difference in sensor position (on top of a car/mobile robot) and the inconsistent intensity measurements. I have found an alternative method to obtain the data I need. I much appreciated your help!


Use Symbol.observable “ponyfill”

This change upgrades symbol-observable and changes use to symbol-observable/ponyfill so that MostJS can be used in JS environments where the primordials are frozen to mitigate prototype pollution attacks.
I have not added unit tests to verify this, but with your consent, I can add a development dependency on SES and use that to lock down the primordials during tests.
This is not a user-visible change, but does enable MostJS to be used in more environments. I do not see a change log to mention this in.

Good to see you again, @briancavalier 😊

Hey @kriskowal 👋  Thanks for this, and for the note about globalThis.  I'll take a closer look soon.

Posted follow-up changes to use a globalthis polyfill so this can still work with a no-eval CSP.

Hey @kriskowal 👋 Thanks for this, and for the note about globalThis. I'll take a closer look soon.

Awesome. I took care of globalThis so this should work with a no-eval CSP now. Took this back out of draft.

I have not added unit tests to verify this, but with your consent, I can add a development dependency on SES and use that to lock down the primordials during tests.

Oops, I just noticed this!  Can you say a bit more about what's involved in adding the SES dep and modifying the tests?

I’ve pushed fixes for the remaining symbol-observables, and removed the commit that added a yarn.lock unintentionally.

Oops, I just noticed this! Can you say a bit more about what's involved in adding the SES dep and modifying the tests?

I could do this in a follow-up. The purpose would be to block future changes that would introduce prototype pollution, either directly or through an upgraded third-party.
This would involve adding import "ses" and calling lockdown() or lockdown({errorTaming: "unsafe"}) at the head of your test runner, or creating a second entry point to your tests that locks down and runs the tests again under those conditions.

@briancavalier I believe this is once again ready for review. Please let me know if this is a satisfactory change.

@kriskowal

This would involve adding import "ses" and calling lockdown() or lockdown({errorTaming: "unsafe"}) at the head of your test runner, or creating a second entry point to your tests that locks down and runs the tests again under those conditions.

I like the idea of a second test entrypoint if that's relatively simple.  Would you be up for opening a PR for that so we can see what it looks like?
BTW, have you looked at @most/core?  It's the new version of the core ideas of most, with a primarily functions-only API.  If we're able to add SES testing in a simple way here, I could imagine adding it there as well if the other maintainers are open to it.
Thanks again!

Thank you! I will watch for the next release.

@kriskowal We just published v1.9.0 with this change.  Sorry for the delay.  We had to deal with some quirks of most's antiquated build setup.

Thank you @briancavalier. You have my sympathies. I have a number of projects with a crusty CI setup that hasn’t run in years. I’ll let you know if I run into integration trouble rolling this up.


Consistency check of SMH file

Introduce consistency check of SMH file (yaml). Examples for - currently not detected - inconsistencies:

systems specify parts that are themselves not specified in the SMH file
system modes refer to modes of their parts that are not specified

A first step (before the semantic check) should be to validate the SMH file against a schema. Rx seems to be a possible way to do this.


Add a link to Bit under the Flexible Toolchains section

Hi 👋,
Full disclaimer: I'm closely working with the Bit team, using the tool in practice and written several articles to their blog, Bits & Pieces
Bit is gaining some traction in the React community (already its a heavy choice to creating design systems with React and sharing independent components), and I think it would be a useful tool for React teams to build applications in more of a scalable way.
More info:
https://harmony-docs.bit.dev/getting-started/creating-components
https://bit.dev
PS. I added the link to Bit as the first item (I assume this section is sorted alphabetically).

Hello @AshanFernando!
Unfortunately toolchains are no longer listed in that page in the latest of react.dev, so we can't include new ones as well.
Let me close this PR as outdated, but feel encouraged to contribute by addressing open issues.
Thank you!


Runtime Error on Windows in standalone script

Justin encountered the below error while trying to run a simple standalone script to upload files. The error message kept repeating indefinitely which makes me wonder if this might somehow be related to #2. The same code did work on his machine when he ran it in Jupyter Lab.
Relevant code:
from glob import glob
from bln.client import Client

TOKEN = ""
project_id = ""

files = glob("C:/Users/UserName/Documents/BLN/*.csv")
client = Client(TOKEN)
client.upload_files(project_id, files)

Error message:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\spawn.py", line 105, in spawn_main
    exitcode = _main(fd)
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\spawn.py", line 114, in _main
    prepare(preparation_data)
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\spawn.py", line 225, in prepare
    _fixup_main_from_path(data['init_main_from_path'])
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\spawn.py", line 277, in _fixup_main_from_path
    run_name="__mp_main__")
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\runpy.py", line 263, in run_path
    pkg_name=pkg_name, script_name=fname)
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\runpy.py", line 96, in _run_module_code
    mod_name, mod_spec, pkg_name, script_name)
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\UserName\Documents\BLN\covid19\case-tracking\usafacts\uploadUSAFacts.py", line 12, in <module>
    client.upload_files(project_id, files)
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\site-packages\bln\client.py", line 238, in upload_files
    with Pool(cpu_count()) as p:
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\context.py", line 119, in Pool
    context=self.get_context())
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\pool.py", line 176, in __init__
    self._repopulate_pool()
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\pool.py", line 241, in _repopulate_pool
    w.start()
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\process.py", line 112, in start
    self._popen = self._Popen(self)
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\context.py", line 322, in _Popen
    return Popen(process_obj)
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\popen_spawn_win32.py", line 46, in __init__
    prep_data = spawn.get_preparation_data(process_obj._name)
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\spawn.py", line 143, in get_preparation_data
    _check_not_importing_main()
  File "C:\Users\UserName\AppData\Local\Programs\Python\Python37-32\lib\multiprocessing\spawn.py", line 136, in _check_not_importing_main
    is not going to be frozen to produce an executable.''')
RuntimeError:
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.

Could this be related?
https://stackoverflow.com/questions/18204782/runtimeerror-on-windows-trying-python-multiprocessing
There is a __name__ == '__main__' in Client though.

This should be fixed in the next release. Windows won't allow multiprocessing when using a module as a library / interactively. It must be run as a main file. So, sadly, windows will have to upload files serially.


userns: mount the volumes from the intermediate namespace

when --uidmap is used, the user won't be able to access /var/lib/containers/storage/volumes.  Use the intermediate mount namespace, that is accessible to root in the container, for mounting the volumes inside the container.
Closes: https://github.com/containers/libpod/issues/2713

LGTM

LGTM

/retest

tests are passing

/lgtm


feat: add tags option to LoggerHandler and LoggerBackend

Added a new configuration option 'tags' to both logger implementations that allows specifying which metadata fields should be included as tags in Sentry events. Similar to the 'metadata' option, it can be configured with a list of keys or :all.
Closes #827

Sorry for a drive-by comment, but what happens if metadata values are maps or lists? Wouldn't tags need to be scalar?


pip install for latest version

pip install git+https://github.com/MLRichter/receptive_field_analysis_toolbox

should install the current main branch, but instead it asks me to authenticate, and rejects my username & password:
output
Collecting git+https://github.com/MLRichter/receptive_filed_analysis_toolbox
  Cloning https://github.com/MLRichter/receptive_filed_analysis_toolbox to c:\users\overl\appdata\local\temp\pip-req-build-gyw719b4
  Running command git clone -q https://github.com/MLRichter/receptive_filed_analysis_toolbox 'C:\Users\OverL\AppData\Local\Temp\pip-req-build-gyw719b4'
  Logon failed, use ctrl+c to cancel basic credential prompt.
  bash: /dev/tty: No such device or address
Username for 'https://github.com': OverLordGoldDragon
  error: failed to execute prompt script (exit code 1)
  bash: /dev/tty: No such device or address
  error: failed to execute prompt script (exit code 1)
  stty: 'standard input': Inappropriate ioctl for device
Password for<EMAIL_ADDRESS>  remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
  remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
  fatal: Authentication failed for 'https://github.com/MLRichter/receptive_filed_analysis_toolbox/'
WARNING: Discarding git+https://github.com/MLRichter/receptive_filed_analysis_toolbox. Command errored out with exit status 128: git clone -q https://github.com/MLRichter/receptive_filed_analysis_toolbox 'C:\Users\OverL\AppData\Local\Temp\pip-req-build-gyw719b4' Check the logs for full command output.
ERROR: Command errored out with exit status 128: git clone -q https://github.com/MLRichter/receptive_filed_analysis_toolbox 'C:\Users\OverL\AppData\Local\Temp\pip-req-build-gyw719b4' Check the logs for full command output.

Never had to authenticate before - I presume it's something from this repository's end? Would help to pip install rather than having to clone (clone works fine).

Woops, typo in pip install.
Might help to include this instruction for those who want the latest version, in README.


New toolbar appearing

When trying to use my forward and backward button on my mouse, I noticed that a new toolbar appears, and it can't be removed unless I exit the pdf and reopen.

I cannot reproduce this, please reopen with more information if this is still an issue.


Python fixes from pyupgrade

The CI errors are related to changes to GitHub's CodeQL scanner, not this PR.
Merged, thanks @andersk!  It's great when an automated tool can make code a lot cleaner.


Add workflow for Update Gradle Wrapper Action.

Hey there 👋, first of all thanks for your work on DTP!
I've got a suggested change: would you be willing to use this GitHub Action to automatically keep Gradle Wrapper updated to latest release?
What does "Update Gradle Wrapper Action" do? It can be configured to run at scheduled intervals (e.g. daily or weekly) and will check whether the Wrapper script in the repo is up-to-date to the latest Gradle release: in case a new Gradle version is available, it will create a PR to update the Wrapper. And that's it!
Why is that a good thing? Well, first of all it alleviates the chore of manually updating the Wrapper, as you got a task that keeps track of new Gradle releases for you! More importantly, it boosts security around the Wrapper update and usage processes: this actions verifies that the gradle-wrapper.jar file has not been tampered with (uses checksum comparison), and it sets the distributionSha256Sum property so that the new Gradle binary itself will be verified locally upon download.
Where can I find more about? The README contains quite detailed information!
In this PR I propose adding a new workflow which runs the action every day at midnight (but feel free to adjust the frequency as you prefer). I've verified it works correctly in my fork of the repo, and you can see here how the generated PR looks like.
The action is under active development, you can have a look at the list of inputs currently supported. There's new features coming up soon and if you'd like to request any particular change just let me know!
I'd love to see the action used by DTP as such a popular project would definitely help me spread the word, but I also genuinely hope you can find this useful. Would love your feedback! ❤

@googlebot I signed it!

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


Haven't figured out printing of the form yet

This applies to the sealing app as well as the expungement one

Duplicate of https://github.com/codeforboston/docassemble-juvenilesealing/issues/26


release: v2.2.0

Description: 概要

Changes: 変更内容

Changes

feat: add html mode (closes #14) (#15) @technote-space

Expected Impact: 影響範囲

Operating Requirements: 動作要件

Additional context: 補足

Codecov Report

Merging #16 (21c314b) into master (cfe910d) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #16   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         6    +1
  Lines          154       177   +23
  Branches        28        31    +3
=========================================
+ Hits           154       177   +23

Impacted Files
Coverage Δ

src/constant.ts
100.00% <100.00%> (ø)

src/index.ts
100.00% <100.00%> (ø)

src/lib/transform.ts
100.00% <100.00%> (ø)

src/lib/utils.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


context: make use of a rw-mutex to protect cancelCtx fields

Reduce mutex contention on cancelCtx when cancellation error is queried from multiple goroutines.
Signed-off-by: Miguel Ángel Ortuño<EMAIL_ADDRESS>

This is strictly worse than a plain mutex


Update index.json

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

Could you please take a look the error message that CI reported?

@j-martens Is this PR still active?

@haroldrandom yes it is.

@j-martens Please take a look the CI's output and fix them first

@haroldrandom I don't work on this team, thus the public PR. It wasn't making errors when I created it many months ago. I don't know what happened. @tjprescott - can you help here?

I'm no longer on the CLI team, but you'd need to pull the changes from master and fire off another build. The build is old enough that it's no longer available for inspection.

@j-martens CI Job Verify Extensions Index is used to compare metadata info between wheel from downloadURL and index.json you provide.
You updated the project_url in index.json but didn't modify project_url corresponding in setup.py of your extensions. That's why it failed CI.
To fix this, please:

update project_url in setup.py in your extension source code folder with the same value.
re-build and upload a new wheel package to your container.
REMEMBER to update sha256sum checksum in your index.json
push changes here.

I believe this time it can work.

Closed as long time not active.


quick-start should be aimed at users, seems to be aimed at contributors

Addressed in #88 #90 #91 #120


#836: Add PIL as a dependency to the Server RPM.

Add python-imaging as a dependency of the Server RPM. It's necessary for publishing maps over WMS, and is not automatically detected by rpm-find-requires.

Fixes #836.

I wrote #843 to add documentation on run time dependencies.


[9.x] Add whereBelongsToById to EloquentBuilder

We need this in case we want to find by relationship id, withouth query the model to reduce mysql queries.
Like filtering the model by relationship in controller from FormRequest, in most efficient way.
This will help also in filtering by relationship when we have only the id, without query the model or use the column name of the relationship

Please undo all styling changes in this PR.

Why is this targeting Laravle 9?

Now, I use v9.x, and will be helpful for me, but if is needed I will contribute also on v10.x, with a optimised for PHP8.1

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


SAK-49520 CKEditor: Added FMath plugin

Would be good to release this as a Sakai Webjar like other plugins, but I don't know how to do it.

@jonespm Thanks! I've moved the 5K files to a webjar and now this is a very simple PR.
This should be broken until the webjar is released and pushed into Maven central, I've verified it locally:

It is not enabled by default, you need to compile Sakai with '-Dckeditor-fmath' flag to enable it, like the accessibility plugin does.

Much better like this, thanks @jonespm


How can I train images without preparing a lmdb dataset?

Once, I have trained it using a custom dataset, converting it into lmdb format. How can I train the model just using raw images ?Could you help me @ku21fan

I have finally achieved to train.

I have finally achieved to train.