Angular Production Build: Not able to remove the Dependencies Details from angular Build generated main[hash].js file

Command
build
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Hello Community,
I am Facing an issue in the Angular Production Build Generated main[hash].js file, the main file generated in builds shows all the information about dependencies, I have tried several things including custom-webpack, but I am unable to remove the details from the main.js file

I want to remove the highlighted part from main[hash].js file generated with ng build --prod
Minimal Reproduction
generated the build using ng build --prod
checked main[hash].js file in browser, dependencies and devDependencies details are still there.
Exception or Error
To remove Dependencies or devDependencies from the angular prod / UAT build generated main[hash].js

Your Environment
Angular CLI: 7.3.0
Node: 10.19.0
OS: win32 x64
Angular: 7.2.3
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.13.0
@angular-devkit/build-angular      0.13.0
@angular-devkit/build-optimizer    0.13.0
@angular-devkit/build-webpack      0.13.0
@angular-devkit/core               7.3.0
@angular-devkit/schematics         7.3.0
@angular/cdk                       7.3.0
@angular/cli                       7.3.0
@angular/flex-layout               7.0.0-beta.19
@angular/material                  7.3.0
@angular/material-moment-adapter   9.1.3
@ngtools/webpack                   7.3.0
@schematics/angular                7.3.0
@schematics/update                 0.13.0
rxjs                               6.4.0
typescript                         3.2.4
webpack                            4.29.0

Anything else relevant?
No response

The support for v7 was dropped long time ago. Please update your stack before opening a support request.

@JeanMeche  I Know, but this project is in Production and has some dependencies due to which I cannot upgrade the stack, appreciate it if you could provide any solution.

For license comments in the output chunks, the extractLicenses option can be used (enabled by default in production for newly generated projects).
As to the package.json content in the output chunks, the application code itself is most likely importing the project's package.json. This is something that would need to be fixed within the application's code and not the Angular CLI.


Add links to related external docs

Adds a prop to the ModuleSummary component that allows linking out to related documentation, for example to the three.js concepts that most threlte components abstract over. Also adds some more or less obvious candidates for links to existing documentation.

Thank you so much for this ❤ Great change and a really good addition for people that are just starting off.


Initial push for contract VIN (factoryNft)

When running tests we have the following trace:
Everything at the top-level was executed.
- test exited with value <fun>.

And no more trace. For me this test is not run.


Fix issue #37 : Create my_path.pth only for local mypy test, remove afterwards

Basically, now my_path.pth is created and destroyed after tests.
Fix https://github.com/pandas-dev/pandas-stubs/issues/37

Can you merge with main and resolve conflicts?

Can you merge with main and resolve conflicts?

Done

Thanks @BrenoJesusFernandes


refactor: render or skip stack based on stackConfigs is provided or not

fix: https://github.com/KusionStack/kusion/issues/84

Coverage decreased (-0.4%) to 73.023% when pulling 318baff8a6c25e16446b46727458d3a0ecd407f5 on howieyuen:skip-unspecified-stacks into afdf541e5dca01d6315f49fecba84389148c9379 on KusionStack:main.


Empty entry in bib-file leads to error when compiling with Biber

Programm used to create bib-file
JabRef 5.3 (latest release)
Programms used to compile the LaTeX document
Miktex and Texmaker
Operating system
Windows, 20H1
Steps to reproduce the behaviour

open your bib-file (e.g. via Jabref or manually)
Create a new Entry (because you intend to enter a new entry, BUT THEN YOU CHANGE YOUR MIND AND FORGET DELETING IT)
Do not enter any data into the entry (= An empty entry).
This is how an empty entry looks like in the bib-file:

@Article{,
}

Save your libary > use this file for your latex project > try to compile your latex project with Miktex and Texmaker > Error ensues, which prevents me from completing my latex compilation.

Error message in biber when i try to compile my document:
Process started

INFO - This is Biber 2.16 INFO - Logfile is 'Democratic Backsliding in South-East-Asia (article).blg' INFO - Reading 'Democratic Backsliding in South-East-Asia (article).bcf' INFO - Found 62 citekeys in bib section 0 INFO - Processing section 0 INFO - Looking for bibtex format file 'bibliography.bib' for section 0 INFO - LaTeX decoding ... INFO - Found BibTeX data source 'bibliography.bib' WARN - Invalid or undefined BibTeX entry key in file 'C:\Users\Thilo\AppData\Local\Temp\biber_tmp_2wgH\f4d088b3f9f145b5c3058da33afd57d4_12036.utf8', skipping ... ERROR - BibTeX subsystem: C:\Users\Thilo\AppData\Local\Temp\biber_tmp_2wgH\f4d088b3f9f145b5c3058da33afd57d4_12036.utf8, line 3, syntax error: found ",", expected one of: number, name (entry type, key, field, or macro name), end of entry ("}" or ")") or quoted string ({...} or "...") INFO - WARNINGS: 1 INFO - ERRORS: 1

Process exited with error(s)

Additional notes:
I just thought i would let you know, since this is relevant for biber AND Jabref.
Here the relevant issue on Jabref:  https://github.com/JabRef/jabref/issues/8096

Not much to be done about this as it's bad syntax and the internal libbtparse library just dies. We could put in a test for this to catch it but there are lots of ways to provide mangles entries and it's very rare.

Trying to solve this on JabRef side via #8645
It has been found that the lack of a citationkey is enough to trigger an error using Biber


Enable caching for faster builds

Specifically:

Cache the files downloaded via apt across Docker invocations, so that we don't pound the network when our apt dependencies change a little.
Cache the bazel build results across Docker invocations, so that rebuilds are fast while testing small changes.

Eventually we may want a "gold build" flag that opts-out of caching for when we're actually doing real releases, or to make the caching opt-in, but during active development it seems like "fast by default" is better.
Also tidy up a few unrelated loose ends -- Bazel version, and capitalization.

I'm using Docker on Bionic via APT.  I thought it was the stock Docker.  I'll go back and check.

Please split the Bazel version and URI changes into a separate PR; those look non-controversial.

Done.

The caching is... concerning. Specifically, it requires BuildKit, which is not available on stock Docker (at least as of Bionic), ...

It works fine for me on stock Bionic, using sudo apt install docker.io= 20.10.7-0ubuntu1~18.04.1.

That is going to seriously limit the environments in which this stuff can be used. (In particular, I might not be able to build images at all.) It would be safer if there was a way to make this optional.

Sounds fine, I will rework this to have some kind of toggle.
However, I think that as we work to get Drake's workspace-related patches merged, using cached builds of Drake is going to be table stakes, at least for me.  Waiting 10-20 minutes to test each one-line change seems like a a non-starter, when it could be just a few tens of seconds.  I recommend that you find a way to use caching, so that you can more effectively help iterate on Drake patching, whether though this PR, or some alternative change you might have in mind.  From my internet searching, this current patch seems like the best practice to share cache folders across Docker builds.

However, I think that as we work to get Drake's workspace-related patches merged, using cached builds of Drake is going to be table stakes, at least for me.

Sure, it's definitely a pain ATM. Also, I'm much more interested in getting Bazel's cache working (bonus if it can work for podman, also; is there a way to leverage VOLUME for this?).
Given that installing packages from apt, not to mention pip, and building dependencies (VTK in particular) takes a significant amount of time, I'm less confident that mucking about with apt cache is a useful win. That stuff should not change often, and the download step shouldn't be taking all that long unless your connection is really slow. Realistically, the price you're going to pay for rebuilding VTK if the "base" layer changes is going to comfortably exceed the price for not having an apt cache.
If we're really that concerned about hitting the network more than absolutely necessary on those hopefully-rare occasions that the "incubator" layer changes, we probably should also be caching the pip and drake-dependencies downloads. (At least the latter; I'm not sure if pip downloads can be cached. We might need to tweak drake-dependencies, but that should be possible to cache; it's a simplified version of fletch, which as I understand is used by folks with no network.)
Also, if we're really, really concerned about the time it takes to rebuild the lower layers, maybe we should use ccache?

That all said, I also don't advise using docker build to test change to Drake itself. Use docker run with the image used to run build-drake.sh and test changes within the running container. That'll be even faster.

That stuff should not change often, and the download step shouldn't be taking all that long unless your connection is really slow.

I've withdrawn that part of the change (the apt caching).

That is going to seriously limit the environments in which this stuff can be used. (In particular, I might not be able to build images at all.) It would be safer if there was a way to make this optional.

Sounds fine, I will rework this to have some kind of toggle.

FYI I just rebased this PR, but have not yet implemented that toggle.  I'll still need to do that before we can merge this.

Circling back to this after some recent CI woes... it seems our CI uses remote caching? Maybe something like that could be useful here to avoid needing to know Dockerkit magic? (Actually, I am surprised now we aren't using a shared cache? Or does Bazel not support that?)

Bazel can cache build and test results using either a local filesystem cache, or a web cache at some URL.  If desired, one can use the cache for reading, but not write back to it.
Drake CI uses the web cache (not a local filesystem cache), so that the dozens+ of concurrent builds can all share their already-completed build results with each other.  For any given ephemeral build machine, the build variant (Debug, Release, CXX=clang-9, etc.) varies a lot from one build to the next, so a filesystem-local cache would not see very many cache hits.  The web cache lets us share across machines much more effectively.
For the Drake CI builds that publish official images, we do not have any caching enabled, so that we can be sure that any kind of cache pollution cannot contaminate our releases.
It would not make sense to try to have pip-drake builds check the Drake CI cache for hits, at least not as of today.  For pip, we're using a different version of Eigen and almost everything else, so I would expect practically zero overlap with CI's existing actions.  Possibly once we have nightly builds of pip-drake running in Drake CI, we could have a way to opt-in to that read-only cache to accelerate local users.
Once we make a plan for how to get this code under CI, we can see if it makes sense for it to access the CI cache.
In this PR, I was proposing using the disk cache, since the build is necessarily happening on just the one, local machine.  Running a local-only http server during the build (with a writeable webdav, or similar) just to pretend to be a local filesystem, would be lot of extra complexity.
All 50+ Drake developers (even beyond just TRI) have access to Ubuntu locally, which has BuildKit built-in already, without any extra hassle, so this PR (once I revise it) will able to help them.  I do still plan to rework this PR to offer a toggle for BuildKit so that it won't break your workflow, but I don't think it's worth playing with web-based caching, since almost everyone will have access to this local caching mechanism.
If you figure out a way to offer a persistent temp filesystem into your variant of docker, we can merge that into pip-drake under a toggle, in addition to this mechanism.


Added support for caching in local storage

@angelnikolov  I added support for caching in local storage. Please review and merge it.

Thank you so much for this PR. I have some notes however.
Your implementation couples the CacheableDecorator tightly with a DOM api and since this decorator should be platform-agnostic (meaning - client/server), we need a better way to provide this functionality.
What I suggest to do is to create a generic IPersistenceAdapter or something in those lines, which would look like:
export interface IPersistenceAdapter {
     public set(any): any | Promise<any> | Observable<any>;
     public get(): any | Promise<any> | Observable<any>;
}

Then, you can extend the cacheable decorator and add a static property to the Cacheable function called Cacheable.persistenceAdapter.
Then you can create a class DomPersistenceAtapter implements IPersistenceAdapter and put it somewhere in the source code of ngx-cacheable but do not depend on it directly from the decorators.
Whoever wants to use persistence, will just have to provide the default dom adapter somewhere up top in their code and it should just work. That way, people could even provide different adapters for persistence like Redis, file-system or whatever.
In the decorators we would need to check what's the runtime return types of the set/get functions of the adapter and handle the setting/getting accordingly.
We will also need to update the promise.cacheable.decorator.ts with those as well.
Again, thank you so much for your contribution and I hope you see the value in what I am proposing :)
If you don't have the time to implement that, I will surely find some time, but won't be today.

@angelnikolov Thanks a lot for reviewing my code. Your suggestion is greatly appreciated and I will look into implementing this and then resubmitting the code.

@angelnikolov I have pushed some changes that I made according to what you suggested. Could you please have a look and tell me if I am on the right path? With this new implementation what I am intending is that whoever uses ngx-cacheable will declare a persistence adapter in their code and then pass it to the decorator via the annotation Cacheable.
For instance, we could declare in our code
const cache = window.localStorage;
then pass this thus,
@Cacheable({persistenceAdapter: cache})
Is this kind of what you wanted?

I think you are on the right track and also given me some food for thought on some things that I thought would be a lot easier to implement. Give me a couple of days and I will show you what I've been thinking and maybe you can do a quick review on it. It's not that different than yours but I had some stuff in mind that would be best explained by code. Thank you so much for this initial implementation!:)

@angelnikolov  I really appreciate you taking out the time to review and comment on my code. Yeah, I'll be very interested in what you have cooked up. I am actually intending to use this library of yours in a project of mine where caching in localStorage is required so it would be nice to have it implemented fully. Best regards.

https://github.com/angelnikolov/ngx-cacheable/pull/35


The  v_generate_view_ddl does not work  for late-binding views

There is a bug in the  v_generate_view_ddl.sql. It does not work  for late-binding views. It produces a extra "CREATE OR REPLACE VIEW [schema.view] AS". For example:, it will generate the below wrong DDL.
--DROP VIEW  cdwds.cdw_d_prod_v ;
CREATE OR REPLACE VIEW cdwds.cdw_d_prod_v ASCREATE OR REPLACE VIEW CDWDS.CDW_D_PROD_V AS SELECT * FROM CDW.D_PROD with no schema binding;
It work fine for regular views.
Luke

Hello lukeli@,
I have tested a new version for the view you have mentioned and it is working now.
--Before
tickit=# select * from admin.v_generate_view_ddl where viewname = 'vw_s3_view';
schemaname |  viewname  |                                                    ddl
------------+------------+-----------------------------------------------------------------------------------------------------------
public     | vw_s3_view | --DROP VIEW public.vw_s3_view;                                                                           +
|            | CREATE OR REPLACE VIEW public.vw_s3_view AS                                                              +
|            | create or replace view vw_s3_view as select * from spectrum.account_registrations with no schema binding;
(1 row)
--New version
tickit=# select * from admin.v_generate_view_ddl_new where viewname = 'vw_s3_view';
schemaname |  viewname  |                                                    ddl
------------+------------+-----------------------------------------------------------------------------------------------------------
public     | vw_s3_view | --DROP VIEW public.vw_s3_view;                                                                           +
|            | create or replace view vw_s3_view as select * from spectrum.account_registrations with no schema binding;
(1 row)
Could you please test the version mentioned in the following link and let me know if it works for you?
https://github.com/alexlsts/amazon-redshift-utils/blob/master/src/AdminViews/v_generate_view_ddl.sql

Hi @alexlsts
If you want the DDL to be complete, I think that you need to append 'with no schema binding' to the end of the create statement.
Other than that, this seems to work.

Hello @jake-barry,
If you execute this view you will see the following output:
tickit=# select * from admin.v_generate_view_ddl where viewname = 'vw_s3_view';
schemaname |  viewname  |                                                    ddl
------------+------------+-----------------------------------------------------------------------------------------------------------
public     | vw_s3_view | --DROP VIEW public.vw_s3_view;                                                                           +
|            | create or replace view vw_s3_view as select * from spectrum.data with no schema binding;
(1 row)
The COALESCE(pg_get_viewdef(c.oid, TRUE), '') have already included the "with no schema binding" for late binding.

Closed as code merged


Unpublish with validation errors causes internal server error

I noticed that when saving or publishing a page with validation errors you are redirected to the page edit form with the fields that are invalid highlighted in red. If I try to unpublish a page with validation errors, I get an internal server error instead of the page form with the invalid fields highlighted. The validation check seems appropriate as that is what the changelog says https://github.com/torchbox/wagtail/blob/07ac5aa8ee5456d308789585d0375a2fbe68ede4/CHANGELOG.txt#L180 and the unpublish method calls save(). Also, this was caused by a direct change in the database (so it didn't go through the URLValidator for this URLField), it wasn't changed with the model api (that wouldn't have happened since the model api runs validator checks). So when trying to unpublish that page, it is not clear in the frontend why it is failing and causes an 500 error page instead.

By the way, "Unpublish" doesn't submit form: it just points to the unpublish confirmation screen (GET request). So probably page had been saved incorrectly before unpublish method was called.

version 1.4.5
I just put the relevant field that is making the page fail

    class BaseCruiseLinePage(Page):
        image_url = models.URLField(validators=[validators.URLValidator(schemes=['https'])])

Here is the traceback

Traceback:
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  132.                     response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/django/views/decorators/cache.py" in _cache_controlled
  43.             response = viewfunc(request, *args, **kw)
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/wagtail/wagtailadmin/decorators.py" in decorated_view
  22.             return view_func(request, *args, **kwargs)
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/wagtail/wagtailadmin/views/pages.py" in unpublish
  599.         page.unpublish()
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/wagtail/wagtailcore/models.py" in unpublish
  698.                 self.save()
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/django/utils/decorators.py" in inner
  145.                     return func(*args, **kwargs)
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/wagtail/wagtailcore/models.py" in save
  445.         self.full_clean()
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/wagtail/wagtailcore/models.py" in full_clean
  436.         super(Page, self).full_clean(*args, **kwargs)
File "/home/nick/.pyenv/versions/django.perx.com/lib/python2.7/site-packages/django/db/models/base.py" in full_clean
  1171.             raise ValidationError(errors)

Exception Type: ValidationError at /admin/pages/198/unpublish/
Exception Value: {'image_url': [u'Enter a valid URL.']}

And on your most recent comment, yeah I understand it goes to the confirmation screen with a GET request. The ValidationError is raised on the POST to that page. So in this example, image_url was changed to a url without the https scheme. It was written as http directly to the database (so no validation). After the POST it doesn't return to the form to show the error, just causes the server error, because of the ValidationError.
Let me know what else you may need, or if you need more clarification.

Now I can reproduce the error on master branch with the following steps:

Define a model. For example:
class BaseCruiseLinePage(Page):
    image_url = models.URLField(validators=[validators.URLValidator(schemes=['https'])])

    content_panels = Page.content_panels + [
        FieldPanel('image_url')
    ]

Add a new page in the Wagtail admin.

Change a value of image_url directly in DB or change model definition to something like this:
class BaseCruiseLinePage(Page):
    image_url = models.URLField(validators=[validators.URLValidator(schemes=['http'])])

    content_panels = Page.content_panels + [
        FieldPanel('image_url')
    ]

(schemes argument was changed from ['https'] to ['http'])

Unpublish a page.

Result: ValidationError
I'm not sure that we need to handle this case. On the one hand if developer decides to change validation rules he should provide a migration for the old data, on the other hand sometimes it's not possible / necessary to migrate old date.
I've marked this issue as "Design decision needed".
Thanks @PresidentNick!

I'm sure this can also be generalized to fields stored on the database that don't pass that field's validators, not just for URLs.

I'm not sure that we need to handle this case. On the one hand if developer decides to change validation rules he should provide a migration for the old data, on the other hand sometimes it's not possible / necessary to migrate old data.

I'd agree with this - if a developer changes validation rules at any point, it's their responsibility to ensure that existing data is valid according to the new rules, so this isn't strictly a bug in Wagtail.
Having said that, we do want to keep Wagtail as developer-friendly as possible, and there isn't really any reason to perform re-validation at the point of unpublishing (and likewise for moving, where this issue has also been reported) - so if there's a nice way to disable model validation on these views without introducing lots of complexity or hacks, it would be good to do that.

I'd agree with this - if a developer changes validation rules at any point, it's their responsibility to ensure that existing data is valid according to the new rules, so this isn't strictly a bug in Wagtail.

Just a note that there are situations where this can happen without a developer making changes. For example if you have a nullable but non-blank foreign key field (e.g., a foreign key to wagtailimages.Image) which cascades to SET_NULL (this is a common pattern on things like image fields), and such an object is deleted.

Fixed in #5828.


When POST ,  A dictionary type data will auto urlencode

Summary.
When the POST data is a dictionary type
Requests will aoto URLencode it.
For example :
postdata = { "url" : "https%3A%2f%2fwww.google.com" }

Actual Result
When my post data have URLencoded data what include URL .
The actual post data is
url=https%253A%252f%252fwww.google.com

Search source code
models.py

def _encode_params(data):
    """Encode parameters in a piece of data.

    Will successfully encode parameters when passed as a dict or a list of
    2-tuples. Order is retained if data is a list of 2-tuples but arbitrary
    if parameters are supplied as a dict.
    """

    if isinstance(data, (str, bytes)):
        return data
    elif hasattr(data, 'read'):
        return data
    elif hasattr(data, '__iter__'):
        result = []
        for k, vs in to_key_val_list(data):
            if isinstance(vs, basestring) or not hasattr(vs, '__iter__'):
                vs = [vs]
            for v in vs:
                if v is not None:
                    result.append(
                        (k.encode('utf-8') if isinstance(k, str) else k,
                         v.encode('utf-8') if isinstance(v, str) else v))
        return urlencode(result, doseq=True)
    else:
        return data

@nateprewitt multipart/form-data only happens when data and files are present. When a dict is passed to data we application/x-www-form-urlencoded it. The behaviour is still correct, though.


Security: unpin passport-oauth2 (CVE-2021-41580)

I believe this vulnerability does not directly affect Docusign customers, as the OAuth2 ID Provider won't allow an empty token.
However, unpinning this dependency will keep automated audit tools happy, plus allows people to more easily take advantage of fixes for future vulnerabilities.
https://github.com/advisories/GHSA-f794-r6xc-hf3v

It would be great if someone can merge and release the new version

Hey all, thank you for putting together a PR for this. We have this on our radar, but will be performing this change upstream of this repo.

hi - can i get a delivery date from docusign (even if it is projected). We're a DS partner and it would be great to close this as a risk even if there is no practicable risk from our risk register.

hi - can i get a delivery date from docusign (even if it is projected). We're a DS partner and it would be great to close this as a risk even if there is no practicable risk from our risk register.

@RalphBragg The fix has already been merged internally. We will have it going out in our next SDK release. The holidays throw a wrench in timing but it should be coming soon

@acooper4960 so next week? technically this is the first week in december but it's not a full week..

Closing as this has been included in PR 283


[Question] How to disable bot OR specify intent in middleware

Bot Info

SDK Platform: Node.js
SDK Version: 3.15.0
Active Channels: Slack
Deployment Environment: local via ngrok

Issue Description
I am trying to disable bot responses in group chats in Slack unless specifically mentioned, this is the designed use case for our bot.
I would prefer to do this in middleware since we have other middleware after this that we wish to intercept and not execute in the scenario.
Code Example
I have implemented group and mention detection like so:
bot.use({
	botbuilder: (session, next) => {

		if (session.message.source !== 'slack') {
			return;
		}
		const botMention = session.message.entities && session.message.entities.find((entity) => {

			return entity.type === 'mention' && entity.mentioned.id === session.message.address.bot.id;
		});
		const isGroup = session.message.address.conversation && session.message.address.conversation.isGroup;
		if (isGroup && !botMention) {
			// Do something here?
		}
		return next();
	}
});

This works fine, but I am unable to find a way to either disable continuing the bot from this point or perhaps handling it in the following middleware via a sessionData variable an then implement some custom routing using the same variable, but this could get quite messy and seems a roundabout solution.
The customRouting  example kind of does what I am trying but using routing instead of middleware. Is this possible?

Great, works perfectly! Thanks @nyxsys .


Authentication error: you cannot auth exceed once in 60 seconds

Describe the bug:
I've had the plugin up and running fine with no issue for some time and a couple of nights back night im now getting this error.
[TuyaWebPlatform] Cannot acquire token, waiting 65 seconds. [TuyaWebPlatform] Retrying authentication after previous error.
[10/16/2021, 8:48:58 AM] [TuyaWebPlatform] Authentication error: you cannot auth exceed once in 60 seconds
Plugin Version - v1.0.2
Homebridge Config
{
"name": "TuyaWebPlatform",
"options": {
"username": "@",
"password": "*****",
"countryCode": "44",
"platform": "smart_life",
"pollingInterval": 10
},
"defaults": [
{
"device_type": "form"
}
],
"scenes": false,
"platform": "TuyaWebPlatform"
}
Device Config - errors
auth_response = requests.post(
Getting credentials
Got credentials
{   'errorMsg': 'you cannot auth exceed once in 60 seconds',
'responseStatus': 'error'}
Traceback (most recent call last):
File "main.py", line 35, in
payload = {"accessToken": auth_response["access_token"]}
KeyError: 'access_token'

I’m having the same problem over and over again. It starts to annoy me! Look at my thread #346
I asked @milo526 to reopen the issue.


Encode payload data for CreateMetadataAccountV3 (with Collections Details)

I am aware that there has not yet been released a version which takes into account certified collections. Anyway, I do plan to make the necessary adjustments to the existing code so as to allow creating a collection.
From my understanding, for creating a certified collection, the following are needed:

Changing MetadataProgram.CreateMetadataAccount function so as to also encode the collectionDetails. However, I tried to change it according to the order, offsets and sizes of arguments listed here https://docs.metaplex.com/programs/token-metadata/instructions#create-a-metadata-account and I don't seem to manage to get it working. My modified version of MetadataProgram.CreateMetadataAccount is:

private static byte[] EncodeCreateMetadataAccountData(MetadataParameters parameters, int? collectionDetailsSize = null, bool isMutable = true)
        {
            byte[] bytes = Encoding.UTF8.GetBytes(parameters.name);
            byte[] bytes2 = Encoding.UTF8.GetBytes(parameters.symbol);
            byte[] bytes3 = Encoding.UTF8.GetBytes(parameters.uri);
            MemoryStream memoryStream = new MemoryStream();
            BinaryWriter binaryWriter = new BinaryWriter(memoryStream);
            binaryWriter.Write((byte)0);
            binaryWriter.Write(bytes.Length);
            binaryWriter.Write(bytes);
            binaryWriter.Write(bytes2.Length);
            binaryWriter.Write(bytes2);
            binaryWriter.Write(bytes3.Length);
            binaryWriter.Write(bytes3);
            binaryWriter.Write((ushort)parameters.sellerFeeBasisPoints);
            int num;
            if (parameters.creators != null)
            {
                List<Creator> creators = parameters.creators;
                num = ((creators != null && creators.Count < 1) ? 1 : 0);
            }
            else
            {
                num = 1;
            }

            if (num != 0)
            {
                binaryWriter.Write((byte)0);
            }
            else
            {
                binaryWriter.Write((byte)1);
                binaryWriter.Write(parameters.creators.Count);
                foreach (Creator creator in parameters.creators)
                {
                    byte[] buffer = creator.Encode();
                    binaryWriter.Write(buffer);
                }
            }

            // collection - ADDED BY ME
            binaryWriter.Write((byte)0);

            // uses  - ADDED BY ME
            binaryWriter.Write((byte)0);

            binaryWriter.Write(isMutable);

            // - whole below if-else block ADDED BY ME
            if (collectionDetailsSize != null)
            {
                binaryWriter.Write((byte)1);

                byte[] collectionDetailsByteArray = new byte[8];
                var collectionDetailsSizeBytes = BitConverter.GetBytes(collectionDetailsSize.Value);

                collectionDetailsSizeBytes.CopyTo(collectionDetailsByteArray, 0);

                binaryWriter.Write(collectionDetailsByteArray);
            }
            else
            {
                binaryWriter.Write((byte)0);
            }

            return memoryStream.ToArray();
        }

I always get a deserialization exception from the on-chain program. I am using testnet at the moment. Can you help me get the encoding of the collectionDetails right until the feature will be implemented in this repo? Also, as I am in the need of using this quite often, I will be delighted to also contribute to the project.
Thank you very much!

Ive implemented MetadataAccount V3 instructions just waiting on the merge from @mariomatic .
Feel free to use my fork that has it implemented.  https://github.com/BifrostTitan/Solnet.Metaplex
This is what you were looking for. It took me several hours to figure this out.
        if(collectionDetails == 0)
        {
            writer.Write((byte)0);  // 0 = null | No collection details
        }
        else
        {
            writer.Write((byte)1);
            writer.Write((byte)0); // collection detail size sits in an array - this byte defines its position | should always be 0
            writer.Write((ulong)collectionDetails); //collection details size of V1 defined as a ulong

        }


(FACT-2677) Add install.rb

add install.rb
move lib code into lib/facter
fix requires not to use absolute paths
move config files into lib/facter

CLA signed by all contributors.

going to merge because it got really big and we need to unstuck next changes. @Filipovici-Andrei we ca do the cleanup in another PR.


FPGA: add Windows flags to the compile options of loop_fusion and optimize_inner_loop

These two samples were missing the /EHsc Windows flags which was making the Windows compiles to fail.

Hey @jimmytwei, please have a look at this PR - it is ready to be merged, thanks!


markdown headings

Hi @oleander
I've been looking for markdown to BBCode converter for ages and yours is the closest one to what I need. I wanted to add H1 and other heading tags, but for some reason, it doesn't work.
Here is what I changed in markdown.js file:
line 10
methods: ["url", "italic", "underscore", "strong", "quote", "image", "h1"],

after line 25 insert
  self.h1 = function(content) {
    return content.replace(/# ?(.*)/gm, '[size=120][b]$1[/b][/size]');
  };

It is ignoring my
# Heading1

Is my regex wrong or am I missing something else?

Never mind, actually it worked just had to clear the browser cache.

Good that you managed to solve it.


Change WAT home in DC_ComputeNode Computenode.bat file

https://github.com/HydrologicEngineeringCenter/WAT_Configs/blob/b4eb1ed407011b2c643bc2dc7ac96b38fbe0ae80/computenode.bat#L6
Can you change the directory here to reference HEC-WAT instead of a build specific path?
i.e. set WAT_HOME=C:\Programs\HEC-WAT\HEC-WAT

It should be C:\Programs\HEC-WAT\HEC-WAT currently you only have C:\Programs\HEC-WAT.


complete booking bug fixed

It was a small bug. You updated the bookings, but didnt send the updated bookings. I fixed that.

Oh. I see. Missed that somehow 😅


Mask resampling + binary mask option

This is a second try to fix #105 and also makes alpha/mask band read more consistent for all dataset.
This is a breaking change and will need to be tested before release

Note: benchmarks show a slight speed decrease (~10ms) but my guess it that bilinear resampling is a bit slower then nearest.

this now lives in #154


Create session for user credentials

https://www.npmjs.com/package/react-cookies

Not now. closing


can't even open webx

when i tries to open BussinNapturePortable.exe in Another hard drives, it fails to lookup ProgramExecutable, it says
I¥www¥BussinNapturePortable¥App¥AppInfo¥Launcher¥BussinNapturePortable.ini is missing [Launch]:PortableExecutable - what am I to launch?

Uhh, try reinstalling the app in a folder that is maybe something like C:\BussinNapturePortable

i had solved this problem by making the administrator permission to its launcher!
sorry for my useless mind!


[AutoPR mysql/resource-manager/postgresql/resource-manager] [Don't Merge, Service roll out 2/20/2018] Swagger For new rdbms API change for new biz model

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2414

Codecov Report

Merging #1918 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1918   +/-   ##
=======================================
  Coverage   53.02%   53.02%
=======================================
  Files        4710     4710
  Lines      116674   116674
=======================================
  Hits        61869    61869
  Misses      54805    54805

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dcbd0d1...43c18ad. Read the comment docs.


When using Enter as keybind, changing HP via default Token HUD is not possible

When right-clicking token and changing HP there, pressing Enter then opens the Token Health pop-up and does not apply the changed HP in the Token HUD.
The Token Health pop-up should not open when the Token HUD is open.

I couldn't reproduce the behavior of not having it apply the changes. For me, it is applying the change and then opening the dialog.
Anyway, I can see how that can be annoying and having it not be opened when the Token HUD is rendered is a good compromise.

Thank you so much for fixing my issues so quickly!

@mclemente Unfortunately this has not been fixed for me in 1.0.3. It still happens.

What system are you using? Can you test with only this module enabled? The token bar changes should take effect before the dialog opens.

It happens with me using dnd5e with only this module enabled. Current versions of everything (V12, dnd5e 3.3).
I open the Token HUD with right click, enter a number, e.g. "-3" and press enter. It does apply the 3 damage, but then the Token Health pops up immediately.

This also makes changing the token's height very annoying. I had to disable the module for now because of this interference. Would love to see a fix.

There's nothing that I can do about it, by the time the changes are applied, Foundry triggers the keybinding and there is no way to tell if the token was just updated by pressing Enter.
I'll probably revert the original fix since it didn't help at all and made the dialog only pop up when the HUD is isn't rendered.
You could just change the keybinding, though.


i18n

I took the liberty of rebasing/rewording your commits, and I merged them into main. Thank you so much for this contribution. This makes for a much more complete UX! :heart:

这是个给人带来快乐的项目，能做一点微小的工作也很快乐。没有它就没有我的第100次无神论 : )
Google Translate: This is a project that brings people happiness, and it’s very happy to be able to do a little bit of work. There would be no my 100th atheism without it.


hdl_checker: init at 0.7.5-devel

Version tag is a development build from 'master' because the current release tag (0.7.4) won't compile.
Description of changes
https://github.com/suoto/hdl_checker
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ? ] Fits CONTRIBUTING.md.

I've tested compiling on both nixos-23.05 and nixpkgs-unstable. Both work fine when ran from the command-line. Tests were disabled however due to reliance on deprecated packages.
I am in no hurry to package this for 23.11, this can be left for later. I just wanted to make the package available to whoever needs it.

Cancelling this pull request as an equivalent rust-hdl (vhdl-ls) is already available and I am no longer interested in merging this.


OPA Plugin - failed to connect to OPA server

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
<IP_ADDRESS>
Current Behavior
When I try to follow the guide to enable to the OPA Plugin, Kong fails to connect to OPA to fetch a policy as it fails to connect to the OPA server. Kong and OPA are running locally with docker-compose. Both the Kong Gateway and OPA are available on localhost, but Kong arent able to connect to the OPA server. This is both true for the <IP_ADDRESS> version and the 2.5 version of the Kong Gateway.
Steps to reproduce:

Fire up the following docker-compose file:

version: '3.7'
services:
  postgres:
    image: postgres:10.17
    container_name: kong-ee-database
    restart: on-failure
    ports:
    - "5432:5432"
    environment:
      POSTGRES_USER: kong ##admin user password
      POSTGRES_DB: kong
      POSTGRES_PASSWORD: kongpwd
    # volumes:
    # - ./curity/curity-opa-kong-config.xml:/opt/idsvr/etc/init/curity-opa-kong-config.xml
  kong-migrations:
    depends_on:
     - postgres
    image: kong/kong-gateway:<IP_ADDRESS>-alpine
    container_name: kong-ee-migrations
    restart: on-failure
    environment:
     - KONG_DATABASE=postgres
     - KONG_PG_HOST=kong-ee-database
     - KONG_PG_DATABASE=kong
     - KONG_PG_USER=kong
     - KONG_PG_PASSWORD=kongpwd
    command: kong migrations bootstrap --v
  kong:
    depends_on:
     - kong-migrations
    image: kong/kong-gateway:<IP_ADDRESS>-alpine
    container_name: kong-ee
    restart: on-failure
    # volumes:
    #   - ./kong-image/kong.yml:/usr/local/kong/declarative/kong.yml
    ports:
     - "8000:8000"
     - "8001:8001"
     - "8002:8002"
     - "8003:8003"
     - "8004:8004"
     - "8442:8443"
     - "8444:8444"
     - "8445:8445"
    environment:
     - KONG_DATABASE=postgres
     - KONG_PG_HOST=kong-ee-database
     - KONG_PG_DATABASE=kong
     - KONG_PG_USER=kong
     - KONG_PG_PASSWORD=kong2004
    #  - KONG_PLUGINS=bundled,phantom-token,opa
    #  - KONG_LOG_LEVEL=debug
     - KONG_PROXY_ACCESS_LOG=/dev/stdout
     - KONG_ADMIN_ACCESS_LOG=/dev/stdout
     - KONG_PROXY_ERROR_LOG=/dev/stderr
     - KONG_ADMIN_ERROR_LOG=/dev/stderr
     - KONG_PROXY_LISTEN=<IP_ADDRESS>:8000
     - KONG_ADMIN_LISTEN=<IP_ADDRESS>:8001
     - KONG_PORTAL_APP_AUTH=external-oauth2
  opa:
    image: openpolicyagent/opa:latest
    container_name: opa
    ports:
    - "8181:8181"
    volumes:
      - ./opa/policies/:/records
    command: "run --server --addr :8181 /records"

In the ./opa/policies we have the following file:
package example

default allow = false

allowBoolean {
  header_present
}

header_present {
  input.request.http.headers["my-secret-header"] == "open-sesame"
}

allowDetailed = response {
  header_present
  response := {
    "allow": true,
    "headers": {
      "header-from-opa": "accepted",
    },
  }
}

allowDetailed = response {
  not header_present
  response := {
    "allow": false,
    "status": 418,
    "headers": {
      "header-from-opa": "rejected",
    },
  }
}

Add enterprise license

http POST :8001/licenses \
  payload='{"license":{}}

Add dummy service and route

http POST :8001/services \
  name=example_service \
  url='http://mockbin.org'

http :8001/services/example_service/routes \
  paths:='["/mock"]' \
  name=mocking

Add the OPA Plugin

curl -X POST http://<IP_ADDRESS>:8001/services/example_service/plugins \
    --data "name=opa"  \
    --data "config.opa_path=/v1/data/example/allowBoolean" \
    --data "config.opa_host=localhost" \
    --data "config.opa_port=8181"

Try out the mock service

http :8000/mock

Response:

HTTP/1.1 500 Internal Server Error
Connection: keep-alive
Content-Length: 42
Content-Type: application/json; charset=utf-8
Date: Fri, 03 Sep 2021 14:43:03 GMT
Server: kong/<IP_ADDRESS>-enterprise-edition
X-Kong-Response-Latency: 44

{
    "message": "An unexpected error occurred"
}

Kong log:

kong-ee            | 2021/09/03 14:43:03 [error] 25#0: *1904 [kong] handler.lua:122 [opa] failed to get decision from OPA: failed to connect to OPA server(localhost:8181): connection refused, client: <IP_ADDRESS>, server: kong, request: "GET /mock HTTP/1.1", host: "localhost:8000"

Expected Behavior
No response
Steps To Reproduce
No response
Anything else?
No response

Got help from Kong Support. The error was in the OPA Plugin (step 4 above) where the config.opa_host=localhost should be changed to the name of Docker service, i.e. config.opa_host=opa".


Manifold Developers Introduction Page

Make a page that new hires can read and refer to in order to get jumpstarted on Manifold without being completely lost.

Link?

https://picolabs.atlassian.net/wiki/spaces/docs/pages/363364396/Developer+s+Introduction I just posted it in the Manifold slack channel too.


Update Docker to latest CE and remove Spartan workarounds

This pull request adds the following updates:

Rename custom NAT network from nat_network to customnat
Add logic to update Docker to the latest CE version in order to have https://github.com/docker/libnetwork/commit/884eaa0157709a3197b9696981c4f1ce0d86120b commit in the build. This will allow us to remove all the Spartan workarounds to get it working.
Remove Spartan workarounds around the broken Docker version
Add LogFile to the New-DCOSWindowsService utils function
Add logging to file to all the wrapped DCOS services

@paulcallen, @yakman2020. Please take a look at these updates.
This pull request adds logic to update Docker from the Windows slave so that we can run an updated Docker version with all our fixes necessary to run Spartan cleanly.
If you think this looks good, please approve and we can merge.


Supporting shared projects

🚀 Feature Requests
Please add *.projitems to the search pattern in https://github.com/NuKeeperDotNet/NuKeeper/blob/master/NuKeeper.Inspection/RepositoryInspection/ProjectFileReader.cs#L41
Describe the feature
Shared projects utilize 2 files a *.shproj which include all the pieces needed for msbuild to automagically include the source in the target project and a *.projitems file which is basically like a (cs/fs/vb)proj file, these can include references to auto merge in to the target project.

As a working around, you can rename the *.projitems file to a *.csproj file and then update the reference in the *.shproj file as well as any places you included a reference to the shared project. This will let nukeeper inspect work but it will fail to update with an error but this at least lets you check versions.