Codalab Competition-V2 webpage not getting rendered properly.

I have installed an instance of Codalab Competition-v2 in our institute's cloud VM which is accessible publically at http://<IP_ADDRESS>/. However, it seems that the web page is not getting rendered correctly and looks different from the one at https://www.codabench.org/.
The outputs from executing the installation steps are these -
$ docker-compose up -d

competitions-v2_minio_1 is up-to-date
competitions-v2_redis_1 is up-to-date
competitions-v2_rabbit_1 is up-to-date
competitions-v2_builder_1 is up-to-date
competitions-v2_db_1 is up-to-date
Starting competitions-v2_createbuckets_1 ...
competitions-v2_flower_1 is up-to-date
competitions-v2_django_1 is up-to-date
competitions-v2_site_worker_1 is up-to-date
Starting competitions-v2_createbuckets_1 ... done

$ docker-compose exec django ./manage.py migrate

Operations to perform:
  Apply all migrations: admin, auth, authtoken, competitions, contenttypes, datasets, forums, leaderboards, oauth2_provider, profiles, queues, sessions, sites, social_django, tasks
Running migrations:
  No migrations to apply.

$ docker-compose exec django ./manage.py generate_data

Creating data of size 3 with an admin account.

$ docker-compose exec django ./manage.py collectstatic --noinput

0 static files copied to '/app/src/staticfiles', 269 unmodified.

I am unable to figure out the reason behind this partial rendering of the webpage.

What's the output of docker-compose logs -f builder?
I am trying to access the page now to see what's wrong, is it still active?

Yes the website is still active. The logs look like this -
Attaching to competitions-v2_builder_1
builder_1         | npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
builder_1         | npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
builder_1         | npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
builder_1         | npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
builder_1         |
builder_1         | ><EMAIL_ADDRESS>postinstall /app/node_modules/nodemon
builder_1         | > node bin/postinstall || exit 0
builder_1         |
builder_1         | Love nodemon? You can now support the project via the open collective:
builder_1         |  > https://opencollective.com/nodemon/donate
builder_1         |
builder_1         | npm notice created a lockfile as package-lock.json. You should commit this file.
builder_1         | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
builder_1         | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
builder_1         | npm WARN<EMAIL_ADDRESS>No license field.
builder_1         |
builder_1         | added 283 packages from 249 contributors and audited 284 packages in 10.779s
builder_1         |
builder_1         | 1 package is looking for funding
builder_1         |   run `npm fund` for details
builder_1         |
builder_1         | found 0 vulnerabilities
builder_1         |
builder_1         | No task specified. Will go through all possible tasks
builder_1         | [nodemon] 1.19.4
builder_1         | [nodemon] 1.19.4
builder_1         | [nodemon] to restart at any time, enter `rs`
builder_1         | [nodemon] watching dir(s): src/static/riot/**/*
builder_1         | [nodemon] watching extensions: tag
builder_1         | [nodemon] to restart at any time, enter `rs`
builder_1         | [nodemon] watching dir(s): src/static/stylus/**/*
builder_1         | [nodemon] watching extensions: styl
builder_1         | [nodemon] starting `npm run -s build-riot`
builder_1         | [nodemon] starting `npm run -s build-stylus`
builder_1         | [nodemon] clean exit - waiting for changes before restart
builder_1         | src/static/riot/admin/user_management.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/admin/user_switch.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/analytics/analytics.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/competition_list.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/_header.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/_registration.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/_run_info.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/_stats.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/_tabs.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/_tags.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/_timeline.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/detail.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/leaderboards.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/log_window.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/participant_manager.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/submission_manager.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/submission_modal.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/submission_scores.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/detail/submission_upload.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/editor/_collaborators.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/editor/_competition_details.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/editor/_leaderboard.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/editor/_pages.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/editor/_participation.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/editor/_phases.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/editor/form.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/management.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/public-list.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/tile/competition_tile.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/tile/front_page_competitions.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/competitions/upload.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/datasets/help_button.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/datasets/management.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/forms/input-file.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/forms/input-select.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/forms/input-text.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/forms/sorting-chevrons.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/loader.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/management.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/place_medals/bronze_medal.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/place_medals/fifth_place_medal.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/place_medals/fourth_place_medal.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/place_medals/gold_medal.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/place_medals/silver_medal.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/profiles/profile_detail.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/profiles/profile_edit.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/queues/management.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/submissions/submission_management.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/tasks/management.tag -> src/static/generated/riot.js
builder_1         | src/static/riot/tasks/task_detail.tag -> src/static/generated/riot.js
builder_1         | [nodemon] clean exit - waiting for changes before restart

Hmm, I still cannot access http://<IP_ADDRESS>/ or https://<IP_ADDRESS>/ to see what could be wrong
It appears like all of the assets are being built and collected...

Well that's strange. It should be accessible. At least to me the incompletely rendered website is visible at http://<IP_ADDRESS>/. And it looks like this - Codalab_competition_v2_webpage.pdf

Yeah that's what I was hoping to see, if you pull up the console is it missing a lot of the styling files and such? A collectstatic (as you've done) should be fixing this... can you refresh and clear cache?

if you pull up the console is it missing a lot of the styling files and such ?

How/where can I check this? Are you suggesting something like curl localhost:80 ?
I executed these, unfortunately, the problem still persists.
docker-compose exec django ./manage.py clear_cache
docker-compose exec django ./manage.py collectstatic --noinput

Ah sorry, I mean like in the "browser console" or "dev tools":

My email is<EMAIL_ADDRESS>maybe we can setup a pairing session this week and I can help you over a Google Hangout/Zoom?

Thank you this will be very helpful, I have sent you a mail with the details.

Closing this as we fixed this in our call yesterday


WIP/Propsal for "API-Mode"

I am using boarding with another UI front end that HTTP Posts the required form data to the boarding app. In order to do so I needed to reconfigure boarding to:
a) disable requiring CSRF tokens
b) setting the required CORS headers on each request
I was wondering weather any1 else is interested in this usage and weather the maintainers would care to support this kind of behavior.
If so I'd offer to provide Docs, refactor it if required, etc. and provide the necessary steps to allow the maintainers to keep this feature maintanable.

Hey @grekko, thanks for the PR. This seems a little out of scope of this project, however feel free to run this as your own fork and use it from there 👍
I'll close the PR for now, however feel free to re-open if you want to continue a discussion

Hi @KrauseFx
nope. Agreed :) thanks for the feedback. Cheers


Question : How does it work ?

Hi,
It would be very interesting to know how the reordering works. I just want to know what logic does it apply when something is moved (dragged) and when do u reorder things and by what logic.
The sudo code for algorithm if written down here, it would be very informative ..
Thanks a lot of this nice stuff ! :)

Hi! So reordering is controlled by the onRowMoved prop. This expects a function which is called whenever a row has changed position.


Changed to use JVM default chunk size

What
Changed to use JVM default chunk size.
How
Changed call to setChunkedStreamingMode(0) to use JVM default.
Moved call to before request interceptors to allow the size to be changed in an interceptor if necessary.
Increased size of buffer used for HTTP output stream to avoid artificially limiting the chunk size. It is worth noting that current HttpURLConnection implementations appear to treat the chunk size as a preference only and in testing the output buffer size was more likely to be used as the chunk size than the size suggested by setChunkedStreamingMode().
Testing
Added new test with chunking HttpTest#testChunking.
Reviewers
reviewer @rhyshort
reviewer @brynh

+1

+1


Stream restart bug fix by introducing manager

Description
Stream restart was not working because same ctx was used due to which we were not able to restart it. Have moved all the stream manager code to separate module, and also, re-initialised stream before restarting.
Fixes https://razorpay.atlassian.net/browse/METRO-127
Type of change

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

How Has This Been Tested?

[x] Tested existing functionality of worker
[x] Tested restart functionality via unit tests
[x] Tested stop functionality by deleting subscription

Is it a breaking change?
No, only the restart and stop functionality will be affected in case something is broken
Can this change be tested effectively via canary? No, as it only affects worker component, and canary is not done for worker yet
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added unit tests that prove my fix is effective or that my feature works (if applicable)
[ ] I have added integration tests for the new feature (if applicable)
[x] I have manually tested my code to the best of my abilities.

Looks good to me but please resolve the comments by reviewdog.

this is defined in same test package but a different file but golang cli linting is not checking all the files.
https://github.com/golangci/golangci-lint/issues/1574
Seems like we need to change some configs, but will not be part of this PR


Support for VCF v4.3

Support for VCF v4.3 changes and gVCF additions.
The following new checks must be implemented:

SAMPLE meta entries structural changes
PEDIGREE meta entries structural changes
FILTER column: Duplicates not allowed

Closed via #37, although it is a known limitation that the "no duplicates allowed" check is not implemented yet (see #35).


Doccument/Examples for usage

Hi Developers,
Appreciate you guys developing this library. I wanted to raise this issue as a method to connect to ask for some sample/examples of usage. or some documentation on usage.
Thank you.

Hello, have you been able to implement the scripts into your own needs?

Hello, have you been able to implement the scripts to your own needs?

Nope. I couldn't as this seems less comprehendible with no documentation for reference to implement based on our need. I have been waiting for one. @BenBenWoodward - any clue from your end?

I was not able to use the script, I could not work out where to start with it.
I have been able to get SAP to refresh via VBA though by telling the Analysis for Office add-in to launch before I open my workbook. This was by the time Python opens my workbook the VSTO add-in has also load and my macros can run.
Below is the script I use.
import os
import win32com.client
from win32com.client import Dispatch
#Launches SAP Office for Analysis
os.system('"C:\Program Files\SAP BusinessObjects\Office AddIn\BiOfficeLauncher.exe"')
#Launch Excel and Open Wrkbook
xl=win32com.client.Dispatch("Excel.Application")
wb=xl.Workbooks.Open("C:\...\...\...\File_Name.xlsm")
#Make Excel Visible
xl.Visible = True
xl.DisplayAlerts = False
#Run Macro
xl.Application.Run("File_Name.xlsm!ModuleName.MacroName")
#Save, CLose and Quit.
wb.Save()
wb.Close()
xl.Quit()
#Cleanup the com reference.
del xl

How do add attributes to the load of the xlsm

Ditto, has anyone figure out how to use this library? The dev didn't release any documentation.


DrupalVM base image: Use SATA controller instead of IDE

Issue Type

Feature Idea

Your Environment
N/A

Your OS
N/A
Full console output
N/A
Summary
When using VirtualBox, the virtual machines are using IDE storage controllers, would it be possible to have this switched to SATA?
This may improve performance and/or reduce host system load, as per VirtualBox documentation:

Like a real SATA controller, Oracle VM VirtualBox's virtual SATA controller operates faster and also consumes fewer CPU resources than the virtual IDE controller.

The more technical/gritty details of the differences can be found elsewhere in the virtualBox documentation. I think the biggest difference would be seen in database operations, and disabling the use of the host I/O cache without a performance hit.
I wasn't sure if this was the correct place to submit this, it might have been better logged against one of the images directly.

Is this something that can be switched via the Vagrantfile, or does it have to be an image build-time change?

I think it could be switched via the vagrant file with https://www.virtualbox.org/manual/ch08.html#vboxmanage-storagectl to attach a SATA controller, then https://www.virtualbox.org/manual/ch08.html#vboxmanage-storageattach to detach the drive, and attach it to the SATA controller.
I have altered the base image locally, but I still needed to alter the controller on the cloned box after provisioning.
So while it may be possible to switch it via the vagrant file, I'm not sure if it's the correct place to switch it?

After some experimentation, I've only managed to get as far as attaching a SATA controller, and detaching the IDE controller. For the attaching the disk to the SATA controller, I'm at a bit of a loss as to how to get the information needed in a programmatic manner. It appears that I'd need to try to parse that information from the output of one of the Virtualbox commands, but I'm not comfortable with that at all. I feel I have to be missing something.
Additionally, it seems I'd have to be relying on the name of the IDE controller remaining "IDE Controller" in order to avoid having to parse further info, doing it from the Vagrant file is starting to seem prone to error.
I'm far from a Vagrant expert, so I hope that I'm missing something in regards to a more robust manner of making such a change.


Consider creating a usd-on-ethereum project

I would also be very interested to see how much USD is on Ethereum, and others might be interested in this as well

Done


Add or document "Admonitions"

In the markdown documentation are some Admonitions like "Tip" , "Note" but I can't find the markdown documentation for that nice feature.
Is it possible to add this Admonitions in a wiki page?

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

ID: 29f1e43f-a069-dd88-7fc7-9cc497fb94f0
Version Independent ID: c261afa7-6eb7-b3f0-9f92-6d2f3c5ac336
Content: Markdown syntax for wikis - Azure DevOps
Content Source: docs/project/wiki/wiki-markdown-guidance.md
Service: azure-devops
Sub-service: azure-devops-wiki
GitHub Login: @chcomley
Microsoft Alias: chcomley

@git001 -- Aleks, thank you for your question.  Please consider these resources if you haven't already:

Azure DevOps Services
Azure DevOps on Stack Overflow

The syntax used in Microsoft Learn documentation is:
> [!NOTE]
> Note text text text.

However, I believe this is a local extension to standard Markdown.
cc @chcomley for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Getting a C Linkage error when installing the package

I'm using macOS high sierra as my OS and my python version is 3.7.0
/usr/local/Cellar/python/3.7.0/Frameworks/Python.framework/Versions/3.7/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
        PyObject *curexc_traceback;
                  ^
    15 errors generated.
    error: command 'clang' failed with exit status 1

Has anyone seen a similar issue before? What steps should I take to fix it?

Oh, yeah. This is because c-files were generated under lower version of Python than 3.7.  As workaround you can install Cython beforehand for correctly generate extension. I'll try to fix it in near future

I am having same issue but with Django docker building

I am having same issues but with django docker building


I want to lock 'Gradle' path

Description of the new feature / enhancement
I want to lock 'Gradle' path
Scenario when this would be used?
by locking path
Supporting information
No response

Looking at the gradle docs, you are asking for an "easy" button to do below?  correct?  /needinfo
from https://docs.gradle.org/current/userguide/installation.html#microsoft_windows_users_2:

In File Explorer right-click on the This PC (or Computer) icon, then click Properties → Advanced System Settings → Environmental Variables.
Under System Variables select Path, then click Edit. Add an entry for C:\Gradle\gradle-7.6\bin. Click OK to save.
Alternatively, you could also add the environment variable GRADLE_HOME and point this to the unzipped distribution. Instead of adding a specific version of Gradle to your Path, you can add %GRADLE_HOME%/bin to your Path. When upgrading to a different version of Gradle, just change the GRADLE_HOME environment variable.


Load NAT modules to fix tests involving CRIU

CRIU uses iptables to lock and unlock the network during checkpoint and
restore. If Podman is running in Podman the automatic loading of modules
does not work and thus this commit pre-loads the necessary modules to
make sure the checkpoint test cases are not failing.
Signed-off-by: Adrian Reber<EMAIL_ADDRESS>

@giuseppe

This tries to fix the currently broken CI due to latest CRIU in Fedora 28. Also see https://github.com/containers/libpod/pull/1855 and https://github.com/containers/libpod/pull/1848

tests are passing!
/lgtm

Ahh yeah, it should be fixed now.

bot, retest this please


What's the size of this library when I submit my app on AppStore

Hello guys,
Want to take rid of Realm, and use SwiftyJSON and I'm trying to figure out how many Mb will increase my app when I submit my app on AppStore.
I hope you understand my question.
Thanks.

Hey @unittesting0 ,  you will likely want to perform an ad-hoc export to see the size of each thinned variant of your app anyway. Does not test it but it may works.


Added Operator and Java 1.8 support.

Added TakeWhile operator.
ObserverAdapter added to override only those methods needed from Observer.
Upgraded to Java 1.8 to support lambdas.

@mohammed-rampurawala thanks for the contribution.


[BUG] Failed to run on a fresh install of Ubuntu on bare metal

Describe the bug
Checking free space in home directory... 858 GiB.
  Your node will run as an unpruned full node.
Starting Bitcoin Core... ok.
  Checking the RPC status... error: timeout on transient error: Could not connect to the server <IP_ADDRESS>:8332

Make sure the bitcoind server is running and that you are connecting to the correct RPC port.

[2024-04-07T19:32:54] ERROR: Failed to run line RPC communication failed after 60 seconds.

[2024-04-07T19:32:54] ERROR: Failed to run line 1.

Steps to Reproduce
Expected behavior
Screenshots (optional)
Desktop (please complete the following information):

OS: [e.g. Debian]
Environment [e.g. bare metal, docker]
Release [e.g. 1.0.0]

Additional context
Add any other context about the problem here.

bitcoin-qt: error while loading shared libraries: libxcb-xinerama.so.0: cannot open shared object file: No such file or directory

Fix was sudo apt install libxcb-xinerama0.


Remove transitive gwt module dependency to Stunner.

Hey @mbiarnes @manstis @pefernan @Rikkola ,
Sorry guys, I forgot to remove the gwt module dependency as well in this already merged PR, so here is the fix for it.
PS: It has been impossible for me, during this weekend, to do a full build for master, I'm facing with some compile issues and all seems up to date, so still not sure if it's just my local or something is bad on the repos... Anyway I say this because I was NOT  been able to test this commit - I expect making the repositories compile again, and for the jbpm-wb module  (which still does not depend on Stunner), the docks will appear on the showcase but probably will fail once trying to open it at runtime (as the hardcoded screen ids used for docks should not be present). Tomorrow will try again and see if there is a better fix for this, but meanwhile, I think this should be merged as the build for jbpm-wb was broken.
Thanks in advance!
Roger

Jenkins is failing the build with same error as in my local, that starts to make sense... I think some other repository build is still failed... this error happens in other repositories, not just kie-wb-common

Jenkins please retest this.

Getting the same exception in kie-wb-common when I do a full build with this change. Probably also happens without it.

Jenkins please retest this.


Can't get past "Stuck? Click to go Home screen"

I can't use the application at all. When I start I am shown a screen:
/ (inaccessible)
Stuck? Click to go Home
Clicking does nothing. I can't navigate away from this screen.
Version: v2.9.0 from fdroid
System: LineageOS 17 (Android 10)

Hey. Thanks for the report. I haven't been actively developing this app lately. May be a while before you see a fix for this.
I've noticed a couple reported from people using LineageOS. This problem is probably bigger than it appears.

Hi,
Same problem on a xiami a2 lite with stock Android rom 10
Thanks

:sob: Thanks for the report!

same error on oneplus 5 with oxygenos 10

same error on oneplus 5 with oxygenos 10

Same issue on some cheap Android Go tablet which won't let me use adb (grrr)

Same issue on Motorola One Power with Android 10:

@ScreamingHawk I think labels for this bug should be updated.

I solve this problem by compile this app from master code.
The f-droid version have this problem in my device xiaoxin pad TB-j606f.

Android 10 switched to Scoped Storage which prevents apps from having broad access to the filesystem. Therefore, Slideshow will likely need to transition to using the system file picker to select the folder that the media is located in to support Android 10+. As a workaround on LineageOS devices, enabling root in the system developer settings and enable "Use Device Root" in Slideshow settings might fix the problem, however I don't have a rooted Android 10 device to test this on.

Same problem here.   It works for me on Android 12, and Android 8, but not Android 10.


Flask >=1.1.0: app.logger RecursionError: maximum recursion depth exceeded

This issue started after #2866 got merged in. After this change, I believe the limitation is that you cannot use a logger name with the same name as the Flask App. This issue occurs on version 1.1.0 onwards, 1.0.4 doesn't have this issue. It might break any app that use __name__ as their logger name and flask app name (as long as it's not __main__).
Expected Behavior

When you navigate to http://localhost:5000/test (or any route that will cause a 404), the logger will simply log 404 Error in this code and not cause a stack overflow or thread dump.
#!/usr/bin/env python3
# -*- coding: utf-8 -*-
import logging

from flask import Flask
from flask.logging import default_handler

# Here for illustrative purposes, __name__ is typically used and is why the main issue occurs, but __main__ doesn't cause the issue
app_name = "foo"

# Logger Configured per Flask Instance, uses __name__ typically
logger = logging.getLogger(app_name)

# Other Business Logic
# ...

# Init Flask App
app = Flask(app_name)
# ...
# app.logger.removeHandler(default_handler)  # Causes Thread Dump if commented out or causes Stack Overflow if left...
app.logger.addHandler(logger)  # e.g. https://flask.palletsprojects.com/en/1.1.x/logging/#email-errors-to-admins (example of adding your own handler)

# Setup Routes
# ...

# Setup Error Handler so we can log something...
@app.errorhandler(404)
def not_found_error(error):
    app.logger.warning("404 Error")
    return "", 404

if __name__ == '__main__':
    app.run(host="<IP_ADDRESS>", port=5000, ssl_context=None, debug=False)

Actual Behavior

When you navigate to http://localhost:5000/test (or any route that will cause a 404), the issue will manifest itself and cause a thread dump or stack overflow.
Current thread 0x000123... (most recent call first):
  File "...python3.6/site-packages/werkzeug/local.py", line 72 in __getattr__
  File "...python3.6/site-packages/werkzeug/local.py", line 169 in top
  File "...python3.6/site-packages/flask/globals.py", line 36 in _lookup_req_object
  File "...python3.6/site-packages/werkzeug/local.py", line 307 in _get_current_object
  File "...python3.6/site-packages/werkzeug/local.py", line 329 in __bool__
  File "...python3.6/site-packages/flask/logging.py", line 30 in wsgi_errors_stream
  File "...python3.6/site-packages/werkzeug/local.py", line 307 in _get_current_object
  File "...python3.6/site-packages/werkzeug/local.py", line 348 in __getattr__
  File ".../python3.6/logging/__init__.py", line 996 in emit
  File ".../python3.6/logging/__init__.py", line 865 in handle
  File ".../python3.6/logging/__init__.py", line 1516 in callHandlers
  ...
Thread 0x000456... (most recent call first):
  ...
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)

Environment

Python version: 3.6, 3.7, 3.8
Flask version: >=1.1.0 (issue) and <= 1.0.4 (ok)
Werkzeug version: 0.16.1?

This line in your code is incorrect, it's trying to add a logger as a handler.
app.logger.addHandler(logger)

🤦♂ Sorry for wasting your time with a legacy code issue. Thanks for all your excellent work.


Meteor 1.7 error in server log

Seems for some reason the headers varibale is undefined in Meteor 1.7
error on fast-rendering path: /reset-password ; error: TypeError: Cannot read property '_injectPayload' of undefined
W20180530-09:48:12.562(-7)? (STDERR)     at Object.getData (packages/staringatlights:inject-data/lib/server.js:63:18)
W20180530-09:48:12.562(-7)? (STDERR)     at packages/staringatlights_fast-render.js:212:38
W20180530-09:48:12.563(-7)? (STDERR)     at packages/staringatlights_fast-render.js:288:7

I got this error while implementing tests.
export TEST_BROWSER_DRIVER=phantomjs
export TEST_WATCH=1
meteor test --driver-package meteortesting:mocha --port 3051

What I did was:

create a packages directory in my app,
downloaded the source from this repository and placed it in packages/staringatlights_inject-data
modified this line so that it checks for the presence of headers:

        // server.js line 63
	if (req.headers && req.headers._injectPayload) {

also had to get rid of the entire onTest in package,js but that might be because of my custom setup.

Thanks @TNick, that fixed it.
For the error:

package.js:30:6: Duplicate source file: tests/init.js

you should just remove the line :
// package.js line 27
api.addFiles(['tests/init.js'], 'server')

in package.js
I didn't check if the tests run.
Can you open a pull request with these changes ?

+1 I'm still seeing this error on the project. Any progress with getting it fixed?

Should be fixed in 2.1.1 now. Thanks everyone.


ability to get team list from Gogs

this allows us to use DRONE_TEAMS in 0.5 with Gogs (in addition to GitHub, Bitbucket)


not authorized `copy' @ error/constitute.c

Hi,
can you explain what might be the issue with the following error message:
$ ragoo.py contigs.fa ref.fa
from: can't read /var/mail/collections
[[Bimport-im6.q16: not authorized `copy' @ error/constitute.c/WriteImage/1037.
from: can't read /var/mail/intervaltree
from: can't read /var/mail/ragoo_utilities.PAFReader
from: can't read /var/mail/ragoo_utilities.SeqReader
from: can't read /var/mail/ragoo_utilities.ContigAlignment
from: can't read /var/mail/ragoo_utilities.ContigAlignment
from: can't read /var/mail/ragoo_utilities.ContigAlignment
from: can't read /var/mail/ragoo_utilities.GFFReader
from: can't read /var/mail/ragoo_utilities.utilities
from: can't read /var/mail/ragoo_utilities.break_chimera
/home/user/.local/bin/ragoo.py: line 16: syntax error near unexpected token `('
/home/user/.local/bin/ragoo.py: line 16: `def write_contig_clusters(unique_dict, thresh, skip_list):'

$ python -V
Python 3.6.7

I'm running ubuntu 18.04
installed ragoo in a python3 env
Thanks in advance!
Ulrike

Hi there,
Though you have installed with a virtualenv, it looks like that environment is not active. In fact, I think it is trying to run ragoo.py as a bash script.
Have you activated the virtual environment? Your command prompt should look more like this:
$ (ragoo_VE) ragoo.py contigs.fa ref.fa where "ragoo_VE" is the name of your virtualenv.

/home/user/bin/miniconda2/envs/mypython3/bin/ragoo.py

I suppose the next thing to try is this:
/home/user/bin/miniconda2/envs/mypython3/bin/ragoo.py contigs.fa ref.fa

using the full path prints the same error :/

Hmm so just to double check, even if you run with the full path, you get the following error:
/home/user/.local/bin/ragoo.py: line 16: syntax error near unexpected token `('
Is that right?

no sorry, slightly different
Traceback (most recent call last):
  File "/home/user/bin/miniconda2/envs/mypython3/bin/ragoo.py", line 4, in <module>
    __import__('pkg_resources').run_script('RaGOO==1.2', 'ragoo.py')
  File "/home/user/bin/miniconda2/envs/mypython3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 666, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/home/user/bin/miniconda2/envs/mypython3/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1437, in run_script
    .format(**locals()),
pkg_resources.ResolutionError: Script 'scripts/ragoo.py' not found in metadata at '/home/user/.local/lib/python3.6/site-packages/RaGOO-1.2.egg-info'

Perhaps you could try recreating your virtualenv using --no-site-packages. I am worried that there might be some cross-talk between your python installations.

I'm closing this since this appears to be a problem with your python setup. Though let me know if anything new comes up.

Hi Michael,to sad. I created a new python3 env, with the result:from: can't read /var/mail/collections
import-im6.q16: not authorized copy' @ error/constitute.c/WriteImage/1037. from: can't read /var/mail/intervaltree from: can't read /var/mail/ragoo_utilities.PAFReader from: can't read /var/mail/ragoo_utilities.SeqReader from: can't read /var/mail/ragoo_utilities.ContigAlignment from: can't read /var/mail/ragoo_utilities.ContigAlignment from: can't read /var/mail/ragoo_utilities.ContigAlignment from: can't read /var/mail/ragoo_utilities.GFFReader from: can't read /var/mail/ragoo_utilities.utilities from: can't read /var/mail/ragoo_utilities.break_chimera /home/user/.local/bin/ragoo.py: line 16: syntax error near unexpected token ('
/home/user/.local/bin/ragoo.py: line 16: `def write_contig_clusters(unique_dict, thresh, skip_list):'
If somebody else is coming up with that issue it would be great if you could keep me up to date.By the way, did you ever compared the performance of RaGOO with multi-CSAR?
Best wishes,Ulrike
Am Mittwoch, 10. April 2019, 15:21:06 MESZ hat Michael Alonge<EMAIL_ADDRESS>Folgendes geschrieben:
I'm closing this since this appears to be a problem with your python setup. Though let me know if anything new comes up.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi there,
I will definitely keep you posted if someone else has similar problems.
And multi-CSAR is for scaffolding based on multiple reference genomes, whereas RaGOO is only for a single reference and a single set of contigs.

Hi There,
I think I might have figured out what went wrong. I need to add a shebang to the script files. Can you please download the latest code from github and try again?

Hi there - I am fairly certain this issue has been resolved, but please reopen if not.


Next release date

Hello guys,
Can you share your plans on next release date, please? It's been a while since the last release in Oct 2014, and I'd very like to see new FactoryGirl release (especially additional data in instrumentation changes).
Thanks!

Ditto. I'm missing the traits: true option of FactoryGirl.lint (i.e. this) which is present on master (and is documented in the README) but is not yet released. :+1: Thanks

Looks like this was released in https://github.com/thoughtbot/factory_girl/releases/tag/v4.7.0

Yay! Thanks for notifying! ❤


Add analytics to elixir

Adding Analytics do Elixir section.

Sorry, I just noticed Plausible Analytics is already there.
So I'm going to close this PR.


Implement funders page

The /funding route is currently implement as a blank page (see https://elixir-cloud.dcc.sib.swiss/funding).
We have now created a Notion page/table with one funding instrument per row. This table should be used to implement the funding page, showing one card per funding instrument/row, quite similar to, e.g., the /partners page: https://elixir-cloud.dcc.sib.swiss/partners
The table has the following properties:

Name
Notion type

Instrument
Title

ProjectTitle
Text

Recipients
Multi-select

Duration
Date (includes end date!)

Website
URL

Icon
URL

IconDark
URL

Here is a mock up of what the card could look like:

And here is an example row of the Notion table:

The following behaviors should be implemented:

A search bar (just like on the /partners page: https://elixir-cloud.dcc.sib.swiss/partners)
Sort order by

end date (from Duration); descending
start date (from Duration); ascending
Instrument; ascending
ProjectTitle; ascending
In other words, ongoing or most recent funding should be on the top, with the ones extending most into the future appearing first (hence descending order of end date); in case of equal end dates, longer running funding instruments should appear before shorter ones (hence ascending order of start date); if there are still ties, instruments should then be alphabetically sorted by instrument name first, and project title second

Clicking on a card should lead to the Website
Above the search box and the cards, there should be a clearly visible banner or similar saying "We would like to express our gratitude to our funders" (or similar)

Great work @tanya17-05, can you please change the fonts/formats for the subheadings according to the ones in the contributor's screen.

Sure @git-anurag-hub


[bp-2.2] Comment out tests that may cause ocp api server to degrade

issue reference:

https://github.com/stolostron/multicloud-operators-foundation/issues/684
https://github.com/stolostron/multicloud-operators-foundation/issues/686

/cc @zhiweiyin318 @ldpliu

/lgtm


Save user when they sort the channel list

That, yes! :+1 and merging.

 Yes please!


unittest_windows_gpu_py3.8  CI failing

"torch.cuda.is_available() is False"
+ '[' 3.8 == 3.6 ']'
++ python -c 'import torch; print(torch.cuda.is_available())'
+ torch_cuda=False
+ echo torch.cuda.is_available is False
torch.cuda.is_available is False
+ '[' '!' -z 11.1 ']'
+ '[' False == False ']'
+ echo 'torch with cuda installed but torch.cuda.is_available() is False'
torch with cuda installed but torch.cuda.is_available() is False
+ exit 1

https://app.circleci.com/pipelines/github/pytorch/vision/11101/workflows/fe23d326-ed62-4477-86b6-61432ca4c238/jobs/854690
https://app.circleci.com/pipelines/github/pytorch/vision/11099/workflows/5aaea50a-e67f-4770-9e9e-f212d39733d8/jobs/854513
cc @peterjc123 @nbcsm @guyang3532 @maxluk @gunandrose4u @mszhanyi @seemethere

This has occurred once again.
https://app.circleci.com/pipelines/github/pytorch/vision/11304/workflows/14a92f57-9098-4519-abbc-48b5ad8cb8b2/jobs/874287

@prabhat00155 @oke-aditya It has been fixed by #4788
If you came across again, please feel free to reopen it.


[Bug]: wasm-types manifesh doesnt match with what is expected by wadm.

Currently , Link property struct is defined as :
pub struct LinkProperty {
    /// WIT namespace for the link
    pub namespace: String,
    /// WIT package for the link
    pub package: String,
    /// WIT interfaces for the link
    pub interfaces: Vec<String>,
    /// Configuration to apply to the source of the link
    #[serde(default, skip_serializing_if = "Option::is_none")]
    pub source: Option<ConfigDefinition>,
    /// Configuration to apply to the target of the link
    pub target: TargetConfig,
    /// The name of this link
    #[serde(skip_serializing_if = "Option::is_none")]
    pub name: Option<String>,

    #[serde(default, skip_serializing)]
    #[deprecated(since = "0.13.0")]
    pub source_config: Option<Vec<ConfigProperty>>,

    #[serde(default, skip_serializing)]
    #[deprecated(since = "0.13.0")]
    pub target_config: Option<Vec<ConfigProperty>>,
}

But WADM requires target to be a string :
 - type: link
          properties:
            target: http-component
            namespace: wasi
            package: http
            interfaces: [incoming-handler]

@ritesh089 this is actually by design, since we've moved to the new format of
target:
  name: <name>

instead of just a String name. You can see below in the custom deserialize code how we're converting the older format to thew new https://github.com/wasmCloud/wadm/blob/main/crates/wadm-types/src/lib.rs#L432

Thank you. Closing the issue .


LINK-1646 | Bump HDS to version 3.0.0 and update header

Description

Bump HDS to version 3.0.0
Change HDS Navigation component to Header component

Closes
LINK-1646
Screenshot

Codecov Report

Merging #91 (bbe873c) into develop (51d5dd7) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop      #91   +/-   ##
========================================
  Coverage    99.64%   99.64%
========================================
  Files          151      154    +3
  Lines         2820     2822    +2
  Branches       455      457    +2
========================================
+ Hits          2810     2812    +2
  Misses          10       10

Files
Coverage Δ

src/domain/app/cookieConsent/CookieConsent.tsx
100.00% <100.00%> (ø)

src/domain/app/header/Header.tsx
100.00% <100.00%> (ø)

...ctionBarDropdownButton/ActionBarDropdownButton.tsx
100.00% <100.00%> (ø)

...ionBarDropdownDivider/ActionBarDropdownDivider.tsx
100.00% <100.00%> (ø)

...ctionBarDropdownHeader/ActionBarDropdownHeader.tsx
100.00% <100.00%> (ø)

src/domain/auth/utils.ts
100.00% <100.00%> (ø)

src/hooks/useSelectLanguage.ts
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Looks good, seems to mostly work.
Two things I noticed:
a) The close text in right corner of the screenshot is clearly missing translations (was there on testing aswell)
b) For some reason, when on the base url (localhost:3001) the finnish language doesn't work locally? Not sure if this is a feature or not but thought I should mention it. Translations work properly on other 404 pages like '/asd'.

Looks good, seems to mostly work. Two things I noticed: a) The close text in right corner of the screenshot is clearly missing translations (was there on testing aswell) b) For some reason, when on the base url (localhost:3001) the finnish language doesn't work locally? Not sure if this is a feature or not but thought I should mention it. Translations work properly on other 404 pages like '/asd'.

Added translations for the close text
Added prefix to default locale to avoid problems with automatic language detection. See https://nextjs.org/docs/pages/building-your-application/routing/internationalization#prefixing-the-default-locale


Feature/ss4 compatibility

This is an update to my previous ss4 compatibility PR. This will get blocks in working order on SS4, until PRs and issues are solved with GridFieldExtensions and a PR from MultiValueField I have made there will still be issues however.

@sheadawson any update on merging this?


Add cmd framework for core, gateway

:tickets: Ticket(s): Closes #37

:construction_worker: Changes
@Rahman2600 was having issues with loading env variables, and env variables in general are pretty awkward to work with cross-platform for dev, so this PR adds a framework (spf13/cobra) and utility lib (libcmd), on which to build CLI's (Command Line Interfaces) for core and gateway.
make pinpoint-core, make pinpoint-gateway builds the binary into ./bin as pinpoint-core and pinpoint-gateway. Options are now set on command line via flags. For example:
./bin/pinpoint-core run --dev --port 1234
./bin/pinpoint-gateway run --dev --core.port 1234

--dev can also be configured via MODE=development in env as before
Despite these changes, the old methods of starting up services via make core, and make gateway should still work
The diff is big, but a good chunk of it is just tests
:flashlight: Testing Instructions
make pinpoint-core ; ./bin/pinpoint-core run --dev
make pinpoint-gateway ; ./bin/pinpoint-gateway run --dev

OR:
make core
make gateway

THEN:
curl localhost:8081/status

todo

[x] tests!

LGTM


cleaning up existing dataset test cases

Description

Cleaning up existing dataset test cases
Adding more Variablesized Dataset tests

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

adding huge amounts of samples (over 100k in a dataset)
adding huge amounts of datasets (>50)
iterating over datasets and dataset samples with the keys(), values(), and items() methods.
explicitly testing the dictionary style set/get/delete methods (to ensure the corresponding "dunder" methods are working) separately from the named add(), get(), and remove() methods.

I would add 1, 2 & all other stress testing stuff to another PR and keep those as separate test cases so that if people want to skip those while running tests. Will add others to this PR itself

@rlizzo This can be merged

Looks good. Merging now.


MetaQuest2 left eye freeze or desync when recording is started

A game running on MetaQuest2 will often either freeze the left eye or have it be out of sync with the right eye when the onboard recording feature is started.
The problem persists when the recording is stopped.
It can be recovered from by double tapping the headset to switch to passthrough and then double tap to get back to the game.
The problem goes along with those errors in the adb log
05-14 13:00:00.238  9564  9622 W OpenXR  : xrReleaseSwapchainImage: No image has been waited on
05-14 13:00:00.238  9564  9622 E godot   : ERROR: OpenXR failed to release swapchain image!  [XR_ERROR_CALL_ORDER_INVALID]
05-14 13:00:00.238  9564  9622 E godot   :    at: xr_result (../../../../../src/openxr/OpenXRApi.h:343) - OpenXR failed to release swapchain image! [XR_ERROR_CALL_ORDER_INVALID]

We've also run into this exact same issue (same adb log errors, same observed behavior). Tracing through every line of the log, it's very clear that the issue happens exactly when returning from passthrough mode to regular play mode.
Some extra context from our experiments:

It seems to require that the time to render a frame be sufficiently high. We narrowed it down to a case where, when rendering one (reasonably) large mesh, the issue was relatively consistent, vs when not rendering that mesh (which made it impossible for us to trigger). As a result, our guess is some sort of race condition in openXR (or something lower level).

We found two relatively easy ways to trigger the issue: First, by double tapping to enable passthrough, then double tapping to disable it. This would sometimes cause the issue, and as mentioned above, it also sometimes fixes the issue.  The second way that relatively reliable triggers the issue is by walking sufficiently far outside of any boundary for a little while, then returning to the play area. Note that neither of these methods is perfectly consistent, but they cause the issue about ~40% of the time.

The issue seems entirely avoidable by not enabling passthrough and not moving your head out of the play area.

We're running with GLES3, and our current framerate is relatively low (~30 FPS). We've reproduced it on multiple MetaQuest2 headsets (all of which are running with the most recent updates). We're on Godot 3.4.4. We're not doing anything super fancy on the rendering side (things like SSAO, etc are all disabled)
My guess is that a minimal reproduction would be "make a scene with some meshes large enough to drop the framerate, walk outside of the play area for a bit and come back a few times".
If that doesn't work or we can provide any more details, please let me know!

@joshalbrecht we have a temporary workaround for this.
If you want to try it copy the two .so files from the zip over the files in godot-openxr/bin/android
openxr_swapchain_fix.zip

Just following up--this seems to have worked for us, as we haven't seen the issue since using the new .so's.
Thanks a bunch!

The 1.3.0 version of the plugin now has @mgschwan fix in it so I'm closing this issue.


feat(typing): add type hints

Didn't use TypeAlias bc it's python>=3.10 so it would require typing_extensions (can be added if necessary).
quality_and_fitness_parsed declares rtype: (float,int) but the second value adds value of q, which may be float.

Wow, we were not really planning much development here

I wanted to do #50 and it always helps to know what's being passed around.

shouldn't we include an empty py.typed file

I'll take a look what to do about py.typed file in this case. Might need to move code to mimeparse/__init__.py, like you've said.

Furthermore, running mypy tells me there is room for improvement

I did check with mypy, and the return type hints are correct, only at some point inside functions the variables don't match them.
For example a weight is initialized with 0 and then at some point a float is added, or dict value is set to None and then overridden with some other value  🤷.
I wanted to keep the change minimal so I've decided to keep it. I'm happy to change it if you're planning to add pre-commit with mypy ;)

Hm, I'm no expert at typing, but I think it would be good to check Mypy's output and see if we can fix the code inside the functions too.
Otherwise, if we just care about the user experience for using mimeparse, maybe we should simply a stubs instead?
What do you think @CaselIT?

Wow, we were not really planning much development here

Do you consider this package as internal to falconry? No problem, I can always fork.

Wow, we were not really planning much development here

Do you consider this package as internal to falconry? No problem, I can always fork.

No, not internal at all. We are actually thinking even to reimplement parts of it an unvendor it from Falcon completely.
By writing that, I just meant that this package didn't attract many contribution in the 8 years since the last release :slightly_smiling_face:

$ mypy mimeparse
Success: no issues found in 1 source file

Yeah, I see that. I thought the changes wouldn't cause any issue, didn't think to run the tests :/

I use it in my project, and I really like having less code to maintain, so...


Issue with Ports

Hi!
When I run docker-compose up I'm getting the following error
▶ docker-compose up
demyx_socket is up-to-date
Starting demyx_traefik ... error

ERROR: for demyx_traefik  Cannot start service demyx_traefik: Ports are not available: listen tcp <IP_ADDRESS>:80: bind: address already in use

ERROR: for demyx_traefik  Cannot start service demyx_traefik: Ports are not available: listen tcp <IP_ADDRESS>:80: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Hi @adibhanna, port 80 is already in used. Is nginx or apache running already?

Closing for inactivity.


Add tracking of funded account requiring deposits

Update  schema: Account

Add fundedAccountNeedsDeposit (boolean flag) so we can track that we have created a particular account using the funded account flow, and nobody has yet sent any funds to it.

Update existing endpoint: POST /fundedAccount

Set fundedAccountNeedsDeposit to true on the Account table record we write.

New endpoint: POST /fundedAccount/clearNeedsDeposit

Clear the initial funded account balance tag from the account record, but only if the current account balance is greater than the minimum account balance (to avoid abuse)

New endpoint: GET /walletAccountState

Return JSON object for current wallet account state -- this is not for fetching on-chain data about the account, but is specifically for fetching metadata that is relevant to the wallet representation of an account that is backed by an on-chain account :)
Currently, just the fundedAccountNeedsDeposit will be sent by this endpoint.  In the future we will likely add other metadata.  e.g. darkMode: true, hidePreviouslyTradedTokens: [...] etc.

NOTE: Original implementation idea was to track the exact amount of funds the account was created with, but would have required backfilling existing account records to change the value if we changed the funded account amount in the future.
After talking it over with @stefanopepe, we decided to make this a boolean flag instead, so our comparison logic will always use the current value that we need deposited to consider the account funded.  Making the amount dynamic rather than setting it explicitly per account means that:

If someone creates an account, doesn't deposit any funds for quite some time, and the amount we require goes down (most likely given the assumption that NEAR tokens will increase in value), then the user can deposit a lower amount and still have the 'lock' removed.  This way if someone creates an account but doesn't fund it for an extended period of time, they aren't forced to send a large $$ value amount of NEAR to fund their account just because they first created it a long time ago.

We never need to backfill existing account records to 'fix' an excessively high or low requirement for funding due to changes in the required amount over time.

What is the related frontend issue&PR? It may help to keep these two related

Added link to https://github.com/near/near-wallet/issues/1752 in the description :)


minor fix for multiline yaml in README

Turned the third policy description in the policy yaml example into a literal block as per the description blocks above it

Thanks! Would you mind signing the contributor agreement linked at the bottom of the readme

No worries. Done


ERROR:autopilot:ARMING MOTORS

Help me out, I am new to Dronekit-python, My goal is to use dronekit python on sitl.
My system is ubuntu 18.04
I am running  $dronekit-sitl copter in one terminal and tried to connect with it from another.
I test it with the sample script.
$python simple_goto.py
But it looks like it is not changing mode and is failed as it tried to arm the motor.

Did you solve this problem? I am taking this error too.

Same issue for me, for this script specifically and my own, which all run successfully on an older install.

Same error... when trying to takeoff the SITL, is not gaining altitude due to the same problem. It was working before the last update.

For me this was caused by the vehicle state not changing to guided mode. I reinstalled an older version of mavlink as per this comment https://github.com/dronekit/dronekit-python/issues/1041#issuecomment-660750737. This solved the problem for me

This problem has persisted but when I downgrade, it produces a haystack of a mess

This problem has persisted but when I downgrade, it produces a haystack of a mess

For me this was caused by the vehicle state not changing to guided mode. I reinstalled an older version of mavlink as per this comment #1041 (comment). This solved the problem for me

thanks @DavidM-GitHub , this work for me

Hello
is there anyone with a solution to this problem


MaximumLength validator error message is wrong

When using the MaximumLength validator, the error message (for MaximumLength(255)) reports:
'Property' must be less than 255 characters. You entered 256 characters.
It should be either:
'Property' must be less than or equal to 255 characters. You entered 256 characters.
'Property' must be less than 256 characters. You entered 256 characters.

Thanks - I've gone with second option as it doesn't require re-translating all of the localized messages. This is checked in and will be in the next release.


Console error message missing when sprite compilation failed

Currently, when you've got an error in your grunt config which will lead to compilation error, you will see that everything is alright and it's misleading:
Tomasz.Ducin@WAWLT548 ~/Tests/svg-sprite-test
$ grunt --force
Running "svg_sprite:basic" (svg_sprite) task

Running "svg_sprite:basic2" (svg_sprite) task

Running "svg_sprite:flags" (svg_sprite) task

Done, without errors.

And the truth is that spriter.compile(function(error, result) { ... } throws an error in fact. Currently, it is handled in the following way:
if (error) {

} else {

which I find a very bad solution. I suggest to provide a standard grunt fail output so that the developer at least knows, that something is wrong with his configuration (e.g. grunt.fail).

The solution for this is done in #39.

Hey @tkoomzaaskz,
awesome — thanks for this contribution. I must have overseen that I never finished that one! :+1:
Cheers,
Joschi


ISO does not support UEFI boot mode

On bare metal using UEFI boot mode the v0.2.0-rc4 ISO is not recognized as bootable.

Please try v0.2.0-rc6, this should be fixed now.

Version - v0.2.0
Verified fixed


EPIC: Community contribution pt II

What
Look at how we can enable community contributions for the service manual.
Why
For the service manual to grow and develop to meet its users' needs and maintain consistent, usable NHS products and services, we need teams to raise and discuss issues they face and tell us how things test with users.
Without regular contributions, the service manual will ultimately fail.
Must
Do it next HMW

[ ] Brainstorm session to generate ideas against HMW pt III
[ ] Brainstorm session to generate ideas against HMW pt IV
[ ] Matrix & Measurements of top ideas to test against HMW pt II

Do it later HMW

[ ] Brainstorm session to generate ideas against HMW pt V
[ ] Brainstorm session to generate ideas against HMW pt VI
[ ] Matrix & Measurements of top ideas to test against HMW pt III

Measure success

[ ] Baseline GitHub contribution figures - to help us measure success

Related
#685

@davidhunter08 - I have boxed off the follow up 'HMW' into this epic to be picked up later on. It would be great to do this with the community as a co-design brainstorm session


Keras Error : Unknown entries in loss dictionary: ['ctc']. Only expected following keys: ['dense_1']

I am new on Keras and I want to use CTC loss to compile my model. But it raised the error just
like what title says. Can anyone help me? The following is my code.

This is my ctc loss:
def ctc_lambda_func(args):     y_pred, labels, input_length, label_length = args     return K.ctc_batch_cost(labels, y_pred, input_length, label_length)
This is my compiling code:
model.compile(loss={'ctc': lambda y_true, y_pred: y_pred}, optimizer='Adam')

You should create model before compile:
    def ctc_lambda_func(args):
        y_pred, labels, input_length, label_length = args
        return K.ctc_batch_cost(labels, y_pred, input_length, label_length)

    loss_out = Lambda(
        ctc_lambda_func, output_shape=(1,),
        name='ctc')([out, labels, input_length, label_length])

    model = Model(inputs=[image, labels, input_length, label_length], outputs=loss_out)

    sgd = SGD(lr=0.02,
              decay=1e-6,
              momentum=0.9,
              nesterov=True)

    model.compile(loss={'ctc': lambda y_true, y_pred: y_pred}, optimizer=sgd)

I'm having the same error, but when trying to execute multi_gpu_model before model.compile in order to make the model be trained on multiple gpus. If I run this:
    def ctc_lambda_func(args):
        y_pred, labels, input_length, label_length = args
        return K.ctc_batch_cost(labels, y_pred, input_length, label_length)

    loss_out = Lambda(
        ctc_lambda_func, output_shape=(1,),
        name='ctc')([out, labels, input_length, label_length])

    model = Model(inputs=[image, labels, input_length, label_length], outputs=loss_out)

    sgd = SGD(lr=0.02,
              decay=1e-6,
              momentum=0.9,
              nesterov=True)
    model = multi_gpu_model(model, gpus=2)
    model.compile(loss={'ctc': lambda y_true, y_pred: y_pred}, optimizer=sgd)

I then get this error:
ValueError: Unknown entry in loss dictionary: "ctc". Only expected the following keys: ['concatenate_1']


【Update Question】About New DLC

New DLC is coming Do you intend to update the archive analysis of new DLC content, such as the byte address correspondence table of new bosses, the correspondence table of new equipment, etc. I am very interested in your project and look forward to your updates. Or would you like to share how to get the correspondence between the BOSS address and the equipment address?

Hello! I actually didn't found these ID's by myself. I found it somewhere I don't even remember. And after DLC release (may be 4-6 weeks) I'll search for new ID's on the internet.
I remember that The Grand Archives's discord have some useful information, you can search there.
Also here is some useful table.


Cookie cutter initial template

TL;DR
Add a command to generate the boilerplate for flyte-ready repos.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
This PR defines a new pyflyte command called init that takes a template and a project name as arguments. These are used to call the template engine provided by cookiecutter.
In terms of where templates are stored, we defined a cookiecutter template in https://github.com/flyteorg/flytekit-python-template/pull/16. Note how we have the ability to keep multiple templates in the same repo, the idea being that we're going to expose them using different templates under the pyflyte init command.
The pyflyte init command defaults to "simple-example" cookiecutter template and this template prompts the user for 2 additional inputs:

app: which is the top-level directory under project-name that will store the actual workflow
workflow: the name of the example workflow.

All inputs have default values.
Also worth noting that the command does not clobber existing user code, i.e. the command fails if the user attempts to overwrite a directory by re-running the command.
Here's how the help provided by click looks like:
❯ pyflyte init --help
...
Usage: pyflyte init [OPTIONS] PROJECT_NAME

  Create flyte-ready projects.

Options:
  --template TEXT  cookiecutter template to be used
  --help           Show this message and exit.

Tracking Issue
https://github.com/flyteorg/flyte/issues/1799
Follow-up issue
NA

Unit test is failing. Fix in https://github.com/flyteorg/flytekit/pull/739.

Only the code coverage tasks are failing.

Small comment then +1


IGNORE - Breaks EE for teamcity job test

Yayy! It worked - https://teamcity.mesosphere.io/viewLog.html?buildId=767912&tab=buildResultsDiv&buildTypeId=ClosedSource_MesosphereEnterpriseDcOs_CosmosEnterprise_IntegrationTestsWithCosmo


Add touchPan option for disabling touch pan

Not quite ready since the static START was referenced outside of Draggable.js
The documentation also needs to be updated. Where is this kept?

Not updated since a long time ago, and we changed lots of touch stuff due to the Chrome 55 PointerEvents. Closing for now.


[HxGrid] Supporting data loading from outside

I have a scenario where I need to prepare data outside of HxGrid before passing it to the Data Provider. This results in no progress indication being displayed, and I have to address it using the following hack:
@if (_dataLoaded)
{
	<HxProgressIndicator InProgress="@(!_dataLoaded)" />
}
else
{
	<HxGrid ...>
}

Is it possible to add support for displaying placeholder rows based on a condition passed from the parent component?

BTW, I just found a forgotten InProgress parameter of the HxGrid which might help you to achieve what you wanted.


Pilot: Fails because url is incorrect format.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
upload_to_testflight fails after waiting for the build to finish processing with the error
An attribute value has invalid url. - The format of the url is invalid. - marketingUrl
An attribute value has invalid url. - The format of the url is invalid. - privacyPolicyUrl

Those two fields are using the exact same files that deliver uses, and deliver is able to complete without an issue.
The URLs have the format https://www.example.com/path. The files do have a trialing newline. Is it possible the deliver is handling that but pilot isn't?
Command executed
This is run inside a custom lane, but it also has the same issue when run individually.
    upload_to_testflight(
      beta_app_review_info: {
        contact_email: File.read("metadata/review_information/email_address.txt"),
        contact_first_name: File.read("metadata/review_information/first_name.txt"),
        contact_last_name: File.read("metadata/review_information/last_name.txt"),
        contact_phone: File.read("metadata/review_information/phone_number.txt"),
        demo_account_required: true,
        demo_account_name: File.read("metadata/review_information/demo_user.txt"),
        demo_account_password: File.read("metadata/review_information/demo_password.txt"),
        notes: File.read("metadata/review_information/notes.txt")
      },
      localized_app_info: {
        "default": {
          feedback_email: "[REDACTED]",
          marketing_url: File.read("metadata/en-CA/marketing_url.txt"),
          privacy_policy_url: File.read("metadata/en-CA/privacy_url.txt"),
          description: File.read("metadata/en-CA/description.txt"),
        }
      },
      skip_submission: true,
    )

Complete output when running fastlane, including the stack trace and command used

[16:01:27]: ----------------------------------
[16:01:27]: --- Step: upload_to_testflight ---
[16:01:27]: ----------------------------------
[16:01:27]: Creating authorization token for App Store Connect API
[16:01:33]: Ready to upload new build to TestFlight (App:<PHONE_NUMBER>)...
[16:01:34]: Going to upload updated app to App Store Connect
[16:01:34]: This might take a few minutes. Please don't interrupt the script.
[16:03:04]: iTunes Transporter successfully finished its job
[16:03:04]: --------------------------------------------------------------------
[16:03:04]: Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online.
[16:03:04]: --------------------------------------------------------------------
[16:03:04]: Successfully uploaded the new binary to App Store Connect
[16:03:04]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
[16:03:04]: Note that if `skip_waiting_for_build_processing` is used but a `changelog` is supplied, this process will wait for the build to appear on AppStoreConnect, update the changelog and then skip the remaining of the processing steps.
[16:03:04]: Waiting for processing on... app_id:<PHONE_NUMBER>, app_version: 2021.7, build_version: 7864, platform: IOS
[16:03:05]: Read more information on why this build isn't showing up yet - https://github.com/fastlane/fastlane/issues/14997
[16:03:05]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:03:36]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:04:06]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:04:37]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:05:07]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:05:37]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:06:08]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:06:38]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:07:08]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:07:39]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:08:09]: Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
[16:08:47]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:09:18]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:09:49]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:10:20]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:10:51]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:11:22]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:11:57]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:12:27]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:12:58]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:13:29]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:14:00]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:14:31]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:15:02]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:15:33]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:16:04]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:16:35]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:17:06]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:17:37]: Waiting for App Store Connect to finish processing the new build (2021.7 - 7864) for IOS
[16:18:08]: Successfully finished processing the build 2021.7 - 7864 for IOS
+--------------------+----------------------------------------------------------------------------------------------+
|                                                   Lane Context                                                    |
+--------------------+----------------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM   | ios                                                                                |
| PLATFORM_NAME      | ios                                                                                |
| LANE_NAME          | ios production_testflight                                                                    |
| SIGH_PROFILE_PATH  | /Users/vagrant/git/AppStore_com.neofinancial.neo.mobileprovision                             |
| SIGH_PROFILE_PATHS | ["/Users/vagrant/git/AppStore_com.neofinancial.neo.mobileprovision"]                         |
| SIGH_UDID          | 2698b2d4-8b3b-4c80-8dba-8c5725111081                                                         |
| SIGH_UUID          | 2698b2d4-8b3b-4c80-8dba-8c5725111081                                                         |
| SIGH_NAME          | com.neofinancial.neo AppStore                                                                |
| SIGH_PROFILE_TYPE  | app-store                                                                                |
| IPA_OUTPUT_PATH    | /Users/vagrant/git/Neo.ipa                                                                   |
| XCODEBUILD_ARCHIVE | /Users/vagrant/Library/Developer/Xcode/Archives/2021-05-05/Neo 2021-05-05 15.55.47.xcarchive |
| DSYM_OUTPUT_PATH   | /Users/vagrant/git/Neo.app.dSYM.zip                                                          |
+--------------------+----------------------------------------------------------------------------------------------+
[16:18:09]: An attribute value has invalid url. - The format of the url is invalid. - marketingUrl
An attribute value has invalid url. - The format of the url is invalid. - privacyPolicyUrl
+------+---------------------------+-------------+
|                fastlane summary                |
+------+---------------------------+-------------+
| Step | Action                    | Time (in s) |
+------+---------------------------+-------------+
| 1    | default_platform          | 0           |
| 2    | app_store_connect_api_key | 0           |
| 3    | get_provisioning_profile  | 3           |
| 4    | build_ios_app             | 353         |
| 💥   | upload_to_testflight      | 1001        |
+------+---------------------------+-------------+
[16:18:09]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
➡  Having deliver/upload_to_app_store issues? Install 2.150.0.rc5
    https://github.com/fastlane/fastlane/issues/16639 [closed] 116 💬
    04 Sep 2020
🔗  You can ⌘ + double-click on links to open them directly in your browser.
#######################################################################
# fastlane 2.182.0 is available. You are on 2.181.0.
# You should use the latest version.
# Please update using `bundle update fastlane`.
#######################################################################
bundler: failed to load command: fastlane (/Users/vagrant/git/bundle-gems/ruby/2.6.0/bin/fastlane)
Spaceship::UnexpectedResponse: [!] An attribute value has invalid url. - The format of the url is invalid. - marketingUrl
An attribute value has invalid url. - The format of the url is invalid. - privacyPolicyUrl
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/api_client.rb:199:in `handle_response'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/api_client.rb:135:in `patch'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/testflight/testflight.rb:67:in `patch_beta_app_localizations'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/2.6.0/forwardable.rb:230:in `patch_beta_app_localizations'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:504:in `update_localized_app_review_for_lang'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:491:in `block in update_localized_app_review'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:487:in `each'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:487:in `update_localized_app_review'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:233:in `update_beta_app_meta'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:159:in `distribute'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:62:in `upload'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:31:in `run'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
  Fastfile:68:in `block (2 levels) in parsing_binding'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in `take_off'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/gems/fastlane-2.181.0/bin/fastlane:23:in `'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/bin/fastlane:23:in `load'
  /Users/vagrant/git/bundle-gems/ruby/2.6.0/bin/fastlane:23:in `'

Environment

 [10:29:57]: Generating fastlane environment output, this might take a few seconds...
🚫 fastlane environment 🚫
Stack

Key
Value

OS
11.2.3

Ruby
2.6.5

Bundler?
true

Git
git version 2.30.2

Installation Source
~/.rvm/gems/ruby-2.6.5/bin/fastlane

Host
macOS 11.2.3 (20D91)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.6.5/lib

OpenSSL Version
OpenSSL 1.1.1d  10 Sep 2019

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode-12-4.app/Contents/Developer/

Xcode Version
12.4

System Locale

Variable
Value

LANG
en_CA.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

require_relative 'Configurations'

default_platform(:ios)

platform :ios do
  before_all do |lane|
    ENV["FASTLANE"] = "1"
  end

  after_all do |lane|
    if !ENV["CI"]
      clean_build_artifacts
    end
  end

  desc "Runs the tests for the app."
  lane :test do
    run_tests
  end

  lane :staging do
    app_store_connect_api_key(
      in_house: false
    )

    get_provisioning_profile(
      adhoc: true,
      skip_certificate_verification: true,
      force: true,
      template_name: "ApplePay In-App Provisioning Distribution"
    )

    build_ios_app(
      export_options: {
        compileBitcode: false
      }
    )

    sentry_upload_dsym
  end

  lane :production_testflight do
    app_store_connect_api_key(
      in_house: false
    )

    get_provisioning_profile(
      skip_certificate_verification: true
    )

    build_ios_app

    upload_to_testflight(
      beta_app_review_info: {
        contact_email: File.read("metadata/review_information/email_address.txt"),
        contact_first_name: File.read("metadata/review_information/first_name.txt"),
        contact_last_name: File.read("metadata/review_information/last_name.txt"),
        contact_phone: File.read("metadata/review_information/phone_number.txt"),
        demo_account_required: true,
        demo_account_name: File.read("metadata/review_information/demo_user.txt"),
        demo_account_password: File.read("metadata/review_information/demo_password.txt"),
        notes: File.read("metadata/review_information/notes.txt")
      },
      localized_app_info: {
        "default": {
          feedback_email<EMAIL_ADDRESS>          marketing_url: File.read("metadata/en-CA/marketing_url.txt"),
          privacy_policy_url: File.read("metadata/en-CA/privacy_url.txt"),
          description: File.read("metadata/en-CA/description.txt"),
        }
      },
      skip_submission: true,
      skip_waiting_for_build_processing: true,
    )
  end

  lane :upload_metadata do
    app_store_connect_api_key(
      in_house: false
    )

    deliver(
      skip_binary_upload: true,
      overwrite_screenshots: true,
      precheck_include_in_app_purchases: false
    )
  end

  desc "Uploads the app privacy details to the app store"
  desc "Requirements:"
  desc " - must be run manually (for now)"
  desc " - an admin or higher member of the development team"
  desc " - the ability to use two factor authentication for that user"
  desc "   - this is because application specific passwords and the App Store Connect API key dont have access to the app privacy details"
  lane :upload_app_privacy_details do
    # Info about uploading privacy details and the expected json format.
    # https://github.com/fastlane/fastlane/pull/17592
    upload_app_privacy_details_to_app_store(
      json_path: "fastlane/metadata/app_privacy_details.json"
    )
  end

  desc "Adds a device to the developer account and triggers a new bitrise build"
  desc "Requires the BITRISE_APP_SLUG and BITRISE_ACCESS_TOKEN environment variables to be set (optionally in a .env file)"
  desc "Options:"
  desc "- `name`\n  - The name of the persion the device belongs to"
  desc "- `device_type`\n  - The type of the device. ex. iPhone 12 Pro, iPad Air (4th Generation)"
  desc "- `udid`\n  - The UDID for the device"
  desc "- `skip_build:true`\n  - Skips triggering a bitrise build"
  lane :add_device_to_staging do |options|
    skip_build = options[:skip_build] || false

    bitrise_username = ENV["BITRISE_USERNAME"] unless ENV["BITRISE_USERNAME"].nil? || ENV["BITRISE_USERNAME"].empty?
    UI.user_error! "Missing environment variable: BITRISE_USERNAME" unless bitrise_username || skip_build

    user_name = options[:name] || UI.input("Who does the device belong to?")
    device_type = options[:device_type] || UI.input("What kind of device is it? ex. iPhone 12 Pro, iPad Air (4th Generation)")
    udid = options[:udid] || UI.input("What is the devices UDID?")

    name = "#{user_name} - #{device_type}"

    UI.confirm("Device Information\nName: #{name}\nUDID: #{udid}\n\nIs this infomrmation correct?") || next

    register_device(
      name: name,
      udid: udid
    )

    !skip_build && UI.confirm("Do you want to trigger a bitrise build?") || next

    trigger_bitrise_workflow(
      workflow: "staging",
      branch: "develop",
      build_message: "Fastlane - Add Device to Staging - #{name}",
      triggered_by: "@#{bitrise_username}"
    )
  end

  desc "Renew provisioning profiles"
  desc "Options:"
  desc "- `all:true`\n  - Try to renew all provisioning profiles"
  desc "- `local:true`\n  - Renew the local provisioning profiles"
  desc "- `staging_debug:true`\n  - Renew the staging debug provisioning profiles"
  desc "- `staging_release:true`\n  - Renew the staging release provisioning profiles"
  desc "- `production_debug:true`\n  - Renew the production debug provisioning profiles"
  desc "- `production_release:true`\n  - Renew the production release provisioning profiles"
  desc "- `force:true`\n  - Forces the provisioning profiles to be renewed even if it hasnt expired"
  desc ""
  lane :renew_provisioning_profiles do |options|
    renew = ->(config) {
      get_provisioning_profile(
        app_identifier: config.identifier,
        adhoc: config.is_adhoc,
        development: config.is_development,
        force: options[:force] || false
      )
    }

    if options[:all] || options[:local]
      renew.call(Configurations.local)
    end

    if options[:all] || options[:staging_debug]
      renew.call(Configurations.staging_debug)
    end

    if options[:all] || options[:staging_release]
      renew.call(Configurations.staging_release)
    end

    if options[:all] || options[:production_debug]
      renew.call(Configurations.production_debug)
    end

    if options[:all] || options[:production_release]
      renew.call(Configurations.production_release)
    end
  end

  desc "Renew push notification certificates"
  desc "Options:"
  desc "- `all:true`\n  - Try to renew all push notification certificates"
  desc "- `local:true`\n  - Renew the local push notification certificate"
  desc "- `staging:true`\n  - Renew the staging push notification certificate"
  desc "- `production:true`\n  - Renew the production push notification certificate"
  desc "- `force:true`\n  - Forces the certificate to be renewed even if it doesnt expire in the next 30 days"
  desc ""
  lane :renew_push_certs do |options|
    if options[:all] || options[:local]
      get_push_certificate(
        development: Configurations.local.is_development,
        app_identifier: Configurations.local.identifier,
        force: options[:force] || false,
        output_path: './certificates'
      )
    end

    if options[:all] || options[:staging]
      get_push_certificate(
        development: Configurations.staging_release.is_development,
        app_identifier: Configurations.staging_release.identifier,
        force: options[:force] || false,
        output_path: './certificates'
      )
    end

    if options[:all] || options[:production]
      get_push_certificate(
        development: Configurations.production_release.is_development,
        app_identifier: Configurations.production_release.identifier,
        force: options[:force] || false,
        output_path: './certificates'
      )
    end
  end

  desc "Download the dsyms from iTunes Connect and upload to Sentry"
  desc "Options:"
  desc "- `version`\n  - The version to download the dsyms from. Uses the version from the xcodeproj is not set."
  desc "- `build`\n  - The build to download the dsyms from. If manunlly set, version won't be used."
  lane :dsym do |options|
    version = options[:version] || get_version_number(
      xcodeproj: "Neo.xcodeproj",
      target: "Neo"
    ) unless options[:build]

    build = options[:build] || latest_testflight_build_number(
      version: version
    )

    UI.confirm("Do you want to download the dsyms for #{version}(#{build})?") || next

    download_dsyms(
      version: version,
      build_number: build.to_s
    )

    sentry_upload_dsym
  end
end

`./fastlane/Appfile`
# app_identifier("[[APP_IDENTIFIER]]") # The bundle identifier of your app
# apple_id("[[APPLE_ID]]") # Your Apple email address

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

require './Configurations'

itc_team_id "120120312"
team_id "8AKPS28AYR"

app_identifier Configurations.current.identifier

fastlane gems

Gem
Version
Update-Status

fastlane
2.178.0
🚫 Update available

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-sentry
1.8.1
✅ Up-To-Date

fastlane-plugin-bitrise_automation
0.4.1
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.3.0

executable-hooks
1.6.0

bundler-unload
1.0.2

rubygems-bundler
1.4.5

bundler
2.1.4

rake
13.0.3

CFPropertyList
3.0.3

public_suffix
4.0.6

addressable
2.7.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.1.1

aws-partitions
1.432.0

aws-sigv4
1.2.3

jmespath
1.4.0

aws-sdk-core
3.113.0

aws-sdk-kms
1.43.0

aws-sdk-s3
1.91.0

babosa
1.0.4

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.20

declarative-option
0.1.0

digest-crc
0.6.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.2

excon
0.79.0

faraday-net_http
1.0.1

multipart-post
2.0.0

ruby2_keywords
0.0.4

faraday
1.3.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.3

gh_inspector
1.1.3

jwt
2.2.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.1

signet
0.15.0

googleauth
0.16.0

httpclient
2.8.3

mini_mime
1.0.2

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.38.0

rexml
3.2.4

webrick
1.7.0

google-apis-core
0.3.0

google-apis-iamcredentials_v1
0.2.0

google-apis-storage_v1
0.3.0

google-cloud-env
1.5.0

google-cloud-errors
1.1.0

google-cloud-core
1.6.0

google-cloud-storage
1.31.0

json
2.5.1

mini_magick
4.11.0

naturally
2.2.1

plist
3.6.0

rubyzip
2.3.0

security
0.1.3

simctl
1.6.8

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

fastlane-plugin-bitrise_automation
0.4.1

fastlane-plugin-sentry
1.8.1

generated on: 2021-05-05

[10:29:58]: Take notice that this output may contain sensitive information, or simply information that you don't want to make public.
[10:29:58]: Open https://github.com/fastlane/fastlane/issues/new to submit a new issue ✅
#######################################################################
fastlane 2.182.0 is available.
You should use the latest version.
Please update using bundle update fastlane.
#######################################################################
2.182.0 Improvements

[snapshot] enable greater customization of the iOS status bar in snapshot screenshots (#18560) via Dave Wood
[Fastlane.Swift] Swift's ConfigItem for conflicting values into Ruby's end. (#18544) via Jorge Revuelta
[Fastlane.Swift] sanitize Swift document comments (#18635) via Jorge Revuelta
[Ruby 3.0] wwitch back to the original commander gem and update dependencies (#18599) via Satoshi Namai
[action] ensure backup_xcarchive preserves symbolic links (#18627) via Matej Bukovinski
[action][git_submodule_update] documentation improvements (#18598) via Manish Rathi
[Ruby 3.0] replace slack-notifier gem with internal library (#18537) via Satoshi Namai
[fastlane_core] xcode_at_least method improvements (#18600) via Manish Rathi
[pilot] clean-up - removed empty tester_util file (#18601) via Manish Rathi
[action][upload_symbols_to_crashlytics]  add check for app_id before searching for gsp and api_token (#18607) via Cristian Lupu
[spaceship] add fetch_all_certificates method (#18620) via Damian Rzeszot
[Ruby 3.0] bump rubocop version (#18564) via Satoshi Namai
[action] import_from_git - Add caching support for branch (#18568) via Hiroki Nagasawa

2.181.0 Improvements

[scan] keep initial xcresult (#18555) via Corey Werner
[spaceauth] add --copy_to_clipboard option to spaceauth (#18538) via Roger Oba
[Ruby 3.0] improve specs for Slack action  (#18512) via Satoshi Namai
[spaceship] fix case sensitive email issue for Spaceship::Members.find (#18573) via Max Ott
[supply] upload native symbols for crash symbolication (#18526) via Marcelo Oliveira
[fastlane][lanemanager] fastlane command suggestion improvement when running using bundler (#18515) via Manish Rathi
[gym] fix in the gym/runner. When moving mac 'app' silently fails if file already exist in that location. (#18529) via Krzysztof
[snapshot] added iPhone 12 models to snapshot reports generator (#18535) via Davide
[fastlane_core][pilot][deliver] fix when polling for build processing to poll for X.Y and X.Y.0 (#18547) via Josh Holtz
[action][ensure_env_vars] efficiency improvement (#18522) via Manish Rathi
[fastlane][action] fix git_branch when not in a git repo (#18525) via Josh Holtz

2.180.1 Improvements

[fastlane] fix fastlane_require to work with RubyGems 3.2.0 and up (#18520) via Josh Holtz

To see all new releases, open https://github.com/fastlane/fastlane/releases
Please update using bundle update fastlane
]

Can you confirm that if you use a string and not a file that it's working?

Yeah, a string without a newline works. I ended up fixing it by calling .strip on the file contents. It appears like that's what deliver does by default.
https://github.com/fastlane/fastlane/blob/e874a47c6e2e0e61590a03d3b71e75e5a505d1ce/deliver/lib/deliver/upload_metadata.rb#L144-L146

It'd be nice if this could strip newlines automatically.


Check 'pod.metadata.labels' exists before using it

In my cluster serverless deploy throws a exception when detecting the pods after deployment is finished.
Here is the screenshot.

After some checking I found out there are some pods in my cluster do not have the property 'metadata.labels', so I added some checking before it is being referenced.
I don't have much experience in Javascript, please feel free to tell me if the fix is not appropriate.

thanks for submitting a PR :) I just left a suggestion

@andresmgot Thanks for the review, changed the code according to your suggestion.

LGTM, I am going to merge the PR and bump the version to do a new release. Thank you for the contribution!


Setting isolation level

How to set the transaction isolation level in Serenity? Many thanks in advance.

Ended up creating custom UnitOfWork class:
    public class UnitOfWorkWithIsoLevel : IDisposable, IUnitOfWork
    {
        private IDbConnection _connection;
        private IDbTransaction _transaction;
        private Action _commit;
        private Action _rollback;

        public UnitOfWorkWithIsoLevel(IDbConnection connection, IsolationLevel isolation)
        {
            if (connection == null)
                throw new ArgumentNullException("connection");

            _connection = connection;
            connection.EnsureOpen();
            _transaction = connection.BeginTransaction(isolation);
        }
.....


Unable to parse pypi response

When trying to use from url for pypi nix-template complains about not being able to parse its response.
$ nix-template python -u https://pypi.org/project/pyEDM/
Determining latest release for pyEDM
[2024-06-17T18:40:15Z ERROR nix_template::url] Unable to parse response from pypi.io to json: Error { path: Path { segments: [Map { key: "info" }, Map { key: "author" }] }, original: Error("invalid type: null, expected a string", line: 1, column: 22) }

System info
$ nix-template --version
nix-template 0.4.1

Similar error:
 nix-template python -u https://pypi.org/project/roboticstoolbox-python/ --stdout
Determining latest release for roboticstoolbox-python
[2024-06-23T00:25:12Z ERROR nix_template::url] Unable to parse response from pypi.io to json: Error { path: Path { segments: [Map { key: "info" }, Map { key: "author" }] }, original: Error("invalid type: null, expected a string", line: 1, column: 22) }


Disable everything but the admission system

When we launch the admission system, we don't want to launch the rest of Samfundet4. Therefore we need a way to disable everything but the admission system, and the things it requires. We only want to allow the following:

Admission system pages
Registering and logging in
For authorized users: Admission admin panel

Attempting to do anything else should either redirect or display an error page.

This is solved through #1215, which won't be merged as it's a temporary solution.


Fixes mismatched hashing of ints versus doubles

SameValueComparerCommon::GetHashCode was hashing tagged ints
differently from javascript numbers (doubles).  E.g. 1 would hash
differently from 1.0.  This made Map, Set, WeakMap, and WeakSet lookups
fail when the input key was double and the stored key was int, and vice
versa.
Fixed by hashing integers as doubles so long as those integers fit in a
double.  int64 values that do not fit in a double are hashed as int64
values.
Fixes gh-390

@abchatra @curtisman would either of you mind looking at this please?

After speaking with Curtis offline we agreed that this hash function works fine for our needs.


Light press on touchpad is buggy

When doing a "light" press on a touchpad the mouse press sometimes doesn't register at all which is really annoying.
It would be good to investigate and fix that.

Switching Qt and C++ (for now, will be reevaluated when there are some good Rust bindings for Qt) so closing.


Full orderbook data

Is there a way to get full orderbook data using the websocket or REST api? I only see ways to get the top 25/100 entires on the orderbook.

I managed to get 800 bids and 800 asks, try experimenting with the limits.
https://github.com/dantimofte/bfxtelegram/blob/0b26f072f48bb226b90671ff5287fcaac308625c/bfxtelegram/btfxbot.py#L221-L224


Disable deploy for packaging module

Overview

See: https://jira.bf.local/browse/ECR-XYZ

[ ] The continuous integration build passes

Coverage remained the same at 85.742% when pulling 41dfea2416f042444c311e7b5df69c9a74399ad9 on fix-deploy into 8c4c9f2f651bc05b83f204dc0b31c7e7ffda25c3 on master.

@dip56 reported that fix is working

Good, hopefully https://jira.bf.local/browse/ECR-3039 will make it unneded

Github cannot fix the bug with "Ctrl+Enter" ignoring the chosen merge method for a year :imp: