Does skywalking want to query the total number of calls of a certain interface in a day?

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

Bug

Which version of SkyWalking, OS, and JRE?

Which company or project?

What happened?
If possible, provide a way to reproduce the error. e.g. demo application, component version.

Requirement or improvement

Please describe your requirements or improvement suggestions.

What do you mean SkyWalking wants? I am confused.

怎么用查询某个接口的一天的调用次数

We don't provide that as default metrics. Search existing questions, this has been asked again and again.


Make ThrottleLogins Configurable

We can change the throtlle "maximum attempts" and "delay time" by edit config/auth.php file.

This PR depends on https://github.com/laravel/laravel/pull/3443

@lukasgeiter Thanks, I'll send new commit.

You need to pass 3 and 60 as second parameters to config(). These values aren't set on any existing L5.1 install.

This needs rebasing.

If user doesn't pull in fresh instance of Laravel, they won't have these settings in /config/auth.php.  I think if user doesn't have this set in config, you should still default to a hard-coded integer.  I would suggest something like 5, not 3 (my reasoning is explained in #9504).

I don't really plan to make this configurable, at least not via a config file.

Fair enough.  I've bugged you too much about this already, but maybe consider PR #9504 @taylorotwell?


Is there a way to select a tab dynamically?

For example I would like to select the 3rd tab instead of the first one in onCreate

Yes , you can do that by writing this code in your Activity
 `bottomBar.setDefaultTab(R.id."YOUR_TAB_ID");`

Hope this helped

@burhanshakir  you can use "performClick()" in the 3rd tab.


[FEATURE] Add shell autocompletion

Description
Add shell completion, it will help with UX of the tool.
Screenshots
No response
Additional information
No response

Hi @surajnarwade . Can you assign this to me?


Not seeing the visual on Call Analytics

When we are testing with some of our own Call recordings, we are not seeing the Call analytics image

as shown for the demo call processed while deploying the solution.
Any suggestions on what could be the issue, or any specific settings to be enabled?
thanks

this issue can be closed. Issue is due to stereo and mono calls..thanks


Add PoshRSJob to listing

This time with the original ReadMe file.

Thanks Boe!
Will tweet about it soon!


[docs] Refactor “Guides” content

The Issue
The “Guides” section occupies a prominent primary navigation spot, but is relatively thin on content. This content isn’t the sort of walkthrough or tutorial-style content I might have expected and could more naturally fit elsewhere.
How This PR Solves The Issue

Moves the lonely Apache redirect note to the FAQ, since it seems like it’s there to answer for a specific problem/issue.
Moves “Controlling CMS Settings Files in DDEV” to the “Usage” page since it’s as fundamental and project-specific thing as managing databases. Includes edits:

Shortens title.
Revises intro for brevity and clarity.
Adds subheading to encapsulate setting control.
Summarizes each bullet point, reordered by severity.
Moves last bullet point into tip.
Removes last section that’s redundant after quickstarts and off-topic for the page.

Moves “PhpStorm Configuration and Integration” to the “Start!” section, which seems more relevant next to shell completion and other initial setup tasks. Includes edits:

Re-titles for brevity.
Adds intro to explain who we’re talking to and why they might care.
Reorders slightly and revise for better flow and navigation.

I also deleted the duplicate “Remote Docker Instances” section from the “Experimental Configurations” page, which I missed in #4495. (I can pull that out of here and into a separate PR if this is unbecoming behavior.)
Manual Testing Instructions
Preview changes locally or inspect the automatic build.
Automated Testing Overview
n/a
Related Issue Link(s)

#4188

Release/Deployment Notes
This will require three redirects I’d be happy to set up:

/users/topics/webserver/ → /users/usage/faq/#why-are-my-apache-http-https-redirects-stuck-in-an-infinite-loop
/users/topics/cms-specific-help/ → /users/usage/cms-settings/
/users/topics/phpstorm/ → /users/install/phpstorm/

Pull away!

Redirects added per deployment notes.


closes #415 Titles are too large in landscape mode

Deploy preview for landscape ready!
Built with commit 7c0fc20845e705494fa2c6cfbf85a0ae181cbbc7
https://deploy-preview-432--landscape.netlify.com


Autocomplete does not work in Sublime 3 build 30xx, Ctags 0.3.2

When I set autocomplete to be true, generating the .tags file, the autocomplete popup but neither Tab or Enter fill the word, it just disappear.

Already passed two years. Someone able to solve it? Autocompletion still does not work.

Anything on the console?

only this: (when I rebuild tags)
Building CTags for P:\4 electronics\soft\Sublime Text projects\STM32F1-test0-GPIO: Please be patient
Finished building P:\4 electronics\soft\Sublime Text projects\STM32F1-test0-GPIO\.tags

Using https://github.com/naoyukik/CTags fork with C:\Program Files\Git\usr\bin added to PATH with https://github.com/naoyukik/CTags/issues/9 patch finally made auto complete work for me!


Can't resolve imports where file name contains multiple dots but no .js in the end

Example output:
Could not resolve import:  [ '/cant/share/folder/structure/useForm.js',
  '../../services/logger.service' ]

Do you have an import path written like this in your code: /cant/share/folder/structure/useForm.js?
If yes, this is probably because of how we use Node's path.resolve(). This could be fixed with a simple condition.
But still, what do you mean by where file name contains multiple dots but no .js in the end, are you speaking about backward dots (../) in your second path? Anyway, can you provide a bit more infos in your issue. Like your files structure, the bugged imports in your code, and more if you have... Thanks you.

@kkogovsek give destiny a try, I just published it with a bunch of changes including a better resolve algorithm.

Closing due to lack of feedback.
@kkogovsek If you're still having problems give me a ping and I'll reopen!


flow-type definitions

Hi!
I was wondering if there are any flow-type definitions for redux-saga out there?
If not, I would then probably start writing them, but I need a helping hand of verifying the output, so we don't publish anything incompatible :-)

Haven't seen any in the wild. There are TypeScript definitions here though, so it shouldn't be too hard to convert. I'm interested as well.

I linked the related flow-typed issue and will hopefully start working on it soon!
The thing is, TypeScript definitions actually look very similar, but they sadly behave differently in very subtle ways, which makes them hard to convert... we will see how far I get :-)

Is this in progress?

Yeah. Progress is tracked in the linked flow-typed issue, but right now I am quite busy with other stuff :-/ ... not sure when I can create a first working PR

Do you have a branch open? I deal w/ redux-saga + flow "errors" daily and would be happy to start adding basic definitions.

Sure, will do this as soon as possible... the thing is that flow cannot deal with these super generic interfaces (like strongly typed call() and such) ... and I only have a very raw scaffold

Any update on this?

Man I am so sorry,... right now I have so many other tasks that I can't work on it properly.
I was also waiting for some syntax enhancements of flow, since they also introduced named exports and other stuff lately.
https://gist.github.com/ryyppy/23db18faba8e5e031b1f81adfc050eb9
This is what I wrote so far, but I already completely lost the track and would also probably pull in the newest progress of redux-saga as well.

Also a good thing about newest flow releases is that they completely reimplemented the union-evaluation, which will be very useful for this lib as well.

@ryyppy
Do you think there is a way to define return type of yield statement in this typical redux-saga code?
/* @flow */

declare var getFoo: () => Promise<string>
declare var call: (fn: () => Promise<any>) => any

function * mySaga(): Generator<*, *, *> {
  // I am expecting a string
  // but yield type can't really be type checked, and are always maybe type
  const foo: ?string = yield call(getFoo)

  // only workaround that works for me for now is to force cast and add all this extra parentheses
  const foo: string = ((yield call(getFoo)): any)
}

Hm, yeah generic Next values are problematic.
To get the full type-safetiness, you have to do some type refinement:
function *mySaga(): Generator<*, *, *> {
  // I am expecting a string
  // but yield type can't really be type checked, since they are dynamic
  // other issue are that return type of yield are maybe type
  const foo = yield call('something');

  // In the corresponding branches, flow
  // will recognize the different types
  // of foo
  switch(typeof foo) {
    case 'string':
      console.log(foo.length);
      break;
    case 'number':
      console.log(foo.toFixed(2));
      break;
    default:
      console.log('meh');
  }

  // Of course, also with if()
  if (typeof foo === 'string') {
    console.log(foo.length);
  }
}

const iter = mySaga();

iter.next('asdf');
iter.next(1);

Here is a sound explanation of samgoldman why this is designed like this: https://github.com/facebook/flow/issues/2080

thks for the explanations @ryyppy

@ryyppy can I help you ?

@tychota : if you are able to get something going, I can definitely do the review and testing for it :-) ... a few posts above is my gist to what I started... right now I build so much vim infrastructure for flow and I barely can find time for that right now

Short update: I feel confident now that I can publish the redux-saga libdefs latest in the end of this week.
Short teaser: https://twitter.com/ryyppy/status/767470833472311297

@ryyppy
I'm trying to use the latest redux-saga defs, and I'm running into a bit of trouble getting takeLatest to typecheck.
Here's an example that I'm trying to figure out:
function* saga0(): Generator<IOEffect, string, string> {
  let foo = yield fork((): Promise<number> => Promise.resolve(1));
  return '';
}

export function* saga() : Generator<IOEffect, *, *> {
  takeLatest('FOO', saga0);
  yield fork(takeLatest, 'FOO', saga0);
}

When takeLatest is called directly, it type checks, but when I declaratively fork takeLatest, I'm getting some lengthy type check errors.
I'm pretty new to both redux-saga and flowtype, so perhaps I'm not using takeLatest correctly. I decided to fork takeLatest for easier testing of the generator.
Any insights? Everything else redux-saga related is type checking and I'm really looking forward to increasing my type coverage. Thanks!

Hmm, this is because the takeLatest requires a Generator type, but gets my own backed simulation of a Generator...
I did this to my definitions and the tests run through:
  declare interface TakeXRet extends Generator<*,*,*> {
    name: string,
  }

Not sure if I should patch this... probably yes :-)

@stratospark Could I ask you to open an issue on flow-typed?

Thanks to the great work by @Alxandr, flow-typed has now updated redux-saga typings. Closing the issue now, if there are any problems with new typings, please report them here by creating a new issue or fix them in flow-typed repository.
If you have any suggestions on what is the best way to incorporate typings directly into redux-saga repository - please let me know. From what I understand the biggest problem is that typings are targeting specified range of flow versions and having them directly in the repository kinda locks them down to that range and might cause problems for people using versions from outside the range.


Interest in switching to box-sizing: border-box?

I would do it like this:
html {
    -webkit-box-sizing: border-box;
    -moz-box-sizing: border-box;
    box-sizing: border-box;
}

*,
*:before,
*:after { /* Inherit box-sizing to make it easier overwrite */
    box-sizing: inherit;
}

But I would need to double-check the borders and padding on everything, of course. Just want to know if it's worth the effort.
Thanks!

Just want to know if it's worth the effort.

Can you tell us why it would be worth the effort? Doubt anyone's dying to change the code just to change the code :)

Sorry. Should've given an explanation! :)
IMO, border-box makes managing element widths and heights a lot simpler by including the element's padding and border size into the width or height calculation.
(without)
.box {
    /* designer must subtract border and padding size to achieve desired height and width. */
    height: 17px;
    width: 17px;
    border: 1px solid black;
    padding: 2px;
}

(with)
.box {
    /* height and width are not dependent on border and padding size. */
    height: 20px;
    width: 20px;
    border: 1px solid black;
    padding: 2px;
}

And when it really comes through:
(without)
.box {
    width: calc(100% - 4em);
    padding: 0 2em;
}

(with)
.box {
    width: 100%;
    padding: 0 2em;
}

Just depends on the preference of the maintainers. ;)

Some more information about this topic and how other frameworks handle it:

https://stackoverflow.com/questions/18854259/why-did-bootstrap-3-switch-to-box-sizing-border-box (also follow the links there)
http://www.cssmojo.com/think-for-yourself/ (first part)
https://css-tricks.com/international-box-sizing-awareness-day/

To summarize: The proposal does not seem to be bad for performance (which might be the case because of the selector) and might even decrease the number of required reflows / layout passes when rendering the website compared to calc(...) (that reduces layout time and energy requirements on mobile devices). It also heavily simplifies the CSS code, because you don't need to carry around numbers twice (e.g. the padding width in padding:...; and width:calc(...); have to match as well as the width of elements and their border size).

We already use this throughout all of Ghost core and Ghost.org - so no explanation of its general benefit is needed. I'm pretty sure @novaugust was asking what the benefit of switching existing code to border-box is, rather than what the benefit of the feature is. Switching everything over is a large, painful task which - at best - leaves everything in... exactly the same state that was in before. Or, at worst: Pretty broken.
For a theme as small as Casper, I don't think it makes sense to do a switchover now. It's more than likely that Casper will need a total rewrite at some point in the future as more features in Ghost are introduced - at which point it would make sense to complete this change.
That said, if anyone feels particularly passionate about tackling this and believes that they can do so without breaking anything: PRs welcome.


Notes about plugin API changes

I will be sending PRs once 0.7.0 lands, but basically there are two things to be aware:

Plugins injecting filters do not need try { } catch() {} blocks anymore.

This complexity is handled inside the transformer closure created by Fly.prototype.filter.

Transformer plugins receive a raw data argument. If you are doing string / text manipulation, you must convert this data to a string. data.toString(), ${data}, etc.

In order to support sourcemaps and open the door to future features, transformer plugins using the Fly.prototype.filter method can now return an object instead of a string:

{ code, map, ext }
// or maybe?
// { data, map, ext }

Inline filters can still return a string / raw data, this has not changed.

:+1: especially for the sourcemap purpose.
Maybe can you add this.filterSync() to encapsulate the code like :
this.filter("ts", (data, options) => {
    return this.defer((data, options, cb) => {
        let d = transpile(data.toString(), options, options.fileName);
        cb(null, d);
    })(data.toString(), options)
}, { ext: ".js" });

So we (plugins creator) can do something like :
this.filterSync("ts", (data, options, cb) => {
    let d = transpile(data.toString(), options, options.fileName);
    cb(null, d);
}, { ext: ".js" });

ps : i am not an expert in finding good names, please find a better name than filterSync ;)
ps2 : yes, i try to create a plugin to compile ts sources :smile:

@manland Thanks! It will be simpler than that.
Now, inside filters just return
const result = transpile(data.toString(), options)
{
  code: result.code,
  map: result.map
  ext: ".js"
}

As for simplifying the async to promise API, we'll stick with proto.defer for the next release, but I am open to suggestions like these in the future! :smile:

Thanks for the tips, looks better in my code !

Thanks for writing a plugin for TS! :grinning:
I'll ping you where 0.7.0 is up and help you update it.


Upgrade to webpack version 2 and change babel preset to babel-preset-env

Hi
Thank you for making great generator for us!
I had upgrade webpack version 2 and babel preset.
Please merge this pull request if you like.
Thank you.

Thanks a lot!
I am happy that you like it!

Thank you merge!


how to expose SSH root path URL when using another SSH server?

Gogs version (or commit ref):
Git version: 0.9.97
Operating system:
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
I am using my own SSH server and I got a little issue where gogs is not exposing the SSH path correctly.
I got this exposed to user :
ssh://gogs@server:222/user/repo.git
but my installation is made on /srv/gogs/
so I would like to expose
ssh://gogs@server:222/srv/gogs/repo/user/repo.git
Is there a simple way to do it?
I already took a look on some older post but didn't found the answer, I also tried to tweak some variable in app.ini but not able to make it either.
I thought that SSH_ROOT_PATH would make the tricks but it is not
Many thanks
Edit : the reason why I want to use another ssh server is mostly because of two factor authentication (yubico)
I also notice a strange behavior when I am not using the included SSH server, if I try to push some data from my local repository I don't see any files pushed but I don't have any error message: all the git push process is working correctly...
Any one who use external SSH server correctly with gogs ?

Hi, if you don't use Gogs's SSH URL for push, you're bypassing Gogs delegation to collect data, that's why you don't get anything (news feeds, etc.), which is incorrect way of using Gogs..


[GSSOC'23] Add discord bot for spotify recommendations

Added code and Readme for a discord bot which allows users to specify a song they like along with a category. The bot can then try to recommend songs to the user.

This is for issue #49 , under GSSOC'23


Fix #376: support dynamic import

support dynamic import

I'd really like this to land. Implemented a few tests here: https://github.com/seasonli/escodegen/pull/1

@seasonli, would be great to get this in. Mind having a look at the tests I opened a PR for in your fork? https://github.com/seasonli/escodegen/pull/1

Since this doesn't seem to be going anywhere, I opened #395 with those tests included.

Fixed by #395.


DOC: Note about collapsing multi-dimensional coordinates

Adds a note on partially collapsing multi-dimensional coordinates to the userguide §9.1, iris.cube.Cube.collapsed and iris.coords.Coord.collapsed.

:+1: in principle. My major hesitation is on the addition to the userguide. Could you take a look at the built userguide, and tell me if you think the addition makes the flow work as well in the context of it being a document designed to be used as a readable narrative? The addition to the reference documentation I am absolutely :+1: on.

As per @pelson's suggestions above, I have:

simplified the addition to the userguide by removing the note directive and almost all of the information,
placed the information removed from the userguide into the note directive in the docstring for iris.cube.Cube.collapsed and added a ref directive for this note, and
added a link to this note to the userguide and the docstring for iris.coords.Coord.collapsed, which I have also simplified in favour of this link.


Url encode and support gitlab anchors

Fixes https://github.com/tcort/markdown-link-check/issues/209 and https://github.com/tcort/markdown-link-check/issues/210

@tcort, is any chance to approve it?

You can use the package autoantwort-markdown-link-check as a temporary workaround.

@autoantwort , thanks! I fetched your branch from this PR.
It was important for me to check if this works for titles in Russian. Thanks for the good patch.


If the data is very large, the network request is very slow, can i use this plugin

I'm worried that more and more requests are pending status, will this be a problem?

You can use this lib for sure, and that's also the purpose of this lib :+1:
It doesn't matter what's the data size, because you are still using the same fetch under the hood. What can make a difference is behaviors like "focus revalidate", and you can turn them off if that becomes a problem (check options). But of course it loses some real-time ablity.
The advantage of this lib under a slow network is, it caches and renders the data ASAP. You can check the Fast Navigation demo: https://swr.now.sh/#fast-navigation.


The build of ffmpeg 5.1.2 will hang at linking avcodec

The build of ffmpeg 5.1.2 will hang on triplet x64-windows, specifically, at linking avcodec.
This is an issue from a draft PR, and I don't know what caused the problem. Please help!
Update: I'm considering this an linker bug because the linker throws no error and hangs.
MSVC Ticket
Update:

It probably caused by nasm. Because when I force x64 to use yasm it can be built without problem.
It also build succeed if --disable-asm --disable-x86asm, so it should be related to assembly issue.
It also build succeed if --enable-asm but --disable-x86asm.
It failed if --disable-asm and --enable-x86asm by missing a symbol ff_tx_codelet_list_float_x86, so it should be related to x86 assembly issue.

Seems this PR #28387 block the CI...
See #28430
Failure to remove_all_inside("D:\buildtrees") due to file "\\?\D:\buildtrees\ffmpeg": The process cannot access the file because it is being used by another process.
##[error]vcpkg clean failed
At C:\a\1\s\scripts\azure-pipelines\test-modified-ports.ps1:133 char:5
+     throw "vcpkg clean failed"
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : OperationStopped: (vcpkg clean failed:String) [], RuntimeException
+ FullyQualifiedErrorId : vcpkg clean failed
##[error]PowerShell exited with code '1'.

You are right, because this problem also stucks CI... Sorry for blocking, and I am not going to commit until I find a way to resolve the issue.

It probably caused by nasm. Because when I force x64 to use yasm it can be built without problem.

It also build succeed if --disable-asm --disable-x86asm, so it should be related to assembly issue.

It also build succeed if --enable-asm but --disable-x86asm,
It failed if --disable-asm and --enable-x86asm by missing a x86 symbol ff_tx_codelet_list_float_x86, so it should be related to x86 assembly issue.

It does appear to be an issue the the microsoft linker and something being emitted by nasm. This may not be an issue with yasm as it is rather old and hasnt been updated in a while so it doesnt support newer instructions. So its possible that 1 or more of those newer instructions are causing issues for the linker. Using yasm isnt really a suitable fallback as its looses modern instruction support and has been deprecated by ffmpeg in favor of nasm.
The only main changes I know of between 5.0 and 5.1 were the removal of some old MMX code paths and the addition of avx512icl instructions. Disabling avx512icl though didnt fix the issue. So the only way to know which instructions are suddenly causing issues would be to step through and disable each asm file one by one until it links (something I dont have time to do).
Its also possible that its an issue with the flags that vcpkg is passing into ffmpeg as ffmpeg have msvc CI boxes (see ffmpegs FATE) that dont have this issue. I also have ffmpeg Visual Studio projects using nasm that dont have these issues either so it seems to be a vcpkg specific issue.


Chimara File association

Ezekiel000 opened 2011-04-21
When Chimara is installed (whether by make install, deb install etc) it would be useful if Chimara is associated with supported IF file types. This would allow you to double click on a story file in the file manager to open it in Chimara. It would also allow an IF icon to be associated with IF story files.
Currently supported file types: z1-8, ulx, blb, zlb, glb, blorb, zblorb, gblorb.
Useful links:

IF icons - http://anamnese.online.fr/site2/index.php?page=esclinux
Gnome Blorb Thumbnailer - http://lg.vblank.net/blorb/
OSX Blorb Thumbnailer - https://github.com/bcressey/bruegel/

@wmvanvliet commented 2012-09-15:

The player we supply is just a sample. Chimara will be integrated into the Grotesque player, which will have to deal with file associations.

@wmvanvliet closed 2012-09-15


Module recreates all settings on each terraform plan/apply

terraform-aws-elastic-beanstalk-environment recreates all settings on each terraform plan/apply
    setting.1039973377.name:               "InstancePort" => "InstancePort"
    setting.1039973377.namespace:      "aws:elb:listener:22" => "aws:elb:listener:22"
    setting.1039973377.resource:           "" => ""
    setting.1039973377.value:                "22" => "22"
    setting.1119692372.name:               "" => "ListenerEnabled"
    setting.1119692372.namespace:      "" => "aws:elbv2:listener:443"
    setting.1119692372.resource:           "" => ""
    setting.1119692372.value:                "" => "false"
    setting.1136119684.name:               "RootVolumeSize" => "RootVolumeSize"
    setting.1136119684.namespace:     "aws:autoscaling:launchconfiguration" => "aws:autoscaling:launchconfiguration"
    setting.1136119684.resource:           "" => ""
    setting.1136119684.value:              "8" => "8"
    setting.1201312680.name:             "ListenerEnabled" => "ListenerEnabled"
    setting.1201312680.namespace:   "aws:elb:listener:443" => "aws:elb:listener:443"
    setting.1201312680.resource:         "" => ""
    setting.1201312680.value:             "false" => "false"

This feature/bug was present for years and is still not fixed:
https://github.com/hashicorp/terraform/issues/6729
https://github.com/terraform-providers/terraform-provider-aws/pull/901
https://github.com/hashicorp/terraform/issues/6257
https://github.com/terraform-providers/terraform-provider-aws/issues/280
https://github.com/hashicorp/terraform/issues/11056
https://github.com/terraform-providers/terraform-provider-aws/issues/461
(tested some ideas from the links above, nothing worked 100%)
The only possible solution is to add this:
lifecycle {
    ignore_changes = ["setting"]
}

but it’s a hack since it will not update the env if you update any of the settings.
Regarding terraform-aws-elastic-beanstalk-environment recreating the settings all the time, here what’s probably happening:

Terraform sends all settings to AWS, but some of them are not relevant to the environment you are deploying
Elastic Beanstalk accepts all settings, applies the relevant ones, and throws away the rest
Next time Terraform asks about the settings, Elastic Beanstalk returns a subset of the values and probably in different order
Terraform can’t decide/calculate if the settings are the same - they sure look different (and would require an advanced algorithm to determine if they are the same)
Terraform assigns new ID to the entire array of settings and tries to recreate all of them
Elastic Beanstalk accepts the settings, applies the relevant ones, and throws away the rest - the cycle repeats

What’s a possible solution?
Introduce var.settings (list of maps) to be able to provide all the required settings from outside of the module.
It might work, but in practice would be very difficult to know all the needed settings and tedious to implement.

Excellent write up

As a minimum would be possible to at least not print the key/value pairs which are unchanged? It would significantly reduce the amount of noise and make it easier to understand if there is anything really different in the "settings".
In my attempts to do terraform apply with unchanged EB settings the vast majority of them are printed to the console with exact same before => after values.
So for example I get outputs like this:
...
      setting.1610162273.name:      "BatchSizeType" => "BatchSizeType"
      setting.1610162273.namespace: "aws:elasticbeanstalk:command" => "aws:elasticbeanstalk:command"
      setting.1610162273.resource:  "" => ""
      setting.1610162273.value:     "Fixed" => "Fixed"
      setting.1683651254.name:      "Application Healthcheck URL" => "Application Healthcheck URL"
      setting.1683651254.namespace: "aws:elasticbeanstalk:application" => "aws:elasticbeanstalk:application"
      setting.1683651254.resource:  "" => ""
      setting.1683651254.value:     "/healthcheck" => "/healthcheck"
      setting.2175068570.name:      "BatchSize" => "BatchSize"
      setting.2175068570.namespace: "aws:elasticbeanstalk:command" => "aws:elasticbeanstalk:command"
      setting.2175068570.resource:  "" => ""
      setting.2175068570.value:     "1" => "1"

...

Is there a reason Terraform prints these unchanged settings?

Please see our other issue on this for more context: https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/issues/43

No, the plan output is determined by terraform and cannot be silenced.  We have no control over it. Needs to be fixed in the provider.

So I guess what I am asking for would be a Terraform feature, right? (I am completely new to Terraform , just started using yesterday).

@tigrannajaryan
yes, looks like the issue is in the TF AWS provider https://github.com/terraform-providers/terraform-provider-aws

Some of the settings used here do not apply to every Beanstalk setup. E.g. when using an ALB (and not the classic ones) all aws:elb:*-settings will be reapplied every time. Those settings are not valid for an ALB or NLB (which have both aws:elbv2:*-settings only).
Besides that, Beanstalk/AWS sometimes accepts slightly different values when it comes to whitespaces. In this module, this setting will cause a reset of all settings, because of "wrong" whitespacing:
setting { # setting change every time on apply
    namespace = "aws:autoscaling:launchconfiguration"
    name      = "SSHSourceRestriction"
    value     = "tcp, 22, 22, ${var.ssh_source_restriction}" // <= whitespaces
  }

This will fix it (in this case):
  setting { # setting change every time on apply
    namespace = "aws:autoscaling:launchconfiguration"
    name      = "SSHSourceRestriction"
    value     = "tcp,22,22,${var.ssh_source_restriction}" // <= no whitespaces
  }

What I just did, was to remove every setting which is not applicable for a classic loadbalancer and checking every setting on whitespace-"errors". Voila: no changes anymore.

Oh, another thing... seems a bug to me in terraform:
settings with lists may be sent unsorted to the AWS API:
  setting {
    namespace = "aws:ec2:vpc"
    name      = "Subnets"
    value     = "${join(",", var.private_subnets)}" // order of values might change
  }

Just sort the input:
  setting {
    namespace = "aws:ec2:vpc"
    name      = "Subnets"
    value     = "${join(",", sort(var.private_subnets))}" // every time the same
  }

For the module, it would make sense to apply the settings as a map from the outside.
With this, we could eliminate those settings which are not applicable for the setup (e.g. passing aws:elb:* settings for a v2-load balancer). Maybe with some locals and an if/else-approach?
As soon as I have time, I try this out and create a PR for this.

@DrFunk-n-stein  thanks!
nice findings.
yes, unsorted settings, whitespaces in values, settings not relevant to the environment you are creating, etc. - all case EB to recreate all settings.
As mentioned above and as you pointed out, providing a map of settings from outside would solve that issue.
Not sure how easy the module would be to use (users would have to know and find out all settings they need).
Please open a PR, we'll review it promptly.
And thanks for the help!

narf. We have to wait for 0.12.:
https://github.com/hashicorp/terraform/issues/7034

I was making my mind about this, maybe we can do a workaround and create several resources of an environment equipped with count. Those could be dependant on the type of load balancer - this way we could handle separate configurations. Downside: it's bloats up the module and there might be a fix for the list-of-maps-issue in 0.12

This is something that I have been meaning to try for a while, which won't solve the problem at all but might at the least make it easier to read
https://github.com/coinbase/terraform-landscape

it looks like some of these problems can be solved by using an app template.  https://www.terraform.io/docs/providers/aws/r/elastic_beanstalk_configuration_template.html. worked for me.

@adjavaherian - thanks a bunch for your tip about the configuration template! It did the trick for me as well.

it looks like some of these problems can be solved by using an app template. https://www.terraform.io/docs/providers/aws/r/elastic_beanstalk_configuration_template.html. worked for me.

The next time I update the setting in aws_elastic_beanstalk_configuration_template, and run terraform plan, I see a lot of settings again:
      setting.399529023.name:       "MinSize" => "MinSize"
      setting.399529023.namespace:  "aws:autoscaling:asg" => "aws:autoscaling:asg"
      setting.399529023.resource:   "" => ""
      setting.399529023.value:      "2" => "2"
      setting.4044472833.name:      "Xms" => "Xms"
      setting.4044472833.namespace: "aws:elasticbeanstalk:container:tomcat:jvmoptions" => "aws:elasticbeanstalk:container:tomcat:jvmoptions"
      setting.4044472833.resource:  "" => ""
      setting.4044472833.value:     "1024m" => "1024m"
      setting.4107956248.name:      "Application Healthcheck URL" => "Application Healthcheck URL"
      setting.4107956248.namespace: "aws:elasticbeanstalk:application" => "aws:elasticbeanstalk:application"
      setting.4107956248.resource:  "" => ""
      setting.4107956248.value:     "/" => "/"

this is a known bug and we are kind of stuck on this. planning to write custom comparison

I was playing with a custom diff in the resource, but I could not detect an abnormal comparison of settings using the test TestAccAWSBeanstalkEnv_settings_update. I am really unsure that the problem is really... The function diff.HasChange("setting") returns false when applying the same configuration which makes no sense considering it does return a diff. I am missing something.

@aknysh You had mentioned at the beginning that we could hackishly override the changes:

The only possible solution is to add this:
lifecycle {
ignore_changes = ["setting"]
}
but it’s a hack since it will not update the env if you update any of the settings.

I am interested in adding that option but I get an error "The block type name "lifecycle" is reserved for use by Terraform in a future version."
Did you get that working, and if so, where did you make the code change?

Would be nice to have a fix/workaround here as seeing the changes is quite annoying. Seems that you can't configure lifecycle in terraform 0.12.x as @boomshadow also described.

This is still not fixed completely.  I've added a comment on the merged fix that still has potential for the problem, https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/commit/b809467c9492ea4fe05399b2e4af2c8d383e45b7#r39525082

This is still not fixed completely.  I've added a comment on the merged fix that still has potential for the problem.
https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/commit/b809467c9492ea4fe05399b2e4af2c8d383e45b7#r39525364

@helvalius @maximmi - This is still happening on v0.22

Yea the fix from @informeto  helps and there is a new issue with the parallel merge of the SpotOn support, for me those variables are still having the issue. I'll see to update that in my pull request or someone else could do a fix for those.

I just wanted to link to this issue: https://github.com/terraform-providers/terraform-provider-aws/issues/1471
...as it seems to be where there is some relatively recent discussion regarding the Terraform provider. There is also a workaround that is quite effective: Just add resource = "" to each setting.

For me, switching to AWS provider v3 solved the problem of reapplication of settings. I was earlier on 2.70.0 and once I switched to 3.22.0, this issue was gone.

Still experience this with terraform 0.14.10 and the aws provider 3.22.0 and the resource = "" in the setting.
  # module.eb-name.aws_elastic_beanstalk_environment.default will be updated in-place
  ~ resource "aws_elastic_beanstalk_environment" "default" {
        id                     = "e-xxxxxxxxxx"
        name                   = "eb-name"
        tags                   = {}
        # (15 unchanged attributes hidden)

      + setting {
          + name      = "ConfigDocument"
          + namespace = "aws:elasticbeanstalk:healthreporting:system"
          + value     = jsonencode(
                {
                  + Rules   = {
                      + Environment = {
                          + Application = {
                              + ApplicationRequests4xx = {
                                  + Enabled = false
                                }
                            }
                          + ELB         = {
                              + ELBRequests4xx = {
                                  + Enabled = true
                                }
                            }
                        }
                    }
                  + Version = 1
                }
            )
        }
      - setting {
          - name      = "ConfigDocument" -> null
          - namespace = "aws:elasticbeanstalk:healthreporting:system" -> null
          - value     = jsonencode(
                {
                  - Rules   = {
                      - Environment = {
                          - Application = {
                              - ApplicationRequests4xx = {
                                  - Enabled = false
                                }
                            }
                          - ELB         = {
                              - ELBRequests4xx = {
                                  - Enabled = true
                                }
                            }
                        }
                    }
                  - Version = 1
                }
            ) -> null
        }

Using aws provider with version 3.22 and terraform 0.14.7 and still having the issue using a Classic load balancer only:
  # module.elastic_beanstalk_environment.aws_elastic_beanstalk_environment.default will be updated in-place
  ~ resource "aws_elastic_beanstalk_environment" "default" {
        id                     = "e-vzua8aifyy"
        name                   = "envir"
        tags                   = {
            "Environment" = "envir"
        }
        # (16 unchanged attributes hidden)

      + setting {
          + name      = "HealthCheckPath"
          + namespace = "aws:elasticbeanstalk:environment:process:default"
          + value     = "/"
        }
      + setting {
          + name      = "InstancePort"
          + namespace = "aws:elb:listener"
          + value     = "80"
        }
      + setting {
          + name      = "ListenerEnabled"
          + namespace = "aws:elb:listener"
          + value     = "true"
        }
      + setting {
          + name      = "ListenerProtocol"
          + namespace = "aws:elb:listener"
          + value     = "HTTP"
        }
      + setting {
          + name      = "Port"
          + namespace = "aws:elasticbeanstalk:environment:process:default"
          + value     = "80"
        }
      + setting {
          + name      = "Protocol"
          + namespace = "aws:elasticbeanstalk:environment:process:default"
          + value     = "HTTP"
        }
        # (62 unchanged blocks hidden)
    }
        ```

My configs are default for these params.

Is this issue still not resolved? it's been two years since last and I have the same problem like @florian0410. I'm using classic loadbalancer. My Terraform version is 1.1.9 with aws v4.58.0 provider. Module version v0.49.0

I'm still getting this issue
Interestingly I dont get it here, but I do have the issue here
but I dont really understand the differentce
terraform version 1.7.2, aws version ~> 5.0


Prettier doesn't format MDX files properly

@vplasencia
Is this still a valid issue?
I can't reproduce it.
I tried:

Turn an mdx file into a file with invalid format. e.g add a ; somewhere in docs/src/components/Articles.tsx
yarn prettier:write
file was formatted as expected

Hey @sripwoud! I think it's still an issue. The easiest way to reproduce it is to comment this line: https://github.com/semaphore-protocol/semaphore/blob/main/.prettierignore#L33, then run: yarn prettier:write, then go inside apps/docs and run yarn start. You should see some errors. Let me know if you don't see any errors.

Ups yeah my bad, I had tweaked an tsx file :man_facepalming:


Scenario Selector - Scenario without names not appearing and not usable

Isssue
Scenarios without names do not appear in the Scenario Selector.

How to replicate
Run the code
from taipy.config import Config, Frequency
import taipy as tp

import datetime as dt

def f(i):
    return i

d1_cfg = Config.configure_data_node('d1', default_data=1)
d2_cfg = Config.configure_data_node('d2')
task_cfg = Config.configure_task(id="task", function=f, input=d1_cfg, output=d2_cfg)
s = Config.configure_scenario_from_tasks('s', [task_cfg], frequency=Frequency.DAILY)

scenario = None

if __name__ == "__main__":
    tp.Core().run()

    [tp.create_scenario(s,
                        creation_date=dt.datetime.now()+dt.timedelta(days=i))
                        for i in range(10)]

    tp.Gui('<|{scenario}|scenario_selector|>').run(port=4999)

Expected behavior
The Scenario Selector should display the scenarios created and be usable.
Version
Taipy 2.3.0 Draft

What we display is a label. If a scenario does not have any name, the id is used as a label.
So I believe the name does exist in the use case described here, but it is empty.

This is not really what is happening or at least, there is more to it. For example, I should have ten scenarios here:


DNS Label example

@jmorcar commented on Tue Mar 17 2020
If were possible, I need an example with dns label on a internal loadbalancer. I see this example:
annotations:
service.beta.kubernetes.io/azure-dns-label-name: myserviceuniquelabel
But, the example I think is for public loadbalancer , while I need internal dns label .local service like:
<miDNSLabel>svc.cluster.local or <miDnsLabel>.<namespace>.svc.cluster.local

Detalles del documento
⚠ No edite esta sección. Se requiere para docs.microsoft.com ➟ Vinculación de problema de GitHub.

ID: 25afcc19-0998-3583-f6d8-e2a619c0e071
Version Independent ID: 7629191a-6b3b-fb22-8b70-fa84fd785f38
Content: Creación de un equilibrador de carga interno de Azure Kubernetes Service (AKS)
Content Source: articles/aks/internal-lb.md

@srvbpigh commented on Tue Mar 17 2020
Hello, @jmorcar
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards,
Microsoft DOCS International Team

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

adding the en-us version of the referenced doc: https://docs.microsoft.com/en-us/azure/aks/internal-lb

In other documentation I've seen a DNS label internal in Azure with this domain: core.windows.net.... How many internal domains there is available in Azure? How AKS could resolve these DNS zones. Is very important to assign DNS names to internal services in AKS and these can be resolved for external resources in Azure (VMs, External LoadBalancer etc..)

Thank you @CeciAc for the feedback!
We've added an item to our backlog and will prioritize accordingly.
#please-close


Deal with net-ftp being unavailable

In Ruby 3.0 net-ftp changed from a bundled gem to a default gem. This means it may not be available, such as when running unit tests.
Since ftp is becoming less and less common, this changes net-ftp to be an optional dependency. Users who do need ftp support should ensure the gem is installed.

@ekohl Thank you 👍

The require 'net/ftp' gem should really be moved into the source_to_file method to properly handle this. Some context, if you're not using puppet generate types, then puppetserver will load types and providers and call the type's title_patterns method. Agent-side code like require 'net/ftp' needs to be guarded so it's only invoked on the agent, and not during compilation.

Thanks @joshcooper .. I'll raise this with the team.


HTTP metrics do not adhere to Prometheus best practice

I wanted to make a PR to fix this, but it looks a little non-trivial and I was wondering to hear author's take on this.
I think that two metrics this library should expose would be http_request_duration_miliseconds and http_requests_total, with an option to disable path label.
@jucrouzet @ddalmais what do you think?

Hi @errordeveloper,
The bundle exposes restify_path_duration as an Histogram, you can excluse some paths with the exclude option (path or regex).
Is it what you're looking at ?

No, that wasn't exactly what I meant... but I ended-up patching epimetheus.
On Tue, 20 Jun 2017, 13:34 Julien CROUZET<EMAIL_ADDRESS>wrote:

Hi @errordeveloper https://github.com/errordeveloper,
The bundle exposes restify_path_duration as an Histogram
https://prometheus.io/docs/practices/histograms/, you can excluse some
paths with the exclude option (path or regex).
Is it what you're looking at ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/etf1/restify-prom-bundle/issues/2#issuecomment-309739157,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPWS3jI1Y8ndQus4cPqDPfc5Mt-WPQOks5sF7xngaJpZM4N6_eY
.


FPv2 improvements

[x] Consider extra ecus for present ecu brand matching - https://github.com/commaai/openpilot/pull/27688
For CAN FD for example, only the two ECUs in the DB are being matched against the hyundai brand, when we could match more (like cornerRadar, adas, etc)
[ ] Put FW versions inside the config for lots of nice helpers in one place - https://github.com/commaai/openpilot/pull/27691
[ ] Consider bus when matching brands - https://github.com/commaai/openpilot/pull/27657
[ ] Sort requests by OBD multiplexing mode, so brands with auto-generated auxiliary requests don't switch unnecessarily because of bad sorting
[ ] Group first subaddress query into parallel query group (reduces total queries by 1)
[x] Only update OBD multiplexing mode when on bus % 1 == 1 - https://github.com/commaai/openpilot/pull/27669
[ ] Test that measures the time to query FW versions in the worse case. For each brand and overall. Fail when there is a large number of queries or OBD multiplexing mode switches (soon to be optimized)
[ ] Batch tester present for finding present ecus (if required). We now send tester present to 79 addresses at once
[x] ~Filter out addresses that are already on the bus before we start to query, they are likely broadcast addrs and we shouldn't extend our timeouts for them~
[x] Break out of IsoTpParallelQuery loop once either all addresses are timed out or done. Right now, We break if all addrs are timed out or done. For example, we wouldn't break if addr A is timed out and not done, and addr B is done and not timed out - https://github.com/commaai/openpilot/pull/27764
[x] Only extend addr timeout in IsoTpParallelQuery if we got a valid consecutive frame - https://github.com/commaai/openpilot/pull/27762

Can make a project if we don't this cluttering up issues

Currently trying to debug a vehicle and I'm wondering if you could take a look? Here is a drive 539cfef88f5a6208|2023-04-05--13-49-04. It's a Mazda CX50 and I can't get it to completely fingerprint. Apparently, their Comma 3 was not shipped with a comma power, however, bus 1 should be connected to the OBD port at the BCM (see this wiring diagram below).

CAN BUS 0/2 is used for communication between the following modules:
― BCM
― EPS control module
― Adaptive front lighting system (AFS) control module/auto leveling control module
― SAS control module  'address': N/A
― DSC HU/CM
― TCM
― PCM
'carFw': [{'address': 1840,
'brand': 'ford',
'bus': 0,
'ecu': 'eps',
'fwVersion': b'VA40-3216Y-B\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
'logging': False,
'obdMultiplexing': False,
'request': [b'>\x00', b'"\xf1\x88'],
'responseAddress': 1848,
'subAddress': 0},
{'address': 1798,
'brand': 'ford',
'bus': 0,
'ecu': 'fwdCamera',
'fwVersion': b'VA40-67WK2-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
'logging': False,
'obdMultiplexing': False,
'request': [b'>\x00', b'"\xf1\x88'],
'responseAddress': 1806,
'subAddress': 0},
{'address': 1892,
'brand': 'ford',
'bus': 0,
'ecu': 'fwdRadar',
'fwVersion': b'VA45-67XK2-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
'logging': False,
'obdMultiplexing': False,
'request': [b'>\x00', b'"\xf1\x88'],
'responseAddress': 1900,
'subAddress': 0},
{'address': 1888,
'brand': 'ford',
'bus': 0,
'ecu': 'abs',
'fwVersion': b'VA40-4300F-D\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
'logging': False,
'obdMultiplexing': False,
'request': [b'>\x00', b'"\xf1\x88'],
'responseAddress': 1896,
'subAddress': 0}],

@MoreTore The carFw you posted shows responses for brand: 'ford', so it won't fingerprint as a Mazda since there are no responses for Mazda FW queries. You should try adding those queries to Mazda's FP config.

1888

Thank you. I didn't understand what was going on there. I will try that.

@incognitojam
Thanks alot that solved it!
(0x730, None): [
b'VA40-3216Y-B\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
]
(0x706, None): [
b'VA40-67WK2-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
]
(0x764, None): [
b'VA45-67XK2-\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
]
(0x760, None): [
b'VA40-4300F-D\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
]
Number of dongle ids checked: 1
Fingerprinted:                0
Not fingerprinted:            1
of which had a fuzzy match: 0
Correct fuzzy matches:        0
Wrong fuzzy matches:          0

When ECUs don't respond and you expect them to, you can check errorLogMessage in useradmin and see what error is being printing for that ECU. If the rx address (usually + 8) exists in ecu responses, you usually just need a different data id for that car and ECU.

When ECUs don't respond and you expect them to, you can check errorLogMessage in useradmin and see what error is being printed for that ECU. If the rx address (usually + 8) exists in ecu responses, you usually just need a different data id for that car and ECU.

Well yes I see errors but I have very little understanding of the whole of what to do.
{'errorLogMessage': '{"msg": "vin query retry (1) ...", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", "version": "0.9.2", "dirty": '
                    'true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": "car_helpers.py", "lineno": 101, '
                    '"pathname": "/data/openpilot/selfdrive/car/car_helpers.py", "module": "car_helpers", "funcName": "fingerprint", "host": "tici", '
                    '"process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created":<PHONE_NUMBER>.1326694}',
 'logMonoTime':<PHONE_NUMBER>5,
 'valid': True}

....

{'errorLogMessage': '{"msg": "Error processing UDS response: (1882, None)", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "exc_info": "Traceback (most recent call last):\\n  File '
                    '\\"/data/openpilot/selfdrive/car/isotp_parallel_query.py\\", line 108, in get_data\\n    dat, updated = msg.recv()\\n  File '
                    '\\"/data/openpilot/panda/python/uds.py\\", line 445, in recv\\n    self._isotp_rx_next(msg)\\n  File '
                    '\\"/data/openpilot/panda/python/uds.py\\", line 502, in _isotp_rx_next\\n    assert not self.tx_done, \\"isotp - rx: flow '
                    'control with no active frame\\"\\nAssertionError: isotp - rx: flow control with no active frame", "level": "ERROR", "levelnum": '
                    '40, "name": "swaglog", "filename": "isotp_parallel_query.py", "lineno": 110, "pathname": '
                    '"/data/openpilot/selfdrive/car/isotp_parallel_query.py", "module": "isotp_parallel_query", "funcName": "get_data", "host": '
                    '"tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created":<PHONE_NUMBER>.9520495}',
 'logMonoTime':<PHONE_NUMBER>8,
 'valid': True}
{'errorLogMessage': '{"msg": "Error processing UDS response: (1882, None)", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "exc_info": "Traceback (most recent call last):\\n  File '
                    '\\"/data/openpilot/selfdrive/car/isotp_parallel_query.py\\", line 108, in get_data\\n    dat, updated = msg.recv()\\n  File '
                    '\\"/data/openpilot/panda/python/uds.py\\", line 445, in recv\\n    self._isotp_rx_next(msg)\\n  File '
                    '\\"/data/openpilot/panda/python/uds.py\\", line 502, in _isotp_rx_next\\n    assert not self.tx_done, \\"isotp - rx: flow '
                    'control with no active frame\\"\\nAssertionError: isotp - rx: flow control with no active frame", "level": "ERROR", "levelnum": '
                    '40, "name": "swaglog", "filename": "isotp_parallel_query.py", "lineno": 110, "pathname": '
                    '"/data/openpilot/selfdrive/car/isotp_parallel_query.py", "module": "isotp_parallel_query", "funcName": "get_data", "host": '
                    '"tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created":<PHONE_NUMBER>.0009077}',
 'logMonoTime':<PHONE_NUMBER>7,
 'valid': True}
{'errorLogMessage': '{"msg": "iso-tp query bad response: (2016, None) - 0x7f2231", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": '
                    '"fw_versions.py", "lineno": 294, "pathname": "/data/openpilot/selfdrive/car/fw_versions.py", "module": "fw_versions", '
                    '"funcName": "get_fw_versions", "host": "tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created": '
                    '1680716947.0209897}',
 'logMonoTime':<PHONE_NUMBER>5,
 'valid': True}
{'errorLogMessage': '{"msg": "iso-tp query bad response: (2017, None) - 0x7f2231", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": '
                    '"fw_versions.py", "lineno": 294, "pathname": "/data/openpilot/selfdrive/car/fw_versions.py", "module": "fw_versions", '
                    '"funcName": "get_fw_versions", "host": "tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created": '
                    '1680716947.0216691}',
 'logMonoTime':<PHONE_NUMBER>6,
 'valid': True}
{'errorLogMessage': '{"msg": "iso-tp query bad response: (2016, None) - 0x7f2231", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": '
                    '"fw_versions.py", "lineno": 294, "pathname": "/data/openpilot/selfdrive/car/fw_versions.py", "module": "fw_versions", '
                    '"funcName": "get_fw_versions", "host": "tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created": '
                    '1680716947.1305494}',
 'logMonoTime':<PHONE_NUMBER>7,
 'valid': True}
{'errorLogMessage': '{"msg": "iso-tp query bad response: (2017, None) - 0x7f2231", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": '
                    '"fw_versions.py", "lineno": 294, "pathname": "/data/openpilot/selfdrive/car/fw_versions.py", "module": "fw_versions", '
                    '"funcName": "get_fw_versions", "host": "tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created": '
                    '1680716947.131053}',
 'logMonoTime':<PHONE_NUMBER>6,
 'valid': True}
{'errorLogMessage': '{"msg": "iso-tp query bad response: (1840, None) - 0x7f2231", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": '
                    '"fw_versions.py", "lineno": 294, "pathname": "/data/openpilot/selfdrive/car/fw_versions.py", "module": "fw_versions", '
                    '"funcName": "get_fw_versions", "host": "tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created": '
                    '1680716948.0305827}',
 'logMonoTime':<PHONE_NUMBER>6,
 'valid': True}
{'errorLogMessage': '{"msg": "iso-tp query bad response: (2016, None) - 0x7f3e13", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": '
                    '"fw_versions.py", "lineno": 294, "pathname": "/data/openpilot/selfdrive/car/fw_versions.py", "module": "fw_versions", '
                    '"funcName": "get_fw_versions", "host": "tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created": '
                    '1680716948.2595744}',
 'logMonoTime':<PHONE_NUMBER>3,
 'valid': True}
{'errorLogMessage': '{"msg": "iso-tp query bad response: (2016, None) - 0x7f2231", "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", '
                    '"version": "0.9.2", "dirty": true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": '
                    '"fw_versions.py", "lineno": 294, "pathname": "/data/openpilot/selfdrive/car/fw_versions.py", "module": "fw_versions", '
                    '"funcName": "get_fw_versions", "host": "tici", "process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created": '
                    '1680716948.4003496}',
 'logMonoTime':<PHONE_NUMBER>4,
 'valid': True}
{'errorLogMessage': '{"msg": {"event": "fingerprinted", "car_fingerprint": null, "source": 0, "fuzzy": false, "cached": false, "fw_count": 4, '
                    '"ecu_responses": [[2025, null, 0], [2024, null, 0], [1896, null, 0], [1900, null, 0], [1806, null, 0], [1848, null, 0]], '
                    '"vin_rx_addr": 0, "error": true}, "ctx": {"daemon": "controlsd", "dongle_id": "539cfef88f5a6208", "version": "0.9.2", "dirty": '
                    'true, "device": "tici"}, "level": "ERROR", "levelnum": 40, "name": "swaglog", "filename": "car_helpers.py", "lineno": 174, '
                    '"pathname": "/data/openpilot/selfdrive/car/car_helpers.py", "module": "car_helpers", "funcName": "fingerprint", "host": "tici", '
                    '"process": 46510, "thread":<PHONE_NUMBER>52, "threadName": "MainThread", "created":<PHONE_NUMBER>.6599796}',
 'logMonoTime':<PHONE_NUMBER>8,
 'valid': True}

@sshane any of this still relevant after all the recent FP work?

The remaining here are more for my reference for future improvements (not needed now).


storage: leave volume uninitialized

So far I've used a dummy initializer when only the pool was supposed to be
initialized. But I want to be able to check whether the volume is initialized
at all and kick out a bunch of get*() methods in the various storage drivers.
This will allow us to reduce the amount of helper functions well call and
increases performance. In essence, all information initialization can then be
done when we call StoragePoolInit() instead of additionally in each single
method.
Signed-off-by: Christian Brauner<EMAIL_ADDRESS>

/me expects segfaults...

jenkins: test this please

Never mind, this won't work nicely due to the fact that on container or image creation we only initialize the pool and then later on initialize the volume in the specific function. So this, while nice, is not straightforward.


Upgrade to Angular 8 and Clarity 2.2

PR to address #272 - Upgrade to Angular 8 and Clarity 2.2

Teamwork :+1:


Launch

Vercel.

[x] Deploy to Vercel
[ ] Set up GitHub action
[x] CNAME
[x] remove existing redirect rule

Maybe Netlify or Dokku instead.

Currently hosted on Netlify: https://app.netlify.com/sites/bespoke-zuccutto-fe9f2a/overview
URL: https://bespoke-zuccutto-fe9f2a.netlify.app/
Redirect set up from http://emp.dave.engineer/

Done. It's now hosted on https://emp.dave.engineer/
No Github action required with Vercel.
https://vercel.com/daves-projects-293308b3/emf-planner


Made test case for using select method with joins and group by

Explain your user case and expected results

https://github.com/go-gorm/gorm/issues/4175

need to read docs more carefully


URL Link Shortener

A beautiful python project which shortens up the website link to be easily carried and used instead of big links
Type of change

[✓] Added new project
[ ] Bug fix
[ ] New features
[ ] Enhanced documentation

Changes proposed in this pull request

Project name :

Short description :

Checklist

[✓] The code is Python 3 compatible
[✓] I have added relevant comments in my file to make code understandable
[✓] I have added my project in a folder which includes all the necessary files

If you are contributing for hacktoberfest ,then please add more features to it.


allow additional metric configuration in ReportDBStatsMetrics

[x] Do only one thing
[x] Non breaking API changes
[x] Tested

What did this pull request do?
Allows providing additional configuration when using ReportDBStatsMetrics directly.
User Case Description
I'm calling it directly with an additional database name attribute:
metrics.ReportDBStatsMetrics(sqlDB, metric.WithAttributes(attribute.String("db", ...)))

LGTM


Bug/595 debounced project code validation is causing trouble

Resolves #595
Any attempt at debouncing a zod refine() ultimately leads to either lying to super-forms or not resolving all validation requests, which made the one way I got it to actually work unintuitive and probably fragile.
The fact that this is async validation means it's server-side, so we don't have to prevent form submissions or anything like that. We're just providing faster feedback.
See 53877d3c18b49eba2e892a7b0f84e7141633ab3f for the super generic approach that I canned lol.
The end result/changeset in 53877d3c18b49eba2e892a7b0f84e7141633ab3f is isolated from the code changes in the more generic approach.
The buggy behaviour is gone:
https://github.com/sillsdev/languageforge-lexbox/assets/12587509/85733158-080d-4ce7-acfb-165abfeab0a8
And the validation still works:
https://github.com/sillsdev/languageforge-lexbox/assets/12587509/abf3c2bc-9518-4d61-aeb9-0955fab0ee7f

@hahn-kev my more complicated version in 53877d3c18b49eba2e892a7b0f84e7141633ab3f did block submitting. I don't think we need to. I think we should see this more as fast feedback than real validation.


ModuleNotFoundError: No module named 'customtkinter'

Hello,
When Installing via 'python setup.py sdist' I get a  ModuleNotFoundError: No module named 'customtkinter'
How can I fix that?

Traceback (most recent call last):   File "/Users/kaivoigt/EV_sim-main/setup.py", line 2, in <module>     from EV_sim.version import __version__   File "/Users/kaivoigt/EV_sim-main/EV_sim/__init__.py", line 15, in <module>     from .tkinter_gui.main import VehicleDynamicsApp   File "/Users/kaivoigt/EV_sim-main/EV_sim/tkinter_gui/main.py", line 9, in <module>     import customtkinter as ctk ModuleNotFoundError: No module named 'customtkinter'

Originally posted by @KaVo194 in https://github.com/m0in92/EV_sim/issues/4#issuecomment-1900673410

Can you please let me know of the python version used for the installation?

Thanks for your kind response. I used Python 3.11.5

No problem!
In step 4, were you able to run the command "pip install -r requirements.txt"? This steps installs the required external python modules used in this project. If you did, can you try running "pip install customtkinter" after running "pip install -r requirements.txt".
Let me know what happens!
Best regards

Hmm. I ran "Here is what happens when I run "pip install -r requirements.txt"
`(base) ➜  EV_sim-main pip install -r requirements.txt
Collecting asgiref==3.7.2 (from -r requirements.txt (line 1))
Downloading asgiref-3.7.2-py3-none-any.whl.metadata (9.2 kB)
Requirement already satisfied: colorama==0.4.6 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from -r requirements.txt (line 2)) (0.4.6)
Requirement already satisfied: contourpy==1.0.5 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from -r requirements.txt (line 3)) (1.0.5)
Collecting customtkinter==5.1.3 (from -r requirements.txt (line 4))
Downloading customtkinter-5.1.3-py3-none-any.whl (295 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 295.2/295.2 kB 6.2 MB/s eta 0:00:00
Collecting cx-Freeze==6.15.1 (from -r requirements.txt (line 5))
Downloading cx_Freeze-6.15.1-cp311-cp311-macosx_11_0_arm64.whl.metadata (6.9 kB)
Collecting cx-Logging==3.1.0 (from -r requirements.txt (line 6))
Downloading cx_Logging-3.1.0.tar.gz (27 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: cycler==0.11.0 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from -r requirements.txt (line 7)) (0.11.0)
Collecting darkdetect==0.8.0 (from -r requirements.txt (line 8))
Downloading darkdetect-0.8.0-py3-none-any.whl (9.0 kB)
Collecting Django==4.2.7 (from -r requirements.txt (line 9))
Downloading Django-4.2.7-py3-none-any.whl.metadata (4.1 kB)
Collecting exceptiongroup==1.2.0 (from -r requirements.txt (line 10))
Downloading exceptiongroup-1.2.0-py3-none-any.whl.metadata (6.6 kB)
Collecting fonttools==4.37.4 (from -r requirements.txt (line 11))
Downloading fonttools-4.37.4-py3-none-any.whl (960 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 960.8/960.8 kB 8.6 MB/s eta 0:00:00
Collecting iniconfig==2.0.0 (from -r requirements.txt (line 12))
Downloading iniconfig-2.0.0-py3-none-any.whl (5.9 kB)
Requirement already satisfied: kiwisolver==1.4.4 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from -r requirements.txt (line 13)) (1.4.4)
Collecting lief==0.13.2 (from -r requirements.txt (line 14))
Downloading lief-0.13.2-cp311-cp311-macosx_11_0_arm64.whl.metadata (4.0 kB)
Collecting matplotlib==3.6.1 (from -r requirements.txt (line 15))
Downloading matplotlib-3.6.1-cp311-cp311-macosx_11_0_arm64.whl (7.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.2/7.2 MB 3.6 MB/s eta 0:00:00
Collecting numpy==1.23.4 (from -r requirements.txt (line 16))
Downloading numpy-1.23.4-cp311-cp311-macosx_11_0_arm64.whl (13.3 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 13.3/13.3 MB 9.1 MB/s eta 0:00:00
Collecting packaging==21.3 (from -r requirements.txt (line 17))
Downloading packaging-21.3-py3-none-any.whl (40 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 40.8/40.8 kB 4.2 MB/s eta 0:00:00
Collecting pytz==2022.5 (from -r requirements.txt (line 18))
Downloading pytz-2022.5-py2.py3-none-any.whl (500 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 500.7/500.7 kB 8.4 MB/s eta 0:00:00
Requirement already satisfied: six==1.16.0 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from -r requirements.txt (line 19)) (1.16.0)
Collecting sqlparse==0.4.4 (from -r requirements.txt (line 20))
Downloading sqlparse-0.4.4-py3-none-any.whl (41 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 41.2/41.2 kB 5.0 MB/s eta 0:00:00
Collecting tomli==2.0.1 (from -r requirements.txt (line 21))
Downloading tomli-2.0.1-py3-none-any.whl (12 kB)
Collecting typing_extensions==4.8.0 (from -r requirements.txt (line 22))
Downloading typing_extensions-4.8.0-py3-none-any.whl.metadata (3.0 kB)
Requirement already satisfied: tzdata==2023.3 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from -r requirements.txt (line 23)) (2023.3)
Collecting setuptools<68,>=62.6 (from cx-Freeze==6.15.1->-r requirements.txt (line 5))
Downloading setuptools-67.8.0-py3-none-any.whl.metadata (6.2 kB)
Requirement already satisfied: pillow>=6.2.0 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from matplotlib==3.6.1->-r requirements.txt (line 15)) (10.0.1)
Requirement already satisfied: pyparsing>=2.2.1 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from matplotlib==3.6.1->-r requirements.txt (line 15)) (3.0.9)
Requirement already satisfied: python-dateutil>=2.7 in /Users/kaivoigt/anaconda3/lib/python3.11/site-packages (from matplotlib==3.6.1->-r requirements.txt (line 15)) (2.8.2)
Downloading asgiref-3.7.2-py3-none-any.whl (24 kB)
Downloading cx_Freeze-6.15.1-cp311-cp311-macosx_11_0_arm64.whl (18.3 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 18.3/18.3 MB 5.0 MB/s eta 0:00:00
Downloading Django-4.2.7-py3-none-any.whl (8.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.0/8.0 MB 9.2 MB/s eta 0:00:00
Downloading exceptiongroup-1.2.0-py3-none-any.whl (16 kB)
Downloading lief-0.13.2-cp311-cp311-macosx_11_0_arm64.whl (3.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.2/3.2 MB 9.1 MB/s eta 0:00:00
Downloading typing_extensions-4.8.0-py3-none-any.whl (31 kB)
Downloading setuptools-67.8.0-py3-none-any.whl (1.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 8.9 MB/s eta 0:00:00
Building wheels for collected packages: cx-Logging
Building wheel for cx-Logging (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for cx-Logging (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [38 lines of output]
running bdist_wheel
running build
running build_ext
building 'cx_Logging' extension
creating build
creating build/temp.macosx-11.1-arm64-cpython-311
creating build/temp.macosx-11.1-arm64-cpython-311/src
clang -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /Users/kaivoigt/anaconda3/include -arch arm64 -fPIC -O2 -isystem /Users/kaivoigt/anaconda3/include -arch arm64 -DCX_LOGGING_CORE -DBUILD_VERSION=3.1.0 -I/Users/kaivoigt/anaconda3/include/python3.11 -c src/cx_Logging.c -o build/temp.macosx-11.1-arm64-cpython-311/src/cx_Logging.o
src/cx_Logging.c:949:5: warning: 'sem_init' is deprecated [-Wdeprecated-declarations]
INITIALIZE_LOCK(loggingState->lock);
^
src/cx_Logging.c:37:33: note: expanded from macro 'INITIALIZE_LOCK'
#define INITIALIZE_LOCK(lock)   sem_init(&lock, 0, 1)
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/semaphore.h:55:42: note: 'sem_init' has been explicitly marked deprecated here
int sem_init(sem_t *, int, unsigned int) __deprecated;
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:211:40: note: expanded from macro '__deprecated'
#define __deprecated    attribute((deprecated))
^
src/cx_Logging.c:2703:5: warning: 'sem_init' is deprecated [-Wdeprecated-declarations]
INITIALIZE_LOCK(gLoggingStateLock);
^
src/cx_Logging.c:37:33: note: expanded from macro 'INITIALIZE_LOCK'
#define INITIALIZE_LOCK(lock)   sem_init(&lock, 0, 1)
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/semaphore.h:55:42: note: 'sem_init' has been explicitly marked deprecated here
int sem_init(sem_t *, int, unsigned int) __deprecated;
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:211:40: note: expanded from macro '__deprecated'
#define __deprecated    attribute((deprecated))
^
2 warnings generated.
creating build/lib.macosx-11.1-arm64-cpython-311
clang -bundle -undefined dynamic_lookup -Wl,-rpath,/Users/kaivoigt/anaconda3/lib -L/Users/kaivoigt/anaconda3/lib -Wl,-rpath,/Users/kaivoigt/anaconda3/lib -L/Users/kaivoigt/anaconda3/lib build/temp.macosx-11.1-arm64-cpython-311/src/cx_Logging.o -o build/lib.macosx-11.1-arm64-cpython-311/cx_Logging.cpython-311-darwin.so -Wl,-soname,cx_Logging.cpython-311-darwin.so
ld: unknown options: -soname
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: command '/usr/bin/clang' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for cx-Logging
Failed to build cx-Logging
ERROR: Could not build wheels for cx-Logging, which is required to install pyproject.toml-based projects
(`


Add suppression option for print messages during training loop?

In chainerrl.experiments.train_agent, statistical information is reported via print per episode during the training loop. However, this sometimes looks so verbose and I want to suppress these messages, but currently there is no good way to do so. Adding some option that enables/disables these prints might be beneficial.

I agree. I think adding an option to suppress them is OK, but using logger instead of print might be more flexible.


add repo deletion

The PR supports chart repository deletion functionality by adding chart-repo delete command. cc/ @prydonius

updated via our quick discussion. ptal @prydonius


Firehose handler

@jaysvoboda this should be alright but wanna take a peak?

woo this would be sweet, though I'd suggest using the regular AWS SDK (similar to https://github.com/tj/http_to_firehose/blob/master/client/client.go)

For the logging case we'd need some form of retries / batching for the rate limiting, dropping logs is never great but this would be really awesome to have

Oops, did not mean send this PR. My bad, I meant to just send it to our fork. Definitely not ready yet, if it comes into any kind of workable shape I'll send over another!

sounds good!


Potential fix for ios 14

Not sure this is fixing all settings, but for me it works for most important ones like bluetooth, display etc., haven't really testet thoroughly, but maybe even seeing this PR will help people resolving other issues

Published https://www.npmjs.com/package/cordova-open-native-settings

Published https://www.npmjs.com/package/cordova-open-native-settings


Fat arrow function as property param problem

First of all, thanks for a great project 👍.
I have a situation were I cannot seem to be able to figure out how to get the parameters for a fat arrow function to be reported correctly:
export class AuthenticationSettings {
    /**
     * A notifier method to call whenever the lookup results have been received.
     * @param authToken - The lookup results.
     */
    public cbSuccess: (authToken: string) => void = undefined;
    //...
}

The documentation generated is as follows:

As you can see the comment for the param is not written as a part of the type declaration, as expected.
I have tried to create the type separately (outside the class):
/**
 * A notifier method to call whenever the lookup results have been received.
 * @param authToken - The lookup results.
 */
type CallbackSuccess = cbSuccess: (authToken: string) => void;

But, that did not help neither. The generated CallbackSuccess documentation has the same issue with non-matching params.
I have searched the issues and docs and found no information on how to do this or whether there has been others who has had this problem earlier.
Anyone know how to get this done?
I am using typedoc 0.5.7 btw.

Any considerations?

In 0.21, this renders as:


Stronly typed use of BackupManagementType class and WorkloadType classes in SDK functions like GetBackupProtectableItems

Library name and version
1.9.0?
Query/Question
Hello,
I'm trying to translate some powershell for restoring a sql database backup to an azure hosted cluster. The azure Az powershell module doesn't seem to translate 1:1 to the c# libraries.
I'm trying for example to translate this line in equivalent c# code using the Azure.ResourceManager.* library
$backupItem = Get-AzRecoveryServicesBackupItem -BackupManagementType AzureWorkload -WorkloadType MSSQL -Name "SQLDataBase;$($SourceSqlAGName);$($SourceDatabaseName)" -VaultId $vault.ID  -ProtectionStatus Healthy

I think I need to use the function GetBackupProtectableItems, but this requires me to create a filter. Something I can find little documetation on.
            string filter = "backupManagementType eq 'AzureWorkload'";
            var result = resourceGroup.GetBackupProtectableItems(vaultName, filter);

searching through this code repo I found that there is a BackupManagementType enum and a WorkloadTypeEnum. But I don't see any functions using these classes.
I'm getting kind of lost.
Do I need to create the filter myself based on these classes?
Where is filter parameter of GetBackupProtectableItems documented?
I would expect for a library wrapping a rest service to support these things in a strongly type way. Not with parsing filter strings. Is this incorrect?
Environment
No response

Thank you for reaching out.  I believe you are looking for help with the  Azure.ResourceManager.RecoveryServicesBackup management plane SDK. @ArthurMa1978 could you help route this to the right team members?

Hi @bzuidgeest , Thank you for using Azure SDK for .NET.
Found one possible sample for you, please check:
https://github.com/Azure/azure-sdk-for-net/blob/84c0361d53cc0cfa4c71f8267e28d5af34c6b889/sdk/recoveryservices-backup/Azure.ResourceManager.RecoveryServicesBackup/samples/Generated/Samples/Sample_ResourceGroupResourceExtensions.cs#L166

/unresolve
sorry for the late reply, but I have been enjoying a holiday. The answer from @HarveyLink does the opposite of answering the question. (though the example might be usefull).
The question is about the lack of documentation for these string based filters and the fact that there are mananged classes that seem to pertain to these filters like BackupManagementType and WorkloadTypeEnum. But they are not used anywhere.
Is there tooling to use these classes directly to specify things, instead of magic strings?

/unresolve
sorry for the late reply, but I have been enjoying a holiday. The answer from @HarveyLink Minghao Chen (WICRESOFT NORTH AMERICA LTD) Vendor does the opposite of answering the question. (though the example might be usefull).
The question is about the lack of documentation for these string based filters and the fact that there are mananged classes that seem to pertain to these filters like BackupManagementType and WorkloadTypeEnum. But they are not used anywhere. Is there tooling to use these classes directly to specify things, instead of magic strings?
Also the filter parameter is undocumented. How do you filter by name or other properties?

BackupManagementType  is used as properties in BackupGenericProtectionContainer and it's subclasses, BackupWorkloadType is used in setup BackupProtectionPolicyData and other classes.
Our current SDK is auto generated from the service RESTAPI, the filter string and no detailed comments are designed by service team. Currently there is no convenience layer supported to bypass those properties in our SDK.
If you need the detailed filter usage comments, you could file an issue at https://github.com/Azure/azure-rest-api-specs

"An OData filter expression that filters elements in the collection." Is hardly detailed documentation

Hi @bzuidgeest  , thank you for reaching out to us about the Azure SDK for .NET. Unfortunately, this issue is related to the service side and not the SDK side, so we are not able to help you with it. Therefore, we are closing this issue for now. If you need more assistance, please open an Azure support request. We apologize for any inconvenience this may cause you.
We value your feedback and we want to make sure that your problem is solved. If you think that we have misunderstood your issue or closed it incorrectly, please feel free to comment on this thread and reopen the issue. We will be happy to assist you further. Thank you for your understanding and cooperation.


Fix overflow bug with code points larger than 2^15

Hi, I encountered a bug where it crashes because of an overflow with code points larger than 2^15 on conversion from u16 to i16. Big codepoints are pretty common with Japanese Kanji so it's a serious bug.
I'm not aware of the filetype details, but generally Unicode codepoints are 21 bits width, so it strikes me odd to use u16 for those, but maybe it's a limitation of TrueType? If it isn't and codepoints outside of the basic multilingual plane aren't just supported yet, I can try and help to refactor the code base.

I was considering implementing the fix with a wrapping add, but there's a problem with that: code_point is an u16 and id_delta is an i16, and wrapping_add in the stdlib isn't defined between those. In this corner case, the theoretical range of either is not superset of the other (code_point might be over 2^15 and 'id_delta' might be negative) so one can't safely convert without widening.

I'll see if I can send some PR's to extend the code base since I might be needing that functionality.

(Btw. I signed the Google Individual Contributor License Agreement.)

Inside EncodingFormat4, code_point is limited to 16 bit values. I believe this computation might wrap and that's the behavior specified by the standard. Thus, I think keeping a 16 bit type here is appropriate.
When EncodingFormat12 is implemented, its representation of code point should definitely be a 32 bit value.
I'm happy to answer questions. Also I know @rtsuk has looked at this, I believe he's interested in correct rendering of (b/w) emoji.
Lastly, the Google CLA is not needed anymore, the ownership of this repo has now passed to me. I should probably update the READMEs and so on. But thanks!

So, I don't think there is a "wrapping conversion" of i16 to u16 or vice versa in stdlib, so I was forced to define one by a transmute. I feel like this is an omission in the stdlib, and it feels bad to introduce unsafe code for a thing like this. What do you think about the newest commit?

Are you sure the as panics? I just checked in the playground and it doesn't. The nomicon says it's a "no-op", which is maddeningly vague; I think they mean the bit representation doesn't change, which is what I expect.
There's another way to write this which is maybe more explicit about the intent: ((code_point as i32) + (id_delta as i32) & 0xffff) as u16. But I think just wrapping_add should work.

I'm pretty sure this was my error. Thanks for fixing it!


9 synth and voice

Created a synth and a voice module, made some unit tests, refactored some other tests

implemented what was needed


downstream script

downstream script

Based on dockerfile updates PR, will rebase when it lands.

/hold

do we want the install.yaml to update to ?

do we want the install.yaml to update to ?

You thinking displayName: https://github.com/Kuadrant/kuadrant-console-plugin/blob/main/install.yaml#L138C1-L139C1 ?


Running storybook locally should use parcel watch or equivalent

Running storybook locally currently uses the compiled CSS and JS in dist. For a better experience conducive to "developing components in isolation," running storybook locally should use CSS and JS before they are built for production (essentially the equivalent of npm run dev).
We could do this by configuring Storybook's webpack to compile everything (this is how we do this in www-frontend, but it is unwieldy), or to figure out how to use assets generated by parcel watch with storybook (cleaner, but there might be compatibility issues).

No longer relevant now that we've switched to vite.


Wondering ETA on Powershell 7 compatibility?

Greetings,
I was wondering what the roadmap is to having the Exchange Online v2 available for use with PowerShell 7?  I'm specifically looking into adding some EXO scripts to my Azure Shell environment but at the time of writing this it appears that is not possible.
[Enter feedback here]

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

ID: de2836a0-0af3-c147-2d4a-78220ac4e0f1
Version Independent ID: 2cde9735-6281-bb9f-bf07-b30b2f6c7f37
Content: Exchange Online PowerShell with modern authentication using V2 Module
Content Source: exchange/docs-conceptual/exchange-online-powershell-v2.md
Service: exchange-online
GitHub Login: @chrisda
Microsoft Alias: chrisda

Hi @VeloGeek, thank you for your feedback.
We don't have this information here, but you can follow the Exchange Teams blog to news about the EXO V2 module:
https://techcommunity.microsoft.com/t5/exchange-team-blog/bg-p/Exchange
You can see in the blog that they're currently working on support for PowerShell Core, but there is no ETA.

@dariomws  Thank you very much for the contribution and sharing this explanation. @VeloGeek Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Rev 'mocha' and @types/benchmark dependencies

Mocha was already fairly recent, but @types/mocha was way out of date.  (Bumped both to the latest version.)
Benchmark was already on latest, but '@types/benchmark' was old.
@CraigMacomber - Splitting this change from #6183 so we can quickly land the '*-lock.json' updates as these tend to churn.

Thanks, @tylerbutler !


Too many projects

Hi
Can we found an elegant way to manage many projects
I test with 50 projects, and i see two things

Maybe a pagination (like max 10 projects) will be fine
The search filter must be placed on top of project list

Do you agree ?
Thx

PR : #39

merged PR #39 thank you!
I will test projects client-side pagination ASAP.

Thanx to you

fixed in 1586b67f1b665fbea2557bcfa8e34b2e720b072a


double++, double--

from "stdlib/io.jou" import printf

def main() -> int:
    foo = 12.34
    printf("%.2f %.2f\n", ++foo, --foo)  # Output: 13.34 12.34
    return 0

Expected output: 13.34 12.34
Actual output: compiler error in file "a.jou", line 5: cannot increment a value of type double
Part of #151

After thinking about this a bit, I'm no longer sure if double++ is a good idea. If you find yourself actually doing that, then maybe you should use int instead.


Un-pin numba

This hopefully resolves the issues with #149

@pgrinaway : Changing from
@jit(float64[:](float64[:], float64[:], float64[:], float64[:]), nopython=True, nogil=True, cache=True)

to just
@jit

seems to have fixed the latest numba-compatibility issues. Is that OK, or will that cause huge performance penalties?

That could cause pretty big performance problems. The arguments to the decorator declare the types of the input and require (via nopython and nogil) that the python code be compiled completely to native code. I don't think we can get rid of those.

That could cause pretty big performance problems. The arguments to the decorator declare the types of the input and require (via nopython and nogil) that the python code be compiled completely to native code. I don't think we can get rid of those.

The numba docs seemed to recommend just letting numba compile things lazily and figure out what it needs to do. I imagine it takes some time the first time you call it with specific arguments, but then it caches the compiled versions.
The only thing it doesn't seem that numba can figure out on its own is whether or not to release the gil. I could try just adding gil=True?
Otherwise, I'm not sure how long it will take to figure out why the latest numba can't deal with the requirements you are placing on those functions in the decorators.

Alternatively, we can wait until continuum produces a version of numba that can satisfy your constraints and continue to live without a conda package until then?

Can you switch to a different version of numpy instead of numba?

The numba docs seemed to recommend just letting numba compile things lazily and figure out what it needs to do. I imagine it takes some time the first time you call it with specific arguments, but then it caches the compiled versions.

Yeah, but at least when I wrote the code, comparing the performance with and without the extra arguments showed a considerable speedup with the arguments.

The only thing it doesn't seem that numba can figure out on its own is whether or not to release the gil. I could try just adding gil=True?

You can also just try nopython=True , which might be good enough.

Otherwise, I'm not sure how long it will take to figure out why the latest numba can't deal with the requirements you are placing on those functions in the decorators.

I will raise an issue on numba Monday. But otherwise, if numba continues to be a problem, this code can be rewritten in (efficient) Cython without too much trouble.

You can also just try nopython=True , which might be good enough.

Sure.

Can you switch to a different version of numpy instead of numba?

Could probably do that temporarily if needed.

OK, it seems that nopython=True is the source of the issues.

This comment suggests unrolling the : slice assignment may help.

Well, it was dying on line 32, right? There's an array allocation there. Maybe numba has been compiled against some different library than the version of numpy that we're using?
What's the disadvantage in following Bas's suggestion?

Line 32 is
rotation_matrix[0, 1] = axis[0]*axis[1]*(1.0-cos_angle) - axis[2]*sin_angle

What's the disadvantage in following Bas's suggestion?

Pin numba to 0.27.0 and numpy to 1.09? It's a hack, rather than a solution, and may cause havoc if you try to install perses alongside other tools, but will do that for now.

Oops, must have been looking at an outdate version.

It's a hack, rather than a solution,

Well, it's a patch. I never intended for that to be permanent. We just need it to work now. If numba proves problematic because of numpy version changes like this, I will code that part up in Cython, as I said above. But if we can punt on that, I think it's best that we do.

Hm, specifying the type for the numpy matrix allocation seems to have fixed things...

Numba can be very fickle about types,

Looks like we're good! I'll merge, since this shouldn't have any performance degradation.


Improve circular reference

Change circular reference error log level.

https://github.com/Azure/azure-rest-api-specs/pull/6982

Solved in<EMAIL_ADDRESS>add error level.


Paste menu not appears

I am using the SquarePinField but the Paste Functionality doesn't seem to work.
Any ideas on how I enable it?

Hi, can you share your xml?
Need to check whether you defined android:textSelectHandle="@drawable/text_handle"
Also can you let me know which version of Android are you targeting

I found out that the android:cursorVisible="false" was creating the problem so after deleting it all worked.
Also I am having another issue. a blue line appears under the boxes and I have to set android:background="@android:color/transparent" in order to make it disappear. Do you have any idea about that?

Can you share a screenshot?

Sure

@poovamraj sorry I noticed app:isCustomBackground="true" so it means it has to have a background setted
So everything is ok please close the Issue
Thanks

That's awesome :) Have a good one!


[TACHYON-255] Follow up for swift module

https://tachyon.atlassian.net/projects/TACHYON/issues/TACHYON-255
Fixes a few formatting/style issues.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/3229/
Test FAILed.


Popping Rotation

Thank you for this package!
I'm finding that often when I start a drag, the handle will pop about 30º or so unexpectedly. Also the handle is a little jerky on rotation. Do you have any advice on how I might correct this behaviour, or how I might be creating the issue?
You can see a demo of my implementation here.

Thank you for your notes. It is indeed a bug because scroll top value is ignored on rotation start. I hope I will fix it soon

@pjarmalavicius thank you very much!


Polish translation

Polish translation - pl.yml
utf8 encoded
Cheers

Also as a gist here: https://gist.github.com/dawmster/9a32ea539e1a50a0dc6d5706d95893e6

I will fix the broken key. Thanks a ton for helping out!

My pleasure, cheers.


Fixed array out of bounds bug in HyperLogLog.

Issue
When using HyperLogLog on a large dataset, I came across a panic due to array out of bounds indexing in the neighbor mean calculation in estimate_bias. This was on the most recent master branch, and not the 0.6.0 version of pdatastructs which I know has a separate index out of bounds bug.
Explanation and solution
The issue occurs due to this line in neighbor_search_startpoints, in particular the case where binary_search_by returns Err(n-1) for n = lookup_array.len(). When no exact match is found, binary searching by key returns the index i of the smallest element that is strictly greater than key, which means that the neighbor startpoints should be (i-1, i) and not (i, i+1). As an example, consider lookup_array = vec![0, 2, 4] and key = 1. Clearly we would want to return startpoints (0, 1), which corresponds to (i-1, i) if i is the return value of our binary search, and not (i, i+1) as the code does now.

Thanks!

bors r+


fix(#2376): send unmodified request json body

fixes: #2376, #2362, #1768
added a checkbox in the collection settings' presets tab to choose if the request body should be parsed and de-commented, or be sent as it is needs to be added

(part of the bruno config presets)
https://github.com/usebruno/bruno/assets/25679466/0e8b477e-2ee4-49b8-b057-7c39968b8837
currently bruno supports adding comments in the json body
and before the actual request is made the comments are removed and the body is parsed as json
ref: PR

Does this cover #2207, #2438 as well? I would think getting a less destructive JSON parsing library like suggested in on of those issues would be the better/more transparent solution for the end user.

CLosing since this was addressed in PR https://github.com/usebruno/bruno/pull/2773