[Feature] Tooltip for step/"flat" line series aligned to category axis

What problem does this feature solve?
Hi,
I have been using echarts successfully in my project and wanted to do the upgrade from version 3.2.x to latest 5.x. There has been some changes though (i believe in 3.5.0) that caused the following issue for me.
I have a global tooltip with trigger property set to axis, 2 x axes of type category and value and some line series defined on the value axis that share the same start/end points to create "step" effect. In versions below 3.5, when you hover over the chart the tooltip shows value for a single serie:
http://jsfiddle.net/392e0mto/2/
When you move the tooltip between chart "columns" (defined by category axis), you can see the serie value being updated:

This behavior allows me to create custom tooltip formatter and show flat time series values in a tooltip relative to the columns on the main category axis:

However in versions 5.x (in fact any version > 3.5.0) i'm not able to get the "time series tooltip per column" effect because tooltip aggregates multiple points such as [1,40][1,60] and snaps to value axis. I'm not able to determine which point to display in the tooltip relative to the category axis columns. You can see the difference in the following demo:
http://jsfiddle.net/x9ypszuf

What does the proposed API look like?
My question is if there is a way to replicate the same behaviour in latest echarts?
I have tried and played with several options but can't seem to find a way around. I'm stuck and can't upgrade. Any help would be much appreciated.

FIY looks like a duplicate of this feature request can also be found: https://github.com/apache/echarts/issues/15122

@pissang @100pah also this was reported back in 2018: https://github.com/apache/echarts/issues/7543. Is there any chance that this could be addressed in the next release?

+1

+1

Sorry to be late here. Try to set on the second xAxis in the xample
axisPointer: {
  snap: false
}

@pissang thanks for your reply! Unfortunately it has no effect, the behavior stays the same.


train

Hello, I would like to ask you some questions when I execute generation.py. Could you please provide me with the environmental requirements for model execution?
no modele named '_regex'

You can refer to the issue #2 #4 for solutions.


Deleted some irrelevant comments

Hello,
I really like ImageAI, and while I was taking a course about how to use GitHub and create a pull request, ImageAI was the first thing that came to my mind.
I hope that my edit is correct since I thought the lines I deleted are useless even if they get uncommented.
kind regards

Good work. Well done @Samir-atra

Thanks so much.


V2: Guest core-dump support for ukvm

Please see #228  for more details

@mato : Changes are ready for review.

@ricarkol @niks3089 I started reviewing this yesterday, and in the process of trying to figure out what the right split between host-os-dependent and -independent code should be went down the rabbit hole of looking for a codified API/ABI for NT_PRSTATUS, which I found carefully hidden away in <sys/procfs.h>. An actual UNIX API I've never used, which appears to date back to the SVR4 days.
In lieu of an actual review I'm now in the process of developing a V3 using these interfaces, based on your V2, which I will PR shortly. Stay tuned.

@niks3089 @ricarkol See #258. This is not quite ready yet, but the main parts are there, and the resulting core files work fine with GDB on Debian.


Dependence on libicu 56.1

Caffe does not tolerate well when icu is updated to a version later than 56.1 (that is what other conda-forge packages pull as of 20170301). We should build it against that latest version of ICU; need to investigate first what caffe dependence brings icu to the mix.
Current workaround, just pin ICU to 56.1 in the environment.

Closing, as this was a problem with aeon depending on sox and the sox package being broken. It is fixed now and a PR upstream is pending.


docs(examples): modernize website examples.md

One more minor fix: The command that says to run bazel run bazel run //kythe/go/storage/tools:triples should be changed to //kythe/go/storage/tools/triples (slash instead of colon).

PTAL


collide step: group_name with spaces

In my .egg file I have a Group name with spaces. The collide step doesn't find any group there nor the rename step is able to rename it without spaces. Is there the possibility to support group_name with whitespaces too?
collide:
  - group_name: "Tempio Maggiore di Roma"
    method: polyset
    flags: keep,descend

Hi!
I will need the following information for debugging:

The egg file the step operates on. Since you're using the pipeline, it should be available in the intermediate folder. If you do not want to/are unable to provide the full file, you can cut out the unrelated sections.
The pipeline command you run. If you use composer, it can be obtained by setting the environmental variable PANDA_UTILS_LOGGING=1.
The version of Panda Utils used (can be obtained by using pip freeze or similar commands).

(I really should add an issue template with these)

I am going to give you anything you need :)

These are the .obj/.blend/.bam/.egg files within the intermediate directory, along with the model-config.yml file to reproduce the pipeline:
misc.zip
This is the command I ran along with its output:
(panda3D) > python -m panda_utils.assetpipeline input/asset-folder phase_1/models/tiberriver phase_1/maps preblend blend2bam bam2egg group_rename[] collide[] egg2bam
panda_utils.pipeline: INFO     Running Pipeline with parameters: ['preblend', 'blend2bam', 'bam2egg', 'group_rename[]', 'collide[]', 'egg2bam']
panda_utils.pipeline.models: INFO     Asset Folder: Converting to blend: test4_buildings.obj, test4_buildings.obj.mtl, test4_buildings.obj_textures, test4_highways.obj, test4_highways.obj.mtl, test4_highways.obj_textures
DEBUG:BlenderGIS-master.core.checkdeps:GDAL Python binding unavailable
DEBUG:BlenderGIS-master.core.checkdeps:PyProj available
DEBUG:BlenderGIS-master.core.checkdeps:Pillow available
DEBUG:BlenderGIS-master.core.checkdeps:ImageIO Freeimage plugin available
panda_utils.pipeline.models: INFO     Asset Folder: Exporting to GLTF: asset-folder.blend
DEBUG:BlenderGIS-master.core.checkdeps:GDAL Python binding unavailable
DEBUG:BlenderGIS-master.core.checkdeps:PyProj available
DEBUG:BlenderGIS-master.core.checkdeps:Pillow available
DEBUG:BlenderGIS-master.core.checkdeps:ImageIO Freeimage plugin available
panda_utils.pipeline.models: INFO     Asset Folder: Converting to bam: asset-folder.glb
panda_utils.pipeline.models: INFO     Asset Folder: Converting asset-folder.bam from Bam to Egg
panda_utils.converter: INFO     Recompilation not needed!
panda_utils.pipeline.models: INFO     Asset Folder: Adding collisions to asset-folder.egg/Sinagoga: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Asset Folder: Adding collisions to asset-folder.egg/Building0: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Found the named group!
panda_utils.pipeline.models: INFO     Asset Folder: Adding collisions to asset-folder.egg/Building1: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Found the named group!
panda_utils.pipeline.models: INFO     Asset Folder: Adding collisions to asset-folder.egg/Building2: flags=keep descend method=Polyset
lding5: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Found the named group!                                 lding3: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Asset Folder: Adding collisions to asset-folder.egg/Building6: flags=keep descend method=Polyset                                                    lding4: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Found the named group!
panda_utils.pipeline.models: INFO     Asset Folder: Adding collisions to asset-folder.egg/Building5: flags=keep descend method=Polysetlding7: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Found the named group!                                 lding6: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Asset Folder: Adding collisions to asset-folder.egg/Building8: flags=keep descend method=Polyset                                                    lding7: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Found the named group!
panda_utils.pipeline.models: INFO     Asset Folder: Adding collisions to asset-folder.egg/Building8: flags=keep descend method=Polysetlding9: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Found the named group!                                 lding9: flags=keep descend method=Polyset
panda_utils.pipeline.models: INFO     Asset Folder: Copying asset-folder.egg into the dist directory                                                                                rectory
panda_utils.pipeline.models: INFO     Asset Folder: Converting asset-folder.egg to bam
this are the pkgs installed in my venv:
(panda3D) > pip freeze                                                                                lding9: flags=keep descend method=Polyset
numpy==1.24.4
panda-utils==1.5.3                                                                           rectory
Panda3D==1.10.12
panda3d-blend2bam==0.23.0
panda3d-gltf==1.0.1
panda3d-simplepbr==0.10
PyYAML==6.0.1

So there are two issues here:

You're looking for Tempio Maggiore di Roma, but the node name is actually Building Tempio Maggiore di Roma:

However, Panda Utils does not properly purge and reapply the quoting from the node names. This will be fixed in version 1.6 (which is currently in development, and I will be pushing it most likely later today).

There are also multiple nodes with that name, which may be problematic for the collide step. I will check out the file's structure in Blender a bit later due to it being a potential incompatibility (I suspect it won't be, but a check can never be wrong anyway).

So there are two issues here:

You're looking for Tempio Maggiore di Roma, but the node name is actually Building Tempio Maggiore di Roma:

However, Panda Utils does not properly purge and reapply the quoting from the node names. This will be fixed in version 1.6 (which is currently in development, and I will be pushing it most likely later today).
There are also multiple nodes with that name, which may be problematic for the collide step. I will check out the file's structure in Blender a bit later due to it being a potential incompatibility (I suspect it won't be, but a check can never be wrong anyway).

How did you enabled such log level? This is diferent from my output. (I think I was really looking for "Building Tempio Maggiore di Roma") isn't it?

Yeah this is because of the issue with quotes (I'm fixing it as we talk). YAML automatically unquotes any quoted string so value: Building Tempio Maggiore di Roma and value: "Building Tempio Maggiore di Roma" are exactly the same.
My output was from python console running eggtree parser directly, not from the pipeline. But apologies, I see you realized that according to the attached model-config file. So it's just the quote bug that remains.

The potential fix should be now available as a part of the 1.6b3 release (pip install panda-utils==1.6b3). Note that if you rely on fully-transparent vertex coloring in your models (which is extremely unlikely but I'm mentioning it anyway) you will have to make adjustments to your config file.
Since there is currently no tests for the eggtree stuff (I plan to add them when I'm less busy) I'll wait on closing until you confirm the fix works properly.

Since you are already putting your hands in it, I was wondering if the collide step could support fnmatch syntax too, as the group_remove one does, since I need to apply it to every group within an .egg file (made of buildings solely). Is that possible?

looking for Tempio Maggiore di Roma, but the node name is actually Building Tempio Maggiore di Roma

I don't know why am I looking for "Tempio Maggiore di Roma", rather than "Building Tempio Maggiore di Roma"

I derived that from the model-config snippet provided in the issue description, the actual model-config file has the correct name so I think it should work.
As for fnmatch syntax, I can probably add that to a bunch of other commands as well.

Apparently there is a bug in the 1.6b3 version that anything that uses EggString (which includes basically every model since things like UV also use it) broke due to the change. I will yank that version and make a new one.

Alright 1.6b4 should be ready for use, let me know if you encounter any other issues.

That's wonderful: decompiling to .egg, the resulting .bam file, I get the following:
<Group> {
  <Transform> {
    <Rotate> { 90.000001961151 1 0 0 }
  }
  <Group> Sinagoga {
    <Collide> { Polyset descend }
    <VertexPool> vpool-collision.vpool1 {
      <Vertex> 0 {
<PHONE_NUMBER>38672<PHONE_NUMBER>28906 26.0000019073486
        <Normal> { 0.919978022575378 -0.391970068216324 -1.71335550191998e-08 }
      }
      .................

this means you fixed both issues for group name with whitespaces, in the group_rename and collide steps!
Now, since I am waiting for you to release the fnmatch syntax support (💯), I will in the meanwhile develop some sort of .egg file parser to retrieve all the buildings within my .egg files and produce a corresponding model-config.yml with them all!

fnmatch is implemented in 1.6b4 already.


[Feature]:  Support for recurring tasks / reminder with time but no date

Goal or desired outcome of this feature
I want to be able to have the reminder work with recurring task so that when the new task is created by tasks, the reminder is updated with the new date.
Describe the feature
When a task that is recurring is marked as complete and is recurring a new task is created and it has a new due date that matches what the recurrence specifies BUT the reminder has the original date/time.  Not very useful.  I'd propose one of two solutions:

update the date of the reminder to the same date as the due date of the newly created task when a task is created by a task completion.
allow a reminder to have just a time and no date.  take this to mean that the reminder should fire at the specified time as the task due date, or if no due date then "today".

Screenshots, mockups, or videos
No response

I'd like to add I would also like the ability to set how a task recurs. (Day, Bi-Daily, Week, Bi-Weekly, Monthly, etc.)

I'd like to add I would also like the ability to set how a task recurs. (Day, Bi-Daily, Week, Bi-Weekly, Monthly, etc.)

the tasks plugin handles that so just handling task completed and updating the reminder when a task completes would do the trick.  maybe clare who is doing the tasks plugin can give you an idea of how to get notified when a task completes

Understood. Perhaps I shouldn't suggest features that overlap with other popular plugins. If that's the case I apologize.
Unfortunately, I personally don't like how the Tasks Plugin uses Emoji as a required component for its syntax. Hopefully at some point they add in a toggle for text-only syntax; I like typing out everything as I go, without opening dialog boxes or search for emojis (I also realize there's an emoji markdown syntax plugin ala ":emoji_here:").
Thank you for the suggestion, of course.


Class 'Kurt\Google\Analytics\Exceptions\InvalidPeriodException' not found

in Period.php line 95
at Period->validatePeriod(object(Carbon), object(Carbon)) in Period.php line 77
at Period->setEndDate(object(Carbon)) in DatesHandler.php line 51
at Analytics->setEndDate(object(Carbon)) in AdminController.php line 43
at AdminController->__construct(object(Analytics))
at ReflectionClass->newInstanceArgs(array(object(Analytics))) in Container.php line 794
at Container->build('App\Http\Controllers\AdminController', array()) in Container.php line 644
at Container->make('App\Http\Controllers\AdminController', array()) in Application.php line 709
at Application->make('App\Http\Controllers\AdminController') in Route.php line 203
......

Hi, I tried to set startDate and endDate in cunstructor manually, but always ended up getting error above. But after I changed the code of Period.php at line 51 to this: $this->validatePeriod(null, $startDate); the error has gone. so what's going on there?
Edit: o yeah, I also got the result of API call like this.

Why the month numbers of December become 11 instead of 12 and for January also 00 instead of 01?

1- Can you please provide which dates you entered to the constructor?
2- Sadly, the google analytics API returns the months starting from 0. It's confusing but it's how it is. ✌

private $ga;

    function __construct(GoogleAnalytics $ga) {
        $this->middleware('auth');
        $this->ga = $ga;
        $ga->setStartDate(Carbon::parse('7 days ago'));
        $ga->setEndDate(Carbon::parse('yesterday'));
    }

is it what did you mean?

o yeah, I forgot to mention that I'm in Laravel 5.3

Are you sure that the carbon objects are giving you the expected results?

I'm rather confused though, but that's what I get

So, what should I do?
And how should I parse google API return data of Date(2017, 00, 01) in PHP, for instance?

You can simply do +1.

OK, thank you

Wait, I didn't notice the last hotfix. As soon as I found it yesterday, I updated the package to it, but my issue still persist before I change line 51 of Period.php

You should be getting an Exception as expected. Can you show me the error message?

Okay, I got it that date response value like Date(2017, 00, 01) is likely intended to be parsed for Javascript's Date method.
As for the error message I got, it's likely triggered by setStartDate and setEndDate method of $ga instance. So, please just tell me or give me an example how to set start and end date of the analytics data that I want.

Please help I still don't get it to set start date and end date.
I just want to get analytics for past week.


Consolidate divertor heat load models

In GitLab by @j-a-foster on Apr 20, 2023, 13:09
The divwade model needs to be made available for all aspect ratios, currently it's only available for STs.
It would make sense for all divertor heat load models to be called from the same switch i_hldiv so this would require adding the Kallenbach model into divertor.py and adding an option for it to the switch.

I believe the first part of this issue has already been completed. The divwade model is called if i_hldv == 2, independently of the type of device/aspect ratio.

The Kallenbach model has been removed from PROCESS and isn't being reintroduced until open source hydrogenic data can be found. The rest of this issue has already been completed so closing.


Ability to ignore files/directories for rebuilds/compiles.

What problem does this feature solve?
I'm working on a Nuxt module.
I am generating JSON files at build/compile-time.
The JSON files are stored in ~/static/json.
They are generated based on Markdown files stored in the ~/contents directory - which I add to options.build.watch.
I was trying to make it so the JSON is regenerated whenever a file in ~/contents is changed.
But the very act of writing the JSON files to the ~/static/json directory itself triggers a recompile/rebuild itself.
<aside>Also, since it's vaguely relevant, I thought I could perhaps get access to a list of files which have changed (so that I could programmatically determine which files to regenerate instead of blindly regenerating everything). So I looked it up online and found a method of doing so (compiler.watchFileSystem.watcher.mtimes) but I couldn't get it to work (always returns an empty array).</aside>
I tried adding ~/contents/json to .nuxtignore per the documentation but it didn't work - changes to the directory continued to trigger rebuilds.
What does the proposed changes look like?
I'm not sure  how the API should look however Chokidar does have an ignored option and so we just need some way to pass that through, in addition to build.watch.

This feature request is available on Nuxt community (#c9700)

Sorry to be impatient but any thoughts or input on this?
It's holding back development of my module somewhat.
Would be nice to know if it is already possible somehow and I'm just missing something, or if some workaround is possible, or if such a feature makes sense or would even be considered etc.?
Thanks!

I think you need to ignore with a pattern like contents/json/*.json (~ not supported)
Also it is highly recommend using buildDir (.nuxt instead of project to emit this assets)

Hmm, not sure that I did include the ~ in the .nuxtignore but I'll give it a try without and report back.
Also I'll look into emitting the assets to the buildDir. Thanks!

@pi0
It doesn't work with static/json/*.json in .nuxtignore.
And that is not a good solution to my problem anyway because I can't expect every user of my module to add a .nuxtignore file.
What can I do? :frowning_face:

Also is the buildDir solution viable? I load these JSON files at runtime in asyncData. I suppose that is an important detail.

@sustained Indeed that's also considered for module authors and supported. Instead of .nuxtignore, you can push to this.options.ignore array from module.
If loading from asyncData, you have to know build hash (resolve json files with require) otherwise if not possible, yes only solution is static/.

@pi0 Yeah, I tried that before (and just tried it again) and it doesn't work either - the changes are still detected causing an infinite loop.
That's why I requested the feature!

@sustained I'm having the same issue. My Nuxt config file extends the webpack config with a custom plugin that generates files for me on webpack's watchRun hook, which is right after webpack detects a change, but right before it recompiles.
In my case I'm generating files in pages/docs and in assets/json, but the effect is the same—webpack gets caught in an infinite compilation loop.
I tried using the watchers property documented here: https://nuxtjs.org/api/configuration-watchers
// nuxt.config.js

export default {
  // rest of my config

  watchers: {
    chokidar: {
      ignored: [
        'pages/docs',
        'assets/json/**/*.json',
        'node_modules',
      ]
    },
    webpack: {
      ignored: [
        'pages/docs',
        'assets/json/**/*.json',
        'node_modules',
      ]
    }
  }
}

However, this doesn't work. I also tried using build.extend to set webpackConfig.watchOptions directly, but that didn't work either.
Possible root causes I could think of:

Webpack's ignored option doesn't work
Nuxt is overriding user-provided ignored values somewhere
Nuxt is not using user-provided ignored values
All or some of the above? Or something else?

I had the same issue and the following worked for me
nuxt.config.js
export default {
// rest of my config
  build: {
    extend(config,{isDev, isClient}){
        config.watchOptions = {ignored : [
        'dir_to_be_ignored/'
      ]}
    }
  }
}

Also having this issue

Running into the same issues, tried every solution in this thread.
App keeps rebuilding on changes in .git directory.

I started working in a new company and wanted to get familar with a not so big existing vue+nuxt project. I'm working on Ubuntu 20.04. I checked out the project, ran npm i and npm run dev and the console started shouting at me with hundreds of thousands of warnings like this:
Error from chokidar (/path/to/project/node_modules/yarn-or-npm/node_modules/cross-spawn/lib): Error: ENOSPC: System limit for number of file watchers reached, watch '/path/to/project/node_modules/yarn-or-npm/node_modules/cross-spawn/lib'
Increasing the number of file watchers on the OS level is frankly an inacceptable workaround rather than a solution to this problem because it doesn't address the underlying problem that stuff is being watched which most likely is never going to be changed while the app is running locally. Who knows what this does to my system performance?
I found the documentation and discussions about this problem to be a bit all over the place. Multiple solution proposals and config properties exist, like this one or this one, but none of these properties did the trick.
However, after way to much fiddling around, in the end, this worked for me:
// nuxt.config.js

  ...
  watchers: {
    webpack: {
      ignored: /(node_modules)|(.git)/
    }
  }
  ...

This excludes the node_modules and .git folders from being watched, so whenever there is a change in there you would need to restart the app. But IMO this is desired behavior anyway.
Links for reference:

https://nuxtjs.org/docs/configuration-glossary/configuration-watchers/
https://webpack.js.org/configuration/watch/#watchoptionsignored

Has anyone got this to work recently?
I've tried:
 watchers: {
    webpack: {
      ignored: /(node_modules)|(.git)/
    }
  }

extend(config, { isDev, isClient }) {
    config.watchOptions = {
      ignored: ['node_modules/', '.git/'] // and various glob variations like **/node_modules/**/* etc
    }
  }

Fully restarting Nuxt, if I edit a file in node_modules directly it still triggers a rebuild

This is annoying. Can't ignore the .git directory. which causes rebuilds.

This reads .nuxtignore
  watchers: {
    webpack: {
      ignoreInitial: true,
      ignored: require('fs')
        .readFileSync('.nuxtignore')
        .toString()
        .split('\n')
        .concat(['node_modules/', '.git/', 'dist/', '.nuxt/'])
        .filter((v) => v.trim() !== '' && !/^#/.test(v))
        .map(
          (v) =>
            new RegExp(
              v
                .replaceAll('.', '\\.')
                .replaceAll('**', '#')
                .replaceAll('*', '[^/]*')
                .replaceAll('#', '.*')
                .trim()
            )
        ),
    },
  },

For anyone (including future me) looking to solve this. In my case, the .nuxtignore file didn't work, nor did any of the solutions here.
What worked for me was adding an ignore array to the nuxt.config.ts file. I was getting TS errors when using some of the other solutions here.
For reference currently running
Nuxi 3.0.0-rc.12
Nuxt 3.0.0-rc.12 with Nitro 0.6.1
ignore: [
  "path/to/ignore/**"
],

Good luck future Chris.


Have you been able to run the bundle analyzer plugin?

When I configure webpack to use the bundle analyzer plugin, nothing happens. I get can get it to create the json file, but normally after the build, the analyzer plugin starts. But when running under nx-plus/vue, that doesn't happen.
I was wondering if you guys had tried to use it or not.

I must have done something wrong the first time I tried it.
With this configuration:
const WebpackAssetsManifest = require('webpack-assets-manifest');
//const VuetifyLoaderPlugin = require('vuetify-loader/lib/plugin')
const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;
const StatoscopeWebpackPlugin = require('@statoscope/webpack-plugin').default;

module.exports = {
    plugins: [
      new WebpackAssetsManifest({
        output: 'asset-manifest.json'
      })
      //, new VuetifyLoaderPlugin()
      // new webpack.IgnorePlugin({
      //   resourceRegExp: /^\.unit\.ts$/,
      //   contextRegExp: /.*/
      // })
    // , new StatoscopeWebpackPlugin({ analyzerMode: 'json', openAnalyzer: true,  generateStatsFile: true })
      , new BundleAnalyzerPlugin({ openAnalyzer: true,  generateStatsFile: true })
    ]
  }

the analyzer window opens after the build is complete.
I also found that you can run the UI on the generated stats file whenver you want by adding this to your package.json scripts section:
    "analyze": "webpack-bundle-analyzer dist/apps/<app>/stats.json"


error train the model

python35 cudnn5.1 keras2.1.2 numpy (1.14.2)
Traceback (most recent call last):
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 526, in get
value = obj._trait_values[self.name]
KeyError: 'layout'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 526, in get
value = obj._trait_values[self.name]
KeyError: 'kernel'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "E:/AutonomousDriving/AirSimE2EDeepLearning/test2.py", line 122, in
validation_data=eval_generator, validation_steps=num_eval_examples//batch_size, verbose=2)
File "C:\Users\oleg\Anaconda3\lib\site-packages\keras\legacy\interfaces.py", line 87, in wrapper
return func(*args, **kwargs)
File "C:\Users\oleg\Anaconda3\lib\site-packages\keras\engine\training.py", line 2072, in fit_generator
callbacks.on_train_begin()
File "C:\Users\oleg\Anaconda3\lib\site-packages\keras\callbacks.py", line 126, in on_train_begin
callback.on_train_begin(logs)
File "C:\Users\oleg\Anaconda3\lib\site-packages\keras_tqdm\tqdm_callback.py", line 129, in on_train_begin
total=epochs)
File "C:\Users\oleg\Anaconda3\lib\site-packages\keras_tqdm\tqdm_callback.py", line 67, in build_tqdm_outer
return self.tqdm(desc=desc, total=total, leave=self.leave_outer)
File "C:\Users\oleg\Anaconda3\lib\site-packages\keras_tqdm\tqdm_notebook_callback.py", line 33, in tqdm
return tqdm_notebook(desc=desc, total=total, leave=leave)
File "C:\Users\oleg\Anaconda3\lib\site-packages\tqdm_init_.py", line 22, in tqdm_notebook
return _tqdm_notebook(*args, **kwargs)
File "C:\Users\oleg\Anaconda3\lib\site-packages\tqdm_tqdm_notebook.py", line 176, in init
self.sp = self.status_printer(self.fp, self.total, self.desc)
File "C:\Users\oleg\Anaconda3\lib\site-packages\tqdm_tqdm_notebook.py", line 96, in status_printer
pbar = IntProgress(min=0, max=total)
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\widget_int.py", line 57, in init
super(cls, self).init(**kwargs)
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\widget_int.py", line 95, in init
super(_BoundedInt, self).init(**kwargs)
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\widget_int.py", line 76, in init
super(_Int, self).init(**kwargs)
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\domwidget.py", line 90, in init
super(DOMWidget, self).init(*pargs, **kwargs)
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\widget.py", line 184, in init
self.open()
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\widget.py", line 197, in open
state, buffer_keys, buffers = self._split_state_buffers(self.get_state())
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\widget.py", line 291, in get_state
value = to_json(getattr(self, k), self)
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 554, in get
return self.get(obj, cls)
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 533, in get
value = self._validate(obj, dynamic_default())
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\domwidget.py", line 23, in _layout_default
return Layout()
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\widget.py", line 184, in init
self.open()
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipywidgets\widgets\widget.py", line 203, in open
self.comm = Comm(**args)
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipykernel\comm\comm.py", line 56, in init
self.open(data=data, metadata=metadata, buffers=buffers)
File "C:\Users\oleg\Anaconda3\lib\site-packages\ipykernel\comm\comm.py", line 83, in open
comm_manager = getattr(self.kernel, 'comm_manager', None)
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 554, in get
return self.get(obj, cls)
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 533, in get
value = self._validate(obj, dynamic_default())
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 589, in _validate
value = self.validate(obj, value)
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 1681, in validate
self.error(obj, value)
File "C:\Users\oleg\Anaconda3\lib\site-packages\traitlets\traitlets.py", line 1528, in error
raise TraitError(e)
traitlets.traitlets.TraitError: The 'kernel' trait of a Comm instance must be a Kernel, but a value of class 'NoneType' (i.e. None) was specified.

This seems like something is wrong with your Keras install. Can you try reinstalling in a clean venv from the InstallPackages.py?

@mitchellspryn  sorry ,i'm a newer and don't know how to reinstall in a clean env

sorry,i don't use jupyter notebook.I edit it in pychram ,so error

It sounds like your environment is not set up properly. Please follow the instructions that are specified in the "Prerequisites and Setup" section of the main README page here. This explains in detail how to install anaconda and the dependencies.
Also, the tutorial files are jupyter notebooks. AFAIK, they won't work directly in pycharm unless you convert them to standard python files. Also, I don't know how pycharm interacts with anaconda virtual environments - you're probably better off just using the notebooks. Is there a specific reason you're trying to use pycharm?


from_source.md

Noticed from_source.md file is referenced in SUMMARY.md but was missing from the repo.
I just ran this sequence of commands to install difftastic on Ubuntu, hopefully they are general enough to cover most platforms.

Argh, I moved the content and never checked in the new file! Thanks for the heads up, this should now be fixed.
By the way, if you'd like to contribute Ubuntu install instructions to the manual, that would be super helpful :)


Sporadic failure of agent queries when multiple tool calls are involved

Describe the bug
I keep running in into this error when using the openai agents:
> cargo run
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.09s
     Running `target/debug/t`
Favorite food tool is called
Date tool is called
thread 'main' panicked at src/main.rs:77:19:
Error invoking LLMChain: AgentError("Error in agent planning: Chain error: LLM error: OpenAI error: invalid_request_error: Invalid parameter: messages with role 'tool' must be a response to a preceeding message with 'tool_calls'. (param: messages.[5].role)")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

And sometimes it works:
[I] niklas@nslaptop /t/t (prod)
> cargo run
   Compiling t v0.1.0 (/tmp/t)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.09s
     Running `target/debug/t`
Date tool is called
Favorite food tool is called
Result: "- The name of the current directory is `/tmp/t`. - Today's date is the 25th of November, 2025. - The favorite food is Pizza."

To Reproduce
I've set up a minimal project based on this example: https://github.com/Abraxas-365/langchain-rust/blob/main/examples/open_ai_tools_agent.rs
Cargo.toml:
[package]
name = "t"
version = "0.1.0"
edition = "2021"

[dependencies]
async-trait = "0.1.82"
dotenvy = "0.15.7"
langchain-rust = "4.4.2"
serde_json = "1.0.128"
tokio = { version = "1.40.0", features = ["full"] }

main.rs
use std::{error::Error, sync::Arc};

use async_trait::async_trait;
use langchain_rust::{
    agent::{AgentExecutor, OpenAiToolAgentBuilder},
    chain::{options::ChainCallOptions, Chain},
    llm::openai::OpenAI,
    memory::SimpleMemory,
    prompt_args,
    tools::{CommandExecutor, DuckDuckGoSearchResults, SerpApi, Tool},
};
use serde_json::Value;

struct Date {}
struct FavoriteFood {}

#[async_trait]
impl Tool for Date {
    fn name(&self) -> String {
        "Date".to_string()
    }
    fn description(&self) -> String {
        "Useful when you need to get the date,input is  a query".to_string()
    }
    async fn run(&self, _input: Value) -> Result<String, Box<dyn Error>> {
        println!("Date tool is called");
        Ok("25  of november of 2025".to_string())
    }
}

#[async_trait]
impl Tool for FavoriteFood {
    fn name(&self) -> String {
        "favorite_food".to_string()
    }
    fn description(&self) -> String {
        "Returns the favorite food".to_string()
    }
    async fn run(&self, _input: Value) -> Result<String, Box<dyn Error>> {
        println!("Favorite food tool is called");
        Ok("Pizza".to_string())
    }
}

#[tokio::main]
async fn main() {
    dotenvy::dotenv().ok();
    let llm = OpenAI::default();
    let memory = SimpleMemory::new();
    let serpapi_tool = SerpApi::default();
    let duckduckgo_tool = DuckDuckGoSearchResults::default();
    let tool_calc = Date {};
    let farvorite_food = FavoriteFood {};
    let command_executor = CommandExecutor::default();
    let agent = OpenAiToolAgentBuilder::new()
        .tools(&[
            Arc::new(serpapi_tool),
            Arc::new(tool_calc),
            Arc::new(command_executor),
            Arc::new(duckduckgo_tool),
            Arc::new(farvorite_food),
        ])
        .options(ChainCallOptions::new().with_max_tokens(1000))
        .build(llm)
        .unwrap();

    let executor = AgentExecutor::from_agent(agent).with_memory(memory.into());

    let input_variables = prompt_args! {
        "input" => "What the name of the current dir, And what date is today, and what is the favorite food?",
    };

    match executor.invoke(input_variables).await {
        Ok(result) => {
            println!("Result: {:?}", result.replace("\n", " "));
        }
        Err(e) => panic!("Error invoking LLMChain: {:?}", e),
    }
}

Are you using open ai via local llm or open ai? I have noticed that using local llm, it is not good based on the model.
At some point it might be worth using function calling directly instead for tools for better reliability given that even local llms are good at this now.

I'm using the openai API, mostly gpt4o mini for testing, but it has also happened several times using gpt4-o

I'm seeing the same thing.

Please try the latest main branch. I was able to consistently get the output correctly with local llm with qwen2.5 but not with llama3.2. Do make sure the model you choose is good with function calling.
Thanks to @chirino for the fix!


FEATURE REQUEST: Support for Pure Neural™ Machine Translation

SYSTRAN going to making neural machine translation.
https://demo-pnmt.systran.net/production
I think it have great translate quilty.
So, can you support this translator?
Thank you for reading >_<

I second this idea. SYSTRAN is very good for zh->en, probably second after Baidu.

After checking http://opennmt.net/  I ended up here. It'd be great to have it implemented.


[iOS] ！！！ Apple review was rejected, weex version is 0.28.0

Could it be because of method naming?

关注

关注。
希望看到 owner 对 https://developer.apple.com/news/?id=09062019b 的评论

This is the offical comment of such issue.
Highlight,

"This update has nothing to do with Weex Apps, but Apps that people try to load from a remote server. Try not to load code from a server if your App(s) falls into the case mentioned above”.


[Usability] Removing a central node does not remove the neighbors

Community Note

Please use a 👍 reaction to provide a +1/vote. This helps the community and maintainers prioritize this request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Describe the bug
A clear and concise description of what the bug is and the environment/context.
There was an expectation that removing a central node would also remove all the connected neighbors. Now it just shows all the previously connected objects as singletons in the view.
To Reproduce
Steps to reproduce the behavior:

Add a node that has multiple neighbors to Graph View on Graph Explorer
Double-click to expand.
Select the original node in Step 1 and click delete.
See that the node's neighbors are left.

Expected behavior
Provide an option to delete node and its neighbors or something similar.

This is a tricky user experience situation to consider.
Let's say I have a graph that looks like this:
flowchart TD
   a(A)
   b(B)
   c(C)
   a --> b
   a --> c

If we delete A then it might make sense to delete B and C as well.
What happens if we instead remove B or C instead of A? Would A be removed since it is a neighbor?
Then let's consider a barely more complex example:
flowchart TD
   a(A)
   b(B)
   c(C)
   d(D)
   a --> b
   a --> c
   b --> d

What happens when I remove A?

A, B, C are removed leaving only D
All nodes are removed

Even if we could decide on a proper approach or algorithm, it is asking a lot of the user to understand the rules around removing nodes.
Preferred Solution
I think the core ask of this feature request is that it is too difficult to remove groups of nodes that are related to each other.
If I'm correct in that assumption, a better approach might be to improve the selection mechanisms. If we do that, the user has the option to more easily select multiple nodes and delete them as a group.
Ideas for selection mechanisms could include:

Select one hop neighbors of selected node
Select all related neighbors and their neighbors of the selected node
Select all nodes matching the type of the selected node


Fix check url

Overview
This PR fixes the backslash check url that causes errors in windows.

Pull Request Test Coverage Report for Build 132

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 131:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


remove nested touchable component to avoid conflict on eject

Description
This module contained an unnecessary touchable opacity component. This has potential to cause conflict with touch events. This component will stop working if the project is ejected from expo.
On what platform have you tested the change?

[x] Android - Emulator
[x] Android - Physical device
[x] iOS - Emulator
[x] iOS - Physical device

Screenshots
Please attach screenshots showing the change if relevant
Checklist

[ ] I have updated mockServer
[ ] I've added analytics as relevent
[x] I have run npm test
[ ] I have run npm run test:i18n

Out of scope and potential follow-up
Is there any related changes that you plan to do in a follow-up PR or voluntarily excluded from the scope?

Tested on android . looks good!


DKIM

Relates to #53
User story

As a mailserver admin I'ld like to use the webinterface to create DKIM keypairs so that I don't have to use the terminal.
As a mailserver admin I'ld like the webinterface to guide me regarding the dns records that need to be set.
As a mailserver admin I want the webinterface to check my domain if I have the dns records properly set up
As a mail sender I want to have my mails signed automatically with my DKIM keypair, so that the receiver is able to verify the source of that email.

Hi @jeboehm,
In my opinion, as one of the core functions of the mail server, the strategy about do the dkim and spf or dmarc ... should achieve the most basic functions in the clearest steps based on the minimum components.
If we need a better experience or more dream story in future, we can call that basic function with a higher level tool at a higher level of perspective.
Let me say it directly that Is it possible to consider to create DKIM keypairs or spf? with simple command line interface?
Please forgive my English level, thank you for your code.
FYI: https://github.com/tomav/docker-mailserver/issues/975#issuecomment-415992417 .

Hey @aaronchn
DKIM support is now added to the current master branch. It is completely configurable via the management interface. Feel free to try it out!
I appreciate your feedback. :)

Hi @jeboehm
To genarate the default DKIM setting for the current domain is a better idea?
With your solution user have to enable Web service If they want to use DKIM feature, this is not they wanted sometimes.
Here is my scrawl that I want to try it in entrypoint.sh with Filter service, but encounter permitted error.
if ! [ -f /media/dkim/dkim_selectors.map ]
then
 chown -R rspamd /media/dkim
chmod 777 /media/dkim
touch /media/dkim/dkim_selectors.map
echo "${DOMAIN} ${CURDATE}" > /media/dkim/dkim_selectors.map
rspamadm dkim_keygen -d ${DOMAIN} -s ${CURDATE} -k /media/dkim/${DOMAIN}.${CURDATE}.key > /media/dkim/${DOMAIN}.${CURDATE}.pub
echo "DKIM public key has been generated:"
cat /media/dkim/${DOMAIN}.${CURDATE}.pub
fi
Honestly, I don't have much skill in this area. If my suggestion is valuable, please consider updating your code. If my suggestion is not feasible, if you are willing , Can you try to guide me how to solve this problem?
Thanks!


Broken link to calendar ICS file

https://github.com/eclipse-tractusx/eclipse-tractusx.github.io/blob/d789b216e1f3f5cb5aaa498854db750463a54414/community/open-meetings.mdx#L13
On the rendered website the link to the calendar ICS file is broken; links to https://eclipse-tractusx.github.io/community/meetings/alignment-and-planning-trace-x.ics. Working link is https://eclipse-tractusx.github.io/meetings/alignment-and-planning-trace-x.ics
//CC @stephanbcbauer

Thank you very much for this issue. We should find a fix for it. Propably just using
meetingLink="/meetings/alignment-and-planning-trace-x.ics"

instead of

meetingLink="../meetings/alignment-and-planning-trace-x.ics"


[Bug]: document page is not loading on the small screen and gets a 404 error.

What happened?
I am getting errors on the small screen on the document page.
Add screenshots

What browsers are you seeing the problem on?
Chrome
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Duplicate of https://github.com/priyankarpal/ProjectsHut/issues/484


python311Packages.aiowithings: init at 0.3.0

Module to interact with Withings
https://github.com/joostlek/python-withings
Description of changes

Things done

Built on platform(s)

[ ] 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/)
23.11 Release Notes (or backporting 23.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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 260635 run on x86_64-linux 1

2 packages built:

python311Packages.aiowithings
python311Packages.aiowithings.dist


Multiple sp same entityid solution

This is a minimal change required to provide at least the possibility of supporting multiple SP entries with the same entity id.
It's required specifically to support multiple integrations with AWS services which all use th same entity_id, but it's not possible (or logical) to create multiple ServiceProvider instances with the same entity-id. So the solution is to add an extra field in an overridden ServiceProvider instance e.g. real_entity_id which takes precedence if provided:
def get_entity_id(self):
    return self.real_entity_id or self.entity_id

The entity_id field can then be used as a lookup/alias field, e.g:
/idp/sso/init?sp=aws-quicksight
/idp/sso/init?sp=aws-appstream
For each ServiceProvider instance the entity_id would hold the alias, e.g aws-quicksight or aws-appstream whilst the real_entity_id fields would be set to 'urn:amazon:webservices'

Codecov Report

Merging #124 (51bd923) into master (0b43257) will increase coverage by 0.16%.
The diff coverage is 97.87%.

@@            Coverage Diff             @@
##           master     #124      +/-   ##
==========================================
+ Coverage   93.10%   93.27%   +0.16%
==========================================
  Files          10       11       +1
  Lines         682      714      +32
==========================================
+ Hits          635      666      +31
- Misses         47       48       +1

Impacted Files
Coverage Δ

djangosaml2idp/views.py
87.06% <87.50%> (-0.27%)
:arrow_down:

djangosaml2idp/admin.py
100.00% <100.00%> (ø)

djangosaml2idp/forms.py
91.66% <100.00%> (ø)

djangosaml2idp/idp.py
100.00% <100.00%> (ø)

djangosaml2idp/models.py
94.83% <100.00%> (+0.53%)
:arrow_up:

djangosaml2idp/settings.py
100.00% <100.00%> (ø)

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 0b43257...51bd923. Read the comment docs.


Develop

Download the current layout & upload a custom one

Sure, i am with you. Thank you for picking these up.


add rule for legend

It's a good practice to prefix the legend with the instance ID, so that dashboards can show all instances, or only a selected one

Yes, I agree with @rgeyer , as there are cases when metrics are aggregated by job or cluster, or something else, effectively dropping instance label. Therefore it would be real challenge to enforce such rule. As a general guideline, it would be nice to have this reminder for legend.

Hello @zeitlinger.
I'm doing some much-overdue maintenance and housekeeping here. Do you still have cycles to look at this?
Or perhaps it's best we close it?

let's close it - the pr is probably out of date


MODE -k and -l

I was following the Evaluation form, So everything is working
we have couple of error with two modes -l and -k are not working properly
-l
If I am in NC and I put MODE #channel -l, it quit the server.
the same happened in irssi but it auto connect again is kind of weird
-k
and if I put NC MODE #channel -k pass I give this result ::c3r1p6.hive.fi 421 *MODE :Unknown command
and in irssi does not work either

<EMAIL_ADDRESS>JOIN #hola
:c2r4p3.hive.fi 331 hola #hola :No topic is set
:c2r4p3.hive.fi 353 hola = #hola :@hola
MODE #hola +l 3
<EMAIL_ADDRESS>MODE #hola +l 3
MODE #hola -l
c2r4p3 :: Documents/_ft_IRC_/irc_working_git ‹90-testcommand-password-user*› %

Debug: Server::loop: received message from client on fd 4: MODE #hola +l 3
Debug: Client::appendToSendBuffer: appending message to sendBuffer for nick hola (excl.CRLF<EMAIL_ADDRESS>MODE #hola +l 3
Debug: Server::sendFromBuffer_: sent 38 bytes to client on fd 4
Debug: Server::recvToBuffer_: received a packet of 15 bytes from client on fd 4
Debug: Message::deserialize_: got prefix_:
Debug: Message::deserialize_: got command_: MODE
Debug: Message::setParameters_: got parameters_ (count): 2
Debug: Server::loop: received message from client on fd 4: MODE #hola -l
Error: Server::loop: out of range exception for fd 4: vector
Debug: Server::disconnectClient_: disconnecting client on fd 4
Debug: Client::unrecordMyChannel: nick hola unrecorded channel #hola
Debug: Channel::partMember: client hola was an operator, removing
Debug: Channel::setOperatorStatus: operator status removed from hola in channel #hola
Debug: Channel::partMember: no operators left, a new operator should be assigned: #hola
Debug: Channel::partMember: client hola parted from channel #hola
Debug: Channel::partMember: no members left, deleted channel: #hola
Info: Clients remaining on server: 0


test(test): fix path to fixtures, fixed #13

Coverage remained the same at 100.0% when pulling 4ab8dddb1b1c7b9cd6e98a828c8d0720bcfbd674 on milestone-0.0.3 into 747132d7498cb729581c470f92c6323e45b8b382 on master.

Coverage remained the same at 100.0% when pulling 4ab8dddb1b1c7b9cd6e98a828c8d0720bcfbd674 on milestone-0.0.3 into 747132d7498cb729581c470f92c6323e45b8b382 on master.


Shrink Koa's support to Node.js' currently supported versions

I'm starting a new project today with Koa and I noticed it "requires" Node.js v7.6 in order to work. Well, since the Node.js' 7th version is far gone - with the 10th one being the oldest still "active" (maintenance patches only) and the 12th being the current LTS, maybe it's time to update Koa's supported Node.js versions.
Is there any good reason to not deprecate Koa's support for Node.js versions prior to the LTS one?
PS: I see there's #1502 that went over this topic before, but it seemed the approach took by its author was a bit aggressive, and the matter didn't have a chance to be taken seriously.

Sorry for those who got notified by email with a very short description - I hit the Create Issue button way sooner, accidentally. 😅

Is there any good reason to not deprecate Koa's support for Node.js versions prior to the LTS one?

To upgrade, we need to bump semver. If you update the minimum requirements we'd be breaking peoples code. This has been talked over in numerous tickets so I'm going to close this one.

@miwnwski thank you very much for giving me proper context!


feat: add node v12.0.0 & electron v5.0.0

Yesterday Node v12.0.0 was released and today Electron v5.0.0 was released. I've attempted to update the targets in this project to reflect this.

Oops -- just saw #62. This is a duplicate.


Fix typo in documentation

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[release-0.1] :book: Update readme file

This is an automated cherry-pick of #5
/assign furkatgofurov7

/milestone v0.1


How to download on windows 8.1

How to download on windows 8.1
It really helps me alot

I think your best bet would be try following the guide for installing on Windows 7

It's working thx


API for generating OSCORE masterkeys

Adds the oc_gen_masterkey which uses a securely seeded PRNG to generate masterkeys suitable for OSCORE encryption.

~format


Ability to change name of Tuner

Is your feature request related to a problem? Please describe.
I am running 2 instances of Xteve in docker. You can trick Plex to run 2 instance of DVR by opening 2 windows and adding a DVR in each one. It works.
Plex errors our on the 2nd Xteve tuner as it has the same name as the 1st.
Describe the solution you'd like
I have accomplished this in telly before, but it allows you to change the tuner name.
I much prefer Xteve.
Add the ability in one of the .json file to change the tuner name.
I tried manually changing the UUID, but doesn't seem to work.

Do you mean that name?

Interesting suggestion....Where does xTeVe get the name for the Tuner? There's that pms.json file....what does that do?

Yes, that name.
I am guessing that is why Plex won't allow me to add 2 DVRs, as they have
the same name from 2 instances of xteve.
On Sat, Feb 22, 2020, 2:37 PM xteve-project<EMAIL_ADDRESS>wrote:

Do you mean that name?
[image: Auswahl_003]
https://user-images.githubusercontent.com/53275662/75098146-f28ba880-55b2-11ea-90eb-b90fd8dd2c16.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xteve-project/xTeVe/issues/93?email_source=notifications&email_token=AAWFPNRZPPNKBR64IDMPPQTREF5JHA5CNFSM4KZKSXW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMVIYPQ#issuecomment-589990974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWFPNUWH34AFBP6XSRW2FDREF5JHANCNFSM4KZKSXWQ
.

This is not needed, I figured it out, so this can be closed.
I tried changing the uuid before but it didn't work, but I only added characters to the end so it must have ignored those. I changed the uuid but kept it the same length, and now it works, I can add 2 tuners. Thanks.


Add customizable singularization rules

Since updating to the kotlin codegen, we've run into lots of issues with bizarre singularization in our project. Examples include Pies -> Py, Ctas -> Ctum, and Slice -> Slouses. Another user opened an issue to report this problem a while back: #1686.
This PR addresses the reality that it is impossible to accurately model the English language in a project like this. Additionally, any fixes to the Singularization rules would end up breaking existing codebases, which isn't ideal. Rather than adding crazy complicated NLP features to the library (which would still have issues), I opted to instead allow users to define custom singularization rules at the project level. These custom rules will take priority over any of the singularization rules built into the plugin. Example usage from our project based on this fork follows:
    apollo {
        generateKotlinModels = true
        customSingularizationRules = [
            "(slice)\$": "\$1",
            "(pie)s\$": "\$1",
            "(cta)s\$": "\$1",
        ]
    }

@EricKuck: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

Just pushed a commit with debug things removed. Happy to change the other things if desired as well.

Sorry I'm a bit late to the party but why not disabling singularization altogether ? Is there a specific reason it is needed ?

I don’t really know why it’s included, but since a fair amount of work went into singularization on both iOS and Android, it seemed like it was a key feature of the library. If disabling it altogether is the preferred method of fixing this problem I’m happy to open another PR that does that instead.

ping @sav007. Wouldn't it be simpler to allow disabling singularization altogether ?

While I’m still happy to open a different PR to disable singularization altogether, it seems to me that there are two possible scenarios here, neither of which would be addressed by making it disableable.

Singularization is a useful feature of the library, in which case it would be unfortunate if people had to opt out if it entirely due to a handful of mistakes it makes.

Singularization isn’t useful, in which case it should be removed from the library, or at least off by default.

Given that someone spent a decent amount of time adding singularization, it seems as though #1 is believed to be the case. If this is correct, shouldn’t we work to make it accessible to everyone instead of telling people they can’t use it if their schema contains models with names it doesn’t work with?

I'm wondering if we're not victims of the sunk cost fallacy here. If we're in case #1, there surely was a reason but I'd like to find out before we invest even more and make any further decision even more complicated.

So I took some time to talk to other client devs at Apollo about this and the much much much easier method of doing this is using aliases when requesting fields, then using the alias to generate the customized field name.
Y’all are very correct about trying to singularize things ourselves being error prone and getting into some NLP stuff that’s waaaay out of scope.
Recommendation would be to deprecate and later remove this feature in favor of aliases on individual fields going forward, particularly since this gives developers more control about when this is applied and when it’s not.

The idea of developer-provided aliases makes a lot of sense to me (much better than trying to fix errors after they've popped up!). Given that this issue is creating some super wacky code in our project, I'm fully on board with opening another PR with whatever suggestions we decide on.
Is there consensus for the alias idea in place of singularization? If so, what would the plan for deprecating singularization be? On one hand, removing it right now would break people's codebases. On the other hand, it's fairly buggy and will continue creating issues for people moving from Java codegen to Kotlin codegen until it's gone.

In terms of how other libraries in the Apollo Comic Universe™ handle it, aliasing instead of trying to do NLP is definitely the strategy we plan to use going forward.
In terms of how to deprecate it in a way that makes sense...uhhhhhhhh.... sprints away leaving @sav007 and @martinbonnin to answer this question

Regarding deprecation, what about adding CompilerParams.useSingularization to the incubating gradle plugin
  /**
   * Whether to singularize fields
   */
  val useSingularization: Property<Boolean>

We could then either:

leave it true by default with a warning that it will change in the future.
or change it to default to false as soon as 1.3.0 is released.

I think I would prefer 2. if users will need to update their code eventually, the sooner the better. To be nice, we could even check if any type in the schema would be impacted based on the current rules. If there are, fail early with a nice error message like:
singularization is disabled by default since 1.3.0, to keep your code compatible, please add this to your build.gradle file:
apollo {
   useSingularization.set(false)
}

This sounds like a good plan to me.
I'm a little unclear what you mean about failing early though. If we error out on detecting a type that would be affected by the change, the only way to get your code to compile again would be to re-enable singularization.

If we error out on detecting a type that would be affected by the change, the only way to get your code to compile again would be to re-enable singularization.

I was thinking that if we detect an affected type and compilerParams.useSingularization is not explicitely set, we throw an Exception. To make the exception go away, users would have to explicitely set useSingularization. Thinking about it again, this will also affect new users so it's not ideal but maybe an acceptable middle ground between giving existing users some context about the required changes and ease of use for newcomers ?
Also, I'm not sure how many schemas in general are affected by this. Is this a corner case or would 90% of the schemas contain types affected by singularization ?

Hey folks, TBH this singularization is pain for a long time. It works great in very simple cases but but awful in corner cases (I wish this feature was never introduced at first place).
I think introducing new flag useSingularization with default value false in incubating gradle plugin makes totally sense to me. And I agree  with @martinbonnin we should remove it altogether in future so if user still uses it useSingularization=true we can produce warning.

I think overall the plan looks good. I just want to give 1 more suggestion with the goal to keep things simple.
What about removing it all together (without any Gradle flag) but still generate them with deprecated warning? In generated Kotlin code, we can even provide a quick fix for the users and they can fix them just using Option + Enter.

Opened a new PR, which adds the flag for disabling singularization altogether: https://github.com/apollographql/apollo-android/pull/1880


xdebug not actived

Description:

Expected Behavior:

Context information:
Output of git rev-parse HEAD
{paste here}

Output of docker version
{paste here}

Output of docker-compose version
{paste here}

System info: Mac, Windows or Linux. Include which disto/version
{paste here}

Steps to reproduce the issue:

Stacktrace & Additional info:
{paste here}

Xdebug not active after run container. But I found fix for the bug:
[8] Log opened at 2021-07-04 15:26:59 [8] I: Connecting to configured address/port: host.docker.internal:9000. [8] W: Creating socket for 'host.docker.internal:9000', getaddrinfo: Invalid argument. [8] E: Could not connect to client. :-( [8] Log closed at 2021-07-04 15:26:59
Fix:
Please master edit xdebug.ini and comment about edit remote hot in xdebug.ini for anyone know.
Find my ip address ubuntu:
ifconfig

xdebug.remote_host="my ip address"
Ex: xdebug.remote_host="<IP_ADDRESS>"
Edit file:
xdebug.remote_host="my ip address"
xdebug.remote_autostart=1
xdebug.remote_enable=1
xdebug.remote_log="/var/www/xdebug.log"
`


Examples in README.md no longer work

On Julia v0.3.11 or greater, putting the following into the command line produces an error:
julia> using ObjectiveC

julia> @classes NSSound
ERROR: Couldn't find class NSSound
 in error at ./error.jl:21
 in call at /Users/rje/.julia/v0.5/ObjectiveC/src/primitives.jl:46

julia> using ObjectiveC, Cocoa
ERROR: Cocoa not found
 in require at loading.jl:47

Please note, this occurs after adding the change in my accompanying pull request.
I am not sure if this is because my Mac is not properly configured, something changed with recent Mac updates, or something changed in Julia.
Best,
Rob

This is fixed in pull request #7.
Best,
Rob


Support dictionary encoding with bitpacked indices

Hi,
I would like to explore enhancing the Lance v2 format's dictionary encoding by integrating bitpacking to further reduce storage space. For instance, in a string array with 50 unique values, the default dictionary encoding would use an uint8 index. However, since 50 unique values can be represented with 6 bits (2^6 = 64 > 50), we could employ bitpacking to store dictionary indices in 6 * num_of_rows bits rather than the current 8 * num_of_rows bits.
I'm interested in working on this enhancement, but I want to ensure that it aligns with the project's evolution and avoids introducing code duplication. In reviewing the codebase, I noticed that while BitpackedArrayEncoder (located in lance-encoding/src/encodings/physical/bitpack.rs) exists, it is not currently in use. Additionally, the BitpackingBufferEncoder, which was introduced in PR #2333, was later removed for some reason.
I would appreciate insights on the following:

Is such an enhancement desirable for the Lance v2 format?
Do you have any suggestions on how to introduce bitpacking for dictionary encoding in a way that avoids code duplication and aligns with the current architecture?

Thanks.

Is such an enhancement desirable for the Lance v2 format?

Yes, this is something we want.

BitpackedArrayEncoder (located in lance-encoding/src/encodings/physical/bitpack.rs) exists, it is not currently in use

It's not in use as it isn't yet stable and thoroughly tested and still under development somewhat (https://github.com/lancedb/lance/pull/2912) and (https://github.com/lancedb/lance/pull/2886).  However, I see no problem with connecting it up to be used as long as it's behind a 2.1 feature gate (this is how FSST is configured right now).  The spot where we pick which encoding to use is https://github.com/lancedb/lance/blob/5606b170a19f6ef3f8294a370395bf767655238d/rust/lance-encoding/src/encoder.rs#L211

Additionally, the BitpackingBufferEncoder, which was introduced in PR https://github.com/lancedb/lance/pull/2333, was later removed for some reason.

It became BitpackedArrayEncoder.

Do you have any suggestions on how to introduce bitpacking for dictionary encoding in a way that avoids code duplication and aligns with the current architecture?

I think we just need to choose it, as mentioned above.  We should use bitpacking in choose_array_encoder whenever:

The type is integral, or temporal
The version is 2.1 or higher
Bitpacking can actually provide an advantage

I believe there is logic to do it here: https://github.com/lancedb/lance/pull/2886/files  So you might try checking out that PR and testing if it works.  It should automatically start using bitpacking for dictioanary indices since we call choose_array_encoder to find the best encoding for the indices.  You'd just need to checkout that PR and then specify 2.1 as the file version in python:
from lance.file import LanceFileWriter

with LanceFileWriter("/some/path.lance", version="2.1") as writer:
  ...

I don't think we have any tests specifically around dictionary + bitpacking (all the bitpacking unit tests focus on integer data).
Things that still remain to work on:

We don't have any (intentional) tests of dictionary + bitpacking.  I suppose, once bitpacking is enabled by #2886 then some of our existing dictionary tests will probably test this.  It wouldn't hurt to have a few python tests for dictionary encoding
Our use of dictionary encoding is still pretty conservative at the moment.  We only use it if there are fewer than 256 keys and only for the string type.  We need to support dictionary encoding for more types (large string, binary, large binary) and we should enable it with uint16 keys if it makes sense.

Do you have any suggestions on how to introduce bitpacking for dictionary encoding in a way that avoids code duplication and aligns with the current architecture?

there might be other issues come up when directly use choose_array_encoer's data_type parameter to do encoding selection, reference: https://github.com/lancedb/lance/issues/2927


Mh death crawl feat

I don't see this as being a very popular feat, since nobody plans to get downed, but it could be interesting nonetheless.

Prone movement happens to be the same speed limitations as this ability. I suggest lowering the speed cap to 3.
In light of the fact that a player that goes down is more likely than ever to die (with the up and coming changes to death saves), and the fact that this feat would be more rarely used, I think the Nanite cost should be removed. To still have limits, you could put in a Max of 2 feat uses per instance of being downed, or just 1 use of the feat per turn.
If my above argument isn't compelling, please consider the following: if the player has no nanites left in their pool and goes down, then the feat does nothing. So, then, a rarely used feat has a high cost and moderate potential to have no effect at all (especially if you are a mage getting picked off in the middle of a fight). Also, the feat has a payoff that is only beneficial if you have teammates who will help you/be able to help and if you can reach them before you die. I'd consider that feat to be underpowered.

(I hope that didn't come across as too critical. I think the idea of this ability is great.)

I think it's reasonable to leave the crawl speed the same? I see your point about removing the nanite cost.

I think it's reasonable to leave it the same. My comment is mostly from a realism perspective.


fix: sync native auth state more frequently for deeplinks

The type of this PR is: fix
This PR resolves MOPLAT-140
Description

Deeplinks are handled on native side of code on iOS, before we route to a deeplink we check the auth state (token, user, expiration), if it is valid we go ahead with the deeplink. If it is not we do nothing. Previously we were syncing this auth state from js side only on sign in. That means if anything goes wrong (e.g app is quit before the token syncs) deeplinks won't work for that user until they sign out and in again, something users probably don't do very often. This instead adds a new hook in the main app, that syncs the token state any time: 1) the app is killed and reopened 2) the token or other auth data changes. That way if something does go wrong there are more chances for it to be corrected.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Mitigation for deeplinks breaking for some users - brian

Android user-facing changes

Dev changes

This PR contains the following changes:

iOS user-facing changes (Mitigation for deeplinks breaking for some users - brian)

  Generated by :no_entry_sign: dangerJS against 8935ec1e59482ea7cd9170f955000909a89fdf8b

ill merge and QA on next beta!


[Settings] Added delete button tooltip to image resizer page

Summary of the Pull Request
Added a tooltip for the remove button for custom image sizes.

PR Checklist

[X] Applies to #7037
[ ] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

I think you want to add the in-progress label on the issue and not on the PR.

/azp run

@crutkas Done


Clarify what babel's legacy: true is for exactly

The docs say:

in your Babel configuration. Note that legacy: true is specifically needed if you want to get the same behavior as transform-decorators-legacy because there are newer versions of the decorator specification coming out, and they do not behave the same way as this plugin does.

It's still not clear what's the difference between legacy: true mode and the normal mode exactly: which types of use cases are removed from the spec, what are the breaking changes, etc.
I have created the same issue in Babel's repo.

The plugin author has posted a link to a blog describing what legacy: true is for and when to use it.
https://github.com/babel/babel/issues/10234


Add README

This is a first go at a README, discribing Toeplitz, TriangularToelitz and Hankel

Great. Thanks a lot.

Coverage decreased (-0.2%) to 72.662% when pulling e91fff26fa1d7b52a59d300c8754968b47b7da3f on ApproxFun:master into 5671b2a57e608d16f76bd6e6ab39f7ce00012f6e on andreasnoack:master.


automaton.run() called from timer

Hi,
Is it possible to call automaton.run() in a function called by timer? (with Ticker library) I would like (for example) leds running when the loop() is not called.
I tried it with a timer called every 1/1000s. My sketch works mostly well for the led (even during wifi setup) but when a button is pressed (managed by automation), it stops...
Cheers.

Hi Jej,
Sure, whenever automaton.run() is not called by the loop() you can call it from other places. All it does is call the different state machine's cycle() method in turn. Are you using an esp8266 by any chance? There's an Automaton library for that. It's weird that it would stop when you press an (Atm_button?) button. That should never happen. Atm_button doesn't block.
Regards,
Tinkerspy

Yep I use esp8266, but I don't really need the http and wifi machines.
I change the parameters of my machines after events, and maybe the problem occurs if the interrupt launch the run() meanwhile... That's why I was doubting that's possible to run this function in parallel. When launched in the loop(), it's sequential with my code.
Thanks for you answer.

Correct me if I am wrong ... but in general "running whatever in parallel ability" seems to be one of Automaton's weaknesses.   I found that sequential operations were much easier to come up with.


Build release binaries with CGO disabled

For the v1.7.1 release, the runner used to build the release binaries was switched from macOS to Ubuntu. A side effect of this was that CGO was then enabled by default so the binaries were dynamically linked. This can cause problems when the dynamic dependencies cannot be found (e.g. clib).
This change explicitly disables CGO for static linking (as we do for all our other provider plugin binaries, for example).
Fixes #65

I'm going to go ahead and merge this so I can prepare a new release, but happy to address any feedback subsequently.


waitfor_pods issue in validation tests

waitfor_pods function stuck if the number of pods created is larger than the minimum expected.

https://github.com/rancher/validation-tests/pull/194 PR will fix this issue.


Exception when trying Access NBitcoin

Hi,
Im using NBitcoin in my PluginSystem in .net core. But when i want to access NBitcoin Ill get these exception:
Could not load file or assembly 'NBitcoin, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null

I can't tell you why without more details.

Nuget doesnt copy the needed dlls to the output window

what step to reproduce?


Require PFS commits to be on a branch

With Global IDs, multiple commits may be accessible in the same repo with the same ID (due to changing multiple branches in a repo within a single transaction, or other more convoluted ways).  While this will likely not be a common issue once we move stats to a system repo, it must still be possible to disambiguate between multiple commits in the same repo with the same global ID.  The first (and most tedious) step towards this is requiring all commits to be made on a branch.  Following this PR, a commit can no longer not be on a branch in a repo.  In addition, in preparation for the aforementioned disambiguation, any place in the API where we specify a commit ID, we may also specify a branch name.
In this PR:

PFS proto changes:

Replaced Commit.Repo with Commit.Branch, as the repo can now be accessed in the Branch
Removed CommitInfo.Branch, it should now be accessed in CommitInfo.Commit.Branch
CommitProvenance.Branch removed, as the branch can now be accessed in CommitProvenance.Commit.Branch
StartCommitRequest.Branch is no longer optional and has been changed from a string to a Branch so that StartCommitRequest.Commit may be omitted entirely since we can get the repo info from the Branch

All PFS client wrapper functions that involve commits also include a branch name parameter
When specifying a commit by branch rather than ID, we will now construct a proto like:

Commit{
+ Branch: {
    Repo: {
      Name: "data"
    },
+   Name: "master",
+ },
- ID: "master",
}

As a side-effect, some code assumed anyone could start a commit on an output repo as long as it was not on a branch.  For the time being, I have removed the check that disallows starting a commit on a branch in an output repo so that this could still work.

I think src/internal/workload is a dead package. Would you mind deleting it with this PR?

I agree with the change to use protos for the parameters of the Go client wrapper.
This is a separate change that @PFedak is working on - obviously we want to get this in first to avoid merge conflicts.

For global IDs, it is not clear to me how we would go from a commit ID to the corresponding commits in the other repos unless the branch names were also a part of the global ID. Would you be able to access a commit in a repo without a branch parameter and potentially get back more than one? It seems like you would have to figure out the right branch otherwise.
You can access a commit without a branch parameter, but it is an error if there is an ambiguity.  For programmatic access, you should generally specify the branch if you know it.  The Global ID Job structure tracks each affected branch.

I am planning on adding a tag parameter for the file operations client side (it is just a field in the protos for the file operations as of now in the branch I am working with). It might make sense for that to be in the file proto somewhere. I guess this should be added to the string encoding in pachctl, but it seems like it is getting a bit unwieldy.
I don't have any opinions on the command-line format without knowing the use cases, but putting it in the file proto seems right.  Once we change the client interface to accept the protos instead of strings, it shouldn't have many collateral code changes.


docs: ActionSheetBase

:tada: This issue has been resolved in version 7.26.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Delete User

✅ Prerequisites

[x] Did you perform a cursory search of open issues? Is this feature already requested elsewhere?
[x] Are you reporting to the correct repository (@magic-sdk/admin)?

✨ Feature Request
By article 17 in the DSGVO (General data protection regulation) in Germany and Europe, you have to delete all user related data. Otherwise Magic Link is not safe to use in EU countries.
Ref in english version: https://data.consilium.europa.eu/doc/document/ST-5419-2016-REV-1/en/pdf Page 141
🧩 Context
Delete user in Magic Link and connected database.
💻 Examples
No example needed.

inactive repo, closed


cron.New().Remove()

code：
id := 1
cron.New().Remove(1)
cron.New().Remove(id)
question：

The parameter requirement is EntryID, why is 1 possible?
1 There is no error, why can't the id?

Hi @tuye01
it's probably a matter of  type inference.

The parameter requirement is EntryID, why is 1 possible?

Here you're assigning the numeric literal directly to the argument and therefore the inferred (or implicitly converted?) type corresponds to the required one. This is possible because cron.EntryID is an alias typedef for int.

There is no error, why can't the id?

While here you first assign the literal to id, which makes the variable have type int and then when you call cron.New().Remove(id) the types do not match.
In fact, if you explicitly type the variable var id cron.EntryID = 1 the removal runs as expected.


refactor: Replace internal account id type with the near-account-id crate

Replace copy-pasta code: https://github.com/near/near-sdk-rs/blob/master/near-sdk/src/types/account_id.rs with https://crates.io/crates/near-account-id/1.0.0-alpha.1 (1.0.0-alpha.1 or newer)

I want to work on it. Please assign me

@Asymtode712 Please, go ahead!

@frol Please review my PR and suggests if there are some changes to be made.

@Asymtode712 Any updates? Do you plan to keep working on it?

@frol This seems already done.


Some fixes for GZipCompressorInputStream

Coverage decreased (-0.001%) to 83.383% when pulling b88dc93e98083448e5ab20a5155a5ce4563413bb on thomasmey:gzip-compressor-static into 0d0dfb142f721abb473a0324ceede467e195d368 on apache:master.

Thanks!


Why rely on fescar-spring.jar to download all other jars?

Why you need it?
I just want to rely on fescar-spring related jar packages，But it download fescar-spring'parent jar,such as eureka-client.jar,zkclient.jar.So much is not what I want to rely on.

i will fix it.

Thanks


String Pool

We can optimize the memory footprint of the compiler by creating an array of literal strings. Then, each token will simply reference an element in that array (either an existing one or creating a new one as necessary) as its literal value, rather than each token owning its own literal value string. Thus, re-used identifiers (of which there are usually many) will not create duplicate strings in memory.

Fixed in #7


Update Article structure page

[x] Add guidance about Medicine article structure
[x] Add guidance about what to do with 'list of abbreviations' sections (define each abbreviation in each first instance it is used in the main text and in display objects (such as each figure caption, table caption etc.) and remove such sections.

Definition of done

[ ] Team reviewed and approved page?
[x] Add changelog to page

This looks good to me @naushinthomson  - thanks for this!


Netagio API implementation bounty - 500mBTC

Netagio just released it's API. 500mBTC bounty on an implementation. If you want to take this bounty let's talk about timing and code quality briefly.
https://github.com/Netagio/Netagio-Exchange-APIs
https://secure.netagio.com/

@zholmes1 I would be happy to finish this now by myse.f and pay out the bounty if the existing code is pushed to the repo. Cheers

@jheusser Can I take over this bounty please?

@hughneale  It's fully implemented, just need to take time to push

@jheusser ok nice one, thanks!

exchange no longer exists


WIP Fixes #2049 Silence stack traces in test output

Nothing we're doing here is binary incompatible, so we could cherry-pick this onto 0.21 when it's ready and minimize the divergence between the branches.

closing this pull request in favor of https://github.com/http4s/http4s/pull/3456, which is raised against series/0.21


What is the use case of this app , pls explain

Whether Frappe Session Defaults can be used for permission control like filter records based on user etc

@chechani No. I created this plugin for someone to enforce setting the session defaults on login for specific users or roles..

I am trying to test the app to see if I could use it to solve a specific issue with sessions but i wasn't able to install it as it threw an error. Opened an issue for it with full traceback.

@flexy2ky I have replied to you..


Rework StdlibInt as StdlibInt

It should be possible to make StdlibInt generic over FiniteInteger now that BinaryInteger has floating-point initializers (#25). So, what's the point of making it generic? Well, it lets us call functions generic over Swift.FixedWidthInteger in addition to Swift.BinaryInteger since StdlibInt<some SystemsInteger> can conform to it.

There's no meaningful way of testing StdlibInt's forwarding rules so I'll try to just interleave some StdlibInt calls in my generic BinaryInteger tests instead (when I get around to reworking it).

Hm. I suppose the tricky part is that Swift.BinaryInteger kind of requires that StdlibInt<IXL>.Magnitude is StdlibInt<IXL>. This is one of the main differences between the two projects. There are multiple solutions to it, but I'll take a moment to consider whether there's any way to create a well-behaved big Swift.UnsignedInteger first.

Hm. I have another idea I want to explore. I could add dedicated DoubleInt.Stdlib and InfiniInt.Stdlib types rather than overabstracting StdlibInt<T>. Imagine additional modules like, "InfiniIntStdlibKit" or DoubleIntStdlibKit. Using this approach, I could simultaneously conform DoubleInt and InfiniInt to Interoperable in the new modules.

Hm. So I'm trying to deduplicate the implementation of InfiniInt.Stdlib and DoubleInt.Stdlib using an AdapterInteger protocol. I'm not sure that's possible, however. Swift.FixedWidthInteger adds a bunch of default implementations, which means that writing defaults in terms of AdapterInteger results in ambiguity. Both, refine Swift.BinaryInteger and neither have priority over the other. Maybe I'll just have to accept the boilerplate.


revert instructions to 0.25.0 while I figure out what's going on

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.755%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2409

Relevant Lines:
2776

💛  - Coveralls


Add product photos to product cards

Value Proposition
As a user
I want to see Photos of the Products on the Product Card Page
So that i can get an idea of the Products
Description

Acceptance Criteria

[ ] can see Photos of the Products you are interested in
[ ] the Photos are not clickable
[ ] the Photos scales with the Product Card

Tasks

[ ] create new feature branch ("AddProductPhotos")
[ ] upload the images to the database (use links to unsplash)
[ ] create a div within the product card in which the image will be shown
[ ] add basic styling to the whole card

Complexity
M

Hi @LudiFlow @niklashmbgr
very nice User Story 👏
Just one minor comment regarding the first AC which is a little bit confusing - or perhaps I misunderstood 😁
I guess that users will not only see the photos of the products they are interested in, but all the products with photos.

can see Photos of the Products you are interested in

And I noticed one more thing in the Tasks:

create a div within the product card in which the image will be shown

Probably you can use the next js Image Component
For further information take a 👀 at the Docs : next js Image Component

well done 👍


OldCantus has an API at /display-melodies/<some identifier> not present in NewCantus

see: http://cantus.uwaterloo.ca/display-melodies/170815
I was looking through a Google Search Console report for CantusDB, and discovered Google was reporting lots of 404 errors for paths with the form /display-melodies/<some identifier>. I think this is an API used to display a table of results on a Chant Detail page when a user clicks "Display melodies associated with this chant". This is a bit of functionality I recall coming across in the codebase, but I've never touched it.
If /display-melodies/ does what I think it does, it's not a problem if it doesn't show up in search results. But it's not clear to me whether any other websites depend on this API (guessing no, since we've received no complaints about this API disappearing. But other sites could be continuing to ping cantus.uwaterloo.ca for this info, possibly). This could be worth looking into further.

While the endpoint in question is still present on OldCantus, the "display the melodies connected with this chant" link has disappeared from the site, so I can't confirm that that link was triggering a call to this endpoint.
Going to make an executive decision and say we don't need to worry about implementing this. Closing.