text:
Selenium and dino game

Hi, While trying to open 'chrome://dino'  url in selenium, it is throwing the following error:
WebDriverException                        Traceback (most recent call last)
 in
----> 1 driver.get("chrome://dino/")
F:\Anaconda\envs\opencv\lib\site-packages\selenium\webdriver\remote\webdriver.py in get(self, url)
331         Loads a web page in the current browser session.
332         """
--> 333         self.execute(Command.GET, {'url': url})
334
335     @property
F:\Anaconda\envs\opencv\lib\site-packages\selenium\webdriver\remote\webdriver.py in execute(self, driver_command, params)
319         response = self.command_executor.execute(driver_command, params)
320         if response:
--> 321             self.error_handler.check_response(response)
322             response['value'] = self._unwrap_value(
323                 response.get('value', None))
F:\Anaconda\envs\opencv\lib\site-packages\selenium\webdriver\remote\errorhandler.py in check_response(self, response)
240                 alert_text = value['alert'].get('text')
241             raise exception_class(message, screen, stacktrace, alert_text)
--> 242         raise exception_class(message, screen, stacktrace)
243
244     def _value_or_default(self, obj, key, default):
WebDriverException: Message: unknown error: net::ERR_INTERNET_DISCONNECTED
i tried googling for a solution but, couldn't find any that fixed the issue.
Kindly help me resolve this.

I have the same problem as Tejas-Haritsa-vk. Have you solved the problem?

I have the same problem as Tejas-Haritsa-vk. Have you solved the problem?

Hi, tfppcn. I have resolved this issue by using the folloing lines of code:
from selenium.common.exceptions import WebDriverException
try:
driver.get(game_url)
except WebDriverException:
pass

Thank you Tejas, I've finally got it to work with your help.
It runs very slowly on my laptop without GPU but at least it runs. What is the highest score you got?
Is it possible to copy a trained model.h5 and use it to speed up the learning?

Thank you Tejas, I've finally got it to work with your help.
It runs very slowly on my laptop without GPU but at least it runs. What is the highest score you got?
Is it possible to copy a trained model.h5 and use it to speed up the learning?

you are welcome @tfppcn, yes it is possible to speed up training using a pre trained model. I haven't trained it for long yet hence no score, the only 2 time I ran it scored around 140-160.

Thank you Tejas, I've finally got it to work with your help.
It runs very slowly on my laptop without GPU but at least it runs. What is the highest score you got?
Is it possible to copy a trained model.h5 and use it to speed up the learning?

Hi @tfppcn , do you happen to know the root cause of the issue?

I’m not sure but looking at the error messages, I guess that selenium is not happy about the web browser being offline.
Tejas’s solution of error handling that with an exception worked. Perhaps selenium has been updated since the last time you ran it.

From: Ravi Munde notifications@github.com
Sent: Thursday, December 10, 2020 5:33:39 AM
To: Paperspace/DinoRunTutorial DinoRunTutorial@noreply.github.com
Cc: tfppcn tfpp_cn@outlook.com; Mention mention@noreply.github.com
Subject: Re: [Paperspace/DinoRunTutorial] Selenium and dino game (#12)
Thank you Tejas, I've finally got it to work with your help.
It runs very slowly on my laptop without GPU but at least it runs. What is the highest score you got?
Is it possible to copy a trained model.h5 and use it to speed up the learning?
Hi @tfppcnhttps://github.com/tfppcn , do you happen to know the root cause of the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Paperspace/DinoRunTutorial/issues/12#issuecomment-741966414, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANTSTCUG7ZWXAJUPHV3N4J3ST67IHANCNFSM4TCOSZOQ.

Hi,
I don't think it is due to selenium update at all as I tried the same
selenium package on two different systems and one worked and the other
didn't. So, I think it is more connected towards the particular system
firewall and security settings maybe. Not 100% sure though, as I checked my
firewall and it was allowing python. Hope this helps.

with regards
Tejas Haritsa V K

On Thu, Dec 10, 2020, 8:09 AM tfppcn notifications@github.com wrote:

I’m not sure but looking at the error messages, I guess that selenium is
not happy about the web browser being offline.
Tejas’s solution of error handling that with an exception worked. Perhaps
selenium has been updated since the last time you ran it.

From: Ravi Munde notifications@github.com
Sent: Thursday, December 10, 2020 5:33:39 AM
To: Paperspace/DinoRunTutorial DinoRunTutorial@noreply.github.com
Cc: tfppcn tfpp_cn@outlook.com; Mention mention@noreply.github.com
Subject: Re: [Paperspace/DinoRunTutorial] Selenium and dino game (#12)
Thank you Tejas, I've finally got it to work with your help.
It runs very slowly on my laptop without GPU but at least it runs. What is
the highest score you got?
Is it possible to copy a trained model.h5 and use it to speed up the
learning?
Hi @tfppcnhttps://github.com/tfppcn , do you happen to know the root
cause of the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<
https://github.com/Paperspace/DinoRunTutorial/issues/12#issuecomment-741966414>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/ANTSTCUG7ZWXAJUPHV3N4J3ST67IHANCNFSM4TCOSZOQ

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Paperspace/DinoRunTutorial/issues/12#issuecomment-742197317,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOSTLU347VGX2QXP7ZPLPZLSUAYFXANCNFSM4TCOSZOQ
.

The suggestion by @Tejas-Haritsa-vk worked for me to get the project running. I am only able to get a score of about 150 or so myself. The chrome browser seems to crash with an error:
NoSuchWindowException: Message: no such window: window was already closed
I'll update here if I can get it fixed and running better.

authors: BlaineOmega Tejas-Haritsa-vk ravi72munde tfppcn

repo: Paperspace/DinoRunTutorial


text:
Making project up to date with upstream

Description
Updating the project with upstream
Rationale
To get the latest functionalities of the main repo.
Use case(s) / visualization(s)

reffered to #11

source: gharchive/pull-request

repo: Parbhat/cookiecutter-django-foundation

license_type: permissive

license_source: bigquery


text:
Push notification not working.

Hi
I have migrated parse server code to aws, running properly except push notification.
I have added cloud code afterSave method including masterKey method.
Now whenever I am saving a item from iOS app, this method is getting called, but no push notification is getting for device, when i checked server log its showing an error:
ERR! parse-server-push-adapter APNS cannot find vaild connection for
/node_modules/parse-server/lib/ParseServer.js:327
throw err;
^
Error: wrong tag
at Error (native)
at Object.createSecureContext (_tls_common.js:132:17)
at Object.TLSSocket._init.ssl.onclienthello.ssl.oncertcb.exports.connect (_tls_wrap.js:972:23)
Can you please let us know what extra setting we need to add?

Hi, did you go through the guide here:  https://github.com/ParsePlatform/parse-server/wiki/Push and create .p12 certificate and use it in your code? also please make sure you generate the right certificate (either sandbox or production).
it will also be nice if you can paste some code (the code where you configure the push and also the afterSave method code)

DId you follow the push guide on the wiki?

This seems to be an error with the push adapter which is provided as a separate module. Please report the issue on this repository https://github.com/parse-server-modules/parse-server-push-adapter

source: gharchive/issue

authors: flovilmart ksingh65 ranhsd

repo: ParsePlatform/parse-server

license_source: github-api


text:
Parse Server S3 Access Denied.

Hello,
I tried A few time but its not working.
Problem is I created bucket and configured it. Also I configure de adapter. I'm getting an url https://onmesocial.s3.amazonaws.com/50fba12a2062cf42220185ea18db12d4_file.jpeg
but I'm getting this error.
<Error>
AccessDenied
<Message>Access Denied</Message>
<RequestId>6B94CFF9376F1B8C</RequestId>
<HostId>
YMxWAo7TcXWQYBg1iYReib1tVmRjpLtmTBl5EEKoWwo+iMF5q9yRYnFq35AX/zEWpUffrZWblNc=
</HostId>
</Error>

Also parse is not writing files to the s3
this is my configuration.
filesAdapter: {
    "module": "parse-server-s3-adapter",
    "options": {
      "bucket": "onmesocial",
      "accessKey": "accesskey",
      "secretKey": "secretkey",
      "directAccess": true,
      "baseUrl": null,
      "baseUrlDirect": false,
      "signatureVersion": 'v4'
    }
  },

Hey @mkaya93, did you follow all the instructions here: https://github.com/ParsePlatform/parse-server/wiki/Configuring-File-Adapters#set-up-your-bucket-and-permissions, including configuring the Policy Document?

@natanrolnik yes I followed the instructions but I'm still getting access denied.

Either that image doest exists in the bucket or the policy in S3 has not being setup correctly!

@Cliffordwh images are not synchronized and adding to bucket either also can't access them.

Couple of things you can try to determine where exactly is the problem: upload a file to S3 bucket by hand and try to access is as anonymous user.
If this works then there's something wrong with your Parse config. Check the accessKey and secretKey. Compare the S3 url of your manually uploaded file with the one that parse generates - sometimes the problem can be different S3 regions. Below is my working config using custom (EU) region.
var S3Options = {
  accessKey: "myaccesskey",
  secretKey: "mysecret",
  bucket: "mybucket",
  region: "eu-central-1",
  signatureVersion: "v4"
}

@mkaya93 are you still having this problem?

I think I'm having the same issue, where files are saved:
In Parse as https://.s3.amazonaws.com/
When I go to S3 the filenames are: https://s3.amazonaws.com//
The Parse filename, just times out, but the images are fine when accessed through S3.  I am using directAccess:true, and can see the file in S3 is set to be publicly viewable.

authors: Cliffordwh Muesly lenart mkaya93 natanrolnik


text:
Push Notification Setup on Parse Server/iOS App

Issue Description
Parse Push notifications send successfully on the mobile client app, but are never delivered to the destination client. Im certain there is step im just missing here, as it worked on Parse.com, but after migrating and setting up with NodeChef and enabling push on both ends, push notifications are not delivered. If there is a guide specifically to set up Parse Server with Client push notification support, Id happily follow it! 👍
Steps to reproduce
Expected Results
I expect a notification to pop up on the destination client device with a message.
Actual Outcome
Nothing is delivered
Environment Setup

Server

parse-server version (Be specific! Don't say 'latest'.) : 2.3.2
Operating System:  NodeChef
Hardware:  Nodechef
Localhost or remote server? Nodechef

Database

MongoDB version: 3.2.11
Storage engine:
Hardware:
Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): AWS/mLab

Logs/Trace

Are your sending the push from your iOS app? If so, Parse Server does not support client triggered push notifications. You must use your master key to send push notifications.
You can also look at the _PushStatus collection in your MongoDB to see all push notifications and their statuses.

I am indeed sending from my app, and ah I see! Is there a guide on how to use the master key to send the notifications?

Check out
http://parseplatform.github.io/docs/parse-server/guide/#send-push-notifications and
http://parseplatform.github.io/docs/js/guide/#sending-pushes
Essentially it's just:
Parse.Push.send({
  where: installationQuery,
  data: {
    alert: "Testing testing 1... 2... 3..."
  }
}, {
  useMasterKey: true
}).then(function() {
 // success!
}, function(error) {
  // error!
});

Excellent, thanks Jeremy! Closing issue now.

authors: JeremyPlease kaifucious


text:
True beginner's migration guide

A lot of people chose Parse because they had no experience with developing backends. The current migration guide is a great start, but much of it is just an executive summary for people who already know what they're doing (particularly the section "Deploying to Heroku/MongoLab").
What's really needed is a true beginner's guide and best practices that takes you through all the steps of setting up a Heroku account correctly, installing node, setting up mongoDB, migrating everything over, making sure everything's working, etc. Ideally, you'd be able to follow the steps to do a complete migration of a standard Parse app with little to no experience in the platform/languages. (Sort of like the original Parse tutorials for developing your first iOS app with Parse integration.)
Otherwise, a lot of developers will be left out in the cold here, either abandoning their apps completely, spending weeks/months learning new platforms/languages, or spending thousands hiring someone else to do it for them.

Agreed

+1

+1

+1, has anyone done pricing of moving to Heroku though?? Their DB's aren't cheap if you want to keep your data safe and replicated.
I'm think we (developers) need to start budgeting for minimum $100/month in hosting. Not cheap for us Indie guys that haven't even launched a product yet. Experts chime in but I just need to get back to the 30 req/sec benchmark. Then be able to scale from there.

+1

Agreed, @nitrag. Looking over their pricing page, I don't really have any clue what I'd need for a simple app that has ~5k users and is doing less than 1 request per second. Would the hobby tier work for that?

+1 yes a detailed guide explaining how to deploy Parse Server on Windows Azure/AWS/Google App Engine would be great !

Looks like we'll also need to crowd-open-source a web-based dashboard.
That's is handy for me while I am still developing.
On Fri, Jan 29, 2016 at 1:04 PM, Michaël notifications@github.com wrote:

+1 yes a detailed guide explaining how to deploy Parse Server on Windows
Azure/AWS/Google App Engine would be great !
—
Reply to this email directly or view it on GitHub
https://github.com/ParsePlatform/parse-server/issues/38#issuecomment-176889908
.

@bmueller According to this comment, a 5$/month Digital Ocean VPS could work for you. I have a few small apps and I'm interested in Digital Ocean right now. You may want to checkout it's pricing plans too.

The current guide is definitely our first stab at explaining the core principles, and I agree we can make better guides for each vendor.
We're thinking of these vendors: AWS, Digital Ocean, Heroku, Azure. Any others you guys would be interested in?

Linode is interesting as well, and the Digital Ocean guide could easily be worked out to also match linode's similar offerings.

@jamesyu great to hear, I think a lot of us would be totally lost without something a lot more in-depth for all the newbies who have no experience doing any of this stuff. Really appreciate the effort you're putting into this.

Perhaps Google App Engine as well

Hey Folks, Creager here from Heroku, happy to help prepare a beginner-friendly guide to getting the parse-server up and running on Heroku!  In the meantime, we're working on adding a Heroku Button to the [parse-server-example]!

The cheapest option I see right now is to use Google App Engine + MongoLab
Any one have better ideas?

On Jan 29, 2016, at 1:04 PM, Michaël notifications@github.com wrote:
+1 yes a detailed guide explaining how to deploy Parse Server on Windows Azure/AWS/Google App Engine would be great !
—
Reply to this email directly or view it on GitHub https://github.com/ParsePlatform/parse-server/issues/38#issuecomment-176889908.

Here's one for GAE that someone wrote: https://medium.com/google-cloud/deploying-parse-server-to-google-app-engine-6bc0b7451d50

@mattcreager @jamesyu and Parse/Facebook staff.
It means a lot to us that you guys are still dedicated to supporting the developers and helping us find the best path forward. Getting us on the right path early (before you move on at FB) will give us the best shot at continuing to improve and grow Parse and the community.
Waht we'd like to see in your guides

Deploying to the different platforms mentioned above BUT also pro's and con's of each. What struggles/limitations can you help us foresee so we can be prepared for that
Reliability: How do we achieve the similar level of stability and data reliability we've had with Parse. With whatever platform we choose, what features/services will we need to ensure no downtime for our users.
Performance benchmarks: What level of server processing power should be considered minimum for supporting X users or X req/s? Can you baseline this since this is now something we will have to manage ourselves?
Operationally - What to look out for, such as the indexing information already provided. Tips to optimize and keep the platform running healthy/stable.

Again, thank you for you time and support.

@meilers https://www.digitalocean.com/pricing/ $5 here gets us close to what Parse was for free.
+1 for a ELI5 guide for multiple providers.

@hslightnin Yes but, correct me if I'm wrong, you can't scale that if you dump the DB, parse-server, etc on the same server. With digitalocean or AWS wouldn't you need a load balancer, multiple nodejs application servers and a mongoDB replicated to be completely safe? What your talking about is potential major downtime. I was hinting at this in my previous post and waiting for some professionals to chime in.

True , but those of us who would never outgrow the free Parse subscription need something that isn’t going to be $400/mo.
From:  nitrag notifications@github.com
Reply-To:  ParsePlatform/parse-server reply@reply.github.com
Date:  Friday, January 29, 2016 at 12:00 PM
To:  ParsePlatform/parse-server parse-server@noreply.github.com
Cc:  Robert hslightnin@gmail.com
Subject:  Re: [parse-server] True beginner's migration guide (#38)
@hslightnin Yes but, correct me if I'm wrong, you can't scale that if you dump the DB, parse-server, etc on the same server. With digitalocean or AWS wouldn't you need a load balancer, multiple nodejs application servers and a mongoDB replicated to be completely safe? What your talking about is potential major downtime. I was hinting at this in my previous post and waiting for some professionals to chime in.
—
Reply to this email directly or view it on GitHub.

I use DigitalOcean to run my Parse Server and it's great. Not too different to run any other NodeJS and MongoDB app.

This is a step by step guide I made for the transition. I hope this helps someone. I just want to say that I don't know anything about node.js and yesterday was my first day using it.
Please try this guide with a not production parse app first. It’s recommended to clone your repo and try with this copy so if something goes wrong, you don't loose any data. I’m not responsible for anything that can happen with your data, app, computer or anything.
First Time Only:
Install source tree (you can use git from console if you want to)
Install node.js. This also installs npm.
Install Heroku toolbelt
Open Terminal
npm install express-generator -g     //Installs a generator for express (where Parse-server works)
Create a Mongolab account
Create a Heroku account
Create a Bitbucket account and setup source tree with this account (for git with source tree)
Every Time a new parse server is needed
Open Terminal
cd my/directory/where/folder/will/be/with/node.js/
express nameOfMyApp     //Creates a template of node.js. MAKE SURE IS ALL LOWERCASE!
cd nameOfMyApp
npm install       //Install dependencies
npm install express —save      //Install dependencies
npm init
Open Source tree
Select create local repository
Select your folder of nameOfMyApp and create repo
heroku login
enter your credentials of heroku
heroku create
echo ‘web: node app.js' >procfile     //Create procfile for Heroku
In source tree, commit and push to Heroku master. Wait for everything to be successful
heroku ps:scale web=1    //Set a node for Heroku
heroku open
Verify it’s working and no error message appears. You should se a Welcome to Express screen
npm install parse-server —save     //Installs Parse Server. If you see a warning of kerberos ignore it
For new parse databases
Create in mongolab new deployment
For the new deployment create a user and a password
For migrations from Parse to mongodb
Enter to parse new dashboard
Go to app settings -> General -> Migrate to external database
From mongolab, search for the MongoDB URI
replace dbuser and dbpassword with your user and password you created
Copy the whole url into parse
Wait for the transition to finish. This can take a few minutes to hours. It depends on the amount of data. Once it finishes, go to mongolab and check that all your info is there.
Final steps:
Open app.js. You can do it with the program of your preference
Add var ParseServer = require(‘parse-server').ParseServer; at the top of the file
Add this before 404 call
// Specify the connection string for your mongodb database
// and the location to your Parse cloud code
var api = new ParseServer({
databaseURI: ‘mongodb://yourMongoDBURL',
cloud: 'parse-server/cloud/main.js',
appId: ‘Your App Id',
masterKey: ‘Your Master Key'
});
// Serve the Parse API on the /parse URL prefix
app.use('/parse', api);
var port = process.env.PORT || 1337;
app.listen(port, function() {
console.log('parse-server-example running on port ' + port + '.');
});
Commit and push to heroku
You’re finished!! Now, to use Parse just point your apps to the new Server. You will need at least version 1.12 for iOS, 1.13.0 for Android, 1.6.14 for JS, 1.7.0 for .NET

@francocorreasosa Could you provide some sort of guide about how you achieve that? I had never used Node JS nor Mongo before and I'm having lots of troubles with it. I'd be forever in your debt.

@Rhadammanthis You'll need to install nginx and do a reverse proxy to the port 5000. Then install nodejs and npm. Next, create a project folder and cd it, do a npm init and npm install pm2 express parse-server --save. Then create a server.js file and paste this:
var express = require('express');
var ParseServer = require('parse-server').ParseServer;

var app = express();

// Specify the connection string for your mongodb database
// and the location to your Parse cloud code
var api = new ParseServer({
  databaseURI: 'mongodb://localhost:27017/dev',
  cloud: '/home/myApp/cloud/main.js', // Provide an absolute path
  appId: 'myAppId',
  masterKey: 'mySecretMasterKey',
  fileKey: 'optionalFileKey'
});

// Serve the Parse API on the /parse URL prefix
app.use('/parse', api);

// Hello world
app.get('/', function(req, res) {
  res.status(200).send('Express is running here.');
});

var port = process.env.PORT || 1337;
app.listen(port, function() {
  console.log('parse-server-example running on port ' + port + '.');
});

Then do pm2 start server.js -i 2
You're done

@francocorreasosa you did all that on digitalocean?

@meilers Yes, in my case I am hosting the DB on the same droplet but if you want you can host the mongo instance in another DB and connect it within the DigitalOcean's Private Network.

My 2¢ : There is a group of users who were drawn to Parse because it was so accessible/easy to use. Everything was in one place and it solved a lot of potential headaches. I am one of those users. Since the news of the shut down broke, I've been looking at the opportunity to switch to something like a Docker container on AWS. However, this just feels like an opportunity to fail in a production environment (I know nothing about professional security, adequate redundancy planning etc.). I've hacked together a working server but I'm sure professionals would laugh/shake their head at my incompetence.
So, I think it would be really helpful to people like me if we could put together a suggested "architecture" for purely managed services where all the security/uptime issues are taken care of by 3rd parties. I haven't found a direct replacement for the breadth of services Parse offered but a combination of 3-4 (?) might work well for a lot of people. I'm happy to contribute my findings/approach but thought the experts on here might be able to provide objective guidance. Off the top of my head, I'm thinking something like this (not done the research yet): Firebase (replaces Core Data)+Heroku??? (Cloud code)+Flurry (analytics)+UrbanAirship (push notifications)...you get the idea.
@gfosco have you got any suggestions where this kind of content could be put/discussed?
BTW something I noticed which isn't obvious in a comment above: the "Migrate to external database" button is only available in the "beta" admin web interface.

I got mine up and running on digital ocean in a couple of hours as well, minus the login. Had an issue with my SB when it migrated I think, but all up and running now.

@docherty I agree it would be helpful to have a list of suggestions on how to rebuild our stack. Would we need to use an external service like Firebase for Core or could we survive simply on Parse Server running on Heroku?
Does anyone have any thoughts on OneSignal for Push? It is completely free. Also I wouldn't use Flurry as they are part of Yahoo, and I've learned my lesson from Facebook with Parse.

I've contacted Digital Ocean to request they add Parse Server to their list of One-Click Applications. That, with MongoDB, would be a big help for those of us without that in-depth backend experience.

Just rewrote a @jpv123's comment above for better readability:
This is a step by step guide I made for the transition. I hope this helps someone. I just want to say that I don't know anything about node.js and yesterday was my first day using it.
Please try this guide with a not production parse app first. It’s recommended to clone your repo and try with this copy so if something goes wrong, you don't loose any data. I’m not responsible for anything that can happen with your data, app, computer or anything.
First Time Only

Install source tree (you can use git from console if you want to)
Install node.js. This also installs npm.
Install Heroku toolbelt
Open Terminal
npm install express-generator -g //Installs a generator for express (where Parse-server works)
Create a Mongolab account
Create a Heroku account
Create a Bitbucket account and setup source tree with this account (for git with source tree)

Every Time a new parse server is needed

Open Terminal
cd my/directory/where/folder/will/be/with/node.js/
express nameOfMyApp //Creates a template of node.js. MAKE SURE IS ALL LOWERCASE!
cd nameOfMyApp
npm install //Install dependencies
npm install express —save //Install dependencies
npm init
Open Source tree
Select create local repository
Select your folder of nameOfMyApp and create repo
heroku login
enter your credentials of heroku
heroku create
echo ‘web: node app.js' >procfile //Create procfile for Heroku
In source tree, commit and push to Heroku master. Wait for everything to be successful
heroku ps:scale web=1 //Set a node for Heroku
heroku open
Verify it’s working and no error message appears. You should se a Welcome to Express screen
npm install parse-server —save //Installs Parse Server. If you see a warning of kerberos ignore it.

For new parse databases

Create in mongolab new deployment
For the new deployment create a user and a password

For migrations from Parse to mongodb

Enter to parse new dashboard
Go to app settings -> General -> Migrate to external database
From mongolab, search for the MongoDB URI
replace dbuser and dbpassword with your user and password you created
Copy the whole url into parse
Wait for the transition to finish. This can take a few minutes to hours. It depends on the amount of data. Once it finishes, go to mongolab and check that all your info is there.

Final steps
Open app.js. You can do it with the program of your preference
Add var ParseServer = require(‘parse-server').ParseServer; at the top of the file
Add this before 404 call
// Specify the connection string for your mongodb database
// and the location to your Parse cloud code
var api = new ParseServer({
databaseURI: ‘mongodb://yourMongoDBURL',
cloud: 'parse-server/cloud/main.js',
appId: ‘Your App Id',
masterKey: ‘Your Master Key'
});

// Serve the Parse API on the /parse URL prefix
app.use('/parse', api);

var port = process.env.PORT || 1337;
app.listen(port, function() {
console.log('parse-server-example running on port ' + port + '.');
});

Commit and push to heroku
You’re finished!! Now, to use Parse just point your apps to the new Server. You will need at least version 1.12 for iOS, 1.13.0 for Android, 1.6.14 for JS, 1.7.0 for .NET

@dcdspace Re Firebase: The reason I'm looking at it (rather than mongoDB) is that I want to replicate the functionality of Parse.User.current() in a hybrid (JS SDK) app. I use this feature to sync data between the device and the server really easily. The Firebase SDK has a similar feature (I need to do more testing but that's what I remember from a while ago). If I just wanted a datastore I'd probably use a managed mongoDB service like mongoLab.
Re. Flurry: I know what you mean but ultimately businesses are typically owned by someone else - Heroku is Salesforce. So while I agree it's a bummer, any service could disappear/change. In the case of Parse/Facebook you have to agree that they've done a pretty good job of trying to help users transition (we have a year, they're paying guys to support the community, they've open sourced their code etc.) I doubt that would have happened if it was a small independent company and the money ran out. Flurry is owned by Yahoo but it's an integral part of their ad business.
I've created a repo here: https://github.com/docherty/parse-migration-to-managed-services with my notes which I'll keep updating and eventually turn into a tutorial for the few people that want to piece together a "managed" replacement for Parse.com .

If it helps, I've created a tutorial on installing Parse API Server on AWS. I have also released an Amazon Machine Image (AMI) with everything already installed, just needs configuration. See: http://bit.ly/parse-server

Thanks @docherty , that is an awesome repo and will be very useful to me and others I'm sure.

I know this would be a long shot but any chance you could package this up like backendless?
https://backendless.com/products/standalone-backendless-quick-start-guide/

Here is a HowTo Step by Step to create a Parse Server on your own Server.
https://medium.com/@jcminarro/run-parse-server-on-your-own-server-using-digitalocean-b2a7d66e1205#.e33bkf4m3

@jamesyu also GAE is missing. The tutorial from medium is not enough in my opinion, totally ignores migration. A comprehensive guide should also consider holding MongoDB in a dedicated GCE cluster, see https://cloud.google.com/launcher/solution/click-to-deploy-images/mongodb?q=mongodb . That can cost less that the 180$ for MongoLab and is just as easy.
For example - just to name one of the things that a typical parse user is not understanding - when configuring the above mentioned cluster, I don't understand if I should have disk space for both data (Parse's Data Storage) and images pointed from that data (Parse's File Storage), or if the latter should go in my GAE Storage space. The migration tool is going to point to the mongo in GCE.
Another thing that is very very unclear is how ParseFiles are managed by the migration tool. That's missing in your guide.
So my suggestions are:

GAE + GCE
Better ParseFile understanding. How are these managed by the migration tool?
Better storage understanding, mostly related to files pointed from ParseFile columns. Where will they be hosted? When assigning storage, should we 10x the data storage or both data and file storage for those files?
Consider writing in your guide that push and dashboard are probably coming.

Another great guide for digital ocean:
http://julienrenaux.fr/2016/01/29/complete-parse-server-migration-guide/

I wrote up a more comprehensive tutorial than the one parse give, and actually realised it's really easy to deploy your own parse server to heroku and mongo lab [https://medium.com/@timothy_whiting/setting-up-your-own-parse-server-568ee921333a#.s09l7a5vh]

@mkll thank you very much for that. Do you think it's cheaper to setup a mongoDB directly in mongoLab and then just add its URI in app.js instead of using Heroku's mongoLab add-on?

Super helpful tutorial @arcopo thanks!

@meilers, your thanks should be addressed to @jpv123, I just rewrote his comment. :)
As for me, I still collect the info and didn't do anything to migrate from Parse.

This is a very nice beginner friendly write up by Timothy Whiting. Even if you've never used Heroku, Mongodb or node.js - https://medium.com/@timothy_whiting/setting-up-your-own-parse-server-568ee921333a#.dfndszn7w

I posted a guide on running Parse Server on a DigitalOcean Ubuntu Droplet (or really any Ubuntu system) earlier this morning.  It's definitely not a full migration guide, but does cover installing Node and running the example code in parse-server-example.
Parse is a new topic to me personally, so I've got some learning to do, but we'd love to see a beginner-friendly migration guide supported within the scope of the open source project that includes our platform (well, and by logical extension generic Linux VPS provider installations).  I can likely devote some energy to helping with that.

First kudos to the parse.com developer team to open source their server. That's an incredible move on their end!
Second, it would be really helpful as mentioned above to get some real world numbers for what service can handle what load and how to set it up for scaling (possibly in the millions of users).
What's the advantage of AWS vs. Heroku vs. GAE vs. Digital Ocean?
I am leaning towards AWS because they just have the biggest server farm there is (imho), but all the guides above are for Heroku or Digital Ocean, is AWS too hardcore to setup?

@markuswinkler actually, the guide I posted was for AWS setup on Ubuntu 14 (http://bit.ly/parse-server), with a pre-built AMI you can easily launch without having to setup the software yourself.

fantastic! Very much appreciated.
I am not too familiar with AWS. How would I scale from there if one server is not enough? I don't have any frame of reference how much a single server can handle or process.

Great discussion and info here... Much appreciated everyone!

Any word on whether Parse is going to open source the dashboard? Browsing/editing data in a GUI was a huge benefit to us when prototyping. It's gonna be a drag to build something like it from scratch...

Looks like the first company has started.

@auggernaut  If you migrate your app from Parse to your own server, Parse still shows you data from your own server, and you are able to see/edit data. I think that they are not going to close it (I don't remeber where I read it)
@gfosco @drew-gross @wangmengyan95 Do you know anything about it?

@JcMinarro they are going to close it, but they are also probably open sourcing that as well.

The parse.com dashboard will still be able to view and edit the data on your self-hosted database, however that won't be true after January 28, 2017. We are working on open sourcing our dashboard so that it can be used with parse-server.

@drew-gross Thank you for clearfy it ;)

Thanks for all the info in this thread very helpful and is putting me at ease slightly.
I was probably in peaceful ignorance to what the parse service was build on, however my question is: Can a single digital ocean droplet offer me the same reliability? Can they be mirrored, load balanced etc to guarantee 9.9999% uptime?
A 'gold standard' Digital Ocean setup including security, data view and backup strategy would be my ideal.
If I can the knowledge I would love to write it - however I'm completely reliant on you kind folks atm. Thanks for all your hard work!

You would have to look into the SLA of Digital Ocean for uptime. Load balancing will up to you after you move to parse-server, and different providers will have different levels of automation in load balancing.

1+ for a open source dashboard.

A dashboard would be great, but also the ability to run multiple apps from one server instance.

If you want to use Heroku, create an account the go to https://devcenter.heroku.com/articles/deploying-a-parse-server-to-heroku and click "Deploy to Heroku", copy the master key and app id from your parse app and you're set. Had me going in under 3 mins after spending hours trying to follow tutorials online

I succeded use DelightedD0D and DigitalOcean with Ubuntu on localhost virtual machine guides.

For anyone having trouble getting going with Heroku, I posted the method I used here:http://stackoverflow.com/questions/35389389/how-can-i-host-my-own-parse-server-on-heroku-using-mongodb/35389397#35389397

i found this tutorial is very easy to follow https://learnappmaking.com/how-to-migrate-parse-app-parse-server-heroku-mongolab/

One more entry from us at DigitalOcean: How To Migrate a Parse App to Parse Server on Ubuntu 14.04. Quite a bit more detailed than my first go at the problem.

I have yet to see something that I am been secure in moving to. I have not seen anything with regard to failover, no-one seems concerned about this - are we that trusting of DO, AWS and Heroku for our uptime.
Using Mongolab is expensive - Parse recommend that 10x size is required. Therefore the MongoLab sandbox plan is fine for those who have <50Mb parse export?
There is little talk about the cloud code and files. Where are they stored and how are they managed?

i have got a begginner Guide from one udemy courses :+1:
The guide is available now at:
http://www.robpercival.co.uk/parse-server-on-heroku/

Now that there's a bevy of content online, different migration and deployment tutorials, I feel like we can close this general issue.  My favorite is the two Digital Ocean guides, they are super thorough, and the migration guide really covers setting up a production-level instance.  Excellent work by the community here!

Dokku Parse Server with pm2?
How can we use dokku parse server with pm2 on digital ocean or else? I mean what will be configuration process?

we @ http://appgain.io have used PM2 with parse server to achive multi parse server instances
we are opening our parse hosting service soon to private beta , if you are interested plz let me know

@mohshaheen  If you want people to be interested in your services, you should list more information on your landing page. As it stands the page is quite barren with just an input to subscribe and nothing even explaining what we would be subscribing to. Honestly, it looks very unprofessional, not at all like a service I would trust my production apps to. I get that its a beta and don't get me wrong, I appreciate what you're trying to do there, it's just that the presentation and information could use some work.

authors: DelightedD0D DrJid JcMinarro Kinzi Rhadammanthis Sadmansamee Taylorsuk abremner arcopo arxidon asContagious auggernaut bmueller brennen dcdspace docherty drew-gross estebantcs francocorreasosa gfosco hslightnin iamrelos jamesyu jpv123 kingmatusevich markuswinkler mattcreager mcdappdev meilers miav mkll mohshaheen niraj-shah nitrag phyominthu poseidonsw sinosoidal skynext thewizster ua24


text:
Retries not working

Describe the bug
The retries parameter in the Parsl Config is not behaving as expected. Setting this parameter to >0 does not cause Parsl to relaunch apps that fail.
To Reproduce
Launch the code below using parsl version 1.2.0.
import parsl
print(parsl.__version__, flush = True)
from parsl.app.app import python_app, bash_app
from parsl.config import Config
from parsl.executors import HighThroughputExecutor

@python_app
def test(fail = False, stdout='std.out', stderr = 'std.err'):
    if fail:
        a = 1/0
    return 'Hello'

if __name__ == '__main__':

    config = Config(
        executors = [HighThroughputExecutor()],
        retries = 2
    )
    print('Loading Parsl Config', flush = True)
    parsl.load(config)

    fut = test(fail = True)

    print(fut.result())

Expected behavior
I expected the app to be launched again and see the ZeroDivisionError: division by zero appear more than once.
Environment

OS: Linux
Python version: 3.10.4
Parsl versionL 1.2.0

Distributed Environment

Where are you running the Parsl script from ? Docker container in cloud VM
Where do you need the workers to run ? Local

This code     print(fut.result()) will only execute after all retries have been attempted. It will return the error message of the final retry attempt.
In the runinfo/*/parsl.log log file for your run, you should see lines like this:
2022-09-05 14:06:04.498 parsl.dataflow.dflow:289 [DEBUG]  Task 0 try 0 failed
...
2022-09-05 14:06:04.522 parsl.dataflow.dflow:289 [DEBUG]  Task 0 try 1 failed
2022-09-05 14:06:04.522 parsl.dataflow.dflow:330 [INFO]  Task 0 marked for retry
...
2022-09-05 14:06:04.546 parsl.dataflow.dflow:289 [DEBUG]  Task 0 try 2 failed
2022-09-05 14:06:04.546 parsl.dataflow.dflow:333 [ERROR]  Task 0 failed after 2 retry attempts

showing the tries happening.

Thanks! I missed that before

authors: avidalto benclifford

repo: Parsl/parsl


text:
allow late migration

Proposal to allow tokens to be migrated after the lockup period, in order to let us decouple the lockup period from 100% of token holders migrating.

yeah i wasn't sure if we needed that event at all but i wanted to match the tests

repo: PartyDAO/party-token

license: MIT


text:
Car bugs

Fifth gear not shifting down
Car shifts from fourth to fifth at ~405 km/h, but doesn't downshift back to fourth before ~140 km/h
Car takes ages to slown down at less than 5 km/h
At less than 5 km/h the car seems to have no grip and won't stop until the handbrake is pressed.
Also makes a burnout at 0 km/h.

https://github.com/PartyKarts-io/UnityGame/pull/30/commits/85dfa826bed30d7f338f44ab4d4d50b24225809d
This has been fixed via this commit + PR

authors: PartyKarts enterprisecock

repo: PartyKarts-io/UnityGame


text:
refactor test create recipe category, create helper function for crea…

…ting recipe categories used in tests

Coverage decreased (-0.09%) to 92.027% when pulling 42cd5be0400eb5176208ccc25d304306e67038cd on reset_password into 57a7bb640cb644741e30357f361a3825f15ba38a on master.

Coverage decreased (-0.09%) to 92.027% when pulling 42cd5be0400eb5176208ccc25d304306e67038cd on reset_password into 57a7bb640cb644741e30357f361a3825f15ba38a on master.

authors: PatrickCmd coveralls

repo: PatrickCmd/Yummy-Recipe-RestAPI


text:
BLE connection "latency"

Hi it's me again.
So my setup right now is a RPI Zero W in the bathroom to control the PAX Calima. Then I have created three python scripts. One to just get the fan status values, one to turn on boostmode and one to turn off boostmode. So I have totally disabled the automatic programming of the fan. (I actually don't think it works very well either)
I have then installed Home Assistant on the PI Zero W and set up command_line sensor and switch to execute the python scripts and fetch the sensor values etc. (I then have a NUC running Debian and my main Home Assistant setup but thats not important here)
This is actually working pretty well. I can read the sensor value and control the fan by any intricate rules I set up using node-red flows.
I only have one thing I really wish could be improved and that is the latency when connecting to the fan. It takes around 10-15 seconds for the script to connect, execute a function and print the return value. Then I have to wait a few more seconds to be sure the connection has been terminated before I can attempt a new connection. I have tried running a script continuously to keep the connection active. But it was neither reliable nor practical. At least with my limited python skills.
So my question is. Is there any way to improve or otherwise get around this ?

I have tried running the script continuously. This results in the fan not responding to sensors at all (noticed when the fan didn't evacuate the humid air when showering). So continuous connection is not preferable.
As for the BLE latency. It requires a bit more digging. It could be slow interactions using the bluepy library. If this is the case, the solution is to rewrite it in another language with more low-level access.
It's also possible that it's related to the bluetooth stack in linux. Being configured with a high scan interval or long timeouts.
First order of business would be to read the characteristics using an existing tool to determine a reference latency. I'm not afraid of rewriting the tool in another language (professionally working as a C/C++ programmer). But determining the issue should be done first :)

I like a good detective case ^^ I just wish I knew enough to go digging myself in this case.

It's hard to measure using the command line as most tools are interactive consoles and not easily "scriptable". But I do experience a much faster response from bluetoothctl when reading and writing characteristics. I'll look into creating a prototype in Rust using rumble. If the problem is python/bluepy related, this should make it disappear quickly.
Don't worry about rust, if you want I can provide a binary blob for RPi to replace cmdline.py.

I've found the major speed bump in the current script. When requesting a Bluetooth characteristic, bluepy invokes a full scan if no previous scan of characteristics has been done. This is the heavier delay.
Tomorrow I might try invoking a limited discovery (only state and pincode) and see if this results in a speedier "state only script".

I haven't had time to test this one out yet. If you're curious you might try it before I get the time!
Just insert the following into a .py file.
import bluepy.btle as ble
from struct import unpack, pack

addr = "58:2b:db:de:ad:be"
pin = "01234567"

fan = ble.Peripheral(deviceAddr=addr)

# Set Auth (You might want to try without)
fan.getCharacteristics(uuid="4cad343a-209a-40b7-b911-4d9b3df569b2")[0].write(pack("<I", int(pin)))

state_c = fan.getCharacteristics(uuid="528b80e8-c47a-4c0a-bdf1-916a7748f412")[0]
try:
    v = unpack('<4HBHB', state_c.read())
    print(v)
except Exception as e:
    print(e)

fan.disconnect()

It essentially skips all the bells and whistles and tries to assign auth without checking for a response and then fetching the state. It doesn't not print the state nicely, but the time until you get the line should indicate (at least somewhat) the latency. You might want to try without auth as well. I don't know if the fan will return any correct values if we skip auth, but hey,  try it!
As I said previously, I haven't hade time to dig into BluePy to debug thoroughly. If this works well, I might not have to...

Thanks Patrick!
I appreciate the effort.
I did a few runs of my old code, with one and two get functions per connection, and your new code and there is not much difference.
But I think I am OK with the way my setup works now actually. Even though I get:
Update of sensor.fan_getstate is taking over 10 seconds

on almost all state updates. But only actual connection errors around a dusin times a day.
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=72, Temp=24.0, Light=1, RPM=0, Mode='Trickle ventilation')
--- 12.643166542053223 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/no_bells_and_whistles.py
(73, 96, 1, 0, 1, 0, 2)
--- 8.390788316726685 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/no_bells_and_whistles.py
(73, 96, 2, 0, 1, 0, 2)
--- 5.072439432144165 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/no_bells_and_whistles.py
(73, 96, 1, 0, 1, 0, 2)
--- 5.480857849121094 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/no_bells_and_whistles.py
(73, 96, 2, 0, 1, 0, 2)
--- 5.103446960449219 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=73, Temp=24.0, Light=2, RPM=0, Mode='Trickle ventilation')
--- 5.533169269561768 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=73, Temp=24.0, Light=2, RPM=0, Mode='Trickle ventilation')
--- 5.386448383331299 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=73, Temp=24.0, Light=2, RPM=0, Mode='Trickle ventilation')
--- 5.301048517227173 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=73, Temp=24.0, Light=1, RPM=0, Mode='Trickle ventilation')
BoostMode(OnOff=0, Speed=2400, Seconds=0)
--- 8.087800025939941 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=73, Temp=24.0, Light=1, RPM=0, Mode='Trickle ventilation')
BoostMode(OnOff=0, Speed=2400, Seconds=0)
--- 7.667898178100586 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=73, Temp=24.0, Light=1, RPM=0, Mode='Trickle ventilation')
BoostMode(OnOff=0, Speed=2400, Seconds=0)
--- 7.581124305725098 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=72, Temp=24.0, Light=1, RPM=0, Mode='Trickle ventilation')
BoostMode(OnOff=0, Speed=2400, Seconds=0)
--- 7.553771734237671 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/no_bells_and_whistles.py
(73, 96, 1, 0, 1, 0, 2)
--- 5.217174053192139 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/no_bells_and_whistles.py
(73, 96, 1, 0, 1, 0, 2)
--- 5.11168360710144 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=73, Temp=24.0, Light=2, RPM=0, Mode='Trickle ventilation')
--- 5.353248119354248 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=72, Temp=24.0, Light=1, RPM=0, Mode='Trickle ventilation')
BoostMode(OnOff=0, Speed=2400, Seconds=0)
--- 7.431379795074463 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=72, Temp=24.0, Light=2, RPM=0, Mode='Trickle ventilation')
BoostMode(OnOff=0, Speed=2400, Seconds=0)
--- 7.634907960891724 seconds ---
pi@hassbian:~ $ sudo python3 /home/homeassistant/.homeassistant/pycalima/calima_get_state.py
FanState(Humidity=73, Temp=24.0, Light=1, RPM=0, Mode='Trickle ventilation')
BoostMode(OnOff=0, Speed=2400, Seconds=0)
--- 7.408637285232544 seconds ---

Keeping to this thread since it is not really a new issue.
I just started using ESPHome for the Mi Flora sensors. It uses the beacons the sensors send out on their own, instead of actively connecting to them. So I just began wondering if the Calima also broadcasts it state on its own and only need the pin code for changing the state?
So it might be a way to go rather than a Pi.
Using a BLE scanner on iPhone I can see it broadcasts a lot of stuff. But that is as far as my skills go..

Generally I don't think BLE broadcasts data before interaction. In general, the only message broadcasted without an explicit request is the advertisement info which is limited in size and typically holds device type, name etc. This is essentially what you see on your connect screen in the phone before connecting.
I don't think Mi Flora advertises values without GATT data request. However, I don't think we need to Auth to the device in order to read data. I don't recall to be honest, but I don't remember it being required. In the previous post I made, I provided a snippet. You could try to remove the auth line and run it without. See if it works anyway.
However, if ESP Home is performant on the Mi Flora devices. It might be a good approach to try, it might be a faster way to interact with bluetooth than via the pi's bluetooth stack. I even think I have an ESP32 lying around, just not the time to mess with it atm.

A little while later..
I have been monitoring the script latency all this time and I just now noticed something interesting. When my fan is running in boost mode it seems to responds much faster.
I will keep an eye on it from now to see if it is consistent.

I wonder if it can then somehow be tricked into the fast lateny mode without actually running the fan.
Stil using the script you suggested:
import bluepy.btle as ble
from struct import unpack, pack
import time

start_time = time.time()

addr = "58:2B:DB:01:D5:33"
fan = ble.Peripheral(deviceAddr=addr)

state_c = fan.getCharacteristics(uuid="528b80e8-c47a-4c0a-bdf1-916a7748f412")[0]

try:
    v = unpack('<4HBHB', state_c.read())
    print(v)
except Exception as e:
    print(e)

fan.disconnect()
print(" %s seconds" % round((time.time() - start_time),3))


text:
Route

How add route rest and redirect async data via ajax in the part of router ?

Do you mean RESTful routes? Redirect is possible in the patricklouys/http library that is used in the tutorial. The Response object has a redirect method described in the docs. With the right response headers, integrating this into Ajax would be pretty simple. You might make another Renderer like the FrontendRenderer in the example, except set it up with some default headers already set, like content type.

authors: hendrixroa philsown

repo: PatrickLouys/no-framework-tutorial

license: mit


text:
Compatibility issue between @mdx-js/react v3.0.0 and mdx-embed v1.1.2 in gatsby-plugin-mdx v4

Is your feature request related to a problem? Please describe.
Yes, I've recently updated gatsby-plugin-mdx to version 4 and encountered a dependency conflict between @mdx-js/react and mdx-embed. When attempting to install mdx-embed alongside the latest version of gatsby-plugin-mdx, npm throws an ERESOLVE error, indicating an inability to resolve the dependency tree.
Error log:
$ npm install mdx-embed gatsby-plugin-mdx-embed
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: pixelpoint-website@0.1.0
npm ERR! Found: @mdx-js/react@3.0.0
npm ERR! node_modules/@mdx-js/react
npm ERR!   @mdx-js/react@"^3.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @mdx-js/react@"^1.6.16" from mdx-embed@1.1.2
npm ERR! node_modules/mdx-embed
npm ERR!   mdx-embed@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/user/.npm/_logs/2023-11-27T13_28_07_570Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /Users/user/.npm/_logs/2023-11-27T13_28_07_570Z-debug-0.log

Describe the solution you'd like
An update or a workaround that would resolve this dependency conflict. Ideally, mdx-embed should be compatible with the latest versions of @mdx-js/react.
Describe alternatives you've considered
I've considered using --force or --legacy-peer-deps flags to bypass the conflict, but this might lead to unstable and potentially broken dependencies. Another option could be to fork mdx-embed and update the peer dependencies myself, but I would prefer an official update for stability and future compatibility.
Additional context
N/A

I am experiencing the same issue

authors: theskillwithin vannyle

repo: PaulieScanlon/mdx-embed


text:
ошибка при добавлении

выдает ошибку при добавление в gradle

проблема актуальна?
последняя версия 1.0.5.4

authors: N-i-p-o-l abercrombiefitchJAS

repo: PaycomUZ/AndroidSDK


text:
图片上传时的图片名称一会能读到一会不能读到

不知道设置的参数对不对，后台一会能读取到文件名称，一会又不能读到文件名，不能读到文件名的时候就是blob

读到和读不到都是上传的同一个文件吗?

有的文件能读到  有的文件不能读到  不是同一个

解决了吗，我也是这样。

authors: Ljlong0908 PeakTai kinderao


text:
[Snyk] Security upgrade python from 3.8-alpine to 3.10.15-alpine

Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

Dockerfile

We recommend upgrading to python:3.10.15-alpine, as this image has only 1 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

CVE-2024-50602 SNYK-ALPINE320-EXPAT-8359601
  436

CVE-2024-9143 SNYK-ALPINE320-OPENSSL-8235201
  436

CVE-2024-9143 SNYK-ALPINE320-OPENSSL-8235201
  436

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – 0a0be083-6459-4ba0-85ad-79f4ffa89013
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

ALB Listening on HTTP
/lb.tf: 74
AWS Application Load Balancer (alb) should not listen on HTTP

Authentication Without MFA
/rw_iam_user.tf: 8
Users should authenticate with MFA (Multi-factor Authentication) to ensure an extra layer of protection when authenticating

Authentication Without MFA
/iam.tf: 21
Users should authenticate with MFA (Multi-factor Authentication) to ensure an extra layer of protection when authenticating

Authentication Without MFA
/initial_iam_user.tf: 8
Users should authenticate with MFA (Multi-factor Authentication) to ensure an extra layer of protection when authenticating

Authentication Without MFA
/dev_machine.tf: 78
Users should authenticate with MFA (Multi-factor Authentication) to ensure an extra layer of protection when authenticating

CVE-2021-41092
Go-github.com/docker/cli-v20.10.7
Vulnerable Package

CVE-2022-24778
Go-github.com/containerd/imgcrypt-v1.1.1
Vulnerable Package

CVE-2023-39325
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-44487
Go-k8s.io/apimachinery-v0.20.6
Vulnerable Package

CVE-2023-44487
Go-k8s.io/apiserver-v0.20.6
Vulnerable Package

CVE-2023-44487
Go-google.golang.org/grpc-v1.38.0
Vulnerable Package

CVE-2023-45133
Npm-@babel/traverse-7.4.5
Vulnerable Package

CVE-2023-45288
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-45311
Npm-fsevents-1.2.9
Vulnerable Package

CVE-2023-49568
Go-github.com/go-git/go-git/v5-v5.4.2
Vulnerable Package

CVE-2023-49569
Go-github.com/go-git/go-git/v5-v5.4.2
Vulnerable Package

CVE-2024-21626
Go-github.com/opencontainers/runc-v1.0.0-rc93
Vulnerable Package

CVE-2024-24786
Go-google.golang.org/protobuf-v1.26.0
Vulnerable Package

CVE-2024-3817
Go-github.com/hashicorp/go-getter-v1.5.9
Vulnerable Package

CVE-2024-4068
Npm-braces-2.3.2
Vulnerable Package

CVE-2024-41110
Go-github.com/docker/docker-v20.10.7
Vulnerable Package

CVE-2024-6257
Go-github.com/hashicorp/go-getter-v1.5.9
Vulnerable Package

CloudTrail Log Files S3 Bucket with Logging Disabled
/cloudtrail.tf: 49
CloudTrail Log Files S3 Bucket should have 'logging' enabled

CloudWatch Console Sign-in Without MFA Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for management console sign-in without MFA

CloudWatch IAM Policy Changes Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for IAM policy changes

CloudWatch Root Account Use Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for root acount usage

CloudWatch Unauthorized Access Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for unauthorized API calls

Cx477c10a4-5717
Go-go.etcd.io/etcd-v0.5.0-alpha.5.0.20200910180754-dd1b699fc489
Vulnerable Package

Cx9c51b693-b977
Go-github.com/containerd/containerd-v1.5.2
Vulnerable Package

Cxb421a484-d05a
Go-github.com/cyphar/filepath-securejoin-v0.2.2
Vulnerable Package

Cxb6dee8d5-b814
Go-gopkg.in/square/go-jose.v2-v2.5.1
Vulnerable Package

DB Instance Storage Not Encrypted
/rds.tf: 50
AWS DB Instance should have its storage encrypted by setting the parameter to 'true'. The storage_encrypted default value is 'false'.

DB Instance Storage Not Encrypted
/rds.tf: 46
AWS DB Instance should have its storage encrypted by setting the parameter to 'true'. The storage_encrypted default value is 'false'.

EC2 Instance Has Public IP
/ec2.tf: 43
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 137
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 98
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 29
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/dev_machine.tf: 52
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 25
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 119
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 183
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 61
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 6
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 122
EC2 Instance should not have a public IP address.

EC2 Instance Has Public IP
/ec2.tf: 96
EC2 Instance should not have a public IP address.

ECS Task Definition Network Mode Not Recommended
/ecs.tf: 45
Network_Mode should be 'awsvpc' in ecs_task_definition. AWS VPCs provides the controls to facilitate a formal process for approving and testing all...

ECS Task Definition Volume Not Encrypted
/ecs.tf: 71
Amazon ECS Task Definition does not have encryption for data at transit enabled. To prevent such a scenario, enable the attribute 'transit_encryption'

EFS Not Encrypted
/efs.tf: 1
Elastic File System (EFS) must be encrypted

EFS Without KMS
/efs.tf: 1
Amazon Elastic Filesystem should have filesystem encryption enabled using KMS CMK customer-managed keys instead of AWS managed-keys

IAM Database Auth Not Enabled
/rds.tf: 46
IAM Database Auth Enabled should be configured to true when using compatible engine and version

IAM Database Auth Not Enabled
/rds.tf: 50
IAM Database Auth Enabled should be configured to true when using compatible engine and version

IAM Policies With Full Privileges
/iam.tf: 108
IAM policies shouldn't allow full administrative privileges (for all resources)

IAM Policy Grants Full Permissions
/iam.tf: 108
IAM policy should not grant full permissions to resources from the get-go, instead of granting permissions gradually as necessary.

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Missing User Instruction
/Dockerfile: 1
A user should be specified in the dockerfile, otherwise the image will run as root

Passwords And Secrets - Generic Token
/cognito.tf: 85
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Token
/cognito.tf: 86
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Token
/cognito.tf: 84
Query to find passwords and secrets in infrastructure code.

S3 Bucket Object Not Encrypted
/s3.tf: 29
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 39
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 71
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 63
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 81
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 49
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 19
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 91
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 61
S3 Bucket Object should have server-side encryption enabled

S3 Bucket Object Not Encrypted
/s3.tf: 51
S3 Bucket Object should have server-side encryption enabled

Sensitive Port Is Exposed To Entire Network
/ec2.tf: 102
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Sensitive Port Is Exposed To Entire Network
/ec2.tf: 77
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Sensitive Port Is Exposed To Entire Network
/ec2.tf: 53
A sensitive port, such as port 23 or port 110, is open for the whole network in either TCP or UDP protocol

Unknown Port Exposed To Internet
/ec2.tf: 78
AWS Security Group should not have an unknown port exposed to the entire Internet

Unrestricted Security Group Ingress
/ec2.tf: 78
Security groups allow ingress from 0.0.0.0:0 and/or ::/0

Unrestricted Security Group Ingress
/ec2.tf: 106
Security groups allow ingress from 0.0.0.0:0 and/or ::/0

Unrestricted Security Group Ingress
/ec2.tf: 58
Security groups allow ingress from 0.0.0.0:0 and/or ::/0

Unrestricted Security Group Ingress
/ec2.tf: 82
Security groups allow ingress from 0.0.0.0:0 and/or ::/0

ALB Is Not Integrated With WAF
/lb.tf: 27
All Application Load Balancers (ALB) must be protected with Web Application Firewall (WAF) service

ALB Not Dropping Invalid Headers
/lb.tf: 27
It's considered a best practice when using Application Load Balancers to drop invalid header fields

API Gateway Access Logging Disabled
/apigateway.tf: 38
API Gateway Stage should have Access Logging Settings defined

API Gateway Access Logging Disabled
/apig.tf: 316
API Gateway Stage should have Access Logging Settings defined

API Gateway Access Logging Disabled
/apig.tf: 316
API Gateway should have Access Log Settings defined

API Gateway Access Logging Disabled
/apigateway.tf: 38
API Gateway should have Access Log Settings defined

API Gateway Deployment Without Access Log Setting
/apig.tf: 309
API Gateway Deployment should have access log setting defined when connected to an API Gateway Stage.

API Gateway Method Does Not Contains An API Key
/apig.tf: 89
An API Key should be required on a method request.

API Gateway Method Does Not Contains An API Key
/apig.tf: 82
An API Key should be required on a method request.

API Gateway Method Does Not Contains An API Key
/apig.tf: 99
An API Key should be required on a method request.

API Gateway With CloudWatch Logging Disabled
/apig.tf: 316
AWS CloudWatch Logs for APIs should be enabled and using the naming convention described in documentation

API Gateway With Invalid Compression
/apig.tf: 65
API Gateway should have valid compression, which means attribute 'minimum_compression_size' should be set and its value should be greater than -1 a...

API Gateway With Open Access
/apig.tf: 92
API Gateway Method should restrict the authorization type, except for the HTTP OPTIONS method.

API Gateway With Open Access
/apig.tf: 85
API Gateway Method should restrict the authorization type, except for the HTTP OPTIONS method.

API Gateway With Open Access
/apig.tf: 102
API Gateway Method should restrict the authorization type, except for the HTTP OPTIONS method.

API Gateway Without Configured Authorizer
/apig.tf: 65
API Gateway REST API should have an API Gateway Authorizer

API Gateway Without SSL Certificate
/apig.tf: 316
SSL Client Certificate should be enabled

API Gateway X-Ray Disabled
/apig.tf: 316
API Gateway should have X-Ray Tracing enabled

API Gateway without WAF
/apig.tf: 316
API Gateway should have WAF (Web Application Firewall) enabled

CVE-2021-41190
Go-github.com/docker/docker-v20.10.7
Vulnerable Package

CVE-2023-3978
Go-golang.org/x/net-v0.0.0-20211015210444-4f30a5c0130f
Vulnerable Package

CVE-2023-48795
Go-golang.org/x/crypto-v0.0.0-20210513164829-c07d793c2f9a
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.19
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.8
Vulnerable Package

CVE-2024-29018
Go-github.com/docker/docker-v20.10.7
Vulnerable Package

CVE-2024-35195
Python-requests-2.26.0
Vulnerable Package

CVE-2024-4067
Npm-micromatch-3.1.10
Vulnerable Package

CloudTrail SNS Topic Name Undefined
/cloudtrail.tf: 34
Check if SNS topic name is set for CloudTrail

CloudWatch AWS Organizations Changes Missing Alarm
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for AWS organizations changes

CloudWatch Disabling Or Scheduled Deletion Of Customer Created CMK Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for disabling or scheduled deletion of customer created CMK

CloudWatch Log Group Without KMS
/cloudwatch.tf: 1
AWS CloudWatch Log groups should be encrypted using KMS

CloudWatch Management Console Auth Failed Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for AWS Management Console authentication failures

CloudWatch S3 policy Change Alarm Missing
/cloudwatch.tf: 43
Ensure a log metric filter and alarm exist for S3 bucket policy changes

CloudWatch S3 policy Change Alarm Missing
/cloudwatch.tf: 11
Ensure a log metric filter and alarm exist for S3 bucket policy changes

CloudWatch Without Retention Period Specified
/cloudwatch.tf: 1
AWS CloudWatch Log groups should have retention days specified

Cloudwatch Cloudtrail Configuration Changes Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for CloudTrail configuration changes

Cloudwatch Security Group Changes Alarm Missing
/cloudwatch.tf: 1
Ensure a log metric filter and alarm exist for security group changes

Cognito UserPool Without MFA
/cognito.tf: 1
AWS Cognito UserPool should have MFA (Multi-Factor Authentication) defined to users

Cx47e4310e-3167
Go-go.etcd.io/etcd-v0.5.0-alpha.5.0.20200910180754-dd1b699fc489
Vulnerable Package

Cx68162182-3f7b
Go-github.com/containerd/containerd-v1.5.2
Vulnerable Package

ECR Image Tag Not Immutable
/sdlc.tf: 58
ECR should have an image tag be immutable. This prevents image tags from being overwritten.

Healthcheck Not Set
/docker_stack.yml: 4
Check containers periodically to see if they are running properly.

IAM Policies Attached To User
/iam.tf: 106
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 89
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 120
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 55
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 119
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/rw_iam_user.tf: 6
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 19
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 98
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 85
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 24
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 102
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/iam.tf: 115
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/dev_machine.tf: 76
IAM policies should be attached only to groups or roles

IAM Policies Attached To User
/initial_iam_user.tf: 6
IAM policies should be attached only to groups or roles

Instance With No VPC
/dev_machine.tf: 52
EC2 Instances should be configured under a VPC network. AWS VPCs provide the controls to facilitate a formal process for approving and testing all ...

Memory Not Limited
/docker_stack.yml: 4
Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than t...

Missing_HSTS_Header
/scenarios/ecs_takeover/terraform/website/main.go: 51
Attack Vector

Pip install Keeping Cached Packages
/Dockerfile: 18
When installing packages with pip, the '--no-cache-dir' flag should be set to make Docker images smaller

Pip install Keeping Cached Packages
/Dockerfile: 4
When installing packages with pip, the '--no-cache-dir' flag should be set to make Docker images smaller

Pip install Keeping Cached Packages
/Dockerfile: 9
When installing packages with pip, the '--no-cache-dir' flag should be set to make Docker images smaller

RDS With Backup Disabled
/rds.tf: 46
Make sure the AWS RDS configuration has automatic backup configured. If the retention period is equal to 0 there is no backup

RDS With Backup Disabled
/rds.tf: 50
Make sure the AWS RDS configuration has automatic backup configured. If the retention period is equal to 0 there is no backup

REST API With Vulnerable Policy
/apig.tf: 325
REST API policy should avoid wildcard in 'Action' and 'Principal'

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 35
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 33
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 35
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 33
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 33
Attack Vector

Relative_Path_Traversal
/scenarios/rce_web_app/assets/rce_app/index.js: 35
Attack Vector

S3 Bucket Logging Disabled
/s3.tf: 27
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 6
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/codepipeline.tf: 8
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 9
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/cloudtrail.tf: 49
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 49
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 9
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Logging Disabled
/s3.tf: 38
Server Access Logging should be enabled on S3 Buckets so that all changes are logged and trackable

S3 Bucket Policy Accepts HTTP Requests
/cloudtrail.tf: 56
S3 Bucket policy should not accept HTTP Requests

S3 Bucket Policy Accepts HTTP Requests
/s3.tf: 15
S3 Bucket policy should not accept HTTP Requests

S3 Bucket Policy Accepts HTTP Requests
/s3.tf: 4
S3 Bucket policy should not accept HTTP Requests

S3 Bucket Without Versioning
/s3.tf: 49
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 9
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 6
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 38
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/codepipeline.tf: 8
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 27
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/s3.tf: 9
S3 bucket should have versioning enabled

S3 Bucket Without Versioning
/cloudtrail.tf: 49
S3 bucket should have versioning enabled

SNS Topic Not Encrypted
/sns.tf: 12
SNS (Simple Notification Service) Topic should be encrypted

SNS Topic Not Encrypted
/sns.tf: 2
SNS (Simple Notification Service) Topic should be encrypted

Secretsmanager Secret Without KMS
/secrets_manager.tf: 12
AWS Secretmanager should use AWS KMS customer master key (CMK) to encrypt the secret values in the versions stored in the secret

Secretsmanager Secret Without KMS
/secrets_manager.tf: 1
AWS Secretmanager should use AWS KMS customer master key (CMK) to encrypt the secret values in the versions stored in the secret

Secretsmanager Secret Without KMS
/secretsmanager.tf: 1
AWS Secretmanager should use AWS KMS customer master key (CMK) to encrypt the secret values in the versions stored in the secret

Security Opt Not Set
/docker_stack.yml: 4
Attribute 'security_opt' should be defined.

Sensitive Port Is Exposed To Wide Private Network
/rds.tf: 6
A sensitive port, such as port 23 or port 110, is open for a wide private network in either TCP or UDP protocol

Unpinned Package Version in Apk Add
/Dockerfile: 6
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Apk Add
/Dockerfile: 3
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unpinned Package Version in Pip Install
/Dockerfile: 9
Package version pinning reduces the range of versions that can be installed, reducing the chances of failure due to unanticipated changes

Unscanned ECR Image
/sdlc.tf: 56
Checks if the ECR Image has been scanned

User With Privilege Escalation By Actions 'ec2:RunInstances' And 'iam:PassRole'

More results are available on AST platform

authors: svc-pe-appsec vrangsr

repo: PearsonAppsec/cloudgoat


text:
Add development Dockerfile

99% of the work is courtesy @jhiemstrawisc and his Dockerfile.
Draft for now well I figure out why I can't run Goreleaser, everything else works as expected.
Closes #88.

@jhiemstrawisc This addresses your comments. I am going to refrain from creating an amd64 image from the osg-software base until a need is identified. I think it makes sense to have us all use the same dev image across both platforms.

repo: PelicanPlatform/pelican


text:
Add kotlin icon

Added icons for kotlin files (kt and kts)
TODO

[X] Use cargo fmt
[X] Add necessary tests
[X] Add changelog entry
[ ] Update default config/theme in README (if applicable)
[ ] Update man page at lsd/doc/lsd.md (if applicable)

Thanks for the PR! 🎉

authors: LeeWeeder meain

repo: Peltoche/lsd


text:
Autotyping

I got monkeytype working, did some type hints, and turned on typechecking in travis.

bors r+

repo: PennyDreadfulMTG/Penny-Dreadful-Tools


text:
site : TypeScript & JavaScript

타입스크립트
자바스크립트
자바스크립트 기초

타입스크립트 07.08

자바스크립트와 다르게 열거형(enum)이 있음
객체지향과 맞지 않는 구조가 있음
제네릭, 람다 등  문법 사용
var 대신에 let을 사용
병합, 데코레이터, 유틸리티 타입, 이터레이터와 제네레이터

이터레이터 : 배열,맵,set,string

컴파일-타임 타입 검사자가 있는 자바스크립트의 런타임

repo: Pensive-dev/DevBlog


text:
Update NETStandard.Library dependency

I can't publish v9.3.0 because of the NETStandard.Library dependency, see screenshot.

@AndreyAkinshin We need to remove NETStandard.Library dependency from project.json file (only from the main BDN project). It is required only for auto-generated project.json to have it.
Where should I push it? Directly to master? Or to coreclr and merge? Or you could remove this line and stash it with last, version-setting commit?

I already accept the PR, so, just push another commit directly in master.

Hmm. I just realized that we have some other dependencies to prerelease packages.
The problem is that these are available only as prerelease:
"System.Console": "4.0.0-beta-23516",
"System.Threading.Thread": "4.0.0-beta-23516",
"System.Diagnostics.Process": "4.1.0-beta-23516",
"System.Runtime.InteropServices.RuntimeInformation": "4.0.0-beta-23516"

So, do you want to say that it is impossible to publish a stable CoreCLR package that uses System.Console?

I am not sure, I am googling it at the moment.

You can't publish as stable a CoreCLR package, because dependencies are unstable.

=(
@adamsitnik, in this case, can we build two nuget packages in artifacts: a stable release (like 0.9.3) without CoreCLR dependency, and a prerelease (like 0.9.3-beta) with CoreCLR support?

@redknightlois Thanks for the info!
@AndreyAkinshin I think yes. You need to go to the project.json file, remove the dnxcore50 part, build the solution in Release and publish the package. Then remove the net40, net45 and dnx451, restore dnxcore50, update the version and build in Release, grab the package and publish it.
Maybe there is cleaner way of doing it, but I have no ideas as for now.

Ok, now we have two version of the package:

stable 0.9.3 (net40+net45+dnx451)
prerelease 0.9.3-beta (net40+net45+dnx451+dnxcore50)

authors: AndreyAkinshin adamsitnik redknightlois

repo: PerfDotNet/BenchmarkDotNet


text:
Perfect can't build with Ubuntu15, DEVELOPMENT-SNAPSHOT-2016-05-31-a

Docs indicate Perfect is build able with DEVELOPMENT-SNAPSHOT-2016-05-31-a, however when attempting to follow the PerfectTemplate instructions, the build fails with the following output on my Ubuntu15 VM (all required system libs have been installed):
cameron@cameron-VirtualBox:~/Development/PerfectStarter/PerfectTemplate$ swift build
Compile Swift Module 'PerfectNet' (5 sources)
/home/cameron/Development/PerfectStarter/PerfectTemplate/Packages/PerfectNet-0.4.0/Sources/NetNamedPipe.swift:187:10: error: use of unresolved identifier 'errno'
                        guard errno == EINPROGRESS else {
                              ^~~~~
/home/cameron/Development/PerfectStarter/PerfectTemplate/Packages/PerfectNet-0.4.0/Sources/NetNamedPipe.swift:259:26: error: use of unresolved identifier 'errno'
                } else if res == -1 && errno == EAGAIN {
                                       ^~~~~
/home/cameron/Development/PerfectStarter/PerfectTemplate/Packages/PerfectNet-0.4.0/Sources/NetNamedPipe.swift:324:26: error: use of unresolved identifier 'errno'
                } else if res == -1 && errno == EAGAIN {
                                       ^~~~~
/home/cameron/Development/PerfectStarter/PerfectTemplate/Packages/PerfectNet-0.4.0/Sources/NetTCP.swift:129:22: error: use of unresolved identifier 'errno'
                return er == -1 && errno == EAGAIN
                                   ^~~~~
/home/cameron/Development/PerfectStarter/PerfectTemplate/Packages/PerfectNet-0.4.0/Sources/NetTCP.swift:463:10: error: use of unresolved identifier 'errno'
                        guard errno == EINPROGRESS else {
                              ^~~~~
/home/cameron/Development/PerfectStarter/PerfectTemplate/Packages/PerfectNet-0.4.0/Sources/NetTCP.swift:556:56: error: use of unresolved identifier 'errno'
                                let errStr = String(validatingUTF8: strerror(Int32(errno))) ?? "NO MESSAGE"
                                                                                ^~~~~
/home/cameron/Development/PerfectStarter/PerfectTemplate/Packages/PerfectNet-0.4.0/Sources/NetTCP.swift:557:43: error: use of unresolved identifier 'errno'
                                print("Unexpected networking error: \(errno) '\(errStr)'")
                                                                      ^~~~~
/home/cameron/Development/PerfectStarter/PerfectTemplate/Packages/PerfectNet-0.4.0/Sources/Net.swift:91:15: error: use of unresolved identifier 'errno'
    let err = errno
              ^~~~~
<unknown>:0: error: build had 1 command failures
error: exit(1): /home/cameron/.swiftenv/versions/DEVELOPMENT-SNAPSHOT-2016-05-31-a/usr/bin/swift-build-tool -f /home/cameron/Development/PerfectStarter/PerfectTemplate/.build/debug.yaml

I receive a similar error with a hello world clean install:
Package.swift
import PackageDescription

let package = Package(
    name: "hw",
    dependencies: [
     .Package(url:"https://github.com/PerfectlySoft/Perfect.git", versions: Version(0,0,0)..<Version(10,0,0))
    ]
)

Hello - this has been corrected. It's also been bumped up to compile against today's new snapshot.
Thank you!

authors: iamcam kjessup

repo: PerfectlySoft/Perfect


text:
For loops

Thought it'd be nice to generate plain for loops as a special case. 😄 What do y'all think?
TypeScript:
for (let i = 1; i <= 10; i++) {
  // ...
}

Lua:
for i=1,10 do
  -- ...
end

We did this at first and that actually caused a lot of issues, why are the current while loops an issue for you?

Now that I think about it, it's not a huge issue. I'm coding in PICO-8 though, so I'll have to see if there's a token count difference between the for and while.

for i = 1, 10 do - 7 tokens, 16 characters
local i = 1 while (i < 10) do i = i + 1 - 14 tokens, 39 characters.
Current translation seems to be about 2x larger, it kinda depends on how often you use for loops (I would generally recommend for...of where possible) what the impact is on your overall code size.
If this is an issue we could look at using a decorator that forces the plain for. The weird edge cases and corresponding bugs we had originally makes me a little hesitant there though.

I was looking at implementing this until I realized there's a pretty big issue with how lua's numeric for works:
for (let i = 0; i < 4; ++i) {
    ++i;
    print(i);
}

In JS, this would produce: 1,3, but in lua, the modification to i would be ignored and the result would be 1,2,3,4. The only solution I can think of is to scan the loop body for assignments to the loop variable, but that would be pretty expensive to do (especially for large loops).

I managed to get a working version that handles that issue, only to realize there's another, bigger one.
Probably the most common desired use case is this:
for (let i = 0; i < myArray.length; ++i) {
    ...
}

for i = 0, #myArray - 1 do
    ...
end

But these two are not the same. In lua, the stop condition in evaluated once, at the beginning. However, in TS/JS, it is re-evaluated every iteration. That means if the array's length changes, the loop will adapt in JS, but not in lua.
This difference can manifest problems in other ways as well. The only 'safe' loop that can be transpiled this way is one where the condition uses a hard-coded literal:
for (let i = 0; i < 10; ++i) {}

Given the amount of work the transpiler has to do to validate this one specific case, I believe it's just not worth implementing at this point.

authors: Perryvw nucleartide tomblind

repo: Perryvw/TypescriptToLua


text:
关于下载虾米下架的音乐

最近下载不了虾米已下架的音乐，以前都还是可以的。比如：もっと強く - 押尾コータロー
而之前一直都可以下载的。不知道是不是虾米官方从服务器里删除了还是把地址换了。请检查一下，谢谢！

无版权听歌的日子结束呐，虾米要想不惹版权官司，这样做是必须滴。

前几天还可以下载。可惜了。

repo: PeterDing/iScript


text:
Add icons for 2D sprite folders.

This adds a folder icon for 2D sprites.

This change is

Thanks for the contribution!

Thanks for a cool plugin!

authors: PhannGor cmilr


text:
Helm charts automation epic

Discussion about the process of joining the network, from here you take the smart contract address, etc

for the moment we plan to remove the need of having a configuration for the ABI file, but the address of the smart contract will be required
the helm charts are not self-contained... they need a set of things as input when joining a new network, besides the smart contract address they require the addresses of the partners (blockchain bootstraping problem, Genesis Block)
We need a single concepts for these things, something like "network bootstraping file" that requires to be maintained and shared with all parteners

Sub-project, organised here: https://github.com/PharmaLedger-IMI/helm-charts/projects/1

repo: PharmaLedger-IMI/epi-workspace


text:
All the items in the view editor are listed twice

Describe the bug
In the view editor, all the elements you can drag are listed twice. See screenshot

Fixed in 08c246ea5984b2ea8af05cd63f2832d18e7602cf

authors: PhilipSkinner ericdevries

repo: PhilipSkinner/elemental-lowcode


text:
Reduce binary size

The binary is really big (14mb), end users dont need debug symbols so we can omit these symbols.
https://github.com/xaionaro/documentation/blob/master/golang%2Freduce-binary-size.md
Adding ldflags -w -s. Seem to make a huge difference in the binary size. One example I saw was a 12mb bin that shrunk to 1 / 7 of the size by just omitting debug flags.

better to do this when it is more stable, omitting debug flags might be a bad idea during development

added -w -s flags to release target in makefile (strips debug symbols)

repo: Phillezi/kthcloud-cli


text:
Logs <0x0d> on the end of some digipeated packets

Many packets getting digipeated are logged with a carriage return at the end. Hopefully this isn't also getting appended to the transmitted packets.
2016-11-13 15:03:21.017 BALDI     R W7COA-9>TXQXPP,WIDE1-1,WIDE2-1:`2E!l!Aj/`"4l}_"
2016-11-13 15:03:21.018 VBALDI    T W7COA-9>TXQXPP,VBALDI*,WIDE2-1:`2E!l!Aj/`"4l}_"<0x0d>

How about this one? (No path specified in the originating station!!)
2016-11-16 01:04:19.662 W8VFR-8   R W8VFR-3>APRX28:/010418h3938.06NI08421.26W#33KM digigate
2016-11-16 01:04:19.665 W8VFR-8   T W8VFR-3>APRX28:/010418h3938.06NI08421.26W#33KM digigate

That is completely different. Please open a new PR and include any examples of what it does, how often, and your station configuration.

I want to be sure the station is actually transmitting this out to RF. It is a remote site on R-SSH, so access is no issue, but I can't verify RF from afar. PR=Pull Request???

Sorry. New Issue ticket, so this thread can stay on topic for the 0x0d logging issue. Problem Report is what we call them at work.

It looks like these are actually coming in on the Rx, and being preserved as the packet is being processed. They aren't showing up on the R logs since it uses a DIFFERENT TNC2 formatter than the T side: https://github.com/PhirePhly/aprx/blob/d3e006fd039db55c77bb7d0ba277197aad4c49d9/ax25.c#L242-L256
This issue seems to be specific to the BALDI station or the local network...

repo: PhirePhly/aprx


text:
Emerald block texture

With latest update blockcarpentry-1.16-0.3.7.jar
Emerald block texture has changed.

Oh nooo I did it again.... Accidentially included the debug texture in the release...  Sorry
Thanks for reporting!
Regards, Manu

Should be fixed with 0.3.8 :)

authors: PianoManu Sunekaer

repo: PianoManu/BlockCarpentry


text:
Upgrade Swagger 2.2.26 -> 2.2.27

This PR contains the following updates:

Package
Type
Update
Change

Swagger
compile
patch
2.2.26 -> 2.2.27

Release Notes

swagger-api/swagger-core (Swagger)
v2.2.27: Swagger-core 2.2.27 released!
Compare Source

fix: https://github.com/swagger-api/swagger-ui/issues/10220 (#4806)
Fix for record component annotations on fields with JsonProperty annotations (#4795)
Fix java.lang.NullPointerException and remove stack trace output from ModelResolver (#4793)
Move applySchemaResolution check to a method (#4791)
feat(gradle-plugin): enable lazy evaluation, implicit task dependencies and fixing setEncoding (#4761)

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade Swagger 2.2.26 -> 2.2.27

See:
- https://github.com/swagger-api/swagger-core/releases/tag/v2.2.27
- https://github.com/swagger-api/swagger-core/compare/v2.2.26...v2.2.27

repo: PicnicSupermarket/error-prone-support


text:
Torrents and magnets not loading when proxy enabled

Whenever i use a proxy server, doesn't matter which type in which used SOCKS5 (with credentials), all torrents or magnets added to PicoTorrent doesn't seem to load. At first i thought it might be my proxy settings, so i disabled them, as expected the torrents work (more or less; see explanation below). Then i tried adding them manually through the PicoTorrent interface itself, no success. Lastly i tried qBittorrent with the same proxy settings filled and enabled, the problem doesn't seem to exist with that client.
The only way i am able to convert back to a working PicoTorrent is by...:
1. ... emptying the credentials, type and uncheck all boxes in preferences (related to proxy).
2. ... close and go to "C:\Users\[username]\AppData\Local\PicoTorrent" and delete 'session.dat'.
I use the servers from NordVPN for my proxy (with credentials) over SOCKS5, in case it might make a difference. I added the log files, just in case.
Logs.zip

Thanks for the report - I'll have a look!

please stop emailing me notification.s
On Wed, Nov 16, 2016 at 3:10 PM, Viktor Elofsson notifications@github.com
wrote:

Thanks for the report - I'll have a look!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PicoTorrent/PicoTorrent/issues/360#issuecomment-261072819,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARIE-53fuuSu6Zh0yFqahuyF2A-r68fJks5q-3E7gaJpZM4K0dAO
.

@Tieria-Shirin If you do not want to be notified, change your 'Follow' settings for the repository,

authors: Tieria-Shirin rain2reign vktr

repo: PicoTorrent/PicoTorrent


text:
iOS Porcupine Issue:

I'm running a test in Xcode and keep coming up with this error:
:1:1 warning: umbrella header for module 'porcupine' does not include header 'pico voice.h'
#import "Headers/porcupine-umbrella.h"
I've added an image as well
Thoughts?

Update porcupine to latest (1.9.6) and you should no longer receive this warning.

authors: laves windowmirror

repo: Picovoice/porcupine


text:
issues while playing in adapter class when loading video and cannot release the video while back press on destroy

hi, I also have this issue with the release in the adapter class. where the video some time playing in the background even if after the back press. Sometimes a youtubeplayerview will show as an error occurred. please try again later in the video. also cannot set vedio in
public class TaskinclassAdapter extends RecyclerView.Adapter<TaskinclassAdapter.ViewHolder> {
String videoId;

Context context;
ArrayList<taskResponse>taskResponses;
public TaskinclassAdapter(Context context, ArrayList<taskResponse> taskresponse) {
    this.context=context;
    this.taskResponses=taskresponse;
}

@NonNull
@Override
public TaskinclassAdapter.ViewHolder onCreateViewHolder(@NonNull ViewGroup parent, int viewType) {
    View v= LayoutInflater.from(parent.getContext()).inflate(R.layout.taskdetailswithvedio,parent,false);
    TaskinclassAdapter.ViewHolder pvh = new TaskinclassAdapter.ViewHolder(v);
    return  pvh;
}

@Override
public void onBindViewHolder(@NonNull TaskinclassAdapter.ViewHolder holder, int position) {

taskResponse taskResponse = taskResponses.get(position);

holder.text_vedio_dec.setText(taskResponse.getDesc());

if (taskResponse.getUrl() == null) {
    holder.playerView.setVisibility(View.GONE);
} else {

    String vedio = taskResponse.getUrl();
    String[] vediofull_link = vedio.split("v=");
    videoId = vediofull_link[1];

    Log.d("string",videoId);

}

  // holder.playerView.getEnableAutomaticInitialization();
     holder.playerView.setEnableAutomaticInitialization(true);
     ProcessLifecycleOwner.get().getLifecycle().addObserver(holder.playerView);

      holder.playerView.addYouTubePlayerListener(new AbstractYouTubePlayerListener() {
        @Override
        public void onReady(@NonNull YouTubePlayer youTubePlayer) {

            youTubePlayer.loadVideo(videoId, 0);
        }

});
     holder.text_title.setText(taskResponse.getTitle());

}

@Override
public int getItemCount() {

    return taskResponses.size();
}

public  static class ViewHolder extends RecyclerView.ViewHolder {
    TextView text_title,text_vedio_dec;
     YouTubePlayerView playerView;
    public ViewHolder(@NonNull View itemView) {
        super(itemView);
         text_title=(TextView)itemView.findViewById(R.id.tasktitle);
         text_vedio_dec=(TextView)itemView.findViewById(R.id.textvediodec);
        playerView= (YouTubePlayerView)itemView.findViewById(R.id.youtube_player_view1);

    }
}

}

@PierfrancescoSoffritti can we change this bug


text:
some questions about GFLOPs and FPS

Hi, @PingoLH :
Thanks for all your Projects. I have tested your model on Jetson Nano and it works fast and accurate.
I have some questions:

Can I ask how do you calculate GFLOPs?
CenterNet-HarDNet85 is the most fast and accurate model in the tabel "Comparison with other state-of-the-art works"

, but why CenterNet-HarDNet85's FPS is similar to YOLOv4 when they run on Jetson Nano?
https://github.com/jkjung-avt/tensorrt_demos:Demo #5

(Maybe some details I didn’t notice.)
Thank you.

Hi,
Thanks for the feedback. GFLOPs was calculated by https://github.com/sovrasov/flops-counter.pytorch.
For 2, I think is because HarDNet still has a lot of concatenate operations, which still couldn't be optimized by TensorRT. Another minor difference is that HarDNet for Jetson was converted through onnx, while YOLOv4 for Jetson was built directly by DarkNet, which might give YOLOv4 a better optimization.

Hi, @PingoLH :
Thanks for your fast reply. I'll try to understand TensorRT's optimizations.
Thank you very much.

repo: PingoLH/CenterNet-HarDNet


text:
DMD load problems

First ,it seems that the model should be loaded as safetensors.Because no safetensors files in https://huggingface.co/PixArt-alpha/PixArt-Alpha-DMD-XL-2-512x512/tree/main.
pipe = PixArtAlphaPipeline.from_pretrained(
model_path,
subfolder="transformer",
torch_dtype=weight_dtype,
use_safetensors=False,
)
Besides, it seems that I can't load the PixArtAlphaPipeline somehow cause some config file missing.
OSError: Error no file named config.json found in directory /root/.cache/huggingface/hub/models--PixArt-alpha--PixArt-Alpha-DMD-XL-2-512x512/snapshots/57df7bb32daad69bc1d6c825a275935113802169.

The same error caught here.

OK. Let's fix it.

Fixed. Let's have a try. https://github.com/PixArt-alpha/PixArt-sigma/commit/2ba2f6efd4b5c6e922ecda04102ceba1430003ec

authors: EYcab chuck-ma lawrence-cj

repo: PixArt-alpha/PixArt-sigma


text:
Clicking on color.png file doesn't open Color Editor

Clicking on color.png file doesn't open Color Editor

This has been fixed.

license: MS-PL