MouseMove callback

The api states:
mouseMoveCallback :function
A callback that can be fired when the mouse is moved while pressed down.
But the behavior seems to be whenever the mouse moves, regardless of wether it is pressed down or not.

The move callback in Input is linked to the Pointer class, so doesn't care if it's coming from the mouse, touch pointer, etc. Which is the method that should be used. The one in the Mouse class is specifically used by the Mouse only and should mostly be ignored. I've flagged it as deprecated, as it shouldn't be used directly.

The move callback in Input is linked to the Pointer class, so doesn't care if it's coming from the mouse, touch pointer, etc. Which is the method that should be used. The one in the Mouse class is specifically used by the Mouse only and should mostly be ignored. I've flagged it as deprecated, as it shouldn't be used directly.


ch40m1um.qjz9zk

possible security issue?
steps to repo

open about chromium

click chromium

see this

No, there's no security issue here. That's just the result of domain substitution with the patch that intercepts all qjz9zk URLs. Is there a problem with this behavior?

just seems a little weird that through the UI, in the about area, you can click on a URL that is blocked.

Well these kinds of links are scattered throughout the UI, so I don't think it's too strange.

Same Problem with Version 109.0.5414.74 (Official Build, ungoogled-chromium) (64-bit)

好吧，这些类型的链接分散在整个UI中，所以我认为这并不太奇怪。

Is there any way to make it cleaner？


Syntax highlighting

I added a very naive implementation of syntax highlighting (headers, lists, links, bold, italic, monospace and strikethrough are supported at this stage).
It can be activated/deactivated through preferences. The syntax refresh delay is also configurable, for battery-life paranoids.

Very nice! Thanks for the contribution! Will merge and check it out :)

My pleasure. It's not the most elegant of solutions, but it will do the job.


Option to not show the plus sign when a new event can be added from a page

I don't ever use that functionality. The plus sign mostly shows up when I'm on Wikipedia. It would be nice to be able to turn it off, as it can be distracting.

+1 a way of disabling that feature entirely would be greatly appreciated. the only thing I want is to see information currently in my calendar. i never want to add new items via the extension.


Added schema creation (postgres) if needed on first migration

fix a problem with first migration when you don't have schema yet.
Before you had a bug like this:
error: create table "config"."knex_migrations" ("id" serial primary key, "name" varchar(255), "batch" integer, "migration_time" timestamptz) - schema "config" does not exist

I'd love to have this functionality as well. Unfortunately the commit broke the build but a conditional call of createSchemaIfNotExists based on if a schemaName exists should resolve the issue.

Its working only with Postgres yet.. I will fix it and make PR again.

@spanyukov Do you think you'll have time to update this PR? I don't mind opening a new PR if not.

@spanyukov Do you think you'll have time to update this PR? I don't mind opening a new PR if not.

I added condition.

Your changes unfortunately don't pass CI. You are probably better off appending the createSchemaIfNotExists to https://github.com/knex/knex/blob/9b82d0653a64bb56397275d524d2a51f06e1a41c/lib/migrate/table-creator.js#L70
Then the change only needs to happen in one place and that place is already "schema aware".
Also there is docker-compose file if you want to run tests locally to verify your changes.

Your changes unfortunately don't pass CI. You are probably better off appending the createSchemaIfNotExists to
https://github.com/knex/knex/blob/9b82d0653a64bb56397275d524d2a51f06e1a41c/lib/migrate/table-creator.js#L70
Then the change only needs to happen in one place and that place is already "schema aware".
Also there is docker-compose file if you want to run tests locally to verify your changes.

thanks! I put this code to schema builder getter as you described.


Update Get-SPEnterpriseSearchStatus.md

Remove SharePoint 2010 applicability. Format examples.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Get-SPEnterpriseSearchStatus.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


Remove use of Mojo::Home

Summary
In both Mojolicious::Renderer and Mojolicious::Static, Mojo::File is already
being used. Rather than using Mojo::Home, we can use path(__FILE__) to shorten
the detection of the resources paths. This more closely mimics what is done
in Minion
Motivation
Code simplification
References
Here is how Minion get path to its resources

merged into upstream


New related_name triggering migrations for all plugins

It appears that this commit changed how the related_name is calculated per CMSPlugin subclass. If I do ./manage.py makemigrations, it attempts to create migrations for any installed app which subclasses CMSPlugin:
$ ./manage.py makemigrations
Migrations for 'cmsplugin_filer_image':
  0009_auto_20160719_0239.py:
    - Alter field cmsplugin_ptr on filerimage
Migrations for 'cmsplugin_filer_file':
  0005_auto_20160719_0239.py:
    - Alter field cmsplugin_ptr on filerfile
Migrations for 'djangocms_inherit':
  0003_auto_20160719_0239.py:
    - Alter field cmsplugin_ptr on inheritpageplaceholder
Migrations for 'cmsplugin_filer_teaser':
  0003_auto_20160719_0239.py:
    - Alter field cmsplugin_ptr on filerteaser
Migrations for 'cmsplugin_filer_folder':
  0003_auto_20160719_0239.py:
    - Alter field cmsplugin_ptr on filerfolder

As far as I can tell, the only thing these migrations do is add the related_name attribute to the cmsplugin_ptr field.
I didn't see any warning about this in the documentation and I don't see bugs or recent migrations added to other projects (cmsplugin_filer_*, etc.) so my first suspicion is that I've goofed something up or am generally suffering from lack of sleep. Apologies if so!
If this is a legitimate bug, this seems to mean that every external plugin app needs to have a new migration added and possibly will need to have point releases that are pinned to django-cms>=3.3.1. I haven't tested, but if these migrations are added to a plugin app that is then run on django-cms<3.3.1, won't migrations detect the lack of a related_name attribute and want to create a migration to remove it?

@jsma
Hello,
Thanks for reporting.
This is a known issue, we've been discussing internally how to address it without too much effort on project developers.
So far we think the best approach is to create the migration for apps that support 3.3.0 and up meaning Django 1.8+ (cmsplugin-filer is an example). For apps that still support Django 1.6 and 1.7, we're planning to either drop 1.6 & 1.7 support or simply add the parent link field explicitly to the plugin model and specify the old related_name.

Should end users (as opposed to reusable app authors) just let makemigrations generate these migrations and apply them?

@jsma you should avoid creating any migrations in apps that are not part of your project sourcecode at all costs. Because they will end up somewhere in the site-packages of your virtualenv and only visible to that specific deployment of the project. So they can disappear again whenever the virtualenv (or docker container) is rebuilt. That would cause all sorts of annoying manual cleanup for your db (ghost migrations, unmerged migrations, ...).
And if you're developing a re-usable app in the context of such a project, a new migration in your app might depend on a migration that only exists in that one project.

@stefanfoulis What's the recommended way to handle that situation? Some apps (djangocms-filer being a prime candidate) quite often don't include the necessary migrations.
Is there a best practice way to handle it? Is that best practice to simply not upgrade to a version of an app with missing migrations? Or is there some way to create placeholder migrations until the app author creates the "official" migrations?

@czpython Re https://github.com/divio/django-cms/issues/5550#issuecomment-233622904 why not release a major version finally (1.0) of all affected plugins, conveying this is for an LTS version of Django (1.8) and up, while the 0.x versions can stay backward compatible.
If this is consistently executed over all djangocms_* projects / plugins then that'd be any easy rule to learn for each and every Django developer using django CMS and its plugins. - What do you think?
In any case, this is something that should be addressed very soon.

@czpython

So far we think the best approach is to create the migration for apps that support 3.3.0 and up meaning Django 1.8+ (cmsplugin-filer is an example). For apps that still support Django 1.6 and 1.7, we're planning to either drop 1.6 & 1.7 support or simply add the parent link field explicitly to the plugin model and specify the old related_name.

Since this was introduced in the 3.3.1 release, shouldn't there a note in the changelog for v3.3.1 that mentions that this is to be expected? My organization maintains about 10 different CMS plugins, and to see that a new migration must be made for all of them because of what might appear at first glance to be a (semver) patch release was a little jarring. At first, I thought this was a problem with our configuration because there was no note of this in the changelog.

Closing as this has now been addressed in all major addons.


integration-ebpf: artifact dependency bpf-linker

Replace the manual dependency machinery in integration-test/build.rs
with:

integration-ebpf -[artifact-dependency]-> bpf-linker.
integration-test -[build-dependency]-> integration-ebpf.
integration-ebpf: build.rs that makes bpf-linker available to rustc.
integration-ebpf: lib.rs (empty) creates a lib target, allows dep from
integration-test.
xtask: filter for test binaries now that the build also produces the
bpf-linker binary.
github: remove cargo install bpf-linker and commentary about cache
invalidation.
integration-test: remove bpf-linker installation instructions.

Drat. This breaks the workflows on stable because cargo refuses to read test/integration-ebpf/Cargo.toml which now contains artifact = ... even though we --ignore integration-ebpf on the command line.
I'm thinking about how to solve this.


present-4.1.0 is not published to Hackage

present 4.1.0 is currently not available on Hackage, which means it's impossible to use the function presentShow since it's only the latest version that has it.

That'll have to wait until it's more stable.

You can use the sh script in your local environment to make it always available.


Add Nicely Formatted Title for Each User Story

Add a first heading user story title for each user story markdown file.


Agberk fix unmatchedorder rac rc

Coverage remained the same at 92.124% when pulling 666d3cf22321b2cecca4ba2617253db417c99fdd on agberk-fix-unmatchedorder-rac-rc into 1d19b11975146626196af753adb2d0617a735c62 on master.


docker: Remove moving app to public path

This will decouple the vue.config.js publicPath definition from the path being served by nginx within the container. This will allow a proxy to sit in front of this container and pass to a subdirectory specified with PUBLIC_PATH.
In other words, the container will always serve from /, but allow PUBLIC_PATH to be defined identically to a separate proxy location to serve on a subdirectory like http://example.com/nextline/.
Here's an example docker-compose config that demonstrates what I mean:
version: '3.7'
networks:
  default:

services:
  nextline-web:
    image: nextline-web:test
    container_name: nextline-web
    environment:
      - API_HTTP=http://localhost/nextline-api/
      - PUBLIC_PATH=/nextline/

  nextline-backend:
    image: ghcr.io/simonsobs/so-daq-sequencer:v0.1.3
    container_name: nextline-backend

  nginx:
    image: nginx
    restart: always
    volumes:
     - ./nginx.conf:/etc/nginx/nginx.conf:ro
    ports:
     - "<IP_ADDRESS>:80:80"

And accompanying nginx config:
user       nginx;  ## Default: nobody
worker_processes  1;  ## Default: 1

error_log  /var/log/nginx/error.log;
pid        /var/run/nginx.pid;
worker_rlimit_nofile 8192;

events {
  worker_connections  1024;  ## Default: 1024
}

http {
  include    /etc/nginx/mime.types;
  #include    /etc/nginx/proxy.conf; #include    /etc/nginx/fastcgi.conf;
  index    index.html index.htm index.php;

  default_type application/octet-stream;
  log_format   main '$remote_addr - $remote_user [$time_local]  $status '
    '"$request" $body_bytes_sent "$http_referer" '
    '"$http_user_agent" "$http_x_forwarded_for"';
  access_log   /var/log/nginx/access.log  main;
  sendfile     on;
  tcp_nopush   on;
  server_names_hash_bucket_size 128; # this seems to be required for some vhosts

  # Nextline Websocket Connection
  # For websocket connection upgrade
  # https://www.nginx.com/blog/websocket-nginx/
  map $http_upgrade $connection_upgrade {
      default upgrade;
      '' close;
  }

  server { # simple reverse-proxy
    listen       80;
    server_name  localhost;
    access_log   /var/log/nginx/nginx.log;
    root         /usr/share/nginx/html;

    # serve static files
    # location ~ ^/(images|javascript|js|css|flash|media|static)/  {
    #   root    /var/www/virtual/big.server.com/htdocs;
    #   expires 30d;
    # }

    #auth_basic "Restricted Content";
    #auth_basic_user_file /etc/nginx/.htpasswd;

    location /nextline/ {
      proxy_pass http://nextline-web/;
    }
    location /nextline-api/ {
      proxy_pass http://nextline-backend:8000/;

      # https://www.nginx.com/blog/websocket-nginx/
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection $connection_upgrade;
      proxy_set_header Host $host;
      #proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
  }
}

If you were to run this without the modification, nextline would being expecting to be served at http://example.com/nextline/nextline/ and internal paths to directories like /js/ would be broken.

Thank you. I will have a look carefully.
Before adding the lines that this PR deletes, I tried many Nginx config and public paths combinations. And I thought that it was impossible to make every combination work without those lines. It will actually be nice without those lines.
For quick comparison with my Nginx config, it might work if you remove the slash after http://nextline-web in your config.
location /nextline/ {
      proxy_pass http://nextline-web;
    }

I will try again soon when I can.

For quick comparison with my Nginx config, it might work if you remove the slash after http://nextline-web in your config.
location /nextline/ {
      proxy_pass http://nextline-web;
    }

Ah, yes, this does work. Rereading the nginx docs on proxy_pass, I can see why this works, though my tendency is to avoid mixing having a trailing slash in the location and not having it in the proxy_pass (and vice versa.)
That said, I will note that this works as well:
    location /nextline {
      proxy_pass http://nextline-web;
    }

Just for the record, this patch is not needed. The problem can be solved with proper configuration of nginx. From our discussion on Slack that is either:
    location /nextline/ {
      proxy_pass http://nextline-web/nextline/;
    }

The key here being the proxy_pass address ending is matched to the set PUBLIC_PATH, in this case PUBLIC_PATH=/nextline/.
Or as you pointed out:
location /nextline/ {
    proxy_pass http://nextline-web;
}

The key here being the lack of a trailing slash.
Knowing this now, I'll close this PR.


refactor: Move function overloads to pyi files

Feature or Bugfix

Refactoring

Detail

Move function overloads to pyi files for the following modules: Athena, S3 Read Parquet, S3 Read Text

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: d79ec800239f7ad59e61ca7312112608f5427c5c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: d79ec800239f7ad59e61ca7312112608f5427c5c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 05e31c7e83698b87a54511036ddfa72e066a09f7
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: a183461df1c4d66b96ad05f86d27ec34e32caf88
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: a183461df1c4d66b96ad05f86d27ec34e32caf88
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: ec553f63cfec20f16aeb0bc56ca6858f0568f8a0
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: ec553f63cfec20f16aeb0bc56ca6858f0568f8a0
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 7bfc58c274ba5ccbd418b436b072f17a92a1cff1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 7bfc58c274ba5ccbd418b436b072f17a92a1cff1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: b693b4369e2298aad8d7f9fb838034389f2f858c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: b693b4369e2298aad8d7f9fb838034389f2f858c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 3ad63869107579cecdf0a7bcde1308d9ba133b8a
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 3ad63869107579cecdf0a7bcde1308d9ba133b8a
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: c7d8257b289391e690612b0b27431feb5b224706
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: c7d8257b289391e690612b0b27431feb5b224706
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 9834b54e6aca1a33bbb57652083d4ee69d0241ef
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Add support for android 8 notifications

Added one channel and assigned the sticky notification to it in order support android 8 notifications.

Works great, thank you. Tested in Android 6 and 8.1

#389


XML parse error

I am on Windows 10 using Windows Subsystem for Linux, Python 3.8. I installed evernote-to-sqlite via pipx (in a venv). I tried using enex files from the latest version of Evernote for Windows (10.6.9 which only lets you export 50 notes at a time) and from Legacy Evernote (<IP_ADDRESS>98 which lets you export all your notes at once). The enex file from latest evernote gives this error:
File "/usr/lib/python3.8/xml/etree/ElementTree.py", line 1320, in XML parser.feed(text)
xml.etree.ElementTree.ParseError: XML or text declaration not at start of entity: line 2, column 6

The enex file from Legacy Evernote gives this error:
File "/home/david/.local/pipx/venvs/evernote-to-sqlite/lib/python3.8/site-packages/evernote_to_sqlite/utils.py", line 28, in save_note
updated = note.find("updated").text
AttributeError: 'NoneType' object has no attribute 'text'

I solved this issue by modifying line 31 of utils.py
content = ET.tostring(ET.fromstring(content_xml.strip())).decode("utf-8")

Thanks for the fix!


format sections

[ ] description
[ ] installation instructions
[ ] usage information
[ ] contribution guidelines
[ ] test instructions
[ ] license
[ ] questions

split and incorporated into issues that get user input


Support building into a dependency which fails due importing XCTest

These build settings make the build work with an Xcode project but fails with a Swift package which just will not work the same way.
ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES
ENABLE_TESTING_SEARCH_PATHS = YES
SYSTEM_FRAMEWORK_SEARCH_PATHS = $(CORRESPONDING_DEVICE_PLATFORM_DIR)/Developer/Library/Frameworks $(inherited)

After setting XCTest as a linked framework to fix the build failure it still fails with PreconditionCatching.
linkerSettings: [.linkedFramework("XCTest")]

The build failure was due to how Xcode adds new package dependencies. Hela was being linked by the primary target which is not a test target. Instead the test targets should be linked. A note has been added to the README.md to make developers aware of this problem.


Tap to place parent

I am using the tap to place script when the app started to let the user move a cube around the room for choosing a location to place holograms.
When I move my cube around and place it again it seems like only some of the holograms are move to the location of the cube and some are still in the old location. I cannot find a difference in these game objects.
The cube with the Tap to Place script is inside a game object called "holograms". The place parent on tap is checked and the Parent game object is set to the Holograms object.

You need to check and make sure the friendly anchor name is different for each object.  If they are all the same and you go to move them, they will all snap back to that one anchor.  You can see Issue #567 and follow if I can get an answer on instantiation as well.

I only need one object as anchor.
The object is used to place a group of holograms where the user wants them. But some of the holograms keep the old position.

You will have to change the anchor position per object if you had any previous anchors attached to that object.  Try clearing the anchor store as well.  Ive come across this issue before.

@mattfedocsg  What do u mean by anchor position and anchor store? How do I clear the anchor store? I'm trying to tap to place a bunch of holograms but only some are above to be moved and relocated. Same problem I guess..


Add: CodiMD

CodiMD lets you collaborate in real-time with markdown. Built on HackMD source code, CodiMD lets you host and control your team's content with speed and ease.

Hi @Rashmi-278 , can you add an entry to the top-level readme?

@boz I have updated top-level readme can we please merge this ?


Possible to do a v1.0.1 release with the dict.upsert change?

This would avoid deprecation warnings with stdlib 0.39, and errors in the next stdlib release.
Thanks!

Yeah totally!

This is done!


fix(deploy-tooling): Add change set, add changes to support deploy & undeploy confirmation

Fix for https://github.com/SAP/open-ux-tools/issues/1501
Show deploy and undeploy confirmation prompt, can be disabled by enabling the --yes flag to the command i.e. npm run undeploy -- --yes

additional unit tests

@longieirl what is going on with this one?


Tighter Wagtail Page Editing Theme

Feature Request
I make use of Streams quite a bit in the construction of my pages.  In the page editing screens I find that I am losing a lot of real estate by nesting my blocks.  It would greatly help if Wagtail could:

Expand the edit page to full screen and
Let the nested blocks cut much less real estate per level.

Steps to Reproduce
In my example, I have 4 levels of nesting.  I create a row, then a column, then a tabbed control, then contents per-tab.
By the time I'm writing the content, I am down to about 15% of my total screen real estate.  See the screen grab for an example, that bottom H2 input field is only 350 pixels wide on a 1280 monitor.  On a smaller screen, it gets cramped even faster.  It isn't just the edit fields that are small, the field names often get clipped as well..

Technical details

Wagtail version: 1.10

Thanks for the report @hairypalm! There's currently ongoing work in improving the design of deeply-nested StreamFields, both in the add-on packages wagtailatomicadmin and wagtailclearstream, and tracked by ticket #2325.


Duplicate URLs visited when simultaneously found by 2 or more goroutines.

A URLs is considered to discovered only after it is processed so it possible that multiple goroutines can find duplicates of an URL before it was processed by the crawler.


Describe the storage layer in the technical report

I'm not expecting a review, this is more to show the progress.

I'm not expecting a review, this is more to show the progress.

bors merge

bors merge


Added connect.timeout() middleware

Uses new socket.setTimeout.
Tests included.
Keeps the options and defaults from the ancient connect-timeout middleware.

Just tried this branch with an actual project - routes that use res.render are working fine, but weirdly routes that use static files (via the static express middleware) generate timeouts. Ideas?

Chrome times out with .txt files, Firefox and Safari only time out with binary files like .jpg and .ico.
Perhaps I misunderstand how the socket detects idleness?


Add a ServiceProxy class for doing service invocation

In much the same way that ActorProxy class is used to abstract dapr to allow strongly typed method calls, similar functionality should be possible for remote service invocation using a ServiceProxy.
e.g.
IMyService helloWorldClient = ServiceProxy.Create<IMyService>(appId);

string message = await helloWorldClient.HelloWorldAsync();

This is also consistent with Service Fabric.

Hi @darraghjones thanks for the suggestion.
I'm closing this as out of scope. This would be a really large undertaking, and it seems to me like this problem is already adequately solved by libraries like Refit - or gRPC in general.

Hi @darraghjones thanks for the suggestion.
I'm closing this as out of scope. This would be a really large undertaking, and it seems to me like this problem is already adequately solved by libraries like Refit - or gRPC in general.

fair enough. is there any intention to try and keep parity (and consistency) with service fabric APIs?
this was originally demonstrated as a 'feature' when dapr was originally launched

fair enough. is there any intention to try and keep parity (and consistency) with service fabric APIs?
this was originally demonstrated as a 'feature' when dapr was originally launched


Make it more obvious that marines can build power nodes without commander's needing to put down blueprints

Fixed in balance patch


feat: dev-env scripts

Context
Related to https://github.com/t3-oss/create-t3-turbo/pull/720, attempts to solve the issue with NextAuth's AUTH_URL and Expo.
See relevant comments:

https://github.com/t3-oss/create-t3-turbo/pull/720#issuecomment-2106041325
https://github.com/t3-oss/create-t3-turbo/pull/720#issuecomment-2111193163
https://github.com/t3-oss/create-t3-turbo/pull/720#issuecomment-2119352026
https://github.com/t3-oss/create-t3-turbo/pull/720#issuecomment-2119368962
https://github.com/t3-oss/create-t3-turbo/pull/720#issuecomment-2120204922
https://github.com/t3-oss/create-t3-turbo/pull/720#issuecomment-2120709037#1034

Highlights

general:

add a system to generate/infer certain env vars for running the apps in development mode
the generation/inference is tied in turbo, so it will run before any of the projects (so they are visible to any app)

nextjs

launches the app with a custom hostname, so it's available though LAN
has a script that writes the env vars (infered from api and auth packages)

expo

reads the API URL from an env var (which in development is infered from hostname and port of the nextjs app)

Benefits

should need 0 initial config related to AUTH_URL (which was the initial objective)
expo's API URL is better constructed (for example, will respect the port)
nextjs app is accessible through LAN (useful to access from mobile phone?)
everything is still configurable from .env in workspace root
expo API URL on production will be read from env var
minimal runtime code has been modified

Drawbacks

nextjs app must be accessed from the network IP instead of localhost (it's shown when the app has started)
any change in network devices will affect in the nextjs accessible address. The worst part of this is that oauth redirects need to be whitelisted in certain providers (ex: Discord), so this is a bit annoying as new ones need to be added
inference logic may fail depending on the device/system (though note that .env has full control if env vars are specified there)
the approach may be incorrect/too complex - I'm biased on this so I'll let others judge!

Screen-capture
https://github.com/t3-oss/create-t3-turbo/assets/16188653/be7b1b8b-fa25-4b9a-a351-774239d907f7
https://github.com/t3-oss/create-t3-turbo/assets/16188653/008d97f8-a0b4-4543-8c8e-621a760776f4
Screenshots
Run project from workspace root

Resulting `.env` files

Running apps

TODO

[ ] Document how to manage env vars when doing a production build of the Expo app

Closed in favor of #1054.


Problem with Checkbox

When using dmc checkbox, there are two checks as can be seen in the image below:

I was able to get rid of the green check by adding the CSS below however, that makes all dcc check marks transparent. Is there another way to solve this? Since I use select option in dash tables, I cannot make all checks transparent.
.ddk-container.ddk-container input[type=checkbox]:checked:before {
    color: transparent;
  }

This seems to be caused by conflicting css from ddk.


Respond to media key and show in now playing widget

Hi,
it would be nice to have control of the app with the media key of macOS and if the play status could show in the now playing widget.
Thanks

Hmm.
Yeap, I could add control of the app with media keys.
Now playing - you mean now playing song or program?

I was talking about the macOS widget in the Notification Center (https://support.apple.com/en-ca/guide/mac-help/mchl2fb1258f/mac) that you can swipe over:

Ohh, my mistake)
Yeap, I think it could be added too. But will be better to have a separate issue for the widget.

Ok. Will do.


Balance Allocation for Multiple Cards On Device KVStore

我用vggnet 11layer 训练，在总的batchsize是36，3个780gpu，conv workspace 设置为 256, cuda-7.0, 但不用cudnn（觉得可以规避一些内存分配的不确定性）， 发现占用gpu：2795m，2661m，2383m，他们100多m的递减差别是怎么产生的？希望能差别小一点，这样显存的利用率高些，毕竟显卡相同，显存利用取决于占用最大的gpu了，batchsize太小我的数据有时不收敛:(

This could due to the memory allocation policy used for the distributed KVStore under mode kvstore_type =  'device'.  I guess this should not be the case for kvstore_type=local
When we do device type kvstore, what is needed is we allocate the reduction temporal memory on each of the device. We do it in a random assignment way.here https://github.com/dmlc/mxnet/blob/master/src/kvstore/kvstore_device.h#L36 to balance the temp weight memory on each device.
If the weight is not uniformly distributed (e.g there is a weight that is particularly big chunk of weight), then this could cause the imbalance.

是的，我是使用kvstore=device，可不可以添加一个比较确定的分配策略？例如从weight从大到小贪心，总是放到当前weight最新的设备，我觉得不少人会喜欢把显存用得满满的，如果随机的话，就有偶尔爆显存的顾虑，即使是随机在显存分配上最好也有个默认的seed，这样不用担心显存每次跑起来不一样：）

This seems to be a good idea. The allocation strategy code is here https://github.com/dmlc/mxnet/blob/master/src/kvstore/kvstore_device.h#L36
Maybe you can consider hack it a bit and contribute back :) ?

yes，I will

这几天代码的跟显存分配的主要改什么？我把代码都checkout了，然后更新了最新版本，然后之前配的网络都跑不起来了，out of memory，查看一下，显存占用多了不少。。。

another possible way is, do random assignment if the size < bigarray_bound_, otherwise, evenly split the array into num_dev parts, and assign one part to each device

This dep checking of slice might block other slices, as we do not
distinguish between non overlapping slices. So the current way is easier
On Sat, Oct 10, 2015 at 1:30 PM Mu Li<EMAIL_ADDRESS>wrote:

another possible way is, do random assignment if the size <
bigarray_bound_, otherwise, evenly split the array into num_dev parts, and
assign one part to each device
—
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/issues/252#issuecomment-147123007.

This issue is fixed by contribution #256  Thanks to @junranhe


Move flutter drive to use 8183 to not conflict with diagnostic server

When @jason-simmons  added the diagnostic server on Android this
happened to conflict with flutter drive's usage of 8182.
We really should fix both of these port users to be dynamic
but this fixes https://github.com/flutter/flutter/issues/3291
for now.
@yjbanov

LGTM

The port issue should be fixed as part of https://github.com/flutter/flutter/issues/3173 as multiple devices also run in to the port conflict issue.


tcg/voyager removed when running php artisan hook:install voyager-themes

Description:
this is my first time installing hook using 'php artisan hook:install voyager-themes' command..
then suddenly when i try to browse my admin panel, class voyager was not found, it turns out my tcg/voyager dependencies were removed when i run php artisan hook:install voyager-themes, is anyone know what the reason this issue happen?

I can't think of any reason why this would happen...


Suggestion: Show Filename or Title

It would be awesome to show the filename of uploaded screens for better management. Even better: Allow custom screen titles.
Keep up the great work! Presentator rocks!

@Wiredframe There is already an option to define custom screen title from the screen settings popup (click on the gear icon located in the top screen bar):

Awesome, thanks for the hint. It would be great if the Title would be shown in the screens overview, too. 👍

Great to hear! Thanks! I'm trying to spread the word about this awesome project on Twitter.

Merged in master. Will be included in v1.4.0 release.

Thanks! Very helpful!


Update nix.yml to fix Mac runner cache

nix builds will behave correctly like this
PR checklist:

[ ] Test coverage for the proposed changes
[ ] PR description contains example output from repl interaction or a snippet from unit test output
[ ] Documentation has been updated if new natives or FV properties have been added. To generate new documentation, issue cabal run tests. If they pass locally, docs are generated.
[ ] Any changes that could be relevant to users have been recorded in the changelog
[ ] In case of  changes to the Pact trace output (pact -t), make sure pact-lsp is in sync.

Additionally, please justify why you should or should not do the following:

[ ] Confirm replay/back compat
[ ] Benchmark regressions
[ ] (For Kadena engineers) Run integration-tests against a Chainweb built with this version of Pact

duplicate


Text will go beyond margin if it is too long

Hi, I'm new to latex, the text will go beyond margin if it is too long, and won't line feed automatically. But I don't know how to fix this.

Check out this help page from Overleaf here.

Check out this help page from Overleaf here.

Thank you for your reply!   I am trying to do the same but using and referred to the link above. But neither of \\, \newline or \hfill \break helped.

@iCHAIT Sorry for the late response, guess you already solve that. My understanding is that you can't line feed in the column of tabular (tell me if you find other solution), but the rest part works well.

Nested tabular allows multiline entries: https://tex.stackexchange.com/a/40562/226501


Backport for BeOS

Does anybody know of a fork that will work in BeOS? I need to backport this, it's very important.

Um... it's already done. Can't you see it?


feat: use ipv4 by default to fix CI flow

Description
For now all CI flows failed as OSD upgrade Node version to v18, which use ipv6 by default. Add --server.host="<IP_ADDRESS>" to enforce CI to setup OSD server in ipv4.
Issues Resolved
#902
Check List

[x] Commits are signed per the DCO using --signoff

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

Dummy run test: https://github.com/opensearch-project/opensearch-dashboards-functional-test/actions/runs/6967378827/job/18959183917?pr=960

@SuZhou-Joe Do we need to backport 2.x branch?

@SuZhou-Joe Do we need to backport 2.x branch?

We should I suppose.

Follow issue for flaky test: #961

In order to make vanilla tests run, we had to downgrade chrome version to v115, or the cypress will hang because of memory limit. I found that we use a customized image in OSD to run cypress test. @kavilla , do you have any context here why we use a customized image instead of the default github runner-image?


Updated Changelog to add release dates

Added Release dates in the changelog for help in #2330

Makes sense.

Merged in 25f7d7c4cab9832f43a70660e6f704bb9ebdc911


Do single writes cover everything?

I was looking at the lux front end on their website and it looks to me like that several registers wont be covered by single writes.
Is it worthwhile to consider taking a look at readMultiParams/ writeParamvalue and sending the entire parameter list like their website does? It looks to me like it reads them out from the inverter that way as it just loads the payload then reads each property in remoteRead.js
BTW you can also easily write any of the parameters via the regular website aslong as you know the response property name... which is listed in the payload of any settings read.

Do you mean the registers that contain times etc? There's an inverter command WriteMulti for that, but it's not currently supported in lxp-bridge.
I don't think it would be a huge problem to add support though, the main issue is how to expose it externally. Maybe something like the usual cmd/$datalog/set/hold/X but then with a payload of comma separated values?
So if you sent this: (don't try this yet, it won't work)
mosquitto_pub -t lxp/cmd/all/set/hold/68 -m '0,0'

Then lxp-bridge coudl set registers 68 and 69 both to zero (those are AC_CHARGE_START_HOUR / AC_CHARGE_START_MINUTE apparently).

No I am use exclusively https://server.luxpowertek.com/WManage/web/maintain/remoteSet
If you inspect this page they have left several js file that contain everything needed to read / write all params.
//Read All Parameter...
				if(currentDeviceType != 5) {		//Not LSP 100K
					showReadParamsResult(response);

					if(startRegister == 0) {
						setTimeout("readMultiParams(40, 40)", 1000);
					} else if(startRegister == 40) {
						setTimeout("readMultiParams(80, 40)", 1000);
					} else if(startRegister == 80) {
						setTimeout("readMultiParams(120, 40)", 1000);
					} else if(startRegister == 120) {
						setTimeout("readMultiParams(160, 40)", 1000);
					} if(currentDeviceType == 6 && startRegister == 160) {
						setTimeout("readMultiParams(200, 40)", 1000);
					} else {
						if(currentDeviceType == 3 && startRegister == 160 && allowCtrlHold601) {			//Off-Grid
							setTimeout("readMultiParams(600, 40)", 1000);
						} else {
							currentReadMultiParamsStartRegister = -1;
							$('#readAllParamButton').button('reset');

and
function showLspReadParamsResult(response) {
	if(response.hasOwnProperty('HOLD_MODEL')) {
		$('input[holdParam="HOLD_MODEL"]').val(response.HOLD_MODEL);
	}
	if(response.hasOwnProperty('HOLD_SERIAL_NUM')) {
		$('input[holdParam="HOLD_SERIAL_NUM"]').val(response.HOLD_SERIAL_NUM);
	}
	if(response.hasOwnProperty('HOLD_TIME')) {
		$('input[holdParam="HOLD_TIME"]').val(response.HOLD_TIME);
	}
	if(response.hasOwnProperty('HOLD_COM_ADDR')) {
		$('input[holdParam="HOLD_COM_ADDR"]').val(response.HOLD_COM_ADDR);
	}
	if(response.hasOwnProperty('HOLD_LANGUAGE')) {
		$('select[holdParam="HOLD_LANGUAGE"]').val(response.HOLD_LANGUAGE);

etc.
Basically when you press that "read" button you get 5 readMultiParams triggered that spit out a payload of every parameter from register 0 to 160 in blocks of 40.
{"HOLD_GRID_VOLT_CONN_HIGH":"262.2","HOLD_GRID_VOLT_LIMIT2_LOW_TIME":"26","HOLD_MODEL_lithiumType":2,"HOLD_MODEL_powerRating":5,"FUNC_GRID_ON_POWER_SS_EN":true,"HOLD_RECONNECT_TIME":"30","FUNC_LSP_ISO_EN":false,"valueFrame":"pgoBADEzMzIwMDUwODdhQUFBAhocAQAAFgsDFCMwAQABAAAAAAAAAAQA1fLoAx4AHgDRBz4KjhIeFNEHPgp+ADMAMAexChoAGgAwB7EKGgA=","FUNC_LSP_LCD_REMOTE_DIS_CHG_EN":true,"FUNC_LVRT_EN":false,"FUNC_LSP_FAN_CHECK_EN":true,"FUNC_NEUTRAL_DETECT_EN":false,"FUNC_LSP_BAT_ACTIVATION_EN":true,"FUNC_FEED_IN_GRID_EN":true,"HOLD_LANGUAGE":"1","HOLD_GRID_VOLT_LIMIT1_LOW_TIME":"126","HOLD_MODEL_usVersion":0,"HOLD_MODEL_meterType":0,"HOLD_GRID_FREQ_CONN_HIGH":"51.5","HOLD_GRID_VOLT_LIMIT1_HIGH_TIME":"51","success":true,"HOLD_MODEL_meterBrand":0,"HOLD_MODEL_measurement":1,"FUNC_DCI_EN":true,"HOLD_MODEL_rule":6,"HOLD_GRID_FREQ_CONN_LOW":"47.5","FUNC_AC_CHARGE":true,"HOLD_COM_ADDR":"1","FUNC_OVF_LOAD_DERATE_EN":false,"HOLD_FW_CODE":"aAAA-1A1C","HOLD_GRID_VOLT_LIMIT2_HIGH":"273.7","FUNC_ANTI_ISLAND_EN":true,"FUNC_FORCED_CHG_EN":false,"FUNC_LSP_BYPASS_MODE_EN":false,"HOLD_MODEL":"0x10AA6","HOLD_MODEL_leadAcidType":0,"HOLD_TIME":"2022-11-03 20:35:48","FUNC_DRMS_EN":true,"HOLD_MODEL_ruleMask":0,"HOLD_GRID_VOLT_CONN_LOW":"200.1","HOLD_CONNECT_TIME":"30","HOLD_GRID_VOLT_LIMIT3_HIGH":"273.7","HOLD_GRID_VOLT_LIMIT3_LOW_TIME":"26","HOLD_START_PV_VOLT":"100","HOLD_PV_INPUT_MODE":"4","FUNC_GFCI_EN":true,"FUNC_FORCED_DISCHG_EN":false,"HOLD_GRID_VOLT_LIMIT2_HIGH_TIME":"26","FUNC_SW_SEAMLESSLY_EN":false,"HOLD_MODEL_batteryType":2,"HOLD_GRID_VOLT_LIMIT1_HIGH":"262.2","FUNC_EPS_EN":true,"HOLD_GRID_VOLT_LIMIT3_LOW":"184","HOLD_GRID_VOLT_LIMIT1_LOW":"200.1","HOLD_SERIAL_NUM":"1332005087","INPUT_BATTERY_VOLTAGE":"49.1","FUNC_ISO_EN":true,"FUNC_LSP_AC_CHARGE":false,

And then if you simply HTML edit in a setting with the parameter name correct, you can write that to the inverter as it sends EVERY param no matter which set button you press.

For instance a div class with functionparam="FUNC_BUZZER_EN" would then allow you to control the buzzer. Despite this enable not being expose to regular user.

Oh nice, I'll have to look at their JS more closely, might learn a few things :)
But I've lost track of what you want lxp-bridge to do, just be able to set things like the buzzer? It can already write to any single register, just need to know which one the buzzer is for example.

No its not really a request more of a heads up i've seen the textual description of every register including how all the different model numbers work etc encase it was useful.

👍 definitely. JS isn't my strong point but its easy enough to read and as I say, might learn a few things :)
I've documented which registers I know in https://github.com/celsworth/lxp-bridge/blob/master/doc/LXP_REGISTERS.txt (though they have HOLD_ all prepended to them, but you should see some familiar looking ones). Will see if I can find any more.
Thanks!

It might be that the functionparams registers are changed by the time you see them.; I haven't yet looked at the correlation.


Bugsnag request failed to complete

I am making a release abb build of react-native.
The first time I built the abb but now can't build it.
give this error

java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Bugsnag request failed to complete

Hi @Salmankhan033.
Could you give me a little more detail about the steps taken prior to this error happening.
What commands are you using to build this?
Also if you could include more of your log from around the time of the error it would be helpful.
Thanks

Thanks for the quick response,
I fixed the issue it's from my side.
Thanks

when  free trial ended the it give issues


How to create a simple button that changes the layer between map and satellite?

Hello the days I'm looking for a solution to create a button to toggle between map and satellite layers all I want is a style toggle button that switches between the map layers and satelite I found an example as http://tombatossals.github.io/angular-leaflet-directive/examples/0000-viewer.html#/layers/dynamic-addition-example but it deletes the layer map and all I want is just to change as it is made by the leaflet-control-layer selector someone could help create that switch style?

Duplicate of Leaflet/Leaflet#4195

I could settle with the function found here https://github.com/angular-ui/ui-leaflet/issues/22 was all he needed to create my custom layer switch
$ Scope.changeBaseLayer = function (key) {
         leafletData.getMap (). Then (function (map) {
             leafletData.getLayers (). Then (function (layers) {
                 _.each (layers.baselayers, function (layer) {
                     map.removeLayer (layer);
                 });
                 map.addLayer (layers.baselayers [key]);
             });
         });
     };

has possibility to do it without andgular?

hello @neomacedo yes you can do with simple javascript, creates a variable to control the corresponding button action display state through jquery style and use the onclick to define the action to change the map.


[Error in EMLI syntax] Any string can be used as a Multi-line string.

Describe the syntax error
Any string, be it "this", 'this', or `this`, can be used as a Multi-line string.
Expected behaviour
I expected that only `these types of strings` would be able to compile as a Multi-line String.
EMLI Code
p {
  "
  This shouldn't compile
  "
}

p {
  '
  Neither should this
  '
}

p {
  `
  But this should
  `
}

HTML Code
<!DOCTYPE html>
  <meta charset="UTF-8">
  <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Document</title>

  This shouldn't compile

  Neither should this

  But this should

Screenshots

Additional context
This is a known issue, and will be fixed in a later update. Do not use any type of string other than `this type` for Multi-line Strings, or they will break in the future.

Fixed!


fixed accessing of message id

$message->_id throws an error. $message['_id'] works.

Fixed with v2.0.4


Implement Delay or Go page

Potentially use the MC page as a reference. Limit to 2 options (?).

Delay or go Ahead page is set up, the axios calls are not yet present. Need to consult with someone as to what calls to the database are required to make them work.


🐛 | Several python modules missing after fresh install

Bug
What I did
I installed the raspberry pi with current RPi OS bullseye image and ran the installer script.
What happened
Several python modules were missing, I needed to install them manually:

ModuleNotFoundError: No module named 'ruamel'
sudo apt install python3-ruamel.yaml

ModuleNotFoundError: No module named 'pulsectl'
sudo pip install pulsectl

from ruamel.yaml import YAML   ModuleNotFoundError: No module named 'ruamel'
sudo apt install python3-evdev

ModuleNotFoundError: No module named 'eyed3'
sudo apt install python3-eyed3

ModuleNotFoundError: No module named 'mpd'
sudo apt install python3-mpd

ModuleNotFoundError: No module named 'alsaaudio'
sudo apt install python3-alsaaudio

zmq.error.ZMQError: Protocol not supported

I expected this to happen
The installation should result in a working jukebox.
Further information that might help
Syslog after installing the missing modules: syslog.log
Software
Base image and version

Raspberry Pi OS stable lite (bullseye, 64bit)

Branch / Release

Git state: 80710235 [2022-02-10] Release 3.2.0  (HEAD, tag: V3.2.0, origin/future3/main) [V3.2.0-dirty]

Installscript
I followed the Installing Phoniebox future3 documentation:
cd; bash <(wget -qO- https://raw.githubusercontent.com/MiczFlor/RPi-Jukebox-RFID/future3/develop/installation/install-jukebox.sh)

Hardware

Raspberry Pi 3 Model B Plus Rev 1.3
Suptronics x400 Soundcard
MFRC522 RFID Reader

Related issues from the same installation: #1839, #1838

As mentioned by @ChisSoc most likely because of 64bit OS.

3.4 was just released, https://github.com/MiczFlor/RPi-Jukebox-RFID/releases/tag/v3.4.0
Could you check, if your problem was fixed?

I can confirm this bug is still occurring with 3.4.0, tested on a RPI 2

I can confirm this bug is still occurring with 3.4.0, tested on a RPI 2 (armv7l)

Hi,
whats is your OS version?
When does error this occure? When the service is running or on manually calling scripts?
If your run the python scripts manually you need to activate the venv first (https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/future3/develop/documentation/developers/pyhton.md)

Raspberry Pi Os Legacy Version 32-Bit
And it occurred while executing the scripts manually (without venv).
Therefore I think you might be right that it was just missing the venv, and is not related to the mentioned bug
Thank you


3D view after upgrade from 7.x to 8.x zoom levels increase

3D view after upgrade from 7.x to 8.x zoom levels increase

Duplicate of #4273


New attribute on users for saving phone number

Description
I would like to have an attribute for users where I can store phone numbers such that I can use webhooks to send notifications to that phone number using external services (e.g. whatsapp, sms, etc.)
Desired Behavior
New attribute for saving phone numbers & ability to use that attribute in creating webhook notifications
Additional Context
No response
Code of Conduct

[X] I agree to follow Jellyseerr's Code of Conduct

I would also like the ability to have a notification service that uses SMS service no notify users about updates/information of their requests.
This was mentioned here in Overseerr.
Unfortunately, this issue was marked as stale as alternative options such as email to text or HTML5 notifications were suggested.
I would like to see the addition of Twilio or other SMS providers integrated and in-turn have a administrator only option to add phone numbers for notifications to the user.

I would also benefit greatly from this. Allowing users to add a phone number or allowing me to manually add them would be great.


BannerView iOS: Fatal error: No bridge module

Hello, when i open screen on which the BannerView widget, my application exits with follow error:
CASIntegrationHelper [AudienceNetwork SDK ] AudienceNetwork SDK The `setAdvertiserTrackingEnabled` flag is not implemented. Please read the `Additional Meta AudienceNetwork steps` page on our wiki.
CASIntegrationHelper [Kidoz Adapter ] Kidoz Adapter Not integrated
CASIntegrationHelper [SuperAwesome Adapter ] SuperAwesome Adapter Not integrated
CASIntegrationHelper [StartIO Adapter ] StartIO Adapter Not integrated
CASIntegrationHelper [CrossPromo Adapter ] CrossPromo Adapter Not integrated
CASIntegrationHelper [HyprMX Adapter ] HyprMX Adapter Not integrated
CASIntegrationHelper [Smaato Adapter ] Smaato Adapter Not integrated
CASIntegrationHelper [Madex Adapter ] Madex Adapter Not integrated
CASIntegrationHelper [ App Tracking Transparency ]  App Tracking Transparency Denied
-[AMADatabaseIntegrityProcessor checkIntegrityIssuesForDatabase:report:]:50 DB integrity check found issues: (
)
-[AMADatabaseIntegrityProcessor checkIntegrityIssuesForDatabase:report:]:50 DB integrity check found issues: (
)
-[AMADatabaseIntegrityProcessor checkIntegrityIssuesForDatabase:report:]:50 DB integrity check found issues: (
)
+[AMACrashLoader purgeRawCrashReport:]:319 FAILED TO REMOVE REPORT:<PHONE_NUMBER>7054336
clever_ads_solutions/BannerView.swift:39: Fatal error: No bridge module!
Lost connection to device.

Exited.

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79 darwin-arm64, locale en-TR)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.91.0)
[✓] Network resources

• No issues found!

banner widget
       BannerView(
          isAutoloadEnabled: true,
          refreshInterval: 20,
          listener: BannerListener(),
        )

pubspec
clever_ads_solutions: ^0.3.1
podfile
source 'https://cdn.cocoapods.org/'
source 'https://github.com/cleveradssolutions/CAS-Specs.git'

platform :ios, '13.0'
use_frameworks! :linkage => :static
$casVersion = '~> 3.7.3'

ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

target 'Runner' do
  use_frameworks! :linkage => :static
  use_modular_headers!
  pod 'CleverAdsSolutions-SDK/Optimal', $casVersion

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
  target 'RunnerTests' do
    inherit! :search_paths
  end
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

Hi @alex-relov, thank you for raising the issue.
In version 0.5.0, we implemented some improvements to address this issue. We remain committed to further enhancing our plugin in the future.

Banner implementation has been reworked in version 0.6.0. The issue no longer occurs.


[Recorder] (low priority) Cross check the replaceableVariables being set in the RecorderEnvSetup for the tests in SDKs

Scenario
We have the account SAS env variable for data-tables, which was being replaced with mockSAS string instead of a fake value that would look like a SAS string.
data-tables SDK parses the URL and removes the SAS from the URL(while making requests) based on the query params present in the SAS. In such a case, replacement with mockSAS wouldn't be enough for playback since it doesn't have the expected key-value pairs leading the playback to fail.
To avoid such problems, make sure all the services are properly mocking out the variables by providing fake values that would structurally look like an expected value.

Pipelines will now handle this with the credscan tool running on the repo


Menu options have changed in the new admin center

Need to update screen shots also.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@JoeDavies-MSFT - PR has been copy edited and is ready for final review.
Thank you.
cc: @kenwith


feat(auth): grant request update api

Changes proposed in this pull request

Implements grant request update API via HTTP PATCH

Context

fixes #406
Checklist

[X] Related issues linked using fixes #number
[ ] Tests added/updated
[ ] Documentation added
[ ] Make sure that all checks pass

Closing since it is now no longer in spec for our implementation.


feat(ansible-verbosity): set the offset on the basis of verbosity level

Signed-off-by: shubhamchaudhary<EMAIL_ADDRESS>
What this PR does / why we need it:

set the offset on the basis of verbosity level to get the failure step

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Checklist

[ ] Does this PR have a corresponding GitHub issue?
[ ] Have you included relevant README for the chaoslib/experiment with details?
[ ] Have you added debug messages where necessary?
[ ] Have you added task comments where necessary?
[ ] Have you tested the changes for possible failure conditions?
[ ] Have you provided the positive & negative test logs for the litmusbook execution?
[ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
[ ] Have you used non-shell/command modules for Kubernetes tasks?
[ ] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
[ ] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
[ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
[ ] Do the artifacts follow the appropriate directory structure?
[ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
[ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
[ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
[ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
[ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
[ ] Can you suggest the minimal resource requirements for the litmusbook execution?
[ ] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
[ ] Has the litmusbooks been linted?

Special notes for your reviewer:

Logs for all possible verbosities are given below
verbosity-0.txt
verbosity-1.txt
verbosity-2.txt
verbosity-3.txt


Migrate from JCenter

JCenter is End Of Life and service availability has been flaky recently.
This project's use of JCenter in the Android gradle build files is causing our builds to fail. Can we remove it and use mavenCentral instead please.

#24
PR for change

Thank you so much @SoftWyer ! It's been merged in v1.3.0. Closing this one now.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.28 to before v5.4.126",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=05736a427f7e16be948ccbf39782bd3a6ae16b14",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7e4e824b109f1d41ccf223fbb0565d877d6223a2"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "05736a427f7e16be948ccbf39782bd3a6ae16b14",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "7e4e824b109f1d41ccf223fbb0565d877d6223a2",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "ftrace: Do not blindly read the ip address in ftrace_bug()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.126 by commit 7e4e824b109f1d41ccf223fbb0565d877d6223a2, it was introduced in version v2.6.28 by commit 05736a427f7e16be948ccbf39782bd3a6ae16b14. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000895


Create filter component for mentor list

Create filter component for mentorlist.

Create filter option for country, technology, and it should be drop down .
Filters are left side and mentorlist should be in right side.
Should return proper results based on user selections.

Hello, can i have this issue ?

Sure @AndreyLop


Integrated logrus in #67


is the ctc implementation gpu runnable?

@rakeshvar  I was wondering if this ctc implementation is gpu runnable.  Do you know if there are any such implementations in Theano/Keras. Except for warp_ctc in Torch I could not find any such implementations which run on GPUUs

Theano's scan function, which is the workhorse for RNNs implemented on it, runs very slow on GPU. See this issue. So if you are keen on GPUs with RNNs, may be you are better off trying TensorFlow, I am not aware of any CTC implementations there. Or try warp_ctc. But that is written in C++ and might be hard to tailor to your needs.


Release 0.6.10

Updates changelog and version references for release 0.6.10

It looks like this was just yanked with no compatible version available, which causes some builds to fail. What's going on? Will there be a 0.6.11 shortly?

the last version accidentally introduced a breakage: https://github.com/eyre-rs/eyre/pull/95
Tho I'm honestly surprised that yanking that version causes builds to fail. I would have expected it to fall back to 0.6.9, can you link to an example of a broken build so I can understand how yanking it still causes issues? We hadn't realized there was an urgency to get the rerelease back out.

Everything that declares a dependency on eyre 0.6.10 will fail. There are 68 results on GitHub: https://github.com/search?q=%2Feyre+%3D+"0.6.10"%2F&type=code. It will not fall back to 0.6.9.
Unfortunately this is widespread as projects use bots to bump the dependency numbers immediately after releases are made available, even if the projects would otherwise build perfectly fine against the older version. I have not seen any of those bots monitor and correct for yanked crates.

https://github.com/alsuren/mijia-homie/pull/435
https://github.com/arxanas/git-branchless/pull/1149
https://github.com/aschey/vercel-tokei/pull/53
https://github.com/auguwu/sentry-eyre/pull/16
https://github.com/bluez-rs/bluez-async/pull/204
https://github.com/charted-dev/charted/pull/1326
https://github.com/charted-dev/emails/pull/215
https://github.com/csunibo/course-description-merged/pull/24
https://github.com/evenfurther/aoc/pull/55
https://github.com/gifnksm/git-http-server/pull/239
https://github.com/johnallen3d/conditions/pull/154
https://github.com/matter-labs/zksync-withdrawal-finalizer/pull/332
https://github.com/MolotovCherry/virtual-display-rs/pull/51
https://github.com/Noelware/hazel/pull/385
https://github.com/Noelware/noeldoc/pull/108
https://github.com/qwandor/dancelist/pull/299
https://github.com/qwandor/octopower/pull/191
https://github.com/rgreinho/labelr-rs/pull/87
https://github.com/talzion12/http-cache/pull/154
https://github.com/Zilliqa/zq2/pull/610

Example failure: https://github.com/evenfurther/aoc/actions/runs/7189388139/job/19580870459
error: failed to select a version for the requirement `eyre = "^0.6.10"`
candidate versions found which didn't match: 0.6.9, 0.6.8, 0.6.7, ...
location searched: crates.io index
required by package `aoc v0.1.0 (/home/runner/work/aoc/aoc/aoc)`
if you are looking for the prerelease package it needs to be specified explicitly
    eyre = { version = "0.6.1-rc.1" }
perhaps a crate was updated and forgotten to be re-vendored?

Unfortunately this is widespread as projects use bots to bump the dependency numbers immediately after releases are made available, even if the projects would otherwise build perfectly fine against the older version. I have not seen any of those bots monitor and correct for yanked crates.

unfortunate indeed, and good to know, thank you. I'll go ahead and expedite getting that re-release out asap.

should be good now: https://crates.io/crates/eyre/versions


Fix for TypeError in self-coordinator

Fix for error:
  File "/root/venv-redis/lib/python3.8/site-packages/redis_benchmarks_specification/__self_contained_coordinator__/self_contained_coordinator.py", line 560, in process_self_contained_coordinator_stream
    execute_init_commands(
  File "/root/venv-redis/lib/python3.8/site-packages/redisbench_admin/run/common.py", line 426, in execute_init_commands
    cmds = k["init_commands"]
TypeError: string indices must be integers

How to reproduce:
Run on testing host:
$ redis-benchmarks-spec-sc-coordinator --platform-name intel64-ubuntu20.04-biredis --event_stream_host benchmarks.redislabs.com --event_stream_port <redacted> --event_stream_pass <redacted> --event_stream_user default --datasink_push_results_redistimeseries --datasink_redistimeseries_host benchmarks.redislabs.com --datasink_redistimeseries_port 12011 --datasink_redistimeseries_pass <redacted> --logname /var/opt/test2.log --redis_proc_start_port 6379 --cpuset_start_pos 0 --docker-air-gap --consumer-id 1

In parallell run testing's triggering:
redis-benchmarks-spec-cli --use-branch --from-date 2023-03-22 --redis_port 12010 --redis_host benchmarks.redislabs.com --redis_pass ***

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.01 :tada:

Comparison is base (a4fa679) 56.74% compared to head (dd782cc) 56.76%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #224      +/-   ##
==========================================
+ Coverage   56.74%   56.76%   +0.01%
==========================================
  Files          24       24
  Lines        2224     2225       +1
==========================================
+ Hits         1262     1263       +1
  Misses        962      962

Impacted Files
Coverage Δ

...tained_coordinator__/self_contained_coordinator.py
58.35% <ø> (ø)

...edis_benchmarks_specification/__common__/runner.py
84.70% <100.00%> (+0.18%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Hi @filipecosta90 , please take a look


Promote to v1.0.0 if no API changes by Mar 1st, 2024

Reasons to do so:

Current API has been stable for a while
Consistent behaviour is defined reasonably strictly, and seems unlikely to change for a while
As per pre-release guidelines of Cargo, It is recommended to not use pre-release dependencies in a library if your library is not also a pre-release, so this should make for easier decision to include in your manifest.

Specific changes when releasing v1.0.0:

Specify rust-version in Cargo.toml as a best practice.
Remove clippy.toml as rust-version will do the same job

Move this out to Mar 1st, given the recent changes.

Ping! :) It's now the middle of April!

Yeah, I've been sitting on it for too long. Will do it this weekend.

v1.0.0 is now out.

Awesome, thank you! c:


Add Azure Container Instance as Execution Mode

Description
This PR adds support for Azure Container Instance as an Execution Mode. In this mode, a container is run on Azure to execute the dbt commands.
Related Issue(s)
This closes #635
Checklist

[x] I have made corresponding changes to the documentation (if required)
[x] I have added tests that prove my fix is effective or that my feature works

Note: I haven't added the step-by-step documentation yet. This is deliberate, as it'd be great to first get feedback on the implementation so I can make sure to align implementation with docs.

Thanks for addressing all the comments! This looks great to me.
I'd like to get another person from the team to review for adding in a new execution mode. Feel free to add in the step-by-step instructions in docs/getting_started/azure-container-instance.rst in the meantime since the implementation looks 👍.

@jbandoro  I've now added a step-by-step-guide. It includes a reference to an example I've put together in the cosmos-example repo. I haven't opened the PR for it yet, because I first fixed the existing examples in there for which a PR is now open here. Once that one is merged, I can open the one with the example DAG for Azure Container Instance.

@tatiana I've reworked the code to include @jbandoro change (much cleaner indeed, nice one!). Would be great if you had time to take another look!

@jbandoro @tatiana In terms of documentation for this, I've now opened another PR on the cosmos-example repo here: https://github.com/astronomer/cosmos-example/pull/6/files. It's a bit of a chicken-egg problem, as that example needs this PR to be merged first, but this PR has a reference to the example in the docs 😅 . Hope this makes sense and is ok!

@jbandoro @tatiana I see you have been merging main with this branch a few times (perfectly fine of course). Anything you would like me to do at this point?

@danielvdende we're trying to get an alpha release of v1.4 out soon, and I was hoping to get this work merged, but the unit tests are failing after merging in the latest commits from main. I checked out this branch and can't reproduce the failing unit tests locally. When I find a solution I'll open up a PR in your fork so that we can we can merge it after all the tests pass, apologies that this is taking some time.

Great @jbandoro! I just merged the PR, and see pipelines running here again now too.


style(http-proxy): fix margin for responsive design

Description
Fixes the http-proxy settings styling for mobile design when active.
Screenshot (if UI-related)
Before:

After:

To-Dos

[x] Successful build pnpm build
[x] Translation keys pnpm i18n:extract
[x] Database migration (if required)

Issues Fixed or Closed

Fixes #XXXX

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

v2.2.0
GitHub release

Your semantic-release bot :package::rocket:


/logs route for displaying application logs implementation.

It looks good now but the app is not building.

You are missing a “using” statement for the extension method

I forgot to push the changes, corrected it now. Thank you @NdubuisiJr.


support multiple versions of database

used model here:
https://github.com/skills/reusable-workflows

This still WIP and valid?

This change got merged separately into main through #90


"unexpected token SPACE" error when fetching first IMAP message

I get an error when trying to use imap-backup on Ubuntu 20.04 to backup e-mails from the Xeams Imap-Server (Imap-Server for QNAP-NASes).
CLI:
$ ~/.imap-backup$ imap-backup
D, [2021-10-05T21:48:07.333383 #11680] DEBUG -- : Running backup of account<EMAIL_ADDRESS>D, [2021-10-05T21:48:07.333430 #11680] DEBUG -- : Creating IMAP instance: <IP_ADDRESS>, options: {:port=>143, :ssl=>false}
D, [2021-10-05T21:48:07.337848 #11680] DEBUG -- : Logging in<EMAIL_ADDRESS>D, [2021-10-05T21:48:07.340273 #11680] DEBUG -- : Login complete
D, [2021-10-05T21:48:07.500932 #11680] DEBUG -- : [Inbox] running backup
D, [2021-10-05T21:48:07.645865 #11680] DEBUG -- : [Inbox] 2766 new messages
Traceback (most recent call last):
	7: from /lib/ruby/2.7.0/net/imap.rb:1120:in `block in initialize'
	6: from /lib/ruby/2.7.0/net/imap.rb:1147:in `receive_responses'
	5: from /lib/ruby/2.7.0/net/imap.rb:1246:in `get_response'
	4: from /lib/ruby/2.7.0/net/imap.rb:2183:in `parse'
	3: from /lib/ruby/2.7.0/net/imap.rb:2259:in `response'
	2: from /lib/ruby/2.7.0/net/imap.rb:2318:in `response_tagged'
	1: from /lib/ruby/2.7.0/net/imap.rb:3310:in `atom'
/lib/ruby/2.7.0/net/imap.rb:3497:in `parse_error': unexpected token SPACE (Net::IMAP::ResponseParseError)

$ gem list imap

*** LOCAL GEMS ***

imap-backup (3.4.0)

config.json (slightly edited for obvious reasons):
{
  "accounts": [
    {
      "username"<EMAIL_ADDRESS>      "password": "xxxxxxxx",
      "local_path": "/home/xxxxx/.imap-backup/mxxx_xxxx.de",
      "folders": [

      ],
      "server": "<IP_ADDRESS>",
      "connection_options": {
        "ssl": false,
        "port": 143
      }
    }
  ],
  "debug": true
}

The server log shows (again with some slight editing):
2021-10-05 21:48:06,911 -  - [      87] ************** New Connection from: <IP_ADDRESS>:143 **************
2021-10-05 21:48:06,912 -  - [      87] S <-- * OK Synametrics IMAP4rev1 server ready 10/5/21 9:48 PM
2021-10-05 21:48:06,913 -  - [      87] C --> RUBY0001 LOGIN<EMAIL_ADDRESS>xxxxxx
2021-10-05 21:48:06,914 -  - [      87] S <-- RUBY0001 OK LOGIN completed
2021-10-05 21:48:06,949 -  - [      87] C --> RUBY0002 LIST "" ""
2021-10-05 21:48:06,950 -  - [      87] S <-- * LIST (\Noselect) "/" ""
2021-10-05 21:48:06,950 -  - [      87] S <-- RUBY0002 OK LIST completed
2021-10-05 21:48:06,989 -  - [      87] C --> RUBY0003 LIST "" "*"
2021-10-05 21:48:06,992 -  - [      87] S <-- * LIST () "/" "Inbox"
2021-10-05 21:48:06,992 -  - [      87] S <-- * LIST () "/" "Junk"
2021-10-05 21:48:06,992 -  - [      87] S <-- * LIST () "/" "PossibleJunk"
2021-10-05 21:48:06,992 -  - [      87] S <-- * LIST () "/" "Trash"
[some folders removed]
2021-10-05 21:48:06,994 -  - [      87] S <-- * LIST () "/" "Drafts"
2021-10-05 21:48:06,994 -  - [      87] S <-- RUBY0003 OK LIST completed
2021-10-05 21:48:07,029 -  - [      87] C --> RUBY0004 EXAMINE Inbox
2021-10-05 21:48:07,074 -  - [      87] S <-- * FLAGS (\Seen \Deleted)
2021-10-05 21:48:07,074 -  - [      87] S <-- * 2766 EXISTS
2021-10-05 21:48:07,074 -  - [      87] S <-- * OK [UIDNEXT 4064] Predicted next UID
2021-10-05 21:48:07,074 -  - [      87] S <-- * 0 RECENT
2021-10-05 21:48:07,074 -  - [      87] S <-- * OK [PERMANENTFLAGS (\Deleted \Seen)]
2021-10-05 21:48:07,075 -  - [      87] S <-- RUBY0004 OK [READ-ONLY] SELECT completed
2021-10-05 21:48:07,076 -  - [      87] C --> RUBY0005 EXAMINE Inbox
2021-10-05 21:48:07,094 -  - [      87] S <-- * FLAGS (\Seen \Deleted)
2021-10-05 21:48:07,094 -  - [      87] S <-- * 2766 EXISTS
2021-10-05 21:48:07,094 -  - [      87] S <-- * OK [UIDNEXT 4064] Predicted next UID
2021-10-05 21:48:07,094 -  - [      87] S <-- * 0 RECENT
2021-10-05 21:48:07,094 -  - [      87] S <-- * OK [PERMANENTFLAGS (\Deleted \Seen)]
2021-10-05 21:48:07,094 -  - [      87] S <-- RUBY0005 OK [READ-ONLY] SELECT completed
2021-10-05 21:48:07,129 -  - [      87] C --> RUBY0006 EXAMINE Inbox
2021-10-05 21:48:07,147 -  - [      87] S <-- * FLAGS (\Seen \Deleted)
2021-10-05 21:48:07,147 -  - [      87] S <-- * 2766 EXISTS
2021-10-05 21:48:07,147 -  - [      87] S <-- * OK [UIDNEXT 4064] Predicted next UID
2021-10-05 21:48:07,147 -  - [      87] S <-- * 0 RECENT
2021-10-05 21:48:07,147 -  - [      87] S <-- * OK [PERMANENTFLAGS (\Deleted \Seen)]
2021-10-05 21:48:07,147 -  - [      87] S <-- RUBY0006 OK [READ-ONLY] SELECT completed
2021-10-05 21:48:07,189 -  - [      87] C --> RUBY0007 UID SEARCH ALL
2021-10-05 21:48:07,203 -  - [      87] S <-- * SEARCH 1 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 .... and lots more till ...... 4063
2021-10-05 21:48:07,204 -  - [      87] S <-- RUBY0007 OK UID completed
2021-10-05 21:48:07,259 -  - [      87] C --> RUBY0008 EXAMINE Inbox
2021-10-05 21:48:07,277 -  - [      87] S <-- * FLAGS (\Seen \Deleted)
2021-10-05 21:48:07,277 -  - [      87] S <-- * 2766 EXISTS
2021-10-05 21:48:07,277 -  - [      87] S <-- * OK [UIDNEXT 4064] Predicted next UID
2021-10-05 21:48:07,277 -  - [      87] S <-- * 0 RECENT
2021-10-05 21:48:07,277 -  - [      87] S <-- * OK [PERMANENTFLAGS (\Deleted \Seen)]
2021-10-05 21:48:07,277 -  - [      87] S <-- RUBY0008 OK [READ-ONLY] SELECT completed
2021-10-05 21:48:07,319 -  - [      87] C --> RUBY0009 UID FETCH 1 (RFC822 FLAGS INTERNALDATE)
2021-10-05 21:48:07,320 -  - [      87] S <-- * 1 FETCH (UID 1 RFC822 {1928}
2021-10-05 21:48:07,320 -  - [      87] S <-- )
2021-10-05 21:48:07,322 -  - [      87] S <--  FLAGS (\Seen) INTERNALDATE "Mon, 28 Dec 2020 12:28:26 +0100 (CET)"
2021-10-05 21:48:07,322 -  - [      87] S <-- RUBY0009 OK UID FETCH completed
2021-10-05 21:48:07,365 -  - [      87] ~~~~~~~~~~~~~~ Connection closed: <IP_ADDRESS> (454 ms)~~~~~~~~~~~~~~

So it looks as if imap-backup actually fetches the first e-mail and then crashes with the exception shown in the beginning.
I must admit I have no idea how to find out, what email with ID 1 actually is but if it is just the oldest e-mail that looks fine to me (althout it contains an embedded picture).
Any idea what to do to further diagnose the reason?

Hi @WoOS2
Thanks for opening the issue.
This problem seems to relate to how Ruby's Net::IMAP parses a response from the IMAP server.
In order to be able to "see" what Net::IMAP fails to parse, I have changed the debug behaviour of the gem.
I've relased this as version 3.4.1
If you set debug: true in the config, as well as logging internals verbosely, Net::IMAP's own debugging is activated. This should give you the body of IMAP responses before they are parsed.
Let me know if that helps.

Sorry, the QNAP is sold (and in the end I copied the e-mails "by hand" from within Thunderbird). I can't try this anymore in this setup.


Rename tools/postgres-init-db to tools/postgres-init-dev-db.

The previous naming was confusing with scripts/setup/postgres-init-db
also existing.

Automated message from Dropbox CLA bot
@timabbott, it looks like you've already signed the Dropbox CLA. Thanks!

Merged.


A11y_AzureDataStudio(Schema,Dacpac,Backup)_DeployDacpac_DeployDacpacSummaryScreen_AI4D: The table under heading "Summary" has no name

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
#A11yMAS; #A11yTCS; #A11y_ADS_Schema_Dacpac_Backup; #Azure Data Studio; #DesktopApp; #Win10; #AI4D; #MAS4.1.2; #MAS1.3.1; #MAS4.2.1;
Environment Details:
Application Name: Azure Data Studio
Application Version: 1.9.0 (user setup)
Commit: 78a42e1d112ae3231777722b51eaf44f83ddbe55
Electron: 3.1.8
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.18362
Additional Details:
Tools Name: Accessibility insight tool
MAS References: MAS4.1.2,MAS1.3.1,MAS4.2.1
Repro Steps:

Launch Azure Data Studio application.
Connect to server with windows credentials.
Navigate to Extensions from left menu.
Search & install Dacpac extension.
Navigate to Connections from left menu.
Expand the server connected in step 2.
Right click an on prem database and select Data-tier application wizard from Context menu.
Select first radio button.
Navigate till next button & hit enter.
Provide all the details for Deploy Dacpac & hit next.
Navigate till Next button & hit enter.
Launch AI4D and hover over the table  present under heading "Summary".

Actual:
The  table under heading "Summary" has no name present for it when the AI4D is hovered over it.
Same issue is observed in the following pages:
1.Extract Dacpac Summary Screen
Follow the exact same steps mentioned above but select the second radio button.
2.Import Bacpac Summary Screen
Follow the exact same steps mentioned above but select the third radio button.
Expected:
There should be an appropriate name present for the table that represents the information in the table.
Recommendations:
Refer below link which is repository of bug fixes code snippets: https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
Screen reader users will not understand/relate any information that has been announced from the table. Users will not be able to co relate the information.
MAS Reference:
MAS 4.1.2-https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={248054a6-5e68-4771-9e1e-242fb5025730}
MAS 1.3.1- https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
MAS4.2.1- https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={a12f3779-bdf1-40c2-bbcc-0e314ea94858}
Attachment for Reference:

Checked and verified in below version the bug is no longer reproduced and hence closing the bug.
Version Details:
Version: 1.12.0-insider
Commit: a584aca96997a18ecedee73a575536332e542718
Date: 2019-09-19T07:58:50.448Z
VS Code 1.38.0
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362
#6660 A11y_AzureDataStudio(Schema,Dacpac,Backup)_DeployDacpac_DeployDacpacSummaryScreen_AI4D.pptx


fix(ingest): update athena type mapping

The types in the mapping need to be valid inputs for SchemaFieldDataType, which means they must come from the codegen'd class. This fixes a regression from https://github.com/datahub-project/datahub/pull/8137.
Fyi @bossenti - I don't think this should have any impact on the functionality of your PR, since the mappers are only used by dbt/looker/similar sources, whereas the custom athena dialect handles it for the athena source itself. This was necessary to avoid a sqlalchemy dependency in dbt/looker since they import sql_types.py.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Thanks for notifying @hsheth2!
I'll give it a quick test.
Just to foster my understanding: Are the type definitions for Athena even needed here?

@bossenti the stuff in metadata-ingestion/src/datahub/ingestion/source/sql/sql_types.py is used by dbt/looker to map strings -> datahub types. The logic in sqlalchemy_type_converter should be used by the actual sources to map sqlalchemy types to datahub types.
The class MapType(types.TupleType) didn't really make sense to me, but if it works then I'm fine leaving it in

CI failure appears unrelated, and this is needed to fix CI so merging in anyways.


No mop mode control for the Dreame d9 anymore

Describe the bug
A clear and concise description of what the bug is.
Hey I got an dreame d9 connected to hk via hoobs and miot. Anything worked well so far until my card got corrupted. After a reflash (and no backup) all my plugins are gone. So I reinstalled miot and connected my dreame. But now, I got no controls over the mop mode anymore. Can anyone help me with this issue? It’s important because I use Automations that toggle she mop water mode.
Regards,
Sauberkiwi

You already opened a discussion for that. No need for an extra issue.


feat: add formatCurrency() and parseCurrency()

Related to #113

@all-contributors please add @linconkusunoki  for code, doc, and tests.

Thanks for letting me know @w35l3y !


operaton-qa-integration-tests-webapps-shared-engine: failed to execute goal install

Describe the bug
During the build process in a Docker Container, the following error occurs:
685.5 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.1.3:install (default-install) on project operaton-qa-integration-tests-webapps-shared-engine: The packaging plugin for project operaton-qa-integration-tests-webapps-shared-engine did not assign a file to the build artifact -> [Help 1]

685.5 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.1.3:install (default-install) on project operaton-qa-integration-tests-webapps-shared-engine: The packaging plugin for project operaton-qa-integration-tests-webapps-shared-engine did not assign a file to the build artifact

(...)

685.5 Caused by: org.apache.maven.plugin.MojoExecutionException: The packaging plugin for project operaton-qa-integration-tests-webapps-shared-engine did not assign a file to the build artifact

(...)

On my MacBook this is actually working, the error only occurs when trying to build a container with a fresh checkout.
To Reproduce
I created a docker container that checkouts the main branch and does a fresh mvn clean install like so:
FROM maven:3-eclipse-temurin-17 AS builder
WORKDIR /home/maven

RUN apt-get update && apt-get install -y git

# install operaton
RUN git clone https://github.com/operaton/operaton.git /home/maven/operaton && \
    cd /home/maven/operaton && \
    git checkout dbbfe94 && \
    ./mvnw clean install -DskipTests=true

Then triggering the build with: docker build -t test .
Expected behavior
It should build and install the Operaton packages into the local maven repository

Perhaps it's the same problem like this one here? https://github.com/operaton/operaton/pull/186

I just tried to reproduce it, first by deleting all artifacts from my local repo and doing a fresh build with no preexisting ones.
I'm curious about the combination of --depth 1 and the checkout of a certain commit. If this is the latest commit, then it should already be present. If it is not the latest commit, then the checkout should not be possible, as your local repo only knows the latest commit. Can you explain this to me?

Yes it's an error in the Dockerfile, the --depth 1 must be removed

I used to do just do a shallow copy but it was then cached by docker, so i added the explicit git sha. But this is only a workaround anyway until beta-2 is released

Can confirm the error with the Dockerfile posted above.


[BUG] Page has been updated but the link has not been rechecked

On Fanatical's bundle page, click on the product and then click left or right to change the product does not recheck the link.
The link will not be rechecked unless I use the "Clear and run (reload)" command directly.
e.g. https://www.fanatical.com/en/bundle/nitro-bundle

Dupe of https://github.com/Revadike/SteamWebIntegration/issues/16


Added changes to clean up the container after a SIGINT

This PR fixes the issue #82
Using trap to run ctrlc_handler function on a SIGINT and clean up the docker containers created.
changes 2 to & to avoid stdout getting printed in docker stop command
Signed-off-by: bharathappali<EMAIL_ADDRESS>

As i couldn't add anyone as reviewers i'm mentioning request for reviewers below
@dinogun @ShishirH

Missed to see -t option in deploy script. Ctrl+C along with deploy.sh -t -c docker solves the issue.
Closing this PR as its not required

While right now only docker terminate works, I believe we should be cleaning up for every environment in the future. In such a case, I think trap "{cluster_type}_terminate" 2 would be better

@ShishirH Yeah we can add that in the ctrlc_handler as in future we may get any other pre-cleanup stuff needs to be done. I'm fine in doing either ways, jus thought having a seperate function will be a good approach.


[Feature Request] Fade to Black option in Switch Scene

Problem
There is no way to fade in and out from black during a Switch Scene event (instead of white, which is the current behavior). You can overlay, but it does not switch scenes.
Describe the solution you'd like
I would like for a toggle on the Scene Switch event for "Fade to Black", and when the Scene Switch event is called, the room transitions to black instead of white. When "Fade to Black" is not toggled, the current behavior is applied and the Scene Switch fades in and out from white.
Alternatives
I considered using an overlay to black and then switch scene, but it would add unnecessary complexity to the scripts I'm trying to work with and not really solve the issue.
Context
I'm currently implementing a Day/Night cycle and when the sun goes down and the time is night, I would like for the scenes to switch by fading to black instead of white (which would be more like daytime.)

Scene switch takes a lot of power to load and place all the new background tiles,
To improve performance and faster vram access, the screen is turned off during these sections, which is white on a gameboy, (you can still notice a small hitch in audio when this happens).
Not turning off the screen and setting palettes black causes almost a second of lag for any scene switching, becuase the vram is still being accessed. This also makes the audio hitch a lot longer.
Things to look into,
Loading the tiles over multiple frames to reduce audio hitch.


Problem with stylePanelAspectRatio

Summary
The setting stylePanelAspectRatio: 'x:x' does not work as expected. Using allowMultiple: false I'd expect a single uploaded image to fit exactly into the view. However it is slightly too large. You can see an example here.
Note: this problem does not exist with stylePanelLayout: 'integrated'.
Images
Chrome

Safari

How to reproduce
Click link, I have checked this on macOS (Chrome + Safari) and it turns out the problem only exists in Chrome.
Expected behaviour
No scrollbar
Additional information

Environment
Version

OS
MacOS

Device
Macbook Pro

Browser
Chrome 72.0.3626.81 (Official Build) (64-bit)

To be honest this mode was only meant to be used in combination with the 'integrated' setting.
I'll see if I can improve this in the future. But for now you can set a fixed height to the filepond root element and a fixed preview height to the image preview (imagePreviewHeight).

Seems this issue still exists; I have resolved the issue with a great function called aspectRatioMakeSlightlyHigher:
const aspectRatioMakeSlightlyHigher = (ratio) => {
  const ratioStable = ['1:1'].includes(ratio)
  if (ratioStable) return ratio

  const integratedIs = this.options && ['integrated'].includes(this.options.stylePanelLayout)
  if (integratedIs) return ratio

  const ratioNew = aspectRatioNumberTo(ratio) / 1.04
  return `${Math.round(ratioNew * 100000000)}:100000000`
}


fixing state inconsistent bug

fix the state inconsistent bug
add the unit test case for state inconsistent bug
review all the state/add filters handling and update associated test cases.

CLA is valid!

@neraliu , please review my latest comments for this PR https://github.com/yahoo/context-parser-handlebars/pull/20.

i agree to ur point, but there are still some consideration about how to define the equal state after the branching logic, so i am good now of not optimizing the code as shown.


New feature: Support for Azure Application Proxy.

Hey,
our Gerrit instance is exposed via Azure Application Proxy when accessed over internet.
Plugin can't connect to instance with following error as it get's Microsoft login page:

Expected JSON but got 'text/html; charset=utf-8'

Would it be possible to add support for some intermediate authentication methods? I guess that some popup window with cookie store should be enough.
What's your take on that?
Br,
Kuba

Does this setup require double authentication, i.e. do you need to authenticate against the Azure proxy and after that against Gerrit?

Yes first I need to log in with my MS account (with 2FA) just to access gerrit, then I need to log in into gerrit.
Based on parts of documentation that I read and behavior that I see, it uses cookies for access control.

@ZawadaZSE did you need any additional setup for your git cli?

Hey, unfortunately we don't have git access over internet -> only gerrit UI.

@ZawadaZSE, do you have more details about your scenario, e.g. when you browse to gerrit UI, can you inspect browser request to find out this cookie's name/value?
If you could retrieve data from your gerrit instance using a tool like e.g. curl -u 'user:pass' ... -b 'cookieName=value' ... -H 'someHeaders' , it would be more clear how to solve your issue.

Yeah, so it works like this.
When I'm not connected to our corporate VPN I can access gerrit via Azure Application Proxy,
curling the endpoint without cookies results with 302 Redirect to Microsoft SSO: https://login.microsoftonline.com/[...]/oauth2/authorize?response_type=code&client_id=[client_Id]&scope=openid&[some_other_params]
After login (with 2FA) I end up with cookie "AzureAppProxyAccessCookie_[client_Id]_1.3"
When I add this cookie to curl I get access to gerrit rest api.


add option to enable network check and document it

What does this PR do?
It adds an option to enable the network check in the docker image. More precisely we used to rm network.yaml.default in the dockerfile, now it's deleted in the entrypoint only if the NETWORK_CHECK env var is not set. So the default behavior stays the same, but people who know what they're doing can enable it.
Why
This allows to monitor the network throughput for the host if the container runs with un-containerized networking (using --net=host). README.md has been updated to explain clearly the implications and the arrangements to make.
Note: using this option without the --net=host option will work but the metrics will be irrelevant. They will only report dd-agent network metrics which are not really useful and are already collected by the docker check anyway.

Awww I was excited waiting for this in the 5.9.0 release but looks like it didn't make it in :'(


Fixes "network deploy" command.

Can you please resolve the merge conflict and add more details to the PR description?


Discuss: should slack-api be haddock'ed?

There are currently no haddock comments in the source.  Should this be added? Might make it easier to jump around. http://hackage.haskell.org/package/slack-api has no links at all. Is this a feature request or absent on purpose?

It looks like the docs failed to build. Let me investigate.

Thanks, looking forward to it. The lens packages has it on github as well (http://ekmett.github.io/lens/frames.html). I don't know how much trouble it is to set that up though.

I just manually uploaded the docs. Feel free to ask any questions if anything is unclear.


Mobile wrapper test

Codecov Report

Merging #184 (f16ac53) into main (c8caffd) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #184      +/-   ##
==========================================
- Coverage   55.16%   55.11%   -0.06%
==========================================
  Files          40       40
  Lines        4374     4378       +4
==========================================
  Hits         2413     2413
- Misses       1565     1569       +4
  Partials      396      396

Impacted Files
Coverage Δ

crypto/models.go
9.09% <0.00%> (-2.03%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Side bar layout fix

PR Fixes:

1 Side bar layout fix now no longer taking 100% of width

Resolves #562
Also, tsconfig.json got auto fixed with lint
Before:

After:

@hkirat  Please check this if needed.


Never sign AuthnRequests when using REDIRECT binding

Signing is done via the Signature query parameter. This is explained in
section <IP_ADDRESS> DEFLATE Encoding of the binding specification. The
signature is never generated for AuthnRequests when using REDIRECT, and
if it were, it is now always removed as part of the DEFLATE encoding.
Note that the specification states that you should first generate an XMLSig, then remove it and then generate the Signature query parameter if the XMLSig was present in the first place. I found this rather inefficient (signature generation is quite expensive), so I opted for not generating the XMLSig at all.

LGTM
cc @mmoayyed


How do you actually use it (Angular 8)?

I'm trying to get hold of the seed number to log it to the console. I need this in order to check seed logged via the build pipeline on Azure, to replicate the test order when a test might fail because of the order it runs.
I've tried the following

karma.conf.js:

function generateSeed(lower, higher) {
    process.env['JASMINE_SEED'] = Math.floor(Math.random() * higher) + lower;
    console.log(process.env['JASMINE_SEED']);
}

module.exports = function (config) {
    config.set({
        ...
        plugins: [
            require('karma-jasmine'),
            require('karma-chrome-launcher'),
            require('karma-jasmine-html-reporter'),
            require('karma-coverage-istanbul-reporter'),
            require('karma-junit-reporter'),
            require('@angular-devkit/build-angular/plugins/karma'),
            require('karma-jasmine-seed-reporter')
        ],

        client: {
            clearContext: false, // leave Jasmine Spec Runner output visible in browser
            jasmine: {
                random: true,
                failFast: true,
                // Add the seed to run a specific randomized order. This is helpful to debug tests that fail only in a specific order.
                seed: generateSeed(1000, 100000),
                failSpecWithNoExpectations: true,
                oneFailurePerSpec: false,
                timeoutInterval: 10000,  // Increases the async callback timeout on test methods
            }
        },
    ...
});

package.json:

...
"devDependencies": {
    ...
    "karma-jasmine-seed-reporter": "^0.2.0",
    ...
}
...

In my test.ts, I am trying to access the seed and log it to the console:

test.ts

console.log(`Using seed ${process.env['JASMINE_SEED']} to randomize the tests`);

However this logs as undefined.
I dont think I understand fully how to use this package, please help?

I misunderstood reporters in general, after further digging I managed to get it working. Closing the issue


BelongsToMany::pivotModel does not resolve to class object

According to docs it's possible to define pivot model to belongsToMany relationship.
In the example from docs it should be enough to pass just string.
However, it does not work.
https://github.com/adonisjs/adonis-lucid/blob/4adb6df3da2464ea116c4f16267d306f756bcda6/src/Lucid/Relations/BelongsToMany.js#L424-L427
pivotModel() just sets pivotModel which has to be already model class.
What's missing here is casting string to model (as in Model::belongsToMany())
https://github.com/adonisjs/adonis-lucid/blob/4adb6df3da2464ea116c4f16267d306f756bcda6/src/Lucid/Model/index.js#L1278-L1279

Ah, found event PR for this issue: https://github.com/adonisjs/adonis-lucid/pull/254

Fixed in 80fc99cf6c0edea8858d22899c59d9ff294ddbb5