Sign in with Google temporarily disabled for this app

When I try to login to the link given by gdrive list, I'm brought to a page stating
Sign in with Google temporarily disabled for this app

This app has not been verified yet by Google in order to use Google Sign In.

Same

Same !

same

Only Dev can do the verification, specifically the GDrive Dev (Petter Rasmussen). So this tool unusable until it's verification process completes.

Same here!

Same here

same here

update, actually this like worked for me
https://www.mynotepaper.com/mount-google-drive-using-gdrive-on-linux-server-with-own-oauth-credentials

Same here

Same

No need to compile from source, just create service account in google console and use --service-account option

No need to compile from source, just create service account in google console and use --service-account option

@yarkm13 can you help us with this? Any further information on how to make it works are very appreciated.

@yarkm13 @quangpham
Guide for those not compiling from source:

Create Service Account & Download the JSON Key. You can follow Offical Google Guide here: https://developers.google.com/identity/protocols/OAuth2ServiceAccount#creatinganaccount
Create GDrive Config directory (should be in ~/.gdrive or /home/MYUSERNAME/.gdrive)
Store JSON Key file in the GDrive Config directory (from Step 2) Tips: use easy name for JSON Key
Run command gdrive --service-account [YOUR JSON KEY NAME HERE] about to test connection
If error like this, follow the step 6-10. If error doesn't occur you can skip it:
Failed to get about: googleapi: Error 403: Access Not Configured. Drive API has not been used in project [PROJECT_ID] before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/drive.googleapis.com/overview?project=[PROJECT_ID] then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry., accessNotConfigured
You should go to https://console.developers.google.com/apis/api/drive.googleapis.com/overview?project=[PROJECT_ID] as instructed.
After Enabling API, you should create credentials for GDrive API by click Create Credentials, and choose Google Drive API from 'Which API are you using?' drop down list.
Choose Other UI from 'Where will you be calling the API from?' drop down list.
Choose User Data from 'What data will you be accessing?'
Click on 'What credentials do I need?' now you will be instructed to create OAuth Client ID (Next Step).
Choose Other, fill name for OAuth Client ID, then click Create. Done, just click Ok, no need to store Client ID or Secret.

Now the important bits is your Service Account have their own Google Drive space. This mean that if you upload file, it won't show up in your drive. To workaround this, your account need to create a shared folder with your service account email as the editor. See this Stackoverflow discussion: https://stackoverflow.com/questions/45492703/google-drive-api-oauth-and-service-account
Now to get the folder ID you can follow the tips from this blog: https://ploi.io/documentation/mysql/where-do-i-get-google-drive-folder-id
Use that folder id as parrent folder to store all of your files, and done! Your files now shows up!
IMPORTANT NOTE: There's an unmerged fix (#331) for changing ownership of files. For now GDrive util will throw error: 'Failed to share file: googleapi: Error 403: The transferOwnership parameter must be enabled when the permission role is 'owner'., forbidden'
This will results in the files uploaded is owned by your service account.
Hope this helps.

@quangpham i think @nathanaelytj has explained completely. I was done the same

My personal Google account have much more Google Drive storage limit than the Service Account  Free Google Drive space (16GB), is there any solution to link my personal account by Service Account OAuth?

Same issue. Any ETA when this is going to get fixed?

Duplicate of: https://github.com/gdrive-org/gdrive/issues/506

Issue still there. App still useless. The service account doesn't have enough space.

@JurajMa create directory in your main account and share it with service account email address. Now you need to point your service account to work with that directory.

@yarkm13 @quangpham
Guide for those not compiling from source:

Create Service Account & Download the JSON Key. You can follow Offical Google Guide here: https://developers.google.com/identity/protocols/OAuth2ServiceAccount#creatinganaccount
Create GDrive Config directory (should be in ~/.gdrive or /home/MYUSERNAME/.gdrive)
Store JSON Key file in the GDrive Config directory (from Step 2) Tips: use easy name for JSON Key
Run command gdrive --service-account [YOUR JSON KEY NAME HERE] about to test connection
If error like this, follow the step 6-10. If error doesn't occur you can skip it:
Failed to get about: googleapi: Error 403: Access Not Configured. Drive API has not been used in project [PROJECT_ID] before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/drive.googleapis.com/overview?project=[PROJECT_ID] then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry., accessNotConfigured
You should go to https://console.developers.google.com/apis/api/drive.googleapis.com/overview?project=[PROJECT_ID] as instructed.
After Enabling API, you should create credentials for GDrive API by click Create Credentials, and choose Google Drive API from 'Which API are you using?' drop down list.
Choose Other UI from 'Where will you be calling the API from?' drop down list.
Choose User Data from 'What data will you be accessing?'
Click on 'What credentials do I need?' now you will be instructed to create OAuth Client ID (Next Step).
Choose Other, fill name for OAuth Client ID, then click Create. Done, just click Ok, no need to store Client ID or Secret.

Now the important bits is your Service Account have their own Google Drive space. This mean that if you upload file, it won't show up in your drive. To workaround this, your account need to create a shared folder with your service account email as the editor. See this Stackoverflow discussion: https://stackoverflow.com/questions/45492703/google-drive-api-oauth-and-service-account
Now to get the folder ID you can follow the tips from this blog: https://ploi.io/documentation/mysql/where-do-i-get-google-drive-folder-id
Use that folder id as parrent folder to store all of your files, and done! Your files now shows up!
IMPORTANT NOTE: There's an unmerged fix (#331) for changing ownership of files. For now GDrive util will throw error: 'Failed to share file: googleapi: Error 403: The transferOwnership parameter must be enabled when the permission role is 'owner'., forbidden'
This will results in the files uploaded is owned by your service account.
Hope this helps.

if follow this step, but command gdrive --service-account will throw an error like this
No valid arguments given, use 'gdrive help' to see available commands
how to solved it?

same issue as @hikmawanaz

same problem

@nathanaelytj
On step 10 I first need to set up "OAuth consent screen", and only after this I can create OAuth Client ID. But obviously, I can't do it because it requires organization / website / verification from google / etc. How can I avoid this?

@yarkm13 @quangpham
Guide for those not compiling from source:

Create Service Account & Download the JSON Key. You can follow Offical Google Guide here: https://developers.google.com/identity/protocols/OAuth2ServiceAccount#creatinganaccount
Create GDrive Config directory (should be in ~/.gdrive or /home/MYUSERNAME/.gdrive)
Store JSON Key file in the GDrive Config directory (from Step 2) Tips: use easy name for JSON Key
Run command gdrive --service-account [YOUR JSON KEY NAME HERE] about to test connection
If error like this, follow the step 6-10. If error doesn't occur you can skip it:
Failed to get about: googleapi: Error 403: Access Not Configured. Drive API has not been used in project [PROJECT_ID] before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/drive.googleapis.com/overview?project=[PROJECT_ID] then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry., accessNotConfigured
You should go to https://console.developers.google.com/apis/api/drive.googleapis.com/overview?project=[PROJECT_ID] as instructed.
After Enabling API, you should create credentials for GDrive API by click Create Credentials, and choose Google Drive API from 'Which API are you using?' drop down list.
Choose Other UI from 'Where will you be calling the API from?' drop down list.
Choose User Data from 'What data will you be accessing?'
Click on 'What credentials do I need?' now you will be instructed to create OAuth Client ID (Next Step).
Choose Other, fill name for OAuth Client ID, then click Create. Done, just click Ok, no need to store Client ID or Secret.

Now the important bits is your Service Account have their own Google Drive space. This mean that if you upload file, it won't show up in your drive. To workaround this, your account need to create a shared folder with your service account email as the editor. See this Stackoverflow discussion: https://stackoverflow.com/questions/45492703/google-drive-api-oauth-and-service-account
Now to get the folder ID you can follow the tips from this blog: https://ploi.io/documentation/mysql/where-do-i-get-google-drive-folder-id
Use that folder id as parrent folder to store all of your files, and done! Your files now shows up!
IMPORTANT NOTE: There's an unmerged fix (#331) for changing ownership of files. For now GDrive util will throw error: 'Failed to share file: googleapi: Error 403: The transferOwnership parameter must be enabled when the permission role is 'owner'., forbidden'
This will results in the files uploaded is owned by your service account.
Hope this helps.

if follow this step, but command gdrive --service-account will throw an error like this
No valid arguments given, use 'gdrive help' to see available commands
how to solved it?

@hikmawanaz I found that the brew installation didn't have the --service-account global options available to it, but it did if I downloaded the binary and used that instead.
Once you'd uploaded files using a service account, how do you then pass ownership to your normal user account? I find it a bit odd having the owner and a service account.

@joemidi first create dir in your service account
./gdrive --service-account gdrive.json mkdir DIR_NAME

get object id of that dir
gdrive --service-account gdrive.json list

and grant permissions for your root account to that dir
gdrive --service-account gdrive.json share --role writer --type user --email 'YOUR_ACCOUNT_EMAIL' DIR_OBJECT_ID

Dont forget to setup sync to that dir, not in root
gdrive --service-account gdrive.json sync upload LOCAL_DIR_TO_UPLOAD DIR_OBJECT_ID --delete-extraneous

Bonus: wou will have extra 15Gb space on Google Drive (data stored by service account will not count in your root account)

@joemidi first create dir in your service account
./gdrive --service-account gdrive.json mkdir DIR_NAME

get object id of that dir
gdrive --service-account gdrive.json list

and grant permissions for your root account to that dir
gdrive --service-account gdrive.json share --role writer --type user --email 'YOUR_ACCOUNT_EMAIL' DIR_OBJECT_ID

Dont forget to setup sync to that dir, not in root
gdrive --service-account gdrive.json sync upload LOCAL_DIR_TO_UPLOAD DIR_OBJECT_ID --delete-extraneous

Bonus: wou will have extra 15Gb space on Google Drive (data stored by service account will not count in your root account)

But doesn't this mean the folder I created is owned by the service account?

@joemidi according to gdrive help you also can grant owner role
./gdrive help share
Share file or directory
gdrive [global] share [options] <fileId>

global:
  -c, --config <configDir>             Application path, default: ~/.gdrive
  --refresh-token <refreshToken>       Oauth refresh token used to get access token (for advanced users)
  --access-token <accessToken>         Oauth access token, only recommended for short-lived requests because of short lifetime (for advanced users)
  --service-account <serviceAccount>   Oauth service account filename, used for server to server communication without user interaction (filename path is relative to config dir)

options:
  --role <role>       Share role: owner/writer/commenter/reader, default: reader
  --type <type>       Share type: user/group/domain/anyone, default: anyone
  --email <email>     The email address of the user or group to share the file with. Requires 'user' or 'group' as type
  --domain <domain>   The name of Google Apps domain. Requires 'domain' as type
  --discoverable      Make file discoverable by search engines
  --revoke            Delete all sharing permissions (owner roles will be skipped)

@joemidi alo i think you can go opposite way: create directory in your root account and than grant permissions to it for service account. But I haven't tested that

@yarkm13 Yes, I ended up doing it this way, you can just share the folder via the web UI, the folder is my own ownership but each file is created by the service account.
I did notice that owner role was available on gdrive share but it seems like it needs PR https://github.com/gdrive-org/gdrive/pull/331 to be complete due to an error message
Failed to share file: googleapi: Error 403: The transferOwnership parameter must be enabled when the permission role is 'owner'., forbidden

I forked this repository to https://github.com/ntechp/gdrive, merge gdrive-org#513, gdrive-org#270, gdrive-org#331
Download the merged source, build it with Go Lang Docker (https://hub.docker.com/_/golang). Use command docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:latest go build -v
All is in this non-official release note: https://github.com/ntechp/gdrive/releases/tag/2.1.0-0.0.1
and the binary goes: https://github.com/ntechp/gdrive/releases/download/2.1.0-0.0.1/gdrive-linux64
This fork temporarily fixes 3 probs:

The OAuth Problem.
The negative number for unlimited space for GSuite users.
The transferOwnership Problem.

I do hope someone maintain this repository, merge all the fixes (because some of the issues already fixed by community), and update the release.

@yarkm13 @quangpham
Guide for those not compiling from source:

Create Service Account & Download the JSON Key. You can follow Offical Google Guide here: https://developers.google.com/identity/protocols/OAuth2ServiceAccount#creatinganaccount
Create GDrive Config directory (should be in ~/.gdrive or /home/MYUSERNAME/.gdrive)
Store JSON Key file in the GDrive Config directory (from Step 2) Tips: use easy name for JSON Key
Run command gdrive --service-account [YOUR JSON KEY NAME HERE] about to test connection
If error like this, follow the step 6-10. If error doesn't occur you can skip it:
Failed to get about: googleapi: Error 403: Access Not Configured. Drive API has not been used in project [PROJECT_ID] before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/drive.googleapis.com/overview?project=[PROJECT_ID] then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry., accessNotConfigured
You should go to https://console.developers.google.com/apis/api/drive.googleapis.com/overview?project=[PROJECT_ID] as instructed.
After Enabling API, you should create credentials for GDrive API by click Create Credentials, and choose Google Drive API from 'Which API are you using?' drop down list.
Choose Other UI from 'Where will you be calling the API from?' drop down list.
Choose User Data from 'What data will you be accessing?'
Click on 'What credentials do I need?' now you will be instructed to create OAuth Client ID (Next Step).
Choose Other, fill name for OAuth Client ID, then click Create. Done, just click Ok, no need to store Client ID or Secret.

Now the important bits is your Service Account have their own Google Drive space. This mean that if you upload file, it won't show up in your drive. To workaround this, your account need to create a shared folder with your service account email as the editor. See this Stackoverflow discussion: https://stackoverflow.com/questions/45492703/google-drive-api-oauth-and-service-account
Now to get the folder ID you can follow the tips from this blog: https://ploi.io/documentation/mysql/where-do-i-get-google-drive-folder-id
Use that folder id as parrent folder to store all of your files, and done! Your files now shows up!
IMPORTANT NOTE: There's an unmerged fix (#331) for changing ownership of files. For now GDrive util will throw error: 'Failed to share file: googleapi: Error 403: The transferOwnership parameter must be enabled when the permission role is 'owner'., forbidden'
This will results in the files uploaded is owned by your service account.
Hope this helps.

Thanks for this useful guide !
gdrive --service-account [YOUR JSON KEY NAME HERE] about command provides a positive return.
I also created dir in my service account and grant permissions for a root account to that dir, but unfortunately the issue remains : authentication needed when I launch any other gdrive command command (for ex  : gdrive upload picture.png).
Have I forgotten something ?

For my case, each service account is limited to 16GB only. So I wasn't entitled to the unlimited quota of the Gsuite account.

@joemidi first create dir in your service account
./gdrive --service-account gdrive.json mkdir DIR_NAME

get object id of that dir
gdrive --service-account gdrive.json list

and grant permissions for your root account to that dir
gdrive --service-account gdrive.json share --role writer --type user --email 'YOUR_ACCOUNT_EMAIL' DIR_OBJECT_ID

Dont forget to setup sync to that dir, not in root
gdrive --service-account gdrive.json sync upload LOCAL_DIR_TO_UPLOAD DIR_OBJECT_ID --delete-extraneous

Bonus: wou will have extra 15Gb space on Google Drive (data stored by service account will not count in your root account)

Thanks, it solved my problem

I forked this repository to https://github.com/ntechp/gdrive, merge #513, #270, #331
Download the merged source, build it with Go Lang Docker (https://hub.docker.com/_/golang). Use command docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp golang:latest go build -v
All is in this non-official release note: https://github.com/ntechp/gdrive/releases/tag/2.1.0-0.0.1
and the binary goes: https://github.com/ntechp/gdrive/releases/download/2.1.0-0.0.1/gdrive-linux64
This fork temporarily fixes 3 probs:

The OAuth Problem.
The negative number for unlimited space for GSuite users.
The transferOwnership Problem.

I do hope someone maintain this repository, merge all the fixes (because some of the issues already fixed by community), and update the release.

This method do help me. Thank you very much!

gdrive --service-account creds.json about properly shows my account information, but upon trying gdrive upload command, it prompt me to open an URL which redirect me to login into my account and halted by Sign in with Google temporarily disabled for this app again
Anything I missed?

I feel overwhelmed by all the steps required to make this work... and all the reports of failure just make me postpone it even more, mainly considering I can't even compile it. The "go" compiler wont accept anything I type, yes I am a "go noob", what is the "go" compile command, as the one at readme.md wont work :(, yes I installed the go-lang package.
So my question is, Why not just fix this:
Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.
I mean, why not we join forces and beg google to verify this app!!!
Anyone knows how to do that? yes, the begging part...
I mean, this app is great and should work "out of the box" and not require all these steps from noobs like me :/.

@AquariusPower I gave up on gdrive and switched to rclone.
Much easier to setup with service account

@skeith
yeah, I am thinking on that too, as we dont know when gdrive will be properly fixed.
There are 4 or 5 alternatives to gdrive.
I wanted gdrive because I made a script that 100% depends on it to do many things,
but may be I can replace it (and may be even what my script does with some other app).
thx on the tip :)

I mean, why not we join forces and beg google to verify this app!!!
Anyone knows how to do that? yes, the begging part...

It's not a google problem. The developer needs to initiate the verification.   The result is that "join forces" boils down to someone forking the project (several have done so already) and paying the fee.
Without someone paying the fee, you'll have to do everything to "become the developer" yourself (because you don't have to pay the fee if you're only using it yourself)

@AquariusPower

I mean, why not we join forces and beg google to verify this app!!!
Anyone knows how to do that? yes, the begging part...

It's not a google problem. The developer needs to initiate the verification. The result is that "join forces" boils down to someone forking the project (several have done so already) and paying the fee.
Without someone paying the fee, you'll have to do everything to "become the developer" yourself (because you don't have to pay the fee if you're only using it yourself)

How much is the fee 😓

Offering my few cents :relaxed:

For joining forces, I agree we as developers/contributors should join forces but we need to think who is responsible for controlling and handling user data through publicly Google verified app? Since anyone controlling the publicly Google verified app can theoretically access your entire Drive contents. Without clear definition of who's responsible for controlling and handling the publicly Google verified app, this app will become wetland for abuse.

Google recently tighten the verification procedure for any public app that request some Google API.

If your public application uses scopes that permit access to certain user data, it must complete a verification process. If you see unverified app on the screen when testing your application, you must submit a verification request to remove it. Find out more about unverified apps and get answers to frequently asked questions about app verification in the Help Center.
From: https://developers.google.com/identity/protocols/oauth2/scopes

And requesting verification is free. The problem lies in creating App Home Page, App Privacy Policy, App Term of Service (App Term of Service marked as Optional by Google). Those legal things need to be present and tailored to fulfill Google Requirements before the app marked as verified.

For fee part, this program actually licensed under MIT: LICENSE and if you read the LICENSE, you can see that you can do what you want in the application as long as you keep the notice. So, no fee. Though it's more of ethical side of things to ask for permission first if someone want to make it official that they take over app maintenance, development and do official releases.

Try backuptogoogle to compile gdrive with your own Google credential and auto backup on your server.

    gdrive version
    gdrive: 2.1.0
    Golang: go1.6
    OS/Arch: linux/amd64

I'm still unable to get the gdrive --service-account key.json about  working
I Still get the error No valid arguments given, use 'gdrive help' to see available commands

I believe this issue has been fixed 2021-05-28 and should be closed.
Quoting the current README:

News
28.05.2021
gdrive is finally verified for using sensitive scopes which should fix the This app is blocked error. Note that the project name will show up as project-367116221053 when granting access to you account. (I don't dare to change any more settings in the google console.)


check_id() function returns True even when "fabric-ca-client identity list" request fails

This is the main reason why most of the integration test fails and have to be repeated. When CA server is not yet ready it sends a 503 error for the command fabric-ca-client identity list but still the function check_id() returns true.

It's a mistake it is in the right way. Problem is somewhere else


Fix Release folder not being created

@samuel100u Please provide more information when you create PR.
For example,
[Issue]: what the problem is ( with steps to reproduce)
[Solution]: how you fix
[Test]: how to test

@samuel100u You don't need to worry about the "Release" folder.
If you succeed to finish the build, then you will see "_deps" folder and it will contain all the outputs.

don't need to worry about the "Release" folder.
If you succeed to finish the build, then you will see "_deps" folder and it wi

yes, but the "Release" file is not a folder.

@samuel100u Thanks for the PR.  It was merged in 4f0384ece28aa25e0cb01cc76eb9ca1ef64ca297. Had to do some slight formatting changes to pass lint.


Fix ci.yml for applicationinsights

I had two errors that I'm hoping to fix in this PR. The first is an extra ci.yml file that is no longer required (and was broken anyway) and the azure-applicationinsights module missing from the targetting string. The build is failing because of lack of code coverage results. This might fix it, although its probably just masking an issue of not handling no code coverage results gracefully (in mgmt scenarios I suspect).

Can one of the admins verify this patch?

OK, this fixes the python - applicationinsights - ci pipeline. By making sure that the client library builds as well as the management library we get some code coverage emitted. It doesn't fix the situation where code coverage missing causes the pipelines to fail, but we wouldn't have noticed if I had the ci.yml file for this setup correctly ;)

Slipped another change in to this PR. I noticed that multiple CG jobs were getting injected during the build and we already had it explicitly in the Analyze step so I've disabled it via a global (still runs in the job we explicitly include it in). We don't see it in the PRs, but we do with manually triggered CI.

@scbedd could you merge this for me?


Visual Studio 2019 - Extension installing failed.

I liked what you did and I wanted to try it, but the installation failed in Visual Studio 2019 Professional, I hope you can fix it or make another installer for 2019 Studio. Thank.
Cutted stack-trace:
6/17/2019 3:35:41 PM - Searching for applicable products...
6/17/2019 3:35:41 PM - Found installed product - Global Location
6/17/2019 3:35:41 PM - Found installed product - Visual Studio Build Tools 2017
6/17/2019 3:35:41 PM - Found installed product - Visual Studio Professional 2019
6/17/2019 3:35:41 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
   at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData)
   at VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported)
   at VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported)
   at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
   at VSIXInstaller.App.Initialize()
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

+1. Pleasu, update support for new studio version

last update of the nuget package is 2018.... this seems dead.

Hello guys,
Ammy is not actively maintained anymore. I can upgrade the extension if anyone still needs it. You should also be able to do that yourself pretty easily. Just install Nemerle and build Ammy.sln. You'll need to modify https://github.com/AmmyUI/AmmyUI/blob/master/src/IDE/Ammy.VisualStudio/source.extension.vsixmanifest for 2019 support.

Aside from VS 2019 support, is it possible to use it with VS code?

@Odepax No, it's not possible.

Dear Ionoy, please pay some attention to the project! It's so interesting, but sink in previous era of VS2017. Now already VS2022 is available, but no hope we can use Ammy there. :(


fix: Always provide firstIndex and totalItemsCount in collection result

The firstIndex and totalItemsCount properties are used in the Table and Cards components. The properties are needed for renderAriaLive announcements and to assign aria-rowcount and aria-rowindex. While the latter can be omitted when there is no pagination, the live announcements are important regardless because those include the change of the total items count when filtering.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

lgtm, pending comment offline about checking impact of interface changes

Checked for the possible impact - no failed packages.


Resolve version specific collection IDs

cc @constantinpape

I tried model_description = bioimageio.core.load_description("diplomatic-bug/staged/1") here, but it still fails.
Let me know once it's ready to be tested @FynnBe?

@constantinpape  should all work now


Filtering include

What this PR does / why we need it:
Backup can be customized with a number of resource filtering options.
This commit includes code to support all types of "include" filtering:

namespace include
resource type include – in this case a the plugin verifies that backed
up resources can be restored. It fails the backup if the included
resources are not enough for a successful restore
selector includes – in this case the plugin adds to backup all objects
that are necessary for a successful restore.

Special notes for your reviewer:
Release note:

NONE

/test pull-kvp-unit-test


feat!: upgrade to Slonik v33

Adds compatibility to Slonik 33.x.y.
BREAKING CHANGE: Due to the API surface changes in Slonik 33, this library will not be backwards compatible with previous Slonik versions.

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update build instructions in README

Call out nvm use to lock Node. version
Switch to NPM instead of Yarn
Whatever else @dayhaysoos says we do for real, reflect in instructions

outdated


Help to run the flow

Hello colleagues.
I'm trying to lift collector. But I'm having a problem and some doubts with the points mentioned here.
1- kafka_broker_host: kafka-host.fqdn.com what can we put in this field in a simple and functional way could it be <IP_ADDRESS>?
2- set_label=bdr1.neptunenetworks.org what we can also put in this field could be none ?
3- KAFKA_ADVERTISED_LISTENERS: INSIDE://:19092,OUTSIDE://kafka.fqdn.com:9092 at this point would the same indication <IP_ADDRESS> be relevant if that were the case?
Log in after the bgp connection is established.
Sep 20 21:41:16 traffic-flow pmacctd[467]: INFO ( default/core/BGP ): [<IP_ADDRESS>] BGP connection reset by peer (0).
Sep 20 21:41:16 traffic-flow pmacctd[467]: INFO ( default_kafka/kafka ): *** Purging cache - START (PID: 9631) ***
Sep 20 21:41:17 traffic-flow pmacctd[467]: INFO ( default/core/BGP ): [<IP_ADDRESS>] BGP peers usage: 1/2
Sep 20 21:41:17 traffic-flow pmacctd[467]: INFO ( default/core/BGP ): [<IP_ADDRESS>] Capability: 4-bytes AS [41] ASN [26xx9]
Sep 20 21:41:17 traffic-flow pmacctd[467]: INFO ( default/core/BGP ): [<IP_ADDRESS>] Capability: MultiProtocol [1] AFI [1] SAFI [1]
Sep 20 21:41:17 traffic-flow pmacctd[467]: INFO ( default/core/BGP ): [<IP_ADDRESS>] BGP_OPEN: Local AS: 26xx9 Remote AS: 26xx9 HoldTime: 90
Sep 20 21:41:21 traffic-flow pmacctd[467]: INFO ( default_kafka/kafka ): *** Purging cache - START (PID: 9635) ***
Sep 20 21:41:22 traffic-flow pmacctd[467]: ERROR ( default_kafka/kafka ): Connection failed to Kafka: p_kafka_check_outq_len()
Sep 20 21:41:22 traffic-flow pmacctd[467]: ERROR ( default_kafka/kafka ): Connection failed to Kafka: p_kafka_close()
Sep 20 21:41:22 traffic-flow pmacctd[467]: INFO ( default_kafka/kafka ): *** Purging cache - END (PID: 9631, QN: 1416/1416, ET: 0) ***
Sep 20 21:41:26 traffic-flow pmacctd[467]: INFO ( default_kafka/kafka ): *** Purging cache - START (PID: 9639) ***

My error was in /etc/pmacct/peering_agent.map
The ip was wrong. Now I have an output equal to the one reported in the example after installation.
Exit:
{"event_type": "purge", "label": "<IP_ADDRESS>", "as_src": 26xx9, "as_dst": 0, "ip_src":
{"event_type": "purge", "label": "<IP_ADDRESS>", "as_src": 0, "as_dst": 26xx9, "ip_src":
I see the "zero" in evidence for as_src and as_dst even though I'm changing helping the bgp_agent_map.


chore: increase e2e test timeout

Increasing the timeout for e2e test which always fails during the release job - https://apm-ci.elastic.co/job/apm-agent-rum/job/elastic-synthetics/job/master/138/console

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #234 opened

Start Time: 2021-03-02T16:08:01.506+0000

Duration: 10 min 7 sec

Commit: 0322382e54332e433572b672dfd9f823094c6961

Test stats :test_tube:

Test
Results

Failed
0

Passed
67

Skipped
0

Total
67

Trends :test_tube:

Steps errors
Expand to view the steps failures

run e2e tests

Took 4 min 32 sec . View more details on here
Description: npm run test

Log output
Expand to view the last 100 lines of log output

[2021-03-02T16:14:37.285Z]
[2021-03-02T16:14:37.285Z] + STACK_VERSION=7.10.0
[2021-03-02T16:14:37.285Z] + docker-compose --file docker-compose.yml up --remove-orphans
[2021-03-02T16:14:37.285Z] + '[' -z https://apm-ci.elastic.co/ ']'
[2021-03-02T16:14:37.285Z] + SLEEP_TIME=10
[2021-03-02T16:14:37.285Z] + echo ''
[2021-03-02T16:14:37.285Z]
[2021-03-02T16:14:37.285Z] + echo 'Waiting for synthetics docker to start...'
[2021-03-02T16:14:37.285Z] Waiting for synthetics docker to start...
[2021-03-02T16:14:37.285Z] ++ docker inspect -f '{{.State.Running}}' synthetics
[2021-03-02T16:14:37.285Z] Error: No such object: synthetics
[2021-03-02T16:14:37.546Z] + '[' '' == true ']'
[2021-03-02T16:14:37.546Z] + sleep 10
[2021-03-02T16:14:47.547Z] ++ docker inspect -f '{{.State.Running}}' synthetics
[2021-03-02T16:14:47.547Z] Error: No such object: synthetics
[2021-03-02T16:14:47.547Z] + '[' '' == true ']'
[2021-03-02T16:14:47.547Z] + sleep 10
[2021-03-02T16:14:57.549Z] ++ docker inspect -f '{{.State.Running}}' synthetics
[2021-03-02T16:14:57.549Z] Error: No such object: synthetics
[2021-03-02T16:14:57.549Z] + '[' '' == true ']'
[2021-03-02T16:14:57.549Z] + sleep 10
[2021-03-02T16:15:07.549Z] ++ docker inspect -f '{{.State.Running}}' synthetics
[2021-03-02T16:15:07.809Z] Error: No such object: synthetics
[2021-03-02T16:15:07.809Z] + '[' '' == true ']'
[2021-03-02T16:15:07.809Z] + sleep 10
[2021-03-02T16:15:17.818Z] ++ docker inspect -f '{{.State.Running}}' synthetics
[2021-03-02T16:15:17.818Z] Error: No such object: synthetics
[2021-03-02T16:15:17.818Z] + '[' '' == true ']'
[2021-03-02T16:15:17.818Z] + sleep 10
[2021-03-02T16:15:27.820Z] ++ docker inspect -f '{{.State.Running}}' synthetics
[2021-03-02T16:15:28.401Z] + '[' true == true ']'
[2021-03-02T16:15:28.401Z] + echo '✅ Setup completed successfully. Running e2e tests...'
[2021-03-02T16:15:28.401Z] ✅ Setup completed successfully. Running e2e tests...
[2021-03-02T16:15:28.401Z] + npx @elastic/synthetics uptime.journey.ts
[2021-03-02T16:15:30.341Z] Waiting for Elastic Search  to start
[2021-03-02T16:16:17.251Z] Waiting for Synthetics to send data to ES for test monitor
[2021-03-02T16:16:56.185Z] Waiting for kibana server to start
[2021-03-02T16:16:56.185Z]
[2021-03-02T16:16:56.185Z] Journey: E2e test synthetics
[2021-03-02T16:16:56.185Z]    ✓  Step: 'Go to kibana uptime app' succeeded (480 ms)
[2021-03-02T16:18:03.995Z]    ✖  Step: 'Check if there is table data' failed (65761 ms)
[2021-03-02T16:18:03.995Z]    ---
[2021-03-02T16:18:03.995Z]       stack: |-
[2021-03-02T16:18:03.995Z]         page.click: Timeout 60000ms exceeded.
[2021-03-02T16:18:03.995Z]         =========================== logs ===========================
[2021-03-02T16:18:03.995Z]         waiting for selector "[data-test-subj=superDatePickerApplyTimeButton]"
[2021-03-02T16:18:03.995Z]         ============================================================
[2021-03-02T16:18:03.995Z]         Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.:
[2021-03-02T16:18:03.995Z]             at Connection.sendMessageToServer (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/node_modules/playwright-chromium/lib/client/connection.js:69:15)
[2021-03-02T16:18:03.995Z]             at Proxy.<anonymous> (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/node_modules/playwright-chromium/lib/client/channelOwner.js:44:61)
[2021-03-02T16:18:03.995Z]             at /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/node_modules/playwright-chromium/lib/client/frame.js:257:40
[2021-03-02T16:18:03.995Z]             at Frame._wrapApiCall (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/node_modules/playwright-chromium/lib/client/channelOwner.js:72:34)
[2021-03-02T16:18:03.996Z]             at Frame.click (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/node_modules/playwright-chromium/lib/client/frame.js:256:21)
[2021-03-02T16:18:03.996Z]             at /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/node_modules/playwright-chromium/lib/client/page.js:406:60
[2021-03-02T16:18:03.996Z]             at Page._attributeToPage (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/node_modules/playwright-chromium/lib/client/page.js:205:20)
[2021-03-02T16:18:03.996Z]             at Page.click (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/node_modules/playwright-chromium/lib/client/page.js:406:21)
[2021-03-02T16:18:03.996Z]             at refreshUptimeApp (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/src/github.com/elastic/synthetics/__tests__/e2e/uptime.journey.ts:38:18)
[2021-03-02T16:18:03.996Z]             at runNextTicks (internal/process/task_queues.js:58:5)
[2021-03-02T16:18:03.996Z]    ---
[2021-03-02T16:18:03.996Z]
[2021-03-02T16:18:03.996Z]    -  Step: 'Click on my monitor' skipped (0 ms)
[2021-03-02T16:18:03.996Z]    -  Step: 'It navigates to details page' skipped (0 ms)
[2021-03-02T16:18:03.996Z]
[2021-03-02T16:18:03.996Z]  1 passed 1 failed 2 skipped (152958 ms)
[2021-03-02T16:18:03.996Z]
[2021-03-02T16:18:03.996Z] npm ERR! code ELIFECYCLE
[2021-03-02T16:18:03.996Z] npm ERR! errno 1
[2021-03-02T16:18:03.996Z] npm ERR! e2e-synthetics@ test: `npm i && npm run setup &&  bash scripts/test.sh`
[2021-03-02T16:18:03.996Z] npm ERR! Exit status 1
[2021-03-02T16:18:03.996Z] npm ERR!
[2021-03-02T16:18:03.996Z] npm ERR! Failed at the e2e-synthetics@ test script.
[2021-03-02T16:18:03.996Z] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[2021-03-02T16:18:03.996Z]
[2021-03-02T16:18:03.996Z] npm ERR! A complete log of this run can be found in:
[2021-03-02T16:18:03.996Z] npm ERR!     /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234/.npm/_logs/2021-03-02T16_18_01_330Z-debug.log
[2021-03-02T16:18:05.323Z] Stage "Publish Docker image" skipped due to earlier failure(s)
[2021-03-02T16:18:05.493Z] Stage "Matrix - STACK_VERSION = '8.0.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:05.503Z] Stage "Matrix - STACK_VERSION = '7.10.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:05.512Z] Stage "Matrix - STACK_VERSION = '7.11.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:05.597Z] Stage "Matrix - STACK_VERSION = '8.0.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:05.611Z] Stage "Matrix - STACK_VERSION = '7.10.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:05.620Z] Stage "Matrix - STACK_VERSION = '7.11.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:05.823Z] Stage "Matrix - STACK_VERSION = '8.0.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:05.835Z] Stage "Matrix - STACK_VERSION = '7.10.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:05.845Z] Stage "Matrix - STACK_VERSION = '7.11.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:06.056Z] Stage "Matrix - STACK_VERSION = '8.0.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:06.071Z] Stage "Matrix - STACK_VERSION = '7.10.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:06.080Z] Stage "Matrix - STACK_VERSION = '7.11.0-synthetics'" skipped due to earlier failure(s)
[2021-03-02T16:18:06.385Z] Failed in branch Matrix - STACK_VERSION = '8.0.0-synthetics'
[2021-03-02T16:18:06.403Z] Failed in branch Matrix - STACK_VERSION = '7.10.0-synthetics'
[2021-03-02T16:18:06.416Z] Failed in branch Matrix - STACK_VERSION = '7.11.0-synthetics'
[2021-03-02T16:18:06.621Z] Stage "Release" skipped due to earlier failure(s)
[2021-03-02T16:18:06.674Z] Stage "Release" skipped due to earlier failure(s)
[2021-03-02T16:18:06.784Z] Stage "Release" skipped due to earlier failure(s)
[2021-03-02T16:18:07.179Z] Running on Jenkins in /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-234
[2021-03-02T16:18:07.294Z] [INFO] getVaultSecret: Getting secrets
[2021-03-02T16:18:07.543Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-03-02T16:18:08.500Z] + chmod 755 generate-build-data.sh
[2021-03-02T16:18:08.500Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-234/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-234/runs/1 FAILURE 606715
[2021-03-02T16:18:08.751Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-rum/elastic-synthetics/PR-234/runs/1/steps/?limit=10000 -o steps-info.json

@shahzad31 Do you know if these attributes changed?


Replaced wikipedia descriptions with distrowatch descriptions

I replaced the wikipedia descriptions of the distros with distrowatch descriptions.
The Debian one contained two very general sentences about linux, which I decided to remove (marked as '[...]').

Thanks! Fixes #8


CXF-7371: use objectweb-asm to extract parameter-names from the debug-info of the service-class

Suggested fix for https://issues.apache.org/jira/browse/CXF-7371.

Please only submit pull requests based on master unless it only effects a particular branch, and only submit a single pull request.   Since this based on 3.1.x, please close this.


Typescript definitions: TextFieldComponent missing in DateTextFieldProps

Environment

Tech
Version

material-ui-pickers
1.0.0-rc.2

material-ui
1.0.0-beta.35

React
16.2.0

Browser
Any

Platform
Any

Steps to reproduce
This snippet will return an error in TypeScript:
<DateTimePicker TextFieldComponent={() =>

}  />
Expected behavior
DatetimePicker should have this property exposed
Actual behavior
Missing property (might be more than that, I'm just trying to use this one for now)

Would you like to open a PR?

Never done that before, but I'll try!

Fixed in rc-3


Add Docker Support

Add Docker support to streamline development and deployment. This will include a Dockerfile for the application and a docker-compose.yml for local development.

This was closed with pull-request #19


[debug] Variables with null values are not displayed.

VSCode Version: 1.4
OS Version: All

When a debug adapter returns Variables with value: null, they are not displayed in the variables viewlet.
However, this is a legitimate situation in some cases:

For compound objects, there may not a useful information to return as a value of the container itself (Okay, this may be worked around by returning some canned string such as "<object>")
Primitive types may also lack values if, e.g. one is debugging an optimized build.  Here, returning a canned string is more problematic, because VSCode will allow editing it and will try storing it back.

IMO, null-valued variables should still be displayed.

@isidorn let's discuss this.

@weinand I think github accidently closed this issue by you pushing a revert of the fix -> reopening

This works for me in latest, in the screenshot you can see that I modified the debug adapter to return null for variable values and they are all nicely displayed.
@vadimcn let me know if you can still reproduce this with latest


App Usage Module

Tracks launches and quits of applications. Uses crankd for tracking.

Removed crankd installation from module

I got this error:
Server An error occurred while processing: Appusage_model
Server Error: DateTime::__construct(): Failed to parse time string (@/Applications/Zotero.app) at position 0 (@): Unexpected character

not sure why?

CREATE TABLE application_usage (event TEXT,bundle_id TEXT,app_version TEXT,app_path TEXT,last_time INTEGER DEFAULT 0,number_times INTEGER DEFAULT 0,PRIMARY KEY (event, bundle_id));```

Thanks! I'm going to add some changes to get the last bugs out.


add related note with pod deleted

add job application has some error and restartPolicy is not Nerver pod will be delete note
https://github.com/kubernetes/kubernetes/issues/78644

/assign @bradtopol

/lgtm
/approve


hostslt list do not work

test link https://raw.githubusercontent.com/lewisje/jansal/master/adblock/hostslt

That’s simply because the URL doesn’t have file extension and thus the correct mime type cannot be detected. You could use GitHub directly for simple text files, don’t you?

On 21 Oct 2018, at 13:59, Mtq<EMAIL_ADDRESS>wrote:
test link https://raw.githubusercontent.com/lewisje/jansal/master/adblock/hostslt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

example. https://gitcdn.xyz/repo/lewisje/jansal/master/adblock/hostslt

OK, I see. I’ll try to do something.


[TextField] InputLabel overlapping

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Text field Input label overlapping
Expected Behavior 🤔
Label should be so in top once data feed.
Steps to Reproduce 🕹
Steps:

Visit https://codesandbox.io/s/statetextfields-material-demo-forked-mlw5z?file=/demo.tsx
Check label overlap the text field value.

Thanks in Adv.

The behavior is expected, see the warning that should guide you in the solution. You should be able to find duplicates of this in StackOverflow


Handle empty file request on dedup store

Description
Fixes #1397 1397
Type of change
Please delete options that aren't relevant.

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

How Has This Been Tested?
Added new test case in unit tests
Checklist

[X ] Tests added/amended

This change is

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Array coercion fail with only 1 item

I noticed a strange behavior when trying to parse a numeric array with only 1 item.
Entry:
{
  id: 1,
  seats: [ 1 ]
}

Result:
{
  id: 1,
  seats: [undefined]
}

Problem happens at that point:
array.js:
if(value[Symbol.iterator]) {
    value = Array(...value);
}

spec:
it.only('coerces items', () => {
  const user = new User({
    books: [1]
  });

  expect(user.books).to.eql([
    1
  ]);
});

Result: AssertionError: expected [ undefined ] to deeply equal [ 1 ]

Fixed by https://github.com/talyssonoc/structure/pull/38


[NzDatePicker] nz-range-picker is not opened on label click in nz-form-item

Reproduction link
https://stackblitz.com/edit/angular-4biav6?file=src/app/app.component.ts
Steps to reproduce

Click on 'Range picker' label.

What is expected?
Picker is opened
What is actually happening?
Picker is still closed

Environment
Info

ng-zorro-antd
11.4.2

Browser
Chrome

Looks like nzId input on nz-range-picker has no effect.

PR #6814


Catalog failure errors are obscure

In GitLab by @jakebeal on Oct 30, 2019, 10:35
This appears to be an error from the document not being in the catalog:

Validation Failed! Schema Validation Error: 'YeastSTATES-CRISPR-growth-cruves' is not one of ['UNKNOWN']  Failed validating 'enum' in schema[0]:     {'enum': ['UNKNOWN'], 'type': 'string'}  On instance:     'YeastSTATES-CRISPR-growth-cruves'

However, there is nothing there that would lead one to understand that the problem is that the document is not listed correctly in the catalog. This error message thus needs to be improved.

In GitLab by @jakebeal on Nov 11, 2019, 10:19
assigned to @tramyn

In GitLab by @tramyn on Nov 20, 2019, 10:15
@jakebeal could you provide me an example that will replicate this issue? I am unsure how to reproduce this bug.

In GitLab by @jakebeal on Nov 20, 2019, 10:36
Here's one: https://docs.google.com/document/d/1Qsw2JBfF75gOyWpbSrlC9SuHYBiV8f-lK_5pF1I3rww/edit?usp=sharing

In GitLab by @tramyn on Nov 25, 2019, 11:33
created branch 146-catalog-failure-errors-are-obscure to address this issue

In GitLab by @mweston on Nov 25, 2019, 14:16
The above file is failing because the file is not in a directory which automatically provides its Challenge Problem enumeration (YeastStates, Novel Chassis, etc.). The generation defaults to "Unknown" which is not a valid challenge problem, so it correctly fails validation. For this particular instance of a validation error (there can be many others), the solution is to place the request document in a relevant challenge problem folder.

In GitLab by @jakebeal on Dec 9, 2019, 10:47
Problem: the JSON schema validator is giving a unified message, and pulling the information out may be complicated. Thus, pushing this back to 2.5 in order to prioritize parameter tables.

In GitLab by @jakebeal on Dec 9, 2019, 10:48
https://python-jsonschema.readthedocs.io/en/stable/errors/#jsonschema.exceptions.ValidationError

I believe this issue has been addressed. @mwes are there additional changes you want IP to support for handling error message for validation?

Hi @tramyn, per testing, this is still unresolved, with the base case still reproducible. Any experiment requests not in a directory that automatically provides its Challenge Problem enumeration (YeastStates, Novel Chassis, etc.) will fail. The generation defaults to "Unknown", which is not a valid challenge problem, so it correctly fails validation. For this particular instance of a validation error (there can be many others), the solution is to place the request document in a relevant challenge problem folder, but the users do not/cannot know to do that to fix the issue.
To reproduce:

Take any experiment request document
Make a copy of it
Move it out of one of the request folders: Novel Chassis, YeastStates, etc.
Try to generate or validate it

The Google Docs validate call returns:

Message details
Exception: Request failed for http://intentparser.sd2e.org returned code 500. Truncated server response: Internal Server Error (use muteHttpExceptions option to examine full response)

Running the intent parser directly or running the generate call e.g.
http://intentparser.sd2e.org/document_request?1-S2qjbDjakh1nmDakqDXkcZmHP437UFpGyNGH49Kx5c

shows the underlying error is still the same (see below). A better interpretation of this that helps the user understand and resolve the issue: "The Intent Parser cannot determine which Challenge Problem this Experiment Request Document is associated with. Is this document in a Challenge Problem folder under DARPA SD2E Shared > CP Working Groups > ExperimentalRequests?"

 'Unknown' is not one of ['NOVEL_CHASSIS', 'INTENT_PARSER_TEST', 'MOSQUITO_RELATEDNESS_INFERENCE', 'BIOCON', 'CELL_GROWTH', 'PROTEIN_DESIGN', 'YEAST_STATES', 'RIBOSWITCHES', 'UNDEFINED']

Failed validating 'enum' in schema['properties']['challenge_problem']:
    {'$comment': 'version: 2.2.0#master; generated: 20200310T152056+00:00; '
                 'source: '
                 'git@github.com:SD2E/python-datacatalog.git@4aeb62a',
     '$id': 'https://schema.catalog.sd2e.org/schemas/challenge_problem_id.json',
     '$schema': 'http://json-schema.org/draft-07/schema#',
     'additionalProperties': False,
     'description': 'Challenge problem enumeration',
     'enum': ['NOVEL_CHASSIS',
              'INTENT_PARSER_TEST',
              'MOSQUITO_RELATEDNESS_INFERENCE',
              'BIOCON',
              'CELL_GROWTH',
              'PROTEIN_DESIGN',
              'YEAST_STATES',
              'RIBOSWITCHES',
              'UNDEFINED'],
     'examples': ['NOVEL_CHASSIS',
                  'INTENT_PARSER_TEST',
                  'MOSQUITO_RELATEDNESS_INFERENCE',
                  'BIOCON',
                  'CELL_GROWTH',
                  'PROTEIN_DESIGN',
                  'YEAST_STATES',
                  'RIBOSWITCHES',
                  'UNDEFINED'],
     'title': 'Challenge Problem Id',
     'type': 'string'}

On instance['challenge_problem']:
    'Unknown'

Users have generally been trained to create their requests accordingly, but new users still run into this, and previous users sometimes forget.

Okay, then it looks like this issue is best classified under milestone 2.8 (cleaning up known UI issues).

Sounds good to me.

@jakebeal for this issue, does it make sense for IP to generate a default challenge problem or would you rather stick with your original request to have IP report a human readable error and have the user check where their document is located in SD2 Google Drive folder?

@mwes I noticed that data catalog accepts an "UNDEFINED" value when validating a SR challenge problem. When will a challenge problem get classified as "UNDEFINED"? Should a document not located in the desired SD2 folder be treated similarly to documents that are in the SD2 experiment request folder and have its challenge problem assign to "UNDEFINED"?

@tramyn the mapping function you're using either populates a successful challenge problem mapping or it does not - the success is binary. It does not return UNDEFINED - this is a placeholder value in the enumeration we don't use.
Unknown looks like a default that is coming from the intent parser and is not a valid value, hence the schema validation error: https://github.com/SD2E/experimental-intent-parser/blob/master/intent_parser/intent_parser.py#L342
This is an error condition and can only be fixed by user action. We should not proceed with any additional parsing or return something that could be attempted to be used - without the challenge problem and experiment_reference we have no context for the experiment request. Filling in UNDEFINED won't solve the problem unfortunately, it will just silently delay it.
A better interpretation of this that helps the user understand and resolve the issue is to return an error that says something to the effect of: "The Intent Parser cannot determine which Challenge Problem this Experiment Request Document is associated with. Is this document in a Challenge Problem folder under DARPA SD2E Shared > CP Working Groups > ExperimentalRequests?"


Fix the link for WavAugment

Codecov Report

Merging #93 into master will decrease coverage by 0.20%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #93      +/-   ##
==========================================
- Coverage   93.16%   92.95%   -0.21%
==========================================
  Files          37       37
  Lines        2838     2754      -84
==========================================
- Hits         2644     2560      -84
  Misses        194      194

Impacted Files
Coverage Δ

test/cut/test_feature_extraction.py
96.92% <0.00%> (-0.22%)
:arrow_down:

lhotse/augmentation.py
91.07% <0.00%> (-0.16%)
:arrow_down:

lhotse/utils.py
83.47% <0.00%> (-0.15%)
:arrow_down:

lhotse/features/mfcc.py
96.77% <0.00%> (-0.11%)
:arrow_down:

lhotse/cut.py
87.07% <0.00%> (-0.09%)
:arrow_down:

lhotse/audio.py
97.45% <0.00%> (-0.07%)
:arrow_down:

test/cut/test_cut.py
98.86% <0.00%> (-0.04%)
:arrow_down:

lhotse/supervision.py
98.21% <0.00%> (-0.04%)
:arrow_down:

lhotse/features/base.py
94.55% <0.00%> (-0.03%)
:arrow_down:

test/test_utils.py
100.00% <0.00%> (ø)

... and 17 more

Continue to review full report at Codecov.

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

Thanks!


High level Info/Documentation of Services | Developement mode

I am developers, looking to understand the purpose of different services used.

can i know views on purpose of different services and may be reference to understand more.

how do we develop changes in python and react like do we need to restart the docker environment when done changes?
Some tricks in debugging the db,api or react.

as per inputs form ShawnZ adding here for reference :
https://github.com/apache/superset/blob/master/CONTRIBUTING.md#setup-local-environment-for-development


Create a branch for data upload only

Hi Scott @swo and Ed @eschrom, this is the branch for uploading the data only. It is rare to upload data in github, while the data size is small, so this PR is just used as an example of uploading data in the workflow, if needed in the future.

I think you want to rebase this branch and keep only https://github.com/CDCgov/cfa-immunization-uptake-projection/pull/11/commits/bdaa9ad9be5a17238672f8dda0e2333740921e3d . Because if you look at Files now, you'll see that this PR deletes a bunch of files, when all you want to do is to add the data

See #12 for what I think this PR should look like, although even that one is missing documentation. Feel free to open a branch off of #12, add some documentation, and we can merge in there!

Closing in favor of #12


Make getAdventureRange more accurate

Do not apply ode to distillate
Fix milk which hasn't been applying for ages
Add tests for everything

This has made me realise that we don't give a correct value for Ode to Booze. If you have 10 turns of Ode and drink a bottle of gin, we will correctly predict 6 adventures gained. But if you only have 2 turns of Ode, we still say 6 when you will actually get 5, i.e. 3 for the 3 fullness 1 adv/fullness booze + 2 for max(turns of ode,fullness). I am not fixing this now but added a disabled test that otherwise fails.

I will definitely work on this this bank holiday and get those tests in


Init m_image to NULL.

This fixes a segfault when closing chailove.
The root problem is that tffFont is never true as far as I can tell.
https://github.com/libretro/libretro-chailove/blob/7c72a5fd1ca9f55edc29d29bff9ab13ec353d641/src/love/Types/Graphics/Font.cpp#L120
And then SDL_Surface* surface is never set.
https://github.com/libretro/libretro-chailove/blob/7c72a5fd1ca9f55edc29d29bff9ab13ec353d641/src/love/Types/Graphics/Font.cpp#L122
Since m_image is not set to NULL this will be true when it should not be.
https://github.com/libretro/libretro-chailove/blob/7c72a5fd1ca9f55edc29d29bff9ab13ec353d641/src/love/Types/Graphics/Font.cpp#L71
Next it will crash here.
https://github.com/libretro/libretro-chailove/blob/7c72a5fd1ca9f55edc29d29bff9ab13ec353d641/src/love/Types/Graphics/Image.cpp#L20
And if that conditional is removed it will crash here instead.
https://github.com/libretro/libretro-chailove/blob/7c72a5fd1ca9f55edc29d29bff9ab13ec353d641/src/love/Types/Graphics/Image.cpp#L58
This can be simply avoided by making sure m_image is inited to NULL.
This might be further improved by fixing ttyFont and ttfFont so they are set, but I'm not sure how this should be done or what the ideal behavior would be...
@RobLoach Does this look good to you? I tested this with both the no content demo and Floppy Bird where it will no longer crash when closed.

Thanks!


enabled syntax highlighting

I only enabled the syntax highlighting feature of GitHub for better readability. Feel free to merge or cancel. :)

@0xflotus  would you mind doing a rebase on top of master to avoid the merge commit? As a side-effect it will also trigger CI.
Due to some CI changes put in place this past week, we need to get CI to run, and the best thing for you to do is to push against your branch again or close this PR and make a new one. Going forward this won't be an issue, but unfortunately, we do not have a way to force CI to run for older PRs.

See #342 I created a new PR


Seems related to https://github.com/flutter/flutter/issues/18498, but now with a stack trace.
cc @mkustermann

We've changed the way we generate these type testing stubs in JIT mode - and no longer call dart::AbstractType::TypeTest so I suspect that this issue is gone now.
Please re-open if this re-appears.


Research on internship application stage-specific tips

3-5 points for it to be succinct and easily digestible.

Done on google docs!


Please publish latest version

The latest version v0.2.1 does not include changes from https://github.com/utgwkk/bulkmockgen/pull/5.
It causes unnecessary updates on go.sum if the project has migrated to go.uber.org/mock/mockgen.

I have just published version 0.2.2. Thank you for your notice!


Pop All Wrinkler button

Since patch 2.018 (including 2.019) the pop all wrinkler button has disappeared.

No, it's still there.  I've been using it.


React native maps showsMyLocationButton position

I am using Expo react-native-app. I have some local data which I want show in maps. For maps I have used React-native-maps. I successfully pull the data and display in maps by using Marker. For user location I have used expo-location and expo-permission. That works fine. I have used React-native-maps one props called  showsMyLocationButton, by default props boolean false. when I made it true I can able to see in IOS Emulator and i think by default position bottom-right. Android emulator I don't see the button at all. This is ios image and this android image. I want to display some data under the maps like a Bottom-Sheet, for that I have used this package. As a result it hide the ios'  showsMyLocationButton.
I want to display the user current location Button like Uber. I tried lots of way to do that but could not able to achieve the goal. I want change the button icon as well but also failed. Really appreciate if someone Help me out.
I shared my code in Snack Ps. it only works in ios and Android, does not work in web View.
This is my code
import React, { useState, useEffect, useCallback } from 'react';
import {
  Dimensions, StatusBar, StyleSheet, Text,
  TextInput, TouchableOpacity, View, Button
} from 'react-native';
import Constants from 'expo-constants';
import Mapview, { Marker, Callout, PROVIDER_GOOGLE } from 'react-native-maps'
import * as Location from 'expo-location';
import * as Permissions from 'expo-permissions';
import datas from './datas.json'
// You can import from local files

import Animated from 'react-native-reanimated';
import BottomSheet from 'reanimated-bottom-sheet';

// or any pure javascript modules available in npm

export default function App() {
  const sheetRef = React.useRef(null);
  const renderContent = () => (
    <View
      style={{
        backgroundColor: 'white',
        padding: 16,
        height: 450,
      }}
    >
      <Text>Swipe down to close</Text>

      <Button
        title="Open Bottom Sheet"
        onPress={() => sheetRef.current.snapTo(0)}
      />

    </View>
  );

  const [state, setstate] = useState({
    "latitude": 60.1098678,
    "longitude": 24.7385084,
    "latitudeDelta": 1,
    "longitudeDelta": 1
  });

  useEffect(() => {
    _onMapReady();
  }, [_onMapReady]);

  const _onMapReady = useCallback(async () => {
    const { status } = await Permissions.askAsync(Permissions.LOCATION);
    if (status !== `granted`) {
      // console.log(`Permisson Denied`);
    }
    const location = await Location.getCurrentPositionAsync({ "accuracy": Location.Accuracy.High });
    setstate({
      ...state,
      "latitude": location.coords.latitude,
      "longitude": location.coords.longitude
    });
  }, [state]);

  return (
    <View style={styles.container}>
      <Mapview
        provider={PROVIDER_GOOGLE}
        initialRegion={state}
        showsIndoors={true}
        showsMyLocationButton={true}
        zoomControlEnabled={true}
        zoomEnabled={true}
        zoomTapEnabled={true}
        showsScale={true}

        showsBuildings={true}
        showsUserLocation={true}
        showsCompass={true}
        onMapReady={_onMapReady}

        style={styles.mapStyle}>
        {
          datas.data?.map((i) => {
            return (
              <Marker
                coordinate={{
                  "latitude": i.location.lat,
                  "longitude": i.location.lng
                }}
                animation={true}
                key={i.id}

              >
                <Callout
                  style={{ "width": 100, "height": 50 }}>
                  <View>
                    <Text>{i.Property}</Text>
                  </View>
                </Callout>
              </Marker>
            );
          })
        }

      </Mapview>

      <BottomSheet
        ref={sheetRef}
        snapPoints={[450, 300, 0]}
        borderRadius={10}
        renderContent={renderContent}
      />

    </View>
  );
}
const styles = StyleSheet.create({
  container: {
    "flex": 1,
    "alignItems": `center`,
    "justifyContent": `center`
    // position: 'absolute',

  },
  mapStyle: {

    "height": Dimensions.get(`window`).height,
    "width": Dimensions.get(`window`).width

  },

});

mapPadding props is the solution

mapPadding={{top: 20, right: 20, bottom: 550, left: 20}}

is there another solution beside mapPadding?

The problem with mapPadding is that when centering the map on a selected marker, they are also offset by the same amount. This is unacceptable in my opinion

The problem with mapPadding is that when centering the map on a selected marker, or animate to lat/lng or just setting a region/bounds, they are also offset by the same amount. Now I need to calculate the offset in lat/lng to get it re-centered, and this is affected by zoom level and screen size/density as 200pixels mean different amounts to different screens and devices, so I have not worked out the calculation yet. It is also different for iOS and Android as the default position of the button is not the same corner of the screen.
This is unacceptable in my opinion, there should be an easy way to position the button, perhaps I will look to open a PR as it must be easier than the calculation I mentioned above.

have u calculated the offset yet? How could i do it?


Allow export type Foo; as valid syntax

Search Terms
Exporting a type defined elsewhere. Export a defined type. Type alias circularly references itself. Can't export a type with the same name.
Suggestion
Currently you can only export types right when you declare them:
export type Foo = string | number;

But many people often use ambient files to make their types available globally throughout the project without the need to import them. This however means that the types cannot be exported directly where they define them because the file would cease to be ambient. The current way of coping with this is naming the type differently for internal use and then reexporting it with a different name:
// in types.ts
type _Foo = string | number;

// in index.ts
export type Foo = _Foo;

I suggest that this inconvenience could be easily solved by allowing this syntax:
export type Foo;

Use Cases
As described above, it's useful to export types defined in ambient files.
Examples
As above
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Why not write
export { _Foo as Foo };

Because that requires me to use _Foo instead of Foo everywhere in the package. Code with lots of leading underscores has a bad smell. And it's not especially comfortable.

Oh, I think I misunderstood. Why not just
export { Foo };

Wow, I didn't know that syntax! However it throws an error:
[ts] Cannot export 'Foo'. Only local declarations can be exported from a module. [2661]

Still, it seems better to allow exporting types that aren't local than to invent whole new syntax. Should I close this issue and reopen a new one then?


print attestor public key

 Add a way to automatically generate attestor private key and display public key when launched


Maybe add acme-client for letsencrypt support

CLI client: https://github.com/onur/letsencrypt-rs
Crate: https://docs.rs/acme-client

Cool! Thank you!


alert resolved question

What did you do?
set up an alertingr rule ,for example:

name: defaultInstances
rules:

record: job_instance_default:defaultinstances
expr: device_status:oms:1m
alert: somethingwrong
expr: job_instance_default:defaultinstances==0
for: 1m

What did you expect to see?
when the device is error I can receive the alert as expect.The alertingrule operates well.
now it is good
What did you see instead? Under which circumstances?
But when the device shutdown,and the "device_status:oms:1m" metric value is changed into nodata
Then the alert resolved later
But I am confused,why did it sent the resolved message?what about the reason?
Environment

Alertmanager version:

version 0.20.0

Prometheus version:
version 2.18.1

Thanks for your report. It looks as if this is actually a question about usage and not development.
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


feat: support for closed issues

I couldn't test this locally, so I'm not sure if it works without any bugs.

👌

To verify your on-demand ISR configuration is correct, you will need to create a production build and start the production server.

https://nextjs.org/docs/basic-features/data-fetching/incremental-static-regeneration#testing-on-demand-isr-during-development

I'm only showing open issues for now 😄 Thank you though!


Audit: Bid1155Contract Transfer and send functions used

The transfer() and send() functions forward a fixed amount of 2300 gas. Historically, it has often been recommended to use these functions for value transfers to guard against reentrancy attacks. However, the gas cost of EVM instructions may change significantly during hard forks which may break already deployed contract systems that make fixed assumptions about gas costs.

@parva-jain can we have a look to it

#77 fixes it


fix #252: crash when duplicate branch is found in tree

Coverage increased (+0.003%) to 99.696% when pulling 0823824a9b3aaa0af498955276a725a06167734b on ndawe:master into 1bac000e7ae64ce631bc45e3aa9f926b18391b2d on rootpy:master.

Coverage increased (+0.003%) to 99.696% when pulling 0823824a9b3aaa0af498955276a725a06167734b on ndawe:master into 1bac000e7ae64ce631bc45e3aa9f926b18391b2d on rootpy:master.


Azure CLI stopped working

Describe the bug
Azure CLI stopped working with my "Azure Subscription 1" (Subscription ID = 4ab4a6f3-e219-4912-84cb-c7a6196ea04a) with the following error:
cindy@Azure:~$ az group create --name learn-deploy-acr-rg --location eastus
The command failed with an unexpected error. Here is the traceback:
[Errno 30] Read-only file system: '/home/cindy/.azure/commands/2021-06-20.06-23-39.group_create.646.log'
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 514, in execute
load_cmd_tbl_func=self.commands_loader.load_command_table, args=args)
File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 170, in raise_event
func(self, **kwargs)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/azlogging.py", line 95, in init_command_file_logging
self._init_command_logfile_handlers(metadata_logger, args)  # pylint: disable=protected-access
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/azlogging.py", line 115, in _init_command_logfile_handlers
logfile_handler = logging.FileHandler(log_file_path, encoding=LOG_FILE_ENCODING)
File "/opt/az/lib/python3.6/logging/init.py", line 1032, in init
StreamHandler.init(self, self._open())
File "/opt/az/lib/python3.6/logging/init.py", line 1061, in _open
return open(self.baseFilename, self.mode, encoding=self.encoding)
OSError: [Errno 30] Read-only file system: '/home/cindy/.azure/commands/2021-06-20.06-23-39.group_create.646.log'
Tried just with "az" and again it's "Read-only file system" error:
cindy@Azure:~$ az
The command failed with an unexpected error. Here is the traceback:
[Errno 30] Read-only file system: '/home/cindy/.azure/commandIndex.json'
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 512, in execute
self.commands_loader.load_command_table(args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/init.py", line 479, in load_command_table
command_index.update(self.command_table)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/init.py", line 595, in update
self.INDEX[self._COMMAND_INDEX_VERSION] = version
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/_session.py", line 86, in setitem
self.save_with_retry()
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/_session.py", line 76, in save_with_retry
self.save()
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/_session.py", line 65, in save
with codecs_open(self.filename, 'w', encoding=self._encoding) as f:
File "/usr/bin/../../opt/az/lib/python3.6/codecs.py", line 897, in open
file = builtins.open(filename, mode, buffering)
OSError: [Errno 30] Read-only file system: '/home/cindy/.azure/commandIndex.json'
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Expected Behavior
Azure CLI should just work.
Environment Summary
Linux-5.4.0-1048-azure-x86_64-with-debian-10.2 (Cloud Shell)
Python 3.6.10
Installer: DEB

azure-cli 2.25.0

Extensions:
ai-examples 0.2.5
ssh 0.1.5

Additional Context
I initially deleted the storage account resource group used by the CLI, but have recreated it when I launched the Azure CLI next time. However Azure CLI just stopped working and always gave error of "read-only file system". Is it locked or messed up somewhere? Could you please help restore the functionality? Thanks.

This issue is resolved. I'm closing it.


Any plans on adding Windows distribution builds on PyPi ?

Yes, very soon! In the next few weeks.

Looking forward to that, you're making some amazing things over there at daily, thank u daily team ❤

great! Is there a pre-release for us to test?

Yes, very soon! In the next few weeks.

Hi, a month passed, any news?

It's a bummer, so many interesting projects and examples in pipecat-ai, yet unusable for most of us since we're on windows.
I've been working with wsl but its just not great, had to stop all my cooking for a while now, any news guys pl ? starting to lose hope over here

dupe of https://github.com/daily-co/daily-python/issues/7

Closing. As already mentioned, duplicated from #7. Things have been a bit hectic, but I do definitely have plans to finish Windows support. It's half way there, from the same base Rust code I was able to get a working Windows build for https://github.com/daily-co/daily-core-sdk. So, it will happen for sure. It's actually a priority for the beginning of 2025.


Pagination in test mode

Hi there, I am using a test token and I would like to know whether it exists any type of restriction in the number of pages, I am only receive one page in all requests.
Thanks for your time.

👋 Thanks for raising this question. To clarify your question so that I understand it better, when you say "I am only receive one page" do you mean that you're only receiving a small amount of flight offers and you'd like to receive more offers for your search request(s)?

Hi there, right. I only received 50 records. But now we have changed the code and we don't use this module, we have integrated our own api rest module to get your data. Thanks.

Thanks for the clarification! Duffel's API supports pagination and you can control this through the listWithGenerator/0 function. An example of this pagination in action can be seen in https://github.com/duffelhq/duffel-api-javascript/blob/77f764e2aae6cca08b05e550ca4646e28452be0b/src/booking/OfferRequests/OfferRequests.spec.ts#L38-L52.

Beyond that, we're very interested to know what pain points you had with our library as we want to make it as easy to use as possible for our customers. If you'd rather discuss this privately, please get in contact with us via<EMAIL_ADDRESS>so that we can continue the discussion.


Modify VDP application to use the accelerator

[ ] Modify fn_posit_fma
[ ] Add a fn_reset_quire
[ ] Modify/Add a new fn_read_quire

Instead of fn_posit_fma create a fn_posit_accel_fma which will directly invoke the fma.p instruction which dispatches to the accelerator using the modified FBox_Core

To compile the function (from the directory which has the c file).
make MAIN=vdp all
Before running the makefile, copy all files from the lib folder into your vdp folder.

To run the test, go to your hardware build directory, and:
make run_example EXAMPLE=/path/to/vdp VERBOSITY=+v0/+v1/+v2 |& tee run.log


[otp_ctrl] Add OTP memory map generation to CI

This adds the OTP memory map translation script to the hw/Makefile and adds a check to CI to make sure the memory map and generated files are in sync.
Signed-off-by: Michael Schaffner<EMAIL_ADDRESS>

CI shows that it works :-)

Haha yes. Now that we've tested this, let me make sure that these files are up to date ;).

lgtm!
On Tue, Oct 27, 2020 at 10:27 AM Michael Schaffner<EMAIL_ADDRESS>wrote:

Haha yes. Now that we've tested this, let me make sure that these files
are up to date ;).
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/pull/3933#issuecomment-717401938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSVPMWE3B5TVTLGZSVLSM37GLANCNFSM4TBEDR6A
.

This has to wait until #3905 goes in (due to updates in the OTP hjson template).


Rename mqtt5 hooks

As discussed a while back I think it's confusing to call the new hooks _v1 introduced in the mqtt5 fsm. They are simply new hooks needed to support the mqtt version 5 protocol and not new versions of the old hooks with the similar names. With this change we can later add new hook versions without it being too confusing...
This depends on the same change in the vernemq_dev repo: https://github.com/larshesel/vernemq_dev/pull/1.
Are the _m5 postfix acceptable for you?

great, merged.


Jenkins Setup

This is a follow-up to TryGhost/Ghost-Config#8 where the idea came up that we could set up a instance of Jenkins to do various things:

Automatic building of RPM packages
Automatic building & upload of release ZIP's
Run tests on more platforms (Windows, OS X, FreeBSD etc - Travis runs on Ubuntu 12.04)
Build docs from the code
...

I could host either a build slave or the entire Jenkins setup. My box runs FreeBSD and has plenty of RAM and disk space, but a rather shitty internet connection (16mbit down, 1mbit up).

Closing this as it has never had traction, and if we do want to do non-travis builds we would likely do them with some other CI solution than Jenkins.


Loading SQLite databases from a remote URL

The jupyterlite/xeus-sqlite-kernel currently seems to require users to create a database as part of a script before they can query it, rather than connect to a sqlite file shipped as part of a JuptyerLite distribution or uploaded to it, or connect to a remote database file.
The phiresky/sql.js-httpvfs Javascript package wraps a SQLite emscripten distribution and also provides a virtual filesystem that allows the SQLite database to access very large remote SQLite databases (if configured appropriately) in an efficient way.
I wonder if this approach could be used to support remote connections from the xeus-sqlite-kernel? Users could then use a simple web server to publish both the JupyterLite environment, and even a large database, and then query the database efficiently from their browser?
The SQLime browser based SQlite playground (nalgeon/sqlime) also offers some interesting "web integrations", as described on its About SQLime page. For example, SQL files can be hosted Github gists, the gist id passed via a URL parameter to SQLime, then loaded and run by the playground when the page is loaded. (Databases files can also be uploaded from the desktop to the playground environment.)

The Basthon in-browser notebook [repo] & SQLite kernel loads a database from a file path specified via a URL parameter:

(I also note here examples of using custom javascript functions to create custom sqlite functions.)

@psychemedia there is a PR here https://github.com/jupyter-xeus/xeus-sqlite/pull/119
with that one can fetch databases with
FETCH <URL> <FILENAME>
and load them later with
`%LOAD  RW
one can then persist  the virtual filesystem into the browsers indexed db, that way one only needs to do the fetching once

Interesting, thanks..:-)
I take it that downloads the whole db, eg compared to the sql.js-httpvfs approach where the idea is you can connect to large remote databases and then just pull what you need chunks at a time?
Still v. useful though :-)

Is it worth closing this, now #119 has been released? :eyes:

xeus-sqlite-kernel > "Loading SQLite databases from a remote URL" https://github.com/jupyterlite/xeus-sqlite-kernel/issues/6#issuecomment-1031751580
%FETCH   https://github.com/jupyter-xeus/xeus-sqlite/blob/ce5a598bdab29eb6aab78a78d0caee93c292ec74/src/xeus_sqlite_interpreter.cpp#L191
xlite.cpp >
void fetch(const std::string url, const std::string filename)
https://github.com/jupyter-xeus/xeus-sqlite/blob/main/src/xlite.cpp#L38

[ ] Loading partial SQLite databases over HTTP

sql.js-httpvfs https://github.com/phiresky/sql.js-httpvfs
sqlite-wasm-http: https://github.com/mmomtchev/sqlite-wasm-http

This project is inspired from @phiresky/sql.js-httpvfs but uses the new official SQLite WASM distribution.

"Using SQLite as storage for web server static content" https://news.ycombinator.com/item?id=42010323

[ ]  Loading partial SQLite databases over HTTP

sql.js-httpvfs https://github.com/phiresky/sql.js-httpvfs
sqlite-wasm-http: https://github.com/mmomtchev/sqlite-wasm-http

This project is inspired from @phiresky/sql.js-httpvfs but uses the new official SQLite WASM distribution.

"Using SQLite as storage for web server static content" https://news.ycombinator.com/item?id=42010323

PRs are welcome