Proxy not working

Hi - As you described I deployed on linux and tried. but seems not working. Where Can I see the log?
I am pretty much intersted this project to add intercept https sites.

what did you do?
Did you follow the USAGE.md instructions?
Which browser do you use?
What are your proxy settings and what host OS do you use?

Yes. I did same instruction. I tested  port is listening too... But no response

or internet activity

I have the same problem. Tested with XFCE on ubuntu server 16.04 (AWS image)

For the sake of completeness:

I've been busy for the last couple months.
I've been building a Web Browser instead, because Web Proxies cannot filter out HTTPS-requested URLs and SOCKS is nothing more than a socket-routing-protocol.
This project is now deprecated, new project is called stealth-browser which can be used as an ad-blocking Web Proxy, too (among various other features that the new architecture allows).


Process leak between experiments

Hello. I noticed a process leak while continuously monitoring processes using this command: while true ; do ps aux | grep python ; sleep 1 ; done. The process pool starts to increase and, at a certain point, the benchmark script becomes unresponsive and eventually times out. This issue might impact the benchmark result, as the processes consume a significant amount of CPU time.

My command was:
python run.py --engines 'qdrant-*'

Got it. I'll submit a PR soon.

Unfortunately, My fix did not work.

It was fixed for me by overriding get_mp_start_method of QdrantUploader.
@classmethod
def get_mp_start_method(cls):
    return "forkserver" if "forkserver" in mp.get_all_start_methods() else "spawn"

It turns out to setting environment variables to enable grpc fork support solves the issue.
https://github.com/grpc/grpc/blob/master/doc/fork_support.md#current-status


OpenVPN auth-gen-token

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

Is your feature request related to a problem? Please describe.
To allow clients to authenticate with an OTP as part of their password, reneg-sec has to be set to 0.
This allows users to stay connected longer than 1 hour.
But to allow ping-restart auth-gen-token is needed, as the OTP is invalid at this time.
Basically: https://forum.opnsense.org/index.php?topic=25124.0
Describe the solution you like
Add auth-gen-token to OpenVPN Server Configuration
Describe alternatives you considered
Setting the option in the advanced configuration - but the field says it will be deprecated.

This would be really nice to have. Especially in combination with auth-gen-token-secret. This way we could use roaming between multiple OPNsense devices while using passwords that contain OTP tokens.

Thanks 🙂

Hi,
this feature is not completely implemented.
Because my answer in forum was just one day after this unknown patch I checked my interface why I have overseen this still in last months...
=>  compared to renec-sec it's missing in some PHP web files to get configured:
root@fw01:~ # grep -rl reneg-sec /usr/local/
/usr/local/sbin/openvpn
/usr/local/opnsense/mvc/app/models/OPNsense/OpenVPN/OpenVPN.php
/usr/local/opnsense/mvc/app/models/OPNsense/OpenVPN/OpenVPN.xml
/usr/local/opnsense/mvc/app/controllers/OPNsense/OpenVPN/forms/dialogInstance.xml
/usr/local/opnsense/mvc/app/library/OPNsense/OpenVPN/TheGreenBow.php
/usr/local/opnsense/mvc/app/library/OPNsense/OpenVPN/PlainOpenVPN.php
/usr/local/include/openvpn-plugin.h
/usr/local/www/vpn_openvpn_server.php
/usr/local/www/vpn_openvpn_client.php
grep: /usr/local/openssl/misc/tsget: No such file or directory
/usr/local/etc/inc/plugins.inc.d/openvpn.inc

in the $copy_fields; $init_fields variables and also in the table part with help entries in server, client and client export pages:
root@fw01:~ # grep -rl auth-gen-token /usr/local/
/usr/local/sbin/openvpn
/usr/local/opnsense/mvc/app/models/OPNsense/OpenVPN/OpenVPN.php
/usr/local/opnsense/mvc/app/models/OPNsense/OpenVPN/OpenVPN.xml
/usr/local/opnsense/mvc/app/controllers/OPNsense/OpenVPN/forms/dialogInstance.xml
grep: /usr/local/openssl/misc/tsget: No such file or directory

PRs welcome :)

To be blunt posting a random full configuration blob and not saying where which particular setting is missing is not helpful.
Steps to reproduce from GUI + expected (configuration file) outcome is required for a sane bug report.

Sorry, forgotten to ask if the missing part of auth-gen-token which is from this PR missing should be a standalone patch or can be included in bigger one


md-slider thumb position does not move when value is updated by external data source

Bug, feature request, or proposal:
Bug
What is the expected behavior?
The slider's thumb position should be updated when an external data source updates the value of the md-slider.
What is the current behavior?
The slider's thumb position is not updated when an external data source updates the value of the md-slider.
What are the steps to reproduce?
Please refer to this plunk: http://plnkr.co/edit/sZHhzGHu5vg2lyj7B0On
I'm using property binding to link the AppComponent class's data property into a target element property (the md-slider).
Note that when an external data source (simulated in the plunk by an input field) changes the component's "level" property, the value of the md-slider (shown to the right of the slider) DOES update.
However the graphical md-slider thumb element DOES NOT update its position.
What is the use-case or motivation for changing an existing behavior?
It's a bug.
Which versions of Angular, Material, OS, browsers are affected?
Angular 2.0 final.
@angular2-material/slider - v2.0.0-alpha.8-2 - Angular 2 Material Slider
Server is running linux.
Browser is running on Windows 7, Chrome v53.0.2785.116 m
Is there anything else we should know?

Hi @jelbourn,
Please forgive me if my assumptions are incorrect.
I noticed that this issue was marked as fixed in release 2.0.0-alpha.10.
I assume that this release now becomes the default for newly-created plunks, such as this one I just made to test the fix:
http://plnkr.co/edit/IojSZiv89EVPotxUr1u0
However the behaviour has not changed - the slider still doesn't move when the value binding changes.

@danny-swimmer I don't believe the plunker has been updated yet.


Don’t break $XDG_DATA_DIRS

Fixes #70

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

1 of 2 (50.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 82.932%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/hooks/useShellEnv.ts
1
2
50.0%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.06%

Covered Lines:
2442

Relevant Lines:
2880

💛  - Coveralls


Searching for a gene on beta

Walking through the old tutorial and looking trying to find the protein family for the mcr-1 genes.  It has not been a pleasant experience.  First I did it without filtering on the global search, which returned 11279 genomic features:

Then I filtered on genomic features (why oh why can't we just call them genes???) and it returned the most confusing page I have ever seen, as well as 11460 hits.  Why the discrepancy?

I understand what you're trying to do, but forcing the user to look at these graphs (which are somewhat confusing) and making them first FIND the tab to get them to the features and then CLICK on that is like making somebody watch an add on YouTube before letting them see their video.  Its more frustrating than rewarding.

The count portion of this ticket is referencing #972

from the global search result, linking to features tab may make more sense. Especially these two profiles are summary of top 10 function/taxon.  Dustin, would you change that? I guess you're working the global search.

Yep, I already changed it where it says Genome Features in the top N results…I forgot to change it in the summary at the top, but have fixed it locally already.

On Oct 6, 2016, at 3:43 PM, hyoo<EMAIL_ADDRESS>wrote:
from the global search result, linking to features tab may make more sense. Especially these two profiles are summary of top 10 function/taxon. Dustin, would you change that? I guess you're working the global search.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/PATRIC3/patric3_website/issues/966#issuecomment-252067910, or mute the thread https://github.com/notifications/unsubscribe-auth/AALobleIFt7-lN6EwnRe_lyh6BAVeuTZks5qxU9_gaJpZM4KPRgy.

fixed on beta.


Provide Example for az account create with multiple --owner-upn args

It would be really helpful if you would provide a sample call for az account create if i want to pass multiple --owner-upn

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

ID: 9abfaa54-0895-29f7-f3bb-ff604912b2ac
Version Independent ID: d1ff3478-8a86-59e4-62ef-449900132a67
Content: az account
Content Source: latest/docs-ref-autogen/account.yml
Service: azure
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@jiasli for awareness


fix(pl.json): added polish fonts, grammatical corrections

Hi arturspiewak,
thanks for the pull request :smiley:
Cheers
Sebastian


Revert "parse bitmap for subdoc connectedbuilding"

This reverts commit 2952a7ac509ebb342cebf1a0e198f970422ea453.

Copyright scan failure
Commit: 67dff1fe8bed5ed2ce1f291faf16acd020663a00
Report detail: https://gist.github.com/rdkcmf-jenkins/0695771c87631278e493ea8c32c2a055

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/webconfig/106/rdkcentral/webconfig

Commit: 67dff1fe8bed5ed2ce1f291faf16acd020663a00

Report detail: gist


Add theme hugo-theme-relearn

Is anything wrong about my PR? Just wondering because all other open PRs but mine are merged?
Just for information: I forked the original Learn theme, because it's stalled for quite some while.

Hello Sören,
thanks for your theme submission. Relearn seems to be a fork of the learn theme that is also listed on www.themes.gohugo.io. Hugo users could find both themes but will not immediately able to understand how they relate to each other, i.e. that relearn is a fork. It might also be of interest for them to know what changes or additions have been made in your fork. This kind of information should be visible in the README of your theme.

Thank for the information. I'll provide some additions in the README in the next few days.

I'll provide some additions in the README in the next few days.

As always, software projects take longer than intended.
Because this theme is meant to be a drop-in replacement of the original learn theme, it visually looks very similar by intent.
I've added a short "motivation" statement in the README.md and prominently in a notice box on the front page of the theme's documentation, giving the main reason behind my fork. This box even shows up in the screenshots, that will be shown in the theme repo.
Additionally I've added a lot of links to the original theme - even in the theme.toml giving credits to the orignial theme and providing a changelog and migration instructions.
Version 2.0.0 of my fork was released a few hours ago. It alone fixes 27 issues, many of them are long outstanding in the original learn theme. And that's only for the latest release - not counted the issues fixed in previous (smaller) releases.
Don't get me wrong: Forking the theme wasn't a light decision and loomed in me for almost a year. I've made proposals on how to revive the development multiple times but with no success. Even other users are discussing the theme's state to no success (see matcornic/hugo-theme-learn#502, matcornic/hugo-theme-learn#505). I've made PRs, code reviews and giving help in the issues comments with almost no reaction from the mentainers.
Although the theme repo mentions the last update to be on 2021-03-31, the commit history shows a different picture.
I am more than willing to dump my fork if the development of the original learn theme comes up to speed again. But for the moment the learn theme is dead.
I hope the information given, help to make a positive decision for including my fork in the theme repo.

@bep, @digitalcraftsman : Given my previous explanation, is there at least a chance to get listed in the theme gallery? Is there something else I can do to get listed?


Error creating AppSync Function: NotFoundException: No data source found named <config_gw_resolver>

Description
In a single run, it is not able to create data sources along with app sync resources. we have to run terraform 2 times for this.
Please provide a clear and concise description of the issue you are encountering, your current setup, and what steps led up to the issue. If you can provide a reproduction, that will help tremendously.
module "appsync" {
  source = "terraform-aws-modules/appsync/aws"
  name   = "config_gw"

  schema = file("${local.files_root_path}/config-gw-graphql/schema.graphql")

  authentication_type = "AMAZON_COGNITO_USER_POOLS"
  user_pool_config    = {
    user_pool_id        = var.investigator_users_pool_id
    app_id_client_regex = var.investigator_client_id
    aws_region          = var.aws_region
    default_action      = "ALLOW"
  }

  additional_authentication_provider = {
    user_pool_config = {
      user_pool_config    = {
        user_pool_id        = var.monitoring_app_user_pool_id
        app_id_client_regex = var.monitoring_app_client_id
        aws_region          = var.aws_region
        default_action      = "ALLOW"
      }
      authentication_type = "AMAZON_COGNITO_USER_POOLS"
    }
  }

  datasources = {
    config_gw_resolver = {
      type         = "AWS_LAMBDA"
      function_arn = aws_lambda_function.config_gw_resolver.arn
    }

    none_source = {
      type = "NONE"
    }
  }

  functions  = local.functions_body
  resolvers  = local.resolver_body
}

⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Terraform:

Provider(s):

Module:

Reproduction

Steps to reproduce the behavior:

Code Snippet to Reproduce

Expected behavior

Actual behavior

Terminal Output Screenshot(s)

Additional context

depends_on = [aws_appsync_datasource.this]


sphinx-panels package not longer maintained

📰 Custom Issue

The sphinx-panels package is now no longer maintained.

The sphinx-panels package is also pinning our dependency tree back to using sphinx v4.5.0, which is rather dated. The latest release of sphinx is now v6.0.0, which was just released on 29 Dec'22.

We should investigate migrating away from sphinx-panels to using sphinx-design instead 🚀

Ping @tkknight ... you up for a bit of this? 🤔

@ESadek-MO Did we want to consider pulling this into iris 3.5.0 release ?
Worth discussing perhaps...


Freezes on xorcrypt cipher

⚠IMPORTANT⚠ if you do not fill this out, we will automatically delete your issue. We will not help anyone that cannot fill out this template.

[X] Have you read our Wiki page "Common Issues & Their Solutions"?

Describe the bug
A clear and concise description of what the bug is.
Ciphey freezes on ciphey -t "tJseAuuesGnosMauFYtogoHdHTeYCnaeMAve" when "Trying xorcrypt cipher".
Seems very similar to issue #395.
Version
⚠IMPORTANT⚠ We need this information because different environments will induce different bugs in Ciphey

OS/Distro: Arch
Python version: Python 3.9.2
Ciphey versions:

Version: 5.11.1
Summary: Automated Decryption Tool
Home-page: None
Author: Brandon
Author-email<EMAIL_ADDRESS>License: MIT
Location: /usr/lib/python3.9/site-packages
Requires: click-spinner, pyyaml, cipheycore, base58, flake8, base91, click, appdirs, yaspin, pylint, loguru, rich, cipheydists, pybase62
Required-by:
---
Name: cipheycore
Version: 0.3.2
Summary:
Home-page: None
Author: Cyclic3
Author-email<EMAIL_ADDRESS>License: None
Location: /usr/lib/python3.9/site-packages
Requires:
Required-by: ciphey
---
Name: cipheydists
Version: 0.3.34
Summary: A collection of distributions, character sets and dictionaries for use in ciphey
Home-page: None
Author: Cyclic3
Author-email<EMAIL_ADDRESS>License: None
Location: /usr/lib/python3.9/site-packages
Requires:
Required-by: ciphey

I also tried the latest git version (commit hash: 1ebec53cf505dd6eac770cdf15fa0c6e596b5001)

Did you use Docker?
No
Verbose Output
https://gist.github.com/hkatzdev/fb09bd054a251bd45ecb2023fd580e4e

To Reproduce
Steps to reproduce the behavior:

What input did you use?: tJseAuuesGnosMauFYtogoHdHTeYCnaeMAve
What flags / arguments did you use?: I tried with -t, -vvv, and -crib. No success with any of them.

Expected behavior
For the program to either crack the cipher or say it can't crack it.

Hey, this is fixed in 6.0.0 where we remove the xorcrypt cipher 😅  https://github.com/Ciphey/Ciphey/issues/591

Oh, sorry! I'll close this issue then.


Orientation not working on iOS

We have tried to lock the camera from rotating.
We have tried either:

by setting the property orientations
barcodePicker.orientations = [Scandit.BarcodePicker.Orientation.Portrait]
or
by using the setOrientations function
barcodePicker.setOrientations([Scandit.BarcodePicker.Orientation.Portrait])
Neither of them are taken into account and as a result the camera keeps rotating.
Has anyone bumped into this?

We are using the latest scandit plugin for phonegap. The application is built using ionic 3.

Any issue with the orientations should have been fixed with #221 which is part of the latest 5.11 release. The previous 5.10 release did not contain this fix yet. Are you sure that you are on the latest version which is 5.11.1?

I grabbed the latest version and it works. Thank you!


Add additional information on which API products to enable for Google.

I'm sorry but I'm going to have to decline this change.
The attention block tells only about the deprecation of api-key-less access, and it's been 2 years since that change so that block should rather be removed completely than be updated.
The required API names are already mentioned in the api_key doc: geopy.geocoders.GoogleV3.__init__


LCFS - BUG Test environment calculation incorrect for one of the electricity options

Describe the Bug
In the LCFS Test Environment, the input for Electricity, Diesel, Ground Support Equipment, Default is not calculating Compliance Units correctly. This line is not following the standard compliance unit calculation formula used for all other fuel supply reporting lines.
Expected Behaviour

The compliance unit calculation for Electricity, Diesel, Ground Support Equipment, Default should use the same formula as all other fuel supply reporting lines
The calculated compliance units should align with the correct inputs provided in the fuel supply reporting line.

Actual Behaviour

The compliance unit calculation for this input is incorrect and does not follow the standard formula.
This discrepancy leads to inaccurate compliance unit reporting for this input type.

Implications
Incorrect compliance unit calculations may result in errors in reporting and compliance assessment.
Users may lose confidence in the accuracy of the system, especially during testing in the LCFS Test Environment.
Steps To Reproduce
Steps to reproduce the behaviour:
User/Role: BCeID

Navigate to the Fuel Supply Input Table in the LCFS Test Environment.
Enter data for Electricity, Diesel, Ground Support Equipment, Default, including energy content, target CI, and fuel CI.
Observe that the calculated compliance units are incorrect and do not align with the standard formula.

Hi @dhaselhan I have added all the default options to dev environment test account LCFS6 in a fuel supply compliance report. You can see the discrepancy there between the compliance unit calculation and what is listed in this spreadsheet. The spreadsheet compliance unit calculation is correct:
Line by line fuel supply entry (3).xlsx

The only ones missing are the "Other" fuel type scenarios. I'll have to come up with some scenarios to test this.


Fix wire format for negative int32 values

According to https://developers.google.com/protocol-buffers/docs/encoding#signed-integers, negative int32 values should be encoded differently:

If you use int32 or int64 as the type for a negative number, the resulting varint is always ten bytes long – it is, effectively, treated like a very large unsigned integer.

However CodedBufferWriter does not distinguish between negative and positive values, and this may cause problems when protos encoded by Dart are decoded by other proto implementations.
To update expected bytes in codec_test I used encoded bytes produced by C++ protobuf implementation.

Good catch!

Also updated a change log. How do I get it merged?

Thanks!


Loaders give [object object] instead of checkpoint or lora name

Loaders give [object object] instead of checkpoint or lora name. The do work when pressing queue prompt only not seeing name and image. My folders are generated with Automatic1111 and the Civitai extension.

same question

Same here. Standard ComfyUI installation. Thanks for any comments or help.

ComfyUI .  You must put the model files you ues into checkpoints/ folder.

I have a problem with Safari on my Mac.


OSQP solver does not accept initial variable values with warm start

In some other issue responses, it has been suggested that starting values can be supplied to a solver by setting the values of variables before solving, and setting warm_start=True, for solvers that support warm start.  For the OSQP solver, warm start is supported and at the low level the solver can accept initial values, but setting variable values before calling the solver does not cause them to be used for an initial warm start.  Warm start with the OSQP interface currently works only for repeated solves with the same problem object, not for supplying an initial guess.  It appears that this could work, but is not implemented.
no-initial-start-with-osqp.zip
The following is the output from the attached example, which runs OSQP on a problem that has been simplified to be a pure LP.  We can see that warm start works between runs, and that supplying a set of optimal variable values at the low level usually causes the number of iterations to be much smaller than a full solve (not on every run though), but trying to supply the suggested values through the values of the variables does not work.  (I assume that the difference in objective value is because I have not figured out how to inject the values into the normal process that would include an unpacking step.)
This is running on Ubuntu with cvxpy 1.0.25.
-- Find a solution for this simplified LP-only problem:
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
-- With freshly created problems, we may see variation but the iteration count is high:
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem: optimal, objective -6752.7757895248415, 28475 iterations
fresh problem: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem: optimal, objective -6752.7757895248415, 28475 iterations
-- With reusing the same problem for warm start, the iteration count is tiny as expected:
reused problem: optimal, objective -6752.775789524827, 25 iterations
reused problem: optimal, objective -6752.775789524774, 25 iterations
reused problem: optimal, objective -6752.775789524785, 25 iterations
reused problem: optimal, objective -6752.775789524899, 25 iterations
reused problem: optimal, objective -6752.775789524937, 25 iterations
reused problem: optimal, objective -6752.775789524898, 25 iterations
reused problem: optimal, objective -6752.775789524795, 25 iterations
reused problem: optimal, objective -6752.775789524822, 25 iterations
reused problem: optimal, objective -6752.775789524884, 25 iterations
reused problem: optimal, objective -6752.775789524901, 25 iterations
-- Trying to supply initial values through initial warm start is not effective:
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 28475 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
fresh problem with xsol: optimal, objective -6752.7757895248415, 14500 iterations
-- The low-level interface has similar behavior to freshly created problems:
fresh problem low-level: solved, objective -6910.584676696744, 14500 iterations
fresh problem low-level: solved, objective -6912.147878322633, 28475 iterations
fresh problem low-level: solved, objective -6910.584676696744, 14500 iterations
fresh problem low-level: solved, objective -6910.584676696744, 14500 iterations
fresh problem low-level: solved, objective -6912.147878322633, 28475 iterations
fresh problem low-level: solved, objective -6910.584676696744, 14500 iterations
fresh problem low-level: solved, objective -6912.147878322633, 28475 iterations
fresh problem low-level: solved, objective -6910.584676696744, 14500 iterations
fresh problem low-level: solved, objective -6910.584676696744, 14500 iterations
fresh problem low-level: solved, objective -6910.584676696744, 14500 iterations
-- The low-level interface accepts the initial solution and usually does fewer iterations:
fresh problem with xsol low-level: maximum iterations reached, objective -9918.64547338846, 30000 iterations
fresh problem with xsol low-level: maximum iterations reached, objective -9918.64547338846, 30000 iterations
fresh problem with xsol low-level: solved, objective -6696.279108862777, 4225 iterations
fresh problem with xsol low-level: solved, objective -6696.279108862777, 4225 iterations
fresh problem with xsol low-level: solved, objective -6696.279108862777, 4225 iterations
fresh problem with xsol low-level: solved, objective -6696.279108862777, 4225 iterations
fresh problem with xsol low-level: solved, objective -6696.279108862777, 4225 iterations
fresh problem with xsol low-level: solved, objective -6696.279108862777, 4225 iterations
fresh problem with xsol low-level: maximum iterations reached, objective -9918.64547338846, 30000 iterations
fresh problem with xsol low-level: solved, objective -6696.279108862777, 4225 iterations

When I hacked it in a way that handles my simple problem shape (don't know enough to do it correctly):
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 4225 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 4225 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 4225 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 7400 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 4225 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 7400 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 4225 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 4225 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 4225 iterations
fresh problem with xsol hacked: optimal, objective -6752.7757895248415, 4225 iterations

Looking at the code, it appears that the values would need to be carried along in the application of the reduction steps because the inverse-mapping mechanism is designed to map back values rather than locations within the solver variable vector.  I could be wrong.

@edbarton1 the idea that the variable .value fields should supply a warm start for OSQP or any other solver is only something we've discussed. It's not implemented. Could you merge this with the discussion in #849?


PSA - Add @p4runtime_translation for all seven PSA types

Intended to address issue https://github.com/p4lang/p4-spec/issues/730

Given the two approvals, going ahead and merging this in.  Thanks for review.


Missing type forward for JsonResult in ASP.NET Core 3.0?

Also posted as https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/1030
Describe the bug
If an ASP.NET Core 3.0 preview 2 application references Swashbuckle.AspNetCore 4.0.1 and uses the Microsoft.AspNetCore.Mvc.JsonResult anywhere in code, a CS0433 compiler error is generated and the application will not compile.
The type 'JsonResult' exists in both 'Microsoft.AspNetCore.Mvc.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' and 'Microsoft.AspNetCore.Mvc.Formatters.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'

To Reproduce

Create a new ASP.NET Core MVC application using the built-in Visual Studio 2019 template using 3.0.0-preview-19075-0444.
Add the following reference: <PackageReference Include="Swashbuckle.AspNetCore" Version="4.0.1" />
Add the following method to ValuesController.cs: public void Foo(int id) => new JsonResult(new { });
Attempt to compile the application.

Expected behavior
The application compiles cleanly.
Additional context
The issue can be worked around by adding the following to the .csproj file of the project as referenced by https://github.com/NuGet/Home/issues/4989#issuecomment-426666530:
<ItemGroup>
  <PackageReference Include="Microsoft.AspNetCore.Mvc.Formatters.Json" Version="2.0.0" Alias="LegacyAspNetCoreJsonFormatter" />
</ItemGroup>
<Target Name="AddPackageAliases" BeforeTargets="ResolveReferences" Outputs="%(PackageReference.Identity)">
  <PropertyGroup>
    <AliasPackageReference>@(PackageReference->'%(Identity)')</AliasPackageReference>
    <AliasName>@(PackageReference->'%(Alias)')</AliasName>
  </PropertyGroup>
  <ItemGroup>
    <ReferencePath Condition="'%(FileName)'=='$(AliasPackageReference)' and '$(AliasName)' != ''">
      <Aliases>$(AliasName)</Aliases>
    </ReferencePath>
  </ItemGroup>
</Target>

Output of dotnet --info:

.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview-010184
 Commit:    c57bde4593

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview-010184\

Host (useful for support):
  Version: 3.0.0-preview-27324-5
  Commit:  63a01b08e5

.NET Core SDKs installed:
  2.0.3 [C:\Program Files\dotnet\sdk]
  2.1.3 [C:\Program Files\dotnet\sdk]
  2.1.100 [C:\Program Files\dotnet\sdk]
  2.1.104 [C:\Program Files\dotnet\sdk]
  2.1.200 [C:\Program Files\dotnet\sdk]
  2.1.201 [C:\Program Files\dotnet\sdk]
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.300-rc1-008673 [C:\Program Files\dotnet\sdk]
  2.1.300 [C:\Program Files\dotnet\sdk]
  2.1.301 [C:\Program Files\dotnet\sdk]
  2.1.302 [C:\Program Files\dotnet\sdk]
  2.1.400 [C:\Program Files\dotnet\sdk]
  2.1.401 [C:\Program Files\dotnet\sdk]
  2.1.402 [C:\Program Files\dotnet\sdk]
  2.1.403 [C:\Program Files\dotnet\sdk]
  2.1.500 [C:\Program Files\dotnet\sdk]
  2.1.502 [C:\Program Files\dotnet\sdk]
  2.1.503 [C:\Program Files\dotnet\sdk]
  2.1.600-preview-009472 [C:\Program Files\dotnet\sdk]
  2.2.100-preview2-009404 [C:\Program Files\dotnet\sdk]
  2.2.100-preview3-009430 [C:\Program Files\dotnet\sdk]
  2.2.100 [C:\Program Files\dotnet\sdk]
  2.2.101 [C:\Program Files\dotnet\sdk]
  2.2.102 [C:\Program Files\dotnet\sdk]
  2.2.103 [C:\Program Files\dotnet\sdk]
  2.2.200-preview-009748 [C:\Program Files\dotnet\sdk]
  3.0.100-preview-010184 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0-rc1-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.0-preview2-35157 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.0-preview3-35497 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0-rc1-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.0-preview2-35157 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.0-preview3-35497 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview-19075-0444 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-rc1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.0-preview2-26905-02 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.0-preview3-27014-02 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview-27324-5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview-27325-3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Presumably due to this breaking change: https://github.com/aspnet/Announcements/issues/325
I don't think a type forwarder can be use because I thought they could be used only when the type moved to an assembly referenced from the original assembly. In this case clearly that can't happen because the whole idea was to move JsonResult to a new, un-referenced assembly, that the developer has to add a reference to on their own. (I'm happy to be wrong about all this, though.)

@pranavkm, any suggestions?

Type forwarding resolves this specific build error. There are other breaking changes with that specific package, but we expect using JsonResult in user code to work pretty smoothly.

@martincostello if you like testing our previews you can get a new build of .NET Core 3.0 with the SDK here https://github.com/dotnet/core-sdk#installers-and-binaries.

@davidfowl Thanks, I'll try out an updated version with a fix today 👍

I've updated out application to SDK 3.0.100-preview-010240 and packages version 3.0.0-preview-19106-07 and while the compilation error no longer persists with the alias workaround removed, all our self-hosted tests are now getting this error at runtime:
System.TypeLoadException: Could not load type 'Microsoft.AspNetCore.Mvc.MvcJsonOptions' from assembly 'Microsoft.AspNetCore.Mvc.Formatters.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
   at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   at System.Signature..ctor(IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   at System.Reflection.RuntimeConstructorInfo.get_Signature()
   at System.Reflection.RuntimeConstructorInfo.GetParametersNoCopy()
   at System.Reflection.RuntimeConstructorInfo.GetParameters()
   at Microsoft.Extensions.Internal.ActivatorUtilities.ConstructorMatcher..ctor(ConstructorInfo constructor)
   at Microsoft.Extensions.Internal.ActivatorUtilities.CreateInstance(IServiceProvider provider, Type instanceType, Object[] parameters)
   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass4_0.<UseMiddleware>b__0(RequestDelegate next)
   at Microsoft.AspNetCore.Builder.Internal.ApplicationBuilder.Build()
   at Microsoft.AspNetCore.Hosting.Internal.GenericWebHostService.StartAsync(CancellationToken cancellationToken)

Looks like that's actually a different issue, and that's a incompatibility in Swashbuckle.AspNetCore caused by the changes to remove Newtonsoft.Json from the core:
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/blob/c8d8edbf1a04ccf5662ad961fd373adaf0d12e32/src/Swashbuckle.AspNetCore.SwaggerGen/Generator/SchemaRegistryFactory.cs#L13


Support standard AWS SDK Credential mechanisms

The current implementation (since 66298789) requires the controller to get its credentials from a Secret object. Can you make that a conditional only if the secret is defined,  and support the default credential chain? This will allow operators to use standard means like IAM Roles for Service Accounts, secrets as a pod's environment variables. The SDK region should be inferred from the standard configuration points too (env var/config file/IMDS).
It would be really nice to not have to reference a secret to set non-secret values such as the Cert ARN in the provisioner, and just directly state that value.

@sudhindra-hub Is there any preventing this merge? Loading aws credentials from alternative mechanisms  would be a very useful feature.


📝 Add MailCatcher to development.md

Add MailCatcher URLs to docs and fix typo in URLs for API docs accessed through localhost.tiangolo.com.

Thank you! @tobiase :partying_face:


Use Collation for PostgreSQL

This is related to #397 but for PostgreSQL

PostgreSQL uses the collations of the OS and there is no way to use a specific collation for a specific query.
Case insensitive comparisons can be achieved by using the ILIKE operator or regexp comparison using ~ or forcing both compared operands to lower case. The latter seems to be most efficient.
If modifying the database is an option, CITEXT fields can be used, but that is of course not a Speedment option.
Conclusion - using collation in Speedment queries is not an option. The best way seems to be the current implementation using LOWER(cn) = LOWER(?). I suggest we close this issue as won't fix.
See
http://stackoverflow.com/questions/7005302/postgresql-how-to-make-case-insensitive-query
https://www.postgresql.org/docs/9.6/static/functions-matching.html
https://www.postgresql.org/docs/9.6/static/citext.html

Concur


Spring Boot 2.x support

Spring Boot 1.x provided integration with spring-security-oauth project that has been removed in Spring Boot 2.x in favor of Spring Security 5. Spring Boot does not want to provide support for spring-security-oauth going forward since going forward Spring Security 5 is the recommendation for OAuth.
Spring Security 5 plans to provide all the features found in spring-security-oauth, but does not yet do so. For example, it is missing RestTemplate integration, resource server, and authorization server support.
We should provide a jar that provides the Spring Boot 1.x OAuth integration for Spring Boot 2. This jar's life cycle will be maintained along with spring-security-oauth project and allow users to continue to support the workflows they had in Spring Boot 1.x with spring-security-oauth until Spring Security 5 OAuth support is ready to be fully migrated to.

When I add it to Spring Boot 2 project and it works fine, i just dislike the dependency on Jackson 1.

This has been fixed via https://github.com/spring-projects/spring-security-oauth2-boot


Waypoints of Caches shown

The waypoints of caches currently in the viewport are now shown. Next step is to show waypoints in the viewport of caches not in the viewport. Apart from this only comments.

As much concerns I had about this feature, the much I live it now! For me it is one of the big five improvements in the last weeks!
Just wanted to tell...

Thanks. It's still not perfect though since if the parent cache is not in the view scope then the waypoints disappear.


No operation for a long time, no response

Description
No operation for a long time, clicking on the content again takes a long time to respond.
Log information.
024/05/16 07:22:36 routers/web/web.go:120:func9() [E] Failed to verify user: user does not exist [uid: 0, name: OAUTH_USER]
2024/05/16 07:22:36 routers/web/web.go:120:func9() [E] Failed to verify user: user does not exist [uid: 0, name: OAUTH_USER]
2024/05/16 08:23:38 routers/web/web.go:120:func9() [E] Failed to verify user: user does not exist [uid: 0, name: OAUTH_USER]
2024/05/16 08:23:38 routers/web/web.go:120:func9() [E] Failed to verify user: user does not exist [uid: 0, name: OAUTH_USER]
2024/05/16 09:24:41 routers/web/web.go:120:func9() [E] Failed to verify user: user does not exist [uid: 0, name: OAUTH_USER]
2024/05/16 09:24:41 routers/web/web.go:120:func9() [E] Failed to verify user: user does not exist [uid: 0, name: OAUTH_USER]

Gitea Version
1.22.0-rc1、v1.21.11、1.21.10
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.39.3
Operating System
AlmaLinux release 9.2
How are you running Gitea?
systemd
Database
MySQL/MariaDB

Where does OAUTH_USER come from, is it a mask character? 🤔

Where does OAUTH_USER come from, is it a mask character? 🤔

I saw this from the log, but I’m not sure exactly how it happened. @yp05327

Could you give more details about the steps how could you address that.

What are the steps you are mean. @lunny

The steps of reproducing this issue and your settings about oauth2 (maybe) ?

@zuozhehao
Are you using Git Credential Manager?
See #31470 and https://github.com/go-gitea/gitea/issues/31470#issuecomment-2193834944

I'm also having this exact issue in Gitea. After a little while, when I push again, the first time always fails, second time succeeds. im logged in via the vscode -> oauth in browser

We close issues that need feedback from the author if there were no new comments for a month. :tea:


Add More Uniforms

This PR
This pr implements many uniforms based on the uniforms provided by FREX.

And with that, I think this PR is ready for review. Let me know if you think anything is unnecessary or if you think this is missing any uniforms.

Is it necessary to have separate uniforms for matrix inverses if they can be computed manually in the shader? If each shader recalculating the inverse is a performance issue, then the inverses can be kept as standard variables but they can be filled in by an internal shader instead of taking up space in the uniform buffer.

We've used about 1kb of the guaranteed 16kb of space in the frame uniform buffer. Space is not a concern.
Calculating the inverses on the CPU is the standard way to do this because it's by far the simplest solution. I doubt whatever marginal gains of doing the inversion on the GPU would outweigh the complexity.

It would be more consistent if all programs received all uniforms. It makes sense that the cull shader shouldn't need fog values, but I also don't see a reason to not provide them.

I agree, but the fog parameters can change across the frame, right? If it's just the color changing then yeah I don't see an issue, but if the distance/shape is different then which version does the cull shader see? If we were to try and cull instances that were fully occluded by fog would we get any false positives?


[api] Prefer have_http_status()

Replaces expect_request_response_with_no_content,
expect_request_success, expect_user_unauthorized,
expect_request_forbidden, expect_resource_not_found, and some uses of
expect_bad_request with matcher have_http_status().
These helper methods add a layer of indirection which adds to congnitive
load - I can never remember which one of them does something other than
check the response status (it is expect_bad_request, which is left
intact where we're passing the optional argument to check the response body).
@abellotti if you feel strongly the other way I won't have lost much - this was mostly a quick find and replace. I don't feel strongly, but I do prefer the clarity of seeing the matcher (have_http_status) next to the thing it is matching against (response) vs having to remember what the helper method does.
@miq-bot add-label test, refactoring, darga/no
@miq-bot assign @abellotti

I like this so much better...I find the abstracted methods confusing from a RSpec readability perspective.

Thanks @imtayadeway I'm good with this.


Dashboard gives "403 Forbidden" alerts when following Astarte in 5 minutes

The guide Astarte in 5 minutes > Grab your tea suggests to login in the Dashboard with a JWT token generated with:
astartectl utils gen-jwt realm-management -k test_private.pem

This is not sufficient to interact with all APIs the Dashboard support, Devices for instance.
The suggested command to generate the JWT token should be:
astartectl utils gen-jwt all-realm-apis -k test_private.pem

When monitoring a device on the dashboard, the websocket connection request to the appengine-api's /socket/websocket gives 403 Forbidden even when the JWT token is for all realm apis.

@Aetherus when generating tokens with astartectl the default expiry is 5minutes, make sure the token is still valid before connecting to the socket.
If you need longer expiration dates you can use the -e flag and set a custom value (in seconds)
If the token was valid, you can inspect its claims to make sure you have both JOIN and WATCH permission on the Astarte channels
  "a_ch": [
    "JOIN::.*",
    "WATCH::.*"
  ],

If you need a quick inspection tool you can use https://jwt.io/

Closed by #537


Add toggleable div with all taxa in numerator/denominator of log ratio

Might subsume the MathJax single-microbe selections into this

I think this is ready, with the slight exception that it isn't toggleable.
But since the textareas are resizable -- I think this is ok? It's not like it should take up an undue amount of space even when lots of taxa are selected.


Docs: No hard breaks in prose

In reference of https://github.com/jquery/globalize/pull/321/files#r22041598, where @scottgonzalez said:

The prose style guide is scattered. See jquery/contribute.jquery.org#75.
The rule is no hard breaks in prose.

Closing this issue in favor of a super set #471.


When Inventory is not available, Shopify API raises a 500 error with no error message visible

shopify_order = ShopifyAPI::Order.new
shopify_order.line_items = [{ variant_id: 123, quantity: 1 }]
shopify_order.blah = blah blah blah
ShopifyAPI::Session.temp("shop_name.myshopify.com", 'asdfasdfadf') { shopify_order.save }

in some cases, returns to us a ActiveResource::ServerError: Failed.  Response code = 500.  Response message = Internal Server Error. error.
Unfortunately, when we look at shopify_order.errors.messages we see an empty hash.
Similarly, when a zip code is invalid the shopify api will not be persisted, not raise an error, and populate the shopify_order.errors.messages.
This is not consistent behavior.
We had to track down the error message in shopify_api-3.2.1/lib/active_resource/connection_ext.rb where we puts out the response.body and received this.
{"errors":"Inventory not available; Asked for {916977441=\u003E1}, got {916977441=\u003E0}"}

Anyone willing to take a look at this with us?

Ping!

Would anyone at Shopify accept a PR if we worked on one? This continues to be an issue for us.

We definitely accept PRs to this repo!

This would be an awesome update to have.
Here's another case where this bit me, which I've opened a post on the api forums about as there seems to be an issue with update existing order resources that have a validation error.
Basically, the thrown exception is ActiveResource::ResourceInvalid: Failed meanwhile if you log the underlying response, it's a 422 Unprocessable Entity {"errors":{"shipping_address":["last name can't be blank"]}}

Hey folks, we recently shipped a fix which ensures this request responds with 422 instead of 500. 500s are nasty. Better error messages would definitely be considered. Let me know your ideas and I'll see what we can get implemented here.


Us structured logging

See if tracing meets our needs or create Event that serializes to JSON
Remove time from logging if RUST_LOG=info prints this out

Index sync times are important to keep an eye on. If you check the main justfile, you'll see download-log and graph recipes which extract performance information from the logs using a regex. However, this is pretty fragile. It would be nice to use structured logging so we emit events to the log as key/value pairs, and then consume them however we want.
Ideas for first steps:

The log crate has experimental support for structured logging, is it mature enough to use? https://github.com/rust-lang/log/issues/328
Alternatively, define an Event enum that implements Serialize and log that with a prefix (like EVENT: )

We can do this when we have a specific need for it.


adding basic Dockerfile

The bot stopped working few days ago, so I've created a Dockerfile to be able to run it myself.

The bot is down because of server issues. I'll look into it, and this pull request in the morning. Thanks. :)

Sorry for the delay, I was having server issues. :+1:

Thank you!


Sharing bug and correspondance between MRTK-Unity and MRTK  depots

Hi guys
We've updated MRTK to  2<IP_ADDRESS>
We have one nasty bug that crashes the unity editor (2017.4.10) with an access violation in SharingClient.dll (mainly when we go out of Play Mode). This was already present in our setup with 2017.1.2f1 and a MRTK from last year.
I'm trying to have a look on this, so I've built the MixedRealityToolkit (latest version) in debug, and I've replaced the SharingClient.dll with my one.
Alas, it looks like the one I've built is full of MixedRealityToolkit__ functions, instead of the HoloToolkit__ of the MRTK-unity 2017.4.10, so my guess is i've picked the wrong commit.
So which commit should i get to be consistent with MRTK-unity 2017.4.10?
Thank you,
Nicolas

The pre-namespace change commit should be https://github.com/Microsoft/MixedRealityToolkit/tree/cb30bf2ca8a26372fae5ec173ef4e7f3afb6498a/Sharing. If you haven't already, please open an issue on that repo with your bug report as well. Thanks!

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.


Is this module abandoned?

I'm wondering if any development will happen after the v10 Foundry update. This module is really useful to visualize distance in a turn and it would be very disapointing to lose this feature!

No, it is not abandoned, but the update will take some time.
https://github.com/manuelVo/foundryvtt-drag-ruler/issues/221#issuecomment-1236386099

Any way I can help make it go faster?

Eagerly looking forward to this module becoming v10-compatible!


Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!

Bug description
Error: Get Config: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!
Details: Unable to<EMAIL_ADDRESS> libssl.so.1.1: cannot open shared object file: No such file or directory

How to reproduce

run next dev and prisma generate will cause the issue

Environment & setup

OS: Ubuntu (WSL2)
Database: MySQL (Planetscale)
Node.js version: 16.15

Prisma Version
4.0.0

Same type of error
Error: Get Config: Unable to establish a connection to query-engine-node-api library. It seems there is a problem with your OpenSSL installation!
Details: Unable to<EMAIL_ADDRESS>/snap/core20/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /lib/x86_64-linux-gnu/libcrypto.so.3)
Prisma CLI Version : 4.0.0
Ubuntu 22.04 LTS
NodeJS 16.15.1

i have try an old version of my code that is actually in production on server. it was working on the same PC with the same config
npx prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Get config: Unable to establish a connection to query-engine-node-api library
Prisma CLI Version : 3.15.2
i don't understand what is going on
thx

@mjpaquet Your environment changed. See this issue and comment for your specific case: https://github.com/prisma/prisma/issues/13717#issuecomment-1151080267

Thank @janpio it was the problem.
NodeJS was sandbox by Ubuntu Software (Snap)
curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash -
sudo apt-get install -y nodejs

now everything is working

I m using fnm still the same issue.

Have you try to manually install OpenSSL and glibC ?
on my case it was already done

Any update on this? This is a breaking change for us...

glibC

have all this installed... still the same issue

Did some investigation. Ubuntu 22.04 has upgraded libssl to 3, and does not propose libssl1.1

I'm also having this issue on Ubuntu 22.04.

If any of you still having this issue are using Homebrew on your machine, I found out through some very annoying debugging that apparently Homebrew had a higher precedence on my $PATH, and since I had installed other programs with it that depended on the OpenSSL 1.1 binary, my system was defaulting to that as the binary to use for OpenSSL instead of the default installed binary by Ubuntu (in my case Pop OS, a derivative of Ubuntu) in /usr/bin/openssl. Try running openssl version and if you get back OpenSSL 1.1.1p  21 Jun 2022 or something with 1.x in it, that may be your issue. By making sure that /usr/bin had precedence in my $PATH over my Homebrew install, my system used the proper binaries installed by apt (openssl, libssl-dev, and libc6). Very niche issue, but hope this might help save someone else 1+ hours of digging :sweat_smile:

This solved my issue! Thanks very much.

smithbm2316

@smithbm2316
Im having the same issue as you described, can you elaborate a little more what the specific fix is?

Did some investigation. Ubuntu 22.04 has upgraded libssl to 3, and does not propose libssl1.1

What was your solution?

Guys, I had this problem here and I found out that anaconda (which uses python) had the openssl version in 1.1.0, even though I updated the openssl version for my machine in 3.0.2 zsh just couldn't find this version the anaconda. What I did was put the version of my machine as the main version of the system, with this change the prism started working again !!

What I did was put the version of my machine as the main version of the system

Can you be more specific?

My computer had two versions of openssl: an anaconda version 1.1.0 and a 3.0.2 version downloaded from ubuntu. The problem was that Prisma was using the version of anaconda that was out of date and not the latest version that was installed. I solved the problem by taking out the anaconda version and using only the updated version

I meant: Can you be more specific about the steps you took to remove Conda's version of OpenSSL? I see that Conda has installed OpenSSL on my system, but when I run conda uninstall openssl, it wants to uninstall Conda and fails.

Now I get it. Well I found out that openssl was the one for anaconda using the command which openssl which returned the path of the anaconda version. With that I opened the .zshrc (nano .zshrc) and commented out everything I had of anaconda reference. To confirm I used the command which openssl again and now it pointed to the path of the most current version

For folks running Prisma on K8 environments (like GKE, etc) in a container, you will want to use node:16-bullseye-slim (or a similar base image with Debian included) instead of just something like node:16-slim.

Now I get it. Well I found out that openssl was the one for anaconda using the command which openssl which returned the path of the anaconda version. With that I opened the .zshrc (nano .zshrc) and commented out everything I had of anaconda reference. To confirm I used the command which openssl again and now it pointed to the path of the most current version

I can confirm the anaconda installation is having issues with openssl. Now works as a charm.
Thanks

I installed OpenSSL.Light and the problem is gone.
Env: Node 16 LTS, Windows 11.

Anaconda = https://www.anaconda.com/? Can you describe the setup a bit how you get into this situation?

Sure @janpio,
The anaconda installation was overwritten the OpenSSL path on Ubuntu. I highly recommend checking which SSL is being used. which openssl. Then make sure is using the OpenSSL path from the installed version instead of the anaconda itself.
Now you can comment out the anaconda to avoid the collision over the path and you will find all the Prisma commands working correctly.

If you have conda running on base, just go ahead and deactivate it conda deactivate then run npx prisma studio

I had the same issue when running my nodejs+prisma app with Docker.
I was initially using FROM node:16-alpine and after changing to FROM node:16-bullseye-slim it was working again.

For @victorkurauchi and others getting this issue on Alpine Linux (especially in Docker), this comment in another issue pointed out that the latest Alpine strips out legacy OpenSSL APIs. This caused this issue to start occurring for me recently. I was able to fix it without downgrading or cross-grading to bullseye or buster by adding this line to my dockerfile before the npm install command:
RUN apk add --update --no-cache openssl1.1-compat

@zackdotcomputer solution worked for me! Just added this line of code to my Dockerfile and was good to go.
If you divide your dockerfile into different steps (like builder and runner), don't forget to add this line to all of them.
Thank you all!

I had the same issue when running my nodejs+prisma app with Docker.
I was initially using FROM node:16-alpine and after changing to FROM node:16-bullseye-slim it was working again.

Just curious, does anyone know what changed that could have caused this to be come an issue? Our docker image was using a pinned version (ie: 16.x.x-alpine) and it started having this issue sometime within the past few days.

I switched from FROM node:16-alpine to FROM node:16-alpine3.16 and it works for me. It's not a "fix", but it will work for me now.

Looks like something is happening with the library: openssl1.1-compat it is now switched to "dev" status: https://pkgs.alpinelinux.org/contents?file=libssl.so&path=&name=&branch=&arch=
Probably switching between images is an intermediate solution...
Adding line below helped to build the image:
RUN apk add --no-cache libc6-compat
RUN apk add --no-cache openssl1.1-compat-dev

Here is the full docker file:
## Docker file from here: https://github.com/prisma/prisma/issues/12417#issuecomment-1238242374

##########
## DEPS ##
##########
FROM node:lts-alpine AS deps
RUN apk add --no-cache libc6-compat
RUN apk add --no-cache openssl1.1-compat-dev

WORKDIR /app

# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
RUN \
    if [ -f yarn.lock ]; then yarn --frozen-lockfile; \
    elif [ -f package-lock.json ]; then npm ci; \
    elif [ -f pnpm-lock.yaml ]; then yarn global add pnpm && pnpm i; \
    else echo "Lockfile not found." && exit 1; \
    fi

COPY prisma ./prisma
RUN pnpm prisma generate

#############
## BUILDER ##
#############
FROM node:lts-alpine  AS builder
RUN apk add --no-cache libc6-compat

WORKDIR /app

COPY --from=deps /app/node_modules ./node_modules
COPY --from=deps /app .
COPY . .

RUN npm run build

############
## RUNNER ##
############
FROM node:lts-alpine  AS runner

WORKDIR /app

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/dist ./
USER nextjs

CMD ["node", "./main.js"]

Hey everyone, Alberto from Prisma here. For anyone getting this error on Linux Alpine (e.g., on node:alpine or node:lts-alpine), please refer to https://github.com/prisma/prisma/issues/16553#issuecomment-1353302617

I was using node:18-alpine in a VS Code dev container and getting this error. My solution was to switch to node:18, and rebuild the container.

Instalei o OpenSSL.Light e o problema acabou. Ambiente: Nó 16 LTS, Windows 11.

❤👌

Even with OpenSSL installed on my machine (I have installed it through Brew), that's what solved for me (Ubuntu 22.04):
https://stackoverflow.com/a/72633324/1747282

Hey @diaraujo13, would you happen to have a Dockerfile describing your machine state? We're aware of OpenSSL detection issues on Ubuntu when using Homebrew, but were unable to reproduce them. Please see this comment for an example.

There's a few different issues in this thread, but all or most of them seem to be fixed already. OpenSSL version detection when Homebrew or Anaconda is installed should be fixed as of Prisma 4.9.0, and support for OpenSSL 3 on Alpine was added in Prisma 4.8.0. One thing I'm not quite sure about and need to check is @mjpaquet's report of Prisma not working with Node.js installed via snap — but this is a completely different problem than the other ones in this GitHub issue and needs to be extracted to a separate issue since it's not trackable as a comment here.
I'm going to go ahead and close this issue, please let us know if I missed something and it needs to be reopened, or open a new issue if you run into any problems!

fixed by running npm remove prisma and then npm install prisma problem solved :+1:


Materials imported from a 3D model file should use ".tres" instead of ".material"

Godot version: 3.2.2 beta
Issue description:
I noticed that when I imported a 3D model (GLTF .glb), Godot created materials, but they were using the binary .material format. I think it would be much better to import materials into the .tres format, since this is how Godot offers to save materials by default when doing so manually, and also because .tres is much more friendly to version control and usually a smaller file size anyway.

I'm fairly sure this is a duplicate of another issue, but I can't find it right now.

Here's my other issue about it. https://github.com/godotengine/godot-roadmap/issues/30

@aaronfranke Can you ensure there's a proposal for this?

This issue is now obsolete as of the new import workflow in Godot 4.0, 3D model files like .glb no longer have their materials saved to separate files, and there is no extract option anymore (but there is a "use external" override feature). Saving materials in the inspector offers to save as .tres first. Therefore, I am closing this issue as fixed in Godot 4.0.


400 Bad Request; Please wait a few minutes before you try again.

Bug Report
Form
Requirements

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version

Platform

[x] I'm using Node.js version v16.14.2

Description
After a short period of time, when I make changes, this error occurs to me
I lost one of my Instagram accounts and whenever I tried to log in, this error was displayed Please wait a few minutes before you try again.
I created a new account, the same thing happened again, but my account was not closed, but the problem is still there.
I read other issues and did not see the correct solution
Code
const instagram = async () => {
  const ig = new IgApiClient();
  ig.state.generateDevice(process.env.IG_USERNAME);
  try {
    const loggedInUser = await ig.account.login(
      process.env.IG_USERNAME,
      process.env.IG_PASSWORD,
    );
  } catch (e) {
    throw e;
  }
};

Error and Output
node:internal/process/promises:279

             triggerUncaughtException(err, true /* fromPromise */);
            ^

IgResponseError: POST /api/v1/accounts/login/ - 400 Bad Request; Please wait a few minutes before you try again.
    at Request.handleResponseError (C:\Users\mmdzov\Desktop\test\insta\node_modules\instagram-private-api\dist\core\request.js:126:16)
    at Request.send (C:\Users\mmdzov\Desktop\test\insta\node_modules\instagram-private-api\dist\core\request.js:54:28)

It is common error. Change IP or wait 1+ hour

@kingbotss Your solution is common and has been mentioned in other issues, even if it works for some it's pretty stupid. First, we need to understand why such an error occurs in this library, then look for a guaranteed and permanent solution. This issue should be there so that if someone ever encounters such a problem, they can find the solution from here.

It is common error. Change IP or wait 1+ hour

Your solution is common and has been mentioned in other issues, even if it works for some it's pretty stupid. First, we need to understand why such an error occurs in this library, then look for a guaranteed and permanent solution. This issue should be there so that if someone ever encounters such a problem, they can find the solution from here.

He is right.
Sometimes, the problem is not related to the API itself. If you are running you application on a webserver, you should know that Instagram often blocks IP addresses from datacenters. The cheaper the server, the easier it is for Instagram to block.
If you need a solid infrastructure to run your app, make sure to build your own 4g mobile proxy network.

@nofearlz
I tried various methods and all failed, including changing the IP address.
I tried without vpn and proxy.
I Tried with shadowsocks.
I tried with vpn.
Every time this error occurred and it was fixed after hours, I changed my way of trying.
I did not hear anything about the 4g proxy network! Can you explain more how to do it?
The next question is, why does this happen on cheap servers?

@nofearlz I tried various methods and all failed, including changing the IP address. I tried without vpn and proxy. I Tried with shadowsocks. I tried with vpn. Every time this error occurred and it was fixed after hours, I changed my way of trying. I did not hear anything about the 4g proxy network! Can you explain more how to do it? The next question is, why does this happen on cheap servers?

Give it a try: https://soax.com/pricing-page . Get a mobile proxy plan, 3Gb is enough to test. Use proxies as close as you can from your real address.

The next question is, why does this happen on cheap servers?

Because a lot of ppl used it in the past to automate engagement actions (like, follow, comment). Instagram flagged the whole ARN from those servers...

@nofearlz
It has expensive plans.
Do you think there is another way to avoid this problem?

Because a lot of ppl used it in the past to automate engagement actions (like, follow, comment). Instagram flagged the whole ARN from those servers...

I realized! Therefore, this has caused problems for developers. Finally, the only way developers have is to use expensive servers to run projects?

I realized! Therefore, this has caused problems for developers. Finally, the only way developers have is to use expensive servers to run projects?

No. It's not the only way. But if you are willing to use many accounts, keep in mind that you'll need a service like that (Or build your own 4g mobile proxy network, like https://proxidize.com/ )
For test purpose, you can use your own IP address as proxy with MITMProxy. If you start to get errors, restart your modem to get a fresh IP addr.

@nofearlz
No, I do not intend to use many accounts.
What do you think about Proxidize Free plan?

For test purpose, you can use your own IP address as proxy with MITMProxy. If you start to get errors, restart your modem to get a fresh IP addr.

Do you think using MITProxy locally and on the server alone can prevent this problem?

What do you think about Proxidize Free plan?
They are great. It will do the job.

Do you think using MITProxy locally and on the server alone can prevent this problem?
There is a small trick, but it may result in challenge/block: You can login locally and then move your cookies/sessions to the server.

What do you think about Proxidize Free plan?

They are great. It will do the job.

Do you think using MITProxy locally and on the server alone can prevent this problem?

There is a small trick, but it may result in challenge/block: You can login locally and then move your cookies/sessions to the server.

You May be logged out on server, use proxy on server.

@nofearlz

There is a small trick, but it may result in challenge/block: You can login locally and then move your cookies/sessions to the server.

The matter became very complicated :((

@kingbotss
I apologize if I was rude above.
I'm really confused, I want to have a useful conclusion from all the talks, but in the end, I feel that there is no definite and correct decision :(( I don't know what to do anymore.

You have to try different proxies, use what is working for you.
If you host script on server, you should use proxy.
working proxy types residential, mobile, backconnect.
For good results  use accounts which had 2fa/SMS/Email verification.

@kingbotss
Backconnect is good, but unfortunately it costs money.
Can I find free?
I saw that backconnect is special for these cases, but can it guarantee that I won't have this problem?
What do you think about smart proxy?

@kingbotss
Backconnect is good, but unfortunately it costs money.
Can I find free?
I saw that backconnect is special for these cases, but can it guarantee that I won't have this problem?
What do you think about smart proxy?

For good results use accounts which had 2fa/SMS/Email verification.

What do you mean by this? I mean, should I use services that support these things?

Proxy: test  test test
Use what is working for you. Sadly, any free proxy will not work. But you can buy proxies.
2fa: If you get challenged, your account safe.

@kingbotss
Thank you
I tried using Proxycrawl  during this period
I was going to put this as a system proxy or ig.state.proxyUrl but I couldn't figure out the correct format to put it in.
I have a cURL but I don't know how to use it
Nothing is written about this in the document
It is similar to the following
curl -x "http://wkx***********IqLRmOA@smartproxy.proxycrawl.com:8012" -k "http://httpbin.org/ip"
How do I use this structure to apply proxy?

You have to use in proxyUrl
Format
http(s)://username:password@host:IP
or
http(s)://host:IP

@kingbotss
If it is not necessary that it must be https, I used the first format and received something like this. Do you think the problem might be where it comes from?
IgResponseError: POST /api/v1/qe/sync/ - 520 ; CSRF token missing or incorrect

That depends on proxy.
Maybe you can close the issue.

@kingbotss
It is possible that the reason for this error is the repeated execution of ig.account.login() in development?
Because every time a refresh is performed, a login occurs, so I thought this could cause this error.

Did you checked my forked repo? Have a look at. Maybe be you can reuse session.

@kingbotss
I see.
Can you give an example of session reuse?

@kingbotss I see. Can you give an example of session reuse?
Edit: Could this  be an example of session reuse?

Yes. Since new API uses headers based authentication


test: synchronizing json spec

What
APM agent specs automatic sync
Why
Changeset

https://github.com/elastic/apm/commit/c379ad0 Extend json-specs tests with cgroup-parsing (https://github.com/elastic/apm/pull/686)

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-09-26T07:50:52.875+0000

Duration: 33 min 11 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
4986

Skipped
3338

Total
8324

:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

:globe_with_meridians: Coverage report

Name
Metrics % (covered/total)
Diff

Packages
100.0% (66/66)
:green_heart:

Files
100.0% (225/225)
:green_heart:

Classes
100.0% (225/225)
:green_heart:

Lines
89.808% (17473/19456)
:+1:

Conditionals
77.144% (3193/4139)
:+1:


Webpack 5 uses dramatically more memory than Webpack 4

Bug report

What is the current behavior?
We’ve been unable to migrate Zulip from webpack 4 to webpack 5 due to an enormous memory usage regression. Memory usage is important to us because many of our users are on VMs with just 2 GB RAM.
In an effort to debug this with as few variables and moving parts as possible, I deleted everything except our JavaScript and an extremely minimal nucleus of the webpack configuration. Then I ran each version of webpack several times, deleting the output and cache directories before each run. I observed that webpack 5 uses nearly 4 GB of memory on this benchmark, while webpack 4 used just 500 to 800 MB.
// webpack.config.js
const assets = require("./tools/webpack.assets.json");

module.exports = {
    mode: "production",
    context: __dirname,
    entry: assets,
};

If the current behavior is a bug, please provide the steps to reproduce.

Other relevant information:
webpack version:  5.38.1
Node.js version: 14.17.0
Operating System: NixOS 21.11
Additional tools: yarn 1.22.10

Webpack5 cache is in memory by default in development mode, you can disable the cache with false, or put it on disk

@myNameIsDu As you can see, I’m in production mode, so the cache is already disabled. (I tried cache: false anyway, and as expected, it has no effect.)

By bisecting commits in webpack and terser-webpack-plugin, I was able to attribute most of the memory usage regression to webpack-contrib/terser-webpack-plugin#344.
I found that patching terser-webpack-plugin to remove enableWorkerThreads: true reduces memory usage back to the range of Webpack 4, without a noticeable performance impact.
@alexander-akait FYI.
$ node_modules/.bin/webpack --version
webpack 5.38.1
webpack-cli 4.7.2
$ sed -i '/enableWorkerThreads/d' node_modules/terser-webpack-plugin/dist/index.js
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack-cli --stats=errors-only
311.26user 5.43system 0:36.25elapsed 873%CPU (0avgtext+0avgdata 675108maxresident)k
0inputs+23704outputs (0major+1511627minor)pagefaults 0swaps
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack-cli --stats=errors-only
312.24user 5.60system 0:36.35elapsed 874%CPU (0avgtext+0avgdata 671892maxresident)k
0inputs+23704outputs (0major+1585726minor)pagefaults 0swaps
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack-cli --stats=errors-only
312.78user 5.36system 0:36.48elapsed 871%CPU (0avgtext+0avgdata 675744maxresident)k
0inputs+23704outputs (0major+1549216minor)pagefaults 0swaps
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack-cli --stats=errors-only
310.10user 5.58system 0:36.41elapsed 866%CPU (0avgtext+0avgdata 675936maxresident)k
0inputs+23672outputs (0major+1565916minor)pagefaults 0swaps
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack-cli --stats=errors-only
312.80user 5.57system 0:36.14elapsed 880%CPU (0avgtext+0avgdata 674420maxresident)k
0inputs+23672outputs (0major+1549756minor)pagefaults 0swaps

@andersk What is Node.js version, built-in worker_threads is faster, but there are some regressions in Node.js in some versions (especial on old 10 and 12)

14.17.0 (as specified in my initial report).
I can reproduce the same issue in Node.js 10.24.1 with NODE_OPTIONS=--experimental-worker, 12.22.1, 14.17.0, and 16.3.0.

Node.js version
stock
remove enableWorkerThreads

10.24.1
574900 KiB
583024 KiB

10.24.1 --experimental-worker
3836652 KiB
596276 KiB

12.22.1
3625192 KiB
672796 KiB

14.17.0
3620284 KiB
673044 KiB

16.3.0
3940128 KiB
557992 KiB

If there’s a speed difference, it’s not perceptible.

Node.js version
stock
remove enableWorkerThreads

10.24.1
36.78s
36.92s

10.24.1 --experimental-worker
37.49s
36.97s

12.22.1
36.95s
37.16s

14.17.0
36.43s
36.88s

16.3.0
36.57s
37.88s

@andersk Can you check 5.1.1 version?
@SimenB maybe you have understand why this is happening, we use jest-worker in terser-webpack-plugin and enable enableWorkerThreads, but memory consuming is very big

We use jest-worker v26 previously (https://github.com/webpack-contrib/terser-webpack-plugin/blob/v5.1.2/package.json#L47), then we update jest-worker to v27 (https://github.com/webpack-contrib/terser-webpack-plugin/blob/v5.1.3/package.json#L47) and look somewhere memory leak in jest-worker...

While I don't know if there is a memory regression in jest-worker version 27.
Increase in memory usage in the main process is expected when using worker threads. This is because unlike forked processes work thread are same process. Overall though, the memory consumption should be lower because there is no overhead from the extra forked processes.

@alan-agius4 I think so because only jest-worker will be updated in near future, will be great of somebody check it on the big project

On the 5.1.1 works good on the 5.1.2 i get error. vm have 2gb ram.

@andersk Can you check 5.1.1 version (terser-webpack-plugin)?

For the test case I’ve shown, the problem seems the same with<EMAIL_ADDRESS>
yarn.lock patch
--- a/yarn.lock
+++ b/yarn.lock
@@ -2637,14 +2637,14<EMAIL_ADDRESS>   resolved "https://registry.yarnpkg.com/isobject/-/isobject-3.0.1.tgz#4e431e92b11a9731636aa1f9c8d1ccbcfdab78df"
   integrity sha1-TkMekrEalzFjaqH5yNHMvP2reN8=

<EMAIL_ADDRESS>-  version "27.0.2"
-  resolved "https://registry.yarnpkg.com/jest-worker/-/jest-worker-27.0.2.tgz#4ebeb56cef48b3e7514552f80d0d80c0129f0b05"
-  integrity sha512-EoBdilOTTyOgmHXtw/cPc+ZrCA0KJMrkXzkrPGNwLmnvvlN1nj7MPrxpT7m+otSv2e1TLaVffzDnE/LB14zJMg==
<EMAIL_ADDRESS>+  version "26.6.2"
+  resolved "https://registry.yarnpkg.com/jest-worker/-/jest-worker-26.6.2.tgz#7f72cbc4d643c365e27b9fd775f9d0eaa9c7a8ed"
+  integrity sha512-KWYVV1c4i+jbMpaBC+U++4Va0cp8OisU185o73T1vo99hqi7w8tSJfUXYswwqqrjzwxa6KpRK54WhPvwf5w6PQ==
   dependencies:
     "@types/node" "*"
     merge-stream "^2.0.0"
-    supports-color "^8.0.0"
+    supports-color "^7.0.0"

<EMAIL_ADDRESS>   version "1.5.3"
@@ -4053,10 +4053,10<EMAIL_ADDRESS>   dependencies:
     has-flag "^3.0.0"

<EMAIL_ADDRESS>-  version "8.1.1"
-  resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-8.1.1.tgz#cd6fc17e28500cff56c1b86c0a7fd4a54a73005c"
-  integrity sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==
<EMAIL_ADDRESS>+  version "7.2.0"
+  resolved "https://registry.yarnpkg.com/supports-color/-/supports-color-7.2.0.tgz#1b7dcdcb32b8138801b3e478ba6a51caa89648da"
+  integrity sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==
   dependencies:
     has-flag "^4.0.0"

@@ -4101,18 +4101,18<EMAIL_ADDRESS><EMAIL_ADDRESS>   integrity sha512-FBk4IesMV1rBxX2tfiK8RAmogtWn53puLOQlvO8XuwlgxcYbP4mVPS9Ph4aeamSyyVjOl24aYWAuc8U5kCVwMw==

<EMAIL_ADDRESS>-  version "5.1.3"
-  resolved "https://registry.yarnpkg.com/terser-webpack-plugin/-/terser-webpack-plugin-5.1.3.tgz#30033e955ca28b55664f1e4b30a1347e61aa23af"
-  integrity sha512-cxGbMqr6+A2hrIB5ehFIF+F/iST5ZOxvOmy9zih9ySbP1C2oEWQSOUS+2SNBTjzx5xLKO4xnod9eywdfq1Nb9A==
+  version "5.1.1"
+  resolved "https://registry.yarnpkg.com/terser-webpack-plugin/-/terser-webpack-plugin-5.1.1.tgz#7effadee06f7ecfa093dbbd3e9ab23f5f3ed8673"
+  integrity sha512-5XNNXZiR8YO6X6KhSGXfY0QrGrCRlSwAEjIIrlRQR4W8nP69TaJUlh3bkuac6zzgspiGPfKEHcY295MMVExl5Q==
   dependencies:
-    jest-worker "^27.0.2"
+    jest-worker "^26.6.2"
     p-limit "^3.1.0"
     schema-utils "^3.0.0"
     serialize-javascript "^5.0.1"
     source-map "^0.6.1"
-    terser "^5.7.0"
+    terser "^5.5.1"

<EMAIL_ADDRESS><EMAIL_ADDRESS>   version "5.7.0"
   resolved "https://registry.yarnpkg.com/terser/-/terser-5.7.0.tgz#a761eeec206bc87b605ab13029876ead938ae693"
   integrity sha512-HP5/9hp2UaZt5fYkuhNBR8YyRcT8juw8+uFbAme53iN9hblvKnLUTKkmwJG6ocWpIKf8UK4DoeWG4ty0J6S6/g==

$ yarn list --pattern=terser-webpack-plugin
yarn list v1.22.10
└─<EMAIL_ADDRESS>Done in 0.36s.
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack --stats=errors-only
313.69user 3.85system 0:36.30elapsed 874%CPU (0avgtext+0avgdata 3798732maxresident)k
0inputs+23704outputs (0major+1243086minor)pagefaults 0swaps
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack --stats=errors-only
313.42user 3.77system 0:36.59elapsed 866%CPU (0avgtext+0avgdata 3479656maxresident)k
0inputs+23704outputs (0major+1221138minor)pagefaults 0swaps
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack --stats=errors-only
311.58user 3.83system 0:35.92elapsed 877%CPU (0avgtext+0avgdata 3910884maxresident)k
0inputs+23704outputs (0major+1287653minor)pagefaults 0swaps
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack --stats=errors-only
310.42user 3.85system 0:35.98elapsed 873%CPU (0avgtext+0avgdata 3721268maxresident)k
0inputs+23672outputs (0major+1251587minor)pagefaults 0swaps
$ rm -rf dist node_modules/.cache; \time node_modules/.bin/webpack --stats=errors-only
311.79user 3.84system 0:36.29elapsed 869%CPU (0avgtext+0avgdata 3683624maxresident)k
0inputs+23704outputs (0major+1263828minor)pagefaults 0swaps

@andersk Maybe you can share your application with me (if need I can sign NDA)? I can disable enableWorkerThreads, but I feel it is wrong, will be great to investigate why it happens

It looks very much like what @alan-agius4 said:
time doesn't measure memory usage of child processes, so using worker_threads will report higher memory usage.

@alexander-akait I did share the application and a full reproduction recipe in the original report above. Totally open source, Apache 2.0 license, no NDA necessary. ☺
@sokra Hmm. You seem to be right that time doesn’t measure what I thought it was measuring. It does measure over the entire child process tree, but it only reports the largest single process within that tree, rather than the total usage of all processes.
I found a tool cgmemtime that does measure the total usage. Based on that better measurement, the discrepancy between webpack 4 and webpack 5 still exists in the actual application, but it’s less dramatic, and doesn’t seem to be visible in this particular benchmark that I extracted.
I will close this report for now, do more experiments with cgmemtime, and open another report if I find something actionable. Feel free to hop into zulip/zulip#16649 if you’d like to follow along.
Thanks all!


Rss links point to the wrong domain

The links from https://fex-emu.com/feed.xml point to "fex-emu.org" instead of "fex-emu.com"

Oops!  Thanks for the bug report! Fixed now.


No 'information protection' link from M365 Compliance page

[Enter feedback here]
Hello:
Since I want to understand how to create or apply or find sensitivity labels that i can extend to Purview, I am following the steps in this article.
Step #1 says 'navigate to Information Protection' page.   In my subscription, there isn't an info protection page but there is 'information governance'. Will upload snapshot from my view of M365 compliance.

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

ID: 9172241a-3e6c-04c5-4906-f33321a5b8a5
Version Independent ID: fe97b1a3-5014-ba55-533f-8dd86836ed24
Content: Automatically apply sensitivity labels to your data - Azure Purview
Content Source: articles/purview/create-sensitivity-label.md
Service: purview
Sub-service: purview-data-catalog
GitHub Login: @batamig
Microsoft Alias: bagol

@KBaroni  Thanks for the feedback! We are investigating and will update you shortly.

I'm looking into this issue now and will update you here! Thank you for your patience!

Hi Whitney - I should have waited a few more hours after provisioning my subscription.  It IS now showing up on my compliance page.  Thank you for following up ~
From: Whitney Henderson @.>
Sent: Tuesday, August 24, 2021 10:53 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Kate Baroni @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] No 'information protection' link from M365 Compliance page (#80090)
I'm looking into this issue now and will update you here! Thank you for your patience!

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F80090%23issuecomment-904812342&data=04|01|Kate.Baroni%40microsoft.com|5c90deb5efa34b83af6808d9671fa074|72f988bf86f141af91ab2d7cd011db47|1|0|637654207827769074|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=zlHCS%2FUnh0GU8mVYSyJLrO4dYyPXjtJeuVk7hIUGbao%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACZEWKSMRSQ24LK23WC65R3T6PE6VANCNFSM5CVHXWGA&data=04|01|Kate.Baroni%40microsoft.com|5c90deb5efa34b83af6808d9671fa074|72f988bf86f141af91ab2d7cd011db47|1|0|637654207827779068|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=p1t5DZMdNpa%2Buu2FUEq%2BqfQj4QrWjuGgtNn1axk2zzQ%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|Kate.Baroni%40microsoft.com|5c90deb5efa34b83af6808d9671fa074|72f988bf86f141af91ab2d7cd011db47|1|0|637654207827779068|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=NJw%2BWNNZ4%2FLMBaOQ7iQImevdN8vEA4Gv0tzo9kttxOE%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26utm_campaign%3Dnotification-email&data=04|01|Kate.Baroni%40microsoft.com|5c90deb5efa34b83af6808d9671fa074|72f988bf86f141af91ab2d7cd011db47|1|0|637654207827789066|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=XVT54OEW2niEVu8HPqDS4PM0YhtcnUPse2t8H6PvB%2B8%3D&reserved=0.


[Logging] Fixed the md5 hash non-printable characters

Modified the md5 hash to print the Array of numbers instead of the non-printable characters when there is a mismatch.
Added few files that are generated locally in the gitignore.
How to test in local?
set the property azkaban.storage.type=LOCAL in the azkaban.properties. This enabled the zip to be stored in LOCAL file system. After that deliberately added few bytes in the validateCheckSum hash. When I ran a flow, it failed with IllegalStateException indicating the mismatch between the hashes.
The flow went through fine when there is a match in the md5 hashes.

Removed the unused imports and updated the PR. It turns out that adding test case for this would be tricky as we have modified the log message. Happy to get more thoughts on this.


Cannot resolve module 'postcss-less'

Hi,  I've started to get the following error in the build stage of my app.
ERROR in ./~/css-modules-require-hook/test/api/processorOpts.js
Module not found: Error: Cannot resolve module 'postcss-less' in /Users/peterm/Workspace/personal/react-lego/node_modules/css-modules-require-hook/test/api
 @ ./~/css-modules-require-hook/test/api/processorOpts.js 5:19-42

my config file is (no mention of less):
const sass = require('node-sass');
module.exports = {
  generateScopedName: '[path]___[name]__[local]___[hash:base64:5]',
  extensions: ['.scss'],
  preprocessCss: (data, filename) =>
    sass.renderSync({
      data,
      file: filename,
    }).css,
};

I see your package.json has a devDependency "postcss-less": "^0.2.0", which looks correct to me as you are using this module for tests.
I suspect the tests are being run accidentally. Is that a post install script that runs the tests which is inadvertently being run when people npm i this module?

this is the code changes i have done to get css-modules to work : https://github.com/peter-mouland/react-lego/commit/63b535c61ba61e964b16cba0a5b6ce64bffc3ebb

I don't have any postinstall scripts in the package.json file as you may find. Only prepublish script which compiles the server code. But it's guarded with in-publish module, so it wont be executed after npm i. So I doubt that tests were being run accidentally.
I checked the related issue and looks like that problem comes from the webpack. In the begining you may find that it tries to compile hooks modules:
WARNING in ./~/css-modules-require-hook/preset.js
Critical dependencies:
13:7-22 the request of a dependency is an expression
 @ ./~/css-modules-require-hook/preset.js 13:7-22

Anyways looks like I forgot to add test folder to the .npmignore so it wont be available after publication, but still you have to find the way to exclude require hook from the compile step in the webpack config.

I published version 4.0.4 so you wont get any problem with tests for now, but still you have to exclude require hook from the compiled files.

Thanks.  I'll look into the exclusion

I've stopped using the preset option in favour of the manual config option.  This is because the plugin/hook is also needed for server-side rendering (and my server files are compiled).


Token insights - restore MyDistribution query, show separate synclist url

Restores bits from #3708, #3346 and #3893.
TokenInsights now queries  _ui/v1/my-distributions to find a synclist distribution base_path, and display that:

(TODO success)

TODO also add validated url