All extension network traffic breaks when system proxy settings are changed

Does this issue occur when all extensions are disabled?: No -- this is a bug that affects all extensions

VS Code Version: 1.75.1
OS Version: macOS Monterey 12.5.1

Steps to Reproduce:

Close VSCode
Set a system-level proxy (I do this by running Proxyman)
Start VSCode -- note, all VSCode extension traffic correctly goes through the proxy
Change the proxy settings (in this case, close Proxyman)
All VSCode extension traffic stops working.  It looks like all traffic continues to be routed through the proxy even though the proxy is no longer active.

This appears to affect all extensions.  I see this behaviour with our own extension (using node-fetch) but also in the GitHub extension.  The error I see in the GitHub extension is Fetching pull requests failed: request to https://api.github.com/repos/matthewjamesadam/vscode/pulls?per_page=20&page=1 failed, reason: connect ECONNREFUSED <IP_ADDRESS>:9090.

Note that built-in VSCode network traffic continues to work -- in the extension sidebar I can search the marketplace, for instance.  So this seems to be something particular to extension network traffic.
I am willing to look into fixing this issue if I could get a pointer as to where in the code to look to fix it.  Thanks!

@matthewjamesadam thanks for creating this issue. Just to clarify is this something new that started happening or was it always like this?
fyi @bpasero for potential sandbox work that might affect this as mentioned in standup

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

@isidorn I do not think this is a new issue -- I believe I've seen this in the past
@bpasero confirmed, this occurs the same in Insider builds

How does it work, this proxy configuration sharing to the extension host process? We've just run into the limitation of nodejs that is using a fixed set of root certificates, instead of respecting the host OS certificate store.
I've been reading the source a bit, and it looks like vscode patches the https & http agent code of node, but I cannot see how we could respect those settings inside of an extension.

@matthewjamesadam Are you changing the system proxy setting while VS Code is open? Does restarting VS Code fix the issue? We cache the proxy (https://github.com/microsoft/vscode-proxy-agent/blob/49c0f39c327ce408ce69247a3db10a2b313d44a2/src/index.ts#L69) for each URL to avoid going all the way to the main process to look up the proxy each time. (We are using an Electron API to do the lookup.)
@DavyLandman We load the root certificates from the OS (https://github.com/microsoft/vscode-proxy-agent/blob/49c0f39c327ce408ce69247a3db10a2b313d44a2/src/index.ts#L401).

@chrmarti does this loading of the root certificates also happen for the extension host? Since we've been running into that. Although we are using node-fetch instead of plain http calls. I'll investigate further, and open an issue if needed.

@DavyLandman Yes, we indeed patch the http and https built-in Node modules in the extension host. node-fetch probably uses these. Separate issue appreciated if this doesn't work as expected. Thanks.

@chrmarti just to report back, indeed, that works, we'll have to dive deeper on why some users with corporate firewalls are having issues, but this just works as intended. sorry @matthewjamesadam to high-jack the issue.

@matthewjamesadam Are you changing the system proxy setting while VS Code is open? Does restarting VS Code fix the issue? We cache the proxy (https://github.com/microsoft/vscode-proxy-agent/blob/49c0f39c327ce408ce69247a3db10a2b313d44a2/src/index.ts#L69) for each URL to avoid going all the way to the main process to look up the proxy each time. (We are using an Electron API to do the lookup.)

@chrmarti in effect, yes, the system proxy settings are changing while VSCode is open.  I am not manually changing the settings myself, but many tools (VPNs, network monitoring tools like Proxyman) work by changing the system proxy settings.  For instance, opening Proxyman changes the system proxy settings to redirect network traffic to itself (acting as a MITM effectively), while closing it reverts the proxy settings.  I use OpenVPN regularly, and whenever I enable or disable the VPN (which I do somewhat often), under the hood it is changing my system proxy settings.
Whenever I take any of these actions while VSCode is open, all extensions that rely on network resources effectively stop working.  Caching the proxy is probably what is causing this.  I am not sure if there is a way VSCode can detect a change to the system proxy settings and clear the proxy cache.  I would be happy to look into this if you gave me a few pointers.

Just to give a little more context: this can happen even without explicit user actions.  OpenVPN will sometimes change its proxy settings when my laptop is closed or opened -- the end result is that sometimes when I open my laptop in the morning, VSCode's extensions are no longer working.


Replacing header and footer navigation

This PR is related to the issue: https://github.com/src-d/backlog/issues/1404
I replaced the header and footer navigation to fit the new landing page.

Signed-off-by: Zuri Negrín<EMAIL_ADDRESS>

Content LGTM

Ready at staging:
https://landing-staging.srcd.run

Fixed the :hover color on links and added anchors to the enterprise section so it points to the small sub-sections.

Hi; Is there any new commit here? I found no new one.

@vcoisne I just pushed the requested changes. I am just missing the Newsletter one as I wasn't sure of where to point it. Please let me know so I can add it properly. Thank you!

I fixed the get-started links to point them to the individual tab anchors

Thank you @znegrin.
Please make the following changes to the header:

Add "Products" and "solutions" to header Nav (Why sourced, Products, Solutions, Community, Ressources, Company)
Solutions linking directly to the 4 new solution pages (See content in mocqups)
Rename Features page - source{d} Community Edition and move it under "Products"
Move source{d} Enterprise under Products as well
List “newsletter” under “resources”

For the footer:

Rename Features page - source{d} Community Edition and move it under "Products"
Move source{d} Enterprise under Products as well

Hi @vcoisne,
I was trying to find the new solution pages but I didn't find any mockup related to them. Can you please let me know where can I find them so I can design those. Once the pages are ready I will replace the navigation as if I do it now those links won't have a destination yet.
Thank you!

Hi @vcoisne,
As requested on #409 I changed the IT Modernization links on header and footer.

@znegrin the solutions page are still work in progress for now. I should have them ready by tomorrow.

If I understood properly @vcoisne requirements, it would be better if we perform the possible changes asap, and leave the new sections being developed for new PR, so the merged menu could be:

Why source{d} (no changes)
Products (new item)

source{d} Community Edition (links to https://landing-staging.srcd.run/features)
source{d} Enterprise (link to https://landing-staging.srcd.run/enterprise)

~Solutions~ (will contain 4 new pages, but not yet ready, better in a PR with that 4 new pages)
Community (reordered, but same content)
Resources (reordered, and new item inside)

add newsletter

Company (no changes)

@vcoisne Need clarifications for:

what's the url for newsletter? maybe http://go.sourced.tech/newsletter?
since current features will be renamed as source{d} Community Edition, should its current link (https://landing-staging.srcd.run/features) be changed? If so, that old link is already being used in the Welcome dashboard of source{d} CE, being PRed by https://github.com/src-d/sourced-ui/pull/164/files, so I think @marnovo should be noticed about the final URL for that page.

Thank you for the great summary of the requirements @dpordomingo
Yes that's the right URL for the newsletter
Yes the URL should be changed from https://landing-staging.srcd.run/features to https://landing-staging.srcd.run/community-edition and updated in the product cc @marnovo @znegrin

URL should be updated as follow:
https://sourced.tech/features/ -> https://sourced.tech/products/community-edition
https://sourced.tech/enterprise/ -> https://sourced.tech/product/enterprise-edition
URL for the solutions pages:
https://sourced.tech/solutions/it-modernization-and-compliance
https://sourced.tech/solutions/devops-cloud-native-transformation
https://sourced.tech/solutions/engineering-effectiveness-efficiency
https://sourced.tech/solutions/talent-assesment-and-management

I updated the header and footer with all the changes. Will change now the url on the proper Enterprise and Community edition pages

already in staging https://landing-staging.srcd.run
should we merge @vcoisne ?

I uploaded the changes requested on #424


When using reactive extension for communication between views, IBOutlet variable is not yet loaded

I have a login view controller which has following extension for communication.
extension Reactive where Base: LoginViewController {
    var signupButtonTapped: ControlEvent<String> {
        let source = base.signupButton?.rx.tap
        return ControlEvent(events: source)
    }
}

On the ViewController which is main view, it has following code snippet.
        loginView?.rx.signupButtonTapped
            .debug()
            .map { Reactor.Action.signup }
            .bind(to: reactor.action)
            .disposed(by: self.disposeBag)

It is supposed to be called when the sign up button in the login view tapped, so that users can proceed to sign up process.
But as soon as app starts, it runs through above codes then it crashes at unwrapping signupButton which is nil.
Any ideas or suggestions are highly appreciated!

I solved this by applying coordinate pattern by using RxFlow.


Window.scroll is broken by material

Bug, feature request, or proposal:
window.scroll() does not work on pages with material
What is the expected behavior?
window.scroll(0, 1500) in browser console should scroll the page
What is the current behavior?
no scroll occurs
What are the steps to reproduce?
run window.scroll(0, 1500) on https://v5.material.angular.io/ (or v6)
What is the use-case or motivation for changing an existing behavior?
scroll is useful
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular material - 5.2.4, 6
Chrome 66, Windows 7
Firefox 59, Windows 7
Is there anything else we should know?
assuming angular docs are written in angular, it's working in angular (tried using window.scroll here and it worked https://angular.io/api/common/http/HttpClient)
This used to work, but I'm not sure when. I don't think it has to do with v6
Printing the value of window.scroll shows a function with native code, so it doesn't appear to be re-assigned. I tried assigning a proxy function to print out when window scroll is called to see if it was being cancelled out or something, but no calls were made except the ones from myself.
There's no errors in the console, it just fails silently.

That's because window.scroll will only scroll if the scrollable content is the body or html, but in our case the content is inside the mat-sidenav-content. This one will work:
document.querySelector('mat-sidenav-content').scrollTop = 1500;

Closing since this is an implementation detail of our docs site, rather than an issue with Material.

Ah okay, thanks. This is ultimately related to the fact that by default angular elements have size 0x0. If you set all elements to display: block, then it would still work normally. I had recently converted my content to all be inside mat-sidenav-content, which explains it.

@narthur157  can you find there is the doc that @crisbeto  mentioned?


graph client intergration

this PR contains:

Microsoft Graph Client Authentication
Calls for different services from the Microsoft Graph

email
profile photo

Approving this since expectation is graphClient error scenarios on auth or API failures will be addressed here - or as part of the next PR, correct?

Approving this since expectation is graphClient error scenarios on auth or API failures will be addressed here - or as part of the next PR, correct?

will address the above comments here! and can see into some edge cases in subsequent PR


Doom will not work

When I open Doom, it just says "id software," and nothing happens.

weird, will try to fix today

weird, will try to fix today

It's still just leading to a 404 for me


feat: Indexing progress indicator

Codecov Report

Merging #9 (7f1ae17) into main (3b67cbb) will decrease coverage by 2.14%.
The diff coverage is 31.03%.

@@             Coverage Diff              @@
##               main       #9      +/-   ##
============================================
- Coverage     82.04%   79.90%   -2.15%
- Complexity      912      924      +12
============================================
  Files            44       45       +1
  Lines          2295     2344      +49
============================================
- Hits           1883     1873      -10
- Misses          412      471      +59

Impacted Files
Coverage Δ

src/Client/Window.php
29.41% <0.00%> (-42.02%)
:arrow_down:

src/Client/WorkDoneProgress.php
0.00% <0.00%> (ø)

src/Indexer.php
58.88% <64.28%> (+0.35%)
:arrow_up:

src/LanguageServer.php
78.44% <100.00%> (+1.17%)
:arrow_up:

src/FilesFinder/FileSystemFilesFinder.php
66.66% <0.00%> (-33.34%)
:arrow_down:

src/DefinitionResolver.php
85.53% <0.00%> (-2.87%)
:arrow_down:


Deposit model and export cleanup

The PubMed-related members of the deposit service data model are removed
and no longer exported.  The DOI that is exported is now always in "raw"
form, with no leading URI scheme or host.

Hi @Trumbore, please rebase this against the tip of master, thanks!

I can't get a clean rebase, will create a new PR.


KAFKA-2536: topics tool should allow users to alter topic configuration

This is a minimal revert of some backward incompatible changes made in KAFKA-2205, with the addition of the deprecation logging message.

I am not super happy about:

Code duplication with ConfigCommand
That the same option is called --delete-config here and --deleted-config in ConfigCommand.

However, since the point is to simply return code that was removed in order to remove it later... I'll commit as is.
Can you file 2 JIRAs:

For ConfigCommand to check if the parameter can be renamed to --delete-config in order to reduce confusion? We didn't release yet, so hopefully it is not too late.
For 0.9.1 to remove the deprecated configs

@gwenshap I have created those Jiras:

KAFKA-2650: Change ConfigCommand --deleted-config option to align with TopicCommand
KAFKA-2651: Remove deprecated config alteration from TopicCommand in <IP_ADDRESS>

I also created pull request #308 for KAFKA-2650.

Committed KAFKA-2650, and I think this will work ok as an interim state.
LGTM.


Update urls to point to awesome-print organization

Quite a few places, still pointed to the old repository making them invalid. This commit just updates those urls to point to the urls underneath the awesome-print organization github account.
One of the things that this fixes is the Travis status which currently is showing up as "invalid".
Commit message:
Before this commit a number or our urls were out of date which
lead to problems such as our build status on Travis being invalid
and people being asked to clone from an old version of the
repository.
Thanks to Michael Dvorkin for his many years of incredible work
on this project and for creating this organization so that the
project could live on with the help of others.

Merging as it's a trivial change which should immediately fix our build status icon.


Request to be a maintainer

Hello,
I'm working on plugin for AdobeXD, and I have a bunch of reusable helpers for community, that I think should be landed here. I saw that some developers making their own packages and publish it from personal account, it's okay but it's not the best.
I'd like to make this as centralized toolkit for all contributions. In addition, I had an experience on working with stuff like this for Figma.
Here's my roadmap, and that's why I need to be a maintaier, to be able to change repo settings:

Configure autopublish to NPM with GitHub Actions #4
Migrate to Typescript to have type definitions #5
Configure autogenerating docs based on TS definitions #6

@kerrishotts @krisnye @ashryanbeats @bantya
I don't know who is the right person for this issue, so ping all contributors 😄

Hi Alexandr, thanks for reaching out about this! I’d love to learn more about your ideas for making this repo more of a centralized resource.
Adobe is on a company-wide holiday today. Let’s talk about it next week?

@ashryanbeats Okay sure, we can schedule call:
https://calendly.com/alexandrtovmach

Ping

@ashryanbeats friendly reminder

Thanks Alexandr. We're moving a little slowly here as we're in the lead-up to bringing this API platform (UXP) to Photoshop:
https://medium.com/adobetech/photoshop-extensibility-enters-a-new-era-soon-how-to-get-involved-early-61ac723b842e
I'll try to get back to you soon.

I see, I'm also looking for UXP release))

Nice! Have you already filled out the interest survey in that blog post?

I'm already a part of Adobe Prerelease Program, thanks for asking 😉


update template during tracking

Is there are reason why we don't update the template as we're tracking? Put another way, why tracker.init(...) is only called in the first frame in demo.py? I feel it'd get better results for tracking over long periods of time, or for slowly changing objects (e.g. people moving etc.).

Good question! However we find either use moving average to update template frame or reinitialize the template frame could not improve the tracking result.

Interesting. Is that on datasets with deformable objects over long periods (e.g. people walking)? Moving average is also a clever idea. I'd be interested to see the code added if you already have it and it's easy.


confine_to_keys not working on 2.0.0

Hi, after moving code to lookup_http, confine_to_keys parameter isn't working.

Thanks for raising this issue, I'll look into this shortly and get back to you.


Improve unrecognized error parsing

In this PR:

Improved unrecognized error message parsing in both clients - included status code and serialized response body to generated error message.
Added unit tests to ensure correct behavior

/azp run


New UI for community Partners Page and WebXDAO icon clickable

Related Issue

Updated the UI of Community Partners Page
Update the UI for Community Partners Page

Describe the changes you've made
I made update the background color of partners grid and I added Hover effect. and i made the WebXDAO clickable and it moves back to the homepage
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update.
[ ] This change requires a documentation update

How Has This Been Tested?
with #26 m run dev
Checklist

[ ] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented on my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)

Original
Updated

original screenshot
updated screenshot

Code of Conduct

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

this a proof of what i have done deployment soon
https://user-images.githubusercontent.com/56732809/193262567-52c03f72-45eb-4a1b-8da3-73a3c3dd13e5.mp4

@krshkodes I need help deploying to github

I will fix it

Related Issue

Updated the UI of Community Partners Page
Update the UI for Community Partners Page

Describe the changes you've made
I made update the background color of partners grid and I added Hover effect. and i made the WebXDAO clickable and it moves back to the homepage
Type of change
What sort of change have you made:

[ ]  Bug fix (non-breaking change which fixes an issue)
[x]  New feature (non-breaking change which adds functionality)
[x]  Code style update (formatting, local variables)
[ ]  Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ]  Documentation update.
[ ]  This change requires a documentation update

How Has This Been Tested?
with #26 m run dev
Checklist

[ ]  My code follows the guidelines of this project.
[x]  I have performed a self-review of my own code.
[ ]  I have commented on my code, particularly wherever it was hard to understand.
[ ]  I have made corresponding changes to the documentation.
[ ]  My changes generate no new warnings.
[x]  I have added tests that prove my fix is effective or that my feature works.
[ ]  Any dependent changes have been merged and published in downstream modules.

Screenshots (if applicable)
Original	Updated
original screenshot	updated screenshot
Code of Conduct

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

here's a link to the Link to the repo


powershell: add DOTNET_CLI_TELEMETRY_OPTOUT=1 to pwsh wrapper

Cc @yrashk (PowerShell maintainer)
Describe the bug
Powershell uses telemetry unless explicitly told not to do it.
In addition to its own environment variable POWERSHELL_TELEMETRY_OPTOUT (already set in the wrapper), it should require another one to disable telemetry from the underlying .NET platform, i.e. DOTNET_CLI_TELEMETRY_OPTOUT should be set to 1
To Reproduce
Steps to reproduce the behavior:

install powershell with nix-env -iA unstable.powershell (assumes you have the unstable channel installed)
launch it with pwsh
Run [System.Environment]::GetEnvironmentVariable('DOTNET_CLI_TELEMETRY_OPTOUT') and verify that it's not set (i.e. no output)

Expected behavior
DOTNET_CLI_TELEMETRY_OPTOUT should be set to 1:
PS /home/user> [System.Environment]::GetEnvironmentVariable('DOTNET_CLI_TELEMETRY_OPTOUT')
1

Additional context
Example of PowerShell's own CI config that disables telemetry on Linux:
https://github.com/PowerShell/PowerShell/blob/4ff9924cbf0d2a64106f04c19137bbb020d844c7/.vsts-ci/linux.yml#L34
This should be fairly easy to change here:
https://github.com/NixOS/nixpkgs/blob/50c265ef0ec2aa6e0b42980d61112c466412ea2b/pkgs/shells/powershell/default.nix#L34
Metadata

system: "x86_64-linux"
host os: Linux 4.19.80-hardened, NixOS, 19.03.173669.27f48796194 (Koi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.1
channels(root): "nixos-19.03.173669.27f48796194"
channels(user): unstable-20.03pre203172.0ee0489d42e"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: powershell
# a list of nixos modules affected by the problem
module:

@yrashk


Condition on Ability not working

I am using nest-casl library to implement authorization on my GraphQL API.
I set the permission as follows:
  // customers.permission.ts
  customer({ user, can }) {
    can(Actions.read, Customer, { id: user.id });
  }

And used the guard and ability as follows:
  // customers.service.ts
  @UseGuards(GqlAuthGuard, AccessGuard)
  @UseAbility(Actions.read, Customer)
  @Query(() => Customer, { name: 'getCustomerById' })
  async getCustomerById(
    @Args('id')
    id: string,
  ) {
    return await this.customersService.getCustomerById(id);
  }

But unfortunately, my customer can query other customers by their ID. This should not be happening, Can anyone help, please?

you need to  pull subject somehow, check https://github.com/getjerry/nest-casl#subject-hook for details


Results

Thank you very much for sharing the code. We used the code you shared to train the model, but the prediction results we got were very poor, just like randomly generated results. Please tell me what causes this.

I found that there seems to be a problem with the test code and the newly trained model cannot be added. Please tell me how to solve it.

Hi , hope you will be fine.
Did you get the improved results ?
Also can you share your GPU memory space that was used during the experiment?
I will be replicating same approach to fine tune SAM on custom medical dataset but my available memory space is only 8GB.
Thanks!

Hi , I trained the model as the writer says , I also got the prediction results very poor , did you solve this problem?
Thanks!

I got the Testing performance : mean_dice : 0.023857 mean_hd95 : 254.548986

我发现测试代码似乎有问题，无法添加新训练的模型。请告诉我如何解决。
请问你解决这个问题了吗


Can we please get an updated version of this for TF2?

There are multiple sections of this guide that are now out of date unfortunatly :( The work around of using the legacy train.py in 1.9 does not work in 2.0 and has no work around unfortunatly.

As posted multiple times here and elsewhere, the Tensorflow maintainers have not yet released a compatible version of the object detection api for TF 2.0.
Most notable reason: TF 1.x has a module called "contrib" that no longer exists in 2.0. Until they can work around that and any other barriers, you will need to use TF 1.x

The Tensorflow maintainers have released the compatible version of the object detection api for TF 2.0. If we get an updated version of this for TF 2.0, It will be really great. Thank you

Hi, everybody, I am new to tensorflow..
I use the tensorflow-1.13,  cudatoolkit , cudnn,  and models-r1.13.0.zip. I follow the tutorial , use the frozen inference graph from this Dropbox link https://www.dropbox.com/s/va9ob6wcucusse1/inference_graph.zip?dl=0
I can run the Object_detection_video.py demo successfully....
but then I try to train....
both train.py or model_main.py ,,,,
It can init ok,,,,,,   but it always halt after start a while.
#######use model_main.py, halts at step =0.
INFO:tensorflow:loss = 3.8967483, step = 0
I0805 10:27:55.944391 19564 basic_session_run_hooks.py:262] loss = 3.8967483, step = 0
////////////////////////////////////////////////////////////////////////////
#######use train.py, halts at step >=90 , Saving checkpoint
I0805 10:50:53.543954 18848 learning.py:507] global step 97: loss = 2.5882 (1.244 sec/step)
INFO:tensorflow:global step 98: loss = 2.5304 (1.294 sec/step)
I0805 10:50:54.840963 18848 learning.py:507] global step 98: loss = 2.5304 (1.294 sec/step)
INFO:tensorflow:global step 99: loss = 2.0427 (0.907 sec/step)
I0805 10:50:55.750564 18848 learning.py:507] global step 99: loss = 2.0427 (0.907 sec/step)
INFO:tensorflow:Saving checkpoint to path training/model.ckpt
I0805 10:58:56.402550  2836 supervisor.py:1117] Saving checkpoint to path training/model.ckpt

after halt ,, the anaconda prompt no longer out put any information..
and gpu usage drop to 0%,,, but cpu usage is above 50%, ram  87%
I try to let it run for 10 hours after halt .  gpu is always 0%,,  cpu is always above 50% ,ram 87%...
but there is no result come out,,,,,
May I should wait for a long time? or it is something errors?
///////////////////////////////////////////////////////////////////////////////////////////////////
for my laptop,
Nitro AN515-52
Core i5-8300H @ 2.30GHz  8 GB RAM
Nvidia GeForce GTX 1050 ( 4 GB )

Hi @wu-jin-liang there is some error. Your code should not halt at all.. Check if your RAM or VRAM is getting exhausted


Add POC dbt tests to mailchimp sync [DE-164]

This PR adds a very basic set of dbt tests to the models and sources in the mailchimp sync. I've also added the dbt-expectations package which opens up the library of tests available to us significantly.

unique checks on ID are passing for the models in 0_ctes and 1_cte_base, but want to verify that this is likely not the case for other sources? (because we haven't deduped on the surrogate key at this point in the pipeline)

This is really cool! Does this mean that dbt tests have to be done at the column level @jackwelty? i can see that getting out of hand with all the tables/columns we currently have on this repo 😓

Short answer is yes 😢. It depends on what we want to test, tests can be configured at both the table and the column level. A table level test would be like "Does this table have greater than X rows?", whereas most of the column level tests configured here are around uniqueness and not null-ness. There's a dbt code gen package that will help us write the schema files quicker, I can dig around to see if there is code to auto-generate tests.

There's a dbt code gen package that will help us write the schema files quicker, I can dig around to see if there is code to auto-generate tests.

ooooo 👀 This tantalizes me greatly - I'll write up a ticket for you to look into dbt code generation strats @jackwelty (not necessarily to prioritize, but I don't want us to forget this ambition)


🚀 Introduce Dependabot Auto Merge

We are using a simple workflow to auto merge the Pull Requests made by Dependabot also it only makes PR's for minor and patch release. I want you to close previously opened Dependabot PR's so it won't conflict or anything

I think we have to first update all the dependencies manually and clean up the code, so I'm going to close this for now and let's reopen this after that's done?
Really appreciate your contribution, truly! Will try and get to this ASAP!


feat: Simplify and merge OIDC configurations

As the title says, this combines 3 classes that handled the OIDC configuration into one. One of them (the policy handler) did not much more than just adding a single line. The other two have been simplified by moving all static config values to the components.js config. Besides that I also removed duplicate values between the two and removed some features that were enabled but not used internally (device auth, account selection, pairwise subject types). These can always be re-enabled in the future should we add support for them.
I didn't move the components.js config to a root folder so it's easy configurable. Mostly because I don't think there's much demand for easily configuring those values and the structure might still change in the future.
The one thing I'm not sure of is that currently the server is configure to have the "webid" and "client_id" claims_supported values in the scope "webid". From going through the examples in the solid oidc spec I think this might be wrong and only the "webid" value should be there, and in the "oidc" scope so that might still change since I'm not completely sure of that one.
As a bonus I now sort of understand what most fields do in the config 😅

The one thing I'm not sure of is that currently the server is configure to have the "webid" and "client_id" claims_supported values in the scope "webid". From going through the examples in the solid oidc spec I think this might be wrong and only the "webid" value should be there, and in the "oidc" scope so that might still change since I'm not completely sure of that one.

Could this be https://github.com/solid/community-server/issues/718 ?

Could this be #718 ?

The issue here about it is only a small config part. I'm not even sure how important that scope part is, but we probably want it correct.
#718 is about actually implementing support for the value that should be found in that field.


Enable cross-chain authorizers

Closes #1284.
The core logic is in initialize-provider.ts and the coingecko-cross-chain-authorizer README has an explanation of how this user-runnable integration works.

Tested on localhost (same way as e2e tests), looks fine.

Thanks. I make some fixes to the cross-chain aspects of the integration and confirmed it's now working on Sepolia (same chain) with a polygon mumbai cross-chain authorizer (in addition to localhost E2E via CI).


scammer

I was scamed by this group CRYPTO TON on Telegram the adress is this:
UQA9Mma_HcXepPY9fAmcG4TijWfDNlB_r8VDdJwUfkTFFOjz
They asked me to conect my wallet to (NOT) notcoin.org for 950K Dogs and afther that i lost all my TONs and zero Dogs cons.
They also removed the "fake aidrop scam post" from the group. But i have screenshots.
I have reported them to Telegram and TON support but no answer ofcourse.

Me has estafado

yy

Rata

Ok I can help you if you wish to recover your lost coins text me on WhatsApp now +1(909) 516-6538


docker version

suggest use same docker version with okd.
now the okd use docker 1.13.x, but when run
./install.sh
seem would install the newest docker .

I found use docker compose,


demo: Add Event Timer Bot (Hacktoberfest Demo)

Event Timer with Copilot Bot using Next.js
In this project, I developed an Event Countdown Timer with Copilot Bot integration using React for the frontend, Tailwind CSS for styling, and the CopilotKit for interactive guidance and suggestions.

Event Timer: Users can add an event with a specific target date and time. The app displays a countdown for the event, and users can manage multiple events by adding or removing them from the list.
Copilot Bot Integration: The app is integrated with Copilot Bot to assist users with instructions on how to set timers, offering help for timer creation in a user-friendly way.

2. Name of Issue/Topic
3. Technologies Being Used
List the technologies and frameworks you used (e.g., CopilotKit, Next.js)

Next.js
Tailwind CSS
CopilotKit

4. GitHub Project Link
GitHub Repo Link:
https://github.com/prathamesh424/EventCounter--Copilotkit
5 bonus points

If your app is live, include the link here:
Live app

6. Screenshot

7. Who Are You?
Please list your GitHub and Twitter handles if you feel comfortable doing so.

prathamesh424 on github
sanket on X

5 Extra Bonus Points
Link to any bonus activities you did such as solving GitHub Issues or posting to Twitter, Dev.to, Medium, etc related to your project and CopilotKit.

A dev.to blog link - Link
Tweet link - Link

#issue #787

@quest-bot loot #787

@NathanTarbert sir please  check out  .

@prathamesh424, did you want to repoen this PR?
I can merge it if you still want to submit it.


Added multiply function, test and init update

Closes issue #2

New comit updated pull request so tests now pass


Automated Latest Dependency Updates

This is an auto-generated PR with dependency updates. Please do not delete the dep-update branch because it's needed by the auto-dependency bot.

@dsherry looks like the access token PR worked!


Make default template methods public.

This makes these methods available to extensions.

Any reason the PR is waiting ?

Looking forward this PR to be merged !

Awesome thank you for the merge @reinink :+1: !
Ans a version bump would be greatly welcome ;-)

@jails You bet, it's coming! :)


chore(*): add a Git .mailmap with my new name

In this way my past contributions are mapped correctly.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Chore.
What is the current behavior? (You can also link to an open issue here)
Git thinks I'm 2 people.
What is the new behavior (if this is a feature change)?
I'm one person again.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
Tests for the changes have been added (for bug fixes / features)
Docs have been added / updated (for bug fixes / features)

Other information:
Output of git shortlog -nse | head -25 after this PR (I see we could use more .mailmap entries, there are lots of duplicates):
   931	Igor Minar<EMAIL_ADDRESS>   692	Misko Hevery<EMAIL_ADDRESS>   677	Peter Bacon Darwin<EMAIL_ADDRESS>   503	Igor Minar<EMAIL_ADDRESS>   364	Vojta Jina<EMAIL_ADDRESS>   364	Matias Niemelä<EMAIL_ADDRESS>   259	Martin Staffa<EMAIL_ADDRESS>   196	Caitlin Potter<EMAIL_ADDRESS>   192	Brian Ford<EMAIL_ADDRESS>   169	Georgios Kalpakas<EMAIL_ADDRESS>   140	Georgios Kalpakas<EMAIL_ADDRESS>   127	Pete Bacon Darwin<EMAIL_ADDRESS>   108	Jason Bedard<EMAIL_ADDRESS>   108	Martin Staffa<EMAIL_ADDRESS>    99	Tobias Bosch<EMAIL_ADDRESS>    94	Michał Gołębiowski<EMAIL_ADDRESS>    71	Lucas Galfaso<EMAIL_ADDRESS>    70	Shahar Talmi<EMAIL_ADDRESS>    65	Jeff Cross<EMAIL_ADDRESS>    52	Chirayu Krishnappa<EMAIL_ADDRESS>    50	rodyhaddad<EMAIL_ADDRESS>    47	Pawel Kozlowski<EMAIL_ADDRESS>    45	Di Peng<EMAIL_ADDRESS>    43	Vojta Jina<EMAIL_ADDRESS>    41	Lucas Mirelmann<EMAIL_ADDRESS>

Interesting. Maybe that's why for a while my commits are saying Martin Staffa committed with Martin Staffa.
Can you add my canonical email<EMAIL_ADDRESS>

@Narretz I added entries for all the people from top 25 or so that had multiple distinct entries in Git commit history. On your name:
Before:
$ git shortlog -nse | grep -i staffa
   259	Martin Staffa<EMAIL_ADDRESS>   108	Martin Staffa<EMAIL_ADDRESS>     6	Narretz<EMAIL_ADDRESS>
After:
$ git shortlog -nse | grep -i staffa
   373	Martin Staffa<EMAIL_ADDRESS>

Cool, thanks. How did you determine which is the canonical email for Igor etc. where it is not exactly clear?

@Narretz Good question! I checked what mail he used in his latest commit to https://github.com/angular/angular; similarly for other people (for some I checked https://github.com/angular/angular.js instead).

BTW, apart from git shortlog, .mailmap is also consulted when git blame-ing. Unfortunately it's not consulted by default for git log or git show but it can be configured to do so:
git config --global log.mailmap true


Call initialize() when trying to add() to a PersistentCollection in order to avoid data loss

Doctrine ODM will lose existing elements in an EmbedMany when you attempt to add() a new element to an embedded collection (aka "PersistentCollection") if it was loaded from the database and not yet initialized. This seems to be the case in at least BETA12, BETA13 and master HEAD. Very scary stuff.
The included unit test shows a very simple sequence of steps where we attempt to try to add() a new element to an embedded collection. This exact same simplistic test will fail when attempted against the master line of Doctrine ODM.
I had to add an optional initialize param to the add() function. This seems to have required that the memory_limit for PHP be set much higher.

Will attempt to look into this Sunday afternoon.

isn't it possible to fix this bug without altering the public API of the class ?

OK, just saw #1119 doing exactly that, which is much better IMO

@stof :+1:


split SASS code in separate files

Allows users that use only balloon-mixins (and not balloon-classes) to avoid importing unused code.
My explicit goal is, on projects that don't use balloon-classes or data- attributes, to change @import "../../node_modules/balloon-css/src/balloon";by import "../../node_modules/balloon-css/src/mixins"; which would result in a 8.2kB reduction of the minified output CSS.
Also this is not a breaking change.

@aduh95 Nice work, but I need more info on that.
Can you please give an use case for using mixins but not data-balloon attributes? Just wondering what could it be used for.

Sure, here how I'm doing it:
:host {
  position: relative;
  --balloon-color: #10101044;

  & > span {
    @include base-effects();
    /* other styles down here */
  }

  &::before {
    @include arrow-up();
    @include base-effects();

    content: "";
    position: absolute;
    z-index: 10;
    /* other styles down here */
  }
}

As I'm using web components, it doesn't make much sense to use data- attributes, and it certainly doesn't make much sense for me to add all that CSS if I'm not using it.

Ok, that makes sense. Merged and published on 1.0.4. Thanks


OCPBUGS-1357: Fix install-plugins.sh to not override locked plugin versions

Do no override locked plugin versions
Verify that locked plugin versions exist in the bundle-plugins.txt file

/assign @akram @jitendar-singh

/retest

/jira refresh

/jira refresh

/jira refresh

/label qe-approved

@akram All tests are passing, please take a look and let me know if you have any questions about what the issue was.

/lgtm


Multiple psc-ide-server executables

I'm getting this error:
Found multiple psc-ide-server executables; using /usr/local/bin/psc-ide-server

But it's not clear where it's finding the "other" executable? If I npm uninstall -g purescript then it doesn't find any.

Hmm, I thought it should list them - which editor are you using this from? This is basically the result of a which (using node-which), so maybe something is throwing it off

Atom

To be clear that's a warning not an error, if that's the executable you expect then you can ignore it. But there should be a list of all candidates logged if you look at the dev console:
https://github.com/nwolverson/purescript-ide-purescript-core/blob/a463a739ccab97572d8802a7dd567c14baa04e94/src/IdePurescript/PscIdeServer.purs#L90

It appears it's finding the same executable 3 times:

Did anyone else ever see this? I'm imagining this is the result of a PATH containing duplicate entries.

Closing due to lack of activity, I assume it's the duplicate PATH entry I suggested.


Don't check for crypto in the exchange data

This prevents the convertCurrency function from throwing an error when it doesn't find BTC or TBTC in the exchangeRate data, as those currencies aren't in the data and aren't needed.
Note: while this fixes the bug being reported by multiple users in 2.0.20, this code hasn't been changed in 8 months, and I feel it's highly likely some other change caused this bug, which still needs to be investigated.
Note: the same change will need to be made with the alt coin branches to use the current crypto currency instead of being hard coded to BTC and TBTC.

closing in liu of #1149


Fix spelling mistake in ProcReceive

There was a spelling mistake in the ProcReceive handler. This PR fixes
this.

Make lgtm work


multi_external_select menu not providing suggestions

Description
Hello,
I'm implementing a multi_external_select menu element.  I created the options however, when I type into the select box, option suggestion is not working.  As you can see in the attached screenshot, I have entered pear into the search box however Apple and Banana are still showing and Apple is highlighted.
I am creating this app using nodejs.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

Expected result:
When I start typing, the options suggestions should narrow based on the text.
Actual result:
All options are showing.
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc

@seratch - Thank you for your reply.  I thought multi_external_select had it built in, similar to multi_static_select.  I was able to figure out what I needed thanks to your reply.  Appreciate it!

Thanks for your reply and I'm glad to hear that my comment was helpful!


[SPARK-8195] [SPARK-8196] [SQL] udf next_day last_day

next_day, returns next certain dayofweek.
last_day, returns the last day of the month which given date belongs to.

Merged build triggered.

Merged build started.

Test build #35677 has started for   PR 6986 at commit 5ef6a8c.

Test build #35677 has finished for   PR 6986 at commit 5ef6a8c.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LastDay(startDate: Expression) extends Expression
case class NextDay(startDate: Expression, dayOfWeek: Expression) extends Expression

Merged build finished. Test FAILed.

Close it because https://github.com/apache/spark/pull/6782#issuecomment-116888516 for now

Merged build triggered.

Merged build started.

Test build #38195 has started for   PR 6986 at commit 5ef6a8c.

Merged build triggered.

Merged build started.

Test build #38195 has finished for   PR 6986 at commit 5ef6a8c.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #38197 has started for   PR 6986 at commit 1a9de3d.

Test build #38197 has finished for   PR 6986 at commit 1a9de3d.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LastDay(startDate: Expression) extends UnaryExpression with ImplicitCastInputTypes
case class NextDay(left: Expression, right: Expression)

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38203 has started for   PR 6986 at commit 2d0629b.

Test build #38203 has finished for   PR 6986 at commit 2d0629b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LastDay(startDate: Expression) extends UnaryExpression with ImplicitCastInputTypes
case class NextDay(left: Expression, right: Expression)

Merged build finished. Test PASSed.

@rxin @chenghao-intel @zhichao-li

Merged build triggered.

Merged build started.

Test build #38382 has started for   PR 6986 at commit d09bcce.

Test build #38382 has finished for   PR 6986 at commit d09bcce.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LastDay(startDate: Expression) extends UnaryExpression with ImplicitCastInputTypes
case class NextDay(left: Expression, right: Expression)

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #38533 has started for   PR 6986 at commit 8846086.

Test build #38533 has finished for   PR 6986 at commit 8846086.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LastDay(startDate: Expression) extends UnaryExpression with ImplicitCastInputTypes
case class NextDay(startDate: Expression, dayOfWeek: Expression)

Merged build finished. Test PASSed.

@adrian-wang I think this one is pretty close - we need to add more user facing documentation and internal comments, as well as unit tests.
Thanks.

Merged build triggered.

Merged build started.

Test build #38627 has started for   PR 6986 at commit dc69630.

Can you address these two issues?

done

Merged build triggered.

LGTM

Merged build started.

Test build #38634 has started for   PR 6986 at commit 02b3426.

Test build #38634 has finished for   PR 6986 at commit 02b3426.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LastDay(startDate: Expression) extends UnaryExpression with ImplicitCastInputTypes
case class NextDay(startDate: Expression, dayOfWeek: Expression)

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38645 has started for   PR 6986 at commit ef7e3da.

Test build #38645 has finished for   PR 6986 at commit ef7e3da.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LastDay(startDate: Expression) extends UnaryExpression with ImplicitCastInputTypes
case class NextDay(startDate: Expression, dayOfWeek: Expression)

Merged build finished. Test FAILed.

Test build #38627 has finished for   PR 6986 at commit dc69630.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class LastDay(startDate: Expression) extends UnaryExpression with ImplicitCastInputTypes
case class NextDay(startDate: Expression, dayOfWeek: Expression)

Merged build finished. Test PASSed.

Thanks - I've merged this.


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=367360769
https://github.com/Azure/azure-cli-extensions/commit/e24250888b94d9989aeffdb460b32fa92033d989

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


No /30 net in SSL VPN since 21.7

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x ] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x ] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
Since OPNsense 21.7 all site to site SSL VPN tunnel stop working.
it is not possible to ad a VPN site to site tunnel with a /30 tunnel net.
existing tunnels stop working.
same configuration on client site is working
To Reproduce
Steps to reproduce the behavior:

Go to 'VPN/OpenVPN/Server/'
Click on 'add server or existing server'
Scroll down to 'save'
See error (The following input errors were detected:
A prefix longer than 28 cannot be used with a net30 topology.)

Expected behavior
Tunnel net with 2 host addresses. (first server second client)
Environment
OPNsense 21.7.2_1-amd64FreeBSD 12.1-RELEASE-p20-HBSDOpenSSL 1.1.1l 24 Aug 2021
CPU type | AMD EPYC Processor (4 cores)

This was introduced back in July due to an OpenVPN pool size configuration change referenced here. The relevant opnSense forum I was able to find here. The problem with the both of these is that it appears that opnSense is attempting to use net30 by default. The error that comes up when creating a new VPN interface is "A prefix longer than 28 cannot be used with a net30 topology." The issue with this is even when creating a p2p vpn (which, I would think, should be using p2p topology rather than net30 or subnet), it forces the use of either net30 or a subnet topology if the topology checkbox is checked. As above, the OpenVPN devs see no valid use for a net30 or subnet topology VPN with less than 2 usable pool IPs. In the case of a p2p topology VPN, this occurs to me to be perfectly fine.
Long story short, prefix checking was implemented here but as far as I can see, it does not take into account peer-to-peer servers and treats all servers as net30 or subnet.

sorry, it looks like I missed it. will make a pr tomorrow

# opnsense-patch 0ee3ecde


Token not removed after logout - user still receiving notifications

Describe the bug
Hi, we are using official Rocket Chat Android app. When user logout form app, user token is not removed form '_raix_push_app_tokens' collection. User still receiving push notifications.
Another case when I logout and next login another user I am receiving notfications from first user, bacuse his token is still in database.
I have tested also on iOS app, and there issue not exists. Token is removed from '_raix_push_app_tokens' collection after logout.
To Reproduce

Logout from  Rocket Chat Android app
Check '_raix_push_app_tokens' collection, token still exists
User still receiving push notifications

Expected behavior
After logout token removed from '_raix_push_app_tokens' collection, user not receiving push notifications
Devices and Versions
Your Rocket.Chat.Android version: 3.4.2
Your Rocket.Chat Server version: 1.1.1
Mobile device model and OS version: LG G6 Android 8.0.0

Duplicate of https://github.com/RocketChat/Rocket.Chat.Android/issues/2322


[Bug]: Failed to process files of length 0 when optimizing

What happened?
Flink stream ingestion job committed an equality-delete file of length 0 after failover, then self-optimizing caught an exception when reading this file.

Affects Versions
master/0.3.0
What engines are you seeing the problem on?
Optimizer, Flink
How to reproduce
1.After Flink job failover, it occasionally commits a file of length 0.
2.Then the self-optimizing will fail, and we can find the exception in optimizer.
Relevant log output
No response
Anything else
I think we should avoid committing a file of length 0, then no exceptions will occur when MOR/Optimizing.
Code of Conduct

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

com.netease.arctic.io.writer.BaseTaskWriter doesn't check the file size (or row count) when close
  @Override
  public void close() throws IOException {
    for (DataWriter<T> dataWriter : dataWriterMap.values()) {
      dataWriter.close();
      completedFiles.add(dataWriter.toDataFile());
    }
    dataWriterMap.clear();
  }

And I think it's not a good way to fix this problem by skipping the files of length 0 in the optimizer. Although it avoids the exception, the underlying problem is not solved.

cc @zhoujinsong @zstraw @shendanfengg

@wangtaohz I do agree that we should not commit an empty file. I will fix this problem in writers.


Update request: calligra 3.2.1 → 4.0.0

Package name: calligra
Latest released version: 4.0.0

Current version on the unstable channel: 3.2.1
Current version on the stable/release channel: 3.2.1

[x] Checked the nixpkgs pull requests

Notify maintainers
@ebzzry @zraexy

https://invent.kde.org/office/calligra/-/tags/v4.0.0
Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Github moment.
Completed in #344930.


server: Fix exception while update domain resource count (#3204)

reimplement #3303 on moved file in 4.12
(should add the fix from #3204  to master)
Description

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):
How Has This Been Tested?

@ustcweizhou , i redid your PR because it wouldn't fwd-merge.

@DaanHoogland ok. what about cherry-pick ?

@ustcweizhou same conflict, this was quicker

@DaanHoogland you could have forward merged with this change?

@DaanHoogland can you also check the Travis failure, is this breaking anything?

@DaanHoogland @ustcweizhou the build fails due to:
/home/travis/build/apache/cloudstack/engine/schema/src/main/java/com/cloud/configuration/dao/ResourceCountDaoImpl.java:270:9: expecting SEMI, found 'try'
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:check (cloudstack-checkstyle) on project cloud-engine-schema: Failed during checkstyle configuration: Exception was thrown while processing /home/travis/build/apache/cloudstack/engine/schema/src/main/java/com/cloud/configuration/dao/ResourceCountDaoImpl.java: MismatchedTokenException occurred during the analysis of file /home/travis/build/apache/cloudstack/engine/schema/src/main/java/com/cloud/configuration/dao/ResourceCountDaoImpl.java. expecting EOF, found 'pstmt' -> [Help 1]

Please hold merging until build is fixed, thanks.

@rhtyd fwd-merge did not work due to the file being moved (out of git bounds)

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2751

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

closing, setting git config global  merge.renamelimit=5635 would have done the trick.

Trillian test result (tid-3570)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 32226 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3304-t3570-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermittent failure detected: /marvin/tests/smoke/test_ssvm.py
Smoke tests completed. 70 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File


cpu: Set SLC bit for GPU tester

This fixes issue #131 by reverting to the old behavior of performing all atomics at the system level. To do this the SLC bit needs to be set for all atomic requests.
Change-Id: I63f4e449be1b02c933832d09700237f8c8026f4c

Thanks Matt! This closes #131

Thanks @abmerop , Dan and I probably missed this with the GLC commit ... I thought we ran the tester before committing but guess not.


Detecting if paid plan is needed

https://docs.google.com/spreadsheets/d/1Fa5e8OniZXCPy3RdMR7B4i5zQpIOzcjhIMh9hfnJ_ZQ/edit#gid=0


sriov: expose sysfs attributes

When VF PCI devices are not bound to their default network driver, it may be
required to access the sriov_numvfs and sriov_drivers_autoporbe attribute
in sysfs to get meaningful information.

sriov: export numvfs as reported in sysfs
sriov: expose sriov_drivers_autoporbe

The sysfs is accepted when it is the reliable (or sometimes only) interface for query specific network related information.
For this case, I search kernel code, there is no other better way to get sriov_drivers_autoporbe.

@rjarry Do you have time to amend your patch base on feedback?

I had completely forgotten about this, sorry :)
I have addressed all comments. Let me know if it looks good.
Cheers.


Update tesseract.js

-psm option is deprecated. Switched to --psm for the latest OCR

Test fails due to usage of ES6 fat arrow function. Wrecker doesn't support ES6?


Added a copyright and year to the footer✅

I have added the copyright and automated year to the footer section.


jderobot-colortuner: 0.0.3-2 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository jderobot-colortuner to 0.0.3-2:

upstream repository: https://github.com/JdeRobot/ColorTuner.git
release repository: https://github.com/JdeRobot/ColorTuner-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.8.0
previous version for package: null

jderobot_color_tuner

No changes

This is failing CI because it is not in alphabetical order; this should be after jderobot_assets.
While you are in there, I noticed that the name of the package inside here is jderobot_color_tuner, while the top-level name you've selected is jderobot_colortuner.  While this is allowed, it seems to make more sense to have those be the same.

@fqez I saw your reference from the upstream source. You only need to add an underscore and edit this file to insert it in the right alphabetical order to resolve the issues raised above.
If you're not going to do that soon we'll close this out due to inactivity soon.

No activity in over a month, so I'll close this out.  If you still want to get this in, please respond to the review comments and re-open.  Thanks.


add Python Connexion API implementation details

add Python Connexion API implementation details

assuming this is a dead end now.


CodeSpace delete so many files

ADD ISSUE DESCRIPTION HERE
Version: 1.73.1
Commit:<PHONE_NUMBER>f055b99068d3688932416f2346dd3b
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/108.0.1462.42
Embedder: codespaces
I decided to publish the project worked on codespace but when I gave a lot of files from the project were deleted.

\gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


XJoy not reading analog stick controls

Is the software not supposed to be able to pick up the analog stick controls? Everything works fine except the left and right analog sticks. It doesn't even show up in the command lines in XJoy.exe when I try moving them. I've tried it on both my Windows 8.1 and my Windows 10 laptops, and neither works.
I'm on XJoy v0.2.0.

Update: Oops nevermind, doesn't seem like it was XJoy's fault after all. Though the analog inputs don't show up in the command prompt, they work perfectly fine in games that support Xbox contollers, like Stardew Valley. I was having problems getting Retroarch to recognise the analog stick inputs, and it seems like it's an issue with RetroArch rather than XJoy.

Yeah, I had it suppress printing the analog state in the terminal because it bogged down performance a ton
Glad it works!!

On Oct 16, 2019, at 3:52 PM, raindew120<EMAIL_ADDRESS>wrote:
Closed #41 https://github.com/sam0x17/XJoy/issues/41.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/sam0x17/XJoy/issues/41?email_source=notifications&email_token=AAOE4LLCO6HKSQ3PFLDD4NLQO5WIHA5CNFSM4JBGNSIKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUIHVSDA#event-2718914828, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOE4LKSVOMXL7SZTWLLUN3QO5WIHANCNFSM4JBGNSIA.


feat: Support Fast Enter Playmode

Uses [RuntimeInitializeOnLoadMethod] to reset statics
fixes #2971
References:
https://forum.unity.com/threads/configurable-enter-play-mode.768689/
https://blog.unity.com/technology/enter-play-mode-faster-in-unity-2019-3

This is great! Thanks!


feat: add jest-dom-prefer-enabled-disabled, jest-dom-prefer-required, jest-dom-prefer-checked rules

implements https://github.com/Belco90/eslint-plugin-testing-library/issues/30

@Belco90 all your requests have been addressed.

alright guys, addressed the feedback.

Awesome, LGTM now!

cool, i don't have permission to merge (yet? 😉)

@thomlom @Belco90 I decided to add the prefer checked and prefer required rules as well. The reason I included them in this PR (then re-titled the PR) is that I extracted the rule for all 3 to share the same code.   So probably best if you give another review.  I will add docs later today.

@benmonro thanks for your work for those additional rules, but please avoid this kind of "controversial" changes as now you are adding lot of stuff out of the scope of the original issue. Also, if one one those new rules added doesn't pass the review, it will block the other from being released. Better to have rules on their own PR to be discussed and reviewed individually. Also you have added more changes related to test coverage threshold that should not be involved here and done in a separated task for it.
So could you leave this PR as before and address those new rules and test coverage threshold in a different one?

I had a feeling you were going to say that.  I'm doing this in my spare
time and don't have the time for that right now.  Sorry.  The code works
and I was dinged for not having coverage before so now it does have it.
If you want to close the PR feel free. No hard feelings.
On Sun, Oct 27, 2019 at 10:22 AM Mario Beltrán Alarcón <
<EMAIL_ADDRESS>wrote:

@benmonro https://github.com/benmonro thanks for your work for those
additional rules, but please avoid this kind of "controversial" changes as
now you are adding lot of stuff out of the scope of the original issue.
Also, if one one those new rules added doesn't pass the review, it will
block the other from being released. Better to have rules on their own PR
to be discussed and reviewed individually. Also you have added more changes
related to test coverage threshold that should not be involved here and
done in a separated task for it.
So could you leave this PR as before and address those new rules and test
coverage threshold in a different one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Belco90/eslint-plugin-testing-library/pull/31?email_source=notifications&email_token=AADBPBDG7I5UQFR32AR2OWDQQW537A5CNFSM4JEODFP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECLDPWA#issuecomment-546715608,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADBPBFC5LJ2EH3XUZA7LP3QQW537ANCNFSM4JEODFPQ
.

--
Ben Monro
Software Developer

I don't want to close this PR at all, just make sure everything is consistent and done following a workflow that make sense for everyone :)
No rush into doing that now, I also created and maintain this plugin in my free time: no one is putting pressure on you. Just create a new branch from this current one (for another PR) and revert this one to the previous commit would be fine, it was already approved just waiting to be merged.

@Belco90 thanks for the feedback.  I decided to move this feature to its own plugin: eslint-plugin-jest-dom.  after more thought, it really does deserve it's own plugin, also there could be potential users who might want to use jest-dom apart from testing-library.  Thanks again for the feedback and keep up the good work, i <3 this plugin.

Hey @benmonro, it's too bad and frustrating that this feature has been moved to its own plugin. These rules are worthwile and it's relevant to include them in this plugin since we can create a shareable configuration for jest-dom just like we did for Angular, React and Vue.
I have the feeling you were frustrated by the review comments. I hope that's not the case since it wasn't the goal at all. I'm curious to have your feedback on this 🙂
Thanks for the discussion anyway!

no, that's not the case at all. I still ❤ this plugin and will still contribute when I come across things we need.  There were 2 main factors in moving it to it's own plugin.  1) jest-dom isn't actually a testing library, even though it's testing library-adjacent.  2) after looking at the fact that each rule had to be prefixed with jest-dom- it seemed as though the code itself was begging for it.


unit of speed

if i use label.metadata.speed_x to read the speed of object, what's the unit of speed? m/s or km/h? I found that some speed is just like speed:2[3.603297793914359e-27, -7.206595587828718e-27]. Why the speed is not zeros but some e-27?

the unit is m/s. Those very small numbers are from numerical errors.


Update reactNativeSDK.mdx

🚀 Deployed on https://62d8855d65359c227bf8a4ab--cozy-fox-0defec.netlify.app


Some metrics of package quality

Per your request:

Of course, follow semver scrupulously. Known breaking changes must bump a major version. Any functionality or API additions must be in a minor bump. Everything else is a patch. Any breakages discovered must be rolled back and ported to the next major version. etc.
npm install should be 100% of what's required in a given module to install all of its dependencies and/or dev dependencies
npm test should always run tests
npm explore foo && npm test should always run foo's tests (ie, always publish test files)
Any build steps or compilation must be done prior to publishing - ie, coffeescript, babel, etc must never be required at runtime to use a module
Any important project-related tasks should be discoverable from the scripts hash in package.json. Makefiles (or any ripoffs of same) are totally fine, but I shouldn't need to know how to use those to run 100% of important tasks: npm run foo can alias to make foo, for example.
Good documentation: include a readme.
package.json must always point to the git repo, to where issues can be filed, and must always include at least one license designation.

So caveats:

If you're just looking at the scripts.test entry and not running it, remember that the default package.json made by npm init has one that's just set to fail automatically, so you'll have to check for that special case.
If you actually run the npm explore foo form, you'd need something like – npm explore foo 'npm install && npm test' to get the dev deps.

Of course, follow semver scrupulously. Known breaking changes must bump a major version. Any functionality or API additions must be in a minor bump. Everything else is a patch. Any breakages discovered must be rolled back and ported to the next major version. etc.

On 0.x.y versions, the x should define backward incompatible API changes, the same way as major versions on post-1.0.0 releases.

All we can check is that the version is valid semver.

APIs could somewhat be check by analizing the methods and their parameters and see if they are added or they change, in that last case it should be in a new major version (or new 0.x). It could be also done to check deleted methods and params and show a warning if they were not marked as deprecated in a previous version.

If you can think of a way of doing that statically from an unbundled package tarball/repo, I'd certainly be interested.

Maybe using esprima or something similar... For prototype defined ones should be somewhat easy, for instance methods (this.foo = function(){}) would need more checking, but I think it's doable up to some degree.

Obviously being Javascript a dynamic language this could never be bullet-proof, but a statically analisis could be done in a high percentace of situations.

yeah, I already have some need for esprima to come along at some point... but this is probably one of those spots where a PR would work best (even if it's just tests).

Look at the exported thing; compare Object.getOwnPropertyNames + Object.getOwnPropertySymbols  and the typeof of their values (and name and length if they're functions, etc going into more depth if the types match), and then do the same walking up the prototype chain. That should allow you to produce a digest hash, as well as determine when observable properties are added, or deleted.
Added would guarantee at least a minor - deleted would guarantee a major - no observable changes is likely a patch.
Obviously for 0.x versions (which nobody should still be using anyways; dock them for that regardless), obviously the second number is for breaking changes, and the third for additions.


Prebuilt binaries of torch.audio for aarch64 cuda

🚀 The feature
torch.audio provides prebuilt binaries for aarch64 + cuda on linux
Motivation, pitch
pytorch now provides aarch64 cuda prebuilt binaries in 2.4.0 (https://github.com/pytorch/pytorch/issues/134117)  but currently torch.audio doesn't provide corresponding prebuilt binaries. It makes very hard to adopt torch on aarch64 + cuda environment, which is often much cheaper in cloud providers.
Alternatives
Build torch.audio from source, which is not ideal for users of this library since it requires lots of works.
Additional context
No response

Nightly binaries are already available for ARM+CUDA. The PyTorch 2.4.0 release only added the torch wheels without torchvision and torchaudio as the latter two builds were created late in the release cycle and thus to avoid last minute churn.


[Bug] [master/task] workflow with sub_process task can't be stop when running

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
version 3.1.7
I want to stop the workflow with 'sub_process' task, but the workflow still 'ready stop' and 'sub_process' task still running.
Task state:

Workflow state:

'sub_process' task log:

Task state should be 'kill' instead of 'stop', cause TaskExecutionStatus only admit 'kill':
  public boolean isFinished() {
      return isSuccess() || isKill() || isFailure() || isPause();
  }

  public boolean isKill() {
      return this == TaskExecutionStatus.KILL;
  }

What you expected to happen
Stop workflow with 'sub_process' task
How to reproduce

create A workflow with a shell task which will sleep 100s.

create B workflow with a sub_process task which point to A workflow.
start B workflow.
after few seconds, stop B workflow instance.

Anything else
No response
Version
3.1.x
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

@ruanwenjun What does 'BLOCK' workflow state mean? What is the corresponding task status for it?


Switch from JSCS to ESLint

Per https://github.com/necolas/postcss-bem-linter/pull/27
I'm inclined to leave this one to you @necolas so you can enforce the code style you like.

fixed by #40


turn "both" layer the default

today the "all" layer is the default, I believe the "both" is sharper

I'm not aware of a "both" layer.  The activity layers I see available are all, ride, run, water, and winter.   This extension uses whichever layer is currently selected by pulling the activity and color values from the url.  When I originally wrote this the url would change from strava.com/heatmap#.../hot/all to strava.com/heatmap#.../hot/ride as soon as you clicked a different activity.  Now the url isn't changing right away for me, but it does change when I move the map a bit.  So that's a bit of an annoying workaround, but it is possible to get the correct layer url for whichever activity and color combination you want to use.

this is the url i'm talkin about, which offer sharper traces tms[3,15]:
https://heatmap-external-{switch:a,b,c}.strava.com/tiles-auth/both/bluered/
Em dom., 27 de jun. de 2021 às 15:46, Zeke Farwell @.***>
escreveu:

I'm not aware of a "both" layer. The activity layers I see available are
all, ride, run, water, and winter. This extension uses
whichever layer is currently selected by pulling the activity and color
values from the url. When I originally wrote this the url would change from
strava.com/heatmap#.../hot/all to strava.com/heatmap#.../hot/ride as soon
as you clicked a different activity. Now the url isn't changing right away
for me, but it does change when I move the map a bit. So that's a bit of an
annoying workaround, but it is possible to get the correct layer url for
whichever activity and color combination you want to use.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zekefarwell/josm-strava-heatmap/issues/1#issuecomment-869208335,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3JYSOKPYJOF7OOTD7VG2DTU5WXDANCNFSM47MNEFZQ
.

Interesting.  Tiles with that url format are not viewable through the web interface at strava.com/heatmap.  This extension relies on the Strava UI for selecting the color and activity so there's not a simple way to support these hidden tiles at the moment.  A separate UI would need to be created.

Interesting, I was also using both (as described on the Strava osm wiki article), but it stopped working today for me (which led me to this extension, nice!). Using all now, which works.

Closing this since the both url isn't working anymore


inotify scheduler for script vars

Description
Adds another scheduler for script-vars, which will execute the command whenever a file/directory changes.
Usage
e.g.
<script-var name="test" files="[/home/user/test,/sys/class/power_supply/]/>

Additional Notes
See the docs I added.

Do you have a concrete usecase example for this? In it's current state, this seems,.. rather confusing (both in terms of code, and for the user) - where would a simple script-var (if necessary, using sth like entr) not suffice?

Can't we just use a listening variable for this? We can easily spawn bg child processes (with &) monitored by linux itself. Making sleep/loop is easy either.

Cant you just use entr or smth

Fine, I'm too lazy to resolve the merge conflicts anyways..


Ability to return status code other than 200 via Aggregation process

Hi,
By default ocelot will return 200 even if any of the down streams returns 404, 401 etc during aggregation process. Is there a way to customize that behaviour?
Our UI-client will make decision based on returned API status code.
for example, if the status code is 401 then show a unauthorize screen
or if the status code is 400 then may be a different screen to show the issue and so on.
I have looked into custom DefinedAggregator to achieve this for a specific route but I want the ability to change the default behaviour for all the routes.
Currently i looking at replacing SimpleJsonResponseAggregator with custom but would like to know if there is any better solution

By default ocelot will return 200 even if any of the down streams returns 404, 401 etc during aggregation process. Is there a way to customize that behaviour?

Based on current implementation if downstream failed then the response will not be included in final aggregated data.
So, we will not change this behavior.
To customize route behavior for aggregated routes you need to develop custom IDefinedAggregator.
Then overriding status code should be possible.

I have looked into custom DefinedAggregator to achieve this for a specific route but I want the ability to change the default behaviour for all the routes.

For all routes you need to develop custom Delegating Handler in which you override status code.

Currently i looking at replacing SimpleJsonResponseAggregator with custom but would like to know if there is any better solution

As for an user, there is no better solution except: IDefinedAggregator and Delegating Handler
As for a developer, there is better solution

fork Ocelot repo in your GitHub account
open in Visual Studio and develop whatever you want!


Rejected blocks no matter [all details included, please review]

hi VERGE dev team @justinvforvendetta could you please review these and suggest, what's causing reject blocks issue. I've tried numerous experiments but all goes to 'reject blocks'. I've included all settings, conf and debug log for you to kind review and help me solve this issue, thanks in advance.
VERGE.conf

Pool Settings tab

Pool Daemon tab

Getinfo output

Getmininginfo out

debug.log file
verge-debuglog.zip
Reject log

Did you update to the latest commits?
https://twitter.com/vergecurrency/status/982399457508646912

Affirmative @jrsikors

@jrsikors what is the right version please advise link to download linux daemon?

it looks like you got the latest commit, was my mistake, i didn't read the version fully :disappointed:

@jrsikors could you please review VERGE.conf, Settings tab and Daemon Tab configuration I've posted earlier screenshots, if everything is alright or I need to add or subtract anything?

would suggest hopping on Discord
https://discord.gg/vergecurrency
to the Verge-Mining-Discussion channel
If you need immediate answers.. Justin unavailable right now

are you using clearnet or master branch? no other pool is having that issue, so im not sure whats going on..
https://umine.org/site/block?id=561
https://nlpool.nl/site/block?id=561
http://yiimp.eu/site/block?id=562
http://antminepool.com/site/block?id=561
https://luckypool.xyz/site/block?id=1

btw, if  you're running on tor, which it looks like you are, the latency probably isnt helping since you are submitting blocks a few milliseconds slower than the other pools.

@justinvforvendetta yes running on tor. could you please guide me, how can I compile VERGE without tor?

https://github.com/vergecurrency/VERGE/issues/487

no, clone the 4.0clearnet branch if you want to mine and submit blocks as fast as the other pools

you can do git checkout 4.0clearnet too, if you don't want to directly clone the 4.0 branch

My question is
I'm at https://github.com/vergecurrency/VERGE/tree/4.0clearnet
When I try to clone I get exactly the same clone url as I get in master,
https://github.com/vergecurrency/VERGE.git
can you please give me command line to clone clearnet 4.0
is it?

git clone https://github.com/vergecurrency/VERGE.git

or

git checkout 4.0clearnet https://github.com/vergecurrency/VERGE.git

@justinvforvendetta @jrsikors
I ran commands this way
 git checkout 4.0clearnet

Branch 4.0clearnet set up to track remote branch 4.0clearnet from origin.

git clone https://github.com/vergecurrency/VERGE.git
after git clone, cd VERGE
./autogen.sh
but it again installs with TOR

you should have done git checkout after cloning.
do this:
git clone https://github.com/vergecurrency/VERGE/tree/4.0clearnet
and then compile =]

@justinvforvendetta
Cloning into '4.0clearnet'...
remote: Not Found
fatal: repository 'https://github.com/vergecurrency/VERGE/tree/4.0clearnet/' not found

ok clone normal and the  git checkout 4.0clearnet and then compile. don't clone again

@justinvforvendetta
fatal: Not a git repository (or any of the parent directories): .git

you need to be in the new verge directory

Alright, should I compile standard way or I need to add some flags with './configure' ?
./autogen.sh
./configure
make

should work just like that

thanks alot guys @justinvforvendetta @jrsikors

I managed to compile 4.0clearnet, it is the correct version, as I see BETA there?

Yep you are good to go .. you can see the commit number in the version
https://github.com/vergecurrency/VERGE/commit/c66e16d2f3b63519b97b33a403866a80e4e340dc

@jrsikors blocks are stuck at 2039377, not moving forward, even though I have restarted with -reindex ?

it should finish syncing, but please come back here if it does not.

sync went smooth, however in debug.log I'm noticing this, is it normal or something not right?

@justinvforvendetta @jrsikors Even after installing non tor version, 4.0clearnet,  I'm still getting rejected blocks, what could be the possible reasons?
here's decode error

@jrsikors @justinvforvendetta
and pool settings are

I'm about at the extent of my mining knowledge unfortunately.
Again -- I would highly recommend hopping on the Discord channel
https://discord.gg/vergecurrency
There is an entire "room" in the channel devoted to "Verge-Mining-Discussion" where I think you would find more help from experienced verge miners.
Otherwise i have to defer to justin if/when he finds time.

@jrsikors I've been to that discord channel and unfortunately there isn't any help at all as they are mere 'miners', none pool owners I could see there.
It's very technical issue I'm sure with your little help it can be nabbed. I'll appreciate if you can refer to Justin to look into this, I can provide as much as infor / details needed.

maybe it's because we have ntime in our headers, so you need to select pos/pow hybrid in the config?

Yes, POW, please advise?

@jrsikors @justinvforvendetta

getinfo

do you understand what I mean when i say ntime is in the header? you would want to select pos+pow if possible, or change the software to recognize ntime

@justinvforvendetta @jrsikors
can I just use POS?

do you understand what I mean when I say that verge is pow, with ntime in the header

Trying to get your point.
I can pool set software to pow/pos.
OR is there anything to add to VERGE.conf file for ntime param?

does that mean instead of just pow, I should use 'pow/pos'

in VERGE.conf, do I need to add staking=0

no, because it will not stake anyway.

It's been weeks going after VERGE mining with rejected blcoks, I have spoke to at least more than half a dozen pools they are running other coins successfully except XVG rejected block that includes me as well.
I've a notion that you guys are manipulating and not allowing everyone else to run pools with XVG only select pools are able to do so.
What the heck it is that I cannot setup my pool right and several others whom I personally talk to but only few select pools are running XVG.
It's horrible process to get  help from you Dev guys, I'll take it forward and bring it in front of the community as far as I can reach this is absolutely corrupt at the end of XVG Dev who are being secretive of mining which is apparently a community project but only select folks are getting benefit. Mind it if you guys do not spill the beans fairly then rest of people will bring the attention more rigorously.

it is not secretive at all. pool admins have not even needed our help. you just need to clone the 4.0clearnet branch.


[Accordion] does not work with "any element you want"

The documentation states you can use the accordion with any element you want but currently that is not the case.
http://foundation.zurb.com/sites/docs/accordion.html
foundation.accordion.js is looking specifically for "li" elements. I have create a pull request with a fix https://github.com/zurb/foundation-sites/pull/7231

Thanks for the PR @evanlask
Closing in favor of https://github.com/zurb/foundation-sites/issues/8013


Add non-alphabetic font-family similar to BLOKK or Redacted

Just an idea. Currently there are tree fonts to choose and all of them are alphabetic so adding non-alphabetic might be useful for some folks. "Lorem ipsum" would look something like this "▮▮▮▮▮  ▮▮▮▮▮", but without space between letters.
Reference fonts:
BLOKK
Redacted

Yeah, this can be helpful when designing mockups/wireframes. Let's see what the team thinks about it.

adding more search keywords: placeholder text lorem ipsum squiggly lines

Awesome idea, we shall def. revisit in the future!


App crash on doing Health check of other signers

[ ] User was able to add others signers properly but after that when they wear trying to perform health check app crashed with blank screen giving successful toast message

Check screen recorder
https://github.com/bithyve/bitcoin-keeper/assets/107177634/5f61867f-ed80-4cfb-862c-b8984543d625
Check screenshots

Verified this issue on keeper app v 1.2.11(381)


BBadge incorrectly declares bg-variant and text-variant properties

Describe the bug
I'm pretty sure the bootstrap badge component doesn't respect the text-* and bg-* classes (see the reproduction below). If I'm right, we shouldn't be exposing the bg-variant and text-variant properties. I think this means removing the us of useColorVariantClasses and manually implementing the handling of the variant property?
Reproduction
https://stackblitz.com/edit/github-bserkl?file=src%2Fcomponents%2FComp.vue
Used Package Manager
pnpm
Validations

[X] Have tested with the latest version. This is still alpha version and sometime things change rapidly.
[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Not quite. This should be something written somewhere in the documentation among components with a default variant prop.
When you use prop variant, it will overwrite props textVariant & bgVariant. So when you have default props like BBadge's variant: 'secondary' you will only get text-bg-secondary
In order to get your
<BBadge text-variant="success" bg-variant="danger"> testing </BBadge>
example to work, you would need to do
<BBadge text-variant="success" bg-variant="danger" :variant="null"> testing </BBadge>
There isn't a great way to fix this manually for users, I think the best is to just have some resource that tells why it doesn't work. BAvatar should suffer from the same issue

Thanks for the explanation. #2200 is my attempt to address this in documentation - and you're right BAvatar has a similar issue and there was a visible bug in the docs if you looked carefully enough. By my reading BButton also has this issue.

https://github.com/bootstrap-vue-next/bootstrap-vue-next/pull/2200#issuecomment-2351273613


Audio Problem; System UI Lags

Hey, so ive recently installed the Pixelify module and I wanted to try out Now Playing, now I have playback issues resulting the system ui to lag out. So I tried to install pixelify again without Now Playing, but the Issue persists. Ive been told to make a log, but the log data is incredibly long.
Device: Xiaomi 11T Pro
GSI Rom: SparkOS 12.6
Android 12L

Guys, if any of you installed the stable version 2.02, try to install the beta version and disable now playing, this solved my issue

Different device, but same issue.
moto edge 2021 xt2141-2 (berlna).
With 2.02, audio was more or less fine as long as now playing is disabled.
But with 2.1, audio constantly crashes regardless of now playing. audio_playform_info.xml is changed with this module?

I'm getting the same as Ziddey on 2.1. I had to revert back to 2.02 to get my audio to work properly. Anyone know if this has been fixed in the latest 2.2 beta?

Same issue here on 2.2 on a Redmi Note 10 Pro.


unifiedpush-common-proxies: 1.3.0 -> 1.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/unifiedpush/common-proxies/releases.
meta.description for unifiedpush-common-proxies is: "A set of rewrite proxies and gateways for UnifiedPush"
meta.homepage for unifiedpush-common-proxies is: "https://github.com/UnifiedPush/common-proxies"
meta.changelog for unifiedpush-common-proxies is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.4.0 with grep in /nix/store/wznw01mkjvr5d9vch84mypjj7vk1cskn-unifiedpush-common-proxies-1.4.0
found 1.4.0 in filename of file in /nix/store/wznw01mkjvr5d9vch84mypjj7vk1cskn-unifiedpush-common-proxies-1.4.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
unifiedpush-common-proxies

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wznw01mkjvr5d9vch84mypjj7vk1cskn-unifiedpush-common-proxies-1.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A unifiedpush-common-proxies https://github.com/r-ryantm/nixpkgs/archive/ea1a24151c94f72a305bc88e42e2db01b98408d0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wznw01mkjvr5d9vch84mypjj7vk1cskn-unifiedpush-common-proxies-1.4.0
ls -la /nix/store/wznw01mkjvr5d9vch84mypjj7vk1cskn-unifiedpush-common-proxies-1.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

unifiedpush-common-proxies

Maintainer pings
cc @yu-re-ka for testing.

Needs to get rebased

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/unifiedpush/common-proxies/releases.
meta.description for unifiedpush-common-proxies is: A set of rewrite proxies and gateways for UnifiedPush
meta.homepage for unifiedpush-common-proxies is: https://github.com/UnifiedPush/common-proxies
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.0 with grep in /nix/store/c5hlb4qmyms26m0fzm8h96sm2i487x82-unifiedpush-common-proxies-1.5.0
found 1.5.0 in filename of file in /nix/store/c5hlb4qmyms26m0fzm8h96sm2i487x82-unifiedpush-common-proxies-1.5.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
unifiedpush-common-proxies

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/c5hlb4qmyms26m0fzm8h96sm2i487x82-unifiedpush-common-proxies-1.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A unifiedpush-common-proxies https://github.com/r-ryantm/nixpkgs/archive/101c09c7cf8fbf52d1f8d171a0fc0f4c6e32e470.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/c5hlb4qmyms26m0fzm8h96sm2i487x82-unifiedpush-common-proxies-1.5.0
ls -la /nix/store/c5hlb4qmyms26m0fzm8h96sm2i487x82-unifiedpush-common-proxies-1.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

unifiedpush-common-proxies

Maintainer pings
cc @yu-re-ka for testing.

should this still be in draft ?

I have PR that is esentially duplicate of this but also unpins go version
https://github.com/NixOS/nixpkgs/pull/235911


HDFS-16232. Fix java doc for BlockReaderRemote#newBlockReader

JIRA: HDFS-16232
Add some parameter descriptions for BlockReaderRemote#newBlockReader.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
16m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m 52s

trunk passed

+1 :green_heart:
compile
0m 58s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
0m 49s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
0m 26s

trunk passed

+1 :green_heart:
mvnsite
0m 57s

trunk passed

+1 :green_heart:
javadoc
0m 40s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 33s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 32s

trunk passed

+1 :green_heart:
shadedclient
23m 40s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 47s

the patch passed

+1 :green_heart:
compile
0m 53s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
0m 53s

the patch passed

+1 :green_heart:
compile
0m 42s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
0m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 17s

the patch passed

+1 :green_heart:
mvnsite
0m 47s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 27s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 38s

the patch passed

+1 :green_heart:
shadedclient
23m 22s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 14s

hadoop-hdfs-client in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

114m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3456/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3456

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 30739e155999 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2fa9e973709092e46ff2a5209808094c8dc5ade1

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3456/1/testReport/

Max. process+thread count
522 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-client U: hadoop-hdfs-project/hadoop-hdfs-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3456/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Hi @tasanuma @Hexiaoqiao , please help review this change. Thanks a lot.

Looks like it just adds period to each of the sentences. +1

I added several parameter description. Thanks @jojochuang for your review.


Change max upload size

This can be done by changing the configuration in the /etc/php5/fpm/php.ini file:
upload_max_filesize = 200M
post_max_size = 200M

:+1:

@vikbez please give a look at #13, I need some :+1: on the PR before merging it upstream