Zoom (key: A) with vertical split windows: When minimizing the NERDTree window, split windows not resized correctly

Environment

Operating System: Red Hat Enterprise Linux release 8.2 (Ootpa)
Vim/Neovim version :version: VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 19 2021 13:59:56)
NERDTree version, found on first line of quickhelp ?: 6.10.16
Are you using any of these NERDTree-dependent plugins?

[ ] Xuyuanp/nerdtree-git-plugin
[ ] ryanoasis/vim-devicons
[ ] tiagofumo/vim-nerdtree-syntax-highlight
[ ] scrooloose/nerdtree-project-plugin
[ ] PhilRunninger/nerdtree-buffer-ops
[ ] PhilRunninger/nerdtree-visual-selection
[ ] jistr/vim-nerdtree-tabs
[ ] Others (specify):

Provide a minimal .vimrc file that will reproduce the issue.

" Occurs with minimal NERDTree install, i.e.
set nocompatible              " be iMproved, required
filetype off                  " required
" set the runtime path to include Vundle and initialize
set rtp+=path/to//Vundle.vim
call vundle#begin()

Plugin 'preservim/nerdtree'

" All of your Plugins must be added before the following line
call vundle#end()            " required

Steps to Reproduce the Issue

Open any file in vim
Open a second file in a vertical split window
Open NERDTree with :NERDTree
Press A to Zoom (maximize NERDTree)
Press A again (minimize NERDTree)

Current Behavior (Include screenshots where appropriate.)
When minimizing NERDTree, only the leftmost window is resized to occupy the entire window and all other split windows are left minimized.
Expected Result
All windows are resized, either back to previous sizes or at least equally split.

All windows are resized, either back to previous sizes or at least equally split.
This can be done by setting equalalways

All windows are resized, either back to previous sizes or at least equally split.

This can be done by setting equalalways

Thank you for the response.
Unfortunately setting this in .vimrc doesn't resolve this as it only applies after splitting or closing a window.
The A (zoom) of NERDTree is simply resizing the NERDTree browser to occupy the entire screen (when maximising) and back to it's normal width (when minimising).

Yeah I'm having issues with vertical splits with A too and was able to verify the behavior you're describing. Interestingly, after using NERDTree A, the <C-w>= command to evenly resize splits fails to adjust vertical splits to even width. I'll see if I can dig in and see what's going on.

Hey so I figured out that this issue is in lib/nerdtree/ui.vim, in the function UI.toggleZoom().
Problem:

During the zoom-ing, the function simply calls vertical resize on the window, which by default maximizes the window to the greatest possible vertical width (squishing all other vertical splits to zero-width)
During the unzooming, the function simply calls vertical resize g:NERDTreeWinSize, which restores the NERDTree but doesn't specify what to do for the other splits. In the case you're describing, the split with the lowest window number is by default getting all of the available leftover window space.

Solution:

Simply equalize split widths during un-zooming. This is made a little more complicated by the fact that winfixwidth is on by default for the NERDTree buffer, preventing split equalization with `='. However, this can be solved by simply:

Unsetting winfixwidth
equalizing the panes
Restoring 'winfixwidth'
Resizing NERDTree to g:NERDTreeWinSize as usual.

This patch fixes the issue for me:
diff --git a/lib/nerdtree/ui.vim b/lib/nerdtree/ui.vim
index a481ba4..d8b60c6 100644
--- a/lib/nerdtree/ui.vim
+++ b/lib/nerdtree/ui.vim
@@ -516,6 +516,9 @@ endfunction
 " zoom (maximize/minimize) the NERDTree window
 function! s:UI.toggleZoom()
     if exists('b:NERDTreeZoomed') && b:NERDTreeZoomed
+        setlocal nowinfixwidth
+        exe "norm! \<C-w>="
+        setlocal winfixwidth
         call nerdtree#exec('silent vertical resize '. g:NERDTreeWinSize, 1)
         let b:NERDTreeZoomed = 0
     else

I'll submit a PR


webhook detect is coming as undefined

Webhook is getting trigged where the detect is coming as undefined when there is overlap of geofences. Here is the snapshot of the geofence and fleet location https://ibb.co/DfM3GWc

Could be a bad data.


CborTextEncoderStream() correctly encoding seems flaky

https://github.com/denoland/std/actions/runs/11271769562/job/31345299955?pr=6099

fixed by https://github.com/denoland/std/pull/6101/commits/df454a0144188b4681bb06b30330f6791a8967ca


Add no-more-json

no-more-json is a little utility API I built using shuttle which filters JSON API responses for you, so you don't have to deal with massive JSON blobs consuming your network bandwidth and memory.
Here's an example from the readme:
You can curl wttr.in to get weather data, and adding format=j1 will return the data in JSON format. Unfortunately the returned JSON is massive (48kb), especially if we only want the current temperature (2 bytes: 27):
curl 'wttr.in/Detroit?format=j1'
{
    "current_condition": [
        {
            "FeelsLikeC": "27",     <-- ✅ The thing we want
            [...]                   <-- ⚠ 29 other lines we don't want ):
        }
    ],
    "nearest_area": [...],          <-- ⚠ 25 lines we don't want ):
    "request": [...],               <-- ⚠ 4 lines we don't want
    "weather": [...]                <-- ⚠ 1248 lines we don't want!
}

The jq query we'd use to extract the feels-like temperature in Celcius is .current_condition[0].FeelsLikeC
We can use no-more-json to make a request to the wttr.in endpoint, extract
the result, and then run the jq query for us on that result, so we just get
back a nice scalar value:
curl 'https://no-more-json.shuttleapp.rs/api?url=https://wttr.in/Detroit?format=j1&q=.current_condition%5B0%5D.FeelsLikeC'
"27"

If we break down that url:
curl \
    'https://no-more-json.shuttleapp.rs/api    <-- endpoint for no-more-json
    ?url=https://wttr.in/Detroit?format=j1     <-- endpoint for the API we want data from
    &q=.current_condition%5B0%5D.FeelsLikeC'   <-- URL encoded jq query to extract the data

See more details in the README

Thanks Boyd! Looks great.


Interception Support

There are any plans to support Interception like Unity (Microsoft IOC)?
Thanks,
Talento90

No plans

Thanks for the fast answer,
Interception is a powerful concept, it's a pity that is not in the roadmap. :-1:
Keep doing a great job, dotnet core is the future :+1:  :+1:
Thanks,
Talento90


feat: add Hashicorp Vault test container and test

also adds tracing library to dev deps b/c I wanted to see the TC logs and figured others might too

Tests in untouched code are failing, perhaps due to added tracing dep? That doesn't make sense, but it's all I can think of.

Overrode my local 1.79 with 1.75 to match CI, but now aws-sqs won't build b/c it needs 1.76+?

I see what happened here. I had the distinct misfortune of issuing a PR just as the upgrade to TC 0.18 landed in main :joy:


Missing small Da Vinci image

https://apps.atlasacademy.io/db/NA/script/9404490910
There should be small Da Vinci in one branch and big Da Vinci in another branch but it's all big Da Vinci.

https://github.com/atlasacademy/apps/commit/f59ea6cd40f98422c1a591dc707b09fa4bc9fcca


Support for nested variables

Adds support for nested variables in ExtractVariableInfo.  It is a targeted fix for #220.  Ideally this will be further expanded in the future to include an even broader expression subset (in particular array/slice indexing).

/cc @aarzilli

Merged, thanks for this patch! In the future, please format you commit messages according to: https://github.com/derekparker/delve/blob/master/CONTRIBUTING.md#format-of-the-commit-message.


extra ctors for RsForward

@rultor release, tag is 0.16.1

@rultor release, tag is 0.16.1

@yegor256 OK, I will release it now. Please check the progress here

Release 0.16.1 already exists! I can't duplicate it, but I posted a comment there. In the future, try to avoid duplicate releases

@rultor release, tag is 0.16.1

@yegor256 Done! FYI, the full log is here (took me 9min)


workbox-webpack-plugin inject manifest not working for 5.0.0-beta.1

Library Affected:
workbox-webpack-plugin
Browser & Platform:
E.g. Google Chrome v51.0.1 for Android, or "all browsers".
Issue or Feature Request Description:
Your request here.
I am using workbox-webpack-plugin 5.0.0-beta.1.  and I am aware that injectManifest should be taking care of all the things. here is how i do this.
I got service-worker in my src directory:
'use strict';
const utils = require('./utils')
const path = require('path')
const DotEnvWebpack = require('dotenv-webpack');
const WorkboxPlugin        = require('workbox-webpack-plugin');

console.log(path.resolve(__dirname, '../src/js/service-worker.js'));
module.exports = {
    mode: process.env.NODE_ENV !== 'development' ? 'production' : 'development',
    entry: {
        main: './src/js/service-worker.js'
    },

    output: {
        path: utils.resolve('dist'),
        publicPath: '/',
        filename: 'service-worker.js',
    },
    resolve: {
        alias: {
            '~': path.resolve('')
        }
    },

    plugins: [
        new DotEnvWebpack({systemvars: true}),
        new  WorkboxPlugin.InjectManifest({
            swSrc: './src/js/service-worker.js'
            include:[
                /\.html$/,
                /\.js$/,
                /\.css$/,
                /\.woff2$/,
                /\.jpg$/,
                /\.png$/
            ]
        })
    ]
};

import { skipWaiting, clientsClaim, setCacheNameDetails } from 'workbox-core';
import { precacheAndRoute } from 'workbox-precaching';
import { registerNavigationRoute } from 'workbox-routing';

skipWaiting();
clientsClaim();

console.log(self.__precacheManifest, " hoops1");
console.log(self.__WB_MANIFEST, " hooops2");
precacheAndRoute(self.__precacheManifest);

When i run the above config of webpack, it makes service-worker.js file in dist, but doesn't contain anything such as importScripts('manifest') and also when running in browser,
console.log(self.__WB_MANIFEST, " hooops2"); //prints empty array

console.log(self.__precacheManifest, " hoops1"); //prints undefined

What do I do?   The problem is that the generated service-worker doesn't have importScripts or anything that are precached json/js.
Any idea or help?

Hi @novaknole ,
You closed this issue, did you resolve it? Any chance you could post how you fixed it for others who are having the same issue please?


fix/meteor 2.6 for #6

For #6  Fixes to work with latest Meteor 2.6

Updated shelljs to 0.8.5.
Fix bundler plugin to pass non-uglified code instead of undefined to fs.writeFileSync in dev mode.

I've tested this with a local dev build in an existing Meteor project and everything seemed to work

To publish this will require the following:

[ ] publish the two Atmosphere packages with the publish-plugins package.json script

do we need to change the name for this community fork?
[ ] omega:meteor-desktop-bundler
[ ] omega:meteor-desktop-watcher

[ ] publish meteor-desktop to npm

this needs to be under a new name in the meteor community org. so @meteor-community/meteor-desktop maybe

I've just pushed a new commit with what I believe is all of the changes necessary to publish the npm and Atmosphere packages under new names in the meteor-community org/namespace.
If I can get access to this repo I'm happy to set up the builds for Travis, Appveyor and CircleCI to get integration tests running. I believe we can use all of the existing builds that wojtkowiak had initially created.

@KoenLav @StorytellerCZ I've just pushed a new commit with what I believe is all of the changes necessary to publish the npm and Atmosphere packages under new names in the meteor-community org/namespace.
If I can get access to this repo I'm happy to set up the builds for Travis, Appveyor and CircleCI to get integration tests running. I believe we can use all of the existing builds that wojtkowiak had initially created.

Note that this is pretty difficult to fully test locally before publishing because it creates one npm package and two atmosphere packages. I've tried my best to force my project to use local packages and everything seems to be working well but there may be some snag that I couldn't foresee

Understood, then I suggest we go with major version jump and release a beta to make sure that we can test things through.

I just encountered an issue while building with this
WARN  meteorApp:  STDERR: /Users/vagrant/git/.meteor/local/isopacks/omega_meteor-desktop-bundler/plugin.meteor-desktop-bundler.os/npm/node_modules/meteor/meteor-desktop-bundler/node_modules/chokidar/lib/fsevents-handler.js:28
  return (new fsevents(path)).on('fsevent', callback).start();
          ^
TypeError: fsevents is not a constructor
    at createFSEventsInstance (/Users/vagrant

It looks like the Atmosphere packages are using an old chokidar version 2.0, I think it needs to be updated to 3.x in both meteor-desktop-bundler and meteor-desktop-watcher

Hello, I'm looking forward to being merged.

Hi @StorytellerCZ - you mentioned 25 days ago that you have this on your weekend ToDo list. I guess something else stopped you but now we have an issue with the electron-builder being broken for MacOS as Apple took out Python 2.7 (see #6726.
Any chances that this merge request is done within the next days? Thanks Jan!

I'm merging this now. I will bump this to v3 due to breaking changes and start publishing things.

Everything is published, now we have to get the tests setup again.


Active RDP session limit

This is not an issue, just a question.
If I have around 100 users in windows 10/8, is there a limit of active RDP connections that can logged in at same time using RDP wrapper?
Nice soft. Hope there would be one for Windows server!

There is no software limit on concurrent sessions, it only depends on hardware (amount of free RAM).
RDP Wrapper is compatible with any edition of Windows NT 6.0+, with server editions too.


Added expandObject method to expand object.

Coverage increased (+0.02%) to 99.08% when pulling 1e647cdc43d362445d9cb914aaacd04565dbee4b on expandObject into 14ba8e04f3cb011d8e849f66f0edde98175d9d12 on master.

Changed version and added to version history @iamigo .


Add logo for Carli project

Description
Explaining how to add an ascii logo to your Linux distribution.
Articles and videos go on https://www.arcolinuxiso.com/13-changing-the-neofetch-ascii-logo-and-creating-a-new-one/
Thanks in advance

do not like the logo anymore
closing


help-docs: Document "Delete topic" mobile app feature.

Adds Desktop/Web tab, replaces instructions with macros, and adds a new tab with instructions for mobile app users.
Screenshots and screen captures:

Step 3 is written in uppercase letters to match the button's text formatting in the mobile app as shown below.
Is this okay or should we change it to "Delete topic"?

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@alya ready for review.

Step 3 is written in uppercase letters to match the button's text formatting in the mobile app as shown below.
Is this okay or should we change it to "Delete topic"?

Hm, good question. It seems helpful to me to match the capitalization, and we do that in https://zulip.com/help/reading-strategies for referring to STREAMS, so I think the caps are reasonable.

Those screenshots look good to me! @timabbott over to you for review.

As a follow up, I also started a discussion about the differences in the UIs: https://chat.zulip.org/#narrow/stream/48-mobile/topic/confirm.2Fcancel.20modals

Merged, thanks @drrosa!


TokenAuthenticationHandler.getRegisteredServiceJwtSigningSecret method does not retrieve the correct property

CAS server version: cas-4.2.0-RC2
Container type/version: apache-tomee-jaxrs-1.7.3
Project: cas-server-support-token
Class: TokenAuthenticationHandler
Method: getRegisteredServiceJwtSigningSecret
Line: 82

Description:
This method is supposed to return 'signing secret' value but it is returning 'encryption secret' because when using TokenConstants object it uses TokenConstants.PROPERTY_NAME_TOKEN_SECRET_ENCRYPTION instead of TokenConstants.PROPERTY_NAME_TOKEN_SECRET_SIGNING.

Thanks for the report. Would you be able to submit a patch? I imagine it's a trivial fix.

You're perfectly right.  Sure I'll submit a patch.

Fantastic.

Hi, I have seen that in the same class 'TokenAuthenticationHandler' (Line 42) on 'getAuthenticator' method, to set 'encryptionSecret' it is also calling 'getRegisteredServiceJwtSigningSecret' when it should call 'getRegisteredServiceJwtEncryptionSecret'. I am fixing that too.

Hi, it's done on waiting PR: https://github.com/Jasig/cas/pull/1558


Marker not reached if clicking between markers

While testing the 'Dynamic video' example, I noticed that, if I click between the markers on the progress bar, the markers are not considered to be reached. Actually sometimes they are and sometimes they're not. Mostly not.
Would be great if the reached markers detection would work without any error between them as well. Consider a simple menu with some so called 'chapter' buttons which should be correlated with the markers and which should be styled differently when their corresponding "chapters" are played, even if the chapter was changed by clicking between markers on the progress bar. It doesn't look very well to have the 'Chapter 1' button styled as active while the user just jumped to 'Chapter 4'.

That's a good idea. Since this may or may not be the behavior that everyone expects, I will add a Boolean option for "betweenMarkerReach". If it's true, the plugin will trigger the reach event when clicked in between the markers.

On Feb 16, 2015, at 2:23 AM, adrianpuescu<EMAIL_ADDRESS>wrote:
While testing the 'Dynamic video' example, I noticed that, if I click between the markers on the progress bar, the markers are not considered to be reached. Actually sometimes they are and sometimes they're not. Mostly not.
Would be great if the reached markers detection would work without any error between them as well. Consider a simple menu with some so called 'chapter' buttons which should be correlated with the markers and which should be styled differently when their corresponding "chapters" are played, even if the chapter was changed by clicking between markers on the progress bar. It doesn't look very well to have the 'Chapter 1' button styled as active while the user just jumped to 'Chapter 4'.

Reply to this email directly or view it on GitHub.

Closing as commit#c7fb109f handles this request.


chart label is not drawn inspite of having ample space

Describe the bug
chart label is not drawn inspite of having ample space
Module

[ x] compose
[ x] views
[ ] compose-m2
[ ] compose-m3
[x ] core (select if none of the above apply)

To reproduce
Create a chart with two data points and spacing of 30
x axis is Epoch days since 1970
y axis any value between 500-800
tickPosition = HorizontalAxis.TickPosition.Center
Expected behavior
labels should be drawn correctly
Screenshots

Android versions
Versions of Android where the bug occurs.
Additional context
Add any other context about the problem here.

Hello! Would you be able to provide a minimal reproducible example?

Sure
This is the data you need to add
//raw data from BE
listOf(
"2022-07-14" to 350f,
     "2022-08-14" to 654f,

}
//ChartEntryModelProducer
ChartEntryModelProducer {
data.map { (y, dateString) ->
FloatEntry(
LocalDate.parse(dateString?.truncateDate()).toEpochDay().toFloat(),
y?.toFloat() ?: 0f,
)
}
.let {
return ChartEntryModelProducer(it)
}
}
//xaxis configuration
val axisValueFormatter =
AxisValueFormatter<AxisPosition.Horizontal.Bottom> { value, _ ->
LocalDate.ofEpochDay(value.toLong()).month.getDisplayName(
TextStyle.SHORT,
Locale.getDefault(),
)
}
  bottomAxis = bottomAxis(
                    label = axisLabelComponent(
                        color = colorResource(id = R.color.content_fill),
                        textSize = 16.sp,
                        typeface = Typeface.DEFAULT,
                        horizontalMargin = 5.dp,
                    ),
                    valueFormatter = axisValueFormatter,
                    guideline = null,
                    tick = null,
                    tickPosition = HorizontalAxis.TickPosition.Center(
                        0,
                        NUMBER_OF_DAYS_IN_MONTH,
                    ),
                )

Please let me know if you need anything else

Thank you! TickPosition.Center#spacing isn’t necessarily the difference between the x values corresponding to two neighboring labels. To determine this difference, one must multiply the value of TickPosition.Center#spacing by the x step. In your chart, the x step is 30, and the difference is 30 squared, which is 900. Please try leaving TickPosition.Center#spacing at the default value of 1. Both labels will then be visible.

if there are three data points the labels appear without changing anything else..
I want to display month (Jan, Feb, March and so on)..if I get two values in say Jan I want to display Jan only once on the xaxis..if I leave the spacing to default 1 it displays Jan multiple times..
Can you please reopen the bug

Thank you for the clarification. We’re currently working on a new API that’ll make this (among other things) possible—I’ll let you know once it’s available. Even so, the current behavior is expected and doesn’t constitute a bug. The issue remains open, but I will be adding the “enhancement” label, not the “bug” label.

Thank you.Please fix asap.

@patrickmichalik  how is it not a bug when you can clearly see there is space to draw the label..Can you please mark these as a bug

Several conditions must be met for a label to be drawn. Here, they’re not met, and so no there’s no label—HorizontalAxis is behaving as expected and as documented. We’re working on making the API more flexible, but the behavior described here isn’t out of the ordinary, and so it doesn’t constitute a bug. Please rest assured that how this issue is labeled has no bearing on our work on the API changes that I’ve mentioned.

Vico 1.7.0 introduces the improvements mentioned. My suggestion would be to set the x step to 1 and normalize your entries’ x values such that the first day of every month corresponds to a whole number n, and the subsequent days correspond to values in the (n, n + 1) interval.

The changes introduced in Vico 1.7.0, 1.7.1, and 1.7.2 should enable you to achieve the result you’re looking for. getXStep lets you lock the x step, and thanks to AxisItemPlacer.Horizontal, you have full control over what x values labels are displayed for.

@patrickmichalik Can you please provide a solution for this? I have a similar requirement where I need to plot all values for both x and y axes, with x representing the months. I followed this link, and the chart is drawing fine. There are endless duplicate month names displayed at the bottom. Please provide a way to display only a single month with multiple values on the chart.

@praveenathuru, as mentioned above, you can use AxisItemPlacer.Horizontal to achieve this. getLabelValues lets you specify which x values are to be labeled. The spacing parameter of AxisItemPlacer.Horizontal.default is insufficient here because months differ in length. You could use spacing if you wanted the labels to be equally spaced. You’d then have to normalize the x values accordingly.

Since it’s now possible to achieve the result described here, I’ll be closing this as completed.


update a document by ID example

Hi!
I was wondering if you can provide me a quick sample code on how to update a document property by using it's ID. Thanks a lot in advance.

the update was not tagged you can check now by updating composer


Refactor to not use slog_scope

Hi, author of slog here.
First of all, thanks for using slog. I sometimes visit reverse dependencies of it, and checks what's going on.
This patch changes the API (breaking change) to take the Logger during init and most importantly not use slog_scope to set the global handler.
Generally accepting Logger manually gives the user of a library maximum of flexibility. If the app is using slog_scope it can always pass slog_scope::logger(), if not it can pass the manual logger it has. Generally libraries should not be using slog_scope (IMO) as it gets in the way of the application that are using slog_scope, might want to set their own handler etc.

On the side-note, I think using a global function in the API (init and get) is rather non-idiomatic (as using any global instances etc). WhileI guess most apps would not need multiple psl instances, it seems to me that letting the user create the Psl object and then call get() on it is the most flexible way. The user can store it globally if it wants to. But it's just my opinion, feel free to ignore it (as the PR) if you disagree.


Gitea 1.16.7 can't add users to teams

Hi. After upgrade gitea from 1.15.2 to 1.16.7. App did't add users to teams in gitea.
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 Begin an organization review: OrganizationName= liferay, OrganizationId= 18
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 6 teams were found in liferay organization
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 Skip synchronization in the Owners team
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 The LDAP ldap.server.local has 18 users corresponding to team project_incomand_developer
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 The gitea http://localhost:3000 has 15 users corresponding to team project_incomand_developer Teamid=10
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 can be added users list [{0  sberezina} {0  nbelokrylova} {0  aborovets}]
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 must be del users list []
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 The LDAP ldap.server.local has 7 users corresponding to team project_incomand_manager
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 The gitea http://localhost:3000 has 5 users corresponding to team project_incomand_manager Teamid=11
May 08 06:54:02 gitea.incomand.local run.sh[18152]: 2022/05/08 06:54:02 can be added users list [{0  aborovets} {0  gjagarian}]
May be they change API?

Hey,
There should be an offical feature in the lateste Gitea Release that supports syncing ldap and groups.
So this project probaly isnt needed anymore....

I do not think so, the Gitea LDAP group sync is expected in the 1.17 release
However I think that will not be the same functionality as this project.
I like the simplicity of your design and the way it works, it fits my use cases exactly.
As for this issue, please check my PR #19 , it seems to solve the problem on newer gitea releases.

PR#19 works for me, thx

Looks like @toshywoshy's commit fixed this issue. If anybody is still having issues, please let us know.


upgraded to work with latest underscore.js version

The current version doesn't work for the newest underscore js due to problems with calling templates (e.g count addition for the number of results) and due to deprecation of _.intersect (now _.intersection).

I guess PR #7 is what you intended to do initially?


Prebuild kernels in installation documentation

Hi,
I'm confused about what the developer installation instructions say about prebuilt kernels. This is the section:
https://xsuite.readthedocs.io/en/latest/installation.html#prebuilt-kernels
When I install from the git repositories, are the kernels automatically compiled since it says " In such a case, the kernels will be compiled automatically during the installation process when running pip install -e" or do I have to run the command xsuite-prebuild regenerate as is explained later?
If I need to run the command, what do I need to add to the path for it to be found? If I just follow the instructions I get "command not found" because it's not automatically on the path.

Hello. It should be found automatically if the xsuite package is installed


Use server-defined increment strategy

See the corresponding PR in gravity: https://github.com/artsy/gravity/pull/10133

done for now. Individual updates will be tackled with new issues/epics


Incorrect date information

I have notice that the widget send Rdates, Exdates and Until dates in UTC format to the server like '20160725T230000Z' but looks like the widget got the timezone info from the browser instead of from the timezone setting
Other issue is that when I access the field information the dates don't have a timezone and it looks like they were converted to the current one.
My browser timezone is UTC+1 and my django TIME_ZONE UTC+2
So in my case the widget send '20160725T230000Z' (datetime.datetime(2016, 7, 25, 23, 0, tzinfo=tzutc())) and when I access the field it contains datetime.datetime(2016, 7, 26, 1, 0).
Any ideas, can this be fixed somehow? Thanks

I have the same issue, the widget does indeed use the browsers timezone setting, but serializes with the django timezone setting (by using pytz).

I am also having the same issue.. the value which is saved is one day less than the required.

I actually solved this by including settings.TIMEZONE = 'My Tz', i didnt realize it wasnt in settings so dates werent converted back properly

I think that this PR https://github.com/django-recurrence/django-recurrence/pull/104 fixes the issue.
@audiolion

but serializes with the django timezone setting (by using pytz).
Are you sure about this? As far as I can see, it just strips the timezone information when serializing.

My current solution was to remove the timezone information from the frontend and letting the backend to convert that date to the current timezone.
diff link (ignore the changes on recurrence-widget.js)

Coming here with the same issue.
More generally, why is this package serializing time information in an RDATE in the first place, even while the frontend widget does not include a time selector?
My team is using this package in an application where we need a set of dates, nothing more. We handle time and timezone separately so that a user, for instance, in Asia can write details relevant to an object located in the EU (saving that timezone), while this data is stored on a server in the US. They select the timezone for this object, they select the time of day relevant to that timezone, and they select the dates; while we do the math and combine all three in the backend.
Meanwhile, this package takes in RDATEs as datetimes set to midnight in the user's browser's timezone, converts that to UTC (on the frontend), then serializes it in the database, then reads it back and automatically converts it to the server local timezone and presents those RDATEs as naive datetimes. What in tarnation?
If you're going to serialize time data, please add a time selector with timezone selector to perform the math properly, and/or include additional parameters from the RFC 2445 spec to indicate the timezone used for a datetime without converting it to UTC. Either that, or drop time serialization entirely and just use the bare date: RDATE:20180613 ought to be valid and produce a simpler datetime.date object.

@GriceTurrble - nice to hear you're using django-recurrence, thanks for the feedback!
If you want django-recurrence to serialize time data differently, please send a pull request. This particular behaviour hasn't ever bitten me (or presumably, any of the other maintainers), so we've never addressed it. As far as I know, we're all working on this in our spare time, by the sounds of your comment you're using it at work*, so perhaps you might have time to work on finding a way forwards here?

apologies if I misinterpreted your comment :)

Yes, this is being used in a work context, though to contribute I'd have to do so on personal time.
That said, I noticed that we are actually using an older version of django-recurrence (1.2.0). Please take what I said earlier with a big grain of salt, as I may be way off base here. Sorry!

Off-topic, but my issue is less about time and more about code ownership. Best to keep things separated to avoid potential problems down the line.
On-topic: I've upgraded to the latest and the same issue exists, with an RDATE being serialized with time information using the user's local machine settings, converted to UTC, and all the rest.
I propose, and aim to work on:

Change the frontend widget/s so that it/they serialize dates as bare dates, without adding time data of any kind. Unless someone else wants to add a widget that collects time data, which I don't think is necessary, then any JS code calculating time can be stripped down.
Allow backend to store datetime.date objects in the form 'RDATE:YYYYMMDD', and de-serializing this format back to datetime.date objects.
If a naive datetime is serialized, it should be localized on server local timezone settings if present (UTC if not). If it is aware already, pass.
Serialize datetime using the second format described in RFC 2445 (Section "<IP_ADDRESS>"), which uses the TZID property to identify the timezone by name.

Continue to support reading the first format, which is already in use, for backwards compatibility.

De-serialize datetimes as timezone-aware by attaching the same timezone originally serialized (perform no implicit conversion to server local timezone)

Optionally add a property on the recurrence field for "utc_rdates" that presents the list of rdates converted to UTC (as a read-only property).

All that and hopefully nothing blows up. :)

Thanks @GriceTurrble. That all sounds good to me. We may want to make this behaviour opt in for at least one release. One thing I'm a little confused about - if we're stripping out times entirely (per your first point), under what circumstances would we be serializing datetimes instead of dates?

Without adding a time selector to the widget, the benefit would be for the
backend. Users may choose to create recurrences programmatically by storing
datetime objects, which can already be serialized with time data. It
wouldn't make sense to remove this functionality as an option.
On Thu, Jun 14, 2018, 12:37 AM Dominic Rodger<EMAIL_ADDRESS>wrote:

Thanks @GriceTurrble https://github.com/GriceTurrble. That all sounds
good to me. We may want to make this behaviour opt in for at least one
release. One thing I'm a little confused about - if we're stripping out
times entirely (per your first point), under what circumstances would we be
serializing datetimes instead of dates?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/django-recurrence/django-recurrence/issues/70#issuecomment-397167847,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJgMPQ57sP-L4YRtvXQk51wHGyPydP2zks5t8eiCgaJpZM4JVg4Q
.

Hi guys, has this been considered for the near future? Or is this project not maintained anymore? Trying to figure out if it's worth adopting it. Looks like the timezone issue is a big one.

This isn't something I'm looking at @pasevin - it's never caused me any issues personally, and I couldn't reproduce the issue when I tried IIRC.
As to whether the library is maintained - it has quite a few active users I think, but I'm no longer doing any feature development or bug fixes myself, as I no longer use this library. That said, I do my best to merge pull requests in a timely fashion, and respond to issues when I see them.

My current solution was to remove the timezone information from the frontend and letting the backend to convert that date to the current timezone.
diff link (ignore the changes on recurrence-widget.js)

I tried it out at it fixes this annoying issue! I think this would be a great addition. I will create a pull request based on this and let the @dominicrodger decide.


download problem

hi i am on an mac an use filzilla and the examplesketch on esp32 without sd

it connects and i see my stored file inside spiffs folder
when i try to download an empty file is downloaded (it shows in filezilla that the file shouldnt be empty)
filzilla ask me to overwirte the empty file and then its still empty

what am i missing ?  is there a permission in the esp32 code i can activate?
or are the filzilla setttings wrong?
i kindly appreciate your help

still not working :/ i started everything new and changed to active mode :/

please check again the serial console.

sorry
Connected to Ananasbude
IP address: <IP_ADDRESS>
...---'''---...---'''---...---'''---...
New Connection from <IP_ADDRESS>:61205
USER ftp
PASS ftp
SYST
FEAT
CWD /SPIFFS
PWD
TYPE I
PORT 192,168,8,54,239,22
MLSD
TYPE A
PORT 192,168,8,54,239,23
RETR vibrations.txt
PORT 192,168,8,54,239,25
RETR vibrations.txt
PORT 192,168,8,54,239,26
RETR vibrations.txt
PORT 192,168,8,54,239,27
RETR vibrations.txt


Parse metadata

[ ] Parse Metadata and MetadataColumn files into memory
[ ] Rewire ProvDAG to use ProvNodes as nodes

Superseded by https://github.com/ChrisKeefe/provenance_py/pull/12, which turned out to be big enough to merit its own independent commit to main.
metadata parsing will be handled in a future PR.


Issue #53190 fix: step 23 of RPG game

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #53190

Hey @ajcruise007
Thank you for opening this pull request.
Related issue is limited only to the first time contributors to this repository. As such I'm going to close this PR. We would welcome future pull requests from you.
Thank you and happy coding.


Remove ValidateOperandBaseType() for  OpenCL.DebugInfo.100

@bashbaug, FYI.

@AlexeySotkin Could you please provide me with some information? e.g., why we need this change.

Oh I saw the commit message. Never mind.
Just one thing unclear for me is the DebugTypeVector.
You said "components of a vector also may be a typedef (uint)", but uint is a basic type that can be expressed by DebugTypeBasic. Am I wrong?

Just one thing unclear for me is the DebugTypeVector.
You said "components of a vector also may be a typedef (uint)", but uint is a basic type that can be expressed by DebugTypeBasic. Am I wrong?

There is unsigned int the basic types table, but not uint

I checked the vector types of OpenCL C and their base types are parts of the basic types that can be described by DebugTypeBasic.

I think it can but in LLVM/Clang it is implemented as the following:
typedef unsigned int uint;
...
typedef uint uint4 __attribute__((ext_vector_type(4)));

Here  is how uint4 is represented in LLVM IR. It preserves the typedefs. I think in C/C++ we can typedef almost any type.

@jaebaek are all failures in CI caused by my patch?

Yeah. Some unit tests fail.
[----------] Global test environment tear-down
[==========] 5505 tests from 338 test suites ran. (13246 ms total)
[  PASSED  ] 5499 tests.
[  FAILED  ] 6 tests, listed below:
[  FAILED  ] ValidateOpenCL100DebugInfo.DebugTypePointerFail
[  FAILED  ] ValidateOpenCL100DebugInfo.DebugTypeQualifierFail
[  FAILED  ] ValidateOpenCL100DebugInfo.DebugTypeVectorFail
[  FAILED  ] ValidateOpenCL100DebugInfo.DebugTypeVectorFailComponentZero
[  FAILED  ] ValidateOpenCL100DebugInfo.DebugTypeVectorFailComponentFive
[  FAILED  ] AllOpenCL100DebugInfoFail/ValidateOpenCL100DebugInfoDebugTypedef.Fail/1, where GetParam() = ("%foo_name %dbg_src %dbg_src 1 1 %comp_unit", "Base Type")

 6 FAILED TESTS
  YOU HAVE 16 DISABLED TESTS

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This is stale.  I will close it.


[SR-13304] Remove explicit use of Python2

Previous ID
SR-13304

Radar
None

Original Reporter
@tbkka

Type
Sub-task

Additional Detail from JIRA

Votes
0

Component/s

Labels
Sub-task

Assignee
None

Priority
Medium

md5: 38c0ab4bee9aefa3422c3e8887cda475

Parent-Task:

SR-13280 Migrate Swift to Python 3

Issue Description:
gyb is still pinned to python2.7
Several md documentation files refer to Python 2.7
`git grep -i python2` for a complete list of references to Python 2.

done in the following patches:
https://github.com/apple/swift/issues/58286
https://github.com/apple/swift/issues/58325
https://github.com/apple/swift/issues/58334


Remove ViewerWindowManager::Instance()

The viewer refactoring provides access to most important viewer objects via a Get method in ViewerBase instead of using ::Instance() all over the place. The object that gets created can be created on demand in the Get method either directly or via ViewerFactory, which can permit objects to be overridden. The ::Instance() pattern does not permit inheritance either, which was the chief cause for removing ::Instance() for so many other viewer classes. 1. Remove the ::Instance() method from ViewerWindowManager2. Create a GetViewerWindowManager() method in ViewerBase that returns the single instance.3. Replace all occurances of ViewerWindowManager::Instance() with GetViewerWindowManager()
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1997
Status: Pending
Project: VisIt
Tracker: Feature
Priority: High
Subject: Remove ViewerWindowManager::Instance()
Assigned to: -
Category: -
Target version: -
Author: Brad Whitlock
Start: 09/24/2014
Due date:
% Done: 0%
Estimated time:
Created: 09/24/2014 02:14 pm
Updated: 10/13/2014 01:01 pm
Likelihood:
Severity:
Found in version: 2.12.3
Impact: 3 - Medium
Expected Use: 3 - Occasional
OS: All
Support Group: Any
Description:
The viewer refactoring provides access to most important viewer objects via a Get method in ViewerBase instead of using ::Instance() all over the place. The object that gets created can be created on demand in the Get method either directly or via ViewerFactory, which can permit objects to be overridden. The ::Instance() pattern does not permit inheritance either, which was the chief cause for removing ::Instance() for so many other viewer classes. 1. Remove the ::Instance() method from ViewerWindowManager2. Create a GetViewerWindowManager() method in ViewerBase that returns the single instance.3. Replace all occurances of ViewerWindowManager::Instance() with GetViewerWindowManager()
Comments:

Duplicate of #2002


Fix #33 by stopping the ConsumerWorker on lease loss

ConsumerWorker with related CheckpointWorker should be stopped on lease loss.
In case of a lost lease, KCL calls the shutdown method of the record processor.
Current implementation logs this call but does not react.
This change will use the graceful shutdown functionality already implemented in the ConsumerWorker for this case.
Since both methods define a checkpointer, it is used to checkpoint instead of the last used one.
I see the correct behaviour with my local manual tests.

Coverage decreased (-0.8%) to 85.989% when pulling 2727dd17d7a0ec986cef2799072cc6e2930a0050 on aquamatthias:mv/fix_33 into 2b258399e07d592be14e911fac8cae4fdea933b6 on WW-Digital:master.

Fixes: https://github.com/WW-Digital/reactive-kinesis/issues/33

Looks good, thanks @aquamatthias !
Couple of questions:

Have you seen the checkpointer change during shutdown? as in, different to the latest checkpointer that's cached? It does make sense that it could change.
Can we add an integration test for this? I'm hoping to get the big Akka Streams PR merged for you over the weekend so that'll give us more int tests in master.

Thanks again for the contributions!!

@markglh

both cases (shutdownRequested and shutdown) explicitly give a CheckPointer. I did not spot a change of the original one, but I think it makes sense to use the provided one.
It was rather hard for me to test the fix locally. I created multiple consumers and restarted some several times, where some stayed alive (so shard workers were created and teared down). Let me think if I can create a simpler integration test. I agree it would be beneficial.

Thanks @aquamatthias - I appreciate that it's a tough one to reproduce reliably!
I tend to agree with regards to passing the checkpointer, would you mind renaming it though to avoid shadowing here - perhaps to shutdownCheckpointer?:
https://github.com/WW-Digital/reactive-kinesis/pull/40/files#diff-ab2f6f101bf09376de753af8e8f829f6R451

Renamed the checkpointer as suggested.
Next step: write an integration test for this fix.

Coverage decreased (-0.7%) to 86.066% when pulling 27e399f4918cc410b45b0ae7df2cb25dbf95a9cc on aquamatthias:mv/fix_33 into 2b258399e07d592be14e911fac8cae4fdea933b6 on WW-Digital:master.

Thanks @aquamatthias!

@markglh Rebased and added an integration test, that ensures that ConsumerProcessingManagers are stopped if a lease is lost.

Coverage increased (+0.3%) to 88.693% when pulling 4f7af861b43d3407f5815a97fa4a97e4c4d6f0b4 on aquamatthias:mv/fix_33 into 765c1c8b10895dadf48b02a6266e557e79bf676c on WW-Digital:master.

Coverage decreased (-0.4%) to 88.0% when pulling 89005560aa6e319c1d37f25c11e5486730684a3d on aquamatthias:mv/fix_33 into 765c1c8b10895dadf48b02a6266e557e79bf676c on WW-Digital:master.

Coverage decreased (-0.2%) to 88.25% when pulling df54f96f187094fc54614989ee960b89b2d9e259 on aquamatthias:mv/fix_33 into 765c1c8b10895dadf48b02a6266e557e79bf676c on WW-Digital:master.

Just tweaked the coveralls settings to be a little more reasonable :)

Coverage decreased (-0.2%) to 88.25% when pulling df54f96f187094fc54614989ee960b89b2d9e259 on aquamatthias:mv/fix_33 into 765c1c8b10895dadf48b02a6266e557e79bf676c on WW-Digital:master.

@markglh Thanks - I don't want to decrease coverage, but this one can only be tested in integration.
The patch is good from my site. I already use this fix in my setup and have not seen this exception since then.

Great @aquamatthias - you happy for me to merge?

Thanks again @aquamatthias  - really appreciate the contributions! I'll get a release sorted in the next couple of days. I might push a few updates for the latest KPL/KCL at the same time, we're a bit behind!
https://github.com/awslabs/amazon-kinesis-client#release-notes
https://github.com/awslabs/amazon-kinesis-producer#release-notes


Cannot find repo in HACS?

Hi,
I have tried to search for the repo - novafos. But it is not there.
Home Assistant Community Store
Integrationsversion:	1.26.2
Frontend-version:<PHONE_NUMBER>3628
Repositories:	1083
Home Assistant 2022.7.0
Brugerfladeversion: 20220706.0 - latest

That is because the integration is not published on the HACS list (I haven't dared to to that).
So do this:
In HACS Go -> integrations -> ... (upper right corner) -> custom integrations.
Add this repository:

Then you should be able to find it when searching in the HACS integration list.
I see this is not mentioned in the README, so I'd better fix that there as well.

Sorry for the late reply!
Thanks for the information. I installed it the manual way, but I think I am missing something. It does not show latest hour or usage today. I will go thrugh the documentation - since I might have missed something.
But this is SOOOO cool :-).
Will close this.

I am in progress with adding this to HACS default, so it can just be found without adding the repo manually.  Your issue pushed me the last 10cm :-)
As for data retrieval you will not see any until the next day because data is delayed in the datahub.  In the attributes you should see the last date data from the hub was valid.  So give it a few days and data should appear over time.


Unable to install grpcio-tools on Python 3.11.5 (MacOS)

I know there are a few closed issues in this repo on this topic and some help in the Troubleshooting.MD but none of those helped me resolve my issue or were similar to the issues I experienced during install.
What version of gRPC and what language are you using?
1.48.2 - Python
What operating system (Linux, Windows,...) and version?
MacOS 14.2.1 (23C71) - (Intel Mac)
What runtime / compiler are you using (e.g. python version or version of gcc)
Python version 3.11.5 and gcc installed by Homebrew (v13.2.0)
What did you do?
Please provide either 1) A unit test for reproducing the bug or 2) Specific steps for us to follow to reproduce the bug. If there’s not enough information to debug the problem, gRPC team may close the issue at their discretion. You’re welcome to re-open the issue once you have a reproduction.

Install Python 3.11.5 and gcc 13.2.0 gcc with brew
Create a virtualenv with the python executable
Activate and run: pip install grpcio-tools==1.48.2

What did you expect to see?
Installs grpcio-tools without any issues
What did you see instead?
Build failure with what seems to be issues related to changes made in Cython in Python 3.11 (https://github.com/python/cpython/issues/89874)
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Full install log:
install.log
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?
Note: I am also experiencing the same build issues in a kubeflow pipeline I am running on google-cloud which uses the python:3.11 docker base image.

Hi, we don't support Python 3.11 for 1.48.2, the oldest version should be 1.49.0 for Python 3.11 support.


No executable in ROS Noetic

Installed with:
sudo apt-get install ros-noetic-system-fingerprint
Ran:
rosrun system_fingerprint imprint
But there is no executable in the share directory.

Can you run apt show ros-noetic-system-fingerprint | grep Version?

Version: 0.6.1-1focal.20221124.025315

That's odd, that's what I have on my end too. Can you run rospack profile and then give the exact output of the following commands:
ls -al /opt/ros/noetic/lib/system_fingerprint/
rosrun system_fingerprint imprint

$ ls -al /opt/ros/noetic/lib/system_fingerprint/
ls: cannot access '/opt/ros/noetic/lib/system_fingerprint/': No such file or directory


Tp2000 766  Measure condition validations & Automatic negative action generation

TP2000-766 Measure condition validations & Automatic negative action generation
Why
Condition codes always require 1 or more positive actions and no more than 1 negative action eg you can have three positive condition actions in a B code, but there must be 1 negative action code. If there is 1 positive action in the condition code then there must be one negative action code in the same condition code. For all positive actions under the same condition code the action code must be equal.
The only time you can have more than negative action code is if different condition codes are applied, both B codes and E codes for example.
To make the journey simpler for users, and to correct issues with the create measure conditions page in the create measure wizards validation improvements have been made at field, form and formset level. We also no longer create the negative actions in the form and they are generated on the creation of the measure and can be viewed from the workbasket details page.
This PR does not include negative action generation when importing conditions via the importer.
This PR does not include displaying the negative actions generated in the create measures review page, the edit measures view or the create measure conditions step in the create measures journey.
This PR does not edit negative actions.
What
This PR includes:

validation on the create measure conditions form page

Inline errors will now appear inline for field errors in the form set
Non field errors in a form will now also appear at the top of the individual form in the formset
Add accross form formset validation

Validation to ensure certificates are not duplicated across the same condition
Validation to ensure prices cannot be duplicated across the same condition
Validation to ensure action codes are equal across the same condition
Validation to ensure conditions are added in alphabetical order

MeasureActionPair model added

save constraints to ensure invalid pairs cannot be created
data migration to create exisiting pairs based on existing action codes
uses this model to filter out negative action codes out of the queryset for the action field in the Measure condition form, so only positive and neutral actions can be created from the drop down.
autogenerates the negative actions at the end of the sequence of positive actions when creating measure conditions at the create measure journey.

Includes a couple docker changes (small)

Checklist
Requires migrations - Yes
Required to create measureActionPair model in db and then migrate the data from the existing MeasureAction model.

Codecov Report
Patch coverage: 92.70% and project coverage change: +0.03 :tada:

Comparison is base (5e0baa0) 92.23% compared to head (d250c32) 92.26%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #877      +/-   ##
==========================================
+ Coverage   92.23%   92.26%   +0.03%
==========================================
  Files         412      412
  Lines       27264    27525     +261
  Branches     2050     2065      +15
==========================================
+ Hits        25148    25397     +249
- Misses       1725     1739      +14
+ Partials      391      389       -2

Impacted Files
Coverage Δ

measures/patterns.py
91.70% <ø> (ø)

measures/tests/test_views.py
98.03% <45.83%> (-1.97%)
:arrow_down:

measures/models.py
97.87% <95.00%> (-0.19%)
:arrow_down:

common/tests/factories.py
99.40% <100.00%> (+<0.01%)
:arrow_up:

measures/forms.py
97.17% <100.00%> (+0.14%)
:arrow_up:

measures/tests/test_forms.py
100.00% <100.00%> (ø)

measures/tests/test_models.py
100.00% <100.00%> (ø)

measures/validators.py
96.39% <100.00%> (+1.21%)
:arrow_up:

measures/views.py
97.44% <100.00%> (+0.05%)
:arrow_up:

... and 10 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Cannot enter Visual mode

when I hit v in Normal mode to enter Visual mode, I get an error:
E5107: Error loading lua [string ":luaa.]:1: unexpected symbol near '\'
:call tagalong#Trigger("

and so if I hit viw to select current word i get the same error with the iw entered as parameters for tagalong#Trigger(
E5107: Error loading lua [string ":luaa.]:1: unexpected symbol near '\'
:call tagalong#Trigger("iw

:version
NVIM v0.5.0-dev+1414-g8cdffd42d
Build type: Release
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -DNDEBUG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict
-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-commo
n -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -
DMIN_LOG_LEVEL=3 -I/home/alexis/Applications/neovim/build/config -I/home/alexis/Applications/neovim/src -I/home/alexis/Application
s/neovim/.deps/usr/include -I/usr/include -I/home/alexis/Applications/neovim/build/src/nvim/auto -I/home/alexis/Applications/neovi
m/build/include

Hm, I just tried it on NVIM v0.5.0-dev+1421-ga72dfec85, and I can enter visual mode just fine, so I can't reproduce the issue with just this information.
How do you install and load the plugin? What I put in .config/nvim/init.vim is:
call plug#begin('~/.local/share/nvim/plugged')

Plug 'AndrewRadev/tagalong.vim'

call plug#end()

I think there might be something about the loading process, because the message says "Error loading lua". I think for some reason, it's trying to evaluate vimscript as lua, but I don't know why. Could you share your neovim config and how you've set the plugin up?

I have the same problem. Pressing v or even attempting to change a tag results in the following
E5107: Error loading lua [string ":lua"]:1: unexpected symbol near '\'
:call tagalong#Trigger("

I tried building Neovim from source, since I know there was a recent PR merged that allows lua config to be loaded -- I thought maybe it's related? But I still can't replicate it with this version:

One thing you could to in order to at least avoid breaking v is to exclude it from the "mappings" list by putting this in your config:
let g:tagalong_mappings = ['c', 'C', 'i', 'a']

This doesn't solve the issue, of course, and I would appreciate if you keep experimenting so we can figure it out.

I tried building Neovim from source, since I know there was a recent PR merged that allows lua config to be loaded -- I thought maybe it's related? But I still can't replicate it with this version:
:version
NVIM v0.5.0-dev+1425-g7da86f55a
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3

Could it be a temporary bug that was fixed? Could you try updating to the latest master and trying it out again?
I also tried :help E5107, but I'm getting E149: Sorry, no help for E5107, so I don't know how to approach debugging the problem :/

I actually remember that I had this exact problem a few months ago when trying out Neovim 0.5 for the first time, so it is not a recent problem. I tried to debug it a bit for you, and it seems when I include https://github.com/folke/which-key.nvim in my config, it actually seems to break this plugin.
call plug#begin()
Plug 'AndrewRadev/tagalong.vim'
Plug 'folke/which-key.nvim'
call plug#end()

lua << EOF
  require("which-key").setup {}
EOF

Interesting. Runninng :checkhealth which_key does give me this:
health#which_key#check
========================================================================
## WhichKey: checking conflicting keymaps
  - WARNING: buffer-local keymap overriding global for mode **"n"**, buf: 0, lhs: **"c"**
  - INFO: old rhs: `:<c-u>call tagalong#Trigger("c", v:count)<cr>`
  - INFO: new rhs: `<cmd>lua require("which-key").show("c", {mode = "n", auto = true})<cr>`
  - WARNING: buffer-local keymap overriding global for mode **"n"**, buf: 0, lhs: **"v"**
  - INFO: old rhs: `:<c-u>call tagalong#Trigger("v", v:count)<cr>`
  - INFO: new rhs: `<cmd>lua require("which-key").show("v", {mode = "n", auto = true})<cr>`

So there's a conflict in mappings, although it theoretically shouldn't be a problem. Weirdly, I still can't replicate the issue even with your above config.
One possibility I'm considering is that it's related to tagalong's behaviour of trying to maintain mappings. Basically, if there's already a mapping for v from the config or from some other plug, it'll try to execute it -- this is probably what's happening here, that tagalong is executing a command that's executing lua code and this is somehow getting messed up. Once again, can't quite replicate it, so hard to say for sure.
Could you execute :map v and show me the results? Here's what I see on my neovim installation:
n  v           *@:<C-U>call tagalong#Trigger("v", v:count)<CR>
n  viÞ         * <Nop>
n  vaÞ         * <Nop>
n  vÞ          * <Nop>
n  v           * <Cmd>lua require("which-key").show("v", {mode = "n", auto = true})<CR>

Mine shows:
n  v           *@:<C-U>call tagalong#Trigger("<Cmd>lua require(\"which-key\").show(\"v\", {mode = \"n\", auto = true})<CR>", v:count)<CR>
n  vaÞ         * <Nop>
n  viÞ         * <Nop>
n  vÞ          * <Nop>
n  v           * <Cmd>lua require("which-key").show("v", {mode = "n", auto = true})<CR>

I think I understand what the problem is. It seems like Neovim has something called <Cmd>, which just aborts the current command-line and does its thing. I think maybe I could get it to work if I replace it with :, but I'm not sure if this won't cause unfortunate side effects. Feels like the safest thing to do is to avoid nesting it. I've pushed a commit that does this, could you try it out?

I think I understand what the problem is. It seems like Neovim has something called <Cmd>, which just aborts the current command-line and does its thing. I think maybe I could get it to work if I replace it with :, but I'm not sure if this won't cause unfortunate side effects. Feels like the safest thing to do is to avoid nesting it. I've pushed a commit that does this, could you try it out?

Yep it works! Thank you.

Great, thanks for helping with the debugging process.
@AlexisFinn Could you try pulling the latest version as well?

Wow, @rbozan @AndrewRadev thanks for looking into this issue so quickly and efficiently.
Sorry I didn't watch this issue so intently as I must admit I can live without tagalong.
So it's a conflict with which-key, I kinda figured it was something like that (I mean surely this would have been spotted otherwise).
Ill try pulling the latest version and see if it works immediately.

Seems to work fine now. Great work, thanks alot.
Closing this issue since it's solved.

Awesome, thanks for checking :+1:


Computation time to show all solutions for given blockers pattern

How many combinations should the software test to list all possible solutions for a given blockers pattern?
The red piece can be rotated or flipped in 4 different ways and it should be tested on 36 different cells, obviously some positions could have a blocker or another already placed piece but in terms of iterations just the red piece accounts for 4*36 combinations, this value has to be multiplied by the combinations of other pieces. This is a huge number and then listing all possible solutions for a given blockers pattern is not possible in a reasonable time.
What's your opinion?

Hi @adibacco , sorry for the delay in responding, I don't check GitHub too often nowadays. Couple of points regarding your questions:
I don't think 4*36 is a huge number (144), and you have to remember that (a) there won't be the full 36 possible places to check for because of blocker pieces, and (b) once you have a single piece in place, the number of possible locations for the next piece is also smaller because you have blockers and the first piece, and so on, and so on.


feat(docs): automatically generate longhornctl documents from the commandline usage

Which issue(s) this PR fixes:

Issue https://github.com/longhorn/longhorn/issues/8992
What this PR does / why we need it:
Automatically generate longhornctl documentation from command line usage.
Benefits:

No need to update README.md with changes in command line usage.
Users can quickly find usage information without downloading longhornctl and running longhornctl --help.

TODO:

We need to add Example in cobra.Command{}.
Add a new page in longhorn official document for introducing the CLI and add link to the README.md.

Special notes for your reviewer:
Additional documentation or context

@mergify backport v1.7.x


Modem bridge not working across dimensions

The Wireless Bridge does not work across dimensions.
I am using CCTweaks version 0.3.2 and computercraft version 1.75

Just a couple of things to check:

How are you binding the two bridges: do they work in the same dimension?
Are both ends chunk loaded?

the 2 blocks are placed like this: [bridge][network cable][wired modem][advanced computer] and connected via the data card item
and yes, both ends are chunkloaded

Could you explain how to set them up?

That should work correctly. I'll have a look.

Updating forge has resolved the issue for me

Hmmmm, very odd. I'm going to close this as I it seems to work on my end and you've managed to fix it.


Merge sweeping personal changes

Overall gameplay, specifically BeatMinecraft has been made more reliable.

that's a lot


Remove the minimize webpack optimization.

--optimize-minimize interferes with @Input an @Output detection.

Preapproved by @igor-ka


Virtual/override mapper methods cause compile errors

Describe the bug
If the partial mapper method declaration has the virtual, override, sealed or new modifier then Mapperly generates invalid code. The generated code then has the compiler error CS8800 ("Both partial method declarations must have identical combinations of 'virtual', 'override', 'sealed', and 'new' modifiers.")
To Reproduce
Steps to reproduce the behavior:

Create mapper classes like shown below.
Try to comple the code.

Expected behavior
Valid code should be generated.
Code snippets
[Mapper]
internal partial class TestDtoMapper
{
    public virtual partial TestDto MapToDto(TestEntity entity);

    public partial TestEntity MapToEntity(TestDto dto);
}

[Mapper]
internal partial class TestDtoMapper2 : TestDtoMapper
{
    public override partial TestDto MapToDto(TestEntity entity);
}

[Mapper]
internal partial class TestDtoMapper3 : TestDtoMapper
{
    public sealed override partial TestDto MapToDto(TestEntity entity);

    public new partial TestEntity MapToEntity(TestDto dto);
}

Environment (please complete the following information):

Mapperly Version: 3.0.0
.NET Version: 7.0.307
Target Framework: net7.0
IDE: Visual Studio v17.6.6
OS: Windows 10

Also found that the following causes the error Both partial method declarations must have identical combinations of 'virtual', 'override', 'sealed', and 'new' modifiers
[Mapper]
public static partial class Mapper
{
    static partial B Map(A source);
}

// generates
private static partial global::Riok.Mapperly.Sample.Mapper.B Map(global::Riok.Mapperly.Sample.Mapper.A source)

    static partial B Map(A source);

That shouldn't be valid code. When I try this I get CS8796 ("Partial method 'Mapper.Map(A)' must have accessibility modifiers because it has a non-void return type.") in the non-generated code.
When I test it with a void return type (and a target parameter) I get a compiler error in the generated code. But I'd say this is fine because you should never use a partial method declaration without accessibility modifier for a mapper (those are only used for methods that might be completely removed by the compiler if they have no implementation).


Opacity on images

I'm using the minimal dark theme and it applies a dimming effect to all images. (Actually, it might be translucence that looks like dimming due to a dark bg, but nevermind.) I really dislike this, but I was able to fix it by adding the following lines in Minimal/theme.css:
.theme-dark .markdown-preview-view img {
    opacity: 1;
}

The problem is that obsidian seems to pick and choose when this works. Sometimes I come back to a note and the images are dimming again. Sometimes it works at startup, sometimes it doesn't. I don't know what that's all about but if you could add it as a toggle to the settings menu that would be perfect.

That is more complicated than necessary. You can simply target the variable directly with a snippet
body {
--image-muted: 1;
}

Simpler is better, but that snippet doesn't work for me for whatever reason. Seems like it should, but no dice.


feat: allow user to disable database validation safe_mode

set the config option opts.db_safe_mode = false to disable the prompt when the db validation function is going to remove more than (10) entries at once.

I've updated it.
There are now two option keys:
db_safe_mode mentioned above, and auto_validate.
Setting auto_validate to false will mean that frecency never cleans up stale entries.
There's a new command :FrecencyValidate to do this manually.

Looking forward to this.

merged and documented


refactor: convert CustomIcon example to TS

Description
The PR converts the example example/Symbol/CircleLayer/CustomIcon.js to example/Symbol/CircleLayer/CustomIcon.tsx.
The functionality of the example is left unchanged, but I did refactor SymbolLayer to not render the icon from styles but as a separate Images component, which reflects the deprecation of image-in-style with v10.
const styles = {
  icon: {
    iconImage: 'icon',
    iconAllowOverlap: true,
  },
};

....

<SymbolLayer
   id="symbolLocationSymbols"
   style={styles.icon}
/>
<Images images={{ icon: exampleIcon }} />

Question to reviewers
Should I have put the new example to example/V10/CustomIcon.js rather?
My understanding is that all examples need to be converted to v10 step by step as well and that those in the exmaple/V10 folder show v10 specific examples. But I am not sure.
Does updating examples help as contribution at all?
Checklist

[x] I have tested this on a device/simulator for each compatible OS
[ ] I updated the documentation with running yarn generate in the root folder
[x] I added/updated a sample - if a new feature was implemented (/example)

Screenshot OR Video
https://user-images.githubusercontent.com/2580640/225661997-8c3e6b2f-9d09-473b-8d49-d6d1006a6651.mp4

@viddity thanks, it looks good to me. This place is fine. We'll soon drop everything other than v10, so no much need for v10 anymore. Those should be really move to 3d, etc groups.


Add entry for lifetime on every facility at userlevel > 0

my first PR from 30,000 ft!

The only thing missing is that I don't test that it's an integer, which the schema probably expects?

Looks good Paul. We can probably add the integer check after? Or we can use my number only text field for this as well.

Can you point me to the number only text field?

I thought I extended the class but I guess not.
This code should do the trick when building the text field.
		TextField isoWeightFrac = new TextField(){
			@Override public void replaceText(int start, int end, String text) {
				if (!text.matches("[a-z]")){
					super.replaceText(start, end, text);
				}
			}

			public void replaceSelection(String text) {
				if (!text.matches("[a-z]")){
					super.replaceSelection(text);
				}
			}
		};

sorry that bottom bit of code is superfluous. Just need
    TextField isoWeightFrac = new TextField(){
        @Override public void replaceText(int start, int end, String text) {
            if (!text.matches("[a-z]")){
                super.replaceText(start, end, text);
            }
        }
    };

hold on whitespace....

whitespace updated...

Is this ready paul?

one sec... switching to context menus as part of this

ready now

crap!! wrong PR  hold on

Nope.. it's OK.  You already merged #111.  The last few commits are more related to that, so this should be good to go on top of that merge.


0.23.1 Breaks Z-Wave Thermostat State Being Correctly Reflected In Interface

Home Assistant release (hass --version):
0.23.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
Z-Wave Thermostat/HVAC on a Raspberry Pi
Description of problem:
The state of the Operation Mode of my thermostat is not reflected correctly in home-assistant. In fact it appears stuck in the default state and never changes. How it looks
The Operation Mode options are {'Off', 'Cool', 'Heat', 'Auto'}. I am able to set the thermostat to Off, Heat, and Auto... and the physical thermostat will receive these calls successfully, however the interface never updates to show the new state. Additionally I can't set it to Cool because it is forever set to Cool in the interface.
I have a zwave switch which works 100% correctly, and the thermostat previously worked in versions 0.19 through to 0.22, with only the latest update breaking it.
When I first encountered the issue I wiped the device and set up HA on a fresh install of raspian but the issue persists.
I have tailed the OZW_Log.txt and the correct values appear to be sent and received between the zwave devices, however I am a neophyte so could be wrong about that.
Expected:
The current 'Operation Mode' should be correctly represented in the interface.
OZW_Log.txt:
############# Setting from Off to Auto #############
2016-07-07 03:49:14.845 Info, Node004, Value::Set - COMMAND_CLASS_THERMOSTAT_MODE - Mode - 0 - 1 - Auto
2016-07-07 03:49:14.845 Detail, Node004, Queuing (Send) ThermostatModeCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x40, 0x01, 0x03, 0x25, 0x45, 0xc3
2016-07-07 03:49:14.845 Detail, Node004, Queuing (Send) ThermostatModeCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x40, 0x02, 0x25, 0x46, 0xc2
2016-07-07 03:49:14.845 Detail,
2016-07-07 03:49:14.845 Info, Node004, Sending (Send) message (Callback ID=0x45, Expected Reply=0x13) - ThermostatModeCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x40, 0x01, 0x03, 0x25, 0x45, 0xc3
2016-07-07 03:49:14.854 Detail, Node004,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-07 03:49:14.854 Detail, Node004,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-07 03:49:16.161 Detail, Node004,   Received: 0x01, 0x07, 0x00, 0x13, 0x45, 0x00, 0x00, 0x83, 0x2d
2016-07-07 03:49:16.161 Detail, Node004,   ZW_SEND_DATA Request with callback ID 0x45 received (expected 0x45)
2016-07-07 03:49:16.161 Info, Node004, Request RTT 1316 Average Request RTT 878
2016-07-07 03:49:16.161 Detail,   Expected callbackId was received
2016-07-07 03:49:16.161 Detail,   Expected reply was received
2016-07-07 03:49:16.162 Detail,   Message transaction complete
2016-07-07 03:49:16.162 Detail,
2016-07-07 03:49:16.162 Detail, Node004, Removing current message
2016-07-07 03:49:16.162 Detail,
2016-07-07 03:49:16.162 Info, Node004, Sending (Send) message (Callback ID=0x46, Expected Reply=0x04) - ThermostatModeCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x40, 0x02, 0x25, 0x46, 0xc2
2016-07-07 03:49:16.170 Detail, Node004,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-07 03:49:16.170 Detail, Node004,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-07 03:49:16.186 Detail, Node004,   Received: 0x01, 0x07, 0x00, 0x13, 0x46, 0x00, 0x00, 0x02, 0xaf
2016-07-07 03:49:16.186 Detail, Node004,   ZW_SEND_DATA Request with callback ID 0x46 received (expected 0x46)
2016-07-07 03:49:16.186 Info, Node004, Request RTT 24 Average Request RTT 451
2016-07-07 03:49:16.187 Detail,   Expected callbackId was received
2016-07-07 03:49:16.805 Detail, Node004,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x04, 0x03, 0x40, 0x03, 0x03, 0xb5
2016-07-07 03:49:16.806 Detail,
2016-07-07 03:49:16.806 Info, Node004, Response RTT 643 Average Response RTT 612
2016-07-07 03:49:16.806 Detail, Node004, Refreshed Value: old value=0, new value=3, type=list
2016-07-07 03:49:16.806 Detail, Node004, Changes to this value are not verified
2016-07-07 03:49:16.806 Info, Node004, Received thermostat mode: Auto
2016-07-07 03:49:16.806 Detail, Node004,   Expected reply and command class was received
2016-07-07 03:49:16.806 Detail, Node004,   Message transaction complete
2016-07-07 03:49:16.806 Detail,
2016-07-07 03:49:16.806 Detail, Node004, Removing current message
2016-07-07 03:49:16.806 Detail, Node004, Notification: ValueChanged
2016-07-07 03:49:16.872 Detail, Node004,   Received: 0x01, 0x09, 0x00, 0x04, 0x08, 0x04, 0x03, 0x42, 0x03, 0x02, 0xbe
2016-07-07 03:49:16.872 Detail,
2016-07-07 03:49:16.872 Detail, Node004, Refreshed Value: old value=Idle, new value=Cooling, type=string
2016-07-07 03:49:16.872 Detail, Node004, Changes to this value are not verified
2016-07-07 03:49:16.873 Info, Node004, Received thermostat operating state: Cooling
2016-07-07 03:49:16.873 Detail, Node004, Notification: ValueChanged
2016-07-07 03:49:16.885 Detail, Node004,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x04, 0x03, 0x42, 0x03, 0x02, 0xb6
2016-07-07 03:49:16.885 Detail,
2016-07-07 03:49:16.885 Detail, Node004, Refreshed Value: old value=Cooling, new value=Cooling, type=string
2016-07-07 03:49:16.885 Detail, Node004, Changes to this value are not verified
2016-07-07 03:49:16.885 Info, Node004, Received thermostat operating state: Cooling
2016-07-07 03:49:16.885 Detail, Node004, Notification: ValueChanged
2016-07-07 03:49:16.939 Detail, Node004,   Received: 0x01, 0x09, 0x00, 0x04, 0x08, 0x04, 0x03, 0x45, 0x03, 0x01, 0xba
2016-07-07 03:49:16.939 Detail,
2016-07-07 03:49:16.939 Detail, Node004, Refreshed Value: old value=Idle, new value=Running, type=string
2016-07-07 03:49:16.939 Detail, Node004, Changes to this value are not verified
2016-07-07 03:49:16.939 Info, Node004, Received thermostat fan state: Running
2016-07-07 03:49:16.939 Detail, Node004, Notification: ValueChanged
2016-07-07 03:49:16.951 Detail, Node004,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x04, 0x03, 0x45, 0x03, 0x01, 0xb2
2016-07-07 03:49:16.952 Detail,
2016-07-07 03:49:16.952 Detail, Node004, Refreshed Value: old value=Running, new value=Running, type=string
2016-07-07 03:49:16.952 Detail, Node004, Changes to this value are not verified
2016-07-07 03:49:16.952 Info, Node004, Received thermostat fan state: Running
2016-07-07 03:49:16.952 Detail, Node004, Notification: ValueChanged

############# Setting from Auto to Off #############
2016-07-07 03:51:24.119 Info, Node004, Value::Set - COMMAND_CLASS_THERMOSTAT_MODE - Mode - 0 - 1 - Off
2016-07-07 03:51:24.119 Detail, Node004, Queuing (Send) ThermostatModeCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x40, 0x01, 0x00, 0x25, 0x47, 0xc2
2016-07-07 03:51:24.120 Detail, Node004, Queuing (Send) ThermostatModeCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x40, 0x02, 0x25, 0x48, 0xcc
2016-07-07 03:51:24.120 Detail,
2016-07-07 03:51:24.120 Info, Node004, Sending (Send) message (Callback ID=0x47, Expected Reply=0x13) - ThermostatModeCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x40, 0x01, 0x00, 0x25, 0x47, 0xc2
2016-07-07 03:51:24.129 Detail, Node004,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-07 03:51:24.133 Detail, Node004,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-07 03:51:25.361 Detail, Node004,   Received: 0x01, 0x07, 0x00, 0x13, 0x47, 0x00, 0x00, 0x7c, 0xd0
2016-07-07 03:51:25.361 Detail, Node004,   ZW_SEND_DATA Request with callback ID 0x47 received (expected 0x47)
2016-07-07 03:51:25.361 Info, Node004, Request RTT 1240 Average Request RTT 845
2016-07-07 03:51:25.361 Detail,   Expected callbackId was received
2016-07-07 03:51:25.361 Detail,   Expected reply was received
2016-07-07 03:51:25.362 Detail,   Message transaction complete
2016-07-07 03:51:25.362 Detail,
2016-07-07 03:51:25.362 Detail, Node004, Removing current message
2016-07-07 03:51:25.362 Detail,
2016-07-07 03:51:25.362 Info, Node004, Sending (Send) message (Callback ID=0x48, Expected Reply=0x04) - ThermostatModeCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x40, 0x02, 0x25, 0x48, 0xcc
2016-07-07 03:51:25.371 Detail, Node004,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-07 03:51:25.371 Detail, Node004,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-07 03:51:25.387 Detail, Node004,   Received: 0x01, 0x07, 0x00, 0x13, 0x48, 0x00, 0x00, 0x02, 0xa1
2016-07-07 03:51:25.387 Detail, Node004,   ZW_SEND_DATA Request with callback ID 0x48 received (expected 0x48)
2016-07-07 03:51:25.388 Info, Node004, Request RTT 25 Average Request RTT 435
2016-07-07 03:51:25.388 Detail,   Expected callbackId was received
2016-07-07 03:51:26.000 Detail, Node004,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x04, 0x03, 0x40, 0x03, 0x00, 0xb6
2016-07-07 03:51:26.001 Detail,
2016-07-07 03:51:26.001 Info, Node004, Response RTT 639 Average Response RTT 625
2016-07-07 03:51:26.001 Detail, Node004, Refreshed Value: old value=3, new value=0, type=list
2016-07-07 03:51:26.001 Detail, Node004, Changes to this value are not verified
2016-07-07 03:51:26.001 Info, Node004, Received thermostat mode: Off
2016-07-07 03:51:26.001 Detail, Node004,   Expected reply and command class was received
2016-07-07 03:51:26.001 Detail, Node004,   Message transaction complete
2016-07-07 03:51:26.002 Detail,
2016-07-07 03:51:26.002 Detail, Node004, Removing current message
2016-07-07 03:51:26.002 Detail, Node004, Notification: ValueChanged

I can confirm this bug, it appears to be a frontend issue.

I just tried but couldn't repro it. I run the hvac demo platform using:
hvac:
  platform: demo

Have two windows open, both have the more info dialog open. When I change operation mode in 1 window, I see it reflected in the other window.
@turbokongen any errors in your console?

I get no errors in the console, but got a clue from the logs today:
ERROR:homeassistant.components.recorder:Error during query: (sqlite3.OperationalError) database is locked
ERROR:homeassistant.components.recorder:Error during query: (sqlite3.OperationalError) database is locked [SQL: 'SELECT states.state_id AS states_state_id, states.domain AS states_domain, states.entity_id AS states_entity_id, states.state AS states_state, states.attributes AS states_attributes, states.event_id AS states_event_id, states.last_changed AS states_last_changed, states.last_updated AS states_last_updated, states.created AS states_created \nFROM states JOIN (SELECT max(states.state_id) AS max_state_id \nFROM states \nWHERE states.created >= ? AND states.created < ? AND states.entity_id IN (?) GROUP BY states.entity_id) AS anon_1 ON states.state_id = anon_1.max_state_id'] [parameters: ('2016-07-12 19:38:46.108186', '2016-07-13 06:32:27.732205', 'hvac.hvac')]

That should not impact the rendering of the more info dialog.

I am having a bit of trouble getting the frontend development up and running, so I will report back with proper info on this when I get that up.

I just pushed a complete revamp of the frontend build chain so best to do a fresh checkout and run setup_js_dev again.

I can't get the frontend dev to work.
But I did some investigation, and this is what happens:
When any of the available options as list items are chosen, the selected item appears briefly(ms) and then returns to the old. The service called badge pops up, and the zwave device responds normally.
When checking the state attributes, it has also changed to the new selected. So the selected item is not refreshed into the selected one in the frontend.
Hopes this makes any sense at all :)

Ok. This is not a frontend issue, but value_Id not changing for some reason. I can't see why? The python open zwave issues the value changed, but the value I'd does not change until next command? Could this be related to #2271

Closed via #2585


can't play video anymore

this plugin can't play video from youtube again. can you solved this?

@sarbagyastha


Add function error faced when using inside a for loop

I've noticed that when I use the Add function in a for loop, python crashes and reports an error.
print(texts)

awadb_client = awadb.Client()
awadb_client.Create("testdb1")

for text in texts:
    print([text])
    awadb_client.Add([text])

The code that led me to this error was as above.
Here are the error information:
[1]    82822 trace trap  /opt/homebrew/bin/python3

I use python 3.11.4 and awadb 0.3.9.
Here are parts of the variables' information:
texts is a list of string.
[text] is a list which only contain one string.

Sure! I can only upload .zip file. The following file is what I used to test.
test.py is the test file
test.log is the log information for this test
Archive.zip


Basic Auth user configuration not working

When configuring basic-auth for a user per the readme instructions:
  # Auth & Roles (optional)
  security:
    default-roles: # Roles available for all the user even unlogged user READONLY until locked down
    - topic/read
    - node/read
    - topic/data/read
    - group/read
    - registry/read
    - connect/read
    basic-auth:
      username: admin
        password: 8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
        roles:
        - topic/insert
        - topic/delete
        - topic/config/update
        - node/config/update
        - topic/data/insert
        - topic/data/delete
        - group/delete
        - group/offsets/update
        - registry/update
        - registry/delete
        - registry/version/delete

The application fails to start with the following error:
org.yaml.snakeyaml.scanner.ScannerException: mapping values are not allowed here
 in 'reader', line 48, column 17:
            password: 8c6976e5b5410415bde908bd4dee15 ...

If I update the yaml configuration to NOT indent the password and roles, application will startup successfully but I can not log into the application.
    basic-auth:
      username: admin
      password: 8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
      roles:
      - topic/insert
      - topic/delete
      - topic/config/update
      - node/config/update
      - topic/data/insert
      - topic/data/delete
      - group/delete
      - group/offsets/update
      - registry/update
      - registry/delete
      - registry/version/delete

This is what is outputted to the application log when attempting to login:
2019-05-09 19:04:57,119 INFO  pGroup-1-2 org.kafkahq.log.access     [Date: 2019-05-09T19:04:57.088348Z] [Duration: 28 ms] [Url: POST /login HTTP/1.1] [Status: 303] [Ip: <IP_ADDRESS>][Length: 0] [Port: 8080]
2019-05-09 19:04:57,154 INFO  pGroup-1-3 org.kafkahq.log.access     [Date: 2019-05-09T19:04:57.134093Z] [Duration: 19 ms] [Url: GET /login/failed HTTP/1.1] [Status: 200] [Ip: <IP_ADDRESS>] [Length: 679] [Port: 8080]

your yaml is invalid, here is the good one :
  # Auth & Roles (optional)
  security:
    default-roles: # Roles available for all the user even unlogged user READONLY until locked down
    - topic/read
    - node/read
    - topic/data/read
    - group/read
    - registry/read
    - connect/read
    basic-auth:
      admin:
        password: 8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918
        roles:
        - topic/insert
        - topic/delete
        - topic/config/update
        - node/config/update
        - topic/data/insert
        - topic/data/delete
        - group/delete
        - group/offsets/update
        - registry/update
        - registry/delete
        - registry/version/delete

especially this part :
    basic-auth:
      username: admin
        password: 8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918

username must be replace by the current login and not added after : that is an invalid yaml

Thanks for the quick answer, it is now working as expected.
I wonder if there is someway in the documentation to make if more clear that username: is supposed to be the actual users username?

Maybe :+1:
But it don't find the better way to explicit it :smile:
Any idea is appreciate :bulb:

I think just removing the description text might work

username:

Or, you want the descriptive text, update the label to something like this:

actual-username: login of user

Nice project btw, looking forward to watching it evolve!


Any way to use 32 bit ODBC sources from 64 bit Julia?

I noticed that listdns() only shows my 64 bit DSN, presumably because I'm using 64 bit Julia (on Windows).  Is there any way to manually connect to 32 bit sources?

You need to use 32-bit Julia, which you can get from the julialang.org/downloads page.

Hi @quinnj -- would you mind expanding on this a bit?  Is this entirely impossible or just that it would involve handling types differently, or what?  I'm not planning on attempting this this, just curious.  Thanks -A

Sure. 32 vs. 64-bit is a hardware issue. i.e. different physical computers will be built using 32-bit memory addresses or 64-bit memory addresses. Due to this being a physical issue, individual applications are typically built targeting either 32 or 64 bit architectures. They've done this with the Microsoft Office suite, for example, which have 32-bit version as well as 64-bit versions. On latest windows, it actually ships with both 32 and 64-bit versions of the ODBC driver manager. On 64-bit, you can actually run 32-bit or 64-bit.
In your case, your machine is 64-bit (by the fact that you can list 64-bit DSN), so it's going to use the 64-bit ODBC library by default. In order to use the 32-bit ODBC library, it's easiest to just use a julia version that was compiled for 32-bit. From the downloads page, you'll notice that for windows, it lists both 32-bit and 64-bit versions of julia. You can download and install both simultaneously. Upon starting up 32-bit julia, you can do Pkg.add("ODBC"); using ODBC and the library is going to pick up on the 32-bit version of the ODBC driver manager library.

I'm afraid I didn't ask my question very clearly, so let me provide a bit of backstory:  I use some 32-bit enterprise software that talks to both 32- and 64-bit ODBC sources.  Do you have any idea how it might be doing that? The application is 32-bit, so I was wondering if it spawns a 64-bit helper process just to work with the 64 bit sources, or if there's some other standard way of doing this.  I realize this is outside of the scope of ODBC.jl, but was just curious if you had any idea since you've worked extensively with these.

Yeah, I imagine that's how they're managing. Spawn a separate "helper process" that can work with the 32-bit version. You can imagine having a similar "super Julia" which was a master Julia application that could spawn 32-bit or 64-bit versions of julia depending on the libraries that needed loading.


[docs] Sync params of callbacks between types and JSDoc description

Mainly affecting event params in event handlers. They were most often documented as object even though we do type them in TypeScript with a more concrete type (e.g. React.SyntheticEvent).
We couldn't do this previously because we considered all type applications to be array types.
Array types are now documented as Array<T> not with the shorthand notation T[]. This ensures valid syntax in case we have Array<T | U>.

Could not agree more to use Array<> over T[]


Use packageurl version 0.9.3 and Add nginx importer

Signed-off-by: Shivam Sandbhor<EMAIL_ADDRESS>

Fixes https://github.com/nexB/vulnerablecode/issues/96


feat(PX-4073): order details payment section

The type of this PR is: Feature
This PR resolves PX-4073
Description
Payment method section, margins in the section list will be fixed by @alexj105.
PR Checklist (tick all before merging)

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

Nice work 👏 I only have one small comment about the PR title, we are trialing semantic commit formatting for PR titles, so the title would be feat(PX-4073): order details payment section

⛴⛴⛴


Crash: runtime error: slice bounds out of range

Your environment.

Version: 3dbe475212b0022669e3c2ebf3812d2ec19526b4
Browser:  Chrome Version 87.0.4280.88 (Official Build) (x86_64) & Chrome Version 87.0.4280.101 (Android)

What did you do?
Running normally with two clients connected in one session. Then a crash occurred with this call stack:
Jan 02 09:52:43 nivelumi-dev startup.sh[5798]: panic: runtime error: slice bounds out of range [36502:36500]
Jan 02 09:52:43 nivelumi-dev startup.sh[5798]: goroutine 432 [running]:
Jan 02 09:52:43 nivelumi-dev startup.sh[5798]: github.com/pion/ion-sfu/pkg/buffer.(*Bucket).push(...)

This is a really strange issue I could not understand how it could happen, I will leave it open until we find the reason

This is a really strange issue I could not understand how it could happen, I will leave it open until we find the reason

I agree checked the math. It seems to work out, but I did notice you changed https://github.com/pion/ion-sfu/blob/457db65ce7b4f056f70e9f8a2202bd8a13dbd101/pkg/buffer/bucket.go#L26 maybe that will fix it. I thought that signed integer division should always truncate toward 0, but maybe I'm wrong.
The only other way I thought it could happen is that if two addPacket / push operations from two threads hit the same bucket at similar times, there could be a conflict. I have very little insight into how this code is utilized in the system or if it is possible that a multithreading issue could be the culprit.

I agree checked the math. It seems to work out, but I did notice you changed https://github.com/pion/ion-sfu/blob/457db65ce7b4f056f70e9f8a2202bd8a13dbd101/pkg/buffer/bucket.go#L26 maybe that will fix it. I thought that signed integer division should always truncate toward 0, but maybe I'm wrong.
The only other way I thought it could happen is that if two addPacket / push operations from two threads hit the same bucket at similar times, there could be a conflict. I have very little insight into how this code is utilized in the system or if it is possible that a multithreading issue could be the culprit.

I'm now on 7ae23aead5deebd45ca99d64fcccde4ddee7b297 and have a new crash with a new call stack that is most likely related
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: panic: runtime error: index out of range [1] with length 0
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: goroutine 591 [running]:
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: encoding/binary.bigEndian.PutUint16(...)
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]:         /snap/go/6745/src/encoding/binary/binary.go:106
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: github.com/pion/ion-sfu/pkg/buffer.(*Bucket).push(...)

Jan 06 06:54:42 nivelumi-dev startup.sh[3105]:         /snap/go/6745/src/encoding/binary/binary.go:106
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: github.com/pion/ion-sfu/pkg/buffer.(*Bucket).push(...)
 It seems to work out, but I did notice you changed
https://github.com/pion/ion-sfu/blob/457db65ce7b4f056f70e9f8a2202bd8a13dbd101/pkg/buffer/bucket.go#L26
maybe that will fix it. I thought that signed integer division should always truncate toward 0, but maybe I'm wrong.
The only other way I thought it could happen is that if two addPacket / push operations from two threads hit the same bucket at similar times, there could be a conflict. I have very little insight into how this code is utilized in the system or if it is possible that a multithreading issue could be the culprit.

All the bucket methods are protected by a lock, so only one thread at a time can modify it.

I agree checked the math. It seems to work out, but I did notice you changed
https://github.com/pion/ion-sfu/blob/457db65ce7b4f056f70e9f8a2202bd8a13dbd101/pkg/buffer/bucket.go#L26
maybe that will fix it. I thought that signed integer division should always truncate toward 0, but maybe I'm wrong.
The only other way I thought it could happen is that if two addPacket / push operations from two threads hit the same bucket at similar times, there could be a conflict. I have very little insight into how this code is utilized in the system or if it is possible that a multithreading issue could be the culprit.

All the bucket methods are protected by a lock, so only one thread at a time can modify it.

I'm now on 7ae23ae and have a new crash with a new call stack that is most likely related
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: panic: runtime error: index out of range [1] with length 0
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: goroutine 591 [running]:
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: encoding/binary.bigEndian.PutUint16(...)
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]:         /snap/go/6745/src/encoding/binary/binary.go:106
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: github.com/pion/ion-sfu/pkg/buffer.(*Bucket).push(...)

Jan 06 06:54:42 nivelumi-dev startup.sh[3105]:         /snap/go/6745/src/encoding/binary/binary.go:106
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: github.com/pion/ion-sfu/pkg/buffer.(*Bucket).push(...)

Jan 06 06:54:42 nivelumi-dev startup.sh[3105]:         /snap/go/6745/src/encoding/binary/binary.go:106
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: github.com/pion/ion-sfu/pkg/buffer.(*Bucket).push(...)

I'm now on 7ae23ae and have a new crash with a new call stack that is most likely related
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: panic: runtime error: index out of range [1] with length 0
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: goroutine 591 [running]:
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: encoding/binary.bigEndian.PutUint16(...)
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]:         /snap/go/6745/src/encoding/binary/binary.go:106
Jan 06 06:54:42 nivelumi-dev startup.sh[3105]: github.com/pion/ion-sfu/pkg/buffer.(*Bucket).push(...)

No, since the error is in this line:
binary.BigEndian.PutUint16(b.buf[b.step*maxPktSize:], uint16(len(pkt)))

You can get the len of an empty packet, but the out of range comes from the buffer

No, since the error is in this line:
binary.BigEndian.PutUint16(b.buf[b.step*maxPktSize:], uint16(len(pkt)))

You can get the len of an empty packet, but the out of range comes from the buffer

No, since the error is in this line:
binary.BigEndian.PutUint16(b.buf[b.step*maxPktSize:], uint16(len(pkt)))

You can get the len of an empty packet, but the out of range comes from the buffer

Sorry. I misspoke. I corrected my previous reply.

No, since the error is in this line:
binary.BigEndian.PutUint16(b.buf[b.step*maxPktSize:], uint16(len(pkt)))

You can get the len of an empty packet, but the out of range comes from the buffer

Sorry. I misspoke. I corrected my previous reply.

does you clients are browsers? Im asking because this may be related to SSRC collision

does you clients are browsers? Im asking because this may be related to SSRC collision

Yes the browser notation above still holds.

Yes the browser notation above still holds.

The latest push should fix this issue, I will leave this open for some days

The latest push should fix this issue, I will leave this open for some days

@tmiv have you got this issue agian, I think it's safe to close for now?

@tmiv have you got this issue agian, I think it's safe to close for now?

close，please reopen if you got this issue again

close，please reopen if you got this issue again