Integrate Bootstrap Listr Alpha in Wordpress

Hello developers,
I wanted to ask can I add bootstrap listr to my wordpress website? Like in a page?
What I want is that I have this layout of a theme, like a regular blog with sidebars and menus etc.
I want this listr to be visible in the post area. I can achieve such a thing with iframe inside the post area but that makes the page too slow. Any other method to integrate this in a wordpress page/post will be very helpful...
Thanks a lot.

This is not an issue.
Anyway, you would probably have to create your own WordPress plugin for this. For details refer to the WordPress Codex.


No card type configured

I can't making this card to work, I followed the instructions, but I keep getting "No card type configured" in lovelace.
I restarted HA after downloading and adding it.
Any advice?
Thanks?

Yeah - I get "Custom element doesn't exist: circle-sensor-card."
You ever get it to work?
Ta!

NM - got it to work - looks like the .js needs to go in the www/community folder; not in the www.
Would love someone to explain why the documentation doesn't match what works?
(Not just for this one - all custom cards that are installed manually just say the www folder...)
Sorry - clearly very new to this!


Still issues with broadcast-channel dependency and svelte-kit

@amen-souissi @benmccann I tried 1.4.1 now.
We still have a problem with broadcast-channel if I remove these lines from svelte.config.js:
vite: {
  optimizeDeps: {
    include: ['broadcast-channel']
  },
}

This is the log:
1:22:06 AM [vite] Error when evaluating SSR module /node_modules/broadcast-channel/dist/es/method-chooser.js:
ReferenceError: require is not defined
    at eval (/node_modules/broadcast-channel/dist/es/method-chooser.js:26:20)
    at instantiateModule (C:\kit\node_modules\vite\dist\node\chunks\dep-e9a16784.js:68197:166)

Do you have any idea?
Maybe this is related to "type": "module" in package.json which is the default in a new SvelteKit project, right?

@frederikhors can you provide a small sample project to reproduce? I can try taking a look to see what the issue is then

npm init svelte@next my-app
cd my-app
npm install
npm install --save @sveltestack/svelte-query
npm run dev

I'm using Windows 10.

I have no issue on Linux. Maybe you're hitting the Vite Windows bug https://github.com/vitejs/vite/issues/2393

Hi, I have the same issue. I'm using macOS.
`500
require is not defined
ReferenceError: require is not defined
at /node_modules/broadcast-channel/dist/es/method-chooser.js:19:20
at instantiateModule (/Users/marcomonsanto/Documents/pessoal/crypto-wallet-svelte/node_modules/vite/dist/node/chunks/dep-e9a16784.js:68197:166)
`

@marcomonsanto can you provide a repo and instructions to reproduce? I just tried the steps above again that @frederikhors provided and still don't see any error

Hi, I don't think this is a window-only bug, cuz I also got this error using Ubuntu Linux. Even I tested a basic repo running in codesandbox, I still got the same error.
Here is a reproduce repo made in Code Sandbox, hope this help: https://codesandbox.io/s/svelte-query-bug-141-f0ksh

Thanks for providing the repo. That's a bug in broadcast-channel: https://github.com/pubkey/broadcast-channel/issues/636

This isn't a real solution that can be merged into broadcast-channel, but as the relevant issue on that repo was closed, I made a fork that removes NodeJS support and the related call to require.
https://github.com/dimfeld/broadcast-channel
I'm not using the broadcast functionality in svelte-query, so can't guarantee that it still works, but the changes were minor.  Hopefully it helps someone until a proper solution arrives:
You can use pnpm overrides, yarn resolutions, or a similar mechanism to force svelte-query to use it.

I sent a PR for this: https://github.com/SvelteStack/svelte-query/pull/50. I'm just doing it to try to get more libraries working on SvelteKit. I don't use svelte-query myself, so help testing would be appreciated as I haven't tested it

Hello,
A new version (v1.5.0) of this library has been published today.
This version makes broadcast-channel an optional dependency.
This should fix all problems with svelte-kit.
If you need to use the experimental broadcastQueryClient, you now need to install it manually (see: broadcastQueryClient).
If you still encounter issues with v1.5.0. Please open a new issue.


Unable to disable XP module

Hello,
I'm trying to disable the XP module as it is something I do not wish to use on my server. I've tried typing ".sm xp disable" and even tried things like ".sm exp disable" and other ways of typing XP such as; xp, XP and Xp to no avail.
I'm assuming that either i'm not typing it correctly or the module doesn't seem to be able to be disabled, which i'm assuming shouldn't be the case?
Thanks in advance! 👍

XP module contains commands such as .xp, .clubinfo, etc.
if you wish to disable XP gain, exclude the server by typing .xpex Server.
But if You're trying to disable commands from XP module, make sure You have Nadeko role. (Make a new role, call it Nadeko and give it to yourself)

What kyousei said.  And btw it works for me.

Do I have to give the Nakedo role any permissions after creating it? And can I disable all modules? Because I dont want to have NSWF module on my server

NSFW commands can't be used outside NSFW channels. so if you don't want NSFW commands, you don't need to do anything.


Support for other container runtimes

Hey team,
First, love the project and thanks for all of your hard work.
Recently I've taken a look at lean-cli for personal use. On my laptop, I use colima as a replacement for Docker desktop due to the recent controversy surrounding their license agreement.
While my docker cli is mostly compliant via the podman interface, the docker client for python is hardcoded to only try to connect to the docker socket in /var/run/docker.sock
When I would try to run live, I would encounter the error:
lean live <flags>

Error: Please make sure Docker is installed and running
Visit https://www.lean.io/docs/lean-cli/key-concepts/troubleshooting#02-Common-Errors for more information

However, I can symlink the docker.sock file in its expected location and get it to run fine:
sudo ln -s $HOME/.colima/docker.sock /var/run/docker.sock

lean live <flags>

Pulling quantconnect/lean:latest...
latest: Pulling from quantconnect/lean
345e3491a907: Pulling fs layer
57671312ef6f: Pulling fs layer

Should we try to enumerate some of the docker alternatives and their socket locations to support other docker compliant runtimes, or document how to symlink sockets to the expected path in order to support running lean-cli for a broader set of runtime environments?

😬 At this point, we're stretched too thin to try and enable support for other non-docker hosts. I would welcome and appreciate a pull-request to enable support for colima but cannot assist in its design.
The top priority currently is to expand the lean-cli to map all the functionality of LEAN. We have so many brokerages and data sources supported in LEAN Core but they're pretty tricky to use since it is all buried in source. The LEAN CLI should able things like:
lean data download --source=yfinance AAPL ...
lean data download --source=iex AAPL ...
lean data download --source=iqfeed AAPL ...

We're gearing up for a crowd-raise to try and increase our funding and bandwidth and would appreciate your help to improve the project further. If you like what we're doing, please join us in the raise =)

No worries. Best of luck!

I for one would welcome podman compatibility, which is already designed to be a drop-in replacement for docker
j


Override workspace settings with a folder one

I'll start with an example because I don't know how to describe my problem
I want to make a workspace with 2 folders

C://Users/me/project/
C://User/me/notes/

My project folder contains a ./vscode/settings.json
I'd like to be able to tell to vscode, "I want you to take in account my settings file from my project folder, override workspace settings if necessary"
I don't know if I explain myself well 😅

If you are not already familiar with multi-root workspaces please read about them here.
If you are already using a multi-root workspace but can't achieve what you want regarding settings please provide more information.

Oh okay !
They are just some extensions that doesn't support multiroot workspaces
I'll contact the devs
Thanks


Support MovieLens dataset

https://grouplens.org/datasets/movielens/

MovieLens dataset をred-datasets から利用できるようにするのに下記のpermission取得が必要な様子である。
https://grouplens.org/datasets/movielens/

Seeking permission? If you are interested in obtaining permission to use MovieLens datasets, please first read the terms of use that are included in the README file. Then, contact us, including a description of how you will (a) use the datasets, (b) redistribute the datasets, and (c) provide attribution.  We typically do not permit public redistribution (see Kaggle for an alternative download location if you are concerned about availability).

OK. Then we don't support it for now.


Add support for TSUN Titan inverter

The TSUN titan inverter having a SNR starting with Y17, seems to use the solarman V5 protocol like the GEN3PLUS series. They also enforce SSL, so that we must use the client mode.
By polling the MODBUS register, we get an unexpected response:
'2024-08-12 11:30:21  INFO |  msg | <   Ctl: 0x4510 Msg: 'msg_command_req''
'2024-08-12 11:30:21 DEBUG | tracer | Send Modbus Command:('<IP_ADDRESS>', 8899):
  0000 | a5 17 00 10 45 42 51 ?? ?? ?? ?? 02 **b0 02** 00 00  | ....EBQF=.|.....
  0010 | 00 00 00 00 00 00 00 00 00 00 01 03 30 00 00 30  | ............0..0
  0020 | 4a de 05 15                                      | J...'
'2024-08-12 11:30:26  INFO |  msg | <   Ctl: 0x4510 Msg: 'msg_command_req''
'2024-08-12 11:30:26 DEBUG | tracer | Send Modbus Retrans:('<IP_ADDRESS>, 8899):
  0000 | a5 17 00 10 45 43 51 ?? ?? ?? ?? 02 **b0 02** 00 00  | ....ECQF=.|.....
  0010 | 00 00 00 00 00 00 00 00 00 00 01 03 30 00 00 30  | ............0..0
  0020 | 4a de 06 15                                      | J...'
'2024-08-12 11:30:27 DEBUG | tracer | Received from ('<IP_ADDRESS>', 8899):
  0000 | a5 10 00 10 15 42 52 ?? ?? ?? ?? 02 01 27 92 0f  | .....BRF=.|..'..
  0010 | 00 6e 05 00 00 5b 8a aa 66 **05 00** c7 15

You can see some anomalies:

The first MODBUS request isn't answered and we send a second one after 5 seconds. Maybe the timeout is too short?
Maybe we use the wrong SensorType number,  0x02b0. (bold in log)  which is fine for GEN3PLUS
we got a (MODBUS?) response with 0x05 0x00, which is not a standard MODBUS response or exception

Update:

The timeout was to short for the error handling, since the error reply come after 6 seconds and our timeout was 5 seconds
adapting the SensorType number don't help. It seems for me that this number will be ignored by the inverter in a MODBUS request
With a invalid register range, I can reproduce the error response even on a GEN3PLUS inverter. That makes sense since the register layout of the GEN3 and GEN3PLUS inverters are only suitable for inverters with up to 4 inputs. The TITAN inverter have 6 inputs, so the need a different register layout.


How / Where to find latest version of templates?

  The landscape is moving quickly, and I understand all files cannot always be up to date, but I always have trouble knowing where to get the latest template.  Specifically for the Angular25Spa template.  There seem to be at least 3 possible places:

ASP .NET Core Template Pack Extension - this doesn't appear to work with VS 2017, so this looks like a dead end at the moment for obtaining the latest template that works with the VS2017 project file.
Yeoman generator - at command line, type yo aspnetcore-spa.  I did this today and I got a template that still has project.json file and no csproj file.
Clone the GitHub repo.  This seems to be the place to get the very latest, as the templates\Angular25Spa folder has a .csproj file, and no project.json / xproj files.

So I guess I'm trying to understand how/where yeoman pulls its source from, if not from the latest version in the repo?   The readme in the repo suggests to use the generator to get the templates.
And when might the VS2017 extension for templates be ready for the AngularSpa app?
Thanks Steve for all your work on this.  We are using this template on a big project and are very happy with it so far.  Just a little frustrating to keep up with all the moving pieces.

As my understanding, VS2017 does not need project.json any more.

Yes I realize that, thank you. That was my point.  The template that still has project.json is clearly out of date.

@rgamage What version are you using, the older version eg. 0.8.2 would you give you a choice of project.json or .csproj
eg.

Whereas the latest version 0.9.0 https://www.npmjs.com/package/generator-aspnetcore-spa just goes straight to .csproj

Understood it's not always clear where the latest stuff is.
You're right that the ASP.NET Core Template Pack Extension is well behind. I'm going to try to get the Angular template removed from that extension, because it's not really needed now we have clean dotnet new support, and it's never going to be as up-to-date.
The other two options - Yeoman and dotnet new - are both continually up-to-date in their underlying package managers. In both cases it's up to you when you upgrade your Yeoman/dotnet new packages locally. And as @flightlevel points out, dotnet new has supported csproj for a while, and in fact that's the only option as of 0.9.0 since project.json is deprecated.


Timex.shift/2 fails for datetimes close to DST change

Steps to reproduce
iex(1)> Timex.shift(Timex.to_datetime(~N[2019-03-31T00:29:55], "Europe/Prague"), hours: 2)
{:error, {:could_not_resolve_timezone, "Europe/Prague",<PHONE_NUMBER>5, :wall}}

This is because ~N[2019-03-31T02:29:55] doesn't exist in Europe/Prague tz, it's a DST change when at 2AM the time is changed to 3AM. However, I was under the impression that shift is supposed to skip these DST changes. Actually, the docs mention this should work, as per the example here: https://hexdocs.pm/timex/Timex.html#shift/2-shifting-across-timezone-changes
Is this expected behaviour or am I missing something? Is there an alternative shift method to skip over DST changes?

Well, it turns out I was running older version of timex so I upgraded to latest and the example above now works. However, my code still crashes but now at even weirder situation.
Added the following test to shift_test.exs in timex and it fails there too.
  test "shift should skip over DST time changes" do
    date = Timex.shift(Timex.to_datetime(~N[2019-03-31 04:29:55], "Europe/Prague"), hours: 1)
    expected = ~N[2019-03-31T05:29:55] |> Timex.to_datetime("Europe/Prague")
    assert date == expected
  end

Don't see any reason why it should fail, so I'd assume this is a bug.

Tracked it down to the following calls
Timex.timezone("Europe/Prague", Timex.to_datetime(~N[2019-03-31 04:29:55], "Europe/Prague"))

Timex.Timezone.resolve("Europe/Prague",<PHONE_NUMBER>5)

and finally
Tzdata.periods_for_time("Europe/Prague",<PHONE_NUMBER>5, :wall)

Likely the same as https://github.com/bitwalker/timex/issues/514 and https://github.com/bitwalker/timex/issues/491

Fixed in master

Thank you!


CLOUDSTACK-9812:Update "updatePortForwardingRule" pi to include additional parameter to update the end port in case of port range

Configure a PF rule Private port : Start port ; 20 ENd POrt 25 || Public Port : Start port 20 ; ENd Port : 25.
Trigger UpdatePortForwardingRule api
ApI fails with following error : " Unable to update the private port of port forwarding rule as the rule has port range "
Solution-
Port range gets modified

@mrunalinikankariya One of the commits is not related to the issue

Can see two cmmits in same card. so


Implementing support for WonderSwan roatations in an .avsi by letterboxing.

New script information comes from this page.
All naming used will be under the unnamed thing I've called it.
On the .avsi file adding this below the default multi-segment should work.
# Multisegment AVI import (Letterbox)
function AppendSegmentLetterbox(
\   clip sample,
\ string base,
\    int target_width,
\    int target_height,
\    int first_val,
\    int last_val,
\ string format,
\ string pix_type
\){
    filename = base + string(first_val, format) + ".avi"
    result = AviSource(filename, pixel_type=pix_type)
    xside = int(target_width - result.width) / 2
    yside = int(target_height - result.height) / 2
    result = result.AddBorders(xside,yside,xside,yside)
    return (first_val < last_val) \
        ? result + sample.AppendSegmentLetterbox(base, target_width, target_height, first_val+1, last_val, format, pix_type) \
        : result
}

On the .avs side of support adding at the start:
CHECKRENAME = true      # enable multisegment import (letterbox)
ms = false           	# enable multisegment import

Since my script was made for avs and not avs+ it doesn't support GScript stuff so putting the first bit into the other bit is more important.
I would put this just before the ms script goes through so it can also disable ms on the complete off chance it was accidentally enabled (and forcing handheld).
WSRENAME = Eval("""
	target_width = 224
	target_height = 224""")

#    Checking for WonderSwan
CHECKRENAME ? Eval("""
    ms = false
    handheld = true
    ((Last.width == 224) && (Last.height == 144)) || \
    ((Last.width == 144) && (Last.height == 224)) ? \
    WSRENAME : false
    """) : false

And then lastly at the ms line changing it after the "resized =" as:
CHECKRENAME ? AppendSegmentLetterbox(ms_base, target_width, target_height, ms_start, ms_end, ms_format, pixelType).ConvertToRGB32() : \
ms ? AppendSegment(ms_base, ms_start, ms_end, ms_format, resizer).ConvertToRGB32() : last

Possibly adding back at line 51 will help for future systems that split dumps on rotation:
target_width = 0
target_height = 0

What I provided was mainly to focus on strictly WonderSwan (and then eventually leaving it open for whatever else has to be interjected).

The queue is very busy right now so this will have to wait.

What if we make the existing MSImport function apply letterboxing instead of resizing? I'm thinking of making it parse all the files to determine the biggest resolution, and then actually importing them all, letterboxed to that resolution.


Add pre-commit hooks

Set up pre-commit hooks for

[ ] Style (black + ruff)
[ ] Clear notebooks output

(please feel free to suggest more)

Some good ones are:

https://github.com/drillan/jupyter-black for autoformatting notebooks, or the better one:
https://github.com/nbQA-dev/nbQA contains both nbqa-black and nbqa-ruff
https://github.com/codespell-project/codespell to catch typos and spelling errors


Optimize get_user_group_values call

This is a small patch that optimizes the calling behavior for get_user_group_values. Instead of querying for the user groups immediately, it will only do so if no other principals could be found and if user_roles has not already been initialized.

Thanks!


Migrate to dart:js_interop

Is your feature request related to a problem? Please describe.
dart:js and package:js are deprecated by Flutter. https://docs.flutter.dev/platform-integration/web/wasm
Describe the solution you'd like
Migrate to dart:js_interop where js is currently used.
https://github.com/search?q=repo%3Afzyzcjy%2Fflutter_rust_bridge package%3Ajs&type=code

Totally agree! Will do that after https://github.com/fzyzcjy/flutter_rust_bridge/issues/1903


ci: migrate upload steps

This PR migrates upload-artifact github action from v3 to v4
Manual backport of #30443

/test-backport-1.12


Fix to issue #158

A simple solution attempt: Modified RulesEngine#getParameters to use the clone() method and return a copy of the parameters object. I'm not sure if a shallow copy is enough, but perhaps others can build on this.

Coverage decreased (-0.3%) to 88.948% when pulling 4ae7be937cebdfdbac0b1c633b58645976889aba on Tap-Ant:master into 34328ab1aab1448e0f7c2efb25bef7bb1de4687c on j-easy:master.

Hi @Tap-Ant
Thank you for the PR!
I'm not sure we need to make RulesEngineParameter implement Clonable and change the API to throw a CloneNotSupportedException. A simple copy of the parameters should be enough. Something like the following in AbstractRulesEngine:
    @Override
    public RulesEngineParameters getParameters() {
        return new RulesEngineParameters(parameters.isSkipOnFirstAppliedRule(), parameters.isSkipOnFirstFailedRule(), parameters.isSkipOnFirstNonTriggeredRule(), parameters.getPriorityThreshold());
    }

WDYT? If you agree, please update the PR accordingly and add a test and the PR will be ready to be merged. Please don't hesitate to add your name to the contributors list in the readme!
Thank you upfront.

Hi @Tap-Ant ,

I'm not sure we need to make RulesEngineParameter implement Clonable and change the API to throw a CloneNotSupportedException. A simple copy of the parameters should be enough.

Fixed with b3ba58c7ec43bebc392f4d5a3522bdb325b3d39e.
Thank you for your PR anyway!


Fix systemctl commands

Proposed changes
Updated systemctl commands as they do not work

I think this is a duplicate of #1523. Thanks for reporting it!


docs: draft for plugin support with declarative config

on #2155
Summary of changes
I have worked out a draft to document the plugin support features in setuptools that covers the following:

overview on making plugin for setuptools
how to register commands (declarative and setup script)
how to obtain parameters from the user's setup configuration (declarative and setup script)

Note that

the declarative style documented here uses the setup.cfg file and I haven't figured out how to do this with pyproject.toml
I have yet to test the examples given or make them self-contained
It doesn't explain how things work under the hood since I feel that should be in a separate document (e.g. developer guide)

If this seems to be on the right track I'll be happy to finalize it:)
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in changelog.d. See documentation for details

I might have misunderstood ticket #2155 or confused about the related context. Are the plugins we intend to describe best practice for not the ones I have documented in this file? Thanks in advance for clarifying that:)

I might have misunderstood ticket #2155 or confused about the related context. Are the plugins we intend to describe best practice for not the ones I have documented in this file? Thanks in advance for clarifying that:)

#2155 mentions #1055, wherein a new entry point (setuptools.finalize_distribution_options) in #1877 was added. The purpose of #2155 is to ensure that behavior is featured prominently as part of the command plugin functionality. I didn't realize that maybe command extensions wasn't already documented.
Ultimately, what #2155 is asking is to capture that setup_keywords is discouraged in favor of setuptools.finalize_distribution_options hooks that set values from configuration files.

I do apologize. The guidance in #2155 was pretty bad, and even as I'm reading it, I'm unsure what additional effort that ticket entailed. For now, I'm going to decline this PR and close #2155, as what's in master now is adequate.


Orchestrator Change Paper Preview showing too many changes

Peter as discussed, I removed this details from #525.
I didn't tick the "include data set definitions" box and these are the results for the Test Branch and CR8000.
They both have lots of extra content.
This extra content is not linked to the August 2024 release.
CR8000 - National Eye Colour Data Set Version 1.docx
Test branch.docx

I have found the cause of the problem. Your branch and the latest released branch contain minor text differences in descriptions of items. This differences should not matter because they are just whitespace differences in the HTML content. As a cut down example, consider:
Your branch:

This is a link

Latest release branch:

   This is a    link

Browsers would consider this content to be the same because the content matches. The only difference is the additional whitespace, this is producing false positives.
I have created this issue for tracking:

MauroDataMapper-NHSD/mdm-plugin-nhs-data-dictionary#114

Thanks @pjmonks - we haven't touched the majority of the items so it is strange that this is happening.

This issue has been fixed and deployed to TEST, TRAINING and LIVE. Please move this to the "Ready for NHS E Testing" state.

To test, run through the scenario you originally described and check that the correct changes are now appearing.

@KatePalmerLilley - I think this is now happening as the CRs we created have not been merged with the August release. Do we do this as a test of merging?
CR8008 which I created today doesn't have extra content. It just has the data set issue, #551


[Composer] names of the entity is not matching

Currently the name of the relation are being used as titles, it should the actual name of the entity.

https://inmanta.slack.com/archives/C045Y42N49W/p1709821275380819

we are using the name of the relation as the title, instead of the name of the entity. Could be added with annotations. @bartv needs to take a better look at it.


word mix-up

I believe destructured is the correct word here.

This PR does not affect the produced WebAssembly code.

Destructuring assignment is a specialized term in JavaScript and PHP
documentation, however I am not familiar with how things are represented in
other languages.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment
https://www.php.net/manual/en/migration71.new-features.php#migration71.new-features.symmetric-array-destructuring
On Mon, Jun 21, 2021 at 7:15 AM Claudio Russo @.***>
wrote:

@.**** commented on this pull request.
I actually prefer deconstructed since destructuring implies destruction of
the original value (which is not the case).
@rossberg https://github.com/rossberg?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dfinity/motoko/pull/2610#pullrequestreview-688305990,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADZBJWGE2TJD6YHFFYHCTJTTT4NOPANCNFSM467KHM2Q
.

"Destructuring" is the established term in a number of communities, so I'm fine with using it.

Superseeded by #2620


Add support for styles on radiobutton wrapper and clarify documentation

I wanted to create a grid layout with set widths on the radio buttons, but due to a missing style attribute on the RadioButton's wrapper Views, I couldn't.
This fixes that missing style attribute and documents it.
This also adds documentation clarification requested in https://github.com/moschan/react-native-simple-radio-button/issues/60

Thanks @joshbroton

bumped 2.6.2 👍


fix insert cell menus change cursor #2312

new css class new-cell-menu-item has been added

cursor is still text caret on the last item "Other languages..."

:+1:


Renaming repository to nuxt/nuxt2

As we introduced Nuxt 3 in nuxt/framework, it makes sense to give this repo a more sensible name to avoid confusion. nuxt2 was decided after discussing with @Atinux.
Considerations: Although GitHub should nicely handle most of the rewrites, we have to ensure it doesn't break any dependent projects that were using nuxt/nuxt.js.
Please mention if you have any concerns. Give this issue a few days before making action.

We are going to merge framework to current repo


Talk Questions

(Questions paraphrased from memory as I forgot to record talk)

@lukasheinrich: Why do we need a build system? Why is

https://github.com/matthewfeickert-talks/talk-odsl-forum-seminar-2023/blob/5fe405662f941d64d2caf468e1c99514dbcc4efb/examples/simple_packaging/pyproject.toml#L1-L6
required vs. the build information be automatically discovered? What do these 11 build systems get us that setuptools didn't?

Someone (sorry, forgot who): Are lock files system independent? Do we want to distribute lock files in version control, or should we just distribute pyproject.toml?

@nhartman94: If we want to make our science reusable, how do we determine when we should be distributing a Python package vs. a Linux container image vs. just a repository with code?

Seriously great questions!
Quick parapharsing of answers:

Why do we need a build system? Why is

https://github.com/matthewfeickert-talks/talk-odsl-forum-seminar-2023/blob/5fe405662f941d64d2caf468e1c99514dbcc4efb/examples/simple_packaging/pyproject.toml#L1-L6
required vs. the build information be automatically discovered? What do these 11 build systems get us that setuptools didn't?

We've always had a build system, it is just that before with setuptools + distuitls, distuitls (now deprecated) was the build backend that was kept hidden from most people until you had to hook into it.
pyproject.toml can't be blank as it is the only place that build system information shows up, so there is no information that it could have used to figure out what was needed.

https://github.com/matthewfeickert-talks/talk-odsl-forum-seminar-2023/blob/5fe405662f941d64d2caf468e1c99514dbcc4efb/examples/simple_packaging/pyproject.toml#L1-L6
is maybe written in the reverse order of how one can think about it. build-backend is telling the build frontend system (e.g. build) "this is the system that is going to build the package". As package building takes place in isolated virtual environments by default to ensure correctness, requires is specifying what tools need to be installed in that isolated environment for the build to take place. Example: hatch doesn't exist on your operating sytem level. So if you want to use hatch as your build backend then we need to tell the build system that we require it and to go install hatchling from PyPI to be able to use for the build.

With packaging standards now tools can explore different solutions. setuptools still does everything, but it now isn't required to suppport all of Python. hatch can know this and then not attempt to deal with compiled extensions and focus on making pure-Python packaging as easy, extensible, and fast as possible. scikit-build-core can use this to have you write the minimal amount of code possible and still get a complicated project pacakged. This

https://github.com/matthewfeickert-talks/talk-odsl-forum-seminar-2023/blob/5fe405662f941d64d2caf468e1c99514dbcc4efb/examples/compiled_packaging/pyproject.toml#L1-L6
is the only information that scikit-build-core had, and it was able to build the C++ and package it for us. With setuptools you would need to write a lot more code.

Are lock files system independent? Do we want to distribute lock files in version control, or should we just distribute pyproject.toml?

Lock files are somewhat system independet. A pip focused lock file is only going to be able to describe the packages at the hash level, and so there is no way to be able to describe what version of Python is required to have installed as well (though this information does get put into the lock file, but only as human readable information). Though all available hashes for that solve do get included, so the lock file can be OS independent. For a conda focused lock file, as you have a general purpose package manager you can now specify thing like the Python version that is required as well and that can get fully described at the hash level acorss OS and platform.

If we want to make our science reusable, how do we determine when we should be distributing a Python package vs. a Linux container image vs. just a repository with code?

Just repo and code: If your computing environment is already set (and somewhat outside of your control) and you are shipping only the source code (e.g. running analysis code in the ATLAS Athena framework) then you don't have much ability to even try to distribute your code as a package. Your code is getting consumed by the framework, and as trying to distribute the framework as part of the code is infeasible you make it clear what version of the framework was used.
Linux container image: Complete presevation. Also have the ability to start with a computing environment that is traditionally thought of as not something to "package" (e.g. ATLAS AnalysisBase) and then install a Python package on top of that during a Docker build and then distribute the base image + package that depends on it as a new image on a Linux container registry (e.g Docker Hub, CERN Harbor)
Python package: If the code is sufficiently standalone and general purpose. For lots of projects this is viable. Examples: Analysis tools (awkward, hist, pyhf), machine learning frameworks (jax, torch), more scoped scientific tools (EnergyFlow, eventIsotropy).


fix spell errors fixes query profile docs

Proposed changes
spell errors fixes for query profile doc
ref: #28437

run buildall


BUG STILL EXISTS - module 'time' has no attribute 'clock' in v2.38.0

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
after first running login successfully, any subsequent command produces the error "module 'time' has no attribute 'clock'" in v2.38.0
File "/venv/lib/python3.9/site-packages/azure/cli/core/_session.py", line 46, in load
if st.st_mtime + max_age < time.clock():
AttributeError: module 'time' has no attribute 'clock'
for example: after running login successfully, running 'account list' will yield the above error.
I have opened the file in the image: /venv/lib/python3.9/site-packages/azure/cli/core/_session.py
and have verified that "< time.clock()" still exists in the code
I have monkey patched the line of code to read:
if st.st_mtime + max_age < time.time()
and it now produces the expected results
login
account list
Describe the bug
time.clock() for python has been long depreciated, yet a reference to the command remains in the azure-cli image
To Reproduce
az_cli(f"login -u {azcliuser} -p {azclipass}")
az_cli(f"account list")
Expected behavior
a list of accounts for the user logging in
Environment summary
ubuntu20.04
python3.9
azure-cli 2.38.0
running in kuberbentes as a container image

Additional context

@jiasli for awareness

Please see https://github.com/Azure/azure-cli/issues/19504#issuecomment-915869524
AttributeError: module 'time' has no attribute 'clock' has long been fixed by azure-cli-2.0.77 (https://github.com/Azure/azure-cli/pull/10777). The current code is:
https://github.com/Azure/azure-cli/blob/fa307d6fdfea663e64977c4bbf8a3dbee5d97753/src/azure-cli-core/azure/cli/core/_session.py#L35
I highly doubt your az_cli is not calling the latest Azure CLI

Thank you... I verified that the requirements.txt file was not locked on a previous version... moved the presence of the azure-cli to the top of the requirements file, and it moved the installed version from 2.0.67 to 2.38.0.
Thank you for pointing me towards the incorrect version.
this can be closed as I believe a dependency in the installation order was driving the installation of the incorrect version.


Enhancement: return the only remote when there is only one

as title and added various fall backs when the integrated remote cannot be determined

Looks good to me - thanks again!


chore: Move from cargo-watch to bacon

chore: Move from cargo-watch to bacon
What

Closes #195 by moving cargo-watch to bacon, the tool blessed by the creator of cargo-watch
Slightly changes the developer experience. The console output isn't as pretty for the pnpm commands, and bacon completely takes over the terminal while running. All of it seems to work the same, although I'd appreciate a bit of testing from someone with more experience working on Isograph before it goes in!
Updated the documentation to encourage developers to install bacon

How

Wrote down what the flags all did in cargo-watch:

-x means command to execute on change
-d is file update debounce time in seconds (does not have bacon equivalent)
-w is watch directory
-s is shell command to execute on change (does not have flag equivalent, jobs are defined in bacon.toml)

Found matching ones (where the existed) in bacon:

-j is job to launch (rough equivalent of -x and -s)
-p is path to watch (equivalent of -w)

Generated the bacon.toml with bacon --init

Added the build and watch-libs jobs to capture the same functionality as pnpm run watch-rs and pnpm run watch-libs. There is no native build command for bacon (it just has check) and they recommended making a custom job

Updated the commands in package.json

FWIW my testing involved running it and seeing that the behavior matched what is described in https://dystroy.org/bacon/ :-D


Lucia Auth Migration

Overview
Changes Made:
We have successfully transitioned from Next-Auth to Lucia Auth for our authentication system.
Details:

Implemented GitHub and Credentials authentication using Lucia Auth.
Introduced a separate authentication database to enhance authentication processes.
Lucia Auth has been integrated as a remote Hasura schema, facilitating user management through email or provider links.

Authentication Database Overview:
Our new authentication database comprises the following tables:

auth_user: Houses user information.
user_key: Manages user keys for various authentication methods (e.g., GitHub, Google, LinkedIn).
user_session: Enables users to maintain sessions across different devices and tabs.

Each user is required to have a primary key, which corresponds to their preferred authentication method. Users also have the option to sign up using alternative methods, promoting flexibility in user authentication.
Remaining Tasks:
While the migration and integration of Lucia Auth have been successfully executed, there are a few pending tasks that need our attention:

Ensuring proper redirection of users to relevant routes following authentication operations.
Implementing redirects to the onboarding page for first-time users.
Enhancing the user experience and user interface of the authentication process.

I think working on #43 should be the next step!


Add WatchRegistration function

The library only provided WatchInstance function that returned a watch of child type that was not triggered by group member subscription updates, so WatchRegistration function was introduced to allow watching member subscription updates.
Besides a redundant call for Exists was removed in a couple of methods. It is ok to just make whatever call we need and check for ErrNoNode error.

@wvanbergen I am not sure if you still maintain this, but if so please take a look.

Looks good, thanks for contributing!


Should notify when build fails

See original issue on GitLab
In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on May 1, 2018, 21:27
Fedora has patched gnome-terminal to present a desktop notification when a command has completed. When I used JHBuild, I always received a notification immediately after my build succeeded or failed, so I could take appropriate action. I relied on this for productivity.
With BuildStream, there is no notification when the build fails. (I think there is a notification when it succeeds.) I'm absentminded and find that I often do not notice a build has failed until much later, sometimes hours later. Since BuildStream presents its own failure prompt to allow the user to choose what action to take, perhaps BuildStream should manually create notifications. But there's a difficultly here: notifying would be undesirable if BuildStream is running in a currently-focused terminal. So maybe integration with gnome-terminal, and investigation of how exactly the terminal notifications work, will be required. Debarshi Ray is the expert on this.

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on May 1, 2018, 23:47
changed title from Should notify when build {-complete-}s to Should notify when build {+fail+}s

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on May 1, 2018, 23:47
changed the description

In GitLab by [Gitlab user @valentindavid] on May 3, 2018, 11:23
mentioned in commit 1a7fa79317f7e90be7b2abc6bf2bd23a00cbf672

In GitLab by [Gitlab user @valentindavid] on May 3, 2018, 11:24
mentioned in merge request !447

In GitLab by [Gitlab user @valentindavid] on May 3, 2018, 11:24
I have create !447. Tell me if this what you want.

In GitLab by [Gitlab user @valentindavid] on May 3, 2018, 11:46
mentioned in commit d0add42f481547dc11f94e567f05dd49f5c66612

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on May 3, 2018, 18:10

I have create !447. Tell me if this what you want.

I think so, thanks!

In GitLab by [Gitlab user @tristanvb] on May 4, 2018, 06:15
There shalt be no terminal, desktop, or even OS specific code being added directly BuildStream - yes that means even with an if clause.
An option for this which, which I had discussed with [Gitlab user @TheRealMichaelCatanzaro] on irc but failed to update / close this issue, is to have this done with a user specific event hook after implementing #188.
A different option would be to implement some concept of extensions or platform specific frondends, but we are not going to start adding if statements for special features in the core, that wont happen.
Instead of WONTFIX'ing this issue, I feel it's more appropriate to leave it open until #188 is fixed in such a way which allows addressing this.

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on May 16, 2018, 15:39

There shalt be no terminal, desktop, or even OS specific code being added directly BuildStream - yes that means even with an if clause.

I think it's very important to find some solution to this, because I'm losing hours. It's nice to avoid hacks when possible, but please consider this a critical issue.

In GitLab by [Gitlab user @tristanvb] on May 17, 2018, 06:50
mentioned in commit e023beb56b180316a58f409d48f158e9dc1ece95

In GitLab by [Gitlab user @tristanvb] on May 17, 2018, 06:50
mentioned in merge request !467

In GitLab by [Gitlab user @tristanvb] on May 17, 2018, 07:30
closed via merge request !467

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on Aug 15, 2018, 00:29
Reopening. I'm testing with buildstream 1.1.6 today, and this isn't working.

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on Aug 15, 2018, 00:29
reopened

In GitLab by [Gitlab user @tristanvb] on Aug 15, 2018, 07:34
Hmmm, according to the python docs, we are detecting the linux platform in the correct way:
https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/_frontend/app.py#L138
And, we emit the custom notification in the case that the TERM environment is either xterm or vte:
https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/_frontend/linuxapp.py#L29
I don't run fedora so I don't really have an easy way to test this notification.
Another point, is that apparently this is only implemented when there is a failed build and a prompt appears; I think it would probably make sense to issue a frontend notification at the end of a build.
[Gitlab user @TheRealMichaelCatanzaro], does the code appear to be doing the right things to you ? and maybe did you expect a notification at end of build which didn't happen ?

In GitLab by [Gitlab user @valentindavid] on Aug 15, 2018, 09:15
My TERM is set to "xterm-256color".

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on Aug 15, 2018, 17:37

[Gitlab user @TheRealMichaelCatanzaro], does the code appear to be doing the right things to you ? and maybe did you expect a notification at end of build which didn't happen ?

I've never seen a notification at the end of a BuildStream build.
Certainly, I want a notification whether the build succeeded or failed.
It would be useful to always get a notification when the terminal tab is not focused (including not on the current workspace... but I don't think it's even possible for a Wayland client to know what workspace it is on!)... that does pretty much require integration with the terminal, which is sadly only available in Fedora right now.
The next best thing would be for BuildStream to unconditionally emit the notification when the build finishes. That might be annoying as I don't need the notification if the build finishes when I'm watching the terminal, but seems like that's the best we can do if it's to be available on all distros. It could be turned off via a config file for developers who don't like it.

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on Aug 15, 2018, 18:59

I've never seen a notification at the end of a BuildStream build.

Well, let me rephrase that: I don't remember ever seeing a notification at the end of a BuildStream build. I reserve the right to be misremembering here. ;)
Only the cases where there is no notification are memorable, because they are frustrating.

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 08:55
mentioned in commit 5d8f6b66f22f5cd15bd18577e32d1fc5e78604c4

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 08:56
mentioned in merge request !672

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 08:57
mentioned in commit 2749294d4faeeb5627df477feea0bc0bce19924d

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 08:58
mentioned in merge request !673

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 09:52
mentioned in commit b3e2c1c4b147aedde626f230134c474b477d30c1

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 09:53
mentioned in commit 52e2f0545b55c36ac0826ddd164bdb140ee4d4af

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 09:57
mentioned in commit 72c60cf70659d495c275142cf668c14115ada8d7

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 15:26
mentioned in commit 369cbb481708a0219101fecdc482b8e1f91bf97d

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 15:26
mentioned in commit 72ad0a8de552334cec7834606e47e89c9e8b161b

In GitLab by [Gitlab user @tristanvb] on Aug 16, 2018, 15:38
mentioned in commit 1e140f7d0ae1228b30154aeb87022e5d188cca9b

In GitLab by [Gitlab user @tristanvb] on Aug 17, 2018, 07:20
mentioned in commit 10f27f3f84dcbf03328193f5ae573f41bc74da01

In GitLab by [Gitlab user @tristanvb] on Aug 17, 2018, 09:52
closed via merge request !672

In GitLab by [Gitlab user @tristanvb] on Aug 17, 2018, 09:52
mentioned in commit c102b92fe4a3f1c71a77629a57a9838b83ee19b8

In GitLab by [Gitlab user @tristanvb] on Aug 17, 2018, 10:35
This should be fixed by !672 and !673.
Reopening for verification, we need to know that this worked on a fedora workstation...
[Gitlab user @TheRealMichaelCatanzaro]: Could you also tell us what your TERM environment variable is set to, please ?

In GitLab by [Gitlab user @tristanvb] on Aug 17, 2018, 10:35
reopened

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on Aug 17, 2018, 14:49
I will test it, thanks.

Could you also tell us what your TERM environment variable is set to, please ?

xterm-256color

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on Aug 17, 2018, 15:59

I will test it, thanks.

Doesn't work.

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on Aug 17, 2018, 16:10
Possible solutions:

Try to do this in a distro-independent way, so everyone benefits
Test in a Fedora VM

In GitLab by [Gitlab user @tristanvb] on Aug 21, 2018, 14:44
mentioned in commit 1be685a7f3a8e0e01a2fd18e1efcee0393abd8f8

In GitLab by [Gitlab user @tristanvb] on Aug 21, 2018, 14:44
mentioned in commit aa9f8eb97c59e990e230862de062e12cc646feea

In GitLab by [Gitlab user @tristanvb] on Aug 21, 2018, 14:45
mentioned in merge request !692

In GitLab by [Gitlab user @tristanvb] on Aug 21, 2018, 14:45
mentioned in merge request !693

In GitLab by [Gitlab user @tristanvb] on Aug 21, 2018, 16:10
mentioned in commit be964b1e1464c442c7bbb010b3ac058f754fa0b1

In GitLab by [Gitlab user @tristanvb] on Aug 22, 2018, 05:54
mentioned in commit e575fac087ed4d8ee5f4605615604030583d5449

In GitLab by [Gitlab user @tristanvb] on Aug 22, 2018, 06:25
mentioned in commit 3d4e649df8acffe3abbd27f393ef1cc981ea2580

In GitLab by [Gitlab user @tristanvb] on Aug 22, 2018, 07:24
closed via merge request !692

In GitLab by [Gitlab user @tristanvb] on Aug 22, 2018, 07:24
mentioned in commit c8bafb687e1ac2c2692f69c0e6f0bb80a2cb7565

In GitLab by [Gitlab user @tristanvb] on Aug 22, 2018, 08:35
[Gitlab user @TheRealMichaelCatanzaro]: So this should really be fixed now in both master and bst-1.2 (users should be on bst-1.2 for a while, I cannot recommend testing master for a while, we are working on making this story more clear presently).
For this issue, we still lack CI which allows testing the interactive parts of BuildStream, but I have:

Downloaded a Fedora 28 VM
Verified that the magick OSC 777 escape code does indeed work in a default terminal in recent Fedora

Note that there is a little bit of wonkiness, at the end of a session; we now trigger the notification of success or failure, in addition to notifying the user when a build fails and there is an interactive prompt.
This is only "wonky" because Fedora, in addition to supporting the OSC 777 in vte which was rejected upstream; also notifies the user when any terminal command completes with the window out of focus. The result appears to be just that the second; hard coded notification in Fedora just overwrites the one we attempt to issue with the OSC 777 escape sequence.
This appears to me to be the right thing; we should make an attempt to notify that the session completed, and if a desktop has additional hard coded notifications; that should not be our concern.

Further, after finding that OSC 777 issues garbage on my terminal; I have made it currently only enabled where:

The terminal uses VTE
The VTE_VERSION >= 4600. This is because we know that a version of VTE that is >= 4600 will at least safely swallow and ignore the non standard escape sequence, so garbage cannot end up on your terminal. For versions of Fedora or other desktops which patch VTE >= 4600 to enable the feature, this will "just work".

It is possible to enable the notification in other terminals, but I consider that separate activities of research and testing.

In GitLab by [Gitlab user @TheRealMichaelCatanzaro] on Nov 16, 2018, 00:54
I know this is late, but:
It's working! :)


mention that SST is called tos in the model

Just figuring things out

@mythicalmothboy Thanks for getting involved with Foundations!
It looks like this PR is just a test, not for merging. Is that correct?
As you've seen here, this repository has an automated system for assigning reviewers to PRs. For work in progress, or just playing around with something isn't meant for review and merging, you can use "Draft Pull Request" mode. That will still generate the full preview but will not assign reviewers.
Let us know if you have questions!


Merge v0.33.1 fixes to master branch

Before submitting
Please complete the following checklist when submitting a PR:

[x] All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests directory!

[x] All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running make docs.

[x] Ensure that the test suite passes, by running make test.

[x] Add a new entry to the .github/CHANGELOG.md file, summarizing the
change, and including a link back to the PR.

[x] Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context: This PR adds #543 changes to master.
Description of the Change:
Benefits:
Possible Drawbacks:
Related GitHub Issues:

Do we want to add multigpu-ci tag and let codecov pass?


benchmark doc and code out of data

doc under Anakin/benchmark/README_CPU.md is out of data.
Three links of models points to 404 page
Those links in Anakin/benchmark/RNN/prepare.sh are also invalid.

Anakin has updates the benchmark in the root README.md, and will push to the Github very soon.


Multiple scope login

Hi,
I have used devise gem in my rails 3 app.
gem 'devise', :git => "https://github.com/plataformatec/devise.git", :ref => ef28bf28140001745e6ec67ba0620864ef4b1350"

In my rails app I have 3 type of user, 1) manager, 2) admin and 3) User.
I have created three seperate models for user, manager and admin as per requirement.
we have 3 routes for each login:
user:           /users/login
manager:   /managers/login
admin:       /admin /login

In my rails 3 app when I access user login page and put the credentials of admin or manager then with my current code(gist url below) I am login with admin or manager whoever credentials I entered and vise-versa.
https://gist.github.com/Ramkrishan/7e9a9c6da04234921566

I have upgrade rails with 4.2.1 and using devise gem devise 3.5.1 with using same controller code is not working fine. also tried with old devise version with the new rails 4.2.1 but also not working fine. I am not able to login with admin using users route getting following logs.
Started POST "/users/sign_in" for <IP_ADDRESS> at 2015-06-08 16:37:48 +0530
Processing by SessionsController#create as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"ldPpNJWF09KcMWFHnn8JIdhmIN9NcvLG2IHNG94w645g7VMZipfId5ZN4Pp2woNZzYyGT1UYJF4B1qJsZcDm7Q=="<EMAIL_ADDRESS>"password"=>"[FILTERED]", "remember_me"=>"0"}, "commit"=>"Sign in"}
User Load (7.2ms)  SELECT  "users".* FROM "users" WHERE "users"."email" = $1 LIMIT 1  [["email"<EMAIL_ADDRESS>Manager Load (2.0ms)  SELECT  "managers".* FROM "managers" WHERE "managers"."email" = $1 LIMIT 1  [["email"<EMAIL_ADDRESS>Admin Load (2.0ms)  SELECT  "admins".* FROM "admins" WHERE "admins"."email" = $1 LIMIT 1  [["email"<EMAIL_ADDRESS>signing in as admin
User Load (5.6ms)  SELECT  "users".* FROM "users" WHERE "users"."email" = $1  ORDER BY "users"."id" ASC LIMIT 1  [["email"<EMAIL_ADDRESS>signed out admin
prepared sign in
before warden auth with {:scope=>:admin, :recall=>"sessions#new"}
Completed 401 Unauthorized in 167ms (ActiveRecord: 30.2ms)

===========================================
I found for the solutions and got that we can use one model user with specific role instead of many models (user, admin and manager) but In my case I need to keep this as it is.
Could you please let me know what is the issue? or what can I need to do to get the feature working fine as before.
Thanks

If your needs require you to sign in using a single route with different "scopes/roles", I'd rather recommend having a single model indeed, it will keep things way simpler.
In any case, please use the mailing list or stack overflow for questions, we reserve the issues tracker for issues. Thanks!


update mapping for anomalydetector

Docs Build status updates of commit 38e5611:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified commit because branch anomalydetector has been deleted or has been force pushed: fatal: Couldn't find remote ref anomalydetector

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


victor-mono: 1.5.2 -> 1.5.3

recreation of NixOS/nixpkgs#176006. Hopefully this will ping only the right people.
Original description below

Description of changes
This PR updates the font Victor Mono to 1.5.3. Release notes here https://github.com/rubjo/victor-mono/releases/tag/v1.5.3
I had to do some modifications to the derivation because I couldn't build it if I just bumped the version number and the sha256 field:

the zip we download does not contain a single directory at the top level so I had to stripRoot = false (not sure why it worked with 1.5.2 because the zip structure is identical :man_shrugging:)
I had a look at the fetchzip function in this repo and saw that it automatically unzips the file and then deletes it, so I replaced the double-unzip from the script with cp otherwise it would fails with a "file not found" error (again, this doesn't seem like a recent change in behaviour for fetchzip so I'm at a loss why the derivation for 1.5.2 was building before)

I wasn't sure against which branch to open this PR. The Contribution manual mentions starting branches from my current nixos channel (22.05) so I opened a PR back to nixos-22.05.
Please let me know if I've done something wrong or opened this PR against the wrong branch :)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

hey @jpotier thanks for the review. I have pushed a new commit that keeps only LICENSE.txt and the share/ folder and rebased the PR on top of master.

hey @jpotier, any chance you could have another look at this PR? Even if you don't want to merge it, I'd like to understand why the build on 1.5.2 worked but on 1.5.3 (with the same zip folder structure) didn't.

Thanks for the kind review @jpotier. What are the next steps to getting this merged?

@alexghr Wait for a kind soul with merge status to pick this up. This already happened a few hours ago ! See comment https://github.com/NixOS/nixpkgs/pull/176066#discussion_r906106308, IIRC SuperSandro2000 has merge privilege.


Add multi-version support - no path mapping yet

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix

[x] Feature

[ ] Code style update (formatting, renaming)

[ ] Refactoring (no functional changes, no API changes)

[ ] Build-related changes

[ ] Documentation content changes

[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

Current dependencies on/for this PR:

main

PR #661   👈

This comment was auto-generated by Graphite.


Remove v-html from project labels

Summary
This removes the need to use v-html when displaying project labels by shifting the span tag outside of the translations inside of en-us.yaml and into the vue template.
Areas or cases that should be tested

Listing projects and namespaces.
Before

After

@mantis-toboggan-md @nwmac I've updated this PR to utilize DOMPurify. Can you take another look?


ci(actions): update renovatebot/github-action action to v40.1.5

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
patch
v40.1.3 -> v40.1.5

Release Notes

renovatebot/github-action (renovatebot/github-action)
v40.1.5
Compare Source
Miscellaneous Chores

deps: update dependency @types/node to v20.11.25 (0af5e4e)

Build System

deps: update dependency typescript to v5.4.2 (e3c8e2c)

Continuous Integration

deps: update renovate docker tag to v37.235.5 (b77198b)
deps: update renovate docker tag to v37.236.0 (caabd0f)
deps: update renovate docker tag to v37.240.1 (042c7eb)
deps: update renovate docker tag to v37.241.0 (4c3342e)

v40.1.4
Compare Source
Documentation

update references to ghcr.io/renovatebot/renovate to v37.226.0 (8f48089)
update references to ghcr.io/renovatebot/renovate to v37.235.1 (b7e835a)
update references to renovatebot/github-action to v40.1.3 (ee6b018)

Miscellaneous Chores

deps: update dependency @semantic-release/npm to v11.0.3 (881f6f4)
deps: update dependency @types/node to v20.11.21 (31b5a14)
deps: update dependency @types/node to v20.11.22 (eb51c16)
deps: update dependency @types/node to v20.11.23 (ecd344d)
deps: update dependency @types/node to v20.11.24 (452275a)

Build System

deps: lock file maintenance (7137e4c)

Continuous Integration

deps: update renovate docker tag to v37.226.0 (fb9e670)
deps: update renovate docker tag to v37.226.1 (b4533c9)
deps: update renovate docker tag to v37.227.0 (04ee023)
deps: update renovate docker tag to v37.227.1 (f8545b0)
deps: update renovate docker tag to v37.229.2 (e2bf98f)
deps: update renovate docker tag to v37.229.3 (56a70c2)
deps: update renovate docker tag to v37.229.5 (551e9ba)
deps: update renovate docker tag to v37.230.0 (9df8367)
deps: update renovate docker tag to v37.231.0 (2b8af91)
deps: update renovate docker tag to v37.231.2 (f11deb8)
deps: update renovate docker tag to v37.232.0 (a5aabe1)
deps: update renovate docker tag to v37.233.1 (39b2ab2)
deps: update renovate docker tag to v37.234.1 (66f6b89)
deps: update renovate docker tag to v37.235.1 (0c31356)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.2.13 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Notion: always send an url for a database

Description
pageUrl is nullable on both Notion models (pages & db) but when we upsert the datasource for pages we use pageCacheEntry.url that is always a string.
This PR make sure we always send an url also for dbs: https://github.com/dust-tt/dust/blob/main/connectors/src/connectors/notion/temporal/activities.ts#L1910
I think I would keep it as is and not change the NotionDatabases object in connectors.
WDYT?
Risk

Deploy Plan

I think I would keep it as is and not change the NotionDatabases object in connectors.

SGTM


Rename migration to avoid conflicts

The AddMissingIndexes migration conflicts with migrations in other
gem(s), eg spree 3.1. The name has been made more specific to avoid
such conflicts.
Fixes issue #773

@seuros Hi, is it possible to make a new release 4.0.1 with this PR merged?

@arpitchauhan because file name is changed, rake railties:install:migrations will copy this migration, so we should check if the index exists.

@krzysiek1507 indeed, I will make a new PR with that change.

@arpitchauhan could you add it for all migrations with changed names?

@krzysiek1507 @seuros I created #779
What other migrations have changed names?

@arpitchauhan sorry, I've checked and this is only one. I thought there is more.


Unable to use ctrl+c to kill script while password prompt is active

I'm unable to terminate my python script with ctrl+c while the prompt from pwinput is active.
Which forces me to close the terminal to stop the script.
Seems like a bug?

Hi asweigart,
I have the same problem, that ctrl-c is not raised.
maybe you want to add the ctrl-c keyboard exception stuff to your code?
Best regards, Jens
:
diff --git a/src/pwinput/init.py b/src/pwinput/init.py
index 15d533e..dab9b64 100644
--- a/src/pwinput/init.py
+++ b/src/pwinput/init.py
@@ -92,6 +92,8 @@ def pwinput(prompt='Password: ', mask='*'):
sys.stdout.write('\b \b')  # \b doesn't erase the character, it just moves the cursor back.
sys.stdout.flush()
enteredPassword = enteredPassword[:-1]

   elif key == 3:  # ctrl-c pressed

       raise KeyboardInterrupt
   elif 0 <= key <= 31:
       # Do nothing for unprintable characters.
       # TODO: Handle Esc, F1-F12, arrow keys, home, end, insert, del, pgup, pgdn

I opened a pull request for the patch :)


Fix: Avoid bad rendering of README on npm

Sorry, the last commit did not go through completely.
I tested it with marky-markdown, the problem was that the a tag  was not closed.
I closed it and moved it after the title.
For clarification, I was talking about the html rendering of the README.md file on npm

Huh well.. the a tag was closed...

O_O
Can you file an issue on https://github.com/npm/marky-markdown to tell them they probably should support more than a subset of HTML

http://stackoverflow.com/questions/3558119/are-self-closing-tags-valid-in-html5
I guess you can't self-close an anchor tag... pretty lame.

It looks like the header auto-creates an anchor tag.  Can we link to #projects-using-this-api instead and remove the <a name="projects" /> instead?

@bsansouci  Yep, that's what I realised about anchor tags too...
@Schmavery That's what I wanted to do, but I realised you could have used the link somewhere else apart from github.
I figured it would be better to keep it that way.
However if the README.md is the sole place the #projects is used, yes it can be referenced with #projects-using-this-api.

Let's go with #projects-using-this-api. I'm pretty sure nothing else references it, and if so, it will still point to the same page.

Roger roger.
And done.


Jepsen tests status

Hi.
During the evaluation of different databases one of the major criteria for us is passing Jepsen test suite. Passing Jepsen test suite confirms some confidence level in testing different quite complicated scenarios in distributed systems.
I did not find any mention of passing Jepsen test suite in the documentation. The only material I have found is an article: https://www.arangodb.com/2017/01/reaching-harnessing-consensus-arangodb/ but seems like it is kinda outdated.
My questions are:

What is the current state of Jepsen tests for the database?
Do you plan to invest your time into the Jepsen tests? Maybe your current test suite covers all Jepsen cases (or maybe perform even more checks)?
If the database pass (or not pass) Jepsen test suite, would be awesome if you put this information somewhere into the documentaion. It is really important for the end-users.

Thanks in advance!

Hi, your issue is really strange.
Don't exist some common for all databases jepsen test suite.
It should be written by someone, it can be written incorrect, etc...
If you see Jepsen reports, it's Kyle and other devs commonly not for free, test concrete databases.
We used jepsen framework to test our raft implementation (Agency), but it's probably outdated.
Maybe we will update it sometime.

What is the current state of Jepsen tests for the database?

We don't use Jepsen framework for tests now.

Do you plan to invest your time into the Jepsen tests? Maybe your current test suite covers all Jepsen cases (or maybe perform even more checks)?

As I wrote, no exist some Jepsen cases, exist Jepsen framework, with a lot of fault injection settings, and user can write tests for it.
Maybe sometime we will add it, but in general I don't like Jepsen framework, it's probably intentional written on Closure.
So personally I prefer native frameworks for fault injection, like in FoundationDB for example.
Another work in this direction is https://developers.facebook.com/blog/post/2022/11/22/hermit-deterministic-linux-testing/

Yes, you are right. I mostly meant introducing some tests for fault-tolerance in "Jepsen" style. I have chosen not clear enough description in the start message - my bad. Honestly, as a user, I do not care much about the implementation of fault-tolerance testing of a database - I just want to check that the database has a mature fault-tolerance test suite and is tested for the fault-tolerance on a regular basis.

I understood, sorry but now we only have manual fault injection in our regular tests


More than one Checkpoint

Hi,
Is it possible to add more than one Checkpoint to store different models based on different metric?
e.g.
net = NeuralNet(callbacks=[Checkpoint(monitor=loss_monitor), Checkpoint(monitor=accuracy_monitor)....])

Thank you

Since this is easily possibly and there does not seem to be an issue, I'm closing this.


OpenId auth, client validation failed because 'https://localhost:44364/' was not a valid redirect_uri for app

There is a mismatch between what is stored to db as redirect uri, in my case - ["http://localhost:5000"] and what is then used as comparison value from open id manager, in my case it is https://localhost:44364/ which is the iiSettings ssl port with domain.
Thank you in advance for checking this out.
Lukas

@Vencalekl this issue must have be fixed with some new changes in the project, this is a configurable entry of STS server now in appsettings.json.


TIMEBLOCKS

TIMEBLOCKS
User Story
AS AN employee with a busy schedule
I WANT to add important events to a daily planner
SO THAT I can manage my time effectively
Acceptance Criteria
GIVEN the daily planner
WHEN the timeblock is viewed
THEN each timeblock is colour coded based on past, present and future

GIVEN the daily planner
WHEN the timeblock is viewed
THEN each timeblock is colour coded based on past, present and future


crypto/x509/x509_vpm.c: Simplify int_x509_param_set1()

This patch simplifies int_x509_param_set1() and also makes it not call strlen twice when srclen is 0 (strdup calls strlen).

+1

Ping - anyone?

Merged.


Cannot compile on 1.0.0-alpha.2

Seems like cannot compile on 1.0.0-alpha.2 on OS X 10.10
Here's the stacktrace
/Users/serdar/.cargo/registry/src/github.com-1ecc6299db9ec823/rand-0.2.0/src/lib.rs:240:5: 240:38 error: unresolved import `std::num::wrapping::Wrapping`. Could not find `wrapping` in `std::num`
/Users/serdar/.cargo/registry/src/github.com-1ecc6299db9ec823/rand-0.2.0/src/lib.rs:240 use std::num::wrapping::Wrapping as w;
                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/serdar/.cargo/registry/src/github.com-1ecc6299db9ec823/rand-0.2.0/src/chacha.rs:16:5: 16:39 error: unresolved import `core::num::wrapping::Wrapping`. Could not find `wrapping` in `core::num`
/Users/serdar/.cargo/registry/src/github.com-1ecc6299db9ec823/rand-0.2.0/src/chacha.rs:16 use core::num::wrapping::Wrapping as w;
                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/serdar/.cargo/registry/src/github.com-1ecc6299db9ec823/rand-0.2.0/src/distributions/range.rs:17:5: 17:39 error: unresolved import `core::num::wrapping::Wrapping`. Could not find `wrapping` in `core::num`
/Users/serdar/.cargo/registry/src/github.com-1ecc6299db9ec823/rand-0.2.0/src/distributions/range.rs:17 use core::num::wrapping::Wrapping as w;
                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/serdar/.cargo/registry/src/github.com-1ecc6299db9ec823/rand-0.2.0/src/isaac.rs:18:5: 18:39 error: unresolved import `core::num::wrapping::Wrapping`. Could not find `wrapping` in `core::num`
/Users/serdar/.cargo/registry/src/github.com-1ecc6299db9ec823/rand-0.2.0/src/isaac.rs:18 use core::num::wrapping::Wrapping as w;

Can’t say for sure, but I think the intention is to track the master until 1.0 stable is released. If you’re an alpha2 user, you should restrict your version bound of the library to 0.1.3 for now.

Yes this library tracks the nightly branch for Rust currently asa there are still a number of breaking changes. I would recommend installing a nightly instead of the alpha, and then everything should work out well!


Add download link to fx/cdf/obs pages

Removes dedicated download pages in favor of a "Download Data" link next to the "Set Time Range" button, so users can view data before they download it.
closes #163
closes #144
closes #157
Gives downloaded files a meaningful name, <object name>_<start>_<end>.<type> where type is 'csv' or 'json'.

Did you figure out the import error? how does this do with core master?

Did you figure out the import error? how does this do with core master?

I'll rebase it upon #209 and make sure it's still functioning.

Working well with the new core. The added interfact looks like the screenshot here. The information buttons next to the format radio buttons link out to the format documentation on solarforecastarbiter.org


border-box styling for mobile

We have relied on blueprint css to default all DOM elements to box-sizing: border-box. See here.
Since we're no longer applying blueprint styling to the mobile app, we need to set this property ourselves.

Looks right to me, based on my research, but I have asked tom to look as well...

Looks good to me - will merge


Extension is missing in the Az command

The documentation is missing the extension in the Az command, it should be:
az network front-door waf-policy instead of az network waf-policy
This az command is also wrong:
az network waf-policy custom-rule should be az network front-door waf-policy rule
In the az network front-door waf-policy rule create command we also have the issue that --match-condiction is an unrecognized argument

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 335de4dc-ee21-8fdd-3b11-b32a0027f16e
Version Independent ID: de448dd6-5a47-c9b8-7fc5-92e898f53274
Content: Configure an IP restriction rule with a web application firewall rule for Azure Front Door Service
Content Source: articles/frontdoor/waf-front-door-configure-ip-restriction.md
Service: frontdoor
GitHub Login: @KumudD
Microsoft Alias: kumud

@stuycks Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.
@KumudD it looks like several of the commands and the format of the commands have changed.

@stuycks Thanks for bringing this to our attention. The az commands in the article have been updated.
#please-close


Restore test location reporting in Swift tests

Switch between String and StaticString based on the Xcode version.

Awesome!


[SRS] Add Naming Conventions and Terminology section

Close https://github.com/arkinmodi/project-sayyara/issues/111

Can you add OEM


Correction for raw affiliation Univ Rennes, CHU Rennes, Inserm, CIC-1414, Biostatistics, Rennes, F-35000, France

Correction needed for raw affiliation Univ Rennes, CHU Rennes, Inserm, CIC-1414, Biostatistics, Rennes, F-35000, France
raw_affiliation_name: Univ Rennes, CHU Rennes, Inserm, CIC-1414, Biostatistics, Rennes, F-35000, France
new_rors: 02vjkv261;015m7wh34;05qec5a53;02baj6743
previous_rors: 02vjkv261;015m7wh34;05qec5a53
works_examples: W4322720159
contact: d9c7dfee635202bf4b05a682faba5aca:be4c4f8a9a78bdb9a8bb4bce41b638a3 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Nana aba08

all directories named in lowercase

Weldone @NanaAba08.
This will be merged as soon as possible.


Questions about reproduction of Figure2cd

Hi,
Thank you for publishing such an excellent paper!  I'm trying to reproduce the results of Figure2c and 2d. In the GEARS_misc/paper/Fig2cd.ipynb, I noticed that the color_pal is directly input. Could you please provide any guidance on how to reproduce these data and how could I get the perturbation results for all genes？
Forgive me for my inexperience, thank you and have a nice day!

I apologize for the inconvenience once again. Could you kindly verify whether the data location in this notebook is still accurate? I seem to have encountered some file non-existence problems during operation. May I inquire if it would be possible to communicate with you via email? I eagerly await your response. Thank you very much for your consideration!

Thanks for your question
color_pal in GEARS_misc/paper/Fig2cd.ipynb just refers to the color palette for the figures and is manually set. It does not refer to the experimental results.
To reproduce the results for GEARS on your own, you can follow this notebook
To plot the results you can point it at your own wandb account where the results from your run would be saved. Otherwise the wandb project linked in the notebook could also be used for the Norman dataset but not for the other two. However, it shouldn't take long to manually regenerate the results for adamson2016 and dixit2016 if you follow the notebook


weboob: use stable branch of the weboob repo

Romain from the Weboob team tells me devel tends to be more stable than stable, so I'll just go with this instead.


[Relax][Runtime] RNNState for Space State Models

This commit adds the RNNState class to the Relax VM, similar to the PagedKVCache, for space state models like RWKV and mamba
cc @tqchen @MasterJH5574

Refactored. Now AttentionKVCache and RNNState have the same base class. would be great if @MasterJH5574 @tqchen Can take a look


Transfer labels

From @lfunkhouser on October 2, 2017 15:24
This issue is used to transfer issues to another repo
Copied from original issue: Esri/solutions-grg-widget#119

This issue was moved to Esri/solutions-geoevent-java#78

This issue was moved to ArcGIS/solutions-erg-widget#8

This issue was moved to Esri/military-feature-toolbox#27

This issue was moved to Esri/military-tools-desktop-addins#30


how to enable godhome statue

I was able to create and place a god home statue, but it only shows the base not the statue itself. I assume there is some way to trigger it but I was not able to find anything. Much appreciated for any help on this!

And "is always unlocked"  config doesn't seem to work either

Looks like I need to specific a boss scene to even unlock it (but I can't specific my scene in unity editor somehow

nvm everything works. I took a look at how this is done in ancient aspid.


Fail to compile: ld.lld: error: unable to find library -lstdc++

Hello HIP community. I have a simple Makefile with my HIP program converted by using hifipy-clang tool:
# Define compiler and compiler flags
CXX = g++
HIPCC = hipcc
SRCS = src
HIPCCFLAGS = -O3 -I /usr/include/x86_64-linux-gnu/c++/11 -I /usr/include/c++/11 -L /usr/lib/x86_64-linux-gnu -v
HIPOBJS = main_hip.o fdtd3d_gpu_hip.o fdtd3d_texture_hip.o

all: hip

hip: hip_gpu.o hip_main.o hip_texture.o
	$(HIPCC) -o hip_gpu $(HIPOBJS) $(HIPCCFLAGS)

hip_main.o: ${SRCS}/main_hip.cpp
	$(HIPCC) -c ${SRCS}/main_hip.cpp $(HIPCCFLAGS)

hip_gpu.o: ${SRCS}/fdtd3d_gpu_hip.cpp ${SRCS}/fdtd3d_gpu_hip.h
	$(HIPCC) -c ${SRCS}/fdtd3d_gpu_hip.cpp $(HIPCCFLAGS)

hip_texture.o: ${SRCS}/fdtd3d_texture_hip.cpp ${SRCS}/fdtd3d_texture_hip.h
	$(HIPCC) -c ${SRCS}/fdtd3d_texture_hip.cpp $(HIPCCFLAGS)

clean:
	rm hip_gpu *.o

The output messages can be viewed here:
hip_out.txt
It can be seen that it complains: ld.lld: error: unable to find library -lstdc++
Take a deeper look at the output, it seems that it skips a lot of directories. How can I fix this issue? I'm pretty sure I have required libraries (I installed ROCm following official docs and my build-essentials is up-to-date with sudo apt-get update). Any help is appreciated.

@mangupta Passing the correct library path successfully compiles it. After running it, it said no ROCm compatible device detected. However, I do have a NVIDIA gpu, which I think is also supported by HIP?

Hi @CanYing0913, have you added your user to the video and render groups? This can be done with the following command
sudo usermod -a -G render,video $LOGNAME

Hi @CanYing0913, by default, access to GPU devices and certain system resources is restricted to the root user or specific groups. The command sudo usermod -a -G render,video $LOGNAME is used to add the current user to the render and video groups on a Linux system. The render group is typically used to grant access to the GPU for rendering tasks. Members of this group can access the GPU devices directly, which is essential for applications that require GPU acceleration, such as those using ROCm for compute tasks. The video group is used to manage access to video devices. This is important for applications that may need to perform video processing or utilize video hardware acceleration.
After adding the current user to the groups, you need to reboot the system to make it work. Here is a link to the Rocm quick installation guide, please let me know if you have more questions.


Floating debug tool bar not properly aligned when using custom menus

enable custom menus  "window.titleBarStyle": "custom"
set the debug toolbar to floating

Notice that the debug toolbar is not properly aligned with the bottom of the tabs.

This is happening because this.partService.getTitleBarOffset() is returning 22px
Which is wrong in this case, it should be 30px
It seems like the partService here should be aware if windows and custom menu is turned on
Forwarding to @bpasero and @sbatten

@sbatten not sure this is a good fix. Getting the clientRect height will force a browser re-layout. And partService.getTitleBarOffset is called whenever quick open is shown, debug actions widget is dragged and quick open is layouted (can be very often).
Could we not instead look at the configuration service and based on that return the value like before?
fyi @bpasero

@isidorn @sbatten yeah I also felt like this could be just hardcoded

The current fix is fine for stable, thus pushing this out to July

I just verified this works in latest insiders.

@bpasero sorry wasn't sure of the impact so I did some js profiling with and without the call and didn't notice a difference in perf so I went with that to avoid hardcoding. Though this is only one of 2 places the height would be hardcoded, I would prefer something a little more dynamic. Is it an option to make the partLayoutInfo method public in layout.ts so that layout can be the source of truth?

@sbatten I would add it to IPartService and then expose it from workbench.ts. Workbench can access layout.ts (and that can be public there).

The milestone here is July but the fix is present in the release/1.25 branch.
Am I missing something?

@ramya-rao-a  A fix is in June. A better fix is in July.


ENH: improve warning for protocol getitem

Coverage remained the same at 86.649% when pulling ec1ca28f67ced5e277fc7a276177666372987055 on branch-protect-hook-stopped-me-from-pushing-this-commit-directly-;_; into cf2abf10e27ccde572464fa34bdc40b0d1736487 on master.


Implement arbitrage bot for issue #958

Resolves ubiquity/arbitrage-bot#3
https://github.com/surafeldev/arbitrage_bot

@surafeldev If this PR is ready for review then pls open it against https://github.com/ubiquity/arbitrage-bot/issues/3, show QA of how it works, provide QA instructions of how to test locally


Polyfill thrashes CPU

See: https://github.com/Financial-Times/polyfill-service/blob/master/polyfills/Element/polyfill-ie7.js#L90
This was observed to be spamming the render process in Chrome; it's a bit strange that this code doesn't at least check for Promises or rAF to do that better.
/cc @triblondon

Thanks, clearly this is a far too aggressive implementation, and we'll update it.
I'm curious about why this was seen in chrome. The default behaviour of the polyfill service is to vary output by user agent, and chrome would not receive this polyfill (because it doesn't need it).
Do you know the cdn.polyfill.io URL of the script resource that served this code to chrome? It's also important to know whether the URL contains a libVersion argument, because if it does a release on our part will not solve the problem for site developers who have chosen to lock their library version.

@slightlyoff the reason it doesn't try using raf or Promises is that neither of those technologies exist in IE7, which this code is designed to run in.  It's even classified as a UA-specific implementation, so the only reason you'd see this in chrome is if the developer overrode the default UA detection or the end user was spoofing an IE7 UA in Chrome.
For example, this script URL would load that code unconditionally:
https://cdn.polyfill.io/v1/polyfill.js?features=Element&ua=ie/7

IE7 is unsupported by the FT.  This polyfill came from an original implementation by @jonathantneal but it looks like I refactored it a bit some time ago.  I've proposed in https://github.com/Financial-Times/polyfill-service/issues/456 to drop a load of browsers from the service, but in the meantime I'll increase the timeout and add a limit to the number of iterations.

OK, seems I let Alex up the garden path a bit on this - the problem is not in the Element constructor polyfill, though the change there is sensible, but in _enqueueMicrotask.

Looks like the enqueueMicrotask polyfill was replaced by a better implementation in a recent release of the service, but the library that the Next FT site is using is locked to a previous version of the code.  I've nudged the Next team to update their dependencies, mitigated the effect of the remaining tight setInterval loop, and am tracking the idea of removing it in #456.

Next FT seem to be specifying _enqueueMicrotask with the always flag, this may be why Chrome got the polyfill.
https://github.com/Financial-Times/next-js-setup/blob/30d4c5ad506b6b7b3b7be014246c94f7a7832ceb/templates/js-snippets/polyfills-url.html#L1


Mnt/annotate keyboard methods

MNT: Annotate all keyboard methods
style: set double quotes as default quoting, before had no default quoting and
some methods were using single quotes and some were using double, my formatter (black)
changed all the quotes to double quotes, and change the indent of  methods (
find_multiple, find, find_until, find_all, find_text,
click, click_relative, double_click_relative,
triple_click_relative, right_click, right_click_relative,
find_app_element
)

Sorry for the size of the PR, guys, but had some 'automate' changes because of the black formatter and the keyboard session is pretty big ;)


query by verified/unverified

Please add the ability to query by verified and unverified, if possible. Example being that I would like to query for all unverified observations for a given concept, dive, or observer.

Implemented in v0.10.0


gotk bootstrap and create helmrelease issue: context deadline exceeded with raspbernetes

After following https://raspbernetes.github.io/docs/installation, I get constant context deadline exceeded errors including in the bootstrap and trying to add any helmreleases.
Here's the cli commands I ran:
gotk bootstrap github --arch=arm64 --components=source-controller,kustomize-controller,helm-controller,notification-controller --owner=jstewart612 --path=raspbernetes --personal --repository=gotk --version=latest gotk create source git monitoring --interval=30m --url=https://github.com/fluxcd/toolkit --branch=main gotk create source helm stable --interval=1h --url=https://kubernetes-charts.storage.googleapis.com gotk create helmrelease sealed-secrets --interval=1h --release-name=sealed-secrets --target-namespace=gotk-system --source=HelmRepository/stable --chart=sealed-secrets --chart-version="1.10.x"
Logs:
source-controller.txt
notification-controller.txt
kustomize-controller.txt
helm-controller.txt

@jstewart612 this isn't necessarily a gotk problem. It's because of the performance of the microSD disc IO and if you check other pods running across your cluster you'll see a lot of similar issues. This can be mitigated in the ansible scripts by increasing the etcd thresholds here https://github.com/raspbernetes/k8s-cluster-installation/blob/e8a72625824ea1198e09554707057d2a011292e5/ansible/group_vars/masters.yml#L18
I've set mine to 200 interval, 5000 timeout, this isn't perfect but if you're able to invest in getting a SSD to boot from you'll see massive performance benefits and you won't have this issue. You can follow this guide to do so: https://raspbernetes.github.io/docs/usb_booting

Confirmed issues to be I/O related:  because the error message just said "timeout" and not anything else, I didn't even think to check etcd, which is screaming timeouts all over the place.
Cheers @xUnholy ty I just got through converting to all SSDs in the cluster and it works great.  Not a gotk problem.


Turtlebot4 development state overview

There are so many correlated issues (#62 #143 #158 #181 #188 #226 #246 #259 #218 ) regarding SLAM and Nav2 on the robot that my team and me starting to question if the Turtlebot4 currently can be used for what was promised. I would like to have an answer what can be expected to work and what is known to be not working currently.
Our experience based on the promised selling points is:

[ ] Robot with SLAM and Nav2

[x] Galactic working before G.5.1
[ ] Humble no working version
[ ] Camera (esp. depth) working only sporadically

[ ] Simulator

[ ] no working version for Humble or Galactic

[x] Documentation

[x] pretty good and up to date but suggests everything above should work

[ ] Lesson Material

[ ]  seriously incomplete

We are trying to get these Turtlebots running since over 6 month now. And it feels like we didn't make any progress because this complex system is so difficult to debug.

@teufelweich I am sorry to hear that you are having difficulties with your set up of the turtlebot4 and can understand that you are feeling very frustrated. 6 months is indeed a long time to be working on a set up. I can respond to you here in regards to the various issues that you are running into or if you would like you can choose to pursue these issues with the client success team. I am not in any position to discuss specifics about discussions you had when purchasing the turtlebot4, but I can speak to what the Turtlebot4 is capable of.
I do want to take a moment to note that SLAM and Nav2 are separate and complex open source projects and as such we do not control whether or not bugs are present in those projects or in general how those projects work. We are however committed to do what is within our control to help users learn how to to use those projects and to contribute to the success of those projects.
The Turtlebot4 product is fully able to run nav2 and slam with both Galactic and Humble, with the physical robot or in simulation with the exception of some specific bugs that are being addressed which I will list below. On this line, I will note that the Turtlebot4 product is built on ROS 2 and is a great tool for learning ROS 2 and other open source tools (for example Gazebo). As much as we try to make the Turtlebot4 user friendly, users still ultimately need to learn how to operate and connect together these ROS 2 systems. I agree that these are complex systems and it does take a lot to learn how to troubleshoot them properly. That in itself is not so much a flaw of the product so much as the point of why it exists. It is also why the community is supportive of beginners and the issues that they run into. As such, most issues we see are people needing to learn ROS 2 and who made mistakes when going through the instructions or are trying to do something in a unique way that is not explicitly described. This is understandable for an educational product but is not to be conflated for deficiencies in what the robot can do.
To my knowledge there are 3 open bugs and I am working on solutions for them when I can:

Create3 CPU at 100% - This can also present itself in terminal output as messages about tf timestamp mismatching. There are several potential solutions that can be tested by someone who is running into this issue but they need to commit to working with us to test things and send us results. Either way I am working on a solution to this issue that can be released to all, but it would help if someone experiencing this issue participated in the process.
There is an issue where the nav2 components are not subscribing to the correct scan topic which makes it ignore unmapped objects. There is a workaround available that is provided to anyone who reports this issue and a patch is also in the works.
Launching  nav2 + slam with namespacing all through the one simulation launch file causes the namespace to be applied to some nodes twice. The work around is to not use namespacing in sim or to launch navigation separately from the simulation using the dedicated navigation launch files when using namespacing. This is also on my list to resolve.

I can give you some insight into the status of the issues that you listed that I have been involved with if you would like. They fit into the following categories:
a) issues where the person asking the question stopped responding and stopped participating in the troubleshooting process (https://github.com/turtlebot/turtlebot4/issues/188, https://github.com/turtlebot/turtlebot4/issues/246, https://github.com/turtlebot/turtlebot4/issues/218)
b) issues that were closed by the user before we could respond (https://github.com/turtlebot/turtlebot4/issues/226)
c) duplicates of existing issues that already have workarounds posted (https://github.com/turtlebot/turtlebot4/issues/260)
d) Issues that are brand new so I can't speak to yet (https://github.com/turtlebot/turtlebot4/issues/259)
If your team is still running into the issues described on any of the inactive tickets then I would encourage them to respond to the tickets and they can tag me if they feel like they are not getting responses from whoever was participating in the discussion previously (or if no one has responded). If they are experiencing multiple issues in the same system please ask them to indicate in their tickets that it is running on the same system and we can help them take a more holistic approach in troubleshooting and identifying the core issues with their setup.
In regards to your last point,I am a software developer and can't speak to the lesson material, please reach out on the appropriate repo about any lesson material. I assume that the appropriate location would be here: https://github.com/turtlebot/TurtleBot4Lessons/issues

I forgot to mention in my previous response. I am not aware of anyone having issues with the camera so please do link me on that issue.

@hilary-luo I'm also experiencing the issue with the create3 100% CPU utilization. Can refer to all related issues with your proposed workarounds (Im only applied the new dds configuration)? Maybe I can contribute/participate, my Supervisor gave me resources/time on the turtlebot to work on this problem

@hilary-luo I'm also experiencing the issue with the create3 100% CPU utilization and am available to help with the debug if necessary. In my case, I'm using the latest Humble release, and the issues I'm seeing is the create3's LEDs go to yellow or red and I can't teleop and I stop receiving ROS messages after some time mapping. Sometimes it recovers after some minutes but sometimes (especially when the LED turns red) everything stops working until the create is restarted.

For anyone wanting to follow along or join in on the cpu at 100% troubleshooting, jump over here https://github.com/turtlebot/turtlebot4/issues/266.

This issue is being closed due to inactivity. I believe every issue that is still present is being responded to and/or tracked on other tickets.


chore: tests creating changesets

What/Why/How?
Reference
Testing
Screenshots (optional)
Check yourself

[ ] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[ ] All new/updated code is covered with tests

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

I think only PRs into main are handled.

I'll just merge into chore/add-chagesets to test firstly :)


powertoys run工作區問題

Description of the new feature / enhancement
我使用powertoys run 時，打開的網頁位於我正在使用的工作區
Scenario when this would be used?
每當我只有一個工作區開啟時
Supporting information
No response

When I use powertoys run, the webpage that opens is in the workspace I am using.
@frank570570 can you elaborate on this? What do you mean with workspace?
/needinfo


fix: #2356 - correct message for "fetch and refresh" dialog

"Refreshing product" (en) / "Actualisation du produit" (fr)
instead of
"Updating the product on the server..." (en) / "Mise à jour du produit sur le serveur..." (fr)
Impacted file:

product_refresher.dart: used the adequate localizations for the "fetch and refresh" method

What

Same UX, different text for the previously misleading "fetch and refresh" dialog

Fixes bug(s)

Fixes: #2356

Codecov Report

Merging #2378 (eb77b50) into develop (2ea0da3) will decrease coverage by 1.23%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop   #2378      +/-   ##
==========================================
- Coverage     8.86%   7.63%   -1.24%
==========================================
  Files          161     200      +39
  Lines         6623    9633    +3010
==========================================
+ Hits           587     735     +148
- Misses        6036    8898    +2862

Impacted Files
Coverage Δ

...kages/smooth_app/lib/widgets/attribute_button.dart
0.00% <0.00%> (-92.00%)
:arrow_down:

...s/smooth_app/lib/data_models/user_preferences.dart
8.73% <0.00%> (-23.57%)
:arrow_down:

packages/smooth_app/lib/themes/smooth_theme.dart
60.00% <0.00%> (-22.98%)
:arrow_down:

...p/lib/generic_lib/dialogs/smooth_alert_dialog.dart
15.29% <0.00%> (-18.92%)
:arrow_down:

...mooth_app/lib/data_models/product_preferences.dart
24.65% <0.00%> (-6.78%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/welcome_page.dart
0.00% <0.00%> (-3.13%)
:arrow_down:

packages/smooth_app/lib/main.dart
14.78% <0.00%> (-3.12%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/scan_example.dart
0.00% <0.00%> (-2.28%)
:arrow_down:

...p/lib/pages/onboarding/consent_analytics_page.dart
0.00% <0.00%> (-1.57%)
:arrow_down:

...smooth_app/lib/pages/product/new_product_page.dart
0.00% <0.00%> (-0.88%)
:arrow_down:

... and 199 more

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 b08fa96...eb77b50. Read the comment docs.

thanks @monsieurtanuki


ssh key section

key_data filed is missing in the create virtual machine section, the document says "Provide a public SSH key in the key_data field"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 163088fc-67d3-aa81-26e7-0155f3aaa90c
Version Independent ID: fafceb81-d8fc-8c20-72e5-b2dddc445f73
Content: Quickstart - Use Terraform to create a complete Linux VM in Azure
Content Source: articles/terraform/terraform-create-complete-vm.md
Service: terraform
GitHub Login: @TomArcherMsft
Microsoft Alias: tarcher

@techiechap Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@TravisCragg-MSFT  Thank you earlier version of  docs has admin_ssh_key block
  admin_ssh_key {  username   = "var.admin_username" path     = "/home/${var.admin_username}/.ssh/id_rsa.pub" key_data = "var.public_key"  }
key_data field is no more required with new config block
    admin_ssh_key {         username       = "azureuser"         public_key     = file("/home/azureuser/.ssh/authorized_keys")     }

Closing out old GitHub Issues. This issue has been resolved. #please-close