Toggling Child Panels

Using the Expanded prop on Expansion panels. I'm trying to toggle expanded based on whether a parent panel was clicked. So if a parent panel is clicked, collapse and open the other parent panel. However, child panels are not being collapsed on click of another parent panel. I'm not sure how to handle the child panel collapses.
This is how I'm trying to do it
  let showPanel;
    if (parent) showPanel = null;
    else if (this.state.currentParent === node.value) showPanel = true;
    else showPanel = false;

  <ExpansionPanel
        expanded={showPanel}
        onChange={this.handlePanelChange(node.value, parent)}

The on handlePanelChange is
handlePanelChange = (panel, parent) => (event) => {
   event.preventDefault();

   if (this.state.currentParent === panel) {
     return this.setState({ currentParent: null });
   }
   if (!parent && this.state.currentParent !== panel) {
     return this.setState({

       currentParent: panel
     });
   }
 };

This toggles parent panels. So that if I click a parent panel and expand a nested child panel within, it will expand the child. Which is good, but if I click another parent panel and come back to the first parent panel. All the children are still expanded. How can you toggle the child panels to collapse as well when the parent expansion is set to false.
This is a sandbox demonstrating the issue https://codesandbox.io/s/mm97zqlmqj
Clicking on "Search" expands panel. Clicking on nested panel expands it. That's good. But if I click data and come back to Search, the nested panel within search is still expanded. The file is tree.js where this code is.

@jodays I'm sorry, it's the same problem as with #13545. It's a state management logic unrelated to Material-UI, not a bug.


[docs] Fix typo in coin-flip.mdx app example

Description
Describe the changes or additions included in this PR.
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Well spotted @madeinfree - thank you for this contribution!


Request history

We would like to be able to create a log of recent request history for the node (the last hour for example). These logs would contain information about what commands were executed, who the request came from (what client). Whether to request failed or succeeded etc. It is open for discussion here so please contribute if you've any good ideas!

Hi @jakekgrog
I believe we can have a thread in the background which logs the history. I think so this feature will be a win when we look at it from the perspective of fault tolerance. We can replay the logs to rebuild the cache in event of node failure.

Hi @Adm28, we already have subsystems that provide on-disk persistence. These can be point-in-time snapshots or an append only file. These only take a snapshot of the cache state, we don't have a way of storing any information related to the actual http requests.

@jakegrog  I wasn't aware of it.
We can create a queue of struct. Each struct can have  timestamp, request_id , command , client, response status etc as member variables.  After every certain interval , all the elements of the queue until the element whose response status isn't known yet can be persisted.
How are you planning to go about this ?

@Adm28 That is a similar approach to the one I'd have taken. Add each "request log struct" to a buffer and flush the buffer at regular intervals.


koordlet: fix unsafe conversion in net_cls

Ⅰ. Describe what this PR does

koordlet: Fix the unsafe conversion in the tc runtime hook plugin.

Ⅱ. Does this pull request fix one issue?

Resolve code scanning alerts #40, #41,
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm


For the scrolling behaviour of table, Inside the  table  Drop Down selection Panel should show outside of the the table.

Describe the bug
When we used (dxc-select) drop down inside of the table,  in case of scrolling behaviour table, the drop down selection panel is not showing outside of the table. I am using cdk version 4 components.
Expected behavior
For the case of scrolling behaviour of table , drop down selection Panel should show outside of the table .
Screenshots

Additional context
Could you please suggest me any solution? It would be helpful for the issue.

Hi Team,
Can someone please suggest a solution/fix for this issue?


coreos-installer: install only the required dracut modules

Install only the minimal number of dracut modules required
by the coreos installer to avoid issues during the installation.
Resolves: fedora-iot/iot-distro#5
Signed-off-by: Miguel Martín<EMAIL_ADDRESS>

Thanks you!!

Looks like RHEL 8 doesn't like the dracut module changes:
dracut: Executing: /usr/bin/dracut --no-hostonly --kver 4.18.0-372.9.1.el8.aarch64 --force -v --show-modules --no-early-microcode --reproducible --modules "prefixdevname prefixdevname-tools systemd-initrd fips modsign rescue i18n kernel-modules kernel-modules-extra network-manager network drm coreos-installer fdo lvm terminfo fs-lib dracut-systemd debug shutdown" --install /.buildstamp
dracut: systemd-initrd needs systemd in the initramfs
dracut: dracut-systemd needs systemd-initrd in the initramfs
dracut: dracut module 'systemd-initrd' cannot be found or installed.

Something went wrong on the merge queue.  Looks like a flake on first inspection.  No details on the failed job (it was a dynamic trigger job).
Requeued.  Will keep an eye on it.


Get Miro reindexes to pass through the transformer cleanly

We’ve done a bunch of reindexes to change the internal model, we should really get this just passing.
So far includes: #2200, #2201, #2210, #2212.

I ran another Miro reindex this morning, which completed successfully. The only item on the transformer DLQ is a Sierra record, so I think this is done!


Add a method to start a new session

Sessionization is now purely based on time since the last event. We could add a method that, if called, resets the session ID and increments the session index.
Possible use cases:

a user switches accounts
a user completes a purchase and returns to the homepage

See also: https://github.com/snowplow/snowplow-objc-tracker/issues/290

Hey @bogaert this can already be done in Android by:

Tracker.pauseSessionChecking()
Tracker.resumeSessionChecking()

The first function shuts down all session checking and the second restarts it, on resumption the session id is incremented.

That's good to know.
I still think there's a case to be made to add a third function, perhaps something like Tracker.startNewSession()? There are 2 reasons:

The function name describes how it's expected to be used.

If a certain event occurs, e.g. a user completes a purchase and returns to the homepage, one would only need to call the one function rather than both function in quick succession.

I'm leaving it open for discussion now. There's some thinking we can do on sessionization in general.

Oh totally agree that we need another function.  Was just mentioning in case you had a pressing case for using something like this!


Share tweet as image

Describe the problem
I want to share a tweet as an image from the sharing options
Describe the solution
Add an option below share tweet content to turn a tweet into an image

Version v3.7.6 implements this feature.


Add Auto width behavior to ItemList

I have rewritten the PR https://github.com/godotengine/godot/pull/39848 which implemented a Auto width functionality in the ItemList node, but never got rebased. It should be the same behavior like using the Auto height feature.
I had the problem that the last 2 letters of a word were not shown. That's why I added 6 pixels to the calculation in line 1481 (item_list.cpp) Please let me know if it is acceptable to hard-code this value.
Closes https://github.com/godotengine/godot/issues/31504

This is my first PR at the GodotEngine. Please tell me if I have done any mistakes or if there is anything I can improve.

Please ask if the original author has abandoned their work, otherwise there's no reason to take it over
Regardless you need to cite them as a coauthor as you've copied their code, you need to get their account name and email from their PR and add them like so:

co-authored-by: Name <email>

The empty line matters

Please ask if the original author has abandoned their work, otherwise there's no reason to take it over, please communicate with other developers

@AThousandShips Thank you for bringing this to my attention and asking Althar93 for me. I'll keep it in mind for next time.

Am I right that the auto_width documentation must be written below auto_height to solve the failling check?

Yes it has to be alphabetical, use --doctool on the built binary to generate automatically

The feature is implemented correctly, but it has problems with fitting to text. See the above comment.

The text is no longer cut, but there is some excessive margin on the right.
https://github.com/user-attachments/assets/ac0b5c30-8cef-421d-9fca-2f7c3163033c

I noticed I had theme_cache.panel_style->get_minimum_size().width  two times in my calculation. I'm checking if thats the problem.

I found the issue, why it is so difficult for me to calculate the spacing:
The H Separation behaves differently on Godot Version 4.2.1 and 4.3
Video of Godot Version 4.2.1

https://github.com/user-attachments/assets/0c2a62ef-2c30-4519-ae2b-1cfb86989c16

Godot Version 4.3

https://github.com/user-attachments/assets/4b4e8ec5-de8d-4d35-9d56-5bbe31fe6304

I will open a bug report for this tomorrow.

I applied the requested changes and fixed a bug that caused the right margin to be too wide when more than one column was used.

The margin problem is fixed.
Though there is a problem where if you increase column count, the size doesn't update immediately:
https://github.com/user-attachments/assets/9a1de7a6-c213-4407-9d74-ef4c8e3c2c9c

I fixed the column update problem. I have noticed that after hiding the visibility of the scrollbar, the size is updated one pixel too late. I could not figure out what is causing this problem.
https://github.com/user-attachments/assets/6a381b4b-e91f-4bfa-a2d9-3a1fe14017ef

Thank you for your quick replies and your patience testing my code so many times!

Thanks!


[Bug]: Deleting duplicate games. [gssoc23]

Give a brief about the bug ✍
Description
country guesser game is added twice
What is the expected behavior? 🤔
Description
Deleting one of the country guesser game
Provide step by step information reproduce the bug 📄
Description
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @thevirengarg !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @thevirengarg ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


BTfRZmWt - Setup React app

also updated README

can we also move backend into it's own folder in this pr


Revert "Update Consensus plugin changes"

Reverts hyperledger/fabric#2287

See comment https://github.com/hyperledger/fabric/pull/2287#issuecomment-234645321


Feat release action

name: Default template
about: Generic template
labels: "feature, needs: AT updates, needs: changelog, needs: branch testing, priority: low"
Component name

Related issue

(#100) Description

Preview

Link(s) to demo page(s) where this element can be viewed:

Link

What has changed and why

Link to discovery documentation (should contain all the planning and requirements for this work):
Testing instructions

Browser requirements
Your component should work in all of the following environments:

[ ] Latest 2 versions of Edge
[ ] Internet Explorer 11 (should be useable, not pixel perfect)
[ ] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[ ] Firefox 68 (or latest version for Red Hat Enterprise Linux distribution)
[ ] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[ ] Latest 2 versions of Safari
[ ] Android mobile device (such as the Galaxy S9)
[ ] Apple mobile device (such as the iPhone X)
[ ] Apple tablet device (such as the iPhone Pro)

Ready-for-merge Checklist
Check off items as they are completed.  Feel free to delete items if they are not applicable.

[ ] Expected files: all files in this pull request are related to one request or issue (no stragglers or scope-creep).
[ ] Tests have been updated to cover these changes.
[ ] Browser testing passed.
[ ] Repository compiles and tests pass.
[ ] Changelog updated (not needed for documentation updates).
[ ] Documentation (README.md, WHY.md, etc.) updated or added.
[ ] Link to the demo recording:
[ ] Approved by designer.

Merging
Please squash when merging and ensure your commit message uses conventional commit formatting.
Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!

Todo for myself after vacation: lerna-generated conventional commits not working yet. Generated files have no entries.


WidgetBinding analyzer noise for Flutter >=3

Change introduced in this commit:
https://github.com/DataDog/dd-sdk-flutter/commit/a6a66306011d20566c258d39203659feca871546
results in noisy analyzer when running from CLI:
./../../../.pub-cache/hosted/pub.dartlang.org/datadog_flutter_plugin-1.0.0-rc.2/lib/src/rum/rum_long_task_observer.dart:44:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
 - 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('../../../../Utils/flutterSdk/flutterStable/packages/flutter/lib/src/widgets/binding.dart').
    WidgetsBinding.instance?.addObserver(this);

This makes tests output hard to read.

Hi @charafau
Yes, I'm with you, I hate it, but fixing this will break Flutter < 3 and I'm not sure anyone has found a good workaround other than us maintaining two versions of the library (which is what we're doing with datadog_tracking_http_client).
See https://github.com/dart-lang/sdk/issues/33249 for more on this.
Sorry 😒

Neverymind @charafau. Someone pointed me to a fix. We'll have it in the next version.

That's great to hear! Thank you!

@fuzzybinary – should I still be seeing this with 1.0.0-rc.2?
../../../../../Developer/flutter/.pub-cache/hosted/pub.dartlang.org/datadog_flutter_plugin-1.0.0-rc.2/lib/src/rum/rum_long_task_observer.dart:44:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
 - 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('../../../../../Developer/flutter/packages/flutter/lib/src/widgets/binding.dart').
    WidgetsBinding.instance?.addObserver(this);

Never mind – I incorrectly took the changelog message for rc.2 to mean it contained this fix but now see that there's a later commit yet to be released.

Yeup... sorry, rc3 will contain this. We should be able to get it out in the next day or so.

This is now live in 1.0.0-rc.3


[bug] dynamic create webview in current window  crash  in  windows 10

Describe the bug
#[tauri::command]
pub fn create_webview_inner(
window: tauri::Window,
url: String,
x: f64,
y: f64,
width: f64,
height: f64,
) -> Result<String, String> {
let window_id = WINDOW_ID.fetch_add(1, atomic::Ordering::SeqCst);
let label = format!("webview_{}", window_id);
let webview_builder =
tauri::webview::WebviewBuilder::new(label.clone(), WebviewUrl::App(url.parse().unwrap()));
let _webview = window.add_child(
webview_builder.auto_resize(),
LogicalPosition::new(x, y),
LogicalSize::new(width, height),
);
Ok(label)
}
The above code can be allowed normally on Mac, but cannot be allowed on Windows
Reproduction
No response
Expected behavior
No response
Full tauri info output
thread 'main' has overflowed its stack

Stack trace
No response
Additional context
No response

I have encountered this issue as well.

Can one of you please post the output of the tauri info command as required by the issue template?
And if you're on v2, do you have tauri's unstable feature flag enabled or not? (if you don't know then the answer is probably no)

Similar issues.
import { WebviewWindow } from '@tauri-apps/api/webviewWindow'
import { getCurrent } from '@tauri-apps/api/window'
...
	const webview = new Webview(getCurrent(),`${app.name}-webview`, options);
	webview.once('tauri://created', function (d) {
		console.log('tauri://created')
		console.log(d)
	});
	webview.once('tauri://error', function (e) {
		console.log('tauri://error')
		console.log(e)
	});
...
[dependencies]
fix-path-env = { git = "https://github.com/tauri-apps/fix-path-env-rs" }
tauri = { version = "=2.0.0-beta.22", features = ["macos-proxy", "unstable"] }
tauri-utils = "=2.0.0-beta.17"
tauri-plugin-shell = "=2.0.0-beta.5"
serde = { version = "1", features = ["derive"] }
serde_json = "1"
tauri-plugin-process = "=2.0.0-beta.5"
tauri-plugin-http = "=2.0.0-beta.5"
tauri-plugin-os = "=2.0.0-beta.5"
tauri-plugin-fs = "=2.0.0-beta.7"
tauri-plugin-deep-link = "=2.0.0-beta.6"

Whether in Win10/Win11, creating a window will crash, tauri://created It will happen, but there are no errors,

@lindongchen Does this also happen if you remove the unstable flag?

@lindongchen Does this also happen if you remove the unstable flag?

error[E0599]: no method named add_child found for struct tauri::Window in the current scope
--> src\webview.rs:35:27
|
35 |     let _webview = window.add_child(
|                    -------^^^^^^^^^ method not found in Window
error[E0599]: no method named add_child found for struct tauri::Window in the current scope
--> src\webview.rs:71:27
|
71 |     let _webview = window.add_child(
|                    -------^^^^^^^^^ method not found in Window
error[E0599]: no method named get_webview found for struct AppHandle in the current scope
--> src\webview.rs:81:22
|
81 |     match app_handle.get_webview(label) {

I have tracked the source code and found that many functions are enabled under the unstable flag, so removing the unstable flag seems meaningless @FabianLars

Apologies, i only looked at your js example and forgot about the initial issue code...

May I know which version can be fixed

The implementations behind the unstable flag currently do not get much priority so i can't give you an ETA.

The implementations behind the unstable flag currently do not get much priority so i can't give you an ETA.

I have a very important project that relies on this feature. Can you help optimize it

No, sorry. I don't have any spare time myself.
One thing I just noticed though, did you ever try making your create_webview_inner command async? That was already a requirement for webview/window creation on windows in v1 so maybe it's the issue here (though it should cause a deadlock, not a crash).

Check src-tauri/capabilities/desktop.json for duplicate permissions. Duplicate permissions here will cause a stack overflow on windows - no idea why. Tested on Win10/11!


Clicking on internal links in the API Guide moves the entire Help panel

Start with a fresh browser
Pull up the Help / API Guide
Click on "Available Fields"
The entire help panel will move up in the browser and now be flush with the top of the top nav bar

Duplicate of #944


The Safari extension doesn't work at all

Sitting on a OS X 10.11.2 Mini here and Safari 9.0.2 tries to run the extension. But beyond showing me the little button I can't get him to do anything. Tried several pages but never go any response from the extension; I can click it but nothing ever happens.

I'm having a similar issue.  Could it be that the bookmarklet is set to use http and the site is on https?

Same here, anything new ?

Same here. Button appears but nothing happens when clicking it.

+1

The problem exist for 3 months and still no answer... doesn't sound good.

+1

I guess yslow extension isn't supported anymore. No update for 2 year and nobody seems to be around anymore... Time to move on guys.

I can't get it to work either... I get some kind of error message about not being able to retrieve anything.  I can't get the exact error message now because I cannot get yslow to pop up anymore.


S3 Bucket  PutBucketAclInfo and  PutBucketOwnershipControls never ending reconcile.

provider version 0.43.1
I'm trying to setup a bucket with ACL Enabled and also bucket owner preferred.  and while the resource appeared Ready And Synced in the logs and CloudTrail i see a never ending stream of  PutBucketAcl, PutBucketOwnershipControls atempts
I tried not setting the canned acl or setting false to all publicAccessBlockConfiguration
apiVersion: s3.aws.crossplane.io/v1beta1
kind: Bucket
metadata:
  name: bucket-name
spec:
  forProvider:
    acl: private
    publicAccessBlockConfiguration:
      blockPublicAcls: false
      blockPublicPolicy: false
      ignorePublicAcls: false
      restrictPublicBuckets: true
    serverSideEncryptionConfiguration:
      rules:
        - applyServerSideEncryptionByDefault:
            sseAlgorithm: AES256
          bucketKeyEnabled: true
    locationConstraint: "us-east-1"
    objectOwnership: BucketOwnerPreferred
    versioningConfiguration:
      status: Enabled
    paymentConfiguration:
      payer: BucketOwner
  providerConfigRef:
    name: provider-here

Currently, PutBucketACL and PutBucketOwnershipControls are invoked on every reconcile. This is actually not trivial to fix because the AWS response is very different from the put request.
One would have to convert spec and AWS response into a type that is comparable by slicing the comma seperated values into arrays. Also, the canned acl needs to be included on top of that which sets a predefined set of ACL properties.


Add support for \Illuminate\Auth\Access\AuthorizationException and such.

When using the authorization mechanics from Laravel, a failed Policy check will throw a "\Illuminate\Auth\Access\AuthorizationException" which goes through Dingo and becomes a 500 error instead of a 403.
Ref: https://laravel.com/docs/5.2/authorization#controller-authorization

Its also require "Illuminate\Http\Exception\HttpResponseException".
It thrown when using FormRequest validation, and Digno does not handle it.

Is it worth adding a default handler for the AuthorizationException and simply rethrowing an AccessDeniedException? You can do it manually like so...
$this->app['api.exception']->register(function (AuthorizationException $exception) {
    throw new AccessDeniedHttpException($exception->getMessage(), $exception);
});

@dominikveils, Dingo has its own FormRequest class you can extend which throws exceptions that can be handled properly.
Or just use a handler like above.


deadlock when running more than one bot on the same oobabooga backend.

If at one point 2 bots happen to do the inference at the same time, both bots get stuck and also oobabooga itself will hang.
At that point, I can either kill all processes, or just kill one of the bots and wait a little bit until the remaining bot and Webui suddenly start working again
Right now my only option to run 2 bots is also to run 2 copies of Oobabooga which forces me to running two separate copies of webui (different ports for all listeners)
If what I described here isn't actually a bug, please make it clear and feel free to close this issue.

I noticed an issue - i dont know if it relates.
But if you refresh the webui while the bot is running - it will default to be displayed as the bot if off. And you can press the "start oobabot" button again while its running, (whitch would be typically grayed out)
If you do indeed press that button then the bot would end up replying twice over to every message untill ooba is fully restarted

as you can see in the picture above. The bot is already running , and "stop" button is grayed out. But the "start" button is clickable.

For anyone's reference, I think this commit is a good starting point, as it coincides with around the time things stopped working:
https://github.com/oobabooga/text-generation-webui/commit/d37a28730dc208ca5fbff50b32818a93a305b5ef

@harlyh Confirmed that the Oobabooga commit above was the one that added the bug.  Until it's fixed, you should be able to Oobabooga off revision 7dc87984a2347794beed957a1923203b70a597b9 without issue.

With Oobabooga's permission, I've posted a PR which will fix the problem on their end here.  https://github.com/oobabooga/text-generation-webui/pull/3048
TBD to see if the maintainers there agree with the approach or not, but at the very least I know that approach will fix it.  Stay tuned!

PR accepted, this should be fixed if you pull the latest text-generation-webui code.


write hfev3 error

Hi, I'm trying to write hfev3 to real disk... but I got two king of error:
./gw write /Users/bigsur/Downloads/Back_To_The_Future_2_Image_Works_AtariST_DiskImage/BackToTheFutureII_ImageWorks_Disk1of1_AtariST_Dump/BackToTheFutureII_ImageWorks_Disk1of1_AtariST_Dump0.scp.HxC_HFEv3.hfe
Writing c=0-81:h=0-1
T0.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T0.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T1.0: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T1.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T2.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T2.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T3.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T3.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T4.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T4.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T5.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T5.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T6.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T6.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T7.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T7.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T8.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T8.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T9.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T9.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T10.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T10.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T11.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T11.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T12.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T12.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T13.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T13.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T14.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T14.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T15.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T15.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T16.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T16.1: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T17.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T17.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T18.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T18.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T19.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T19.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T20.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T20.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T21.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T21.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T22.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T22.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T23.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T23.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T24.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T24.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T25.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T25.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T26.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T26.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T27.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T27.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T28.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T28.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T29.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T29.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T30.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T30.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T31.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T31.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T32.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T32.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T33.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T33.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T34.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T34.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T35.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T35.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T36.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T36.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T37.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T37.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T38.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T38.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T39.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T39.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T40.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T40.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T41.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T41.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T42.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T42.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T43.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T43.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T44.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T44.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T45.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T45.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T46.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T46.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T47.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T47.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T48.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T48.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T49.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T49.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T50.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T50.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T51.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T51.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T52.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T52.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T53.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T53.1: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T54.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T54.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T55.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T55.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T56.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T56.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T57.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T57.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T58.0: Writing Track (Flux: 199.8ms period, 219.7 ms total, Terminate at index)
T58.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T59.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T59.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T60.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T60.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T61.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T61.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T62.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T62.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T63.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T63.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T64.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T64.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T65.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T65.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T66.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T66.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T67.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T67.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T68.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T68.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T69.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T69.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T70.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T70.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T71.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T71.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T72.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T72.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T73.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T73.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T74.0: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T74.1: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T75.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T75.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T76.0: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T76.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T77.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T77.1: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T78.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T78.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T79.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T79.1: Writing Track (Flux: 199.8ms period, 219.7 ms total, Terminate at index)
Traceback (most recent call last):
File "./gw", line 8, in
sys.exit(main())
File "/Users/bigsur/Library/Python/3.8/lib/python/site-packages/greaseweazle/cli.py", line 69, in main
res = main(argv)
File "/Users/bigsur/Library/Python/3.8/lib/python/site-packages/greaseweazle/tools/write.py", line 246, in main
util.with_drive_selected(
File "/Users/bigsur/Library/Python/3.8/lib/python/site-packages/greaseweazle/tools/util.py", line 323, in with_drive_selected
fn()
File "/Users/bigsur/Library/Python/3.8/lib/python/site-packages/greaseweazle/tools/write.py", line 247, in
lambda: write_from_image(usb, args, image), usb, args.drive)
File "/Users/bigsur/Library/Python/3.8/lib/python/site-packages/greaseweazle/tools/write.py", line 71, in write_from_image
wflux = track.flux_for_writeout(cue_at_index = not no_index)
File "/Users/bigsur/Library/Python/3.8/lib/python/site-packages/greaseweazle/track.py", line 155, in flux_for_writeout
wflux = self._flux(for_writeout=True, cue_at_index=cue_at_index)
File "/Users/bigsur/Library/Python/3.8/lib/python/site-packages/greaseweazle/track.py", line 173, in _flux
assert 0 < s < e < bitlen
AssertionError
or if I set --version=3 optionI got
./gw write /Users/bigsur/Downloads/Back_To_The_Future_2_Image_Works_AtariST_DiskImage/BackToTheFutureII_ImageWorks_Disk1of1_AtariST_Dump/BackToTheFutureII_ImageWorks_Disk1of1_AtariST_Dump0.scp.HxC_HFEv3.hfe::version=3
** FATAL ERROR:
/Users/bigsur/Downloads/Back_To_The_Future_2_Image_Works_AtariST_DiskImage/BackToTheFutureII_ImageWorks_Disk1of1_AtariST_Dump/BackToTheFutureII_ImageWorks_Disk1of1_AtariST_Dump0.scp.HxC_HFEv3.hfe::version=3: Unrecognised file suffix '.hfe::version=3'
Known suffixes:
.a2r   .adf   .ads   .adm   .adl   .d64   .d71   .d81   .d88   .dcp   .dim
.dsd   .dsk   .edsk  .fdi   .hdm   .hfe   .ima   .img   .imd   .ipf   .mgt
.msa   .raw   .sf7   .scp   .ssd   .st    .td0   .xdf
this on macOS Bigsure
./gw info
Host Tools: 1.15.1
Device:
Port:     /dev/cu.usbmodem144301
Model:    Greaseweazle F1 Plus (Unbuffered)
MCU:      72MHz, 20kB SRAM
Firmware: 1.4
Serial:   GW066BFF303538524D43052323
USB Rate: Full Speed (12 Mbit/s)
but same if I use gui GreaseweazleGUI 2.116 on windows with host tools 1.15
Writing c=0-81:h=0-1
T0.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T0.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T1.0: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T1.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T2.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T2.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T3.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T3.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T4.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T4.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T5.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T5.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T6.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T6.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T7.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T7.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T8.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T8.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T9.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T9.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T10.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T10.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T11.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T11.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T12.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T12.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T13.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T13.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T14.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T14.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T15.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T15.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T16.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T16.1: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T17.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T17.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T18.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T18.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T19.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T19.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T20.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T20.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T21.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T21.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T22.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T22.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T23.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T23.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T24.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T24.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T25.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T25.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T26.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T26.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T27.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T27.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T28.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T28.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T29.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T29.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T30.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T30.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T31.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T31.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T32.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T32.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T33.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T33.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T34.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T34.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T35.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T35.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T36.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T36.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T37.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T37.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T38.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T38.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T39.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T39.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T40.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T40.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T41.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T41.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T42.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T42.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T43.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T43.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T44.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T44.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T45.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T45.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T46.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T46.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T47.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T47.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T48.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T48.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T49.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T49.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T50.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T50.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T51.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T51.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T52.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T52.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T53.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T53.1: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T54.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T54.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T55.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T55.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T56.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T56.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T57.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T57.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T58.0: Writing Track (Flux: 199.8ms period, 219.7 ms total, Terminate at index)
T58.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T59.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T59.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T60.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T60.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T61.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T61.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T62.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T62.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T63.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T63.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T64.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T64.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T65.0: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T65.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T66.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T66.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T67.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T67.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T68.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T68.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T69.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T69.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T70.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T70.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T71.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T71.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T72.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T72.1: Writing Track (Flux: 199.8ms period, 219.9 ms total, Terminate at index)
T73.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T73.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T74.0: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T74.1: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T75.0: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T75.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T76.0: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T76.1: Writing Track (Flux: 199.8ms period, 220.0 ms total, Terminate at index)
T77.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T77.1: Writing Track (Flux: 199.8ms period, 220.1 ms total, Terminate at index)
T78.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T78.1: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T79.0: Writing Track (Flux: 199.8ms period, 219.8 ms total, Terminate at index)
T79.1: Writing Track (Flux: 199.8ms period, 219.7 ms total, Terminate at index)
Traceback (most recent call last):
File "C:\Users\runneradmin\AppData\Roaming\Python\Python311\site-packages\cx_Freeze\initscripts_startup_.py", line 130, in run
File "C:\Users\runneradmin\AppData\Roaming\Python\Python311\site-packages\cx_Freeze\initscripts\console.py", line 16, in run
File "gw.py", line 3, in
File "C:\hostedtoolcache\windows\Python\3.11.4\x64\Lib\site-packages\greaseweazle\cli.py", line 69, in main
File "C:\hostedtoolcache\windows\Python\3.11.4\x64\Lib\site-packages\greaseweazle\tools\write.py", line 246, in main
File "C:\hostedtoolcache\windows\Python\3.11.4\x64\Lib\site-packages\greaseweazle\tools\util.py", line 323, in with_drive_selected
File "C:\hostedtoolcache\windows\Python\3.11.4\x64\Lib\site-packages\greaseweazle\tools\write.py", line 247, in
File "C:\hostedtoolcache\windows\Python\3.11.4\x64\Lib\site-packages\greaseweazle\tools\write.py", line 71, in write_from_image
File "C:\hostedtoolcache\windows\Python\3.11.4\x64\Lib\site-packages\greaseweazle\track.py", line 155, in flux_for_writeout
File "C:\hostedtoolcache\windows\Python\3.11.4\x64\Lib\site-packages\greaseweazle\track.py", line 173, in _flux
AssertionError
or
** FATAL ERROR:
C:\bttfII.hfe::version=3: Unrecognised file suffix '.hfe::version=3'
Known suffixes:
.a2r   .adf   .ads   .adm   .adl   .d64   .d71   .d81   .d88   .dcp   .dim
.dsd   .dsk   .edsk  .fdi   .hdm   .hfe   .ima   .img   .imd   .ipf   .mgt
.msa   .raw   .sf7   .scp   .ssd   .st    .td0   .xdf
C:\greaseweazle-1.15-2.1>
maybe I misunderstand and hfev3 isn't to be useful?

Can you please upload or attach the problematic hfev3 image file? Hfev3 is mainly intended for emulation (Goteks) but it should not cause a crash in gw write! So I will reproduce this and fix the bug. Thank you.

hfev3.zip
in the zip file the hfe disk images (2xBTTFII, R-Type, SOTB) that give Assertion Error....
the other one, gives another error but maybe a faulty image
./gw write /Users/bigsur/Downloads/bombuzal-image-works-disk-1of-1-atari-st.scp.-02-data-hx-c/Bombuzal/Bombuzal_ImageWorks_Disk1of1_AtariST.scp.HxC_HFEv3.hfe
** FATAL ERROR:
HFEv3: Short track data
hope can be helpful... TNX

By the way what is the source of the hfev3 files? HxC tools?


Update README.md for clarity and concision

Reworded several sentences and paragraphs for clarity and concision. No key
information or links were altered.

I'm not really convinced that adding "Godot" in all those sentences makes things clearer. We know we are a talking about Godot, it's its Readme.md file.

Hi all, thank you for your feedback. I've made more updates based on your comments.

@akien-mga @groud Were there any other changes you guys would like to see before approving the pull request?

I think almost all the "Godot" you added should actually be removed. It make the writting style heavy.
Replacing "It" by "Godot" does not really improve the consicion.
But to be honest, I'm not even conviced this PR improves the text at all. I think it was already clear before, the new text is still clear but just written in another way.

Thanks for the new feedback @groud. I've made the changes you mentioned, I appreciate the input.
I do believe the PR improves the text in multiple ways. My goal was to maintain all of the original information, and just polish the writing a bit. For example, some sentences were fragmented by missing words, and others contained incorrect use of definite articles, there was some missing punctuation etc. All of this stuff is relatively minor, but summed together I thought it was worth the effort.

It looks ok to me now. If other people are ok with the changes we can merge.

Oh sorry, you will have to squash the commit together though.

 Let me know if there's anything else you need.
Thanks :)

To be honest I still agree with @groud, I don't see why repeating "Godot" in every single sentence makes the readme clearer. It's the readme file of the godotengine/godot repository, which is titled ## Godot Engine at the top. I don't see why we'd need to be more explicit than that.
The section ### Documentation and demos now mentions Godot 5 times (once per sentence), against only once previously.
In #### Free, open source and community-driven we already mentioned Godot twice, no need to repeat it a third time.

Closing this as there is no support for merging the PR.
Sorry, we should have caught this sooner and not asked you to spend further time on edits.
We still thank you for spending the time helping to improve Godot!


Remove spell check code action

This isn't working in the following case, so removing support for this code action.

Revert tracking issue: https://github.com/dotnet/aspnetcore/issues/31808

Hmm, is it a C# issue?

Hmm, is it a C# issue?

Not entirely sure, it just no-ops on code action resolution. My bet is it's an issue with the formatting of the edited code action breaking down in the mapping layer (similar to what happened with FQN).
Using the unformatted code action endpoint may resolve it, but that starts to set a somewhat dangerous precedent. Warrants further investigation.

@allisonchou do you know why we get the Path->Math spell check correction when Math.PathSeperator is not a valid term either?

@TanayParikh hmm, not sure. I tried repro'ing in a regular C# file just now and not seeing the same thing.


Add test case for incompatible target filtering

@illicitonion I believe this PR should be merged into branch incompatible-target and not main, but I could not figure out how to specify that from the github PR UI


Improve schema implementation to deal with ByteBuf

Is your feature request related to a problem? Please describe.
Currently all the schema implementations deal with byte[] only. It introduces a lot of object allocations and produces garbages, which is not friendly to Java language.
We should improve the schema interface to handle ByteBuf or ByteBuffer.

This has been implemented by #5123


Add .fit file support

is it possible to add .fit files to this?

I have recently been in the same situation and included a small function that converts fit to gpx files.
Are you interested in my solution?


swagger-ui visit swagger.yml file in the  monocular

    I have installed monocular, now want to visit monocular api interface  by  the swagger-ui , I noticed in the monocular source code has a swagger.yml, how can direct access to the deployment of monocular applications swagger.yml?
    For example, monocular ui's first page is http: //<IP_ADDRESS>, so then swagger.yml file path is "http://<IP_ADDRESS>/swagger.yml"?  or " http://<IP_ADDRESS>/api/swagger.yml ? or others?

Did anyone know?

Did anyone know?

@mistyle the swagger ui is not meant to be exposed via the API. You can load it into a swagger UI viewer if you wish you view it.


Use third party ip geolocation api

To easily get visitor ip address and detail geo location (country name, city name, lat, lng position, etc).
Is it possible to add (optionally) third party ip geolocation API, such as ipgeolocationapi.com or ipify.org
(psst... the ipify has node.js library)
Maybe it can answer #437 dan #444 :smiley:

The app already uses an internal lookup database. That's how it's able to determine the country from the IP address. It's a design decision not to collect more data than just country.


fastlane env --quiet option or --force

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
Would like to run bundle exec fastlane env on our CI box.  piping in 'n' results in the same error.  Would like a --force option if possible :)
Complete output when running fastlane, including the stack trace and command used
bundler: failed to load command: fastlane (/Users/distiller/ios/vendor/bundle/ruby/2.3.0/bin/fastlane)
FastlaneCore::Interface::FastlaneCrash: [!] Could not retrieve response as fastlane runs in non-interactive mode

Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
would like fastlane env --force or fastlane env --quiet as a possibility :)
Partial
fastlane gems

Gem
Version
Update-Status

credentials_manager
0.16.2
✅ Up-To-Date

fastlane_core
0.53.0
✅ Up-To-Date

spaceship
0.36.2
✅ Up-To-Date

cert
1.4.3
✅ Up-To-Date

deliver
1.14.5
✅ Up-To-Date

frameit
3.0.0
✅ Up-To-Date

gym
1.11.3
✅ Up-To-Date

sigh
1.11.2
✅ Up-To-Date

match
0.10.0
✅ Up-To-Date

pem
1.3.2
✅ Up-To-Date

pilot
1.11.1
✅ Up-To-Date

produce
1.2.1
✅ Up-To-Date

scan
0.13.1
✅ Up-To-Date

screengrab
0.5.5
✅ Up-To-Date

snapshot
1.16.2
🚫 Update availaible

supply
0.7.1
✅ Up-To-Date

fastlane
1.106.2
✅ Up-To-Date

Oh wow, nice catch, thanks 👍  Working on this right now

I just pushed https://github.com/fastlane/fastlane/pull/6782  🚀This will be in the next release


get rid of constants and replace with constant module

closed with the new parameterized (new-std ...) construct


Octant leaks the cluster's admin.conf and a malicious pod/exposid worker node can gain cluster administrator privileges

Summary
When  Octant deployed in the Kubernetes cluster as a pod, it leaks the cluster's admin.conf and a malicious pod/exposed worker node can gain cluster administrator privileges
What steps did you take and what happened:
1.Deploy Octant as a Pod:
Because Octant does not provide any official guide for deploying the Octant as a pod in a Kubernetes cluster, I deploy the Octnat  as a Pod following the guide of antrea.io(https://antrea.io/docs/v1.9.0/docs/octant-plugin-installation/)
kubectl create secret generic octant-kubeconfig --from-file=admin.conf=/home/younaman/.kube/conf -n kube-system
kubectl apply -f https://github.com/antrea-io/antrea/blob/main/build/yamls/antrea-octant.yml
2.Access Octant Web Service from a pod/worker node:
Octant automatically loads admin.conf when it starts up, and accesses the UI with the kubernetes-admin context.
A malicious pod can easily obtain the "data" of the secret named "octant-kubeconfig" from the "Config and Storage/Secret/" in dashboard UI, which is my cluster's admin.conf, and do whatever he/she likes to the whole cluster.
What did you expect to happen:
It looks like the Octant intended to be run as a desktop/client application, and the Octant has no access control to deploy inside a cluster at all. As far as I am concerned, the Octant should enable the authentication feature(i.e., ask for token or kubeconfig when a user access the dashboard UI), and do not use the cluster's admin.conf to access the cluster automatically when accessing the dashboard UI
Anything else you would like to add:
As mitigation, I try to mitigate the risk following these steps:
1.Do not use the "admin.conf" to deploy and install the Octant:
This will prevent Octant from finding /kube/admin.conf from KUBECONFIG on startup, and the Octant can not create context automatically. As a result, the Octant will force the user to upload the admin.conf they have when they first access the
web service. And create context according to the file upload by user.
To be more specifically, it triggers the func (l *LoadingManager) UploadKubeConfig(), which create a temporary file named kubeconfigxxxxxxxx under the /tmp/octant directory. And the
Octant create context according to this temporary file.
For example:
kubectl create secret generic octant-kubeconfig --from-file=/home/younaman/.kube/conf -n kube-system.
kubectl apply -f https://github.com/antrea-io/antrea/blob/main/build/yamls/antrea-octant.yml
2.Restart the Octant pod after each access to the dashboard UI. Thus, the Octant can not find /kube/admin.conf on start up, and will force the user to upload his/her own admin.conf and create a
new /tmp/octant/kubeconfigxxxxxxxx temporary file.
Please notice that this so-called "mitigation method requires a lot of manual steps. To solve this problem fundamentally, the Octnat may need to add authentication/ access control restrictions when accessing the dashboard UI.
Environment:

Octant version (use octant version):
Version:  0.24.0
Git commit:  5a8648921cc2779eb62a0ac11147f12aa29f831c
Built:  2021-09-09T01:54:00Z
Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"clean", BuildDate:"2022-06-15T14:22:29Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"clean", BuildDate:"2022-06-15T14:15:38Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc):
A three-node Kubernetes cluster, each node is Ubuntu 20.04 TLS.

By the way, I have reported this vulnerability by mailing the<EMAIL_ADDRESS>but there is no response last three weeks. So I report this issue through github.

Hi @younaman ,
As far as I know, WMware Tanzu / Octant do not officially support deploying to Kubernetes. In that regard, I'm not sure your issue will be addressed because it concerns an unsupported deployment scenario.
Nonetheless, I have my own repo that provide an Helm chart to deploy Octant on a Kubernetes cluster. The Helm chart is configurable so you can customize or provide your own RBACs (excluding get on secret for example).

@aleveille Thanks for your reply! For your first point, Octant officially does not support deploying to Kubernetes, however, as I listed in my comments(https://antrea.io/docs/v1.9.0/docs/octant-plugin-installation/), other third-party apps (such as antrea) deploy the octant as a dashboard UI in a cluster officially. So my issue is not an "unsupported deployment scenario", and octant/other third-party apps should consider this scenario as far as I am concerned.
For your second point, you offer me a good chart! I will try on my local environment, and I will tell you if it solves my considerations:)
Besides, are there any "official developers" or "official maintainers"  who can give us (me and @aleveille) more comments?


Federated user has permissions to send/receive messages

Describe the bug
Federated user is used only for console access, so there should not be authorization rule for sending/receiving

Federated users are no loner a feature, closing.


Local playback does not work on arm

When selecting Built-in Audio Stereo as output in the addon configuration, local playback (speaker: "Computer") does not work and fails with these messages in the log:
Addon Audio Config

Log on RPi3B+ 32bit (armv7)
[  LOG]   laudio: Cannot open shared library /usr/lib/arm-linux-gnueabihf/alsa-lib/libasound_module_ctl_pulse.so ((null): /usr/lib/arm-linux-gnueabihf/alsa-lib/libasound_module_ctl_pulse.so: cannot open shared object file: No such file or directory)
[  LOG]   laudio: Failed to attach mixer 'default': No such device or address
[  LOG]   laudio: Could not open mixer 'default' ('(null)')

Log on RPi4B 64bit (aarch64)
[  LOG]   laudio: Cannot open shared library /usr/lib/aarch64-linux-gnu/alsa-lib/libasound_module_ctl_pulse.so ((null): /usr/lib/aarch64-linux-gnu/alsa-lib/libasound_module_ctl_pulse.so: cannot open shared object file: No such file or directory)
[  LOG]   laudio: Failed to attach mixer 'default': No such device or address
[  LOG]   laudio: Could not open mixer 'default' ('(null)')

Fortunately this can be fixed by adding libasound2-plugins to RUN_DEPS in the Dockerfile on both of these platforms.

Ah sorry, I should have specified that you need to use "pulseaudio" as the backend for local, not alsa.
Can you try and confirm it does work ? libasound2-plugins has a plugin to redirect alsa output to pulseaudio, which is why it solves it too.
audio {
...
	type = "pulseaudio"
...
}

If it works fine for you I'll add a note to the readme

Thanks for this clarification! I just rebuilt the addon without libasound2-plugins and can confirm that applying your change in /share/forked-daapd/forked-daapd.conf makes it work.

Great, thanks for the confirmation !


[WIP][SPARK-44863][UI] Add a button to download thread dump as a txt in Spark UI

What changes were proposed in this pull request?

This PR added a button to download thread dump as a txt w.r.t. jstack formatting
Why are the changes needed?

The formatting of raw jstack can be relatively easy to read and analyze using various thread tools.
Does this PR introduce any user-facing change?

How was this patch tested?

UI change

Raw Dump File
driver.txt
Reporting by external tools
https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMjMvMDgvMjAvZHJpdmVyLnR4dC0tMTMtNTMtMjI=&
Was this patch authored or co-authored using generative AI tooling?

no

cc @gengliangwang @gatorsmile

also @sarutak and @jasonli-db

cc @jasonli-db and @gengliangwang  would you mind take a look?

thank you all, merged to master
https://github.com/apache/spark/pull/42654 is for branch 3.5

@yaooqinn thank you so much for working on this!


JOSS review: Installation

@miniufo - well done on your submission to JOSS.
As part of my review of your submission (see https://github.com/openjournals/joss-reviews/issues/5510), I have some questions/suggestions regarding software installation:

In the "how to install" (https://github.com/miniufo/xinvert#2-how-to-install) section of your README file it says "install via pip (not yet)" but as far as I can tell it can be installed by pip. What is the meaning of "not yet"?
Do you think it would be advantageous to also make the package available via conda (i.e. conda-forge) for users who manage their python environments using conda?

that's right.  I forgot to update this.  (not yet) should be removed.
Definitely should be in conda.  Right now I send a PR to conda for another package here, which is the first time I do this.  I am not sure how long it would take (or maybe I do something incorrect).  Maybe you can point me to the right path on how to make xinvert available via conda.

Your xgrads PR looks fine to me - hopefully they will action it soon.
Since xinvert is available via pip I don't think waiting for it to be available via conda should delay your JOSS publication. It would be nice to have it available via conda eventually, but it's not absolutely necessary for publication with JOSS.

That's great.  I'll follow the steps of xgrads and make a PR of adding xinvert to conda recipe.

Hi @DamienIrving, I've removed 'not yet' in the README.md.  Also, I've sent a PR to conda recipe, waiting it to be merged.  Please see if this issue is fixed now.

Awesome. Thanks, @miniufo.


Calculate UEF; move simulation code into HPWH

Description

Enables calculation of UEF (uniform energy factor) for a specified Model (preset or file). The code is placed within the test suite and follows the form of existing tests. However, the functionality serves only as a utility at this stage, so no new tests are added. The UEF value is simply displayed on the console upon completion.
The UEF calculation routine runs four simulations using synthetic schedule profiles, while tracking the total volume of water drawn and the total energy "consumed", then applies the definition from document EERE–2019–BT–TP–0032. No variations in water density or specific heat capacity were included.
Previously, HPWH model tests used simulation code implemented in main.cc. These did not have the form of a set of routines callable from other projects in HPWHsim, so the simulation code was transformed into a set of HPWH member functions. Considerable clean-up and reorganization of the simulation code was performed, which enables broader utility than was previously available.
One evident error in the previous code that calculated modified draws for year-long tests was found. This resulted in change of some values in DHW_YRLY.csv, but will have no impact on uses of HPWHsim that do not involve the built-in simulation routines.
The previous code performed energy-balance checks when running simulations, but did not report the results. Enabling a failure for energy-balance errors revealed a previously unidentified energy-balance issue on the order of 0.01% for a model with an external condenser configuration. Therefore, the failure mechanism was temporarily disabled, pending address of this issue in a separate PR.
An additional option was added to allow specification in testInfo.txt of temperature units as degF.

Author Progress Checklist:

[X] Open draft pull request

[X] Make title clearly understandable in a standalone change log context
[X] Assign yourself the issue
[X] Add at least one label (enhancement, bug, or maintenance)
[ ] Link the issue(s) addressed by this PR (under "Development" in the sidebar menu)

[X] Make code changes (if you haven't already)
[X] Self-review of code

[X] My code follows the style guidelines of this project
[X] I have added comments to my code, particularly in hard-to-understand areas
[X] I have only committed the necessary changes for this fix or feature
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have ensured that my fix is effective or that my feature works as intended by:

[x] exercising the code changes in the test framework, and/or
[X] manually verifying the changes (as explained in the the pull request description above)

[X] My changes pass all local tests
[X] My changes successfully passes CI checks
[X] Add any unit test for proof and documentation.
[X] Merge in main branch and address resulting conflicts and/or test failures.

[X] Move pull request out of draft mode and assign reviewers
[ ] Iterate with reviewers until all changes are approved

[ ] Make changes in response to reviewer comments
[ ] Merge in main branch and address resulting conflicts and/or test failures.
[ ] Re-request review in GitHub

Reviewer Checklist:

[ ] Read the pull request description
[ ] Perform a code review on GitHub
[ ] Confirm all CI checks pass and there are no build warnings
[ ] Pull, build, and run automated tests locally
[ ] Perform manual tests of the fix or feature locally
[ ] Add any review comments, if applicable
[ ] Submit review in GitHub as either

[ ] Request changes, or
[ ] Approve

[ ] Iterate with author until all changes are approved

This works, but it's not exactly what I had in mind. I was envisioning a method on a HPWH object like double HPWH::calculateUEF(). It wouldn't rely on external data files, but have the draw profiles compiled into the class as a private static data member.


Use Ubuntu18.04/Bionic in travis build

Coverage decreased (-0.01%) to 87.273% when pulling 75a643fb306ba59e23ee9e9f188ca118f2f9533e on PeterAlfredLee:travis_test into 05a995ee725f153b39be111c8b51adbed24d30a4 on apache:master.


stray blue stroke highlight

I had a stray blue stroke highlight leftover after moving a shape away- maybe related to the use of undo/redo
from Eric

@ericr can you add repro steps?


Overriding Views not working for me

Laravel: v 5.6
Voyager: v1.1
PHP: 7.0
Database:mysql

Description:
i am trying to override a view and its not working for me,
as suggested in doc,
i have created folder as Myproject/resource/views/vendor/voyager/{slug}
created a hello there file in the name of browse.blade.php
when i refresh the page, its not talking... instead refers to tcg/voyage..../browse.blade.php

Please post the full path to the file you have created plus the slug of the bread you want to override.


'sample linkage' may not always be a GUID

Current description of slot:sample link
"A unique identifier to assign parent-child, subsample, or sibling samples. This is relevant when a sample or other material was used to generate the new sample."
Because we no longer required a source material identifier or sample GUID (GUID is assigned by NMDC) the user may not have a GUID to provide sample links. We should update the description to say "The sample name of samples to be linked to this sample. This should match a sample name provided to NMDC & should identify the sample relationship that is being provided. This is relevant when a sample or other material was used to generate the new sample."
Should update examples.
core: soil core 1
parent: sample A
pooling: sample 1, sample 2, sample 3

Double checking - is this edit happening in the submission schema or the NMDC schema?

Please make some valid and invalid examples files for this, no matter which schema you put it in.
Do you need any help putting slots into the submission-schema in a way that bypasses the nmdc-schema?

nmdc-schema
Yes, Bea, do you know how to make example files?

nmdc-schema
Thanks! Yes I will add example files.


dependent fields is not working django-select2

dependent fields is not working django-select2

id changed dynamically


TypeError: Cannot read property 'removeEventListener' of undefined

Swiper fails when I try and destroy the instance of swiper.

[x] bug
Swiper Version: 5.3.8.
Platform/Target and Browser Versions: Mac OS, Chrome 81.0.4044.129 and Safari 13.1

What you did
This happens when I try to unmount and destroy the instance.
Expected Behavior
Should just unmount and clean up events and styles.
Actual Behavior
I get a TypeError: Cannot read property 'removeEventListener' of undefined.
 el.removeEventListener('mousedown', swiper.onTouchStart, false);

What was your solution?


-g 1 flag does not work

When I  call the flag -g 1, the output file with the name followed by "Other", and the objects isn't been named as an integer from 1 to n.
So, what's wrong with my work?
Thanks for your help.

Can you share the file so I can reproduce  the issue?

The buildings in the file are stored as GenericCityObject, not as Building, with denoted semantic surfaces. Since the objects are not semantically labelled, the result you get is as expected. If you need that, consider procuring a semantically rich model.

OK, thanks!


Made all RequestMappings GET method only

Request methods for all calls should be GET only.
There was a few formatting fixes as well (from the Spring Cloud conventions formatter template).
Fixed gh-188

Thanks. Did you fill in the contributor's agreement (link in README)?

Yes, I did a while back when I submitted a PR to spring-cloud-netflix.

Steve

On Fri, Jul 10, 2015 at 6:58 AM, Dave Syer<EMAIL_ADDRESS>wrote:

Thanks. Did you fill in the contributor's agreement (link in README)?
—
Reply to this email directly or view it on GitHub
https://github.com/spring-cloud/spring-cloud-config/pull/189#issuecomment-120384964
.

Closed via 2818859c1a1c02a0830756b39608841074e2fc01


get_assets_url() won't return the api url containing jq binary assets, only on macOS

I've tried debugging this as much as I could, but I simply don't have access to a macOS system to debug effectively.

Oh lord it might be sed

It was sed. Thankfully POSIX-compliant regexes saveed the day. Bug is fixed.


Discontinue counts and use marginal_distribution in basics/04

This PR includes the following updates to basics/04:

Discontinue the use of counts
Use qiskit.result.marginal_distribution for filtering statistics

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

Not really sure why checks are failing: the error message seems unrelated to the updated file.


New frontend and Planner

Why this change?
(You can also directly link an issue).
What does this PR include?
User API changes
How did I test the PR?
New dependencies included

[ ] I have added the dependencies in setup.py

I will merge the PR for adding new functions.
Feel free to leave comments


Issue following "Testing a Thread Network with Visualization" codelab

Following this codelab.
On page 6 the instructions are sparse. I got a test to run but I'm getting an EM copied below.
I don't have a j-link device, and I'm not sure where to find the DUTserial for hwconfig.ini. Are either of those two missing requirements causing this issue? Or is there something else im missing? I don't see anywhere to define a port. I do see clusters.conf but I'm not sure what to put for the port in that.
purvisb@purvisb-linux:/opt/openthread_test$ sudo python3 ~/git/silk/silk/unit_tests/silk_run_test.py
Setting results dir to /opt/openthread_test/results/silk_run_10-31/test_run_on_10-31-21:50/
Setting OTNS server host to localhost
Found 5 test cases.
Running tests...
[2021-10-31 21:50:04,791] [silk] [INFO] Log dest: /opt/openthread_test/results/silk_run_10-31/test_run_on_10-31-21:50/2021-10-31_21.50.04_TestFormNetwork
[2021-10-31 21:50:04,791] [silk] [INFO] SET UP CLASS TestFormNetwork
[2021-10-31 21:50:04,791] [silk.otnsManager.gRPCClient] [DEBUG] Starting gRPC client with address localhost:8999
[2021-10-31 21:50:04,792] [silk.otnsManager] [INFO] OTNS manager created, connect <IP_ADDRESS> to localhost.
[2021-10-31 21:50:04,792] [silk.otnsManager.gRPCClient] [INFO] Sending cmd: title "TestFormNetwork.set_up" x 0 y 20 fs 20
[2021-10-31 21:50:04,804] [silk.otnsManager.gRPCClient] [INFO] Sent cmd: title "TestFormNetwork.set_up" x 0 y 20 fs 20, resp: output: "Done"
[2021-10-31 21:50:04,804] [silk.otnsManager.gRPCClient] [INFO] Sending cmd: speed 1.0
[2021-10-31 21:50:04,815] [silk.otnsManager.gRPCClient] [INFO] Sent cmd: speed 1.0, resp: output: "Done"
[2021-10-31 21:50:04,896] [silk] [INFO] ########## List all available dev boards ##########
[2021-10-31 21:50:04,897] [silk] [INFO] 1915:cafe Nordic_Semiconductor             nRF528xx_OpenThread_Device          ECCFCD37CB31                                         /dev/bus/usb/005/022
1915:cafe Nordic_Semiconductor             nRF528xx_OpenThread_Device          ECCFCD37CB31                                     01  /dev/ttyACM3

Failed to add Dev-8A7D
Failed to add Dev-8A7D
[2021-10-31 21:50:04,932] [silk] [ERROR]   File "/usr/local/lib/python3.8/dist-packages/silk-1.0.0-py3.8.egg/silk/tests/testcase.py", line 250, in wrapper
[2021-10-31 21:50:04,932] [silk] [ERROR]     func(*args, **kwargs)
[2021-10-31 21:50:04,932] [silk] [ERROR]   File "/opt/openthread_test/ot_test_form_network.py", line 52, in setUpClass
[2021-10-31 21:50:04,932] [silk] [ERROR]     cls.hardware_select()
[2021-10-31 21:50:04,932] [silk] [ERROR]   File "/opt/openthread_test/ot_test_form_network.py", line 34, in hardware_select
[2021-10-31 21:50:04,932] [silk] [ERROR]     cls.router = ffdb.ThreadDevBoard()
[2021-10-31 21:50:04,932] [silk] [ERROR]   File "/usr/local/lib/python3.8/dist-packages/silk-1.0.0-py3.8.egg/silk/node/fifteen_four_dev_board.py", line 142, in __init__
[2021-10-31 21:50:04,932] [silk] [ERROR]     self.get_device(sw_version=sw_version)
[2021-10-31 21:50:04,932] [silk] [ERROR]   File "/usr/local/lib/python3.8/dist-packages/silk-1.0.0-py3.8.egg/silk/node/fifteen_four_dev_board.py", line 626, in get_device
[2021-10-31 21:50:04,932] [silk] [ERROR]     self.device_path = self.device.port()
[2021-10-31 21:50:04,932] [silk] [ERROR] Hardware Configuration Error !!!
[2021-10-31 21:50:04,932] [silk] [INFO] ======================================================================
[2021-10-31 21:50:04,932] [silk] [INFO] ==================== CHECK HARDWARE CONFIGURATION ===================
[2021-10-31 21:50:04,932] [silk] [INFO] ======================================================================
[2021-10-31 21:50:04,932] [silk] [INFO] TestFormNetwork....................................FAILED SETUPCLASS
[2021-10-31 21:50:04,932] [silk] [INFO] ======================================================================

========================================================================
===================== HARDWARE TEST SET-UP ERRORS ======================
========================================================================
setUpClass (ot_test_form_network.TestFormNetwork)
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/silk-1.0.0-py3.8.egg/silk/tests/testcase.py", line 250, in wrapper
    func(*args, **kwargs)
  File "/opt/openthread_test/ot_test_form_network.py", line 52, in setUpClass
    cls.hardware_select()
  File "/opt/openthread_test/ot_test_form_network.py", line 34, in hardware_select
    cls.router = ffdb.ThreadDevBoard()
  File "/usr/local/lib/python3.8/dist-packages/silk-1.0.0-py3.8.egg/silk/node/fifteen_four_dev_board.py", line 142, in __init__
    self.get_device(sw_version=sw_version)
  File "/usr/local/lib/python3.8/dist-packages/silk-1.0.0-py3.8.egg/silk/node/fifteen_four_dev_board.py", line 626, in get_device
    self.device_path = self.device.port()
AttributeError: 'NoneType' object has no attribute 'port'

========================================================================
========================== TEST RESULTS RECAP ==========================
========================================================================
========================================================================

========================================================================
=============================== SUMMARY ================================
========================================================================
Start time:     Sun Oct 31 21:50:04 2021
End time:       Sun Oct 31 21:50:04 2021
Execution time: 00:00:00
Tests skipped:  0
Tests errors:   1
Tests run:      0
Tests passed:   0
Tests failed:   0

I don't have a j-link device, and I'm not sure where to find the DUTserial for hwconfig.ini. Are either of those two missing requirements causing this issue? Or is there something else im missing? I don't see anywhere to define a port. I do see clusters.conf but I'm not sure what to put for the port in that.

The nRF52840 DK includes an onboard SEGGER J-Link debugger.
You can use J-Link Commander's ShowEmuList command to discover the serial number of an attached J-Link device.

I have an nRF52840 MDK. I don't believe this has an onboard SEGGER J-Link debugger. Let me know if the mdk model does have that.
Are there any other options available for me?

I have an nRF52840 MDK. I don't believe this has an onboard SEGGER J-Link debugger. Let me know if the mdk model does have that.
Are there any other options available for me?

Silk currently requires the SEGGER J-Link debugger.

Understood, Thanks!


doc: forceLink seems to replace string IDs with links to objects, but this is not documented

forceLink seems to replace string IDs with links to objects, but this is not documented. I. e. https://github.com/d3/d3-force/blob/master/README.md#forceLink doesn't say anything about this. I discovered this only by experimenting with code

It’s implied in two places, but I agree it should be clearer. In link.links:

Each link is an object with the following properties:

source - the link’s source node; see simulation.nodes
target - the link’s target node; see simulation.nodes
index - the zero-based index into links, assigned by this method

For convenience, a link’s source and target properties may be initialized using numeric or string identifiers rather than object references; see link.id.

And in link.id:

The id accessor is invoked for each node whenever the force is initialized, as when the nodes or links change, being passed the node and its zero-based index.

So the implication is that if you don’t specify link objects whose link.source and link.target properties are objects, they will be replaced by object references whenever the link force is initialized. See the implementation here:
https://github.com/d3/d3-force/blob/c7d165a72e2ebd74e5dda43e176d9326c7d424e8/src/link.js#L60-L61
This applies not just to string identifiers but the default numeric indexes, too (when you haven’t specified a custom link.id accessor).
Forces are initialized when they are attached to simulations and when the simulation’s nodes change. Related, simulation.force and simulation.nodes should explicitly mention that they (re-)initialize forces; this is currently only documented by force.initialize.


Failed invoking az interactive when opening in Learn.microsoft.com

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az interactive
Errors:
The command failed with an unexpected error. Here is the traceback:
No module named 'prompt_toolkit.interface'
Traceback (most recent call last):
  File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/interactive/custom.py", line 41, in start_shell
    azext_interactive.start_shell(cmd, style=style)
  File "/home/eriawan/.azure/cliextensions/interactive/azext_interactive/__init__.py", line 10, in start_shell
    from .azclishell.app import AzInteractiveShell
  File "/home/eriawan/.azure/cliextensions/interactive/azext_interactive/azclishell/app.py", line 33, in <module>
    from prompt_toolkit.interface import Application, CommandLineInterface
ModuleNotFoundError: No module named 'prompt_toolkit.interface'

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 interactive

Expected Behavior
Environment Summary
Linux-5.4.0-1094-azure-x86_64-with-glibc2.35 (Cloud Shell), CBL-Mariner/Linux
Python 3.9.14
Installer: RPM

azure-cli 2.41.0

Extensions:
interactive 0.4.5
ai-examples 0.2.5
ml 2.10.0
ssh 1.1.2

Dependencies:
msal 1.20.0b1
azure-mgmt-resource 21.1.0b1

Additional Context
screenshot:

Duplicate of https://github.com/Azure/azure-cli/issues/24213


Invalid checksum calculated when changelogs have not changed

Environment
Liquibase Version:liquibase-core:3.8.1
Liquibase Integration & Version: Gradle 6.2.1
liquibase-gradle-plugin:2.0.2
snowflake-jdbc:3.9.2
Database Vendor & Version: Snowflake 4.19.3
Operating System Type & Version: Docker Engine - Community 19.03.8
Description
We currently have 2 repositories that run liquibase. The first repository is used to deploy liquibase changes and the second is used to perform liquibase rollbacks. Everything including changelogs are kept identical between the repositories, the only difference between them being the Jenkinsfile which runs a different liquibase command.
The checksum calculated when liquibase rollback (second repository) is executed differs from the checksums calculated when liquibase updateTestingRollback is run in the first repository, but only for certain changesets. The checksum is calculated to be identical (expected behaviour) for all changsets other than stage creation changsets which use raw sql. We are using logicalFilePaths.
Example of a stage creation changeset which has a different checksum between the repositories.
  - changeSet:       id: 35       author: redacted       label: snowflake_init       validCheckSum: "1:any"       changes:         - sql:             sql: use schema ${xxxSchemaName};                 create stage ${xxxStageName}                   storage_integration = ${xxxIntegrationObjectName}                   url = 's3://${xxxStageBucketName}'                   file_format = xxx_csv                   encryption=(type='AWS_SSE_KMS' kms_key_id = '${s3.kms-key-id}');       rollback: use schema ${xxxMftSchemaName};                 drop stage ${xxxStageName};

Steps to reproduce

Create two repositories
Set up gradle/liquibase in first
Copy everything into second repository
Run liquibase updateTestingRollback in first repository to apply changes to Snowflake db
Run liquibase rollback (any rollback method) in second repository (different checksum calculated for stage creation raw sql changeset)

Actual Behavior
Liquibase rollback fails due to liquibase.exception.ValidationFailedException: Validation Failed:      3 change sets check sum
Despite there being no differences in the changesets which should mean the checksums are calculated to be the same. We are using logicalFilePaths
Expected/Desired Behavior
Checksum should be calculated as the same between the repositories.
┆Issue is synchronized with this Jira Bug by Unito

Thanks @dh-capital for creating this issue.  We will take a look and add it to the queue.


Start up the server even if a directory is missing

If there are no policies directory, for example, we should still just start the server to avoid users tripping this.

This bug report is confused: the server doesn't read the filesystem so it will always start up.
Also, as it turns out, as of commit 064ce887477286866971682fbf0979690e1a8dd2, chisel apply is also robust against missing directories.
So there is no bug here.


Does this adapter work?

Can I include it into repository?

Hi, I think the iobroker.hid Adapter is already in the repository. Isn't it?

Yes. Hid is in repo. Some people say, it does not work:(
But no logs... so ignore it.
пн, 26 мар. 2018 г., 18:43 Soef<EMAIL_ADDRESS>
Hi, I think the iobroker.hid Adapter is already in the repository. Isn't
it?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/soef/ioBroker.hid/issues/1#issuecomment-376232323,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEXqgAUN2187JQ4MnB2oealwDMWmWXGMks5tiRrJgaJpZM4IUBVs
.


Pid32 h automate novacustom tests v1

@philipandag should this still be a draft?

@philipandag should this still be a draft?
@mkopec
Not all tests are working, so I suppose not. I have explained it on Jira.


Update time-sync model to use alternative datetime library

Story
As a developer I want to rely on actively maintained dependencies.
Rationale
We use momentjs to handle time conversions in our time-sync model, but it is now deprecated and other alternative libraries are recommended instead.
Implementation details
Remove moment and replace with Luxon.
Priority
3/5
Scope
Affects time-sync model only
Size
1-2 days
What does "done" look like?
momentjs no longer used in time-sync model, all unit tests passing
Does this require updates to documentation or other materials??
no
What testing is required?
All existing unit tests passing
Is this a known/expected update?
Expected since start of  Jan 24

@jmcook1186 I'm having a dig around the repo having seen the upcoming hackathon. I'd be happy to take this one to 'warm up' if useful?

HI @jamescrowley - sure thing - thanks a lot! Assigning to you now.