vimUtils.vimrcFile: fixes packpath order

Motivation for this change
Fix vimUtils.vimrcFile's packDir import order:

Currently the packDir's plugins are added in rtp after $VIMRUNTIME. This breaks a lot of plugins as most of them expect the pack that the plugin is in  to be loaded before $VIMRUNTIME.
Just adding set packpath^=... is not enough and rtp must also be prepended with the packDir's path. This's makes vim/neovim load plugins from packs in packDir in order specified by its placement in rtp (weird behavior but that's how it works).
With the changes in this PR vim and neovim will load the packDir in a similar manner as when placed in .vim/ or .config/neovim and load order will be correct.

Fixes #39364
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@jonringer @kalbasit Can this PR get reviewed ?

this seems to be a long standing issue, and it seems like you did your due diligence on investigating a solution. Thanks!

Just tested this with a simple config :

My main concern is that people have already developed hacks around the pre-existing design, and they might be incompatible with this fix.

that being said, I would rather have "normal path" work fine, than people having to search through issues and PRs to get their vim workflow going. The individuals who have already developed hacks likely have context to what they did and why it might be wrong.

@timokau might have some insights.

I'll give this PR a try in my vim config and report back.

@megheaiulian I can reproduce the issue with such minimal shell.nix:
with import <nixpkgs> {};
stdenv.mkDerivation {
  name = "env";
  buildInputs = [
    (neovim.override {
      configure = {
        customRC = ''
          set shiftwidth=2
          set softtabstop=2
          set expandtab

          call coc#config('coc', {
          \ 'preferences': {
          \   'codeLens.enable': "true",
          \   'colorSupport': "true",
          \   'extensionUpdateCheck': "never",
          \   'formatOnSaveFiletypes': [ "go" ],
          \ },
          \ 'suggest': {
          \   'acceptSuggestionOnCommitCharacter': "true",
          \   'enablePreview': "true",
          \   'timeout': 2000,
          \   'triggerAfterInsertEnter': "true",
          \ },
          \})
        '';
        packages.myVimPackage = with vimPlugins; {
          start = [
            coc-nvim
          ];
          opt = [ ];
        };
        # Works fine with:
        #plug.plugins = with vimPlugins; [
        #  coc-nvim
        #];
      };
    })
  ];
}

I'm getting this error with package system:
Error detected while processing /nix/store/0jgkc9zhi5h40xqkkd27wa343mshzx3l-vimrc:
line   30:
E117: Unknown function: coc#config

While with plug implementation it just works.

It's been so long I forgot what was breaking on my end.
But I removed my workaround and various plugins seem to work still.
Success?
Happy to test specific things.

@rvolosatovs After further investigating this I think your expectations are wrong.
This works exactly like placing that customRC in your .config/nvim/init.vim and having coc-nvim in  ./config/nvim/pack/myVimPackage/start/coc-nvim. The vimrc loads first and even if the plugin is in start you can't call functions from it there as it is not yet loaded. You can use a AutoCmd to configure the plugin or let g:coc_user_config = ....
Please note the goal of this PR is not to have packages.packageName work like plug.packages. The goal is to have packs work like they do when loaded from defaults dotfiles paths.

Thank you for investigating, my bad then - I assumed all plugins would be loaded already. https://github.com/neoclide/coc.nvim/wiki/Install-coc.nvim#using-vim8s-native-package-manager also does not mention anything about it :thinking:

@rvolosatovs you could ask upstream about it and maybe fix their documentation than.

I think we should backport this one also to at least 20.03, but let's wait for a bit until it its the unstable channel.

I wish this would be fixed upstream, seems like a bug to me. But at least we finally have a fix for nix, thanks @megheaiulian!


Add toggle for indoor activities on Yearly Progression

feature req #598
Adds toggle next to the commute toggle. Functions in much the same way.
Only tested with manual entries, both ones set as a "virtual ride" and those tagged as "indoor cycling" set the SyncedActivityModel.trainer to true

@devon-badman Great work ! Very thanks !!!
I will merge once i added some "unit test" which test your includeIndoorRide filtering and also my includeCommuteRide (didn't test the filter on).
Thanks for all !!
Tom

Merged by https://github.com/thomaschampagne/stravistix/commit/a0fbfb3c2ef0e215b343e2e01ff1af9dac5b002d


Implement user roles

Roles
Use roles to observe results or perform actions from different user perspectives. Also, it's a solution for
the forms authentication problem. Role initialization will be executed once per task on first demand and can be shared among tests and fixtures. Technically role saves created cookies and storages state. When we switch role in tests and if it's not initialized yet then initializations steps run and we return back to the page on which we stopped execution. If it's already initialized then page will be just reloaded with the new credentials.
helpers.js
import { Role } from 'testcafe';

export var registeredUser = Role(t => {
    await t
        .navigateTo('http://example.org')
        .typeText('#login', 'TonyStark')
        .typeText('#password', 'swordFish');
        .click('#login');
});;

test.js
import { registeredUser } from '../helpers';
import { Role } from 'testcafe';

fixture `example.org tests`;

test('Anonymous users can see newly created comments', async t => {
    await t
        .switchRole(registeredUser)
        .navigateTo('http://example.org')
        .typeText('#comment', 'Hey ya!')
        .click('#submit')
        .switchRole(Role.anonymous());

        var comment = await t.select('#comment-data');

        expect(comment.innerText).eql('Hey ya!');
});

[ ] Add cookie jar switcher on hammerhead side
[ ] Implement switchRole and switchToDefaultRole API

[ ] es-next API
[ ] raw API

[ ] Implement anonymous role

Hi Ivan,
I see you're making progress with this case. Is it already in such a state that I could test with it? Or are the bits still to be implemented vital for being able to use it?

@p-bakker
I've only made some refactorings to the moment to prepare construction site for the feature. I've decided to outline things before diving into actual implementation, because there are lots of things to consider for this feature. However, I believe we'll be able to ship it in alpha build somewhere in the end of the next week.

Things that left to consider:

Do we need Role.anonymous()? I still struggle to believe that Role() (constructor without parameters) is a comprehensive API for it.
Is loginPage role constructor parameter should be mandatory? What about scenario when you use server code to create new user and only afterwards navigate to login page?

What about t.ctx: it'll be shared between test and role or not?

@helen-dikareva good point

If we run test step-by-step we will continue debugging in role? And after?
Or if  debug() was set in role, will we continue debugging test?

@helen-dikareva We should keep debugging even in role initializer

Great to see this case being closed. When is the next alpha expected?

@p-bakker We plan to release it today. I'll add note here once it will be available.

Excellent. Am already modifying my tests to start using this as soon as it's released.
While at that, I realized a function to get the active role would be helpful. Is that already included/possible?

I'm happy to let you know that<EMAIL_ADDRESS>is released, and now you can try the Role feature! Install it with npm install testcafe@alpha. You can get the Role API reference using this link: User Roles. As you can see, unfortunately currently there is no function to get the active role.

@p-bakker

While at that, I realized a function to get the active role would be helpful. Is that already included/possible?

We haven't considered such scenario. What's the use case for this?

@inikulin to answer your question above: in my domain specific classes that wrap all interaction with the browser, I expose an API for the writers of tests to use when they want to clean up server-side sessions, since every role equals a login equals a serverside session in my case. When they call my API to cleanup/exit a serverside session, they can pass in a Role. If that Role isn't the currently active Role, I must switch to the Role they want to exit first, before performing an exit in the app, after which I need to some back to my previously active Role.
If the role they want to exit is the active Role, I need to do different stuff.
Makes sense?

I'm playing around with this new functionality, but I'm afraid it ain't working for me.
The stuff I'm testing is a webapp with very dynamic URL, which are closely tied to serverside state.
An example of the flow:

I open the app by going to domain:port/myApp
As the server determines I'm not yet logged in, it redirects me to domain:port/somethingRandom
if I provide proper credentials, the server again redirects me to domain:port/anotherRandomValue

I read the following in the new docs:

If you switch to a role for the first time in test run, the browser will be navigated from the original page to a login page where the role initialization code will be executed. Then the original page will be reloaded with new credentials. If you switch to a role that has already been initialized, TestCafe simply reloads the current page with the appropriate credentials.

The flow described here for when you switch to a role for the first time will not work in my scenario, neither will the part when you switch to an already initialized role: the reload of the current url with the credentials of another Role won't fly, because the url's are session (thus Role) specific.
So it seems to me that this new feature will not work in my scenario where url's are session/role specific and where the login procedure isn't isolated under it's own url and affects the main page under testing only by just setting a cookie of some sort.
Or am I missing something here?
To clarify: the first thing I hoped this feature would allow me to do is just log in once per fixture and have my entire testsuite broken up in individual tests (up to now I just had one test which started with the login in order to make this work). The second thing would be being able to switch between different logged in users during tests

@p-bakker So, if I understood you correct you just basically have URL-based session management? No cookies involved?

No, the session is managed by a JSESSIONID cookie, but the urls of the app are also very dynamic/unique by session

Interesting, so everything will work fine if we'll store URL in Role to which login action led and then on Role switch we redirect to this URL?

Yes, thinking the entire flow through, as far as I can see that would indeed would make it work

@p-bakker OK, it seems easy to implement. I'm only struggling to come up with meaningful option name for such behavior. Any suggestions?

Pfff, good question. Something like dynamicSessionUrls?
It's a bit difficult, because such setting would do multiple things:

change the behavior of of switching between Roles: currently it reloads the current URL with a different Role, so the test remains in the exact same 'route' in your webapp/webpage. The new behavior would redirect the test back to the URL where the app/page was after login everytime.

Come to think of it, maybe the setting should be called something like persistUrl or useActiveUrl/useLastUrl, with a behavior that when switching Role, you get redirected back to the Url where that Role was last. In case it's the first time switching to the Role, the last url is the url where the test was when the login action led to.
Think that such behavior is more generic and could even be useful when you don't have dynamic, session-based url's, as it allows writing tests for apps/pages where you can't just go to any Url, but where there is a sort of sequence to things.
Hope that sort of makes sense

@p-bakker Unfortunately functionality that allows to preserve URL will not make it into next release - we are closing sprint today. However, I've issued a separate ticket for it and more likely we'll implement it in the beginning of the next sprint: https://github.com/DevExpress/testcafe/issues/1339. Meanwhile, you can use following workaround:
import { t, Role, ClientFunction } from 'testcafe';

const getLocation = ClientFunction(() => location.href);

const someRole = Role('http://page', async () => {
      // init steps...

      someRole.preservedUrl = await getLocation();
});

async function switchToRoleAndKeepUrl(role) {
    await t.useRole(role);

    if (role.preservedUrl)
        await t.navigateTo(role.preservedUrl);
}

fixture `Fixture`;

test('Test', async () => {
     //...
      await switchToRoleAndKeepUrl(someRole);
     //...
});

@inikulin no problem, however: I tried your workaround, but for me the code after await t.useRole(role); in  switchToRoleAndKeepUrl is never executed, which means the workaround doesn't function.
Does this workaround work for you?
My code is like this:
console.log('activating session')
 await TestController.useRole(session)
 console.log('session acivated ', session.preservedUrl)

I see the first log statement appearing in the console, but never the second

@p-bakker I can't reproduce it on my side, this works fine for me:
import { t, Role, ClientFunction } from 'testcafe';

const getLocation = ClientFunction(() => location.href);

const someRole = Role('http://google.com', async () => {
    someRole.preservedUrl = await getLocation();
});

async function switchToRoleAndKeepUrl (role) {
    await t.useRole(role);

    console.log('session acivated', role.preservedUrl);

    if (role.preservedUrl)
        await t.navigateTo(role.preservedUrl);
}

fixture `Fixture`
    .page `https://devexpress.github.io/testcafe/example/`;

test('Test', async () => {
    await switchToRoleAndKeepUrl(someRole);
});

@p-bakker Did you manage to make it work on your side?

@inikulin  Yes, I did get it working according to how it should work.
The entire feature however doesn't not work for my specific scenario, but that is a different story, see: https://github.com/DevExpress/testcafe/issues/1339#issuecomment-289529144


[Enhancement][OpenSearch & OpenSearch Dashboards]

Is your feature request related to a problem? Please describe.
Deployment works great in a dual-stacked set-up, however, there is no way for me to set the ipFamilyPolicy to "preferDualStack"
Describe the solution you'd like
Being able to pass this variable would be great, but to be on the safe side, I'd keep it set to singlestack (to keep working as currently expected).
Describe alternatives you've considered
The alternative is me manually adjusting the service to include this.

Just thinking out loud here... should I also include the ipFamilies option to be complete? This way a singlestack ipv6 could be created as well


can't use the powershell to launch the bash.exe

VSCode Version:1.4
OS Version:win 10 14393.10

Steps to Reproduce:

use Ctrl+` to call the powershell
when I want to use the BashOnWindows, it show the result:

Try c:\Windows\sysnative\bash.exe

@Tyriar thanks,it works.
I try to put c:\Windows\sysnative\ in the environment variable ,and it work when it just use bash to call the bash.exe.


add Money to Nox.Ui.Blazor.Lib

add Money to Nox.Ui.Blazor.Lib
Note: added temp MoneyDTO / MoneyModel conversion methods to ListEntityPageBase so that that Add Form works for now - need to review when we come to integrate generator output
Also have used Format & Symbol info to handle currency display for now until we have something better using Currency Ref Data integrated into Nox.Ui.Blazor.Lib
Changed Nox.Ui.Blazor.Lib to ref Nox.Core instead of Nox.Types

@DanielHodgeGH we already have the money and country extensions available see f8b7c64

thanks have created https://regusit.atlassian.net/browse/NOX-549 so I dont forget


Publish Convert-WindowsImage to the PowerShell Gallery

Would it be possible to publish the Convert-WindowsImage module to the PowerShell Gallery? There is an unofficial version posted that has not been updated since 2016.

I've recently posted an updated version of the module to the gallery - it contains all recent changes.
https://www.powershellgallery.com/packages/Hyper-ConvertImage

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Show Ray from anywhere command double press

Describe the Bug
When pressing the shortcut command to 'show Ray from anywhere', I have to press the shortcut twice for it to navigate to Ray. I have tested to see if this is an issue with Workspaces, but it seems to happen even when i'm not using them.
Versions
Ray - 1.12.0
MacOS - Big Sur 11.2
Edit
Noticed that when you have ray open and press your shortcut, the screen just goes black. If you press your shortcut again, it comes back. Also, if you press your shortcut once (so the screen is black), then navigate away from Ray and press your shortcut again, you only need to press it once to show.

We have made some changes around this in a new release that will be available shortly.

Any idea on when this fix will be released? Still happening for me (Ray 1.14.7)


Validator does not enforce readOnly

The validator allows clients to send data over properties having 'readOnly: true'

Thanks.  I reported this in https://github.com/apigee-127/sway/issues/57 but forgot to discuss do so here.


Fail to execute "Execute Function Now..." action after deploying the JavaScript V4 project to a Node.js 14 function app

OS: All
Azure Resources extension: 20231114.1
Azure Functions Extension Version: v1.13.1
Regression: Not a regression
Repro Steps:

Create a JavaScript V4 project and open in VS Code.
Create a Node.js 14 function app -> Deploy the JavaScript V4 project to it -> Expand the function app -> Expand Functions -> Right click the function -> Click "Execute Function Now..." -> Fill default for the request body -> Enter.
Check whether succeeds to execute "Execute Function Now..." action.

Expect:
Succeed to execute "Execute Function Now..." action.
Actual:
Fail to execute "Execute Function Now..." action.

More Info:

This issue also reproduces for the TypeScript V4 project.
This issue doesn't reproduce after deploying the JavaScript V4 project to the function app created with other Node.js runtimes.
This issue doesn't reproduce after deploying the JavaScript V3 project to the Node.js 14 function app.

Node v14 is ~EOL so we won't expect this to work going forward.  We should revisit whether or not we should block users from creating function apps with this runtime.

This actually doesn't have anything to do with EOL dates. The old programming model (v3) is supported on Node.js v14+ and the new programming model (v4) is supported on Node.js v18+ as documented here. The new model has never and will never work on Node 14. The old model should continue to work regardless of the EOL date, although customers are required to upgrade before they receive customer support


[FLINK-17159] Use testcontainers for Elasticsearch ITCases

This should harden the tests because we now use random ports for the ES
nodes. I have a suspicion that we had clashes before, which were causing
test instability.
Additionally, this allows us to get rid of quite some of our own code
for setting up an ES environment. Once we drop ES5 we can additionally
drop ElasticsearchResource and EmbeddedElasticsearchNodeEnvironment.
Brief change log

replace use of ElasticsearchResource by testcontainers
we cannot do that for ES 5 because there is no docker container for it

Verifying this change
Covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

@aljoscha I can take a look as well if you want as I coded the Apache Beam connectors for ES.

@echauchot Sure, but this is just touching the tests as little. 😅

I was trying to do that but there is no official elasticsearch-oss image for 5.x versions provided by elastic: https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html.
I'm still seeing if we can somehow make it work.

@aljoscha FYI 5.x images are available on Docker Hub:
https://hub.docker.com/layers/elasticsearch/library/elasticsearch/5.6.16-alpine/images/sha256-5e2dac90ba245b61ef764a44b811cb79f3acda1e8e8ee370a49c0cb5dd70f537?context=explore

@bsideup These images don't work out-of-box with testcontainers. I spent an hour trying to make it work with the non-elastic images but don't want to spend more time because I'm hoping we'll deprecated ES5 soon.

@bsideup These images don't work out-of-box with testcontainers. I spent an hour trying to make it work with the non-elastic images but don't want to spend more time because I'm hoping we'll deprecated ES5 soon.

But the images I sent above are the official Elastic ones for 5.x so they should work

They are different in what configuration they allow from the outside, so things that testcontainers expects to work don't work for some reason. For reference, these are the ES images from the ES docker repo: https://www.docker.elastic.co/r/elasticsearch. But the 5.3.3 image from there also doesn't work out-of-box with what I'm trying to do. I suggest to merge this as is once CI is green and someone else can try and make it work for ES5 if they want to. But I think it's not worth the effort since I'm hoping we can deprecate/remove ES5 soon.

They are different in what configuration they allow from the outside, so things that testcontainers expects to work don't work for some reason. For reference, these are the ES images from the ES docker repo: https://www.docker.elastic.co/r/elasticsearch. But the 5.3.3 image from there also doesn't work out-of-box with what I'm trying to do. I suggest to merge this as is once CI is green and someone else can try and make it work for ES5 if they want to. But I think it's not worth the effort since I'm hoping we can deprecate/remove ES5 soon.

Ok thanks for these precisions. I agree spending too much time on making it work for ES5 might not be useful as the end of life of the last ES5.x was 2019-03-11 and it is no more maintained by elastic since version 7.0 is out. LGTM for merging once CI is green. I saw no thread about deprecating/removing ES5 support in the ML so I'll create one.

@echauchot There were multiple such threads ;)

https://lists.apache.org/thread.html/r0baa1ffbc12b0f3d9312d3145091b4df4298112e4eecb7687d89fee3%40<user.flink.apache.org>
https://lists.apache.org/thread.html/r3144c1417d577ac165f9ae1f1466686312384965c4afeaf7c7a6b38f%40<dev.flink.apache.org>

@dawidwys thanks for the links, I did not found the threads, no need to create a new one then :)

Merged!


checkpoints unavailable

Hello,
This seems to be very promising work, and I am looking forward to testing the summarization pipeline. However if bart-it seems to be available with transformers, it is not the case with any of the fine tuned models or any of the tokenizers. Is there another way to load the bart-it-fanpage for example ?
Thank you in advance!

Hi @Herice31-53 ,
Thank you for the kind words. You can access all models by simply using the following:
from transformers import AutoModel, AutoTokenizer

model_tag = "morenolq/bart-it"
model = AutoModel.from_pretrained(model_tag)
tokenizer = AutoTokenizer.from_pretrained(model_tag)

model_tag can be set to:

morenolq/bart-it - for pre-trained model (no fine-tuning)
morenolq/bart-it-fanpage - for fanpage
morenolq/bart-it-ilpost - for Il post
morenolq/bart-it-WITS - for Wikipedia style summarization

If you want to access one of them independently, you can clone the repository by running:
git clone URL

Where URL is simply one of the paths on the HuggingFace Hub.

Hello,
This is actually my issue.
The code you provided:
from transformers import AutoModel, AutoTokenizer
model_tag = "morenolq/bart-it"
model = AutoModel.from_pretrained(model_tag)
works only for model_tag=morenolq/bart-it
When calling this with any other model_tag, the model simply won't load. I checked and they are indeed present on Huggingface since I do not have any error, but the model still won't load.
Any idea why ?
Worst case I can just retrain them using your summarization training.
Thanks for your reply !

Thank you for highlighting this. In case someone is wondering, you can simply do:
git clone URL
and then use the local path instead of the model tag.


Broken link to the data

Hi @csimstu2,
when I try to download the provided dataset I get an error 404, so the link to the data seems to be broken. Could you check it, please?

Hi,
Thanks for bringing up this issue. Currently we are in the stage of checking all license issues before releasing the data. If that goes through we should be able to release the data this week.

Ok, thank you for replying!


support minimal node image

Related to https://github.com/lovell/detect-libc/issues/10#issuecomment-346224092

@lovell can you have a look at this pull request? :-)

FWIW, if I was doing this, I'd write a safe readdirSync wrapper that returns an empty Array instead of throwing an exception.. not sure if that would be consistent with the prevailing style, though.

Thanks both, I'll publish a new release later today.


Multivariate normal sampling

When trying to sample from the MVN distribution:
x = pyro.sample("my_sample",dist.MultivariateNormal, mu,sigma)   print(x)
However, instead of a FloatTensor Variable, it returns simply
MultivariateNormal()
Is this expected behaviour / how can we pyro.sample from the distribution for now?
Many thanks

To sample from distribution objects, write
x = pyro.sample("my_sample", dist.MultivariateNormal(mu,sigma))
print(x)

@jpchen Do you have an ETA on publishing documentation for the dev branch #547 so users can see this new idiom?

this is not a change related to using dev, this is just about pyro semantics. there was an identical issue here. see the usage in this example.
sorry, been busy with other high priority work. we'll have versioning for documentation before our next release, though thats not related to this problem.

@jpchen This issue was caused by obsolete documentation at http://pyro.ai. You and I updated docs from pyro.sample("name", dist.normal, mu, sigma) to pyro.sample("x", dist.Normal(mu, sigma)), but these changes are not yet published.


install zan via pecl/yum/apt-get?

It's inconvenient to compile zan extention in production environment. Of course docker is a selection.
But is zan stable enough to submit to pecl?

Fork a existing pecl package and add it to pecl again?
Never see this happened before.

@gouchaoer We have no plan to publish zan in other repo yet.
Thanks for your suggest, enjoy!  :)


Two critical problems with blocks.

When it came to testing this library I have noticed two things.

You can't create a component block within a nested sfc.
You can use a component that was created by the component block inside of another one.

I don't know if those decisions were intentional or not. but it seems like you did not think of this stuff.
If these two problems are not solved then using JSX would be the superior chioce. I think Number 1 does not need to be solved but No.2 does.
Along with #4 these are the problems with the library so far. I'm personally comfortable with the library as these problems will n
Created text component

ot limit my current projects but they are still problems.
Attempt to use text component inside of the increment button one

Link to minimal reproducible example
https://github.com/louiss0/vue-nested-sfc-test

Oh if you are done with these problems please go to 1.0.0 People will not take this lib seriously if you don't go to 1.0.0 soon. Or they will be suspicious. I know the JS community doesn't take this stuff seriously but please don't make that mistake.
Im rooting for the success of this lib

Thanks for the suggestions!
Regarding the first issue, it's due to how compiler-sfc parses blocks following the HTML Standard. Even within scripts you can't have a closing </script> inside a string (e.g. <script> const str = "</script>"; </script>). The same applies to other blocks including the component block, you can't include the literal </component> inside its content, because the content is treated as raw text.
Regarding the second issue, it has to wait until #6 is fixed.
Regarding the images, I'm not sure which issue they're referring to (the reproduction link doesn't have the same example), is this another issue?

Well then I'm going to have to maybe close this issue when No.2 is solved. This library is ready for prime time now. But I have to say that If No.2 is not solved this library will not grow too much.

Thanks for the suggestions!
Regarding the first issue, it's due to how compiler-sfc parses blocks following the HTML Standard. Even within scripts you can't have a closing </script> inside a string (e.g. <script> const str = "</script>"; </script>). The same applies to other blocks including the component block, you can't include the literal </component> inside its content, because the content is treated as raw text.
Regarding the second issue, it has to wait until #6 is fixed.
Regarding the images, I'm not sure which issue they're referring to (the reproduction link doesn't have the same example), is this another issue?

I think you forgot to solve the second problem I have found a way to use components that are inside of others but that is not how I want things to be done.
For me to use and SFC inside of another SFC I need to export the component then import it inside of the other one.
I wish there was a way to manipulate blocks so that the components would be auto imported this is what I mean here


[BUG] Problems with inconsistent XY dimensions between calibration, background images, and data recon

Problem
Errors arise when using different image dimensions for calibration, background images, and data reconstruction.
recOrder keeps track of the ROI and image dimensions used for calibration. I believe errors pop up (need to confirm) if then a different image size is used for data acquisition and reconstruction. I believe this is because the calibration image size metadata is used for pre-allocating reconstructed data arrays. The image size used for calibration should not affect downstream acquisition and recon - size of recon arrays should be determined from size of raw data arrays.
Errors also pop up if using bg images and raw data of different XY dimensions, which mostly makes sense. Right now there is no check if the bg images and raw data are of the same XY dimensions and the error message is not meaningful. At the beginning of the recon we should check that the dims are consistent and raise a meaningful error if they are not.
As a sub-case of this, sometimes we acquire bg images at full FOV and acquire data from a smaller ROI. MM does a good job at defining the exact location of the ROI. We should take advantage of that and use the correct sub-crop of the bg images when reconstructing data from a smaller ROI.

In preparation for the 0.2.0 release I have confirmed that a calibration on an ROI does not affect downstream acquisitions (the ROI fields in the calibration_metadata file are not used in creating the reconstruction arrays).
I have decided to leave this issue open and change it to a 1.0.0 release. I am having enough difficulty getting matched-dimension background correction to work reliably in online and offline mode, so I am weary of handling all combinations of mismatched sizes.
For 1.0.0 we will only support offline-mode reconstructions, so all of these different cases can be tested automatically.

Task list for this issue

[x] decouple calibration ROIs from downstream analysis (see #169)
[ ] if the acquisition is smaller than the background, crop the background image appropriately and apply the "Measured" background correction correctly.
[ ] if the background is smaller than the acquisition, warn the user, average the background, then apply a uniform background correction.

Talon, I think you've described the correct expected behavior in

[ ]  if the acquisition is smaller than the background, crop the background image appropriately and apply the "Measured" background correction correctly.
[ ]  if the background is smaller than the acquisition, warn the user, average the background, then apply a uniform background correction.

The second case is useful, for example when imaging relatively confluent cells where the user cannot find a completely empty FOV within the sample. Then I would acquire a background over a small ROI free of cells, and manually average the intensity to perform background correction. I think letting recOrder/waveorder do that would be convenient, but should come with proper documentation and maybe a warning - it's not necessarily intuitive what may happen if the user supplies samples and bg images of different sizes.


argument error

when i try to use python train_scene.py -s got this error

when i try to use python train_scene.py -s got this error

i also get the same bug, you may need change zhe code~

Hi, do you use the diff-rasterizer provided by 3DGS? Please use our provided one in the submodule.

Hi, do you use the diff-rasterizer provided by 3DGS? Please use our provided one in the submodule.
@Jumpat
i use this python /home/xiangyue/joonwon/SegAnyGAussians/convert.py  -s /home/xiangyue/joonwon/SegAnyGAussians/imgs/owl/  but i got that eerror

Hi, do you use the diff-rasterizer provided by 3DGS? Please use our provided one in the submodule.

yes i use python /home/xiangyue/joonwon/SegAnyGAussians/convert.py  -s /home/xiangyue/joonwon/SegAnyGAussians/imgs/owl/
but got that error  @Jumpat

There must be some misunderstood, since the convert.py does not involve the rendering and thus it should not report such error. The convert.py is only a script that calls the colmap for image processing.

There must be some misunderstanding, since the convert.py does not involve the rendering and thus it should not report such error. The convert.py is only a script that calls the colmap for image processing.

I'll try again thanks

There must be some misunderstanding, since the convert.py does not involve the rendering and thus it should not report such error. The convert.py is only a script that calls the colmap for image processing.

I set the environment to overwrite the existing gs3d environment, so I guess I did something wrong there, thanks.


qt-box-editor: init at unstable-2019-07-12

latest unstable version is only one to build with tesseract4 and qt5
Motivation for this change
LGTM I have tested that the binary works for my OCR training
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nix-review pr 64677 1

1 package were build:

qt-box-editor

@GrahamcOfBorg build qt-box-editor

Build is failing on darwin.

I do not have any nice way of testing darwin. This was the error cp: -r not specified; omitting directory 'release/qt-box-editor-1.12rc1.app'. I have been using cp in the linux build since for some reason the binary is not being put in bin for the installPhase automatically. Do you know why this is?

The qmake files lack an INSTALLS and a target.path so they don't install anything.

@worldofpeace fixed! Thank you so much for the help

@GrahamcOfBorg build qt-box-editor

Thanks @costrouc.
Just going to test the darwin build.
@GrahamcOfBorg build qt-box-editor

Seems to build. I admittedly don't know that much about macos, so that could be the incorrect target.path.
But at least it isn't failing to install anything.


chore(linting): import order

Try out this version of the Hiro Wallet - download extension builds.

Hope you appreciate this one Fara. Edu mentioned in our 1:1 and realised it's been a while since I last checked the prettier plugin, which at the time, didn't have the options we wanted.

Merging quick to avoid conflict issues, assuming this has your 👍🏼  @fbwoolf


Cannot start the Application

System: Arch Linux (KDE)
The Error message is:
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
14:03:18.161 › Checking for update
Gtk-Message: 14:03:18.485: Failed to load module "appmenu-gtk-module"
(node:12486) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
14:03:18.555 › {
level: 'info',
from: 'AssetCache',
type: 'latestVersionPath',
data: {
message: 'latestVersion.json path /home/lepliex/.config/notion-app-enhanced/notionAssetCache-v2/latestVersion.json'
}
}
14:03:18.558 › Error: Error: ENOENT: no such file or directory, open '/opt/Notion Enhanced/resources/app-update.yml'
14:03:18.559 › {
level: 'info',
from: 'AssetCache',
type: 'errorReadingPath',
error: {
name: 'Error',
message: "ENOENT: no such file or directory, open '/home/lepliex/.config/notion-app-enhanced/notionAssetCache-v2/latestVersion.json'",
stack: "Error: ENOENT: no such file or directory, open '/home/lepliex/.config/notion-app-enhanced/notionAssetCache-v2/latestVersion.json'"
},
data: {
message: 'Error reading /home/lepliex/.config/notion-app-enhanced/notionAssetCache-v2/latestVersion.json'
}
}
14:03:18.560 › {
level: 'info',
from: 'AssetCache',
type: 'currentVersionLoaded',
data: {}
}
14:03:18.561 › {
level: 'info',
from: 'AssetCache',
type: 'syncVersionEmptyLatestVersion'
}
14:03:18.561 › {
level: 'info',
from: 'AssetCache',
type: 'currentSyncedAssetsJson',
data: {}
}
14:03:18.575 › {
level: 'error',
from: 'main',
type: 'unhandledRejection',
error: {
name: 'TypeError',
message: 'focused_window.isMaximized is not a function',
stack: 'TypeError: focused_window.isMaximized is not a function\n' +
'    at Object.__exports.createWindow (/opt/Notion Enhanced/resources/app/embedded_enhancer/mods/core/createWindow.js:42:43)\n' +
'    at handleActivate (/opt/Notion Enhanced/resources/app/main/main.js:71:36)\n' +
'    at startup (/opt/Notion Enhanced/resources/app/main/main.js:149:5)\n' +
'    at processTicksAndRejections (internal/process/task_queues.js:97:5)'
}
}
14:03:18.737 › Websocket listening on 40023...
14:03:18.740 › Set up server listeners with auth (6912c2e61c19cd2d84152d554696e9146d5676cf)...
(node:12486) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
(node:12486) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
14:03:19.945 › {
level: 'error',
from: 'main',
type: 'uncaughtException',
error: {
name: 'TypeError',
message: 'One-time callback was called more than once',
stack: 'TypeError: One-time callback was called more than once\n' +
'    at ClientRequest. (/opt/Notion Enhanced/resources/app/main/schemeHandler.js:194:9)\n' +
'    at ClientRequest.emit (events.js:315:20)\n' +
'    at SimpleURLLoaderWrapper. (electron/js2c/browser_init.js:105:6293)\n' +
'    at SimpleURLLoaderWrapper.emit (events.js:315:20)'
}
}
14:03:19.949 › {
level: 'error',
from: 'main',
type: 'uncaughtException',
error: {
name: 'TypeError',
message: 'One-time callback was called more than once',
stack: 'TypeError: One-time callback was called more than once\n' +
'    at ClientRequest. (/opt/Notion Enhanced/resources/app/main/schemeHandler.js:194:9)\n' +
'    at ClientRequest.emit (events.js:315:20)\n' +
'    at SimpleURLLoaderWrapper. (electron/js2c/browser_init.js:105:6293)\n' +
'    at SimpleURLLoaderWrapper.emit (events.js:315:20)'
}
}
14:03:19.955 › {
level: 'error',
from: 'main',
type: 'uncaughtException',
error: {
name: 'TypeError',
message: 'One-time callback was called more than once',
stack: 'TypeError: One-time callback was called more than once\n' +
'    at ClientRequest. (/opt/Notion Enhanced/resources/app/main/schemeHandler.js:194:9)\n' +
'    at ClientRequest.emit (events.js:315:20)\n' +
'    at SimpleURLLoaderWrapper. (electron/js2c/browser_init.js:105:6293)\n' +
'    at SimpleURLLoaderWrapper.emit (events.js:315:20)'
}
}
14:03:19.955 › {
level: 'error',
from: 'main',
type: 'uncaughtException',
error: {
name: 'TypeError',
message: 'One-time callback was called more than once',
stack: 'TypeError: One-time callback was called more than once\n' +
'    at ClientRequest. (/opt/Notion Enhanced/resources/app/main/schemeHandler.js:194:9)\n' +
'    at ClientRequest.emit (events.js:315:20)\n' +
'    at SimpleURLLoaderWrapper. (electron/js2c/browser_init.js:105:6293)\n' +
'    at SimpleURLLoaderWrapper.emit (events.js:315:20)'
}
}
14:03:19.956 › {
level: 'error',
from: 'main',
type: 'uncaughtException',
error: {
name: 'TypeError',
message: 'One-time callback was called more than once',
stack: 'TypeError: One-time callback was called more than once\n' +
'    at ClientRequest. (/opt/Notion Enhanced/resources/app/main/schemeHandler.js:194:9)\n' +
'    at ClientRequest.emit (events.js:315:20)\n' +
'    at SimpleURLLoaderWrapper. (electron/js2c/browser_init.js:105:6293)\n' +
'    at SimpleURLLoaderWrapper.emit (events.js:315:20)'
}
}
14:03:19.960 › {
level: 'error',
from: 'main',
type: 'uncaughtException',
error: {
name: 'TypeError',
message: 'One-time callback was called more than once',
stack: 'TypeError: One-time callback was called more than once\n' +
'    at ClientRequest. (/opt/Notion Enhanced/resources/app/main/schemeHandler.js:194:9)\n' +
'    at ClientRequest.emit (events.js:315:20)\n' +
'    at SimpleURLLoaderWrapper. (electron/js2c/browser_init.js:105:6293)\n' +
'    at SimpleURLLoaderWrapper.emit (events.js:315:20)'
}
}
14:03:19.962 › {
level: 'error',
from: 'main',
type: 'uncaughtException',
error: {
name: 'TypeError',
message: 'One-time callback was called more than once',
stack: 'TypeError: One-time callback was called more than once\n' +
'    at ClientRequest. (/opt/Notion Enhanced/resources/app/main/schemeHandler.js:194:9)\n' +
'    at ClientRequest.emit (events.js:315:20)\n' +
'    at SimpleURLLoaderWrapper. (electron/js2c/browser_init.js:105:6293)\n' +
'    at SimpleURLLoaderWrapper.emit (events.js:315:20)'
}
}

I'm still having this issue, even after installing the 2.0.18-1 AppImage from the releases tap. Not sure what to do. I haven't been able to use notion locally for a while.


Potential Bug in CenterPoint

Describe the bug
When training using CenterPoint, it will raise an error at L404 https://github.com/open-mmlab/mmdetection3d/blob/391a56b6af48f5056a769c4cd18dfac2a67c6c06/mmdet3d/models/dense_heads/centerpoint_head.py#L402-L405
The error message is
*** TypeError: can't convert cuda:0 device type tensor to numpy. Use Tensor.cpu() to copy the tensor to host memory first.

I suspect it is due to the update of numpy, which changes the behavior of np.array function. Now I use numpy 1.20.0, and I have tried using an earlier version of numpy like 1.19.1 but then there will be another error like this https://github.com/open-mmlab/mmdetection3d/issues/301.
Currently I can solve this error by
        device = heatmaps[0][0].device
        heatmaps = [[y.cpu() for y in x] for x in heatmaps]
        heatmaps = np.array(heatmaps).transpose(1, 0).tolist()
        heatmaps = [torch.stack(hms_).to(device) for hms_ in heatmaps]

but it may increase the training time since it brings memory copy between CPU and GPU.  Could you please share your numpy and mmpycocotools version or other solutions to this problem?
Reproduction

What command or script did you run?

./tools/dist_train.sh configs/centerpoint/centerpoint_02pillar_second_secfpn_dcn_4x8_cyclic_20e_nus.py 4

Did you make any modifications on the code or config? Did you understand what you have modified?
I didn't make any modifications
What dataset did you use?
nuScenes

Environment

Please run python mmdet3d/utils/collect_env.py to collect necessary environment infomation and paste it here.

sys.platform: linux
Python: 3.8.8 | packaged by conda-forge | (default, Feb 20 2021, 16:22:27) [GCC 9.3.0]
CUDA available: True
GPU 0,1,2,3,4,5,6,7: Tesla V100-PCIE-16GB
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.2, V10.2.89
GCC: gcc (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
PyTorch: 1.6.0
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2019.0.5 Product Build 20190808 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v1.5.0 (Git Hash e2ac1fac44c5078ca927cb9b90e1b3066a0b2ed0)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 10.2
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75
  - CuDNN 7.6.5
  - Magma 2.5.2
  - Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_VULKAN_WRAPPER -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.7.0
OpenCV: 4.5.1
MMCV: 1.2.5
MMCV Compiler: GCC 7.3
MMCV CUDA Compiler: 10.2
MMDetection: 2.10.0
MMDetection3D: 0.11.0+391a56b

You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

I think for some reason the LiDARInstance3DBoxes is converted to cuda in the current version? It works well a few months ago

Thanks @tianweiy for your help, I install np1.19.4 and the problem was solved


Reorder tuning strips

As a user, I want to reorder the tuning strips.
Consider:

Drag and drop
Up/down buttons (good only for a few moves; tiresome for more)

Drag and drop is not accessible for keyboard-only users, so if drag and drop is done, it would be helpful to also provide keyboard-focusable button on each tuning strip that activates a move operation controlled with cursor keys, finalized by Enter/Space keys, and aborted by the Escape key.

New design option: a button on the tuning bar to promote it to the top as a reference tuning. This makes full reordering possible with a little thought, but the most foreseen use of this feature is to select a tuning as reference, or to group two items at the top.

Example of implementation. A Promote as reference icons displays for all tunings except the top tuning.

When you select Promote as reference on a tuning row, it moves to the top, and is used as reference. That means its lines drop through all the other tunings, for easy visual comparison.


Enable PolyKinds

This change enables the kind of the indexes to be polymorphic, whereas previously they were fixed to kind *. It's a backwards compatible change.

Do you have any other changes in mind or can I upload these changes to Hackage?

I have no other concrete changes at this point, I'm just playing around
with the library to see if it works for a small project I have in mind. If
something else comes up I'll report it here, but go ahead and upload it to
hackage if you want to.
On Apr 3, 2016 3:41 AM, "Gabriel Gonzalez"<EMAIL_ADDRESS>wrote:

Do you have any other changes in mind or can I upload these changes to
Hackage?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Gabriel439/Haskell-Index-Core-Library/pull/7#issuecomment-204889197

Actually, let me verify whether the "Do" module also needs to have
PokyKinds enabled before sending this to hackage.
I'm not sure.
On Apr 3, 2016 10:30 AM, "Renzo Carbonara"<EMAIL_ADDRESS>wrote:

I have no other concrete changes at this point, I'm just playing around
with the library to see if it works for a small project I have in mind. If
something else comes up I'll report it here, but go ahead and upload it to
hackage if you want to.
On Apr 3, 2016 3:41 AM, "Gabriel Gonzalez"<EMAIL_ADDRESS>wrote:

Do you have any other changes in mind or can I upload these changes to
Hackage?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Gabriel439/Haskell-Index-Core-Library/pull/7#issuecomment-204889197

I can upload now if you want

Gabriel, feel free to upload this, I won't be submitting any new changes
soon.
On Apr 4, 2016 10:34 PM, "Gabriel Gonzalez"<EMAIL_ADDRESS>wrote:

I can upload now if you want
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Gabriel439/Haskell-Index-Core-Library/pull/7#issuecomment-205583073

Alright, this is up on Hackage as index-core-1.0.3


sentry_flutter not recognized

Platform:

[ ]  Dart
[x]  Flutter Android or iOS
[ ]  Flutter Web

IDE:

[x]  VSCode
[ ]  IntelliJ/AS
[ ]  XCode
[ ]  Other, which one?

split-debug-info and obfuscate (Flutter Android or iOS) or CanvasKit (Flutter Web):

[ ]  Enabled
[ ]  Disabled

Platform installed with:

[x] pub.dev
[ ] GitHub

Output of the command flutter doctor -v below:
❯ flutter doctor -v
[✓] Flutter (Channel stable, 3.0.1, on macOS 12.3.1 21E258 darwin-x64, locale en-GB)
• Flutter version 3.0.1 at /usr/local/Caskroom/flutter/2.2.3/flutter
• Upstream repository https://github.com/flutter/flutter.git
• FLUTTER_GIT_URL = https://github.com/flutter/flutter.git
• Framework revision fb57da5f94 (3 weeks ago), 2022-05-19 15:50:29 -0700
• Engine revision caaafc5604
• Dart version 2.17.1
• DevTools version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc2)
• Android SDK at /Users/pedroluz/Library/Android/sdk
• Platform android-32, build-tools 33.0.0-rc2
• ANDROID_HOME = /Users/pedroluz/Library/Android/sdk
• Java binary at: /Users/pedroluz/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/212.5712.43.2112.8609683/Android Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 13.4)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2021.2)
• Android Studio at /Users/pedroluz/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/212.5712.43.2112.8609683/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
[✓] Android Studio (version 2021.2)
• Android Studio at /Users/pedroluz/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/212.5712.43.2112.8512546/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
[✓] VS Code (version 1.67.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.42.0
[✓] Connected device (3 available)
• Pedro's iFodas (mobile) • 8bcbadc6fc517c318b274a9ca9dbf57a320b79e0 • ios            • iOS 15.5 19F77
• macOS (desktop)         • macos                                    • darwin-x64     • macOS 12.3.1 21E258 darwin-x64
• Chrome (web)            • chrome                                   • web-javascript • Google Chrome 102.0.5005.61
! Error: Pedro's iFodas is not connected. Xcode will continue when Pedro's iFodas is connected. (code -13)
! Error: Pedro's iFodas is busy: Fetching debug symbols for Pedro's iFodas. Xcode will continue when Pedro's iFodas is finished. (code -10)
[✓] HTTP Host Availability
• All required HTTP hosts are available
• No issues found!
The version of the SDK (See pubspec.lock):
6.5.1

I have the following issue:
I would like to know why is that after instalation nothing of sentry_flutter is recognized.
The description goes here ...
Steps to reproduce:

add to sentry_flutter: ^6.5.1 to pubspec
flutter pub get
add package:sentry_flutter/sentry_flutter.dart'. anywhere in your code
FAIL

Actual result:
Target of URI doesn't exist: 'package:sentry_flutter/sentry_flutter.dart'.
Undefined name 'SentryFlutter'.
Expected result:

Not complaning, recognize the import, work without making me waste 3 days.

@Narven can you provide a repro? it works for me.

Manage to fix the problem. Looks like it was a issue with Dart Analysis Server on vscode. but running the restart command... is now work.
Thanks @marandaneto


-v commandline flag is ignored

Environmental Info:
K3s Version: v1.24.6+k3s1
Node(s) CPU architecture, OS, and Version:
Linux lenovo 5.14.21-150400.22-default https://github.com/k3s-io/k3s/issues/1 SMP PREEMPT_DYNAMIC Wed May 11 06:57:18 UTC 2022 (49db222) x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
k3d, 3 servers, 0 agents
Describe the bug:
-v is silently ignored, eg., using -v=6 does not result in trace logs being produced by docker logs -f k3d-$CLUSTER_NAME-server-0.
Steps To Reproduce:

Install k3s (tested with v1.24.6+k3s1)
Run k3s with  the -v=6 option

Expected behavior:
Lines such as the following should be produced:
time="2022-12-16T14:45:04Z" level=trace msg="WATCH READ id=26, key=/registry/leases/kube-system/k3s, revision=1833"

Actual behavior:
No lines with level=trace are produced.

Closing since it looks like this is desired behavior.


Create kigamboniacademy.txt

Commit Kigamboni Accademy

@emmanuelmbwambo This is a duplicate to #19196. I am closing this request as a duplicate.


Fix eager offset storage bug

Await handle before storing new offsets
If we don't do this then we run the risk of committing offsets for
messages that may not have been handled yet. It exposes consumers to the
possibility of consuming messages more than once, but makes this wrapper
behave closer to how Kafunk does in terms of at-least-once semantics.
Addresses one of the concerns raised in #9.

Doh, nice catch.
My test environment behaves funky, as soon as I fix it, I'll merge.


Error "Cannot read property 'openConfigFile' of undefined" when starting python program without the debugger

Environment data
VS Code version:  1.18.0
Python Extension version:  0.8.0
Python Version:   2.7.14
OS and version:    Windows 10
Actual behavior
Press Ctrl+F5 to start a python program without the debugger, and VS Code displays the error
"Cannot read property 'openConfigFile' of undefined"
F5 to start with the debugger works fine.
Expected  behavior
Should just start the program. It always did with Python Extension 0.7.0, which I had been using for some time.
Steps to reproduce:
Start any python program inside version 0.8.0 of this extension, without the debugger.
Logs
No output

This is the same as issue #25

@Agnpalm we think this is a slightly different case.

Duplicate of #25


Enable quantization flag

In the last version of TFLite there is an Enable quantization  flag which allow you to use GPU delegate for quantized models.
Otherwise you end up loading model as without GPU delegate (at least from my experiments).
Here are the links to the TFLite:

For Android here and here and
For iOS here

Actually I already experimented with it and it kinda working:
You can take a look into this commit https://github.com/applikationsprogramvara/tflite_flutter_plugin/commit/11f81946c17ae5c5bf6361a64b13b94abeaf11ac
Though I am not sure how it will work with the previous versions, where the quantization flag is still missing.
You can consider to add the code to the main branch.

Thanks @applikationsprogramvara, Would you like to make a PR for this?


Working in swift 4

Their is an issue in it, its slider which is show at the bottom of the tab is not working it is hold on a pageMenu tab and don't move to the next

the same to you


Add support for "modify at position"

Requirements:

inject lines
inject (append) line at specified column;
Inject result of the function

Not all tests yet written for this approach


Doesn't handle when imports are commented out

example:
// import Foo from 'foo';
/*
import Bar from 'bar';
import Baz from 'baz';
*/
import React, {
//  useState,
  useCallback,
//  useRef,
  useEffect
} from "react";

From the above, we should filter out:

import Foo from 'foo';
import Bar from 'bar';
import Baz from 'baz';
useState
useRef

And we should only "see":
import React, {
  useCallback,
  useEffect,
} from "react";

I still see commented out imports.
How did you fix this?


Coverity: dereference after null checks

[ ] documentation is added or updated
[x] tests are added or updated

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Merged to master, thanks for the feedback.


XCode build fails: Redefinition of enumerator 'SYNTAX_ERR

Bug Report
XCode build fails: Redefinition of enumerator 'SYNTAX_ERR
Problem
The error started to appear when I added the below cordova plugins to the project where cordova-sqlite-storage plugin already existed:

cordova-plugin-file
cordova-plugin-qrscanner

What is expected to happen?
Build should not break.
What does actually happen?
Xcode build fails
Information
The cordova-sqlite-storage plugin has WebSQLError enum with SYNTAX_ERR = 5 and cordova-plugin-file plugin has CDVFileError enum with SYNTAX_ERR = 8. It seems to be the problem with the same name for these enums.
Command or Code
N/A
Environment, Platform, Device
See ionic info output
Ionic:

   ionic (Ionic CLI)             : 4.10.3 (/Users/alexryltsov/.nvm/versions/node/v10.14.2/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.4.0
   @angular-devkit/build-angular : 0.12.3
   @angular-devkit/schematics    : 7.2.3
   @angular/cli                  : 7.2.3
   @ionic/angular-toolkit        : 1.2.3

Capacitor:

   capacitor (Capacitor CLI) : 1.0.0-beta.24
   @capacitor/core           : 1.0.0-beta.24

Cordova:

   cordova (Cordova CLI) : 8.1.2<EMAIL_ADDRESS>   Cordova Platforms     : none
   Cordova Plugins       : no whitelisted plugins (0 plugins total)

System:

   Android SDK Tools : 26.1.1 (/Users/alexryltsov/Library/Android/sdk/)
   NodeJS            : v10.14.2 (/Users/alexryltsov/.nvm/versions/node/v10.14.2/bin/node)
   npm               : 6.5.0
   OS                : macOS Mojave
   Xcode             : Xcode 10.2.1 Build version 10E1001

Version information
See above
Checklist

[x] I searched for existing GitHub issues
[x] I updated all Cordova tooling to most recent version
[x] I included all the necessary information above

ping @brodybits

Linking to xpbrew/cordova-sqlite-storage#868, which is marked as a bug. I would like to resolve this problem on the cordova-sqlite-storage side. (I will probably need a few weeks to look into this one.)
The SYNTAX_ERR enumerator seems to have been defined on both plugins for several years. So I find it pretty strange that this problem would suddenly appear after multiple years. I wonder if it has anything to do with an Xcode update or any other framework updates?

https://github.com/apache/cordova-plugin-file/blob/5e12b5e9f63b12aef5198e9a72ac8d7b8e834442/src/ios/CDVFile.h#L26-L40
I don't even know why this is clashing with yours...

I solved it by simply removing and adding the plugin again.


I'm going to close this, for a couple of reasons:

We prefer that minor changes (including typos) are reported in #23, that way we can group them all together.
This isn't really a change that I want to make. This is simply the "server branding" and generally isn't that visible - in Vanilla the brand is also lowercase.
"Because it annoys you a little" is not really a reason that we accept changes like this. When proposing a change, please be prepared to back up why such a change is necessary. For things like this, feel free to ask us why we've chosen to do it in this way on Discord because there may be deeper reasons to consider (probably not the case here but changing the case of a string that is used as an ID can easily break things).

Thanks!


Update example.yml

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/nnsnodnb/firebase-app-distribution?version=dev:3d5cef4740ab1f7e90e6375c28ecbf33912d38e2

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/nnsnodnb/firebase-app-distribution?version=dev:f98455c1765842c9ccd5ffde670080d6e992795d

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/nnsnodnb/firebase-app-distribution?version=dev:f98455c1765842c9ccd5ffde670080d6e992795d


Avoid infinite loop when autocorrecting with Style/IfUnlessModifier

Style/IfUnlessModifier can autocorrect long lines which use an if/unless modifier to
if...end form. It can also autocorrect if...end form to modifier form if the body
is only a single line.
Obviously, there is the potential for an infinite autocorrect loop here. The cop tried
to avoid that by checking whether the if...end conditional would overflow the maximum
length of a line if converted to modifier form.
However, the check is based only on the size of the conditional code itself and not
other statements which may follow after end, like this:
if condition
  do_this
end; other_statement; yet_another

This (hideous) code could result from an autocorrect of something like this:
do_this if condition; other_statement; yet_another

So the cop still can and does cause infinite loops. A simple solution is to avoid
flagging long lines which use if/unless modifiers if there are other statements
following on the same line. Of course, such long lines are still a problem; but we can
allow Layout/LineLength to flag them rather than Style/IfUnlessModifier.

The build is currently failing.

Sorry about that.

Thanks!


Do you plan on keeping up with AdminLTE releases?

Just curious, since there is a new version over at almasaeed2010/AdminLTE/releases if you plan on updating your package to new releases of AdminLTE ?

Yes as soon as I have a moment ;-) I accept Pull request too ;-)

I might look into it this weekend then! :)

Done! It will be available soon on new 2.0 release or in dev-master now!


Configuration Tranformation Guide Missing

Hello everyone, I'm wondering why there is no page explaining how to generate a configuration transformation of the  Nlog.config
I'll explain the use case and I somehow made it work but I would like to know the proper way to do this:
I'm on a .Net (core) 5.0 Web App with Visual Studio 2019. Until today I used the Web.config only to transform the Nlog section, but I decided to get rid of the Web.config because it is not needed anymore, especially when you publish to a Linux Target the Web.config is not generated, neither taken into consideration.
So far it's years that the configuration of a .net core application it's done via AppSettings.json which is loaded / transformed at runtime but still no clear (or poor) documentation on how to configure Nlog with Appsettings. All the documentation keep referring it to the Nlog.config, event the latest 5.0, which in case of Visual Studio it's not transformed out of the box like the Web.config, so my question is how to transform the Nlog.config at build or publish time, it seems there is not a clear guideline to do it so and you need to run tools like SlowCheetah or Post Publish actions that are far to be optimal.
Besides that it seems that Nlog it's one of the last libraries using .config files as configuration source, on Microsoft website everything refers to json files since long time...
Any documentation about this? Many thanks

StackOverflow is probably a good place to start:
https://stackoverflow.com/questions/22438204/config-transformation-on-nlog-does-not-work
https://stackoverflow.com/questions/11633382/xml-file-transforms-using-one-click-publish-but-not-web-deploy
https://stackoverflow.com/questions/46443700/transform-a-file-other-than-web-config-replace-element
Also notice that you have NLog.config include other NLog.config so you can have a default NLog.config that is included by environment-specific NLog.config (That includes additional modifications).
You can also use GDC in the application to setup environment specific-values that can be referenced in the NLog.config

Hello @snakefoot I have already red the first article before posting this question and they solve it or putting the Nlog configuration in the Web.config or using Slowcheeta. The second it's of 8 years ago, I don't even know if .Net Core was available 8 years ago so I suppose it won't apply, third link same story, outdated.
The last solution of publishing various profiles in the Nlog.config means that I will need to publish settings for Test and Production environment together even if I'm publishing to Development environment... it doesn't seem a real solution... for sure not a secure one
I have already tried with true and putting the proper namespaces in the file, nothing works on Visual Studio 2019. So I suppose there isn't a clear way to do it so and I will need to stick to Slowcheeta or change logging library, it seems a little strange because Serilog perhaps supports it out of the box...

Yes that is the problem free open-source projects. They only improve when someone needs a feature bad enough.
Sent from my Sony Xperia
---- Vincenzo Pucarelli wrote ----
Hello @snakefoothttps://github.com/snakefoot I have already red the first article before posting this question and they solve it or putting the Nlog configuration in the Web.config or using Slowcheeta. The second it's of 8 years ago, I don't even know if .Net Core was available 8 years ago so I suppose it won't apply, third link same story, outdated.
The last solution of publishing various profiles in the Nlog.config means that I will need to publish settings for Test and Production environment together even if I'm publishing to Development environment... it doesn't seem a real solution... for sure not a secure one
I have already tried with true and putting the proper namespaces in the file, nothing works on Visual Studio 2019. So I suppose there isn't a clear way to do it so and I will need to stick to Slowcheeta or change logging library, it seems a little strange because Seriloghttps://github.com/serilog/serilog-settings-configuration perhaps supports it out of the box...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NLog/NLog/issues/4288#issuecomment-775864929, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXZ7HFCAVQYLYFZYOSGM7DS6EKPNANCNFSM4XJIUWQQ.

Anyway please come back if you find the secret sauce that make everything work. When using NetCore then Microsoft is selling the appsettings.json that also include override logic:
See also: https://github.com/NLog/NLog.Extensions.Logging/wiki/NLog-configuration-with-appsettings.json#environment-specific-configuration

Cool, this seems to be the solution, don't know why I didn't find it before, it should be linked directly in the main Nlog Wiki Page, it's pretty important to configure new applications, many thanks

@ollie10 Having NLog-config in the appsetting.json is still pretty "new", so have not gained that much traction.

I will be an "early adopter" so! Cheers! Besides that you can even have an nlog.json file and keep separated appsettings and other components, If I will have problems integrating it I'll come back, my main concern is that extensions will work with that too, I think so, I'm using Syslog which is pretty straightforward to configure, let's see if it works as expected

Please tell if you bump into something annoying, then we might be able to make the road less bumpy for future users. Also notice that all Wiki-pages are open, so you are welcome to improve the place that are lacking.

@snakefoot well I would say that this could be the first stopper... the packages is not available in nuget (anymore?)

https://www.nuget.org/packages/NLog.Extensions.Logging
Sent from my Sony Xperia
---- Vincenzo Pucarelli wrote ----
@snakefoothttps://github.com/snakefoot well I would say that this could be the first stopper... the packages is not availablehttps://www.nuget.org/packages/NLog.Extension.Logging in nuget (anymore?)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NLog/NLog/issues/4288#issuecomment-776135451, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXZ7HAYS3IJSP4ZQKBOVOLS6F3I7ANCNFSM4XJIUWQQ.

Ok thanks, in the github page it's written wrongly NLog.Extension.Logging without plural Extensions, I will give it a try

@ollie10 Thank you for noticing and updating the wiki. I have added some more examples of how to load NLog-config from appsettings.json


issue #180 - Add OnEventWrittenHandler extensibility, to DiagnosticSo…

Add OnEventWrittenHandler extensibility, to DiagnosticSourceTelemetryModule, similar to EventSourceTelemetryModule

Nicely done. LGTM.

@rggammon I forgot to ask you to update the CHANGELOG. Would you mind sending a separate PR for this?
Thank you for your contribution again!

no problem :)


error when created a new solution configuration with empty of "Copy settings from"

if i created a new solution configuration with empty of "Copy settings from", then publish the project, an error "Target ValidateMSBuildTollsVersion skipped. Previously built unsuccessfully.". Publish failed.
but success when i choose Debug or Release of "Copy settings from". so, why an option "Empty" existed if must to choose one of Debug and Release? if can choose the option item "Empty", where to complete this new configuration for success publish?

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

ID: 5fd27543-2a22-9a63-eefd-4cf5f786191c
Version Independent ID: b7aa9bfd-4e9a-42bf-9e20-44caf2141cd8
Content: How to: Create and edit configurations - Visual Studio
Content Source: docs/ide/how-to-create-and-edit-configurations.md
Product: visual-studio-dev15
GitHub Login: @gewarren
Microsoft Alias: gewarren

@StevenFlyover The product team isn't completely sure of your repro steps and has requested that you please report this issue using Report a Problem in Visual Studio. Initiate your report by choosing Help > Send Feedback > Report a Problem from Visual Studio.


--downloadSource doesn't feel natural

/kind bug
What versions of software are you using?
Output of odo version:
odo v1.2.0 (7f14dab)
Server: https://c101-e.us-east.containers.cloud.ibm.com:30409
Kubernetes: v1.16.2
How did you run odo exactly?
odo preference set experimental true
odo create openLiberty myapp --downloadSource

Expected behavior
After using odo for a few days, --downloadSource was the one option that I thought was a bit odd and didn't really fit. Yes, it is downloading source, but it's already downloading the devfile without this option, and as a user I'm thinking about the function (creating a starter or default project) more than how it's happening and the fact it implies files being downloaded.
Suggest we change the option to something like "--starter".

+1 for starter, I like that it's one word, it's concise and simple.
Other optional alternatives (that I'm less crazy about):

--starterProject
--templateProject
--downloadProject

Personally I like the following options that don't mention the word Project

--starter
--templateSource

Because IMO Porject is pretty confused terminology (OpenShift project -> "namespace" VS devfile project -> template) and we should be careful to use it especially all OpenShift user might still think Porject is Namespace related thing by default

+1 for --starter
It is simple and conveys the operation/function the user is performing.

I think --starter is nice and simple, but we need to look at the semantic meaning of projects in a devfile. Are they really considered a starter project? Or all the components of my application?

That's still being discussed (https://github.com/devfile/kubernetes-api/issues/42), but based on where it's at I think there will be a distinction between projects (part of the app, always cloned) and starters (optional resources to start with, copied in).

I like --starter, I found --downloadSource undiscoverable (I didn't guess its purpose even from the CLI help). Later, perhaps, --starter[=NAME | git-repo] if people want to select a specific starter, though starters should have as little code as possible, so maybe a well run stack will not have many of them

+1 for --starter. In the odo case, we'll probably only use starters (optional sample app) and we'll probably never use projects which ties to the setup of a given workspace to always clone the project(s).
Following the pattern for https://github.com/openshift/odo/issues/3000, --starter[=NAME] will allow user to specify a specific starter within a devfile.
If none specified by just using --starter, the first starter on the devfile will be used.
However, I don't think 'git-repo' fit into that command since the git repo info should be part of the starter definition in the devfile.

/area devfile

As specified in the odo terminology change proposal (https://docs.google.com/document/d/1PBZqactXlfSpeSwt7EkaVlnt43qsUV2eExwFXpYJahc/edit#heading=h.1y4eznz1mtnr), we'll rename the current --downloadSource option to --starter

This item should covers:

rename of the --starter in CLI
any required test change
doc changes

I can work on this
/assign


Fixes 'teams tab get' and 'teams app list' commands. Closes #2930

Fixes 'teams tab get' and 'teams app list' commands. Closes #2930

Awesome! Thank you @Jwaegebaert. We'll review it asap

Merged manually. Thank you! 👏


WIP: Bump up rust to 2021 edition

Ran cargo fix --editions which resulted in the addition of whitespace in identifiers due to reserved syntax of 2021. See: Reserving Syntax
Update individual Cargo.toml's to edition = "2021"
Add rust-version = "1.58" per comment from @fanatid https://github.com/project-serum/anchor/issues/1026#issuecomment-968885945
Cargo 'rust-version'  docs Note: This is actually optional according to the Cargo docs

Continues work by @smrnjeet222 on #1030

Tests are failing due to 'rust-version' requirement set to 1.58, moving to WIP and dropping to 1.56

This now passes with the rust-version set to '1.56'. The reason for the split failure at "1.58" is that the setup-anchor-cli is doesn't 'rustup' to nightly like test-core does.
Removing the WIP tag from this PR.


textract 1.6.5 has a non-standard dependency specifier extract-msg<=0.29.*

Describe the bug
DEPRECATION: textract 1.6.5 has a non-standard dependency specifier extract-msg<=0.29.*. pip 24.0 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of textract or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063
extract-msg<=0.29.*

I temporarily fixed this issue with
cd textract-1.6.5
sed -i requirements/python 's/\(<=.*\)\(\*\)/\10/'

duplicate of #476


Feature request: Creation of bug in Jira based on Github security alert for vulnerable dependencies

In 2018, Github introduced security alerts for vulnerable dependencies in repos ref https://help.github.com/articles/about-security-alerts-for-vulnerable-dependencies/
This is an important security feature and many organisation would like to:

Act immediately by evaluating the impact the vulnerability has on their solutions
Keep a paper trail on decision process for the vulnerability.

To achive this, many use Jira today. It would make sense to extend the Github to Jira extension to allow the creation of new bug issues of high criticality when a vulnerability alert is triggered for a given Github repo.
Since April 2018 there exist a webhook in Github for the vulnerability alerts which can be used for this new feature ref https://developer.github.com/changes/2018-04-24-preview-dependency-graph-and-vulnerability-hooks/

Hi @elsewhat. I'm from a team at Atlassian that is currently in the process of migrating the ownership over to us from GitHub. As a part of this, we're currently going through the backlog of issues and prs to see what can still be addressed and what should be closed.
I've flagged this with the 'to-triage' label so my team can discuss. We'll keep you posted on the status of this.

If you need inspiration we build a GitHub Action for mapping security alerts to Jira tickets: https://github.com/reload/github-security-jira

If you are looking at integrating code scanning alerts with Jira (both ways) - take a look at https://github.com/github/ghas-jira-integration

Hey @elsewhat. We merged support for GH's code scanning alert webhook back in April. Is this what you are after? https://github.com/atlassian/github-for-jira/pull/712

The code scanning alert webhook sounds great, thank you! You can consider
this issue closed.
On Thu, 25 Aug 2022, 08:33 Rachelle Rathbone, @.***>
wrote:

Hey @elsewhat https://github.com/elsewhat. We merged support for GH's
code scanning alert webhook back in April. Is this what you are after?
#712 https://github.com/atlassian/github-for-jira/pull/712
—
Reply to this email directly, view it on GitHub
https://github.com/atlassian/github-for-jira/issues/150#issuecomment-1226835256,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIUYJZJOESSGB4SI3DUDBDV24HVLANCNFSM4GHGIF6Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

Awesome!

Correct me if I'm wrong, @elsewhat, but wasn't this issue for vulnerable dependencies like Dependabot alerts? #712 is for code scanning like finding vulnerable code, no? I'm still hoping for Dependabot support.


Update all Python dependencies

Python requirements updated via inv packages.upgrade

@humitos I wonder if we should use this bot -- it's pretty handy: https://github.com/writethedocs/www/pull/788

@ericholscher looks like a good addition.
I'm reading it and checking its configuration. I need to check how it updates the packages since there are some that we don't have to upgrade automatically because of different reasons.
pur handles the <= properly for this cases and we are also using --skip when calling it.

There is an example without too much configuration at #5271 that breaks because of the things that I mentioned. Maybe there is a way to configure it for our needs.

I configured it at #5272 and I suppose that it should work as we need.


Add zlib-ng for more efficient compression at higher levels

fixes #119

Wrote a little benchmarking script (saving it here for reuse later):
#!/usr/bin/env python3
import itertools
import os
import sys
import time
from xopen import xopen

def main():
    testfile = sys.argv[1]
    out = sys.argv[2]
    for threads, compresslevel in itertools.product((0, 1, 4), range(1, 7)):
        start = time.time()
        block_size = 128 * 1024
        with open(testfile, "rb") as in_file:
            with xopen(
                out, "wb", compresslevel=compresslevel, threads=threads
            ) as out_file:
                while True:
                    block = in_file.read(block_size)
                    if block == b"":
                        break
                    out_file.write(block)

        stop = time.time()
        print(
            f"Compressed at level {compresslevel} with {threads} threads; "
            f"filesize: {os.stat(out).st_size}, "
            f"time: {stop -start} seconds"
        )

if __name__ == "__main__":
    main()

Current main:
Compressed at level 1 with 0 threads; filesize: 405313510, time: 3.3767712116241455 seconds
Compressed at level 2 with 0 threads; filesize: 404989250, time: 3.6654465198516846 seconds
Compressed at level 3 with 0 threads; filesize: 407253483, time: 7.312707424163818 seconds
Compressed at level 4 with 0 threads; filesize: 386930500, time: 25.895344734191895 seconds
Compressed at level 5 with 0 threads; filesize: 374207207, time: 46.744099140167236 seconds
Compressed at level 6 with 0 threads; filesize: 355347468, time:<PHONE_NUMBER>8959045 seconds
Compressed at level 1 with 1 threads; filesize: 405313274, time: 3.204677104949951 seconds
Compressed at level 2 with 1 threads; filesize: 404989061, time: 3.268627405166626 seconds
Compressed at level 3 with 1 threads; filesize: 407251397, time: 7.039590835571289 seconds
Compressed at level 4 with 1 threads; filesize: 387016236, time: 25.5415096282959 seconds
Compressed at level 5 with 1 threads; filesize: 374290891, time: 46.197908878326416 seconds
Compressed at level 6 with 1 threads; filesize: 355500797, time:<PHONE_NUMBER>1647949 seconds
Compressed at level 1 with 4 threads; filesize: 405313274, time: 3.209529399871826 seconds
Compressed at level 2 with 4 threads; filesize: 404989061, time: 3.3253917694091797 seconds
Compressed at level 3 with 4 threads; filesize: 407251397, time: 7.039556980133057 seconds
Compressed at level 4 with 4 threads; filesize: 387016236, time: 6.912431478500366 seconds
Compressed at level 5 with 4 threads; filesize: 374290891, time: 12.286827325820923 seconds
Compressed at level 6 with 4 threads; filesize: 355500797, time: 28.226975440979004 seconds

Results zlib-ng branch:
Compressed at level 1 with 0 threads; filesize: 405313510, time: 3.390442132949829 seconds
Compressed at level 2 with 0 threads; filesize: 404989250, time: 3.4523391723632812 seconds
Compressed at level 3 with 0 threads; filesize: 407253483, time: 7.442785978317261 seconds
Compressed at level 4 with 0 threads; filesize: 368802018, time: 21.94339346885681 seconds
Compressed at level 5 with 0 threads; filesize: 359170597, time: 28.51734709739685 seconds
Compressed at level 6 with 0 threads; filesize: 347379910, time: 47.41038107872009 seconds
Compressed at level 1 with 1 threads; filesize: 405313274, time: 3.212735652923584 seconds
Compressed at level 2 with 1 threads; filesize: 404989061, time: 3.277775287628174 seconds
Compressed at level 3 with 1 threads; filesize: 407251397, time: 7.07685923576355 seconds
Compressed at level 4 with 1 threads; filesize: 368802018, time: 20.918381452560425 seconds
Compressed at level 5 with 1 threads; filesize: 359170597, time: 27.791999101638794 seconds
Compressed at level 6 with 1 threads; filesize: 347379910, time: 44.957818031311035 seconds
Compressed at level 1 with 4 threads; filesize: 405313274, time: 3.197093963623047 seconds
Compressed at level 2 with 4 threads; filesize: 404989061, time: 3.2572927474975586 seconds
Compressed at level 3 with 4 threads; filesize: 407251397, time: 7.0963521003723145 seconds
Compressed at level 4 with 4 threads; filesize: 368802018, time: 20.83365035057068 seconds
Compressed at level 5 with 4 threads; filesize: 359170597, time: 27.362520933151245 seconds
Compressed at level 6 with 4 threads; filesize: 347379910, time: 44.91855430603027 seconds

Some observations:

zlib-ng obtains nice results at single-threaded and 0-threaded use cases especially regarding filesize.
not having multithreaded options for zlib-ng hurts a bit. Crabz should come next as suggested by #117 .
Igzip at level 3 is a bit redundant. It only works effectively when AVX-512 is available. This is not available usually, so I'd rather have zlib-ng run this level. This however is not possible with the current model, where we simply try if it works and use the first option that sticks.
Pigz at 4 threads pretty much crushes zlib-ng at 1 thread (as expected) so it might be better to prefer that when more threads are an option and crabz is not available? (Though unlikely, as it is available in conda and I also think that is the only reason people have pigz available.)

I think when adding crabz the code will be even more crowded. So a different model should be used in order to properly choose the correct tool for the job weighing threads, compression level etc. But that is for another PR.

This leaves a few holes in the test suite as what willl happen when zlib-ng is not installed is not properly tested. I will address these in a coming PR where I will refactor _open_gz a bit as it is currently getting a bit too overcomplicated.
If you prefer, I can also do it as part of this PR.


propose, nodejs compatibility

Hi @rvagg
Not sure you really want this, please let me know, i ll make a fork then.
It replaces your tsml module by underscore.template module.
By running it againt its repository, i found sometimes commit.summary was not set.
I fixed that dirtily, i believe this way in a way it won t break any es6 things i m not aware.
jshint did not complain anything here.

const should be available everywhere fwiw
a couple of style things I'd like fixed up before I properly review, will comment inline on those

hope that works, i also fine tuned a little bit

Hi,
i made more significant changes in a separate branch, here
https://github.com/maboiteaspam/changelog-maker/tree/better-project-id-detection
See a relevant commit message here for an overview of the changes
https://github.com/maboiteaspam/changelog-maker/commit/196426be10541b829112fcb388fd624edff53491
Do i merge that into this ?

I actually quite like the changes you made to detect the default package, I've been wondering how best to achieve that, I can live with debug too. Happy to merge but I'd appreciate some more work to match style, I know it's quirky but it's my quirky.

i.e. happy to have those additional changes you've made, once we get the style nits right then I'll add you as a collaborator here

Hi,
it s fine to be demanding about the code style.
It s just i see now the jshint config does not seem to be inline with the comments you made.
Are you standard (feross/standard) user ? Or semi-standard ?
Please let me know i'll put that into the npm run lint script command.

I checked this source code against standard / semi-standard. None of them really fit the style in this repository. It s fine to me, i like their initiative, not their code style.
Then i checked my words and the jshint i have here would not catch semi colons. Did not try to tune its config, instead i gave a try to eslint, because i prefer its output output, with the help of https://github.com/valorkin/eslint-rules-mapper it was real quick.
I then adjusted the existing rules to pass the source code. It s bit unusual to proceed that way.
you can check the whole config,
here https://github.com/maboiteaspam/changelog-maker/blob/eslint/.eslintrc
I have put my specific adjustments to pass the lint into a specific commit here
https://github.com/maboiteaspam/changelog-maker/commit/83ae289ce090ae4e0a8d1e09df8f51ae6f627000
Let me know, at the end, my belief is that manual code style checking does not worth a cent. I d really prefer have one linter config to comply to.

so many errors running eslint with that .eslintrc, do I need to be using a pre-release version or something to make it happy?

only a few minor style nits and we can land this

Hope it s fine.

sorry to be a pain, but could you squash this all into a single commit please? there's a heap of noise here. If it's too difficult to squash with the rebased activity in the middle then perhaps submit a new PR with a single commit?

Agreed, i found also all those commits was not satisfying. Need to check how to do that.

opened #16, closing #12.


chore(master): release 1.2.1

:robot: I have created a release beep boop
1.2.1 (2022-08-18)
Bug Fixes

issue with releasing and bump deps (322db17)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/cobraz/xlsx-mxlookup/releases/tag/v1.2.1 :sunflower:


Implementing solution for issue #1340

Description of the problem
This PR is intended to implement a solution for issue #1340 which I raised previously. This PR adds the ability to create a custom tooltip to be displayed as a descriptive text for the column instead of just displaying the column name.
Description of Changes
This PR introduces a new variable tooltip of type kivy.properties.StringProperty to contain the descriptive text for the column. The column_data property is also expanded to contain a tuple of 4 items instead of 3 as before. The items are arrange in the form column_data = [ (column_name, column_size, column_tooltip, column_sort_function) ]
Screenshots of the solution

Code for testing new changes
from kivymd.app import MDApp
from kivymd.uix.datatables import MDDataTable
from kivy.metrics import dp

class TestApp(MDApp):
    def build (self):
        return MDDataTable(column_data = [("column 1",dp(30),"this is column one"), ("column2",dp(30),"this is column two")]

TestApp().run()

@ht-thomas OK, thanks for the PR. But please be careful! There are syntax errors in your changes.

@ht-thomas Your changes contain errors. Please, after applying the change, test the code with examples from the documentation...

I'm requesting for you to review my the PR again.

Your changes break the current API

Is it possible to work around it?

@ht-thomas It's just that your changes don't work with the very first example from the documentation for the MDDataTable widget.

I think it's because I introduced the tooltip argument to be the third argument where the sort function was supposed to be. What if I made it the last parameter? That would maintain the current API and also extend functionality.

@ht-thomas Any changes should not break the current API.

I've refactored the code to maintain the existing API

@ht-thomas
Your recent changes don't work with your sample code:
from kivymd.app import MDApp
from kivymd.uix.datatables import MDDataTable
from kivy.metrics import dp

class TestApp(MDApp):
    def build(self):
        return MDDataTable(
            column_data=[
                ("column 1", dp(30), "this is column one"),
                ("column2", dp(30), "this is column two"),
            ]
        )

TestApp().run()

The sample code is now nullified. We can use already the existing examples in the kivymd documentation.

@ht-thomas I don't understand. Then what is the essence of your changes? I don't see how to use it...

The New example will be like this,
from kivymd.app import MDApp
from kivymd.uix.datatables import MDDataTable
from kivy.metrics import dp

class TestApp (MDApp):
    def build (self):
        return MDDataTable(column_data = [("Name",dp(30),None,"Name of client"), ("Employment",dp(30),lambda *sort_args:sort_function(*sort_args),"Employment status of client")]

TestApp().run()

A simple example usage could be like this. I've not written sort_function in the example, this is just an example of how to use it.

@ht-thomas OK I will merge this when I finish some started changes.

Alright, thank you @HeaTTheatR