qsignature

Should qsignature or any sample mixup / contamination tools be run on the joint pipeline? I see this in the logs:
There is no qsignature for this species: GRCh37

Hi,
Is not implemented by default, you need to activate using mixup_check. More here: https://bcbio-nextgen.readthedocs.org/en/latest/contents/configuration.html#quality-control
I will change the message because it shouldn't say that, is only that you don't have the option in the yaml file in this case.
thanks for notice this!

Great! The reason I ask is that sample mixups picked up by sex mismatch, plate infidelity, or blatant IBD irregularities are the norm. A few basic checks in the joint cohort calling would be very very helpful.

Okay, I accidently added mixup_check: true instead of mixup_check: qsignature. The joint pipeline crashed the controller and submission jobs. Maybe worth some config checking to avoid the whole pipeline going down.
This was in the log.
[2015-03-18T22:46Z] sh-5-15.local: Approx 95% complete for 20_2015-03-15_project_batch3_n24_fb_joint-sort-prep-downsample.bam
[2015-03-18T22:46Z] sh-5-15.local: Approx 100% complete for 20_2015-03-15_project_batch3_n24_fb_joint-sort-prep-downsample.bam
[2015-03-18T22:46Z] sh-5-15.local: Analysis complete for 20_2015-03-15_project_batch3_n24_fb_joint-sort-prep-downsample.bam
[2015-03-18T22:46Z] sh-5-15.local: bamtools stats : 2_04
[2015-03-18T22:46Z] sh-2-36.local: Unexpected error
Traceback (most recent call last):
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 38, in _setup_logging
    yield config
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 145, in pipeline_summary
    return ipython.zip_args(apply(qcsummary.pipeline_summary, *args))
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/qcsummary.py", line 61, in pipeline_summary
    data["summary"] = _run_qc_tools(work_bam, data)
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/qcsummary.py", line 114, in _run_qc_tools
    cur_metrics = qc_fn(bam_file, data, cur_qc_dir)
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/qcsummary.py", line 628, in _run_qsignature_generator
    if mixup_check and mixup_check.startswith("qsignature"):
AttributeError: 'bool' object has no attribute 'startswith'
[2015-03-18T22:46Z] sh-2-36.local: Generating summary files: ['', '1_28']
...
2015-03-18 15:57:49.987 [IPClusterStop] Using existing profile dir: u'/scratch/PI/euan/projects/athletes/bcbio/project_batch3_n24_fb_joint/work/log/ipython'
2015-03-18 15:57:50.133 [IPClusterStop] Stopping cluster [pid=27392] with [signal=2]
2015-03-18 15:57:50.897 [IPClusterStop] Using existing profile dir: u'/scratch/PI/euan/projects/athletes/bcbio/project_batch3_n24_fb_joint/work/log/ipython'
2015-03-18 15:57:50.922 [IPClusterStop] Stopping cluster [pid=27392] with [signal=2]
Traceback (most recent call last):
  File "/share/PI/euan/apps/bin/bcbio_nextgen.py", line 216, in <module>
    main(**kwargs)
  File "/share/PI/euan/apps/bin/bcbio_nextgen.py", line 42, in main
    run_main(**kwargs)
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 45, in run_main
    fc_dir, run_info_yaml)
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 81, in _run_toplevel
    for xs in pipeline.run(config, run_info_yaml, parallel, dirs, samples):
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 192, in run
    samples = qcsummary.generate_parallel(samples, run_parallel)
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/qcsummary.py", line 40, in generate_parallel
    sum_samples = run_parallel("pipeline_summary", samples)
  File "/share/PI/euan/apps/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipython.py", line 129, in run
    for data in view.map_sync(fn, items, track=False):
  File "/home/dwaggott/.local/lib/python2.7/site-packages/IPython/parallel/client/view.py", line 366, in map_sync
    return self.map(f,*sequences,**kwargs)
  File "<string>", line 2, in map
  File "/home/dwaggott/.local/lib/python2.7/site-packages/IPython/parallel/client/view.py", line 66, in sync_results
    ret = f(self, *args, **kwargs)
  File "<string>", line 2, in map
  File "/home/dwaggott/.local/lib/python2.7/site-packages/IPython/parallel/client/view.py", line 51, in save_ids
    ret = f(self, *args, **kwargs)
  File "/home/dwaggott/.local/lib/python2.7/site-packages/IPython/parallel/client/view.py", line 1123, in map
    return pf.map(*sequences)
  File "/home/dwaggott/.local/lib/python2.7/site-packages/IPython/parallel/client/remotefunction.py", line 271, in map
    ret = self(*sequences)
  File "<string>", line 2, in __call__
  File "/home/dwaggott/.local/lib/python2.7/site-packages/IPython/parallel/client/remotefunction.py", line 78, in sync_view_results
    return f(self, *args, **kwargs)
  File "/home/dwaggott/.local/lib/python2.7/site-packages/IPython/parallel/client/remotefunction.py", line 254, in __call__
    return r.get()
  File "/home/dwaggott/.local/lib/python2.7/site-packages/IPython/parallel/client/asyncresult.py", line 118, in get
    raise self._exception
IPython.parallel.error.CompositeError: one or more exceptions from call to method: pipeline_summary
[3:apply]: AttributeError: 'bool' object has no attribute 'startswith'
[3:apply]: AttributeError: 'bool' object has no attribute 'startswith'
[3:apply]: AttributeError: 'bool' object has no attribute 'startswith'
[6:apply]: AttributeError: 'bool' object has no attribute 'startswith'
.... 20 more exceptions ...

Daryl;
Sorry about the issue and thanks for the feedback. I pushed a fix to do better error checking of inputs to catch these issues up front. Please let us know if you run into any other problems.

I now (after b72dc4c) receive an error for 'kraken', which is supposed to accept a boolean (per the documentation), but is not part of the whitelist ALG_ALLOW_BOOLEANS in pipeline.run_info, resulting in ValueError: Incorrect settings in 'algorithm' section for sample_01: kraken set as true

Sven-Eric;
Thanks much for the heads up and apologies for missing that one. If I missed any other's please do let us know -- the downside of having a separate validation step is being sure they are in sync. Thanks again.

Hi,
as a follow up, the documentation was wrong, and kraken shouldn't accept booleans. I changed documentation to specify the correct values that should be minikraken or a custom path.
Sorry about that error in the docs. I fixed it, and hope now run again smoothly.


IRC channel maintenance

Some of us (@wikimatze and me @adam12) have been idling in the channel and helping users, but some things have been difficult without operator status (like updating channel title).
@skade implemented a temporary fix a while ago, but it would be great to have a more permanent fix.
I opened discussions with Freenode staff, and it was suggested that the project be registered with them through a short email.
The format of that email to follow this: https://gist.github.com/AbstractBeliefs/f82487dc7d7db54d7c94740c25c08084
To be submitted here:
<EMAIL_ADDRESS>By someone from this list:
https://github.com/orgs/padrino/people
And then we can update the list of operators.
Is this something we can get taken care of?
cc @achiu (channel founder)

Or maybe we can ask directly on freenode about our issues. Think @achiu should give ops right to all @padrino/core-members then we should have at least one person who can handle the channel.

The following mail has been sent:
Hi,

we've talked to kline on #padrino and we're following his advice mentioned on https://freenode.net/groupreg

----------------------------------------------------------------------------------------------------------

# About your project
Your project name: Padrino
Your project blurb: Padrino is a Ruby web framework built upon the Sinatra web library

Links to places we can find out more about your project:
- http://padrinorb.com/
- https://github.com/padrino

# About you and your staff
Your nick: wikimatze
Your relationship to the project: I'm one of the project maintainers
Nicks of alternate GCs:
- achiu
- skade
- adam12
- wakatara

# About freenode
Channels you'd like to claim (typically #projectname): #padrino
Channel namespaces you'd like to claim (typically #projectname-*): #padrino-*
Cloak namespaces you'd like to claim (typically projectname/*): padrino/*

Notes you may wish to read:
* Group registration: https://freenode.net/groupreg
* Information on freenode policies: https://freenode.net/policies

----------------------------------------------------------------------------------------------------------

Cheers

Matthias

Now let's wait and see.

Think we can close those issue now.

Think we can close those issue now.

Agreed.


Update updated_main.py

Added the feature of automatic sending the email.

Make commit message better.
https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/ -> Only see section on "Commit Message Comparisons"


Render Texture in IE

Hello, it looks like Render Textures dont work in IE for Windows Phone (Edge is well) after 4.1.1 version.

Hi @Ewance - could you create a jsfiddle that reproduces this issue please?

Hi @themoonrat , I just open Render Texture examples on WindowsPhone 8.1
and demos dont work with pixijs after 4.1.1
http://pixijs.github.io/examples/#/basics/render-texture.js
http://pixijs.github.io/examples/#/demos/render-texture-demo.js
pixi 4.1.1 looks fine

I can't see anything wrong on a windows 10 phone with Edge, but I do see problems with Windows Phone 8.1 with IE

Hey @Ewance I don't have a Windows Phone, but can you check if this is fixed for you on the latest version? If not, can you try setting the legacy option via the WebGLRenderer constructor and see if that fixes your issue?

@englercj: I just gave this a try and I'm having issues rendering textures from a dataURI in IE 11 and Edge. Creating a texture from a png works fine in both. I've tried to run this with legacy set to true and false. I created a jsfiddle that uses Texture.fromImage() using a png and a data uri. It works fine in other browser, just not IE or Edge.
https://jsfiddle.net/psyrendust/c3ntwfab/
Windows Edge

Windows IE 11

Windows Firefox

Windows Chrome

OS X Chrome

Hi @psyrendust this is a different issue. This issue is about using RenderTextures in IE. Would oyu mind opening a new issue for your problem?
Thanks!


Support XML

Fixes #4
This PR heavily refactors the Model used to represent VTK files in order to support the modern XML VTK file formats.
An intermediate XML file Model called xml::VTKFile is introduced in the xml module for a pure low-level XML interface, which can be accessed via the unstable feature by using import_xml. Support for XML files is feature gated behind the xml feature which is enabled by default.
Preliminary work is included for enabling an async interface for importing files, however it is blocked on tokio support in quick-xml.
A file documenting the transition from previous versions of vtkio is included in CHANGELOG.md.


Use operator_libs_linux.v2.snap

Issue

Update to latest version (v2) of operator_libs_linux.
Solution

charmcraft fetch-lib charms.operator_libs_linux.v2.snap

Also update current code that used v1.
This update is not included in #213
Context

Replaces #247
Bumping a major version can be tricky, but the library methods used by the snap are not affected.
Testing Instructions

Release Notes

Revision 17 of charm 'grafana-agent' released to edge


[mesheryctl] Misleading error on invalid meshconfig

See mesheryctl Command Tracker for current status of commands.
Current Behavior

If I have an ill-formatted config.yaml inside .meshery directory and I try to execute any mesheryctl command, it results in the error shown below which is misleading as the actual issue the invalid yaml

Desired Behavior

Screenshots/Logs

Environment

Host OS: Mac Linux Windows
Meshery Server Version: stable-v
Meshery Client Version: stable-v
Platform: Docker Kubernetes

Contributor Resources

mesheryctl Contributing Guide
Beginner's guide to contributing to Meshery and mesheryctl
mesheryctl Command Tracker
Meshery CLI Commands and Documentation
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Hey @Revolyssup Can I work in this?

@Revolyssup Please assign this issue to me

@Santosh1176 @Pritishchugh22 thanks for jumping in. Please confirm that you've read the style guide for Meshery CLI in the Meshery Docs Contributing section and that you're able to build and run mesheryctl and Meshery Server.

@leecalcote Yes, I've gone through the Docs for contributing to Meshery CLI and almost resolved this issue. I'll confirm, if this is the desired outcome and raise a PR.

@leecalcote Yes I have also gone through the required documents and would like to work on this.

@Revolyssup i would like to work on this issue

@Pritishchugh22  , Sorry I missed this chat. @manikmmalhotra  grabbed this issue in today's dev call. You can find some other good first issues around. I will assign you on the next one.


fix(core): remove trailing comma in function signature

Fix #10843
Since it's not supported on many browsers, we should just remove it

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[x] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Maybe stupid queston but shouldn't you use some linter to detect this kind of problems?

A minifier would have removed the comma but not the bundle itself. So the minified version is probably working but not the dev version
Eduardo San Martin Morote

On 20 Nov 2019, at 12:28, Phan An<EMAIL_ADDRESS>wrote:

This is the real stupid question: The bundler should already have handled this, right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Release 1.0.14 does not include smithy 1.0.3

Describe the bug
Release 1.0.14 should have included smithy 1.0.3 (this issue, this PR).
Smithy 1.0.2 is included instead (excerpt from Gradle module metadata):
"dependencies": [
        {
          "group": "org.jetbrains.kotlin",
          "module": "kotlin-stdlib",
          "version": {
            "requires": "1.9.10"
          }
        },
        {
          "group": "aws.sdk.kotlin",
          "module": "aws-config",
          "version": {
            "requires": "1.0.14"
          }
        },
        {
          "group": "aws.sdk.kotlin",
          "module": "aws-core",
          "version": {
            "requires": "1.0.14"
          }
        },
        {
          "group": "aws.sdk.kotlin",
          "module": "aws-endpoint",
          "version": {
            "requires": "1.0.14"
          }
        },
        {
          "group": "aws.smithy.kotlin",
          "module": "http-client",
          "version": {
            "requires": "1.0.2"
          }
        },
        {
          "group": "aws.smithy.kotlin",
          "module": "runtime-core",
          "version": {
            "requires": "1.0.2"
          }
        },

Using the SDK in IntelliJ also shows 1.0.2, as does a Gradle build scan.
Expected behavior
Smithy 1.0.3 is distributed with AWS Kotlin SDK.
Current behavior
Smithy 1.0.2 is distributed with AWS Kotlin SDK.
Steps to Reproduce
Use AWS Kotlin SDK 1.0.14 and observe the transitive dependencies.
Possible Solution
Release 1.0.15 with a correction for whatever went wrong to include smithy 1.0.3.
Context
Unable to make select SDK requests with AWS Kotlin SDK 1.0.0+ per this issue, addressed in Smithy 1.0.3.
AWS Kotlin SDK version used
1.0.14
Platform (JVM/JS/Native)
JVM
Operating System and version
macOS Sonoma

Of note, the changelog text in the PR is also not showing in the release notes for 1.0.14 - its like those (merged) PR changes were skipped.

Yes it appears I failed to merge the version bump into the correct branch of aws-sdk-kotlin. It has now been merged into the release branch and is currently being built and released to Maven.

Excellent!  thx.

Good to hear, thanks for your patience.


Page for session 2 quiz and solution notebook

This page will be where participants can access the quiz and solution. The plan is for these to go up midway through each training week.

Could I confirm checking your notebook against the solution before doing the quiz does not disqualify you from progressing towards certification?


Landscape view - initial refactor

This refactors the blueprint code to allow dev work on a new "landscape" graphical mode.
It is disabled in the last commit so should be no change to UX with this,
but the other changes should make it easier to work on a landscape view by playing with the sizes of nodes.  They refactor much more of the layout-specific logic into subclasses, make the elements being rendered more flexible, and make more of the computations derived from known values.
There is more work to make things like ghost nodes fully derived from the nodes they ghost, which we will need for the landscape view to be able to fill the space but this gets us a good bit of the way there.
If landscape is enabled, it doesn't do what we want, but it has slightly different boxier behaviour to the normal mode to indicate the direction of travel.

retest this please

@ahgittin I've tried to build this locally, but I'm getting build errors, and the build is also failing on Jenkins. Can you rebase against master please


如何训练单模态数据，没有图片的

是否已有关于该错误的issue或讨论？ | Is there an existing issue / discussion for this?

[X] 我已经搜索过已有的issues和讨论 | I have searched the existing issues / discussions

该问题是否在FAQ中有解答？ | Is there an existing answer for this in FAQ?

[X] 我已经搜索过FAQ | I have searched FAQ

当前行为 | Current Behavior
训练纯文本数据报错
期望行为 | Expected Behavior
No response
复现方法 | Steps To Reproduce
No response
运行环境 | Environment
- OS:
- Python:
- Transformers:
- PyTorch:
- CUDA (`python -c 'import torch; print(torch.version.cuda)'`):

备注 | Anything else?
No response

目前暂时没有发布纯文本的训练代码


Local history: allow to configure entries location to be relative to workspace

I hope we can have an option to save the backup file relative to the original file (inside .vscode for example). like local history does.
why not use local history if it does what I want? because it was not updated for 2 years and have a lot of bugs that makes it unusable for me: for example it stopped working with the single file mode, I have to open a folder in vscode otherwise it does not work...)

a setting to configure where to store local history entries

yes exactly

maybe with support for a relative path to store into the workspace is desired here?

yes with relative path, but I hope it will work in the single file mode too (without needing to use a workspace/folder). this is how local history worked before vscode changed something internally.

Where would the history be stored into when in single file mode where no folder is opened?
relative to the file I m working on, inside a folder. for example .vscode/History or .history or some configurable path from settings.

But you might end up with a lot of .vscode folders for every "loose" file you edit in.

This is not a problem at all, this is how notepad++ works too (and also the local history), it works very well, I feel safe when I see these backup folders near my files, and I can fully and easily control the backup files, and I can move the parent folder without losing the backup files, and I can rename or delete the original file and still be able to find easily the backup file...

it stopped working with the single file mode, I have to open a folder in vscode otherwise it does not work...)

How do you get that "single file mode"? Currently, every single file that I open in VSCode, even these that are not inside the current workspace, are saved to the Local History.
I would like that VSCode save files to the Local History only if they are part of the currently opened workspace. I don't want it to make file backups for each and every file that I want to edit in VSCode, even my shopping lists and playlist files.

There is a workbench.localHistory.exclude setting that is somewhat helping but not ideal, sounds like a new feature request to file.

@Z-E-D I use a batch (.bat) to open vscode, and I use the portable vscode (zip file).
so this is how I open vscode to get the single file mode:
code.exe -r  myfile
but remember that vscode will open itself in the same mode it had when you close it, so to test this first close any open folder using File>Close Folder or File>Close Workspace.
but why this now that vscode has implemented the local history and it works as you want it.

Thanks for responses. I am using VSCode in portable mode, but I would like to avoid creating batch files if I just want to edit a simple file of any kind, just to prevent making its backup.
I just opened a new issue for my request (#146649).

This would be great as I'd imagine that in my environment (editing files on a shared drive) it would allow my colleagues to also view the file history.

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Remove

Summary
<AlertBox /> is already deprecated in v3 in favour of <Alert />.
This PR removes it completely from v4, not being available anymore for clients.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Get next line - very large fd

if one implements gnl by using a mx_fd option, a very large fd causes a seg fault.

The issue here is not a large file but a large fd.
I have seen implementations like this where essentially a large array of string pointers is initiated as a static variable and accessed simply using r_str[fd] when called.
The problem is that if too many files are open, the fd may be greater than MAX_FD_N. If this value is large enough, you will not have an error (which should be a bus error and not a segfault), but then you're using about 80MB of memory for no reason. It would be interesting to add this test as I have seen a lot of implementations lately that take this (highly inefficient) shortcut

Hello @tobyhw
How would you handle tests for that issue?
Should we open file descriptors with gnl with huge number of iterations? How many iterations? How to determine when the test is relevant?


How to extend to a new model?

Related to #177
I'm looking to use extract_eq() to help with the nlmixr2 package.  It typically uses nonlinear, mixed-effect models that are defined by multiple equations.
For that, I was looking at several items of how this is working and I have a few questions and thoughts:

Do you have some documentation of how to implement a new model?  My specific thought is that it would help to provide guidance on how to do the final wrapping of the output in multiple equations.  There are probably a lot more questions that would help.
When writing for nlmixr2 models, many of the arguments for extract_eq() don't apply.  As part of #177, have you considered having the generic as something much simpler like extract_eq <- function(model, ...) {UseMethod("extract_eq")}?
Would you consider exporting the escape_tex() function?  Are there other internal helper functions that may be necessary for generating high-quality outputs?

Hi @billdenney, those are all really good questions. The truth is development has majorly stalled on this because I just don't really have the motivation to keep up with it anymore (switching careers has something to do with that, but general burnout is a larger factor).
I had talked with @JaySumners about even taking over as maintainer, but he is the main person that has really thought through extensibility. The short answer is it's not very extensible now, and we had hoped to make it more so, but never actually got around to it.
Sorry if that's a disappointing response, but perhaps Jay will have more context or more info for you. Also happy to talk about PRs if you'd like to take on something on your own.

@datalorax , sorry to hear about the burnout feeling.  Are you considering transitioning the package to @JaySumners for maintenance?
I think that the package is useful.  If neither of you have time for maintaining and extending it, have you considered seeing if ropensci would be interested in taking over development?

That's not a bad idea. I'm not sure I'm ready to do that yet, but it's definitely worth considering.

I wasn't intending it to be a push-- it is intended as a brainstorm.  (Tone is hard by both email and github issues.  😄 )

Yeah no worries, I didn't intend it as pushing. I genuinely appreciate the thought!


thread per core golang like glommio / seastar?

thread per core golang like glommio / seastar?

no thread-per-core here, we only configure the number of goroutines listening for epoll, through the SetNumLoops API

do u think there's a possibility to use thread per core in future + io_uring for this? i mean is it part of the roadmap?
like monoio

E.. monoio is coded in rust, golang I think might be hard to implement it, custom goruntime doesn't seem to be accepted.
So maybe the solution rust -> cgo -> golang is better?

what's the overhead like with cgo calling golang? i heard it's extremely terrible. right?

not yet researched ...

golang cannot let user side codes to imlement the thread-per-core architecture. and cgo is not a good idea to be used in high performance use-case. @hiqsociety


Trying to get react-canvas working with ngReact

Hi,
ngReact is easy to install and to use with angularjs...
... but how to proceed when you want to use a react library like flipboard/react-canvas as it relies on requirejs.
I tried without success to load react and react-canvas with browserify.
Maybe I'm on the wrong way ?
oliver

@oliviercooper thanks for reporting this.
I created this pull request a while back, to show how you could use browerify with ngReact. Perhaps you can find some inspiration there.
Let me know how you get on.

Hi,
I spent a lot of time trying to make it works without success (I think because of my project structure).
I decided to upgrade my project to a new angularjs boilerplate (https://github.com/jakemmarsh/angularjs-gulp-browserify-boilerplate)
Just starting with this one, it seems to be easier.
For using ngReact I followed your pull request tips :
'use strict';
var angular = require('angular');
// angular modules
require('angular-ui-router');
require('react');
require('ngreact/ngReact');
require('./templates');
require('./controllers/_index');
require('./services/_index');
require('./directives/_index');
// create and bootstrap application
angular.element(document).ready(function() {
var requires = [
'ui.router',
'react',
'templates',
'app.controllers',
'app.services',
'app.directives'
];
// mount on window for testing
window.app = angular.module('app', requires);
angular.module('app').constant('AppSettings', require('./constants'));
angular.module('app').config(require('./routes'));
angular.module('app').run(require('./on_run'));
angular.bootstrap(document, ['app']);
});
As you seen, the only difference is require('ngreact/ngReact') and not require('ngReact') as the node_modules folder is in minus characters, why ?
oliver

@oliviercooper did you figure out what the problem was ?

hi,
My initial project was not relying on requirejs and It was too complex to properly integrate angularjs and requirejs. A good refactoring and boilerplate migration were usefull.
oliver


[Feature Suggestion] Full charge only attacks

What about a feature that you can attack with weapons in full charge only?

Yup that's not a bad idea. I may add it in the future =)
I'm not sure it would make combats better but there is only one way to know!

I would LOVE to see this! I have some players who absolutely refuse to wait for the bar to fill and then complain about the game being too hard.

I might work on an update of this mod soon, I will let you know when the work is done

any progress on this?

Hello, indeed I forgot to mention it on GitHub!
When starting to work again on this mod, in order to add many other features from combat snapshots, someone mentioned that Combatify is a mod that does exactly this: adding every feature from combat snapshots. As I don't do duplicate mods, I decided to stop adding features from combat snapshots, and I will even remove the ones I already added to the next release that will be for the next Minecraft major version.
By doing so, this mod will focus on adding only original features to combat. This will be way easier for me to maintain and avoid duplicate functionalities, when one mod is already doing the work correctly.

Awesome! Thanks for finding this!


Add document about lua functions

@ryoppippi
I'll add them to doc/jetpack.txt and readme.md

I decide to remove init() function from new vim-jetpack because we can change the configuraiton parameters as follows.
vim.g.jetpack.ignore_patterns = {'/foo/bar'}

I feel it is more neovim-way. Would you mind to tell me your opinion?

I think it looks ok. so I'll close this issue. Thanks


Y categories

New row categories. Complete rewrite of core and grid modules. Now simpler and more flexible. Introduced switch to turn off headers altogether.


Fix quota manager integration

Please check if the PR fulfills these requirements

[x] The commit messages are descriptive
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[ ] An issue has been created for the pull requests. Some issues might require previous discussion.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

This fixes the integration and support of quotas in Julie Ops, including current state and deletion.

What is the current behavior? (You can also link to an open issue here)

It does not work at all because the quota manager is not plugged and the data model does not contain quota declaration.

What is the new behavior (if this is a feature change)?

Quotas are supported for creation, current state and deletion with as usual a flag to allow deletion.
No prefix management has been implemented because quotas are only using Users and therefore quotas should be declared in only one unique file.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No.

Other information:

IMPORTANT: Please review the CONTRIBUTING.md file for detailed contributing guidelines.
IMPORTANT: Your pull request MUST target master.
PLEASE REMOVE THIS TEMPLATE BEFORE SUBMITTING

This PR appears to have broken the unit tests, as it expects to find a broker on localhost:9092.

This PR appears to have broken the unit tests, as it expects to find a broker on localhost:9092.

Indeed, I have created another PR to fix this #582.
Any help is welcome 🙂

I replied in your other PR.


Android: Picture share from Gallery to mattemost is not working

Summary
Android App Image Share from Gallery with no effect / Upload
Environment Information

Device Name: Samsung Galaxy S20FE
OS Version: Android 11 / One Ui-Version 3.1
Mattermost App Version: 1.45.0
Mattermost Server Version: 4.6.2

Steps to reproduce
Open Samsung Gallery app
Open picture you want to send
Hit share button
Select Mattermost from list
Now enter text or leave it empty
Select organisation and channel to post to
Hit send button in upper right corner
App closes
Nothing happens on the server
Expected behavior
I expect the share function to upload the image with the text provided.
Sending the same picture with text from within the Mattermost app works fine
Observed behavior (that appears unintentional)
Instead of sending the message with attachement to the server, nothing happens.
Possible fixes
Unfortunatly, I have no idea

@snowowl78 We haven't been able to reproduce this, would you be open to upgrading your Mattermost server to the latest version (v5.37.0)?

@amyblais I am sorry the Server is not under my control. But I took a look again to the server version (via the app's information screen) So I provided the wrong version to you.  As you will see in the provided Screenshot, the cyrrent actual server version is already at 5.33.2,  maybe this helps to investigate further?

@amyblais I am sorry the Server is not under my control. But I took a look again to the server version (via the app's information screen) So I provided the wrong version to you.  As you will see in the provided Screenshot, the current actual server version is already at 5.33.2,  maybe this helps to investigate further?

@snowowl78 Was this working with the previous v1.44 Mattermost app version?

I am sorry, I have never tried this before. This was the very first time I used this share function in combination with the mattermost app.

@snowowl78 Are you the only one on your server seeing this issue or do you know if there are other people on the same server affected by this?
If just one user is affected, it may be related to a connection instability.

I asked my colleagues to try to verify this behaviour.
On the other side do I not believe that this is related to a connection instability, because sharing from wihtin mattermost-app itself worked perfectyl fine.
I tried this more than ones now, and can still reproduce it every time.

@snowowl78 Does this still reproduce on the latest beta (V2)?

Sorry @larkox I can't tell


Gitignore: .toggletasks.json

I'm trying out toggletasks
and I don't want to rm it manually from the directory everytime if that's fine

Thank you :)


chore: append STRRL's Weekly Report #29

Signed-off-by: STRRL<EMAIL_ADDRESS>

WOW! Vercel bot! COOL!


Odd results in Audit Exercises

Hi,
I'm getting what looks like an odd result from the Audit exercises.
My code for the exercise is here.

The test data hasn't been modified and looks like this.

This is what is in the debug output. It shows both the "Build Bridge" "Restarted" entry and the "Dam River" "Damming" entry as having ProcessingDateFrom times of 05:00:00.000 which is an hour behind the 06:00:00.000 they should be. The other entries have not been adjusted in any way so I can't see any reason these two entries have been adjusted.

I am in Australia/Brisbane with no daylight savings so I am standard AEST time.
Because of this time difference my test is failing. I don't think I have done anything wrong.
Any ideas?

Thanks for reporting this issue. We'll have to either amend the docs to force America/New_York as the timezone (-Duser.timezone=America/New_York) on the command line, or fix the processing date to do UTC conversions (timezoneConversion="convert-to-utc") and change the data.

Any reason why some of them were changing?
Is it much work to UTC the ProcessingDate?

UTC should be straight forward. @nikhilnanivadekar will try to do the utc thing over the next day or two.

Oh cool.

I've just had a thought.
I wonder if the TimeZone.inDaylightTime has the knowledge of historic daylight savings. Here in Queensland we no longer have Daylight Savings. However we did have and it would not always have been as it is a more recent idea.
The Times back in the 1960's are coming through fine. The times in the 2000's are fine it is the dates in the 1990's that are 1 hour adjusted which when I was a kid did have daylight savings.
I shall look at when Daylight Savings here in Queensland Australia come in to effect and ended to see if that matches up.

I tried UTC but the tests break in various timezones. So, the fix I have in #27 is to set the database timezone to be same as local timezone, and convert the processing, business dates to database timezone.

If you look at this it details the Daylight Savings years here in Queensland, Australia.
https://en.m.wikipedia.org/wiki/Daylight_saving_time_in_Australia
I tried a date in 1972 and got the same 1 hour adjustment of the time. So the TimeZone.inDaylightTime is pretty smart.
So I guess the problem for me is that the assert in the test is looking for a specific date and time and not one that has been adjusted.

OR maybe it is more that if I am inserting the following Daylight Savings or not
1      , "Build Bridge" , "Restarted", "1990-01-01 06:00:00.0", "1992-12-01 23:59:00.0"
I should get the same back and not
1      , "Build Bridge" , "Restarted", "1990-01-01 05:00:00.0", "1992-12-01 23:59:00.0"

I tried switching using Reladomo's built in timezone conversion to UTC, and it works with almost every timezone and date, except Australia/Brisbane and 1990-01-01 06:00:00.0. I even started using Joda time's parsing to see if that made a difference, but it didn't.
As far as the kata is concerned, it's just a learning tool and I'm pretty sure you've learned more than was intended :smile:
I'm not certain if there is a core issue here that needs to be addressed. If you run into a problem in your own code, let us know.

@gs-rezaem Lucky me for living near Brisbane....
Thanks for looking in to it. I'll move on with more integration with my main app and see how I go.


CCH normalization / y-offset

Hey!
@morales-gregorio and I stumbled across the following issues when using cross_correlation_histogram to calculate the time-lagged auto-correlation function. These might not be actual issues but boil down to different conventions with their respective (dis-)advantages. Just want to raise it here to make you aware.
If I understand the cross_correlation_histogram function correctly, it calculates
CCH_{s1,s2}[k] = sum_n s1[n+k] * s2[n]

where s1 and s2 are BinnedSpikeTrain.to_array()s. All the following points are based on this.
Normalization (time)
For me, a (binned) spiketrain has dimension 1/time such that it's integral equals the total number of spikes. Hence, I expect the CCH to have the dimension 1/time^2. However, in agreement with the above definition, it is dimensionless. This amounts to a factor 1/binsize**2 difference.
Normalization (convolution)
The sum_n in the CCH depends on the length of the binned spiketrains. Thus, the CCH of a realization of a stationary process that is twice as long as another realization leads to a CCH that differs by a factor of two. To avoid this, I think the CCH should be divided by the length of the binned spiketrains. This amounts to a factor binsize/T difference.
y-offset
For long times, the time-lagged correlation should (for reasonable processes) decay to zero. However, in the above definition it decays to the squared rate because s1 and s2 are not centered. This amounts to a subtraction of the product of the mean values of s1 and s2.
Taking all three points into account, I arrive at
CCH_new = CCH_old / binsize / T - rate**2

for the auto-correlation (for the cross-correlation the rate might of course be different).
Just to be clear: none of the above amounts to the question whether the variance should be divided out imho.

It took a long time to think about what you wrote and what we actually do with it in CCH.
As you saw, CCH function has cross_corr_coef flag. However, it does slightly different than your proposal. But the equation for computing the cross-correlogram for poisson spike trains seems to be established since 1982 and used in papers interchangeably, so we stick to the equation, which is given in our book which in turn refers to Eggermont 1992a.
But if you look closely at the equation and our implementation of cross_corr_coef(), you find differences. That makes me wonder if the implementation is correct at all.  It has to be correct though because we have a test to compare CCH + cross_corr_coef output with corrcoef() function.
After you switched to cross_corr_coef=True in spike_train_timescale(), it started to work as you expect?

Thanks for looking into this! For the timescales, cross_corr_coef=True works fine. There, I only need the y-offset corrected, which is done in cross_corr_coef=True, and I don't care about the normalizations because I normalize the CCH to one (https://github.com/NeuralEnsemble/elephant/blob/master/elephant/spike_train_correlation.py#L816).
I thought about the normalization a bit more. Based on Gruen & Rotter (2010) chapter 5, it is imho consistent with Eq. (5.2) and (5.4) to neglect both the y-offset and the normalization (time). Both are just conventions I think and one simply has to be consistent (and put a reference). However, I think the normalization of the convolution is necessary. Eq. (5.4) reads
CCH_{s1,s2}[k] = \frac{1}{N} sum_{n=1}^N s1[n] * s2[n+k]

while the code calculates
CCH_{s1,s2}[k] = sum_{n=1}^N s1[n] * s2[n+k]

as far as I can see.

Hm, there are different conventions on how to normalize CCH, see https://de.mathworks.com/help/matlab/ref/xcorr.html
The current implementation follows scaleopt='none' strategy event though, according to the book, we should have used scaleopt='bias' strategy. This is strange, indeed. We even have a test that checks our CCH result with a bare np.correlate() without any normalization.
I've opened a PR that adds this flag to another similar function of ours - cross_correlation_function(). Do you think it makes sense to add scaleopt flag here as well?

Yes, I think adding a scaleopt flag sounds like a good solution to this. I'd argue that scaleopt='bias' should be the default here imho.

This was fixed by #277 , if not, feel free to reopen this issue.


ArgumentException in ImageDimensionService with progressive JPGs

Sorry for the duplicate, I just created a pull request.
Hi,
we are getting ArgumentExceptions in the ImageDimensionService when using progressive JPGs. In DecodeJfif you are looking for a 0xc0 marker which is only valid for baseline jpgs. For progressive jpgs it should be 0xc2.
Additionally I would suggest that you replace the throw new ArgumentException(ErrorMessage); with return Size.Empty; so the fallback Image.FromStream can be used.
Keep in mind that you need to reset the stream position to the beginning (stream.Position = 0;) right before the Image.FromStream because the BinaryReader has already read some bytes.
Regards,
Benjamin

Fixed in version 1.4


Could you compare this to thing/geom?

I noticed you do a comparison to dali. Could you do something similar with thing/geom?
The whole thing/geom collection of libraries is huge - It's a mammoth piece of work that's very Clojure-y and extensible. I'm curious why reinvent the wheel instead of extending that. (maybe just for fun, :) ) It looks very similar but I'm guessing that I'm missing some critical design difference that makes what you want to do incompatible or fundamentally different.
It also doesn't come with a rasterizer btw. Just hiccup->svg/xml. I've used SalamanderSVG successfully (was quicker than Batik) as well as rendering directly with JavaFX primitives
PS: Thanks for ob-babashka.el :). I'm gunna try to do something similar for Clojure and thing/geom

Thanks for your great suggestion. I've heard of thing/geom but it just didn't cross my mind to add it as a comparison.
It's a fair question wondering why I've made this lilbrary instead of usign thing/geom. The first reason you actually mention:

thing/geom is huge and thus a potential (admittedly subjective) no-go for some people. In fact, I'll admit that as I was first learning Clojure, I found thing/geom and turned away from it due to the shear volume of namespaces. In short: it didn't feel accessible to me. svg-clj is much smaller in scope and so may be a 'quick and easy' tool for some situations.
This library is absolutely a project for fun/learning on my end. But, I do feel quite strongly that there is enough utility here to be valuable to at least a few people.

Finally, I suspect  there are some design differences that I would have to look into further and add to the readme.
Once again thanks for the suggestion, I really appreciate getting input from the community :)
Btw, glad you like ob-babashka.el. I'll keep my eyes open for work with thing/geom!

Ah, yeah, I get how it looks overwhelming. I had the same impression at first. It's actually just a suite of mini-libraries that mostly work independently
If you look at the original master branch and its org literate stuff then it should be relatively easy to understand. Here is the SVG one: https://github.com/thi-ng/geom/blob/master/geom-svg/src/core.org
This can be used independent of the rest of the geom project and I think it's doing a lot of things similar to you. It's sorta just 3 parts:

a serializer to go hiccup->SVG/XML
some "utility" stuff.. colors/transforms/etc
basics functions that take params and return hiccup

The other namespaces in geom can be thought of in two ways:

even lower level stuff that's used by SVG and other namespaces: ex matrix/vector/color
higher level stuff that usually leverages SVG: ex: I mostly use geom-viz, this make declarative plots, and it will use the SVG namespace to generate those

So then when you want to extend the functionality you write your own mini-library in effect and you can leverage the existing ecosystem. Though.. frankly I've barely scratched the surface when it comes to that myself :) . I've only really just wrote my own hiccup-JavaFX serializer
If I get a babel mode working then I'll post a link/example here :))

I never managed to make a babel mode. The ELisp wouldn't comply :)
But I did make a setup with ob-clojure. Maybe you'll find it useful
https://geokon-gh.github.io/literate-clojure.html
The last example kinda showcases thing/geom firing at all cylinders
Hope it's useful!
(there are also a lot of little details I couldn't work out - in the green Note sections.. feedback and tweaks much appreciated)

Wow, thanks so much for sharing this :)
It'll be great to go through in more detail when I have the time (life's a tad busy at the moment, but hey, that's how things go).
I think with your example here I can put together a nice comparison!
Again, really appreciate your input.
I'll run things on my machine soon and see if I can give any feedback :)

Oh please take your time. And if you don't get around to it, don't worry. I was just working on this literate mode thing on my own and came across your lib. That's all. I was gunna make that write up anyway.
If you have any feedback of suggestions at some point that'd be great - but I didn't mean to give you any extra work :)


JFR test disabled on Windows, options parsing output

Failures are merely runtime taking too long over the threshold.


Generator Functions are not assignable to type GeneratorFunction

Bug Report
🔎 Search Terms
GeneratorFunction Symbol.toStringTag
🕗 Version & Regression Information
The type GeneratorFunction seems to be completely useless as generator functions are not assignable to it.
This exists at least since v3.3 (probably earlier with the introduction of Generators) and can still be reproduced with the newest nightly in the playground.
⏯ Playground Link
Playground link with relevant code
💻 Code
let foo: GeneratorFunction = function * () { return 1}
// Property '[Symbol.toStringTag]' is missing in type '() => IterableIterator<number>' but required in type 'GeneratorFunction'.

🙁 Actual behavior
The types are not assignable to each other because Symbol.toStringTag is available on GeneratorFunction though not on Function. That's quite weird as it should actually be usable on all objects. I'm wondering why it was not added to the Object interface, but only to the GeneratorFunction.
What's even more strange is that the function* gets inferred to () => Generator which is accurate, though it makes the GeneratorFunction interface pretty useless.
🙂 Expected behavior
I would expect that Function and GeneratorFunction are compatible (Symbol.toStringTag is available on all Objects or at least on Functions too). I would also expect that function* gets inferred as GeneratorFunction.
Is it a bug? I'm not sure ... it could also be the result of various constraints that I am unaware of or that I could not find.  In that case I'd be very grateful for an explanation :)
Thanks in advance,
Jonas
This question originated from StackOverflow

Have same issue with function that expect argument with type GeneratorFunction
https://www.typescriptlang.org/play?#code/CYUwxgNghgTiAEAzArgOzAFwJYHtXxjXgApFUAueAcRFRBigxxgDE1NdUBKSgNxyzAA3ACgRhVKXbY8AKhJd4AbxHx4ATywgIweAEZRazdt0AmQxq074AZlEBfLkKA

Can we fix that in TypeScript 5.3?

(Symbol.toStringTag is available on all Objects or at least on Functions too)

Unfortunately, Function.prototype does not define [Symbol.toStringTag] since that would affect the toString() output of all class instances.
Currently, all function types have an effective supertype of Function. Unfortunately, we cannot give generator functions and methods a different effective supertype as that wouldn't carry over to declaration emit:
declare let foo: () => Generator;
let bar: GeneratorFunction = foo; // error

The only way we could make this consistent in declaration emit would be to introduce a "generator function type" syntax, i.e., declare let foo: * () => Generator, or something like it. However, aside from making it fit with GeneratorFunction, there's no other real value to be gained by introducing new syntax for this.
Barring that, we could just remove the construct signature and [Symbol.toStringTag] from GeneratorFunction. However, doing so could break existing users if anyone is using new with GeneratorFunction. In addition, by stripping those elements from the type what you would essentially have is no better than (...args: any) => Generator.
Instead, I would argue that you really shouldn't be using GeneratorFunction in this way as it is not an interface to conform to. Rather, it is the superclass of a given generator function. In that way, it has the same behavior as any other attempt to assign a subtype constructor to a supertype constructor that does not conform to the same set of signatures:
class A {
    constructor(public x: number) {}
}

class B extends A {
    constructor(x: number, public y: number) {
        super(x);
    }
}

let foo: typeof A = B; // error: Type 'typeof B' is not assignable to type 'typeof A'.


Bump ms-rest

Would it be possible to bump ms-rest to the latest version ? Current one is using request 2.74 that uses a deprecated version of uuid (node-uuid) ?

@BillZengMSFT Please take a look.

@RamjotSingh @BillZengMSFT Created PR (#82 )

Any updates ?


AR View Landscape

Please add Landscape feature to AR view.
It would be very helpful.

@glesage any news on these?

Any news on the landscape mode since 18 Sep 2013 ?

Any news on the landscape mode?

+1.
Would love to have this feature!

@glesage any news on landscape  ?
if anyone have any idea, please share.. it would be very helpful.


Editing keybind seemingly doesn't work

I've tried to change "MinimizeKeybind" to Enum.KeyCode.V but it seemingly hasn't worked
local Window = Fluent:CreateWindow({
	Title = "",
	SubTitle = "",
	TabWidth = 120,
	Size = UDim2.fromOffset(615, 366),
	Theme = "Dark",
	MinimizeKeybind = Enum.KeyCode.V,
})

Sorry in advance if I've misunderstood something!

@Compwnter it doesn't look like the library supports the MinimizeKeybind part at all.

added MinimizeKey argument, used when theres no MinimizeKeybind


Setup fails, cannot get latest flash projector version

The initial setup no longer works.
Grabbing of the latest flash projector leads to a timeout and crashes the setup

Simply adding a user agent seems to fix the problem.
(_Getlatest() in IntitialSetup.au3)
	HttpSetUserAgent("Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0")


Research and Implement Democat/Swervelib update for 2024

Research and implement the democat/sweverlib fork of the SDS swervelib repository in the Drivetrain subsystem.

https://github.com/democat3457/swerve-lib


Warning

With new Azure PowerShell Az module installed, the template will fail to deploy. I retried on a VM with old PS module, and there it works fine.

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

ID: ea439429-69f0-2878-495f-92cbaf61c789
Version Independent ID: d9e2e3f9-8387-cde6-2042-93bae86645f0
Content: Visual Studio Azure resource group projects
Content Source: articles/azure-resource-manager/vs-azure-tools-resource-groups-deployment-projects-create-deploy.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@mcurko - thanks for this feedback. I am in the process of removing the recently added text about installing the Az module and adding a note that the script in the project does not work with the Az module.

adding triage labels and closing as resolved.


Fixed bugs of converters in the case of that the range of variable is 0

Summary
Fixes #1238
Details and comments
When the range of additional slack variables is 0, the InequalityToEquality and IntegerToBinary converters had unexpected behaviors.
This PR fixes that issue.

How about showing a warning that an integer variable has 0-range?
E.g.,
qp = QuadraticProgram()
qp.integer_var(name='x', lowerbound=0, upperbound=0)
# -> Warning: integer variable 'x' has range 0.

I think it does make sense. Shall I add the warning message?

I'm OK. What do you think, @stefan-woerner and @woodsp-ibm?

When adding a variable to QP the Variable class has this
        if lowerbound > self.upperbound:
            raise QiskitOptimizationError("Lowerbound is greater than upperbound!")

This seems to imply that lowerbound equal to upperbound is a valid Variable, whether it is 0 or some other number. In effect the variable is a constant value assuming at least one of the bounds is an inclusive value.
So this issue is fixing an issue in the conversion, not where the user did this but where a conversion would add a variable which would be a constant and have value 0 due to bounds. I am not sure where the problem arises with this 'constant'. It seems as an end user I am able to create such 'constants' via having the bounds the same. In one of the conversions such a constant is dropped in the other an error is raised.
On the warning suggestion is this some special case with 0 - or is it true for any with upper/lower bounds equal? Should this be a warning or should the check in Variable be changed to include equality such its an error. Maybe this equality is just an issue for these two convertors and it is fine for QP in general to have such Variables with only one possible value i.e. a constant. So I cannot say one way or another if raising a warning is the right thing to do - in my mind it depends on what is the expected behavior when bounds are the same and/or both are 0.

I think lowerbound == self.upperbound is not a valid condition as a variable. Such variable should be given as a constant of the input model. So, it is an option to modify the condition as follows.
        if lowerbound >= self.upperbound:
            raise QiskitOptimizationError("Lowerbound is equal to or greater than upperbound!")

The conversion algorithm uses an assumption that the range of bounds is non-zero.

I think having lb == ub is valid. E.g. think about some higher level algorithms (decomposition etc.) that automatically update bounds and leverage a QUBO solver underneath, then that might happen (and is not necessarily handled specifically).
So I would not at a warning.
You can either let the converter replace it by a constant and introduce the value again later to the solution. But for transparency reasons, I would just handle it as is, i.e., introduce a single qubit, that is forced to be 0.

I see. Then, we maybe need another converter to substitute 0-range integer variables with constants. It is possible to implement it using QuadraticProgram.substitute_variables.

yes, we already have this functionality via substitute_variables. We can add such a converter on our backlog. For now, I would let the user handle this special case.

OK. So, I think this pullreq is ready if the conflict is resolved. We need to make another converter IntegerToConstant as another pullreq.

Can we fix the conflict here so this can be merged - I believe the PR is ready.

Hi Steve, sorry, I had not merged the master. Now, the conflict should be solved.  Ya, the PR is ready.


Segfault when inserting embeddings into vss_table

Summary:
When inserting data into the virtual table "vss_chunks" using SQLite, a segmentation fault occurs in the C++ code of the "vssIndexUpdate" function.
Steps to reproduce:

Create a virtual table "vss_chunks" using the vss0 module with the following SQL statement:
Insert data into the "chunks" table with the following Python code:

def save_resource(resource: Resource):
    conn = create_connection()
    cursor = conn.cursor()
    cursor.execute('''
        INSERT INTO resources (url, title)
        VALUES (?, ?)
    ''', (resource.url, resource.title))

    resource_id = cursor.lastrowid
    for chunk, embedding in zip(resource.chunks, resource.embeddings):
        embedding_bytes = embedding.tobytes()
        cursor.execute('''
            INSERT INTO chunks (chunk, embedding, resource_id)
            VALUES (?, ?, ?)
        ''', (chunk, embedding_bytes, resource_id))

    conn.commit()
    conn.close()

r = salmon.create_article('https://news.ycombinator.com/item?id=34218724')
save_resource(r)

Insert data from the "chunks" table into the "vss_chunks" virtual table with the following SQL statement:

connection = create_connection()
cursor = connection.cursor()
cursor.execute('''
            INSERT INTO vss_chunks (rowid, chunk_embedding)
                SELECT rowid, embedding
                FROM chunks
        ''')
connection.commit()
connection.close()

Logs from IntelliJ when attempting the same query using its SQL console:
# Problematic frame:
# C  [vss0.so+0xb7eb9]  vssIndexUpdate(sqlite3_vtab*, int, sqlite3_value**, long long*)+0x459

Environment:
Operating system: Ubuntu 22.04.2 LTS
Python version: 3.10.6
SQLite version: 3.40.0
sqlite_vss version: 0.0.4 (installed with pip)
sentence_transformers: multi-qa-mpnet-base-cos-v1 model when generates 768 dimensional embeddings
Schema:
def init_db():
    conn = create_connection()
    cursor = conn.cursor()
    cursor.execute('''
        CREATE TABLE IF NOT EXISTS resources (
            id INTEGER PRIMARY KEY,
            url TEXT,
            title TEXT
        )
    ''')

    cursor.execute('''
        CREATE TABLE IF NOT EXISTS chunks (
            id INTEGER PRIMARY KEY,
            chunk TEXT,
            embedding BLOB,
            resource_id INTEGER,
            FOREIGN KEY (resource_id) REFERENCES resources (id)
        )
    ''')

    cursor.execute('''
        CREATE VIRTUAL TABLE vss_chunks USING vss0(
        chunk_embedding(768)
    );
    ''')
    conn.commit()
    conn.close()

Thanks for filing @MahmoudFawzyKhalil !
I'm having trouble reproducing: Can you try running this python script and see if you find the same issue?
import sqlite3
import sqlite_vss
import numpy as np

db = sqlite3.connect(":memory:")
db.enable_load_extension(True)
sqlite_vss.load(db)

print(db.execute("select vss_version()").fetchone()[0])

db.executescript("""
CREATE TABLE IF NOT EXISTS resources (
    id INTEGER PRIMARY KEY,
    url TEXT,
    title TEXT
);

CREATE TABLE IF NOT EXISTS chunks (
    id INTEGER PRIMARY KEY,
    chunk TEXT,
    embedding BLOB,
    resource_id INTEGER,
    FOREIGN KEY (resource_id) REFERENCES resources (id)
);

CREATE VIRTUAL TABLE vss_chunks USING vss0(
  chunk_embedding(768)
);

INSERT INTO resources (url, title)
  VALUES ("foo", "bar");

""")

db.execute("""
INSERT INTO chunks (chunk, embedding, resource_id)
  VALUES ("foo", ?1, 1);
""", [np.zeros((1, 768), dtype=np.float32)])

db.execute("""
INSERT INTO vss_chunks (rowid, chunk_embedding)
  SELECT rowid, embedding
  FROM chunks;
""")
db.commit()

results = db.execute("select rowid, vector_debug(chunk_embedding), * from vss_chunks").fetchall()

print(results)

db.close()

If that works, then in your original database, can you run:
SELECT DISTINCT length(embedding)
FROM chunks

And see what it returns? I have a feeling that some of the embeddings lengths are not 3072 (768*4), which might be causing the segfault

Testing the code works
Sadly it returns a single row with 3072 as the length

I managed to reproduce the issue in the script you sent:

Create a file db with one connection
Execute some statements on that connection
Close it
Create another connection and do the insert into the vss_table

Using just a single connection in my code solved the issue. Also, re-running the script on the same database is fine even though it opens a new connection, as long as it is the only one opened in that go.
import sqlite3
from typing import List, Any

import sqlite_vss
import numpy as np

db = sqlite3.connect("bla.db")
db.enable_load_extension(True)
sqlite_vss.load(db)

print(db.execute("select vss_version()").fetchone()[0])

db.executescript("""
CREATE TABLE IF NOT EXISTS resources (
    id INTEGER PRIMARY KEY,
    url TEXT,
    title TEXT
);

CREATE TABLE IF NOT EXISTS chunks (
    id INTEGER PRIMARY KEY,
    chunk TEXT,
    embedding BLOB,
    resource_id INTEGER,
    FOREIGN KEY (resource_id) REFERENCES resources (id)
);

CREATE VIRTUAL TABLE vss_chunks USING vss0(
  chunk_embedding(10)
);

INSERT INTO resources (url, title)
  VALUES ("foo", "bar");

""")
db.execute("""
INSERT INTO chunks (chunk, embedding, resource_id)
  VALUES ("foo", ?, 1);
""", [np.zeros((1, 768), dtype=np.float32)])
db.commit()

print(db.execute("SELECT * FROM chunks").fetchall())
# Close connection and create a new one
db.close()

db = sqlite3.connect("bla.db")
db.enable_load_extension(True)
sqlite_vss.load(db)

db.execute("""
INSERT INTO vss_chunks (rowid, chunk_embedding)
  SELECT rowid, embedding
  FROM chunks;
""")
db.commit()

results = db.execute("select rowid, vector_debug(chunk_embedding), * from vss_chunks").fetchall()

print(results)

db.close()

Thank you @MahmoudFawzyKhalil ! I can now reproduce, attempting a fix

Smallest possible repro:
.open tmp.db
.load dist/debug/vector0
.load dist/debug/vss0

CREATE VIRTUAL TABLE vss_chunks USING vss0(
  chunk_embedding(1)
);

.open tmp.db
.load dist/debug/vector0
.load dist/debug/vss0

INSERT INTO vss_chunks (rowid, chunk_embedding)
  SELECT 2, json_array(1);

If you create a vss0 table, don't insert any data, close the connection, open a new connection, and then try to insert into the table, it segfault. This is because we only serialize the Faiss index after write transactions are commited. But if you don't insert into the table when it's first created, there's no write transaction commit, so the index never gets written.
Will add a new test case and a new version bump shortly.

Thank you @asg017

Following for the fix as well. Was meaning to submit a bug report this week about the same behavior, noticed when I included the table setup as part of migrations in an app. Workaround (and what I did originally, which masked the issue) was to perform the table setup after seeding the database.
Looking forward to being able to remove the temporary hack around I had in place :)

This has now been fixed in v0.0.5. The loadable extensions/python package/npm package/deno module have all been updated as well.
Will close, but please file another issue if you find anything else! Thanks for the initial report.

Confirmed working for my use case. Thanks!


Rails 5.2 support

Currently it depends on rails (< 5.2, >= 4.2).

Being worked on.

Finished. Version 0.3.3 is now available on RubyGems.


Fix docstring for method flip_up_down

Can one of the admins verify this patch?

Jenkins test this please.

Jenkins test this please.

Flaky timeout of a GPU test, not related to the PR.


Include a note about no mix types of query in a single one

Changes
Fixes https://github.com/jakartaee/data/issues/732

@otaviojava this is the wrong section, that section is supposed to be the lexical structure.

You could put it in 5.3.3, for example.

You could put it in 5.3.3, for example.

done


[G810] Battlefield 1 Patch LED SDK crash

How often does this problem occur?
Always
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:

Open Aurora
Click patch logitech led sdk in BF1
Aurora Crash

What is the version of Aurora you are experiencing this issue with?
beta0.6.3
Does the previous version of Aurora have this issue?
idk
Please include any logs, screenshots, or files that are related to this issue:
Crash logs [ https://pastebin.com/kuJSQjNy ]

Did you click the button with bf1 open?

And you get the same exact error in both cases? That log looks like you probably had it open. Do it with it closed and send me a log of it still fails.

And you get the same exact error in both cases? That log looks like you probably had it open. Do it with it closed and send me a log of it still fails.

here is the latest crash logs
Open BF1 : https://pastebin.com/L64XXUZj
Close BF1 : https://pastebin.com/Yj8HxPi5

Seems like I know the problem that LogitechLed.dll used by LGS. When I close LGS I can patch led sdk but keyboard no light while in BF1 so I open LGS again but also no light too. so I patch again and then it crash again. Maybe LGS cause this?

When you patch it should send lights to aurora, but it wont send them to LGS anymore. Have you restarted your system after patching?
Also, if you want lgs to get the lights again, go into C:\Program Files\Logitech Gaming Software\SDK\LED\x64 , delete LogitechLed.dll and rename LogitechLed.dll.aurora_backup, deleting the aurora_backup part. Repeat this for C:\Program Files\Logitech Gaming Software\SDK\LED\x86 .
Again, as the wrapper makes light go to aurora, it shouldnt be needed.

When you patch it should send lights to aurora, but it wont send them to LGS anymore. Have you restarted your system after patching?
Also, if you want lgs to get the lights again, go into C:\Program Files\Logitech Gaming Software\SDK\LED\x64 , delete LogitechLed.dll and rename LogitechLed.dll.aurora_backup, deleting the aurora_backup part. Repeat this for C:\Program Files\Logitech Gaming Software\SDK\LED\x86 .
Again, as the wrapper makes light go to aurora, it shouldnt be needed.

WOW man it works. After follow your instructions it's work like charm. Thank you very much man!!

I'll close topic now


New pagination default not included in upgrade guide

In Ash GraphQL 1.0.0-rc.3, For list queries where the resource action has pagination, the graphql query now returns paginated results when previously it didn't.
I actually prefer this, but it is a change that I didn't see in the upgrade guide. I think the new default is :keyset if available.

🤔 I'm confused TBH. I thought AshGraphql always does pagination if the action supports it? Was it not doing that before?
I think the thing that changed is that primary actions are now paginatable by default.


Add convert_to_tensor in certain ops in JAX

This PR fixes the TypeError that occurs when certain ops do not retrieve the value from KerasVariable when using jax backend.
colab to reproduce the error:
https://colab.research.google.com/drive/1LeIIJsj29K3uI2t2dXmd0yhHCCkKeHj4?usp=sharing
Argument '<KerasVariable shape=(1, 2, 3), dtype=float32, path=test_layer_4/variable_4>' of type <class 'keras.src.backend.jax.core.Variable'> is not a valid JAX type.

Arguments received by TestLayer.call():
  • inputs=jnp.ndarray(shape=(10, 2, 3), dtype=float32)

The solution is to add convert_to_tensor in these ops.

Codecov Report
Attention: 37 lines in your changes are missing coverage. Please review.

Comparison is base (c8700f4) 80.14% compared to head (b0842e9) 53.90%.
Report is 36 commits behind head on master.

Files
Patch %
Lines

keras/backend/jax/numpy.py
0.00%
37 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #19186       +/-   ##
===========================================
- Coverage   80.14%   53.90%   -26.24%
===========================================
  Files         341      362       +21
  Lines       36163    39047     +2884
  Branches     7116     7563      +447
===========================================
- Hits        28982    21050     -7932
- Misses       5578    16488    +10910
+ Partials     1603     1509       -94

Flag
Coverage Δ

keras
53.90% <0.00%> (-26.09%)
:arrow_down:

keras-jax
?

keras-numpy
53.90% <0.00%> (-3.18%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


chore(RingTheory/PowerSeries/Basic): rename Polynomial.ToPowerSeries -> Polynomial.toPowerSeries

According to naming convention, it should be Polynomial.toPowerSeries. It's already MvPolynomial.toMvPowerSeries for MvPolynomial.

Thanks!
bors merge


Run ResNet Cross Entropy Experiment

Opening an issue to run the resnet with cross entropy experiment. I'll update once completed

For tracing purposes - this was logged as run silvery-frog-102 on my wandb account


Sidebar Context removes original menu entries

Hello.
When I use Sidebar Context then I only get the new menu entries, the original ones (like Activate Scene) are gone.

I also noticed that the "Configure" option is also not there when you right-click scenes in the sidebar. I just used find the culprit and it pointed me to Sidebar Context.


Generate md5sum

Added calculation of md5sum. Checked a handful against generated header files, specifically Image.msg which includes an array and a Header and TransformStamped.msg which includes a Header and another msg datatype from the same package.
Added helper methods throughout to make structs a little smarter and reduce duplicated code
Adjusted pipeline to exclusively use ROS types and data directly derived from msg file during parsing and to not do any Rust code generation until we are doing generation (specifically around literals for constants).

@Carter12s All of the tests appear to be failing for what I think is the same reason: test_msgs/Float64Stamped has a dependency on std_msgs/Header which is no longer an intrinsic type (and shouldn't be).
I could modify the pipeline for noetic to define ROS_PACKAGE_PATH, and then add ros1_test and ros2_test features similar to roslibrust tests. Is this your preferred approach?

This now fixes #82 #73 #54 all as an added bonus in my quest for passing CI.

Shouldn't this have update the generated code in roslibrust_test to include md5's for all our generated types? Why don't I see that change or a test failing because of an uncommited delta?

I added generation of the md5sum here, I did not add it to the types that are generated yet.

Something that's nasty is that we're starting to have a growth in the number of entry points for code generation which use different current working directories or which don't look at ROS_PACKAGE_PATH. It seems like it might be worth considering if we can reduce them down before releasing a 0.7.0.


consumer stucked after adding new  consumers to the KEY_SHARED subscriptions

linked issue: #8115
Consumer could be stucked. after adding new consumer to the key_shared subscriptions.  same issue #8115 raised  before , be fixed in #10096
But after testing the code, We still got stucked.
 I think it's the reason why no message send. But I haven't found why these happened

close via #10096

@gaozhangmin From the topic stats, there are 13 messages does not been acked for consumer "5382f", this might cause the mark delete position can't move forward, could you please help check why the consumer "5382f" does not ack the messages?

@gaozhangmin From the topic stats, there are 13 messages does not been acked for consumer "5382f", this might cause the mark delete position can't move forward, could you please help check why the consumer "5382f" does not ack the messages?

OK I will check it.

After I checked why messages were not acked. I found, Event there is just one key_shared cosumer without adding new consumer, unacked messages still  increment.
I tried consumer provided by bin/pulsar-client. it worked as expected.
MayBe I wrongly used the tools provided by streamnative/examples。
since it's not a bug, i will close this issue.
thanks!


Fix on parsing intalls when request is in another language than english.

For example in spanish, specially Argentina, installs are:
De 100.000 a 500.000, not 100,000 - 500,000.
Thanks to @fedejaure

This is from 2 years ago and outdated, so will close it for now.
This does, however, bring up an issue with supporting languages other than English; especially in the latest version, I rely on the additional info section's title strings, hardcoded in English, to match the correct keys and values. This is certainly going to break depending on the language, but due to the obfuscated HTML and CSS there's not a great way to make this truly language-agnostic.
Feel free to suggest something in a new issue or pull request.


Install scripts have not been created

Dependent on routes, dashboard, practically everthing:
Last thing to do

Progress: Created a configure script, which should install required packges (nodejs, ruby, git, curl .etc)
Makefile.new: Make file for installing (make, make install)

On hold


Added 404.html and text to index.html

There are merge conflicts in 'public/index.html'. Solvr them and tesend


Add Slack as a rules_xcodeproj user

Can you rebase? There is a conflict with the recent Robinhood addition.


[pre-ll] Support HLSL semantic indexes

Fixes #2748
PR checklist:

[x] tested examples with the following backends: DX11

The AttributeVar::slot on GLSL maps to the binding location of a vertex input and on HLSL maps to the index of a semantic. GLSL requires unique names for its vertex attributes and allows for a bind location to address it by index. HLSL, on the other hand, allows for multiple semantics of the same name, if they have different indexes.
~I believe this changeset will break all vertex attribute names except those with explicit semantic indexes on DX11.~ Edit: This changeset makes link_input on VertexBufferCommon try the semantic name concated with the semantic index is just the semantic name does not match anything. This is a small amount of extra work on non-directx platforms but seems to work for me.
I'm looking for advice on how to either implement this feature or workaround it in the code calling into gfx. (reworking the shaders might be difficult since they are from SPIRV-Cross, which forces all semantics in its HLSL output to be indices from TEXCOORD).
Thanks for your time!

Just to be sure, this change is currently backwards incompatible and would require adjusting all the HLSL shaders, right?

I've done some work to this branch, as my previous attempt made it require a vertex attribute have a semantic index equal to the attribute slot assigned to it.
Ideally this change should be backwards compatible, but in the latest revision I believe I have fixed a bug in the DX backend regarding multiple vertex buffers in a single pipeline (though I don't have a test for this yet).
Here's a bit of a brain dump:

AttributeVar's slot doesn't seem to do anything on directx (I am unaware of being able to explicitly set registers on individual vertex attributes is possible?)
attrib.slot was previously the value set for the InputSlot, but that's a field meant for the buffer binding index when there are multiple vertex buffers (https://docs.microsoft.com/en-us/windows/desktop/api/d3d11/ns-d3d11-d3d11_input_element_desc)

I'm unsure how this worked in the past

My current solution involves adding a "semantic_index" field on AttributeVar (that is set to 0 on all other platforms)

I tried to reuse attrib.slot for the semantic index, but it looks like that value is used as the index for some arrays in the DX impl (and setting it to existing values on multiple attributes causes indices in those arrays to be overridden)

I don't like that my solution for link_input is "try the semantic, then try the semantic with the index, then fail"

@tangmi thank you for the investigation! It would take me a bit of time to remember the internals of pre-ll DX11 backend. Overall, don't put too much trust it in - it was likely rolled out with the examples being the only test case. Saying that, the instancing example has multiple vertex buffers, which according to your findings shouldn't be working correctly, but it does.

Unfortunately I think the instancing example just happens to work. If I reorder the vertex attributes in the shader, the example stops displaying output.
Here are some observations:

It looks like DX's input element's input slot is clamped to the range of bound vertex buffers
Gfx reads the AttributeVar::slot from the order of the HLSL reflection data

So if the following vertex buffers are bound in the instance example
vertex buffer 0 => position data
vertex buffer 1 => translate and color instance data

The HLSL has a vertex defined as
struct VsInput {
	float2 pos: a_Position; // <-- will be assigned AttributeVar::slot = 0
	float2 trans: a_Translate; // <-- will be assigned AttributeVar::slot = 1
	uint color: a_Color; // <-- will be assigned AttributeVar::slot = 2
};

Then:

a_Position's InputSlot will get set to 0 (vertex data)
a_Translate's InputSlot will get set to 1 (instance data)
a_Color's InputSlot will get set to 2, but clamped to 1 (instance data)

And the example works
Reordering the vertex attributes in the shader to something like:
struct VsInput {
	float2 trans: a_Translate; // <-- will be assigned AttributeVar::slot = 0
	float2 pos: a_Position; // <-- will be assigned AttributeVar::slot = 1
	uint color: a_Color; // <-- will be assigned AttributeVar::slot = 2
};

Then:

a_Translate's InputSlot will get set to 0 (vertex data) <-- incorrectly set
a_Position's InputSlot will get set to 1 (instance data) <-- incorrectly set
a_Color's InputSlot will get set to 2, but clamped to 1 (instance data)

@kvark I think this is ready to review. All the examples run without modification (excluding render_target, which is missing HLSL shaders).
My reservations with these changes are:

Adding a DX-only semantic_index field to AttributeVar is hacky
link_input could be implemented better (i.e. T::query could generate code to look for semantic indices instead of link_input trying both, but idk how well this would work for code that manually implements query)

Thank you for evolving the PR into shippable state! Could you please rebase instead of introducing the merge commit?
Also, does @msiglreith want to have a look before we proceed?

So, the semantic name can basically be chosen randomly, right? In case of SPIRV-Cross outputted shaders, user need to be aware of the ordering of the vertex input. They need to match the declaration on the host side. Does my understanding match with the code?

The semantic name still needs to be set correctly, unfortunately. Since HLSL can't bind attributes by index, SPIRV-Cross maps the binding location to index of a consistent, but arbitrary, semantic: TEXCOORD.
As an aside, I believe any semantic could've been chosen, but I think people were mostly already using TEXCOORD for packing custom data in DX9/10. In DX11+, I think any semantic that doesn't conflict with the SV_ ones would work.

@kvark This should be rebased and ready for re-review! Please let me know if there's anything else I should do.

@kvark I've rebased the new changes into this branch and updated the PR comment at the top. There should be no actual changes from tangmi#5, but please sanity check me if you think it's a good idea!


Removing a group from the "servers" list does not delete the user from those servers

Suppose there is a user joebloggs with the following permissions:
- username: joebloggs
  user_state: present
  # ...
  servers:
    - www-dev
    - www-prod

Running this role will create the user on the "www-dev" and "www-prod" hosts.
Now suppose that the user should no longer have access to production hosts, so the users entry is changed to:
- username: joebloggs
  user_state: present
  # ...
  servers:
    - www-dev

(i.e. www-prod is removed). The joebloggs user will not be deleted from existing www-prod hosts.

Never mind, I notice in the README

Note: Deleting users is not done on purpose.


Modify css file to truncate class docs

As suggested by @yyao, it would be a bit cleaner to have only the methods summary on the page for a given class, and the docstring of the actual methods documented on a separate page.

@aphearin @yyao - if I understand this right, you're suggesting essentially that each class documentation page be split into two pages, is that right?  One with the methods docs and the other with just the list?
I think this is possible but not trivial because it probably requires some amount of hacking into autosummary to make two pages instead of one.  (Although maybe the autosummary templates can be split in this fashion? I'm not sure without looking into it more...) I don't think it would work to mess with the css itself, though - the autosummary templates give more fine-grained control for this sort of thing.
But can you clarify the motivation for this?  When I look at e.g. http://halotools.readthedocs.org/en/master/api/halotools.empirical_models.Moster13SmHm.html the first thing you always see is the summary, so I don't really see what the point is of it being on a separate page.
If the trouble is that the pages looked crammed together, it would be a lot easier to adjust the templates to inject some additional space between the sections (or even just the CSS could probably do that).

If I understood @yyao correctly, the main motivation was to make the halotools docs look more like the numpy docs. So, there would actually be many more pages than even you described, @eteq. There would be a single page per class method. I have since reviewed many of the Halotools classes and now no longer agree that this is actually preferable. There are many very short, focused class methods that have very simple behavior, and it would be overkill to give them their own page.
However, I still think @yyao has a point: each class' documentation really does get pretty crowded into a long page. And I think the hybrid solution you proposed could substantively help: adjusting the templates to having cleaner separation between the "methods summary" section and the "methods documentation" section would really help. Also, roughly equally importantly, the "methods documentation" section itself is really crowded and the distinct methods get crammed together.
That being said, I think this falls very firmly in the category of "cosmetic" changes that should not have too much time spent on. If there are simple manipulations to the CSS that can accomplish part of the remedy, that would be perfectly sufficient in my opinion, and probably the best bang-for-the-buck.


get previous Cilium pod logs

When running sysdump, we expect to have logs from Cilium pods for the Cilium pods that are currently running, as well as the previous logs for the Cilium pods, provided that such logs exist (i.e., there was a previous instance of that pod running).

@ianvernon cluster-diagnosis runs the bug tool here:
https://github.com/cilium/cluster-diagnosis/blob/4958dacb09bf7f623a70d00d7095d88c10953437/cluster-diagnosis/sysdumpcollector.py#L124
which should be the one retrieving the logs from the previous pods

@aanm bugtool runs inside the Cilium pod, which doesn't have kubectl installed in it to get the previous logs. We need to run this from outside the Cilium pod.

@ianvernon ohhh that's why then! thanks!

This functionality is present now, closing.

@ianvernon you forgot to click the button to close this ;-)


Clean up timer resources properly when using RPCBus

Fixes #1062

I don’t think that’s necessary, at most we are draining a single element.
If it becomes a performance bottleneck, we can always optimize later.
Op ma 31 mei 2021 om 19:20 schreef goshawk-3 @.***>

@.**** commented on this pull request.
In pkg/util/nativeutils/rpcbus/rpcbus.go
https://github.com/dusk-network/dusk-blockchain/pull/1063#discussion_r642609594
:

  return bytes.Buffer{}, ErrRequestTimeout

}

if !timer.Stop() {

<-timer.C

Should we drain this chan in a separate goroutine so we don't block
callTimeout
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/dusk-network/dusk-blockchain/pull/1063#pullrequestreview-672462600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHGLVWBKEVFHRGA477U6V53TQPAMVANCNFSM453GQFAQ
.


When presing ENTER it adds 4 karaktere

When pressing "ENTER" in the text box  it adds 4 karaktere even tho its empty

Nice catch, will address this soon.


how to write high performance http -> unary grpc proxy

I want to write a gateway proxy, that can transfer http request to unary grpc reqeust for backend microservice
            >------- http request --->                 >------ unary grpc reqeust ---->
client                                       gateway                                              backend service
            >------- http response--<                 <------ unary grpc response ---<

I wrote a demo with UnaryGrpcClient，but it's need aggregate both request and response in memory，how can i avoid aggregate?
public class ProxyService implements HttpService {
    private final UnaryGrpcClient client;

    public ProxyService() {
        this.client = new UnaryGrpcClient(WebClient.of("http://<IP_ADDRESS>:7777"));
    }

    @Override
    public HttpResponse serve(ServiceRequestContext ctx, HttpRequest req) {
        CompletableFuture<HttpData> future = req.aggregate()
                .thenCompose(x -> {
                    byte[] body = x.content().array();
                    Demo.ClientRequest request = Demo.ClientRequest.newBuilder()
                            .setBody(ByteString.copyFrom(body))
                            .build();
                    byte[] payload = request.toByteArray();
                    return client.execute("/protobuf.ClientRequestService/request", payload);
                }).thenApply(HttpData::copyOf);
        return HttpResponse.of(ResponseHeaders.of(HttpStatus.OK), Mono.fromFuture(future));
    }
}

but it's need aggregate both request and response in memory，how can i avoid aggregate?

An aggregation for a request seems to be needed if you want to wrap a request payload with a unary gRPC message.
If you don't want to aggregate the unary response, what you can do at the moment is forks our UnaryGrpcClient, removes the aggregation part, and return HttpResponse itself.
https://github.com/line/armeria/blob/3eef7032c7503c4525a73aa7c0148121859bab8b/grpc-protocol/src/main/java/com/linecorp/armeria/client/grpc/protocol/UnaryGrpcClient.java#L97-L115

@ikhoon thanks for the feedback，i agree with your point, that i can't avoid aggregate both request and response，because i want transfer data from one proto to difference proto.


Replace InfiniteLoop.dk URL with archive.org URL

The link to the article seems to be offline. I replaced it with a cached version on archive.org.

Thanks a lot for this PR! Well spotted!


Replace iMOD Python's regridder to xugrid's regridder

In GitLab by @JoerivanEngelen on Feb 9, 2023, 11:55
The present regridder in iMOD Python is powerful, tried and tested.
However, it is quite complicated and hard to maintain (partly shown by quite some open issues concerning the regridder in this repository).
Furthermore, it doesn't support unstructured regridding.
Recently xugrid has included a regridder module, which is an unstructured regridder, and there also already is some unexposed code for structured grids. Another advantage is that it is set up in a more maintainable way.
Probably best to have a grace period where the iMOD Python regridder is still included but a DeprectationWarning is thrown when used, as quite a few scripts depend on the old regridder.
Update (01/08/2023)

xugrid's regridder now regrids structured grids
We have no replacement for the LayerRegridder yet

In GitLab by @JoerivanEngelen on Aug 1, 2023, 15:35
added #496 as child task

In GitLab by @JoerivanEngelen on Aug 1, 2023, 15:35
marked the checklist item Make sure structured regridders works are better supported in xugrid. as completed

In GitLab by @JoerivanEngelen on Aug 1, 2023, 15:39
added #498 as child task


Add support for taxonomies, reading time and date on blog post

This PR adds support for taxonomies (tags and categories) for blog posts.
Also added the blog post date and reading time on blog post header.
Attached is the screenshot

Page shows ben-franklin tag

List of tags on http://localhost:44719/tags/

List of tags on http://localhost:36977/tags/

Table of contents

That is used to create an index template for taxonomy terms using all the custom metadata added to the taxonomy (terms.html)

Thanks @dnth for the contribution. I will try to change the design for for those elements.

You probably have a better grasp of the organization of the project than me.. i believe those adjustments are needed.. thanks a lot!


Dont use subscriptionIdentifier if broker doesnt support it

Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
Prevent subscriptionIdentifier v5 property being included in subscription if the broker has stated it does not support it.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[ ] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Any indication when we can see this merged into a Maintenance Release?
We are using AWS IoT with Nodered v3.0.2 on a fleet of production devices. We were intended to move to MQTTv5 last week, but we can't until this ends up in a release.

We plan to release 3.1 in the next week that will include this fix.
We haven't discussed whether we'll do a 3.0.x maintenance release as well at this point.


Graceful shutdown with multi component in runtime fails

In what area(s)?

/area runtime
What version of Dapr?

1.13.x

Expected Behavior
Dapr continue to accept only requests coming from main application even after receiving SIGTERM, and wait that all routines are closed before shutdown.
Actual Behavior
We suppose that an application need to communicate with multiple components (Redis + Kafka) and invoke other services (Application 2 and Application 3):

The success scenario
It's more clear i guess in the picture, but let's describe it

User HTTP invoke the application through dapr and wait for final result
The main application (App1 in the picture) invoke an external services (it can be another dapr invoke or an external services invoke)
Dapr invoke Application 2 and 3 reply with responses
Same like App2
Same like App 2
The main application call dapr for state store (redis in this use case)
Dapr invoke redis and reply with results
The main application call dapr for PubSub prosucing data (kafka in this use case)
Dapr invoke kafka and reply with status
Global Reply to the user with sucess 👍

The failed scenario
In the middle of processing and dapr recieve a SIGTERM, the next invoke or component call will fail because dapr will not anymore accept any external request and will try to finalize the last routine before shutdown.
For example : (what we have like an issue)

step (1) to (5) was successful
In same time that step (6) was outgoing dapr recieve a SIGTERM
the step (6) and (7) was successful
Next step (8) will fail because dapr will not accept the request and all request of user automatically will be failed

We observe that we have already routine not finished (the request of the user waiting the response) but we don't accept anymore any request after the SIGTERM. It's an issue because the application not finished all theire processing with all components
We have a workaround by using --dapr-graceful-shutdown-seconds. The issues with this option is:

using a timer that we cannot quantify it. Example : we can set a long duration but it prevent to stop pods when scaledown waiting this timer
we don't know how many time external processing can take. Example: if we put dapr-graceful-shutdown-seconds < external service processing then dapr start gracefulshutown and block next component (i.e. pubsub/kafka )

Hi @elabedo, does --dapr-block-shutdown-duration do what you want? This will block until the app reports as unhealthy which you can control.
https://docs.dapr.io/reference/arguments-annotations-overview/

Hi @JoshVanL , i think using --dapr-block-shutdown-duration is a workaround more than the right solution as I have described above my opinion about this option. In fact, we cannot set a duration that we cannot predict which number to set.
For Example: If we put --dapr-block-shutdown-duration=20 and the last request finished to process before(i.e. 500ms to finish), so we prevent scale down of the pod because we need to wait 19,5 seconds based on the option used. Do you confirm that @JoshVanL ?

@elabedo the given duration is an upper bound. Dapr will also stop blocking when the app reports as unhealthy, which your application has runtime context for when to do, i.e. all messages have been processed.

Hi @JoshVanL, Thank you for your answer. If you can highlight in the documentation of   --dapr-block-shutdown-duration that this value is the "upper bound".

@elabedo it is implied via the statement “from starting until the given duration has elapsed or the application becomes unhealthy”
https://docs.dapr.io/reference/arguments-annotations-overview/
I must admit that I remember the verbiage being a lot more explicit in conveying the “upper bound” behaviour, though I was thinking of the release notes.


Add basic drag & drop functionality to color instances

Hey @pabueco, thanks for the great tool! I was playing around with it and felt a drag and drop interaction for the color mixer would be handy. If it's something you're interested in including please check out this PR. It includes a simple version that relies on the HTML API (see gif below).

Hey @rocbear, thank you very much for your contribution. I really like the drag and drop functionality.
The only issue is that toggling the color picker does no longer work.  When the colored area of a <ColorCard /> is clicked, a color picker should be shown. I guess that it might have something to do with the HTML drag API in combination with the listener on the card:
on:click|self={() => (isColorPickerVisible = !isColorPickerVisible)}

Maybe this could also be fixed by only allowing the user to drag the colors with a handle, like an additional icon next to the close icon, instead of the whole element. But this might make the implementation a bit more complex.
If you fix this issue (in the way that you prefer) I will happily merge this.
Thank you! ✌

@pabueco ah right, thanks! I'll look into it and update the PR tomorrow.

@pabueco I think the problem came from Svelte not being able to tell how to keep track of the items by key, which I'd changed to colorInstance where it was previously index. I realized that doesn't matter because there's no way to uniquely identify the colors without adding some kind of ID.
I'm new to Svelte so I'm not sure if my most recent changes are ok in practice, but they seem to work. I just wrapped the #each block in a #key pragma that watches changes to a variable which I update whenever the list order is changed. It feels messy anyway because there are no visual cues to show how the list will be reordered when a drop is made.
Maybe a 'reverse order' or 'shift forward/back' button would be a better option?

So, first of all it's nice that it works now!
I also don't have that much experience with svelte, but your approach seems sensible and works well.
On the other hand it might also be a good idea to just generate a random id in the Color model and use that as the key in the loop.
I agree that it does not feel perfect, but it's a lot better than having no way to reorder the colors. And as long as a feature like this does not negatively impact the experience of the app in general I'm happy to have a working solution that has room for improvement in the future.
While I generally prefer buttons (up, down, reverse, etc.) to reorder elements because they are usually easier to implement and more consistent across devices, I don't really want to add more icons to the color cards. An option would be to add a dropdown to each color and move the delete and reorder functionalities in there. But that also doesn't sound that great to me.
So I think as long as everything is working correctly your current solution is just fine.
If you want to refine it a bit, the behaviour seen in this repl feels quite nice and seems quite easy to implement.
Thanks for your work!

@rocbear Just a quick info. I just merged this PR which added a unique id to each color instance and is used in the each loop of the mix tool. So this should allow you to remove the hacky solution with the update time.