Use rdma-core package (instead of CDT) & add to linux_aarch64

Previously we used the CDT for rdma-core. However it would be better to use the package if possible. This makes that change. It is also aligned with how we use rdma-core elsewhere.
Additionally it looks like rdma-core would be needed on linux_aarch64, but we didn't have it there before. So this makes sure to add it.

Checklist

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

Not seeing Azure here. Going to try restarting
@conda-forge-admin , please restart CI

Looks like that fixed it

Am seeing the following on CI
sed: can't read /home/conda/feedstock_root/build_artifacts/libcufile_1710268372716/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib/pkgconfig/cufile*.pc: No such file or directory

Based on looking locally, this appears to be happening because ${PREFIX}/lib/pkgconfig already exists. So the line below moves pkg-config into ${PREFIX}/lib/pkgconfig, which gives us ${PREFIX}/lib/pkgconfig/pkg-config. Where instead we would want all the .pc files in ${PREFIX}/lib/pkgconfig
https://github.com/conda-forge/libcufile-feedstock/blob/7f8e1ec3054c062a85da3279bb9f85e54c1f5087/recipe/build.sh#L10
IOW this looks like a bug in build.sh

@conda-forge-admin , please re-render

@conda-forge-admin , please re-render

@conda-forge-admin , please lint

@conda-forge-admin , please re-render

I'm not sure the rdma-core package is providing what we needed from the cdt package originally.
One example from the 12.4.1 build log I see:
INFO (libcufile,targets/x86_64-linux/lib/libcufile_rdma.so.1.9.1): Needed DSO x86_64-conda-linux-gnu/sysroot/usr/lib64/libmlx5.so.1 found in CDT/compiler package conda-forge/noarch::libibverbs-cos7-x86_64==22.4=h9b0a68f_1105

And here I see:
WARNING (libcufile,targets/x86_64-linux/lib/libcufile_rdma.so.1.9.1): $RPATH/libmlx5.so.1 not found in packages, sysroot(s) nor the missing_dso_whitelist.

@conda-forge-admin , please re-render

It seems the rerendering failed 😅

Not sure why it wouldn't find the libraries, they are all there
rdma-core-52.0-hcccb83c_0/lib
├── libefa.so -> libefa.so.<IP_ADDRESS>
├── libefa.so.1 -> libefa.so.<IP_ADDRESS>
├── libefa.so.<IP_ADDRESS>
├── libhns.so -> libhns.so.<IP_ADDRESS>
├── libhns.so.1 -> libhns.so.<IP_ADDRESS>
├── libhns.so.<IP_ADDRESS>
├── libibmad.so -> libibmad.so.<IP_ADDRESS>
├── libibmad.so.5 -> libibmad.so.<IP_ADDRESS>
├── libibmad.so.<IP_ADDRESS>
├── libibnetdisc.so -> libibnetdisc.so.<IP_ADDRESS>
├── libibnetdisc.so.5 -> libibnetdisc.so.<IP_ADDRESS>
├── libibnetdisc.so.<IP_ADDRESS>
├── libibumad.so -> libibumad.so.<IP_ADDRESS>
├── libibumad.so.3 -> libibumad.so.<IP_ADDRESS>
├── libibumad.so.<IP_ADDRESS>
├── libibverbs.so -> libibverbs.so.<IP_ADDRESS>
├── libibverbs.so.1 -> libibverbs.so.<IP_ADDRESS>
├── libibverbs.so.<IP_ADDRESS>
├── libmana.so -> libmana.so.<IP_ADDRESS>
├── libmana.so.1 -> libmana.so.<IP_ADDRESS>
├── libmana.so.<IP_ADDRESS>
├── libmlx4.so -> libmlx4.so.<IP_ADDRESS>
├── libmlx4.so.1 -> libmlx4.so.<IP_ADDRESS>
├── libmlx4.so.<IP_ADDRESS>
├── libmlx5.so -> libmlx5.so.<IP_ADDRESS>
├── libmlx5.so.1 -> libmlx5.so.<IP_ADDRESS>
├── libmlx5.so.<IP_ADDRESS>
├── librdmacm.so -> librdmacm.so.<IP_ADDRESS>
├── librdmacm.so.1 -> librdmacm.so.<IP_ADDRESS>
└── librdmacm.so.<IP_ADDRESS>

I seem to recall we encountered a similar situation elsewhere (but can't find the example now), where a CTK component in $PREFIX/targets/<arch>/lib depends on non-CTK packages in $PREFIX/lib. Maybe we need to patch rpath manually for the cuFILE libraries?

Looks like we need libnuma based on this CI warning:
WARNING (gds-tools,gds/tools/gdsio): $RPATH/libnuma.so.1 not found in packages, sysroot(s) nor the missing_dso_whitelist.

Yeah it looks like there is something up with the rpath for gds-tools based on this line from CI:
WARNING (gds-tools,gds/tools/gdsio): $RPATH/libcufile.so.0 not found in packages, sysroot(s) nor the missing_dso_whitelist.

Yep, this is related to issue: https://github.com/conda-forge/cuda-feedstock/issues/10

@conda-forge-admin , please restart CI

@conda-forge-admin, please restart ci

Thanks Billy! 🙏
Were you meaning PR: https://github.com/conda-forge/cuda-nvcc-impl-feedstock/pull/25 ?

Thanks Billy! 🙏
Were you meaning PR: conda-forge/cuda-nvcc-impl-feedstock#25 ?

That is all set also, I approved it and put more comment. Thanks.

Thanks Billy! 🙏

The conclusion Billy and I reached after looking into the warnings above more closely is there is likely a remaining RPATH issue in this package, which we will need to look into. This will be follow up work


Removing known issue

Removing known issue as the devs reacted very fast to my last follow-up and pushed a fix into prod.

Thanks for fixing this!


Migration to local

As a developer, I want to be prepared to hand off the project to the client for transferring Home Assistant from the cloud to a local device.

Home Assistant should be run locally, according to all references I've seen
Home Assistant Cloud is the de facto for doing what we're doing with AWS

Not a requirement from Kyle, so bumping down priority for now.


use more permissive engine ranges

So I don't see this when I npm install: npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.10.x","npm":"1.2.x"} (current: {"node":"1.5.1","npm":"2.7.5"})

Sorry for the delay. Thanks for the PR. I've merged your commit, and it's available as v0.1.1 on npm. Let me know if there are any problems!


Can I custom double-click and triple-click selection behavior

For a_b_c style word selection , sometimes I want to select single word like 'a', while in other situations I prefer to select the whole phrase a_b_c. I know the {"editor.wordSeparators": "_"} setting could work to select the single word separated by underline. But when I set this I can't select the whole phrase any more.
Can I just custom triple-click to select the whole phrase, and use ctrl + L to select the whole line, thank you.

Let's track in https://github.com/microsoft/vscode/issues/3130


upgrade: bump to Go 1.12.6

Signed-off-by: yeya24<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
update to Go 1.12.6
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #635 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #635      +/-   ##
==========================================
+ Coverage    48.2%   48.22%   +0.01%
==========================================
  Files          99       99
  Lines        5889     5889
==========================================
+ Hits         2839     2840       +1
  Misses       2825     2825
+ Partials      225      224       -1

Impacted Files
Coverage Δ

supernode/daemon/mgr/scheduler/manager.go
24.81% <0%> (+0.75%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2a431f4...c4cda9e. Read the comment docs.


WIP: Swap Out Pattern Lab Styleguidekit

Testing out swap out styleguidekit repos to get internal assst paths on Netlify squared away

Closing out - new PR I have up supersedes this one :)


Slowdown on save

I noticing slowdown when neo-tree is open. I assume it caused by updating the tree on save?
Log: neo-tree.nvim.txt
I use default settings.

Deja vu! Looking at those logs, it's not really doing anything. It is tracking your movements opening and closing buffers and switching windows, but none of those events actually caused a refresh. Nothing that happened in these logs could have had a noticeable impact on performance.
Are you sure that these logs cover the period where there is a slowdown?

Hm... I tried to check it, but :lua require("neo-tree").show_logs() results in empty file for me on the latest master. My configuration:
local config = {
  log_level = 'trace', -- "trace", "debug", "info", "warn", "error", "fatal"
  log_to_file = true, -- true, false, "/path/to/file.log", use :NeoTreeLogs to show the file
}

require("neo-tree").setup(config)

I accidentally broke logging in the prior commit. It is fixed now.

Okay, here we go: neo-tree.nvim.txt
Config:
local config = {
  enable_diagnostics = false,
  enable_git_status = false,
  enable_modified_markers = false, -- Show markers for files with unsaved changes.
  log_level = 'trace', -- "trace", "debug", "info", "warn", "error", "fatal"
  log_to_file = true, -- true, false, "/path/to/file.log", use :NeoTreeLogs to show the file
}

require('neo-tree').setup(config)

The core problem here is that the "buffer_changed" event is firing continuously. This is triggered by the BufWritePost and BufFilePost autocmd events. I would say that something is wrong in your setup for these events to be firing continuously like that. You might want to try a minimal setup without any other plugins.
As a workaround, you can avoid the problem within neo-tree by using the libuv file watcher instead of relying on those buffer changed events:
local config = {
  enable_diagnostics = false,
  enable_git_status = false,
  enable_modified_markers = false, -- Show markers for files with unsaved changes.

  log_level = 'trace', -- "trace", "debug", "info", "warn", "error", "fatal"
  log_to_file = true, -- true, false, "/path/to/file.log", use :NeoTreeLogs to show the file
  filesystem = {
    use_libuv_file_watcher = true, -- This will use the OS level file watchers to detect changes
  }

}

require('neo-tree').setup(config)

It just occurred to me that maybe you were spamming a save file mapping on purpose to illustrate the save slowdown. If that's the case, then I'd say everything looks fine as far as I can see. If you were not intentionally saving every second, then see my prior comment.

It just occurred to me that maybe you were spamming a save file mapping on purpose to illustrate the save slowdown.

That's what I did :D

As a workaround, you can avoid the problem within neo-tree by using the libuv file watcher instead of relying on those buffer changed events:

Still have the same slowdown... Log: neo-tree.nvim.txt
(this time I saved only once)

From the logs, that looks like neotree is working correctly. There does seem to be an unusual number of buffers (133?) opened in this session, and a lot of movement between windows.
The strangest things I notice are that there is a file named 4913, which keeps getting renamed. Also, tree.lua keeps getting renamed to tree.lua~ and back again. If you only saved once, then something else is going on here because there was a rapid fire of this file being saved and renamed many times in a second. Neo-tree did properly debounce that so many of the events were skipped, but that still means several refreshes for one save action.

That's strange... Here is the log plugins (only necessary to run neo-tree): neo-tree.nvim.txt. The same slowdown still happens

Still the same behavior, here is the relevant part of the logs without the extra noise of event calls that do nothing:
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  file_open_requested  with args:  {
  open_cmd = "e",
  path = "/home/gena/.config/nvim/init.lua",
  state = {
    async_directory_scan = "auto",
    bind_to_cwd = true,
    bufnr = 2,
    commands = {
      add = <function 1>,
      ...
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  vim_win_enter  with args:  {
  afile = "README.md"
}
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:132: Handler  neo-tree-win-enter  for vim_win_enter called successfully.
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  vim_buffer_enter  with args:  {
  afile = "README.md"
}.
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  vim_buffer_added  with args:  {
  afile = "init.lua"
}
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  vim_buffer_enter  with args:  {
  afile = "init.lua"
}
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  vim_buffer_enter  with args:  {
  afile = "init.lua"
}
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  file_opened  with args:  /home/gena/.config/nvim/init.lua
[TRACE Sun May  1 12:23:59 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:132: Handler  buffers.vim_buffer_added  for vim_buffer_added called successfully.
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  vim_buffer_changed  with args:  {
  afile = "init.lua"
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "4913",
  status = {
    rename = true
  }
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "4913",
  status = {
    change = true
  }
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "4913",
  status = {
    rename = true
  }
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "init.lua",
  status = {
    rename = true
  }
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "init.lua~",
  status = {
    rename = true
  }
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "init.lua",
  status = {
    rename = true
  }
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "init.lua",
  status = {
    change = true
  }
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "init.lua",
  status = {
    change = true
  }
}
[TRACE Sun May  1 12:24:02 2022] ...lugins/start/neo-tree.nvim/lua/neo-tree/events/queue.lua:158: Firing event:  fs_event  with args:  {
  path = "init.lua~",
  status = {
    rename = true
  }
}

You had README open, then you opened init.lua, then there was a flurry of changes and renames, and some strange file called 4913 was also saved.
Maybe you should try it with the minimal init that is in the neo-tree repo:
nvim --noplugin -u tests/mininit.lua

Still the same behavior, here is the relevant part of the logs without the extra noise of event calls that do nothing:
You had README open, then you opened init.lua, then there was a flurry of changes and renames, and some strange file called 4913 was also saved.

That strange, I disabled all plugins and configuration expect a few mappings in my init.lua.
Okay, here is the log where I disabled everything except <C-s> mapping to save the file and still have a slowdown on save:
neo-tree.nvim.txt
And here is the branch with my configuration where you can see that I disabled everything: https://github.com/Shatur/neovim-config/pull/2

That is definitely a clean log without any of the extra events from the prior logs. I don't see anything wrong with this log though. It looks like a single "write" action happened at the very end and the corresponding refresh started and ended within the same second.
I should have asked earlier, what do you mean by slowdown? Can you demonstrate it in a video?

Then maybe it's not an issue. When I use ui client I spinning cursor for a moment and on cli cursor blinks for a moment. It usually happens on some sync action.

Log with my regular init.lua, looks clean too: neo-tree.nvim.txt

Definitely looks fine. Strange that it is so different from earlier logs.
As far as I can see, there's nothing to do here. 🤷♂

Strange that it is so different from earlier logs

Maybe something wrong with my configuration, will investigate, thanks for pointing it out.

As far as I can see, there's nothing to do here. man_shrugging

But why do we need to redraw the tree If I just changed the file and have all markers disabled?

But why do we need to redraw the tree If I just changed the file and have all markers disabled?

That event also captures new and renamed files. If you don't want any automatic updates at all, I can add an enable_buffer_write_refresh option to let you disable that last event subscription as well.
Is there something more happening than a blinking cursor? Does nvim freeze up on you for some period of time after a save?

That event also captures new and renamed files.

Hm... But I don't had any new files on that save. Trying the following:
local config = {
  enable_diagnostics = false,
  enable_git_status = false,
  enable_modified_markers = false, -- Show markers for files with unsaved changes.
  log_level = 'trace', -- "trace", "debug", "info", "warn", "error", "fatal"
  log_to_file = true, -- true, false, "/path/to/file.log", use :NeoTreeLogs to show the file
  enable_buffer_write_refresh = true,
}

require('neo-tree').setup(config)

Still have the issue: neo-tree.nvim.txt

Does nvim freeze up on you for some period of time after a save?

Yes, it freezes for a few hundred ms.

Hm... But I don't had any new files on that save. Trying the following:

The events are just not that precise. I detect the fact that a file has been written to disk, whether it is an overwrite or a new file is unknown.

Yes, it freezes for a few hundred ms.

How can you even tell? Are you auto saving on a timer or on every keystroke?

The events are just not that precise. I detect the fact that a file has been written to disk, whether it is an overwrite or a new file is unknown.

Oh, got it. Then this unavoidable, yes. In nvim-tree I just disabled this feature using auto_reload_on_write option and don't have any slowdowns.

How can you even tell? Are you auto saving on a timer or on every keystroke?

If I save and quickly move - there will be a delay. And this delay depends on how tree is big.

Also thanks for looking into it, I appreciate your help.

On second thought... Maybe we could disable tree autoreload too?

I just added a new option for you in the latest commit:
local config = {
  enable_diagnostics = false,
  enable_git_status = false,
  enable_modified_markers = false, -- Show markers for files with unsaved changes.
  enable_refresh_on_write = false, -- Refresh the tree when a file is written. Only used if `use_libuv_file_watcher` is false.
}

If you use those settings there won't be any auto refresh at all.

I just added a new option for you in the latest commit:

Worked like a charm, thank you!


RFP: Breaking changes?

We'll be bumping to thrifty 2.0.0 due to breaking codegen changes for Kotlin unions.
While we're at it, if anyone has breaking changes they'd like to see, now's a good opportunity!

With the release of 2.0.0-RC1, I think it's safe to say that we won't be contemplating further breaking changes.


Upgrade to 4.1.43 (from 4.1.40) results in missing definition for SetServiceState

Hi,
I upgrade the InTheHand.Net.Bluetooth package from 4.1.40 to 4.1.43.
After that the line :
bdi.SetServiceState(BluetoothService.SerialPort, true);
is giving an error
Error	CS1061	'BluetoothDeviceInfo' does not contain a definition for 'SetServiceState' and no accessible extension method 'SetServiceState' accepting a first argument of type 'BluetoothDeviceInfo' could be found (are you missing a using directive or an assembly reference?)
downgrading to 4.1.40 solves the issue.
Is there something changd or broke ?
Regards,
MarFan

With the recent refactoring work the SetServiceState method only exists in the win32 dll of the library because it's the only platform which supports it. What are you trying to use it for? Because there is probably an easier solution.


Use CMake to generate the release zip/tar

This should make it easier to include things that aren't binaries... May also be useful for the boilerplate.

Aha! This should allow me to check off some things from the list. Thank you!


feat: add feedback form in header

Reuse the form for reporting feedback from rep.equinor.com. The feedback should be forwarded to service-now and our assignment group there
Service now public rest api docs:
https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/api-rest.html

[ ] equinor/sepes-api#788
[ ] #1558
[ ] clarify to user that the dialog creates a service-now task
[ ] clarify to user how to follow up the task in service-now
[ ] set to production

@bonyfusbouvet, I added some tasks in to this Issue, lets reopen it and keep the Issue until it is set to production. Have you seen how the subtasks kan be converted to new Issues tracked in this Issue?

@einaren yes I can see that. There is a icon in the right which says -convert to issue-


Fix incorrect docstring for to_base64 Relay util

Description
This change fixes the docstring for the to_base64 function in the Relay utils module. The docstring incorrectly stated that the return type was a tuple, but it is actually the base64 encoded global ID string. I think this was a copy/paste mistake from the from_base64 function.
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[x] Documentation

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to Gavin Bannerman for the PR 👏

Get it here 👉 https://strawberry.rocks/release/(next)

Looks good, do you also want to make a patch release for this? 😊

@patrick91 I've amended my commit and added a patch release file now ✅

Thanks for contributing to Strawberry! 🎉 You've been invited to join
the Strawberry GraphQL organisation 😊
You can also request a free sticker by filling this form: https://forms.gle/dmnfQUPoY5gZbVT67
And don't forget to join our discord server: https://strawberry.rocks/discord 🔥


Google Fonts - Unable to Widget Test Text Color

Package
google_fonts
Existing issue?

[X] I checked the existing issues

What happened?
Expected vs actual result:
Expected:
The color property of a Text widget using GoogleFonts should be testable when using a textTheme.
Actual:
The below test fails because color is null. I apologize in advance if this is me misunderstanding how theme inheritance works.
Steps to reproduce:
    testWidgets('Text widget has correct color', (WidgetTester widgetTester) async {
      const textKey = Key('foo');

      await widgetTester.pumpWidget(
        MaterialApp(
          theme: ThemeData(
            primaryColor: Colors.red,
            textTheme: GoogleFonts.redHatTextTextTheme().apply(
              bodyColor: Colors.red,
              displayColor: Colors.red,
            ),
          ),
          home: Scaffold(
            body: Text(
              key: textKey,
              'Hello, world!',
              style: GoogleFonts.redHatText(fontSize: 32),
            ),
          ),
        ),
      );

      await widgetTester.pumpAndSettle();

      final text = widgetTester.firstWidget<Text>(find.byKey(textKey));

      expect(
        text.style?.color,
        Colors.red,
      );
    });

Relevant log output
No response

This is WAI, the text styles are null by default. Please see https://stackoverflow.com/questions/59190126/check-for-color-during-widget-test for testing widget color, for example.


Stormy weather disabling all monitors except main radar

Hello !
Many times now during our playthroughs, we had this annoying bug that when the ship get struck by lightning, monitors go off and only the middle screen can go on again.
The only solution we have now is to quit and re-host or relaunch the game entirely.
General Improvements resolved this bug not too long ago, but we noticed this bug only happens again when we buy the BodyCam ship upgrade, which is why i am posting here, thinking it may come from OpenBodyCam maybe ?
Here is the code of our modpack, in case it's just a conflict of something else we didn't notice at the time :
018f92dc-f8e8-7cc7-dfb0-f73dcf34b329
To reproduce the bug, you just need to buy the bodycam ship upgrade and then go on Stormy and get struck by lightning on the ship.

I can't reproduce that with your code, but I'm guessing whatever you're encountering may be an issue with GeneralImprovements, unless some error from OpenBodyCams shows up in your logs when that happens. OpenBodyCams itself doesn't really change anything with the GeneralImprovements BetterMonitors except for the one that it replaces.
It would probably be good to make a copy of your logs when that happens and send it over to Shaosil. If you do find that it's caused by OpenBodyCams, feel free to post here and I can reopen this, but I'll close it for now.


"Allow Damage" Doesn't Allow Fall Damage

Is this intentional?

Vanilla limitation. Having creative flight enabled at all makes the player immune to fall damage.
I may consider patching that to ignore if you're in Creative+ mode, as if you were to take fall damage with allow damage off it'd just be ignored anyway.

Ah, I see. To avoid bloating the tracker with another issue, may I also ask if it's possible to prevent vines, cobwebs, etc. from slowing you down in noclip mode?


link to docs broken

I think it should redirect to the pythonhosted site (as in this commit), but I'm not 100% sure

Thanks for reporting this. pythonhosted.org is closing down however. I hade forgot to push
to the gh-pages branch. Thank you for pointing this out. I have now pushed to the gh-pages branch (with docs for the three latest versions), the link should now work.
(I found some edge cases in my script for this and patched it here: https://github.com/bjodah/chempy/commit/00a1fc6f3386305ce6a74d8ebad482e0e71f53dd )


Terminal doesn't respond to SIGINT (CTRL+C KeyboardInterrupt) when running as administrator

Environment
Windows build number: Windows NT 10.0.19041.0
Windows Terminal version: Version: 0.10.781.0

Steps to reproduce

Start one terminal as administrator, and one normally
Using PowerShell or cmd (didn't test other shells), start some continuous process, e.g  ping -t localhost
Try to interrupt process with ctrl+c on each terminal.
Observe that it only works on the unelevated terminal.

Expected behavior
SIGINT causes console process to exit, regardless of elevation
Actual behavior
Process does not respond to SIGINT, and requires manual termination from taskmgr or another shell

Can't repro this, as admin.

I think it's the way I'm launching it, as it's a bit improper. I have a shortcut on my taskbar with the target
C:\Windows\System32\cmd.exe /c start /b wt
that is set to run as administrator, just so that it defaults to admin. I just tried and it works as expected if I Right click -> Run as Administrator.
I can't remember why I used the above target, but setting the it to wt.exe appears to produce the desired behavior, and CTRL+C works fine.

Ah, thanks for following up. That’s really quite strange. I’m not sure there’s anything we can do about that; perhaps there is something strange about app activation in this context... ☹
For now, I’ll resolve this one as External. Please let me know if you have any other ideas or any other leads.

I think it's the way I'm launching it, as it's a bit improper. I have a shortcut on my taskbar with the target
C:\Windows\System32\cmd.exe /c start /b wt

Why doesn't the shortcut simply run wt.exe?
The /b option of CMD's start command calls CreateProcessW with the creation flag CREATE_NEW_PROCESS_GROUP and without the flag CREATE_NEW_CONSOLE, so it sort of acts like running a background process in the current console session, especially if combined with redirecting the process standard input to NUL.
A process that's created in a new console process group initially has Ctrl+C disabled (i.e. the ConsoleFlags in the PEB process parameters has the first bit set). I guess it's because only 'foreground' processes should see Ctrl+C. This setting gets inherited by child processes.
Interestingly, this flag remains set in the process parameters and inheritable even if we run a non-console application such as Windows Terminal. I suggest that Windows Terminal should clear this flag to enable Ctrl+C on startup via SetConsoleCtrlHandler(NULL, False).

Good catch, @eryksun. Thanks!

Why doesn't the shortcut simply run wt.exe?

@eryksun That's a mistake on my part. I don't quite remember why I ended up with that, and it seems completely unnecessary in hindsight. Thanks for the insight.

 It's a home run IMO, and I'm genuinely excited to see what comes next 👍

Still seeing this intermittently in v1.6.10571.0.

Windows terminal 1.11.3471.0
I can reproduce this problem.
Windows terminal stopped responding on Ctrl + C after executing and just trying to log-in by ssh on any host.

I can confirm @vladsol observation as well.

Login with SSH on any remote host. Then exit that
Run ping <IP_ADDRESS> -t
Try to exit with ctrl+c

Created a new issue for this at https://github.com/microsoft/terminal/issues/13503

ctrl + c doesn't work

If you are experiencing this issue, file a new bug and fill out the template. This one is four years old and has been closed for the majority of that time.


ImportError: No module named 'u2fval.yubicommon'

While creating source distribution, I'm getting following  error:
Traceback (most recent call last):
    File "setup.py", line 29, in (module)
       from u2fval.yubicommon.setup import setup
ImportError: No module named 'u2fval.yubicommon'

have you run git submodule init and git submodule update ?

Yes, I had run both commands. I'm following the instructions given here.

What OS are you running? Is there anything in vendor/yubicommon?

Windows. Yes there is some src files into vendor/yubicommon. I'm new to python so, may be I missing something to configure path environment variable specific to python project.

Ah, that explains it. Windows doesn't support symlinks which is causing
this issue. This should be better documented. Inside u2fval/ there is a
yubicommon symlink which on Windows shows up as a file. You'll need to
delete that file and replace it with a copy of the directory
vendor/yubicommon/yubicommon. In the end you should have
u2fval/yubicommon/init.py, etc. After that you should be able to build
the source release.


Strange address sanitizer complaints by Apple clang

This happens when running the plugin demo with asan on mac:
It does not happen with clang15 on Linux and it seems that it shouldn't happen on mac as well.
/Users/runner/work/dynamix/dynamix/code/./dynamix/mutate.hpp:13:10: runtime error: member call on address 0x7ff7b95e7ca0 which does not point to an object of type 'dynamix::common_mixin_init<tap::person>'
Errors while running CTest
0x7ff7b95e7ca0: note: object is of type 'tap::mixin_person'
 01 00 00 00  f0 34 ec 06 01 00 00 00  b0 79 ec 06 01 00 00 00  ff ff ff ff f7 7f 00 00  80 ea aa 06
              ^~~~~~~~~~~~~~~~~~~~~~~
              vptr for 'tap::mixin_person'
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /Users/runner/work/dynamix/dynamix/code/./dynamix/mutate.hpp:13:10 in
/Users/runner/work/dynamix/dynamix/code/dynamix/object_mutation.cpp:236:20: runtime error: call to function int dynamix::util::call_mixin_default_ctor<tap::teacher>(dnmx_mixin_info const*, void*) through pointer to incorrect function type 'int (*)(const dnmx_mixin_info *, void *)'
mixin_info_util.hpp:16: note: int dynamix::util::call_mixin_default_ctor<tap::teacher>(dnmx_mixin_info const*, void*) defined here
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /Users/runner/work/dynamix/dynamix/code/dynamix/object_mutation.cpp:236:20 in
/Users/runner/work/dynamix/dynamix/code/dynamix/object_mutation.cpp:167:9: runtime error: call to function void dynamix::util::call_mixin_dtor<tap::teacher>(dnmx_mixin_info const*, void*) through pointer to incorrect function type 'void (*)(const dnmx_mixin_info *, void *) noexcept'
mixin_info_util.hpp:21: note: void dynamix::util::call_mixin_dtor<tap::teacher>(dnmx_mixin_info const*, void*) defined here
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /Users/runner/work/dynamix/dynamix/code/dynamix/object_mutation.cpp:167:9 in
/Users/runner/work/dynamix/dynamix/code/./dynamix/mutate.hpp:13:10: runtime error: member call on address 0x7ff7b95e75a0 which does not point to an object of type 'dynamix::common_mixin_init<tap::person>'
0x7ff7b95e75a0: note: object is of type 'tap::mixin_person'
 b0 [60](https://github.com/iboB/dynamix/actions/runs/4453732770/jobs/7822459107#step:6:61) 00 00  f0 34 ec 06 01 00 00 00  b0 79 ec 06 01 00 00 00  ff ff ff ff f7 7f 00 00  c0 eb aa 06
              ^~~~~~~~~~~~~~~~~~~~~~~
              vptr for 'tap::mixin_person'
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /Users/runner/work/dynamix/dynamix/code/./dynamix/mutate.hpp:13:10 in
[doctest] doctest version is "2.4.9"
[doctest] run with "--help" for options

More time needs to be invested here.

It seem that this is either a clang-14 issue or an apple-clang issue. I cannot reproduce this with clang 15 on Linux

yep. It does not happen on apple clang 16


cannot play in ios with base64 audio

Describe the Bug
when i playing base64 audio with track player it works well on ios 15,16 etc.but it deosn't work on ios 17 beta and ios 14.
I am testing with both physical devices and simulators.May be this with something to do with base64 audio memory stream.
But we need this kind of features to carete encrypted/decrypted audio player.
{"error": {"code": "ios_track_unplayable", "message": "The track could not be played"}, "state": "error"} this is error message from track player.
StreamingPlaylist_VerifyLeadingMagicNumber: missing #EXTM3U (this is error message from xcode)
Steps To Reproduce
How can someone else reproduce this bug?
Code To Reproduce
const App = () => {
const track1 = {
url: data:audio/wav;base64,${auidoBase64}, // Load media from the app bundle
title: 'Coelacanth I',
artist: 'deadmau5',
// Load artwork from the app bundle
duration: 166,
};
const track2 = {
url: require('./auido/file_example_WAV_2MG.wav'), // Load media from the app bundle
title: 'Coelacanth I',
artist: 'deadmau5',
// Load artwork from the app bundle
duration: 166,
};
const setUpPlayer = async () => {
await TrackPlayer.setupPlayer({
iosCategory:IOSCategory.PlayAndRecord,
});

};
useEffect(() => {
setUpPlayer();
}, []);
const duration = useProgress().duration;
const position = useProgress().position;
const addSong = async () => {
await TrackPlayer.add({
...track1,
  contentType:'audio/wav',
  pitchAlgorithm:PitchAlgorithm.Linear
});
console.log("Successfully added song...")

};
const playSong = async () => {
await TrackPlayer.play();
console.log("Successfully Play song...")
};
const pauseSong = async () => {
await TrackPlayer.pause();
console.log("Successfully Pause song...")
};
const resetSong = async () => {
await TrackPlayer.reset();
console.log("Successfully Reset song...")
};
console.log("Progress==>",useProgress())
console.log("State===>",usePlaybackState())
return (
<View style={{flex: 1, justifyContent: 'center', alignItems: 'center'}}>
<View
style={{
flexDirection: 'row',
width: 100,
justifyContent: 'space-between',
marginBottom: 30,
}}>
{duration}
{position}

<Pressable style={{marginBottom: 10}} onPress={playSong}>
Play

<Pressable style={{marginBottom: 10}} onPress={pauseSong}>
Pause

  <Pressable onPress={addSong}>
    <Text>Add</Text>
  </Pressable>

  <Pressable onPress={resetSong}>
  <Text>Reset</Text>
</Pressable>
</View>

);
};
export default App;
Replicable on Example App?
Can you replicate this bug in the React Native Track Player Example App?
Environment Info:
System:
OS: macOS 13.4
CPU: (8) x64 Apple M1
Memory: 26.90 MB / 8.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 16.14.0
path: /usr/local/bin/node
Yarn:
version: 1.22.19
path: /usr/local/bin/yarn
npm:
version: 9.6.7
path: /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.11.3
path: /usr/local/bin/pod
SDKs:
iOS SDK: Not Found
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8193401
Xcode:
version: /undefined
path: /usr/bin/xcodebuild
Languages:
Java:
version: 11.0.15
path: /usr/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.3
wanted: 0.72.3
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
"react-native-track-player": "^3.2.0
both device and simualtors
macos version 13.5
How I can Help
What can you do to help resolve this?
Have you investigated the underlying JS or Swift/Android code causing this bug?
Can you create a Pull Request with a fix?

normally we leave it to default type in our actual project.It not just on iOS 17 ,it was happened in iOS 14 too.What can i do?Our app is already on production.

Sure ! here is example project ro reproduce ==> https://github.com/thureintun-me/RNTPBase64
in order to test u need iOS 17 running physical device or xcode beta 15.2
above sample project (base64 memory string play) work well on android.but in iOS it can only paly local song.

@dcvz is there anything I can do to make it work?

@thureintun-me did you get any resolution for this? I'm experiencing a similar issue too on iOS 17.

No fixes for this yet!

Event.PlaybackState {"error": {"code": "ios_track_unplayable", "message": "The track could not be played"}, "state": "error"}
LOG  Event.PlaybackProgressUpdated {"error": "The operation couldn’t be completed. (SwiftAudioEx.AudioPlayerError.PlaybackError error 4.)"}. this is the update issues logs from RNTP version 4.1.0 @dcvz  and @GITyannie  we still cannot solve the issues let us know when you fin a way to solve

@dcvz same issue. Please help me 😭

useTrackPlayerEvents(events, async event => {
console.log('🚀🚀🚀', event);
}
const track: any = {
id: item?.id,
creator: item.creator,
url: item?.voice, // https audio URL which plays in Android and browser as well
duration: 411,
title: item?.description,
artwork: 'https://imgtr.ee/images/2023/03/01/Riqm1.png',
artist: item?.creator?.level,
};
await TrackPlayer.add([track]);
await TrackPlayer.play();
🚀🚀🚀 {"error": {"code": "ios_track_unplayable", "message": "The track could not be played"}, "state": "error", "type": "playback-state"}
🚀🚀🚀 {"error": "The operation couldn’t be completed. (SwiftAudioEx.AudioPlayerError.PlaybackError error 4.)", "type": "playback-error"}
works well on Android. but in iOS it shows above error.

I am having the same problem
audio file working fine on Android devices, In IOS returning an error
{"error": {"code": "ios_track_unplayable", "message": "The track could not be played"}, "state": "error", "type": "playback-state"}
{"error": "The operation couldn’t be completed. (SwiftAudioEx.AudioPlayerError.PlaybackError error 4.)", "type": "playback-error"}
I have an old app code (Developed 1 year ago) and in the old code, it is working fine on both devices.
I applied the same code event I used the old version also, but in the new project not working.
Please help me out with this as I have already spent 4 weeks

I think I found a solution for myself, but I'm not sure if it will work for you. I download audio using
rn-fetch-blob, with this config. I added the wav format for ios.
      const { config } = RNFetchBlob       const options = {         fileCache: true,         appendExt: IS_IOS ? 'wav' : '',       }       // @ts-ignore       const url = voice?.uri         ? // @ts-ignore           voice?.uri         : await config(options)             .fetch('GET', voice?.main_url || '')             .catch((error) => {               console.log('%c voice dowload error', 'color: red', error)             })
I also added type when adding a track, I don't know if it affects the final result of the work.
`const addTrack = async () => {
const track: AddTrack = {
url: urlVoice, // Load media from the network
title: 'Voice message',
// @ts-ignore
date: voice?.created_at || new Date(voice?.id).toUTCString(), // RFC 3339
id: voice?.id,
type: TrackType.HLS, // here
}
console.log('addTrack', track)

return await TrackPlayer.add(track).catch((error) => {
  console.log('add track error', error)
})

}`
To record audio, I use react-native-audio-recorder-player, with the following settings:
`const audioRecorderPlayer = new AudioRecorderPlayer()
const audioSet: AudioSet = {
AudioEncoderAndroid: AudioEncoderAndroidType.AAC,
AudioSourceAndroid: AudioSourceAndroidType.MIC,
AVModeIOS: AVModeIOSOption.measurement,
AVEncoderAudioQualityKeyIOS: AVEncoderAudioQualityIOSType.high,
AVNumberOfChannelsKeyIOS: 2,
AVFormatIDKeyIOS: AVEncodingOption.aac,
}
const dirs = RNFetchBlob.fs.dirs
const date = +new Date()
const path = Platform.select({
ios: dirs.DCIMDir + /audio-message-${date}.m4a,
android: ${dirs.CacheDir}/audio-message-${date}.mp3,
})
console.log('audio path', path)
await audioRecorderPlayer.startRecorder(path, audioSet, true)
`


Separate button for resetting rotation

Not sure about this, but many people are asking how to reset rotation. The current way is a long tap on the geolocation button. It is utterly not discoverable. Another way is to rotate the map back: it snaps to zero inside like 30°.
If we had a dedicated rotation reset button, this could be simplified, and snapping could be lowered to 10°.
One option is to just replace geolocation button, but then, it is used much more often than rotation reset: you walk the entire street with the same rotation.
I really don't want to clutter the screen with buttons.
Maybe replace zoom in and out buttons?..

I really don't want to clutter the screen with buttons.

Absolutely agree; there is too little screen estate to begin with... If there is any other way, it should IMHO be preferred to another button

The current way is a long tap on the geolocation button. It is utterly not discoverable

That is true. Maybe adding it in that in-app FAQ might help discoverability a little?
And/or keep the same behaviour, but perhaps change appearance of the icon:

perhaps make it actually  animated rotated compass showing direction the map is in (a'la StreetComplete).
That might not only give hint it might be orientation related so people might try long press on it; but (even if they miss that long-press functionality) it would make "snap to N when < 30 degrees angle" much more discoverable and easier to use (currently one has to know where North is to be able to reorient map to North, which kinda defeats the many uses of snap-to-N feature).
or if that is too complicated, perhaps at least add red "N" on current icon or something to indicate it might relate to compass  orientation too?

Because, once mapper learns of that functionality,  long press actually works great from usability point of view.
It is just that it is hard to discover just by looking at the screen.

Maybe replace zoom in and out buttons?..

Well, removing them would mostly preclude one-handed use (although those using buttons currently feel somewhat buggy anyway, e.g. https://github.com/Zverik/every_door/issues/489, so maybe removing them wouldn't be such a huge loss?)
But I would prefer to have functional zoom buttons...


du: add --app as alias of --apparent-size to match GNU

This seems to be a case of something we're currently missing on all utils:
   Most programs that accept long options recognize unambiguous
abbreviations of those options.  For example, ‘rmdir
--ignore-fail-on-non-empty’ can be invoked as ‘rmdir --ignore-fail’ or
even ‘rmdir --i’.  Ambiguous options, such as ‘ls --h’, are identified
as such.

Clap doesn't seem to have support for that yet. There is an open issue from April 2020: https://github.com/clap-rs/clap/issues/1786. We could try to implement it there and use it once Clap 3 is released.
For now, we could just add these aliases of course.

yeah, for now, I just want to fix GNU tests :)

I've opened a PR to Clap for this feature: https://github.com/clap-rs/clap/pull/2525. Let's hope it it will get merged and we'll be able to use it soon.

it didn't fix GNU tests but it showing some different errors

don't hesitate to merge then directly btw ;)


Enhanced support for metadata in SAV Files

In our research group, we store a significant amount of data in SPSS's SAV format. The format is advantageous due to its comprehensive metadata handling capabilities, which include variable labels, value labels, missing value definitions, and multiple response sets, among others. However, this format poses significant challenges when we attempt to utilize other programming languages or tools for data analysis and manipulation.
To increase interoperability and efficiency within our group, we're exploring open-source, platform/language-agnostic formats similar to the SAV format, specifically those capable of storing complex metadata.
We have been testing Frictionless, but we find the standard somewhat lacking in terms of support for the complex metadata available in the SPSS's SAV format (and even SAS's sas7bdat/sas7bcat format too).
Currently, we manually extract all this information and store it in CSV files, but this seems like a task that a framework like Frictionless should handle seamlessly.
We would greatly appreciate it if Frictionless could enhance support for reading all the metadata available in the SAV format. In particular, it would be beneficial if it could apply formatting options to data specified in the metadata.
This includes, but is not limited to:

In addition to reading variable labels (field descriptions), also read value labels (important for categorical variables, e.g., questionnaire responses)
Formatting numeric values according to their specified formatting options when reading (e.g., read numeric values with no decimals as integers and not floats)
Ensuring dates are not returned as epoch time
Be able to seamlessly "apply" value labels when displaying data

This link provides a comprehensive guide to the different types of metadata possible to specify in the "Variable view" in SPSS.
We believe that such enhancements would not only benefit our research group but also other users who work with similar data formats. We look forward to seeing these improvements in future versions of Frictionless.

Hi @ipimpat,
Thanks a lot for such a well-described feature request!


Instancing, loosing materials

Hello. I am trying to make instancing. As I guess, each my actor should have RuntimeMeshComponent, but all have same RuntimeMesh. I have two types of actors:Storage, that initialize mesh(before all actions) and children, those have this code in constructor(Generated from BP):
runtime_mesh = CreateDefaultSubobject<URuntimeMeshComponent>(TEXT("RuntimeMesh"));
RootComponent = default_scene_root;
default_scene_root->CreationMethod = EComponentCreationMethod::Native;
runtime_mesh->CreationMethod = EComponentCreationMethod::Native;
runtime_mesh->AttachToComponent(default_scene_root, FAttachmentTransformRules::KeepRelativeTransform);
	if (!runtime_mesh->IsTemplate())
		runtime_mesh->BodyInstance.FixupData(runtime_mesh);

And in UserConstructionScript I assign RuntimeMesh to RMC of the Child
runtime_mesh->SetRuntimeMesh(storage->runtime_mesh->GetRuntimeMesh());

Also Child has the event, that modifies RMC, As I expect, all children and storage will be changed
...
runtime_mesh->UpdateMeshSection(0, Vertices, Triangles, Normals, TextureCoordinates, VertexColors, Tangents);
auto TheMaterial_Dyn = UMaterialInstanceDynamic::Create(TheMaterial, this);
		runtime_mesh->SetSectionMaterial(0, TheMaterial_Dyn);

And then I have strange results.
Case 1: RMC of storage has no materials, I make the child and then set material for RMC of storage in the editor. I expect, that child has material, but it has no the same.
Case 2: I set material for RMC of storage in editor and then make child. Child has no material and different address of RemoteMesh
Case 3: I set material of storage in UserConstructionScript  by C++
auto TheMaterial_Dyn = UMaterialInstanceDynamic::Create(TheMaterial, this);
		runtime_mesh->SetSectionMaterial(0, TheMaterial_Dyn);

and then I make child.. and the child has the material! It also has different address of RM then storage! Then I change material of storage in editor but material of child does not changes. When I call event of child, geometry and material changes for storage and children.
In all cases on event geometry changes for storage and children. In 1 and 2 I also change material of Child by editor or C++ and where is no effect for storage and others.
I do not know, how UE works, but I think, that RM should be shared data in shared smart pointer.

Closing as this is for an outdated version of the plugin that's no longer supported.
If you experience this or any other issues in the current version, feel free to report again!
Thanks!


[libarchive] Fix static linking dependencies

Fix configuration of libarchive's dependencies zstd and zlib, which would otherwise cause undefined symbols error when linking statically.

Versions bumped as requested.

I have to idea why the x64_linux CI tests failed.

c++: error: /mnt/vcpkg-ci/installed/x64-linux/debug/lib//libglib-2.0.a: No such file or directory
c++: error: /mnt/vcpkg-ci/installed/x64-linux/debug/lib//libglib-2.0.a: No such file or directory
c++: error: /mnt/vcpkg-ci/installed/x64-linux/debug/lib//libglib-2.0.a: No such file or directory

/azp run

@DDoSolitary
The failures on x64-linux are not related with this PR. I have rerun to rebuild.

/azp run

I'm unable to reproduce the x64-linux error locally. Running ./vcpkg install --overlay-ports=scripts/test_ports cmake:x64-linux on my Arch Linux installation on WSL works without issues.
The errors in windows triplets seems irrelevant. They failed due to some network errors.

/azp run

@JackBoosY

c++: error: /mnt/vcpkg-ci/installed/x64-linux/debug/lib//libglib-2.0.a: No such file or directory

It's quite surprising that it's trying to link against glib. The cmake port doesn't depend on the glib port at all (not even intermediately, glib is not installed when I built cmake in a clean vcpkg installation).

cc @ras0219 @ras0219-msft
Can you please take a look?
Thanks.

Strangely, after removing libglib-2.0.so from /usr/lib, build fails with another error
CMake Error at /root/vcpkg/installed/x64-linux/share/cmake/Qt5Core/Qt5CoreConfig.cmake:95 (message):
  Library not found: glib-2.0

So I still have no idea why it's unable to find the glib library in the CI build.

Depends on PR #15808.

@DDoSolitary
Could you please resolve the conflicts?

@NancyLi1013 Rebased.

LGTM now, thanks for your patience @DDoSolitary.

LGTM now, thanks for your patience @DDoSolitary.


precompile on Julia v1.8

Since Julia v1.8 aims to incrementally precompile modules, importing this package in my startup.jl causes a little Info warning every time I start a REPL that AbbreviatedStackTraces is skipping precompilation. Not a big nuisance but it has made me curious as to why __precompile__(false) is necessary for this amazing package.

Warnings are emitted when you load code that overwrites existing methods in other modules, and this stops the warning. If you find a way around that, please let me know.

Ah yes, I see. The only way I know of getting around that would be to use a package like Suppressor.jl.  However, this would add an additional dependency to the package and hide the fact that incremental precompilation isn't functioning for those functions.
If you would like to use Suppressor.jl, I've already tested to make sure it would work and would be happy to submit the PR.

Thanks for checking! I'm not sure. My view is that this functionality should be put into Base, and this packing is only a demonstration. One of the reasons I have to overwrite the whole chain is that it seems the way these functions are integrated makes them resistant to using the new version. But overwriting these whole functions could be problematic if they change in Base but aren't kept in sync.

I think the best solution would be for Julia to stop repeatedly trying to precompile packages that have deliberately disabled precompilation. https://github.com/JuliaLang/julia/issues/47123
So I'm going to close this as something I won't fix, but I appreciate the suggestion!

Actually, turns out there's another fix, which is coming -- sticking the code inside __init__() avoids the issue.

What's the status of this fix? I would really appreciate avoiding the visual noise of this otherwise great package!

Sorry for not updating this issue - turned out that other idea still didn't work.


Build a new Docker image for this test and use it.

Fixes https://clusterhq.atlassian.net/browse/FLOC-1657
This won't actually work until the image is on Dockerhub.  We should set up an automated build for it (I lack access).
Or else someone should explain why the docker-images repository is a better place for this kind of thing and then maybe clusterhq/docker-images#13 is a better idea (and the Dockerfile can be dropped from this PR).

To confirm, this will work because, as described in https://github.com/ClusterHQ/docker-images/pull/13, nothing else is ever using this, right? Please add a comment to the test to explain why it is special and resubmit. Won't this mean that we aren't testing a case which a user could run into and get the error message that we have been seeing in Buildbot?

[From the docker-images PR] Hmm.  Come to think of it, I'm not sure why docker-images exists at all.

Perhaps keeping the Dockerfiles with the code implies that the Dockerfile as it was in 0.3.0 corresponds to the image one will get when following the documentation for 0.3.0, but instead you get the latest images from the hub. But that doesn't seem particularly valid - particularly when we have examples of similar in Flocker (e.g. the new 404 page). Or perhaps when the RTD SSL proxy was useful, that proxy would be used for all documentation and not just the documentation that the proxy settings lived with. Maybe others have clearer ideas.
Oh, that reminds me, the "Readthedocs Flocker SSL Proxy" is no longer useful and highlights a pattern that when we have things in many hardly-touched repositories which don't go through code review, those repositories rot.
If this does get merged, there should be a follow-up issue to move the files from docker-images and perhaps to delete that repository.
Sorry for the incomplete / vague "review" but I'm just not sure what is best here. I'll give this back to you @exarkun but perhaps you'll want to just put it in review for someone else to look at.

This isn't the only test with this problem. If the others (see failures on http://build.clusterhq.com/builders/flocker%2Finstalled-package%2Ffedora-20/builds/1452/steps/trial/logs/stdio) can be fixed similarly please create follow up issues or resolve them here.

Won't this mean that we aren't testing a case which a user could run into and get the error message that we have been seeing in Buildbot?

Only the test method actually tries to remove the image.  Flocker itself never needs to do this so a user should never be able to encounter the problem being fixed in the test.

Perhaps keeping the Dockerfiles with the code implies that the Dockerfile as it was in 0.3.0 corresponds to the image one will get when following the documentation for 0.3.0, but instead you get the latest images from the hub. But that doesn't seem particularly valid

That's a really good point.  Perhaps I should make the test pull a certain tag of the image corresponding to the version number of Flocker.  This would probably complicate the release process, though - or is there a way to have Docker hub automatically tag certain release versions of an image?  I didn't notice such a feature in my exploration of the service.
Since this particular image has no interesting behavior and should never have any interesting behavior, I don't think we should need to modify it.  So a compromise solution may be to just leave a comment pointing out that it's a kind of unversioned external resource and warning anyone who ends up needing to change it that they'll have to do something about that.

This isn't the only test with this problem.

I think it is the only test with this particular problem.  The other failures look similar but are about containers being running rather than images being in use.

Thanks, the comments make it very clear now. Create a follow-up issue to move images out of the docker-images repository. This can also include an instruction to version the images - it might not be necessary for this particular image but I can certainly imagine this biting us in the future.
If you like, perhaps as part of this issue, edit the README of the docker-images repository to state that it is deprecated and new, similar Dockerfiles should be with the relevant code. See https://github.com/ClusterHQ/fedora-packages/blob/master/README.rst for similar.
Merge when you are satisfied.

Ok, I've figured out how to get Docker Hub to build this image and added some notes in:

https://clusterhq.atlassian.net/browse/FLOC-1696

Had to rename the README file so that Docker Hub could use it in its description.
I'll force another build and then merge if green.

Hmm. The problem still seems to be occurring on in this build:

http://build.clusterhq.com/builders/flocker%2Finstalled-package%2Ffedora-20/builds/1491
http://build.clusterhq.com/builders/flocker%2Finstalled-package%2Ffedora-20/builds/1491/steps/trial/logs/stdio

I checked that it's building the latest revision (93ff54954db74611584c200c51870f7f66f2851c)
[ERROR]
Traceback (most recent call last):
  File "/opt/flocker/lib/python2.7/site-packages/twisted/internet/defer.py", line 140, in maybeDeferred
    result = f(*args, **kw)
  File "/opt/flocker/lib/python2.7/site-packages/twisted/trial/_asynctest.py", line 279, in <lambda>
    return lambda: f(*args, **kwargs)
  File "/opt/flocker/lib/python2.7/site-packages/flocker/testtools/__init__.py", line 841, in run_process
    raise CalledProcessError(returncode=status, cmd=command, output=output)
subprocess.CalledProcessError: Command '['docker', 'rmi', u'flockerlocaltests/355822175895']' returned non-zero exit status 1

flocker.node.functional.test_deploy.DeployerTests.test_links

...
[ERROR]
Traceback (most recent call last):
  File "/opt/flocker/lib/python2.7/site-packages/flocker/node/functional/test_docker.py", line 348, in test_pull_image_if_necessary
    docker.remove_image(image)
  File "/opt/flocker/lib/python2.7/site-packages/docker/client.py", line 903, in remove_image
    self._raise_for_status(res)
  File "/opt/flocker/lib/python2.7/site-packages/docker/client.py", line 94, in _raise_for_status
    raise errors.APIError(e, response, explanation=explanation)
docker.errors.APIError: 409 Client Error: Conflict ("Conflict, cannot delete a76a82ba882f because the container e98b79fa9a3e is using it, use -f to force")

flocker.node.functional.test_docker.NamespacedDockerClientTests.test_pull_image_if_necessary
-------------------------------------------------------------------------------
Ran 1576 tests in 317.136s

FAILED (skips=84, expectedFailures=10, errors=10, successes=1473)
program finished with exit code 1
elapsedTime=321.270958

Is it possible that tests are being run in parallel  on a single build slave?
Or perhaps this is a Docker bug after all.

Is it possible that the NamespacedDockerClientTests are running before the docker daemon has actually enacted the container cleanup that was initiated after the same test in GenericDockerClientTests.
In which case, perhaps the solution is retry the image removal until docker images reports it gone....or something along those lines.

I thought something like this might reproduce the Docker condition where Docker reports that it has removed a container, but the server state hasn't yet caught up and server refuses to delete the image for that container.
while true; do
    container_id=$(docker run --detach clusterhq/test_pull_image_if_necessary)
    docker stop $container_id
    docker rm $container_id
    # I'd expect this to sometimes fail...but it doesn't
    docker rmi clusterhq/test_pull_image_if_necessary
done

https://github.com/docker/docker/pull/11137 may be a fix for this problem.
It looks like ContainerRm used to return success even if the cleanup operations had not succeeded. It will now only behave that way if you specify --force (I think)
So if incomplete container removal is what's preventing our subsequent image remove API call failing, we should see an error when the container removal fails.

Resolved this in a slightly different way.  See #1878.

I deleted the DockerHub automated build: https://hub.docker.com/r/clusterhq/test_pull_image_if_necessary


Zoom on iPad

Great app but all comics are always fully zoomed. As a result, the smallest of them look poorly on iPad's.

I agree. Showing multiple comics on-screen at once would be better use of the space. Failing that, I'd prefer to see a smaller but less blurry comic in the middle of a white screen than a much-too-large comic which took up all the space.

Cool, that could easily be done. I prefer the smaller/zoomed out version vs. multiple on screen at once.

Actually, now that I think about it the main comic selection view literally is a view which displays many comics on screen at once.

Given that many of them can be read from the comic screen and that I added the ability to view the alt text from the list directly, I'm going to close this now as its low on the priority list. Let me know if you have any concerns. Thanks!


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_576wl_cl7_/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_576wl_cl7_/clone/recipe/meta.yaml:21: cython_needs_compiler: Cython generates C code, which will need to be compiled
ERROR: /tmp/abs_576wl_cl7_/clone/recipe/meta.yaml:23: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_576wl_cl7_/clone/recipe/meta.yaml:25: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_576wl_cl7_/clone/recipe/meta.yaml:41: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_576wl_cl7_/clone/recipe/meta.yaml:41: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_576wl_cl7_/clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: /tmp/abs_576wl_cl7_/clone/recipe/meta.yaml:41: missing_description: The recipe is missing a description
Errors were found


Add Kusto function definition of SpecsPipelinesBuildsJobLogs.kql

See the comment in the added function for details.
I followed the guidance I wrote down earlier here:
https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/625/Kusto-Query-Catalog?anchor=adding-functions-to-`azsdkengsys`-cluster

I assume you are just backing up this here which is fine

Exactly!

/CheckEnforcer Override

/CheckEnforcer Override

/check-enforcer override


Fix verifying ATX chain containing a checkpointed ATX

Motivation
All ATXs in the checkpoint are considered to be valid and don't require checking POST.
Description
Because a checkpointed ATX doesn't have a blob in the database - it's not possible to obtain its PoST.
Test Plan
Added a unit test for the fixed scenario.
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[ ] Update documentation as needed
[x] Update changelog as needed

bors merge


fix(blockingproxy): Start bpRunner strictly after setupDriverEnv

If local driver provider is used, seleniumAddress appears in config only after setupDriverEnv() is resolved.
Here is an example of the error caused by missing seleniumAddress during bpRunner start:
protractor$ node ./built/cli.js --webDriverLogDir ./ ./spec/driverProviderLocalConf.js
[22:41:26] I/launcher - Running 1 instances of WebDriver
[22:41:26] I/local - Starting selenium standalone server...
[22:41:26] I/BlockingProxy - Starting BlockingProxy with args: --fork,--seleniumAddress,,--logDir,./
[22:41:27] I/local - Selenium standalone server started at http://<IP_ADDRESS>:37560/wd/hub
[22:41:27] I/protractor - Starting BP client for http://localhost:38175
[22:41:27] E/launcher - Error: connect ECONNREFUSED <IP_ADDRESS>:80
[22:41:27] E/launcher - WebDriverError: Error: connect ECONNREFUSED <IP_ADDRESS>:80
    at WebDriverError (/home/wncm/cyletrip/protractor/node_modules/selenium-webdriver/lib/error.js:27:5)
    at parseHttpResponse (/home/wncm/cyletrip/protractor/node_modules/selenium-webdriver/lib/http.js:521:11)
    at doSend.then.response (/home/wncm/cyletrip/protractor/node_modules/selenium-webdriver/lib/http.js:440:13)
    at process._tickCallback (internal/process/next_tick.js:109:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/home/wncm/cyletrip/protractor/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/home/wncm/cyletrip/protractor/node_modules/selenium-webdriver/chrome.js:709:29)
    at createDriver (/home/wncm/cyletrip/protractor/node_modules/selenium-webdriver/index.js:167:33)
    at Builder.build (/home/wncm/cyletrip/protractor/node_modules/selenium-webdriver/index.js:623:16)
    at Local.getNewDriver (/home/wncm/cyletrip/protractor/lib/driverProviders/driverProvider.ts:60:29)
    at Runner.createBrowser (/home/wncm/cyletrip/protractor/lib/runner.ts:225:39)
    at q.then.then (/home/wncm/cyletrip/protractor/lib/runner.ts:391:27)
    at _fulfilled (/home/wncm/cyletrip/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/home/wncm/cyletrip/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/home/wncm/cyletrip/protractor/node_modules/q/q.js:796:13)
[22:41:27] E/launcher - Process exited with error code 199

Process finished with exit code 199

I signed it!


Why is the local scratch folder in 750 instead of 700 ?

https://github.com/ComputeCanada/spank-cc-tmpfs_mounts/blob/master/cc-tmpfs_mounts.c#L118
Qt complains about the permissions of the folder not being 700
also discussed here:
https://github.com/flatpak/flatpak/issues/3397
https://codereview.qt-project.org/c/qt/qtbase/+/256521

Note: 750 appears in a few other places in the C code


new default intervals for Pilot

Repeat of PR #779
Release note:

NONE

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/new-e2e-rbac_no_auth.sh
f5b752ebb12b2f99159a78f9d71c2a4a85a1b557
link
/test new-e2e-rbac_no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Verified from logs that the short refresh delays are maintained for tests..
    "cds": {
W0913 14:39:45.827]       "cluster": {
W0913 14:39:45.827]         "name": "cds",
W0913 14:39:45.827]         "connect_timeout_ms": 1000,
W0913 14:39:45.827]         "type": "strict_dns",
W0913 14:39:45.827]         "lb_type": "round_robin",
W0913 14:39:45.827]         "hosts": [
W0913 14:39:45.827]           {
W0913 14:39:45.827]             "url": "tcp://istio-pilot.mixer-test-83a972637e3b4521955f6fce48:8080"
W0913 14:39:45.827]           }
W0913 14:39:45.827]         ]
W0913 14:39:45.827]       },
W0913 14:39:45.828]       "refresh_delay_ms": 1000
W0913 14:39:45.828]     }
W0913 14:39:45.828]   },

/lgtm


Maximum Sum decreasing Subsequence in Julia | GSSoC'21 | DP

💥 Proposal
Maximum Sum decreasing Subsequence in Julia
Have you read the Contributing Guidelines on Pull Requests?
YES

/assign


Client side streaming

Hi! Amazing job with this plugin!
We were using the library my making simple RPC calls and with server streaming without a problem, but the gRPC service we are using has moved to a bidirectional streaming RPC.
It sounds like TurboLink supports both client and server streaming, so we should be okay, but we're having trouble figuring out how to get the client streaming working. After we initialize the function and send a request, sending a second request to the same function doesn't seem to work.
Can you describe the general flow of how client streaming works with Blueprints?
Thanks in advance!

It confuses me too....

You could see the full demo, in blueprints test tab, the Watch method shows this case.
The key point is 'You must reuse the context'


2020-11-02 - KDB Project Call Meeting Agenda

Date
Monday, November 2nd, 2020 - 10am EST / 3pm BST
// First Monday of every month
Attendees

Fullname
Affiliation
GitHub Username

Agenda

(5 min) Convene, roll call, welcome new people.
(5 min) Approve previous meeting minutes.
(5 min) Kdb Studio updates.
(5 min) Kdb Studio README?

Do we need to say anything specific about icons in the README, or just remove the blurb?
What do we want to say about downloading a JAR?
Are labels rendered in GitHub Markdown?

(10 min) Updates on best practices to contribute upstream?
(5 min) Saving CSV files with compound columns: https://github.com/finos/kdb/pull/32

.h.tx[`csv]:{.q.csv 0: .finos.html.stringifyCompoundColumns x}

(5 min) Allow multi-line functions to be pasted into the console.

https://github.com/alvin-c-shih/kdb/blob/master/misc/mline.q
Does not support \d.  Do we want it to?

(5 min) AOB, Q&A, Adjourn.

Decisions Made

Decision 1
Decision 2
...

Action Items

Action 1
Action 2
...

WebEx info
Webex

https://finos.webex.com/finos/j.php?MTID=mfc9190e818fd85f9e3ece5166f23d920

Dial-in and Project Materials

US: +1-415-655-0003 US Toll
UK: +44-20319-88141 UK Toll
Access code: 663 746 304
GitHub Repos:

https://github.com/finos/kdb
https://github.com/finos/kdb-studio

Wiki Page:

https://finosfoundation.atlassian.net/wiki/spaces/DT/pages/329383945/kdb+Project

KDB Metrics on FINOS

https://metrics.finos.org/goto/033b15c80f0d08cab70f40f4358932f6

hi!

morgan stanley

hi


Fix disconnect remote endpoints on close endpoint

This fixes #19, though has not been thoroughly tested. The behavior matches that of network-transport-tcp.

This repositoru has moved, and this PR was re-created here: https://github.com/haskell-distributed/distributed-process/pull/417


Cannot compile on homeassistant

Hi I am attempting to compile this on esphome on homeassistant, but am facing the following error:
INFO ESPHome 2024.3.1
INFO Reading configuration /config/esphome/playbulb-candle.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing playbulb-candle (board: esp01_1m; framework: arduino; platform<EMAIL_ADDRESS>--------------------------------------------------------------------------------
HARDWARE: ESP8266 80MHz, 80KB RAM, 1MB Flash
Dependency Graph
|-- ESPAsyncTCP-esphome @ 2.0.0
|-- ESPAsyncWebServer-esphome @ 3.1.0
|-- DNSServer @ 1.1.1
|-- ESP8266WiFi @ 1.0
|-- ESP8266mDNS @ 1.2
|-- noise-c @ 0.1.4
|-- NeoPixelBus @ 2.7.3
Compiling .pioenvs/playbulb-candle/src/main.cpp.o
In file included from src/main.cpp:45:
src/ping_esp8266.h:22:10: fatal error: esphome/components/sensor/sensor.h: No such file or directory
   22 | #include "esphome/components/sensor/sensor.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
*** [.pioenvs/playbulb-candle/src/main.cpp.o] Error 1

========================== [FAILED] Took 1.44 seconds ==========================
I have included the libraries below:
esphome:
  name: playbulb-candle
  friendly_name: playbulb-candle
  includes:
    - ping/ping_esp8266.h          #file located here: /config/Keypad_I2C.h
    - asyncping/AsyncPing.h

esp8266:
  board: esp01_1m

# Enable logging
logger:

Any ideas what I am doing wrong here?
Thanks

Probably, the file was removed/renamed in esphome. I have not updated my esphome for a while.


vimPlugins.neuron-vim: ihsanturk/neuron.vim ->  fiatjaf/neuron.vim

Motivation for this change
The current derivation for vimPlugins.neuron-vim points to ihsanturk/neuron.vim, which doesn't seem to be actively maintained. This PR switches over to an actively maintained fork, fiatjaf/neuron.vim, which works with recent versions of neuron.
Things done
First I removed the original ihsanturk/neuron.vim from vim-plugin-names. Then I ran the update script like so:
./update.py --add fiatjaf/neuron.vim

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

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

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

hey @SuperSandro2000, I think you'll find that the commits are a little better organized now. The first one, 22d65ff, just contains the results of update.py with no modifications to the plugin list. The next one, 927c644, is the result of update.py --add fiatjaf/neuron.vim and only includes the change to the generated nix expression and vim-plugin-names list. Finally, 4d69f745fe96cd19a672fa991a381c67f2aadc7f de-dupes the neuron-vim entry by removing the unmaintained plugin from the plugin list and generated nix expression.

Conflict arose with the base; just fixed that.

Hey team, any further blockers?
/cc @SuperSandro2000 @jonringer

You got it, thanks Jonathan. I had originally spread it out because I was following the vim plugin-specific instructions (using update.py).


Add sound modes from telnet connection

When using the new telnet interface, the sound modes are reported diffrently on my Marantz SR5008.
This adds the sound modes as they are reported by the telnet connection.

@ol-iver could you merge this?


Create a timeline

Add a list of all your activities, achievements, work experience. Add as much info as you can remember. In case you don’t have working experience tell about your pet-projects or student projects. Don’t be shy :)

I don't have many activities, but I want to start jogging very soon.


Improve vagrant setup

Don't port forward to invalid ports (above 65535)
Don't port forward the mesos-slave and mesos-master ports, since those daemons only listen on the host-only adapters.
Forward port 6627 which is the Storm Nimbus thrift port, in case you want to submit topologies by making a connection from outside the master VM, and by using localhost:6627 instead of the host-only-master-IP:6627.
Avoid adding duplicate entries to /etc/hosts when repeatedly provisioning or running the start scripts.
Rename vagrant-launched start scripts to be a bit clearer on the intent of each.
Add date to the "starting" log for each service.
Instead of just stopping the mesos-master on the slave VM, we also disable upstart's automatic starting of mesos-master on the slave VM.
Remove incorrect use of sudo with echo; common problem in docs and provisioning shell scripts.  The provision scripts are run under sudo by vagrant by default. When run manually, they must be run under sudo as well.
Allow reprovisioning to succeed by changing an element of the inline provision script to use ln -sf (force) instead of just ln -s
Don't pass IP to start-nimbus.sh script, since it doesn't use it.
Set IPs in variables instead of hard-coding them.
Add a script which can be used to submit a topology JAR file, and document it.
Link from base repo document to Vagrant docs.
Removed trailing whitespace.
Removed tab chars.
Make apt-get provisioning invocations "loggable" by suppressing progress indicator ('-q' option)
Prevent "default: stdin: is not a tty" error during vagrant provisioning.
Enable running of docker images by enabling the containerizer in the mesos-slave configs set by the vagrant-launched scripts.
Prevent problem with MesosNimbus failing to start because of being unable to create its configured log dir (config: storm.log.dir => /vagrant/_release/storm-mesos-0.9.6/logs).  This is done by creating the "logs" dir in the release dir during the build-release.sh packaging step.

root cause: seemingly a bug in the virtualbox guest additions file sharing driver: if a dir previously accessed by the guest is removed from the host, then the guest gets confused and thinks the dir is present even though it really isn't anymore

mkdir within guest failing because "the file exists", even though ls (on outer host or within guest) shows that the file doesn't exist

improve build by downloading storm binary package in tarball format instead of zip, so that we have better perms in resultant package.
improve build by setting user & group IDs as 0 instead of whoever happens to build it
improve comments in storm.yaml
made the 2nd VM ("slave") optional, and have it off by default, since the 1st VM ("master") has all the components needed (mesos-master, mesos-slave, mesos-nimbus, storm ui, zookeeper).
during provision script runs, stop/kill previous storm & mesos daemons. Really we should be doing some more formal starting of the nimbus & ui a la runit or something, but that can be fixed later.
set the ownership of the files in the tarball package to be root.
check that tar is gnu-tar and not bsdtar (e.g., --owner should be supported)
document location of mesos configs
document location of zookeeper configs & data
added links to vagrant.md to the Web UIs of mesos and storm.
added info to vagrant.md docs about where various log files of interest can be found.
wipe out mesos-slave work_dir on each vagrant provision, to allow ease of accessing the executor & task logs via wildcards.
Adjust bin/build-release.sh dockerImage function to just run the docker build, which also runs bin/build-release.sh from within the docker container.

@choang & @JessicaLHartog : I've pushed some fixes for your comments.

I can confirm that the vagrant up workflow works flawlessly.  :ship: for that piece.  (I saw references to Docker which I did not test)

@choang : thanks for testing & the review. The docker stuff is not fully "in-scope" for this change really, I just wanted to make it clear that bin/build-release.sh dockerImage was broken by #65's changes to the Dockerfile, and thus simply replaced its contents with a trivial invocation of a docker-build.  It should probably be adjusted, will address later.

@choang & @JessicaLHartog & @dskarthick:  I followed Chi's tip for passing the storm.yaml into the MesosNimbus, it works great!  See setting of STORM_CONF_DIR in vagrant/start-nimbus.sh.
Was able to show that we can simply set storm.log.dir in storm.yaml in the MesosNimbus, and it will propagate to the MesosSupervisor & workers, thus obviating any need for us to be modifying cluster.xml explicitly.  Woot.

It looks like the changes here will have several conflicts with those in #77. Perhaps we can :ship: this one sooner rather than later, so that #77 can re-base and that PR will become easier/shorter to review?


routeMiddleware not working for request method OPTIONS

Laravel Version: 5.4.21
PHP Version: 7.0

Description:
App\Http\Kernel::$routeMiddleware not working in Laravel 5.4 (may be in 5.3) for request method OPTIONS.
Because https://github.com/laravel/framework/blob/v5.4.21/src/Illuminate/Routing/RouteCollection.php#L232
But I'm not have elegant solution for this problem.
Steps To Reproduce:

Add my middleware (for example OptionsCorsMiddleware) to App\Http\Kernel::$routeMiddleware array.
Send OPTIONS request - middleware not handle.
Add my middleware to App\Http\Kernel::$middleware array.
Send OPTIONS request - middleware was handle, but I don't want run my middleware (or middleware from https://github.com/barryvdh/laravel-cors) for all requests.

The thing is the OPTIONS request won't match any of your routes so the router will error before running any of your route middleware, that's why it has to be a global middleware.

@themsaid Thanks. I will know that it impossible and that register global middleware for OPTIONS method is good solution.
I hope this information will be useful to somebody.


Using nightly builds on Travis CI is broken

Using nightly builds on Travis CI has been advertised in docs for Crystal language for some time now, yet ATM it doesn't work.
Refs: https://github.com/travis-ci/travis-build/blob/b2a89dad8e7020c4c28b396639b36d87e5b1d4f6/lib/travis/build/script/crystal.rb#L80

Without nightly releases users caring about having their codebase tested on Travis CI against current Crystal are left with 3 less-than-optimal-options:

Wait for next Crystal release—which might happen... who knows when?
Use docker with nightly tag—but! nightly is 11 days old as of now, and new builds are tagged with nightly-YYYYMMDD scheme, making it hard to point at just that last release—fixed in #5837
Build it manually—ouch

Since nightly releases are being build as of #5182, the only thing missing would be hooking this up to apt package index, which is used by Travis CI.
With that in place we'd be able to use nice'n'simple .travis.yml:
language: crystal
crystal:
  - latest
  - nightly

Howgh! Thanks for reading!

@matiasgarciaisaia @bcardiff 1 week l8r... ping?

Ping again... 🕦 🌙  💤

@bcardiff 🏓

It's fine, so the nightly.crystal-lang.org domain should be redirected something else, right @jhass? The packages there were unsigned or it was using some key?

Yeah.
They were signed by a subkey of the one used for the main APT repo. I can check later this evening if I can still find it, if needed.

Regarding hosting debian packages on S3, I've found some resources which could help with that:

https://github.com/krobertson/deb-s3
https://github.com/aptly-dev/aptly

We already host debian packages on s3 for the releases. We should just ask travis to change how the crystal: nightly option works, and publish packages in the existing repo.

That is ask Travis just means sending a pull request to travis-build

Yes, and to do that we need to have an apt repo with nightlies.
See https://github.com/travis-ci/travis-build/blob/271a31325b6ad383d690ed81149554495eda08e9/lib/travis/build/script/crystal.rb#L80-L85

Actually if you'd keep the same domain and gpg key, the PR to travis-build is needless, it would Just Work™

@jhass if you had chance to find the certificate for nightly send it to me / follow up by email.
I was waiting for news from https://bintray.com/ for OSS projects and use nightlies there and see if it could be used to automate publishing of all releases. @Sija the options you send only support .deb packages.

For travis nothing else. But if we aim for nightlies in the same platforms as the official packages then, they are not enough as a complete solution. Worst case we host them in S3 but we want to check if a services may come handy.

@bcardiff my personal grief is stated in the original post, that is, using nightlies on travis, I also believe that would cover majority of use-cases. On my local machine I have no problem with compiling crystal myself, I don't need packaged nightlies for that. Of course that would be neat and all, but is it worth the hassle?

Just a note: For the time being, you can also use this script to install Crystal nightly from circle ci artifacts: https://gist.github.com/straight-shoota/a2f4b29203936c04c578d6f6a1ad5f9b

@bcardiff Anything going on with this?

@Sija Not yet. The workaround for now is to use docker nightly images or the script, but in travis would be easier to use docker nightly

Any guide on how to run a shard build with crystal nightly docker image? Should I include a Dockerfile in the shard's repository?

https://bintray.com supports OSS now, as seen on their website

@vladfaust Just follow the guides to using docker images in your build: https://docs.travis-ci.com/user/docker/ and use image crystallang/crystal:nightly.

There are difficulties if need to test against databases with docker approach. I wonder why nightly doesn't work now? It's clearly a bug because Travis says nightly should work...

Bintray looks promising, especially with free OSS package... Perhaps it's the time to re-evaluate the situation? 🏓 @bcardiff

Any update on this?


Fixing DDP, catalyst test errors

Description

Temporarily turned off DDP tests
Fixed catalyst example
Refactored catalyst notebook

Related to: fix test errors
Any expected test failures?
Tests will fail on python 3.11

Add a [X] to relevant checklist items
❔ This change

[ ] adds a new feature
[X] fixes breaking code
[X] is cosmetic (refactoring/reformatting)

✔ Pre-merge checklist

[X] Refactored code (sourcery)
[X] Tested code locally
[X] Precommit installed and run before pushing changes
[X] Added code to GitHub tests (notebooks, scripts)
[ ] Updated GitHub README
[ ] Updated the projects overview page on Notion

🧪 Test Configuration

OS: Windows
Python version: 3.8
Neptune version: 0.16.15
Affected libraries with version: catalyst==22.4

@normandy7 - docs will need to be updated to reflect catalyst changes

LGTM!

@normandy7 - docs will need to be updated to reflect catalyst changes

Gonna need some pointers. Not everything that's changed in this PR has a counterpart in the docs guide, as it's fairly generic. Is it the installs and imports that need changing? Are both tensorboard and torchvision required?

just checked the docs, I think we should be good as is

Got it, thanks


Windows success

Hello,
great project you have running here. Had anybody success running this with windows  10 bash or under normal Windows just to utilize the gaming pc that is sitting?

Does it have rsync and ssh?
On Sun, Mar 12, 2017, 15:40 Rene Gens<EMAIL_ADDRESS>wrote:

Hello,
great project you have running here. Had anybody success running this with
windows 10 bash?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gojuno/mainframer/issues/157, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7B3JS_yARPsH_qKWVMZgNbcXgKsXA4ks5rk-fSgaJpZM4MahwS
.

@artem-zinnatullin yes it has both of them but I have trouble setting up the ssh up until now. Has anybody else tried it?

Hi @renegens, you can set up a docker container with Linux on your windows machine. I have recently written this blog post which explains the Mainframer setup on a windows machine with docker container. It may be helpful to you.
Blog Post : https://medium.com/@balachandarkm/speed-up-android-builds-with-mainframer-docker-container-in-a-powerful-remote-machine-ce7b9e122a49

@balachandarlinks Thanks for pointing this out, will check it asap. Great post btw :)

@balachandarlinks like 👍 !

I'm closing this issue for now, to sum up: preferred software options on remote machine with Windows OS are Docker, VM with Linux or integrated "bash supported" (parts of Linux/Ubuntu environment).
Please feel free to comment into this issue or submit a PR with documentation on configuring Windows as remote machine for Mainframer.


test-plugin test is broken

There was a change in the API of SynthSubset class some time back.
The plugin didn't get updated in this test:
https://github.com/chipsalliance/Surelog/actions/runs/3551926372/jobs/5966501132

This was fixed with https://github.com/chipsalliance/yosys-f4pga-plugins/pull/407 (merged two days ago, last Surelog build is four days old). I'll update the integration repository and rerun the CI to verify.

Updated the integration repository (https://github.com/antmicro/yosys-systemverilog/pull/1313), the Surelog test now passes, see https://github.com/chipsalliance/Surelog/actions/runs/3551926639.


Body Stream Closes when running Browser Request

So I am trying to write some middleware that will authenticate the request, todo the middleware needs to make a call to another HTTP server to find out, (the final version will use cache)
I have boiled down to the smallest working example of things breaking. Observe the body changing to unreadable.
If I use a StreamingRequestMiddleware everything will work fine, however as soon as I do a browser request the request body closes and becomes unreadable.
Maybe I am missing something and this is how it's meant to work, if so a workaround or solution direction would be most welcomed.
I don't really want to do a blocking http call, (I have tested this and this works other than it blocking the whole server)
<?php
require __DIR__ . '/../vendor/autoload.php';

use Psr\Http\Message\ResponseInterface;
use Psr\Http\Message\ServerRequestInterface;
use React\Http\HttpServer;
use React\Http\Middleware\StreamingRequestMiddleware;

$http = new HttpServer(

    new StreamingRequestMiddleware(),
    function (ServerRequestInterface $request, callable $next) {
        dump($request->getBody()->isReadable()); //true

        return $next($request);
    },
    function (ServerRequestInterface $request, callable $next) {
        dump($request->getBody()->isReadable()); //true

        $browser = new React\Http\Browser();

        return $browser->get('https://www.google.com')->then(
            function (ResponseInterface $response) use ($next, $request) {
                dump($request->getBody()->isReadable()); //false

                return $next($request);
            }
        );
    },
    function (ServerRequestInterface $request) {

        dump($request->getBody()->isReadable()); //false

        return new React\Http\Message\Response(
            200,
            ['Content-Type' => 'text/plain'],
            'Hello World!'
        );

    }
);
$socket = new React\Socket\SocketServer('<IP_ADDRESS>:8080');
$http->listen($socket);
echo 'Listening on ' . str_replace('tcp:', 'http:', $socket->getAddress()) . PHP_EOL;

Hold the phone
I am experimenting with adding a middleware to pause the body stream before doing anything else

    new StreamingRequestMiddleware(),
    function (ServerRequestInterface $request, callable $next) {
        $request->getBody()->pause();
        return $next($request);
    },...```

Since you went with a streaming request body we expect you to take care of it. Pausing or buffering at the start can be a way. However it is meant for use cases where you parse the body as it streams in. But it is only recommended to use a streaming body if you have a need for it. If you don't, drop it and let the server buffer the body for you.
So in your case what probably happened is:

Request comes in
Body is still streaming in when your closure gets called
Browser sends request out
Fully body came in while that request is out
Body stream closes
Browser request completes
You confused of what just happened


Add test for infinite loop

A test to ensure the while loop bug in waitForSlaveConnection does not return.

Can one of the admins verify this patch?

I think this is abandoned.


Can't get more than 10 orders

hi
Thanks a lot for the extension. Works like a charm.
I can't get more than 10 orders from the REST API. I saw a few discussions on the other issues but couldn't find a solution so far.
I changed the API version from v3 to v2 but with the same end result.
Ideas currently:

Query String parameter ignored by my server (unlikely)
Server settings prevent more items from being returned (I don't know where to look exactly)

If I use "OrdersByDate" I can get different orders but always only 10.
Do you have any hints?

I'm also having this issue after updating some plugins... It would be great if they could update this!

Hey @engineererr
Sorry for the late reply. Have you tried using a tool like Fiddler to see exactly what you're getting as a result of the API call that the connector is making? are you able to use the same REST API call in other tools ? (perhaps Postman?)
It seems likely to be a limit set at the server level, but that would require some investigation as to what exactly you're getting in response from the server. I wouldn't be able to tell you exactly where to look for either as I'm not really an expert on that side of things, but I'd encourage you to get ahold of your WooCommerce admin to get more information around this.
Basically, if it works in any other tool but it doesn't work with this connector then its safe to say that there's something wrong with the connector. Otherwise, it's more than likely a server setting or limitation purposely set by the server or perhaps by your host.
The fact that with the "OrdersByDate" function you only get 10 confirms that there's something unique happening with your specific server. The connector is effectively just following the documentation that the WooCommerce provides in terms of how pagination should behave in standard circumstances using the "Link Header" as stated in the link below:
https://woocommerce.github.io/woocommerce-rest-api-docs/#pagination
Perhaps what's happening is that your specific instance of WooCommerce does not provide the "Link Header" so the connector simply can't figure out what should be the next page.
@DataHippo93  hope the above information helps. Unfortunately, I don't have other contributors to this repo, so its only me trying to provide some assistance.

Hey @migueesc123 was able to resolve the issue in my fork. I ended up having to use the Orders by Date function to get all the orders. I also added products which I needed.
https://github.com/DataHippo93/WooCommerceConnector
I am planning to build this out to more API endpoints for my own internal use cases and will keep you posted

@DataHippo93 I tried to compare both connectors and the only change that I'm able to see is that your connector has the Products data in it.
Was there anything else changed? Are you still only getting 10 rows with this connector? if not, what changed or what was the issue and how did it got resolved?

Issue is that the line:
Metadata = Value.Metadata( Orders) [Headers] [Link],
Should be:
Metadata = Value.Metadata( Orders) [Headers] [link],
With a lower case l in the last link.


torchvision support mobilenet and shufflenet

Hi, thanks for sharing your great work!
I found that the torchvision has been updated, and it support mobilenet, shufflenet and so on.
Will you update your repository?

Hi @liminn.
Yes, I am planning to take a look at the new torchvision models this week and try to add them to my package.

@creafz  Great!

I have uploaded cnn_finetune 0.6.0 to PyPi, it contains new pretrained models from torchvision: resnext50_32x4d, resnext101_32x8d, mobilenet_v2, shufflenet_v2_x0_5, shufflenet_v2_x1_0, googlenet. Please open a new issue if you encounter any problem with the new models.