'@StateObject' used inline will not work unless tagged with '@Previewable' Warning when Building App

Related to #106 & https://github.com/TheAcharya/MarkerData/issues/106#issuecomment-2380016195
Based on this apple developer forum post, this is a known issue in Xcode 16.
I believe this '@StateObject' used inline will not work unless tagged with '@Previewable'  it would be fixed in future versions of Xcode.
Related -
https://www.avanderlee.com/swiftui/previewable-macro-usage-in-previews/
https://stackoverflow.com/questions/60105438/swiftui-preview-provider-with-binding-variables/66175501#66175501
https://www.hackingwithswift.com/forums/swift/new-atpreviewable-and-previewer-issues-for-swiftdata/27357
https://www.reddit.com/r/SwiftUI/comments/18xdv0h/why_dont_we_need_stateobject_since_xcode_15/?rdt=55626
⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Other/ExportDestinationPicker.swift:106:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ExtractView.swift:356:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ExtractView.swift:357:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ExtractView.swift:359:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var extractionModel = ExtractionModel(
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/Label/OverlaySettingsView.swift:143:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/General Settings/FileSettingsView.swift:116:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/General Settings/FileSettingsView.swift:117:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/General Settings/NotificationSettingsView.swift:55:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/General Settings/NotificationSettingsView.swift:56:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ContentView.swift:139:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ContentView.swift:140:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ContentView.swift:142:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var extractionModel = ExtractionModel(
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ContentView.swift:147:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var queueModel = QueueModel(
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/QueueView.swift:184:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/QueueView.swift:185:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/QueueView.swift:187:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var queueModel = QueueModel(
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/Image/SwatchSettingsView.swift:94:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Other/ExportDestinationPicker.swift:106:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ExtractView.swift:356:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ExtractView.swift:357:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ExtractView.swift:359:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var extractionModel = ExtractionModel(
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/Label/OverlaySettingsView.swift:143:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/General Settings/FileSettingsView.swift:116:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/General Settings/FileSettingsView.swift:117:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/General Settings/NotificationSettingsView.swift:55:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/General Settings/NotificationSettingsView.swift:56:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ContentView.swift:139:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ContentView.swift:140:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ContentView.swift:142:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var extractionModel = ExtractionModel(
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Main/ContentView.swift:147:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var queueModel = QueueModel(
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/QueueView.swift:184:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/QueueView.swift:185:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var databaseManager = DatabaseManager(settings: settings)
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/QueueView.swift:187:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var queueModel = QueueModel(
    ^~~~~~~~~~~~

⚠  /Users/runner/work/MarkerData/MarkerData/Source/Marker Data/Marker Data/Views/Detail Views/Image/SwatchSettingsView.swift:94:5: '@StateObject' used inline will not work unless tagged with '@Previewable'

    @StateObject var settings = SettingsContainer()
    ^~~~~~~~~~~~

Hopefully we can address this in future versions of Marker Data.

@milanvarady I have attempted to fix the '@StateObject' used inline will not work unless tagged with '@Previewable' the warnings using ChatGPT.
I have created a separate branch. https://github.com/TheAcharya/MarkerData/tree/Fix-Warning
Based on this initial build, there were no warnings.
I have also created test-build.  On using the application, there were no apparent issues on first glance.
However, could you please check is the code / approach is correct or if it might pose or conflict with our remain codebase.
https://github.com/TheAcharya/MarkerData/compare/main...Fix-Warning
Thank you.

I have fixed the previews and updated some other ones as well.


Feature: Camera Info feature scaling

Hi everyone,
we created a branch in our projects that introduces handling of CameraInfo which are published along with scaled versions of images and their detections, while still displaying them on the original image
A detector for example may use a different aspect ratio or in general a scaled down version of the input and output features in that space while still using the original frame ID. CameraInfo handles most cases already (roi, binning, ....). Such a behaviour can be tested using one of the image_proc nodes like decimate, which publishes an adapted camera_info for that image (along with the decimated image).
What would be the benefit:

No extra debug images need to be published
Easier debugging or visualization

How can it be solved (a first working solution https://github.com/AIT-Assistive-Autonomous-Systems/rqt_image_overlay/tree/use_camera_info_humble ):

Adapt the painter to scale and shift the origin and painting space.
No adaption in the plugins itself needed.

Current identified issues:

Since painting space is scaled, text or other resolution dependent painting may look pixelated.

Can be worked around using a debug image currently
Could be solved by adapting the API with a scaling param or by adding a get_pixel_from_dpi to API for plugins to use (or query it from the painter?).

Currently, the camera_info (as seen in the commits) is set to the namespace of the data topic (plugin topic).

In most scenarios this will be the case
A subscriber is always created (may not be desired).
The topic may reside somewhere else (not in data topic namespace). Which would likely need a configurable param in the GUI.

From our perspective even without fixes for these issues the benefit already outweighs these, but we would like your comments before we start a PR.
PS: We might not have much time to work on this issue besides an initial PR or just may occasionally leave comments, but we will assist as much as we can.

Hi @devrite, thanks for your feature request! I had a look at the branch you posted.
My initial thoughts are against adding this feature and here's why:

The main intent of this plugin is to display detected objects on the image it was detected in. It expects the incoming message to contain all information for it to be drawn onto the image. This feature is essentially asking the message to be drawn onto a separate image from the one it was detected on, where additional information is required (CameraInfo).
This increases complexity of the plugin for a rather special use case.

With your use case, here are some of my alternative recommendations that can be done without changes to RQt Image Overlay:

Create a new debug ROS msg that contains all information to display the message onto the original image. That would be the msg and the CameraInfo. In the overlay plugin you're implementing, do the painter scaling:

void SampleLayer::overlay(
  QPainter & painter,
  const custom_msgs::msg::MsgWithCameraInfo & msg)
{
    painter.save();
    if (msg.camera_info && msg.camera_info.width > 0 && msg.camera_info.height > 0) {
      auto binning_x = msg.camera_info.binning_x == 0 ? 1 : msg.camera_info.binning_x;
      auto binning_y = msg.camera_info.binning_y == 0 ? 1 : msg.camera_info.binning_y;
      auto camera_width = msg.camera_info.width / binning_x;
      auto camera_height = msg.camera_info.height / binning_y;
      auto x_scale = painter.viewport().width() / static_cast<double>(camera_width);
      auto y_scale = painter.viewport().height() / static_cast<double>(camera_height);
      painter.translate(QPoint(msg.camera_info.roi.x_offset * x_scale, msg.camera_info.roi.y_offset * y_scale));
      painter.scale(x_scale, y_scale);
    }

    // Draw msg here

    painter.restore();
}

OR Use coordinates that match the original image in your message.
OR Don't display the messages on the original image, but display them on the modified image

@ijnek ´Thanks four your comments. I still hope though that some version of it may find it to the plugins if not the original. Here are our reasons why iterated. Let me know what you think.
I am not sure if I would say it adds much extra complexity as it hides everything from the underlying plugins and it is not much code. To avoid undesired behaviour (currently I can not really think of any) an GUI-flag could be added (disabled on default) that would enable feature space conversion or use the current fixed behaviour (disabled).
I am not sure if the use case is so special as we ourselves either always rescaled features (for processing or debug display) ourselves, or we did not and further processing was in reduced feature space. Or we added code for debug images, which almost looks the same in all nodes, for the same type of message, which is a little bit redundant and may introduce transformation errors while a tested plugin would avoid that. Besides introducing these nodes or code for debug images may affect live performance (bandwith, memory, cpu). I'm quite sure that most of us have written code to handle just that or started nodes just to display these results on the image resp. rescale images.
In rviz, similar operations are perfomred when features are being reprojected to the camera image from 3D. So 3D based features (which could also be overlayed in rqt) will always need the info (of at least the image being overlayed), creating an extra message for all these messages (vision_msgs) to just contain all meta data seems a little bit tedious. If you think about what TF is doing it is the same: Transform what you get to the space you need it in instead of publishing it to every needed space as well as not publishing the whole TF tree along with the actual message. Besides if you would want to overlay 3D detections you might even need TF access in the plugin.
Actually our contribution could even be improved if you do not want them to be displayed on the original but even smaller image (for bandwith reasons). Also something I have seen a lot when people working with remote devices over slow links or not so reliable links. In this case the plugin would even need to consider the info of the overlayed image too (just like for 3D). But this can be a next step.
If this does not meet your requirements, that is totally fine, we just thought we share that need with more people.
There maybe alternatives that I have not looked into yet. Since plugins they are not bound to the message type in the interface and a new layer for the same message can be created a new plugin base/API resp. just another overlay derived from this as a base.
Thanks for your thoughts!

Will close it for now. If I have time to work on an alternative or anybody has extra ideas, we can reopen it.


[question] Does typedoc supports something like jsdoc tutorials?

Hi,
I'm wondering if typedoc supports something like jsdoc tutorials.
I generated typedoc for one project but haven't found anything related to that.
Tutorials in jsdoc allow a user to add markdown pages that aren't bound to code. It's useful if one wants to add a guide or some examples that don't fit in the README.
thanks

HI @makepanic, currently typedoc does not have a feature exactly like this. See #247 and #63 for related discussions.

Thanks, i'll close this issue


BarChart onPress for each bar

Is there any way to make the onPress function work differently for each bar? Or the onPress function returns something that can be used to identify which bar was clicked?

const handleBarPress = (barData) => {
console.log(barData);
setModalVisible(true); // Open the modal when a bar is pressed
};
onPress={handleBarPress} // Assign the handleBarPress function to onPress prop
/>

<Modal
animationType="fade"
transparent={true}
visible={modalVisible}
onRequestClose={() => {
setModalVisible(false); // Close the modal when pressing the back button
}}
>

You pressed
<TouchableOpacity
style={styles.closeButton}
onPress={() => setModalVisible(false)} // Close the modal when pressing the close button
>
CLOSE

);
using this way you can see what is being returned and make your logic from that.


Question about setting Request referrer

Is there any way to set the referrer for each yielded request?
Sorry if this is the wrong location for a question, but I didn't know where else to post it!
A

Hello, @allan-farrell it's missed in Readme, so thanks for the question.
Well, the Referer is just a header:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer
You can set up any of the headers (include Referer) by the singleton headers method as a settings declaration:
  headers "Referer" => "http://example.com",
          "Whatever" => "whatever value"


Start item cleanup/start dungeon items

still needs ui

Still need to give this a test but would it make sense to have the maps as starting items by default? Would be good for newer players to have the dungeon maps already to help with finding checks.

Still need to give this a test but would it make sense to have the maps as starting items by default? Would be good for newer players to have the dungeon maps already to help with finding checks.

It might make sense to add them to the startitems for the beginner presets


Adapt workaround for spyder UMR to work with newest version of spyder

Yes I know this is horrible but until a fix for disabling this in spyder is available we should try our best to disable it

I'm not familiar with how spyder works under the hood and what this workaround actually does (although i get the general idea of it). and i didn't spend much time on it. So, i just trust you on this :)


Fix Image defaultSource not showing on iOS

Summary
Fix Image defaultSource not showing on iOS.
This bug was introduced somewhere between RN 0.63 and 0.65. On iOS, defaultSource does not show while the image is being downloaded, only if it fails or there's no internet.
Changelog

[iOS] [Fixed] - Fix Image defaultSource not showing on iOS
Test Plan

Ran both debug and release builds on an iPhone 12 pro (iOS 14.6)

@cristianoccazinsp Do you think you could also put together a RNTester example of this behavior to ensure we don't break it again?

@lunaleaps this is my first PR ever to RN so I wouldn't even know where to start! In fact, I'm not 100% sure this is the right place to fix this issue.  When debugging, the issue is clear, the default image is never loaded by default unless there's a network error, so the fix made sense in this location.  However, who ever changed this last may have more idea if this is the right place to add the "load default image" code.
Either way, if you could point me where to start with a RNTester change, I could try.

Gotcha
Yea basically you want to create a reproduction of the issue you were seeing and stick it as an example in here: https://github.com/facebook/react-native/blob/1465c8f3874cdee8c325ab4a4916fda0b3e43bdb/packages/rn-tester/js/examples/Image/ImageExample.js#L243
Have you run RNTester before? Here are the instructions to run in this repo: https://github.com/facebook/react-native/tree/1465c8f3874cdee8c325ab4a4916fda0b3e43bdb/packages/rn-tester#running-this-app
Once you have that app running, you can navigate to the Image examples.
I'd imagine you'd want to construct a way to reproduce the issue.. how did you test it for yourself?

The test was simple, defaultSource simply does not work on iOS and RN 0.65.1; it doesn’t work at all unless you run the app without internet connectivity.
It also has the caveat that if you must run this in release mode as without internet not even the default source image will work (because resources are downloaded from the host when in debug mode)

@cristianoccazinsp Got it, then maybe just adding an image with a default source is sufficient to RNTester.

I will give it a try once I get some free time, although most likely out of scope for me.
Any chance someone with more knowledge of this code can take a look as well to make sure I changed what I was supposed to?

@lunaleaps I made the effort to test the rn-tester app image section.  I believe images with defaultSource where there, even if they didn't work. How are you even testing this?
I made a slight tweak to the test so it loads a larger image and also busts cache in order to ensure the defaultSource image is in fact visible.
I have also confirmed that my PR fixes the issue, and it was otherwise broken without the native iOS change. However, I don't know how are you going to ensure this is tested and detected if it breaks again.
Lastly, and perhaps material for another PR, there are various unhandled promise rejection logs and warnings, the code doesn't seem to be bug-free.

@lunaleaps any updates on this? Think this can make its way up to the next RN version? What's missing?
Thanks!

@cristianoccazinsp it was commited in https://github.com/facebook/react-native/commit/900210cacc4abca0079e3903781bc223c80c8ac7 and it will be included in the next release.


Failure Attempting to create AppServicePlan

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az appservice plan create
Errors:
No module named 'decorator'
Traceback (most recent call last):
python3/dist-packages/fabric/connection.py, ln 5, in <module>
    from invoke.vendor.six import StringIO
ModuleNotFoundError: No module named 'invoke.vendor.six'

...

python3/dist-packages/fabric/connection.py, ln 10, in <module>
    from decorator import decorator
ModuleNotFoundError: No module named 'decorator'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az appservice plan create --name {} --resource-group {} --sku {}

Expected Behavior
Environment Summary
Linux-4.4.0-18362-Microsoft-x86_64-with-glibc2.29
Python 3.8.2
Shell: bash

azure-cli 2.0.81

Extensions:
azure-devops 0.17.0

Additional Context

appservice

Was able to work around using: https://github.com/Azure/azure-cli/issues/13343#issuecomment-624367680
This was a fresh install of WSL, Ubuntu, AZ CLI, everything

could you pls share your previous install story to help trouble shooting? thanks

@Rich-Lang only common package I see included b/w the 2 githhub issues is the azdevops extension can you try uninstalling that extension & trying & also question above on how the original install was done?

I just reproduced the issue on a fresh Azure VM.

Created Azure VM with Image = "Windows 10 Pro, Version 1809"
RDP into box
PS Admin Prompt: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Reboot & RDP again
Install Ubuntu from store (https://www.microsoft.com/en-us/p/ubuntu/9nblggh4msv6?ocid=9nblggh4msv6_ORSEARCH_Bing&rtc=1&activetab=pivot:overviewtab)
From Ubuntu command prompt: sudo apt update
sudo apt install azure-cli
az appservice plan create --name myAppServicePlan --resource-group SQLAzureDotNetCoreDev --sku FREE

@Rich-Lang please install azure-cli following the instructions:https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view=azure-cli-latest
The azure cli comes with the WSL is an old version and not tested by our team. We publish packages to https://packages.microsoft.com/repos/azure-cli. Please install and update from there.


LockClock just went free

https://github.com/LineageOS/android_packages_apps_LockClock/commit/b642154c0afbd5e497c254c4111fbdec6859984f
Hooray!

Note: it still requires gms to run properly, but at least it doesn't include play services anymore.

It does not require gms, there is a reference to "com.google.android.gms", but it can as well be filled with UnifiedNlp. It's just there to detect if there is a network location provider installed, and in case there is none, it will fallback to GPS.

Ah, okay, I wasn't sure about that. Thanks for clarifying.

So is that app 100% free and the apk doesn't include any non-free lib now?

yes, at least for the latest release of LineageOS

Great. Now SetupWizard and Gello... They could also remove unrar and TimeService.

SetupWizard change that makes it free was merged as well and should be present in next nightly.

Was Gello freed?

I have a question, I updated today my LineageOS and the new setup wizard is included.
Before updating I deleted freecyngn.
But now setup wizard crashes and the home button doesn't work.
If I delete the new setup wizard and it's directory everything works five.

With the removal of external_google LineageOS/android@4ac2915366981cc1264381720a83a34d91e313ed, does that mean LineageOS is now free of the proprietary components of Google?

It would be usefull to have a list of non-free parts of LineageOS (if any). Can someone do this please?

@Thrilleratplay @Luca1991
I believe Gello is the only non-free component of LineageOS right now, besides TimeService (which is part of device-specific blobs). It can be disabled by simply removing gello/Android.mk in vendor/cm. It's not in the manifest because it replaces Browser.
Besides that, there's still the built-in anonymous analytics (which aren't as hurtful since they can be disabled), and there's leftover stubbed(?) code for the analytics in Trebuchet.

There is also unrar that is non-free

@mid-kid thank you for clarifiying that. So there is 0 chances for TimeService :(
So the items in the list ATM are:

Gello
Unrar
TimeService (which AFAIK it is not going to be freed)

Correct me if I'm wrong

@Luca1991 That list looks accurate from what I have found.  A few things to expand on.
Gello:
I have been trying to build LineageOS from source and could not figure out why Gello was still being compiled without the respective repos.  I found the answer in vendor_cm where the apk will be downloaded if the source isn't available.  A less obtrusive way to remove it from personal builds is to use vendor_extra like this
Trebuchet
ambientsdk was removed in the last commit LineageOS/android_packages_apps_Trebuchet@7b7aab45b223d0a6d551aebbe3f421c7376343b2
Unrar
While the license is not copyleft, I would still consider LineageOS/android_external_unrar free free and open source.  Seeing that most firmware is not open source, I think this is of little consequence.
TimeService
Correct me if I am wrong here, but while LineageOS/android_vendor_qcom_opensource_time-services is open source it is dependent on Qualcomm firmware blobs which are not.

@Thrilleratplay your post is great!
As for Gello, in theory, the problem relies in ambientsdk, right? I'm not sure what there's in there... I might reverse engineer the aar to give it a look. Maybe we can strip it from Gello. We will see.
As for timeservice, I'm afraid you are correct, and that file is just the "glue" to call functions from the blob.

@Luca1991 I do not see any gerrit submissions or github fork commits to suggest that anyone has started to free Gello.  I am ok with yanking it out of my build but if you want to free it for others, I would also at the Gello build script. It looks like Google Play services are a dependency.

@Thrilleratplay I'm afraid the time-services repo you linked are but a simple header to link with their blobs. The real TimeService can be found in different vendor trees: https://github.com/TheMuppets/proprietary_vendor_oneplus/tree/cm-14.1/oneplus2/proprietary/app/TimeService amongst other apps of it's kind.

@Thrilleratplay I'm pretty sure that the official repo for Gello is this: https://github.com/LineageOS/android_packages_apps_Gello
But I can't find any reference to ambientsdk here.

@Luca1991 That is the source repo but LineageOS's vendor_cm will download and install the prebuilt apk by default or compile from source.  The build process is handled by the Gello build script which looks like it will pull in Google Play services.  There is another repo,LineageOS/android_external_gello-env which does have ambientsdk, I am not sure if this is still being used or is just legacy jetsam.

@Thrilleratplay Ah this make a lot of sense. Well I think that the best way to check this is to reverse engineer the gello.apk and check against ambientsdk. In this way we can be sure that LineageOS/android_external_gello-env is (or isn't) used.
When we know that, we can then try to hack android_external_gello_build to remove unneeded stuff.

@Luca1991 How would I check whether ambientsdk is used? It's possible to extract the apk file with apktool (https://ibotpeaches.github.io/Apktool/).

@zuglufttier quick answer, search LineageOS for ambiantsdk.  Thorough answer, build and grep the code.

@Thrilleratplay sorry for the late reply, I was very busy with work lately.
Anyway I've reverse-engineered the gello.apk (downloaded from https://github.com/LineageOS/android_packages_apps_Gello/releases/), and I can say that:

if the packagename of ambientsdk is "com.cyngn.ambient", then there is no trace of it in smali-code.

in gello.apk the included libs starting with "com." are: "com.android", "com.google" (*), "com.qualcomm" and "com.quicinc", so no trace of com.cyngn.

there is no reference of "ambient" keyword in the Manifest

The included binary libs are: libgiga_client.so, libicui18n.cr.so,  libicuuc.cr.so, libsta.so, libstlport_shared.so, libswe.so, libsweadrenoext_22_plugin.so, libsweadrenoext_23_plugin.so, libsweadrenoext_plugin.so, libswecore.so, libswenetxt_plugin.so, libsweskia.so, libswev8.so, libswewebrefiner.so.

*com.google is also used for GCM

@Luca1991 Not surprised that ambient was removed.  What are the com.google references?  I was more concerned that Google play services are still being built in.
If it can be confirmed that Google play is no longer in Gello, does that mean this project is no longer needed for LineageOS after a certain version?

https://lineageos.org/Changelog-9/
Uhm, rejoice?
Only closed software left in lineageos now is the device binary drivers (which include TimeService.apk). There's still open source but non-free software left, if you're going to be pedantic about that (which imo you should, but android is, well, android), which includes unrar amongst (probably) others.
Now you can freely recommend lineageos to your friends without having to bite your tongue about the proprietary software/tracking it includes. The only "tracking" left is the statistics which can be disabled in the setup wizard IIRC.
Now, if some magic were to happen and all binary drivers were freed...

@mid-kid:

The only "tracking" left is the anonymous statistics which can be disabled in the setup wizard IIRC.

Wasn't that the case for trebuchet? I think they got rid of it here: https://github.com/LineageOS/android_packages_apps_Trebuchet/commit/7b7aab45b223d0a6d551aebbe3f421c7376343b2

@zuglufttier No, I'm talking about the anonymous statistics in CMParts (In the settings app, accessed by Personal -> Privacy -> Anonymous Statistics).


The 'Save' button is enabled if emptying the Id field in the 'Access Policies' dialog

Storage Explorer Version: 1.25.0-dev
Build Number: 20220513.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Monterey 12.3 (MacBook Air M1 2020)
Architecture: ia32\x64
How Found: From running test cases
Regression From: Previous release (1.24.1)
Bug Description

The 'Save' button is enabled if emptying the Id field.
The 'Save' button is disabled if typing an invalid Id then changing to a valid Id.

Steps to Reproduce

Expand one storage account -> Blob Containers.
Create a blob container -> Right click the blob container -> Click 'Manage Access Policies...'.
Click 'Add' -> Empty the Id field.
Check whether the 'Save' button is disabled.

Expected Experience
The 'Save' button is disabled.

Actual Experience
The 'Save' button is enabled.

Verified this issue on the build main/20220615.6. Fixed.


The classRegex doesn't seem to work

Describe the bug
I'm trying to modify the regex so that the sorting works outside of className=.... For example, I want to modify the following regex:
"headwind.classRegex": {
    "css": "\\B@apply\\s+([_a-zA-Z0-9\\s\\-\\:\\/]+);",
    "html": "\\bclass\\s*=\\s*[\\\"\\']([_a-zA-Z0-9\\s\\-\\:\\/]+)[\\\"\\']",
    "javascript": "(?:\\bclassName\\s*=\\s*[\\\"\\']([_a-zA-Z0-9\\s\\-\\:\\/]+)[\\\"\\'])|(?:\\btw[\\.\\sa-zA-Z]*`([_a-zA-Z0-9\\s\\-\\:\\/]*)`)",
    "javascriptreact": "(?:\\bclassName\\s*=\\s*[\\\"\\']([_a-zA-Z0-9\\s\\-\\:\\/]+)[\\\"\\'])|(?:\\btw[\\.\\sa-zA-Z]*`([_a-zA-Z0-9\\s\\-\\:\\/]*)`)",
    "typescript": "(?:\\bclassName\\s*=\\s*[\\\"\\']([_a-zA-Z0-9\\s\\-\\:\\/]+)[\\\"\\'])|(?:\\btw[\\.\\sa-zA-Z]*`([_a-zA-Z0-9\\s\\-\\:\\/]*)`)",
    "typescriptreact": "(?:\\bclassName\\s*=\\s*[\\\"\\']([_a-zA-Z0-9\\s\\-\\:\\/]+)[\\\"\\'])|(?:\\btw[\\.\\sa-zA-Z]*`([_a-zA-Z0-9\\s\\-\\:\\/]*)`)"
}

so that the sorting can work for situations like this:
import c from 'clsx'

const container = c(`w-5 flex`) // should then change to `flex w-5`

<div className={container} />

However, it's unable to sort it

Hey @TheCapedBaldi! The version currently available on the VSCode Marketplace is a few versions behind what’s on this repo, and classRegex doesn’t seem to work on that one. v2.0.0 is available in alpha in #122 and might solve your issue!

Thank you @phacks. I will give it a go at it shortly, and close this ticket once it works 🙏🏻

@homerjam This is the classRegex we use for HAML files (the syntax is similar to Pug’s):
"headwind.classRegex": {
  "haml": [
        {
            "regex": "\\.([\\._:a-zA-Z0-9\\-]+)",
            "separator": "\\.",
            "replacement": "."
        },
        "\\bclass\\s*:\\s*[\\\"\\']([_a-zA-Z0-9\\s\\-\\:\\/]+)[\\\"\\']"
    ],
},

@homerjam In case it helps, here is the classRegex we use for HAML files (the syntax is similar to Pug’s):
"headwind.classRegex": {
  "haml": [
        {
            "regex": "\\.([\\._:a-zA-Z0-9\\-]+)",
            "separator": "\\.",
            "replacement": "."
        },
        "\\bclass\\s*:\\s*[\\\"\\']([_a-zA-Z0-9\\s\\-\\:\\/]+)[\\\"\\']"
    ],
},

Thanks, perhaps I'm using it wrong. Is this inside package.json?

Oh—it’s inside VSCode’s settings. Here’s how to change those: in VSCode, open the Command Panel (⌘⇧P) then search for Preferences: Open Settings (JSON).
You can then edit that JSON file to add the classRegex, save and restart VSCode for it to take effect.


replace JSON format of isb.message with a binary format

Today we have implemented MarshalBinary and UnmarshalBinary to encode and decode using JSON as the intermediary format. We should try out using binary formats.
The code change itself is minimal, we should try encoding/gob first.

[ ] Run the performance test before the change (measure CPU usage, TPS, etc.)
[ ] Make the change
[ ] Compare the performance

This is not a problem for jetstream ISB, because we convert to Jetstream format which considers only the Payload field (which is already a []byte) of the Body. Redis ISB on the other hand passes Body which is a struct that wraps Payload, it uses MarshalBinary and UnmarshalBinary to covert it to a []byte.

Clarified with @vigith more, it turned out to be since Body only has Payload field ATM, we are good to remove the wrapping about Payload and directly expose it in Message. In this way we won't need to ser/deserialize it, neither the performance benchmark is required.


Dynamic menu overlaps the tray

When the tray is configured to display at the bottom or at the right of the screen, a dynamic menu will overlap the tray instead of displaying just next to it.
This only happens with dynamic menus and only if the tray is at the bottom or at the right side of the screen. I'm using Ubuntu 18.04, JWM v 2.3.7. I also tested the latest development snapshot s1685, but the problem persists.
The two attached images may make the problem more clear. In the first image everything is fine, because the tray is at the top of the screen. The rootmenu is not hiding the tray. The problem is visible in the second image. As you can see here, the rootmenu is hiding the tray, which is not desirable.

Placing a TrayButton within a bottom-aligned Tray, where the TrayButton is used to invoke a RootMenu, the initial menu doesn't overlap the tray; however, other menus displayed by Include statements do overlap the tray.
It would be nice if TrayButton or RootMenu included x- and y-offset options.


Remove console.log from packages

There are multiple packages including console.log statements, see: https://github.com/search?q=repo%3ASphereon-Opensource%2FSSI-SDK+"console.log"+language%3ATypeScript&type=code&l=TypeScript
It would be great if they are either

renamed to console.debug
replaced by a library that allows specific debugging like https://www.npmjs.com/package/debug
completely removed.

Actually we are currently working on an event service which will replace all these calls. By default it will use the debug package, but we also provide persitence options. Given it is using events these are completely decoupled. The initial version will probably land this week, then we will start replacing calls.


v1.15 Backports 2024-11-06

[ ] #35784 (@sayboras) :warning: resolved conflicts

Once this PR is merged, a GitHub action will update the labels of these PRs:
 35784

/test-backport-1.15

/test-backport-1.15


Error: watch closed before Until timeout

I followed the "CONTRIBUTING.md" instructions to install binderhub locally. When I ran this command:
helm install --timeout=1000000 --name=binder-test-hub jupyterhub/jupyterhub --version=v0.7.0-f58c7e7 --namespace=binder-test -f /Users/demaasit/binderhub/testing/minikube/jupyterhub-helm-config.yaml
I get the following error:
Error: watch closed before Until timeout
Should I increase the "VERY-LARGE-NUMBER" in --timeout=1000000?

Yes, locally on minikube on my Mac OS.

You could also try removing the timeout arg.

@Emaasit did removing the --timeout arg solve this for you?

Fwiw, I saw this error with JupyterHub on AKS with a very large --timeout. There were hook-image-puller pods left running. When I ran without --timeout, helm install quickly succeeded.

Hi :wave: This is an old issue so I'm closing it. If you have more questions please use the Jupyter community forum https://discourse.jupyter.org/.


vscode-extensions.ms-python from unstable cannot be built due to too new lttng-ust

Describe the bug
vscode-extensions.ms-python fails to build from unstable, as it requires liblttng-ust.so.0, but the latest version of the lttng-ust derivation (2.13.0) provides only liblttng-ust.so.1, and patchelf fails to to fix up the binaries from the vscode extension.
Steps To Reproduce
Steps to reproduce the behavior:

attempt to build vscode-extensions.ms-python from unstable

Expected behavior
Package builds
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
@jraygauthier
@bjornfor
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.14.1, NixOS, 21.05.3001.12eb1d16ae3 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.15`
 - channels(root): `"nixos-unstable-21.11pre313614.09cd65b33c5, home-manager-21.05, nixos-21.05.3001.12eb1d16ae3, nixos-hardware"`
 - channels(dylan): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Yep, I'm getting this one too.

I am as well.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.13.12, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.11`
 - channels(root): `"nixos-21.11pre310725.870959c7fb3, nixos-20.09-20.09.4393.068984c00e0, nixos-hardware"`
 - channels(jskrzypek): `"home-manager, nixos-21.11pre319562.c21ba4f7bb4, nixos-20.09-20.09.4404.a13824fe5e3, nixos-unstable-21.11pre319562.c21ba4f7bb4, nixpkgs-21.11pre318361.a3a23d9599b"`
 - nixpkgs: `/home/jskrzypek/.nix-defexpr/channels/nixpkgs`

On the lttng-ust front, the so name bump was apparently really intended and not a error as can be seen at https://github.com/lttng/lttng-ust/commit/05e8ff1f80c9a6dcd7db559c7a39b4c46e85e2a7.
Here's what I think we should be doing (please correct me if I am wrong):

See if updating the extension to latest fixes to issue.
If not, open a bug in the extension tracker that they should update to latest lttng-ust.
In the meantime, re-introduce the previous version of the lib as lttng-ust-2-10 refering to the derivation from previous commit (before ab2501bd171f2c930ebd3f3bf6b6a1a228477a08 that broke us).
Explicitely assign the extension's lttng-ust dependency to previous version (e.g.: lttng-ust = lttng-ust-2-10;) at callPackage site.

@dcbaker, @Bondrake, @jskrzypek, @ratsclub, @kinnison: Fix available at https://github.com/NixOS/nixpkgs/pull/140564.


 This commit fixes this.
Checklist

[X] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

You may want to target this at the gz-sim7 branch, so that the fix goes into the initial Garden release

You may want to target this at the gz-sim7 branch, so that the fix goes into the initial Garden release

Do I have to create new PR for that?

You may want to target this at the gz-sim7 branch, so that the fix goes into the initial Garden release

Do I have to create new PR for that?

I already did it, you should:
git fetch
git merge origin/gz-sim7
git push origin otore19/addNewLine2

Homebrew failures don't seem to be related to this PR. Merging.


Demo a multi-repo task with 'git switch somebranch'

Is your feature request related to a problem? Please describe
I have not found a reliable way to set specific/different git branches for participating repositories using tasks in the multi-repo front end.
Describe the behaviour you'd like
On multi-repo startup, I would like to manually set the git branch of certain participants to a branch that is NEITHER the same as the branch of the multi-repo front end NOR the default branch of the participant.
Describe alternatives you've considered
I have tried creating tasks in the multi-repo front end's .gitpod.yml file that:
  cd ../<proj-handle>          # Switch to a participant repo workspace
  git switch <desired-branch>  # Change the participant repo branch
  npm install                  # Install NPM dependencies

I change directory command is respected as is the npm install. The git switch command fails with "invalid reference". I have tried writing the task as a multi-line 'command' AND by breaking the lines into appropriate 'before', 'init' and 'command' components.
Additional context
I can perform the git switch manually, in a shell AFTER the new Multi-Repo gitpod session is fully launched. [It's just something else to remember to do.]
I suspect, but cannot confirm, that the timing of Multi-Repo's git clone and set branch activities may not be complete when the tasks are run.

 If I do everything in a single front-end task, the git switch statements are respected.
- name: <front-end>
    command: |
      npm install
      pushd .; cd ../<proj-1>; git switch <proj-1-branch>; npm install; popd
      pushd .; cd ../<proj-2>; git switch <proj-2-branch>; npm install; popd
        :
      pushd .; cd ../<proj-N>; git switch <proj-N-branch>; npm install; popd

@WesleyMConner you can make it a bit more readable like such:
tasks:
  - name: Set custom branches
    command: |
      # Array for REPO:BRANCH name(s).
      # REPO resolves to `/workspace/REPO` directory.
      repo_branch=(
          proj-1:staging
          proj-2:dev
          proj-3:next
          website:temp
      )

      for item in "${repo_branch[@]}"; do {
          IFS=':' read -r repo branch <<<"${item}" || true;
          git -C "/workspace/${repo}" switch "${branch}";
      } done

Also, would it have been helpful if there was a branch parameter for additionalRepositories like this?
additionalRepositories:
  - url: https://github.com/gitpod-io/demo-multi-repo-backend
    checkoutLocation: backend
    branch: dev # Non-existent currently

A 'branch' option on additionalRepositories would be ideal for my use case. I was killing and re-creating a number of Gitpod instances working through the logic. That churn would be less necessary with a built-in facility.
As a rule, there are a few additional things I do, including: (1) Specify the workspaceLocation for vsCode and add subsequently add each participating repo to the referenced file. (2) Setting up a default per-repo terminal (in the proper directory).
I suspect there will always be some of this tailoring. Any out-of-the-box automation is a plus.
I am curious why the git switch couldn't be performed in a per-repo command section. It might be helpful to understand the startup model better to know why insertion in a per-repo command fails. Currently, I'm not using teams; so, haven't played with the teams-specific behavior.

I am curious why the git switch couldn't be performed in a per-repo command section.

If you mean the snippet I shared, it's obviously doable, you're already following a similar method on your initial snippet. My last snippet was aimed at having the whole git switch logic in one task.
Here's another simpler example tailored to address (2) Setting up a default per-repo terminal (in the proper directory).
tasks:
  - name: Frontend
    command: |
      cd /workspace/frontend
      git switch <branch>
      npm install
  - name: Backend
    command: |
      cd /workspace/backend
      git switch <branch>
      npm install

(1) Specify the workspaceLocation for vsCode and add subsequently add each participating repo to the referenced file.

Is this what you mean?

https://www.gitpod.io/docs/configure/workspaces/multi-repo#adding-additional-repo-folders-to-vscode-explorer

the git switch failed with the message "invalid reference"

That's odd 😅
Does checkout help?
What's the output of git branch -v for that git repo directory?


Review use of compute to validate LatLong data with Dask

The initial accessor implementation uses a .compute() call to pull data into memory for validating that a series contains valid LatLong data when using Dask dataframes. This compute call is potentially expensive. We might want to consider removing this validation check for Dask instead.
Without the validation it would become possible for users to create a column as a LatLong logical type, even if the data did not fit the standard formatting. Removing the validation would put the burden on users to make sure their data was valid to prevent other downstream issues.
Current code for reference:
def _is_valid_latlong_series(series):
    '''Returns True if all elements in the series contain properly formatted LatLong values,
    otherwise returns False'''
    dd = import_or_none('dask.dataframe')
    if dd and isinstance(series, dd.Series):
        series = series.compute()
    if series.apply(_is_valid_latlong_value).all():
        return True
    return False

note: adding this to next sprint starting on march 9  @thehomebrewnerd

Support for Dask dataframes is being dropped.


Please don't force admin privileges

Sometimes I want to run the debloat script as a non-privileged user. Some parts silently fail, but that is fine. It still removes user-specific apps, turns off cortana, fixes PDF defaults, etc.
The new update forces the script to quit if it isn't running as an admin, which is much less helpful.

I removed it in the latest update.


Webpack - wait until bundle finished

After adding the plugin config to the webpack config file (see https://github.com/glittle/badi-web3/blob/master/build/webpack.dev.conf.js), when I start the system, it stalls forever and says:
webpack: wait until bundle finished: /__webpack_hmr

If I remove lines 37-39 of that file, it works fine.  The file referenced in the entry exists.
What am I missing?

Thanks, Olivier.
new serviceWorkerPlugin({
^
TypeError: serviceWorkerPlugin is not a constructor

With the .default added, I get the above error.  And removing the new doesn't help, of course.
In reviewing what I'm doing, what I really want is simply the ability to specify a file that will be served from the root of the website beside the 'index.js', both in the dev environment and when the build is run.  Do you have any suggestions on how I can do that? It seems that this is a webpack configuration exercise, but I haven't found how to do it.

My bad, we already have the add-module-exports babel plugin. No need for that .default.

I'm gonna close that issue. Sorry, I don't have time to investigate.

Hi,
I think best would be to at least leave it open for when you'll have time for it. I know how time can be an issue in itself, but this does needs a fix.
Great work with the plugin btw.

I've changed my approach so that I no longer need this plugin... so you don't need to hold it open on my behalf.

Actually, it's could be linked to an issue with webpack@2. I'm looking into that.

Wrong assumption, it's working fine with it: #17.

I have figured our the issue using https://github.com/glittle/badi-web3/commit/2201697.
Actually, there are two issues right here.
1. Wrong parameter
@glittle The path you are providing doesn't match with a file on the system...
-entry: path.join(__dirname, 'special/sw-badi-web3.js'),
+entry: path.join(__dirname, '../special/sw-badi-web3.js')

2. Error swallowed
@rstoenescu as the path argument provided is invalid, the ServiceWorkerPlugin plugin crash and throw an exception. However, that error is never showed. That's most likely due to the custom logic implemented inside build/script.dev.js. I suggest you having a look at the https://github.com/webpack/webpack-dev-server implementation could help.


[BUG] Blob uri isn't converted to str when source path is used as uri

Tracking issue
Closes flyteorg/flyte#5872.
Why are the changes needed?
When FlyteFile is used, TypeEngine converts it to a Flyte Blob literal. There exists a condition that the source path (i.e., path value of FlyteFile) is directly used as the Blob uri, as can be checked here.
This works fine when the source path is originally of type str, or remote_path is explicitly specified. However, it fails when the source path is of type os.PathLike and remote_path is None, just as shown below:
"""
Test the behavior of type transformation of FlyteFile.
"""
from pathlib import Path
from typing import Optional

import flytekit
from flytekit import task, workflow
from flytekit.types.file import FlyteFile

@task
def write_hello_task(
    use_str_path: bool,
    remote_path: Optional[str] = None
) -> FlyteFile:
    path = Path(flytekit.current_context().working_directory) / "hello.txt"
    if use_str_path:
        path = str(path)
        f = open(path, mode="w")
    else:
        f = path.open(mode="w")

    f.write("Hello!")
    f.close()

    return FlyteFile(path=path, remote_path=remote_path)

@workflow
def write_hello_wf(
    use_str_path: bool,
    remote_path: Optional[str] = None
) -> FlyteFile:
    return write_hello_task(use_str_path=use_str_path, remote_path=remote_path)

To reproduce the error, run the following command:
pyflyte run test_flytefile.py write_hello_wf --no_use_str_path

What changes were proposed in this pull request?

Cast source_path to str type before it's served as Blob uri.

How was this patch tested?

path is of type str and remote_path=None

pyflyte run test_flytefile.py write_hello_wf --use_str_path

path is of type str and remote_path="my_hello.txt"

pyflyte run test_flytefile.py write_hello_wf --use_str_path --remote_path "my_hello.txt"

(Solved) path is of type os.PathLike and remote_path=None

pyflyte run test_flytefile.py write_hello_wf --no_use_str_path

path is of type os.PathLike and remote_path="my_hello.txt"

pyflyte run test_flytefile.py write_hello_wf --no_use_str_path --remote_path "my_hello.txt"

Run tests reported in flyteorg/flyte#5872,

pyflyte run examples/data_types_and_io/data_types_and_io/file.py normalize_csv_file --csv_url "https://people.sc.fsu.edu/~jburkardt/data/csv/biostats.csv" --column_names "[\"Name\", \"Sex\", \"Age\", \"Heights (in)\", \"Weight (lbs)\"]" --columns_to_normalize "[\"Age\"]"

python examples/data_types_and_io/data_types_and_io/file.py

Setup process
git clone https://github.com/flyteorg/flytekit.git
gh pr checkout 2881
make setup && pip install -e .

Check all the applicable boxes

[ ] I updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] All commits are signed-off.

Related PRs
None
Docs link

Hi @Future-Outlier,
Thanks very much for the guidance. To make the commit history clear, I planned to separate the commits of the modified flytefile test and the flytedirectory one. But, the PR was closed. Should I open another PR to add the fd part? Or, is there a better solution? Thanks!


R29: Home Page: The Software Home Page line graph shall display a timeline graph of recalls over time

Tools: JQuery
metadata: recall_initiation_date, voluntary_mandated

c3 timeseries graph used to satisfy this requirement. jquery is utilized to make ajax request to openfda endpoint to get the dates as well as the number of recalls on that particular date

Completed.
SQA


Create view for managing Unbonding Locks

What's the problem? (required)
I am not able to manage my unbonding locks within the explorer.
What's the current behavior? (required)
No unbonding locks shows up within the explorer.
Do you have any personal experiences dealing with this problem? (optional)
Yes, when someone unbonds, whether partially or fully, the LP tokens are held within an unbonding lock for a period of 7 days. After 7 days passes then the token holder is able to withdraw or rebond their tokens. Currently the UX for this process is bad. Each unbond creates a new lock. See this issue for more details surrounding unbonding locks.
Describe a possible solution you've considered (optional)
I would like to see users having the ability to manage their unbonding locks within the explorer's MyAccount Delegating page. A section would show up with all the user current and pending unbonding locks, where with the click of a button, tokens can be withdrawn when a lock is ready or rebonded whether lock is ready or not. For this to happen a view that uses the component mentioned in issue #294  is needed for helping to display and manage unbonding locks.
Additional context (optional)
Each unbonding lock should have two buttons, withdraw and rebond. The withdraw button should be disabled if the unbonding lock is not ready to be withdrawn and the rebond button is only enabled when the token have not been withdrawn or rebonded.

Note: The styling and architecture of the unbonding lock view should follow the same styling  and architecture within the explorer. That is, data for the unbonding locks should come from the graphql-sdk which fetches data from the blockchain using the Livepeer SDK.
Please see partial unbonding and fully unbonding for a walk through of the mock ups and user flow of how partial/fully unbonding should operate.

Randy, see other comment, but the text underneath the 30 LPT and 20 LPT is not the right text. Please use the text that is in the mockup flow. Dont find the text by clicking on the index, instead, use preview flow (the correct mockup is selected as part of the flow), as I have old drafts in the index that were not deleted.


The automated release is failing 🚨

:rotating_light: The automated release from the next branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the next branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 1.0.0 on branch next cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=1.5.0 can be published from branch next.
The following commits are responsible for the invalid release:

ci: trying to fix rel version (ad79b07)
chore(release): 1.0.0-next.2 [skip ci] (9e2b0dd)
ci: fix pnpm-lock location (689bcf0)
chore(release): 1.0.0-next.1 [skip ci] (37a4092)
ci: downgrade semantic-release (1c089fc)
ci: i'm losing my mind on this one (3fa448e)
ci: trigger release (0b3c5c0)
ci: trigger release (72f37d6)
ci: trigger release (1ffc1da)
ci: trigger release (6c1e61b)
ci: add missing deps (2b3287f)
ci: go back to pat (5f3f97f)
ci: use github token from actions (f591094)
ci: fix pre-release version (4bf8e85)
ci: add missing dev dependency (19745b0)
ci: trying with PAT (f1dc773)
ci: trying again (d5d41bd)
ci: trying again (7772c26)
ci: trying to fix pnpm (7bcbd68)
ci: fix package manager (234a8cc)
feat: dynamics -> simulations (#13) (a74996e)
fix: running dynamic page should now work (21734ce)
fix: disable preload data on running page (089f96b)
fix: disable preload of my-dynamics (575dd88)
chore: update ecosystem (5311fda)
fix: use full baseurl if not development (d5be1d6)
fix: server start command (ac38ebc)
fix: add SSL to server (c5c098c)
fix: add _npt.gro to results download (8be8f77)
chore: add first post (66f6ec8)
chore: update translations (f0d24e4)
chore: remove unneeded file (f5ccd7d)
fix: instruct users to contact admin for old simulations (b83f6ee)
fix: missing translations (4b8e2b3)
feat: add download archive button (6603ed7)
fix: update translations and images (22f02a1)
fix: update db schema (d2c21cc)
fix: navbar scroll, email sending (b19a616)
chore: remove unneeded console.log (a9e3264)
fix: mobile navbar positioning, initial theme load (e0daf89)
chore: update prisma version (f55bd9c)
chore: reworking directories (eb8066e)
fix: get initial theme synchronously (0085537)
revert: going back to pm2 for client deploy (1016d6f)
fix: moving thread number to config file (5af7e96)
chore: update readme (c7562cd)
fix(acpype | prodrg): usage of box_distance and ignore (97cb69f)
fix: change redis default port (1478e2c)
chore: deploy scheme ready (e6a42cd)
fix: dockerization almost done (2a4c2ba)
feat: containerization in progress (cb720da)
chore: moving deploy to docker (4058b33)
fix: minimum python version (a3ae014)
fix(client): smooth transition on dynamic form submit button (4899a38)
feat(client): improvements to sidebar, animations and loading states (ef01b75)
fix(client): behaviour and style merging (9d8c732)
fix(server): not returning command list when requestes (1c794a2)
feat(client): use framer-motion for animations (60657be)
chore(repo): move to yarn (b5280e2)
chore: add institutions logo (fc5bb32)
chore: rename acpype test pdb (b26c593)
feat: only process molecules with 5000 or less atoms (234e596)
fix: i18n namespace loading on dynamic forms (8933cc2)
feat: move to next-translate instead of next-i18next (e1dcbf3)
feat: updated posts view (73c3033)
fix: show loading state on route changing (0f6631d)
fix: migrate from nextjs-progressbar to next-progress (62baae0)
feat: redirect user from vd1 to reset password screen on first login (4e3d463)
fix(client): fix page viewport on mobile (2788fbb)
fix(client): blog page not rendering tab title (395e3ad)
fix(client): sign up form loading state not showing up (f9b3e4b)
fix(client): sign in form loading state not showing up (fd377ef)
feat(client): added ability to reset password (c780d68)
fix: revert tailwind dark mode enabler (1561325)
fix: correct and re-enabled gray color (ef07c5c)
docs(client): added storybook and Button stories (787bfa3)
chore: fixes for production (da24e51)
chore(client): add log to mailer (16f2538)
fix(server): download logic (95d02d0)
fix(client): disable prisma log query (1cfa7c5)
chore: fix pm2 ecosystem file (d73014a)
chore: pm2 ecosystem file (bed728e)
chore: pm2 ecosystem file (b33ceb4)
chore: pm2 ecosystem file (0e6da7e)
chore: for tests (2ea6a66)
chore: pm2 ecosystem file (0699e48)
chore: pm2 ecosystem file (7dfbac3)
chore: pm2 ecosystem file (00c0645)
chore: pm2 ecosystem file (a05ecb9)
chore: pm2 ecosystem file (66130bb)
chore: pm2 ecosystem file (e075dde)
chore: pm2 ecosystem file (e714ff9)
chore: pm2 ecosystem file (f5aba4a)
chore: pm2 ecosystem file (a86f1a5)
chore: pm2 ecosystem file (aecca37)
chore: pm2 ecosystem file (e28b76e)
chore: pm2 ecosystem file (976fd15)
fix(server): fix nthreads to 10 (dc4b249)
fix(server): min python 3.9 (fcf83f6)
fix(client): improve blog managing (10de12d)
fix(client): reduced usage of useState in forms, built static blogs for all languages (9470688)
fix(client): admin cron job fix (e876cf5)
fix(client): send mail url (e413957)
fix(client): admin sign up request list item behaviour on small screens (b46f09c)
fix(server): run server on networ IP (bcbc78d)
feat(client): re-enabled PRODRG dynamic execution (add8e05)
feat: migrate PRODRG to linux commands (0fb1f45)
feat(mail): send mail on admin approval/rejection (539b81e)
fix: send mail on dynamic status changed (922b12a)
fix(cron): don't send email when no inactive users (c0ca8b7)
fix: rename admin requests cron job (7394fe9)
feat: mailer (accd472)
chore: add logo for email (dd0ee45)
feat: md_pr update (02afc10)
chore(client): restructure components (323e6be)
fix: changed generate routes, added update mdpr route (4d7b180)
fix(client): type errors and title positioning (53c342f)
fix(client): dynamic card sṕinner color (7091d5a)
fix(server): command running pid saving on wrong place (6e19b0a)
fix(client): disable abort button when the request is running (fb9271e)
fix: abort task route, improvements on UI and more (1165112)
fix(server): update default celety services (a9cda03)
fix(client): improvements to layout (fd4a9b9)
chore(tests): add testfiles (982e2d5)
fix(server): fixes for admin page to view all running dynamics (1f106a0)
feat(client): admin page to view all running dynamics (eeddab9)
fix(client): cleanup on unused imports on admin approval/reject page (62c9124)
feat(client): admin request approval/reject page (8db28aa)
fix(client): add info about signup (588ad4f)
fix(client): screen scroll, signin error messages (fbe6b3f)
feat(client): signup page (5e0fe33)
fix(client): move some pages away from getServerSideProps (9b03c48)
fix(client): min height on mobile, link to admin page (78f63cf)
fix(client): tailwindcss auto classname sorter (bdda700)
fix(client): behaviour on mobile and desktop (9523855)
fix(client): improvements to mobile UI (2d2b316)
chore(vscode): always prefer non-relative imports (7814ca4)
fix(server): send last log lines reversed (1fb1965)
fix(client): improvements to dynamic related pages (1618f8f)
fix(client): update main (8f07e77)
fix(client): improve colors (d121046)
fix(client): font family (3912c6d)
fix(client): lazy load some default components (4de545a)
fix(client): search bar wrong color on dark mode (5bfcca8)
fix(client): drop multi color theme in favor of light and dark theme (f5bdc6a)
fix: remove unneeded component (12398cc)
feat(client): redone layout (4f55ca7)
fix(client): icon size on buttons (c09080d)
fix(client): mobile nav lock body scroll (3b4ed6f)
fix(client): add spacing in about sections (7a97449)
fix: add title to work icon on maintainer card (8fa963d)
fix: improved about page (6fb771b)
fix: lockfile, add .env.example (4c9807d)
feat(client): add progressbar on top, and fix loading state on page transition (55b77d3)
fix(client): color scheme persistence (465ac29)
feat(client): loading state on auth form, added some content to home page (f2a7122)
fix: translations (5021b51)
chore: trigger deploy (f749850)
feat(client): fixes and about page with some initial content (aa4f646)
fix(client): backend url from env (a84a1e8)
fix(client): 404 page title (2dfe246)
fix(client): custom 404 page, prodrg force fields (c7ed6b1)
feat(client): added prodrg page, some fixes to failing api calls (5246a43)
fix(client): don't use node as edge backend (7bbb1a6)
fix(client): duplicated header links (2afffcb)
fix: vercel build (ea6112c)
fix: vercel build (641e80b)
fix: vercel build (687af35)
fix: vercel build (542e9c6)
fix: improvements (f885bc4)
feat(client): authentication done (d3a9d1b)
fix(client): improvements to breadcrumb (0fccc0a)
feat(client): improved page transitions, translations and components (cf91a86)
fix(server): download command list for running and queued dynamics (3a84a83)
feat: added file downloads for dynamics ran on server (40668fa)
feat: added acpype dynamic, improved visuals (56152f2)
feat: added acpype dynamic, dynamic cancellation (6cb44ac)
feat(server): improved the way running data is returne (15b5307)
feat(client): added dynamic breadcrumb, finished running page, started translations (6528324)
chore(repo): update pnpm-lock (db547f6)
feat(client): you can now generate and start a APO dynamic (be9cb52)
feat(server): big changes on APO dynamic generation and dynamic execution (6e4f8f9)
feat(server): run route now just calls celery process (2306af0)
chore: flower.service -> celery-flower.service, docs on setting up celery (5eafc63)
feat: added celery to run dynamics (2695f41)
feat(server): added route to get user dynamic run status (ee3bbac)
feat: ability to start APO dynamic (ba2a914)
fix(client): improved select/input border color, fixed future form translation keys (fee3c74)
feat(client): a bunch more things (d9c4efc)
feat(client): started redoing layout (c96855a)
feat(apps): added base code for client and server (c79c56f)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch next with git revert or git reset.
A valid branch could be main or next.
See the workflow configuration documentation for more details.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the next branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the next branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 1.0.0 on branch next cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=2.0.0 <1.0.0 can be published from branch next.
The following commits are responsible for the invalid release:

ci: trying to fix rel version (55a7339)
ci: trying to fix rel version (b8bf891)
ci: trying to fix rel version (aff6c1a)
ci: trying to fix rel version (ad79b07)
chore(release): 1.0.0-next.2 [skip ci] (9e2b0dd)
ci: fix pnpm-lock location (689bcf0)
chore(release): 1.0.0-next.1 [skip ci] (37a4092)
ci: downgrade semantic-release (1c089fc)
ci: i'm losing my mind on this one (3fa448e)
ci: trigger release (0b3c5c0)
ci: trigger release (72f37d6)
ci: trigger release (1ffc1da)
ci: trigger release (6c1e61b)
ci: add missing deps (2b3287f)
ci: go back to pat (5f3f97f)
ci: use github token from actions (f591094)
ci: fix pre-release version (4bf8e85)
ci: add missing dev dependency (19745b0)
ci: trying with PAT (f1dc773)
ci: trying again (d5d41bd)
ci: trying again (7772c26)
ci: trying to fix pnpm (7bcbd68)
ci: fix package manager (234a8cc)
feat: dynamics -> simulations (#13) (a74996e)
fix: running dynamic page should now work (21734ce)
fix: disable preload data on running page (089f96b)
fix: disable preload of my-dynamics (575dd88)
chore: update ecosystem (5311fda)
fix: use full baseurl if not development (d5be1d6)
fix: server start command (ac38ebc)
fix: add SSL to server (c5c098c)
fix: add _npt.gro to results download (8be8f77)
chore: add first post (66f6ec8)
chore: update translations (f0d24e4)
chore: remove unneeded file (f5ccd7d)
fix: instruct users to contact admin for old simulations (b83f6ee)
fix: missing translations (4b8e2b3)
feat: add download archive button (6603ed7)
fix: update translations and images (22f02a1)
fix: update db schema (d2c21cc)
fix: navbar scroll, email sending (b19a616)
chore: remove unneeded console.log (a9e3264)
fix: mobile navbar positioning, initial theme load (e0daf89)
chore: update prisma version (f55bd9c)
chore: reworking directories (eb8066e)
fix: get initial theme synchronously (0085537)
revert: going back to pm2 for client deploy (1016d6f)
fix: moving thread number to config file (5af7e96)
chore: update readme (c7562cd)
fix(acpype | prodrg): usage of box_distance and ignore (97cb69f)
fix: change redis default port (1478e2c)
chore: deploy scheme ready (e6a42cd)
fix: dockerization almost done (2a4c2ba)
feat: containerization in progress (cb720da)
chore: moving deploy to docker (4058b33)
fix: minimum python version (a3ae014)
fix(client): smooth transition on dynamic form submit button (4899a38)
feat(client): improvements to sidebar, animations and loading states (ef01b75)
fix(client): behaviour and style merging (9d8c732)
fix(server): not returning command list when requestes (1c794a2)
feat(client): use framer-motion for animations (60657be)
chore(repo): move to yarn (b5280e2)
chore: add institutions logo (fc5bb32)
chore: rename acpype test pdb (b26c593)
feat: only process molecules with 5000 or less atoms (234e596)
fix: i18n namespace loading on dynamic forms (8933cc2)
feat: move to next-translate instead of next-i18next (e1dcbf3)
feat: updated posts view (73c3033)
fix: show loading state on route changing (0f6631d)
fix: migrate from nextjs-progressbar to next-progress (62baae0)
feat: redirect user from vd1 to reset password screen on first login (4e3d463)
fix(client): fix page viewport on mobile (2788fbb)
fix(client): blog page not rendering tab title (395e3ad)
fix(client): sign up form loading state not showing up (f9b3e4b)
fix(client): sign in form loading state not showing up (fd377ef)
feat(client): added ability to reset password (c780d68)
fix: revert tailwind dark mode enabler (1561325)
fix: correct and re-enabled gray color (ef07c5c)
docs(client): added storybook and Button stories (787bfa3)
chore: fixes for production (da24e51)
chore(client): add log to mailer (16f2538)
fix(server): download logic (95d02d0)
fix(client): disable prisma log query (1cfa7c5)
chore: fix pm2 ecosystem file (d73014a)
chore: pm2 ecosystem file (bed728e)
chore: pm2 ecosystem file (b33ceb4)
chore: pm2 ecosystem file (0e6da7e)
chore: for tests (2ea6a66)
chore: pm2 ecosystem file (0699e48)
chore: pm2 ecosystem file (7dfbac3)
chore: pm2 ecosystem file (00c0645)
chore: pm2 ecosystem file (a05ecb9)
chore: pm2 ecosystem file (66130bb)
chore: pm2 ecosystem file (e075dde)
chore: pm2 ecosystem file (e714ff9)
chore: pm2 ecosystem file (f5aba4a)
chore: pm2 ecosystem file (a86f1a5)
chore: pm2 ecosystem file (aecca37)
chore: pm2 ecosystem file (e28b76e)
chore: pm2 ecosystem file (976fd15)
fix(server): fix nthreads to 10 (dc4b249)
fix(server): min python 3.9 (fcf83f6)
fix(client): improve blog managing (10de12d)
fix(client): reduced usage of useState in forms, built static blogs for all languages (9470688)
fix(client): admin cron job fix (e876cf5)
fix(client): send mail url (e413957)
fix(client): admin sign up request list item behaviour on small screens (b46f09c)
fix(server): run server on networ IP (bcbc78d)
feat(client): re-enabled PRODRG dynamic execution (add8e05)
feat: migrate PRODRG to linux commands (0fb1f45)
feat(mail): send mail on admin approval/rejection (539b81e)
fix: send mail on dynamic status changed (922b12a)
fix(cron): don't send email when no inactive users (c0ca8b7)
fix: rename admin requests cron job (7394fe9)
feat: mailer (accd472)
chore: add logo for email (dd0ee45)
feat: md_pr update (02afc10)
chore(client): restructure components (323e6be)
fix: changed generate routes, added update mdpr route (4d7b180)
fix(client): type errors and title positioning (53c342f)
fix(client): dynamic card sṕinner color (7091d5a)
fix(server): command running pid saving on wrong place (6e19b0a)
fix(client): disable abort button when the request is running (fb9271e)
fix: abort task route, improvements on UI and more (1165112)
fix(server): update default celety services (a9cda03)
fix(client): improvements to layout (fd4a9b9)
chore(tests): add testfiles (982e2d5)
fix(server): fixes for admin page to view all running dynamics (1f106a0)
feat(client): admin page to view all running dynamics (eeddab9)
fix(client): cleanup on unused imports on admin approval/reject page (62c9124)
feat(client): admin request approval/reject page (8db28aa)
fix(client): add info about signup (588ad4f)
fix(client): screen scroll, signin error messages (fbe6b3f)
feat(client): signup page (5e0fe33)
fix(client): move some pages away from getServerSideProps (9b03c48)
fix(client): min height on mobile, link to admin page (78f63cf)
fix(client): tailwindcss auto classname sorter (bdda700)
fix(client): behaviour on mobile and desktop (9523855)
fix(client): improvements to mobile UI (2d2b316)
chore(vscode): always prefer non-relative imports (7814ca4)
fix(server): send last log lines reversed (1fb1965)
fix(client): improvements to dynamic related pages (1618f8f)
fix(client): update main (8f07e77)
fix(client): improve colors (d121046)
fix(client): font family (3912c6d)
fix(client): lazy load some default components (4de545a)
fix(client): search bar wrong color on dark mode (5bfcca8)
fix(client): drop multi color theme in favor of light and dark theme (f5bdc6a)
fix: remove unneeded component (12398cc)
feat(client): redone layout (4f55ca7)
fix(client): icon size on buttons (c09080d)
fix(client): mobile nav lock body scroll (3b4ed6f)
fix(client): add spacing in about sections (7a97449)
fix: add title to work icon on maintainer card (8fa963d)
fix: improved about page (6fb771b)
fix: lockfile, add .env.example (4c9807d)
feat(client): add progressbar on top, and fix loading state on page transition (55b77d3)
fix(client): color scheme persistence (465ac29)
feat(client): loading state on auth form, added some content to home page (f2a7122)
fix: translations (5021b51)
chore: trigger deploy (f749850)
feat(client): fixes and about page with some initial content (aa4f646)
fix(client): backend url from env (a84a1e8)
fix(client): 404 page title (2dfe246)
fix(client): custom 404 page, prodrg force fields (c7ed6b1)
feat(client): added prodrg page, some fixes to failing api calls (5246a43)
fix(client): don't use node as edge backend (7bbb1a6)
fix(client): duplicated header links (2afffcb)
fix: vercel build (ea6112c)
fix: vercel build (641e80b)
fix: vercel build (687af35)
fix: vercel build (542e9c6)
fix: improvements (f885bc4)
feat(client): authentication done (d3a9d1b)
fix(client): improvements to breadcrumb (0fccc0a)
feat(client): improved page transitions, translations and components (cf91a86)
fix(server): download command list for running and queued dynamics (3a84a83)
feat: added file downloads for dynamics ran on server (40668fa)
feat: added acpype dynamic, improved visuals (56152f2)
feat: added acpype dynamic, dynamic cancellation (6cb44ac)
feat(server): improved the way running data is returne (15b5307)
feat(client): added dynamic breadcrumb, finished running page, started translations (6528324)
chore(repo): update pnpm-lock (db547f6)
feat(client): you can now generate and start a APO dynamic (be9cb52)
feat(server): big changes on APO dynamic generation and dynamic execution (6e4f8f9)
feat(server): run route now just calls celery process (2306af0)
chore: flower.service -> celery-flower.service, docs on setting up celery (5eafc63)
feat: added celery to run dynamics (2695f41)
feat(server): added route to get user dynamic run status (ee3bbac)
feat: ability to start APO dynamic (ba2a914)
fix(client): improved select/input border color, fixed future form translation keys (fee3c74)
feat(client): a bunch more things (d9c4efc)
feat(client): started redoing layout (c96855a)
feat(apps): added base code for client and server (c79c56f)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch next with git revert or git reset.
A valid branch could be main.
See the workflow configuration documentation for more details.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the next branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the next branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 1.0.0 on branch next cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=2.0.0 <1.0.0 can be published from branch next.
The following commits are responsible for the invalid release:

fix: trigger release (9018750)
ci: trying to fix rel version (55a7339)
ci: trying to fix rel version (b8bf891)
ci: trying to fix rel version (aff6c1a)
ci: trying to fix rel version (ad79b07)
chore(release): 1.0.0-next.2 [skip ci] (9e2b0dd)
ci: fix pnpm-lock location (689bcf0)
chore(release): 1.0.0-next.1 [skip ci] (37a4092)
ci: downgrade semantic-release (1c089fc)
ci: i'm losing my mind on this one (3fa448e)
ci: trigger release (0b3c5c0)
ci: trigger release (72f37d6)
ci: trigger release (1ffc1da)
ci: trigger release (6c1e61b)
ci: add missing deps (2b3287f)
ci: go back to pat (5f3f97f)
ci: use github token from actions (f591094)
ci: fix pre-release version (4bf8e85)
ci: add missing dev dependency (19745b0)
ci: trying with PAT (f1dc773)
ci: trying again (d5d41bd)
ci: trying again (7772c26)
ci: trying to fix pnpm (7bcbd68)
ci: fix package manager (234a8cc)
feat: dynamics -> simulations (#13) (a74996e)
fix: running dynamic page should now work (21734ce)
fix: disable preload data on running page (089f96b)
fix: disable preload of my-dynamics (575dd88)
chore: update ecosystem (5311fda)
fix: use full baseurl if not development (d5be1d6)
fix: server start command (ac38ebc)
fix: add SSL to server (c5c098c)
fix: add _npt.gro to results download (8be8f77)
chore: add first post (66f6ec8)
chore: update translations (f0d24e4)
chore: remove unneeded file (f5ccd7d)
fix: instruct users to contact admin for old simulations (b83f6ee)
fix: missing translations (4b8e2b3)
feat: add download archive button (6603ed7)
fix: update translations and images (22f02a1)
fix: update db schema (d2c21cc)
fix: navbar scroll, email sending (b19a616)
chore: remove unneeded console.log (a9e3264)
fix: mobile navbar positioning, initial theme load (e0daf89)
chore: update prisma version (f55bd9c)
chore: reworking directories (eb8066e)
fix: get initial theme synchronously (0085537)
revert: going back to pm2 for client deploy (1016d6f)
fix: moving thread number to config file (5af7e96)
chore: update readme (c7562cd)
fix(acpype | prodrg): usage of box_distance and ignore (97cb69f)
fix: change redis default port (1478e2c)
chore: deploy scheme ready (e6a42cd)
fix: dockerization almost done (2a4c2ba)
feat: containerization in progress (cb720da)
chore: moving deploy to docker (4058b33)
fix: minimum python version (a3ae014)
fix(client): smooth transition on dynamic form submit button (4899a38)
feat(client): improvements to sidebar, animations and loading states (ef01b75)
fix(client): behaviour and style merging (9d8c732)
fix(server): not returning command list when requestes (1c794a2)
feat(client): use framer-motion for animations (60657be)
chore(repo): move to yarn (b5280e2)
chore: add institutions logo (fc5bb32)
chore: rename acpype test pdb (b26c593)
feat: only process molecules with 5000 or less atoms (234e596)
fix: i18n namespace loading on dynamic forms (8933cc2)
feat: move to next-translate instead of next-i18next (e1dcbf3)
feat: updated posts view (73c3033)
fix: show loading state on route changing (0f6631d)
fix: migrate from nextjs-progressbar to next-progress (62baae0)
feat: redirect user from vd1 to reset password screen on first login (4e3d463)
fix(client): fix page viewport on mobile (2788fbb)
fix(client): blog page not rendering tab title (395e3ad)
fix(client): sign up form loading state not showing up (f9b3e4b)
fix(client): sign in form loading state not showing up (fd377ef)
feat(client): added ability to reset password (c780d68)
fix: revert tailwind dark mode enabler (1561325)
fix: correct and re-enabled gray color (ef07c5c)
docs(client): added storybook and Button stories (787bfa3)
chore: fixes for production (da24e51)
chore(client): add log to mailer (16f2538)
fix(server): download logic (95d02d0)
fix(client): disable prisma log query (1cfa7c5)
chore: fix pm2 ecosystem file (d73014a)
chore: pm2 ecosystem file (bed728e)
chore: pm2 ecosystem file (b33ceb4)
chore: pm2 ecosystem file (0e6da7e)
chore: for tests (2ea6a66)
chore: pm2 ecosystem file (0699e48)
chore: pm2 ecosystem file (7dfbac3)
chore: pm2 ecosystem file (00c0645)
chore: pm2 ecosystem file (a05ecb9)
chore: pm2 ecosystem file (66130bb)
chore: pm2 ecosystem file (e075dde)
chore: pm2 ecosystem file (e714ff9)
chore: pm2 ecosystem file (f5aba4a)
chore: pm2 ecosystem file (a86f1a5)
chore: pm2 ecosystem file (aecca37)
chore: pm2 ecosystem file (e28b76e)
chore: pm2 ecosystem file (976fd15)
fix(server): fix nthreads to 10 (dc4b249)
fix(server): min python 3.9 (fcf83f6)
fix(client): improve blog managing (10de12d)
fix(client): reduced usage of useState in forms, built static blogs for all languages (9470688)
fix(client): admin cron job fix (e876cf5)
fix(client): send mail url (e413957)
fix(client): admin sign up request list item behaviour on small screens (b46f09c)
fix(server): run server on networ IP (bcbc78d)
feat(client): re-enabled PRODRG dynamic execution (add8e05)
feat: migrate PRODRG to linux commands (0fb1f45)
feat(mail): send mail on admin approval/rejection (539b81e)
fix: send mail on dynamic status changed (922b12a)
fix(cron): don't send email when no inactive users (c0ca8b7)
fix: rename admin requests cron job (7394fe9)
feat: mailer (accd472)
chore: add logo for email (dd0ee45)
feat: md_pr update (02afc10)
chore(client): restructure components (323e6be)
fix: changed generate routes, added update mdpr route (4d7b180)
fix(client): type errors and title positioning (53c342f)
fix(client): dynamic card sṕinner color (7091d5a)
fix(server): command running pid saving on wrong place (6e19b0a)
fix(client): disable abort button when the request is running (fb9271e)
fix: abort task route, improvements on UI and more (1165112)
fix(server): update default celety services (a9cda03)
fix(client): improvements to layout (fd4a9b9)
chore(tests): add testfiles (982e2d5)
fix(server): fixes for admin page to view all running dynamics (1f106a0)
feat(client): admin page to view all running dynamics (eeddab9)
fix(client): cleanup on unused imports on admin approval/reject page (62c9124)
feat(client): admin request approval/reject page (8db28aa)
fix(client): add info about signup (588ad4f)
fix(client): screen scroll, signin error messages (fbe6b3f)
feat(client): signup page (5e0fe33)
fix(client): move some pages away from getServerSideProps (9b03c48)
fix(client): min height on mobile, link to admin page (78f63cf)
fix(client): tailwindcss auto classname sorter (bdda700)
fix(client): behaviour on mobile and desktop (9523855)
fix(client): improvements to mobile UI (2d2b316)
chore(vscode): always prefer non-relative imports (7814ca4)
fix(server): send last log lines reversed (1fb1965)
fix(client): improvements to dynamic related pages (1618f8f)
fix(client): update main (8f07e77)
fix(client): improve colors (d121046)
fix(client): font family (3912c6d)
fix(client): lazy load some default components (4de545a)
fix(client): search bar wrong color on dark mode (5bfcca8)
fix(client): drop multi color theme in favor of light and dark theme (f5bdc6a)
fix: remove unneeded component (12398cc)
feat(client): redone layout (4f55ca7)
fix(client): icon size on buttons (c09080d)
fix(client): mobile nav lock body scroll (3b4ed6f)
fix(client): add spacing in about sections (7a97449)
fix: add title to work icon on maintainer card (8fa963d)
fix: improved about page (6fb771b)
fix: lockfile, add .env.example (4c9807d)
feat(client): add progressbar on top, and fix loading state on page transition (55b77d3)
fix(client): color scheme persistence (465ac29)
feat(client): loading state on auth form, added some content to home page (f2a7122)
fix: translations (5021b51)
chore: trigger deploy (f749850)
feat(client): fixes and about page with some initial content (aa4f646)
fix(client): backend url from env (a84a1e8)
fix(client): 404 page title (2dfe246)
fix(client): custom 404 page, prodrg force fields (c7ed6b1)
feat(client): added prodrg page, some fixes to failing api calls (5246a43)
fix(client): don't use node as edge backend (7bbb1a6)
fix(client): duplicated header links (2afffcb)
fix: vercel build (ea6112c)
fix: vercel build (641e80b)
fix: vercel build (687af35)
fix: vercel build (542e9c6)
fix: improvements (f885bc4)
feat(client): authentication done (d3a9d1b)
fix(client): improvements to breadcrumb (0fccc0a)
feat(client): improved page transitions, translations and components (cf91a86)
fix(server): download command list for running and queued dynamics (3a84a83)
feat: added file downloads for dynamics ran on server (40668fa)
feat: added acpype dynamic, improved visuals (56152f2)
feat: added acpype dynamic, dynamic cancellation (6cb44ac)
feat(server): improved the way running data is returne (15b5307)
feat(client): added dynamic breadcrumb, finished running page, started translations (6528324)
chore(repo): update pnpm-lock (db547f6)
feat(client): you can now generate and start a APO dynamic (be9cb52)
feat(server): big changes on APO dynamic generation and dynamic execution (6e4f8f9)
feat(server): run route now just calls celery process (2306af0)
chore: flower.service -> celery-flower.service, docs on setting up celery (5eafc63)
feat: added celery to run dynamics (2695f41)
feat(server): added route to get user dynamic run status (ee3bbac)
feat: ability to start APO dynamic (ba2a914)
fix(client): improved select/input border color, fixed future form translation keys (fee3c74)
feat(client): a bunch more things (d9c4efc)
feat(client): started redoing layout (c96855a)
feat(apps): added base code for client and server (c79c56f)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch next with git revert or git reset.
A valid branch could be main.
See the workflow configuration documentation for more details.

Good luck with your project ✨
Your semantic-release bot :package::rocket:


Fix dependencies

This project uses semver, please check the scope of this pr:
Closes: https://github.com/ciena-frost/ember-frost-list/issues/167

[ ] #none# - documentation fixes and/or test additions
[ ] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[X] #major# - incompatible API change

CHANGELOG

Added bower to devDependencies since it is no longer included with Ember CLI
Updated to version 4 of ember-frost-core
Updated to version 9 of ember-frost-sort and move from dependencies to devDependencies since only used in the dummy app
Updated to version 5 of ember-prop-types and moved from devDependencies to dependencies
Removed blueprints since they are no longer needed to install packages
Updated ember-computed-decorators to a dependency instead of a devDependency
Updated ember-hook to a dependency instead of a devDependency
Removed unused ember-concurrency package since it is now included via the dependencies of ember-frost-core
Removed unused ember-elsewhere package since it is now included via the dependencies of ember-frost-core
Removed unused ember-spread package since it is now included via the dependencies of ember-frost-core
Updated ember-truth-helpers to a dependency instead of a devDependency
Removed unused ember-get-config package
Updated ember-data-factory-guy to use the published version with the fix instead of a branch

Changes Unknown when pulling f018230186f8a36ee0baad7b2742880992f29616 on juwara0:fixDependencies into ** on ciena-frost:master**.

👍


OLS Search and Data stats are not loading

Using Chrome (Version 117.0.5938.132) on Mac the Search feature is not working.
Screenshot of page that is not loading

Hi Trish!
Thank you for reporting this!
As far as I can see all the OLS4 pods were up and running at this time, but K8s related services had an extreme high memory use. I have opened a ticket with infrastructure to follow up on this. I will report back once I have feedback from them.

Infrastructure have addressed this now.

@henrietteharmse - fyi, this behaviour is happening again.

It's working again.

This problem came up again today. I am following up with infrastructure.

Happened again. Hence latest settings is still not resolving the issue.

And again!

We had a productive discussion with infrastructure in this regard. Currently it seems the node on which the ols4-backend runs, may be hitting some limit. Figuring this out is made difficult by the fact that the very sophisticated monitoring that infrastructure has on the cluster also fails when we have an outage on the backend. I am are checking the ols backend for potential leaks that can cause this behaviour and hope to have this complete by 23 Oct latest.  Infrastructure is monitoring specific limits to see whether crashes can be associated with reaching a specific limit.

It seems like we now have gotten to the bottom of this issue. Based on infrastructure monitoring the ols-backend created a disproportionate amount of threads (125000!!!). This was due to Solr, Neo4J and HTTP connections that were not closed in the ols-backend. After the latest commit on stable I can now confirm that all connections are closed and since the update on the 19 hours ago, the number of threads used in the ols-backend have been stable.


Recipe App

Hello and welcome to "Recipe App"
This project was created collaboratively by @anshuman7negi and @Zilola-Nazarova
In this project, we created "Recipe App" that keeps track of all your recipes, ingredients, and inventory. It will allow you to save ingredients, keep track of what you have, create recipes, and generate a shopping list based on what you have and what you are missing from a recipe. Also, since sharing recipes is an important part of cooking the app allows you to make them public so anyone can access them.
General requirements:

there are no linter errors
correct Gitflow is used
work is documented in a professional way

Project requirements:
We followed the layout of the wireframes provided. We just personalized colors, typographies, spacings, etc.
You can see Sign in and Sign out buttons in navbar. Login page and registration page are built with Devise.
Recipes list (Recipes button in navbar):

displays a list of recipes created by the logged-in user
leads to recipe details

Public recipe list (Public Recipes button in navbar):

displays a list of all public recipes ordered by newest
leads to recipe details
if the user is the owner of the recipe, allows the user to delete it

Recipe details:

displays a toggle button that allows for a recipe to be made public or private
if the recipe is public or the user is the owner of the recipe, displays the recipe details
if the user is the owner of the recipe, leads to the form that allows the user to add new food

Food list (Food button in navbar):

displays a list of food added by the logged-in user
leads to a form that allows users to add new food

General shopping list view (Shopping list button in navbar):

shows the list of food that is missing for all recipes of the logged-in user
counts the total food items and total price of the missing food

We made sure there were no N+1 queries happening. We used bullet gem to re-check our solutions.
We created a navigation menu that allows users to open all of the pages we created.
We added unit and integration tests for all models and views.

Thank you for your time and effort reviewing our PR @mukhammadrizooff 🙏🏻


What, if anything, have you done to thwart CPU frequency scaling?

You need to make sure your CPU is running at full clock speed when starting the test. Otherwise, part of the test is a scaling of the CPU frequency, which isn't fair.
If you run the test 20 times for each application and measure all the results, what are the variance of the measurements? If you use something like Haskell's criterion or my own eministat to analyze the results, are they stable against outlier variance?

Haskell's code is able to detect variance: https://travis-ci.org/ChristopherKing42/skynet/builds/109503734#L460


Cleaning Folder

Brad had a verify tool & a downloader... Decided to toss these into folders.

Works for me, and I agree helper tools can and should have their own directory.


NDRS-760: Track which peers had the data and prioritize them.

https://casperlabs.atlassian.net/browse/NDRS-760
Track which peers we successfully have downloaded data from and prioritize them when we request the next piece of data.
Every 5 successful attempts we will try 1 new peer (which is not in the set of the successful peer). If it has the data, it will be added to the set.

bors merge

bors merge