Finish "social debt" Experiences section

There is still a TODO statement in the "Experiences" section, could you review this and add what's missing? Thanks, pal.

still to finish implementing first draft description according to agreements perhaps needs a bit of blending with Sven’s solution

@maelstromdat thanks for the contribution. I’m not sure @svenjohann noticed it though.
One thing: It‘d be great to add suggestions as pull-requests especially if you want others to comment. Committing to the master branch also has the disadvantage that formatting issues are immediately populated to the live version of the method guide - which I only noticed while presenting aim42 during a training I gave. ;)

Hello Alex!!
you are right, my bad :) I’ll be more careful for next times, I wanted to commit on my own branch but wasn’t sure whether this was acceptable let’s hope @svenjohann forgives me as well!! ahahahah  btw I’ll commit some more contributions somewhere over the next WE and do pull-request
D.

On 23 Oct 2017, at 23:11, Alexander Heusingfeld<EMAIL_ADDRESS>wrote:
@maelstromdat https://github.com/maelstromdat thanks for the contribution. I’m not sure @svenjohann https://github.com/svenjohann noticed it though.
One thing: It‘d be great to add suggestions as pull-requests especially if you want others to comment. Committing to the master branch also has the disadvantage that formatting issues are immediately populated to the live version of the method guide - which I only noticed while presenting aim42 during a training I gave. ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/aim42/aim42/issues/234#issuecomment-338798063, or mute the thread https://github.com/notifications/unsubscribe-auth/ABzr9zAPUnMFRAVVcC5dwvJg20UaTOlYks5svQESgaJpZM4P1h62.


bsd: Allow IPv6 on NetBSD

Do not exclude IPv6 functionality on NetBSD.

@qbit could you check if it works on OpenBSD?

Builds fine, but I get a lot of ipv6 errors in `make check.

Is this good enough? Or just enable ipv6 only for NetBSD?

Lets just do NetBSD for now - I will poke around and see if I can clean up the OpenBSD stuffs.

I never installed other BSD than NetBSD, so I will leave them to others. All ipv6 tests pass on my OS.
I'm going to rediff the patch and enable ipv6 on NetBSD only.

done!

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/511/

@gibfahn FYI, on macOS, the CI job I just launched yielded No space left on device

@cjihrig sounds like https://github.com/nodejs/build/issues/899, unfortunately only the build infra group have access to the macOS machines at the moment AFAIK.

Ah OK. I thought that included you. Thanks anyway 😄

Apple is using NetBSD code.. however it does not define NetBSD.

@krytarowski Yea, I wasn't worried about the CI failure with regards to this PR. I was just trying to bring attention to it, since it will likely need to be cleaned up.

Landed in https://github.com/libuv/libuv/commit/001a4a11f624153a3f27a7efef9746eb03d519d7. Thanks!


Make otel error log less scary

Description

Setting up OTel requires a specific secret to be created.
This is totally optional, so most of the time this secret won't be there, so logging the error is a bit excessive.
How can this be tested?

Deploy the operator without having the Otel secret setup,and check the log of the operator is less scary

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 58.77%. Comparing base (ddc28a2) to head (21eb287).

Files
Patch %
Lines

pkg/util/dtotel/otel.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3266   +/-   ##
=======================================
  Coverage   58.77%   58.77%
=======================================
  Files         325      325
  Lines       18153    18153
=======================================
  Hits        10669    10669
  Misses       6285     6285
  Partials     1199     1199

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


node_modules in npm package causes some problems

I was getting the error below before delete the node_modules folder under {myproject}\node_modules\angular2-esri4-components...
Was this included in npm by mistake?
This was not happening in the example project though..somehow I'm doing some extra static checking?
The error:
"ERROR in Error encountered resolving symbol values statically. Calling function 'makeDecorator', function calls are not supported."

@derobiom there were some issues with getting this error in an earlier version of this library while working with the Angular CLI.  I believe that it has been corrected though.  I am not getting this error anymore.
If you are still receiving the error can you please provide more information about your project so that I can reproduce the issue?

I tested the npm install again and there are no problems so please disregard.  I think that I may have run npm install again but from a child directory and received another inadvertent "node_modules" folder that did not cause a problem until the production build did the static checking thingy.


chore(main): release 0.3.1

:robot: I have created a release beep boop
0.3.1 (2024-11-06)
Bug Fixes

Always run build workflows (#23) (afd4380)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.3.1
:sunflower:


Try to reduce the number of Remote constuctors

We have tons of them and it makes any related refactoring / improvement painful. Maybe we could reduce their number.

Please assign this one to me.

Please assign this one to me.

I considered this done, do you have anything particular in mind? We can create a separate more specific issue for it

OK, I thought it might be referring to making a more general constructor and then replacing some of the existing constructors with construction functions. It's quite a bit of work and I have half-done it.


T021

Details

Talktorial ID: 021
Title: XXXXXXXXXXXXXXXXXXXXX
Original authors: XXXXXXXXX
Reviewer(s):
Date of review:

Content review

Potential labels or categories (e.g. machine learning, small molecules, online APIs): XXXXXXXX
One line summary: XXXXXXXXXX
[ ] The table of contents reflects the talktorial story-line; order of #, ##, ### headers is correct
[ ] URLs are linked with meaningful words, instead of pasting the URL directly or linking words like here.
[ ] I have spell-checked the notebook
[ ] Images have enough resolution to be rendered with quality, without being too heavy.
[ ] All figures have a description
[ ] Markdown cell content is still in-line with code cell output (whenever results are discussed)
[ ] I have checked that cell outputs are not incredibly long (this applies also to DataFrames)
[ ] Formatting looks correctly on the Sphinx render (bold, italics, figure placing)

Code review

Time it took to execute (approx.):
[ ] Variable and function names follow snake case rules (e.g. a_variable_name vs aVariableName)
[ ] Spacing follows PEP8 (run Black on the code cells if needed)
[ ] Code line are under 99 characters each (run black -l 99)
[ ] Comments are useful and well placed
[ ] There are no unpythonic idioms like for i in range(len(list)) (see slides)
[ ] All 3rd party dependencies are listed at the top of the notebook
[ ] I have marked all code cell with output referenced in markdown cells with the label # TODO: CI
[ ] I have identified potential candidates for a code refactor / useful functions
[ ] All import ... lines are at the top (practice part) cell, ordered by standard library / 3rd party packages / our own (teachopencadd.*)
[ ] I have update the relative paths to absolute paths.
List here unfamiliar libraries you find in the imports and their intended use:

?
What happened here?

No worries, it was discussed in our meeting. No changes are lost :)

All good!


DynamicProgress should take ownership over progressbars

I believe that DynamicProgress should take ownership (unique pointer) to progress bars it consumes.
According to examples user is meant to access progress bars via DynamicProgress instance,
so progress bar object has no use after being added to DynamicProgress.
Current solution forces user to keep progress bar object alive as long as DynamicProgress is alive.
This is a bit of inconvenience.
For example when spawning dynamic set of tasks executed by a thread pool,
where each task creates a progress bar object, it is required to keep this object alive
after task execution, which may be cumbersome.

Agree, std::reference_wrapper<T> is meant to be used as a function parameter to the constructor of std::thread and to functions like std::make_pair and std::invoke. We do not see the STL using it as anything other than a parameter type.
Saving std::reference_wrapper must be dealt with care since it can lead to dangling pointers very easily. For example, if the user saves its Indicator into a vector and does dynamic_progress.push_back(indicators.back()), the next time the vector realloc itself, the reference_wrapper become dangling.

Seems reasonable and makes sense, could you update the README as well @Kicer86? Thanks!

@p-ranav done


Please add an interface around git add -p, git reset -p, and git commit -p

These operations are enormously helpful when crafting a clean repository. The command line dialog for these sub-commands can be a bit arcane. A nice GUI would improve the the workflow tremendously.

Can you elaborate on this?

These -p flag allows users to stage or unstage partial commits. The command line walks the user through their change patch by patch hunk where they can agree to stage, edit or ignore the hunk.

On May 16, 2017, at 3:13 AM, João Moreno<EMAIL_ADDRESS>wrote:
Can you elaborate on this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This is https://github.com/Microsoft/vscode/issues/3563

We have support for partial staging, unstaging and reverting.

Not very discoverable... but still. 👍


docs(getting-started): fix helm command

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 50.99%. Comparing base (d1a7ba6) to head (36d6f14).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #412   +/-   ##
=======================================
  Coverage   50.99%   50.99%
=======================================
  Files          73       73
  Lines        4334     4334
=======================================
  Hits         2210     2210
  Misses       1935     1935
  Partials      189      189

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Issue with Widevine New Version Impacting Existing Offline Persistence License and Ineffectiveness of --disable-component-update in CastLab Electron Version 17

Environment Information:
CastLab Electron Version: 17
Offline Persistence License Downloaded with Widevine Component: 4.10.2557.0
Offline Persistence License Not working New Widevine Component : 4.10.2662.3 and 4.10.2710.0
Offline Persistence License Validation Period : 1 year
Operating System: Windows
Issue Description:
I have encountered a significant problem with the Widevine component in CastLab Electron version 17. It appears that the new version of Widevine is having a detrimental effect on my existing offline persistence license, causing previously accessible content to become inaccessible. Additionally, it seems that the --disable-component-update flag is not effectively preventing updates, which is compounding the issue.
Context:
I have been using CastLab Electron version 17 with an offline persistence license that was downloaded approximately six months ago. Up until now, this setup has been working seamlessly, allowing me to access and play content offline. However, recently, it seems that the Widevine component has been updated to a new version, and as a result, my previously downloaded content is no longer playable.
Specific Issues:
1.Widevine New Version Effect on Existing Persistence License: The new version of Widevine appears to be affecting my existing offline persistence license. As a result, content that was previously accessible offline is no longer functioning. This issue has had a notable impact on my ability to view content that I had expected to be available offline.

Ineffectiveness of the --disable-component-update flag: I attempted to mitigate the issue by using the --disable-component-update flag, with the expectation that it would prevent component updates, including Widevine. However, it seems that this flag is not working as intended, and the Widevine component is still being updated.

Questions:

Is this behaviour with the new Widevine version and offline persistence license expected, or is it possibly a bug or unintended behaviour?

Why is the --disable-component-update flag not effectively preventing component updates, particularly in the case of Widevine?

When the CDM is updated, depending on exactly what changed, all persisted licenses may be invalidated (with major security updates this is always the case). When this happens they will need to be refreshed with the new CDM. Disabling updates is one way to delay this, but once the installed CDM is revoked all bets are off.
I've not had any reports of problems with --disable-component-update (this option is inherited from Chromium), but I'd need to look into it to be sure.. As an alternative the components API we added provides a way to disable updates more directly.

Our primary objective in reaching out to castlabs is to seek information and potential solutions related to the impact of Widevine component updates on existing persistence licenses. Specifically, we are interested in understanding whether there is a way to ensure that Widevine component updates do not adversely affect existing persistence licenses, or if there is a mechanism for updating old persistence licenses without requiring manual intervention.

There is no way to entirely prevent the licenses being invalidated. As you already have been trying to do, a band aid solution is to disable updates entirely to buy some time. This can't be used indefinitely though since the older CDM will be revoked after a large security update, which means it will stop working sooner or later. The timeframe for this is entirely defined by Widevine, and not public information.
What can be done is to implement a scheme to test and update the persisted licenses when a CDM update occurs. This might not be as easy as it sounds though, in part because the EME CDM API is rather rigid and hard to work with, but also since you'd need to maintain the required information to be able to refresh the licenses yourself (e.g CDM session-id mapping, content key identification meta-data (probably in manifest), DRM service configuration, authrorization, and so on). Exactly how to do this would, and what you need, would differ depending on the streaming and/or DRM service in use.
A few approaches have been discussed in several older tickets, but high-level it would generally go something like this:

When a CDM update is detected, loop over all offline content and try to load  (and unload) the matching persisted license.
If a license can't be loaded, mark it for update (or maybe rather the offline content it belongs to, unless the content has expired for a valid reason, of course).
If there is no internet connection, save the list for later and warn the user that the content licenses have expired.
Once a connection is available, loop over the list again and and trigger license requests to refresh them. Make sure to update the CDM session-id mappings for the offline content with the new session.

Using a scheme similar to what is described here could mean that updates can be done without manual intervention assuming the requirements to get a new license is fulfilled. If service authorization has expired though, and can't be automatically refreshed, manual intervention will be required to re-authenticate.
On another note, I see you also mentioned being on ECS 17, which is rather old. Google has recently more strictly started observing their policy to keep CDMs available for years worth of Chromium releases. This means you are well out of the supported window with ECS 17, and you can't be sure to receive CDM updates (or even a CDM at all on a first install, see #169).

Thanks for your detailed response
Any idea, why this is so complex to manage in Windows alone?. We have same application with offline support for Android platform- We havent faced any issues - we do not see any updates on CDM - i guess it happens only via OTA based OS updates which is very rare. In Windows, we see multiple updates and theres no public info on the same and it invalidates the license and causes more issue from end user. Unlike a OTT application where user gets to download a handful of videos, users downloads few hundreds-thousands of videos - educational content in our application and this will become a nightmare if there are frequent updates that invalidates the license.

You are essentially right, browsers on desktop platforms (Windows, macOS and Linux) all use the Widevine Browser CDM (L3), which is not the same as the CDMs used on something line an Android device. Many Android devices even have a L1 CDM, which has a higher security rating since it relies on hardware to protect the keys and media. Typically the browser CDM needs to be updated much more often than the types of CDMs used devices, so this is why the problem is more prevalent for desktop implementations.
Unfortunately this is a necessary evil for Widevine to be able to maintain the security of the Browser CDM. The update schedule used to be public information, but was also made private because of security concerns. DRM is messy, but often a requirement from content owners, so it is something that media playback solutions need to deal with.

Thank you for shedding light on the challenges and possible solutions related to Widevine CDM updates.
I'm curious to understand why there's a difference in the behaviour of the application between Windows and Android environments. It's fascinating to note that the same application on Android, using ExoPlayer, operates seamlessly, while encountering issues in the Windows environment. Could you provide insights into any fundamental distinctions in how Widevine CDM functions on these platforms or any specific technical considerations that might be contributing to this variation? This comparison will be valuable in pinpointing the root cause and resolving the issue, especially given the contrast in performance between the two environments.

I have a specific query related to the identification of differences between the version of Widevine for which a persistence license was downloaded and the current Widevine version. Is there a method or mechanism that allows us to determine whether there is a difference between the two versions? This information is crucial, as it will enable us to inform our users about any potential compatibility issues.

Is there a method or mechanism that allows us to determine whether there is a difference between the two versions?

The only approach I know for sure works is the one I described above, i.e. that after an update you try to load the previously persisted licenses and check the result.
Like I described above you can try to load persisted licenses to make sure they can be loaded after an update, but the CDM does not provide any other means


2.8.4. still fails to install dafny backend on macos

Type: Bug
now on M2 mac air, still doesn't work.  see #246
delete path settings to homebrew dafny
accept extension upgrace
reload
dafny crashes as follows:
[Error - 10:22:52 AM] Connection to server is erroring. Shutting down server.
Failed to load /Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-2.8.4/out/resources/3.9.0/dafny/libhostpolicy.dylib, error: dlopen(/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-2.8.4/out/resources/3.9.0/dafny/libhostpolicy.dylib, 0x0001): tried: '/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-2.8.4/out/resources/3.9.0/dafny/libhostpolicy.dylib' (mach-o file, but is an incompatible architecture (have (x86_64), need (arm64e)))
An error occurred while loading required library libhostpolicy.dylib from [/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-2.8.4/out/resources/3.9.0/dafny/]

Extension version: 2.8.4
VS Code version: Code 1.72.1 (129500ee4c8ab7263461ffe327268ba56b9f210d, 2022-10-10T17:25:13.482Z)
OS version: Darwin x64 21.6.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Apple M2 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_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)
3, 10, 12

Memory (System)
24.00GB (0.11GB free)

Process Argv
--crash-reporter-id cbc8828b-9f0c-43dc-9ec9-540e2195ee37

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
2144e591:30553903
pyindex848:30577860
nodejswelcome1cf:30583748
fc301958:30573243

got the latest IDE  just now, v3.0.3.  Still doesn't work

Failed to load /Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib, error: dlopen(/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib, 0x0001): tried: '/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib' (no such file), '/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64'))
An error occurred while loading required library libhostpolicy.dylib from [/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/]
[Error - 3:28:50 PM] Connection to server got closed. Server will not be restarted.

@keyboardDrummer  weren't we handling arm64 binaries? Could you diagnose what happened?

@kjx could you delete /Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/ and then restart VSCode and open a Dafny file, and inspect the "Output" tab while looking at the "Dafny VSCode" channel, so you see output like the following:
Standalone language server installation started.
deleting previous Dafny installation at /Users/<user>/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github
downloading Dafny from https://github.com/dafny-lang/dafny/releases/download/v3.10.0/dafny-3.10.0-x64-osx-10.14.2.zip
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
extracting Dafny to /Users/<user>/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Standalone language server installation completed.
Language server: {"command":"/usr/local/bin/dotnet","args":["/Users/<user>/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/Dafny.dll","server","--verify-on:Save","--verification-time-limit:20","--cache-verification=0","--cores:7","--notify-ghostness:true","--notify-line-verification-status:false","--warn-shadowing"]}

And then paste that output here?

Hmm. so I tried that. I managed to delete the files OK, but now get a different error popup:

/opt/homebrew/bin/dotnet is not a compatible dotnet file. Dafny requires the ASP.NET Core Runtime 5.0 or 6.0, got Microsoft.AspNetCore.App 7.0.0 [/opt/homebrew/Cellar/dotnet/7.0.100/libexec/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 7.0.0 [/opt/homebrew/Cellar/dotnet/7.0.100/libexec/shared/Microsoft.NETCore.App]

then i installed the binary for botnet 6.-0 but cant find it.
dafny 3.10 <IP_ADDRESS>215 keeps working from the command line...

So I found botnet 6 installed it, set the path, restarted VScode and eventually...
from the Dafny VSCode channel:

Standalone language server installation started.
deleting previous Dafny installation at /Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github
downloading Dafny from https://github.com/dafny-lang/dafny/releases/download/v3.10.0/dafny-3.10.0-x64-osx-10.14.2.zip
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
extracting Dafny to /Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Standalone language server installation completed.
Language server: {"command":"/usr/local/share/dotnet/dotnet","args":["/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/Dafny.dll","server","--verify-on:Save","--verification-time-limit:10","--cache-verification=0","--cores:8","--notify-ghostness:true","--notify-line-verification-status:true","--verifier:vcscores=8"]}

Meanwhile the Dafny Language Server Channel

[Error - 5:54:51 AM] Connection to server is erroring. Shutting down server.
Failed to load /Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib, error: dlopen(/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib, 0x0001): tried: '/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib' (no such file), '/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/libhostpolicy.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64'))
An error occurred while loading required library libhostpolicy.dylib from [/Users/kjx/.vscode/extensions/dafny-lang.ide-vscode-3.0.3/out/resources/3.10.0/github/dafny/]

soL then I delete the botnet 6 path,  point at the home-brew dafny, and al goes fine


Update admin_generator for Django 1.9. Fix #784

Fixes the error where it expects an app name but gets the module instance.
LookupError: No installed app with label '<module 'my_app.models' from '/path/to/my_app/models.py'>'.

Could you please fix the test errors ?
(Sorry for the inconvenience since one other test is also failing)
Also if you could please add a test case for this ?

Ah yes I was sick and then totally forgot about this.

Think we already have another fix for this which still allows running the command without any arguments.
If this didn't solve the issue please open a new PR.


Make HeatMap more general

The HeatMap Element has gone through a lot of redesign, initially being defined as a Raster type and then allowing columnar data. This PR refactors HeatMap to improve the simplify aggregation step and allow any number of value dimensions which can appear as hover information in bokeh. Still a WIP and I need to ensure the code is backward compatible (it should be).

@jlstevens The PR is now ready for review, I'll rebuild the test data shortly. The test data will have to be updated because HeatMap no longer pads with NaN values in the constructor, instead it computes a 2D gridded aggregate, which is used for display. I've also readded the previously supported raster as a property so it can go through a deprecation cycle. Representing the HeatMap as a gridded aggregate is much more flexible since it allows multiple value dimensions.

Still need to add thorough unit tests for the aggregation. I'm also now wondering whether I should add a warning when you pass non-aggregated data to a HeatMap, i.e. if you had two clashing values for the same 2D index, e.g. there are two different values for index ('A', 'a') in the heatmap, it would just silently ignore the second value. Really it should warn you that you should aggregate your data using some function (mean, max, min) before passing it to the HeatMap.

Also deprecates support for unpickling the original HeatMap format (which was replaced in 1.4).

Ok, I've made my comments for now (and you have already replied to most of them). The biggest suggestion is that get_2d_aggregate might be better expressed as an operation (if that makes sense).

The biggest suggestion is that get_2d_aggregate might be better expressed as an operation (if that makes sense).

Yes, get_2d_aggregate is basically a fairly crude approximation of datashader aggregation for categorical key dimensions (i.e. 2D aggregation without the binning).

@jlstevens Once tests are passing this is ready for a second review and then merge.

@jlstevens Tests now passing on the PR build.

I made three more comments for you to reply to. Otherwise looks good and I expect this will be merged very soon!

Latest comments addressed, ready to merge when tests pass.

Tests passed. Merging!


Deposit Untrusted Assets

Description
Allow wallet users to deposit off-chain assets to anchors without a trustline.

[X] “Add Asset” button enters the issuer/home domain but skips adding trust to said asset .
[X] Add an “Add Trust” button that allows users to add trustline explicitly.
[X] Claiming balances from those assets adds trustline to account (one time) to claim.
[X] Added and untrusted assets in Balances can only be add a trustline and Deposit to a claimable balance supported anchor
[X] When Asset is added Trust Asset button appears when asset is trusted it is not and we see the typical Send Deposit Withdraw buttons.

Addresses issue: #64
Type of change

[X] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Deposit Untrusted Asset

yarn install yarn start
go to http://localhost:3333/
Create Account
Add Asset

asset code: SRT home domain: https://testanchor.stellar.org/
You should see this in your Balances

 SRT:
 0.0000000
 TrustAsset Deposit

Attempt a deposit with the deployed testanchor

You can insert any dummy information
The Deposit may error out at this time due to some high DEX traffic

If Deposit is successful you should see that amount deposited in your Claimable Balances
Attempt to claim your claimable balance

The claim may error out at this time due to some high DEX traffic

If successful your Balance should look like SRT:
 10.0000000
 Send Deposit Withdraw

Trust Asset

yarn install yarn start
go to http://localhost:3333/
Create Account
Add Asset

asset code: SRT home domain: https://testanchor.stellar.org/
You should see this in your Balances

 SRT:
 0.0000000
 Trust Asset Deposit

Attempt to trust asset

Adding trustline may error out at this time due to some high DEX traffic

If successful your Balance should look like SRT:
 0.0000000
 Send Deposit Withdraw

Claimable Balance Untrusted Asset (From Fresh State)

yarn install yarn start
go to http://localhost:3333/
Create Account
Add Asset

asset code: SRT home domain: https://testanchor.stellar.org/
You should see this in your Balances

 SRT:
 0.0000000
 Trust Asset Deposit

Attempt a deposit with the deployed testanchor

You can insert any dummy information
The Deposit may error out at this time due to some high DEX traffic

If Deposit is successful you should see that amount deposited in your Claimable Balances
Save Secret Key and sign out and sign in (removing your state on storage)
Verify claimable balance is still present but Balances will only include assets that are trusted (XLM etc)
Attempt to claim your claimable balance

The claim may error out at this time due to some high DEX traffic

If successful your Balance should look like SRT:
 10.0000000
 Send Deposit Withdraw

Recent Changes

Change BALANCE[keystore] to only include untrusted assets

Now called UNTRUSTEDASSETS[keystore]

Refactor balanceDisplay to pull from both  UntrustedAssets and account.state.balances

NOTE: Balance interface used for UntrustedAssets entries needs a flag (untrusted: boolean) to indicate whether or not it's trusted during balanceDisplay's balanceRow mapping.

Port LoadAccount's secret key(prompt) logic to updateAccount

Deleted LoadAccount and only call updateAccount

Recent Changes

Change BALANCE[keystore] to only include untrusted assets

Now called UNTRUSTEDASSETS[keystore]

Refactor balanceDisplay to pull from both  UntrustedAssets and account.state.balances

NOTE: Balance interface used for UntrustedAssets entries needs a flag (untrusted: boolean) to indicate whether or not it's trusted during balanceDisplay's balanceRow mapping.

Port LoadAccount's secret key(prompt) logic to updateAccount

Deleted LoadAccount and only call updateAccount


Attempt to download rfcxxxx state ... error

A run of idnits with the latest version results in the following error for all RFC cited in the draft. In this case it was being run against draft-ietf-idr-bgp-model-15.txt
Attempted to download rfc8277 state...
The downloaded file seems to be corrupt, proceeding with outdated information.
Removing the .idnits directory in home does not help.

I get the same output of the above command. So do not know what is happening. Here is some more info.
Version check.
$ ../idnits/idnits --version
idnits	2.17.1

Non-debug run after removing .idnits folder in home directory.
   Attempted to download rfc0000 state...
   Failure fetching the file, proceeding without it.
   Attempted to download rfc159 state...
   Failure fetching the file, proceeding without it.
   Attempted to download rfc201 state...
   Failure fetching the file, proceeding without it.
   Attempted to download rfc428 state...
   Failure fetching the file, proceeding without it.
   Attempted to download rfc5800 state...
   Failure fetching the file, proceeding without it.
   Attempted to download rfc665 state...
   Failure fetching the file, proceeding without it.

Debug run after removing the .idnits folder in home directory. The problem seems to be with some specific RFCs.
+ for ref in '$rfcrefs'
echo $ref | tr -d "\r"
++ echo 201
++ tr -d '\r'
+ ref=201
+ name=rfc201
+ num=201
+ '[' '!' rfc201 = rfc ']'
+ download 'rfc201 state' https://datatracker.ietf.org/doc/rfc201/idnits2-state/ /Users/mahesh/.idnits/rfc201.state 'Doc-rfcnum: 201'
+ name='rfc201 state'
+ url=https://datatracker.ietf.org/doc/rfc201/idnits2-state/
+ file=/Users/mahesh/.idnits/rfc201.state
+ test='Doc-rfcnum: 201'
+ cd /Users/mahesh/.idnits
+ '[' /Users/mahesh/.idnits/rfc201.state ']'
$FDATE $file.date 2>/dev/null
++ stat -f %Sm -t %Y-%m-%d /Users/mahesh/.idnits/rfc201.state.date
+ filedate=
tmpfile
++ tmpfile
basename $0
+++ basename ../idnits/idnits
++ prefix=idnits
++ for tmpdir in '$TMPDIR' '$TMP' '$TEMP' /tmp .
++ '[' -d /var/folders/gl/sn4vgdl1119900k_2gn21ps0000ghf/T/ -a -w /var/folders/gl/sn4vgdl1119900k_2gn21ps0000ghf/T/ ']'
++ tmpfn=/var/folders/gl/sn4vgdl1119900k_2gn21ps0000ghf/T//idnits-57611.tmp
++ '[' -f /var/folders/gl/sn4vgdl1119900k_2gn21ps0000ghf/T//idnits-57611.tmp ']'
++ rm /var/folders/gl/sn4vgdl1119900k_2gn21ps0000ghf/T//idnits-57611.tmp
++ echo /var/folders/gl/sn4vgdl1119900k_2gn21ps0000ghf/T//idnits-57611.tmp
++ exit
+ tempfile=/var/folders/gl/sn4vgdl1119900k_2gn21ps0000ghf/T//idnits-57611.tmp
+ debug 'Status file /Users/mahesh/.idnits/rfc201.state is dated .'
+ '[' '' ']'
+ '[' '' = 2023-01-19 ']'
+ note ''
+ '[' '' ']'
+ '[' -f /Users/mahesh/.idnits/rfc201.state ']'
+ note ' - No rfc201 state file. Attempting to download it...'
+ '[' '' ']'
+ /usr/local/bin/wget --timeout=2 -q -O - https://datatracker.ietf.org/doc/rfc201/idnits2-state/
+ '[' -z '' ']'
+ '[' '' ']'
+ echo '   Attempted to download rfc201 state...'
   Attempted to download rfc201 state...
+ echo '   Failure fetching the file, proceeding without it.'
   Failure fetching the file, proceeding without it.
+ touch /Users/mahesh/.idnits/rfc201.state.date

The failure at rfc201 is expected - there is no state to give you for that RFC. Same for all in the list you show in the above comment.
See, e.g., https://www.rfc-editor.org/info/rfc201
When you reran this, though, you didn't get the following that you originally reported? If there's an issue to fix here, that's the exercise point to focus on.
Attempted to download rfc8277 state...
The downloaded file seems to be corrupt, proceeding with outdated information.

If you didn't, and the only complaints you see are for the 6 you listed above, this is expected, and you should close the issue.

Hi @rjsparks, we could be dealing with two different issues here.
The first one being the six RFCs that have no state information. I know my document does not reference RFC201, so not sure why it is being downloaded. I can close it, but idnits will continue to give these errors unless either we do not download them, or have some dummy download file with them.
To the second error about file being corrupt, I have seen that error more than once. It was probably not in the last run. I can keep an eye out, but suspect the bug to be transient. Could it be the datatracker is not able to keep up with all the requests coming at it?

The first one being the six RFCs that have no state information. I know my document does not reference RFC201, so not sure why it is being downloaded. I can close it, but idnits will continue to give these errors unless either we do not download them, or have some dummy download file for them.

Yes - we have no plan to change that for this implementation of idnits. We will look to make the next re-implementation behave differently.

Could it be the datatracker is not able to keep up with all the requests coming at it?

We have no indication of the datatracker not being able to keep up, but the script is running as an anonymous user and has a short timeout (2), so there's a chance that if cloudflare  (or the datatracker if the edge closest to you doesn't have the document in cache) isn't responsive in that short timeout that you could be running into issues.


Cosmetics and #10

Here's an alternative to #10 and #9.

Cool, that gets rid of those issues.

Just one question, don't we want to import sys as _sys?


UHF-10969: Remove leading/trailing spaces

UHF-10969

What was done

Added an update hook to remove non-breaking spaces, any leading or trailing %20 and spaces from link urls.

How to install

Make sure your instance is up and running on latest dev branch.

git pull origin dev
make fresh

Update the Helfi API Base

composer require drupal/helfi_platform_config:dev-UHF-10969

Run make drush-cr

How to test

[ ] Create a page with a set of broken links (ask @khalima or AI for a list of links with leading/trailing spaces, non-breaking spaces and %20.
[ ] Copy the links to any text field in any entity and save the entity
[ ] Verify that the links are broken by opening the entity in a browser window
[ ] Run make drush-updb drush-cr
[ ] Refresh the browser window and check that the links have been trimmed.
[ ] Check that code follows our standards

Other PRs

https://github.com/City-of-Helsinki/drupal-helfi-platform-config/pull/854
https://github.com/City-of-Helsinki/drupal-module-helfi-tpr/pull/174

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.07%. Comparing base (d5d46f3) to head (9576a0e).
Report is 13 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #191      +/-   ##
============================================
- Coverage     89.14%   89.07%   -0.07%
- Complexity      523      527       +4
============================================
  Files            78       79       +1
  Lines          2091     2106      +15
============================================
+ Hits           1864     1876      +12
- Misses          227      230       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


"start" vs "continue" and the "ui-break-done" event

I have a question about the use of the "ui-break-done" event.  This seems to be configured to fire 50ms after any of the launch configurations have completed "loading".  When this fires the "exec-run" command is executed.  However, I noticed that the attach configuration which utilizes the "exec-continue" doesn't behave in this same way.  The attach configurations wait to receive the "configurationDoneRequest" prior to executing the "exec-continue" command.  I'm curious why the launch commands don't behave in the same way, waiting for the configuration to complete prior to executing the "exec-run" command.
It seems by using this arbitrary timeout to delay the "exec-run" command, it may result in not waiting for all of the configuration to have completed prior to starting execution.  There are a number of open issues complaining about not hitting breakpoints set in the UI, and I wonder if this might potentially be the cause...if execution starts prior to the configuration completing.
I was recently experimenting with adding a breakpoint as part of the "configurationDoneRequest", but noticed that execution had started prior to my breakpoint command having been sent, which led me down this path to understand how the launch configurations trigger the execution of the "exec-run" command.
Is there a reason that this delay is used or should the correct behavior be similar to that for the continue which waits until the configuration has completed prior to beginning execution?

that's some of the earliest code of this extension, the timeout was inserted probably to make sure, that the UI only calls commands on a valid initialized miDebugger instance. The event is just for the UI to switch into the "debugging is running" view, telling the user that they may now start issuing debug commands, it should not call any commands by itself. The debug host (vscode) may call debug methods on this event though.
50ms is just a nice length for a lot of work to be done, while looking to the user like it is almost instant (in UI design typically operations should not take longer than 100ms to be perceived as instant)

Hi @WebFreak001, thanks for the follow-up.
I may be misunderstanding something, but it appears to me that the "ui-break-done" event is only used by the extension.  From my investigation, it is emitted in all of the "launch" scenarios, but there appears to only be a single listener, as shown here, which is where the "exec-run" command is sent.  That is why it appears to me that the "exec-run" is sent 50ms after "loading" completes, irregardless of whether the UI has finished initializing all of the breakpoints.  In other words, there appears to be a race condition between when the "exec-run" is issued and when the breakpoint configuration completes.
Evidence of this seems to show up in at least issue #260.  I looked through the logs provided in that issue and it appears that in cases where the breakpoints don't appear to be hit, the "exec-run" is issued prior to the breakpoint having been set (i.e., inferring "exec-run" from those logs based on the "Running executable" text in the output in relationship to "token:5" where the breakpoint is set).  I noticed similar behavior in my own experimentation where "exec-run" was being issued too early, and that is what led me down this path.  Just re-running the same scenario I could get instances where sometimes the breakpoint was set before the "exec-run" was issued, and sometimes afterwards, thus it seems pretty easy for this to happen.
Comparing the "launch" to the "attach", it appears the "attach" does not use this same behavior (i.e., timer) to kick off the "exec-continue", and in fact waits for the "configurationDoneRequest" to be sent prior to issuing that command, as shown here.  So, if nothing else there appears to be an inconsistency between how "exec-run" is handled versus how "exec-continue" is handled.  My guess is that the "exec-run" likely should not be issued until the "configurationDoneRequest" is received, similar to how the "exec-continue" is handled.

oh given that FIXME comment I might have implemented that as a workaround because some stuff didn't work. But if it works now, feel free to adjust the initialization behavior to be more correct and not use timers.

Ok, that makes sense.  Yes, I had noticed that FIXME in the past and was a bit curious about it.  I think I looked at one time and it had been added years ago.  The "configurationDoneRequest" does seem to work fine for me, and is essential for continuing execution for the "attach" configurations, so I think it is safe to use for the "launch" configurations as well.  I'll work on a PR request to remove the timer approach and model it after how the "exec-continue" behaves.

If so the #260 could be closed by the meantime. Thanks @brownts !

@jgueytat Did you already verified of #260 is actually fixed after applying those changes?

fixed by #304

Hi guys the #260 seems to work properly now. But I am enable to test it on Gitpod. :(

For the #260 on Gitpod with the version v0.25.1 I still get the warning and no breakpoint.
warning: Error disabling address space randomization: Operation not permitted

With VSCode and WSL and the exact same configuration. It seems I get the breakpoint properly.

Hi @jgueytat, I'm a little confused.  Did you test this with the latest from this repository or with v0.25.1?  The reason I ask is because, from the comments above, it appears you were testing with the previously released version and this fix would not have been incorporated into that version.  This fix will be in an upcoming release which has not yet occurred.  Is it possible for you to test with the latest in this repository?

I don't know yet how to compile and test a plugin. That beeing said I would find really cool to develop the plugin in Gitpod itself. ;) I'll give that a try.


bevy_reflect: ignored fields are not ignored by FromReflect

bevy version:  main as of 1bd33ca
When deriving FromReflect on tuple structs, the field index of fields declared after a field marked with #[reflect(ignore)] are not as one would expect them.
Here is an example:
#[derive(Reflect, FromReflect)]
struct Foo(
  u32, // :0
  #[reflect(ignore)]
  f32, // :1
  String, // :2
);

let mut tuple_struct = DynamicTupleStruct::default();
tuple_struct.set_name("Foo".to_owned());
tuple_struct.insert(22_u32);
tuple_struct.insert(3432423234234_i128);
tuple_struct.insert("hello world".to_owned());

let foo = Foo::from_reflect(&tuple_struct).unwrap();

println!(
    "tuple_struct\n[0]: {:?}\n[1]: {:?}\n[2]: {:?}\n",
    tuple_struct.field(0),
    tuple_struct.field(1),
    tuple_struct.field(2),
);
println!(
    "foo\n[0]: {:?}\n[1]: {:?}\n[2]: {:?}\n",
    foo.field(0),
    foo.field(1),
    foo.field(2).
);

Prints the following:
tuple_struct
[0]: Some(22)
[1]: Some(3432423234234)
[2]: Some("hello world")

foo
[0]: Some(22)
[1]: Some("hello world")
[2]: None

The unexpected behavior is here:
let mut tuple_struct = DynamicTupleStruct::default();
tuple_struct.set_name("Foo".to_owned());
tuple_struct.insert(22_u32);
// vvv required, otherwise Foo::from_reflect returns None
tuple_struct.insert(3432423234234_i128);
tuple_struct.insert("hello world".to_owned());

let foo = Foo::from_reflect(&tuple_struct).unwrap();

You'd expect to be able to build Foo from a DynamicTupleStruct with exactly two fields, not three. The correct behavior would be to account for it in the FromReflect implementation.

This affects everything actually, not just FromReflect. Calling TupleStruct::field_at will have a similar problem.
So this more generally relates to the behavior of field indices on structs with ignored fields as a whole.

Calling TupleStruct::field_at will have a similar problem.

The sample example demonstrates it's not the case. In the following code .field is the method on the TupleStruct trait
println!(
    "foo\n[0]: {:?}\n[1]: {:?}\n[2]: {:?}\n",
    foo.field(0),
    foo.field(1),
    foo.field(2).
);

Calling TupleStruct::field_at will have a similar problem.

The sample example demonstrates it's not the case. In the following code .field is the method on the TupleStruct trait

println!(

    "foo\n[0]: {:?}\n[1]: {:?}\n[2]: {:?}\n",

    foo.field(0),

    foo.field(1),

    foo.field(2).

);

The output shown in the issue post demonstrates it works as expected.

This should print:
foo
[0]: Some(22)
[1]: Some("hello world")
[2]: None

Which correctly ignores the field at index 1.
The issue I was generalizing this to is regarding whether the reflected index should be the same as the declaration index or not.
A user could take this info and try to edit a non-reflected instance to confusing results.
We could simply disregard those instances and say, "Don't rely on reflection outside of reflection." That's a totally fair stance I think haha, but we could also consider adding a method to convert reflected indices to declaration indices:
foo.decl_index(1); // Some(2)

Or, as suggested by others, print a warning if the ignored fields don't come last.
Just wanted to possibly open this up to other solutions if that's what we want to look into. If not, then solving it at least for FromReflect is good enough.

Thinking on this a bit, I feel like a good start would be to implement the warning system. Making sure users know to put these fields last, will help protect them from running into this issue in the first place.
With that as a temporary[^1] fix, we can begin to explore other ways of dealing with this problem.
[^1]: Possibly not temporary depending on if a better solution can't be found

Actually, it might not be possible to emit a warning since that API is still unstable. We could maybe consider making this a full on error.
It might make sense considering we don't actually support deserializing tuple structs with a #[reflect(skip_serializing)] marker anywhere but the end. Otherwise, it fails to deserialize and we end up with the warning:
WARN bevy_asset::asset_server: encountered an error while loading an asset: Expected integer

Or worse, it ends up putting a value into the skipped field anyways 😬.
Alternatively, we could print a warning only when (de)serializing or calling FromReflect (or whatever else breaks because of this) to let the user know that things might not work correctly. However, if a third-party crate doesn't test that their reflected types serialize properly or that it doesn't use FromReflect properly, then consumers of that crate won't be able to correct the behavior themselves (not without forking or creating a PR at least).
This would require us adding some sort of API to check if there are any misplaced ignores/skips, though, since we don't always have the registry (i.e. in FromReflect) to get that info from type data (which is where we at least store skip_serializing info).

I think we should go with the compile error (I wish we could do compile warnings). However, I understand and am open to the second option of just printing a warning during (de)serialization/FromReflect. I just think we should prevent this incorrect behavior for everything rather than just rely on warnings being conditionally printed out (and the first option is also just a lot simpler/cleaner to implement). Any other thoughts?


Hondsrug example throws ValidationErrors

In GitLab by @JoerivanEngelen on Oct 26, 2023, 16:02
To reproduce change in:
https://deltares.gitlab.io/imod/imod-python/examples/mf6/hondsrug.html
simulation.write(modeldir, binary=False, validate=False)

To:
simulation.write(modeldir, binary=False, validate=True)

This throws:
ValidationError:  model:
	* dis package:
		* top:
			* not all values comply with criterion: > bottom
		* idomain:
			* 6 disconnected areas detected in model domain

The issues here:

top: In cells where idomain = -1, the thickness of cells is zero. Modflow 6 accepts this, but we do not ignore idomain = -1.
idomain: The ActiveCellsConnectedSchema only looks for idomain > 0, but this ignores that idomain = -1 also connects cells to each other.

In GitLab by @JoerivanEngelen on Oct 26, 2023, 16:32
created branch 608-hondsrug-example-throws-validationerrors to address this issue


[TC-0066] (pt2) pipeline config for running tests

dynamically setting the ENV variable when running make build-test or make build-local
If ENV=ci the frontend builds with the cypress base image

Changing branch name to link to Jira


Test

:pushpin: Commit 1e0b364 has been approved by kteza1

@bill1gates r+

:hourglass: Testing commit 1e0b364 with merge 1e0b364...


[Bug - next-pwa]: Not working

Provide environment information
There are no install icon came out on the address bar
Link to reproduction - Issues with a link to complete (but minimal) reproduction code help us address them faster
Just install the package and followed the steps
To reproduce
Here is the next.config.js
/** @type {import('next').NextConfig} */

const withPWA = require("@ducanh2912/next-pwa").default({
  dest: "public",
});

const nextConfig = {
  experimental: {
    appDir: true,
  },
  env: {
    BASE_URL: process.env.BASE_URL
  }
}

module.exports = withPWA(nextConfig)

Describe the bug
PWA install icon not showing
Expected behavior
Should show install icon
Screenshots (if relevant)

Additional information (if relevant)
No response
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T8101
Binaries:
  Node: 18.16.0
  npm: 9.5.1
  Yarn: 1.22.19
  pnpm: N/A
Relevant packages:
  next: 13.4.4
  eslint-config-next: 13.4.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.0.4

warn  - Latest canary version not detected, detected: "13.4.4", newest: "13.4.5".
Please try the latest canary version (npm install next@canary) to confirm the issue still exists before creating a new issue.
Read more - https://nextjs.org/docs/messages/opening-an-issue

I can't reproduce with our examples/basic (which is a just barebone Next.js app) on Chromium 114.0.5735.106:

Thanks for providing an example @DuCanhGH , will diagnose more and see which causes the problem :)

Service worker was installed and running, but still the installation button is not showing.

Just got solve the problem, it needs a manifest.json which is not added on the documentation, only if next version 9 below. but seeing the example, which has manifest.json which is I guess needed to be on the project even on higher version.
Now it works fine now :)

@allestaire yeah you need to have manifest.json to have that, I thought your problem was that the service worker wasn't properly installed.
I did mention adding manifest.json in next-pwa's Getting started section though!

@allestaire yeah you need to have manifest.json to have that, I thought your problem was that the service worker wasn't properly installed.
I did mention adding manifest.json in next-pwa's Getting started section though!

Sorry for that,
I see it on the repo on Step 2.
But on the documentation itself it is place on below next9 version,
So Im guessing that on next 9 above there will be no need of manifest.json

@allestaire yeah that sounds like a weird confusion. It's nice that you have figured the issue out!

Thank you for your fast response 😄


 To do so, edit the top post and then comment after this one so I can check back.
Closing in the meantime, because a number of people never report back and it’s useless to keep the issue open in that case and without all the required information.

Updated post. I am also seeing this exact same problem on a different Mac. If you want the brew cask doctor output from that one as well, let me know.

I’m guessing the uninstall script may no longer exist. Try file '/opt/homebrew-cask/Caskroom/crashplan/4.4.1/Uninstall.app/Contents/Resources/uninstall.sh' to see if it does.

Updated CrashPlan to 4.5.0, and the uninstall script is here if you need it.
@vitorgalvao The script is in the same location (Uninstall.app/Contents/Resources/uninstall.sh)

The problem comes because it's looking for $appSupportDir/install.vars -> /Library/Application Support/CrashPlan/install.vars and it doesn't find it, I think.

@adityadalal924 Looks like you’re right.
Going through the gist you posted and working back from that variable, we eventually get to the problem: they have an hardcoded path.
Added to https://github.com/caskroom/homebrew-cask/issues/12858, which falls under changes for #13201.
@fuzzy76 For now, to fix this, please edit /opt/homebrew-cask/Caskroom/crashplan/4.4.1/Uninstall.app/Contents/Resources/uninstall.sh and change that line to appDir="/opt/homebrew-cask/Caskroom/crashplan/4.4.1/Uninstall.app".

Thanks :)

Thanks :)


Manuel Vazquez Peer Review

Hi team,
Great job so far. I enjoyed reviewing your graphs and learned about durations in PE policy, something I never really thought about in the past. Here is some feedback:
Strengths

I thought you did great in preparing your datasets and joining multiple data pieces

You ordered your graph nicely by mean and included error bars with mark up was cool. Good to see operationalization of some concepts we learned in class.

The interactive piece is cool

Areas of improvement

Some parts of the code didn't merge for me because of numeric/character mismatch. Had to make an edit update

The graph that plots grad rates by region and PE policy is a little busy and hard to find a key takeaway. Consider simplifying a little. I could see a few different ways: removing region, or perhaps remove states from Y axis and plot PE policy? Right now, it is hard to see any relationship between PE policy and grad rates. Simplifying might work well because you will have the interactive piece.

@datalorax

Nice review, Manuel! I really appreciate the code edits as well.


Font Size does not properly scale on Windows

Describe the bug
Fonts don't scale properly on HIDPI screens on Windows.
To Reproduce

Set display scaling to a high percentage in Windows Settings.
Run CSharpMath.Forms.Example.UWP
Go to Even more tab and note the text size is quite small

For example compare 300% scaling:

To 100% scaling:

Expected behavior
The font should get larger, not smaller at higher scale (similarly to the tab text, as you can see in the screenshots.
Environment (please complete the following information):

Platform: CSharpMath.SkiaSharp
Package Version or Commit: latest
Device: Windows 10

Probably related to #136.

Should be fixed in latest commit. Try the nightly packages!

Will check!

Tested on latest master and it works great 👌 . Closing!


Weird behavior with #@press when triggering another command at the same time

I have the following in input.conf:
s      script-binding uosc/subtitles    #! Subtitles
TAB    script-binding uosc/toggle-ui    #@press
TAB    script-binding uosc/toggle-ui    #@release

If I keep pressing TAB and then press s (without releasing TAB), then press either s again or ESC to close uosc/subtitles window and finally release TAB, then everything is inverted: uosc ui is permanently displayed and is hidden if I keep TAB pressed.
Expected behavior in this case: when releasing TAB, uosc UI isn't displayed because TAB isn't pressed.
It also occurs when triggering other commands like script-binding quality_menu/audio_formats_toggle or script-binding quality_menu/video_formats_toggle.
Video of the issue, although the keys I'm pressing aren't displayed on the screen so it's not very useful:
https://user-images.githubusercontent.com/78810647/212176370-98c5a729-16c5-450c-bfbb-63d016009db1.mp4
Thoughts?

Use set-min-visibility instead to toggle-ui.
https://github.com/tomasklaen/uosc/issues/317
script-message-to uosc set-min-visibility 1 #@press
script-message-to uosc set-min-visibility 0 #@release


Miniforge

Consider adding support for miniforge. It's a conda installer similar to miniconda, but it's developed by the community and has conda-forge as the default channel. Some people might still want to use the usual miniconda installation, so we should make it possible to choose (probably with miniconda being the default).
This idea was originally brought up by @jiawen in https://github.com/spietras/rules_conda/issues/2#issuecomment-962496775

Thanks for opening the new issue! I just poked around conda.bzl and it looks reasonably straightforward to add miniforge as another target.
If you haven't already started, I can probably find some cycles to give this a shot in a week or two.

If you are willing to try then sure, take a shot. Just keep in mind that #2 might change things up a little bit.


Angular 10 and Nativescript 7 app crashes on iOS

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

CLI: ns 7.0.8
Plugin(s):

"dependencies": {
    "@angular/animations": "~10.1.2",
    "@angular/common": "~10.1.2",
    "@angular/compiler": "~10.1.2",
    "@angular/core": "~10.1.2",
    "@angular/forms": "~10.1.2",
    "@angular/platform-browser": "~10.1.2",
    "@angular/platform-browser-dynamic": "~10.1.2",
    "@angular/router": "~10.1.2",
    "@danvick/ngx-translate-nativescript-loader": "^2.0.0",
    "@nativescript/angular": "~10.1.0",
    "@nativescript/core": "~7.0.0",
    "@nativescript/firebase": "^11.0.0-rc.8",
    "@nativescript/theme": "~2.5.0",
    "@ngrx/effects": "^7.2.0",
    "@ngrx/entity": "^7.2.0",
    "@ngrx/store": "^7.2.0",
    "@ngrx/store-devtools": "^7.2.0",
    "@ngx-translate/core": "^11.0.1",
    "apkup": "^1.2.0",
    "nativescript-appversion": "^1.4.1",
    "nativescript-barcodescanner": "^3.4.1",
    "nativescript-fancyalert": "^3.0.6",
    "nativescript-feedback": "^1.3.7",
    "nativescript-geolocation": "^5.1.0",
    "nativescript-google-places-autocomplete-last-version": "^1.0.4",
    "nativescript-iqkeyboardmanager": "^1.5.1",
    "nativescript-open-app": "^0.2.0",
    "nativescript-phone": "^1.4.0",
    "nativescript-theme-core": "~1.0.4",
    "nativescript-ui-listview": "^9.0.2",
    "nativescript-ui-sidedrawer": "^9.0.3",
    "nativescript-vibrate": "^4.0.1",
    "ngrx-store-freeze": "^0.2.4",
    "reflect-metadata": "~0.1.12",
    "rxjs": "~6.6.0",
    "tslib": "^2.0.0",
    "zone.js": "~0.10.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.1001.2",
    "@angular/cli": "~10.1.2",
    "@angular/compiler-cli": "~10.1.2",
    "@nativescript/android": "7.0.0",
    "@nativescript/ios": "7.0.0",
    "@nativescript/schematics": "^10.1.0",
    "@nativescript/tslint-rules": "~0.0.5",
    "@nativescript/webpack": "~3.0.0",
    "@types/jasmine": "~3.5.0",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "^12.12.62",
    "codelyzer": "^6.0.0",
    "ghooks": "^2.0.4",
    "jasmine-core": "~3.6.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~5.0.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage-istanbul-reporter": "~3.0.2",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "protractor": "~7.0.0",
    "ts-node": "~8.3.0",
    "tslint": "~6.1.0",
    "typescript": "~4.0.2"
  },

NativeScript-Angular:
Angular: 10

Describe the bug
When I build on emulator, and device it works. When I build for device and open on device it open and close fast
here is video: https://streamable.com/u4dym2
To Reproduce
This commad is used to create build:
tns build ios --bundle --env.environment="prod" --env.uglify --env.aot --clean --release --for-device --provision YOUR PROVISIONING PROFILE
I tried this with brend new app same thing
New project generated with:
ng new --collection=@nativescript/schematics my-shared-app --shared
I tried with ns as well
When I do run on emulator like this:
tns run ios --bundle --env.environment="prod" --env.uglify --env.aot --clean it works
So I guess it is some bug with this part:  --release --for-device
Expected behavior
Sample project
App should work as it working on emulator

Look through your plugins, I see some referring to version that are not compatible with NS 7 - I would suggest at least these changes:
"nativescript-appversion": "^1.4.1" -> "@nativescript/appversion": "~2.0.0",

"nativescript-theme-core": "~1.0.4" -> "@nativescript/theme": "~3.0.0",

"nativescript-barcodescanner": "^3.4.1" -> "nativescript-barcodescanner": "~4.0.0",

"nativescript-iqkeyboardmanager": "^1.5.1" -> "@nativescript/iqkeyboardmanager": "~2.0.0",

(and fixing the places where they are used as well).
Not that this should work in a simulator, it just seems a bit odd that you can run the NS7 project with these old plugin versions, so I would start by updating them (and check the remaining ones, too).


The import fails using sugarss syntax

The syntax sugarss which could be the sass for postcss and still being developed by @ai
Is using a syntax similar to sass and gets rid of semicolons. Which is an issue with this plugin since the parser looks for semicolons and won't import the file if there's one missing.
Opened an issue on sugarss repo which leads me here
https://github.com/postcss/sugarss/issues/13#event-588554352
I think that this plugin is more encline to be the one to be compatible with sugarss since using precss with it makes a lot of sense and it's even stated on the syntax project readme.
https://github.com/postcss/sugarss/
The two other plugins which could handle this are https://github.com/postcss/postcss-import by @MoOx and https://github.com/trysound/postcss-easy-import by @TrySound. In this case I think the later makes more sense if it couldn't be supported by this plugin.
Falling back to .css files for now :)

@esiao First of all stop using cssnext (which is deprecated) in favour of postcss-cssnext.

@TrySound it's the case I just don't include it in the plugin name
var cssnext = require('postcss-cssnext');

@esiao {compress:true} doesn't exist in postcss-cssnext. Which version of postcss-import did you try?

@TrySound I made my tests using it like this :
var plugins = [
precss(), || atImport(), || atEasyImport({prefix: false, extensions: ['.sss'], glob: false})
// short(),
// cssnext({compress:true}),
// lost(),
// calc(),
// reporter()
];
For the versions :
"postcss-import": "^8.0.2"
"postcss-easy-import": "^1.0.1",
"precss": "^1.4.0"

if precss use partial-import first, using others plugins for this is useless, use those first.

To clarify for everyone, this is exactly what I did.
I first tried using only precss. It didn't work as expected with the missing semicolon error.
I then tried using postcss-import, didn't work too because of the missing semicolon warning.
And lastly tried postcss-easy-import which did fail too because of the missing semicolon warning.
The issue here is only that the importers expects to have valid CSS when importing which is not the case because .sss is using a sass like syntax without semicolons.
I first thought it was an issue with sugarss execution timeline, the parser should do it's job before the plugins to provide valid css. But this doesn't seem to be the direction @ai is wanting, it's more to the plugin to adapt their parsers based on the parser option or the extension name.

postcss-import is supposed to handle the syntax option https://github.com/postcss/postcss-import/blob/17708d4bbe2649c388f3a712e07647f76b8c989c/index.js#L304

Sorry everyone, the issue was me not having enough attention and not using the parser correctly as revealed by @TrySound here.
https://github.com/postcss/sugarss/issues/13#issuecomment-196299398


nan is affected by the update to V8 8.9 in Node.js

See https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2639/nodes=fedora-latest-x64/testReport/junit/(root)/citgm/nan_v2_14_2/

Is this the v8 version which will be in Node 16? Or is it expected that there are more API changes till then?

Not sure. We might still be able to update V8 once more before Node 16.


[SPARK-30654][WEBUI][FOLLOWUP] Remove bootstrap-tooltip.js which is no longer used.

What changes were proposed in this pull request?

This PR removes bootstrap-tooltip.js which is no longer used.
That script is replaced with bootstrap.bundle.min.js in SPARK-30654 ( #27370 ).
Why are the changes needed?

For cleaning up repository..
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Manually checked whether tooltips are shown in the UI and no error message shown in the debug console.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/27226/
Test PASSed.

Test build #122564 has started for PR 28515 at commit da1b096.

Test build #122564 has finished for PR 28515 at commit da1b096.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122564/
Test FAILed.


UI freezes on tiling WM

I see mentions of the next release using native window borders. I'm not sure if this is directly related.
Arch x86_64
https://aur.archlinux.org/packages/google-play-music-desktop-player-git/
Initial "Sign in" loads but stops right after.
https://my.mixtape.moe/qpwoci.mp4
Works in nested openbox.

Try running with the --disable-gpu option

Aha that worked. My GPU setup is
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Bonaire XTX [Radeon R7 260X/360]
           Display Server: X.Org 1.18.1 driver: (unloaded: amdgpu) Resolution<EMAIL_ADDRESS>           GLX Renderer: Gallium 0.4 on AMD BONAIRE (DRM 2.43.0, LLVM 3.9.0)
           GLX Version: 3.0 Mesa 11.3.0-devel (git-1f862e9)

For some reason GPU acceleration is brekaing things on linux.  I should add that to a FAQ somewhere

Yeah GPU acceleration in general on Linux is a mess. Thanks for the response and this wonderful application!


Add AuthPass repo (OSS flutter password manager)

(added at random position in the hope to avoid conflicts)

Thanks, @hpoul
Will figure out a way to improve this workflow. I was thinking to have an Airtable form. Do you have any suggestions?

@jai-deepsource i think PRs are a natural and easy way for this 😅 i actually think making it alphabetically sounds like an easy fix #165 .. although it will be painful to do the transition :-) you could also just create a single file for each first character and keep repositories.toml as a fallback catch-all 🤔


Update readme.md

Spotted a typo. It sounds like you mean to say "a list of files" where it was "a list a files".

Thanks for this. I'm taking any pull requests. Please file an issue and I'll be happy to look at it


Support PyTorch scalars

PyTorch master now supports scalars. Pyro currently breaks with PyTorch master.

I think this works now. We don't use scalars in all our examples, but many test and examples already use scalars.

@fehiepsi Do you know whether your gp module supports scalars? I'm starting to use it and I noticed that your tutorial still uses 1-dimensional tensors like variance = torch.Tensor([10]) rather than scalars like variance = torch.tensor(10.0).

@fritzo I think that it should be fine. We use length_scale with X / length_scale and variance to multiply with the final computation of covariance matrix. At some place we do variance.expand(...) but the behavior of this method is the same for both scalar and non-scalar tensor. I will fix if you detect any error related to scalar tensors.


"Mangayomi" is not opening on pc

Steps to reproduce
I encountered the same error every time I tried to open the app as usual by clicking on it.
Expected behavior
"It should open normally; however, that's not happening."
Actual behavior
I tried to open it, but nothing happened. I also tried using the administrator, but still, nothing happened.
Mangayomi version
v0.2.6
Device
Lenovo ThinkPad L540
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated all installed extensions.

can confirm same behavior in win10. reinstalling the previous version fixed the issue.

v0.2.6 not opening on Windows 10, for now, use v.0.2.55 though you can't delete via galley but manually delete chapters or the folder.

Seems like I'm not the only one facing similar issues.

Same here, Windows 11, 0.2.6, nothing happens on opening

Fixed! check the latest release


Access iterator inside each loop

Is it possible/can the index be accessed inside a ${{ each...}} loop?
I'm using an array to hold a list of names for repeated stages, and I'd like to set the dependency based on the previous one
e.g. in jinja 2 there is an index option - loop.index

I'd love this as well. For now, you may have a bit of luck attempting to detect the index using a hack I posted in a related issue:
https://github.com/microsoft/azure-pipelines-yaml/issues/427#issuecomment-580372308

have the same issue, @djpugh how did you solve this?

@Hkyx I gave up with trying, and just manually put stuff in...

Thanks @djpugh  :/

Another Microsoft rabbit hole. I try to use the loop and run a job, but then the job name has to be unique. To give a job name I try to find the index, but no. Why I need a job (instead of without a job), yeah because some tasks has to be server tasks and some has to be agent tasks. Microsoft world is all about these complex and illogical matrixes. Microsoft is about these rabbit holes and people working with their technology are just enjoying the job security

This issue moved here: https://developercommunity.visualstudio.com/t/access-iterator-inside-each-loop/1192557
It appears to have gone very stale.

NOTE: I'm using this workaround to get the index:
- ${{ each itemValue in parameters.myListOfValues }}:
  - pwsh: |
      $currentIndex = [array]::IndexOf(($env:FULL_LIST| ConvertFrom-Json), "${{ $itemValue }}")
      # ... do something with the index
    env:
      FULL_LIST: ${{ convertToJson(parameters.myListOfValues) }}


Doesn't Generate Mocks for Params and Return Values

When we have a type like:
type Foo interface {
    Foo() bar.Bar
}

Where bar.Bar is an interface type, we should generate a mock for bar.Bar as well.

Solved quite some time ago.


Remove Object.mixin

It never made it

I guess you meant "did not become part of ECMA2015"?

Yes.


Cakephp 3

Will this code support ver 3 of cakephp?

Hi, you can see the branch 3.X .

Thanks, can this be installed with composer? I didn't see it listed.

You can use composer require lowg33kdev/cakephp-gravatar-plugin
https://packagist.org/packages/lowg33kdev/cakephp-gravatar-plugin

Thanks, how do I also call the display

You must load the helper on your controller, and after use this on your view:
$this->Gravatar->generate('my-email@test.com)`
In second parameter, you can add an array with options (you can see options here)


Added no output adapter

The new adapter allows the user to get a response from the chat bot without having that response displayed ( in the terminal, for example ).

Looks good :+1:

Awesome. Let me know if you have any problems with it.

I will keep you posted.


spring-boot:run and livereloading of web static assets

I would like to live-reload my web assets as I change them instead of recompiling at each point.  My project uses this spring boot starter project and the camunda-bpm-spring-boot-starter-webapp dependency.  I have some customized assets that overlay the default webapp assets that currently live in src/main/webapp/* in my project.
I was looking into using the spring-boot-devtools util to enable live-reloading, but I don't think this plays nicely with mvn overlay paradigm. See this recent issue on the matter:  https://github.com/spring-projects/spring-boot/issues/1030
I would like to know if this project, or perhaps the camunda webapp project, has any plans to move away from the overlay paradigm. Or is there another way to make livereloading work with either the devtools or some other utility that accomplishes the same thing?  Does this project intend to introduce any development tools for developing the webapp further or are there larger changes happening in the webapp project to facilitate frontend development and extension?
Thanks! Also thanks for all the recent development on this project.  It's been very helpful.

Btw, when I say "live-reloading", I'm not talking about how-swapping java classes.  I just want to livereload static assets that are being overlayed onto the default webapp.

Hi @fouasnon how did you setup the overlay of the default webjar content did you just serve the static content on the same location of the webjar content?  Do you have a sample project on github.

@fouasnon Have you posted your question to camunda webapp project or found any solution?

I have not posted my issue to the general forum, but forking the 7.5 web app repo seems like a better alternative to the mvn overlay style at the moment.

OK. Do you like to provide a small sample project?

I'm facing same issue. I liked camunda-starter-webapp feature but like to customise tasklist in my springboot project without loosing other benefits provided by embedded web app.. But can't really do that.. So, for taking my Camunda application to enterprise level can't really happen by using embedded camunda-*-starter-webapp.. Any thoughts ?


Default the ContainerUser to rootless users on .NET 8 and above

Fix #373
Defaults the ContainerUser to platform-specific non-root users when targeting .NET 8 and above.

@vlada-shubina added one now - but it introduced a bit of noise as I had to make some code changes to make analyzers in .NET 8 happy.

Correction - I was able to write one locally but it would require us to move to a .NET 8 SDK - I'm not sure that we want to do this. The test build a net8.0 MinimalTestApp, set the user to app, and then ran the container with docker run to ensure everything still worked (which it did).


Update quickstarter

Tested against Daml Finance at 1fc439ac7fb089ad2d566202a6c104df7ff412d7

LGTM - I presume you tested removing the config that everything still works?

yes, I tested against this week's snapshot, where LF 1.15 has been made stable


C++ Program doesn't create functional audio files

All attempts fail with "I/O Error", working on fixing this now that I have access to a computer

I've figured out that there were a multitude of problems with the C version, but I did not have the 5150 to test until recently when I opened this issue. I've tested and as far as I can tell the binary functionality is now working. The source code has not been updated yet. I'll test the basic functionality next, and if it's working now I'll publish the fixed version.


benchmarks building is limited to gcc and its instructions are not well documented and failing.

Compiler limitation
benchmarks building is limited to gcc , but I'm using clang(and CXX is set to clang++), so I needed to modify the Makefile in benchmarks to something like:
CXX ?= g++
default:
	$(CXX) -std=c++11 -O3 bench1.cpp -s -o bench1 -lpthread
# the rest is similar

Dependency issues
bench1 builds fine without any dependencies.
bench2 requires WebSocket++ which in turn requires boost >> 1.41 (my production server default version of boost, I don't know the lower limit of version, but I just switched to the latest version)
bench3 and wsPP are similar to bench2.
uWS refers to missing ../uWS.cpp and ../utf8.cpp, the former is possibly just ./uWS.cpp, but the latter is not present.

8d978eb3dcd52a55ffdf7e3da01e8cc0f35a3a93

Now it builds. You need WebSocket++, Boost and I use G++ in this Makefile. On OS X g++ is an alias to clang++.

Thanks for the quick fix.
Yeah, g++ alias is the case for Mac, but we need to use g++ and clang++ separately under Linux, and CXX is the standard implicit variable for C++ compiler in GNU make and the usage of these variables are also suggested in GNU Makefile Conventions for better portability and substitutablity:

The Makefile rules for building and installation can also use compilers and related programs, but should do so via make variables so that the user can substitute alternatives. Here are some of the programs we mean:

ar bison cc flex install ld ldconfig lex
make makeinfo ranlib texi2dvi yacc

Use the following make variables to run those programs:

$(AR) $(BISON) $(CC) $(FLEX) $(INSTALL) $(LD) $(LDCONFIG) $(LEX)
$(MAKE) $(MAKEINFO) $(RANLIB) $(TEXI2DVI) $(YACC)

I mean, this is not a big deal, but it would be nice if I don't need to substitute g++ after every git pull :smile: , or if we could just use CMake to compile these benchmarks, it automatically uses CXX and its variants.
I would create a PR if you're OK with this, and I'll add some build instructions in it too.

Ah, nice. Did not know about $(CXX) in the Makefiles. It works here.

Sure add info and request for a pull.

Sorry for the delay, PR sent.


[fxnetworks] improve extraction

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[ ] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Explanation of your pull request in arbitrary form goes here. Please make sure the description explains the purpose and effect of your pull request and is worded well enough to be understood. Provide as much context and examples as possible.
Adding Series name, episode and season info to the extractor

sorry about that, fixed the test vid

No, you didn't. Have you even tried to run it after these changes?

I had two different versions on two different computers. I feel dumb. I swear I'm getting passing this time with what I have comitted...
python test/test_download.py TestDownload.test_FXNetworks
[FXNetworks]<PHONE_NUMBER>847: Downloading webpage
[ThePlatform] dRzwHC_MMqIv: Downloading SMIL data
[ThePlatform] dRzwHC_MMqIv: Checking video URL
[ThePlatform] dRzwHC_MMqIv: Checking video URL
[ThePlatform] dRzwHC_MMqIv: Checking video URL
[ThePlatform] dRzwHC_MMqIv: Checking video URL
[ThePlatform] dRzwHC_MMqIv: Checking video URL
[ThePlatform] dRzwHC_MMqIv: Checking video URL
[ThePlatform] dRzwHC_MMqIv: Downloading JSON metadata
[info] Writing video description metadata as JSON to: test_FXNetworks_dRzwHC_MMqIv.info.json
[debug] Invoking downloader on u'http://fxdlv.fxnetworks.com/FX_Networks/668/523/BET_S2_FIRSTLOOK_SEASONPREMIERE_SEPT14_CLEAN_FXWEB_1033460803894_mp4_video_1280x720_2500000_primary_audio_eng_8.mp4?__gda__=1509228942_3d55a77ce16e404060ef656258ad818d'
[download] Destination: test_FXNetworks_dRzwHC_MMqIv.mp4
[download] 100% of 10.00KiB in 00:00
.
----------------------------------------------------------------------
Ran 1 test in 2.247s

OK


AttributeError: qualname on Python 3.9 with typing.Sequence, Collection, Iterable or other generic aliases

To reproduce:
$ python3.9 -c 'from pydantic_settings import BaseSettings, CliSettingsSource
from typing import *
class S(BaseSettings):
    s: Sequence[int]  # or Collection, Iterable, etc.
CliSettingsSource(S)'

Traceback (most recent call last):
  File "<string>", line 5, in <module>
  File "/.../.venv/lib/python3.9/site-packages/pydantic_settings/sources.py", line 1165, in __init__
    self._connect_root_parser(
  File "/.../.venv/lib/python3.9/site-packages/pydantic_settings/sources.py", line 1574, in _connect_root_parser
    self._add_parser_args(
  File "/.../.venv/lib/python3.9/site-packages/pydantic_settings/sources.py", line 1656, in _add_parser_args
    kwargs['metavar'] = self._metavar_format(field_info.annotation)
  File "/.../.venv/lib/python3.9/site-packages/pydantic_settings/sources.py", line 1886, in _metavar_format
    return self._metavar_format_recurse(obj).replace(', ', ',')
  File "/.../.venv/lib/python3.9/site-packages/pydantic_settings/sources.py", line 1874, in _metavar_format_recurse
    list(map(self._metavar_format_recurse, self._get_modified_args(obj))), obj_qualname=obj.__qualname__
  File<EMAIL_ADDRESS>line 711, in __getattr__
    raise AttributeError(attr)
AttributeError: __qualname__

The error also happens when using types based on typing._BaseGenericAlias, like typing.Collection or typing.Iterable
The call ultimately fails on this line:
https://github.com/python/cpython/blob/3.9/Lib/typing.py#L711
The support for .__qualname__ for generic aliases was added only in Python 3.10:
https://github.com/python/cpython/blob/3.10/Lib/typing.py#L977
Hence this call on Python 3.9 is wrong:
https://github.com/pydantic/pydantic-settings/blob/v2.6.1/pydantic_settings/sources.py#L1874

Somehow pydantic~=2.10.0 is causing this break.
uv run --isolated --no-project --with pydantic-settings --with pydantic==2.10.0 --python python3.9 - <<EOF
from pydantic_settings import BaseSettings, CliSettingsSource
from typing import *
class S(BaseSettings):
    s: Sequence[int]  # or Collection, Iterable, etc.
CliSettingsSource(S)
print("success")
EOF

Results in:
Traceback (most recent call last):
  File "<string>", line 5, in <module>
  File "/.../lib/python3.9/site-packages/pydantic_settings/sources.py", line 1165, in __init__
    self._connect_root_parser(
  File "/.../lib/python3.9/site-packages/pydantic_settings/sources.py", line 1574, in _connect_root_parser
    self._add_parser_args(
  File "/.../lib/python3.9/site-packages/pydantic_settings/sources.py", line 1656, in _add_parser_args
    kwargs['metavar'] = self._metavar_format(field_info.annotation)
  File "/.../lib/python3.9/site-packages/pydantic_settings/sources.py", line 1886, in _metavar_format
    return self._metavar_format_recurse(obj).replace(', ', ',')
  File "/.../lib/python3.9/site-packages/pydantic_settings/sources.py", line 1874, in _metavar_format_recurse
    list(map(self._metavar_format_recurse, self._get_modified_args(obj))), obj_qualname=obj.__qualname__
  File<EMAIL_ADDRESS>line 711, in __getattr__
    raise AttributeError(attr)
AttributeError: __qualname__

But:
uv run --isolated --no-project --with pydantic-settings --with pydantic~=2.9.0 --python python3.9 - <<EOF
from pydantic_settings import BaseSettings, CliSettingsSource
from typing import *
class S(BaseSettings):
    s: Sequence[int]  # or Collection, Iterable, etc.
CliSettingsSource(S)
print("success")
EOF

Prints:
success

That line creates an instance of class CliSettingsSource and then immediately throws it away, just to demonstrate this bug.
The code I shared is just a minimal reproducible example for a more complex bug that we encountered in our internal codebase. The original code is proprietary so I can't share it, but this smaller example also makes it easier to identify and fix the underlying issue.
In our real codebase class S(BaseSettings): ... is a much more complex class where only one of the fields is a generic alias. Also in our case cli_settings_source = CliSettingSource(S) is not just initialized and thrown away, but instead it's assigned to a variable and used later on to do something useful.

@palotasb Thanks for your reply. Yes, it is related to a change in Pydantic. we have some custom logic ported from Pydantic.
I created https://github.com/pydantic/pydantic-settings/pull/497 to fix the problem.
Could you please test it?


Add Cluster Resources requests/limits for netviz container in the optional netviz deployment

Currently, while the CRD supports it, the Helm Chart is unable to provide resource limits/requests for the NetViz component, this adds that capability.

Fixed some conventions (netViz vs. netVizPod as parent).

it's not.  the resources are created to the CRD which supports the second set of resource limits/requests.  The operator then reconciles that post publishing the CRD to the server which specifies the resource limits and requests at the container level and not at the pod level.


Need to provide gas_price for every tx, otw it'll revert with ERROR: (VirtualMachineError) Insufficient funds for gas * price + value [APE-1430]

Environment information

OS: macOS
Python Version: 3.11.3
ape and plugin versions:

$ ape --version
0.6.21

$ ape plugins list
Installed Plugins
  alchemy      0.6.4
  arbitrum     0.6.2
  ens          0.6.1
  etherscan    0.6.10
  foundry      0.6.16
  hardhat      0.6.13
  infura       0.6.3
  solidity     0.6.9
  template     0.6.1
  tokens       0.6.2
  vyper        0.6.11

Contents of your ape-config.yaml (NOTE: do not post anything private like RPC urls or secrets!):

$ cat ape-config.yaml
name: Test

foundry:
  fork:
    arbitrum:
      mainnet:
        upstream_provider: <URL>

What went wrong?
Please include information like:
Test.sol:
pragma solidity 0.8.17;

contract Test {
    error Revert(uint x);
    event Transfer(address indexed spender, address indexed receiver, uint256 amount);

    function f() external returns (uint) {return 1;}

    function test() external {
        // revert Revert(1);
        require(false, 'xd');
    }

    fallback() external payable {}
}

Spin up console command:
ape console --network arbitrum:mainnet-fork:foundry
Inside console:
In [1]: alice = accounts.test_accounts[0]

In [2]: alice.balance =<PHONE_NUMBER>00000000000

In [3]: test = project.Test.deploy(sender=alice)
> ...
> ERROR: (VirtualMachineError) Insufficient funds for gas * price + value

How can it be fixed?
It was working prior to 0.6.21

TIL max gas is not good for Arbitrum local networks


Accessing different Oppia pages wiki needs an update

Add the getting-started pages for the following two pages of Oppia. The pages should contain similarly detailed information as we have for the contributor dashboard.

[x] LaCE @SanjaySajuJacob
[ ] Dev workflow

Per discussion with @nithinrdy, maybe the correct entry point for this is through the per-team getting-started pages -- here's the one for Contributor Dashboard, and we might want similar ones for the other two teams, LaCE and dev workflow.

@Nik-09 please update the project board with the expected merge date.

hi @Nik-09, just a follow-up for this issue, can you please update the expected merge date for this issue. thanks!

@Nik-09 Are you still working on this issue? Please let me know so that I can update the project board.

Per discussion with @nithinrdy, maybe the correct entry point for this is through the per-team getting-started pages -- here's the one for Contributor Dashboard, and we might want similar ones for the other two teams, LaCE and dev workflow.

I have updated the description as per the comment.

Hi @Nik-09 -- @SanjaySajuJacob has actually prepared this doc for LaCE onboarding: https://github.com/oppia/oppia/wiki/LaCE-onboarding-guide. Do you think it is sufficient for this issue?
Also @U8NWXD @gp201 @JeeveshGarg @Shivkant-Chauhan do you want to make a similar doc for folks onboarding to the dev workflow team? I'm not sure what should go on it, so checking to see if there are any common issues that arise for new contributors (or contributors starting a project in a new domain) that you're aware of. Possibly even a list of links to the relevant wiki pages might be helpful (e.g. "If you're working on XYZ, look at ABC").

Hi @Nik-09 -- @SanjaySajuJacob has actually prepared this doc for LaCE onboarding: https://github.com/oppia/oppia/wiki/LaCE-onboarding-guide. Do you think it is sufficient for this issue?

Yes, the page is very effective; I think adding an overview section for the LaCE team will be better.

@U8NWXD OK, but in that case, what do you think about a "Welcome to the Dev Workflow Team" page that lists the broad areas and points to the relevant wiki pages for each? Then we have a getting started page for each team, which we can perhaps include in the emails we send folks when inviting them to a team (or in the getting started page).
(Just double-checking this point since your comment didn't address it directly; if you still don't want it, then that's fine!)

I think that could be useful. Here are the pages I can think of to link:

Automated testing and Debugging pages
Lint checks
Backend typing
Codebase overview
Oppiabot
Third-party libs
Build process
How the wiki works


Added Project Eve to the landscape

LGTM

The logo you used has Engine in white so it doesn't show. I can ask @alexcontini to change the white text to purple if you want.

@dankohn Sounds great... can you ask him to just submit a PR with it? There's an issue with the build atm (see failed build above), so it won't be merged right away. I didn't create the original netlify account, so does't look like I can fix it. Reaching out to see if I can find out who owns it.

Alex is a woman. Ibrahim and I have access to the Netlify, but you should be able to see the error that it failed because you removed Kubernetes as graduated. We have a test that looks for it. We'll change the test to look for Eve instead.

you should be able to see the error that it failed because you removed Kubernetes as graduated


ingress: export Config[T] type.

The ingress cell does not export its config type (i.e. the type is visible to the rest of the hive, but the type is not exported outside of the package).
Exporting config types is useful for forked projects to be able to check configuration of various components within Hive. Thus this export the type.

/test


[documentation] : refactoring the page setup✨

the pages in the github are slightly messed up , I can fix them by creating proper folders and make sure all the links work. Can you please assign this task.

@07sumit1002 can you assign this issue to me if currently no one is working on it please!