PhaseScriptExecution error during IOS build.

I have an issue during IOS build with flutter. I receive this error during build (Android builds fine):
PhaseScriptExecution Run\ Script /Users/appveyor/Library/Developer/Xcode/DerivedData/Runner-edbyerddbiuubgfgxijtdvcduzhj/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/Runner.build/Release-iphoneos/Runner.build/Script-9740EEB61CF901F6004384FC.sh
The script being called exists and contains:
#!/bin/sh
/bin/sh "$FLUTTER_ROOT/packages/flutter_tools/bin/xcode_backend.sh" build

The command being run from fastlane is:
Dir.chdir "../.." do sh("flutter", "build", "ios", "--release", "--no-codesign") end
This occurs on our build server.
For the life of me I cant figure this one out. I've been working on it a couple days.
My project was on flutter 1.25.0-8.3 BETA, I upgraded to flutter 2.8.0 STABLE
Any clues at to what I'm doing wrong? I have the build log if that would help, what is the best way to provide it?
Steps to Reproduce
Execute from fastlane script:
Dir.chdir "../.." do sh("flutter", "build", "ios", "--release", "--no-codesign") end
Logs

Logs
I have detailed logs, but they are massive 3mb+ what is the best way of getting them to you?

Flutter doctor says:

worker-629-002:flutter appveyor$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.8.0, on macOS 12.2.1 21D62 darwin-x64, locale en-US)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[!] Android Studio (not installed)
[!] Connected device
! No devices available

! Doctor found issues in 4 categories.

I've tried adding
export FLUTTER_ROOT="/Users/appveyor/flutter" as per here: https://github.com/flutter/flutter/issues/49495

Running the command results in:
worker-628-001:Runner.build appveyor$ ./Script-9740EEB61CF901F6004384FC.sh
/bin/sh: /packages/flutter_tools/bin/xcode_backend.sh: No such file or directory

My project was on flutter 1.25.0-8.3 BETA, I upgraded to flutter 2.8.0 STABLE

That beta version is a bit old and latest stable is 2.10.5.
Is there a way to provide complete verbose log that shows the error ? You can put that verbose log in a text file and share it here.
Also provide ios/podfile

There is currently no ios/podfile. This is something that has had me wondering, do you actually need to use Pod? or is it optional. As I previously had everything working without it?
Runner-Runner.log

This is something that has had me wondering, do you actually need to use Pod? or is it optional. As I previously had everything working without it?

If you have plugins in your project, respective pods will be created. If you don't have any plugins, there won't be any pods.
From what I see, you don't seem to have any plugins and hence you don't see any podfile or pods, is it correct ?
But the log you shared seems to show plugins already, so that doesn't seem to be the case. If there are plugins in your app, you should see ios/podfile.
It seems your app with valid archs is messed up, as I see from the log:
export arch\=undefined_arch
So please check your app configuration once again because the error seems to be occuring due to mis-config or not using valid archs.

Admittedly, I have tried about 9 million things to try and get this to work. I might have had a pod file present during that build.
Where do I define the Arch in flutter? Did a quick google but didn't return any info about it. Would this be in fastlane perhaps?
Sadly, I've had to revert the entire project back to an earlier commit. I've spent about a week tracking this down and I have had no luck. My plan was to go back to a known good build and then move forward from there.

Okay after rolling everything back to latest known working. Still getting the same error.
Flutter Doctor -V
[✓] Flutter (Channel beta, 2.6.0-5.2.pre, on Mac OS X 10.15.7 19H1715 darwin-x64, locale en-US)
    • Flutter version 2.6.0-5.2.pre at /Users/appveyor/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 400608f101 (8 months ago), 2021-09-15 15:50:26 -0700
    • Engine revision 1d521d89d8
    • Dart version 2.15.0 (build 2.15.0-82.2.beta)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at /Users/appveyor/android-sdk
    • Platform android-29, build-tools 29.0.0
    • ANDROID_SDK_ROOT = /Users/appveyor/android-sdk
    • Java binary at: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_292-b10)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode-12.3.app/Contents/Developer
    • CocoaPods version 1.11.3
[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
[!] Connected device
    ! No devices available
! Doctor found issues in 4 categories.

Build machine Arch:
Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
Flutter Version:
flutter_macos_2.6.0-5.2.pre-beta
PodFile:
# Uncomment this line to define a global platform for your project
# platform :ios, '9.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

pubspec.yaml (Last bits omitted.)
name: livevenue
description: test

# The following line prevents the package from being accidentally published to
# pub.dev using `pub publish`. This is preferred for private packages.
publish_to: 'none' # Remove this line if you wish to publish to pub.dev

# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# In Android, build-name is used as versionName while build-number used as versionCode.
# Read more about Android versioning at https://developer.android.com/studio/publish/versioning
# In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
# Read more about iOS versioning at
# https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.0+1

environment:
  sdk: '>=2.12.0 <3.0.0'

dependencies:
  livevenue_common:
    path: ../shared/livevenue_common
  livevenue_api:
    path: ../shared/livevenue_api
  intl: ^0.17.0
  url_launcher: ^6.0.3
  equatable: ^2.0.0
  geolocator: ^7.0.3
  rxdart: ^0.27.0
  flutter_bloc: ^7.0.0
  flutter_secure_storage: ^4.2.0
  font_awesome_flutter: ^9.0.0
  cached_network_image: ^3.0.0
  package_info: ^2.0.0
  carousel_slider: ^4.0.0-nullsafety.0
  dio: ^4.0.0
  shimmer: ^2.0.0
  stripe_sdk: ^5.0.0-nullsafety.0
  awesome_card: ^1.1.5
  credit_card_validator: ^2.0.0-nullsafety.0
  mask_text_input_formatter: ^2.0.0-nullsafety.2
  formz: ^0.4.0
  qr_code_scanner: ^0.4.0
  firebase_core: 1.3.0
  firebase_messaging: 10.0.2
  overlay_support: ^1.2.1
  flutter_local_notifications: 8.2.0
  collection: ^1.15.0-nullsafety.4
  vrouter: ^1.2.0+7
  badges: ^2.0.1
  timeago: ^3.1.0

  flutter:
    sdk: flutter

dev_dependencies:
  effective_dart: ^1.3.1
  flutter_test:
    sdk: flutter

When running the build manually:
The code exits with:
ERROR [2022-05-10 20:30:22.43]: Exit status: 65

EXCLUDED_ARCHS[sdk=iphonesimulator*]=i386

Here can you update to add arm64 and see if it helps ?
['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'arm64 i386'

I'm getting this error during build:
[!] [!] Dictionary missing value for key "EXCLUDED_ARCHS", expected '=' and found "[" (Nanaimo::Reader::ParseError)
I set project.pbxproj to be:
EXCLUDED_ARCHS[sdk=iphonesimulator*] = 'arm64 i386';

Same error:
** ARCHIVE FAILED **
The following build commands failed:
PhaseScriptExecution Run\ Script /Users/appveyor/Library/Developer/Xcode/DerivedData/Runner-edbyerddbiuubgfgxijtdvcduzhj/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/Runner.build/Release-iphoneos/Runner.build/Script-9740EEB61CF901F6004384FC.sh

Updated Log:
Runner-Runner.log

I'm getting the same issue with a new project:
app_test.zip
▸ Running script 'Run Script'
** ARCHIVE FAILED **
The following build commands failed:
PhaseScriptExecution Run\ Script /Users/appveyor/Library/Developer/Xcode/DerivedData/Runner-hjdtgitipgxpcigyzqszwlwtdqow/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/Runner.build/Release-iphoneos/Runner.build/Script-9740EEB61CF901F6004384FC.sh
(1 failure)
ERROR [2022-05-11 20:30:19.10]: Exit status: 65
Using commands:
  bundle install --quiet
  bundle exec fastlane build --verbose

Does the same occur when you try to build locally ?
Are you trying this on latest versions ?

I don't have a MAC so I cant try it locally.
I'm unable to upgrade due to the new versions of flutter forcing me to switch to the new embed mode.

This probably seem to be causing due to mis-configuration or some setup issue at your end and per you said it occurs on your build server. Without actually replicating it locally and correct steps to replicate, it'll be hard to analyze / debug further.

With the project that I created using flutter new above works for you and compiles?
That application is a flutter new project with nearly no modification.
Could this be related to signing key issues?

I think this might relate to Fastlane, will try with them and see if they have any ideas and will report back here.

I seem to have go this working, I'm honestly not 100% sure what did it.
But I think part of it was disabling XCode auto signing:
disable_automatic_code_signing(
  team_id: "",
  profile_name: "",
  code_sign_identity: ''
)

Thanks for the help and sorry I cant give people a more concreate answer.


ScottPlot 5 scatter plot fill problem when using ConnectStyle StepHorizontal.

The issue has to do with FillY between 2 scatter arrays. The arrays are set up with ConnectStyle.StepHorizontal. The problem is that if I try to fill the space between two scatter arrays using plt.Plot.Add.FillY, the Fill appears to assume the use of ConnectStyle.Straight.
IMHO, the Fill should match up with the ConnectStyle.
ScottPlot version is ScottPlot.WPF version 5.0.21.
private void TestScottPlot5()
{
    double[] zeros = new double[10];
    double[] data = new double[10];
    double[] positions = new double[10];
    ScottPlot.WPF.WpfPlot myPlot = WpfPlot1;    // name of ScottPlot instance in the xml file

    for (int i = 0; i < 10; i++)
    {
        positions[i] = i;
        zeros[i] = 0;
        data[i] = Math.Sin(2.0 * Math.PI * (double)i / 10.0);
    }

    var scatterZeros = myPlot.Plot.Add.Scatter(positions, zeros);
    scatterZeros.ConnectStyle = ConnectStyle.StepHorizontal;

    var scatterData = myPlot.Plot.Add.Scatter(positions, data);
    scatterData.ConnectStyle = ConnectStyle.StepHorizontal;

    var xyy = myPlot.Plot.Add.FillY(scatterZeros, scatterData);
    xyy.FillStyle.Color = ScottPlot.Colors.Blue.WithAlpha(100);
}

Adding additional context to move this issue forward, this is the current behavior of the code above:

For more context, these are the lines of code that need to be modified to create a polygon that respects the step shape:
https://github.com/ScottPlot/ScottPlot/blob/fdd1dfdf0fd8d32ce3176337c2140f5f14e44a20/src/ScottPlot5/ScottPlot5/Plottables/FillY.cs#L31-L44

if you set FillY=true, this seems to work already.
        double[] zeros = new double[10];
        double[] data = new double[10];
        double[] positions = new double[10];

        for (int i = 0; i < 10; i++)
        {
            positions[i] = i;
            zeros[i] = 0;
            data[i] = Math.Sin(2.0 * Math.PI * (double)i / 10.0);
        }

        var scatterZeros = myPlot.Add.Scatter(positions, zeros);
        scatterZeros.ConnectStyle = ConnectStyle.StepHorizontal;

        var scatterData = myPlot.Add.Scatter(positions, data);
        scatterData.ConnectStyle = ConnectStyle.StepHorizontal;

        scatterZeros.FillY = true;
        scatterData.FillY = true;


[REQUEST] Expose Host Manipulation in API

Nope is becoming a project that is unwieldy to use directly in game because, although it is powerful and can perform for a wide variety of use cases, a firm understanding of its internal structure. So, it seems that it might become much more useful as an engine that runs external plugins like:

Towns plugin ("Outpost")
Prison plugin ("Stockade")

So, to support such endeavors, we need an API that basically does everything that the command structure does. So, we need to pull the behavior out from

command -> HostSystem

to

command -> host API -> HostSystem.

This will now be tracked here https://github.com/pietelite/nope/issues/17


NaN loss during training

When I use RAdam in estimator, I encounter  'NaN loss during training' problem. However Adma works fine.

Me too, have you solved it now?


fix make verify failed and add dev image workflow

What type of PR is this?
/kind cleanup
What does this PR do?

add verify-all.sh fix make verify failed
make clean add  go clean -cache for macos make all failed
delete deprecated serviceAccount in the clusterlink-elector.yml scheduler/deployment.yaml mysqll-operator.yaml
add dev_images.yml workflow to publish dev person image packages

Which issue(s) does this PR fix?
No issues
Fixes #
make verify failed
Special notes for your reviewer:
@duanmengkk
Does this PR introduce a user-facing change?
NONE

Is there any kosmos project template to init or create project easily ? @OrangeBao


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes.

Bicep or Terraform?
Bicep
Module Classification?
Resource Module
Module Name
avm/res/elastic-san/elastic-san
Module Details
Implement elasticSan, privateEndpointConnections, volumegroups, snapshots and volumes
https://learn.microsoft.com/en-us/azure/templates/microsoft.elasticsan/allversions
Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username (handle)
jbinko
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

Hi @jbinko,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"

Hi @jbinko,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:

For your module:

ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry

For your module's repository:

Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

Work in progress

Work completed. PR created: #3809

[x] Module published.
[x] GitHub teams are available and assigned to their parents.
[x] CODEOWNERS file updated.
[x] Issue template file updated.

The module index will be updated to reflect this change.
Thank you for your work @jbinko! I'm closing this issue now.


Tracking the test case to bifurcate the sampling error

This is all about finding the MWE to see what changed.

On julia 1.6 instantiate new HMCExmaples branch, make sure it will work with a simple short RBC kalman run.  If not, then I can help debug it
Then with print_level = 1 https://github.com/HighDimensionalEconLab/HMCExamples.jl/blob/main/src/turing_models.jl#L126 should do an output of every sample from turing and then show in https://github.com/HighDimensionalEconLab/HMCExamples.jl/blob/main/src/turing_models.jl#L131

So I think the basic approach is to just run something like

julia --project --threads auto -O1 bin/fit_FVGQ_1_kalman.jl --results_path ./results/main_rbc_1_FVGQ --overwrite_results true --num_samples 1000 --print_level 1

and then maybe pipe the output to a file?  with > output.txt or just copy/paste the output at the end.

With this, we shhoud be able to see all of the theta that are proposed and then see a println("Perturbation failed / Infinite variance with retcode $(sol.retcode)")

Then with this

Switch over entirely to the DSSM package itself, as HMCExamples is no longer required.
Pick one that looks like it probably shouldn't have been rejected (we can come back to thte list) and then switch over to the DSSM entirely and make sure  we can manually call generate_perturbation and generate_perturbation_derivatives! on the theta and get it to return a retcode != Success.

Keep that test code around because we will want to check soemthing equivalent on old code.

Then switch to the old branch of DSSM back when things "worked" in january, instantiate the pacakges, etc.
Now take the theta that you thought shouldn't have been rejected and that you were able to manually trigger a failure on with the DSSM for the later version, and try the same thing with the old DSSM code.
If that also triggers an error, maybe try a different theta from your list of rejected thetas from HMCExamples.

Once we find the theta which (1) triggers an error in the new DSSM; and (2) doesn't trigger in the new DSSM, we can take the next step in bifurcating the differences.

Closing since we can reproduce the wrong gradients.


Potential to improve aggregation algorithm?

https://github.com/oduwsdl/MemGator/blob/542d96df52fe32e384ef8185fe8e3cbb8ea942a0/main.go#L452-L466
...seems to indicate a form of "online" insertion sort, which seems like it would be temporally expensive. Is there the potential to optimize this algorithm for more efficient sorting of URI-Ms (and other metadata) from a set of TimeMaps to a combined one?

@ibnesayeed and I spoke in-person and I was very wrong. @ibnesayeed If you could provide some explanation here, I think it would do you implementation justice.

The algorithm used here is pretty efficient and optimized for the kind of data we deal with (where it is mostly linear in practice). We are exploiting the fact that most of the archives often return TimeMaps already sorted in chronological order. In that case it is simply a matter of traversing the linked list of a TimeMap from an upstream archive and the accumulated linked list in the same direction and merging nodes from the new one into the accumulated one in minimum number of traversals and comparisons. In rare cases when an archive provides data in random or reverse order, the cost will go a little up, but not at the time of merging, instead when that individual upstream TimeMap is being parsed and converted into a linked list. The reverse order can further be optimized by specifying the sort order in the archive description (in the JSON file), but I did not know any archives that return data in reverse chronological order, so never attempted to add more logic for that. There are some other optimizations in place when lists are being merged, for example assigning new linked list to the base (or accumulated liked list) if the base is empty or swapping the base with the new one if the new one is longer so that a short list is merged into a long one and not the other way, hence fewer number of comparisons.
That said, if you find any other potential optimization opportunities without increasing the memory footprint then please feel free to discus and implement them. TimeMaps can be very long, so memory will remain a concern when selecting a sorting algorithm.

@machawk1 I am closing this now, but please feel free to reopen if you find some issues in it.


Kong Manager in Kong OSS

Discussed in https://github.com/Kong/kong/discussions/12296

Originally posted by pritishpattanaik January  5, 2024
Hi All,
How to secure Kong Manager ?  I am running kong 3.5 on RHEL with hybrid deployment. Please advise if anyone has configured authentication in Kong Manager. Did anyone encounter this challenge. I don't understand what's the point of having a beautiful Admin UI without authentication. I just proposed  my team to use Kong OSS but now i am completely stuck.
So far i've created two services

AdminAPI Service with http://<kong_control_plane_ip>:8001
route - /admin-api

KongManager service with http://<kong_control_plane_ip>:8002
route -   /manager
~/asset.*      # added for accessing css/html

I am getting below error while accessing Kong manager via data plane route.
http://<kong_data_plane_ip>:8000/manager
error in chrome console.
Refused to apply style from 'http://10.x.x.x:8000/assets/index-518a32f1.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

Use https://github.com/Kong/kong/discussions/12296 for the future discussion.


Prefixed JSON filenames with the image UUID

Summary
Added the image UUID as a prefix for the various JSON files generated from the image metadata interface
Related Issues / Discussions
Closes #6469
QA Instructions
Go to "info" for a generated image, switch to "Metadata", "Image Details", etc. and click the JSON download button. The downloaded file should now have the image UUID with an underscore and then the JSON label itself. If there is no UUID (no image_name), the fallback will just be the label.
Merge Plan
N/A
Checklist

[x] The PR has a short but descriptive title, suitable for a changelog
[ ] Tests added / updated (if applicable)
[ ] Documentation added / updated (if applicable)

Lets provide the filename we want directly in the parent component

Done - hopefully that looks a bit better?

Updated. Thanks for the guidance.


Add transcoder address to job info

What does this pull request do? Explain your changes. (required)

The SDK function getJob() currently will not return a transcoder address in the result object if the transcoder did not already submit an on-chain claim to store the transcoder address on-chain. This PR calls the contract function electActiveTranscoder in order to compute the assigned transcoder address to be returned with the result object.
How did you test each of these updates (required)

Does this pull request close any open issues?

Fixes #190
Screenshots (optional):

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.

@yondonfu good suggestion. I just added the test.


WPF HexEditor throws System.NullReferenceException when setting selection from code

Problems
I am building a WPF application capable of highlighting a specific portion of a data file in the hex editor. I loaded the file into the hex editor by binding the Stream property in XAML, then I specify the portion of the file to be selected and highlighted in the hex editor by calling the SetPosition method. And the SetPosition method immediately throws a System.NullReferenceException. Related code snippets are listed below:

Bind Stream property in XAML

<wpfhex:HexEditor x:Name="hexEditor" Grid.Row="1" ReadOnlyMode="True"
                  Stream="{Binding ElementName=_self, Path=RawDataStream}"/>

Event handler to be invoked when user choose to select and highlight some portion of the file

// RawDataStream is a dependency property of type System.IO.MemoryStream
RawDataStream = someStream;     // Set the underlying data stream of the hex editor
// hexEditor.Stream = someStream;    // If I replace the statement above by this statement, exception still exist

if (someStream != null)
{
    // And set the portion of the file to be highlighted
    // This throws System.NullReferenceException
    // startOffset and length are all not below 0
    // and startOffset + length is not beyond the end of the stream
    hexEditor.SetPosition(startOffset, length);
}

StackTrace of the exception
   在 WpfHexaEditor.HexEditor.SetScrollMarker(Int64 position, ScrollMarker marker, String description)
   在 WpfHexaEditor.HexEditor.SelectionStart_ChangedCallBack(DependencyObject d, DependencyPropertyChangedEventArgs e)
   在 System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
   在 System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
   在 System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
   在 System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
   在 System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
   在 System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
   在 WpfHexaEditor.HexEditor.SetPosition(Int64 position, Int64 byteLength)
===== Unrelated Stacks =====

Platform

.NET Framework 4.7.2, WPF
NuGet WPFHexaEditor Version 1.6.2

The binding now work correctly. I need to check this.
you can "bind" your stream in code like this
            _findMs = new MemoryStream(1);
            _findMs.WriteByte(0);
            FindHexEdit.Stream = _findMs;

Your stream are opened before the binding is called ??


Create an autodeploy of the FairOS docs

The docs should be generated from the repo and deployed to:

docs.fairos.fairdatasociety.org (fully working when DNS are set, I guess)
some redirect from current location?

@jmozah and @IgorShadurin Discuss also including the instructions on how to spin up the stack on a server (written down by @IgorShadurin as notes currently)

@crtahlin Seems like the domain docs.fairos.fairdatasociety.org not tied to our host


qpwgraph fails to open with "Could not initialize GLX"

Describe the bug
When I launched qpwgraph with the command flatpak run org.rncbc.qpwgraph it fails with these error messages:
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QColorSpace(), profile  QSurfaceFormat::NoProfile)

Could not initialize GLX

What did you expect to happen?
I expected when I launch qpwgraph for it to launch without problems.
Output of rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:latest
                   Digest: sha256:d0b9a69f5ee8ed549b6ee19dca94127390c988fc3c2383679914f5190ef41a9a
                  Version: 40.20240822.0 (2024-08-23T04:12:10Z)
          LayeredPackages: alacritty sunshine

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:latest
                   Digest: sha256:477dab81e8d2ed1645c837249cddb00a81c06127d449fe434c38f52476cdf877
                  Version: 40.20240821.0 (2024-08-22T05:48:52Z)
          LayeredPackages: alacritty sunshine

Hardware
Operating System: Bazzite 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.9.12-205.fsync.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
Motherboard Name: B550 Pro4
Extra information or context
This works on the previous version, so I entered rpm-ostree rollback and it worked again.
Screensharing in Vesktop also doesn't work and it fails with a very similar error message.

Same problem with VLC and every other Media Player I tested:
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
Could not initialize GLX

Upstream error with flatpak, already fixed and should be shipped out to everyone soon.


fix SSL_get_wbio may return rbio on quic

I believe it is a typo :)

This pull request is ready to merge

Merged to master branch. Thank you for your contribution.


snappy compression

I used sarama AsyncProducer using snappy compression to send messageSet(5 messages per messageSet),I found that  the origin data were 3940 bytes, and the compressed data were 832 bytes.It indicated the snappy compression has worked..While I checked kafka log data，it showed "offset: 1047825 position: 484851876 isvalid: true payloadsize: 3607 magic: 0 compresscodec: SnappyCompressionCodec crc:<PHONE_NUMBER>" and it seemed that the kafka broker had decode data and encode data again..
How can I store compressed data in kafka which should be 832 bytes per messageSet in this case ?

Kafka configuration is outside the scope of this project; if sarama is sending the data compressed, then there is nothing else we can do on our end. Please ask perhaps on the kafka-users mailing list.

ok。3ks.


Fix zsh global install

This fixes zsh global completion breakage introduced in #463, and updates the test to use a similar method as activate-global-python-argcomplete for zsh.
The zsh global completion script was previously mixing paradigms; it seems that you are supposed to use a file with a #compdef comment which is autoloaded, or manually call compdef yourself. I've updated this to only use the #compdef comment, but it does feel like everything would be simpler if we went the other way and sourced the file directly as we do with bash. The only catch with that is we would probably have to append this to ~/.zshrc instead of ~/.zshenv since we need compdef to be available, and it seems undesirable to autoload compdef on the user's behalf.

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

Comparison is base (d696194) 81.12% compared to head (f4b91dd) 81.12%.
 Consider uploading reports for the commit 6095cde to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #466   +/-   ##
========================================
  Coverage    81.12%   81.12%
========================================
  Files           10       10
  Lines          784      784
========================================
  Hits           636      636
  Misses         148      148

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

@evanunderscore as far as I know, we can't source the file directly (at least not without making our installation process a lot less general). Zsh has no default facility to source completion scripts at startup - instead it scans the first lines of these files for compdef declarations. The actual scripts are sourced on demand according to those declarations.
By the way, we will be facing something similar with bash soon. Bash completion v1 (which is what we use for global completion installation) sources entire scripts, but it's deprecated. Bash completion v2 uses a similar lazy-load pattern that does not allow registering a global completion fallback (complete -D, which is what we use).
We could always use the alternative strategy of telling the user to source the file directly in their rc script, but that's not a systemwide installation method and it's brittle in other ways.
Testing this branch now.

Testing looks good, I agree this approach seems to be the best.

Released in v3.2.0.


Documentation link is dead

What is the question: Are the documentation links dead ?
Hi,
I was interessted in seeking ressource for this project, but it seems the docs link is dead as it goes to a github 404 (https://github.com/serverlessworkflow/synapse/blob/main)
Is there another link ?
Regards,

@Smixi Thanks for the info! It should now be fixed ;)


Remove website deployment GitHub action

This will fix #9229. The deployment will resume once #9276 is merged.

 I didn't even think of just disabling it. 🤦♂
Can you disable it and see if that unblocks your pr? I'm away from the computer right now. If it works I'll just hold off on merging this.

Yep my other PR is unblocked! Thanks for the help!


Move away from hard-coded machine name

Adding more architecture types or moving machine around was starting to
take its toll on how often we reconfigure the jenkins scripts. This
change decouples which physical machine actually runs the jobs and makes
sure that only a provisioner change (machine name) is needed to relocate
resources to the right place.

Please ensure that the lab reflects these changes on all machines


Capytaine v1.5

Checklist

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

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

@conda-forge-admin, please rerender

Failing due to

conda.CondaMultiError: HTTP 502 BAD GATEWAY for url https://conda.anaconda.org/conda-forge/linux-64/python_abi-3.11-3_cp311.conda

...

And now it works...


Updating problems getting light bar to work.

Thomas,
I was out of town for a bit and didn't have a chance to reply. My issue is not with the controller; it is working. The issue is either with the sketch or the communication between the controller and the Teensy.
Here are some clues that I observed:

The sound works from the controller, but I can only get a single led to the light.
I get the same responses if I run the controller from a Mac, Mint Linux, or the pie.
When I say the controller is working, I mean the play, pause, and stop buttons. The eye icon and the? Done seen to have any effect.
Also, do you have the procedure you posted for loading the controller on the pi? I may need to reinstall it, and I did not save it anywhere. I hope this helps; if not perhaps you could suggest where to start looking>
thank you again

When you execute this
import usb
for dev in usb.core.find(find_all=True):
    print(dev)

in your Python environment with properly flashed and attached Teensy LC, there should be something like this
DEVICE ID 16c0:0483 on Bus 020 Address 022 =================
 bLength                :   0x12 (18 bytes)
 bDescriptorType        :    0x1 Device
 bcdUSB                 :  0x110 USB 1.1
 bDeviceClass           :    0x2 Communications Device
 bDeviceSubClass        :    0x0
 bDeviceProtocol        :    0x0
 bMaxPacketSize0        :   0x40 (64 bytes)
 idVendor               : 0x16c0
 idProduct              : 0x0483
 bcdDevice              :  0x273 Device 2.73
 iManufacturer          :    0x1 Teensyduino
 iProduct               :    0x2 USB Serial
 iSerialNumber          :    0x3 5667580
 bNumConfigurations     :    0x1

printed to screen. If not, your Teensy is either not properly flashed or not properly attached to your USB. To check that, you do not need the controller software:

Check, whether Teensy is properly flashed.
When attaching the light bar to your USB port, the outer LEDS should be lit for half a second, one in red, the other in green. If you see only the green one, you have to adjust NUMLED in the firmware's source code to the number of LEDs of your stripe. If you do not see the 0.5 secs flash at all, something went wrong with programming the Teensy. Try it again.
Try another USB cable.
Surprisingly, not all USB cables work properly with Teensy. So best try some different vendors and lengths. I got best results with Amazon Basic Cables.

Good luck

Thank you for the information. I verified that the teensy is working correctly, but unfortunately, I had to reinstall the software on my pi. I decided to install the legacy 32-bit version and would like you to provide the steps for installing the Controller Software on the PI. Here is what I recall stepwise:

Create a Controller Directory
download EMDR folders and files
pip3 install -r requirements.txt
Download and install libusb
Setup autostart on pi

That's about what I recall. Thanks for your help.
Dan
By the way! Harvey is a great film. I have a copy on DVD that I dug out a week ago. The lady who played the female nurse was a good actress but retired only a few years later to marry. They stayed married for 60+ years, quite uncommon for an actor today.

For setting up Raspberry Pi without PiBakery, please refer to: https://github.com/Harvey71/emdr/issues/4

Thank you, Thomas
Daniel Bell, PhD
Program Chair, Interactive Media Design
Franklin University
<EMAIL_ADDRESS>614.947.6117
From: Thomas Niebur @.>
Date: Monday, February 6, 2023 at 10:59 AM
To: Harvey71/emdr @.>
Cc: Daniel Bell @.>, Author @.>
Subject: Re: [Harvey71/emdr] Updating problems getting light bar to work. (Issue #6)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
For setting up Raspberry Pi without PiBakery, please refer to: #4https://url.avanan.click/v2/___https:/github.com/Harvey71/emdr/issues/4___.YXAzOmZyYW5rbGluZWR1OmE6bzpkMDQ3MWQwMzg4NjJkYWYxZDllNzJhZmU2OWYyNmQwNjo2OmMzZGQ6NTUxYjMyNmE5MjgwOWE4ZjBhZjMyNmQ2NjgxYjE2MTI0YmM0ZmQ0NTk1NmRmZTBiNmExN2RjODQwOWU4NDNmYjpoOlQ
—
Reply to this email directly, view it on GitHubhttps://url.avanan.click/v2/___https:/github.com/Harvey71/emdr/issues/6%23issuecomment-1419318161___.YXAzOmZyYW5rbGluZWR1OmE6bzpkMDQ3MWQwMzg4NjJkYWYxZDllNzJhZmU2OWYyNmQwNjo2OmM4ZWY6ZTlhOTM3Y2ZjZmUyNzJlZjYzNjAyNjkyN2U3Mjk0N2Y2OWYyOWRiMWJlYjA3N2NjODJjNmM3MmFkMGNhYjFlNzpoOlQ, or unsubscribehttps://url.avanan.click/v2/___https:/github.com/notifications/unsubscribe-auth/ABPDAEGGU7BV77PO35YVFW3WWENSFANCNFSM6AAAAAAUOGUFHQ___.YXAzOmZyYW5rbGluZWR1OmE6bzpkMDQ3MWQwMzg4NjJkYWYxZDllNzJhZmU2OWYyNmQwNjo2OjA2Mjg6YTA5MTE5YzRhMTExZmExMGZiYWU2OGIyMzA2MGNjMzdiZDcwMWQ4YWEyM2ViMzU0N2IzNTBiNzYwZjAxNTM3YjpoOlQ.
You are rece iving this because you authored the thread.Message ID: @.***>

Hi Thomas,
any idea why this command is returning Permission Denied?
echo "dtparam=audio=on"|cat - boot/config.txt &>/boot/config.tmp

You have to be root to write to that file. Try this before:
sudo su

would python3-sdl2 be a viable alternative for E: python3-sdl?  I get an error: E: Unable to locate package python3-sdl

Should work, too. Just try it. :-)


Bug using SSR with version 5. Crashes with "More hooks than previous render" when running Google Audit / Lighthouse

Site with Styled Components 4 and SSR is working great, but when upgrading to Styled Components 5, we can put the app in an erroneous state by running Google Audit in Chrome.
Steps to reproduce
Use Styled Components 5 or 5.0.1.
Setup SSR according to "Advanced usage" on Styled Components homepage.
Render components with some styled components.
Expected Behavior
Page should render without problem every time.
Actual Behavior
Manual pageloads gets rendered fine, but when running Google Audit, the Node server running SSR crashes and must be restarted.

We can’t debut or help with this unfortunately without a reproduction or more information.
Based on the version having been tested thoroughly though, by us and by users, it may be the case that this is a usage issue, in which case StackOverflow or Spectrum may be more helpful. 🙏
Please do post a reproduction though and I’ll take a look 👍

You were correct, this was a case of usage error. The issue is resolved, and it was not because of Styled Components. Thanks for the quick response though =)


KAFKA-6729: Reuse source topics for source KTable's materialized store's changelog

In InternalTopologyBuilder#topicGroups, which is used in StreamsPartitionAssignor, look for book-kept storeToChangelogTopic map before creating a new internal changelog topics. In this way if the source KTable is created, its source topic stored in storeToChangelogTopic will be used.

Added unit test (confirmed that without 1) it will fail).

MINOR: removed TODOs that are related to removed KStreamBuilder.

MINOR: removed TODOs in StreamsBuilderTest util functions and replaced with TopologyWrapper.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@mjsax @bbejeck @xvrl for reviews.

retest this please

@mjsax addressed comments.


Publishing failed - When deploying Azure Function App V1 from Visual Studio

Hello there
I have an Azure Function V1 whihc has SharePointPnPCoreOnline nuget library package. This package don't work on Azure Function higher than V1. The solution works fine when running it locally but when i try to deploy to Azure, it create the function then fails.
I understand by default it create App Service function as V2. So i manually change the version setting back to V1 in Function app settings, then run the publish from VS again, but this still fails. This is the message from my output window:
1>------ Build started: Project: DMSQueueTrigger, Configuration: Release Any CPU ------
1>C:\DMSQueueTrigger\DMSQueueTrigger\DMSQueueTrigger.csproj : warning NU1608: Detected package version outside of dependency constraint: Microsoft.NET.Sdk.Functions 1.0.24 requires Newtonsoft.Json (= 9.0.1) but version Newtonsoft.Json 11.0.1 was resolved.
1>C:\DMSQueueTrigger\DMSQueueTrigger\DMSQueueTrigger.csproj : warning NU1608: Detected package version outside of dependency constraint: Microsoft.Data.Services.Client 5.6.4 requires Microsoft.Data.OData (= 5.6.4) but version Microsoft.Data.OData 5.8.4 was resolved.
1>DMSQueueTrigger -> C:\DMSQueueTrigger\DMSQueueTrigger\bin\Release\net461\bin\DMSQueueTrigger.dll
1>Done building project "DMSQueueTrigger.csproj".
2>------ Publish started: Project: DMSQueueTrigger, Configuration: Release Any CPU ------
2>Detected package version outside of dependency constraint: Microsoft.NET.Sdk.Functions 1.0.24 requires Newtonsoft.Json (= 9.0.1) but version Newtonsoft.Json 11.0.1 was resolved.
2>Detected package version outside of dependency constraint: Microsoft.Data.Services.Client 5.6.4 requires Microsoft.Data.OData (= 5.6.4) but version Microsoft.Data.OData 5.8.4 was resolved.
2>DMSQueueTrigger -> C:\DMSQueueTrigger\DMSQueueTrigger\bin\Release\net461\bin\DMSQueueTrigger.dll
2>DMSQueueTrigger -> C:\DMSQueueTrigger\DMSQueueTrigger\obj\Release\net461\PubTmp\Out
2>Publishing C:\DMSQueueTrigger\DMSQueueTrigger\obj\Release\net461\PubTmp\DMSQueueTrigger -<PHONE_NUMBER>0928466.zip to https://dms-sb-queuetrigger.scm.azurewebsites.net/api/zipdeploy...
2>The attempt to publish the ZIP file through https://dms-sb-queuetrigger.scm.azurewebsites.net/api/zipdeploy failed with HTTP status code RequestTimeout.
Also this from the log file:
09/01/2020 15:34:09
System.AggregateException: One or more errors occurred. ---> System.Exception: Publishing failed.
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.Publish.Framework.Model.DefaultPublishSteps.<>c__DisplayClass26_0.b__2()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Publish.Framework.Model.DefaultPublishSteps.d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Publish.Framework.ViewModel.ProfileSelectorViewModel.d__202.MoveNext()
---> (Inner Exception #0) System.Exception: Publishing failed.<---
System.Exception: Publishing failed.
===================
Can you please give me a pointer or how to deploy Function App V1.
Thanks

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


[feat] Use In Cluster Config to remove dependency on a kubectl container running kubectl proxy when running pod inside a K8s Cluster

When running inside a pod , with service account tokem kubenetes clients can use InClusterConfig
// kubernetes gives to pods. It's intended for clients that expect to be
// running inside a pod running on kubernetes. It will return ErrNotInCluster
// if called from a process not running in a kubernetes environment.

This obliterates the need to include a kubectl container for running kubectl proxy

@kylemcc can you please have a look

Thanks! I'll take a look this weekend

🧟  any possibility that this will just merge and work after 18 months? @kylemcc

🧟 any possibility that this will just merge and work after 18 months? @kylemcc

Let's find out...


Add visual indication for integrated terminal bell

Implement some or all settings for making the (integrated) terminal bell:

focus the terminal
highlight the terminal
highlight the corresponding VS Code instance in the taskbar

Background and motivation
Some terminal emulators (e.g. mintty) support setting the terminal bell to give a visual indication either by flashing and/or highlighting the application window. This is a really handy feature, because hearing a terminal bell without knowing where it comes from can be frustrating. From an accessibility perspective this feature is not only handy, but actually essential.

Upstream: https://github.com/xtermjs/xterm.js/issues/1161

We have this now, it shows up as a yellow/warning color ⚠ on the tab.


Youtube video buffering stagnation

First observed on 2024-08-02 at
https://www.youtube.com/watch?v=89dGC8de0CA&t=100s
Workaround:

for locally installed extension from master branch: comment out this.wrapEval(); line and rebuild.
for chrome store installed extension (v1.0.4): disable extension untill resolved or better solution found.

The fix tactic currently in mind is to wrap eval only if eval panel is enabled... or find alternative site... not sure

Wrapping eval function can be toggled on demand via dropdown menu, afterwards full refresh advised.
To not break sites having such issues for unaware users the default is off.


[WIP][ART-3530] create an ironic plashet

paired with https://github.com/openshift/ocp-build-data/pull/1443/files this creates a 4.11-ironic plashet next to4.11 and 4.11-el8.

When transitioning to el9, how likely is it that we need to have two repositories up for a brief time simultaneously? Would it make sense to namespace the repository name with the rhel-version (both in local buildvm cache and the ose repo (plashet)?

good point @joepvd i don't know that we'll need it (ironic may be able to transition all at once without too much disruption) but a little future-proofing can't hurt.

needs a good deal more supporting work in other areas (rebuild job, elliott etc) but I think this piece of work is ready.

another good catch, it looks like we don't have auto-signing enabled for this PV yet (I attached to our signing advisory, nothing got signed).
however we don't need that before code freeze, and I don't think we need to wait on that now.

@sosiouxme Yeah, but the problem is setting --arch ${release_arch} signed without auto-signing will probably cause doozer hanging there forever.


pkg/build: Support building Linux on ppc64le

Right now pkg/build only supports building Linux on x86. Adapt it so it builds on ppc64le too.
We might also need to look at supporting cross-compilation...
Working on this, I expect to submit a PR in the next few days.

I've gotten the build scripts to successfully generate a disk image with grub-ieee1275, which is what we probably want to use with the pseries qemu machine model. If we ever want to implement support for the powernv machine model down the track we might need to do something a bit different.
I'll tidy things up and submit some patches soon - I haven't taken a look at cross-compilation yet.

Great!
The build function should know the target arch and you can get the host arch from runtime.GOARCH if necessary. If we have a cross-build from amd64, then we could setup ppc64 qemu instances on syzbot in future (that's in plans for other reasons: more emulated devices, arm64).
Note: the current linux build does lots during build (that create-gce-image.sh script). The current trend is to move as much as possible offline and give necessary artifacts to pkg/build in imageDir so that it does only the necessary minimum of work to install the kernel. For qemu it's not even necessary to install the kernel, because we could use the injected boot, so build procedure could just build and copy-out kernel. But at the time I did not know what I am doing and what I want and what are the option. Preparing the image once offline makes things much simpler. I mean you don't have to mimic everything we are doing now.

I'll take a look at cross-building then - it really shouldn't be too hard at all.
Re injecting the kernel: I was thinking about that - using qemu's -kernel option was the first thing that came to mind and indeed is how I've been running syz-manager manually so far. I'm not sure what my longer term plans might be if we ever decide we want to run this on some kind of cloud, and whether keeping kernels inside the disk image is better for that or not...

I'm not sure what my longer term plans might be if we ever decide we want to run this on some kind of cloud, and whether keeping kernels inside the disk image is better for that or not...

The build procedure also knows target VM type. So these are not conflicting. For qemu it could build the kernel and return, for other also proceed to installing kernel into the image.

I've been busy with other things for the last few weeks - for now I'm going to go with the existing approach of installing the kernel in the disk image. But we should definitely work on handling the qemu case differently. Also the script name references GCE and that's becoming increasingly inaccurate... should that get renamed or should we find a way to separate non-GCE cases?

I've been busy with other things for the last few weeks - for now I'm going to go with the existing approach of installing the kernel in the disk image. But we should definitely work on handling the qemu case differently. Also the script name references GCE and that's becoming increasingly inaccurate... should that get renamed or should we find a way to separate non-GCE cases?

Yes, GCE is a inaccurate. The script is more "build complete image" (with user-space system and kernel, bootable, etc). The name is historical. I don't mind if we rename it.
Also, there is lately a trend of moving more logic out of pkg/build. I.e. for *BSD OSes we now supply a template image as input and only install the new kernel in pkg/build. It's more flexible, faster and has less runtime dependencies. The way pkg/build works for linux is also historical.


Fixes: #715 Dark mode  / light mode fixed

Related Issue
Fixed the dark and light mode , not working properly , some element were not visible .
Fixes:  #715
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Before :
Here button was not visible

After :  And also visible in dark and light mode

Here Text was not visible

After:

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes. Make sure to attach before & after screenshots in your PR.]
Checklist:

[x] I have made this change from my own.
[ ] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@MOHIT-IITP
Your pull request has been successfully merged! Don't stop here—continue contributing by addressing more issues and aiming to become a top contributor. Exclusive swag awaits for those who go the extra mile!
Great contribution to GSSOC'24 EXTENDED! 🎉


Error building jupyterlab

I'm having trouble getting an end to end build to work with the current tree.
Everything is OK through to the last command but then this command:
jupyter lab build

fails with:
[LabBuildApp] > node /data/tools/anaconda3/envs/beakerx_again/lib/python3.7/site-packages/jupyterlab/staging/yarn.js run build:dev:minimize
[LabBuildApp] yarn run v1.15.2
$ jlpm run build:dev
$ jlpm run build
$ webpack
ModuleNotFoundError: Module not found: Error: Can't resolve '../lib/tree.js' in '/Volumes/Space2/tools/anaconda3/envs/beakerx_again/share/jupyter/lab/staging/node_modules/beakerx-jupyterlab/dist'
    at /Volumes/Space2/tools/anaconda3/envs/beakerx_again/share/jupyter/lab/staging/node_modules/webpack/lib/Compilation.js:925:10
    at /Volumes/Space2/tools/anaconda3/envs/beakerx_again/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:401:22
    at /Volumes/Space2/tools/anaconda3/envs/beakerx_again/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:130:21
    at /Volumes/Space2/tools/anaconda3/envs/beakerx_again/share/jupyter/lab/staging/node_modules/webpack/lib/NormalModuleFactory.js:224:22
...

I got it to go a little further by doing this:
cd <anaconda env>/share/jupyter/lab/staging/node_modules/beakerx-jupyterlab/dist
mkdir ../lib
cp -R * ../lib/

(this just copies the files it's looking for to the place that it is looking for them).
However then that just dies with a similar error but looking for a file that is nowhere in the source tree:
ModuleNotFoundError: Module not found: Error: Can't resolve '../lib/td_index.js' in '/Volumes/Space2/tools/anaconda3/envs/beakerx_again/share/jupyter/lab/staging/node_modules/beakerx-jupyterlab/dist'

Any hints to get the build working?

Hi @ssadedin
I've just built jupyterlab and I have not problems with the "jupyter lab build" command. Everything works.
Please try to clone the repo to new directory and run the installation instructions once again.
Additionally please check if we have the same version of yarn and node.
My versions:

yarn --version
1.19.1

node -v
v12.12.0


Using Mandoline with SnapKit 4.0.0

I'm using SnapKit 4.0.0 in my project, and trying to install Mandoline through Cocoapods raises the error:
[!] Unable to satisfy the following requirements:

SnapKit (~> 4.0.0) required by Podfile
SnapKit (= 4.0.0) required by Podfile.lock
SnapKit (~> 3.2.0) required by Mandoline (1.0.0)

I got the same issue.
Is there anyone know how to fix it


Routine maintenance updates

Update key dependencies and test
Setup Github Actions to create issues when new versions of key dependencies are out

Langenium #44

Updated dependencies to latest, had to skip three.js 168 for now as other dependencies used don't support it yet

TODO:

Update three.js
Ensure README contains update procedures


CIDR array response reversed to properly deliminated string

Newer to JS and thought I would tackle issue #91 .  I realize this makes another set of tests fail which I can correct, just wanted to see if this approach was acceptable.

Hm, this looks good to me but it was years since I last touched JS so I'm not sure how much "best practice" is this. @silverwind any comment?

Overriding built-ins is never "good practice" but I don't see another way, so looking fine to me.

I realize this makes another set of tests fail which I can correct, just wanted to see if this approach was acceptable.

Looks like the CI is green, which tests are failing here?

correctly detects IPv4 and IPv6 CIDR addresses is failing due to the additional function present in the object when the equality check is done.  Interesting that travis says it's green when you can clearly see the failed assertions in the same output.

OK, hm, that seems like a serious issue because it breaks the public interface. We need another way.

True the public interface changes, it's vanilla array vs a array w/the toString built-in overridden.  If this change needs to be made, I am not sure I see another way as @silverwind pointed out, besides just punting on this issue.

Maybe a separate method?

Make them non-enumerable properties:
diff --git a/src/ipaddr.coffee b/src/ipaddr.coffee
index 4c63563..3c31872 100644
--- a/src/ipaddr.coffee
+++ b/src/ipaddr.coffee
@@ -452,9 +452,11 @@ ipaddr.IPv4.parseCIDR = (string) ->
   if match = string.match(/^(.+)\/(\d+)$/)
     maskLength = parseInt(match[2])
     if maskLength >= 0 and maskLength <= 32
       parsed = [@parse(match[1]), maskLength]
-      parsed.toString = () -> this.join('/')
+      Object.defineProperty(parsed, 'toString', {
+        value: () -> this.join('/'),
+      })
       return parsed

   throw new Error "ipaddr: string is not formatted like an IPv4 CIDR range"

@@ -511,9 +513,11 @@ ipaddr.IPv6.parseCIDR = (string) ->
   if match = string.match(/^(.+)\/(\d+)$/)
     maskLength = parseInt(match[2])
     if maskLength >= 0 and maskLength <= 128
       parsed = [@parse(match[1]), maskLength]
-      parsed.toString = () -> this.join('/')
+      Object.defineProperty(parsed, 'toString', {
+        value: () -> this.join('/'),
+      })
       return parsed

   throw new Error "ipaddr: string is not formatted like an IPv6 CIDR range"

@silverwind 's suggestion causes this to behave as desired.  I've updated the PR with this change.  Thanks.

Thanks!


moved namespaces do not receive the RBAC permissions of their new project

Rancher Server Setup

Rancher version:2.6.4
Installation option (Docker install/Helm Chart): Docker

Information about the Cluster

Kubernetes version: 1.22.7
Cluster Type (Local/Downstream): bare metal

User Information

What is the role of the user logged in? ADMIN

Describe the bug

moved namespaces do not receive the RBAC permissions of their new project
To Reproduce

create a new project and assign project owner roles to some users
move an existing namespace from another project into the new project
try to launch jobs/pods as a user that's a project owner on the new project
Result
access denied
Expected Result
successful job/pod
Additional context
workaround seems to be to move the namespace to the new project and then to add the users/roles to the project but for an existing project this means removing and re-adding all users/roles and work/jobs/pods fail to launch until the needed service accounts have bee re-added

this issue still is still present in 2.6.6


Unhandled Exception in _PlutoLazyPaginationState.setPage

Describe the bug
An unhandled exception occurs when navigating to another page while PlutoLazyPagination widget is still processing an async request :
Unhandled Exception: 'package:flutter/src/widgets/scroll_controller.dart': Failed assertion: line 170 pos 12: '_positions.isNotEmpty': ScrollController not attached to any scroll views.
#0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:51:61)
#1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:40:5)
#2      ScrollController.jumpTo (package:flutter/src/widgets/scroll_controller.dart:170:12)
#3      _PlutoLazyPaginationState.setPage.<anonymous closure> (package:pluto_grid/src/plugin/pluto_lazy_pagination.dart:183:45)
<asynchronous suspension>

To Reproduce
Steps to reproduce the behavior:

Create a PlutoGrid with a PlutoLazyPagination widget in it.
Mock the fetch request to some long operation, for example:

await Future.delayed(const Duration(seconds: 5));

While the async operation is working try to navigate to some other screen.

Expected behavior
Check if the ScrollController is actually attached to a view before attempting to do the jumpTo() action.
Additional context
The place where the exception happens is in the pluto_lazy_pagination.dart file, at the setPage() function, line 183 :
void setPage(int page) async {
    if (_isFetching) return;

    _isFetching = true;

    stateManager.setShowLoading(true, level: PlutoGridLoadingLevel.rows);

    widget
        .fetch(
      PlutoLazyPaginationRequest(
        page: page,
        sortColumn: stateManager.getSortedColumn,
        filterRows: stateManager.filterRows,
      ),
    )
        .then((data) {
      stateManager.scroll.bodyRowsVertical!.jumpTo(0); // <-- Unhandled Exception here

      stateManager.refRows.clearFromOriginal();
      stateManager.insertRows(0, data.rows);

      setState(() {
        _page = page;

        _totalPage = data.totalPage;

        _isFetching = false;
      });

      stateManager.setShowLoading(false);
    });
  }

It seems that when the async operation is invoked, there is a possibility that when the then() callback is called the PlutoGrid to be already removed from the screen.
One possible solution for resolving the issue can be to just check if the widget is still mounted. Something like this:
if(mounted) {
            stateManager.scroll.bodyRowsVertical!.jumpTo(0);

            stateManager.refRows.clearFromOriginal();
            stateManager.insertRows(0, data.rows);

            setState(() {
              _page = page;

              _totalPage = data.totalPage;

              _isFetching = false;
            });

            stateManager.setShowLoading(false);
          }

Issue is fixed with PR - #830


Uploading a malformed pipeline yaml results in a blank page

Closes: #1522
Description
#1522
Error page is being displayed instead of redirecting it to blank page

How Has This Been Tested?
Import this pipleline yaml file
TestPipeline01-modified.yaml.txt
and check for the error page

Test Impact
no test coverage

Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@kywalker-rh can you please take a look at this?

yeah I do agree with you @manaswinidas , but in this scenario , what is happening that the error is unknown until it reaches the graph tab (which is  in https://github.com/opendatahub-io/odh-dashboard/blob/main/frontend/src/concepts/pipelines/topology/core/PipelineVisualizationSurface.tsx )
to get what  you have suggested , I will need to move the error useState somewhere in pipelineDetails and pass it as props
@andrewballantyne any suggestion on this?

I assume this is an error for both the graph and the yaml, correct? Is there anything a user can do to fix the issue, other than deleting the pipeline and uploading a new one? If there is an action the user can take to fix it we should make that clear and provide a link to allow them to do it. If there is nothing they can do to fix it, and they can only delete it, then we can include an action to delete it.

I assume this is an error for both the graph and the yaml, correct? Is there anything a user can do to fix the issue, other than deleting the pipeline and uploading a new one? If there is an action the user can take to fix it we should make that clear and provide a link to allow them to do it. If there is nothing they can do to fix it, and they can only delete it, then we can include an action to delete it.

How do they fix it @kywalker-rh? Not in our UI obviously -- but if we just lock them down, say some vague error that is not directly related to their Pipeline (more about the Topology having rendering issues), shouldn't we give them the opportunity to see the error and view the yaml in one spot?
@manaswinidas great suggestion!

@andrewballantyne I was trying to understand the issue more. I don't have a full understanding of the possible error state, so its hard to prescribe something. If its a yaml issue, and we can provide them with a good error, and a way to view the yaml (even better if we can highlight the offending lines) then that is definitely the best option. If its more complicated than that maybe we should chat in a thread.

@andrewballantyne I was trying to understand the issue more. I don't have a full understanding of the possible error state, so its hard to prescribe something. If its a yaml issue, and we can provide them with a good error, and a way to view the yaml (even better if we can highlight the offending lines) then that is definitely the best option. If its more complicated than that maybe we should chat in a thread.

Whoops, wrong ticket, deleted my other comment...
We have no idea where the issue is @kywalker-rh -- but we cannot render the graph. In this case, it was the name of a task not linking up to another task... so when the nodes were rendered the PF Topology was like "yeah, no that's invalid data" and this stops it from whitescreening.
But I think we want the YAML tab, so they can try to make sense of it. If they can't, they are already in a bad place. It's a bad Pipeline YAML.

Okay, I'm getting all my wires crossed today 🤦
Das was referencing moving away from the tabs (I thought she was saying we should add them lol)... no this is all good across the board... just going to approve this lol.


Delete unnecessary files in git

.class files are binary, so not recommended in git.
Configuration files from the local IDE are not recommended either.
Also added a gitignore to avoid this effect in the future.

Thanks melascuco.


AST nodes missing properties if code does not compile

To get the sourceFile to walk for our linter, we're using ts.createProgram().getSourceFile() to get the AST for a given file -- since using ts.createSourceFile doesn't seem to attach the source file to all the child nodes, which causes code to fail if you call getChildren or getText on the node. However, if the read-in typescript code doesn't compile, for any reason, createProgram will also not attach the source file to most of the nodes, resulting in the same errors. Is there a reason why the source file is not attached to all the nodes when the code does not compile? Can you guys fix this, please?
Thanks!

Using ts.createSourceFile doesn't seem to attach the source file to all the child nodes

Sorry, could you explain what you mean here? Are you trying to get the source text from a given Node and then getting a crash?

I'm trying to do various things on a given node -- among them get the children of a node (via getChildren or getChildAt) or get the text of a node (via getText) or get the position of a node (via getStart or getEnd) all of which gives a crash if the source file is not attached to the node. It's pretty clear from the error messages and a little bit of digging this is because they do this based on the source file, but the source file is not there.

So much of that functionality requires parent references to be bound so that we can reach up to the SourceFile; however, parent binding occurs in the binder, which is only triggered when using createProgram.
However, we know this is a pain point. Binding has some unnecessary overhead, and you shouldn't need to do it if all you want is a syntactic view of the code.. In the upcoming 0.5 version of the API, we've changed the signature of createSourceFile:
function createSourceFile(filename: string, sourceText: string, languageVersion: ScriptTarget, setParentNodes = false): SourceFile

You'll be able to call createSourceFile with the setParentNodes flag set to true and get the desired behavior.

Sure -- it's good to know that that functionality is coming in the next version of the API, thank you for that -- but this doesn't help with the fact that when we do use createProgram (as we do now), but the file doesn't compile, it still won't attach parent nodes. Is there a way to fix/deal with that, at all?

We are looking into updating the API so that a call to getParent() would cause all parents to be linked correctly. i think is is a fair request to make. reopening.

@gscshoyru  you just need to call program.getTypeChecker(), this will force all parent pointers to be set as part of initializing the checker. the creating is not a lot of work, so you are not incurring much of additional costs here.

Oh, goody, that seems to do the trick. Thanks!

Great, glad to hear it!
For the record, I don't know if we'd be able to lazily populate parent pointers in a clean way, so I'm not sure that's something we'll end up doing. We'll have to discuss it more.


Issue in Set Up for the Mobile Development Kit (MDK) ( US & AP)

Hi Colleagues,
We are testing Starter scenarios for the September Month cycle.
Here, we are not able to create New Mobile app for both US & AP region.
Tutorial link : https://developers.sap.com/group.mobile-dev-kit-setup.html
Trail account link :  https://cockpit.hanatrial.ondemand.com/trial/#/home/trial
Steps to reproduce:
1.In your web browser, open the SAP BTP trail cockpit : https://cockpit.hanatrial.ondemand.com/trial/#/home/trial
2. Provide the login details to log on to your account.
3. Click subaccount available in your global account.
4. In the left pane, choose Services → Service Marketplace.
5. Search for Mobile, and click Mobile Services tile.
6. Choose Support to open SAP Mobile Services Cockpit.
7. The SAP mobile service cockpit dialog, Select API Endpoint, appears. Before you click on Login, make sure to provide the correct API endpoint belongs to your BTP subaccount.
8.  click on Login to continue.
9. The current API Endpoint value appears. Choose the relevant Organization and Space from the dropdown list, and then choose
Open
10. Navigate to SAP Mobile Services cockpit.
11. On the home screen, click Create new app or navigate to Mobile Applications → Native/MDK → New.
Here,

We are getting Type of the Application as No data , Click on next
After entering ID & Name under Basic Info License type lite is disappearing
After we are unable to proceed further steps as next button is not working.

Please find the screenshot & recordings for your reference.

https://github.com/user-attachments/assets/9142c0a4-a2d9-4034-ba5a-40b8e4c21880
Thanks & regards,
Akash

@Akashbm964 Pls. check again. I am able to see the required information in my ap21 trial. See attachment.

Hi @jitendrakansal ,
I am able too see the type of Application page

@Akashbm964 are you now able to proceed and app creation works?

Yes I could be able to create MDK Apps & it got created .
But, I got issue with SAP build code service in AP region
I am unable to start SAP Build code as I am getting error Some entitlements are missing

@Akashbm964 Is your trial in US10? or AP region?
Please note that The trial version of SAP Build Code is currently only available in the US10 region. See this information here https://developers.sap.com/tutorials/build-code-setup.html

The trial version of SAP Build Code is currently only available in the US10 region, it is not available in AP21, hence you see the entitlement missing message.
You can delete your current trial account and create a new one in US region to continue.

Hi @jitendrakansal ,
Thanks for the update .
SAP Build Code was available in AP region till last month.
May I know, Is there any specific reason for removing it in AP region ?


Restructure site compatibility-impacting changes table for stable and experimentation columns

Docs Build status updates of commit f687221:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 7bf0def:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 9a093eb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 331228b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 0bae423:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/web-platform/site-impacting-changes.md
:white_check_mark:Succeeded

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

Received #sign-off offline and merging.


Ensure all supporting Azure resources send telemetry data to Log Analytics

As a project developer, I want all Azure resources to send diagnostic information to the Log Analytics Workspace, so that we can begin analyzing collected telemetry data for those resources

Mentioned in #190


BZ-1241810: enforce cache control on HTTP headers (html is not enought)

http://github.com/uberfire/uberfire-extensions/commit/e9e1e7bfd


Added the ability to automatically apply isnull filters when model …

…field is nullable
Closes: DNE
What's Changed
Added the ability to automatically apply isnull filters when model field is nullable
TODO

[x] Explanation of Change(s)
[x] Added change log fragment(s) (for more information see the documentation)
[ ] Unit, Integration Tests
[x] Documentation Updates (when adding/changing features)

@glennmatthews I know we spoke about another approach, it quickly got complicated to consider what to do in various situations, such as an empty string vs null check on a char or 0 on an integer. This seemed to be a reasonable approach considering that it is basically 5 lines of code (not including comments, blackified spacing, tests, etc.), follows an established pattern, and works for plugins, api, graphql immediately.
That being said, I didn't want to spend the time building tests without confirmation that this approach makes sense.

See also #1905.

@glennmatthews, thanks for the reference, didn't know about that PR. This should be different since we are doing a if field.null and field.get_internal_type() in constants.FILTER_LOCAL_FIELDS: check, so only if the model field is nullable will this show up.

For reference, the alternate approach that I'd personally prefer would be to extend the existing "exact" filters (e.g. name, name__n, ip_version/ip_version__n, etc.) to recognize the existing NULL_CHOICE_VALUE setting, so that the filter would be ?name=null/?name__n=null rather than ?name__isnull=true/?name__isnull=false.
My preference for that approach is that we already have a tremendous number of uniquely named filter variants, and not wanting to worsen that problem by adding yet more of them.

It would pose some problems on the filter form presentation though, as there's no way for a number input field to show a "null" value string, etc. So this approach has its advantages as well.

This was the issue. It seemed like a rabbit hole, and at least we have documented this in the future to fix. All in all, I actually working with it, I did genuinely prefer this approach.


How to extract font size with words ?

i can check that pdfminer provides output in form of text,html,xml and tag.
In text file output it is difficult to differentiate headings with next sentences.
I thought if i can get font size for words i can use it.
I tried XML but font size is available for each and every letter instead of a word.
Is there a simple way out to separate headings with next sentences?
Thanks !

Hi @tuner007,
There is no way for pdfminer.six to get the font-size of words, since for each word the font-sizes of each of the letters can differ.
You can create your own logic on top of the output of pdfminer.six by programatically extracting the text. For example, to get all the characters with their font sizes you can do the following:
(Note I am using the font-size-test.pdf from the samples directory in the pdfminer.six repository. But you can use any pdf you want)
from pdfminer.high_level import extract_pages
from pdfminer.layout import LTTextBox, LTChar

path = '/home/pieter/projects/pdfminer-upstream/samples/font-size-test.pdf'
for page in extract_pages(path):
    for text_box in page:
        if isinstance(text_box, LTTextBox):
            for line in text_box:
                for char in line:
                    if isinstance(char, LTChar):
                        font_size = int(round(char.size))
                        heading = 'is heading' if font_size > 16 else ''
                        print(char.get_text(), '-', font_size, heading)

The start of the output is:
O - 28 is heading
S - 28 is heading
X - 28 is heading
  - 28 is heading
S - 28 is heading
t - 28 is heading
y - 28 is heading
l - 28 is heading
e - 28 is heading
s - 28 is heading
  - 28 is heading
1 - 12
2 - 12
  - 12
1 - 12
2 - 12
  - 12
1 - 16
6 - 16
  - 16

An example for extrac


Enable to add adapter to Moshi

The library uses an global Moshi instance that can't me modified.
object MoshiUtils {     val moshi: Moshi by lazy {         Moshi.Builder()             .build()     } }
A fast dirty solution would be just changeing it to var so that we could modify it and add adapters.

Hey @mateuy-dev
Sorry for the late reply. While I can make this change easily, I am curious about the use case. Why would you want to modify the Moshi instance? If it's a common use case, I can provide a better construct. Could you give me an example for this pls?

I see two upvotes on the issue, and I think that's a good signal that someone else also aligns with your thoughts :)
I've added a setMoshi function to the retrosheet interceptor. You can override the Moshi behavior using this construct from 2.0.2

Thanks.
If I remember it correctly, I needed to add a custom adapter.


Prevent naming collisions with native qcodes attributes.

This commit adapts the node tree generation to append a tailing underscore to parameter names that colided with native qcodes attribute on the Instrument/Node classes. Since QCoDes simply ignores attempts to add colliding names and just raises a warning, this change is not breaking.
Currently only the name log from /zi/debug/log is colliding but this fix also works for future collisions.

Thanks @tobiasah I was meaning to submit a bug for this after I made the change to qcodes. This seems like a good fix

@tobiasah It would be great to see this merged and in a release along with the python 3.7 drop pr if possible

@tobiasah It would be great to see this merged and in a release along with the python 3.7 drop pr if possible

done https://pypi.org/project/zhinst-qcodes/0.5.4/


How does the reported 90.93 reported?

Thanks for sharing this nice work!
I am wondering how is the 90.93 reported? Is it the mean value of the system performance under different random seeds or the best result among several random seeds?
Thank you very much!

Hi,
Yes, this is an average over several experiments using different random seeds. There was a bit of variance. In particular, the best results on the validation set were often very close, but the score on the test set associated to these best scores on the validation set were sometimes quite different (I guess the validation set was a bit small). Results on the test were oscillating between 90.4 and 91.3 or something like that.

Thank you very much!


Fix Artifacts and resource_path

cc @etpinard

I think this should work now. It's kinda scary knowing if anything was missed we're a bit screwed with the Julia Registrator 😱

Ok great!
Looks like we'll "need" to install julia during the test workflow to make the tests pass:
https://github.com/etpinard/dash-textarea-autocomplete/runs/4526678687?check_suite_focus=true
It's probably not a bad idea to run a few Julia tests, so installing julia in the CI workflow might be worthwhile.
But, if ever we want to make a PR to dash.py to make its dash-generate-component command implements Artifacts, we'll need to rewrite this step in python. So perhaps we try to rewrite the julia script in python now :thinking:

F A N T A S T I C
Looks like things are working:

:tada: :tada: :tada:

Ok since Julia is included in the image we use in the tests.yml workflow. Let's not "waste" time converting the script to python for now. It might be nice to add a Julia test, something like
julia -e 'using Pkg; Pkg.add(url="https://github.com/etpinard/,....", rev="$GITHUB_COMMIT"); using DashTextareaAutocomplete'

so that we don't run into problems when we try to register the julia package.

Here we go! :rage1:


migrate bucardo pg article and update links to code changes

What changed, and why it matters
Migrate Bucardo article from Intercom. Still relevant as many are still running PG <10. Updated links to code and samples; removed images and replaced with permalinks to Bucardo repo
Addresses #297

Hope you're cool with me jumping in real quick and fix what Vale complains about, @encima ?

https://github.com/aiven/devportal/pull/1249/commits/4eb36674b4501d2ab0f6178495b2924b44dbd0e1 fixes a merge conflict with .github/vale/dicts/aiven.dic


One AGIC for Public and Private Ingresses

Is your feature request related to a problem? Please describe.
I have 1 AGIC and 1 AKS cluster. In cluster, I have some public exposed applications. Also, In Azure DNS Zone, I have a register "A" for each application to access to them using DNS.
Azure DNS Zone:
app1.mydomain.com -> Public IP App Gateway
app2.mydomain.com -> Public IP App Gateway
Now, I want to have one private application, only accesible from internal network. I will connect to application using a VPN. I want to access to this application using a DNS. Currently, I'm able to access using the private IP.
Azure DNS Zone:
app-private.mydomain.com -> Private IP
I have annotated the Service for private application with this:
service.beta.kubernetes.io/azure-load-balancer-internal: 'true'
I have annotated the ingress for private application with this:
appgw.ingress.kubernetes.io/use-private-ip: "true"
Also, I have configured the private frontend IP in Application Gateway.
I checked that the when ingress is deployed, I can see the rule:
https://app-private.mydomain.com -> app-private:port with an IP in LoadBalancer that is the private IP of App Gateway.
Also, In Application Gateway, a listener is created as private and is associated to the Frontend IP configuration.
But, I'm not able to access to my private application using the dns.
Does AGIC support Private and Public Ingresses in the same time?
Describe the solution you'd like
I would like to access to private/public applications using the DNS and only one AGIC.

Did you find any solution to your problem?

@akshaysngupta Its just sad that this issue was closed without a link to te real issue which I found in the mean time https://github.com/Azure/application-gateway-kubernetes-ingress/issues/948. The real problem ist that AGIC currently does not support private AND public ingresses (IPs) on the same time on the same port (80/HTTP and/or 443/HTTPS).


Avoid using cPickle on Windows

This integrates a change from VMware introduced back in 2013.
The Windows Python multiprocessing module uses the standard Python pickle
module. Unfortunately, SCons compat code renames cPickle to pickle, and
they are slightly different in an incompatible way. End result is that
'import SCons' broke a VMware script called iscons on Windows. This change
tests for os.name == 'nt' and doesn't rename cPickle in this case.
Contributor Checklist:

[ ] I have created a new test or updated the unit tests to cover the new/changed functionality.
[ ] I have updated master/src/CHANGES.txt directory (and read the README.txt in that directory)
[ ] I have updated the appropriate documentation

So you'd like to change upstream SCons to work for code which is VMWare specific?
SCons itself doesn't (Currently) use the dispatch table?
Does your other  PR #3404  need the dispatch table?
Also in PY3 doesn't it automatically load cPickle by default?

So you'd like to change upstream SCons to work for code which is VMWare specific?
SCons itself doesn't (Currently) use the dispatch table?
Does your other PR #3404 need the dispatch table?
Also in PY3 doesn't it automatically load cPickle by default?

Ah okay, that makes sense. I'm happy to keep VMware-specific changes on the VMware side. Maybe I should open by figuring out whether you all want iscons upstream. I'll ask around and see whether it is something that required a bunch of VMware-specific hacks to implement.

So you'd like to change upstream SCons to work for code which is VMWare specific?
SCons itself doesn't (Currently) use the dispatch table?
Does your other PR #3404 need the dispatch table?
Also in PY3 doesn't it automatically load cPickle by default?

Ah okay, that makes sense. I'm happy to keep VMware-specific changes on the VMware side. Maybe I should open by figuring out whether you all want iscons upstream. I'll ask around and see whether it is something that required a bunch of VMware-specific hacks to implement.
But no, the other PR doesn't need the dispatch table. Just iscons.

Maybe bring the discussion on iscons over to the users mailing list or the discord channel? (Slight preference at least for the initial brain dump of what iscons is to be on the mailing list)

So my drive-by comment, not having completely grokked the details (is there a link describing the incompatibility?) is if the way scons uses pickle interferes with the use of the Python multiprocessing module, then there's a problem to deal with.

I looked into it further and found that python 2.7.1 has the following code in Lib/multiprocessing/forking.py:
`
from pickle import Pickler
class ForkingPickler(Pickler):
dispatch = Pickler.dispatch.copy()
@classmethod
def register(cls, type, reduce):
    def dispatcher(self, obj):
        rv = reduce(obj)
        self.save_reduce(obj=obj, *rv)
    cls.dispatch[type] = dispatcher

`
I don't know much about Python dispatch tables so unfortunately I can't say much definitively. Does this help explain?

Ok I get it now. Without this change, SCons code on Windows can't use the cpython multiprocessing module's Process class, specifically Process.start. The reason is that Process.start uses forking.py's Popen class. This class is implemented differently on Windows compared to other platforms; the Windows side uses the ForkingPickler class, which as mentioned above uses the dispatch table.
Core SCons doesn't run into this issue because it doesn't use the multiprocessing module. So I guess it can be considered to be a VMware-specific problem. Let me know whether you want me to close this pull request and continue to apply this patch internally at VMware.

Forcing non cPickle also means slower performance for pickle on windows.
Good to know this is a requirement for multiprocess.
We may have to revisit, but for now I'll close it.


Could not resolve com.goncalossilva:murmurhash:0.4.0.

During the build I got this error:
:shared:iosSimulatorArm64Main: Could not resolve com.goncalossilva:murmurhash:0.4.0.
Required by:
project :shared
Possible solution:

Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

Could you please help me?

Please share your Gradle configuration, particularly where you list the dependency on this library. Also, is there any other error before this one? Thank you.

Closing due to lack of response, but I'd very much like to help debug this in case there is a problem.
The artifact is listed on Maven: https://central.sonatype.com/artifact/com.goncalossilva/murmurhash/0.4.0


cypari2, cysignals: updates

Motivation for this change
Some Sage-related package updates that didn't make it into #114881. For future PRs, the following still needs to be done (after Sage 9.3, probably):

The eclib update requires Sage patches that change the public API (https://trac.sagemath.org/ticket/31443), so I think we should just wait until Sage 9.3 to upgrade it.
The pari update is still not ready upstream (https://trac.sagemath.org/ticket/30801).
gap needs to be updated to 4.11.1.

Closes #103810.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 117123 at 305874ad run on aarch64-linux 1

8 packages built successfully:

python38Packages.cypari2
python38Packages.cysignals
python38Packages.fpylll
python38Packages.pplpy
python39Packages.cypari2
python39Packages.cysignals
python39Packages.fpylll
python39Packages.pplpy

2 suggestions:

warning: unclear-gpl
gpl2 is a deprecated license, check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/python-modules/cypari2/default.nix:62:5:
   |
62 |     license = licenses.gpl2;
   |     ^

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/development/python-modules/cysignals/default.nix:2:3:
  |
2 | , fetchpatch
  |   ^

Thank you @omasanori! Changed cypari2 to reflect that.

Tests are failing on aarch64, but they were already failing before (see the testrun on https://github.com/NixOS/nixpkgs/pull/117017 for example). Any ideas?

If the failure is unrelated I think the fix is out of scope for this PR. You could mark sage as broken on that platform for now to reduce the time hydra and others waste trying to build it and increase the "signal to noise ratio" of the CI.
Is this PR still a work in progress?

@timokau I was doing some more investigation on the aarch64 failures (every test that uses Jmol hangs, apparently), but as you said this is out of scope for the current PR. So this PR is ready now.

As for marking sage as broken on aarch64, I am debugging the jmol hangs at #117465. If I can't find a cause, I'll mark it as broken there.

Thanks for the review and for merging!


Elements from overlays after viewer.drawer.clearOverlays stay in DOM

It may be a desired behavior, but currently in my setup, after loading a new slide and performing viewer.drawer.clearOverlays; all elements added via addOverlay appear directly as  childs, and I heavily rely on overlays in my project.
Should I just remove them in my script, or it's a bug and openseadragon should drop them after clearOverlays?

Hmm...looks like this issue might be related to this line:
https://github.com/openseadragon/openseadragon/blob/master/src/overlay.js#L196
For one thing, it seems we had intended to put it back where we got it from, but instead we're just adding it to the body. Kind of seems like maybe we shouldn't be trying to put it back at all though.


What to display if there is no image?

Current design uses the podcast/episode image by default, can assume that is available for now, this is not a priority.