Cannot add or delete urls - js/insert.js doesn't seem to be updated for modern browsers

In reference to:
https://github.com/YOURLS/YOURLS/issues/2089 (version info here)
https://github.com/YOURLS/YOURLS/issues/392
and direct relevance to http://www.davewooding.com/yourls-not-working/
and after reading the wiki, the FAQ, and the installation guide and an unnecessary close the reason of a mod having a bad day or in-denial,
**You cannot add or delete urls that start with http. **This includes deleting, modifying, or adding or you will get an Ajax Access-Control-Allow-Origin err.
Could it be the insert.js needs updating for modern browsers?
If I follow the instructions above http://www.davewooding.com/yourls-not-working/ and modify insert.js - I actually CAN delete a url without an ajax error, proving that it is, indeed, something to do with this file, although I can't add because the code stops due to having "illegal characters" (hidden line break chars? Issue with replace("http://", "") thinking // is a comment or something, even if it's within a string? I'm not sure, but I do know that this file needs work.
Any suggestion what to do without an instant close of topic? I'm still looking into this BUG as I speak and will reply if I find a solution before someone else.
EDIT 1:
I checked out my config.php and noticed something:
Although I have define( 'YOURLS_SITE', 'http://my.site' ); , my.site/admin will redirect to www.my.site/admin
Could CORS be failing because www vs no www?

Resolved - The .htaccess generated does NOT predict that a parent directory's .htaccess could possibly redirect to www, and does not counter-measure this (which 90% of sites in 2016 seem to do), therefore failing CORS due to www vs non www.

@dylanh724 Thanks for your feedback.
That said, please respect people and try to make more constrictive reports to avoid "Oh big problem! Nevermind, I've read the docs and it's now fixed.".
Also, if you think documentation or even the YOURLS itself isn't as good as it should be, your contribution is welcome.

"That said, please respect people and try to make more constrictive reports to avoid "Oh big problem! Nevermind, I've read the docs and it's now fixed.".
How was this relevant to this post? I fixed this by research, trial and error.


new-sequence command

Addresses #16.

Sorry, I've been out of town and just got back. I'll look at this pull request this afternoon.

No problem

Alright, I looked through everything but tests/new_sequence.rs. It looks good, just a few minor things.  But the working directory is attached to the process, so we can't really solve the problem. The only solution I see is not even using the working directory and only using absolute paths. But that would mean reworking a lot of things in both the tests and the arg parsing/dispatch code. So lets not do that now, or anytime soon, unless you feel that its worth it.
Also, super sorry for procrastinating. I hate it when other people procrastinate on stuff I'm waiting on, and I feel really guilty when I do it to others. So, really sorry.

The changing directories is annoying, but I agree that it is a back burner issue for now. No problem on the procrastination; I've been busy, I know this probably isn't your absolute top priority right now, and I am totally fine if it takes a couple days for a PR to get reviewed. :smile:

Ready for re-review

K, you forgot to change "unknown" => "No file extension". I marked out one other error message in the regex compilation. side from that it looks good. However, I haven't actually managed to get sfml to compile on my computer. We're going to need to double check that every thing is statically linked (so that the native dependencies are compiled right into the binary we distribute). I'll give this a ship it after those 2 error messages are fixed and I have this working.

K, I got it compiling and tests pass. Rust's internal ld didn't check /usr/local/lib by default. I had to set an env var LIBRARY_PATH="/usr/local/lib". Weird though, idk why rust doesn't use system ld.

Major problem I forgot to mention: Why is everything executable all of a sudden? Change the permissions back.

Everything is executable because I had to transfer the files via flash drive, and there must've been a default file mode set. Will change back.

LGTM. After you switch the permissions, go ahead and squash and merge.


Unable to find dependencies

Unsure of what the exact issue is and why it cannot find the modules node_modules when doing browserify build:
JAWS: -------------------------------------------
JAWS:  Dashboard:  Deploying Lambdas...
JAWS: -------------------------------------------
JAWS: Lambda Deployer:  Packaging "lAwsmUsersCreate"...
JAWS: Lambda Deployer:  Saving in dist dir /var/folders/9h/_6jlx37d1flfdfdf0z1v50r80000gn/T/lAwsmUsersCreate@1444044791712
JAWS: Getting ENV file from S3 bucket: jaws.dev.useast1.myapp-nj1ghi1x.com in us-east-1
Error running browserify bundle
{ [Error: Cannot find module 'bluebird' from '/private/var/folders/9h/_6jlx37d1flfdfdf0z1v50r80000gn/T/lAwsmUsersCreate@1444044791712/aws_modules/awsm-users/create']

ls /private/var/folders/9h/_6jlx37d1flfdfdf0z1v50r80000gn/T/lAwsmUsersCreate@1444044791712/node_modules/awsm-users/node_modules
bcryptjs     bluebird     debug        dotenv       jsonwebtoken moment       node-uuid

https://github.com/dekz/awsm-users/tree/1.3

@dekz Sorry, I meant to share this with you last night:  https://github.com/ac360/awsm-users/blob/master/lib/users.js
But, your logic has to be moved to the lib folder.  Particularly, your dependencies or they won't resolve.  We're attempting to make the aws-modules more like regular modules and not editable templates.  I didn't get very far with this but it shows off the pattern you will need.
So, the lib folder is where you write your logic and require all of your dependencies.  In the awsm/lambda should not require those dependencies.  Instead, those files should only require your aws-module itself, and use that.  In your aws-module, you expose functions/methods for awsm/lambda/files to use.

That explains that, cheers Austen!

This is actually quite onerous. I can't just code up an endpoint: I have to code up a node module with an arbitrary opinionated structure just to write an endpoint.
Can we just make it so that I can install and require node_modules in the awsm folder?
Sometimes you don't want to make a reusable module to share, you just want to write some code....

@jwulf Could you clarify on "Can't code up an endpoint"?  You can still code up a lambda function/endpoint without making a corresponding node_module.  Just make sure your lambda's dependencies are in the root package.json, which is shared by all Lambdas.
This is a big decision.  I'm very open to feedback here.  Especially from you @jwulf!

When using the module create command you can create a module within your project without the need for an NPM module. As @ac360 mentioned, loading project dependencies from the aws_modules dir shouldn't be a problem and works the exact same way as for every other Node.js project. :)

Yep. I really like this design. Now it's both a template and an NPM. Whatever your project needs.

how do you include external (non awsm) modules in JAWS? I'm requiring them as normal and it works when I jaws run, but jaws deploy is giving me this error:
 {
  "errorMessage": "Cannot find module '/private/var/folders/9n/bsnlhf010h310zdh9pcb5s0x6ng6pf/T/lJasperUpdatecdr@1444446978230/node_modules/pg-bricks/node_modules/pg/lib/client'",
  "errorType": "Error",
  "stackTrace": [
    "Function.Module._resolveFilename (module.js:338:15)",
    "Function.Module._load (module.js:280:25)",
    "Module.require (module.js:364:17)",
    "require (module.js:380:17)",
    "i (/var/task/aws_modules/jasper/updatecdr/handler.js:1:497)",
    "/var/task/aws_modules/jasper/updatecdr/handler.js:1:688",
    "Object.<anonymous> (/var/task/aws_modules/jasper/updatecdr/handler.js:2:16197)",
    "Object.events (/var/task/aws_modules/jasper/updatecdr/handler.js:2:17253)",
    "i (/var/task/aws_modules/jasper/updatecdr/handler.js:1:637)",
    "/var/task/aws_modules/jasper/updatecdr/handler.js:1:688"
  ]
}

dekz 13:36
you need to make your lambda code (index.js) a smal wrapper around your lib code
your code in lib can resolve the 3rd party requires
l85m 13:49
yep that's what I have now - there are no 3rd party requires in aws_modules, only in lib
I require lib like this var action = require('../../../index.js').updatecdr;
contents of ../../../index.js is exports.updatecdr = require('./lib/updatecdr.js');
dekz 13:50
and you did a npm install —save pg-bricks
l85m 13:50
yep
./node_modules has all the dependencies
including pg-bricks
second line of updatecdr.js is var db = require('pg-bricks').configure(constring);
dekz 13:56
whats in your handler.js file?
l85m 13:56
'use strict';

/**
 * AWS Module: Action: Lambda Handler
 * "Your lambda functions should be a thin wrapper around your own separate
 * modules, to keep your code testable, reusable and AWS independent"
 */

require('jaws-core-js/env');

// Modularized Code
var action = require('./index.js');

// Lambda Handler
module.exports.handler = function(event, context) {
  action.run(event, context, function(error, result) {
    return context.done(error, result);
  });
};

here's ./index.js
 var action = require('../../../index.js').updatecdr;

module.exports.run = function(event, context, cb) {
  return action(event, cb)
};

dekz 13:58
that ../../../index.js is in your jaws project root?
l85m 13:58
yep
feels like there's a better way to do that which I'm missing
dekz 13:59
move those functions into the lib folder
I’m not that familiar with how the Browserify build works though sorry
l85m 14:00
this is what's in ../../../index.js:
 exports.updatecdr = require('./lib/updatecdr.js');

no worries, appreciate you trying to help
not really sure what the right structure is, the docs don't seem to have it
the folder structure completely excludes node_modules and lib
this one: https://github.com/jaws-framework/JAWS/blob/master/docs/project_structure.md
dekz 14:04
ah yes that is frustrating
l85m 14:05
I'll check out the browserify docs - I didn't really even know that browserify was doing the magic until you just said it
dekz 14:06
do you want to push your code some where @l85m, might get a chance to take a look at it later tonight
l85m 14:08
thanks for the offer @dekz - unfortunately there's some stuff in here we can't share right now but I will just go back to a non jaws approach for now and try and figure it out on monday. ping you back when I figure it out
thanks again for trying to help!

I ran some tests and I've noticed 2 problems, both related to Browserify:

If an NPM module has optional dependencies (for example, redis module has optional dependency on hiredis), the Browserify build fails when this dependency is not found. This can be solved by passing the ignoreMissing option to Browserify. (See PR: https://github.com/jaws-framework/JAWS/pull/215)

In the specific case of the pg-bricks package, it has underlying dependencies which contain some require statements which break the Browserify build. I've submitted 2 PR's to fix this (https://github.com/brianc/node-pg-types/pull/43 and https://github.com/brianc/node-postgres/pull/875), but it might take some time before these changes are generally available in pg-bricks.

To clarify things a bit more, you should be able to simply require node modules from JS files in the aws_modules directory in the usual way, i.e. you can simply do:
var db = require('pg-bricks');

There is no need to wrap stuff in an index.js file, that's only required when creating reusable NPM modules.
Better docs on these subjects have to be provided, this is on the roadmap!

@joostfarla - just to clarify, is this meant to reflect how things should work, or how they currently do?

To clarify things a bit more, you should be able to simply require node modules from JS files in the aws_modules directory in the usual way

Also thanks for looking into pg-bricks.  I'll use your PR until it's merged.

just to clarify, is this meant to reflect how things should work, or how they currently do?

This is how things currently work!

Following up on this, I'm getting the error Cannot find module<EMAIL_ADDRESS>both if I use pg-bricks or pg-promise. any idea? thanks!

@thenikso hey could you please explain the modification you did to the module? Did you end up using Browserify (= Optimizer) or Webpack?
Thanks

hi @laurentmeyer I used webpack with the 0.4 which helped me to debug the problem. now with serverless 0.5 I'm using browserify (only because the webpack plugin hasn't been updated yet) and you can find more info about this problem here https://github.com/serverless/serverless-runtime-babel/issues/8


Localize code-of-conduct.md for Hindi

Please describe why this term needs to be updated
Why this term needs to be updated? (briefly)

Localize Code of Conduct for Traditional Hindi because it is available in various languages excluding Hindi.
-https://github.com/cncf/foundation/blob/main/code-of-conduct.md

Can you assign me @jihoon-seo ,So that I will work on this

That file is in https://github.com/cncf/foundation, not in this repo.
You may start with opening an issue in https://github.com/cncf/foundation .

I have opened this issue in CNCF Foundation @jihoon-seo


fixed invocation of pkg_add (freebsd)

I've just caught it. The [pkg_add(1)] (https://www.freebsd.org/cgi/man.cgi?query=pkg_add&apropos=0&sektion=1&manpath=FreeBSD+9.1-RELEASE&arch=default&format=html) has no sub-command called install (it has no sub-commands at all) so the previous code always tried to install a package called install, which obviously was failing. This PR shall fix the issue.

Thanks.

Released as v2.63.1.


Error:(2, 0) Cannot add extension with name 'idea', as there is an extension already registered with that name.

I could not use your plugin:
Error:(2, 0) Cannot add extension with name 'idea', as there is an extension already registered with that name.
changing constants in org.jetbrains.intellij.IntelliJPlugin to
private static final CONFIGURATION_NAME = "ideaplus"
private static final EXTENSION_NAME = "ideaplus"
solved this problem (or is it just a symptom?)
 I wan't just to write a simple idea-plugin for PhpStorm and integrate it in travis-CI. Maybe you can provide some help for me?

Extension was renamed to 'intellij', uploaded 0.4 version.


Shortcut to assign application to zone directly

If you have many zones it's quite cumbersome to put the right application in the right zone.
Although it remembers the previous assignment it;s often that you have to redo the assignment due to opening the application multiple times and assign to different zones.
Ability to use a shortcut + number / key to assign an application directly to zone.  (e.g CTRL+SHIFT+ 1 for zone 1).

You really need to give more information.

@Davidoffski1234 one issue you'll face is "active monitor" for this.  If you have multiple monitors, what goes where
@enricogior, do we have a tracking issue for this?  I know we discussed being able to do this for the first 10 (0-9) zones.  feel like this was a tracking item for v2 editor

The tracker is https://github.com/microsoft/PowerToys/issues/1411


EpollEventLoopGroup missing Executor-based constructor

EpollEventLoop is sold as a drop-in replacement for NioEventLoop (at least on Linux), but EpollEventLoopGroup only has the ThreadFactory-based constructor, not the Executor-based constructor that NioEventLoopGroup also includes.

thanks for reporting @alugowski


add 1000phone

Please add 1000phone to education license. 1000phone(千锋教育）is a IT training institution which offers front-end (JavaScript) corse for students.

@MinionsHero I am sorry, this domain does not belong to a university, nor to a college. I have to close the request without merging. Please ensure that you are familiar with this repository rules located at the bottom of this page before submitting a new request.
Please apply for an appropriate licensing option (which may also be free) at https://www.jetbrains.com/buy/classroom/#commercial
Thank you for the understanding!


Add Default Zone Endpoint for users

Description
Store on the user template the last zone it used, allowing it to use the same zone next time it logs in.

Progress Status

[x] Branch created
[x] Code committed to development branch
[x] Testing - QA
[x] Documentation
[x] Release notes - resolved issues, compatibility, known issues
[x] Code committed to upstream release/hotfix branches
[x] Documentation committed to upstream release/hotfix branches

A new bug was introduced in 5.8.3, changing he image of a disk on a VM Template of a vCenter VM causes a JS error due to missing imports. Fixed in repo.


Collaborative editing of single file

Issue Type: Bug
As soon as we tried to collaboratively edit the same file it lost sync and changes from remote are not reflected in actual files.
Extension version: 0.3.93
VS Code version: Code 1.22.1 (950b8b0d37a9b7061b6f0d291837ccc4015f5ecd, 2018-04-06T00:21:13.607Z)
OS version: Darwin x64 16.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.21GB free)

Process Argv
/Applications/Visual Studio Code.app/Contents/MacOS/Electron

Screen Reader
no

VM
0%

Did this repro multiple times, or just once? Were both sides running macOS & VSCode?

Multiple times (it was our first experience as well, just loaded solution and I was like - this is what broke in similar products before when we try to write the same function together. And unfortunately same happened here), we reverted to actually talking to each other: now I will write, now I will write, now I will write.
I was using Mac and my partner was using Windows. We both used VSCode with plugin downloaded today.

What programming language were you using? And who was the person sharing -- windows or VS Code?

We used javascript. Sharing person was on windows.

Last clarifying question: On the VS side, they saw their edits in the document as they typed, or it didn't let them type at all


Change cirrus-ci to match backend

Purpose
What is the context of this pull request? Why is it being done?
When I created the whitelist entry for this service on the backend, I added a dash. It is faster to fix it here then there.
Notable Changes
Are there any changes that need to be called out as particularly tricky or significant?
No
Tests and Risks?
Is this covered by existing tests? New ones? If no, why not?
Yes, tests updated
Update the SHA1SUM file
Also make sure that you update the sha1 hash by running sha1sum codecov and updating the SHA1SUM file with the output
Change the codecov to - in the file before commiting so it can be compared against the server file
Fixes #237

Merged, waiting on deploy

This has been deployed.


Buggy location for Lang-40 is wrong

Hi,
I found that the buggy location for the Lang-40 bug in the Defects4J benchmark is wrong. The correct line should be 1048  (instead of 223 in the current version) according to Defects4J-dissection

Hi @thanhlecongg ,
This is interesting. The data for the fault localization was taken from SequenceR, so I will have to update the benchmark repository and the submodule reference. Thanks for the info! :) Will put it as an issue on the other repository


Release 2.2

:white_check_mark: Build vswhere 2.2.3+g404256adc9 completed (commit https://github.com/Microsoft/vswhere/commit/404256adc9 by @heaths)


When sorting by downloads, mods with 0 downloads appear higher than the mod with the most downloads

Edit  - only happens when sorting from lowest at the top and highest on the bottom


Unable to load the epub List.

I am able to configure the Project Successfully.
but running application on real device I didn't get any Epub List.
I have also read the various link in issues section.
https://github.com/readium/SDKLauncher-Android/issues/98#issuecomment-231199794
but it does not resolve the issues.
Every time I got the same Toast.
"No eBooks Found: /storage/emulated/0/sdcard0/epubtest"
Please help me out

does the 'epubtest' folder exist on your "sdcard" (Android internal storage)

Yes ,
Even I have paste a EPUB also in the same folder.

Yes,
I have paste the EPUB file also to the same folder.

hardware device or software emulator?
either way, what do you see in the folder when you use ADB?
'adb shell ls -als /sdcard'

I am using real device to Debug

I have done it by re-cloning the Same Version may be there is issue with the previously cloned Repo.
Thanks Guys


Is MSB5004: The solution file has two projects named X correct?

When trying to build Microsoft.CSharp.sln from corefx with msbuild (v14.0.24720.0), I get the following error:

Solution file error MSB5004: The solution file has two projects named "Microsoft_CSharp".

The solution file indeed has two projects with the same name, so the error looks correct. But in Visual Studio 2015, the solution builds correctly. Is this discrepancy expected? If not, which one is wrong, msbuild or VS?
(Since there doesn't seem to be any reason for the duplicate project name, I have also created an issue in corefx to fix the solution: dotnet/corefx#7024.)

The check is there because MSBuild uses project names  to construct target names when generating metaproj files from the solution, and if there are multiple targets with the same name, the last one wins.
But that's just an implementation detail and MSBuild should support duplicate names if Visual Studio does. There's already infrastructure to generate a unique name, but I can't tell if that unique name is actually used.

As you know "Project Name" in the solution file context means "string immediately after the GUID in the sln file" not "filename of project". It does originate from the filename, and if you rename the project in VS it will rename both so generally they match.
The reason that VS stores the project name separate from the filename is that it can be different from the filename. VS allows two projects to have the same name in the solution, if they are in different solution folders. Solution folders are virtual folders, stored only in the solution (as virtual projects!) and visible as folders in the solution explorer. (VS does not allow projects to have the same name merely by being in different file system folders -- because those real folders aren't usually shown in the solution explorer)
This solution has no solution folders so it is not valid for it to have two projects with the same name. VS is tolerant of the hand edit but when you save the solution again, you will see the project name was updated to match the file name.
GetUniqueProjectName() prefixes the project name with any solution folder name, so it will handle any solutions that VS would write out. In this case, to make MSBuild as tolerant as VS, the code probably should go further if the name is still not unique. For example, it could use the file name instead of the project name. It should not simply change to use the file name, or some other scheme, as the unique project name is used to generate public target names as noted above. So people do "msbuild my.sln /t:fooproject:build". So it's important that the names generated using valid solution files remain the same. Ideally, the result would be deterministic as well.
The VS solution parser is so complex and the format so horrible that many times this code has had to change to be equally tolerant. It would be wonderful if .sln could be replaced with something MSBuild format.

Customers sometimes generate .sln using scripts, BTW, so it is quite common for them to not be written out exactly as VS would write them.

Closing as "won't fix" since this is an invalid solution file and there's a workaround of opening and resaving in VS. Tagging as sln-related in case we decide to come back and be more tolerant, like VS itself is.
If anyone else runs into a similar problem, please note it here. If this is more common of a problem than I currently think we could revisit the decision to not build tolerance in.

I have the same problem with sln files generated with premake. Visual studio opens the solution without issues, msbuild crashes. Opening and resaving doesn't help, because I'm working on a Jenkins build that re-generates the solution file every time.


configure: Check for libraries only when libc does not provide

Using AC_CHECK_LIB ignores symbols already provided by other libraries,
or in other words it links libuv against libraries that it does not need.
Attempts to remove specific libraries were met with arguments that older
libc versions would still require them.[0]
Fix this by using AC_SEARCH_LIBS instead of AC_CHECK_LIB.
[0] E.g. https://github.com/libuv/libuv/pull/2493

I'm okay with this change but I'd like to know what the concrete issue was that you ran into. Something with librt?

Cf. bug reports like [1] where (for good reasons) one or more of those auxiliary libraries happens to be installed on a (development) system, and libuv picks those up instead of the libc internals.
[1]https://bugs.gentoo.org/show_bug.cgi?id=710620

This change breaks the linux and freebsd builds with link errors along these lines:
./.libs/libuv.so: undefined reference to `pthread_atfork'

And:
test/run_tests-runner-unix.o: In function `process_wait':
/usr/home/iojs/build/workspace/libuv-test-commit-freebsd/nodes/freebsd11-x64/test/runner-unix.c:272: undefined reference to `pthread_create'
./.libs/libuv.so: undefined reference to `pthread_barrier_init'
./.libs/libuv.so: undefined reference to `pthread_condattr_destroy'
./.libs/libuv.so: undefined reference to `pthread_barrier_destroy'
./.libs/libuv.so: undefined reference to `pthread_barrier_wait'
./.libs/libuv.so: undefined reference to `pthread_condattr_init'
./.libs/libuv.so: undefined reference to `pthread_condattr_setclock'
cc: error: linker command failed with exit code 1 (use -v to see invocation)

This may require use of AX_PTHREAD[2] or similar.
[2] https://www.gnu.org/software/autoconf-archive/ax_pthread.html

This change breaks the linux and freebsd builds with link errors along these lines:
./.libs/libuv.so: undefined reference to `pthread_atfork'

And:
test/run_tests-runner-unix.o: In function `process_wait':
/usr/home/iojs/build/workspace/libuv-test-commit-freebsd/nodes/freebsd11-x64/test/runner-unix.c:272: undefined reference to `pthread_create'
./.libs/libuv.so: undefined reference to `pthread_barrier_init'
./.libs/libuv.so: undefined reference to `pthread_condattr_destroy'
./.libs/libuv.so: undefined reference to `pthread_barrier_destroy'
./.libs/libuv.so: undefined reference to `pthread_barrier_wait'
./.libs/libuv.so: undefined reference to `pthread_condattr_init'
./.libs/libuv.so: undefined reference to `pthread_condattr_setclock'
cc: error: linker command failed with exit code 1 (use -v to see invocation)

The FreeBSD build log seems to point to a network timeout in git fetch unrelated to my changes.
https://ci.nodejs.org/job/libuv-test-commit-freebsd/1833/console
The POSIX threads implementation related errors may have been fixed by the latest push.

@jer-gentoo You need to go one level deeper: https://ci.nodejs.org/job/libuv-test-commit-freebsd/1833/nodes=freebsd11-x64/console

Oh right. Does the recent push change anything about that?

Sorry, I thought I'd started the CI last night. Here is a new run: https://ci.nodejs.org/job/libuv-test-commit/1897/

AX_PTHREAD required an argument, so I've changed that now.

https://ci.nodejs.org/job/libuv-test-commit/1901/

https://ci.nodejs.org/job/libuv-test-commit/1901/

That looks to me like a single build failure in an OS X cmake build, which should be unrelated to the autotools changes I introduce here.

Landed in b4fe4f6ad91d380c6af2b4ab2a1c624e58947608. Thanks!


Readiness and liveness probes in Kubernetes

I'm struggling to setup a health check for the proxy container on Kubernetes. Some documentation or guidance around this would be great. We're having to delete pods quite regularly due to an app not being able to connect.
Tried defining a tcp liveness probe which didn't quite do the trick.

So far we don't expose such thing unfortunately...
As a work around you can check by run cmd:
netcat -U /cloudsql/$INSTANCE_CONNECTION_STRING
As for the "an app not being able to connect" issue, if you think it might due to cloud sql proxy, please send an email with following information to<EMAIL_ADDRESS>so I may be able to help out looking at some internal data.

with a link to this page.
describe the issue you have.
the full name of your cloud sql instance.
the command your run
the full logs

When trying to deploy as recommended in kubernetes with spinnaker, it seems the lack of the probe causes the highlander strategy to tear down the node.
I'll try the netcat, but it would be convenient if there was a typical set of endpoints without having the INSTANCE_CONNECTION_STRING in more than one place.

netcat is not available on the stock image, so this:
livenessProbe:
  exec:
    command: ["netcat", "-U", "/cloudsql/coverbid:us-central1:db=tcp:3306"]
  initialDelaySeconds: 5
  timeoutSeconds: 10

fails with
Liveness probe failed: rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"netcat\": executable file not found in $PATH"

I misunderstood netcat's location and options on the image.
I attempted the following:
livenessProbe:
  exec:
    command: ["nc", "/cloudsql/foo:us-central1:db=tcp:3306"]
  initialDelaySeconds: 5
  timeoutSeconds: 3

and it failed with:
Liveness probe failed: nc: bad address '/cloudsql/foo:us-central1:db=tcp:3306'

Has anyone else gotten nc to work as a probe?

Would you please try:
livenessProbe:
  exec:
    command: ["nc", "<IP_ADDRESS>", "3306"]
  ...

The command I pasted before (netcat -U /cloudsql/$INSTANCE_CONNECTION_STRING) was for unix domain socket.

Thanks @AthenaShi, that does report success.

Seems like there's no problem left for this thread.  Close it.

The healthcheck using netcat in zero-I/O mode works, but has the annoying side-effect of spamming our stackdriver logs with errors:
New connection for "xxxx"
Client closed local connection on <IP_ADDRESS>:3306

Hi,
I have added the Liveprobe  using netcat is basically working for me, but It is also spamming my logs with this message:
 Writing data to local connection on <IP_ADDRESS>:3306 had error: write tcp <IP_ADDRESS>:3306-<IP_ADDRESS>:45075: write: broken pipe
Can anyone give me a hint how I could solve this problem?

Are there any plans to get this running agin?
I've had multiple occasions where I get a dial tcp <IP_ADDRESS>:3307: connect: connection refused on the proxy.

None of this solutions is working for me. I'm getting this, no matter what utility I try to use (executing a command with /bin/sh, netcat, nc, telnet)
Readiness probe failed: OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "nc": executable file not found in $PATH: unknown```
Has everything been so thinned out that I have no way to check this now?

You'll need to use the alpine or buster images to have a shell and nc. See https://github.com/GoogleCloudPlatform/cloudsql-proxy/issues/523 for details.

@klaus993 The default images are based on distroless, which has no shell. There some other tages mentioned here: https://github.com/GoogleCloudPlatform/cloudsql-proxy#container-images
Additionally, if using k8s you can check the examples here for how to uses the built in port check:
https://github.com/GoogleCloudPlatform/cloudsql-proxy/tree/main/examples/k8s-health-check#running-cloud-sql-proxy-with-health-checks-in-kubernetes

Thank you for the clarification @kurtisvg @enocom ! I wasn't aware of this.

cloudsql-proxy 1.25.0+ now supports health checks via the -use_http_health_check flag: https://github.com/GoogleCloudPlatform/cloudsql-proxy/tree/main/examples/k8s-health-check#running-cloud-sql-proxy-with-health-checks-in-kubernetes


v1.1.0 Release Checklist

v1.1.0 Release Checklist

Adding support for OCP 4.13.6+

[ ] Decide upstream version of Intel Device Plugins

[ ] Review SELinux requirements and if any patches needed in container-selinux project.

[ ] Review NFD configuration and add node feature rules.

[ ] Review KMM configuration and if we can integrate KMM version 1.1

[ ] Update Documentation

[ ] Machine Configuration.

[ ] Build init container and plugin images

[ ] Build operator bundle and operator image

[ ] Release GPU driver version 2.0.0 for OpenShift here https://github.com/intel/intel-data-center-gpu-driver-for-openshift

[ ] Cut the release

Decide upstream version of Intel Device Plugins

my proposal is to go with v0.28 to catch up the development cycle

Build init container and plugin images

and drop SGX and GPU initcontainers

Build operator bundle and operator image

a must-have requirement is to move to "seamless upgrade" with v0.28

@mythi  quick question.. Since OCP version 4.13.10 currently has NFD version 4.13, and the majority of the changes in version 0.28.0 are designed for NFD 4.14, how can we ensure compatibility between version 0.28.0 and OCP 4.13.10? Should we continue to rely on initcontainers as a workaround due to the absence of NFD 4.14 in OCP 4.13.10?


Mark Dense.init(weight:bias:activation) as @differentiable.

Currently, weight is the only differentiability parameter.
Making bias a differentiability parameter requires Optional differentiation:
https://bugs.swift.org/browse/TF-1153.

What's this for? Depending on what it's for, it might be extremely confusing to users why they can't differentiate with respect to bias. Could you make it differentiable wrt bias by defining two separate initializers init(weight, bias, activation) and init(weight, activation)?

+1 on @marcrasi's suggestion.
Perhaps mentioning in a comment that bias is not differentiable yet would also be useful wrt maintaining documentation.

What's this for? Depending on what it's for, it might be extremely confusing to users why they can't differentiate with respect to bias. Could you make it differentiable wrt bias by defining two separate initializers init(weight, bias, activation) and init(weight, activation)?

Sorry for not providing context! @texasmichelle is working on https://github.com/texasmichelle/swift-models/tree/gpt2_example. She ran into a non-differentiability error because Dense.init is not @differentiable.
$ swift build
/Users/danielzheng/swift-models/Models/Text/GPT2/Model.swift:319:13: error: expression is not differentiable
            Dense(weight: embedding.weight.transposed(), bias: Tensor(0.0), activation: { $0 })) }()
            ^
/Users/danielzheng/swift-models/Models/Text/GPT2/Model.swift:319:13: note: cannot differentiate functions that have not been marked '@differentiable' and that are defined in other files
            Dense(weight: embedding.weight.transposed(), bias: Tensor(0.0), activation: { $0 })) }()
            ^

I think marking Dense.init as @differentiable makes sense. It cannot be differentiable wrt bias currently because bias has type Tensor<Scalar>?. TF-499 tracks conforming Optional to Differentiable.
All said, does this patch make sense to you?

@dan-zheng what if instead of making this change we considered adding a dense layer with non-optional bias to the GPT2 implementation?

I think a doc comment makes this good enough. Users will get a static differentiability error and they'll be a bit confused but the comment should clarify it and I don't think it's likely to cause bugs.


how to replaced human head with rat head

Thank you contribution for the mne, and it is a good tool to deal with EEG. And how to replaced human head with rat head?

I fear it's far from trivial.

Closing since no code changes necessary, feel free to post on Discord if you still want to pursue this, maybe someone has tried


[Event Request] Codeunit 7301 "Whse. Jnl.-Register Line"

To allow serial numbers with different quantity than -1, 0 or 1, I need a publisher in function "InsertWhseEntry":
Currently:

shall be like:

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Add English Docs for Kubernetes/TrueNAS Install method

Adding English docs to address https://github.com/misskey-dev/misskey/issues/6728.

🙏


Edited NTR and BS rules.

About the PR
NTR and BS rules are now slightly edited.
Why / Balance
Just look at the changes yourself, bro.
Technical details
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
None.


How to know if offboard.set_position_global completed sucessfully

As the return value of the API only denotes success of message sent to pixhawk, not the completion of the API.
There is no way to know if the drone has reached to the destination Lat/Long.
Should we need to monitor telemetry position callback to check if the drone is on right path and do an estimation based on speed and angle and predict lat long ?
Please guide
-Thanks

Are you sure that you want the offboard mode? Feels like you maybe want action.goto_location instead? Which doesn't confirm when the position is reached either, so you have to use the telemetry :innocent:.
But offboard is a more advanced mode of PX4.

Telemetry Position has to be constantly monitored in the callback to check if the drone is on track and reached destination.
Moreover there could be a slight delta in actual destination lat,long,alt.
Why isn't there a broadcast in Mavlink similar to MISSION_CURRENT for this case.
How long would the GCS wait before giving next goto_location, assuming that we are giving a defined mission but an on the fly fine grained lat long controlled by keyboard keys.

I guess that's a PX4 question :sweat_smile:. I don't know how difficult it would be for PX4 to have a concept of "goto"...

How long would the GCS wait before giving next goto_location, that drone has reached the destination.
How do you handle this in the code that uses MAVSDK?


pull request for e2e test at 01/28/2017 12:56:33

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


JavaScript Quiz

JavaScript Quiz
User Story
AS A coding boot camp student
I WANT to take a timed quiz on JavaScript fundamentals that stores high scores
SO THAT I can gauge my progress compared to my peers
Acceptance Criteria
GIVEN I am taking a code quiz
WHEN I click the start button
THEN a timer starts and I am presented with a question
WHEN I answer a question
THEN I am presented with another question
WHEN I answer a question incorrectly
THEN time is subtracted from the clock
WHEN all questions are answered or the timer reaches 0
THEN the game is over
WHEN the game is over
THEN I can save my initials and my score

I also faced a similar issue on my site but thankfully I hire a developer which resolve that's issue.


Can I Change The URL?

See the following code
var oc = require('orthanc-client');
var client = new oc({
    url: 'http://localhost:8042',
    auth: {
      username: 'foo',
      password: 'bar'
    }
});

Can i change the url value  http://localhost:8042 by live url of running orthanc server?

Sure, this is just an example. You can set the url value to your live running Orthanc server url.

I changed the URL it is working fine.
Thanks!


Option to create missing properties

What about an option to create a Property if doesn't exist?

That's funny you mentioned that.  I've been looking how to add Quantity to drawings.  I'm not in love with the idea, but have had several requests, including from my own guys.  Anyway, I realized it would be handy to add the Property if it didn't exist.  I was going to add it to the Property Find/Replace functionality.  Would that cover what you were suggesting?

I don't like the idea of adding quantities on the drawing as well; it is not where that information should be.
Yes the Find/Replace would become Find/Replace or Add

@farfilli This is done I think.  If you get a chance to try it out, let me know how it goes.
I added an option on the Configuration Tab, Miscellaneous Group, to enable/disable it.  I updated the readme also.  It's the last paragraph in this section: https://github.com/rmcanany/SolidEdgeHousekeeper#property-find-replace

Done


[Issue]: RuntimeError: HIP error: invalid argument  when running  any model

Problem Description
Error details:
When I try to run any model (including the example: https://rocm.blogs.amd.com/artificial-intelligence/pytorch-lightning/README.html) it returns following error:
RuntimeError: HIP error: invalid argument
HIP kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing AMD_SERIALIZE_KERNEL=3
Compile with TORCH_USE_HIP_DSA to enable device-side assertions.
Comments
We have invested in  ROCm AMD instead of NVIDIA CUDA but this is stopping us from using these GPUs in any meaningful way. Can you please let me know how to fix this issue please?
setup details:
$  echo "OS:" && cat /etc/os-release | grep -E "^(NAME=|VERSION=)";
OS:
NAME="Rocky Linux"
VERSION="8.6 (Green Obsidian)"
$   echo "CPU: " && cat /proc/cpuinfo | grep "model name" | sort --unique;
CPU:
model name      : AMD EPYC 7642 48-Core Processor
$   echo "GPU:" && /opt/rocm/bin/rocminfo | grep -E "^\s*(Name|Marketing Name)";
GPU:
Name:                    AMD EPYC 7642 48-Core Processor
Marketing Name:          AMD EPYC 7642 48-Core Processor
Name:                    gfx906
Marketing Name:          AMD Instinct MI50/MI60
Name:                    amdgcn-amd-amdhsa--gfx906:sramecc+:xnack-
Name:                    gfx906
Marketing Name:          AMD Instinct MI50/MI60
Name:                    amdgcn-amd-amdhsa--gfx906:sramecc+:xnack-
Name:                    gfx906
Marketing Name:          AMD Instinct MI50/MI60
Name:                    amdgcn-amd-amdhsa--gfx906:sramecc+:xnack-
Name:                    gfx906
Marketing Name:          AMD Instinct MI50/MI60
Name:                    amdgcn-amd-amdhsa--gfx906:sramecc+:xnack-
ROCm details:
$ rpm -qa | grep rocm
rocm-opencl-sdk-<IP_ADDRESS>700-63.el8.x86_64
rocm-hip-sdk-<IP_ADDRESS>700-63.el8.x86_64
rocm-core-<IP_ADDRESS>700-63.el8.x86_64
rocm-hip-runtime-<IP_ADDRESS>700-63.el8.x86_64
rocm-opencl-runtime-<IP_ADDRESS>700-63.el8.x86_64
rocm-cmake-<IP_ADDRESS>700-63.el8.x86_64
rocm-hip-runtime-devel-<IP_ADDRESS>700-63.el8.x86_64
rocm-hip-libraries-<IP_ADDRESS>700-63.el8.x86_64
rocm-llvm-<IP_ADDRESS>52.50700-63.el8.x86_64
rocm-ocl-icd-<IP_ADDRESS>700-63.el8.x86_64
rocm-device-libs-<IP_ADDRESS>700-63.el8.x86_64
rocm-llvm5.7.0-<IP_ADDRESS>52.50700-63.el8.x86_64
rocminfo-<IP_ADDRESS>700-63.el8.x86_64
rocm-opencl-<IP_ADDRESS>700-63.el8.x86_64
rocm-smi-lib-<IP_ADDRESS>700-63.el8.x86_64
rocminfo5.7.0-<IP_ADDRESS>700-63.el8.x86_64
rocm-language-runtime-<IP_ADDRESS>700-63.el8.x86_64
rocm-opencl-devel-<IP_ADDRESS>700-63.el8.x86_64
rocm-core5.7.0-<IP_ADDRESS>700-63.el8.x86_64
Operating System
Rocky Linux(VERSION="8.6 (Green Obsidian)")
CPU
model name      : AMD EPYC 7642 48-Core Processor
GPU
AMD Instinct MI50 (Radeon Instinct MI50 32GB)
ROCm Version
ROCm 5.7.0
ROCm Component
No response
Steps to Reproduce
just try to run your example code: https://rocm.blogs.amd.com/artificial-intelligence/pytorch-lightning/README.html
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response

Hi @atifkhanncl, could you please provide the output of the following commands:

python3 -c 'import torch' 2> /dev/null && echo 'Success' || echo 'Failure'
pip show torch
python3 -c 'import torch; print(torch.cuda.is_available())'
dkms status

Also, is it possible to try running the sample on ROCm 6.2.2 either by upgrading your host or using the rocm/pytorch docker image? This will provide a better baseline for your configuration as there have been many changes since ROCm 5.7.0.

Hi @harkgill-amd ,
upgrading ROCm has to be done by scheduling a time. If its necessary i shall do that, in the meanwhile following are the outputs of your queries
$ python3 -c 'import torch' 2> /dev/null && echo 'Success' || echo 'Failure'
Success
$ pip show torch
Name: torch
Version: 2.4.1+rocm6.1
Summary: Tensors and Dynamic neural networks in Python with strong GPU acceleration
Home-page: https://pytorch.org/
Author: PyTorch Team
Author-email<EMAIL_ADDRESS>License: BSD-3
Location: /home/user/miniconda3/envs/rocm_torch/lib/python3.10/site-packages
Requires: filelock, fsspec, jinja2, networkx, pytorch-triton-rocm, sympy, typing-extensions
Required-by: lightning, pytorch-lightning, torchaudio, torchmetrics, torchvision
$ python3 -c 'import torch; print(torch.cuda.is_available())'
True
$ dkms status
bash: dkms: command not found

I gave this a run on my end with an AMD Radeon PRO VII, which is also gfx906/GCN 5.1. Was able to run the sample on both a ROCm 5.7.0 baremetal install and within the rocm/pytorch 6.2 docker container. I'll confirm what the recommended ROCm version is for PyTorch+MI50, but in the meantime, a few other things that'll help:

Could you please provide the complete traceback? I see a few similar reports that were caused by a call to torch.cuda.cudart().cudaMemGetInfo(device).
Try the sample using the rocm/pytorch docker container. This worked with gfx906 and will help eliminate any installation issues besides the dkms.
sudo dnf install dkms prior to running dkms status. With this, we're trying to see if amdgpu-dkms was successfully installed and is the correct version. If the sample does not work within the docker container, the dkms would be the last component related to the host installation.

Any other details related to how ROCm was installed on your system would also be great.

I took up your advice and created a clean new environment with following setup
conda create --name rocm python=3.11 pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/rocm5.7 wget https://raw.githubusercontent.com/wiki/ROCm/pytorch/files/install_kdb_files_for_pytorch_wheels.sh export GFX_ARCH=gfx906 export ROCM_VERSION=5.7 ./install_kdb_files_for_pytorch_wheels.s pip install lightning transformers datasets torchmetrics
After this I tried to run the sample code:  https://rocm.blogs.amd.com/artificial-intelligence/pytorch-lightning/README.html.
It detects all 4 GPUs
print(f"number of GPUs: {torch.cuda.device_count()}") print([torch.cuda.get_device_name(i) for i in range(torch.cuda.device_count())]) output: number of GPUs: 4 ['AMD Instinct MI50/MI60', 'AMD Instinct MI50/MI60', 'AMD Instinct MI50/MI60', 'AMD Instinct MI50/MI60']
But when I move the model to gpus using model.to(device). It get stuck on this step with kernel status= busy. it does not get past this step.
I will try docker container next

Hi @harkgill-amd ,
I am trying docker image as follows

I have to use singularity instead of docker due to our organisation's security policy. But this should not make any difference
I pull a rocm pytorch image (tried rocm/pytorch:latest, pytorch:latest-release, pytorch:rocm6.2_ubuntu22.04_py3.10_pytorch_release_2.3.0
)
run it as follows  singularity exec --bind /path/to/mount:/mnt pytorch_rocm6.2_ubuntu20.04.sif /bin/bash
This starts a container on GPU node but when i check if it has pytorch by  python -c 'import torch' 2> /dev/null && echo 'Success' || echo 'Failure' it returns Failure. The docker images I pulled says they should have pytorch pre-installed. Can you see what is happening here?

I gave singularity a try with the rocm/pytorch image and was able to run both the MNIST and PyTorch Lightning samples on gfx908.

sudo dnf install dkms prior to running dkms status. With this, we're trying to see if amdgpu-dkms was successfully installed and is the correct version. If the sample does not work within the docker container, the dkms would be the last component related to the host installation.

Can you try the aforementioned steps to see if amdgpu-dkms is installed correctly? If possible, could you also set the environment variable export AMD_LOG_LEVEL=3 and reproduce the invalid device function error either in the conda environment or container? This should provide a more detailed look at what's causing the error to be thrown.


CARDS-2178: Survey Events CSV export has paths instead of labels for the assigned survey

start in prems mode
create a visit information form
using /bin/browser.html, locate the Survey Events form that was generated, and in it:
find the INCOMPLETE answer for "initial invitation sent on", add a new property of type Date named value, set any date for it
change the jcr:lastModified date of the form to yesterday
go to /system/console/configMgr
edit the last configuration entry, for UHN-Survey-Events
change the export path from /csv-export to ., save
go to /Subjects.csvExport?config=UHN-Survey-Events
on disk, check the CSV that was dumped in the directory where you started cards from, make sure it has labels instead of /Survey/ClinicMapping/2075099 paths.

tested


Error while converting enex files under Ubuntu

/usr/lib/ruby/2.3.0/rexml/parsers/baseparser.rb:362:in `pull_event': Declarations can only occur in the doctype declaration. (REXML::ParseException)
Line: 1
Position: 2815
Last 80 unconsumed characters:
<!DOCTYPE en-note SYSTEM "http://xml.evernote.com/pub/enml2.dtd"><en-note>
<li
        from /usr/lib/ruby/2.3.0/rexml/parsers/baseparser.rb:185:in `pull'
        from /usr/lib/ruby/2.3.0/rexml/parsers/treeparser.rb:23:in `parse'
        from /usr/lib/ruby/2.3.0/rexml/document.rb:288:in `build'
        from /usr/lib/ruby/2.3.0/rexml/document.rb:45:in `initialize'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/md_converter.rb:15:in `new'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/md_converter.rb:15:in `convert'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/note.rb:9:in `initialize'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/enex_converter.rb:30:in `new'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/enex_converter.rb:30:in `block in parse_plural_notes'
        from /usr/lib/ruby/2.3.0/rexml/parent.rb:40:in `each'
        from /usr/lib/ruby/2.3.0/rexml/parent.rb:40:in `each'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/enex_converter.rb:27:in `map'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/enex_converter.rb:27:in `parse_plural_notes'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/enex_converter.rb:9:in `convert'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/lib/ever2boost/cli.rb:26:in `convert'
        from /var/lib/gems/2.3.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
        from /var/lib/gems/2.3.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
        from /var/lib/gems/2.3.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
        from /var/lib/gems/2.3.0/gems/thor-0.20.0/lib/thor/base.rb:466:in `start'
        from /var/lib/gems/2.3.0/gems/ever2boost-0.1.5/exe/ever2boost:4:in `<top (required)>'
        from /usr/local/bin/ever2boost:23:in `load'
        from /usr/local/bin/ever2boost:23:in `'

same problem under macOS 10.13.2
ever2boost version: 0.1.5

same problem. are there any solutions?

I occured same problem, figured out adding some xml options to .enex file like this;
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE en-export SYSTEM "http://xml.evernote.com/pub/evernote-export3.dtd">
<en-export export-date="20180227T115050Z" application="Evernote" version="Evernote Mac 7.0.1 (456248)">
- <note><title>test</title><content><![CDATA[
+ <note><title>test</title><content><![CDATA[<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE en-note SYSTEM "http://xml.evernote.com/pub/enml2.dtd">
<en-note>
test
</en-note>
]]></content><created>20180227T115026Z</created><updated>20180227T115032Z</updated><note-attributes><author>narukami894</author><source>desktop.mac</source><reminder-order>0</reminder-order></note-attributes></note>
</en-export>

Deleting every instance of <!DOCTYPE en-note SYSTEM "http://xml.evernote.com/pub/enml2.dtd"> in the Evernote export will allow the script to run without error.
I exported a notebook containing 52 notes. I had to delete 52 doctypes embedded in CDATA as a result.
Even then, the resulting output was less than ideal. Every note has <?xml version="1.0" encoding="UTF-8" standalone="no"?> still embedded in it. The Evernote formatting was also completely lost.
Overall I think there's a lot of work to be done here to make this migration path viable.


Multiple EXC_BAD_ACCESS Crashes

Goals
Have my app run normally without crashes.
Expected Results
Same as "Goals" (above).
Actual Results
I'm seeing EXC_BAD_ACCESS in at least 2 different places. Please see:-

This might be related to #6556, but since that has been closed for a while, I decided to open a new issue for this.
Steps for others to Reproduce
So far, I have been unable to reproduce this in a sample project, but, here are a few things I can tell:-

Crash occurs randomly during a mass import when several write transactions are committed in quick succession on a single serial operation queue.
This happens on brand new installation (i.e. not upgrading from old file format, also, not following compaction).
My realm is stored in shared app group container (if that matters).
So far, I have been unable to reproduce this on the Simulator, but it occurs fairly frequently when running on an actual device (iPad 6th generation).
Since one of the crashes happens in do_encryption_read_barrier, I think it's also worth mentioning that my Realm is not encrypted.
~I have noticed that I can get rid of this crash if is slow down my writes (since my writes are committed on a serial background queue using NSOperation subclasses, adding [NSThread sleepForTimeInterval:1.0]; after [realm commitWriteTransaction]; in my NSOperation subclass is enough, but this is obviously not ideal).~ I eventually hit this crash irrespective on this change.
One way that I have found to get rid of these crashes is to not use realm notifications of any kind, or use KVO on realm objects. (Which is also not ideal).
A pattern I have noticed: This crash manifests itself after I have crashed once with a "mmap() failed: Cannot allocate memory size: XXXXXXXX offset: 0" exception during a mass import upon a fresh install, after which there are only EXC_BAD_ACCESS crashes no "mmap() failed" exceptions. I must say though: the exact same code had absolutely no "mmap() failed" exceptions or EXC_BAD_ACCESS crashes when used with realm-cocoa version 4.3.2.

Code Sample

None right now.
Version of Realm and Tooling

Realm framework version: 5.3.5
Realm Object Server version: N/A
Xcode version: 12 Beta 6
iOS/OSX version: iOS 14 Beta 6
Dependency manager + version: SPM (or Dynamic Framework built from source)

Hi @kunalsood ,
Thanks for the detail in your issue template! Would you be able to share what your Realm models look like and what size mass import your are doing?
Thanks,
Lee

Would you be able to share what your Realm models look like

Sure thing (It's an ObjC Project, so sharing what my headers look like) :-
@interface Feed : RLMObject

@property NSString *uniqueIdentifier; //Primary Key Property
@property NSString *title;
@property NSString *url;
@property NSString *displayTitle;
@property NSString *siteUrl;
@property NSString *summary;

@property NSInteger alphabeticalSortingDisplayIndex;

@property (readonly) RLMLinkingObjects *folders;
@property (readonly) RLMLinkingObjects *articles;

@end

@interface Article : RLMObject

@property NSString *uniqueIdentifier; //Primary Key Property
@property NSString *syncServiceIdentifier;
@property NSString *title;
@property NSString *link;
@property NSString *image;
@property NSString *excerpt;
@property NSString *author;

@property (readonly) NSString *summary;
@property (readonly) NSString *content;

@property double date;

@property BOOL isStarred;
@property BOOL isUnread;

@property Feed *feed;

@interface Folder : RLMObject

@property NSString *uniqueIdentifier; //Primary Key Property
@property NSString *displayName;

@property NSInteger alphabeticalSortingDisplayIndex;

@property RLMArray<Feed> *feeds;

@end

@interface Articles : RLMObject

//There should only ever be one object of this kind in the database

@property NSString *uniqueIdentifier; //Primary Key Property

@property RLMArray<Article> *oldestFirst;
@property RLMArray<Article> *newestFirst;

@end

This should probably be self-explanatory in telling what properties are stored in realm & what aren't, and which ones are relationships & which ones are inverse-relationships. Please let me know if you'd also like to see my implementation (i.e. what is in my '.m' files) of these.

what size mass import your are doing?

I'm importing no more than 15-20 Folder objects, 30-40 Feed objects, 6000-50000 Article objects, and only 1 Articles object. The order in which my mass import goes is as follows:-
Step 1: Create a unique Articles object is it doesn't already exist.
Step 2: Create all Feed objects in a single write transaction.
Step 3: Create all Folder objects, and establish relationships with appropriate Feed objects in a single write transaction.
Step 4: Create Article objects in batches of 100, establishing relationships with appropriate Feed objects as I go though them. So, for 6000 Articleobjects, I would end of committing 60 write transactions.
With Realm 5.3.5, I'm not able to get to the end of this import without crashing (4 out of 5 times), even on my smallest test case of 6000 Article objects.

This could be explained by a bug where we run notifications after the relevant realm version has been reclaimed and is no longer accessible.

This could be explained by a bug where we run notifications after the relevant realm version has been reclaimed and is no longer accessible.

That would make sense assuming the way this is done in core has changed.

UPDATE: In my (completely anecdotal/unsubstantiated) testing with Realm Cocoa 5.4.0, I have been unable to re-produce this crash. I will post another update in the next few days.

UPDATE: Still hitting this crash on 5.4.0

UPDATE: Still hitting this crash on 5.4.7, also, hitting this crash even if I'm not using Realm's notifications, or KVO (this might have been the case al along, just today is the first time I've hit this crash when not using notifications or KVO).

It may also be worth noting that all these crashes happen on the main thread. I do not write to Realm from the main thread ever. So, this probably has to do with some kind of corruption happening in the database when writing to it from an NSOperationQueue, which causes these crashes when trying to read from the realm after said writes. (Of course, I'm just speculating this).

@kunalsood Thx for info.

Can you provide a stack backtrace of a crash for the case where you do not use KVO or notifications at all? (if it's different from the one at the top of this issue), it might help us.

You wrote at the top of the issue:

A pattern I have noticed: This crash manifests itself after I have crashed once with a "mmap() failed: Cannot allocate memory size: XXXXXXXX offset: 0" exception during a mass import upon a fresh install, after which there are only EXC_BAD_ACCESS crashes no "mmap() failed" exceptions. I must say though: the exact same code had absolutely no "mmap() failed" exceptions or EXC_BAD_ACCESS crashes when used with realm-cocoa version 4.3.2.

Is this still correct?
Also, I need to be sure I interpret this correctly: you are saying that first the app runs fine (importing lots of data) until it crashes with mmap failed. Then subsequent runs of the app fails immediately (or fast) with EXC_BAD_ACCESS ?  At the point of the mmap failed, what's the size of the realm file? Is it possible to get a stack backtrace at this point (as opposed to at the EXC_BAD_ACCESS) ?

@kunalsood Thx for info.

Can you provide a stack backtrace of a crash for the case where you do not use KVO or notifications at all? (if it's different from the one at the top of this issue), it might help us.

It crashed at realm::util::EncryptedFileMapping::read_barrier, I do not have a stack trace handy right now, but, I'll try and get one to you over the new few days.

You wrote at the top of the issue:

"A pattern I have noticed: This crash manifests itself after I have crashed once with a "mmap() failed: Cannot allocate memory size: XXXXXXXX offset: 0" exception during a mass import upon a fresh install, after which there are only EXC_BAD_ACCESS crashes no "mmap() failed" exceptions. I must say though: the exact same code had absolutely no "mmap() failed" exceptions or EXC_BAD_ACCESS crashes when used with realm-cocoa version 4.3.2."
Is this still correct?

Yes, this is still correct.

Also, I need to be sure I interpret this correctly: you are saying that first the app runs fine (importing lots of data) until it crashes with mmap failed. Then subsequent runs of the app fails immediately (or fast) with EXC_BAD_ACCESS ? At the point of the mmap failed, what's the size of the realm file? Is it possible to get a stack backtrace at this point (as opposed to at the EXC_BAD_ACCESS) ?

The import never completes. At first attempted import, it crashes with mmap failed at some random point/line-of-my-code during the import (it is at a different point/line-of-my-code every time). When I re-launch the app, and attempt the import again, it eventually crashes again with EXC_BAD_ACCESS (again, at different point/line-of-my-code every time).
Does that clarify it? Please let me know if it doesn't.

Do you at any point have multiple processes (not just threads) accessing the realm file?

Yes, I do have iOS 14 Widgets reading (never writing) from the realm file at certain points (I call appropriate WidgetCenter APIs to request the system to reload the widget data, but, when the system actually attempts a reload is not something I can control, as the system throttles reload attempts to conserve battery and other resources etc.)

Ok, last thing first:
"Yes, I do have iOS 14 Widgets reading (never writing) from the realm file at certain points (I call appropriate WidgetCenter APIs to request the system to reload the widget data, but, when the system actually attempts a reload is not something I can control, as the system throttles reload attempts to conserve battery and other resources etc.)"
Does such a widget have the realm file open... if so, how often does it refresh its view of the data? Or does it work by only opening the realm when it needs access, reading data, then closing it again immediately? What I'm after is: could a widget lock on to a version of realm data for an extended period of time, while the app is rapidly committing data as it receives it from the server?

Also, checking my understanding: We have at least 3 active entities working in parallel here:

A widget. It only reads from the database.
The main thread. It also only reads from the database.
A background thread. It writes heavily.
And it is always the main thread that crashes.

Does such a widget have the realm file open... if so, how often does it refresh its view of the data? Or does it work by only opening the realm when it needs access, reading data, then closing it again immediately? What I'm after is: could a widget lock on to a version of realm data for an extended period of time, while the app is rapidly committing data as it receives it from the server?

From my understand of how widgets work, no, widgets should not lock on to a version of the data in realm for an extended period of time at all. It only reads from the database when it needs to create an updated view, and does not hold on to any realm, realm objects, realm collection objects, or notification tokens. I just read from the realm, convert the data I need from realm to native objects, and let the realm go. This also does not happen very frequently during the import either. At most 2-3 times.

Also, checking my understanding: We have at least 3 active entities working in parallel here:

A widget. It only reads from the database.
The main thread. It also only reads from the database.
A background thread. It writes heavily.

And it is always the main thread that crashes. The widget never crashes. Are there other members at this party?

Yes, that is all correct.

It'll take me some time to get you this info, as I do not use Realm 5.x in production (due to this exact issue), but, I'll get you this info APAP. Apologies about the delay.

Here we go:
file extension: realm
file byte size count: 335544320
formatted file size: 335.5 MB

file extension: lock
file byte size count: 1184
formatted file size: 1 KB

file extension: note
file byte size count: 0
formatted file size: Zero KB

This is using Realm Cocoa version 5.4.8
This particular crash was hit when about 45k into an import of around 55k Article objects.
Just as an aside: I do not appear to be hitting this crash as often as I used to. What I mean when I say that is: I was able to successfully complete my import a few times before I hit this crash. I only hit this crash when using KVO & Realm Notifications.

@kunalsood can we confirm that this is still happening on the latest 10.x version of Realm?

I'm afraid I won't have a chance to test this throughly enough before January. So, please feel free to close this issue if you must, and I'll open a new issue if I see this when I get around to testing it.

That's fair, we appreciate the heads up– we'll close this for now and do reopen it if it persists on the latest versions of Realm.

update here: Ive noticed the same issue if I'm integrating realm via SPM. Using carthage is just fine.

update here: Ive noticed the same issue if I'm integrating realm via SPM. Using carthage is just fine.


Group Normalization

Hi,
Is it possible to add support for Group Normalization (normalization over groups instead of batches)?
https://arxiv.org/abs/1803.08494
torch.nn.GroupNorm

This is not a trivial task, unfortunately. It has been on our radar for a while, but we can't promise anything for now.


virtcontainers: add support for CPU affinity at pod granularity

Original logic would not allow a container to be updated if it wasn't
in the running state. A container should be able to be updated if it
is either running or is created and in ready state.
This better matches the logic in CRI-O today, and allows for the use
case where a created container is updated by due to K8S CPU manager
adjusting the CPU affinity of a created but not yet running container.
Fixes #878
Signed-off-by: Eric Ernst<EMAIL_ADDRESS>

@egernst please address the comment

mea culpa -- not ready for review yet.  thanks for taking a look Sebastien.


tests(examples/things.py): tests for first things.py example

tests for example code
reconfigure flake8 to make this possible

Testing for #1423

This PR is based off and will require https://github.com/falconry/falcon/pull/1526 to be practically merged.

@Ciemaar flake8 was complaining about your docstring-style string, not sure what it was expecting, so I went on to convert it to strings inside parenthesis.


报错：run.sh: line 57: tools/parse_options.sh: Not a directory

cd /examples/aishell/s0
bash run.sh --stage -1
run.sh: line 57: tools/parse_options.sh: Not a directory

check the soft link and your environment.

@smil4ever I met the same problem with you, did you solved it ?

@robin1001 Do you confirm that we need to create any soft link under examples/aishell/s0?

I also met the same problem with you, did you solved it now?

@smil4ever I met the same problem with you, did you solved it ?

I also met the same problem with you, did you solved it now?

@smil4ever I met the same problem with you, did you solved it ?

@smil4ever I also met the same problem with you, did you solved it now?

@smil4ever I met the same problem with you, did you solved it ?

@seekFire I also met the same problem with you, did you solved it now?


ImSpinner and Global Alpha Value

Hello, I am enjoying ImSpinner so far but there is one slight problem.
For some reason, all ImSpinners seem to ignore the global alpha value.
I am working on a fade transition effect. When I use my fade functions,
-which manipulate the global alpha value- everything is affected by
the alpha change except for ImSpinners. I would really appreciate some
input on this. Thanks in advance and amazing job with ImSpinner.

Thanks, will fix it

Thanks for the quick fix.


Unable to resolve path for relative .jsx files

I am importing .jsx files from other .jsx files.  The imports work fine if I specify an absolute path, but fail with import/no-unresolved when I use relative paths.
My folder structure:
/imports
ui
pages
vocabulary
test
TestContainer.jsx
TestView.jsx
in TestContainer.jsx, this statement works fine:
import { TestView } from '/imports/ui/pages/vocabulary/test/TestView.jsx';
... and both of these get "Error: Unable to resolve path to module './TestView.jsx'. (import/no-unresolved)"
import { TestView } from './TestView.jsx';
import { TestView } from 'TestView.jsx';
My .eslintrc:
{
"plugins": [
"meteor",
"react"
],
"extends": [
"airbnb",
"plugin:meteor/recommended"
],
"parserOptions": {
"ecmaVersion": 6,
"sourceType": "module",
"ecmaFeatures": {
"jsx": true,
"impliedstrict" : true
}
},
"rules": {
"semi": 2
},
"env": {
"es6": true,
"browser": true,
"node": true,
"meteor": true
},
"settings": {
"react": {
"pragma": "React",  // Pragma to use, default to "React"
"version": "15.0" // React version, default to the latest React stable release
},
"import/resolver": { "meteor": {"extensions": [".js", ".jsx"]} },
},
"scripts": {
"lint": "eslint .",
"pretest": "npm run lint --silent"
},
"eslintConfig": {
"plugins": [
"meteor"
]
},
"indent": [2, 2]
}

The folder structure that I carefully indented above got messed up. Here's another way to describe it.  The two files are /imports/ui/pages/vocabulary/test/{TestContainer, TestView}.jsx.  I want to import these with relative rather than absolute references.

I just noticed that I'm having the same problem with .js files, using "import { xxx } from './xxx.js';
I created these files a few days ago, and did not see this error when I last edited the files.  But when I opened them up today, I see these errors.

It sounds like an issue with the meteor resolver. What happens if you switch to the node resolver?

Yes, I agree. I intended to open this against the meteor resolver.  Will try again on that.


am not able to validate the json file using packer

This is my json file and i have started my powershell with admin permissions  and just am trying to validate the json but am getting following error:
command :packer validate .\nginx.json
Error : Failed to initialize build 'amazon-ebs': error initializing builder 'amazon-ebs': Unrecognized remote plugin message: Error starting plugin server: Couldn't bind plugin TCP listener
{
"builders": [
{
"type": "amazon-ebs",
"access_key": "access-id",
"secret_key": "pwd",
"region": "us-east-1",
"source_ami": "ami-a4dc46db",
"instance_type": "t2.micro",
"ssh_username": "ubuntu",
"ami_name": "packer-nginx"
}
]
    }
]

}

The script isn't right, u can use Visual Studio code for writing json script.
Else use online json validator to see ur script is error free.

Yes,i m using visual studio code only and the same code is working in my friends system  .

Did you install aws cli in your machine ?

Json is invalid, Please share complete script which you are use.

once again ,i started the same procedure from beginning and got the same issue showing the below steps

issue: unable to validate the json file
step 1:
nginx.json template
{
"builders":[
{
            "type": "amazon-ebs",
            "access_key": "access-id",
            "secret_key": "secret-id",
            "region": "us-east-1",
            "source_ami": "ami-a4dc46db",
            "instance_type": "t2.micro",
            "ssh_username": "ubuntu",
            "ami_name": "packer-nginx"
          }

]

}
step 2:

PS C:\Windows\system32> packer --version
1.2.4
PS C:\Windows\system32> cd E:\packerzone\may2018\nginx
PS E:\packerzone\may2018\nginx> packer --help
Usage: packer [--version] [--help]  []
Available commands are:
build       build image(s) from template
fix         fixes templates from old versions of packer
inspect     see components of a template
push        push a template and supporting files to a Packer build service
validate    check that a template is valid
version     Prints the Packer version
PS E:\packerzone\may2018\nginx> packer validate .\nginx.json
Failed to initialize build 'amazon-ebs': error initializing builder 'amazon-ebs': Unrecognized remote plugin message: Error starting plugin server: Couldn't bind plugin TCP listener
PS E:\packerzone\may2018\nginx>


Documentation and implementation differ

The part about Routerunner's Middlewares differs from the actual implementation.
In the documentation the process method's signature is stated like this:
 public function process(string $controller)
But it actually is like this:
 public function process(ServerRequestInterface $request, Call $call)
https://github.com/timtegeler/routerunner/blob/12552e13e3a141a653407de6011afa69439700b5/src/Middleware/MiddlewareInterface.php#L20

Thanks :)


msm refactor design

In pyemma there is no separation between model and estimator in the msm part.
In order to create such a separation and make code more readable / maintainable, we have to decide where exactly to cut.
In general there is statistics about the input dtrajs as well as the count matrix. This can, e.g., be captured in a separate TransitionCountEstimator - TransitionCountModel pair.
A MSM in principle does not need to be estimated from data but can be constructed from a transition matrix P. In that case there would be a MarkovStateModel instance.
If however the MSM is estimated from data, a TransitionCountModel is intermediately needed and the attributes are probably still interesting for further evaluation.
The question is how to most conveniently combine these two models into one.

One could make use of multiple inheritance, i.e., class EstimatedMarkovStateModel(MarkovStateModel, TransitionCountModel).
Composition: The EstimatedMarkovStateModel is a glorified tuple of the MarkovStateModel and TransitionCountModel
The MarkovStateModel has a (default None) reference to a TransitionCountModel
General restructure: The base model is defaulted to None and only exists within an estimator once it has been fitted.

on a related note: i propose to change dt_dtraj to something more descriptive like discrete_time_unit

#9 has implemented 3.


feat: implement import wait and timeouts

Signed-off-by: squat<EMAIL_ADDRESS>

Ran into this: https://github.com/hashicorp/terraform-plugin-framework-timeouts/issues/46


Laravel Voyager: Missing required parameters for [Route: voyager.user-roles.edit]

Version information

Laravel: v5.7
Voyager: v1.1.10
PHP: 7.2
Database: MySql 5.7

Description

Missing required parameters for [Route: voyager.user-roles.edit...
Steps To Reproduce
Steps to reproduce the behavior:

Go to Tools
Click on Database
Scroll down to  'user_roles' and click  Add BREAD to this table. Seer error 'SQLSTATE[42S22]: Column not found: 1054 Unknown column 'created_at' in 'order clause' (SQL: select * from user_roles order by created_at desc)'.
Then add Timestamps to table user_roles.
Click  Browse BREAD  on 'user_roles'
See error 'Missing required parameters for [Route: voyager.user-roles.edit] [URI: admin/user-roles/{user_role}/edit].'

Screenshots

Additional context
Thanks you every body!

Thats both described here and here

Closing

Same error on fresh installation withou dummy data. Missing required parameters for [Route: voyager.bread.delete] [URI: admin/bread/{id}]. (View: ~\tcg\voyager\resources\views\tools\database\index.blade.php)

Same error on fresh installation withou dummy data. Missing required parameters for [Route: voyager.bread.delete] [URI: admin/bread/{id}]. (View: ~\tcg\voyager\resources\views\tools\database\index.blade.php)

just change file vendor\tcg\voyager\resources\views\tools\database\index.blade.php in line 96
from
{{ route('voyager.bread.delete', ['id' => null]) }}
to
{{ route('voyager.bread.delete', ['id' => '']) }}
hope this helps

Let's not resume closed issues, there is already an open issue with linked PR.
@alwan-h that won't work with next Laravel release.
This is the proper fix
https://github.com/the-control-group/voyager/pull/4587/files


Backport: Cluster restore from S3 failed and recovered after around 90mins

Backport https://github.com/rancher/rancher/issues/21263

Tested with July 1st build from branch v2.2-head.
K8s version : v1.14.3
Steps:
Create a custom cluster using S3 configuration with nodes as below:
N1 - control, worker
N2, N3, N4 - 3 etcds
Create a few workloads
Power off etcd nodes N2, N3, N4
After powering off the etcd nodes, the cluster changed to "Unavailable" state as expected.
Cluster was accessible through UI. The etcd nodes were deleted and new etcd nodes were added. Restore was performed from S3. Restore was successful. Cluster was active.  Snapshot restore was performed several times and it was successful.
Error logs  below were not found after the fix as expected.
failure to delete a non-existing pod `2019/07/01 18:22:30 [ERROR] ClusterController c-abcd [cluster-provisioner-controller] failed with : [pods "nginx-ingress-controller-2tgtq" not found]`

Snapshot restore on local cluster was also tested. No issues were found


Fix flaky RemoteFSTranslogTests testMetadataFileDeletion test #9605

Description
This closes #9605. The flakiness in this test is on account of translog.trimUnreferencedReaders() being no-op when called due to previous deletion still ongoing and holding the permits. The current run of translog.trimUnreferencedReaders() on checking for permits sees that the required permits are not available and skips the deletion. To elaborate more on generation deletion, the approach is to acquire the permits, trigger async deletion and post successful deletion, release the permits. With this PR, I am making sure that after trimUnreferencedReaders(), we check that the required permits are available before calling the same method back again.
Related Issues
Resolves #9605

Check List

[ ] ~New functionality includes testing.~

[x] All tests pass

[ ] ~New functionality has been documented.~

[ ] ~New functionality has javadoc added~

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[ ] ~Commit changes are listed out in CHANGELOG.md file (See: Changelog)~
[ ] ~Public documentation issue/PR created~

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

❕ Gradle check result for a63fa6a: UNSTABLE

TEST FAILURES:

      1 org.opensearch.remotestore.RemoteIndexPrimaryRelocationIT.testPrimaryRelocationWhileIndexing

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

Flaky test - https://github.com/opensearch-project/OpenSearch/issues/9191

How many times did we run the test to see if the flakiness still persists?

Had run it for 1K+ iterations on local. Running the entire class test suite for couple of hours more.

2K iterations have run without any failures.

3K iterations ran without any failures.


Update Handling of Loading Proxies from the Environment

Fixes #21946
This PR updates how ProxyOptions loads proxies from the environment.
Previously, it was mistaken that java.net.useSystemProxies was required to be true to use JVM proxy configurations. Instead the property is used to determine whether system proxies, such as HTTPS_PROXY and HTTP_PROXY, are allowed to be used during proxy lookup.
Now, when attempting to load proxies from the environment java.net.useSystemProxies is checked before attempting to load HTTPS_PROXY and HTTP_PROXY based proxies. The order of loading proxies has remained unchanged where system proxies will be preferred over JVM proxies.

Will the example code at https://docs.microsoft.com/en-us/azure/developer/java/sdk/proxying#use-a-configuration-proxy need updating?

Will the example code at https://docs.microsoft.com/en-us/azure/developer/java/sdk/proxying#use-a-configuration-proxy need updating?

Yes! Thank you so much for catching this 😄


Move back the sheet_cleanup code to the beoutbreakprepared/nCoV2019 repo

I'm not sure if it's worth keeping this repository if what it's solely doing is building stuff for that other repo.
The others are building their projects in another repo under open-covid-data so I propose that we migrate the code back to beoutbreakprepared/nCoV2019, sounds good?

sure sounds good, I've moved things back there!

Please move the github action workflow as well so that tests are run on pull requests, that's definitely a nice thing to have.

https://github.com/open-covid-data/mvp-notes-and-ideas/tree/master/.github/workflows

The SOP link in the spreadsheets also need to be moved to the repo's link.


feat: kakarot_getStarknetTransactionHash

Resolves: #1238
Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Testing

What is the new behavior?
This PR implements the kakarot_getStarknetTransactionHash method that converts an Ethereum B256 transaction hash to the corresponding Starknet transaction hash.
Does this introduce a breaking change?

[ ] Yes
[x] No

I just left some comments. But in general I think that we should handle errors in the kakarot_get_starknet_transaction_hash function rather than systematically unwrap which could:

Cause panic (which we want to avoid).
Prevent us from having access to clean logs allowing us to uncover potential bugs by analyzing errors.


Vulnerability roundup 92: jenkins-2.235.5: 7 advisories [5.4]

search, files

[ ] CVE-2020-2220 CVSSv3=5.4 (nixos-unstable)
[ ] CVE-2020-2221 CVSSv3=5.4 (nixos-unstable)
[ ] CVE-2020-2222 CVSSv3=5.4 (nixos-unstable)
[ ] CVE-2020-2223 CVSSv3=5.4 (nixos-unstable)
[ ] CVE-2020-2229 CVSSv3=5.4 (nixos-unstable)
[ ] CVE-2020-2230 CVSSv3=5.4 (nixos-unstable)
[ ] CVE-2020-2231 CVSSv3=5.4 (nixos-unstable)

Scanned versions: nixos-unstable: c59ea8b8a0e.
Cc @coreyoconnor
Cc @earldouglas
Cc @fpletz

20.03 is frozen and EOL
20.09 is at 2.249.2
master is at 2.249.3
Closing.


Add db reingest range command

Simple command to support ledger range reingestion. Can be used to distribute reingestion of ledgers across multiple machines:
horizon1> horizon db reingest range 1 10000
horizon2> horizon db reingest range 10001 20000
horizon3> horizon db reingest range 20001 30000
...

Thanks, added new issues: https://github.com/stellar/go/issues/917 https://github.com/stellar/go/issues/918.


[FEATURE]: Update version of generated repositories when tagging

Is there an existing issue for this?

[X] I have searched the existing issues

New feature
In koinos-proto-cpp for example, we should update the VERSION in the project() call programmatically.
Anything else?
No response

The PR did not work. Reopening for next release.

Resolved by #246.

Worked! https://github.com/koinos/koinos-proto-cpp/commit/be14c4fcf429b2b69b17a983e5922f5ce4910a65


Include ACF settings sync into dev scripts commands

We currently pull in CFM settings changes when running npm run local or npm run refresh. Would it be advisable to include synch ACF settings with these scripts as well?
Gist for plugin to add WP CLI command for ACF sync: https://gist.github.com/hirasso/c48c04def92f839f6264349a1be773b3

Will add to Four Kitchens queue. Now that we aren't using WP-CFM, we should probably clean that out.

PR Added to include the WP-CLI command. The command needs to be run manually using wp-cli or terminus in pantheon environments.
 example usage wp-cli: wp tw acf-sync-field-groups
 example usage terminus: terminus wp the-world.{environemt} -- tw acf-sync-field-groups


"Region is missing"

Hello, I'm trying to implement the plugin in the company I work for. But after having configured everything, when trying to access the page where the codepipeline widget should appear, I get an error 500.

in the print you can see that he is trying to access the arn.
below the backend code and in the app-config
awsCOdeSuite.ts
import { createRouter } from "@aws/aws-codesuite-backend-plugin-for-backstage";
import { PluginEnvironment } from "../types";

export default async function createPlugin(env: PluginEnvironment) {
  return await createRouter({
    logger: env.logger,
    config: env.config,
  });
}

app-config.yaml
app:
  title: Portal do Desenvolvedor
  baseUrl: http://localhost:3000

aws:
  mainAccount:
    accessKeyId: xxxxxxxxxxxxxxxxxxxx
    secretAccessKey: xxxxxxxxxxxxxxxx
    region: 'us-east-2'

Can someone help me?

Hi @ericksposito. Sorry to see you're having problems with the plugin. I spent a little time trying to reproduce your issue but so far I'm not having any luck.
I see the ARN in the screenshot, can you please paste the entity annotation you used with the account ID removed?

hey. Thanks for the answer. this one
aws.amazon.com/aws-codepipeline: arn:aws:codepipeline:us-east-2:683720833731:portaldx-staging

@ericksposito were you ever able to resolve this issue?

@ericksposito @niallthomson I am running my backstage instance with docker hosted on ECS so I did not pass in any AWS profile information since the credentials are pulled from the IAM role.
I added a AWS_REGION=my-region environment variable which solved the above issue for me.
It seems like all calls with the region are pulled from the region in the ARN parsing so I am not sure why/were this would be required.

We have started a new project to better scale our efforts regarding Backstage plugins. The functionality in this repository is being migrated. If this issue is still relevant please create a new issue in this repository:
https://github.com/awslabs/backstage-plugins-for-aws


doc: code blocks looks weird in light mode

Code blocks in docs looks weird/unreadable in light mode. Looks okay in dark. Example - https://www.sea-ql.org/SeaORM/docs/relation/one-to-one/#defining-the-relation

oh it really is. I don't know how to fix it though

Also, even in dark mode, the contrast is too low on highlighted lines.

Ah right, may be we should override the highlight color in CSS.

Hey @ssiyad, thanks for the prompt! I just fixed the theme, https://github.com/SeaQL/seaql.github.io/commit/93501d5ce09de2c62ea07517cb7065b94cc59d6a. Please check again!

Fixed on https://github.com/SeaQL/seaql.github.io/commit/93501d5ce09de2c62ea07517cb7065b94cc59d6a

@billy1624 It looks so much better now. Thanks!

Many thanks!


Add uninstall parameter to Parallels Virtualization SDK

The most-possibly-ever-final fix here :( Sorry. Now, everything gets unpacked and done the way it is supposed to. Tested for a gillion times. And added an uninstall parameter.

A gillion times tested?! That's good enough for me! :muscle:

@phinze Ahah, yeh, I'm really sorry for that :disappointed: First time I have written the cask on the Windows machine, without testing, the second time I realized that the downloading link is broken, and only the third one (it's true that all good things come in threes :v: ) I performed everything that was needed. My laziness will lead to no good :sweat_smile: ...


branch.subscribe called with +non_branch_link under some circumstances

This has only been confirmed on Android so far with 2.0. To reproduce:

Build and run webview_example on an Android device or emulator.
Get a link to any of the content views using the Share button.
Ensure that the app is not running. (Kill it if necessary.)
Launch the app from the link you generated (e.g., mail it to yourself and then open it in the Mail app).
Background the app without killing the app.
Open the same link again without killing the app.
Background the app without killing the app.
Foreground the app without killing the app or opening a link.

The params returned in the subscribe method include a +non_branch_link that may or may not be a Branch link. This parameter is returned by the native Android SDK. However, the problem is not reproducible with the Android SDK directly. It's probably caused by some state in the RN codebase.
Output from logcat with webview_example: https://gist.github.com/jdee/cf8b1902e1b9d071dad8c48b44a6523e
This behavior is consistent when testing with react-native-branch 2.0
If you can reproduce this in any other situation, please comment and include:

Detailed steps to reproduce, preferably with one of the examples in this repo.
Test platform (iOS, Android or both).
Version of react-native-branch.
Version of native Branch SDK if using react-native-branch < 2.0.

FYI, got the same issue on Android, with react-native-branch 2.0.0-beta...
I cannot really give detailed step to reproduce, as ATM it seems that it always fails (i.e. every clicked branch link is considered by the sdk as a non-branch-link).

I have a similar issue when using the test key. If I have #ifdef DEBUG [RNBranch useTestInstance] in my AppDelegate.m uncommented, it would use my test key as it's supposed to, but I'll get "+non_branch_link" every time. Once I comment that out, the branch data comes thru successfully using the live key.
It would be nice to use the test key and have branch.subscribe register that the clicked link is in fact a branch link

@bporter2387 That sounds like an issue with the configuration of the test instance.
Some things to check:

Make sure that the test instance is properly configured in the Branch Dashboard.
If you are using an app.link subdomain, you need to add myapp.test-app.link and myapp-alternate.test-app.link to your associated domains entitlement (iOS) and manifest (Android).

This can also be automatically set up and validated using Fastlane and the branch plugin. See the examples in this repo, e.g. webview_example, for use with React Native.

Noticing this issue on Android. Noticed this issue when I tried to setup Android App Links. When I click the link it takes me to the app, but every time I put the app in the background and open the app up again, it will re-trigger branch.subscribe
react-native: 0.47.2
react: 16.0.0-alpha.12
react-native-branch: 2.0.0-beta.7

@jdee is there an update with this bug?

Apologies for the long delay. It took a while to find the smoking gun(s). I can reproduce this problem in other environments (native Android and iOS apps) without RN. It may be a server issue, though I'm not sure at the moment. Branch is working on it. The good news is, if it's a server issue, it should just go away with no action on your part.
The subscribe callback is invoked at times other than link opens. Often you'll get { "+clicked_branch_link": false, "+is_first_session": false }. Generally this means the SDK checked for a deferred deep link and found nothing. It's necessary to check the +clicked_branch_link parameter anyway. If you're only using Branch links, then that's all you really need to do. If you're also using non-Branch links with the Branch SDK, then you also need to check the +non_branch_link field, and this will be broken for you right now.
Regarding where to call the subscribe method, the important thing is that it needs to be called at app launch and remain in place throughout the lifetime of the app. We've been recommending componentDidMount in the root component for this, but perhaps there is a better place.
See the examples in this repo, particularly App.js in the webview_example for recommended usage of branch.subscribe. Also see the new webview_tutorial app, which walks you step by step through adding Branch to a simple app.
Finally, in the future if you have problems like this, you'll undoubtedly get better results by opening a support ticket at https://support.branch.io or by emailing<EMAIL_ADDRESS>Branch has an excellent support team, and I assure you they'll get the job done for you. (Unlike me, it seems.)

@jdee thank you for your work! Also will definitely go with the support team next time.

This is addressed by a patch in the Android SDK: https://github.com/BranchMetrics/android-branch-deep-linking/pull/484. It fixes the problem in testing with webview_example. When the next release of Android is available, a patch will be released here with that update. Thanks for your patience.

The fix for this is in the master branch with Android 2.12.2. I'll release this as 2.1.1 after I have a chance to test it, probably tomorrow morning.

Fixed in 2.1.1, which was released to NPM.


Skip db:seed if already done

created_at and updated_at are part of the JSON responses, so to make sure it will be a fair comparison, I think we should use the same timestamps across different Ruby commands too.
If you agree with that idea, I'll backport this to the original railsbench as well.

That looks good. Given how slow the inserts are, I'm all for this :-)
I had thought about just checking that the data existed, but of course that's not correct. This is a better approach.


triggering another menu to open should close the previously opened menu

Steps to reproduce:

Have two or more menus showing
Open one of the menus
Click something else on the page

Menu should close

Open one of the menus
Click the trigger of the second menu

previous menu should close, but stays open

See lib/components/Menu.js. Code is only checking that the newly focused item has a Menu__ className. In this case the second menu also has the appropriate className. As such the first menu, although it looses focus, stays open.

So I was comparing the various Menu components in Github vs what's in the NPM module and it looks like they're not consistent with each other. I wanted to ask if the NPM module is up to date or which I should use. I'm mainly interested in the changes for closing the open menu - https://github.com/instructure-react/react-menu/pull/7
So far all the changes in that PR are not present in the NPM module I just re-installed.

i'll cut a new release once i get the build sorted it. it went a little wonky in a PR

Cool beans. Thanks and yeah let me know when that's up!

@knomedia Oh do you have a time estimate on when you think everything will be ready to update on the NPM side? We wanted it for our production release coming up pretty soon

fixed by by https://github.com/instructure-react/react-menu/pull/7

@tedlin182 0.0.6 with ^^ fix has been pushed to npm

Hey @knomedia - I tried updating/removing and re-installing/etc. and still am only getting the 0.0.5 version from NPM. Is there something I'm missing or is there possibly some issue still?

@tedlin182 v0.0.6 is up on npm. I get the new version on a fresh npm init followed by npm install --save react-menu
have you bumped the version in your package.json file?

@knomedia
Hey, yeah i bumped up the version and thought maybe just removing the module and re-doing npm install --save react-menu would have worked, but it didn't. I even just removed it from my package.json file completely and doing a npm install --save react-menu would work, but it didn't.
Could be something with my local, but I'll try what you stated above and see if that works. If I run into the issue when we push the change to staging, I'll let you know.

@knomedia
I actually just tried removing all of my node modules and running npm install and got this error:
No compatible version found<EMAIL_ADDRESS>npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.5"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

@tedlin182 have you considered the nuclear option? rm -rf node_modules && npm cache clean && npm install

Still getting that error. I may check with the other devs to see if they're running into this issue, but it's quite odd it's not working.
npm ERR! notarget No compatible version found<EMAIL_ADDRESS><0.0.7'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.5"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

@knomedia
So there may have been some fix to React Menu that we did locally and pushed to our private NPM which may be causing the issue. Going to see if that's the cause though.

@knomedia
I saw that you have the /** @jsx React.DOM */ pragma still, but looks like that's been deprecated in the newer React versions 0.12:
https://github.com/callemall/material-ui/issues/364
https://facebook.github.io/react/blog/2014/10/16/react-v0.12-rc1.html
It was breaking on my local when starting up, but changing your file extensions to .jsx seemed to work.
Just a heads up


directly remove and install Widevine in Kodi CDM dir

This pull request includes:

fix for removing Widevine on Windows
move remove_widevine to Helper class
always use Kodi CDM dir to install Widevine CDM to, phase out use of inputstreamhelper addon data CDM dir
determine widevine path based on static filename (just like InputStream Adaptive does)
wait until InputStream Adaptive installation is complete (xmbc.executebuiltin wait parameter)
use notification dialogs when installing or removing Widevine CDM

This is how it should have been. Thanks!


Bump deCONZ to 2.05.79

Hi @kropp,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Please link up the release notes in the PR descriptions.
At this point, I don't see any releases or release announcements. This means there is also no indicator on the stability on the release version you are bumping.

The changelog is out: https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/V2_05_79.

@domoritz thanks, updated the description
@frenck sorry, I was too excited about OSRAM Mini Switch integration added to the latest version. Will wait until Release Notes are published next time.