Use the xdg standard to store the config in linux

Thanks for this. I get the XDG_CONFIG_HOME, but have some doubts about the os.path.expanduser(os.path.join("~", ".config")). Common locations are also ~/.myapp.cfg or ~/.myapp/config.cfg, and they would be impossible to reach by means of the ~appdata prefix in this way.
Is ~/.config part of a standard? If it is, why is any home dir always so cluttered with hidden dirs?

Dear Almar Klein,
Thank you for taking the time to consider this PR.
Almar Klein<EMAIL_ADDRESS>writes:

Thanks for this. I get the XDG_CONFIG_HOME, but have some doubts
about the os.path.expanduser(os.path.join("~", ".config")).

According to the xdg specification
(https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html),
the default value of the XDG_CONFIG_HOME variable is '~/.config/'.

Common locations are also ~/.myapp.cfg or ~/.myapp/config.cfg

Indeed, I have seen these locations before, but I thought that it was
some emerging behavior due to the lack of standard. I have also seen
several projects moving the configuration files from directories like
~/.myapp.cfg or ~/.myapp/config.cfg to ones following the xdg
standard.
As a user, I tend to prefer the xdg specification over the '~/.myapp/'
directory because it avoids cluttering my home directory. In addition, I
can keep all my configuration files in a predefined place by setting
only one environment variable: XDG_CONFIG_HOME.

, and they would be impossible to reach by means of the ~appdata
prefix in this way.

IMHO, user using the ~appdata prefix want the framework to use a
standard directory, not the '~/.myapp/' folder.
(like get_app_dir in click ?
http://click.pocoo.org/5/api/#click.get_app_dir).
My best,
Konubinix
GPG Key    : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A

Ok, I see that click does use the .config as a default. I'll assume that this is the best approach and that ~.config always exists (I checked that it does on Ubuntu Lucid Lynx).

Thanks!


Making the workflow robust to differences in acquisition protocols

[i] Right now the preprocessing workflow can only handle inputs from workflows that follow the HCP scanning protocol. However, most studies and especially older studies, will have utilize a traditional double echo fieldmap approach. Hence, the workflow needs to be able to handle both approaches.
[ii] It would also be good to test different types of fieldmaps, such as GRE, SE and spiral fieldmaps.
[iii] Lastly, it would be good to build in a contingency for when a protocol has no fieldmaps, or when fieldmaps are missing for some subjects.

@craigmoodie look at you, Github pro! so proud

thanks @vsoch! :+1:

So let's make a nipype pro from a Github pro:
[i] Added #20.
[ii] Added #20 and #21.
[iii] Added #19.
@craigmoodie, Do these cover all the defined use-cases?

Hi Osteban, there is also the case where the user will inputs two phase-encoding reversed spin-echo field maps, but this is already implemented in the original workflow that I uploaded. Otherwise, I think those issues should cover all of the other use cases.

Cool. Yes, that is the default use-case as you initially implemented it. Actually, that should exactly correspond to this new workflow: https://github.com/poldracklab/preprocessing-workflow/blob/master/fmriprep/workflows/fieldmap.py#L15. For this reason I did not open any other ticket.
Now that this issue is mapped to the 3 elementary tasks (#19, #20 and #21) I will close it.
Thanks for reporting!


Running kaggle challenge dataset

hello，could you add  kaggle challenge dataset， thanks！

Hi, we added a reference to the Human Protein Atlas Image Classification Kaggle Challenge.
Is this the challenge you were referring to?


feat: IListEmpty and friends

Fix for #75

I've just added the other Empty types aswell, do you have some suggestion what i could add to the current tests? @marcglasberg

Two things:
Whats your opinion on overriding isEmpty / isNotEmpty on the Empty types like so:
  /// An empty list is always empty, by definition
  @override
  bool get isEmpty => true;

  /// An empty list is always empty, by definition
  @override
  bool get isNotEmpty => false;

Do you think we should discourage or even disallow instantiating the IListEmpty directly instead of using IList.empty()?
Although it is one char longer i see the benefit of automatic type coercion beeing IList and not IListEmpty:
var ilist1 = IList.empty() // is of type IList
var ilist2 = IListEmpty() // is of type IListEmpty

I do not see the benefit of having a variable of type FooEmpty, users will always want to reassign the list if they declare an empty ilist right?

Yes, you should override all methods that now have trivial implementations, including isEmpty etc. This will make it faster.
And I also see no point in instantiating IListEmpty directly, if you can simply write const ilist1 = IList.empty() and get an IList.

What do you think can we do to discourage instantiating IListEmpty()? We could make the constructors private

Yes, sure, make them private.

Thanks.


add pyproject.toml and setup.cfg support.

Hi @hakancelik96,
I plan to use your helper tool in my projects but is it possible to release a new version of unimport with pyproject.toml and setup.cfg support? You can find all the developments in this pull-request, if you have a feedback, I can fix asap:

First of all, all my changes are backwards-compatible. It doesn't affect the old habits.
I included the default .unimportant.cfg file to Config class because toml is a bit different than .ini files, It's not a good idea to parse toml files with ConfigParser.
toml is an optional dependency. It's just for parsing pyproject.toml file.
I added two tests for checking all formats if they're generating the same outputs, you can run tests with: python setup.py test

Thank you for this project. It's very useful, congratulations.

A big thank you for your contribution.
Everything looks great, the changes you make are great, I'm taking out the new version.


The library seems to be working fine, but there is no logged change on matomo

Describe the bug
I set up a basic installation of a flutter app, added some parts of the example code. The console shows expected output:
[Matomo] Matomo Initialized: firstVisit=2024-03-27 09:30:05.789Z; lastVisit=2024-03-27 09:36:08.090201Z; visitCount=2; visitorId=null; contentBase=https://com.example.flutter_new_build_gradle; resolution=1080.0x2208.0; userAgent=Android 11 (SDK 30), Google sdk_gphone_x86
[Matomo] Processing queue 1
[Matomo]  -> {requests: [?idsite=4&rec=1&new_visit=1&action_name=Flutter+Demo+Home+Page&url=https%3A%2F%2Fcom.example.flutter_new_build_gradle%2Fhomepage%3F&_id=77df4c6fbe6349bd&rand=568357132&apiv=1&_idvc=2&_viewts=1711532168&_idts=1711531805&res=1080x2208&h=9&m=36&s=9&cookie=1&ua=Android+11+%28SDK+30%29%2C+Google+sdk_gphone_x86&lang=en_US&uid=Nelson+Pandela&pv_id=V1Ex5r&cdt=2024-03-27T09%3A36%3A09.163850Z]}
[Matomo]  <- 200
[Matomo] Processing queue 2
[Matomo]  -> {requests: [?idsite=4&rec=1&ca=1&url=https%3A%2F%2Fcom.example.flutter_new_build_gradle%2Fhomepage%3F&_id=77df4c6fbe6349bd&rand=122132530&apiv=1&_idvc=2&_viewts=1711532168&_idts=1711531805&res=1080x2208&h=9&m=36&s=19&cookie=1&ua=Android+11+%28SDK+30%29%2C+Google+sdk_gphone_x86&lang=en_US&uid=Nelson+Pandela&pv_id=V1Ex5r&e_c=Main&e_a=Click&e_n=IncrementCounter&cdt=2024-03-27T09%3A36%3A19.000227Z, ?idsite=4&rec=1&ca=1&url=https%3A%2F%2Fcom.example.flutter_new_build_gradle%2Fhomepage%3F&_id=77df4c6fbe6349bd&rand=97035459&apiv=1&_idvc=2&_viewts=1711532168&_idts=1711531805&res=1080x2208&h=9&m=36&s=26&cookie=1&ua=Android+11+%28SDK+30%29%2C+Google+sdk_gphone_x86&lang=en_US&uid=Nelson+Pandela&pv_id=V1Ex5r&e_c=Main&e_a=Click&e_n=IncrementCounter&cdt=2024-03-27T09%3A36%3A26.050347Z]}
[Matomo]  <- 200
[Matomo] Processing queue 0

On our Matomo installation I do not see any logging though. It appears as if nothing has been received.
I suspect that this is not a problem with the library, but I also set up tracking for a website on the same matomo installation and it works fine. Any hints, if I might need to fulfill some steps in matomo, or on the app side would be very appreciated :)
To Reproduce
Steps to reproduce the behavior:
My app code:
import 'package:flutter/material.dart';
import 'package:matomo_tracker/matomo_tracker.dart';

const String _matomoEndpoint = 'https://MYMATOMOPAGENAME.com/';
const int _matomoSiteId = 4;
const _testUserId = 'Nelson Pandela';

// Use this as dispatchSettings in MatomoTracker.instance.initialize()
// to test persistent actions. Then run the example, cause some actions
// by clicking around, close the example within 5min to prevent the
// dispatchment of the actions, run the example again, wait at least 5min,
// finally check the Matomo dashboard to see if all actions are there.
const DispatchSettings dispatchSettingsEndToEndTest =
    DispatchSettings.persistent(dequeueInterval: Duration(minutes: 5));

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await MatomoTracker.instance.initialize(
    siteId: _matomoSiteId, url: _matomoEndpoint, verbosityLevel: Level.all,
    // dispatchSettings: dispatchSettingsEndToEndTest,
  );
 MatomoTracker.instance.setVisitorUserId(_testUserId);
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      navigatorObservers: [matomoObserver],
      theme: ThemeData(
        // This is the theme of your application.
        //
        // TRY THIS: Try running your application with "flutter run". You'll see
        // the application has a purple toolbar. Then, without quitting the app,
        // try changing the seedColor in the colorScheme below to Colors.green
        // and then invoke "hot reload" (save your changes or press the "hot
        // reload" button in a Flutter-supported IDE, or press "r" if you used
        // the command line to start the app).
        //
        // Notice that the counter didn't reset back to zero; the application
        // state is not lost during the reload. To reset the state, use hot
        // restart instead.
        //
        // This works for code too, not just values: Most code changes can be
        // tested with just a hot reload.
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> with TraceableClientMixin {
  int _counter = 0;

  void _incrementCounter() {
    MatomoTracker.instance.trackEvent(
      eventInfo: EventInfo(
        category: 'Main',
        action: 'Click',
        name: 'IncrementCounter',
      ),
    );
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // TRY THIS: Try changing the color here to a specific color (to
        // Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
        // change color while the other colors stay the same.
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          //
          // TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
          // action in the IDE, or press "p" in the console), to see the
          // wireframe for each widget.
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }

  @override
  String get actionName => widget.title;

  @override
  String? get path => '/homepage';
}

Expected behavior
I expect Matomo to log the received messages.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 10
Browser: Firefox
Version [e.g. 22]

Smartphone (please complete the following information):

Device: Emulator, Smartphone was also tested inbetween
OS: Android 11

Additional context
We currently use Matomo 5.0.2

@TesteurManiak
Hey, I was wondering if there is something you need from me to verify this problem or give any support?

@tfitzke Unfortunately, considering that the requests are returning a valid status code, it might have something to do with your installation (even if it works correctly on the web). Have you tried to sent event to a non hosted Matomo instance to see if it works better? Other than that I have no idea what might cause that.

A direct call via: http -v GET "https://MYMATOMOPAGENAME.com/matomo.php?idsite=4&rec=1" is working

With non-hosted, you mean a cloud installation of matomo?
Yes

Hey, we found the problem!
We had to use:
const String _matomoEndpoint = 'https://MYMATOMOPAGENAME.com/matomo.php';
This was due to matomo telling us, we need to use the address "https://MYMATOMOPAGENAME.com/" and I was under the impression the plugin will add the "matomo.php" part, as it apparently does in the JavaScript plugin!

Great, glad you've fixed your issue 👍

This also bit me yesterday, maybe add a remark in the readme that you have to add the matomo.php

on a second note, maybe it would be good idea to set the verbosityLevel not to none as a default.


Add bookmarks (or show starred repos)

Since version 0.9.1 (commit https://github.com/jonan/ForkHub/commit/c13fa394fba1f494242a1eb60da2063231d3170d) it doesn't show my starred repos anymore, and adding bookmarks seems impossible (I used the starring function for that, as Github itself describes the starring as a bookmark function). Please add an option to bookmark a repository or reverse this change.

I believe it was removed due to user feedback.  I also used it as a way to bookmark repos. Perhaps it would be a good idea to have a setting that let's user's turn it on or off. That way those who like it would be able to use it again.

I found how to bookmark projects, however I can only bookmark the issue page of a project and it is stored locally on the device so it does not synchronise between my tablet and phone.

Bookmarks are fast links to issue searches, what you want is the list of starred repos (just clearing this so we are in the same page).
I agree that showing the starred repos is a needed feature, but they shouldn't be shown in your repositories list, because people normally have a lot of starred projects and that kind of makes the repositories tab useless.
I'll try to create a new way of showing them.

In that case, adding starred repo's in the list below Gists, Issue database and Bookmarks would be the easiest solution IMO.

I'm also missing starred repositories. I don't watch every my starred repositories to not clutter main feed, but sometimes I want to check what's happening in other projects and without showing starred repositories it's impossible (I don't fork everything around :-) ).
Please think about it - maybe at the beginning just add an option to turn it on/off as @RandomlyKnighted suggested?

I like @johasnw666's suggestion. The sidebar is almost empty and is the 1st or 2nd place I looked for my starred repos.

+1

+1

Please add the "stared" option. It's really useful.

+1


more fix to load_mem and from_mem

Now that SoLoud copies sound data bytes, it makes sense to use &[u8] as type parameter.

Oops I also just pushed some changes. I've trying to trigger undefined behavior using copy=false and takeownershipt=false and can't seem to get that. Even by explicitly deleting the memory buffer after passing to soloud:
    let mut wav = audio::Wav::default();

    let bytes = std::fs::read("sample.wav")?;

    wav.load_mem(&bytes)?;

    drop(bytes);

OMG. It was my brain bug again. It is realeased
https://github.com/jarikomppa/soloud/blob/3346bbc3c69ec3869337351dadde357b687b241e/src/core/soloud_file.cpp#L157


Update README.md

"The requested package creocoder/yii2-nested-set-behavior could not be found in any version, there may be a typo in the package name."

Fixed.

Fixed.


custom_prng: better error messages for key validation

Thanks for the context, so you think we should leave these errors as-is? If we want to go one level up we could check this in _check_prng_key which is called by the user-level functions - would that be better? (currently _check_prng_key calls PRNGKeyArray so it would just be moving the check up a single level)

I think we want these particular checks to live in the PRNGKeyArray constructor, even after #9263, since we want to be sure they hold at that point. I wouldn't hoist them to jax.random, but we can add more specific heuristic checks there if we'd like. I'd suggest we:

take your proposed change with a different error message prefix, e.g. JAX encountered invalid PRNG key data: ...;
[optional] add any heuristic checks to _check_prng_key that specifically look for gotchas that can happen in the interim. For example, since my understanding is that we were motivated by this: if key data is scalar we can raise with something along the lines of "are you using vmap and did you mean to pass in a batch of keys?"

I say item 2 is optional since _check_prng_key will be drastically simplified after #9263 (to an isinstance check, if anything). Thoughts?

OK, PTAL. I basically did (1), I think it makes sense to punt on (2) because things will be changing so significantly.


Regression msi

@JanPrusinowski Do you expect that any more fixes are needed after reviewing my results from yesterday? Or after your full regression run.

@macpijan I think that this is ok. I have run few tests which failed in your run due to connection issues or similar cases to verify if they run correctly - and they do.


Implement missing virtual tables for Accord debugging

patch by Aleksey Yeschenko; reviewed by Benedict Elliott Smith for CASSANDRA-20062

The main thing blocking my +1 is the txn_blocked_by table.  We either need to move it back where it was, or change JVM-Dtest to handle the changes.
My stance is txn_blocked_by should move back and if there are concerns about the table we should address them.  If there is a valid believe that this table should not be exposed in prod in the current state I am fine moving it (though I disagree).


December Patch to fix small details from first release

Modified Windows Docker; removed FluxCD flux-system from staging; fixed naming in Pulumi backend

Thank you very much 😄 🛩


How do I configure it?

I have created a configuration file:
coffeelint --makeconfig > /Users/user_name/.atom/coffeelint.json
I changed the value of the recommended length of a line.
Default settings:
"max_line_length": {
	"value": 80,
	"level": "error",
	"limitComments": true
}

I replaced at it:
"max_line_length": {
	"value": 140,
	"level": "warn",
	"limitComments": true
}

How to setup? What am I doing wrong?

Okay. The file should be placed in the project root.


Map state needs an undo redo stack

Whenever an edit is made to the underlying model, we should push the edit onto an undo/redo stack. We'll also need buttons for this (to support touch)

Talked with Richard about this. Thinking about a log structure.

Done.


feat: pipeline routes

Generates pipelines models to access Devopness API routes.

@mlpbraga please expose the new services to SDK consumers in DevopnessApiClient.ts

Closing as no longer needed after #568


refactor: remove unneeded .stackblitzrc, update template dependencies

This PR harmonizes what basic config files we find in a starter template.
What's in package.json
Almost all starters have a package.json file. I've tried to harmonize those files to follow this pattern:
{
  "name": "{folder-name}-demo",
  "version": "0.0.0",
  "private": true,
  "scripts": { … },
  "dependencies": { … },
  "devDependencies": { … }
}

Some templates may not have "scripts" (most for some EngineBlock starters), some may not have "devDependencies".
Open questions:

What should we use for the package name?

Should we include one at all?
Is the "{folder-name}-demo" pattern okay, or do we want to use “starter” or “template” instead of “demo” maybe?
Note that if we end up using a name that matches an existing package on npm, running npm info will show information for that package merged with info from the local package.json, which is quite strange, but maybe a very rare problem.

Is the "version" even useful? I’m tempted to just drop it.

Removing all the .stackblitzrc files
All the .stackblitzrc files in WebContainer projects were spelling out defaults, such as { "installDependencies": true, startCommand: "npm run dev" }.
I removed them for the sake of readability, but if we want to include one with defaults in every WC starter template we could do that too.
Making sure every WC template has a .gitignore
For every WebContainer-based template, I made sure it had a .gitignore file that listed at least:

node_modules
whatever caching folder the framework is using (.next, .nuxt, .svelte-kit, etc.)
whatever build output folder resulted from running npm run build (build, dist, etc.)

Harmonizing index.html files

Made sure every one had a <!DOCTYPE html>
Removed <meta http-equiv="X-UA-Compatible" content="IE=edge">
Used the same minimal viewport meta everywhere: <meta name="viewport" content="width=device-width">

Harmonizing base CSS styles
We had base style.css files which looked like:
h1, h2 {
  font-family: Lato;
}

That's not super useful, especially since the preview documents don't load the Lato fonts at all. (They used to, in EngineBlock projects, but we removed those fonts in early 2022 for performance reasons.)
Instead I'm proposing a very basic stylesheet looking like this:
* {
  box-sizing: border-box;
}

body {
  margin: 0;
  padding: 1rem;
  font-family: system-ui, sans-serif;
  color: black;
  background-color: white;
}

h1 {
  font-weight: 800;
  font-size: 1.5rem;
}

I'd drop version as well, but I don't have strong feelings about that.

Dropped it. I agree that it's not useful for projects.

For the package name, I think the -starter makes a bit more sense

Changed from -demo suffix to -starter suffix.


There are no commands defined in the "typesense" namespace.

Describe the bug
There are no commands defined in the "typesense" namespace.
To Reproduce
Steps to reproduce the behavior:

Init a new symfony project  symfony new --dir=typesense --webapp --version=6.0
Require this bundle symfony composer require acseo/typesense-bundle
Define a default config with a simple entity
Try to launch command symfony console typesense:create

I tried to set this on symfony 6.2, 6.1 and 6.0.
Same result each time.

Edit : Seems to work if I rename the config file acseo_typesense.yaml instead of acseo_typesense.yml

Confirmed on my side. Thanks @guillaume-a


[Search] Check meta description tag - Yahoo Bing Google

HTML Tags: Ensure your HTML element and alt attributes are descriptive, specific, and accurate.
Bing - https://www.bing.com/webmasters/help/webmasters-guidelines-30fba23a
Google - https://developers.google.com/search/docs/advanced/crawling/special-tags
Yahoo - https://help.yahoo.com/kb/search/fix-incorrectly-displayed-webpage-title-description-sln2195.html

Commit #17


[Bug] Stacked bar graph with overlapping bar breaks when having only 2 data points

Version
5.5.0
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=bar-simple&code=PYBwLglsB2AEC8sDeAoWsAeBBDEDOAXMmurGAJ4gCmRA5JALZW0A0JAvm-uTvkaqTKUasWgDcAhgBsArsw5dYeKgCcIVQrADaJdAMGxoEpkQBEABlOLBAIwkqA4hJBmAtAEZz5gKRXdpOxUAdQgAEzAACzMATgBWX2tSUIkwCSItLXcWWHcAXWytACZswtz8_3QKajpA2n9Of31BIxNYU3c_AyVUgGMAazMwYFSpToNAkPCots8fMcFk1PTM7LyC4thS8q6qkVpa-sSm0haRU0L50jxegbahkcv0CbDIs1mEithFtO0VnPztBstolKsIavY6oIGuhcih2ABuIA
Steps to Reproduce
Clicking the link is sufficient to reproduce the issue.
Current Behavior
The graph breaks and shows no bars or legends.
The problem exists only when each of the series have two datapoints. When there are more datapoints, the bars are displayed (see MWE).
Expected Behavior
The expected behaviour is that there are two stacked bars (with two series in each bar). And behind the stacked bars, there is one unstacked bar.
Environment
- OS: Manjaro Linux, Windows 11
- Browser: Brave 1.65.114, Firefox 124.1.0
- Framework: -

Any additional comments?
No response

removing barGap maybe ?

removing barGap maybe ?

I need the gap since I'm trying to have the bars on series 1 be like a total that sometimes won't match the stacked children thus the bar will appear from behind like in the docs

Changing the value of BarWidth to anything more than 100
Changing the value of BarGap to anything less than 100
Will fix this problem, but the main reason I wanted to report this is adding a third bar on any of the 3 series fixes the problem too
See this example

There seem to be multiple problems with bar series.
The issue in the given example seems to be axis type: 'time' together with barWidth: '100%' but only at exactly 2 datapoints: Demo
Another issue seems to be that axis type: 'value' does not work at all with stack. The documentation is somewaht confusing on which axis types should work: Demo
For axis type: 'time' without the use of barWidth: '100%' its working fine: Demo
Axis type: 'category is working as intended: Demo

More on that the BarWidth seems to have some "reversed" behavior when there are only 2 values on a series
90% width on 2 values
90% width on 3 values


Rd 9191 opentelemetry js distro fix issue with version GitHub action

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


(fix): deleted the unrequired keys in electronics part

Deleted the unrequired keys in electronics part

Summary by CodeRabbit

Refactor

Updated the structure and formatting of the data array used in the Tabs component.
Renumbered the key properties for better consistency.
Improved the presentation of headings, descriptions, and links within the component for enhanced user readability.

LGTM

Good work! keep going!


[feature request] Provides the mermaid content

Dear,
Thanks for your service, is it possible to allow to get the mermaid file/content  generator from the schema ?
Thanks
Best Regards

Hey @bioinfornatics! Good to hear you like the tool.
It should be possible to add a text area to the site that displays the mermaid code, yes. It likely needs changes around this part of the code:
https://github.com/Skn0tt/prisma-erd/blob/46ef6de751432c5a3847dd46a38ad41af53085c2/src/index.ts#L25-L30
If you can provide a Pull Request with that, i'm happy to review it! In the meantime, you can get the Mermaid contents from the console:


Fix example YAML

Fixed gem inclusion in example config YAML so it is read as an array element and not a --prefixed string.

Whoops. Thanks for the eagle-eyed catch. Merging now :)


Not really useable on XP due to extreme CPU usage

I do understand that it's still a very early stage as far as XP compatibility is concerned but I thought it's not a bad idea to let you know that it's not really useable on XP.
The CPU usage percentage rarely drops below 80% on a virtual machine.
I can't test it on a real computer right now but I doubt that it would be much better.

It's complicated to respond without your VM settings and host machine specifications.

I do understand that it's still a very early stage as far as XP compatibility is concerned but I thought it's not a bad idea to let you know that it's not really useable on XP. The CPU usage percentage rarely drops below 80% on a virtual machine. I can't test it on a real computer right now but I doubt that it would be much better.

on real computer is about 50...80%

Closing this, as there are literally no details about the hardware/VM configuration. Chromium browsers have lacked HW acceleration on XP systems since 2014, which does attribute to the elevated CPU usage. In those days, multimedia-heavy content was offloaded to Flash Player, so the lack of acceleration was not as apparent. It is also true that XP, particularly XP x64 (5.2/2003) can run on pretty darned powerful hardware where even the lack of acceleration is notable, but not a showstopper.
To the OP, raise the memory and CPU allocation to your virtual machine. Please be more detailed in future tickets.

Reports should be made with real hardware, as that's what web browsers target. Using web browsers on VMs is not practical unless you're doing something hmm... I don't know... Why would people use browsers in VMs?

Why would people use browsers in VMs?

unfortunately most of these annying persons don't use actual hardware and then complain about Supermium not working flawlessly
https://www.reddit.com/r/windowsxp/comments/11l57nv/how_do_people_here_use_xp_today/

Why would people use browsers in VMs?

unfortunately most of these annoying persons don't use actual hardware and then complain about Supermium not working flawlessly
https://www.reddit.com/r/windowsxp/comments/11l57nv/how_do_people_here_use_xp_today/

Using web browsers on VMs is not practical unless you're doing something hmm... I don't know...

it would make much more sense the other way round with XP as host and W7 on a virtual machine

I know for a fact that other browsers will run just fine even in virtual machines

why don't you use those other browsers if they work fine then ?

(BTW, there are good reasons why people would use browsers in VMs)

what good reasons do you need a 2024 browser on a VM for ?

@Andika207
I'm trying to help improving this browser by providing feedback.
So there is absolutely no reason to call me an "annoying person" just because I wanted to let the developer know that the browser isn't usable on VMs.
I don't feel the urge to provide feedback, if feedback is not required than I'd be happy not to provide feedback at all.
@all
About the VM:
Yes, a VM usually behaves different than a real computer.
It is usually more sluggish, less responsive, less snappy, call it what you want.
But still it is very well capable to run browsers without any major problems.
Yes, there might be glitches when you try to watch HD youtube videos or do something else that requires a decent graphics card (not just a VM emulation) etc but in general a browser should work fine, also in VMs.
Especially on a computer that is only 3 years old (and therefore too modern to run Windows XP natively) but also on older computers.
So if a browser uses more than 80% of the CPU resources (on a VM with plenty of RAM that runs on a 3-year-old host PC) with just one tab loaded (google search page) it does say something about the browser.
It says there is something wrong and that it might be a good idea to solve that problem if the developer really wants it to work properly on Windows XP.
@andika207
One good reason to use browsers in a VM would be to click on links that you're not entirely sure about. Links that you think might be dangerous.
On a VM it doesn't matter at all because you can simply turn it off and reset it.
That's not as easy on a real computer.

I wanted to let the developer know that the browser isn't usable on VMs.

the only unusable thing is your virtual machine otherwise it would have been stated on the Supermium website

But still it is very well capable to run browsers without any major problems.

if you know for fact there are other browsers that work fine for you go and use them

Yes, there might be glitches when you try to watch HD youtube videos

ah ok, you want a decent browser to watch YT videos on a virtual machine with XP....

So if a browser uses more than 80% of the CPU resources with just one tab loaded it does say something about the browser.

the browser is what it is and there won't be a special edition exclusively optimized for XP
if you feel it's a resources hog you can can either use real hardware or get the source code and compile a lite version for virtual machines

One good reason to use browsers in a VM would be to click on links that you're not entirely sure about.

If the developer doesn't care that his browser isn't working too well on XP, so be it, it's none of my business.
I just wanted to provide feedback.
Your opinion doesn't really matter much to me.


Realtime collaborative drawing with SVG-edit

Some links

http://dev.tiki.org/Realtime+Collaborative+Drawing
http://webodf.org/blog/2012-04-05.html
http://thenextweb.com/2009/06/05/experience-worlds-google-wave-svg-editor-gadget
/

Original issue reported on code.google.com by marclaporte on 16 Apr 2012 at 9:07

So I guess there's no such feature yet?


fix: Mpd update bugfix for Location tag

Specification:

<IP_ADDRESS>. Content Generation and Service Offering guidelines
A content provider may use the MPD.Location to redirect the service to a different MPD
update server. A content provider may use Base URLs on different levels to easily move anc
replicate content and offer it for example on multiple CDNs. Redirection may be used to op34 erationally move clients while requesting content.

For that reason. Mpd must update after checking other elements.

I don't understand the problem.  I don't understand how the quoted part of the spec supports your conclusion that the MPD must be updated as soon as the Location tag is seen.
It sounds to me like Location is used to redirect subsequent manifest updates.
Are you trying to make Location apply to relative content URLs in the initial manifest?

The Location tag has one or more manifest URL's. The player must test one of them be correct. After that, play the manifest inside that URL.

I'm sorry, this does not seem to be correct behavior for the player.  I don't see anything that says that the Location element should trigger an instant refresh of the manifest.  In fact, if each manifest response contains a Location element, your PR would create an infinite loop.
As far as I can tell, the Location element should affect subsequent manifest requests, but not trigger any immediate requests.  That is the current behavior of Shaka Player, so I don't believe there is any issue with Location that needs to be corrected.
Thanks for contributing!

Hi Joey,
Can you please explain why the MPD below not working on shaka player?
Am I missing something? With my fix, it will work.
On the other hand, infinite loop problem still occurs on my fix.
<MPD mediaPresentationDuration="PT634.566S" minBufferTime="PT2.00S" profiles="urn:hbbtv:dash:profile:isoff-live:2012,urn:mpeg:dash:profile:isoff-live:2011" type="static" xmlns="urn:mpeg:dash:schema:mpd:2011" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:mpeg:DASH:schema:MPD:2011 DASH-MPD.xsd">     <Location>https://dash.akamaized.net/akamai/bbb_30fps/bbb_30fps.mpd</Location> </MPD>
Thanks,
Cemsina

It's because your initial MPD contains no content.  My understanding of the spec is that this is not the correct usage of <Location>.  For this, you should probably just use an HTTP-level redirect.

Besides this, your change has unintended consequences for applications which place a <Location> tag in every update.  This would be completely valid, to redirect on each update to another server.  With your change, that scenario would trigger an infinite loop of rapid requests, which would be a serious bug.


amplify pull doesn't update password criteria on Android

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v19.0.0
Amplify CLI Version
10.8.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Updated Cognito User Pool password criteria (change minimum length, add/remove required character types) in the console
Describe the bug
In an Android project, when updating the password criteria in Cognito, amplify pull does not update the amplifyconfiguration.json with the new criteria.
Expected behavior
amplifyconfiguration.json should be populated with the updated criteria.
Reproduction steps

amplify init in an Android project
amplify add auth, choose default auth settings
See amplifyconfiguration.json password defaults: min length 8, no special requirements
Edit Cognito user pool password requirements
amplify pull, shows update to Auth
No change to amplifyconfiguration.json
amplify pull shows no update to Auth

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @tjleing :wave: thanks for raising this! How were the password requirements updated? Was this modification made through the AWS Console? If so, it would instead be suggested to make this modification by modifying the following keys of your auth resource's cli-inputs.json file:
"passwordPolicyMinLength": 20,
"passwordPolicyCharacters": [],

before
"passwordProtectionSettings": {
	"passwordPolicyMinLength": 8,
    "passwordPolicyCharacters": []
},

after:
"passwordProtectionSettings": {
    "passwordPolicyMinLength": 20,
    "passwordPolicyCharacters": []
},

You can also make granular modifications with overrides, however these changes will not carry to your amplifyconfiguration.json file
import { AmplifyAuthCognitoStackTemplate } from '@aws-amplify/cli-extensibility-helper'

export function override(resources: AmplifyAuthCognitoStackTemplate) {
  resources.userPool.addPropertyOverride('PasswordPolicy', {
    MinimumLength: 10,
    RequireLowercase: true,
    RequireNumbers: true,
    RequireSymbols: true,
    RequireUppercase: true,
    TemporaryPasswordValidityDays: 3,
  })
}


2.1.0 release links

fuse link is pointing at amq online
https://github.com/integr8ly/user-documentation/blame/master/modules/ROOT/pages/release-notes/master.adoc#L146

amq online is using fuse version
https://github.com/integr8ly/user-documentation/blame/master/modules/ROOT/pages/release-notes/master.adoc#L152L154

@briandooley  not sure if these issues are still valid?
I'd suggest checking them on git lab
@austincunningham  as mentioned in readme for repo, this isn't an active repo, we just use it for publishing previews, we're not following issues here

This looks to me like the github has been updated recently. The https://github.com/integr8ly/user-documentation/blame/master/modules/ROOT/pages/release-notes/master.adoc#L146 line just points to a heading.
Nevertheless, I checked. In the preview, the link to fuse online (https://access.redhat.com/documentation/en-us/red_hat_fuse/7.6/) points to the correct docs.
The link to amq online currently is https://access.redhat.com/documentation/en-us/red_hat_amq/{fuse-version}/ .  This happens to go to the correct page as the fuse and amq versions are the same but the {fuse-version} should be removed.

closed out of date


[WIP] Add support for 1.24+

Signed-off-by: Jayadeep KM<EMAIL_ADDRESS>Adding support for k8s 1.24
Major changes

Service account token for dashboard is created using tokenrequest api. Due to this change
Use the ca cert from /var/run/secrets/kubernetes.io/serviceaccount/ca.crt to populate the secret in hub since we don't have a secret for serviceaccount anymore

TODO:

[ ] add some test cases (currently there are no tests for these methods)
[ ] test in 1.25
[ ] test in <1.20 (for backward compatibility)

closing in favor of https://github.com/kubeslice/dev-charts/pull/53


Access request URL (for search params)

It's not clear how, or if it's possible, to access the request URL for the purposes of inspecting the pathname and search params and rendering based on that information.
Is it possible? Are there examples? The use of wouter to accomplish this isn't clear.

Very interesting find, I wasn't aware of this limitation.
It seems this is being tracked in wouter here: https://github.com/molefrog/wouter/issues/58
I'm not sure if atm this can be solved with wouter, but it's worth noting that our V2 release allows you to BYO routing lib.

In v2 this is possible, I've updated our wouter example to include how this could be done. Although, would be far better if wouter had this support baked in.
https://github.com/exhibitionist-digital/ultra/tree/main/examples/with-wouter
The secret sauce is a custom context provider, and some event listening.


Passphrase for imported ssh keys

The guide states:

When using the key pinentry will be invoked to request the key's passphrase. The passphrase will be cached for up to 10 minutes idle time between uses, to a maximum of 2 hours.

I was wondering if there's any way to avoid having to enter a key passphrase (either when using they key, or even when importing it), and rely only on the physical presence of the YubiKey and its PIN.
If so, would it be severely insecure?

As far as I read this section of the guide correctly, it is "only" about importing a SSH key to the GPG agent, and NOT the YubiKey itself. So the imported key is not anyhow related to the YubiKey.
Maybe the section's title should read "Import SSH keys to GPG agent".

True.
My question is if, since the YubiKey is also available, can the passphrase be somehow skipped? Afterall, we are already protected by the key itself and its pin.

If you like to protect your (private) SSH key with a YubiKey and entering the PIN, you need to use a PGP key on the YubiKey and then use the authentication subkey of it for SSH purposes, as stated in this excellent guide. A key that is imported to GPG agent will never be protected by a YubiKey.


Add generic type parameter for useFocusZone container ref

The type of the containerRef returned from useFocusZone is RefObject<HTMLElement>. This prevents it from being assigned to any actual HTML elements, because HTML element ref prop types are invariant[^1]. If you attempt to do the following you'll get a TypeScript error:
const {containerRef} = useFocusZone()

return
...

Type 'RefObject<HTMLElement>' is not assignable to type 'LegacyRef<HTMLDivElement> | undefined'.
  Type 'RefObject<HTMLElement>' is not assignable to type 'RefObject<HTMLDivElement>'.
    Property 'align' is missing in type 'HTMLElement' but required in type 'HTMLDivElement'.

Currently the only workaround is a typecast (containerRef as RefObject<HTMLDivElement>) or defining the ref outside the hook using useRef.
This could easily be fixed by adding a generic type parameter to useFocusZone so that the consumer could define an element type to be used, for example:
const {containerRef} = useFocusZone<HTMLDivElement>()

return
...

[^1]: This is surprising, but it happens because HTML element ref props accept both object and callback refs. Thus they are typed as (with some simplification) (element: T | null) => void | {current: T | null}. The function type makes T contravariant while the object type makes T covariant, resulting in an invariant type that accepts only exactly T. For more details on covariance and contravariance see the TypeScript documentation.

Thanks for reporting. Looks like an open source contributor spun up a PR https://github.com/primer/react/pull/5468 so I'm moving this to "In review" for the team to help get over the line.


Link is not correct (correct page but not correct step)

Hi, the section in this document (bottom of section 6) that reads like this:
certificate information required for the client to authenticate. For steps to export a certificate, see Generate and export certificates for Point-to-Site using PowerShell.
Has a link to another document. However it links to the wrong section in that document. It should point to section and and it goes directly to section 4 (export) ...  It should have linked to section 1 (generate) that is why I could never get this to work until Microsoft support pointed this out.

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

ID: 59e72010-dab4-54d9-1409-c95b0ce60824
Version Independent ID: 0da5450c-6181-1c27-93c0-b0c698d2d598
Content: Connect a computer to an Azure virtual network using Point-to-Site and native Azure certificate authentication: Azure Portal
Content Source: articles/vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@blouwagie  - It actually should point to Export. Right above it, those links should point to generate. I just tested and it seems to work correctly.

I'm confused, both Microsoft support and I thought it went to section 4
where it should have gone to section one.
Bart Louwagie
Holmes, NY
<EMAIL_ADDRESS>On Fri, Feb 8, 2019 at 3:41 PM Cheryl McGuire<EMAIL_ADDRESS>wrote:

@blouwagie https://github.com/blouwagie - It actually should point to
Export. Right above it, those links should point to generate. I just tested
and it seems to work correctly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/24582#issuecomment-461939988,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASWZ9R0Lw2abDMPfAnWep8vXNoIoMHhQks5vLeELgaJpZM4aw8DL
.

@blouwagie - the change has published, so I think we're all set. Thanks for letting me know that it was confusing!

#please-close

Thank you!
Bart
On Mon, Feb 11, 2019 at 12:03 PM Cheryl McGuire<EMAIL_ADDRESS>wrote:

@blouwagie https://github.com/blouwagie - the change has published, so
I think we're all set. Thanks for letting me know that it was confusing!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/24582#issuecomment-462407688,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASWZ9U6z2R2AdNvvHkS7LwR1Bwfw4cWSks5vMaJwgaJpZM4aw8DL
.


[MP-432] fixed up and tested as a cluster

Can you add the ticket number into the PR title and commit message?

dog.. soz I missed it

LGTM :+1:


CI security scan

Description of the changes
CI security scan using GHA and Snyk
PR Review Checklist
Author

[ ] the PR should focus on a single subject. Change only relevant files to the problem you’re working on
[ ] clean and format the code
[ ] add unit tests for your changes and make sure all unit tests are passing
[ ] add a risk label after carefully considering the "blast radius" of your changes
[ ] describe the intent of your changes in the description. don't just rewrite your code in prose
[ ] assign at least one reviewer
[ ] address the feedback
[ ] add a "ready for review" label. Only PRs with this label will be reviewed.

Reviewer

[ ] review code for readability
[ ] verify that high risk behavior changes are well tested
[ ] check license for any new external dependency
[ ] ask questions about anything that isn't clear and obvious
[ ] approve the PR when you consider it's good to merge

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Juan Hernandez seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Create test for parser

I think create test flow from now on is important.
Else the code base will only become more and more complex.

Then we should use CharStream instead of FileStream
About lexer, parser & listener


stm32: adc: Simplify code with dt bindings addition (DNM)

Encode more information in device tree to simplify driver implementation.
This is only POC for now:

Need to extend to other series
Some other data could help to reduce driver complexity

Supersed by https://github.com/zephyrproject-rtos/zephyr/pull/53868


Add compare with object_store in docs

Would love to learn more about the differences between opendal and object_store!
Seems like the ecosystem is adopting object_store more and more but opendal looks easier and with more diversity of connectors.
What are your thoughts on this @Xuanwo?

Thanks for your interest! I will add the doc this week.

Hi, @davidgasquez
I have added a comparison at https://opendal.databend.rs/comparisons/object_store.html.
Please let me know if you want to know more~

I think that's perfect! Thanks @Xuanwo!

Heya @Xuanwo! I think the link broke after moving to the Apache org. Do you know if the md file is still around?

Thanks! Totally missed that. Should've done better and search a bit more. Appreciate the help @suyanhanx!


problem with list rendering

What is &% in the following?
&%default-ul {
  list-style-type: disc;
  margin-bottom: $base-spacing / 2;
  padding-left: $base-spacing;
}

&%default-ol {
  list-style-type: decimal;
  margin-bottom: $base-spacing / 2;
  padding-left: $base-spacing;
}

It does not seem to end up in the comiled css file.

This is confusing me too.
My assumption (which I'm starting to think is wrong) based on the biitters example page is that
ul,
ol {
  list-style-type: none;
  margin: 0;
  padding: 0 0 0  $base-spacing;
  &%default-ul {
    list-style-type: disc;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
  }

  &%default-ol {
    list-style-type: decimal;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
  }
}

would compile to

ul,ol {
  margin: 0;
  padding: 0;
  list-style-type: none
}

ul.default {
  list-style-type: disc;
  margin-bottom: 0.75em;
  padding-left: 1.5em
}

ol.default {
  list-style-type: decimal;
  margin-bottom: 0.75em;
  padding-left: 1.5em
}

That CSS is what is in the example page's style sheet, but not what I'm getting from bitters which is just
ul,
ol {
  list-style-type: none;
  margin: 0;
  padding: 0 0 0 1.5em; }

I'm guessing the SCSS for the example page actually looks like this, not what's in the repo:
ul,
ol {
  list-style-type: none;
  margin: 0;
  padding: 0 0 0  $base-spacing;
  &%default-ul {
    list-style-type: disc;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
  }

  &%default-ol {
    list-style-type: decimal;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
  }
}

ul.default {
  @extend %default-ul;
}

ol.default {
  @extend %default-ol;
}

Yes?

For newbies it'd help if this was better explained, or if bitters _lists.scss was actually what was used on the example page.

@jb510 The Bitters _lists.scss is what is being used on the example page. When using a placeholder selector, selectors that start with % Sass won't compile the styles till it is extended to another non-placeholder selector. So in this case until you extend %default-ul and %default-ol there will be no added CSS output. You can look at the example page scss that was linked above here: https://github.com/thoughtbot/bitters/blob/gh-pages/_sass/_example.scss#L5 In order to show those styles we need to add those selectors otherwise they would look just like the other non-styled lists.
I would encourage you to read the documentation on placeholder selectors here: http://sass-lang.com/documentation/file.SASS_REFERENCE.html#placeholder_selectors_

Kyle. Thanks. I fully understand how it works. I didn't initially, but as you can see in the sassmeister link above I figured it out.  Do you understand why it is confusing to newbies though?
I, and I suspect many, would assume the example page just used _lists.scss.  The output shown on the example page it clearly doesn't.  It uses those extensions (see my sassmeister link above demonstrating the scss that is likely being used on the example page).


Improve the Tolerance of the Wheel Speed Algorithm

As it was noted during today's test #171, the wheel speed sensor frequently failed to read a value due to the shaking of the wheels. Therefore, we want to improve the tolerance of the algorithm so that it does not compromise easily.
Also, it has been brought to attention that although the vehicle was at rest, the program still outputs some random speeds. Further investigation is required.

A Multi-sensor Hypothetical Fusion Inference Algorithm
When there is a huge difference between the readings of different wheel speed sensors, we assert that there is failure. We use other available valid data to infer the speed. If multiple inference suggest speeds that fit in an acceptable range, take the smallest reading the lies in that range as the final output.
Definition of "huge": the difference is greater than the overall variance of the speed sequence.
Implementation
The implementation of this algorithm deeply depends on the utilities introduced in #173. I'm going to make the inferences available without matplotlib.
Little bit concerned about the performance, but should be fine.
@qmascarenhas Please review.

@qmascarenhas This is way too hard and time-consuming to realize. I won't be able to finish it within a week. I propose we go with better mounting methods.

No problem @ATATC - it shouldn't be too difficult to find a way to reliably secure the magnet to the wheel spoke without it twisting due to wheel/spoke vibration. We can postpone this task to after the race.

In my investigation of the zero speed problem (replaying mode really helped), I suspect that it might be caused by the "enhancement" of the wheel speed algorithm introduced 4 months earlier. I'll try to fix that first. I suggest we schedule another test next week before the race.

We can test all we want on the temporary cart setup we have. We need to assign priority to the test drives this week to get the drivers and pit crew race ready. Our work on and with VeC99 is going to have to happen outside of their time with the vehicle until we can assure them that we have a stable solution that will not disrupt their practice routine.
We need to be able to race VeC99 without LEADS so if there is a LEADS catastrophic failure on race day there is no panic.

Do we still have enough time to install the instrumentation system?

Yes! I need to do one more test on the cart with the longer wheel speed sensor wires (those measurements you took on Friday) and we should be good. If you could give me a hand with that this week while I iron out some of the mechanical installation issues, that would be great!

Yes sure. I should be available any afternoon this week.

Wednesday is off. Other days are free.

ok. Let's try to work to the following schedule then:

Tue May 21 3pm - 4:30pm: Test LEADS on cart with the longer wires for the 3 wheel speed sensors and live video stream from OBS to YouTube.
Wed May 22: I will be working on the LEADS mechanicals for integration under the hood of VeC99
Thu May 23: 3pm - 5pm: Final testing of LEADS on VeC99 in simulated racing situation.

Do we have a time schedule for the race day?

Can't see it.

i just updated the comment.

Did u tell Jerry that he needs to come to my place at 7?

No I didn't. Can you sort that out with him directly?


[Workshop page] Indent of the text from the logo is different from the rest in unit "Контакти"

Environment: Windows 10 x86(64), Opera GX 82.0.4227.50
Reproducible: always
Build found: Frontend: gcp-0.0.50, Backend: gcp-0.0.101
Preconditions

Go to main page https://oos.dmytrominochkin.cloud/#/
Find section/group with link to school`s website

Steps to reproduce

Go to details, by clicking on "Детальніше" button
Pay attention to indent of text from the logo in hyperlink to school`s website

Actual result
The indent of text from the logo in hyperlink to school`s website is shorter than indent of rest elements in unit "Контакти"
Expected result
The indent of text from the logo in hyperlink to school`s website is the same to rest elements in unit "Контакти"
User story and test case links
"User story #58" https://github.com/ita-social-projects/OoS-Backend/issues/58
[Test case] (https://jira.softserve.academy/browse/OS-192)
Labels to be added
"Bug", Priority ("pri: "), Severity ("severity:"), Type ("UI, "Functional"), "API" (for back-end bugs).

Verified and closed


Fix exports webpack plugin

Package versions had double quotation marks in them like: ""2.9.0"" So when comparing if a package version ""2.9.0"" >= "2.8.0" it would return false. This means extensions will not be able to be loaded even if the criteria are actually met (have a version greater than what the extension is using).