Product image upload causes app crash for published version

I've published the app to windows VM , i can upload product image inside the VM using <IP_ADDRESS>:8080 , but when i access the APP from external computer using IP : 2.23.xx.x.x:8080 , everything works except product image upload , it causes app crash
========================================
Error: ENOENT: no such file or directory, open 'C:\Apps\ShoppingAPP\public\uploads\af065f578dffbb7ed76c091e0ad937ab'
Emitted 'error' event on ReadStream instance at:
at C:\Apps\ShoppingAPP\node_modules\graceful-fs\graceful-fs.js:190:14
at C:\Apps\ShoppingAPP\node_modules\graceful-fs\graceful-fs.js:241:16
at FSReqCallback.oncomplete (fs.js:155:23) {
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'C:\Apps\ShoppingAPP\public\uploads\af065f578dffbb7ed76c091e0ad937ab'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node app.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\Administrator\AppData\Roaming\npm-cache_logs\2020-05-08T10_38_35_131Z-debug.log
==================================================
LOG FILE CONTENTS
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\Program Files\nodejs\node.exe',
1 verbose cli   'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli   'start'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Apps\ShoppingAPP\node_modules.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files\Amazon\cfn-bootstrap;C:\Program Files\nodejs;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;C:\Users\Administrator\AppData\Roaming\npm;C:\Users\Administrator\AppData\Local\Programs\Microsoft VS Code\bin;C:\ProgramData\Administrator\GitHubDesktop\bin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\Apps\ShoppingAPP
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c', 'node app.js' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
13 verbose stack Error<EMAIL_ADDRESS>start: node app.js
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:310:20)
13 verbose stack     at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:310:20)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd C:\Apps\ShoppingAPP
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v12.16.2
19 verbose npm  v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>start: node app.js
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Looks like permissions. Make sure the /uploads directory can create new files and directories within it.

I have the same issue.  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/centos/.npm/_logs/2020-05-18T09_49_00_063Z-debug.log
(Note the directory name from the ENOENT differs from that in the public/uploads directory)

I'm 100% sure this is permissions. @robrob-github Can you try a test by running the app as root to see if the error persists?

@mrvautin i was running on Amazon EC2 windows vm ,  and give full permission to the uploads folder , the strange thing is that image upload works when i access the app with localhost , but crashes when i access with vm public IP from other pc.

@EngMohamedNor Could that be related to user running the Webserver (IIS on windows - App Pool?) not having permission to the folder? I'm not familiar with Windows but from memory IIS user permissions requires some tweaking.
Running an application as localhost and serving from a Webserver are two very different things permission wise.

@mrvautin I'm not using IIS directly , IIS is running on port 80 and i am running the app on 8080 , installed Node and  started the app with command prompt , don't know how IIS can affect based on my configuration. i thought express was enough . it's my first experience hosting Node app on windows

You already have more experience running a Nodejs on Windows!

@mrvautin everything else is working , will try to spend sometime on this ...

@mrvautin @EngMohamedNor @robrob-github
I can confirm the same. I use docker with nginx as reverse proxy on aws. Did the usual troubleshooting and research.
I have tried different browsers (to see if browsers trigger it (content length)).
Tried different node versions.
Hacked around with the admin route a bit.
The result is same. The app crashes as it can't find the uploaded file.
The store front has no (broken images).
It could be cors, it could be proxy header issues, it could be something else, it could be the fs/fsevent package issue or any other dependent module issue ...
Ping back here if you need more info
GET /admin/orders 302 10.202 ms - 68
GET /admin/login 200 167.660 ms - 11927
POST /admin/login_action 200 136.798 ms - 30
GET /admin 302 7.939 ms - 76
GET /admin/dashboard 200 95.099 ms - 25435
GET /admin/products 200 70.709 ms - 27252
GET /admin/product/new 200 76.882 ms - 27361

Product indexing complete
POST /admin/product/insert 200 17.390 ms - 85
GET /admin/product/edit/5ec6f2f0f9f831001085f003 200 101.171 ms - 30716
events.js:187
throw er; // Unhandled 'error' event
^

Error: ENOENT: no such file or directory, open 'public/uploads/03fdb92763542461d502f1a4aaeb8c34'
Emitted 'error' event on ReadStream instance at:
at internal/fs/streams.js:132:14
at FSReqCallback.oncomplete (fs.js:146:23) {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: 'public/uploads/03fdb92763542461d502f1a4aaeb8c34'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node app.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-05-21T21_30_43_835Z-debug.log
docker build:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/glob-watcher/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

0 info it worked if it ends with ok
1 warn npm npm does not support Node.js v13.0.0
2 warn npm You should probably upgrade to a newer version of node as we
3 warn npm can't make any promises that npm will work with this version.
4 warn npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12.
5 warn npm You can find the latest version at https://nodejs.org/
6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
7 info using<EMAIL_ADDRESS>8 info using<EMAIL_ADDRESS>9 verbose run-script [ 'prestart', 'start', 'poststart' ]
10 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>11 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>12 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
13 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/expressCart/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/u
sr/bin:/sbin:/bin
14 verbose lifecycle<EMAIL_ADDRESS>CWD: /var/expressCart
15 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node app.js' ]
16 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
17 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
18 verbose stack Error<EMAIL_ADDRESS>start: node app.js
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
18 verbose stack     at EventEmitter.emit (events.js:210:5)
18 verbose stack     at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18 verbose stack     at ChildProcess.emit (events.js:210:5)
18 verbose stack     at maybeClose (internal/child_process.js:1028:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
19 verbose pkgid<EMAIL_ADDRESS>20 verbose cwd /var/expressCart
21 verbose Linux 5.6.13-232.aws
22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
23 verbose node v13.0.0
24 verbose npm  v6.12.0
25 error code ELIFECYCLE
26 error errno 1
27 error<EMAIL_ADDRESS>start: node app.js
27 error Exit status 1
28 error Failed at the<EMAIL_ADDRESS>start script.
28 error This is probably not a problem with npm. There is likely additional logging output above.
29 verbose exit [ 1, true ]

From Chrome Dev tools:
A cookie associated with a cross-site resource at http://cloudflare.com/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
Uncaught TypeError: Cannot read property 'message' of undefined
at Object. (admin.js:766)
at c (jquery.min.js:2)
at Object.fireWith [as rejectWith] (jquery.min.js:2)
at l (jquery.min.js:2)
at XMLHttpRequest. (jquery.min.js:2)
jquery.min.js:2 POST https://store.mysite.com/admin/file/upload net::ERR_HTTP2_PROTOCOL_ERROR 200
jquery.min.js:2 POST https://store.mysite.com/admin/file/upload 502
200 and 502 keeps changing depending on if server crashed and restarted
Nginx conf:
server {
server_name  store.mysite.com;
listen <IP_ADDRESS>:443 ssl http2;
ssl_certificate /etc/nginx/certs/mysitecert.pem;
ssl_certificate_key /etc/nginx/certs/mysitekey.pem;
ssl_client_certificate /etc/nginx/certs/cloudflare.crt;
ssl_verify_client on;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header HOST $http_host;
proxy_set_header X-NginX-Proxy true;
proxy_pass http://ecart:1111;
}
client_max_body_size 5M;
}

Everything else is working. One thing is that the menu doesn't appear.

If anyone has a working docker + nginx config, please share

@nomadcult I've tested using Docker locally and its working fine. Seems to be related to AWS only. Is there specific permissions you need to set in AWS to write files to the /uploads directory? Can you give me more info on your AWS deployment so I can try replicate?

@mrvautin
Please see my config: https://gist.github.com/nomadcult/3fc2ed3f768d813f27336892b8664ddf
That helps you replicate on aws.
I use clear linux on aws.

This issue somehow persists

I'm no Docker expert but I just spun up a server on Digital Ocean, ran the steps in the readme (docker-compose up --build) with the default Dockerfile and everything works fine. Tested uploads and working correctly.
It looks like something specific to AWS. Can you try asking their support/forums?

@nomadcult I've made some small changes to the handling of uploads. Not sure if it will resolve your issues or not. Can you please test the latest master?

Heyy, i got an error can i get the version with image uploads

Using Nodejs

Closing issue due to inactivity. Can reopen if required.


Adding -e option to test dependencies for datadog packages

What does this PR do?
Adding -e option to test dependencies for datadog packages
Motivation
This will make it easier to make changes to datadog packages.
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes

Closing this - https://github.com/DataDog/integrations-core/pull/2036/files


Update Azure App Service libraries for Java article

https://docs.microsoft.com/en-us/java/api/overview/azure/appservice?view=azure-java-stable
We already have Track2 article: Azure Resource Manager App Service client library for Java | Microsoft Docs
Do we update content, or just bring down this Track 1 article? Or do some search optimization?

After discussed with @weidongxu-microsoft  and @nickzhums, we decided to update the Track1 article. Because using google search, the Track1 article comes as the top-hit result, and we don't have control on google's indexing, so it's better to update the Track1 article.
The pr is already merged.
https://github.com/Azure/azure-docs-sdk-java/pull/2125


Feature: No Such Book found

Feature description

in this if the book is not found then no such book found can be added @SauravMukherjee44 what do you think
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

to get better user experience we can add feature that if the book is not present then we can display that book is not present which ensures the user that book he want to search which is not present on the site @SauravMukherjee44


Drip Singleton structure for translations model.

This is in repsonse to @dankohn's comments in
3c4e46b3ebb3e63673b103b47c3e9fb1d9c0d944
Signed-off-by: Jason Dossett<EMAIL_ADDRESS>

Codecov Report

Merging #853 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #853   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          45     45
  Lines        1442   1440    -2
=====================================
- Hits         1442   1440    -2

Impacted Files
Coverage Δ

app/models/translations.rb
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

+1


Got error

i got undefined merchant issue can any one help

Feel free to reopen issue if you haven't resolved it yet, but provide us with a little more details on the error you are encountering.


The name of Model.groups indicates a field/property

I feel the name of Model.groups is obscure. The word indicates to me a property or field similar to vars or nodes. It is, however , a method. I think we should either choose an imperative like get_groups or make it a property.

Old discussions:

https://github.com/liesel-devs/liesel-nextgen/pull/16#issuecomment-1301838570
https://github.com/liesel-devs/liesel-nextgen/pull/42#issuecomment-1319819271


v 0.9.0 does not work on node 0.12

https://github.com/quartzjer/ursa/pull/109
https://travis-ci.org/quartzjer/ursa/builds/83831352

https://github.com/quartzjer/ursa/pull/111

fixed in master, I'll push a v0.9.1 tomorrow w/ it


feat(ios): add iOS 14 limited photo access permission status

There is a new photo permission status (PHAuthorizationStatus.limited) that was released in iOS 14 as outlined here, which also introduced a new API to get that status for iOS 14+ (PHPhotoLibrary.authorizationStatusForAccessLevel)
This PR adds the new status and the new API to get it for iOS 14+ and falls back to the original implementation for older iOS. @farfromrefug I also added NSPhotoLibraryUsageDescription to the demo's plist so I can test the permission without causing the app to crash :)

@williamjuan027 wow  i love it ! Thank you so much for your work!!! love that community!

Wow, that was fast. Thanks @farfromrefug , likewise 🍻


configure is insensitive to FCFLAGS

Specifying FCFLAGS when running configure, for example:
$ FCFLAGS=-O3 FC=ifort ./configure

does not affect what flags are being used when running make. In fact, the flags are always -Wall -O0 -C -fbacktrace, which are the gfortran flags hardwired in src/lib/Makefile.am:
# Items needed specifically by autotools
AM_FCFLAGS = -Wall -O0 -C -fbacktrace

Specifying FC works as expected.
@blippy can you look into this at your convenience? Thanks!

yes. I'll look into it.

I've asked some questions on Stackexchange to see how autotools actually behaves.
The documentation is VERY confusing.

I am discussing this issue over at http://stackoverflow.com/questions/35117315/so-what-is-am-fcflags , if you're interested. The consclusion so far is that I shouldn't set AM_FCFLAGS.
I will investigate further.

I "think" this is now fixed. I've done my own testing, and it looks OK.
It could definitely use some testing by others though, esp. where other compilers are concerned. I have not been able to perform configuration tests in the presence of alternative compilers.

Right, I believe this is fixed, I just forgot to close the issue few days ago. Thanks!!


Update DriverDataSource to not convert all provided property values to String.

This PR updates DriverDataSource to preserve the original driver property values provided to DriverDataSource's constructor instead of converting all property values to String representations. This addresses issues like those brought up in https://github.com/brettwooldridge/HikariCP/issues/1496 and https://github.com/brettwooldridge/HikariCP/issues/1242 where non-String Object property values are being provided.
This is particularly important for the latter issue of compatibility with the Snowflake JDBC driver, which supports a "privateKey" property requiring a value of type java.security.PrivateKey but throws an exception due to DriverDataSource's current behavior of converting the property value to a String representation.
Updates have also been  madeto PropertyElf for consistency, as suggested in comments on an older unmerged PR (https://github.com/brettwooldridge/HikariCP/pull/1557) for this issue.

Hi @alex-rentz it looks like the build issue is unrelated to this PR. Its present in current dev as well.
Can you please see how this fix can be released asap.
We are using HikariCP and blocked on this issue, specifically for supporting Snowflake jdbc.

Hi @alex-rentz it looks like the build issue is unrelated to this PR. Its present in current dev as well. Can you please see how this fix can be released asap. We are using HikariCP and blocked on this issue, specifically for supporting Snowflake jdbc.

Thanks for pointing that out. My approval doesn't mean much in this repo - will need a maintainer to approve.

@brettwooldridge can I draw ur attention to this PR for an early merge?

@brettwooldridge Any chance I could get your thoughts on this? It's a pretty significant blocker to using Hikari to connect to Snowflake.

Same here!!, we need this pr to be merged to use HikariCP with snowflake.
We have the same problem using the private key as property.
There's anything we can do to unblock this pr?.
Thank you for your work and regards!!

Hi. Any progress or blockage with this PR? We need this change so we don't have to work with a forked version of HikariCP

I would imagine that this could be a breaking change for any user that happened to be passing non-string values into the configuration currently.
The JDBC spec is defined to use a Properties class for the driver properties. This would imply that to be compliant with the spec, all driver properties must be a string. Is Snowflake using functionality that technically isn't right?
The JavaDoc for the Properties class refers to adding non-String values as a "compromised" Properties object

I would imagine that this could be a breaking change for any user that happened to be passing non-string values into the configuration currently.
The JDBC spec is defined to use a Properties class for the driver properties. This would imply that to be compliant with the spec, all driver properties must be a string. Is Snowflake using functionality that technically isn't right?
The JavaDoc for the Properties class refers to adding non-String values as a "compromised" Properties object

This is a great point regarding it potentially breaking some users, but I don't see anything in the JDBC spec (relating to Datasources) that requires a String property value. Can you share what it is that indicates this requirement?
I was referring to the latest spec here in section 9.6.1 - https://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-spec/index.html

Hello everyone,
this is also a blocking issue for my client's project.
When, if at all, can we expect a new release with this issue solved?

In my opinion the responsibility to fix this lies with Snowflake. As far as I know, no other JDBC driver uses non-string properties. And there is nothing in the JDBC spec that implies that anything other than String properties should be supported. (JDBC spec uses the Properties class and the Properties class specifically states that using non-string objects will cause undefined behavior).
Also as I stated before, implementing this has the chance of being a breaking change. So it feels like modifying HikariCP to support this cases isn't the Correct™ solution to this problem.
Is there a different way to provide the PrivateKey to Snowflake without needing to pass the object itself as a property?

I can appreciate that you keep things running smoothly for existing consumers of HikariCP. It would be up to Snowflake to implement an alternative to using a PrivateKey directly - let's say, using a URL from which a private key could be loaded at runtime. However, this String-casting decision is effectively preventing use of Snowflake, which would otherwise be supported.
In addition, due to the security concerns of use of private key, I'd advocate for the continued use of Java's PrivateKey interface in this context. I suspect the use of keys or other authentication methods will become more common in JDBC, so this won't be a Snowflake-only concern in the future.

As @lfbayer pointed out, this would be a breaking change. The first alternative would be to request that snowflake accept a base64 encoded key. The second is to use programatic configuration of the HikariConfig rather than Properties-based. Through programmatic configuration there is a setDataSource(javax.sql.DataSource dataSource) method. This method exists to allow the user to configure and create their DataSource as desired, and then provide it to the pool.

As @lfbayer pointed out, this would be a breaking change. The first alternative would be to request that snowflake accept a base64 encoded key. The second is to use programatic configuration of the HikariConfig rather than Properties-based. Through programmatic configuration there is a HikariConfig.setDataSource(javax.sql.DataSource dataSource) method. This method exists to allow the user to configure and create their DataSource as desired, and then provide it to the pool.

I can look into whether programmatic option makes sense for us. It may require a special case compared to what we do for other JDBC connection creations, or a re-write of the code we had for that. Though it seems like a good workaround.
How would we feel about a configuration option "Preserve Datasource Property Types" or something of that nature to allow flexing on this behavior?


Custom Log Formatting

Description
The PR adds two flags:

--terragrunt-log-format [bare | pretty | json | keyvalue]
--terragrunt-log-custom-format "%time %level %prefix %msg"

Context
https://linear.app/gruntwork/issue/TG-419/support-deep-log-format-customization
Closes #3431

TODOs
Read the Gruntwork contribution guidelines.

[ ] Update the docs.
[ ] Run the relevant tests successfully, including pre-commit checks.
[ ] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[ ] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide

Resolved in v0.68.15 release.


It just Cant find relevant documents

Hey, loaded with my legal petitions , more than 90 documents.
Asking question, it gives "no information in given context", even some of simple questions. I am sure it has all of context in vectordb and Returning source files is not related about question.
So i am sure the vector searching part is responsible for this. Because when i try with different name space and upload only that document ( or 1-2 additional) It can find related context and merge it into template.
So, how to improve vector searching phase? How to push it to find relevant documents. I am using Turkish language, is it possible reason?

I've also encountered this problem. Curious if there's a threshold of documents beyond which this method of ingestion starts to degrade.

I have a few (<5) large pdfs (50 to 200 pages) and an index of 1000 vectors and it works pretty well.
I think it is worth playing around with various doc structures and consider combining a large number of small documents in consolidated PDFs.

Its about embeddings. Embeddings are good at English but not that good in other languages


Ice Cap 3 jet enemy bomb explosions are invisible

Hmm, I do see them with both OIT on and off on my GTX 760M


Support new runtime isJiti and isEsno?

Describe the feature
I'm developing a vite plugin using unbuild, if it's in stub mode(jiti), inject a package for main.ts using a relative path, otherwise use the package name.
Additional information

[ ] Would you be willing to help implement this feature?

If run directly as a command, I can use process.mainModule.filename to confirm the runtime.
If I use programming to load modules (like the stub mode of unbuild), I don't know how to determine the current runtime.
Currently, I am using the build: done hook of unbouild to output process.env.JITI=true'.
  hooks: {
    'build:done': (ctx) => {
      if (ctx.options.stub) {
        writeFileSync('dist/index.mjs', `process.env.JITI = true;\n${readFileSync('dist/index.mjs', 'utf-8')}`)
      }
    },
  },

I think we might need to expose such env/static flag from jiti itself to allow detection.


ComplexMultiplication optimization

[ ] rm is_conj parameter

Well done! Please increase package version so we can publish after merge.


#if CSHARP_8_0

I can't find documentation anywhere that talks about this. If it isn't supported, it should be! Thanks

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

ID: 5694e62b-c756-1f62-4014-2ceafa54c011
Version Independent ID: 3f01c378-22e4-197c-a862-ab4a924506c7
Content: Select the C# language version - C# Guide
Content Source: docs/csharp/language-reference/configure-language-version.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Adding @jcouv for comment on this feature.

I'm not aware of any such feature. I'm not sure when you would want to use that.
You should be able to get this behavior by defining your own constant in MSBuild:
<PropertyGroup Condition="'$(LangVersion)'=='8.0'">
   <DefineConstants>$(DefineConstants);CSHARP_8_0</DefineConstants>
</PropertyGroup>

It's useful for those of us who love great new language features, those of us to refactor constantly, always looking for a better way to express things.  After you're sure you won't have to go back to the old compiler, you can remove the #if and the old crufty syntax.
Nice workaround!

I'll close this as answered.
Thanks @jcouv for the great workaround


Update version to 2.0.5-SNAPSHOT.

Signed-off-by: Pan Li<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master     #195   +/-   ##
=======================================
  Coverage   80.68%   80.68%
=======================================
  Files          39       39
  Lines         963      963
  Branches      124      124
=======================================
  Hits          777      777
  Misses        125      125
  Partials       61       61

Continue to review full report at Codecov.

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


ability to change font size

Your Rocket.Chat.Android version: 1.0.8
The default font size for chat messages is too small for my eyesight. This is an accessibility issue.
The feature to change font size was added to the desktop app, but I cannot find it in the Android app.

The Android app does not have support for it, yet.
We do need to add some basic settings/preferences in the app. Let's add it to the #186 list.

Since this issue was added to another issue, let's close it.


[gateway, http, project] Metrics support

Optional support for Metrics.
enabled in dawn with the feature metrics
Metrics: https://github.com/metrics-rs/metrics

Well other than fixing the bugs I think I will also add metrics to the http module and then this is ready to review

What kind of metrics could be good to have from the HTTP module?


Fix clean up of invalid UTF-8 sequences in WebSocket server.

If an invalid UTF-8 sequence is sent to the client, the client will break the connection with the server.

This has been fixed per commit 0e225f1. It will be pushed out in the upcoming release.


Atmospheric Models 》ideas for a new release

Adding some references here: https://doi.org/10.5194/acp-21-18351-2021
*I'm able to provide help, if wanted

https://doi.org/10.1021/cr020648p

Could you assign me on this issue to complete the tasks related to it, @schneiderfelipe? I've forked the repository to add my contributions as PRs. 😊


Fixed #26093 -- Allowed escape sequences extraction by gettext on Python 3

Thanks Sylvain Fankhauser for the report.

Technically, it was bug in gettext and it is fixed now (but not released yet, probably will be included in the next version after 0.22.5).
https://savannah.gnu.org/bugs/?65778
Somewhere in the future when everyone uses new gettext this workaround may no longer be needed.

Thanks, great to know! It might be worth completing the comment in the source code, as I fear your comment here might get forgotten or even lost. What do you think?

Here's a reminder: https://code.djangoproject.com/ticket/35684


Look into optimizing the dataset loading

Right now it takes a couple of minutes to load in all of the images and compute polygons for the various annotated masks. I should look into a vectorized version of the polygon function that will speed this computation up.
I should also see if ChatGPT has some simple improvements to make that could speed up my code.

Not really an issue. It's negligible compared to training time.


May I ask how can this be used?

Hi,
I have taken a look at the source and it seems to take 2 parameters, one for old asset directory and the other for new asset directory.
I suppose that after assetripper export finished, the project is duplicated, and the 'new' one should remove the scripts for textmeshpro for example and import the package for it.
Then run the application with the 'old' one that is intact after exporting and the 'new' one with has the package imported and the decompiled textmeshpro scripts removed, right?
That didn't seem to work.
Thanks for advance.

Hi. I don't currently have any guides, and I don't plan on making this GitHub issue into one. However, if you have specific questions, I might be willing to answer them.

Thank you, I think I figured it out and it worked.
I imported the packages to the project, then set the new folder to the packages cache folder and the old folder to the Assets folder and it worked.
Of course I had to add a lot of exception handling, but it worked in the end.


Upgrade to Artemis 2.5.0

@grs Please review the latest commit. It appears that the 'to' property of the message is now changed in Artemis. A new message annotation was added containing the original address. I've modified the mqtt-gateway to look for that annotation. I'm not sure if the change in Artemis is intended or a bug though.

@lulf it looks like there is already similar logic that was looking at an application property. So perhaps the change is that artemis now uses a message-annotation instead.


Improve the locations syntax for the Gradle plugin

Right now, I must specificy this:
flyway { locations = [ 'filesystem:sql/new'] }

What is unexpected is that this does not work:
flyway { locations = 'filesystem:sql/new' }

It would be convenient to use when an only location is needed. In Groovy this is natural.
Also, all over Gradle the usual way to specify files or locations is through the use of Project.file(...): I think this should be allowed as an alternative to the 'filesystem:...' string syntax.
Accepting also a FileCollection would then be great (as per Project.files(...) or Project.fileTree(...)), but I think this would require a change to the Flyway core to be correctly supported.

Closing as this is a very niche requirement with very little added value that has seen no additional support over the last 4 years.

It's a pity. The use of files and file collections is the standard way of specifying paths and file resources in Gradle, rather than a niche requirement :-(


ValidSetSwing - OPTION check is wrong

OBSERVED
The compiler shows this warning
Warning	C4804	'>': unsafe use of type 'bool' in operation

For this code
		if (d->HasProperty(BME_PROPERTY_OPTION))
		{
			if (_move.m_option_die[i]>1)
				return false;
		}

m_option is a BitArray and it returns true or false, so the "return false" will never run.
EXPECTED:
No compiler warning, and this code returns false in the given case appropriately.

There's a comment on the function that suggests that it might not effectively matter:
// drp071505 - OPTION check was wrong (not checking any dice, but probably didn't matter)

fixed in commit 3726079


Added a robust gitignore & ported mypy configs over to the pyproject.toml

Added a more robust .gitignore file that stops .venv, log, etc from getting into the SCS accidentally.
Mypy version 0.9xx supports pyproject.toml as a valid config format (PEP-621 also recommends that]. So, ported the current configuration over to the pyproject.toml file.

Hi @rednafi , I'm completely unable to process PRs right now and might not be able to for a few months.
But I also don't want to dampen your spirit since you clearly have interest in trycast. Would you like to be a comaintainer, and be able to make changes directly?

@davidfstr Absolutely. I'd love to do a bunch of cleanups, add proper linting, update the readme and fix some of the types. Once I'm done with this, I'll ping you for a new release. Let's do this.

Sounds great @rednafi . I've invited you as a direct contributor.


Moving/Copying Mails does not work because of Quota

RainLoop version, browser, OS:
Current, Firefox, Chrome on Windows
Expected behavior and actual behavior:
Copying mails should work whenever quota is not reached. If the user has less space available than a shared mailbox uses, the user cannot copy content to the folders of the shared mailbox. An errormessage is received on the rainloop Client
Steps to reproduce the problem:
Generate 2 Users, the sharer and the normal user.
The Sharer has to have quite some space occupied, lets pick 1.5GB as an example. He/She has a Quota of 2 GB.
The normal user has 1GB Quota and uses 500MB of that.
As the normal user wants to copy a message from his inbox to the shared mailbox, an overquota message is displayed.
The server does not show any error. The error does not occur in Thunderbird/Outlook.
Sharing Mailboxes can be achieved by using sogo, horde or thunderbird with acl plugin
Logs or screenshots:

ImapClient.php Line 1100 always checks quota of Inbox:
$this->SendRequest('GETQUOTAROOT "INBOX"');
would be better to parse the destination folder and query for that:
$this->SendRequest('GETQUOTAROOT "{$aFolder}"');
Unfortunately I'm quite new to php dev and do not understand how Actions->DoQuota() is called, any hints?


Error in path simplification algorithm breaks output paths: "c0 0" curveto curve command stripped

The path simplification algorithm strips "c0 0" commands from the path. The output looks quite different as a result.
See the attached testcase for an example:

a.svg = SVG file before scouring
b.svg = SVG file after scouring

Look at beak and claws for the visual difference.

(by eduard-braun2)

(by eduard-braun2)

(by eduard-braun2)

Fixed in #110.


Unable to find any endpoint declarations when endpoints are in a different assembly

If I have all my endpoints in their own assembly, when calling builder.Services.AddFastEndpoints(), I get the error "System.InvalidOperationException: 'FastEndpoints was unable to find any endpoint declarations!'"
If I have other classes in the same assembly that get referenced before fast-endpoints, then I don't get this error. For example, if I have some services that I reference through DI, the error doesn't happen.
This feels like a quirk with how .NET loads assemblies and subsequently can find classes through reflection, like  Assembly.GetEntryAssembly()?.GetReferencedAssemblies();
fastendpoint-error.zip

This fixes the issue in my code, and more generically without the ".Where" clause, may be a good fall back for this type of use case.
 options.DisableAutoDiscovery = true;

              var assemblies = DependencyContext.Default?
                  .RuntimeLibraries
                  .Where(a => a.Name.Contains("PartOfMyNameSpace", StringComparison.InvariantCultureIgnoreCase))
                  .Select(a => Assembly.Load(a.Name))
                  .ToList();

              options.Assemblies = assemblies;

yes you need specify additional assemblies for type discovery.
https://gist.github.com/dj-nitehawk/b3615fad393beabefe929e3f81af6822


Design Always Fails Synthesis after Updating to Develop

I have a design that synthesizes properly on rc4 but fails when I updated OpenLane to develop (nothing else changed). The advice from Slack is to increase the clock period and double check the clock, but those did not resolve the issue. Below are more details:
Error:
puts "\[INFO\]: Setting load to: $cap_load"
[INFO]: Setting load to: 0.01765
set_load  $cap_load [all_outputs]
tns -3.94
wns -2.24
[ERROR]: during executing: "sta /openLANE_flow/scripts/sta.tcl |& tee >&@stdout /openLANE_flow/designs/mac_cluster/runs/17-11_00-16/logs/synthesis/opensta.log"
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
child killed: segmentation violation

[ERROR]: Please check sta  log file
[ERROR]: Dumping to /openLANE_flow/designs/mac_cluster/runs/17-11_00-16/error.log

opensta.log (it's short so posting directly here)
OpenSTA 2.2.0 0d73b5b65a Copyright (c) 2019, Parallax Software, Inc.
License GPLv3: GNU GPL version 3 <http://gnu.org/licenses/gpl.html>

This is free software, and you are free to change and redistribute it
under certain conditions; type `show_copying' for details.
This program comes with ABSOLUTELY NO WARRANTY; for details type `show_warranty'.
Warning: /home/anson/cs250_pdk/sky130A/libs.ref/sky130_fd_sc_hd/lib/sky130_fd_sc_hd__ff_n40C_1v95.lib, line 31 default_operating_condition ff_n40C_1v95 not found.
Warning: /home/anson/cs250_pdk/sky130A/libs.ref/sky130_fd_sc_hd/lib/sky130_fd_sc_hd__ss_100C_1v60.lib, line 32 default_operating_condition ss_100C_1v60 not found.
create_clock [get_ports $::env(CLOCK_PORT)]  -name $::env(CLOCK_PORT)  -period $::env(CLOCK_PERIOD)
set input_delay_value [expr $::env(CLOCK_PERIOD) * $::env(IO_PCT)]
set output_delay_value [expr $::env(CLOCK_PERIOD) * $::env(IO_PCT)]
puts "\[INFO\]: Setting output delay to: $output_delay_value"
[INFO]: Setting output delay to: 40.0
puts "\[INFO\]: Setting input delay to: $input_delay_value"
[INFO]: Setting input delay to: 40.0
set clk_indx [lsearch [all_inputs] [get_port $::env(CLOCK_PORT)]]
#set rst_indx [lsearch [all_inputs] [get_port resetn]]
set all_inputs_wo_clk [lreplace [all_inputs] $clk_indx $clk_indx]
#set all_inputs_wo_clk_rst [lreplace $all_inputs_wo_clk $rst_indx $rst_indx]
set all_inputs_wo_clk_rst $all_inputs_wo_clk
# correct resetn
set_input_delay $input_delay_value  -clock [get_clocks $::env(CLOCK_PORT)] $all_inputs_wo_clk_rst
#set_input_delay 0.0 -clock [get_clocks $::env(CLOCK_PORT)] {resetn}
set_output_delay $output_delay_value  -clock [get_clocks $::env(CLOCK_PORT)] [all_outputs]
# TODO set this as parameter
set_driving_cell -lib_cell $::env(SYNTH_DRIVING_CELL) -pin $::env(SYNTH_DRIVING_CELL_PIN) [all_inputs]
set cap_load [expr $::env(SYNTH_CAP_LOAD) / 1000.0]
puts "\[INFO\]: Setting load to: $cap_load"
[INFO]: Setting load to: 0.01765
set_load  $cap_load [all_outputs]
tns -3.94
wns -2.24

Config:
# User config
set ::env(DESIGN_NAME) mac_cluster

# Change if needed
set ::env(VERILOG_FILES) [glob $::env(DESIGN_DIR)/src/*.v]
set ::env(SYNTH_READ_BLACKBOX_LIB) 1

# Fill this
set ::env(CLOCK_PERIOD) "200"
set ::env(CLOCK_PORT) "clk"

set ::env(SYNTH_MAX_FANOUT) 7
set ::env(PL_TARGET_DENSITY) 0.35

set filename $::env(DESIGN_DIR)/$::env(PDK)_$::env(STD_CELL_LIBRARY)_config.tcl
if { [file exists $filename] == 1} {
	source $filename
}

Note: I've also tried changing the parameters a bit to see if anything changes, but the error is consistent.
Openlane commit: (I tried 2, both fail: d03377b84212527a269dfc58bb637a9e921af150 (Nov 13), d9584fd1923a525de4a69b3da5a9d6f59fa25d9f (newest as of Nov 16))
Repo of OpenLane design: https://github.com/TsaiAnson/exampleDesignOpenLaneMACCluster
^ This design synthesizes fine on rc4 while fails on develop.
Slack Post (openlane channel): https://skywater-pdk.slack.com/archives/C016H8WJMBR/p1605399551389700
Could someone take a look for the issue? Thanks in advance.

Since it is at STA stage, your synthesis was successful. The violation might be when OpenSTA is writing check reports. See the reports/synthesis directory to see which of the opensta.timing.rpt or opensta.min_max.rpt or opensta.rpt are missing. You can get an idea where the flow stopped from that. Since you have negative slack, there are paths that should be reported here, but the flow might not be finding them resulting in this error. Are you providing a sky*config.tcl file and have you enabled simple CTS? I have come across this type of error when simple CTS is enabled on a structural top block like yours. I didnt solve it, but STA at this stage is not really necessary, so run interactively and replace run_synthesis with run_yosys and disable simple CTS. You can spend time worrying if this repeats during STA after CTS.

@TsaiAnson: I reran that out of the box and it worked normally up to placement (which is expected since we changed the way padding is done and PL_TARGET_DENSITY needs to be modified). However, I didn't face that segfault. So it might be an issue with your RAM, memory, CPU, or even permissions?
Maybe try running one of the test designs that we know pass successfully through the flow on develop? md5 maybe since it has a similar cell count?
Here is a log proof:
CELL_PIN) [all_inputs]                                                [162/2087]
set cap_load [expr $::env(SYNTH_CAP_LOAD) / 1000.0]
puts "\[INFO\]: Setting load to: $cap_load"
[INFO]: Setting load to: 0.01765
set_load  $cap_load [all_outputs]
tns -3.94
wns -2.24
[INFO]: Synthesis was successful
[INFO]: Running Floorplanning...
[INFO]: Running Initial Floorplanning...
OpenROAD 0.9.0 e582f2522b

P.S: once your machine issue is resolved try out these configs (to pass placement):
set ::env(FP_CORE_UTIL) 40
set ::env(PL_TARGET_DENSITY) 0.45

This has nothing to do with the segfault.

Thank you @diecaptain @agorararmard for the advice.
I've done some more tinkering and finally got it to work! However, it seems like it's an open_pdks/skywater-pdk issue now (at least on my machine). After I reverted my open_pdks and skywater-pdk commits to the ones used in rc4, I was able to get the global placement error you mentioned earlier @agorararmard. I was then able to get past that error with your suggested config for FP_CORE_UTIL and PL_TARGET_DENSITY.
To summarize, here are the commits of openlane, open_pdks, skywater-pdk that failed (weird seg violation) and passed (completed with no errors):
Failed setup:
openlane: d9584fd1923a525de4a69b3da5a9d6f59fa25d9f
open_pdks: 94513d439f76501eacb39701f6e98f3b4f07dcdf (automatic from Makefile)
skywater-pdk: d8e2cf1ba006ed01468aa60e7f4e85a1ece74ca4 (automatic from Makefile)
Working setup:
openlane: d9584fd1923a525de4a69b3da5a9d6f59fa25d9f
open_pdks: 48db3e1a428ae16f5d4c86e0b7679656cf8afe3d (rc4)
skywater-pdk: 5cd70ed19fee8ea37c4e8dbd5c5c3eaa9886dd23 (rc4)
@agorararmard If you want to try to recreate the weird seg violation error, I believe you can just run make in the openlane dir to automatically update and build the later pdks that caused the weird seg violation on my machine.

@TsaiAnson: Actually, I did use the commits from the Makefile on develop. Anyhow, since this is resolved, I'm closing this issue.

Ah that's strange. Thanks for the heads up though.

I run into the same issue using the same git commits checked out from @TsaiAnson  under "Working Setup". It may still be an issue.

@ojotoxy: So, to clarify you're using openlane:develop but with the pdk commits in openlane:rc4 (master)?


Country Name

Hi, it would be perfect to have country names available aswell. Anyway, great package!

IMO this should be done on I18n level, there is no good reason to turn small lib into repository of 5k names (just to cover most spoken languages)

useless without the country names.

Any update?


add the order kwarg to cupy.reshape and the underlying ndarray method

This PR implements a simple means to support the order kwarg in ndarray's reshape method.
namely, the trick used here is that:
x.reshape(newshape, order='F')

is equivalent to:
x.transpose().reshape(newshape[::-1]).transpose()

Various reshape test cases were duplicated for Fortran order to verify that this is indeed the case.
This transpose-based implementation probably has slight overhead vs. a lower-level implementation, but is considerably simpler and seems to have fairly small overhead. This is probably because transpose is fast as it returns a view rather than a copy.

Here is a quick benchmarks in an Ipython indicating that the overhead is likely only ~1 microsecond when applying order='F' to a fortran-ordered array vs. applying order='C' to a C-ordered array.  This overhead is substantially less than the overhead of making a copy (at least for the moderate array size tested here).
import cupy
from cupy import testing

x = testing.shaped_arange((200, 3, 400), cupy)
xf = cupy.asfortranarray(a)

# C-order reshape of C-ordered array
%timeit x.reshape(3, -1, order='C')
2.23 µs ± 192 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

# F-order reshape of F-ordered array
%timeit xf.reshape(3, -1, order='F')
3.3 µs ± 39.1 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

# two cases where a copy is made
%timeit xf.reshape(3, -1, order='C')
47.5 µs ± 199 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

%timeit x.reshape(3, -1, order='F')
49 µs ± 663 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

Jenkins, test this please.

Jenkins CI test (for commit 791ad15f9e5b21536a0cdf4e9942b3820b471e06, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Could you check test failure?
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_3.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_33.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_12.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_18.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_0.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_24.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_15.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_27.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_6.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_30.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_21.test_reshape_contiguity
    tests.cupy_tests.manipulation_tests.test_shape.TestReshapeOrder_param_9.test_reshape_contiguity

13:51:06 _______________ TestReshapeOrder_param_3.test_reshape_contiguity _______________
13:51:06
13:51:06 self = <cupy.testing.parameterized.TestReshapeOrder_param_3 testMethod=test_reshape_contiguity>
13:51:06
13:51:06     def test_reshape_contiguity(self):
13:51:06         shape_init, shape_final = self.shape_in_out
13:51:06
13:51:06         a_cupy = testing.shaped_arange(shape_init, xp=cupy)
13:51:06         a_cupy = cupy.asarray(a_cupy, order=self.order_init)
13:51:06         b_cupy = a_cupy.reshape(shape_final, order=self.order_reshape)
13:51:06
13:51:06         a_numpy = testing.shaped_arange(shape_init, xp=numpy)
13:51:06         a_numpy = numpy.asarray(a_numpy, order=self.order_init)
13:51:06         b_numpy = a_numpy.reshape(shape_final, order=self.order_reshape)
13:51:06
13:51:06         assert b_cupy.flags.f_contiguous == b_numpy.flags.f_contiguous
13:51:06 >       assert b_cupy.flags.c_contiguous == b_numpy.flags.c_contiguous
13:51:06 E       AssertionError: Parameterized test failed.
13:51:06 E
13:51:06 E       Base test method: TestReshapeOrder.test_reshape_contiguity
13:51:06 E       Test parameters:
13:51:06 E         shape_in_out: ((2, 3), (1, 6, 1))
13:51:06 E         order_reshape: F
13:51:06 E         order_init: C
13:51:06 E
13:51:06 E       AssertionError: assert True == False
13:51:06 E        +  where True =   C_CONTIGUOUS : True\n  F_CONTIGUOUS : True\n  OWNDATA : False.c_contiguous
13:51:06 E        +    where   C_CONTIGUOUS : True\n  F_CONTIGUOUS : True\n  OWNDATA : False = array([[[ 1.],\n        [ 4.],\n        [ 2.],\n        [ 5.],\n        [ 3.],\n        [ 6.]]], dtype=float32).flags
13:51:06 E        +  and   False =   C_CONTIGUOUS : False\n  F_CONTIGUOUS : True\n  OWNDATA : False\n  WRITEABLE : True\n  ALIGNED : True\n  UPDATEIFCOPY : False.c_contiguous
13:51:06 E        +    where   C_CONTIGUOUS : False\n  F_CONTIGUOUS : True\n  OWNDATA : False\n  WRITEABLE : True\n  ALIGNED : True\n  UPDATEIFCOPY : False = array([[[ 1.],\n        [ 4.],\n        [ 2.],\n        [ 5.],\n        [ 3.],\n        [ 6.]]], dtype=float32).flags
13:51:06
13:51:06 a_cupy     = array([[ 1.,  2.,  3.],
13:51:06        [ 4.,  5.,  6.]], dtype=float32)
13:51:06 a_numpy    = array([[ 1.,  2.,  3.],
13:51:06        [ 4.,  5.,  6.]], dtype=float32)
13:51:06 b_cupy     = array([[[ 1.],
13:51:06         [ 4.],
13:51:06         [ 2.],
13:51:06         [ 5.],
13:51:06         [ 3.],
13:51:06         [ 6.]]], dtype=float32)
13:51:06 b_numpy    = array([[[ 1.],
13:51:06         [ 4.],
13:51:06         [ 2.],
13:51:06         [ 5.],
13:51:06         [ 3.],
13:51:06         [ 6.]]], dtype=float32)
13:51:06 self       = <cupy.testing.parameterized.TestReshapeOrder_param_3 testMethod=test_reshape_contiguity>
13:51:06 shape_final = (1, 6, 1)
13:51:06 shape_init = (2, 3)
13:51:06
13:51:06 tests/cupy_tests/manipulation_tests/test_shape.py:124: AssertionError

I am traveling and don't have access to a GPU for the next couple of days, but will take a look later in the week.

Okay, this seems to be an issue with different behavior in older numpy. If I mark the test as requiring numpy >= 1.12 it should work.
simple example:
import numpy as np
np.arange(6).reshape((1, 6, 1)).flags

This will show True for C contiguous, but False for F contiguous in NumPy 1.9-1.11, but True for both in NumPy 1.12+. Having both be True seems correct to me, so I think we just need to require 1.12+ on that test.

This is ready to try the CI again.  (I assume a core team member needs to request from Jenkins?)


fix: Make devTools enabled dependent on if dev environment

Description
This PR makes devTools enabled or not for renderer processes dependent on environment.
Note: engineering

@psjostrom we can simply override this change inside getWindowOpts right? instead of changing it in every place?

@psjostrom we can simply override this change inside getWindowOpts right? instead of changing it in every place?

Sure, calls for an API change for getWindowOpts, but I can of course do that also. Pushed commit with that change.


Could not find com.android.tools.build:gradle:2.3.3

Hello
what should I do?
Today i update gradle 4.6 version, then install and link react-native-sqlite-2 package.
Sync Failed:
Could not find com.android.tools.build:gradle:2.3.3.
Searched in the following locations:
file:/C:/Program Files/Android/Android Studio/gradle/m2repository/com/android/tools/build/gradle/2.3.3/gradle-2.3.3.pom
file:/C:/Program Files/Android/Android Studio/gradle/m2repository/com/android/tools/build/gradle/2.3.3/gradle-2.3.3.jar
https://jcenter.bintray.com/com/android/tools/build/gradle/2.3.3/gradle-2.3.3.pom
https://jcenter.bintray.com/com/android/tools/build/gradle/2.3.3/gradle-2.3.3.jar
Required by:
project :react-native-sqlite-2
https://jcenter.bintray.com/com/android/tools/build/gradle/  --- The requested path was not found.

I get a similar error:
`A problem occurred configuring project ':react-native-sqlite-2'.

Could not resolve all artifacts for configuration ':react-native-sqlite-2:classpath'.
Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
Required by:
project :react-native-sqlite-2
`

Any clues as to what might cause this?

Having the same issue. Manually updating the packages build.gradle (bad I know, but I was in a hurry) to match my project's fixed the issue for now. This is what I'm using:
repositories {
        jcenter()
        mavenCentral()
        mavenLocal()
        maven {
            url 'https://maven.google.com/'
            name 'Google'
        }
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.0'
    }

@anderssv it happened to me when upgrading RN to 57. I see several commits to the repo that will fix this issue when they are released
@joe-pritchard I had to do the same thing to work on the project, waiting for the newer release of the repo

Hi there,
After having some googling I found some information about this issue.
https://github.com/oblador/react-native-vector-icons/issues/910#issuecomment-446302095

Some packages were mistakenly removed by Google., and they are currently working on putting them back: https://issuetracker.google.com/issues/120759347.

The 2.3.3 version is looking for a file that has dissappeared from jcenter and that causes the error.
According to this thread, you can avoid this error by adding it to your android/build.gradle like so:
subprojects {project ->
    if (project.name.contains('react-native-sqlite-2')) {
        buildscript {
            repositories {
                maven { url "https://dl.bintray.com/android/android-tools/"  }
            }
            dependencies {
                classpath "com.android.tools.build:gradle:2.3.0"
            }
        }
    }
}

At the moment I don't have time to check if it works, but I believe it should work.

That configuration is worked well. Thank you all :)

Hi there,
After having some googling I found some information about this issue.
oblador/react-native-vector-icons#910 (comment)

Some packages were mistakenly removed by Google., and they are currently working on putting them back: https://issuetracker.google.com/issues/120759347.

The 2.3.3 version is looking for a file that has dissappeared from jcenter and that causes the error.
According to this thread, you can avoid this error by adding it to your android/build.gradle like so:
subprojects {project ->
    if (project.name.contains('react-native-sqlite-2')) {
        buildscript {
            repositories {
                maven { url "https://dl.bintray.com/android/android-tools/"  }
            }
            dependencies {
                classpath "com.android.tools.build:gradle:2.3.0"
            }
        }
    }
}

At the moment I don't have time to check if it works, but I believe it should work.


Sends POST request instead of PUT when UploadMethod.PUT is selected

Title is self explanatory. When looking at the dev tools, it shows that a POST is consistently sent even when UploadMethod.PUT is selected.

@passsionforprogramming is this on Android or iOS ?

@passsionforprogramming this seems to work, please use the beta version 3.0.0-beta.3


crashing navigation.navigate call because _history undefined

Issue
What happens is that i ask the user to load a url with a verification token in it.
My [routeRegistry.login.verifyToken.path] should pick this up, and it does. It then loads the VerifyToken component in the bottom of this issue.
But when everything goes fine, and it is suppose to call navigate, navigate crashes on this line https://github.com/frontarm/navi/blob/master/packages/navi/src/Navigation.ts#L182
It says _history is undefined.
How come?
Code setup
I have this route setup for now
export default mount({
  '*': map((request, context) => {
    const { authService } = context
    if(_.isEmpty(authService.currentUser)){
      const originalUrl = encodeURIComponent(request.originalUrl)
      return redirect(
        `${routeRegistry.login.path}?redirectTo=${originalUrl}`,
        {exact: false}
      )
    }
    return getAuthenticatedRoutes();
  }),
  [routeRegistry.root.path]: redirect(routeRegistry.login.path),
  [routeRegistry.login.path]: map(async (request, context) => {
    const { authService } = context
    if(!_.isEmpty(authService.currentUser)) {
      const path = decidedRedirectPath(request.params.redirectTo, routeRegistry.dashboard.path)
      return redirect(path)
    } else {
      return getLoginRoute();
    }
  }),
})

const getLoginRoute = () => {
  return mount({
    '/': route({
      title: 'Login',
      view: <SignUp />
    }),
    [routeRegistry.login.verifyToken.path]: route((req,context) => {
      const token = req.params.token
      return {
        title: 'Verifying...',
        view: <TokenVerification token={token} authService={context.authService} />,
      }
    }),
  })
}

With this verifyToken component
import { useNavigation } from 'react-navi';

export default ({token, authService}) => {
  let navigation = useNavigation();
  useEffect(() => {
    const verifyEmailAsync = async () => {
      const { res } = await verifyEmail(token);
      if(res.status === 200) {
        await authService.login(res.data.token)
        navigation.navigate('/dashboard');
      }
    }
    verifyEmailAsync();
  }, [])

  return (

Loading..

  );

Usually, the only way that this._history can be undefined is that the <Router> component itself has been unmounted.
Could you show me how your <Router> component is being defined? Is it at the top level or somewhere lower?

@jamesknelson So I have the router defined at the highest level.
Above this is just the app inject into the DOM.
So dont understand why the router is ejected?
Can it have something to do with how I mount and stuff?
That the current route is not mounted somehow?
Or should it be available anyways?
Have added all my router logic underneath.
It happens under getNonAuthenticatedRoutes, and tokenVerification. We load the page from a link in an email and verify their login that way.
const RouterLayer = () => {
  const authService = AuthService.useContainer();
  if(_.isEmpty(authService.currentUser) && authService.loading) authService.login();
  if(authService.loading) return <LoadLayout authService={authService} />

  return (
    <Router routes={routes} context={{authService}}>
      <MainLayout authService={authService}>
        <Suspense fallback={null}>
          <View />
        </Suspense>
      </MainLayout>
    </Router>
  )
}

const ProviderLayer = () => {
  return (
    <AuthService.Provider>
      <RouterLayer />
    </AuthService.Provider>
  )
}

export default ProviderLayer;

export default mount({
  '*': map((request, context) => {
    const { authService } = context
    if(_.isEmpty(authService.currentUser)){
      const originalUrl = encodeURIComponent(request.originalUrl)
      return redirect(
        `${routeRegistry.login.path}?redirectTo=${originalUrl}`,
        {exact: false}
      )
    }
    return getAuthenticatedRoutes();
  }),
  [routeRegistry.root.path]: redirect(routeRegistry.login.path),
  [routeRegistry.login.path]: map(async (request, context) => {
    const { authService } = context
    if(!_.isEmpty(authService.currentUser)) {
      const path = decidedRedirectPath(request.params.redirectTo, routeRegistry.dashboard.path)
      return redirect(path)
    } else {
      return getNonAuthenticatedRoutes();
    }
  }),
  [routeRegistry.invitation.path]: route((request, context)=>{
    const { authService } = context
    const token = request.params.token
    return {
      title: 'Decentralized ID login',
      view: <InvitationVerification authService={authService} token={token} />
    }
  }),
  [routeRegistry.admin.path]: map(async (req, context) => {
    const { authService } = context
    const { currentUser } = authService
    if(!currentUser.isAdmin) {
      Notify.error('You do not have admin rights');
      return redirect(routeRegistry.root.path);
    }
    return route({
      title: 'Diwala admin page',
      view: <Admin />
    })
  }),
})

const getNonAuthenticatedRoutes = () => {
  return mount({
    '/': route({
      title: 'Login to Diwala',
      view: <SignUp />
    }),
    [routeRegistry.login.onboard.path]: route({
      title: 'How decentralized ID works',
      view: <OnboardWizard />
    }),
    [routeRegistry.login.verifyToken.path]: route((request,context) => {
      const token = request.params.token
      return {
        title: 'Verifying...',
        view: <TokenVerification token={token} authService={context.authService} />,
      }
    }),
    [routeRegistry.login.didLogin.path]: route((request, context)=>{
      const { authService } = context
      return {
        title: 'Decentralized ID login',
        view: <DidLogin authService={authService}/>
      }
    })
  })
}

const getCoursesRoute = () => {
  return mount({
    '/': map(async (request,context) => {
      return route({
        title: "Your courses",
        view: <Courses/>,
      })
    }),
    '/:id': map(async (request,context) => {
      return route({
        title: "Specific course",
        view: <Course/>,
      })
    })
  })
}

const decidedRedirectPath = (redirectParams, fallback) => {
  if(redirectParams) {
    return decodeURIComponent(redirectParams)
  }
  return fallback;
}

const getAuthenticatedRoutes = () => {
  return mount({
    [routeRegistry.verifyUserInfo.path]: route(async (req, context) => {
      const { authService } = context;
      return {
        title: "Verify your information",
        view: <VerifyUserInfoFormComponent authService={authService} />
      }
    }),
    [routeRegistry.registerEntity.path]: getRegisterRoute(),
    [routeRegistry.dashboard.path]: map(async (request,context) => {
      const { authService } = context;
      if(!authService.currentUser.name) return redirect(routeRegistry.verifyUserInfo.path);
      if(!authService.currentEntity || !authService.currentEntity.verificationTxn) return redirect(routeRegistry.registerEntity.path);
      return route({
        title: "Diwala",
        view: <Dashboard currentEntity={authService.currentEntity}/>,
      })
    }),
    [routeRegistry.courses.path]: getCoursesRoute(),
    [routeRegistry.organization.path]: route({
      title: 'Organization',
      view: <Organization />
    }),
    [routeRegistry.userSettings.path]: route((request, context)=>{
      const { authService } = context;
      return{
        title: 'Your settings',
        view: <UserSettings authService={authService} />
      }
    })
  })
}

const getRegisterRoute = () => {
  return mount({
    '/': map(async(req, context) => {
      const { authService } = context;
      if(_.isEmpty(authService.currentEntity)) {
        return route({
          title: "Register your entity",
          view: <RegisterEntity authService={authService} />
        })
      }
      return redirect('/register/unverified');
    }),
    '/unverified': route(async(req, context) => {
      const { authService: { currentUser }} = context;
      return {
        title: 'Your entity has to be verified',
        view: <UnverifiedEntity currentUser={currentUser} />
      }
    }),

  })
}

One possible reason that this is happening is that if authService.loading becomes true after the routes have already loaded, e.g. when login is required, then this line here will unmount the router:
if(authService.loading) return <LoadLayout authService={authService} />

You can check if this is the case by putting a console.log with this line and checking if it is appearing in the console when the issue occurs.
Other than that, does <AuthService.Provider> always render its children? Or does it occassionally render nothing?

@jamesknelson thanks for tips, I will check it out within the next couple of days I believe
The authservice provider comes from unstated hooks: https://github.com/jamiebuilds/unstated-next
So no rendering happening there.

Well, what happened now was that I did not need that navigate there after all.
Because the auth service will login at that point, and the authservice set state function will make sure the router activates again and redirects/renders to the new right route

I'm hitting a similar error, except this itself (of Navigation.prototype.navigate) is undefined. My Router is the top-level component and is not being un/remounted. Do you have any clue why this could be?

I replicated the error here: https://codesandbox.io/s/dreamy-platform-c6b5g

@strass the issue here is that navigate isn't bound Navigation class, so you can't destructure it -- you'll need to call it as a method:
navigation.navigate(...)

Here's a codesandbox with a fix: https://codesandbox.io/s/infallible-rosalind-cskfu
If you want, I'd be happy to submit a PR that binds it so that it is possible to destructure.

Aaah, that explains a lot. I think that it should be possible to destructure or the typescript defs should be updated so that this case errors.

Would be happy to update TS defs, but is it even possible to type it that way? I'm not familiar with the right approach.

I'm not sure either – I think this is an artifact of typescript's duck typing, where it doesn't care whether an instance is a class or an object as long as it has all the right properties. I skimmed the docs and none of the class methods seem to cover this... Might be easier to just make it destructurable ;)

Yeah. I'm not sure when I'll have time, but would definitely accept a PR! Should just be a matter of binding the navigate functions.

Fixed in 0.13.6


Unable to logout of /arpa_reporter tool

Current state

When user clicks the Logout button on the arpa tool, they are not actually logged out.

Ideal State

When user clicks the Logout button the arpa tool, their session token is cleared and they need to be redirected to the login page.

Implementation details
There is a slight difference in how the ARPA and Finder tool handle sign outs. I think the issue lies in the clearing of the SET_LOGGED_IN_USER variable.
Finder Implementation: https://github.com/usdigitalresponse/usdr-gost/blob/_staging/packages/client/src/store/modules/users.js#L47
ARPA Implementation: https://github.com/usdigitalresponse/usdr-gost/blob/_staging/packages/client/src/arpa_reporter/store/index.js#L178

@as1729 to fill out the ticket with screenshots/loom

@ajhyndman I just added what I was able to find about this issue between the two codebases. My thinking was we just need to set logged in user to null on the ARPA tool, but I didn't actually get to writing any code. Thanks for your help!

This is now working.


docstring improvements

Improvements needed when looking at the html function reference

add NonlinearIOSystem to system creation section, interconnect to interconnection section
remove evalfr and freqresp (they still live in matlab module). Replace them with __call__ methods and frequency_response respectively. The former ends up being a bit verbose, I'm open to other ideas for how to present this.
updates lyap and care descriptions to be consistent with other functions
misc other formatting and consistency issues in various functions

Coverage remained the same at 94.831% when pulling 3a554b5070661d6b9b1554ee0b716afa30f9b390 on sawyerbfuller:update-docs into 8c764d0ea3ab57a080e97fd42a8bf49a75829592 on python-control:main.

old:

new:


Palo Alto Networks GlobalProtect: Include additional information and wording improvements

Add Reply URL (Assertion Consumer Service URL) as documented by Palo Alto Networks, see:
How to setup Azure SAML authentication with GlobalProtect
Reword the section about the Metadata XML file since it contains quite a bit more than just the SAML signing certificate.
Reference a generic file name instead of metadata.xml (it isn't always named like that and may lead to user confusion).
Mention import IdP errors that may be caused by lack of privileges of the signed-in user or 31 character limit of the SAML profile name.
Concerning the 31 character limit, see PAN customer support portal:
SAML IdP Metadata import fails with error message “Failed to parse IDP Metadata” due to Profile name having more than 31 characters
The XML import error due to lack of privilege issue is based on personal experience. I don't know the exact permission required on PAN-OS, but I can confirm that it ended up working with superuser permissions.

@jeevansd
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@matsimon, we're creating a separate PR for this in our repo for better content validation, you can expect the changes within 3-4 working days.
#please-close

Hi, thanks for the update, I wanted to ping on this topic since the current documentation hasn't been updated since (last update was in late 2023).

@matsimon, the article has updated as per your request, please let us know where isn't updated -https://learn.microsoft.com/en-us/entra/identity/saas-apps/palo-alto-networks-globalprotect-tutorial


Сan’t make a VD as the main one with sunshine ver24.8.6

Hello!
I'm using sunshine-moonlight with laptop and TV.
So it's just laptop display and VDD one, both 1080p, using VDD as main one.
But new version (24.8.6) works with sunshine only when it's not main display.
Laptop specs:
Win11 22h2
Core I5-11400H
RTX 3050
Right now moved to release HDR branch

same problem

This could potentially be sunshine/moonlight not grabbing the correct data, I'll take a closer look into this in a bit

Are you setting the display name in the Sunshine settings? It will be something like \.\DISPLAY37
You can run this script in Powershell to get the name of your virtual monitor:
irm scripts.mikethetech.com/display | iex
Then enter it in the Sunshine Display Sink settings.


Add -passin arg to ocsp

Add support for -passin to ocsp so the ocsp responder can be started programmatically.
Docs are updated, but no testing was added since after a quick look at the tests, it didn't seem like command-line switches were explicitly tested. Happy to add a test if necessary.
I did test it manually.
Fixes #10682
Checklist

[x] documentation is added or updated

Merged to master as 1cf20ca31b.
Thank you for the PR.


Code Signing Issue with Alamofire Latest SDK

@cnoon
I am really surprised to see this response from you. This issue is not with the iOS or XCode, it is something related to Alamofire itself. Moreover, it is not the issue specifically for me but for all the developers who are going to use the latest SDK with XCode 6.3. I have been using this since very long time but I never faced this issue earlier. I also tried the sample code which comes along with the SDK. It is giving the same issue. Moreover, app is running properly on Simulator as it don't require Code Signing but problem is with the device when I am use Development provisioning. According to Apple, all the third party SDK should be code signed automatically but they recently made some changes so I am not sure what is the actual issue and FYI, I have also looked around the Stackoverflow and then I came here as I also know this is not a forum.
This is the suggested answer which didn't worked for me, I hope you will understand this Now.
http://stackoverflow.com/questions/26459911/resource-rules-has-been-deprecated-in-mac-os-x-10-10
@mattt You please also take a look on this! This issue is coming with the example coming along with your SDK.

I made some changes in the build settings and now I am getting these two errors
error: remove /Users/username/Library/Developer/Xcode/DerivedData/NRN_Connect-cdtyqrtjoobklshabffstsfiaowi/Build/Products/Debug-iphoneos/NRN Connect.app/Frameworks/Alamofire.framework/_CodeSignature: Directory not empty
error: couldn't remove '/Users/username/Library/Developer/Xcode/DerivedData/NRN_Connect-cdtyqrtjoobklshabffstsfiaowi/Build/Products/Debug-iphoneos/NRN Connect.app/Frameworks/Alamofire.framework' after command failed: Directory not empty
Here is the screenshot

@harshcs We've responded now twice to the same support request, asking that you please not do this again. Please respect @cnoon's and my authority on this project. Any code signing issues you're having cannot be related to Alamofire itself, as Alamofire is just a Swift file. It's all to do with how you're incorporating it into your project.


Lazy loading assets

Hi!
Very nice project... I was looking for something just like this.
But, it would be very nice if it could also load assets like embedded js and css  in the template files.
One of the most concerns regarding SPA's is about performance. So, is better to load js and css bundles progressively. Having all css and js already in the first page load can be a huge performance issue. It's always nice to get just the assets for that page you're visiting...
It's really difficult to find some router that does that, I can achieve that using a combination with some router library and a module that loads html,css,js that I had to write on my own, but it has jQuery's dependency.
If your router could do such thing it would be perfect...
Great project! Keep it up!

Hi,
thanks for your interest in vanilla-ui-router and for your feature request :) Sounds very interesting.
I plan a "middleware" feature (similar to that of redux or expressjs) which is registered once while creating the router-object and is called immediately before any route-handler is invoked. Then it's possible to write a lazy-loading middleware or any other "plugins". I like the middleware concept because it keeps the router-core very simple and small and you can achieve complex additions which are completely encapsulated from the rest.
What do you think about that?
I hope I'll find some time in the near future, implementing the middleware feature. Then we could test the lazy loading as a middleware. If you are interested, pull requests are very welcome :)
René

What do you think about that?
Perfect!

I hope I'll find some time in the near future, implementing the middleware feature. Then we could test the lazy loading as a middleware. If you are interested, pull requests are very welcome :)
Sure! I am not sure if I can write some poc because I'm already committed to another project, but I can certainly help with fixes and tests.

I can share my solution so maybe it can be useful somehow.
My abstraction that loads html, css, js : https://github.com/jails-org/Demos/blob/master/TodoSPA/front/modules/loader/index.js
The use-case can be found here:
https://github.com/jails-org/Demos/blob/master/TodoSPA/front/apps/application/index.js#L42
The third-party router calls my loader on every url changes, the loader will get all assets and cache them, it will always load them only once.
Thank you for your attention, I'm hoping for more vanilla js contribution from front-end community just like this one.
o/


Add t.co shortened link replacement with real links

FxTwitter has it, seems easy to implement

This is already implemented

My bad


Add JustList: {JustList name}

TSk9EaNG4YRJWCfDAuHpbJd2FmkK3uKyHL

Please fill out the application in the correct format. Incorrect formats will result in the issue being closed. Also, confirm that a liquidity pool has been created on SunSwap


Stable API for Swashbuckle.AspNetCore.SwaggerGen

Hi
I'm using Swashbuckle for API generation with gRPC HTTP endpoints. To do this I've overridden Swashbuckle's IContractResolver.
In recent versions of Swashbuckle there have been API breaking changes here. See https://github.com/grpc/grpc-dotnet/issues/167#issuecomment-727814053
I've updated my library to use the latest changes in Swashbuckle.AspNetCore.SwaggerGen - https://github.com/aspnet/AspLabs/pull/319 - but I noticed in the latest source code that ISerializerDataContractResolver was renamed again to ISerializerBehavior.
My ask is that you try to find a stable API for Swashbuckle.AspNetCore.SwaggerGen. Thanks 😄

Totally fair ask - and you're probably not going to be happy about some of the further changes I'm exploring for that area of the code 😅. I've been a little more "dynamic" about refactoring that particular abstraction because a) it's an area of the code that I'm constantly battling with and believe there has to be a simpler way and b)  it's super low-level and not really something I'd consider as part of the "public interface". Not for the faint-hearted - something that should come with an "extend at your own risk" warning.
But of course, now that you've made me aware of an important project that does exactly that, I'll definitely strive for a stable API. Based on the current refactorings I'm looking at, perhaps we could agree on one final "breaking" change before locking it in for the longer term. I'll ping you with the MR when it's ready.

Had an issue regarding this, though fully unrelated to the gRPC lib, and wish just to document it here.
We observed the following error in our ASP .NET Core 3.1 project:

(click to expand) Could not load type 'Swashbuckle.AspNetCore.SwaggerGen.IDataContractResolver' from assembly 'Swashbuckle.AspNetCore.SwaggerGen, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=d84d99fb0135530a'.
Application startup exception: System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.
Could not load type 'Swashbuckle.AspNetCore.SwaggerGen.IDataContractResolver' from assembly 'Swashbuckle.AspNetCore.SwaggerGen, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=d84d99fb0135530a'.
   at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
   at System.Reflection.RuntimeAssembly.get_DefinedTypes()
   at Microsoft.AspNetCore.Mvc.ApplicationParts.AssemblyPart.get_Types()
   at Microsoft.AspNetCore.Mvc.Controllers.ControllerFeatureProvider.PopulateFeature(IEnumerable`1 parts, ControllerFeature feature)
   at Microsoft.AspNetCore.Mvc.ApplicationParts.ApplicationPartManager.PopulateFeature[TFeature](TFeature feature)
   at Microsoft.AspNetCore.Mvc.ApplicationModels.ControllerActionDescriptorProvider.GetControllerTypes()
   at Microsoft.AspNetCore.Mvc.ApplicationModels.ControllerActionDescriptorProvider.GetDescriptors()
   at Microsoft.AspNetCore.Mvc.ApplicationModels.ControllerActionDescriptorProvider.OnProvidersExecuting(ActionDescriptorProviderContext context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider.UpdateCollection()
   at Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider.Initialize()
   at Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider.GetChangeToken()
   at Microsoft.AspNetCore.Mvc.Routing.ActionEndpointDataSourceBase.<>c__DisplayClass11_0.<Subscribe>b__0()
   at Microsoft.Extensions.Primitives.ChangeToken.ChangeTokenRegistration`1..ctor(Func`1 changeTokenProducer, Action`1 changeTokenConsumer, TState state)
   at Microsoft.Extensions.Primitives.ChangeToken.OnChange(Func`1 changeTokenProducer, Action changeTokenConsumer)
   at Microsoft.AspNetCore.Mvc.Routing.ActionEndpointDataSourceBase.Subscribe()
   at Microsoft.AspNetCore.Mvc.Routing.ControllerActionEndpointDataSource..ctor(IActionDescriptorCollectionProvider actions, ActionEndpointFactory endpointFactory)
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite singletonCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.<RealizeService>b__0(ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.AspNetCore.Builder.ControllerEndpointRouteBuilderExtensions.GetOrCreateDataSource(IEndpointRouteBuilder endpoints)
   at Microsoft.AspNetCore.Builder.ControllerEndpointRouteBuilderExtensions.MapControllers(IEndpointRouteBuilder endpoints)
   at OUR_PROJECT_NAME.Startup.<>c.<Configure>b__5_0(IEndpointRouteBuilder c) in /src/src/OUR_PROJECT_NAME/Startup.cs:line 78
   at Microsoft.AspNetCore.Builder.EndpointRoutingApplicationBuilderExtensions.UseEndpoints(IApplicationBuilder builder, Action`1 configure)
   at OUR_PROJECT_NAME.Startup.Configure(IApplicationBuilder app, IWebHostEnvironment env) in /src/src/OUR_PROJECT_NAME/Startup.cs:line 76
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder)
   at Microsoft.AspNetCore.Hosting.ConfigureBuilder.<>c__DisplayClass4_0.<Build>b__0(IApplicationBuilder builder)
   at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.Configure(IApplicationBuilder app)
   at Microsoft.AspNetCore.Mvc.Filters.MiddlewareFilterBuilderStartupFilter.<>c__DisplayClass0_0.<Configure>g__MiddlewareFilterBuilder|0(IApplicationBuilder builder)
   at Microsoft.AspNetCore.HostFilteringStartupFilter.<>c__DisplayClass0_0.<Configure>b__0(IApplicationBuilder app)
   at Microsoft.AspNetCore.Hosting.WebHost.BuildApplication()

The issue we had was that we had a dependency on an internal package of our that referenced some Swashbuckle.AspNetCore.* packages, and one being Swashbuckle.AspNetCore.Newtonsoft, all with version 5.4.1. We then had a dependency on this internal package, but also an explicit reference to Swashbuckle.AspNetCore with version 5.6.3.
Just to visualize, our .csproj had something like this:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <!-- snip -->
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="OUR_INTERNAL_PACKAGE" Version="1.1.449" />
    <PackageReference Include="Swashbuckle.AspNetCore" Version="5.6.3" />
  </ItemGroup>
</Project>

As the Swashbuckle.AspNetCore NuGet package does not reference Swashbuckle.AspNetCore.Newtonsoft but the OUT_INTERNAL_PACKAGE does, NuGet then resolved the following versions:

The solution here was just to force the Swashbuckle.AspNetCore.Newtonsoft package up to v5.6.3 by simply adding it to the projects .csproj file as well.
  <Project Sdk="Microsoft.NET.Sdk.Web">
    <PropertyGroup>
      <!-- snip -->
    </PropertyGroup>
    <ItemGroup>
      <PackageReference Include="OUR_INTERNAL_PACKAGE" Version="1.1.449" />
      <PackageReference Include="Swashbuckle.AspNetCore" Version="5.6.3" />
+     <PackageReference Include="Swashbuckle.AspNetCore.Newtonsoft" Version="5.6.3" />
    </ItemGroup>
  </Project>

Not the most pleasant of debugging sessions I've experienced, so hopefully this comment could help someone else that experiences the same issue.

@JamesNK - I've maintained a backwards compatible API (vs 5.6.3) for the upcoming 6.0.0 release.
However, the current design and related abstractions are becoming increasingly unworkable as new features are added. Once 6.0.0 is out, I want to tackle this with some fundamental design changes. In doing so, I'll seek to minimize disruption by maintaining dual implementations with old APIs marked obsolete for a single major version cycle.

Hi @domaindrivendev  I am seeing the same issue with :
<PackageReference Include="Swashbuckle.AspNetCore.SwaggerGen" Version="6.0.2" />
as well. System.AggregateException : One or more errors occurred. (Could not load type 'Swashbuckle.AspNetCore.SwaggerGen.IDataContractResolver' from assembly 'Swashbuckle.AspNetCore.SwaggerGen, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=d84d99fb0135530a'.)

Any suggestions?
I saw from above comments it should have been resolved in 6.0.0?
I will try to update the Swashbuckle.AspNetCore.Newtonsoft and see if that fixes the issue.
Regards,
Vikas

Had an issue regarding this, though fully unrelated to the gRPC lib, and wish just to document it here.
We observed the following error in our ASP .NET Core 3.1 project:
(click to expand) Could not load type 'Swashbuckle.AspNetCore.SwaggerGen.IDataContractResolver' from assembly 'Swashbuckle.AspNetCore.SwaggerGen, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=d84d99fb0135530a'.
The issue we had was that we had a dependency on an internal package of our that referenced some Swashbuckle.AspNetCore.* packages, and one being Swashbuckle.AspNetCore.Newtonsoft, all with version 5.4.1. We then had a dependency on this internal package, but also an explicit reference to Swashbuckle.AspNetCore with version 5.6.3.
Just to visualize, our .csproj had something like this:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <!-- snip -->
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="OUR_INTERNAL_PACKAGE" Version="1.1.449" />
    <PackageReference Include="Swashbuckle.AspNetCore" Version="5.6.3" />
  </ItemGroup>
</Project>

As the Swashbuckle.AspNetCore NuGet package does not reference Swashbuckle.AspNetCore.Newtonsoft but the OUT_INTERNAL_PACKAGE does, NuGet then resolved the following versions:

The solution here was just to force the Swashbuckle.AspNetCore.Newtonsoft package up to v5.6.3 by simply adding it to the projects .csproj file as well.
  <Project Sdk="Microsoft.NET.Sdk.Web">
    <PropertyGroup>
      <!-- snip -->
    </PropertyGroup>
    <ItemGroup>
      <PackageReference Include="OUR_INTERNAL_PACKAGE" Version="1.1.449" />
      <PackageReference Include="Swashbuckle.AspNetCore" Version="5.6.3" />
+     <PackageReference Include="Swashbuckle.AspNetCore.Newtonsoft" Version="5.6.3" />
    </ItemGroup>
  </Project>

Not the most pleasant of debugging sessions I've experienced, so hopefully this comment could help someone else that experiences the same issue.

Thanks @jilleJr for your detailed response. Unfortunately I saw the same issue with 6.0.2 version as well. I would not have been able to resolve this issue quickly if I had not seen your comment. The error is very misleading and until you check the code like you did, its not possible. Thanks once again!


use BIGSECTORS to launch Devnet

Goal here is to allow some flexibility when launching the devnet

Yea look like viper converts an string env var to false when you ask for it using getBool


please add support for sx1280

Hi, Please support sx1280 so we can have much higher data rates.
Thanks

Hi @skylinezum
The new module has been added! Could you test if it works correctly?
Thanks!


Waypoint doesn't trigger on page refresh/reload

I use Waypoint (jQuery flavour) to fade-in / fade-out a "Go top" button when the user scrolls the page down and up. It works fine, but when page is refreshed the "Go top" button doesn't appear even if the offset has passed.
Here is my JS code, taken from Waypoint debug site and very slightly changed:
$('.scroll-top').waypoint({
    offset: 800,
    handler: function(direction) {
        if (direction === 'down') {
            $(this.element).animate({ opacity: 1 })
        } else {
            $(this.element).animate({ opacity: 0 })
        }
    }
});

I tried to create a JSfiddle, but refreshing the page doesn't behave as a real page, so I did an example test page
A Google search didn't help so much, and even on Stackoverflow I didn't get answerrs
Please, any help?

Have you tried that code inside "$(document).ready()"?

Yes, of course: I always put my jQuery script into that :-)

I had the same issue. I wrapped my waypoint function in a timeout:
setTimeout(function(){

$('.scroll-top').waypoint({
    offset: 800,
    handler: function(direction) {
        if (direction === 'down') {
            $(this.element).animate({ opacity: 1 })
        } else {
            $(this.element).animate({ opacity: 0 })
        }
    }
});

}, 100);

Thanks the setTimeout method worked perfectly for me :)


A1 add parentheses

Styling things like g(x)^3 as (g(x))^3 will reduce some extraneous cognitive load on these questions.

This is a limitation of how Sage produces LaTeX representing the power of a function - we'd only be able to accomplish this by typesetting the LaTeX by hand (or do something more clever than I know how to at the moment).
Keeping this open but it's not a quick fix for the fall.


mmap=True not compatible error

To Reproduce

Open corrscope and add some channels
Click on 'Preview' or 'Render'

Expected behavior
Seeing the result
Actual behavior
I got the error message:
"Traceback (most recent call last):
File "corrscope\gui_init_.py", line 750, in run
File "corrscope\corrscope.py", line 242, in play
File "corrscope\corrscope.py", line 207, in _load_channels
File "corrscope\corrscope.py", line 208, in
File "corrscope\channel.py", line 79, in init
File "corrscope\wave.py", line 150, in init
File "corrscope\utils\scipy\wavfile.py", line 690, in read
File "corrscope\utils\scipy\wavfile.py", line 485, in _read_data_chunk
ValueError: mmap=True not compatible with 3-byte container size."
Screenshots

Version

OS: Windows 10 x64
Corrscope version: 0.8.1
How you installed corrscope: official Windows binaries
How you obtained FFmpeg: i downloaded the full windows binary and put it on "C:\Users\Henrique\AppData\Local\Microsoft\WindowsApps"

afaik, this is an error with your wav files. If it's not a supported format (by format I don't mean wav or mp3, I mean bit-depth), Corrscope will not render it.

so do i have to make the depth 16/32 bit?

yes, that should work


Link solidity libraries

This is a first approach for linking solidity libs before deploying logic contracts.
Implemented so far:

[x] Solidity libs discovery
[x] Solidity libs linking
[x] Solidity libs tracking (in zos.network.json)
[x] Fixed zos status ... --fetch command to compare implementations as both logic contracts and solidity libs

Still have to:

[ ] Add tests
[ ] Fix skipped tests
[ ] Finish fixing the zos status ... --fix command
[ ] Recursive solidity libs discovery

@jcarpanelli please review the new commits!


Stop step name aliasing.

Currently we assume that
[10]
[20]

is the same as
[default_10]
[default_20]

and allow the use of
sos run script default

We also allows
[A]
[A_20]

and assumes
[A]

is equivalent to
[A_0]

These all make sense but has caused ambiguity in the specification of sos_step and from_steps.
For example, we need to make sure that both
sos_step('default_10')

and
sos_step('10')

work, and perhaps also
sos_step('default')

and things get complicated with the new from_steps input option because
[10]
[20]
[30]
input: from_steps=['default_10']

would be confusing but it is difficult to support
[10]
[20]
[30]
input: from_steps=['10']

because of internal use of default_10. (It is not very difficult but troublesome and confusing anyway).
I would suggest that we get rid of step name aliasing and use whatever user specifies as the step name. The side effect is that we can no longer do
sos run script default

because the workflow does not have a name, but the numeric numbered steps are the default ones so default in the command is not needed anyway.

I agree. I have had this problem with sos_step before. With the new "share" the default behavior can indeed be more confusing than before. But if a script only has one step will that be recognized and used as default? When there are multiple steps, will the ones with default_ be recognized to be the default step with sos run? I am talking about backwards compatibility.

Yes, workflow A
[A]

or
[A_1]
[A_2]

will be called by
sos run script

since A is the only workflow in the script.