Support for Mongoose 7

Currently, instrumentation-mongoose explicitly does not support Mongoose 7:
https://github.com/open-telemetry/opentelemetry-js-contrib/blob/82267ab02f8d9b27613b5926089c42d04d4a4a7e/plugins/node/instrumentation-mongoose/src/mongoose.ts#L78-L83
Testing on one of my recently upgraded services that are now span-less, things appear to work out of the box if I just change that constraint. However, I suspect there might be edge cases or breakages I'm not triggering.
Renovate seems to have given up on the automatic bump here, #1420, but the lerna error is pretty opaque to me. Is outside help useful here, or mainly a question of a maintainer having time to look at it?
cc @blumamir since I saw you in the component_owners file

So, finally had some time to take a look at this. As mentioned, the happy path works for me, in a code base which has fixed the breaking changes between v6 and v7. However, just bumping the version in this library does not work quite as smoothly... The main issue is the dropped callback support. This appears to require a somewhat large refactoring to remove it from this library.
Also, what are the compatibility concerns? Do you typically say that it is required to bump instrumented libraries in your application when updating this library?

So, finally had some time to take a look at this. As mentioned, the happy path works for me, in a code base which has fixed the breaking changes between v6 and v7. However, just bumping the version in this library does not work quite as smoothly... The main issue is the dropped callback support. This appears to require a somewhat large refactoring to remove it from this library.
Also, what are the compatibility concerns? Do you typically say that it is required to bump instrumented libraries in your application when updating this library?

We usually don't require that our users update their library to continue receiving telemetry, though this is up to the component owner to decide.It's hard to say for me without knowing the exact details of the instrumented library, changes and instrumentation library, but there are usually two ways to handle this:

introducing new package that supports mongoose >= 7 (<8) with it's own tests etc (this was done with redis when it was bumped to v4)

see https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-redis
see https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-redis-4

supporting both in the same library and adapting the instrumentation code to deal with both versions

see https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-mongodb

this has also different tests for different versions that are run via TAV (see https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-mongodb/.tav.yml)

Thanks @carlpett
As marc mentioned, we usually prefer to introduce new supported major version as a PR here with tav and a human eye to brief the changes and verify what needs to be updated to maintain stability and functionality of the instrumentation.
I could find some time to look at it soon, but your help will be highly appreciated if you can open a PR to do the work + describe what changed so it's easy to review.  Please feel free to reach out in slack or here if you need to discuss changes or assistance in applying a fix.
note that when adding support to a new version, you need to:

update the relevant line in instrumentation.ts as you already pointed out.
Add the new range to tav.yml and run it to verify it is green for all new and old versions
update the README where supported versions is advertised.
Apply any fixes and adaptations to instrumentation code to support new patched functions signatures or data types.

Also, what are the compatibility concerns? Do you typically say that it is required to bump instrumented libraries in your application when updating this library?

Yes.
It is generally always a good recommendation to use up-to-date OTEL packages with wider support and bug fixes. We can't tell if a future major version of instrumented packages will break users code. Actually, the instrumentation can also break on minor and patches, since we patch internal functions which are not committed to follow semver and can introduce refactors for which we are not compatible. For this, we run test-all-versions daily to catch these problems as early as possible.

I gave up last year because I ran out of time, mostly forgot about it, and then now had to rediscover everything again :)
Looking at it, if the instrumentation should support both <7 and >=7, it might be quite complicated. The removal of callback support changes a lot, which seems quite entangled with being supported throughout the library. Would it be feasible to have a different implementation for the older version?
Also, I'm unable to get the tests running, I'll open a separate ticket for that to avoid side-tracking here.

Hi, I have just started testing out OpenTelemetry in our test env and found it super useful. Most of libs are working out of the box with auto injection library (thank you a lot!), except mongoose. We use ^7.0.4 version of mongoose, seems it is not supported yet. What are the plans? I am not JS developer, otherwise would be involved with development part of it, too.

Since this issue was opened mongoose has released another major version. Any plans on supporting those? Mongoose 7.0 has been out for over a year now.

I'd also love to see support for the latest Mongoose versions.
However, for those who might wonder about a "work-around": Using @opentelemetry/instrumentation-mongodb works with Mongoose, as it depends on that package. I've tested it and queries are being traced. I'm aware that this is not a perfect solution, but at least something, until the support for the latest mongoose version is there as well.


refactor(provider-template): HttpClient

Short description of what this resolves:
Update the default http import to the new HttpClient
Ionic Version: 1.x / 2.x / 3.x
3

@danielsogl,
Thanks!
Thanks,
Dan


servers field in event-subscription-template.yaml not in line with API guidelines

Problem description
The servers field in the example file event-subscription-template.yaml does not follow the API guidelines.
Expected behavior
Change the example to follow the API guidelines to avoid introducing misalignment by coping from this example. In particular:

update the servers field

Yes, indeed it needs correction, the guidelines are following:
https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#servers-object
https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#52-api-version-in-url-oas-servers-object
@bigludo7 Can we resolve it within https://github.com/camaraproject/Commonalities/pull/313 ?

Sure !
Please assign it to me.

Request took into account in #313 :)


Investigate whether HTML tags can be included in item names

See #270 , but we need to be sure it doesn't break the core Foundry UI.

Consider this during UI rework.


Validate mission model file on upload

This issue is to add validation of the mission model file on upload.

What kinds of "validation" do we have in mind for this issue? As written, it leaves everything to the imagination.
Are there particular issues that we are considering "validation" in response to?

We want to do three levels of validation:

Validate that the uploaded file has the .jar extension
Validate that the uploaded file actually is a .jar (and not just like a .png with a .jar extension)
Validate that the uploaded JAR is a Mission Model.

As is, we allow and attempt to parse any file that the user uploads, but we ought to outright reject files that don't meet Step 1 and 2. Also, we ought to at least be louder about parse errors if not reject non-mission-model JARs (step 3), since you cannot work with a Mission Model in Aerie if it doesn't parse.

Once we have API versioning, that seems reasonable.
My main reason for wanting to do the parse up front is so that we catch models that Aerie can't work with quickly. For example, if I make a model that has two activity types with the same name, the model will compile, but when I go to work with it, it's useless (since activity types couldn't be loaded due to the name collision).

Can you elaborate on what you mean by "parse"? I understand "parse" as "read a String into a structured data type", but I'm not sure that's what you mean here. Are you looking more to attempt a classload into the JVM? I'd call that "load" more than "parse".

if I make a model that has two activity types with the same name, the model will compile

This ought to be a compilation failure. The annotation processor should catch this. In fact, the merlin.protocol API returns a Map<String, DirectiveType<>>, so from a protocol level it is not even possible to have two activity types with the same name.
The fact that Map.ofEntries throws an error on duplicate keys just means the generated code isn't doing its jobs carefully enough. We should throw a compilation error if the processor detects this -- and it can.


add contains/contained_by filter operators

there are a couple areas that could be smoothed out (eg modify_criterion/comparator where I added conditions to not lower for the array)

old and we don't need it


Add Cargo.lock file

I recently wanted to add a package for protoc-gen-rust to Nixpkgs but was stymied because the buildRustPackage derivation requires a lock file. I considered using a fork for the package instead, but I feel it'd be more optimal to make the change directly here.

Rust recommendation is not to commit Cargo.lock:

If you’re building a non-end product, such as a rust library that other rust packages will depend on, put Cargo.lock in your .gitignore.

https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html

In this case, though, there are also executables being shipped, not just libraries. So I feel that that particular recommendation doesn't apply. If you'd like those executables to be included in reproducible builds, I do think that the lockfile is necessary.

In this case, though, there are also executables being shipped, not just libraries.

But Cargo.lock applies to all of them, including libraries.

Suit yourself. I'll use a fork and protoc-gen-rust will be prevented from inclusion in Nixpkgs.


Touch 4.0 release to see pipelines moving

Description
Some dummy change to see how pipelines take 4.0 version
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

/test ?

/test ?

/test all

For the record, https://issues.redhat.com/browse/DPTP-3394 was created for this. Closing for now.


remove version pin from runtime compiler dependency

avoids installation conflicts due to improper handling of pins in conda-build, where pins from conda_build_config create conflicts with inherited dependency pins, instead of being overridden

@conda-forge-admin please rerender


Change ears repository

Hi!
As the ears crate is unmaintained I forked it and fixed some stuff. Also added Windows ci and uploaded it to crates.io.

Fantastic, this is the crate I was looking for recently but skipped over it because of failing tests and lack of maintenance +1

Ok, thank you


Issue 37128: fixes for user displayName issue on Permissions page and…

… various Study pages / Ext grids

@labkey-jeckels This pull request diff looks much happier with the line endings after @labkey-ians change yesterday with the .gitattributes file.


Write method do not triggers onInput or onchange events

Expected behavior
On write on inputs that generate an XHR the request should be generated
Actual behavior
The input is filled with the text but the XHR request is not sent
Steps to reproduce

Write in input field that have generates XHR request
The event is not trigger

Versions
node v11.10.1
taiko Version: 0.7.1 (Chromium: 74.0.3723.0)

@BorjaRobles Could you please give us an example as to where this happens? It would be easier for us to fix this.

There are some changes pushed in related to write api. Can you please verify if it works fine with master ?
npm install<EMAIL_ADDRESS>-g

@BorjaRobles Please give a try to the latest taiko as @NivedhaSenthil has suggested.

oh looks fixed now ! thx @NivedhaSenthil


Failed to remove instance as device is busy

Description of problem
I want to remove all my instances as follows:
docker rm -f  `docker ps -a -q`

However, it seems that I  FAILED TO REMOVE ANY ONE, the output is:
Error response from daemon: Cannot destroy container b719f5700c1c: Driver devicemapper failed to remove root filesystem b719f5700c1c3f17e6f61506de1326e736d63aa692150957baa82cb882ab02ed: Device is Busy
...
...
FATA[0137] Error: failed to remove one or more containers

But when I exec
docker ps -a

I can't find any instance from the output, it seems to remove them successfully!

Environment details
The docker is running on an instance of openstack using kvm.
krystism@docker:~$ docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8

krystism@docker:~$ docker info
Containers: 13
Images: 351
Storage Driver: devicemapper
 Pool Name: docker-253:1-131744-pool
 Pool Blocksize: 65.54 kB
 Data file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
 Data Space Used: 10.35 GB
 Data Space Total: 107.4 GB
 Metadata Space Used: 18.11 MB
 Metadata Space Total: 2.147 GB
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 3.13.0-35-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 2
Total Memory: 3.861 GiB
Name: docker
ID: ALD7:CBPH:KKHE:KDBQ:GWAF:LXRR:E6Z5:6M5S:3RGY:MA4D:NWKB:QIK7
WARNING: No swap limit support

krystism@docker:~$ uname -a
Linux docker 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Steps to Reproduce

Create some containers.
Try to remove them.
Restart the docker daemon.
Exec "docker ps -a".

Actual Results: All the removed container emerge again.
Expected Results: Should not show any instance.

dup of https://github.com/docker/docker/issues/5771 or https://github.com/docker/docker/issues/5684?

This might be fixed on master by #9886

This is a duplicate of #5684 and #4036.
This particular error will be fixed by #10225. Other errors seen in #4036 have been fixed by #10195.
I'm going to close this now.


Fix streaming test

Replace hardcoded StreamingRecognizeResponse with type name

Well that was silly. LGTM.

Current coverage is 82.16% (diff: 100%)

Merging #841 into master will not change coverage

@@             master       #841   diff @@
==========================================
  Files           323        323
  Lines         12514      12514
  Methods           0          0
  Messages          0          0
  Branches       1641       1641
==========================================
  Hits          10282      10282
  Misses         1804       1804
  Partials        428        428

Powered by Codecov. Last update 87d0cac...1d346a0


Update README.md with the latest client delcaration related changes

Description:
$subject should be done with the changes introduced by https://github.com/ballerina-platform/graphql-tools/pull/94
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

This should include the changes introduced by #99


Add style of change display of overflow text

Add a style to change the display of the overflow text. This will break
between words if possible, and if not possible will force a line wrap
when it hits the maximum with.
/cc @ssalinas

will be nice to not have the command line args go off the screen anymore 💃

@PtrTeixeira Could we see an example of the new wrapping behavior? In general I'd recommend against having dropdown items take up multiple lines and instead use an ellipsis w/ tooltip overflow pattern. But would like to see this in context.

This is what I had part way through the working on this:

I didn't think of using a tooltip to get the full content for the menu items. Will move over to that.

👍 thanks for the suggestion mark

@PtrTeixeira on staging right now it seems that additional arguments are not showing up in the history. A previous list of args with > 1 arg seems to only show the first one.


Anything I need to do in the .bicep files to update to .NET 9.0?

I have the application deployed and working great in Azure, but I want to upgrade the code to use .NET 9.0 and am unsure if I need to make any changes in the .bicep files to get a container in Azure that has .NET 9.0? Or will ACA just take care of it all and it will "just work"?
Thanks,
Stu

So I am guessing that I need to update the following line in the app/Dockerfile from:
FROM mcr.microsoft.com/dotnet/aspnet:8.0 AS base
to
FROM mcr.microsoft.com/dotnet/aspnet:9.0 AS base
Would that be correct, anyone with more Docker experience than me?

Working with .NET 9.0, with a nice performance boost for the WebAssembly load time :-)


Improve typings

I've added some missing functions in the TS typings and fixed some compilation errors. I will keep improving them as I find more issues. #8

Thanks @jorgeyp and @samccone !


Migration for upgrading to 0.16

Updates all rows from all clock tables, setting site_id = 0 WHERE site_id IS NULL

Decided to avoid this for now. I'm making the migration in my app instead, it's a little simpler for something only we need.


Allow ResolverTypeWrapper to return null or Promise

In the linked blog post for the typescript-resolvers plugin
there is a TS error (TS2322) because the users query could
find no matching user and therefore return undefined:
src/resolvers.ts:16:5 - error TS2322: Type '(parent: {}, args: RequireFields<QueryUserArgs, "id">) => { id: string; email: string; profile: { age: number; name: string; }; } | undefined' is not assignable to type 'Resolver<ResolverTypeWrapper<User>, {}, any, RequireFields<QueryUserArgs, "id">> | undefined'.
  Type '(parent: {}, args: RequireFields<QueryUserArgs, "id">) => { id: string; email: string; profile: { age: number; name: string; }; } | undefined' is not assignable to type 'ResolverFn<ResolverTypeWrapper<User>, {}, any, RequireFields<QueryUserArgs, "id">>'.
    Type '{ id: string; email: string; profile: { age: number; name: string; }; } | undefined' is not assignable to type 'ResolverTypeWrapper<User> | Promise<ResolverTypeWrapper<User>>'.
      Type 'undefined' is not assignable to type 'ResolverTypeWrapper<User> | Promise<ResolverTypeWrapper<User>>'.

16     user: (parent, args) => {
       ~~~~

Found 1 error.

I think there is a legitimate case where this would fail
and we'd want to return null or potentially Promise
with Promise<T | null> | T | null.
Blog post is here: https://the-guild.dev/blog/better-type-safety-for-resolvers-with-graphql-codegen

@TylerBrock It is a bit hard for me to grasp what is wrong here and what you are trying to address. Can you please give a detailed explanation of what is actually wrong and how we might fix it?


[v2 sys-mgmt-agent] Fail to connect to system-agent through proxy

🐞 Bug Report
Affected Services

 The issue is located in: system agent
Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Description and Minimal Reproduction

Deploy edgex with security enabled.
Send Ping request with token
GET https://localhost:8443/sys-mgmt-agent/api/v2/ping

🔥 Exception or Error

Response:
{
  "message":"An invalid response was received from the upstream server"
}

Kong log:
2021/05/27 08:19:04 [error] 101#0: *1076 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: kong, request: "GET /sys-mgmt-agent/api/v2/ping HTTP/1.1", upstream: "http://<IP_ADDRESS>:58890/api/v2/ping", host: "<IP_ADDRESS>:8443"

🌍  Your Environment
Deployment Environment:
**EdgeX Version:**Master
Anything else relevant?

@cherrycl , this is because I had not yet gotten to this issue.
https://github.com/edgexfoundry/edgex-compose/issues/103
Transferring this to the compose repo


Fix: add owner reference in workflow context cm

Description of your changes

Fixes #
I have:

[x] Read and followed KubeVela's contribution process.
[x] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

/cc @leejanee

add test case in e2e test , verify that context-store configmap can be deleted after delete application

Will add the test case later.


Task: Data for datepicker in the property pane

3589 unique user has used the ADS date picker in the property pane.
@vasanthappsmith: This is not a burning problem but we can think about how can we avoid layout shift in datepicker while changing months


Need help to enable Sub-GHz for ieee802154_cc13xx_cc26xx

I am looking for some guidance on enabling Sub-GHz for CC13xx.
I am not an expert, but on reading through the CC1352 TRM, it seems like we just need to set the channel correctly. There are two places in the code that needs change it looks like:

Channel setup (11-16)?

https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/ieee802154/ieee802154_cc13xx_cc26xx.c#L81

loDivider in CMD_RADIO_SETUP:

https://github.com/zephyrproject-rtos/zephyr/blob/1342dadc365ee22199e51779185899ddf7478686/drivers/ieee802154/ieee802154_cc13xx_cc26xx.c#L698
Please let me know if you plan to support Sub-GHz for CC13xx in the near future. If not, any guidance you provide in moving forward would be appreciated. Thanks! @bwitherspoon

SubGHz support for the CC13xx/CC26xx was added https://github.com/zephyrproject-rtos/zephyr/pull/29598


Tracking in git?

My question is really a simple one today, and I'm drawing a blank. I'm doing my development work locally via MAMP, and we've got repository set up for our whole WP project on Bitbucket. Due to the needs we have we usually track everything we have in wp-content including themes, etc. I'm trying to add in my changes on a new project I just started up, but I keep getting a notification that the theme has been modified, but it is untracked, and I can't get it to track. I recall you made some changes that the ultimate output is now in the src file, but i'd like to get a little more info/recommendation from you on how to effectively manage our build within the FoundationPress theme package as you've got it set up now.

I'm not sure I understand what you're asking. But to me this seems more like a general question around using Git, than an issue with FoundationPress.  I guess you will be able to get help on this at Stackoverflow.

No worries - really more of a question about approach for how you'd recommend managing via git so that I wouldn't need to delete your git files in order to track my own for update/upgrade reasons.


CouchDB memory consumption increases when deploying on RHEL9

Description
I've noticed that CouchDB's memory usage increases abnormally when Hyperledger Fabric(HLF) is running on certain operating systems.
I deployed HLF v2.5.0 on a VM with RHEL9 installed and deployed a minimal BC network using fabric-samples/test-network.
Then the memory usage of the CouchDB container reached around 1.5GB.
I also found that the same phenomenon occurs when deploying HLF v2.4 or some earlier versions on RHEL9.
On the other hand, when deploying HLF on RHEL8 or Ubuntu, CouchDB memory usage was only about 50MB.
Due to this phenomenon, when a HLF network consisting of 2 Peers×2 organizations is deployed in one VM for example,
the network cannot be started unless 6 GB of VM memory can be secured for CouchDB.
As a result, even a network with a minimum configuration can only be started on a VM with high specifications.
Steps to reproduce
After installing HLF by the method described in "Getting Started" section of hyperledger-fabricdocs, execute the following command.
cd fabric-samples/test-network
network.sh up createChannel -ca -c mychannel -s couchdb -i 2.0.0
network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-javascript/ -ccl javascript

This repository is for Fabric code issues. For CouchDB container issues you'll need to raise through the CouchDB community.


Add PyPy to Travis

Continue #33

Same problem with pypy and pypy3
$ make test-all
- removing old data
- creating new tests/db/ (required for tests)
.Exception in thread Thread-2:
Traceback (most recent call last):
  File "/opt/python/pypy3.5-5.8.0/lib-python/3/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/travis/build/RaRe-Technologies/sqlitedict/sqlitedict.py", line 392, in run
    conn.commit()
  File "/opt/python/pypy3.5-5.8.0/lib_pypy/_sqlite3.py", line 474, in commit
    raise self._get_exception(ret)
_sqlite3.OperationalError: cannot commit transaction - SQL statements in progress

It doesn't work, I close this PR.


ZAP import scan results failing with 'NoneType' object has no attribute 'group'

It appears that if a ZAP xml report is generated with a uri that is not fully qualified, an exception is thrown upon importing it to DefectDojo.
More generally it appears this regex shown in the screenshot showing the stack trace may be too restrictive? Just guessing.
I am using the latest docker image of defect-dojo (appsecpipeline/django-defectdojo)

I have attached 2 scrubbed ZAP report files showing the problem:

'doesnotwork.xml': this is the raw XML file, scrubbed for privacy. Importing this fails with the attached screenshot
'works.xml': I have manually added 'fake.com' to the uri field in the XML file, and this is imported successfully

the only difference between the two are line 12:
in 'doesnotwork':
<uri>http://scrubbed/auth/signOut</uri>
in 'works':
<uri>http://scrubbed.fake.com/auth/signOut</uri>
To reproduce the problem:

attempt to import the 'doesnotwork.xml' file as ZAP scan file, get the attached screenshot.

And heres the copy-pasta of the stack, scrubbed a bit.
Request Method: POST
Request URL: ..../engagement/8/import_scan_results

Django Version: 1.8.10
Python Version: 2.7.10
Installed Applications:
('django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.sites',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'polymorphic',
 'overextends',
 'django.contrib.admin',
 'django.contrib.humanize',
 'gunicorn',
 'tastypie',
 'djangobower',
 'auditlog',
 'dojo',
 'tastypie_swagger',
 'watson',
 'tagging',
 'custom_field',
 'imagekit')
Installed Middleware:
('django.middleware.common.CommonMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware',
 'dojo.middleware.LoginR
[evidence.zip](https://github.com/OWASP/django-DefectDojo/files/688140/evidence.zip)
equiredMiddleware')

Traceback:
File "/django-DefectDojo/venv/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
  132.                     response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/django-DefectDojo/venv/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py" in _wrapped_view
  22.                 return view_func(request, *args, **kwargs)
File "/django-DefectDojo/dojo/engagement/views.py" in import_scan_results
  270.                 parser = import_parser_factory(file, t)
File "/django-DefectDojo/dojo/tools/factory.py" in import_parser_factory
  33.         parser = ZapXmlParser(file, test)
File "/django-DefectDojo/dojo/tools/zap/parser.py" in __init__
  33.             self.items = self.get_items(tree, test)
File "/django-DefectDojo/dojo/tools/zap/parser.py" in get_items
  60.             site = Site(node)
File "/django-DefectDojo/dojo/tools/zap/parser.py" in __init__
  137.             self.items.append(Item(alert))
File "/django-DefectDojo/dojo/tools/zap/parser.py" in __init__
  201.             protocol = mregex.group(1)

Exception Type: AttributeError at /engagement/8/import_scan_results
Exception Value: 'NoneType' object has no attribute 'group'

Here are the xml files in-line
works.xml
<?xml version="1.0"?><OWASPZAPReport version="2.5.0" generated="Thu, 5 Jan 2017 16:43:07">
<site name="http://scrubbed" host="scrubbed" port="80" ssl="false"><alerts><alertitem>
  <pluginid>10010</pluginid>
  <alert>Cookie No HttpOnly Flag</alert>
  <name>Cookie No HttpOnly Flag</name>
  <riskcode>1</riskcode>
  <confidence>2</confidence>
  <riskdesc>Low (Medium)</riskdesc>
  <desc>
A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.
</desc>
  <instances>
  <instance>
  <uri>http://scrubbed.fake.com/auth/signOut</uri>
  <param>scrubbed</param>
  <evidence>Set-Cookie: scrubbed</evidence>
  </instance>
  </instances>
  <count>1</count>
  <solution>
Ensure that the HttpOnly flag is set for all cookies.
</solution>
  <reference>
http://www.owasp.org/index.php/HttpOnly
</reference>
  <cweid>16</cweid>
  <wascid>13</wascid>
</alertitem>
</alerts></site>
</OWASPZAPReport>

doesntwork.xml
<?xml version="1.0"?><OWASPZAPReport version="2.5.0" generated="Thu, 5 Jan 2017 16:43:07">
<site name="http://scrubbed" host="scrubbed" port="80" ssl="false"><alerts><alertitem>
  <pluginid>10010</pluginid>
  <alert>Cookie No HttpOnly Flag</alert>
  <name>Cookie No HttpOnly Flag</name>
  <riskcode>1</riskcode>
  <confidence>2</confidence>
  <riskdesc>Low (Medium)</riskdesc>
  <desc>
A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.
</desc>
  <instances>
  <instance>
  <uri>http://scrubbed/auth/signOut</uri>
  <param>scrubbed</param>
  <evidence>Set-Cookie: scrubbed</evidence>
  </instance>
  </instances>
  <count>1</count>
  <solution>
Ensure that the HttpOnly flag is set for all cookies.
</solution>
  <reference>
http://www.owasp.org/index.php/HttpOnly
</reference>
  <cweid>16</cweid>
  <wascid>13</wascid>
</alertitem>
</alerts></site>
</OWASPZAPReport>

Thanks in advance!

Hi @professorgrumps, thank you for the detailed submission. @grendel513 @aaronweaver this is an interesting one. We could set endpoint to null if the url isn't correctly qualified. Not sure it would be a good idea to store an unqualified url with the qualified endpoints? any thoughts or input? otherwise I'll just not create an endpoint reference for this situation.

Agree with your assessment, thanks for looking into it.
Jay
On Thu, Jan 5, 2017 at 2:35 PM, Greg Anderson<EMAIL_ADDRESS>wrote:

Hi @professorgrumps https://github.com/professorgrumps, thank you for
the detailed submission. @grendel513 https://github.com/grendel513
@aaronweaver https://github.com/aaronweaver this is an interesting one.
We could set endpoint to null if the url isn't correctly qualified. Not
sure it would be a good idea to store an unqualified url with the qualified
endpoints? any thoughts or input? otherwise I'll just not create an
endpoint reference for this situation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OWASP/django-DefectDojo/issues/183#issuecomment-270750150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOQ3ruDyvsTzYHwT53CpECkflGVopGyks5rPVQNgaJpZM4LcB2U
.

Thanks for the response @devGregA  @grendel513  - just a clarification on our use case: we plan to use ZAP reports that are run against internal test hosts whose hostname may infact not be FQ'ed. For example, we may have a shared test instance of an application that internally is resolved by 'http://mytestapp/'

Therefore, we will expect our ZAP reports to have unqualified URLs / URIs identified by a scan.
Hence, would it not make sense to have 'mytestapp' show up as a legit endpoint when imported by defect-dojo?

Hope this makes sense, and excuse my ignorance in the above - just started playing with defect-dojo and I'm excited about the problem it could potentially solve for us!

Hi @professorgrumps haven't forgotten about this just still trying to figure out how to make the use case work.

Sorry for the delay / thanks for the update @devGregA , looking forward to suggestions / resolutions!

@devGregA  - We could have a setting that allows unqualified/invalid URLs.  I don't think we should, by default accept invalid URLs.

@grendel513  - agreed!

@grendel513 is the URL displayed on a finding if it doesn't match the endpoint? I don't believe so? I wonder if we did a if endpoint == None: display URL. If that would resolve this issue. I do not think we should store non-FQDN endpoints due to plans with scan integration 2.0.

Hi everyone, we have discussed this at length and will not be able to support non-FQDN endpoints because we would break our database schema. Endpoints are stored as FQDN's broken into their proper parts / labels. This construction is used in a variety of different views that would have to be altered to accommodate a non-FQDN model. I Wish I had better news :(. I will push an update that handles this case and has an appropriate error message. I'm pretty sure I know @grendel513 's feelings regarding this @aaronweaver @mtesauro please let me know if you feel strongly otherwise.

@professorgrumps also just wanted to highlight that I greatly appreciate the detailed files / steps you provided to reproduce the issue. I'm sorry I couldn't provide a better outcome.

@devGregA Would it be worth adding an option to tag on a local domain suffix? For example in the global settings or on the import level have an option to tack on  a suffix such as corp.local.
Example: If validation for endpoint fails tack on corp.local. qaserver01 --> qaserver01.corp.local

@devGregA @aaronweaver @grendel513 thanks a bunch for the effort, and sorry for the delay in my response.
For our use case and completeness... we have both a suitable workaround as well as a bit of "might have been holding it wrong" - after updating ZAP, then running our acceptance tests thru it and importing the raw export into DDJ as described above... turns our ZAP is now reporting the FQDN in the export. Its also possible our tests were update to explicitly use FQDNs. Either way, its working for us now!
I also see the reason for not fully supporting non-FQDN from DDJ's point of view - certainly makes sense.
Thanks again!


Added reload delay timer adjustment actions for MLAG SSU workflow

Added actions that will help users with SSUs for MLAG switches.  The idea is to use the Set Reload Delay Timers to 0 action before performing the SSU so that interfaces won't go into an errdisable state after the SSU 'reload' and then to use the Revert Reload Delay Timers action to set the reload delay timers back to the values that they initially were at the beginning of the change control.  This should help ensure that the SSU is hitless for all connected hosts while also making sure the switch is in compliance after the SSU is complete.

Thanks for the addition Joe!


Zombie docker container

http://<IP_ADDRESS>/view.html?username=core&jobName=cntk-test-7281-29045
http://<IP_ADDRESS>/view.html?username=core&jobName=cntk-test-32111-16436
http://<IP_ADDRESS>/view.html?username=core&jobName=cntk-test-17823-30716
http://<IP_ADDRESS>/view.html?username=core&jobName=cntk-test-13837-18133
http://<IP_ADDRESS>/view.html?username=core&jobName=job-submit-10782-9665
http://<IP_ADDRESS>/view.html?username=core&jobName=cntk-test-7609-30085
All these job hang when exit

A new instance:
http://<IP_ADDRESS>/view.html?username=core&jobName=cntk-test-23968-15013
Can't exec into it, docker top shows that only a zombie hdfs_mount process exists.
core@paigcr-a-gpu-1035:~$ sudo docker top fb194e6b8a75
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
root                27134               26804               0                   00:26               ?                   00:00:07            [hdfs-mount] <defunct>

It might relate to this issue:
https://github.com/moby/moby/issues/35910

This is due to the OOM issue that we instruct Docker to ignore it. So the system runs into troubles.


fix: scroll to active entity in explorer on route change

Description
Brings active JSObject, API and queries into viewport.
Fixes #11937
Fixes #10740
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:red_circle: Total coverage has decreased
// Code coverage diff between base branch:release and head branch: fix/11937-explorer-scroll-to-active-entity

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
total
56.48 (0)
37.96 (-0.01)
36.27 (0)
56.7 (0)

:green_circle:
app/client/src/pages/Editor/Explorer/Files/index.tsx
76.19 (-0.13)
27.78 (-5.55)
50 (10)
79.49 (-1.07)

:green_circle:
app/client/src/sagas/ModalSagas.ts
36.61 (0.34)
18.42 (-1.02)
23.08 (0)
38.24 (1.01)

:red_circle:
app/client/src/utils/WorkerUtil.ts
89.76 (0)
70.59 (-1.96)
100 (0)
93.33 (0)

/ok-to-test sha=f85a97e

/ok-to-test sha=f12b6f5

/ok-to-test sha=af607c7

/ok-to-test sha=1778e22


Fully support polymorphic relationships

Orbit's standard sources are able to handle polymorphic relationships, but the schema does not yet have a way to define them. Currently the RelationshipDefinition type just allows a string for model. I believe we should allow an array as well (i.e. string | [string]) here. An alternative would be to have a separate field explicitly for polymorphic relationships, but I'm not sure that would be preferable.
This work will need to be paired with on the store's SchemaValidationProcessor to recognize that polymorphic types are allowed.
We should review any other potential areas where polymorphism is not fully supported and add tests that focus on polymorphism.

@dgeb I definitely prefer the idea of allowing an array of strings for type. It seems simple and intuitive. I'm not sure what advantage having a separate field provides.
I poked around in SchemaValidationProcessor and wasn't sure what would need to be updated there. It appears the processor only validates that the types in question exist within the schema. I don't see where it validates the actual relationship definitions.
For example. If I want to add a related record between Model A and Model B for Relationship C. It looks like it only checks that A and B are defined in the schema. I don't see where it checks to see if A is a valid type of C on B.
Does this validation exist and I'm not seeing it? If so, can you point me in the right direction? If not, is this something we should add?
Thanks for your work on this. I'd love to help where I can.

@cibernox I suppose we could also allow a wildcard character, like *, for type. This would mean any type is valid without having to list actual types or validate against them. If you want to support validations, then you would list them in an array.

Hi! We've also ran into a use case where polymorphic relationships are a must.
@cibernox, have you abandoned the PR? Have you used any workaround?
@dgeb Please provide more details on what and where should be done for polymorphism to happen. We're eager to make it work, but unfortunately can't afford spending a week digging into this.
In the worst case we'll have to resort to an ugly workaround such as having a separate property for each relationship type and populating them in a serializer. :(

@lolmaus I was able to reestructure my data model to avoid polymorphic relationships.

Implemented by @ggayowsky in #627 🚀


Not working in my android phone

Speech Recognition Module is not working on my Android phone
When I type
python -m speech_recognition

in my termux app it gets stuck at
A moment of silence, please...

My Phone
Xiaomi Redmi 8a Dual

I don't think that running in termux is a good idea for this package. If you want to use the microphone just save the audio files from inside a proper android app to /sdcard then adb pull them to your laptop to evaluate. It's unlikely that this pip package will work directly with mic through termux. I am not even sure that termux requests proper mic access in it's app manifest.

Okey


Add documentation to Icinga2 modules

What kind of documentation? Did you have a look into the docs folder?

I did not notice the docs over there, so I will close the issue.


x/net/http2: test timeouts on js-wasm builder

2019-12-09T16:08:50-c0dbc17/js-wasm has an interesting timeout failure.
It's not obvious to me whether it is due to a bug in the test, a bug in the js/wasm standard library, or a bug in x/net/http2 or one of its dependencies that happens to be exposed by the different goroutine scheduling on js/wasm.
The presence of a goroutine blocked in net.(*bufferedPipe).Read via crypto/tls makes me suspect a concurrency bug in either golang.org/x/net/http2 or crypto/tls, but admittedly that evidence is not compelling.
I also can't reliably determine how often this occurs or on what platforms because I can't fetch most of the x/net logs (#35515).
CC @bradfitz @FiloSottile @tombergan

The earliest of these failures I could find by manual inspection of the dashboard is https://build.golang.org/log/8d467bcc05d2e38b1b903835bb15858dfc547a62, at CL 208798.

That's also in TestIssue20704Race rather than TestServer_Push_RejectAfterGoAway, so retitling.
The failure mode is otherwise the same: stuff blocked in golang.org/x/net/http2.readFrameHeader and crypto/tls.(*Conn).Read, and runnable goroutines otherwise. Maybe the tests are just too slow overall on that builder.

2020-05-28T22:51:25-3c3fba1/js-wasm](https://build.golang.org/log/0aa1bda5f467f2ae4b476f4c9642b25b66fd880e)
2020-04-21T23:12:49-e086a09/js-wasm
2020-03-24T14:37:07-d3edc99/js-wasm
2020-03-20T22:07:50-118fecf/js-wasm
2020-03-19T23:41:17-63522db/js-wasm

CC @neelance in case you haven't seen this one.


Highlighter not working correctly in touch screen mode

Describe the bug 📝
In touch screen mode, the objects cannot be selected by touching the screen.  The bug can be found in the documentation https://docs.thatopen.com/Tutorials/Components/Front/Highlighter
Reproduction ▶
No response
Steps to reproduce 🔢
No response
System Info 💻
System:
    OS: Windows 11 10.0.22631
    CPU: (32) x64 Intel(R) Core(TM) i9-14900HX
    Memory: 5.25 GB / 15.63 GB
  Binaries:
    Node: 21.7.2 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527

Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

Fixed from<EMAIL_ADDRESS>

Thank you for your update but I tried just now with this version<EMAIL_ADDRESS>but the bug is still there

It is the same. Is my Highlighter setup wrong?

Forget about that boss, it works now, thank you


Allow custom databases

Right now, only tables can be made. This means it is pretty awkward to run a SELECT query on multiple tables at once, because you have to choose one (arbitrarily) to call .query on.
My suggestion for the syntax is:
// create a database (should it be called Database of SQLDatabase?)
const db = new Database(`CREATE DATABASE db`);
await db.create();

// create a table on that database (same problem as above. should we use a prefix?)
const tbl = new Table(`CREATE TABLE tbl`, db);
await tbl.create();

// query that table through one of two methods
// method 1: through the tbl class
tbl.query(`SELECT * FROM ${tbl.name}`);
// method 2: through the parent db
db.query(`SELECT * FROM ${tbl.name}`);

It is basically the same API as a table (has a name, query method, etc) but when db.create() is called it creates a Dexie Database instead of a table.
I think we should still allow creating a table without providing a db as a second argument since for most only one table is needed and adding a Database will just increase complexity.

Solved in the above commit. The API used is identical to what is outlined above in this post.
The default DB name is __JSQL_DEFAULT__, and a custom name can be provided through the second argument of the Table constructor.


feat: use maxNodeDepth + includeShadowTree

Use maxNodeDepth and includeShadowTree in CDP serialization.

Silly me. I regenerated expectations with Chrome Dev. Will do that with Canary tomorrow

I think this is finally ready to go. Fingers crossed!


Update Composer dependencies (2021-06-01-00-12)

Visual regression test passed!
View the visual regression test report


[SSoC 2.0] FAQ template website Ready

🛠 Issue (Number) - 1633

Closes #1633
Description

FAQ is used for many productive websites.
So, i have create a template for the same

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@zugzwang03 @TusharKesarwani @harshit-paneri sir, please review this pr

https://github.com/TusharKesarwani/Front-End-Projects/tree/main/Projects/FAQ Page
Already present in the repo


Initial changes to get website themed and set up

Here is a web font repo if you want to change to a serif like discussed
google fonts


Add a new right arrow icon

In the new integration setting project, we have a feature to make a panel expand and collapse, so we would like to add a new right arrow icon to be used to together with the existing IconArrowDropDown.
Here's the design from Polly Lee and she has provided me the svg file for the new right arrow icon.

^ @dbecherdialpad @tedgoas-dialpad
Not sure what's the right process here, I guess I need your approval before submitting the PR?

@linlidialpad Generally myself, Josh, or David review / approve. I'll add us all, thanks for the PR!

@linlidialpad Or I guess you have to do that since it's your PR?

@tedgoas-dialpad yep, I will submit the PR soon. Btw, can you grant me write permission to this repo? I cannot push a remote branch at the moment. Thanks!


how do i install?

linux/arch

I think you need rust + cargo and then run the following commands:
git clone git@github.com:lapce/lapce.git
cd lapce
cargo build

Failed to build:
lapce> error: failed to sync
lapce> Caused by:
lapce>   found duplicate version of package `xi-rope v0.3.0` vendored from two sources:
lapce>          source 1: registry `crates-io`
lapce>          source 2: https://github.com/lapce/xi-editor#5578c725
lapce> Traceback (most recent call last):
lapce>   File "/nix/store/qcr9904iv7flbkd9g56rk5fc11lyn7df-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 42, in <module>
lapce>     main()
lapce>   File "/nix/store/qcr9904iv7flbkd9g56rk5fc11lyn7df-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 17, in main
lapce>     assert list(data.keys()) == ["source"]
lapce> AssertionError

clone and run make help it'll give you targets to try out

You'll need to install cmake and freetype2 (libfreetype6-dev) on Ubuntu 21.10 if they are not already present, plus also install packages to fix the inevitable linker errors (https://github.com/lapce/lapce/issues/11)
sudo apt install cmake libfreetype6-dev libxkbcommon-dev libxcb-xfixes0-dev libxcb-shape0-dev

Failed to build:
lapce> error: failed to sync
lapce> Caused by:
lapce>   found duplicate version of package `xi-rope v0.3.0` vendored from two sources:
lapce>          source 1: registry `crates-io`
lapce>          source 2: https://github.com/lapce/xi-editor#5578c725
lapce> Traceback (most recent call last):
lapce>   File "/nix/store/qcr9904iv7flbkd9g56rk5fc11lyn7df-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 42, in <module>
lapce>     main()
lapce>   File "/nix/store/qcr9904iv7flbkd9g56rk5fc11lyn7df-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 17, in main
lapce>     assert list(data.keys()) == ["source"]
lapce> AssertionError

Seems like nix can't handle multiple versions of the same crate with the same version string. Try building using cargo directly instead of nix.

Seems like nix can't handle multiple versions of the same crate with the same version string. Try building using cargo directly instead of nix.

I've tried, the same problem.

This one liner will build lapce from git without to clone anything(of course dependences needs to be installed manually)
cargo install --git https://github.com/lapce/lapce lapce --locked

This one liner will build lapce from git without to clone anything(of course dependences needs to be installed manually)
cargo install --git https://github.com/lapce/lapce lapce --locked

Would you happen to know what all deps are needed? Would like to verify i have everything setup before i try again.

I'm using Arch and everything I needed to build was cmake and rust.
sudo pacman -S rust cmake
git clone git@github.com:lapce/lapce.git
cd lapse
make install

Failed to build:
lapce> error: failed to sync
lapce> Caused by:
lapce>   found duplicate version of package `xi-rope v0.3.0` vendored from two sources:
lapce>          source 1: registry `crates-io`
lapce>          source 2: https://github.com/lapce/xi-editor#5578c725
lapce> Traceback (most recent call last):
lapce>   File "/nix/store/qcr9904iv7flbkd9g56rk5fc11lyn7df-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 42, in <module>
lapce>     main()
lapce>   File "/nix/store/qcr9904iv7flbkd9g56rk5fc11lyn7df-cargo-vendor-normalise/bin/.cargo-vendor-normalise-wrapped", line 17, in main
lapce>     assert list(data.keys()) == ["source"]
lapce> AssertionError

Seems like nix can't handle multiple versions of the same crate with the same version string. Try building using cargo directly instead of nix.

The problem is not nix, the error is thrown by cargo, the error comes out even before the build starts while getting vendor dependencies.
cargo can process any number of the same crate from both different versions and from different sources, provided that the code is written correctly in the target application, more than once I've met such applications where one crate had different sources and versions.
If we run cargo vendor to get vendored sources we get the same error
❯ cargo vendor --manifest-path Cargo.toml
error: failed to sync

Caused by:
  found duplicate version of package `xi-rope v0.3.0` vendored from two sources:

  	source 1: registry `crates-io`
  	source 2: https://github.com/lapce/xi-editor#5578c725

This shouldn't be
Rust 1.57.0

I see. cargo build accepts it just fine. It only breaks cargo vendor, which isn't too surprising as cargo vendor produces a single (directory) registry and within a single registry there can't be duplicate versions.

This is what i did on this regolith (based on ubuntu) distribution
apt install libfreetype6-dev libexpat1-dev libx11-xcb-dev

yet i am still getting this error
...
nux-gnu/lib/libcore-0e3656b1fda5fd7b.rlib" "-Wl,--end-group" "/home/ymo/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcompiler_builtins-5c77a3b4d3711371.rlib" "-Wl,-Bdynamic" "-lz" "-ldl" "-lxcb" "-lxcb-render" "-lxcb-shape" "-lxcb-xfixes" "-lxkbcommon" "-ldl" "-lexpat" "-lfreetype" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-Wl,--eh-frame-hdr" "-Wl,-znoexecstack" "-L" "/home/ymo/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/home/ymo/3rdp/github/lapce/lapce-src/lapce-master/target/debug/deps/lapce-40bd144e32277fd2" "-Wl,--gc-sections" "-pie" "-Wl,-zrelro,-znow" "-nodefaultlibs"
  = note: /usr/bin/ld: cannot find -lxcb-render
          /usr/bin/ld: cannot find -lxcb-shape
          /usr/bin/ld: cannot find -lxcb-xfixes
          /usr/bin/ld: cannot find -lxkbcommon
          collect2: error: ld returned 1 exit status

I would really appreciate if someone can put the required libraries in a Readme


Emissary can't find tlsSecret for Ingress resource

Describe the bug
Hello, when I'm trying to create Ingress resource with TLS enables using the manifest below:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: kubia-ambassador-ingress
  annotations:
    kubernetes.io/ingress.class: ambassador
spec:
  tls:
  - hosts:
      - host.example.com
    secretName: example-tls-secret
  rules:
  - host: host.example.com
    http:
      paths:
      - path: /kubia
        pathType: Prefix
        backend:
          service:
            name: kubia-service
            port:
              number: 80

I'm getting the following error:
2021-12-02 16:50:31 diagd 2.0.5 [P21TAEW] ERROR: Secret example-tls-secret.default unknown
2021-12-02 16:50:31 diagd 2.0.5 [P21TAEW] ERROR: Host kubia-ambassador-ingress-0-0: invalid TLS secret example-tls-secret, marking inactive

At the same time if I will use native emissary resources then all is Ok with the same secret:
apiVersion: getambassador.io/v3alpha1
kind: Host
metadata:
  name: minimal-host
spec:
  tlsSecret:
    name: example-tls-secret
  hostname: host.example.com
  mappingSelector:
    matchLabels:
      examplehost: host
  requestPolicy:
    insecure:
      action: Route
---
apiVersion: getambassador.io/v3alpha1
kind: Mapping
metadata:
  name: quote-backend
spec:
  hostname: "*"
  prefix: /backend/
  service: kubia-service:80

Also I've tried to obtain TLS certificate automatically using cert-manager and in such case I'm getting the absolutely same error.
I have a bunch of my test resources in namespace default and emissary-ingress in a separate one. Do I miss something or may this be a bug? Can you please help to understand.
To Reproduce
Steps to reproduce the behavior:
Deploy Ingress resource with TLS secret presented.
Expected behavior
Ingress resource works absolutely the same way as Host + Mapping resources.
Versions (please complete the following information):

Ambassador: 2.0.5
Azure Kubernetes Service
Version v1.19.11
Helm Chart version emissary-ingress-7.1.10

This is still an issue in Emissary 2.2.2. workaround is to create the following TLSContext and referencing the Host that was auto-created for Ingress resource. Such host does not exist in the K8S api but Emissary logs show that it is named $ingressname-0-0 so the TLSContext looks like this :
apiVersion: getambassador.io/v3alpha1
kind: TLSContext
metadata:
  name: ingress-tls
spec:
  hosts:
    - ingressname-0-0
  secret: ingress-tls-prod

Closing to prioritize issues without available workarounds.

The fix that my colleague added in https://github.com/emissary-ingress/emissary/pull/4607 works for my case at least. Hoping it'll be merged quickly, but can be tested with this image in the meantime: olemarkus/emissary:3.2.1-0.20221006115358-fdcb80b50ad7-dirty.1665227182

Let's not just close issues because they have a workaround. Closing means we're not going to do anything about the issue. Not the same as de-prioritizing it over other items.

Fixed via https://github.com/emissary-ingress/emissary/pull/4610 thanks to @olemarkus. Should be available in the next release of Emissary/Edge Stack (sometime this week or early next week). I'll close out this issue after the release.

Ok, I'm going to close this issue now since we just released emissary 3.3.0 with the fix for this. Please re-open this issue if you have any problems with the fix in that release.


What if we called Microcosm instances repo  instead of app?

var app = new Microcosm() has been gnawing at me for a while. Particularly inside of Presenter intent callbacks, I really like how this reads:
class PlanetsPresenter extends Presenter {

  onCreate(repo, props) {
    return repo.push(createPlanet, props)
  }

  // ...
  render() {
    return
  }

}

Also open to other suggestions. store came to mind, but that's not really accurate.

victory


HTTP Endpoints don't send a response or send incomplete responses if the prepare function returns anything.

Describe the bug
Whenever the prepare function of src/setup.js returns anything (headers, etc.), the HTTP endpoint causes an Error: Transferred a partial file. This does not happen if the prepare function is not present or does not return anything.
Logs
There is not much to see here. I've only tested the endpoints using Insomnia, so no browser logs. (Though, I suspect there wouldn't be any aside from the aforementioned partial fire error.)
yarn run v1.22.5
warning package.json: No license field
$ svelte-kit dev
(node:83958) ExperimentalWarning: The ESM module loader is experimental.
> Listening on http://localhost:3000

To Reproduce
The issue happens after a fresh install of Kit. My setup options were to disable TS in components, and to use SCSS for preprocessing.
I've made a repo to show exactly where the issue occurs: @didier/svelte-kit-broken-endpoints. See src/setup.js for an example.
Expected behavior
I would expect the endpoint to send a respond, irregardless of whatever the prepare function does and returns.
Stacktraces
None, no visible errors occur besides the HTTP client warning me of the Error: Transferred a partial file.
Information about your SvelteKit Installation:
System:
  OS: macOS 11.2.3
  CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Memory: 156.12 MB / 16.00 GB
  Shell: 5.8 - /bin/zsh

Binaries:
  Node: 12.17.0 - ~/.nvm/versions/node/v12.17.0/bin/node
  Yarn: 1.22.5 - /usr/local/bin/yarn
  npm: 6.14.4 - ~/.nvm/versions/node/v12.17.0/bin/npm
  Watchman: 4.9.0 - /usr/local/bin/watchman

Browsers:
  Brave Browser: <IP_ADDRESS>
  Firefox: 83.0
  Firefox Developer Edition: 85.0
  Firefox Nightly: 74.0a1
  Safari: 14.0.3

npmPackages:
  @sveltejs/kit: ^1.0.0-next.55 => 1.0.0-next.55
  svelte: ^3.29.0 => 3.35.0

Severity
This issue is blocking usage of SvelteKit entirely, as HTTP Endpoints are part of the core functionality.
Additional context
I've had contact with @antony about this. Raising the issue here so other contributors can take a look.

The prepare example in the repo overwrites the response headers with the request headers, which also includes stuff like content-length headers, which I suspect is what is happening considering the Error: Transferred a partial file.
Are you able to replicate this without overwriting the response headers with the request headers?

Ah, that is an interesting angle I hadn't yet looked at. That would make sense. I'll try to recreate it as soon as I get the chance. Having said that: if what you mentioned is indeed the reason for this error, I think this could be a useful tip in the docs. Because I would expect returning the arguments to not break the response.

I've done some more testing. I'm not entirely sure what is going on.
The following function causes the error, presumably because of content length not matching.
export async function prepare({ headers }) {
  return {
    headers,
  };
}

So I tried each incoming header individually. Turns out, when you still return everything like this, nothing breaks.
Example 1: Return all headers
This was my first approach. Quickly found out this doesn't really matter as its the header key of the response that's causing the error.
export async function prepare({ headers }) {

  // Destructure every part of the headers
  const { host, cookie, accept } = headers
  const userAgent = headers['user-agent']
  const contentType = headers['content-type']
  const contentLength = headers['content-length']

  return {
    host,
    cookie,
    userAgent,
    contentType,
    contentLength,
    accept,
  }
}

Example 2: 'Rebuild' header object and return
This example returns the header key in the response just as if you would return it directly. However, this example does not break the response. Am I missing something?
export async function prepare({ headers }) {
  // Destructure every part of the headers
  const { host, cookie, accept } = headers
  const userAgent = headers['user-agent']
  const contentType = headers['content-type']
  const contentLength = headers['content-length']

  return {
    headers: {
      host,
      cookie,
      userAgent,
      contentType,
      contentLength,
      accept,
    },
  }
}

In example 2 you are setting the header contentLength, not content-length, so there is no issue. Change it to 'content-length': contentLength and you should see the same behavior as the original code.

Oh, you're totally right. Been a long day 😅. That does indeed replicate the issue. I don't think this is a bug then—though I still think this could be mentioned in the docs, as this can be confusing for new users. Especially when coming from Sapper. Do you agree?

I've certainly seen this specific mistake crop up a number of times, so it can definitely be a documentation exercise.

Note that prepare has been replaced by getContext: https://kit.svelte.dev/docs#hooks

Closing since getContext no longer returns a response header, and handle takes in a request object instead, so there's no longer a header -> header function signature.


Auto Refresh when Re-accessing Release Note / Extensions Instructions tabs

I know this has been reported before. I'm just reiterating how retarded it is that tabs "auto-refresh/reload" on access/focus.
You throw up the release notes on update and then it loses our place every time we re-select the tab.
Same with extension instructions and notes.
 Why is there no setting to change it?

/duplicate of #27498


web socket keep alive no longer working version upgraded from v17 to v18

Hi
we are running envoy proxy in front of a janus WebRTC server using websockets
Using envoy version envoy :
version: d6a4496e712d7a2335b26e2f76210d5904002c26/1.17.1/clean-getenvoy-bb8060d-envoy/RELEASE/BoringSSL works fine and this works and I we can see two way keep alive going over the websocket.
When we update the envoy proxy to version to:
envoy  version: d362e791eb9e4efa8d87f6d878740e72dc8330ac/1.18.2/clean-getenvoy-76c310e-envoy/RELEASE/BoringSSL
the keep alive no longer works and therefore our sessions disconnect .
the envoy.yaml is basically the default and other than any existing changes to v3 api .
Suspect its related to  "max_stream_duration"
Can anyone advise ?

@alyssawilk might know if something has changed in this area

could be related to https://github.com/envoyproxy/envoy/issues/16129 ?


Lab content: Align difficulty of R and Py exercises

Some exercises (e.g. 2, 3) differ in that the R solution is in base R while the Python solution is in PyTorch. It maybe makes sense to start a bit earlier with TensorFlow in R, but at the same time also having a "base Python" version would maybe help to not overwhelm students.

Now in slds-lmu/lecture_i2dl/issues


merge master to live-based branch

Docs Build status updates of commit 9d391b8:
:clock10: Full build: the average full build time is 22 min(s) 20 sec(s), this is based on the last 53 build(s) for this repository.

Docs Build status updates of commit 9d391b8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

README.md
:white_check_mark:Succeeded

azps-1.8.0/Az.ApiManagement/Update-AzApiManagementRegion.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Blueprint/New-AzBlueprintAssignment.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Compute/Add-AzImageDataDisk.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Compute/Az.Compute.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Compute/New-AzImage.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Compute/New-AzVM.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Compute/New-AzVmss.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Compute/Set-AzDiskImageReference.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Compute/Set-AzDiskUpdateDiskEncryptionKey.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Compute/Set-AzSnapshotImageReference.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.DataLakeStore/Get-AzDataLakeStoreItemPermission.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.DataLakeStore/Restore-AzDataLakeStoreDeletedItem.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.FrontDoor/New-AzFrontDoorRoutingRuleObject.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.KeyVault/Set-AzKeyVaultAccessPolicy.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Monitor/Set-AzActivityLogAlert.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/New-AzApplicationGatewayFirewallPolicy.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/New-AzNetworkSecurityGroup.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Network/Remove-AzNetworkInterfaceTapConfig.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.RecoveryServices/Get-AzRecoveryServicesAsrProtectionContainerMapping.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Sql/Add-AzSqlDatabaseToFailoverGroup.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Sql/Az.Sql.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Sql/Set-AzSqlServerActiveDirectoryAdministrator.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Sql/Update-AzSqlSyncSchema.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Storage/Get-AzStorageUsage.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Websites/Switch-AzWebAppSlot.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-2.4.0/Az.ApplicationInsights/Remove-AzApplicationInsightsApiKey.md
:white_check_mark:Succeeded

azps-2.4.0/Az.Automation/Register-AzAutomationDscNode.md
:white_check_mark:Succeeded

azps-2.4.0/Az.Blueprint/New-AzBlueprintAssignment.md
:white_check_mark:Succeeded

azps-2.4.0/Az.Blueprint/Publish-AzBlueprint.md
:white_check_mark:Succeeded

azps-2.4.0/Az.Blueprint/Set-AzBlueprintAssignment.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/Az.CognitiveServices.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/Get-AzCognitiveServicesAccount.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/Get-AzCognitiveServicesAccountKey.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/Get-AzCognitiveServicesAccountSku.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/Get-AzCognitiveServicesAccountType.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/Get-AzCognitiveServicesAccountUsage.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/New-AzCognitiveServicesAccount.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/New-AzCognitiveServicesAccountKey.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/Remove-AzCognitiveServicesAccount.md
:white_check_mark:Succeeded

azps-2.4.0/Az.CognitiveServices/Set-AzCognitiveServicesAccount.md
:white_check_mark:Succeeded

azps-2.4.0/Az.ContainerRegistry/Get-AzContainerRegistry.md
:white_check_mark:Succeeded

azps-2.4.0/Az.ContainerRegistry/Get-AzContainerRegistryCredential.md
:white_check_mark:Succeeded

azps-2.4.0/Az.ContainerRegistry/Get-AzContainerRegistryReplication.md
:white_check_mark:Succeeded

azps-2.4.0/Az.ContainerRegistry/Get-AzContainerRegistryWebhook.md
:white_check_mark:Succeeded

azps-2.4.0/Az.ContainerRegistry/Get-AzContainerRegistryWebhookEvent.md
:white_check_mark:Succeeded

azps-2.4.0/Az.ContainerRegistry/New-AzContainerRegistry.md
:white_check_mark:Succeeded

azps-2.4.0/Az.ContainerRegistry/New-AzContainerRegistryReplication.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit ede31e5:
:clock10: Full build: the average full build time is 22 min(s) 7 sec(s), this is based on the last 54 build(s) for this repository.

Docs Build status updates of commit ede31e5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

docfx.json
:white_check_mark:Succeeded

docs-conceptual/azps-1.8.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-1.8.0)

docs-conceptual/azps-1.8.0/install-az-ps.md
:white_check_mark:Succeeded
View (azps-1.8.0)

docs-conceptual/azps-1.8.0/manage-subscriptions-azureps.md
:white_check_mark:Succeeded
View (azps-1.8.0)

docs-conceptual/azps-1.8.0/new-azureps-module-az.md
:white_check_mark:Succeeded
View (azps-1.8.0)

docs-conceptual/azps-1.8.0/uninstall-az-ps.md
:white_check_mark:Succeeded
View (azps-1.8.0)

docs-conceptual/azps-2.5.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-2.5.0)

docs-conceptual/azps-2.5.0/install-az-ps.md
:white_check_mark:Succeeded
View (azps-2.5.0)

docs-conceptual/azps-2.5.0/new-azureps-module-az.md
:white_check_mark:Succeeded
View (azps-2.5.0)

docs-conceptual/azps-2.5.0/using-experimental-modules.md
:white_check_mark:Succeeded

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


How can I use an Image object from dart:io  instead of image provider to display image ?

I am using ImagePicker package to get image and then using readasbytes to convert it into Uint8list  then using decodeImageFromList function of dart:io to get image object ,now how can I display this .

You can get file from ImagePicker.
PickedFile? pickedFile = await ImagePicker().getImage(source: ImageSource.gallery);
if (pickedFile != null) {
   File file = File(pickedFile.path);
}

Then use FileImage ImageProvider.
PhotoView(
	imageProvider: FileImage(file),
)

@FaKenKoala  thnx will try that.


Removed hook

Removed the preHandler hook and replaced with  a request decorator, users can easily add the hook if necessary (see README changes).
Also, if JWT validation or webhook call fails, do not throw: just the user is not added.

@mcollina PTAL


Start working on faster CI

Resolves #132

This has shaved about 2 minutes off of the amount of time it typically takes to execute tests.

I believe we had Docker caching but it was removed because it was taking up too much space. Any ideas on how we can bring that back?


java.lang.VerifyError: Bad return type

create table sink_redis(
name string,
level string,
age string)
with (
'connector'='redis',
'host'='<IP_ADDRESS>',
'port'='6379',
'redis-mode'='single',
'password'='123456',
'command'='hset');

select * from  sink_redis;

[ERROR] Could not execute SQL statement. Reason:
java.lang.VerifyError: Bad return type
Exception Details:
Location:  org/apache/flink/streaming/connectors/redis/common/mapper/row/sink/RowRedisSinkMapper.getCommandDescription()Lorg/apache/flink/streaming/connectors/redis/common/mapper/RedisCommandBaseDescription; @4: areturn
Reason:
Type 'org/apache/flink/streaming/connectors/redis/common/mapper/RedisCommandDescription' (current frame, stack[0]) is not assignable to 'org/apache/flink/streaming/connectors/redis/common/mapper/RedisCommandBaseDescription' (from method signature)
Current Frame:
bci: @4
flags: { }
locals: { 'org/apache/flink/streaming/connectors/redis/common/mapper/row/sink/RowRedisSinkMapper' }
stack: { 'org/apache/flink/streaming/connectors/redis/common/mapper/RedisCommandDescription' }
Bytecode:
0x0000000: 2ab6 0013 b0
I used sql-client,Flink version is 1.13.6.

do not support redis source table,just join or sink.

close

close


Use the-graph 0.6 from NPM

Editing a graph
    component search
        should add a node when result is clicked

Has intermittent failures on Saucelabs, sometimes on IE, sometimes on Safari

Looks like VersionEye picks up bower license for the-graph, which was indeed missing. Added in 0.6.1


Isaac/pay usage tracker schema

Problem solved

update usage tracker schema with pay fields

chainName: String

tokenSymbol: String

dstChainId: UInt64

dstTokenAddress: String

dstChainName: String

dstTokenSymbol: String

msLatency: UInt64

toAmountUSDCents: UInt64

secondaryProvider: String

onRampId: String

Changes made

[x] service-utils: Update usage tracker schema

How to test
Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
Address:

PR-Codex overview
The focus of this PR is to add new fields to the usage tracking schema for Cloudflare worker.
Detailed summary

Added chainName, tokenSymbol, dstChainId, dstTokenAddress, dstChainName, dstTokenSymbol, msLatency, toAmountUSDCents, secondaryProvider, and onRampId fields to the usage.ts file for Cloudflare worker.
Updated the publishUsageEvents function signature.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@IDubuque please fix the lint issue, then add the merge-queue label to have this auto-merge when ready


Fix ProductFun constructor when row/column has size 1

example is
ProductFun(exp(-x^2-y^2),Disk())

This is fixed by @a75477c7a19da4b0dfd6184b0591013983a0ebfa.
There are a couple more issues with ProductFun maybe we can go through a little more thoroughly after feat-bivar is merged:
I'm not sure I understand why ProductFun is sometimes constructed by a LowRankFun. This is lines 57, 84 & 85 in ProductFun.jl.
I don't think chopping in the ProductFun constructor by a matrix of coefficients is the right place. The chopping should be specified before that stage in other constructors (and almost always is anyway)

Example was meant to be ProductFun((x,y)->exp(-x^2-y^2),Disk()).  Looks like Mikael fixed this!


Check if joining a channel is successful (or get a list of channel)

Hello, I have a game and I want the user to input account name, secret and channel for the game to join, and I want to check thoses parameters against invalid parameters, and I didn't see anything about the channel, I'm not really familiar to Twitch and I'm not sure if this is relevant but I don't want the user to just wait for ever, thinking the game is busy joining channel even if it's not.

I'm sorry, completely missed this issue. This is possible by checking if the channel_data_received signal is emitted - it is only emitted once the initial channel tags have been sent.
I'm currently rewriting the entire plugin which will make everything much easier.


Kibbeh: Room chat auto scroll is not working

I think @benawad commented out the auto-scroll logic, probably because it had some efficiency problem.
https://user-images.githubusercontent.com/38838675/112665191-9c0b3080-8e7c-11eb-99cb-b7916ab35e2b.mp4

This seems even more broken now, I don't even have a chat scroll.
https://user-images.githubusercontent.com/56125930/112697879-69fbcd80-8e80-11eb-808c-9f3d181d9de3.mov

I believe this has been fixed, can you confirm? @nadirabbas @vishy-dev

yeah


Text Tool gets Insert Mode in addition to Overwrite Mode

Feature Proposal

Use Cases

Ofc overall overwrite mode is the right mode for an ASCII Art software in general

But sometimes you may want to correct text by normal text insertion

Doing that with an overwrite mode can be quite tedious:

Move text with the move tool
Then type in text in newly free blank postion
Notice you have a few blanks to few or too many
Move text with the move tool
… until you finally got it.

Or export, paste into other text editor, perform insertions there, then clear all and paste back.

… also an interrupted not so smooth workflow.

So having an insert mode, would definitely pay off for some situations.

Or as all other tool shortcuts are bound to the alt key, feel free to make it alt-i and alt-o
But ensure to never conflict with the other tool mnemonics,
see section "Tool shortcuts" in #238


pb.h: Fix build on MSVC

Apparently MSVC lacks C-style static asserts, but it does have C++ style static asserts even in C code. Monado has used nanopb with this patch for some time and it seems to work fine.

Can you elaborate on which MSVC version and with what compiler options?
The automatic CI builds run with Visual Studio 2019 and /std:c11, and haven't needed this option.
If this is specifically about C99 standard, it makes sense to make the #ifdef conditional on that.

All of them fail to build in Monado CI, _Static_assert isn't available on our CI at least.

https://gitlab.freedesktop.org/ryan.pavlik/monado/-/jobs/33803634#L242

Okay it seems /std:c11 did the trick, or in our case setting set(CMAKE_C_STANDARD 11).

Ok, it seems that MSVC defaults to some C89/C99 hybrid.
For general programming, it certainly makes sense to use standards from this century.
But I added a commit that should fix this in branch now, if it is easy for you, could you check if commit e57ec4a works without /std:c11?

Yes, that does seem to work. yeah the C support in MSVC is not great and very weird by default.

Thanks for testing!

Thank you for the change, yeah agreed setting c11 is probably not a big ask. We just hadn't done it, but doing it now. But probably is good to also support the default hybrid C89/C99 as well.

@akashthakur76 reported in commit comments that they get "expected declaration specifiers or '...' before numeric constant" in line 200: PB_STATIC_ASSERT(1, STATIC_ASSERT_IS_NOT_WORKING) with MSVC in C89 mode after the latest change.
@akashthakur76 Can you tell what compiler settings you are using and which version of MSVC?

Well thanks Petteri. I'm able to fix the problem now. The comments given in pb.h helped in fixing.


Add LLaVA support

We added code to support llava. #307
test code:
from vllm import MLLM, SamplingParams
prompts = [
    "what is doing the man",
    "what you name",
    "what can I do for you",
    "what is doing the man",
】
images = [{
    "src_type": "url",
    "image_src": "IMAGE_URL"}]*4

sampling_params = SamplingParams(temperature=0.8, top_p=0.5, max_tokens=1024)
model,tokenizer = "/PATH/LLaVA-13b-delta-v1-1", "/PATH/LLaVA-13b-delta-v1-1"
gpu_memory_utilization = 0.9
mllm = MLLM(model=model,tokenizer=tokenizer, gpu_memory_utilization=gpu_memory_utilization)
outputs = mllm.generate(prompts, images, sampling_params)
# Print the outputs.
for output in outputs:
    prompt = output.prompt
    generated_text = output.outputs[0].text
    print(f"Prompt: {prompt!r}, Generated text: {generated_text!r}")

Thanks. Is it working with LLaVA1.5?

@LinkerCodeMonkey do you still plan to work on this PR?

Closed as we added support for LLaVA in #3042


Convert to java library for server-side compatibility

Finished and available in eosio-java-rpc-provider


The views bar is not showing properly

That  is using the latest Developer Build in its factory state (no custom settings).

I believe this is a duplicate of #2242, post has no dev feedback but temporary fix provided by users


Added some missing requirements to the README file

I added some missing requirements to the README file. Could be that those are installed together with dependencies, but are not loaded by default then.

Thanks for contributing!


nix-perl: fix build for 2.24

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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.

Add a :+1: reaction to pull requests you find important.

@ofborg build nixVersions.nix_2_18.perl-bindings nixVersions.nix_2_19.perl-bindings nixVersions.nix_2_20.perl-bindings nixVersions.nix_2_21.perl-bindings nixVersions.nix_2_22.perl-bindings nixVersions.nix_2_23.perl-bindings


[Workers] Chat tutorial with durable objects

Not ready for review until Cody K. updates the repository for Wrangler 2

may seem super obvious, but I think it's worth describing how to actually use the thing - e.g. go to edge-chat-demo.your-name.workers.dev in your browser, put in your name and a chat room, send some messages, try the same room url from a different browser / different name
Also think it's worth linking the deletion instructions on the readme


counterparty-cli: local variable 'btc_out' referenced before assignment, can with "--unconfirmed"

I get this when I try to open a bet from a testnet address.
[INFO] Running v9.49.3 of counterpartyd.←[0m
[INFO] Connecting to database.←[0m
←[31m[ERROR] Unhandled Exception←[0m
Traceback (most recent call last):
  File "c:\counterpartyd_build\dist\counterpartyd\counterparty-cli.py", line 869
, in <module> args.unsigned)
  File "c:\counterpartyd_build\dist\counterpartyd\counterparty-cli.py", line 232
, in cli unsigned_tx_hex = util.api(method, params)
  File "c:\counterpartyd_build\dist\counterpartyd\lib\util.py", line 69, in api
    raise RPCError('{}'.format(response_json['error']))
lib.util.RPCError: {'message': 'Server error', 'code': -32000, 'data': {'message
': "local variable 'btc_out' referenced before assignment", 'args': ["local vari
able 'btc_out' referenced before assignment"], 'type': 'UnboundLocalError'}}←[0m

Then I add --unconfirmed and it goes through right away.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

This issue was moved to CounterpartyXCP/counterparty-cli#2


Some examples create lepiter playground pages in the default knowledge base

There are other examples to deal with.


NotSerializableException: DefaultProjectLayout$(FixedDirectory|FixedFile) when attempting to use @Input for path-type inputs

Trying to use a DirectoryProperty or FileProperty with @Input for path-type (not content) task inputs.
Expected Behavior
Similar to what happens with @Input with a File.

When used on a File object that refers to a file or directory, the up-to-date check is only dependent on the path and not the contents of the file or directory. To make it depend on the contents, use InputFile or InputDirectory respectively.

Current Behavior
Serialization exceptions on task inputs

java.io.NotSerializableException: org.gradle.api.internal.file.DefaultProjectLayout$FixedFile

(I think) the workaround is to make the desired property @Internal and map it to a different internal output like:
@Internal
final DirectoryProperty myDir = ...

@Input
final Provider<File> myDirAsFileProvider = myDir.asFile

Context
Desire to use the strongly modeled types to represent "paths" in a similar way to how @Input works.
Steps to Reproduce (for bugs)
import static java.util.Objects.requireNonNull
import javax.inject.Inject

class DirTask extends DefaultTask {
  @Input
  final DirectoryProperty exampleInputDir
  @Input
  final RegularFileProperty exampleInputFile

  @OutputDirectory
  final DirectoryProperty exampleOutputDir

  @Inject
  DirTask(ProjectLayout projectLayout) {
    this.exampleInputDir = projectLayout.directoryProperty()
    this.exampleInputFile = projectLayout.fileProperty()
    this.exampleOutputDir = projectLayout.directoryProperty()
  }

  @TaskAction
  void doThing() {}
}
tasks.create('myTask', DirTask) {
  exampleInputDir.set(layout.projectDirectory.dir('myDir'))
  exampleOutputDir.set(layout.buildDirectory.dir('outDir'))
  exampleInputFile.set(layout.projectDirectory.file('build.gradle'))
}

tasks.wrapper.gradleVersion = '4.6'

./gradlew myTask
Your Environment

Build scan URL: https://scans.gradle.com/s/46zmqosqhxt5a

Thanks for reporting. It seems like a missing implements Serializable there.

@mkobit Could you describe your use-case for adding the file/directory path as an input to the task as opposed to the contents? For cacheable tasks, we actually print a warning when this happens.

@wolfs good point about the the cacheable tasks.
The use case here is, I don't think, not a general one. I have a personal project where I use Gradle as more of a "personal environment/workflow management" tool rather than a build tool. It is basically a place for me to experiment with some Gradle features and get a feel for some of the new things coming down the pipeline.
What I was trying to accomplish was "take an input file or directory, and symlink it to the destination" while seeing how up-to-date checking and modeling with the Property and lazy configuration types. So, the output would be a symlink file/directory somewhere and the input would be a path to some file or directory.
My expectation coming in was that it would be treated in a similar way as:
@Input
File dirOrFilePath

which I believe just cares about the path of the input.
I was seeing if I could still strongly model the input as either a Directory or RegularFile (could actually probably use FileSystemLocation) instead of a Provider<File> (or something like that) and how up-to-date checking would work when I ran into this.
Looking through this a little more and thinking through it, my expectations may be wrong and this may be invalid. I do notice that the :buildSrc:validateTaskProperties does not show any warnings or errors, so maybe that is the only improvement here?

Well, if the generated symlink is the output, then Gradle would actually snapshot the contents of it. So everytime something in the symlinked file changes, Gradle would re-execute the task.
I think that the built-in up-to-date checking won't help much for the task under question. The task would be up-to-date when the input path would be a symlink pointing to the right target. The output is the actual symlink.
So you would need to add the path of the symlink you want to create and the path which will be the target of the symlink as an input (currently as Strings) and for the outputs you need to declare outputs.upToDateWhen { }, adding the condition that the file at the path of the symlink is a symlink pointing to the target.

Awesome, that makes sense @wolfs . I think that everything here works as should be expected, so unless you think there is any follow up I think this can be closed.


Basic PLD implementation

Just some WIP code so far.

Goring Analysis based on DoT uptime from the SMN Module

Absolutely, thanks for getting started on it!
On 24 July 2018 at 17:34, Michael Braun<EMAIL_ADDRESS>wrote:

@MikeMatrix commented on this pull request.
In src/parser/jobs/pld/About.js
https://github.com/xivanalysis/xivanalysis/pull/39#discussion_r204651646
:

@@ -0,0 +1,21 @@
+import React, {Fragment} from 'react'
+import {Icon, Message} from 'semantic-ui-react'

+import CONTRIBUTORS from 'data/CONTRIBUTORS'
+import CoreAbout from 'parser/core/modules/About'
+
+export default class About extends CoreAbout {

description =

Will do.
As I mentioned in PR and in chat, this was more or less whipped up in a
short evening before sleep, so I just copied something to get something
semi-sensible in place.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/xivanalysis/xivanalysis/pull/39#discussion_r204651646,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgm23_mHz3qJI-XEjWTjNtttF2MQv7Fks5uJs4ZgaJpZM4Vbyu7
.

--


Proof-of-Concept:  Avoid N^2 behavior in NC4_inq_dim

The current library seems to have some behavior which is N^2 in the number of vars in a file.
The NC4_inq_dim routine calls down to nc4_find_dim_len which iterates through each var in the file/group and calls find_var_dim_max_length on each var and finds the largest length of the dim on each of those vars. This is done only for unlimited vars.
I have a file with 129 dim and 1630 vars.  The unlimited dimension is of length 41.  In my test program, I am reading data from 4 files which have the same dim and var count and reading every 4th time step (unlimited dimension).  If I run a profile, I see that 98.2% of the program time is in the nc_get_vara_float call tree and most of that is in find_var_dim_max_length (94.8%).
There are 66,142 calls to nc_get_vara_float resulting in 107,307,290 calls to find_var_dim_max_length with twice that number of calls to malloc/free and calls to 5 HDF5 routines.  All of this, at least in my case, to return the same 41 each time.
The proof of concept patch here will check whether the file is read-only (or no_write) and if so, it will cache the value of the dim length the first time it is calculated.   With this change, my example run is sped up by a factor of 60.  The time for NC4_inq_dim and below drops from 97.2% down to 2.7%.
I'm not sure whether this is the correct fix, or if there is some behavior that I am overlooking, but my users would definitely like a 10 second run compared to a 10 minute run...
This is on current Netcdf master branch.
I will try to attach some valgrind/callgrind profiles.

First plot is current behavior.  Second plot shows profile with this PR applied.

Awesome idea @gsjaardema !

Thanks.  Not sure why it didn't show up before, but it definitely stuck out in the set of files the user gave me...

Thank you @gsjaardema. I'm a big fan of callgrind/valgrind/kcachegrind.  Thanks for providing the comprehensive visuals.  Merging in!

It was originally going to take 8 hours to run, so I had to scale the problem down some.  But it definitely pointed out where the problem was...  I just wish it would run on my Mac...

How and when is the cached value invalidated when the size
of the unlimited changes?

It cannot change because he's only doing it for files open NC_NOWRITE.
On Thu, Apr 30, 2020 at 5:53 PM Dennis Heimbigner<EMAIL_ADDRESS>wrote:

How and when is the cached value invalidated when the size
of the unlimited changes?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Unidata/netcdf-c/pull/1709#issuecomment-622179693,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCSXXGYJ6HPBZPLAV4D6CTRPIFNXANCNFSM4MVYQLQQ
.

I see.


Allow DrupalPod to launch from "node" link

Is your feature request related to a problem? Please describe
If you share an issue with the handy short link, such as: dgo.to/3478994, it redirects to https://www.drupal.org/node/3478994 rather than https://www.drupal.org/project/project_browser/issues/3478994, which means DrupalPod doesn't identify it as an issue that it can open.
Both URLs refer to the same ussue, but the Drupalpod extension only recognises the /issues/ link.
Describe the solution you'd like
Make the DrupalPod extension recognise /node/ links.
Describe alternatives you've considered
Currently I find the easiest workaround is to click on "issues" in the breadcrumbs, then find the issue in the list to get to the URL that DrupalPod will recognise.
Additional context

Please open the issue in https://www.drupal.org/project/drupalpod, the new home of Drupalpod.

Transferred to the drupal.org issue queue. Feel free to close this one.


API docstring refine and example adding

Type of Change
Add user examples to user facing APIs.
Refine docstrings.
Description
JIRA ticket: https://jira.devtools.intel.com/browse/ILITV-2622
Expected Behavior & Potential Risk
How has this PR been tested?
Dependency Change?

@WenjiaoYue Please consider IO API helper structure and docstring scan in CI.