Problems with dbrestore and single-transaction

@ZuluPro So i have been having issues with dbrestore (sometimes) and looking deeper i may have found the root problem.
Basically if i did python3 manage.py dbrestore -i postgres_backup_v13102016_133318.psql i would run into some errors and my database would not restore.
The error was ERROR:  current transaction is aborted, commands ignored until end of transaction block and invalid command \N
Looking deeper i found that this error is being caused by the flag --single-transaction .
To replicate, i took the psql dump (generated by dbbackup) and tried to restore it manually and got the same errors as the db restore command:
psql --host=smal_postgis --user=postgres --single-transaction postgres < /code/backups/postgres_backup_v13102016_135112.psql
I then noticed that the single-transaction variable was being set to True here https://github.com/django-dbbackup/django-dbbackup/blob/3.0.2/dbbackup/db/postgresql.py#L12
To prove my theory, i ran and it restored fine:
psql --host=smal_postgis --user=postgres postgres < /code/backups/postgres_backup_v13102016_135112.psql
Hope this helps fixing the issue or is there a way for me to set single_transaction to False with the dbrestore command?

Oh i tried with django-dbbackup==3.0.2 and django-dbbackup==3.0.3 and Django==1.10 and Postgres==9.5

Hello @psychok7,
Effectively there's a way to unset single-transaction:
See http://django-dbbackup.readthedocs.io/en/latest/databases.html#postgresql
I put single transaction by default to avoid inconsistent restore, but maybe it will change.
Otherwise, I'm writing a connector using pg_restore and binary backups.
One thing remains, do you know the exact cause of this error ?

@ZuluPro the only errors i see are in the beggining of the restore when the database is empty regarding indexes, relations or sequences like for example ERROR:  relation "public.users_userprofile" does not exist.  After the initial errors because it does not exist yet everything runs fine. I don't think there are any errors when there is a database in place.
Maybe make the opposite behavior for single-transaction and by default being False??

@psychok7
In fact, I think about change it to False but the single transaction behavior is useful for data consistency.

@ZuluPro i did i quick test and my theory is right.
so basically the problem is with the does not exist error when you have no database or no table with that name to drop before starting the restore. for some reason single-transaction is not playing right with the drop table.
do you think there might be a way for single-transaction to ignore the drop error in the beggining of the .psql ?? or if in fact there is an error to automatically switch to false??

@ZuluPro by the way with DBBACKUP_SINGLE_TRANSACTION = False or SINGLE_TRANSACTION = False i get the same problem and my database does not restore

@psychok7
It is a connector settings, in DBBACKUP_CONNECTORS = {}

oh ok

@ZuluPro so adding the setting 'SINGLE_TRANSACTION': False allows me to restore the db with dbrestore, although i still see the drop errors in the postgres logs like for example:
smal_postgis_1       | ERROR:  extension "postgis_topology" does not exist
smal_postgis_1       | STATEMENT:  DROP EXTENSION postgis_topology;
smal_postgis_1       | ERROR:  extension "postgis" does not exist
smal_postgis_1       | STATEMENT:  DROP EXTENSION postgis;
smal_postgis_1       | ERROR:  schema "tiger" does not exist
smal_postgis_1       | STATEMENT:  DROP SCHEMA tiger;
smal_postgis_1       | ERROR:  schema "public" does not exist
smal_postgis_1       | STATEMENT:  DROP SCHEMA public;

Are the dumps being made in a different way then in version below 3.x?

@psychok7
The drop statements are created by 'DROP': True (default value) of  DBBACKUP_CONNECTORS, --clean of pg_dump.
I think you can avoid this behavior with by set 'DROP': False, but I'll work to simplify that and make documentation more explicit.

@ZuluPro honestly i prefer having 'DROP': True as default because i definetly want to delete my old data when i restore my db (and i assume everyone else). I understand the importance of single-transaction but if there is no way of making it play nice with the drop command then i prefer not having it.

@ZuluPro hi there, did you address anything related to this on newer releases? I am using  django-dbbackup==3.0.2 and i just realized DROP is not working for me.
Currently in order to restore as a workaround i have to go into postgres and delete everything first.
my settings are like:
DBBACKUP_CONNECTORS = {
    'default': {
        'USER': 'xx',
        'PASSWORD': 'xxx',
        'HOST': 'xx',
        'DROP': True,
        'SINGLE_TRANSACTION': False
    }
}

Then i get errors like:
smal_postgis_1       | STATEMENT:  CREATE SCHEMA public;
smal_postgis_1       | ERROR:  relation "auth_group" already exists
smal_postgis_1       | STATEMENT:  CREATE TABLE auth_group (
smal_postgis_1       | 	    id integer NOT NULL,
smal_postgis_1       | 	    name character varying(80) NOT NULL
smal_postgis_1       | 	);

Any ideas why this is happening??

@psychok7 DROPoption in PostgreSQL adds DROP statements inside the dump file.
If you didn't create the dump with this option, it won't work...

@ZuluPro i am creating with the option and i do have DROP statements in the dump.
Fiddling a bit more, i found that the DROP issue might not be because of dbbackup, i manually did a pg_dump --clean and the created structure was similar do dbbackup.
When googling i found some of the errors i am having, for example here . The thing is the solution seems to be manual and i could not rely on pg_dump --clean anymore. (i am not even sure why i have this dependencies issues in the first place)

@ZuluPro to add to the previous comment, the solution that works for me currently is to first drop my database schemas and tables with drop schema public cascade; after that i don't run into any errors when restoring (with psql or with dbbackup).
I don't know if this is a common issue or not, or if there is even a better solution but maybe have a setting in dbbackup that would first drop schema public cascade; before doing its normal behavior?

@ZuluPro hi, i am testing a new project with Django 1.11 and this problem still happens.
Luckily my workaround still works with django-dbbackup==3.0.2 by setting 'DROP': True and 'SINGLE_TRANSACTION': False and deleting manually everything in the database with drop schema public cascade; before doing a dbrestore.
But with the latest version django-dbbackup==3.1.3 it does not work. i run into "new" problems (tried both with data in my db, and with a clear db and the restore does not work in any case):

root@644a3e82f4f5:/code# python3 manage.py dbrestore --settings=proj.settings.local
Finding latest backup
Restoring backup for database 'default' and server 'None'
Restoring: default-ed296d619dd6-2017-05-02-220642.psql
Restore tempfile created: 1018.5 KiB
Are you sure you want to continue? [Y/n] y
Traceback (most recent call last):
  File "manage.py", line 22, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/__init__.py", line 363, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/__init__.py", line 355, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/management/commands/dbrestore.py", line 54, in handle
    self._restore_backup()
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/management/commands/dbrestore.py", line 94, in _restore_backup
    self.connector.restore_dump(input_file)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/base.py", line 96, in restore_dump
    result = self._restore_dump(dump)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/postgresql.py", line 78, in _restore_dump
    return super(PgDumpGisConnector, self)._restore_dump(dump)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/postgresql.py", line 53, in _restore_dump
    stdout, stderr = self.run_command(cmd, stdin=dump, env=self.restore_env)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/postgresql.py", line 20, in run_command
    return super(PgDumpConnector, self).run_command(*args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/base.py", line 150, in run_command
    "Error running: {}\n{}".format(command, stderr.read()))
dbbackup.db.exceptions.CommandConnectorError: Error running:  psql postgres --host=proj_postgis --port=5432 --username=postgres --no-password --set ON_ERROR_STOP=on
b'ERROR:  schema "public" does not exist\n'

root@644a3e82f4f5:/code# python3 manage.py dbshell --settings=proj.settings.local
psql (9.5.6, server 9.5.5)
Type "help" for help.

postgres=# create schema public;
CREATE SCHEMA
postgres=# \q
root@644a3e82f4f5:/code# python3 manage.py dbrestore --settings=proj.settings.local
Finding latest backup
Restoring backup for database 'default' and server 'None'
Restoring: default-ed296d619dd6-2017-05-02-220642.psql
Restore tempfile created: 1018.6 KiB
Are you sure you want to continue? [Y/n] y
Traceback (most recent call last):
  File "manage.py", line 22, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/__init__.py", line 363, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/__init__.py", line 355, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.5/dist-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/management/commands/dbrestore.py", line 54, in handle
    self._restore_backup()
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/management/commands/dbrestore.py", line 94, in _restore_backup
    self.connector.restore_dump(input_file)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/base.py", line 96, in restore_dump
    result = self._restore_dump(dump)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/postgresql.py", line 78, in _restore_dump
    return super(PgDumpGisConnector, self)._restore_dump(dump)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/postgresql.py", line 53, in _restore_dump
    stdout, stderr = self.run_command(cmd, stdin=dump, env=self.restore_env)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/postgresql.py", line 20, in run_command
    return super(PgDumpConnector, self).run_command(*args, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/dbbackup/db/base.py", line 150, in run_command
    "Error running: {}\n{}".format(command, stderr.read()))
dbbackup.db.exceptions.CommandConnectorError: Error running:  psql postgres --host=proj_postgis --port=5432 --username=postgres --no-password --set ON_ERROR_STOP=on
b'ERROR:  relation "public.users_userprofile" does not exist\n'

Hope that helps for a bugfix.

This new issue that i am having might also be related to https://github.com/django-dbbackup/django-dbbackup/issues/230

@psychok7 : Really sorry to read that,
Let me some time, I already began Postgres Binary Connector.
I'll add it and check Django 1.11.

@ZuluPro that is really good news. let me know if you need help testing it when your done.
Thanks

@psychok7 See PR #241

This PR fixes these problems.


refactor(send): promisify send

Clean up / respond to the two (!(!!err)) comments above, but other than that looks good. Really like the promisified syntax so much better that cb-soup.


Include response output: spo homesite until spo navigation commands

Add the response output for a few of the commands under the service:

spo documentation location

This in place for the following command groups:

spo homesite
spo hubsite
spo knowledgehub
spo list
spo listitem
spo mail
spo navigation

You can reference the commands planner plan and planner bucket. They are already contain the Response heading in their documentation.
For more information what guidelines to follow, be sure to check out the epic issue #3754

I could work on this one 😄

I could work on this 😄

All yours!


Deploy Via GitHub URL

We should be able to execute ie based on GitHub urls instead of the user needing to have the file stored locally.
To accomplish this feature, no need to have a scalable solution. We can have a manually maintained whitelist for what is allowed to be executed.
For example:
ie execute http://github.com/mysuperprojcet/docs/helloworld.md

If there are dependent files, then we'd need a path to the working directory.


chore: update wasmcloud-component-adapters

Feature or Problem
This bumps the version of wasmcloud-component-adapters, so when we next release wash-lib/wash, the docs should build 🤞, as this dependency no longer requires an internet connection to build in docs.rs
Related Issues
Resolves https://github.com/wasmCloud/wash/issues/831

Gotta figure out dat nix though


el7 is hardcoded for versions/tars

in https://github.com/redhat-cop/automate-tower-ha-dr/blob/master/tower-vars-base.yml#L20 el7 is hardcoded. This causes issues for el8.

Closing based on functionality added in https://github.com/redhat-cop/automate-tower-ha-dr/pull/17


JSON Parsing Error on Remote Workspace Creation

Describe the bug
When attempting to create a workspace using a remote profile on an Azure ARM machine running Daytona v0.3.1 from a local machine, the process fails with the error "FATA[0009] unexpected end of JSON input". However, creating the workspace directly on the remote machine with the same Daytona command and repository succeeds.
To Reproduce
Steps to reproduce the behavior:

Set up a remote profile targeting an Azure ARM machine running Daytona v0.3.1.
From the local machine, attempt to create a workspace with the command daytona create using repo https://github.com/metcalfc/simple-flask.
Observe the error "FATA[0009] unexpected end of JSON input".
SSH into the remote machine.
Run the same daytona create command with the same repository.
Notice that the workspace is successfully created.

Expected behavior
The daytona create command should work identically and successfully create a workspace when run from a local machine using a remote profile or directly on the remote machine.
Screenshots

@nkkko does daytona server logs -f work in this setup?
Just wondering because this might be a websocket issue with your remote machine.


Cannot Open Page error

Hi,
If a user doesn't have the what's app installed, and clicked on the button they see the "Cannot Open Page" pop-up on iOS, and on Android the link is broken.
Would there be a way to let users know that they have to install What's App for sharing instead of these pop-ups or broken links?
Please refer to the attached image:

This isn't possible at all.


update license to rtw

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

we don't plan on releasing any additional 3.x products


Support Flatpak/Appimage

Hi
I like the app. But, the thing is to ensure the app can reach many distribution. universal packaging such as flatpak or Appimage is important. Is it possible to support those?

@dtantono Hello. at the moment I release binary output since 1.0.7 so you can use it in across different distros
After some stablization of the app I will consider a better packaging approach

Hi, I was looking a Flatpak release too, I hope to see it soon, I am excited to try AB Download Manager


Adding codecov integration

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@26caa74). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master      #8   +/-   ##
========================================
  Coverage          ?   0.00%
========================================
  Files             ?      15
  Lines             ?     505
  Branches          ?      63
========================================
  Hits              ?       0
  Misses            ?     505
  Partials          ?       0

Continue to review full report at Codecov.

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


Restructure RateConstant class for optimization

Restructure RateConstant class to optimize the performance for UpdateState() that has to look up a V-table for each rate constant for its operation.

Since UpdateState is called only once in the Solve routine, the performance hit won't noticeably affect the solving time and it's not worth our time to do this ticket


Resolves #23 Update authentication TCK to use latest WildFly and the EE feature pack.

Closing at this is linked to the wrong issue.


⚠ File access has degraded performance

In 71d8abb, File access (https://fyle.uk/file/fish) experienced degraded performance:

HTTP code: 200
Response time: 3630 ms

Resolved: File access performance has improved in accad89 after 10 minutes.


Check docs in on PR

I think the recent CI changes lead to a situation where the docs aren't built per PR anymore, but only once its merged. That could lead to failures on master that we can't detect before merging.
Docs should be built the same way per PR and on merge to master (in which case they'll be published to https://docs.fedimint.org):
https://github.com/fedimint/fedimint/blob/529c6d5c4401d231c44748fb243dfe0da8d96971/.github/workflows/docs.yml#L26-L30

Will do. Build on all branches, publish on pushes to master.

It seems like we are relying on nightly flags to create index.html, so I think for now I'll leave the non-nix workflow to build and upload it when landed in master.


Drop down lists don't show if more than 7

If there are more than 7 elements in the datalist (for tags), the list won't show when the drop down arrow is clicked

No longer an issue


nixos/mautrix-whatsapp: automatic appservice registration option, pull login_shared_secret_map setting from env file

Description of changes
Automatically add the generated appservice registration file to synapses settings when the corresponding option is set. Also pull the login_shared_secret_map from the environment file if it exists.
These changes are analogous to the implementation in the newer mautrix-signal module.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4397

This breaks existing configurations


uv build, hatchling and ignore-vcs

Thanks for the awesome tools.  I've been swapping our projects over to uv as time permits and it's really simplified our entire build and release process.
I have noticed one inconsistency though.  In one of our projects, I need to bundle static assets that are generated and stored in folder that is in the .gitignore file.
With other build tools, I've been able to explicitly add the assets to the to the artifacts setting and they will be included in the final generated whl file.
However, with uv, I've had to set the ignore-vcs variable to make these assets be included in the final build.
I'm on the v0.4.30, but I've seen this behavior in the last few releases as well.  Is this expected?
The repository that I see this behavior in is not public, but if it would help, I can get an MVCE repo created.
Thanks

I'm not 100% sure.  That's basically the reference implementation for the spec.

I'm not 100% sure.  That's basically the reference implementation for the spec.

I'll double check and get back to you.

Interesting!
It looks like python -m build produces the same behavior as uv build.  I can only get the file included when the ignore-vcs setting is present.  However, the same projects did include them with with PDM and hatch.
The current change of ignore-vcs is totally fine for me, so I think we can close this.  However, it's probably good to add share this anecdote I noticed when running these tests:  artifacts can be totally omitted from my build configuration when I enable the ignore-vcs setting.  The path I'm adding happens to be within the module.
I'll try to get some clarifications from the hatchling author as well.  The documentation is worded as if it is specifically for assets that have been ignored by VCS.
Thanks for the really quick response!

I wanted to close the loop on this.  I had a chance to chat with ofek and I figured out the difference here.
I was using the top level configuration for hatch like so:
[tool.hatch.build]
dev-mode-dirs = ["."]
sources = ["."]

This type of declaration has been removed from the hatchling documentation.   The recommendation is to merge the settings needed into each build target instead.
Hopefully this will help others if this is encountered.

Thanks for following up @cofin, appreciate it!


Genevieve Genome Report not visible

General Checkups

[x] Have you checked that there isn't already an existing issue that describes what you report below?
[x] Have you checked that there isn't already an open pull requests for this issue/update/change?

Description
When I'm not logged in and load the explore/share page, I don't see Genevieve listed: https://www.openhumans.org/explore-share/
It seems it should be listed here -- users share data with it, and it currently has "approved" status.

This missing things is weird, but we've known this page has issues. Thinking about it, I think the explore-share page should have the following logic:
Any approved and active project that is either...

(a) requesting access to username or data sources
(b) NOT listed in the add-data list

This would capture a lot of what we're currently unhappy about (regarding projects not showing up). I think there's still some cases where I'm not excited by how things sort out. e.g. a survey-based research study that deposits survey data ... would only show up as "add-data".
(That said, this would hopefully be a clear improvement over the current listings.)
@gedankenstuecke what do you think?

Right, the surveys are one thing, the Twitter archive would still be only 'add data', despite being designed to largely explore data. How about we give project leads a choice to choose where they'd like to be listed?

I like that idea! Explore/share is something we can't automatically determine.
Proposed behavior, what do you think?

In response to "Where should your project be listed?" a project can select "Add data" and "Explore & Share", and at least one of these must be true. (Although maybe the backend should have two different fields here.)
If "Add data" is set to "true" there must also be a "returned data description" (otherwise the form is considered invalid)
But it is allowed to have a "returned data description" without being listed as "Add data"

And for existing projects, the new fields can default according to the logic I described above.

Yep, that sounds good to me! 👍

Just noticed: The Juno Exploratory doesn't show up on either page as well.


Show an option to connect on site that supports Lightning login

Hi,
When I enter on staker.news site I need to do three steps to login using lightning. I think when the user enter on Stacker news site, Alby should detect that the site support lightning login and automatically popup a window like:
We detected that Stacker News support lightning login. Do you want to login with Alby? Yes or NO and do not show this popup again.

Related to: https://github.com/getAlby/lightning-browser-extension/issues/833

This would need to be a call from stacker.news side, am I right? @escapedcat

We don't know beforehand if a website supports lnurl-auth logins, there is currently also no effort to implement a spec for websites to signal that to extensions.
Closing this issue as there is nothing we could add on our end to support that currently. Users will be prompted as they click the "sign in with lightning" button on different websites.


fix: make distrobox automatically disable, fix versioning

This PR makes the distrobox module disabled when the bin path isn't executable. I didn't make the changes to the other drivers because that would kinda be like "silently failing." If flatpak or bootc fail to update the user should probably know and the program should send an error.
This also makes it so there's proper versioning within the SPEC so it doesn't get built as "version 1.0" constantly

Whenever you feel this PR is done, please ping me! I'd like to test out those changes

Check out the patch I sent you on discord, that should be the literal last thing to get this done.


errata

there must add the C:\Windows\Microsoft.NET\Framework\v4.0.30319\SQL\en\SQL to the path
cheers!

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

ID: 2df8da82-d4dc-9d98-dad2-aa44be3ca125
Version Independent ID: 4e42da0c-d227-3e41-ad5e-e771c744e2c5
Content: How to: Create and Run a Long Running Workflow
Content Source: docs/framework/windows-workflow-foundation/how-to-create-and-run-a-long-running-workflow.md
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Closing as this does not appear reproducible. Our path is at "C:\Windows\Microsoft.NET\Framework\v4.0.30319\SQL\en"  . If this is not the case, then please reopen. Thanks!


Unable to deploy successfully

Describe the bug
I'm currently trying to deploy this. My first problem was that I already have reached the limit os service plans in my subscription.
So I changed the template to reference an existing service plan.
While this worked I now got the error:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"message":"AppSetting with name 'Acmebot:SubscriptionId' is not allowed."}]}
I then changed all "Acmebot:" to "Acmebot__" and it successfully deployed. I've set up authentication but now I'm stuck with  "The service is unavailable." and the portal says "Azure Functions runtime is unreachable"
To Reproduce
Steps to reproduce the behavior:

Try deploy with "Deploy to azure" button.

If you are using a customized ARM Template, I cannot support it. Deployment is supported only on Windows Consumption or App Service Plan.

@shibayan Thanks. The hint with windows helped me.


Quadkey support

Tile matrix sets have the notion of X/Y/Z coordinates so technically we can generate a quadkey.  However not all tile matrix sets have 4 children per parent which breaks the parent/child hierarchy.  A good example of this is Canadian NAD83 LCC.
This all being said, I do think there are many benefits to supporting quadkeys:

serialization/deserialization of tiles
server side caching (generating unique per-tile cache keys)
fast parent/child lookups

I think this comes down to whether or not morecantile will support tile matrices which don't decimate by a factor of 4 (width or height is 2**zoom).  From the README, docstrings, and general usage my thought is that it shouldn't, but that isn't entirely clear.

I'm not sure to understand what you are proposing @geospatial-jeff
I didn't add a quadkey method because you can use the one from mercantile directly.
If I remember morecantile.quadkey was present in the previous version but I removed it because I didn't like the magic of having from mercantile import quadkey in morecantile.__init__

@geospatial-jeff  (Not sure if this is the best place to post this)
This is something I'm quite interested in, we have been looking at how to make QuadKeys from the NZTM tiling scheme.
there are a few issues with NZTM when it comes to quadkeys,

zoom 0 is a 2x4 grid
zoom 8 to  zoom 9 and zoom 13 to zoom 14 use a 2.5x increase rather than a 2x increase.

To work around these two issues we have had two thoughts
Create a new TileMatrixSet
since the bounding box and origin are know we could create another tile matrix set that starts with a 1x1 tile at the original z0 resolution and then increase, using a 2x factor for all zoom levels. This would make a nice quadkey for all zoom levels we would need, but then tiles will never really "align" to the original. We thought this would be just creating another TileMatrixSet and didnt want to have two NZTM TileMatrixSets
Create a offset based QuadKey mapping for NZTM,
Most of NZTM increases by 2x and is almost square, we can take z0 which is 2x4 and make it a virtual 4x4 grid, then we can zoom out and create a virtual z-1 (2x2) and z-2 (1x1) which would then perfectly map to quadkeys,

QK '' =>  z:-2, x:0, y:0 (not a real tile)
QK '0' => z-1, x:0, y:0 (not a real tile)
QK '21'  => z:0, x:1, y:2 (real tile!)

Then we have QuadKeys that could be "valid" or "invalid", the TileMatrixSet knows if they are valid or not,
This still leaves the problem of z8-z9 transition, the z8 -> z9 transition means that a z9 tile may have 4 z8 tiles as it's parent so any math that creates a covering of a tile >= z9 may need up to 4 parent tiles.
what this means in practice is we can use QuadKeys to easily reference anything between z0 and z8, then possibly have to use 4 quad keys for anything in >= z9.
We have currently gone with the second option (example source: https://github.com/linz/basemaps/blob/master/packages/geo/src/tms.quad.key.ts)
But we are open to better solutions!

@blacha as you mention the 2.5x zoom fundamentally breaks the math behind quadtrees so I think the approach you have come up with is as good as you can get.  Creating an offset quadkey is a clever way of handling the differing matrix dimensions.

I think we don't have to decide yet if we always want to support quadkeys. We could just implement a function that checks if a custom Tile Matrix Set supports quadkeys. If not we just raise an NoQuadkeySupport error. I would implement this function and then just copy over the two functions quadkey and quadkey_to_tile from mercantile and add them to the TileMatrixSet  class. Is it ok if I create a PR for this?

Just to follow up on this, we ended up deciding that it was worth the effort to replace the old tile matrix set with one that is quad key compatible, the 2.5x scale jumps also caused issues with things like COG creation with GDAL (this is now fixed)
So now we have:

NZTM2000 Deprecated
NZTM2000Quad

closed by #56


fix english grammar

wondering what does 'the' mean in French XD

Hello how are you man ?
Thanks I really appreciate your contribution.


Convert the source code to TypeScript

The first step is to rename all of the files to .ts and use ts-node or one of the new alternatives like https://github.com/esbuild-kit/tsx to run the code. Then get Jest working.
We'll probably have to disable a bunch of ESLint rules temporarily while we work on adding type annotations.

This can wait until after 1.0. I need to create a new milestone for 1.0.

No need for a TypeScript runtime. We can compile the code and run it with Node.

The server part is done now. Just need to do the typescript-generator.


exp socket hang up

All of my builds fail with CircleCI at
[exp]  ERROR  watch /home/ubuntu/citest2/node_modules/react-native-maps/lib/android/build/tmp/expandedArchives/classes.jar_rvtuwwbhztnbbkxi8oruhd9v/android/support/v4/hardware/fingerprint ENOSPC

I'm guessing because of the watch command? Here is the full log.
if [ "$CI_PULL_REQUEST" != "" ]; then yarn appr; fi
yarn appr v0.27.5
$ appr
[appr] Logging into Expo...
There is a new version of exp available (44.0.0).
You are currently using exp 36.0.0
Run `npm install -g exp` to get the latest version

Success.
[appr] Logged into Expo.
[appr] Preparing project for publish...
[appr] Publishing project into Expo.
There is a new version of exp available (44.0.0).
You are currently using exp 36.0.0
Run `npm install -g exp` to get the latest version
[exp] Making sure project is set up correctly...
-[exp] Warning: Not using the Expo fork of react-native. See https://docs.getexponent.com/.

-[exp] Warning: 'react' peer depencency missing. Run `npm ls` in /home/ubuntu/citest2 to see full warning.
[exp]
[exp] If there is an issue running your project, please run `npm install` in /home/ubuntu/citest2 and restart.

[exp] Your project looks good!
[exp] Unable to find an existing exp instance for this directory, starting a new one...
[exp] Warning: Not using the Expo fork of react-native. See https://docs.getexponent.com/.
[exp] Warning: 'react' peer depencency missing. Run `npm ls` in /home/ubuntu/citest2 to see full warning.
[exp]
[exp] If there is an issue running your project, please run `npm install` in /home/ubuntu/citest2 and restart.
[exp] Starting React Native packager...
[exp] Scanning 826 folders for symlinks in /home/ubuntu/citest2/node_modules (9ms)
[exp]
[exp] Running packager on port 19001
[exp]
[exp]
[exp]
[exp] Looking for JS files in
[exp]    /home/ubuntu/citest2
[exp]
[exp]
[exp]
[exp]
[exp] React packager ready.
[exp]
[exp]
[exp]
[exp] Publishing...
[exp]  ERROR  watch /home/ubuntu/citest2/node_modules/react-native-maps/lib/android/build/tmp/expandedArchives/classes.jar_rvtuwwbhztnbbkxi8oruhd9v/android/support/v4/hardware/fingerprint ENOSPC
[exp]
[exp] {"code":"ENOSPC","errno":"ENOSPC","syscall":"watch /home/ubuntu/citest2/node_modules/react-native-maps/lib/android/build/tmp/expandedArchives/classes.jar_rvtuwwbhztnbbkxi8oruhd9v/android/support/v4/hardware/fingerprint","filename":"/home/ubuntu/citest2/node_modules/react-native-maps/lib/android/build/tmp/expandedArchives/classes.jar_rvtuwwbhztnbbkxi8oruhd9v/android/support/v4/hardware/fingerprint"}
[exp] Error: watch /home/ubuntu/citest2/node_modules/react-native-maps/lib/android/build/tmp/expandedArchives/classes.jar_rvtuwwbhztnbbkxi8oruhd9v/android/support/v4/hardware/fingerprint ENOSPC
[exp]     at exports._errnoException (util.js:1022:11)
[exp]     at FSWatcher.start (fs.js:1429:19)
[exp]     at Object.fs.watch (fs.js:1456:11)
[exp]     at NodeWatcher.watchdir (/home/ubuntu/citest2/node_modules/jest-haste-map/node_modules/sane/src/node_watcher.js:150:20)
[exp]     at Walker.<anonymous> (/home/ubuntu/citest2/node_modules/jest-haste-map/node_modules/sane/src/node_watcher.js:374:12)
[exp]     at emitTwo (events.js:106:13)
[exp]     at Walker.emit (events.js:191:7)
[exp]     at /home/ubuntu/citest2/node_modules/walker/lib/walker.js:69:16
[exp]     at go$readdir$cb (/home/ubuntu/citest2/node_modules/graceful-fs/graceful-fs.js:149:14)
[exp]     at FSReqWrap.oncomplete (fs.js:123:15)
[exp]
[exp] socket hang up
Error: socket hang up
    at createHangUpError (_http_client.js:254:15)
    at Socket.socketOnEnd (_http_client.js:346:23)
    at emitNone (events.js:91:20)
    at Socket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
/home/ubuntu/citest2/node_modules/appr/index.js:22
      throw new Error('Failed to publish package to Expo');
      ^

Error: Failed to publish package to Expo
    at publishError (/home/ubuntu/citest2/node_modules/appr/index.js:22:13)
    at ChildProcess.child.on.code (/home/ubuntu/citest2/node_modules/appr/scripts/spawn.js:16:5)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
error Command failed with exit code 1.

if [ "$CI_PULL_REQUEST" != "" ]; then yarn appr; fi returned exit code 1

Action failed: if [ "$CI_PULL_REQUEST" != "" ]; then yarn appr; fi

I was able to bypass this issue by adding nonPersistant to the app.json
{
  "expo": {
    "sdkVersion": "20.0.0",
    "packagerOpts": {
      "nonPersistent": "--nonPersistent"
    }
  }
}

Thank you so much for sharing.

Should this be included in the project readme for setup? I can confirm that on a new CRNA project, setup fails without this option in app.json (with Travis CI atleast).


Consider renaming this proejct to autoware-carla-cosimulation

Just my one cent.
It helps visitors to understand the purpose of the repository and distinguish it from other bridge code and subprojects.

Close since it's not in the roadmap


PolyDraw stream addition to allow setting an additional variable to color polygon

Allow for assigning each Polygon an additional variable to color by.
For instance allow use the example gallery/demos/bokeh/box_draw_roi_editor.ipynb
and have each ROI have it's own line_color at the very least.

@ayoungs Finally working on this, what I've done initially is allow specifying style_cycles on the PolyDraw stream. For example here we define a cycle for the fill_color:
poly = hv.Polygons([[(2, 2), (5, 8), (8, 2)]])

poly_stream = streams.PolyDraw(source=poly, drag=True, show_vertices=True,
                               style_cycles={'fill_color': ['red', 'green', 'blue']})

poly

which will be applied whenever we draw a new polygon. Is this sufficient for your purposes or do you need something more complex?


fix option for -macs_file in model file

-macs_file does not currently work because we can currently only run SimPrily with the -random_discovery option. Therefore, the issue https://github.com/agladstein/SimPrily/issues/27 should be completed first for -macs_file to work.
This is because -macs_file reads from a static file with the output of a simulation (e.g. tests/test_data/sites.txt). The model file, and macs_args must have the same sample sizes as static file.
If the model file has the same sample sizes as the static file, but the option -random_discovery is used, macs_args will have different sample sizes - and there will be an error.
One workaround is to not use read from the model file at all when using -macs_file.
The first line of the static file is the command used to run simulation. This line could be used to create macs_args.

difficulty - medium


Vim complained with"E716: Key not present in Dictionary" error msg when open a po file

environment

vim: VIM - Vi IMproved 8.0 Included patches: 1-134
vim-airline: e83ed24
OS: Debian 8.6 jessie
Have you reproduced with a minimal vimrc: Yes.
What is your airline configuration: The po extension is enabled (as by default).
if you are using terminal:
terminal: GNOME Terminal 3.14.1
$TERM variable: screen-256color-bce (inside a GNU screen) or xterm (bare terminal).
color configuration (:set t_Co?): 256
if you are using Neovim: No.
does it happen in Vim:

actual behavior
When the po extension is enabled (by default it does), vim would prompt an error message like:
Messages maintainer: Bram Moolenaar<EMAIL_ADDRESS>"po/zh_CN.po" 14482L, 410914C
Error detected while processing function <SNR>64_on_exit:
line    6:
E716: Key not present in Dictionary: /path/to/po/zh_CN.po
Press ENTER or type command to continue

when it open a po file.  And the error message automatically disappeared after a few seconds.  I have to run :messages to retrieve the error message.
When the po extension is disabled (e.g. let g:airline#extensions#po#enabled=0), the error message would not appear any more.
expected behavior
I'm not sure but

if this error should not appeared: it's a bug and should be fixed in the future.
if this is expected as a side effect introduced by the async feature of the po extension: I think it's better to figure out a way to hide the error message ;-)

Tried to reproduce the bug on my Macbook.  Same vim version and same vim-airline version.  OS: macOS Serria 10.12.2.  Vim is the Homebrew's pre-built version.  The po extension is explicitly enabled.  Result: No error message.  No  "xxxx translated messages." in status bar.  The po extension seem not working.  I tried a built-from-src brew vim and got the same result.

how to reproduce?

@chrisbra Here's how I reproduce the error:

Setup a fresh new OS environment.  I use vagrant + virtualbox.  Something like $ vagrant up debian/jessie64 or $ vagrant up ubuntu/trusty64.  I tried both and reproduced error on each of them.

Inside the vm, run # apt-get install -y build-essential libncurses5-dev (for building vim from src) and # apt-get install -y gettext ( for the msgfmt cmd).

Get vim v8.0.134 src from https://github.com/vim/vim/archive/v8.0.0134.tar.gz .  Extract it to somewhere, for example /tmp/vim-8.0.0134.  Inside it, run # ./configure --prefix=/usr/local --with-features=huge && make && make install.  Now vim8.0 binary should be installed in /usr/local/bin/vim.

Set a minimal vimrc in the home dir, make sure it contain set laststatus=2 to make sure vim-airline would be presented.  Create the .vim dir under the home dir, get vim-airline pkg from HEAD of the official github repo https://github.com/vim-airline/vim-airline , and copy all its contents into ~/.vim.

Now open a po file.  For example, I use this: https://github.com/git/git/blob/master/po/bg.po .  curl it to somewhere and open it by /usr/local/bin/vim /path/to/bg.po.  Now the E716 error should appear (and disappear soon).  Use :messages to check the error message.

Tried to reproduce the bug on my Macbook. Same vim version and same vim-airline version. OS: macOS Serria 10.12.2. Vim is the Homebrew's pre-built version. The po extension is explicitly enabled. Result: No error message. No "xxxx translated messages." in status bar. The po extension seem not working. I tried a built-from-src brew vim and got the same result.

Err, this is because the lacking of the msgfmt utility in my macOS.  Sorry :-o

I actually only see this, with invalid po files. However I think I have fixed it now.

I think I know how to reproduce. I'll explain my setup so you can try it out. Have NERDTree open on startup, creating another window. I used this autocmd:
autocmd VimEnter * if argc() == 1 && isdirectory(argv()[0]) && !exists("s:std_in") | exe 'NERDTree' argv()[0] | wincmd p | ene | endif

Add this config for vim-airline:
let g:airline_exclude_filetypes = ['nerdtree']

So two windows start up but one is excluded and thus does not have the context set - i.e. s:contexts in autoload/airline.vim`. But only during startup. Thoughts on how to fix this?

don't see this. BTW: this issue is about po files, don't know how nerdtree comes into play here.

@chrisbra just thought that it may have been related but nvm I guess

As I said, I cannot reproduce. Please post exact steps with your minimal vimrc. And also show the error message.

@oldsharp  Hi, I found the same issue. And I found it should be some bug with the taglist plugin. The issue disappear after I disable the taglist plugin.

for po files? What exactly is the error message?


GPII-2615: Improve "schema link" support.

See GPII-2615 for details.

@amb26, at least on my machine I can reproduce the error catching failure by running npm test.  The failing test file runs just fine individually, that command is:
node tests/js/server/parser-update-failure-tests.js

The npm test command also uses instrumented code to prepare code coverage reports. I just confirmed I see the same error running node tests/all-tests.js without using Istanbul.

Hi - this failure is caused by a conflicting definition within gpii-express' test libraries at https://github.com/GPII/gpii-express/blob/master/tests/js/lib/globalFailureHandler.js - as it seems, this component constructs and makes a global instance unconditionally as soon as the gpii-express test library is included. The problem is then that your definition on line 74 of parser-update-failure-tests.js
                   event:    "{globalErrorHandler}.events.onError",

binds onto this global object and awaits its firing rather than the one on line 53. So the error is not that your global error handler is not firing in preference to the fatal error handler, but that you are waiting for the firing of the wrong event. This could have been verified with a logging statement at line 53.
You have a few possibilities -
i) rewrite your gpii-json-schema test so that it uses the definition from gpii-express which looks like was intended to be used as a shared utility
ii) write a more specific selector at line 74 {gpii.tests.schema.globalErrorHandler}.events.onError which ensures to match your own handler rather than gpii-express'
iii) rewrite the utility in gpii-express so that it does not load unconditionally but only on receipt of a directive like gpii.test.express.loadGlobalErrorHandler();
iv) others

Thanks very much for figuring that out.  Although option 2 seems the laziest and easiest, options 1 and 3 combined smell better.  For my sins I will search my collected works and confirm whether there are other clones lurking around waiting to hit the same problem and update those as well.

@amb26, this pull now uses the updated global failure handler from gpii-express.  I'd like to merge the related express pull first so I can use a released version in this pull.

Thanks.  I cut the 1.0.3 release and updated the forward-facing version in master.


Dashboard link on Pages documentation

Example URL(s)
https://developers.cloudflare.com/pages/
Actual Behavior
the "Your Cloudflare Pages Dashboard" links to the product site and not your dashboard - not sure if it's a bug or by design
Expected Behavior
Link to my dashboard
Additional information
No response

Specifically, the 3rd button should link to https://dash.cloudflare.com/?to=/:account/pages


spawn_unsafe should require that F: Send

The spawn_unsafe method in Crossbeam should include a bound on the function f: F that it is also Send. Otherwise, you may end up calling functions that access non-thread-safe things like UnsafeCell. This also brings the definition more in line with that of std::thread::spawn. Specifically, the signature should be:
pub unsafe fn spawn_unsafe<'a, F>(f: F) -> JoinHandle<()>
where F: FnOnce() + Send + 'a

The bounds were deliberately left off to provide a maximally flexible, unsafe spawning function -- i.e., to cover even the case where you wanted to work with a non-Send closure unsafely.
That said, the flexibility isn't needed for scoped threads, and of course does add to the overall danger of this function. Arguably, this treatment of Send might be better accomplished through a newtype wrapper anyway. So I'm open to adding the bound.

An alternative might be to provide two unsafe functions instead of one, where one requires Send, and its use is recommended where possible.

Given that there's not a pressing need for a version without Send, I'd accept a PR that just added Send to the current method.

PR submitted: #55.


Investigate inconsistency between nix build and nix develop

Currently nix build works as intended, it runs the preinstall script without issue and outputs nixt in result/bin. Nix develop fails to build. It appears that tsc is not running with the correct working directory, causing tsc to print its help screen instead of transpiling. If the shell node2nix provides is meant for dev use then npm install probably shouldn't be running at all. If it's meant to be run, npm install should return the same result as it does when building. I may have to roll my own devShell.
><EMAIL_ADDRESS>preinstall /nix/store/9230zmgs46fpc1ggw68d0485ax44cikz-node>
> npm run build

><EMAIL_ADDRESS>build /nix/store/yw2xs0sw9bpyi3gm92w1qachw3wxa0s9-node-dependencies-nixt-0.2.1/nixt
> tsc

Version 4.7.4
tsc: The TypeScript Compiler - Version 4.7.4

COMMON COMMANDS

  tsc
  Compiles the current project (tsconfig.json in the working directory.)

  tsc app.ts util.ts
  Ignoring tsconfig.json, compiles the specified files with default compiler options.

  tsc -b
  Build a composite project in the working directory.

  tsc --init
  Creates a tsconfig.json with the recommended settings in the working directory.

  tsc -p ./path/to/tsconfig.json
  Compiles the TypeScript project located at the specified path.

  tsc --help --all
  An expanded version of this information, showing all possible compiler options

  tsc --noEmit
  tsc --target esnext
  Compiles the current project, with additional settings.

COMMAND LINE FLAGS

--help, -h
Print this message.

--watch, -w
Watch input files.

--all
Show all compiler options.

--version, -v
Print the compiler's version.

--init
Initializes a TypeScript project and creates a tsconfig.json file.

--project, -p
Compile the project given the path to its configuration file, or to a folder with a 'tsconfig.json'.

--build, -b
Build one or more projects and their dependencies, if out of date

--showConfig
Print the final configuration instead of building.

COMMON COMPILER OPTIONS

--pretty
Enable color and formatting in TypeScript's output to make compiler errors easier to read.
type: boolean
default: true

--target, -t
Set the JavaScript language version for emitted JavaScript and include compatible library declarations.
one of: es3, es5, es6/es2015, es2016, es2017, es2018, es2019, es2020, es2021, es2022, esnext
default: es3

--module, -m
Specify what module code is generated.
one of: none, commonjs, amd, umd, system, es6/es2015, es2020, es2022, esnext, node16, nodenext
default: undefined

--lib
Specify a set of bundled library declaration files that describe the target runtime environment.
one or more: es5, es6/es2015, es7/es2016, es2017, es2018, es2019, es2020, es2021, es2022, esnext, dom, dom.iterable, webworker, webworker.importscripts, webworker.iterable, scripthost, es2015.core, es2015.collection, es2015.generator, es2015.iterable, es2015.promise, es2015.proxy, es2015.reflect, es2015.symbol, es2015.symbol.wellknown, es2016.array.include, es2017.object, es2017.sharedmemory, es2017.string, es2017.intl, es2017.typedarrays, es2018.asyncgenerator, es2018.asynciterable/esnext.asynciterable, es2018.intl, es2018.promise, es2018.regexp, es2019.array, es2019.object, es2019.string, es2019.symbol/esnext.symbol, es2020.bigint/esnext.bigint, es2020.date, es2020.promise, es2020.sharedmemory, es2020.string, es2020.symbol.wellknown, es2020.intl, es2020.number, es2021.promise/esnext.promise, es2021.string, es2021.weakref/esnext.weakref, es2021.intl, es2022.array/esnext.array, es2022.error, es2022.intl, es2022.object, es2022.string/esnext.string, esnext.intl
default: undefined

--allowJs
Allow JavaScript files to be a part of your program. Use the 'checkJS' option to get errors from these files.
type: boolean
default: false

--checkJs
Enable error reporting in type-checked JavaScript files.
type: boolean
default: false

--jsx
Specify what JSX code is generated.
one of: preserve, react, react-native, react-jsx, react-jsxdev
default: undefined

--declaration, -d
Generate .d.ts files from TypeScript and JavaScript files in your project.
type: boolean
default: `false`, unless `composite` is set

--declarationMap
Create sourcemaps for d.ts files.
type: boolean
default: false

--emitDeclarationOnly
Only output d.ts files and not JavaScript files.
type: boolean
default: false

--sourceMap
Create source map files for emitted JavaScript files.
type: boolean
default: false

--outFile
Specify a file that bundles all outputs into one JavaScript file. If 'declaration' is true, also designates a file that bundles all .d.ts output.

--outDir
Specify an output folder for all emitted files.

--removeComments
Disable emitting comments.
type: boolean
default: false

--noEmit
Disable emitting files from a compilation.
type: boolean
default: false

--strict
Enable all strict type-checking options.
type: boolean
default: false

--types
Specify type package names to be included without being referenced in a source file.

--esModuleInterop
Emit additional JavaScript to ease support for importing CommonJS modules. This enables 'allowSyntheticDefaultImports' for type compatibility.
type: boolean
default: false

You can learn about all of the compiler options at https://aka.ms/tsc

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `tsc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /build/.npm/_logs/2022-07-19T23_32_20_182Z-debug.log

error: builder for '/nix/store/aly55j3zr5s2vhzqj2yc535rywf1hb5v-node-dependencies-nixt-0.2.1.drv' failed with exit code 1;
       last 10 log lines:
       > npm ERR! errno 1
       > npm ERR<EMAIL_ADDRESS>preinstall: `npm run build`
       > npm ERR! Exit status 1
       > npm ERR!
       > npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script.
       > npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
       >
       > npm ERR! A complete log of this run can be found in:
       > npm ERR!     /build/.npm/_logs/2022-07-19T23_32_20_182Z-debug.log

Upon further inspection (I included pwd in the build script), tsc is run in the correct directory; however, tsconfig.json is not present in the nix store.

The issue was that package.json is shared between the derivations for nixt and the node-dependencies so when the node-dependencies are built the preinstall script (the build script, by proxy) is run but tsconfig.json and the source tree are not present in that derivation. Worked around this by checking for tsconfig.json in the build script and exiting cleanly if it is missing. This could be an issue as if tsc for any reason throws, the error will be ignored and the script will still return 0.


Created Ipython Notebook companions for Chapter 3 and 9

Greetings Chris,
So I've forked your GitHub repo and created a small iPython Notebook called «GeoProcPy-Ch3-VectorData.ipynb» and shared it on my GitHub account:  https://github.com/ClaudeCoulombe/osgeopy-code with some additions and modifications in order to make the code working.
I will withdraw the notebook if that offend you in any way.
Claude COULOMBE
Montréal

Hi Claude,
No, that's cool. The code used to work without those changes, and I didn't
realize that it had been broken. I should update all of the code in the
repo when I have time...
Chris
On Fri, Jul 10, 2020 at 3:07 AM Claude COULOMBE<EMAIL_ADDRESS>wrote:

Greetings Chris,
So I've forked your GitHub repo and created a small iPython Notebook
called «GeoProcessing_with_Python-Chap3-VectorData.ipynb» and shared it on
my GitHub account: https://github.com/ClaudeCoulombe/osgeopy-code with
some additions and modifications in order to make the code working.
I will withdraw the notebook if that offend you in any way.
Claude COULOMBE
Montréal
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cgarrard/osgeopy-code/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABB7LOEKGBEFLZOS5VAJOCLR23K4RANCNFSM4OWMYFDA
.

Thanks,
Keep up your good work!
Claude
P.-S.: I've also posted on the book forum

Greetings Chris,
I've just commit another IPython Notebook. This time is about your chapter 9 code, «GeoProcPy-Ch9-RasterData.ipynb».
Best
Claude

Chapter 10 - Working with raster data
I’ve forked the GitHub repo and created a companion IPython Notebook for chapter 10, Working with raster data called GeoProcPy-Ch10-ProcessRasterData.ipynb. On my GitHub: https://github.com/ClaudeCoulombe/osgeopy-code
Hope that can help someone else
Claude Coulombe
Montréal

Greetings Chris,
Chapter 11 - Map algebra
Another companion IPython Notebook for chapter 11, map algebra called GeoProcPy-Ch11-MapAlgebra.ipynb. On my GitHub: https://github.com/ClaudeCoulombe/osgeopy-code
I've got an error with scipy.stats.binned_statistic that I was not able to correct by now.
Claude

Greetings Chris,
Chapter 12 - Map Classification
Probably my last companion IPython Notebook contribution since I'm mainly interested by raster data processing. This one about chapter 12, map classification called GeoProcPy-Ch12-MapClassification.ipynb, On my GitHub: https://github.com/ClaudeCoulombe/osgeopy-code
I've got an error with sample = data[rows, cols, :] for which I've found a patch. It was a problem with fractional pixel offset.
Best
Claude


Update wallaby.config.js

Reusing jest settings from package.json in wallaby config: https://github.com/facebook/jest/issues/2140#issuecomment-261868204

Thanks @ArtemGovorov! I can remember following an example when created this wallaby.config but I can't find it anymore. This is looking much better to me than duplicating configs!


Table of Contents

Adds right-hand Table of Contents
Removes automatic H2, H3 hierarchy in left hand sidebar, only included H1 links.
Prevent ToC on devices smaller than 1300px wide
Miscellaneous corrections on web-configurator.md

Desktop
Before:

After:

Mobile
Site appears unchanged as smaller screens set the width of the ToC to 0%


chore: fix helgrind failure in async_socket_linux

while ((value = interlocked_add(&async_socket->pending_api_calls, 0)) != 0)

Maybe it is not a good idea for me to look too much at this file.
So here's a question: why isn't pending_api_calls enough of a check and we ALSO need event_complete_executing?

Refers to: linux/src/async_socket_linux.c:287 in 080adbd. [](commit_id = 080adbdc2d369135440461d5ed9a5b7da2788da2, deletion_comment = False)

            (void)interlocked_increment(&async_socket->pending_api_calls);

This is sort of "here and everywhere".

In reply to:<PHONE_NUMBER>

Refers to: linux/src/async_socket_linux.c:531 in 080adbd. [](commit_id = 080adbdc2d369135440461d5ed9a5b7da2788da2, deletion_comment = False)

return result;

Iteration 6 comment: I believe there's multiple issues with this file, some of them I've noticed in previous iterations, some in iteration 6 and I don't think (or I don't see how!) we are addressing them.
So I will still be "waiting".

Refers to: linux/src/async_socket_linux.c:738 in 080adbd. [](commit_id = 080adbdc2d369135440461d5ed9a5b7da2788da2, deletion_comment = False)

while ((value = interlocked_add(&async_socket->pending_api_calls, 0)) != 0)

pending_api_call protects against closing while the API's (async_socket_send_async and async_socket_receive_async) are executing, while event_complete_executing protects against closing while in the event_complete_callback function.

In reply to:<PHONE_NUMBER>

Refers to: linux/src/async_socket_linux.c:287 in 080adbd. [](commit_id = 080adbdc2d369135440461d5ed9a5b7da2788da2, deletion_comment = False)


Network Variable Issue

Description
Whenever I add more than 3 offline players to a network variable list, the list times out and console sends me this message, "[Skungee] Timed out attempting to send network variable {test::*}". But, when I use text in a network variable list, I can add as many values as I want.
Actual Behavior
Lists times out after more than 3 offline players are added to a network variable list
Expected Behavior
To be able to add more than 3 offline players in a network variable list
Steps to Reproduce the Problem
1.Add 3 offline players to a network variable list
2.Add 1 more offline player to a network variable then console error message "[Skungee] Timed out attempting to send network variable {test::*}" is recieved
Specifications
Skungee Version: 2.0.0-ALPHA-7
Proxy Platform and Version: Waterfall Build #371
System/Panel (if applicable):

Did u find a solution?


Add signal to cancel container connection attempt

This PR adds IProgress/AbortSignal to the Container.connect() flow. This is used to cancel a connection attempt if Container.disconnect() is called while connection is still in progress.
Follow up: Add test for this scenario. This test is already written, but it will be easier to add to this PR after https://github.com/microsoft/FluidFramework/pull/10009 is merged.
Closes #9789

do you think your concern https://github.com/microsoft/FluidFramework/issues/9789#issuecomment-1110504912 should be addressed as part of this PR? If so, we should probably also implement the state tracking variable we talked about https://github.com/microsoft/FluidFramework/issues/9789#issuecomment-1110101741 in this PR as well.

We should prefer smaller PRs when possible. So if something can be addressed independently, we should use such opportunity. Devil is in the details, of course. :)


PowerShell profile does not run when exiting dotnet-repl with Ctrl+C

This image shows my PowerShell profile running on startup of my terminal. In this example, my profile just has Write-Host "Running profile..." in it.
When I click Ctrl+C to exit dotnet-repl my profile doesn't run so my terminal is not ready to use.

(My actual use case is using Powerline in Windows Terminal. See https://docs.microsoft.com/en-us/windows/terminal/tutorials/powerline-setup. When I click Ctrl+C, my prompt is not set up.)

What version are you using?
This seems to work for me on 0.1.30;

Thank you. I updated to 0.1.35 and it's working now.


ctrlp cannot specify folder search files

I have too many files in my working directory. It will be very slow to search the whole directory

You can use search.exclude to exclude some folders by glob pattern. What else are you looking for?


Better handle errors when writing verification tags in the verifier

We just got an error when trying to verify a bag (https://wellcome-ingest-inspector.glitch.me/ingests/e00994b3-e170-4f84-a9c9-230880e65422). The bag itself was fine, but the storage service couldn't write a verification tag, so it failed:

WARN w.s.b.s.s3.S3StandaloneBagVerifier - Errors verifying s3://wellcomecollection-storage-staging-unpacked-bags/digitised/e00994b3-e170-4f84-a9c9-230880e65422:
 https://wellcomecollection-storage-staging-unpacked-bags.s3.eu-west-1.amazonaws.com/digitised/e00994b3-e170-4f84-a9c9-230880e65422/data/alto/b31983042_0003_0289.xml: We encountered an internal error. Please try again. (Service: Amazon S3; Status Code: 500; Error Code: InternalError; Request ID: XQ9RHMC8VXQD7VX8; S3 Extended Request ID: G/kScO/UnrPj8/+j7WXWpLvymaiN9RUvlGgZ2v9+tecw4tM0uhJ7MJYsunBOF5X9oS2u78Q7rlw=)
 WARN weco.storage.tags.s3.S3Tags - Tags on s3://wellcomecollection-storage-staging-unpacked-bags/digitised/e00994b3-e170-4f84-a9c9-230880e65422/data/alto/b31983042_0003_0289.xml: error when trying to write: StoreWriteError(com.amazonaws.services.s3.model.AmazonS3Exception: We encountered an internal error. Please try again. (Service: Amazon S3; Status Code: 500; Error Code: InternalError; Request ID: XQ9RHMC8VXQD7VX8; S3 Extended Request ID: G/kScO/UnrPj8/+j7WXWpLvymaiN9RUvlGgZ2v9+tecw4tM0uhJ7MJYsunBOF5X9oS2u78Q7rlw=), S3 Extended Request ID: G/kScO/UnrPj8/+j7WXWpLvymaiN9RUvlGgZ2v9+tecw4tM0uhJ7MJYsunBOF5X9oS2u78Q7rlw=)

This needs a couple of changes:

~We shouldn't bother writing these tags at all in the pre-replication bag verifier (which is where this occurred)~
[x] We should retry writing the tags if it initially fails
[ ] We shouldn't fail verification if we can't write a tag – it's a nice-to-have rather than essential

here's a collection of relevant-looking log messages from around the time of the incident:
Alex 2021-09-01 storage debugging.csv

Okay, so it looks like S3Tags probably did retry the writes (at the very least, we have tests for that), but the only information is in debug logs.

I'm going to skip item 1 – we don't actually need to skip writing tags in the pre-replication verifier, and it adds extra complexity and failure modes.


Foreach loops degrade performance

Describe the bug
There has been a mismash of communication on the performance of foreach vs for loops. Research suggests around Unity 5 that foreach loops with List<> elimnated unnecessary garbage collection. But other collection types, such as IEnumerable, still allocated additional enumerator memory. Further, there is research to suggest foreach loops create additional assembly instructions and processing.
References:
https://jacksondunstan.com/articles/3805
https://jacksondunstan.com/articles/4573
https://jacksondunstan.com/articles/3458
https://docs.unity3d.com/Manual/IL2CPP-CompilerOptions.html
To reproduce

Expected behavior
For non-critical code paths, foreach loops are fine and mostly nominal especially if used with the appropriate collection type. But we should strive to use for loops instead of for-each loops in critical paths or large collections. We only benefit with foreach for slightly cleaner code
Screenshots
If applicable, add screenshots to help explain your problem.
Your Setup (please complete the following information)

Unity Version 2018.4.13
MRTK Version mrtk_development

Target Platform (please complete the following information)

HoloLens
HoloLens 2
WMR immersive
OpenVR

Additional context
Add any other context about the problem here.

@Troy-Ferrell, do you have a list of files with critical path foreach loops? Not an issue if the answer is no. Just thought i would ask.

yes, I have started work on this. Particularity targeting
MRTK.cs
FocusProvider.cs
MixedRealityInputModule.cs
Next level would be any pointer classes and their updates


Board Review: Azure-cosmos for Python

Thank you for starting the process for approval of the client library for your Azure service.  Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
** Before submitting, ensure you adjust the title of the issue appropriately **
The Basics

Service team responsible for the client library: CosmosDB
Link to documentation describing the service: https://docs.microsoft.com/en-us/azure/cosmos-db/introduction
Contact email (if service team, provide PM and Dev Lead): chrande
Expected code complete date: 5/31
Expected release date: ~june

About this client library

Name of the client library: azure-cosmos
Target language for this review: Python
Other languages that are to be targeted:
*Java, .Net and Javascript
Link to the service REST APIs:
Link to the reference documentation:
Link to several samples:

Champion Scenarios
A champion scenario is a use case that the consumer of the client library is commonly expected to perform.  Examples might be "Update Firmware", "Download a file", "Recognize faces in a list of pictures".  Champion scenarios are used to ensure the developer experience is exemplary for the common cases.  You need to show the entire code sample (including error handling, as an example) for the champion scenarios.

Champion Scenario 1:

Describe the champion scenario
Link to the code sample

_ Repeat for each champion scenario _
Thank you for your submission

Scheduled for 5/10 @ 9:30am

Feedback from the board review:
[] @christopheranderson to get adparch access to the raw user study data
[] @christopheranderson and @johanste to talk paging offline
[] @christopheranderson to send out what user studies he has planned
[] @adrianhall to set up a discussion on taking dependencies on Azure Core libraries for Cosmos
[] @adrianhall to invite @christopheranderson  to the board meeting for #298
[] @adrianhall to produce PR conflating README repo and design guidelines links into single table
[] @adrianhall to investigate solutions for design guidelines compliance checking


Quality issues when drawing SKBitmap with transparency on rotated canvas

This happens only when canvas is rotated with angles different than 90, 180, 270, and 360 degrees, so any angle that is not a multiple of 90 degrees leads to quality issues. By quality issues I mean with jagged edges, it looks like anti-aliasing is turned off.
Here you can see the code that replicate this issue:
using System.IO;
using SkiaSharp;

namespace DemoSkia
{
    class MainClass
    {
        public static void Main(string[] args)
        {

            using (var surface = SKSurface.Create(2000, 300, SKImageInfo.PlatformColorType, SKAlphaType.Premul))
            {
                SKCanvas canvas = surface.Canvas;
                canvas.Clear(new SKColor(255, 255, 255, 0));

                var TextStyleFillColor = new SKColor(0, 0, 0, 255);

                var TextStyleFillPaint = new SKPaint()
                {
                    Style = SKPaintStyle.Fill,
                    Color = TextStyleFillColor,
                    BlendMode = SKBlendMode.SrcOver,
                    IsAntialias = true,
                    Typeface = SKTypeface.FromFamilyName("Helvetica", SKTypefaceStyle.Normal),
                    TextSize = 14f,
                    TextAlign = SKTextAlign.Left,
                    IsVerticalText = false,
                    TextScaleX = 1f,
                    TextSkewX = 0f
                };

                Stream fileStream = File.OpenRead("3-2.png");

                using (var stream = new SKManagedStream(fileStream))
                using (var bitmap = SKBitmap.Decode(stream))
                using (var paint = new SKPaint())
                {
                    var scaled = bitmap.Resize(new SKImageInfo(247, 260, bitmap.ColorType, bitmap.AlphaType), SKBitmapResizeMethod.Lanczos3);

                    paint.IsAntialias = true;

                    var x = 0;
                    var y = 20;
                    var angle = 0;

                    // this looks fine with no rotation
                    canvas.DrawBitmap(scaled, SKRect.Create(x, y, 247, 260), paint);
                    canvas.DrawText($"{angle} degress (good)", x + 20, y, TextStyleFillPaint);

                    // this looks bad with 15 degrees rotation
                    angle = 15;
                    x += 270;
                    canvas.RotateDegrees(angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawBitmap(scaled, SKRect.Create(x, y, 247, 260), paint);
                    canvas.RotateDegrees(-angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawText($"{angle} degress (bad)", x + 20, y, TextStyleFillPaint);

                    // this looks bad with 45 degrees rotation
                    angle = 45;
                    x += 270;
                    canvas.RotateDegrees(angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawBitmap(scaled, SKRect.Create(x, y, 247, 260), paint);
                    canvas.RotateDegrees(-angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawText($"{angle} degress (bad)", x + 20, y, TextStyleFillPaint);

                    // this looks bad with 120 degrees rotation
                    angle = 120;
                    x += 270;
                    canvas.RotateDegrees(angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawBitmap(scaled, SKRect.Create(x, y, 247, 260), paint);
                    canvas.RotateDegrees(-angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawText($"{angle} degress (bad)", x + 20, y, TextStyleFillPaint);

                    // this looks good with 90 degrees rotation
                    angle = 90;
                    x += 270;
                    canvas.RotateDegrees(angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawBitmap(scaled, SKRect.Create(x, y, 247, 260), paint);
                    canvas.RotateDegrees(-angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawText($"{angle} degress (good)", x + 20, y, TextStyleFillPaint);

                    // this looks good with 180 degrees rotation
                    angle = 180;
                    x += 270;
                    canvas.RotateDegrees(angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawBitmap(scaled, SKRect.Create(x, y, 247, 260), paint);
                    canvas.RotateDegrees(-angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawText($"{angle} degress (good)", x + 20, y, TextStyleFillPaint);

                    // this looks good with 270 degrees rotation
                    angle = 270;
                    x += 270;
                    canvas.RotateDegrees(angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawBitmap(scaled, SKRect.Create(x, y, 247, 260), paint);
                    canvas.RotateDegrees(-angle, x + scaled.Width / 2, y + scaled.Height / 2);
                    canvas.DrawText($"{angle} degress (good)", x + 20, y, TextStyleFillPaint);
                }

                using (var data = surface.Snapshot().Encode())
                {
                    using (var stream = File.OpenWrite("image.png"))
                    {
                        data.SaveTo(stream);
                    }
                }
            }
        }
    }
}

The code above generates this image (click on the image to see higher resolution version):

I'm using net core 2.0.0 with SkiaSharp v1.59.1 on Mac and Linux and it happens on both.

+1 for this, there's a big issue here - have there been any updates?

I don't think that is an issue from the SkiaSharp bindings, but the actual native C++ DLL.  Can you rewrite this program in C++ and see if the same results happen?  If so, you'll need to then take this over to the Skia developers: https://bugs.chromium.org/p/skia/issues/list
Though, there could be some flag you might be missing.

Did you get any traction on this?  I'm having the same issue.

The reason for the bad quality is the fact that only the resize is a high quality operation. The drawing step is just using the fastest/default. To improve the drawing quality, you need to set the paint quality:
paint.FilterQuality = SKFilterQuality.High

In addition, instead of first resizing and loosing most of the image data, and then trying to rotate, it may be better to do this in a single operation. If you draw an image at a smaller size than the original, it will scale - also using the filter quality.


add folder 'img' and update readme-md

add folder 'img' to electron-logo.svg

'/electron-logo.svg' to 'img/electron-logo.svg'

Pls change in the readme file as well.

Pls change in the readme file as well.

this has been updated in this pull-request/branch.

thank you @sudhakar3697


Include an "info" action variant for bootgrid.

-=david=-

Ideally, we want to find a way to register buttons automatically instead of defining new groups for different kinds of clusters. But for now this works well enough. Thanks!


[v4] Disable Prismic Toolbar

I saw this from v4 docs,

Note: The toolbar is required for previews to function and cannot be disabled.

But I don't understand why this became necessary. This is a major blocker to me as I don't want the Toolbar to appear on my site.

Hi @cometkim,
The toolbar is necessary to set a preview-specific cookie in the browser. Without this, previews would not be registered as being "active."
It also enables a few features:

Automatic refreshing when content is saved in Prismic (i.e. "live" preview sessions)
Share links
Links to edit documents used on the page

If you want to hide the toolbar from editors, you could use CSS to ensure it is invisible:
iframe[src*=".prismic.io/prismic-toolbar/"] {
  visibility: hidden;
}

This will allow the toolbar to be present to manage the preview cookie and automatically refresh the page while having no visible UI.

I see. I added a global style to my website
#prismic-toolbar-v2 {
  visibility: hidden;
}

It would be nice to add docs for this. or we can add an options to supports it behind of a scene

And since the toolbar is required, it's better to provide a preconnect directive for the prismic toolbar location.


[WIP] ES2023 support

JIRA: CPOUI5FOUNDATION-850

coverage: 94.587% (-0.08%) from 94.663%
when pulling 26ef6e6dcd06b18fc382f9a9627d70608e304591 on es2023-support
into 3dca5ed2d0b02423eb860601b69d998bd6cb4545 on main.

coverage: 94.667% (+0.004%) from 94.663%
when pulling 26ef6e6dcd06b18fc382f9a9627d70608e304591 on es2023-support
into 3dca5ed2d0b02423eb860601b69d998bd6cb4545 on main.

coverage: 94.667% (+0.004%) from 94.663%
when pulling 1a219c81e05c01a57ad7c404f3b3de722dc45fee on es2023-support
into 3dca5ed2d0b02423eb860601b69d998bd6cb4545 on main.

coverage: 94.667% (+0.004%) from 94.663%
when pulling 730f8bd9be3f3741e1d12efede774e3ce7687fc2 on es2023-support
into 3dca5ed2d0b02423eb860601b69d998bd6cb4545 on main.

coverage: 94.667% (+0.004%) from 94.663%
when pulling 7e64aedbee367f8108b4be08659b95cd3b516ff1 on es2023-support
into 3dca5ed2d0b02423eb860601b69d998bd6cb4545 on main.

coverage: 94.667% (+0.004%) from 94.663%
when pulling 93432b032dccb7eb26aa3a7d230137cbeed680af on es2023-support
into 3dca5ed2d0b02423eb860601b69d998bd6cb4545 on main.


Occasional timeout when changing tile size

Seems to be related somehow to the more zoomed-in map sizes. Haven't noticed this problem on the larger map sizes. So far observed on maps with tile size of at least 36px. Always seems to occur once enemies have already spawned on the map.

Issue confirmed to be due to the minimum distance between spawnpoint and exit being too large for the map. If the map is very small it is possible for there to be no valid spawnpoint positions, resulting in an infinite loop.

Fixed. Now if there are too many failed attempts to place a spawnpoint it will just place it on any empty tile, rather than doing an infinite loop.


[docs] collapsible component props

I think we can add a collapsible container for component props on the docs site so the others can read the docs without getting distracted by other component props doc

Superseded by #67.


Sagetv UI Hang

I did a clean install of Windows 10. The SageTV log shows UI hangs.
sagetv_0.zip

At a glance, this looks like you were having network connectivity issues.  Most the hangs appear to be while trying to download relatively small files, and the downloads were failing.

This is because of the STV modification you have which stops the thread
which was causing CPU usage problems on your system for some reason.  It's
waiting on a timeout and is blocking other things at that time...it's also
exacerbated by other slowness in network connectivity that Fuzzy pointed
out.
On Tue, Nov 8, 2016 at 2:49 AM, Christopher Piper<EMAIL_ADDRESS>wrote:

At a glance, this looks like you were having network connectivity issues.
Most the hangs appear to be while trying to download relatively small
files, and the downloads were failing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/sagetv/issues/212#issuecomment-259105546, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANEIDHRxdQpNAgkEIWb3HY_dB8s_W5gqks5q8FPBgaJpZM4KsB_z
.

--
Jeffrey Kardatzke
<EMAIL_ADDRESS>Google, Inc.

I disabled my high cpu usage fix plugin and I am still getting a UI Hang.
sagetv 11-8.zip

The log file printing out a hang when its finishing up startup is normal...you're not even seeing the UI yet and it was only delayed loading by a couple seconds. There were no hangs in the log file after the UI was loaded.


[RBI] Issues reported by rbi

[ ] If I sell or buy tokens, it seems that only the total “my balance is updated” in EUR and not the actual ET1 account, see transactions for selling 2 GTs (images 1 - 2)
[ ] If I buy GTs from my ETs – it does not seem to add up after the transaction. In this example I spent 250 ETs for ~4 GTs and it is not reflected in the spent ETs – I only have ~125 EUR less (which is only worth 2 GTs) but still I have extra 4 GTs. Meaning, where is the missing 250 ETs (images 3 - 4)

Images 1 - 2 (before - after):

Images 3 - 4 (before - after):

the overall balance values after both transactions (sale of 2 gt1 and purchase of 4 gt1) are correct:

step
actual-total / correct-total
actual-gt1 / correct-gt1 = eur-value
actual-et1 / correct-et1

initial
10.007,26 / 10.007,26
4,1 / 4,1 = 256,26
9.751 / 9.751

sale of 2 gt1  (receive ~124,81)
9.882,45 / 10.007,26
2,1 / 2,1 = 131,45
9.751 / 9.875,81

purchase of 4 gt1 (spend 250 et1)
10.007,27 / 10.007,27
6,11 / 6,11 = 381,47
9.625,8 / 9.625,8

Most likely, the customer experienced a delay in the broadcast of et1 transaction, hence only the gt1 transaction result was displayed in balance. After the 2nd transaction, on purchase of gt1 for 250 et1, both transactions were broadcasted before the customer refreshed the page, so the balance was updated to the right values. There's not more gt1 received or less et1 spent than requested.
In order to make the transactions broadcast faster, the priority strategy was set to High.
closing as not a bug.


Uncaught TypeError: Cannot read property 'lang' of undefined

I did include the german language file of summernote and use lang="de-DE" in my sumemrnote directive. But I am getting the error: Uncaught TypeError: Cannot read property 'lang' of undefined

@doczoidberg
Can you explain more detail for the issue? Because I can't reproduce it.
In my test, there is no error.

this seams to be a summernote problem. => https://github.com/summernote/summernote/issues/851


Is this project still alive?

Given there was no activity here for almost a year and my attempt of contribution received no feedback I am wondering if this project is still alive.
I am creating this issue in the hope this has more visibility than creating a PR.

I have volunteered to help maintain this project!


Generators "not supported" even when targetting ES6

Visual Studio display a syntax error in function* and the message "Generators are not currently supported." even when I'm targeting to compile to ES6, that already has support for generators.
This message wouldn't apper only in ES3 or ES5 mode?

Hi @lmcarreiro, support for generators are slated for TypeScript 1.6. See our roadmap for more details.

Hi @DanielRosenwasser, thanks for response...
But it's not a TypeScript support, I'm talking only about syntax recognition when compiling TypeScript to ES6.
For generators support I'm using traceur in TypeScript *.js output files...
Will it work only in 1.6 too?

Ah, I misunderstood - in fact, I think I ran into this issue myself with #3328. @paulvanbrenk can you confirm that this is a duplicate and has since been fixed?

@lmcarreiro if it compiles as expected on the command line it's indeed the same issue as #3328 which has been fixed.

@lmcarreiro can you confirm that on the command line, this compiles correctly right now?

Which version should it work? I tried in 1.5.0-beta and it doesn't work.
//a.ts
function* a() {
	yield 1;
}

>"C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.5\tsc" --target ES6 a.ts
a.ts(1,9): error TS9001: Generators are not currently supported.
a.ts(2,2): error TS9000: 'yield' expressions are not currently supported.

>"C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.5\tsc" --version
message TS6029: Version 1.5.0-beta

@mhegazy should that be showing 1.5.2 or something along those lines?

Generators support is added in 1.6, 1.5-beta or 1.5.2 would give you the same error message (see roadmap). @lmcarreiro if you want to use that, grab the latest from master it should do the trick.

Thank you all for your answers...
I took the last version on master branch and it worked. Compiles ok with ES6 and displays an error with ES5.
>"C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.5\tsc" --version
message TS6029: Version 1.5.3

>"C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.5\tsc" --target ES6 a.ts

>"C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.5\tsc" --target ES5 a.ts
a.ts(1,9): error TS1220: Generators are only available when targeting ECMAScript 6 or higher.

>

@lmcarreiro we are should be adding ES5 support in the next release (post 1.6). plans has not solidified yet at this point, but stay tuned.

Is there a way to squelch the "Generators are not currently supported." warnings? Currently outputting to ES6 and transpiling with Babel, but would like to still have type error warnings.


Can't get it work with CRA.

Here's what I did:
import React from 'react';
import ReactDOM from 'react-dom';
import Styletron from 'styletron';
import { StyletronProvider } from 'styletron-react';
import App from './App';
import './index.css';

const styletron = new Styletron(document.getElementsByClassName('styletron'));

ReactDOM.render(
  <StyletronProvider styletron={styletron}>
    <App/>
  </StyletronProvider>,
  document.getElementById('root')
);

and the rest is the same as CRA. I keep getting error below:
Uncaught TypeError: Cannot read property 'sheet' of undefined
    at StyletronClient.injectDeclaration (styletron-client.js:92)
    at injectWithPlugins (inject-style-prefixed.js:89)
    at Object.injectStyle [as injectStylePrefixed] (inject-style-prefixed.js:46)
    at StyledElement (styled.js:77)
    at ReactCompositeComponent.js:306
    at measureLifeCyclePerf (ReactCompositeComponent.js:75)
    at ReactCompositeComponentWrapper._constructComponentWithoutOwner (ReactCompositeComponent.js:305)
    at ReactCompositeComponentWrapper._constructComponent (ReactCompositeComponent.js:280)
    at ReactCompositeComponentWrapper.mountComponent (ReactCompositeComponent.js:188)
    at Object.mountComponent (ReactReconciler.js:46)

Hi @sammkj, do you have an HTML stylesheet element that matches document.getElementsByClassName('styletron')?  My guess is that returns undefined, which is why you're seeing the error.
Normally, the argument into the Styletron constructor is an HTML style element that contains server-rendered styles that are used to hydrate the client's CSS cache.  If you're not using server rendering for Styletron, you could do something like this:
import React from 'react';
import ReactDOM from 'react-dom';
import Styletron from 'styletron';
import { StyletronProvider } from 'styletron-react';
import App from './App';
import './index.css';

const styleSheet = document.createElement('style');
document.head.appendChild(styleSheet);
const styletron = new Styletron(styleSheet);

ReactDOM.render(
  <StyletronProvider styletron={styletron}>
    <App/>
  </StyletronProvider>,
  document.getElementById('root')
);

This will instantiate your React app's Styletron instance with an empty stylesheet, which it will use to apply newly encountered declarations.
@rtsao, would it make sense to make the constructor argument optional?  I think the answer is no, since that could lead to implicit poor performance where StyletronClient silently re-adds a bunch of existing declarations to the DOM, but maybe I'm missing something.

Yeah, maybe it's better for client-side use cases to have automatic creation of a stylesheet if one isn't passed into the constructor.

@scott113341 I tried your suggestion. I still got the same error.

@sammkj The styletron client constructor expects a NodeList or HTMLCollection. The following should work.
const styleSheet = document.createElement('style');
document.head.appendChild(styleSheet);
const styletron = new Styletron([styleSheet]); // note the array literal here

That said, I think it makes sense for a stylesheet to be optional. Styletron used to only use one stylesheet, so before it made sense to create it yourself and just pass it in. But now that it uses multiple sheets, I think this doesn't make as much sense.

@rtsao ooppss. I admit that I didn't read the docs thoroughly. It's working now!

It would be nice to add a demo to the ReadMe like styled-components has. I adapted that one to use styletron. Check it out.

@vinnymac Nice! Added to the README 🎉

Closing this issue in favor of https://github.com/rtsao/styletron/issues/34


Could not load a Sketch preview "images/5dd04a87d1827ce5b0a269d480e531417eafcce4.pdf"

Describe the bug
Source Sketch File from the UX/UI designer won't load on xlayers.dev
To Reproduce
Steps to reproduce the behavior:

Go to 'xlayers.dev'
Click on 'upload file from your computer'
Scroll down to 'sharetribe flex desktop'
See error

Expected behavior
Source file uploaded into xlayers.dev so we can convert from Sketch to react code
Screenshots
If applicable, add screenshots to help explain your problem.
Sketch (please complete the following information):

version: web interface (v53?)

Desktop (please complete the following information):

OS: win7, macOS (both have experienced the same error)
Browser: chrome, safari
Version: latest for both

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser: [e.g. stock browser, safari]
Version: [e.g. 22]

Additional context
I couldn't upload the sketch file to github, but you can download it here:
https://www.dropbox.com/s/unzg262038i2s4d/Sharetribe-FLEX_Desktop.sketch?dl=0

Hi, thank you for taking your time to submit this issue. Based on the provided error I believe this issue is the same issue as described in #321, would you mind to verify this for me? The fix for this issue is already provided in the issue.
If your are willing to contribute or always wanted to start contribute we can help you with this by guiding you through the process. If you're not interested that's fine also 😊

That appears to be the same issue. I'll run locally and make the adjustment to the code and let you know if it works. Thanks!

hey @bitcointroy, did you have some time to look into the issue? If you didn't worry  just checking in 😃

This issue is fixed by #324 when we deploy a new release you should be able to work with version 56 of sketch.


Added data points

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


Fix grammar in usingtask-element-msbuild.md

Summary
I was looking over this document and I reread this sentence several times, trying to understand what the intent was.

Because there is no Runtime or TaskHost specified, the task will be executed the MSBuild process, in the runtime and architecture that happen to be running for a given build.

I believe it meant that "the task will be executed in the current MSBuild process", but I just added in since I wasn't exactly sure. Feel free to modify the PR if there is a better phrasing for clarity.

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


Login not working -  seems encrypted password issue

I asked this on Stack Overflow, but no response in a month. I can log in via omniauth-twitter and via my admin user, but regular users get a 401, even after password reset link. On password reset, Devise logs in user, but if you logout and try to log in using new password, get a 401. If I create a new user, it won't let me log in.
In checking user records, it doesn't seem to be generating the hash for encrypted_password on save. If I check using .valid_password? "password", I get false, even after resetting password.
I am running Ruby 2.3.1 + Rails <IP_ADDRESS> + Devise 4.4.1
Nothing in the sessions_controller.rb
application_controller.rb
class ApplicationController < ActionController::Base
  # Prevent CSRF attacks by raising an exception.
  protect_from_forgery with: :exception

  before_action :configure_permitted_parameters, if: :devise_controller?

protected

def configure_permitted_parameters
  devise_parameter_sanitizer.permit :account_update, keys: [:username, :customer_id, :password, :password_confirmation, :remember_me, address_attributes: [:name, :address1, :address2, :city, :state, :zip]]
end

def after_sign_in_path_for(resource_or_scope)
  if admin_user_signed_in?
    admin_root_path
  else
    if request.env['omniauth.auth']
      provider = request.env['omniauth.auth'].provider
      session["login.#{provider}"] = provider
    end
    edit_user_registration_path
  end
end

end

sessions/new.html.haml
= form_for(resource, as: resource_name, url: session_path(resource_name)) do |f|
        = devise_error_messages!
        .field
          = f.label :email
          %br/
          = f.email_field :email, autofocus: true
        .field
          = f.label :password
          %br/
          = f.password_field :password, autocomplete: "off"
          - if devise_mapping.recoverable? && controller_name != 'passwords' && controller_name != 'registrations'
            = link_to "Forgot your password?", new_password_path(resource_name), class: "right small"
        %br/
        - if devise_mapping.rememberable?
          .field.small
            = f.check_box :remember_me
            = f.label :remember_me
        .actions.center
          = f.submit "Log in", class: "waves-effect waves-light btn"
      = render "devise/shared/links"

routes.rb
 devise_for :users, controllers: {registrations: "users/registrations", sessions: "users/sessions", passwords: "users/passwords", omniauth_callbacks: 'omniauth_callbacks'}, skip: [:sessions, :registrations]

  devise_scope :user do
    get    "login"   => "users/sessions#new",         as: :new_user_session
    post   "login"   => "users/sessions#create",      as: :user_session
    delete "signout" => "users/sessions#destroy",     as: :destroy_user_session

    get    "signup"  => "users/registrations#new",    as: :new_user_registration
    post   "signup"  => "users/registrations#create", as: :user_registration
    put    "signup"  => "users/registrations#update", as: :update_user_registration
    get    "account" => "users/registrations#edit",   as: :edit_user_registration

    put 'update_plan', :to => 'users/registrations#update_plan'
    put 'update_card', :to => 'users/registrations#update_card'

  end

Console output:
Completed 401 Unauthorized in 15ms (ActiveRecord: 1.7ms)
Processing by Users::SessionsController#new as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"x0ACUBAv4MPdK2DmFvIC0c/PqiWgD+AK/+Z2VxMmtWrGvFrKcgs+gLdbJcxUo1W8QWTP2ccbDdX6WOLu0ATovQ=="<EMAIL_ADDRESS>"password"=>"[FILTERED]","remember_me"=>"0"}, "commit"=>"Log in"}

Thanks!

Hello @airjoshb, thanks for your report.
Can you provide us a sample application that reproduces the issue in isolation?
You can also use our bug report template.
That would help us find the issue.
Thank you!

I discovered the issue - and can't recall why it was there - but had attr_accessor for password, so it wasn't encrypting. A very random old search had pointed that out. All my tests were passing btw, which was weird. Thanks.


feat: Implement flow health probing

Description
Changes proposed in this pull request (what was done and why):

Introducing the flowhealth package. This package is specifically designed to generate Prometheus alert rules for OTel Collector. Additionally, it utilizes the Prometheus client library to query these alerts and to map them to specific situations such as throttling, data drops, buffer saturation, etc. Please note, that this initial PR does not cover status conditions; these will be addressed in a follow-up.

Changes refer to particular issues, PRs or documents:

https://github.com/kyma-project/telemetry-manager/issues/822

Traceability

[x] The PR is linked to a GitHub issue.
[x] New features have a milestone set.
[x] New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
[x] The corresponding GitHub issue has a respective area and kind label.
[ ] The follow-up issues (if any) are linked in the Related Issues section.
[ ] Adjusted the documentation if the change is user-facing.
[x] The feature is unit-tested
[ ] The feature is e2e-tested

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build

/test pull-telemetry-manager-build


avoid unreasonable growth of the repository size

At the moment, the rfcs repo is pretty huge. The big history of
gh-pages is to blame, as each gh-pages commit contains a 50MB search.js
file. There's little value in preserving history of gh-pages branch,
so let's avoid creating new commits.
Note that someone should manually squash existing commits to one on the gh-pages branch. Alternatively, we can merge a one-off change to .travis.yml for squashing.

this is "fixing" #2750 ?

Ah indeed, the approach in #2751 seems better!