UAT | Sprint 11 | Remove Text

IN the following field, extra text exists in the label.
Change
Upload Affidavit to be submitted in-lieu-of statement under Section 223, Bharatiya Nagarik Suraksha Sanhita, 2024 (The note below)
to
Upload Affidavit to be submitted in-lieu-of statement under Section 223, Bharatiya Nagarik Suraksha Sanhita, 2024

hi @rajeshcherukumalli, Changes are already done, pls check
cc : @Ramu-kandimalla

Hi @rajeshcherukumalli : Tested in dpg-dev, the changes were already done, as a part of this ticket: https://github.com/pucardotorg/dristi/issues/2200
cc: @Ramu-kandimalla


add slash command groups to groups.mdx

This PR adds basic documentation of Slash command groups to the groups.mdx file

Slash command groups aren't supposed to be in this category, this is for the extension

Slash command groups aren't supposed to be in this category, this is for the extension

Alright, got it.


API for Adjusting Numerical Threshholds

Hi, I'm one of the Psi4 developers.
Recently, we've had a bug report of inconsistencies between our ECPs (computed using your library) and PySCF. As part of my investigation, I would like to use libecpint using more stringent threshholds for prescreening, numerical integration, etc. Sadly, the optional settings where these likely are is not documented.
What options does libecpint give us to control tightness of the integrals?

Hi, thanks for the message.
I see that the referenced issue is closed, and the errors had nothing to do with libecpint in the end.
The documentation for options has been updated in the (as-of-yet unmerged) version 1.1 PR, so I'm closing this issue. That said, in case you need to know right now, Psi4 is using the lower level API for which the already-available code documentation states how to set the integration thresholds, and change the size of the radial integration grids.


Fixes #31: Add --no-color option to suppress terminal colors

See issue #31.
The colors will be automatically suppressed if the stdout is not a TTY.
Also added (undocumented) --color command to force colors even if we are not outputting to a terminal.

Thanks. Cherry-picked into master. In the future please always use braces around if statements. I updated it manually in this commit: d9fe3538b65bea6b681796cbb945a1896752e568


feat: new keyword to check if symlink exists or not

Add Symlink Should Exist and Symlink Should Not Exist keywords.
Quick test case to verify how the new keywords work.


SI_CONVERSION errors

Jeremy suggested including SI_CONVERSION as an x_ attribute in HAPI metadata.
However, the conversion factor for the same unit is not always the same. The file http://mag.gmu.edu/git-data/cdawmeta/data/reports/units-CDFUNITS-SI_CONVERSION-map.json has nodes of the form
km/s: [
"1.0e3>m s^-1",
"1000.>m s^-1",
"1e3>m/s",
"1e-3>m/s",
"1.0e3>m/s",
"na",
"1.0E-3>m/s"
]

which means a variable with UNITS = km/s was found to be associated with all of the values in the array. To determine where a SI_CONVERSION appears, see the table.

See also #14


New diagram for mesh expansion example

Replaces the diagram at https://istio.io/docs/guides/integrating-vms/
(original is located in Community Drive -> Misc -> Drawings for Istio.io site)

/ok-to-test

/cc @rshriram

Please update markdown to have the proper width and ratio values for revised images.

@oaktowner you have 2 boxes for reviews service... think one should be rating instead.  Also, do you think it will be better if we have all k8s services shown within k8s so it is clear which ones run in k8s?

New changes are detected. LGTM label has been removed.


Benchmarking

Draft PR for the benchmarking suite and github action workflow

Closing as this should be implemented via a python-project-template update.


Fixes initial FileEntry creation to have correct path

Run CodeMaid

Requesting review for CodeMaid formatting.
Settings used are checked in at CodeMaid.Config in the root directory.

I'm assuming these are all formatting changes in the csharp files and approve it.

This is the only real code change - a fix to remove a double print of the base archives name in RecursiveExtractor
https://github.com/microsoft/OSSGadget/blob/95751cd2f77609619de616f972b8d684b18695de/src/RecursiveExtractor/Extractor.cs#L173

This is the only real code change - a fix to remove a double print of the base archives name in RecursiveExtractor
https://github.com/microsoft/OSSGadget/blob/95751cd2f77609619de616f972b8d684b18695de/src/RecursiveExtractor/Extractor.cs#L173

LGTM, also, is there a rule for CodeMaid to limit lines to 80 chars or less? That might help readability

We should align on a standard CodeMaid config (haven't used it before) -- but also not sure that we should go with 80 as our limit -- maybe 110? Slashdot article.

The default in code maid is wrapping comments (not lines) at 100.  I'm not sure there's a setting to format code lines.  I can bump it to 110.

I bumped the setting to 110 and removed regions because I ended up not liking what it did - it wasn't rearranging things into the regions on save.
You can get CodeMaid here: https://marketplace.visualstudio.com/items?itemName=SteveCadwallader.CodeMaid

I am not in favor of wrapping all lines (vs comments), but we should try to stick to ~120 characters when possible.

@jacobmsft I went through Extractor.cs and wrapped lines closer to 120 per your comment manually.

@jacobmsft I went through Extractor.cs and wrapped lines closer to 120 per your comment manually.

Sounds good...its not a must do for me, but it was helpful when Resharper used to do it in VS (normal VS word wrap is not as helpful), Makes online code-viewing/reviewing easier. Thought codemaid also might have it...nevermind.


Some alignment in the various information windows would be nice

We jump on new web pages (new tab, e.g., upon clicking on an article), we create Google Maps info popups (e.g., cave basic information popup, or the other map tools popup), and we create entirely new windows (cave classification).
Not entirely clear to me what the choices are here, and if we're making the right choices. I think the cave basic information popup needs to be on this page, because changing all the time to a different page would be distracting. And articles and cave classifications are long/large enough that they deserve their own page. But what's the logic in new windows vs. jumping to a new address in a new tab? Or could we put more things Google Maps info popups?

cave information should go into an infowindow. That's the intended use of an Infowindow, really.

articles and cave maps opened from the infowindow should open in a new tab (not the current one) because they are long reads and also take the reader away. This is the UX designers view [name in pm].

The cave classification window is a reference sheet that should remain visible at the same time as the map itself (do not replace current page, do not open in a tab) and it must be movable so that it does not cover any caves. All this means that it must be a popup window. Think of it as, if not a tool palette, then at least as a reference book, or contextual help. I for example, want to drag it to the second screen while I browse the map. Then I can easily reference it whenever I open a cave infowindow as see something cryptic like "B,BEF" or "HD3". Please note that this popup window could also show climbing grades, ski piste grades, and other classifications depending on sport on the map.

That was the easy stuff.

The filter window could open up as a tool palette, but I believe that we can live with an Infowindow, too. Having too many popups can be annoying, and especially if the one you need to USE gets buried under other windows. So perhaps it is best to just keep it on the map as it is now. The fact that the infowindow is tied to coordinates and has a sharp tip looks a bit strange, but is bearable.

Same is true for the About window and More maps...

Good analysis!
(There may be a subgroup of people -- and I'm in that group -- that usually has full screen browser windows, and for them the new window doesn't work so well. But I understand the logic now. Thanks!)

Instead of a pop-up, the reference window could also be hidden as a side panel and slide open when one clicks on a button (typically a triangular icon that point to the right or down). It would remain visible as long as the user wants, and on single-screen full-screen and on mobile, and everywhere, and the map would remain movable. Of course then, it cannot be dragged onto another screen (unless it has a pin icon and it can be unpinned and ... well lots of work).
Of course, again, a side panel that slides open once one clicks on a triangle icon in some corner...


Review and update Component ownership page in intranet

update the Ownership document - https://intranet.giantswarm.io/docs/product/team-ownership/ #20226

done and merged


Fix removeToken() issue

A quick fix for issue  #33

Hi @rllola.
This issue will be fixed with #25. But, while we're waiting for Angular 1.4 stable we can merge your PR.
Just squash the 2 commits.
Thanks.

Hi @ruipenso
Done.
Thanks.

@rllola Can you please remove the dist files?

@ruipenso Done.

Landed on commit eb6be56.
Thank you.


flawfinder: 2.0.15 -> 2.0.18

Motivation for this change
Update to latest upstream release 2.0.18
Migrate it to buildPythonApplication.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 128813 run on x86_64-linux 1

1 package built:

flawfinder


Update machine-learning-data-science-move-azure-blob.md

Changed link to How to Use the Blob Storage Service from Python to go to the Azure.com link, not GitHub

Hi @msolhab, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (mohabib). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Added Incremental Merkle Tree implementation

[ ] Since this PR suggests a bug fix, the tests have been added and the coverage is 100%.
[x] Since this PR introduces a new feature, the update has been discussed in an Issue or with the team.
[ ] This PR is just a minor change, like a typo fix.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (fa4cce3) 100.00% compared to head (4928abc) 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff            @@
##            master       #45   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           28        29    +1
  Lines          882       944   +62
  Branches       124       128    +4
=========================================
+ Hits           882       944   +62

Impacted Files
Coverage Δ

...cts/libs/data-structures/IncrementalMerkleTree.sol
100.00% <100.00%> (ø)

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


Should zsh become the default user shell in Agora?

zsh has been the default user shell on macOS since Catalina -- and I see no really great reason why not to do so as well, it's a great shell, and the user is still free to choose another if they really want to.
It would add one package to the dependencies, and whatever configuration was needed, plus we'd have to fix it somehow so gnustep-make works right.

I've been using zsh as my shell for years now, so this works for me.


ERROR: Exception on thread Thread[main,5,main] (pop OS Linux)

Hi. I'm experiencing this problem on a laptop that is currently running pop os. I initially though it had to do something with android 12 but after testing on a windows computer it worked just fine!
I looked on issues but couldn't find a similar problem. (not very familiar with github though..)
Thank you in advance <3 this is GREAT software
___________________________________-
INFO: scrcpy 1.17 https://github.com/Genymobile/scrcpy
/usr/share/scrcpy/scrcpy-server: 1 file pushed. 3.2 MB/s (34012 bytes in 0.010s)
[server] INFO: Device: samsung SM-A525M (Android 12)
INFO: Renderer: opengl
INFO: OpenGL version: 3.0 Mesa 21.3.5
INFO: Trilinear filtering enabled
INFO: Initial texture: 864x1920
WARN: Device disconnected
[server] ERROR: Exception on thread Thread[main,5,main]
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplaySurface(SurfaceControl.java:75)
at com.genymobile.scrcpy.ScreenEncoder.setDisplaySurface(ScreenEncoder.java:243)
at com.genymobile.scrcpy.ScreenEncoder.internalStreamScreen(ScreenEncoder.java:91)
at com.genymobile.scrcpy.ScreenEncoder.streamScreen(ScreenEncoder.java:60)
at com.genymobile.scrcpy.Server.scrcpy(Server.java:80)
at com.genymobile.scrcpy.Server.main(Server.java:252)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:374)
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(Native Method)
at com.genymobile.scrcpy.wrappers.SurfaceControl.setDisplaySurface(SurfaceControl.java:73)
... 7 more
Caused by: java.lang.IllegalArgumentException: displayToken must not be null
at android.view.SurfaceControl$Transaction.setDisplaySurface(SurfaceControl.java:3370)
at android.view.SurfaceControl.setDisplaySurface(SurfaceControl.java:2344)
... 9 more
WARN: Killing the server...

INFO: scrcpy 1.17 https://github.com/Genymobile/scrcpy

You need scrcpy >= 1.18 for Android 12. You can install the latest on linux by following these instructions: https://github.com/Genymobile/scrcpy/blob/master/BUILD.md#simple

Woah, thanks a LOT! <3


Replace .min.css with .css /1

Fixes #26180

None of the Blazor articles/files/samples/examples are broken AFAIK. Let's not change the Blazor-related markup because the display of code is usually exactly what the dev will see from a project template when they open a file that they're being instructed to change.

I checked on the .NET 6 bits for Blazor, and the minified assets are the ones that are used. Yes, please remove the Blazor updates from this PR. This is going to break both Blazor WASM and Blazor Server apps.

@guardrex does Blazor override .gitignore and check in the min files?
WHen I do a global search and replace in VS Code, how do I exclude Blazor files?

Yes, that's right ...
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/.gitignore
In VSC, use the files to exclude filter with a path to the blazor folder ... that should factor out all of the Blazor stuff.
WRT debugging, there is no debugging of non-min files with Blazor, per se, because the size of such files unminified is a killer on top of all of the assets that must be downloaded to the client. The project templates don't have unminified assets. For example for WASM ...
https://github.com/dotnet/aspnetcore/tree/main/src/ProjectTemplates/Web.ProjectTemplates/content/ComponentsWebAssembly-CSharp/Client/wwwroot/css/bootstrap


Unpin pyarrow in CI

We've temporarily pinned pyarrow<2 in the CI environments as there were some changes that broke our tests. We should test against pyarrow 2.

https://github.com/dask/dask/runs/1281335438?check_suite_focus=true#step:6:211
================================== FAILURES ===================================
_________________________ test_get_pyarrow_filesystem _________________________

    def test_get_pyarrow_filesystem():
        from fsspec.implementations.local import LocalFileSystem

        pa = pytest.importorskip("pyarrow")

        fs = LocalFileSystem()
>       assert isinstance(fs, pa.filesystem.FileSystem)
E       AssertionError: assert False
E        +  where False = isinstance(<fsspec.implementations.local.LocalFileSystem object at 0x00000224F12C08C8>, <class 'pyarrow.filesystem.FileSystem'>)
E        +    where <class 'pyarrow.filesystem.FileSystem'> = <module 'pyarrow.filesystem' from 'C:\\Miniconda3\\envs\\test-environment\\lib\\site-packages\\pyarrow\\filesystem.py'>.FileSystem
E        +      where <module 'pyarrow.filesystem' from 'C:\\Miniconda3\\envs\\test-environment\\lib\\site-packages\\pyarrow\\filesystem.py'> = <module 'pyarrow' from 'C:\\Miniconda3\\envs\\test-environment\\lib\\site-packages\\pyarrow\\__init__.py'>.filesystem

dask\bytes\tests\test_local.py:366: AssertionError
___________________________ test_get_pyarrow_fs_s3 ____________________________

s3 = <s3fs.core.S3FileSystem object at 0x00000224805B9BC8>

    def test_get_pyarrow_fs_s3(s3):
        pa = pytest.importorskip("pyarrow")
        fs = DaskS3FileSystem(anon=True)
>       assert isinstance(fs, pa.filesystem.FileSystem)
E       AssertionError: assert False
E        +  where False = isinstance(<s3fs.core.S3FileSystem object at 0x0000022482EA3BC8>, <class 'pyarrow.filesystem.FileSystem'>)
E        +    where <class 'pyarrow.filesystem.FileSystem'> = <module 'pyarrow.filesystem' from 'C:\\Miniconda3\\envs\\test-environment\\lib\\site-packages\\pyarrow\\filesystem.py'>.FileSystem
E        +      where <module 'pyarrow.filesystem' from 'C:\\Miniconda3\\envs\\test-environment\\lib\\site-packages\\pyarrow\\filesystem.py'> = <module 'pyarrow' from 'C:\\Miniconda3\\envs\\test-environment\\lib\\site-packages\\pyarrow\\__init__.py'>.filesystem

Some additional failures like test_append_with_partition[pyarrow] further down I think.
This is perhaps related to pyarrow 2.0 being released yesterday?

cc @dask/io for visibility

I'll start looking into this - Seems that a new pyarrow package was released.

Just starting to look into this now - Sorry for the delay.  It looks like pyarrow-2.0 deprecated the pyarrow.FileSystem API, so we can no longer check that the fsspec file-system object is an instance of pyarrow.FileSystem (which is done in several tests).  Beyond that, it seems that pyarrow's new file-system API is causing issues (but haven't dug into the specific reasons yet) - Perhaps @martindurant and/or @jorisvandenbossche already know what the problem(s) may be.

The two tests shown above can be updated. It's actually a change in fsspec (but triggered by pyarrow 2.0 release) that fsspec will no longer inherit from the indeed deprecated python pyarrow.filesystem objects (see https://github.com/intake/filesystem_spec/pull/411). In pyarrow 2.0, all relevant code paths should now also accept plain fsspec filesystems, and thus subclassing from the pyarrow.filesystem is no longer needed.

The two tests shown above can be updated. It's actually a change in fsspec (but triggered by pyarrow 2.0 release) that fsspec will no longer inherit from the indeed deprecated python pyarrow.filesystem objects (see intake/filesystem_spec#411)

Agreed - The failure in those particular tests makes perfect sense.  Unfortunately, there are 22 tests failing, and some of them seem to go beyond type checking (from a high-level glance).

The other failures in the parquet tests, I cannot reproduce locally (I have some others though, related to categorical dtype). We also run the dask tests nightly on arrow's CI, where we don't see any failures

The other failures in the parquet tests, I cannot reproduce locally (I have some others though, related to categorical dtype). We also run the dask tests nightly on arrow's CI, where we don't see any failures

Thanks - That is good to know.  I also cannot reproduce the failures locally (they may be Windows specific)

Ah, I missed the fact that they're on windows. Yes, it's certainly likely that it is windows specific. We had regularly path issues on windows, it might be we missed some

I could reproduce the test failures on Windows, and diagnose the issue: https://issues.apache.org/jira/browse/ARROW-10462
See the arrow issue for the longer story, but in short: because of switching fsspec's LocalFileSystem (passed by dask to ParquetDataset) with our own LocalFileSystem, we were generating ParquetDatasetPiece.path with a mixture of \\ and /. And dask is using that exact path as a key in a dictionary here:
https://github.com/dask/dask/blob/48a4d4a5c5769f6b78881adeb1b3973a950e5f43/dask/dataframe/io/parquet/arrow.py#L568-L573
When creating the full_path above, it was using fs.sep, which is / even on Windows when using fsspec.
But somewhere in pyarrow, we started to use \\ to when creating the piece's path. Example output from debugging session from one of the dask parquet tests:
(Pdb) dataset
<pyarrow.parquet.ParquetDataset object at 0x00000290D7506308>
(Pdb) dataset.paths
'C:/Users/joris/AppData/Local/Temp/pytest-of-joris/pytest-25/test_partition_on_pyarrow_0'
(Pdb) dataset.pieces[0].path
'C:/Users/joris/AppData/Local/Temp/pytest-of-joris/pytest-25/test_partition_on_pyarrow_0\\a1=A\\a2=X\\part.0.parquet'

So you see the mixture of / and \\ here, while dask was expecting a path with all /.
We can fix that on the pyarrow side (and hopefully put that in a 2.0.1 release).

(fsspec does have a function in the LocalFileSystem module for making paths posixy)

Yep, and that's what dask is using to pass a base path in posix style to pyarrow. That's also the reason the base style in the example output above is still posix style, but so we have a "bug" when joining the additional file path (the bug is already present in older versions of pyarrow, but only surfaced now in dask due to a change in how we handled fsspec filesystems)

We can fix that on the pyarrow side (and hopefully put that in a 2.0.1 release).

Thank you for looking into this @jorisvandenbossche ! Getting the fix into 2.0.1 would be great :)

So the reason that the bug surfaced now is because the new fsspec filesystems no longer inherit from pyarrow.filesystem.FileSystem, and because of that we take a different code path where we are swapping fsspec's LocalFileSystem with our own LocalFileSystem (which has a different path separator on Windows). While before (when fsspec subclassed pyarrow), we didn't actually take this code path ..


Dont call as_json on Delayed::Backend::Sequel::Job

instead call #to_hash, and turn all the keys to strings, to
keep the rest of the implementation untouched

We are seeing an error in Rollbar, when using Sequel and Delayed Job.
'undefined method `as_json'' for #Delayed::Backend::Sequel::Job:0x007fe7f57d31f8
In this file: https://github.com/rollbar/rollbar-gem/blob/master/lib/rollbar/plugins/delayed_job/job_data.rb#L9
we are calling on @as_json on this class in Delayed Job Sequel
https://github.com/TalentBox/delayed_job_sequel/blob/56e7d69e1710b75ae7044a884961e1ebfd6a4661/lib/delayed/backend/sequel.rb
I updated Rollbar to just use #to_hash, if #as_json is not defined.

Hey @davidbegin, thanks for this. Let me test it and we'll merge it.

Hey @davidbegin,
thank you very much for the notes. You've found a missing piece we forgot to move when we added the plugins architecture. So, JobData should be in the correct namespace and the require in the job_data spec should be fixed.
We'll do this change ourself and check that the specs are passing in master. After that, I think it's a good starting for your PR.

@jondeandres Has there been any movement on this PR? Is there anything I could do to help?
Thanks!


Implement code and pre blocks support on iOS

Details
Adds support for displaying and customising code and pre blocks on iOS.

Still discussing the expected behavior for codeblocks here

It looks like padding in markdownStyle only affects the size of the rectangle in the background and not the text itself:

It's okay for the initial implementation but ultimately we'd like padding to affect the text layout here as well.
I don't think it's possible to achieve padding for inline code on iOS (Slack for iOS also does not support it).
However, I think it should be possible to implement padding for codeblocks. As for horizontal padding, I've copied this code from blockquotes and it seems to work:
https://github.com/Expensify/react-native-live-markdown/blob/cd42c45c0a76c4beba86e52899e196d9f176eb46/ios/RCTMarkdownUtils.mm#L119-L122

As for vertical padding, ChatGPT says that the only option is to set lineSpacing but this affects the height of the cursor so I'm not really sure how to implement it.

There seems to be some problem with codeblocks containing only one character:
https://github.com/Expensify/react-native-live-markdown/assets/20516055/935e409f-8dae-4829-8a51-9d877e905534


Following the tutorial, the container could not be started

zhangzs@Precision-7960-Tower:~$ docker run   -it   --rm   --net=host   --ipc=host   --pid=host   --gpus all   -e=DISPLAY   -e=ROS_DOMAIN_ID   -v /mnt/b/代码/glim/config:/glim/config   koide3/glim_ros2:humble_cuda12.2   ros2 run glim_ros glim_rosnode --ros-args -p config_path:=/glim/config
[2024-08-15 07:40:19.070] [glim] [info] config_path: /glim/config
[2024-08-15 07:40:19.070] [glim] [info] load libodometry_estimation_gpu.so
warning: cudaErrorNoDevice
: no CUDA-capable device is detected
warning: cudaErrorNoDevice
: no CUDA-capable device is detected
warning: cudaErrorNoDevice
: no CUDA-capable device is detected
[2024-08-15 07:40:19.074] [glim] [info] load libsub_mapping.so
warning: cudaErrorNoDevice
: no CUDA-capable device is detected
[2024-08-15 07:40:19.075] [glim] [info] load libglobal_mapping.so
warning: cudaErrorNoDevice
: no CUDA-capable device is detected
[2024-08-15 07:40:19.075] [glim] [info] load libmemory_monitor.so
[2024-08-15 07:40:19.075] [glim] [info] load libstandard_viewer.so
[2024-08-15 07:40:19.079] [glim] [info] load librviz_viewer.so
glfw error 65543: GLX: Failed to create context: BadValue (integer parameter out of range for operation)
[ros2run]: Segmentation fault
zhangzs@Precision-7960-Tower:~$ docker info
Client: Docker Engine - Community
Version:    26.1.4
Context:    default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version:  v0.14.1
Path:     /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version:  v2.27.1
Path:     /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 4
Running: 0
Paused: 0
Stopped: 4
Images: 6
Server Version: 26.1.4
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: nvidia runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: d2d58213f83a351ca8f528a95fbd145f5654e957
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.5.0-45-generic
Operating System: Ubuntu 22.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 112
Total Memory: 250.7GiB
Name: Precision-7960-Tower
ID: 8441afb6-6b8d-40ef-adff-3734a93d7a4f
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
registry.byd.com
<IP_ADDRESS>/8
Registry Mirrors:
https://hub.uuuadc.top/
https://docker.anyhub.us.kg/
https://dockerhub.jobcher.com/
https://dockerhub.icu/
https://docker.ckyl.me/
https://docker.awsl9527.cn/
http://registry.byd.com/
Live Restore Enabled: false

Make sure that you installed NVIDIA container toolkit.

yes，I have installed

Can you see nvidia driver information with the following command? If not, there should be some issues in docker setup.
docker run --gpus all nvidia/cuda:12.2.0-devel-ubuntu22.04 nvidia-smi

Perhaps NVIDIA driver was not installed in the host system?
It seems like nvndia container toolkit is installed, according to Runtimes: nvidia runc io.containerd.runc.v2.


/data/local/tmp/process.sh[340]: /system/xbin/su: inaccessible or not found

Tried to patch Android x86_64 API 30 using Manager:
./patch.sh manager
ramdisk.img: 1 file pushed. 337.6 MB/s (1346686 bytes in 0.004s)
magisk.apk: 1 file pushed. 424.8 MB/s (6874374 bytes in 0.015s)
busybox: 1 file pushed. 412.6 MB/s (2074240 bytes in 0.005s)
process.sh: 1 file pushed. 13.2 MB/s (11525 bytes in 0.001s)
[*] Checking Android version
[*] Unzipping Magisk ..
[*] New Magisk packaging format detected ..
Connecting to raw.githubusercontent.com (<IP_ADDRESS>:443)
wget: note: TLS certificate validation not implemented
saving to '/data/local/tmp/tmp/lib/x86/busybox'
busybox                4% |*                               |  100k  0:00:20 ETA
busybox              100% |********************************| 2170k  0:00:00 ETA
'/data/local/tmp/tmp/lib/x86/busybox' saved
[-] API level greater then 30
[*] Check if we need to repack ramdisk before patching ..
[-] Multiple cpio archives detected
[*] Unpacking ramdisk ..
[-] Dumping from 0 to 1726632 ..
[-] Dumping from 1726720 to 4030140 ..
[*] Repacking ramdisk ..
[*] Build fake boot.img ..
[*] boot.img is ready, launch MagiskManager and patch it.
[*] Installing MagiskManager ..
/data/local/tmp/process.sh[340]: /system/xbin/su: inaccessible or not found
/data/local/tmp/process.sh[340]: /system/xbin/su: inaccessible or not found
[*] Clean up
/data/local/tmp/ramdisk.img: 1 file pulled. 114.8 MB/s (1342590 bytes in 0.011s)

Nevermind, the error does not affect the process. I was able to patch standalone and replaced ramdisk.img. All good


Update to OpenSearch 1.3.8

OpenSearch 1.3.8 has been released - would be great to get an update of the runner too.

opensearch-runner 1.3.13 has been released.


Support overriding description of $ref as part of OpenAPI 3.1

Hello,
I'm trying to add linting to large OpenAPI 3.1 files and and got many no-$ref-siblings errors because we often override the description to add more details.
Since this was supported by some tools and not others I started digging a bit more into what the standard actually is.
It seems that starting with OpenAPI 3.1, it is possible to override the description and summary of a reference, but ONLY those two fields.
Here's a link to the relevant part of the spec : https://spec.openapis.org/oas/v3.1.0#reference-object
And a relevant issue on the OpenAPI-Specifcation repo confirming this behaviour : https://github.com/OAI/OpenAPI-Specification/issues/2744
Here's a quick a example that works if you paste it in https://editor-next.swagger.io, and stops working when setting the OpenAPI version to 3.0.0 :
openapi: 3.1.0
info:
  title: Demo
  version: 1.0.0

components:
  schemas:
    Order:
      description: An Order
      type: object
      properties:
        id:
          type: integer
        customer:
          description: A happy customer
          $ref: "#/components/schemas/Customer"

    Customer:
      description: A Customer
      type: object
      properties:
        id:
          type: integer

Cool, will add it to the list!

a "recent" page explaining the $ref model in details has been published by OpenAPI initiative there
https://learn.openapis.org/referencing/overview.html and around how to resolve reference


Azure ARC :: Omboarding :: AZCM0104 :: Failed To Get OS Information :: Failed to obtain FqdnDNS

Hello,
I'm receiving the following error when trying to onboard my CentOS 7 machine to Azure ARC.
DEBUG[0031] Successfully acquired Authorization Token
DEBUG[0031] Generated Resource Id                         VM Id=XXXXXXXXX-XXXXXXXX-XXXXXXXXX
ERROR[0032] Failed to discover OS information for onboarding  Error="Failed to obtain FqdnDNS: "
DEBUG[0032] Starting client connection on: /var/opt/azcmagent/socks/himds.sock
DEBUG[0032] Awaiting status message from agent...
DEBUG[0032] Status Message received
DEBUG[0032] Cancelled change token
INFO[0032] Exit Code:  AZCM0104: Failed To Get OS Information
FATAL[0032] Failed to obtain FqdnDNS:
FATAL[0032] Failed to obtain FqdnDNS:
DEBUG[0032] Exiting...

Versions:
sudo azcmagent version
azcmagent version  1.7.21162.003

uname -a
Linux BejoNLCentOS02 3.10.0-1160.21.1.el7.x86_64 #1 SMP Tue Mar 16 18:28:22 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/centos-release
CentOS Linux release 7.9.2009 (Core)

Thanks for reaching out to us , but at this time it does not look like you are referring to a document but to a specific scenario . If that's the case we request you to please post your question on Microsoft Q&A and other forums , we have our engineers and others who are monitoring them and will be happy to help .
If you have a document which you are following and if you think it needs  an update , please let us know about that here .

Since we have not recived any response from you  so going ahead and closing the issue for now .


Feature: Select issuer namespace in certificate record

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
You have to get three different issuers if you want to use certificates in three different namespaces.
What you expected to happen:
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: lol-com
  namespace: yellow
spec:
  secretName: lol-com-tls
  issuerRef:
    name: letsencrypt
    namespace: default

should create a certificate in namespace yellow, with the issuer in default
Environment:

Kubernetes version (use kubectl version): server 1.92, client 1.8.6
Cloud provider or hardware configuration**: GCE
Install tools: helm tiller
Others: google cloud console

This functionality was not included on purpose to maintain namespace isolation within a Kubernetes cluster.
In order to not need to create 3 Issuer resources, you can alternatively create a ClusterIssuer resource which is a non-namespaced Issuer. You'll then use something like:
apiVersion: certmanager.k8s.io/v1alpha1
kind: Certificate
metadata:
  name: lol-com
  namespace: yellow
spec:
  secretName: lol-com-tls
  issuerRef:
    name: letsencrypt
    kind: ClusterIssuer

More information on cluster issuers can be found here: https://github.com/jetstack/cert-manager/blob/master/docs/user-guides/cluster-issuers.md
Hope that helps!


Macedonian language

Macedonian language

Can you also add it to the readme please?

Sure, the language is added to the readme.


add setup.py to install python package

This PR adds a setup.py file inside serialbox-python which can be used to pip install it as a python package.
It also adds a build-pip workflow step which pip installs serialbox-python and runs the python tests.

Hi there, this is jenkins continuous integration...
Do you want me to verify this patch?

The tests do now appear to be running (I replaced a sys.exit with the appropriate set-sentinel-value call), but not on CI. I'm unsure why, but it doesn't appear to be finding CMakeLists.txt at the top level of the repo. You can check it out on our branch tests here.

@havogt Could we kick off CI for this PR?


Internet of Things (IoT) Posting data with a REST Client

Great Tutorial!
However I cannot get a response in Step6 of Part3.
I changed "prevent_xsrf": false
Maybe because of missing authorization?
Can you provide the details about the roles assigned to user CODEJAMMER?
Thanks!

I solved the issue. The URL in Step 2 has to include the port 8090. Then it works


Dimensions of blank ball are wrong, may damage typewriter

Hi, sorry to be alarmist, I love the idea of this project, however, it is currently unusable and dangerous due to the included STL file for the blank typeball having incorrect dimensions.
The dimensions are close enough that I was fooled into shaving it down a little and pressing it onto the spindle. The typeball I printed then went on, but it did not come off. Removing it as gently as I could was too violent of a force for the fragile head, and it has now put my Selectric II slightly out of alignment.
I believe that addressing issue #1 should be high priority for you, since as is, the hosted files supplied on Printables, as well as the blank STL included in this repo, will continue to disappoint, and damage the vintage equipment of those who actually try to print and use them.

Thanks for the info, I'll pull down the Shapeways links and put a warning on the Printables ones. I certainly don't want to damage any typewriters!
Can you tell me about the printer and resin you used to print the typeball? Was typeball height wrong, or the diameter of the spindle hole, or something else? I'll get issue #1 resolved now, though the parameters in the source file are still tuned for my printer and my resin (which apparently makes it too tight for others to print).
Best of luck re-aligning your Selectric!

Hi, thanks for the quick response. 🙂
I used an Elegoo Saturn 2 resin printer with Siraya tech blu engineering resin. This resin is harder than other resins & ideal for mechanical applications such as 3D printed selectric type element. 🙂
My printing profile is calibrated, you can see a successful "Towns" print in the picture attached. You should definitely consider calibrating your print profile to an existing standard model instead of adjusting the 3D model to match.
In the moments before I tried to remove the ball, I was impressed that the printer does in fact have enough resolution to successfully type a very convincing floppy disk icon.

In researching realignment, I found out that there are over 800 different adjustments, and that an untrained person like myself can very quickly get it even worse out of alignment. I'll have to wait until I can get it back to a professional, but until then I have come to terms with the fact that my unit just has a bit of a wonky personality now.

The printer I used is a Formlabs 3B+ that is mostly used for validating biomedical devices; I assure you it is well calibrated :)
The typewriter that I tested on initially was a Model I Selectric, perhaps the spindle is a slightly different dimension? The fit was very good but not all the keys work on that machine so I can't use it consistently.

Elements for I & II are the same, I think it should be the same dimensions on the spindle. 🤔

I took a couple measurements, ⬇👍📏

Thanks for posting the typeball_blank.scad source code. The 0.362 inch diameter measurement I took of that IBM type element, it looks like the radius should be about 4.60 mm, but BOSS_INNER_RAD is defined as 4.30 mm.

It's actually maybe more complicated? The .362 is from dedent to dedent. There are 6 small dedents on the inside of the boss which are not actually modeled at all in the typeball and may have some use. I'm going to try just a larger radius but will report back on that.

Thank you for all the measurements and corrections in the PR! Dave Hayden of selectricrescue.org made some major improvements and created a version that works quite well in just OpenSCAD, without relying on external tools. You can get a copy of it here: https://selectricrescue.org/balls/SelectricElement88.scad
Dave also suggests:

As for messing up the alignment, my guess is that they rotated or tilted the element which put slack in the corresponding tape and it fell off one of its pulleys. It's an easy fix, you tilt or rotate it again and guide the tape back onto the pulley and gently release the ball back to its neutral position. If that's what happened hopefully they didn't use it too much with the tape off and kink it up.


[Operator] Support ndim > 3 for batch_dot

In batch_dot, i.e, C = batch_dot(A, B),  both inputs A & B must have ndim=3. However, in some cases our inputs could have have higher dimensionality. We can consider to support the following two cases:

[ ] Both A, B have ndim >3
We should compute the output as:
C[..., i, j] = sum_k (A[..., i, k] * B[..., k, j]), for all indices i, j.

For example, if the shape of A is (batch_size, a1, a2, …, b, c) and the shape of B is (batch_size, a1, a2, …, c, d), the shape of C will be (batch_size, a1, a2, ..., b, d).
This is similar to the matmul in Tensorflow

[ ] One of A, B have ndim > 3
Assume A.ndim >3, we have
C[b, ..., i, j] = sum_k (A[b, ..., i, k] * B[b, k, j]), for all indices i, j.

Supporting these two cases will solve the problems in https://discuss.gluon.ai/t/topic/2534/8, https://discuss.gluon.ai/t/topic/5618/9

同问，1.3 pre版本的都已经更新了，但是貌似还是只支持3 dim.

数据量较大，reshape有点慢，弄好了通知一声，更新一下代码，@sxjscience


chore: add auto labeller

:tada: This PR is included in version 2.0.4 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


feat(api): configure local and staging to store api assets using S3 protocol

Ticket https://phabricator.wikimedia.org/T354744

Leaving this a draft until chart and API images are actually released. I tested this by using the chart branch checked out locally and skaffolding api

This is also still missing values for staging. I'd probably have to test this while dibsing as I'm not entirely sure which configuration values staging actually wants.

Tested this successfully in staging.


More project info

Populate some basic information in the readme
Add a code of conduct + contributing guide to allow for early contributors

Let's merge and move on from that.


Handle both CommonJS and ES6 style module.exports.

In ES6/Babel 6 doing export default function() {} results in that
function being assigned to module.exports.default rather than to
module.exports directly as it does in CommonJS.
Currently the Homebridge platform plugin setup expects the initializer
function to be available from require in CommonJS style, and so it
breaks for projects using ES6. Additionally there is currently no
helpful error when this happens; Homebridge fails to boot with Node
reporting a JS type error that plugin.initializer is not a function.
Here I've retained backwards compatibility with CommonJS style, but
check to see if module.exports is a function itself or if we need to
access module.exports.default. If neither is a function, we throw a
helpful error.

@nfarina Any chance we could get this merged?

not sure anyone is home anymore..

Sorry - I am out of town this week and haven’t had time to open the laptop. I will look at this soon. Thank you!

This is great - thank you for your patience! Merging.

yay


Unnecessary assert in merge_param

https://github.com/google/flax/blob/14dffa6dbe3419acf4bc9ec9459a426cf61d6079/flax/linen/module.py#L1602
I believe this assert to be unnecessary as the check for b when a is None has already been done a few lines above.

Only reason I see to do this is because the type checker cannot infer b is of type T without that assert, else I agree that its not logically required.

Indeed, if I recall correctly this was required for type inference with pytype. I'll close this for now as the assert itself doesn't hurt.


Fixing typo in docs for MoccalClient written as JavaClient

In The end user document we have a typo in section 2.2
The doc mentions that to create a client API we extend JavaClient whereas it should be MoccaClient

@Man-Has-No-Name thank you so much for your contribution!


Portal bridge should guarantee that data was successfully bridged

Portal bridge cannot currently provide either information nor guarantees about how many nodes successfully received the bridged content.
Trin's propogate_gossip function (which is used by portal bridge) is not aware of how many populated ACCEPT messages were received by trin in response to the OFFER messages that it sends, nor how many resulting uTP streams succeeded.

This was resolved in #1032


Mute/reminder

What's this PR for?

https://github.com/zulip/zulip/issues/17008
Moreover we added reminder. It allows user to find muted topics which time of remind came to an end (time of remind depends on for how long user muted particular topic). They are shown on the list in one place, after clicking "Ending mutations" in left panel, under button "Recent topics".

Testing plan

We've done manual tests, personally testing every functionality that have been made in this commit.

Screenshots

Thanks for working on this, @MBrOssss !
In general, we highly recommend working on issues labeled as "help wanted" or "good first issue", as those issues are guaranteed to be ready to be worked on. Because #17008 did not have a specific product design, there are a number of changes that will have to be made in how users interact with this feature.
Please let me know if you are interested in continuing with this feature, in which case I can spend some time to develop a design proposal for it. Alternatively, you are welcome to find a more fully specced out feature to pick up.


A swift3 branch is welcome

public func index(after i: OrderedDictionary.Index) -> OrderedDictionary.Index {
  return (i + 1)
}

This is all was needed to make it compile (to satisfy protocol changes). Still there are some warnings.

I hope to tackle the migration to Swift 2.3/3 during the next week.

Any update?

Due to those frequent changes in the development process of Swift 3 I decided to wait until the final release. In the next weeks I'm going to tackle the update of my app to Swift 3 and since my uses this library I am going to update it as well.

The final release is out since tuesday :) https://swift.org/blog/

I know 😉

Currently I'm waiting for ReactiveCocoa to get updated for Swift 3, so that I can start updating my app. For now I've created a release which targets Swift 2.3.

any update? why do you need ReactiveCocoa?


Pull in latest win32-service gem

Also bump all the omnibus gems. This new gem resolves deprecation warnings on Ruby 2.4
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

I'm assuming the Travis failures re: utf-8 are unrelated as they appeared previously in the build history.


Update GoViral import to create JSON file

There is code duplication occurring as I'm updating each source to produce separate files. In this case the verbatim duplication is unnecessarily complicated (this source only creates one file, but the code anticipates potential multiple files), but I'm leaving it verbatim so it's straightforward to refactor later. (I'd like more time to think about how to do the refactoring, separate from this task.)

:+1:!


Updated build recipe and patches to ray-1.3.0

Signed-off-by: Gregory Shimansky<EMAIL_ADDRESS>
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Ping @vnlitvinov
Would love to still have your input, otherwise merging in ~24h.

@h-vetinari @vnlitvinov is currently on vacations and probably will answer only on the next week.

@gshimansky: @vnlitvinov is currently on vacations and probably will answer only on the next week.

OK, thanks for the info. One thing that would make me much more comfortable in merging this is if we were running the test suite on the build - see #5. If you could tackle that as well, it would be amazing. 🙃

@h-vetinari yes you are right, using Ray tests to verify the build would be great. I saw #5 and will keep it in mind.

This needs a merge or rebase to fix the build_num back to 0.

Isn't it 0 already? https://github.com/conda-forge/ray-packages-feedstock/pull/14/files#diff-f3725a55bf339595bf865fec73bda8ac99f283b0810c205442021f29c06eea9aR27

Isn't it 0 already? https://github.com/conda-forge/ray-packages-feedstock/pull/14/files#diff-f3725a55bf339595bf865fec73bda8ac99f283b0810c205442021f29c06eea9aR27

That's exactly the issue (diff not updated because no merge or rebase) - this is the state on master: https://github.com/conda-forge/ray-packages-feedstock/blob/7bb94d437b5e42e7d4e7a3e1a9eeaf400d6a22f6/recipe/meta.yaml#L28

Seems ray.metrics_agent has been removed?
Traceback (most recent call last):
  File "/home/conda/feedstock_root/build_artifacts/ray-packages_1624303001859/test_tmp/run_test.py", line 23, in <module>
    import ray.metrics_agent
ModuleNotFoundError: No module named 'ray.metrics_agent'

I'd be fine with removing that import-test (including comment), but would be nice if someone could confirm the upstream API break (removing an importable subpackage) - WDYT @vnlitvinov?

Looking at Ray diff between version 1.2.0 and 1.3.0 it seems like they moved metrics_agent.py into _private package.
https://github.com/ray-project/ray/compare/ray-1.2.0..ray-1.3.0

I'd be fine with removing that import-test (including comment), but would be nice if someone could confirm the upstream API break (removing an importable subpackage) - WDYT @vnlitvinov?

@richardliaw could you please comment?..

@vnlitvinov sorry having a bit of trouble following - are you asking to verify that the metrics agent is changes?

@richardliaw
We've added the check to import ray.metrics_agent to the package CI to make sure we check the Ray initialization pipeline (ref: #16). Is it correct that the ray.metrics_agent is now moved? How should we check that what we build is in a working state?

How should we check that what we build is in a working state?

This because ray.init() seemed to do different things in our CI than for user installs (cf #16). Note though that this is just a baby step - I'd much rather run the full test suite (#5), but it's not clear to me how that should be called. I've asked on the upstream tracker already - would be very helpful if you could support there @richardliaw.

While we're waiting for a better solution for testing the packages I've changed the import tests to check for ray._private.metrics_agent to keep packaging efforts rolling.


Doc on TF serving - document Istio and other features like prometheus

migrating this to website

See also #97 we should have a new guide page for just TFServing and put all the information about TFServing there.

/assign
Will get this done once #97 is closed (currently pr #102 in review).

Waiting on #105.

/close


Callbacks of the event listeners getting duplicated by bugsnag library

Hi we're facing some issues with bugsnag
Open this URL
The website has been created with Shopify and according with the Shopify's feedback your bugsnag.js library is loaded on any page that renders a video.
When the page is loaded on a iPad with iOS 13 and Safari 13, try rotate the furniture by dragging horizontally the glider chair, the first time it rotates properly.
Then change the features using the configuration panel of the right section  and try to rotate the furniture again, here is the error, sometimes it opens the zoom unexpectedly, even if you try to rotate it keeps opening the zoom and it is not the expected behavior.
(If you were not able to reproduce the issue please refresh the page and try again)
As a background, we listen for the touch events to detect if the user taps the screen to rotate the viewer or if the user double taps the screen to enter the zoom mode.
To achieve that, we create two event listeners for the cylindo-viewer-container element; one of them checks if the user rotates the viewer and the other one keeps listening if the user double taps the screen to open the zoom module. In the right panel of the below screenshot as you can see both functions "c" and "l" are set properly when a user enters the website the first time.

Then, when features are changed, the library bugsnag.js changes our core and creates some wrapper functions that override our internal functions and it causes the error because one of our functions is duplicated.
The duplicated function is the one that we use to open the zoom module when the user double taps the screen. Since both resultant functions are triggered when the user touches the screen once, our core understands that as a double tap and opens the zoom module. Please see the below screenshot, it shows the duplicated functions in the right panel and the function "c" has dissapeared.

As you can see the functions were created within the file inline-script-content.js that file belongs to the bugsnag library and in that file there is the logic that is affecting the viewer. Actually I think you may already aware about the issue because you've have some comments saying that the resultant function mustn't be anonymous due to a bug in the stack generation logic and you pointed the code to an issue report.

So currently, the bugsnag library is hijacking the callbacks of the event listeners and for some reason is duplicating some of them, any idea why this is happening?

Bugsnag version: It seems to be version 6
Browser version: iOS 13, Safari 13:
Device: iPad

Hi bugsnag team, any update on this ^ ?

Hi bugsnag team, do you have any updates on this issue?

Hi @Esteban26, we've been looking into this but haven't been able to reproduce the issue you're seeing.
I did notice that the DOM structure for that page has changed slightly since you raised the issue - have you been able to get to the bottom of the problem?
For some additional context, the Bugsnag code you're referring to wraps every builtin place you can provide a callback so that we can trace it back in case an inline script caused it. The code comments here are referring to an issue where that particular function was being named incorrectly when generating a backtrace.

@Esteban26 can you confirm if you're still seeing the issue and if so share a reliable way to reproduce?

Hi Matt, sorry for the late reply, I'll try to reproduce it by early next week and if I'm able I'll share with you some videos of the current behavior.

@Esteban26 - were you able to reproduce? If so please share the full details and we can re-open this issue.


LESQ-888: OakUnitListItem Component

How to review this PR
Leave this text block for the reviewer

Check component hierarchy is followed correctly
Check the design Heuristics have been followed
Check naming conventions have been applied
Check for these gotchyas:

Missing exports for Oak components
Accidental export of Internal components
Snapshots of unexpected components have been modified
Circular dependencies
Code duplication (via not using base components)
Non-functional storybook for this or related components
Sensitve files changed eg. atoms, or style tokens
Relative imports
Default exports

Add your PR description below
Refactored Unit List Item Component, created within the components lib and storybook
Link to the design doc
https://www.figma.com/design/YcWQMMhHPVVmc47cHHEEAl/🟢-Oak-Design-Kit?m=dev
A link to the component in the deployment preview
https://deploy-preview-209--lively-meringue-8ebd43.netlify.app/?path=/docs/components-organisms-teacher-oakunitlistitem--docs
Testing instructions
Navigate to the storybook link to test the design at different states and on different view ports
ACs
Build new Unit List Item component with corresponding states denoted in Figma designs

I know you didn't ask for my review but I have snuck in :P What is this unavailable value and why does it add a black border around the card?

Removed the border. Presumed if any units were expired or not released yet they would be unavailable

[ ] Unfortunately looks like small (and large) mobile views in Storybook bleed over the edge.

I'll trust Monika on all the colours and spacings!

Fixed the overflow bug @Monika-Koziol would it be possible to check the alignment on the small phone view?

This was behaving weirdly for me, and only me so we are merging and will see how it works once on the site.

Should be fixed now
https://github.com/oaknational/oak-components/assets/91190841/4ac6ff66-6d5c-4d0d-bba7-9f1b08cf507e


指定“视频格式"为ts后文件音轨损坏

Code of Conduct

[X] 我已在 Release 检阅最新版本并尝试，且问题依旧
[X] 我清楚知道，反馈非最新 Release 版的错误是无意义的
[X] 我清楚知道，可以通过附件功能上传完整文件

运行环境
Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-190-generic x86_64) && Python 3.8.10
biliup 版本
v0.4.76
所录制的主播网址
https://play.afreecatv.com/xxxx
错误描述
在该帖里已有提过，视频具体信息：
ffprobe version 7.0.1-tessus  https://evermeet.cx/ffmpeg/  Copyright (c) 2007-2024 the FFmpeg developers
  built with Apple clang version 15.0.0 (clang-15<IP_ADDRESS>)
  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libfreetype --enable-libgsm --enable-libharfbuzz --enable-libmodplug --enable-libmp3lame --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-version3 --pkg-config-flags=--static --disable-ffplay
  libavutil      59.  8.100 / 59.  8.100
  libavcodec     61.  3.100 / 61.  3.100
  libavformat    61.  1.100 / 61.  1.100
  libavdevice    61.  1.100 / 61.  1.100
  libavfilter    10.  1.100 / 10.  1.100
  libswscale      8.  1.100 /  8.  1.100
  libswresample   5.  1.100 /  5.  1.100
  libpostproc    58.  1.100 / 58.  1.100
[aac @ 0x7fd8a7204c40] More than one AAC RDB per ADTS frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[aac @ 0x7fd8a7204c40] Assuming an incorrectly encoded 7.1 channel layout instead of a spec-compliant 7.1(wide) layout, use -strict 1 to decode according to the specification instead.
[aac @ 0x7fd8a7204c40] channel element 1.7 is not allocated
[aac @ 0x7fd8a7204c40] channel element 3.4 is not allocated
[aac @ 0x7fd8a7204c40] Sample rate index in program config element does not match the sample rate index configured by the container.
[aac @ 0x7fd8a7204c40] Too large remapped id is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[aac @ 0x7fd8a7204c40] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list<EMAIL_ADDRESS>[aac @ 0x7fd8a7204c40] channel element 2.12 is not allocated
[aac @ 0x7fd8a7204c40] channel element 3.7 is not allocated
[aac @ 0x7fd8a7204c40] channel element 2.10 is not allocated
[aac @ 0x7fd8a7204c40] channel element 1.0 is not allocated
[aac @ 0x7fd8a7204c40] channel element 1.6 is not allocated
[aac @ 0x7fd8a7204c40] channel element 2.8 is not allocated
    Last message repeated 1 times
[aac @ 0x7fd8a7204c40] channel element 3.8 is not allocated
[aac @ 0x7fd8a7204c40] channel element 3.3 is not allocated
[aac @ 0x7fd8a7204c40] channel element 3.0 is not allocated
[mpegts @ 0x7fd8a7004b00] Could not find codec parameters for stream 1 (Audio: aac (LTP) ([15][0][0][0] / 0x000F), 7.1, fltp): unspecified sample rate
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
Input #0, mpegts, from 'xxxx.ts':
  Duration: 04:10:32.10, start: 1.400000, bitrate: 6564 kb/s
  Program 1
    Metadata:
      service_name    : Service01
      service_provider: FFmpeg
  Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 60 fps, 60 tbr, 90k tbn
  Stream #0:1[0x101]: Audio: aac (LTP) ([15][0][0][0] / 0x000F), 7.1, fltp
[aac @ 0x7fd8a7019f00] Assuming an incorrectly encoded 7.1 channel layout instead of a spec-compliant 7.1(wide) layout, use -strict 1 to decode according to the specification instead.

利用 ffmpeg -analyzeduration 100M -probesize 100M -i "$file" -c:v copy -c:a aac -b:a 128k "${file%.ts}.mp4" 转码并不可行：
  for file in *.ts; do ffmpeg -analyzeduration 100M -probesize 100M -i "$file" -c:v copy -c:a aac -b:a 128k "${file%.flv}.mp4"; done
...
[aac @ 0x7fe3a2806c80] More than one AAC RDB per ADTS frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[aac @ 0x7fe3a2806c80] Assuming an incorrectly encoded 7.1 channel layout instead of a spec-compliant 7.1(wide) layout, use -strict 1 to decode according to the specification instead.
[aac @ 0x7fe3a2806c80] channel element 1.7 is not allocated
[aac @ 0x7fe3a2806c80] channel element 3.4 is not allocated
[aac @ 0x7fe3a2806c80] Sample rate index in program config element does not match the sample rate index configured by the container.
[aac @ 0x7fe3a2806c80] Too large remapped id is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[aac @ 0x7fe3a2806c80] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list<EMAIL_ADDRESS>[aac @ 0x7fe3a2806c80] channel element 2.12 is not allocated
[aac @ 0x7fe3a2806c80] channel element 3.7 is not allocated
[aac @ 0x7fe3a2806c80] channel element 2.10 is not allocated
[aac @ 0x7fe3a2806c80] channel element 1.0 is not allocated
[aac @ 0x7fe3a2806c80] channel element 1.6 is not allocated
[aac @ 0x7fe3a2806c80] channel element 2.8 is not allocated
    Last message repeated 1 times
[aac @ 0x7fe3a2806c80] channel element 3.8 is not allocated
[aac @ 0x7fe3a2806c80] channel element 3.3 is not allocated
[aac @ 0x7fe3a2806c80] channel element 3.0 is not allocated
[mpegts @ 0x7fe3a2804f80] Could not find codec parameters for stream 1 (Audio: aac (LTP) ([15][0][0][0] / 0x000F), 7.1, fltp): unspecified sample rate
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
Input #0, mpegts, from 'xxxxx.ts':
  Duration: 04:10:32.10, start: 1.400000, bitrate: 6564 kb/s
  Program 1
    Metadata:
      service_name    : Service01
      service_provider: FFmpeg
  Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 60 fps, 60 tbr, 90k tbn
  Stream #0:1[0x101]: Audio: aac (LTP) ([15][0][0][0] / 0x000F), 7.1, fltp
[aac @ 0x7fe3a28127c0] Assuming an incorrectly encoded 7.1 channel layout instead of a spec-compliant 7.1(wide) layout, use -strict 1 to decode according to the specification instead.
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Press [q] to stop, [?] for help
[aac @ 0x7fe3a28127c0] channel element 1.0 is not allocated
[aist#0:1/aac @ 0x7fe3a2905400] [dec:aac @ 0x7fe3a281c540] Error submitting packet to decoder: Invalid data found when processing input
[aac @ 0x7fe3a28127c0] More than one AAC RDB per ADTS frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[aac @ 0x7fe3a28127c0] channel element 3.12 is not allocated
[aist#0:1/aac @ 0x7fe3a2905400] [dec:aac @ 0x7fe3a281c540] Error submitting packet to decoder: Invalid data found when processing input
[aac @ 0x7fe3a28127c0] Reserved bit set.
[aac @ 0x7fe3a28127c0] Number of bands (37) exceeds limit (19).
[aist#0:1/aac @ 0x7fe3a2905400] [dec:aac @ 0x7fe3a281c540] Error submitting packet to decoder: Invalid data found when processing input
[aac @ 0x7fe3a28127c0] channel element 1.7 is not allocated
[aist#0:1/aac @ 0x7fe3a2905400] [dec:aac @ 0x7fe3a281c540] Error submitting packet to decoder: Invalid data found when processing input
[aac @ 0x7fe3a28127c0] channel element 3.4 is not allocated
[aist#0:1/aac @ 0x7fe3a2905400] [dec:aac @ 0x7fe3a281c540] Error submitting packet to decoder: Invalid data found when processing input
[aac @ 0x7fe3a28127c0] Sample rate index in program config element does not match the sample rate index configured by the container.
[aac @ 0x7fe3a28127c0] Too large remapped id is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[aac @ 0x7fe3a28127c0] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list<EMAIL_ADDRESS>
-c copy, -c copy -map 0, 加 -strict experimental, -vn -c:a aac -b:a 128k -ar 44100 单独提取音轨... 都没有用。
不是一个文件，所有ts文件都是如此。
mpv播放无法识别音轨，相当于白录了。（不指定“视频格式”确实可以避免，但...

好像是音轨数错误？上面这个是7.1，另一个ts文件则是3.0,；没指定ts格式的flv文件的是stereo.
任务平台

任务平台

# 在这里填写你的配置文件

报错日志以及其他描述（如果有）

### 日志

# 在这里填写你的报错日志

其他补充描述

https://github.com/biliup/biliup/blob/d8720dac0363e7f33c64c087ad391f5342c2b222/biliup/engine/download.py#L174-L177
删去 176 行即可


Remote data packages with resources relative to their URL should be safe

For example, the datapackage.json at https://raw.githubusercontent.com/datasets/gdp/master/datapackage.json defines a resource with a relative path (data/gdp.csv), which should be downloaded at https://raw.githubusercontent.com/datasets/gdp/master/data/gdp.csv. This should be considered safe, as their "base path" is the same (https://raw.githubusercontent.com/datasets/gdp/master).
This currently isn't the case. This issue was reported by @ndkv's on https://github.com/ckan/ckanext-datapackager/issues/38#issuecomment-199694709

I ran into a similar safe/unsafe issue: uploading a remote datapackage.json (i.e. unzipped) that uses relative paths for its resources [1] gives an Unsafe ... error while uploading the same package with "absolute" urls [2] works fine.
This seems to be the intended behaviour

To avoid a resource with a path like /etc/shadow, this extension only accepts paths relative to the datapackage's ZIP file. As you haven't uploaded a ZIP, but the actual datapackage.json, that doesn't exist, so no local path is valid.

While I see the need to prevent /etc/shadow-like paths, I'm not sure disallowing relative resource paths for remote packages (i.e. unzipped) is intended as well. Also, the spec allows relative paths for remote pacakges

NOTE: the use of a url allows a data package to reference data not contained locally in the Data Package. The path attribute may also be used for Data Packages located online – in this case it determines the resource file’s URL relative to the datapackage.json’s URL.

I'm not familiar (at all) with inner working of CKAN/extension code but it seems that the culprit is line 151 in the safe function linked above
if not resource.local_data_path.startswith(self.base_path):

I guess remote data packages have their URL as base_path. Relative paths are rejected since they don't start with the URL. urls on the other hand pass this test just fine.
So, to allow relative paths on remote packages we'd need to treat path differently, right?
[1] https://github.com/ndkv/datasets/blob/master/gemeenschappelijke_regelingen/partial/datapackage.json
[2] https://github.com/ndkv/datasets/blob/gh-pages/gemeenschappelijke_regelingen/partial/datapackage.json
[3] http://dataprotocols.org/data-packages/#required-fields-1
BTW The "unsafe" message initially tricked me into thinking that the package's description attribute was the culprit as it contains links (it isn't and the links are stripped). It might be better, if possible, to mention something about the difference between url and path.

We currently consider any remote resource as safe, but what about a remote datapackage.json like:
{
    "name": "unsafe",
    "resources": [
        { "path": "../../foo.csv" }
    ]
}

Say that the datapackage.json lives at http://www.foo.com/bar/baz/datapackage.json, then the resource would be at http://www.foo.com/foo.csv. Is it unsafe or not?
Considering that this datapackage is equivalent to:
{
    "name": "unsafe",
    "resources": [
        { "path": "http://www.foo.com/foo.csv" }
    ]
}

and that is safe, I say we consider the first one safe as well. All in all, we consider every remote resource to be safe.
Thoughts?

While researching this issue I stumbled on #97.
Once that is fixed safe() should be updated to check remote_data_paths as well. [Line 151] (https://github.com/frictionlessdata/datapackage-py/blob/master/datapackage/datapackage.py#L151) should be replaced by something like this.
if resource.local_data_path:
    if not resource.local_data_path.startswith(self.base_path):
        return False

if resource.remote_data_path:
    if not resource.remote_data_path.startswith(self.base_path):
        return False

Thoughts? I'll send pull requests of you think this is the right approach.

I think this needs more discussion.
We currently consider all remote resources to be safe. The issue with this is when uploading a datapackage to, for example, a CKAN instance using ckanext-datapackager. The CKAN instance will load the datapackage and its resources if it's safe. We only consider local resources to be safe it they're relative to the datapackage.json path, so a user couldn't send a datapackage with a resource as /etc/shadow, for example. However, as all remote resources are considered safe, they could still send a datapackage pointing to http://<IP_ADDRESS>/secret-file.txt in the server's local network and have its contents published on CKAN.
This is kind of difficult to exploit, as it requires knowledge of the server's intranet and the ability to upload a datapackage to CKAN. This is only considering CKAN, though. There might be uses of datapackage-py that makes this hole easier to exploit.
We could limit remote resources to the same base path of the datapackage.json, the same way we do with local resources, but that means that it won't be possible for a datapackage to point to resources outside of it domain (e.g. the World Bank data portal).
I think it's OK to consider all remote resources as safe, as we do now, maybe just documenting this possible attack vector so clients can handle it. What do you think, @pwalsh @roll @rgrp?

Another option is to detect local network IPs with e.g. the ipaddress module. We can then either flag them as unsafe or issue a warning in case someone is willingly/knowingly working with private IPs.

ipaddress looks like a real complication..
Sometimes such kind of problems could be fixed stepping a few steps back and re-checking everything starting from is this a properly defined problem we try to solve or may be we could solve other problem to achieve the real goal?
I'm not fully into this situation so a a fresh look - why e.g. just to do not forbid dots in paths?

@roll The local paths are fine: if it's inside the datapackage.json's folder, it's safe; otherwise it's unsafe. For remote paths is a bit more tricky: there can be URLs only accessible from the server.
The attack vector I'm thinking is a user with permission to upload to a CKAN instance using ckanext-datapackager (e.g. http://datahub.io), and a server with access to a webserver that the user can't access directly (e.g. in a Intranet, but can be outside). The user could upload a datapackage.json with a remote resource that points to this URL. CKAN would then hit that URL, download whatever is in it and upload as a CKAN resource, which can be read by the attacker.
This is a very narrow attack vector without a simple solution. In this case, I'd suggest we should just log it in a comment (e.g. the safe() docstring) letting the user know, so she can evaluate and decide what to do about it (if anything at all). At most, we could add a safe(no_remote_resources=False) or similar to allow the user to decide if remote URLs are OK or not, but I wouldn't implement that before we have an actual user needing it (probably the datahub itself).

FIXED by #139 and #140


F2 rename no longer works

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.83.1
OS Version: OS Name	Microsoft Windows 10 Pro Version	10.0.19045 Build 19045

Steps to Reproduce:

Click on a variable/function name
Press F2, rename box pops up as usual
Enter new name and press enter
Variable/function is renamed but none of the references to it are

Sorry, was due to accidental duplicate variable name.


Observing peers should not also validate committed blocks.

@SamHSmith, why we don't want to re-validate block?

Yes that what my reason. Having thought about it I do not think they gain to be had is significant. The reason being that an observing peer isn't participating in the consensus process and is therefore not delaying block production by spending time validating.


Add mpv.net store version path detection to syncplay

Describe the bug
Syncplay doesn't detect mpv.net from store.
To Reproduce
Steps to reproduce the behavior:

Install https://www.microsoft.com/en-us/p/mpvnet/9n64sqztb3lm
Run syncplay
mpv.net from store is not detected.

Expected behavior
Syncplay detected $env:LOCALAPPDATA\Microsoft\WindowsApps\mpvnet.exe as mpv.net binary
Screenshots
If applicable, add screenshots to help explain your problem.
Version and platform:

OS: Windows 11 Pro
Syncplay version and build type: Syncplay 1.6.9

Additional context
Add any other context about the problem here.

Syncplay was looking for mpv.net in the following locations:

'c:\program files\mpv.net\mpvnet.exe'
'c:\program Files (x86)\mpv.net\mpvnet.exe'

Thanks to your suggestion I will now add  '%LOCALAPPDATA%\Microsoft\WindowsApps\mpvnet.exe' to the list.

@soredake The way mpvnet.exe file in the WindowsApp seems to be some sort of weird dummy file which Python doesn't detect as existing, so I had to hack it to actually look for mpvnet.com instead but then run the .exe version.
When you have time please test it out at and let me know if it works properly for you - you can give either the portable or installer versions of Syncplay a try:

Portable version: https://github.com/Syncplay/syncplay/suites/4809975579/artifacts/135272074
Installer version: https://github.com/Syncplay/syncplay/suites/4809975579/artifacts/135272075

@Et0h thanks, it detects it now.


update integration test

work in progress, add more test

Codecov Report

Merging #630 (903f717) into pipeline (5596d7c) will increase coverage by 0.20%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           pipeline     #630      +/-   ##
============================================
+ Coverage     72.14%   72.34%   +0.20%
============================================
  Files            96       96
  Lines         10822    10822
============================================
+ Hits           7807     7829      +22
+ Misses         2535     2511      -24
- Partials        480      482       +2

Impacted Files
Coverage Δ

pkg/object/mqttproxy/session.go
82.20% <0.00%> (+7.97%)
:arrow_up:

pkg/filters/kafkabackend/kafka.go
72.36% <0.00%> (+11.84%)
:arrow_up:

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 5596d7c...903f717. Read the comment docs.


Qt example ?

Hi,
I know Qt example has been replaced but I'd like to know which version of OSPray has the most recent version of it before it was deprecated ?
Cheers

v1.2.1 is the latest, v1.3 replaced it.


NFT: collaboratorField should not be passed as an API parameter

The collaboratorField like collaborators[0] or  collaborators[1] should not be passed in the proof_fields on the api endpoint.
Instead the centNode should add the collaborators field automatically to the proofs.

Closing this issue as it will be addressed differently.


[red-knot] Detect classes with incompatible __slots__ being used in multiple inheritance

This isn't necessarily a priority for red-knot, but it's something that we'll want to do at some point and it could be easily done now.
Two classes that both have nonempty __slots__ cannot be used in multiple inheritance. We should detect this and emit a diagnostic for it.
>>> class Foo:
...     __slots__ = ("a",)
...
>>> class Bar:
...     __slots__ = ("b",)
...
>>> class Baz(Foo, Bar): ...
...
Traceback (most recent call last):
  File "<python-input-2>", line 1, in <module>
    class Baz(Foo, Bar): ...
TypeError: multiple bases have instance lay-out conflict

We'll probably want to check for this as part of this method here: https://github.com/astral-sh/ruff/blob/82faa9bb62e66a562f8a7ad81a645162ca558a08/crates/red_knot_python_semantic/src/types/infer.rs#L510-L520
Notes on the semantics:
(1) A class with no __slots__ can be used in multiple inheritance with a class that has __slots__
>>> class A: ...
...
>>> class B:
...     __slots__ = ("a",)
...
>>> class C(A, B): ...
...
>>>

(2) Empty __slots__ are fine in combination with multiple inheritance:
>>> class A:
...     __slots__ = ()
...
>>> class B:
...     __slots__ = ("a",)
...
>>> class C(A, B): ...
...
>>>

(3) But even two classes with equal __slots__ will fail in multiple inheritance if they are both non-empty:
>>> class A:
...     __slots__ = ("a",)
...
>>> class B:
...     __slots__ = ("a",)
...
>>> class C(A, B): ...
...
Traceback (most recent call last):
  File "<python-input-11>", line 1, in <module>
    class C(A, B): ...
TypeError: multiple bases have instance lay-out conflict

(5) And __slots__ are inherited by subclasses:
>>> class A:
...     __slots__ = ("a",)
...
>>> class B(A): ...
...
>>> class C:
...     __slots__ = ("c",)
...
>>> class D(C): ...
...
>>> class E(B, D): ...
...
Traceback (most recent call last):
  File "<python-input-16>", line 1, in <module>
    class E(B, D): ...
TypeError: multiple bases have instance lay-out conflict

Perhaps the case where this comes up most is with builtin/extension types, that aren't implemented in Python and thus don't use __slots__ Python API, but do still have a bespoke instance memory layout (rather than just a dictionary of attributes), like a Python class that uses __slots__. E.g. you can't multiple-inherit int and str for this reason.
But typeshed does not explicitly apply __slots__ to types like int or str that effectively do have slots. We could potentially advocate to change this. But in the meantime, fully implementing this feature would also require adding a special case to always consider some known typeshed classes as having slots.

Yeah, I think there's three distinct issues here:

If two classes both have non-empty __slots__ definitions that are "visible" (i.e., we can see the __slots__ definitions in the source-code files we treat as the canonical source of information for those classes) to red-knot, and they're used in multiple inheritance, should we emit a diagnostic? I think we clearly should, because we have all the information we require to detect that an exception will definitely be raised at runtime. Lots of libraries and applications use classes with __slots__, so I think we'll catch a lot of possible bugs just by implementing this.

Typeshed generally doesn't include __slots__ for any classes (even pure-Python) in its stubs. It probably should, as it would give type checkers a lot more information to work with in this domain, allowing them to catch a lot more bugs. This has been discussed previously in https://github.com/python/typeshed/issues/8832.

As you say, you get an identical error message at runtime to the __slots__ error message if you try to multiple-inherit from various builtin classes such as str or int that CPython considers to be "solid bases", despite the fact that these classes do not have __slots__ definitions (at least, not __slots__ definitions that are visible from the Python level):
>>> class Foo(int, str): ...
...
Traceback (most recent call last):
  File "<python-input-0>", line 1, in <module>
    class Foo(int, str): ...
TypeError: multiple bases have instance lay-out conflict
>>> hasattr(int, "__slots__")
False
>>> hasattr(str, "__slots__")
False

There are various possible ways we could detect this. Typeshed could pretend that they have __slots__ definitions even though they don't (at least, not in the same way as pure-Python classes that define __slots__); we could hardcode a list of builtin classes in red-knot that you can't combine in multiple inheritance; or we could work on a new standardised type-system feature that allows us to express when a class is a "solid base" that you can't use in multiple inheritance.

I think these are all quite separate questions; the only one I was attempting to tackle in this issue was question (1).

Those are great edge cases @InSyncWithFoo! I think for an initial implementation of this check we could easily defer them all however, and only emit the incompatible-slots error if two classes in the bases list have non-dynamic slots definitions that are both definitely bound. We could then open follow-up issues to expand the check and detect issues in more cases. This would make the initial PR easy for us to review and would be in keeping with the principle that we should avoid aim to avoid false positives as much as possible (even if it causes false negatives in some situations) in our initial implementation of red-knot.


Add documentation stub for authentication

Since I had to figure this out on my own I thought I'll scribble some docs for it so the next guy won't have to :)
I've no experience with sphinx docs, I hope this will do mostly.

I've merged this PR into the 0.9.1-dev branch and squared it away with the rest of the docs. I'm trying to figure a few little things out with it, though, so I'm making some comments on the commit.


Add CameraFlightPath.createTween maximumHeight test

Tweak camera flight path height computation and add a test for the maximumHeight parameter.
Continuation of #3675 for #3674.
CC @anne-gropler I made a couple tweaks and added a test to your PR if you're interested.

Looks good! Thanks @bagnell


ELB-iSCADA request for ID and Password

Hello all,
I'm using ELB-iSCADA as LTE modem after powering it up it asks for login id and password, what should I write?

No idea. This is not a good place to ask about this.


grunt-php does not work with node v0.10.x

Travis disagrees → https://travis-ci.org/sindresorhus/grunt-php/jobs/89385595

Well, it's not working on our old environment here with node 0.10.12 on Windows 7, don't know if it's worth to investigate any further.

Looking into Node.js 0.10 issues isn't very high on my priority list, but feel free to open an issue with some more information.

Thanks, I'll check it more deeply.


spawn.py issues

when I run train.py I get:
19-01-02 21:35:49.755 - INFO: Model [SRRaGANModel] is created.
19-01-02 21:35:49.773 - INFO: Start training...
Traceback (most recent call last):
  File "train.py", line 154, in <module>
    main()
  File "train.py", line 79, in main
    for i, train_data in enumerate(train_loader):
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\site-packages\torch\utils\data\dataloader.py", line 819, in __iter__
    return _DataLoaderIter(self)
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\site-packages\torch\utils\data\dataloader.py", line 560, in __init__
    w.start()
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\multiprocessing\process.py", line 105, in start
    self._popen = self._Popen(self)
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\multiprocessing\context.py", line 223, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\multiprocessing\context.py", line 322, in _Popen
    return Popen(process_obj)
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\multiprocessing\popen_spawn_win32.py", line 65, in __init__
    reduction.dump(process_obj, to_child)
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\multiprocessing\reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)
TypeError: can't pickle Environment objects

E:\projects\BasicSR\codes>Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\multiprocessing\spawn.py", line 105, in spawn_main
    exitcode = _main(fd)
  File "C:\Users\Claes\AppData\Local\Programs\Python\Python36\lib\multiprocessing\spawn.py", line 115, in _main
    self = reduction.pickle.load(from_parent)
EOFError: Ran out of input

I am running windows 10 home and python 3.6.8 gtx 1060 max q

Seems like it is a bug of Pytorch-windows. I would recommend you report this to Pytorch forum or switch your platform to Linux.


Use @:autoBuild on interface

Hey, to make it simpler to implement LazyProps, you can use an @:autoBuild macro instead.
@:autoBuild(LazyPropsBuilder.build()) interface LazyProps {}

Then you can implement that interface on any class instead of specifying the complicated @:build metadata.

Btw, have you checked out Dataclass? It does almost the same thing, but uses fields instead: https://github.com/ciscoheat/dataclass

Thanks for the suggestion. I'll consider using an interface as it evolves.


Insert Subcircuit popup changes

Changes:

Replaced the "insert subcircuit" button with a "create subcircuit" one in case no other circuits are already existing in the project.
Removed a no longer used reBuild function.

Screenshots of the changes:

I don't think this is necessary.


HW1

only add readme and rename the folder
(I don't know what else can put in readme)

I prefer move  shell folder to hw1/project1 or something instead of make it stand alone

3.p5 rename to 3.p1
rm .zip
doc有需要寫kernel版本嗎，應該每個人都不一樣

I prefer move shell folder to hw1/project1 or something instead of make it stand alone.

I can't understand 😦

I prefer move shell folder to hw1/project1 or something instead of make it stand alone.

I can't understand 😦

forget about it

3.p5 rename to 3.p1

rm .zip

doc有需要寫kernel版本嗎，應該每個人都不一樣

LGTM


Does not seem to start

Problem
I downloaded and ran the application (allowing it in the Security and Privacy) but nothing seems to happen
Details:
Installation Method: brew
OS Version: MacOS Big Sur 11.2.3
Additional Context
Love the idea, just need to get it to work, please let me know if you need more information

Seems to have started after a restart


部署成功之后集群内都不能新建pod了，报错failed calling webhook

集群版本1.26.9

Can you share your webhook configuration and the svc information under the kube-system namespace?

Everything seems fine, is your k8s cluster working normally? You can further check if the network of the cluster is working properly.

I have checked the cluster network, host network, service network, Kube Proxy, and Cilium CNI, all of which are normal

能加你微信或者钉钉吗？我好像已经定位到原因了

请问这个问题，怎么解决的呢？我也遇到了同样的情况，所有的组件看起来都正常，但是就是有Failed calling webhook, failing open vgpu.hami.io: failed calling webhook "vgpu.hami.io": failed to call webhook: Post "https://hami-scheduler.kube-system.svc:443/webhook?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
E0707 11:53:33.346585       1 dispatcher.go:180] failed calling webhook "vgpu.hami.io": failed to call webhook: Post "https://hami-scheduler.kube-system.svc:443/webhook?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

请问这个问题，怎么解决的呢？我也遇到了同样的情况，所有的组件看起来都正常，但是就是有Failed calling webhook, failing open vgpu.hami.io: failed calling webhook "vgpu.hami.io": failed to call webhook: Post "https://hami-scheduler.kube-system.svc:443/webhook?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) E0707 11:53:33.346585 1 dispatcher.go:180] failed calling webhook "vgpu.hami.io": failed to call webhook: Post "https://hami-scheduler.kube-system.svc:443/webhook?timeout=30s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

@luli817 @chaunceyjiang

当时解决了后面就忘记了


Pipeline S3 config update

Description of your changes:

Modify s3 config to update artifacts keyformat with date to avoid name collisions
use emissary as containerRuntimeExecutor for workflow-controller-configmap
update associated pipeline chart content changes with this PR https://github.com/awslabs/kubeflow-manifests/pull/654

Testing:

[ ] Unit tests pass
[x] e2e tests pass
Details about new tests (If this PR adds a new feature)
Details about any manual tests performed

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ryansteakley please review it from your end


If the user doesn't grant Bluetooth on the Bluetooth screen, or we detect bluetooth is off at any other point, send them to a screen that tells them how to turn on Bluetooth

This is done here:
https://github.com/covid19risk/covidwatch-ios/pull/56
There is a comment in the code on the Home View explaining that the homescreen itself could be customized to let the user know there is an issue on top of or instead of the existing UIAlert


Error in drmsd computation

I think the drmsd computation in the function calc_avg_drmsd_over_minibatch is wrong.
https://github.com/OpenProtein/openprotein/blob/e4e2e0c8597f1f113b7074d0e6b223f8d019138e/util.py#L267
Here actual_coords_list[idx] is a tensor of size [seq_len, 9].
The 9 coordinates are the x,y,z corresponding to C', C-alpha, N
You want to convert it into a tensor of size [seq_len*3, 3]
But the current code does not convert the coordinates correctly.
>>> torch.tensor([[1,2,3,4,5,6,7,8,9],[10,11,12,13,14,15,16,17,18]]).transpose(0,1).contiguous().view(-1,3)
tensor([[  1,  10,   2],
        [ 11,   3,  12],
        [  4,  13,   5],
        [ 14,   6,  15],
        [  7,  16,   8],
        [ 17,   9,  18]])

You can see the coordinates are mangled.
I think the correct code should be
actual_coords = actual_coords_list[idx].view(-1, 3)

>>> torch.tensor([[1,2,3,4,5,6,7,8,9],[10,11,12,13,14,15,16,17,18]]).view(-1,3)
tensor([[  1,   2,   3],
        [  4,   5,   6],
        [  7,   8,   9],
        [ 10,  11,  12],
        [ 13,  14,  15],
        [ 16,  17,  18]])

Hey @ecvgit , thanks for flagging this. If this is the case, it is presumably also a problem here https://github.com/OpenProtein/openprotein/blob/e4e2e0c8597f1f113b7074d0e6b223f8d019138e/openprotein.py#L84 ? I've set up some proper unit tests soon so things like this can be verified.