[DESIGN] Finalise optimal JSON structure for answers payload

Determine an optimal JSON structure for sending answers payloads to the API.
Describe the solution you'd like
<More details to follow, here or in comments>
Describe alternatives you've considered
<A clear and concise description of any alternative solutions or features you've considered.>
Additional context

This is the proposed payload for the answers endpoint: https://viewer.diagrams.net/?page-id=z5HBLktNAcPlfK06zZkv&page-id=z5HBLktNAcPlfK06zZkv&target=blank&highlight=0000ff&nav=1&hide-pages=1#G17NrR06_ZNPUmfwvVBoKOmFXpj7ThOhDm
cc: @JBurkinshaw  @julia-rom

A few thoughts on this:

The API route contains form type (e.g. .../registration_answers, .../intervention_answers, .../monitoring_sequence). I don't see a reason why question_form_type needs to be included in the request body because of this.
Maybe we only need question_id and answer_value within an answer object (possibly answer_other as well but I am struggling to remember its purpose). Does the API need to be aware of the other property values?

Can the UI be responsible for ensuring the answers in the payload are for the questions related to a specific form section?
Does the UI need to tell the API what the question_parent_id and question_type are or can the API be trusted to know that based on what the question_id is?

I might be wrong on this, but would it make sense to use PUT to submit all answers and POST only to create a new monitoring sequence? Other than creating a new monitoring sequence, does POST do something PUT cannot? From these docs:

The HTTP PUT request method creates a new resource or replaces a representation of the target resource with the request payload.
The difference between PUT and POST is that PUT is idempotent: calling it once or several times successively has the same effect (that is no side effect), whereas successive identical POST requests may have additional effects, akin to placing an order several times.

That's a fair point. I forgot to remove question_form_type when I split the forms into their own tables.
Details:

Purpose of the fields:question_form_section: Will be removed,
question_id: Stores the reference to Question ID
question_parent_id: Stores the reference to the parent Question. Can be useful for validation.
question_type: Can be any of string, float, integer, or array
answer_value: Stores the actual answer to the question. Multiple and single choice is stored as array.
answer_other: If the answer_value happens to be a choice and one of the choice is "Other"

If we agree backend will be the source of truth as far as the definition of the questions is concerned, then we can reduce the fields into:question_id: Stores the reference to Question ID
answer_value: Stores the actual answer to the question. Multiple and single choice is stored as array.
answer_other: If the answer_value happens to be a choice and one of the choice is "Other"

Let's do that (use PUT). This is one of the reason I feel this isn't really restful as it doesn't really fit into the usual pattern of HTTP verbs. The supposed attributes are actually represented as rows (instead of columns).

If we agree on #2, please note that I will still store the values this way:

just catching up on this thread...
@ghelobytes for #2 ... you have

question_id: Stores the reference to Question ID
answer_value: Stores the actual answer to the question. Multiple and single choice is stored as array.
answer_other: If the answer_value happens to be a choice and one of the choice is "Other"

In that case, would I just be sending an array with an object with those three properties for each form section? I'm also struggling to understand why we need the 'other' part. Do you know if we have this kind of question?

isn't the second form type just called monitoring? Was intervention_answers specified as a name? Also agree that we don't really need the form section name, as we can infer it from the question number/id

isn't the second form type just called monitoring? Was intervention_answers specified as a name? Also agree that we don't really need the form section name, as we can infer it from the question number/id

The forms are Registration, Intervention, and Monitoring.
Registration and Intervention maps to 1 set of answers only.
Monitoring is recurring so there will be multiple set of answers.

is there a route I can test out with the answers payload (basic structure for now) @ghelobytes ?

In gist:
curl --location --request PUT 'https://mrtt-api-test.herokuapp.com/api/v2/sites/1/registration_answers' \
--header 'Content-Type: application/json' \
--data-raw '[
  {
    "question_id": "Q1.1",
    "answer_value": "Bakawan Restoration Project"
  },
  {
    "question_id": "Q1.5",
    "answer_value": {
      "area_km": 10,
      "geojson": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              30.0,
              10.0
            ],
            [
              40.0,
              40.0
            ],
            [
              20.0,
              40.0
            ],
            [
              10.0,
              20.0
            ],
            [
              30.0,
              10.0
            ]
          ]
        ]
      }
    }
  },
  {
    "question_id": "Q2.5",
    "answer_value": [
      {
        "choice": "Full protection"
      },
      {
        "choice": "No management"
      },
      {
        "choice": "Other",
        "value": "Community protected"
      }
    ]
  }
]'

I'm a little confused at how to implement this with AXIOS. Wouldn't the first submit be a POST? Would I use 'https://mrtt-api-test.herokuapp.com/api/v2/sites/1/registration_answers' in the axios call?

We decided early this week that PUT would be suitable as it can be used to create or update records. One example (there are many more and I haven't followed this one): https://stackabuse.com/how-to-make-put-http-request-with-axios/

@ghelobytes for some reason my tag wasn't working in the previous comment - could you confirm whether https://mrtt-api-test.herokuapp.com/api/v2/sites/1/registration_answers is the correct route to use when testing the PUT call?

@julia-rom This is an example on how you would use axios to send the answers:
<html>
  <!-- python -m http.server 9000 -->
  <head>
    <script src="https://unpkg.com/axios/dist/axios.min.js"></script>
    <script>
      function send_answers() {
        var url =
          "https://mrtt-api-test.herokuapp.com/api/v2/sites/1/registration_answers";
        var payload = [
          {
            question_id: "Q1.1",
            answer_value: "Bakawan Restoration Project",
          },
          {
            question_id: "Q1.5",
            answer_value: {
              area_km: 10,
              geojson: {
                type: "Polygon",
                coordinates: [
                  [
                    [30.0, 10.0],
                    [40.0, 40.0],
                    [20.0, 40.0],
                    [10.0, 20.0],
                    [30.0, 10.0],
                  ],
                ],
              },
            },
          },
          {
            question_id: "Q2.5",
            answer_value: [
              {
                choice: "Full protection",
              },
              {
                choice: "No management",
              },
              {
                choice: "Other",
                value: "Community protected",
              },
            ],
          },
        ];

        axios.put(url, payload).then(function (response) {
          console.log(response.data);
          console.log(response.status);
        });
      }
    </script>
  </head>
  <body>
    <button type="button" onclick="send_answers()">Send answers</button>
  </body>
</html>

cc: @JBurkinshaw

hmm right now if I send to 'https://mrtt-api-test.herokuapp.com/api/v2/sites/1/registration_answers' using an axios patch request, I get a 404

it looks like items 0-3 are being added onto the response. Is this seed data that you used in the api @ghelobytes. I'm only adding 3 - 7.  I also have to update the question ids from the descriptive titles

it looks like items 0-3 are being added onto the response. Is this seed data that you used in the api @ghelobytes? I'm only adding 3 - 7. I also have to update the question ids from the descriptive titles

@julia-rom
This made me realize the current behaviour should be a PATCH (partial updates).
I'll reimplement PUT so that the records will stay true to the payload (i.e. if you remove an answer to the question in the payload, that get's delete in the DB too).

ok, I think that's ok for now since we haven't implemented editing yet

In general, answers payload will take the form of:
[
    {
        "question_id": "Q1",
        "answer_value": [ "CHOICE A", "CHOICE B"]
    },
    {
        "question_id": "Q2",
        "answer_value": [ "CHOICE A", "CHOICE B"]
    },
    ...
]

Where answer_value will be validated against a jsonschema defined for the question_id.
Related ticket: https://github.com/globalmangrovewatch/gmw-api/issues/40

Example Postman and Thunder client requests: mrtt_requests.zip


Set database collation

Set database collation to match upstream settings. Related to https://github.com/gitlabhq/gitlabhq/pull/8195.

@maxlazio squashed.

@bbodenmiller would you be kind to also add this change in the template example?
https://github.com/gitlabhq/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template#L206

@axilleas done.

@bbodenmiller Great, thanks :)


Need action usage prompt on UI (not Zepplin UI)

A newbie of SSM UI hards to figure out the action argument of "read" is "-file file-name".
We should put usage prompt for each action on UI.

#630 was created to solve this issue

resolved in #692


Linux support

Is this suppose to work on Linux. My attempts to get it running are met with
"install_driver Unimplemented!" and
"start_service Unimplemented!"
I cloned the repo and did ./build.sh in the main directory. I cded to Platbox/compiled
and tried to get both the paltboc_cli and the example to work but were meant with the unimplemented errors.
I wanted to make sure I wasn't doing something wrong before looking at writing the linux support.

There is Linux support indeed. You need to compile the driver and load it manually however. If you copy the compiled driver into the same directory where platbox_cli is, you can then use "platbox_cli start".


added lumin spatial mesh observer profile

XRTK - Mixed Reality Toolkit Pull Request
Overview
added lumin spatial mesh observer profile
Related Submodule Changes

https://github.com/XRTK/XRTK-Core/pull/848

/azp run


[Bug] Query result duplicate primary key

Search before asking

[X] I searched in the issues and found nothing similar.

Paimon version
0.7.0-incubating
Compute Engine
Flink 1.18.0
Minimal reproduce step
we have a flink job write data to paimon table，table options is：
+---------------------------+---------+
|                       key |   value |
+---------------------------+---------+
|                    bucket |       8 |
|     scan.remove-normalize |    true |
| deduplicate.ignore-delete |    true |
|        changelog-producer |    none |
|               file.format | parquet |
+---------------------------+---------+
What doesn't meet your expectations?
When job execute for some time, we use batch mode query table ,some of our query results duplicate primary key.

When we update paimon version to query this table,it also has duplicate primary key.
Anything else?
I want to know what cause this problem. Is this problem caused by writer operator? Does a later version fix this issue?
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

It may happens when you changed the bucket numbers and have not overwrite table first.

It may happen when you change the bucket number but have not overwrite table first.

Bucket number have not been modified since the table was created.

What about your table schema?  @herefree

What about your table schema and did you delete data before? deduplicate.ignore-delete is true @herefree

{
"id" : 2,
"fields" : [ {
"id" : 0,
"name" : "",
"type" : "STRING NOT NULL",
"description" : ""
}, {
"id" : 1,
"name" : "",
"type" : "STRING",
"description" : ""
},
......
{
"id" : 54,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 55,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 56,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 57,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 58,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 59,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 60,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 61,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 62,
"name" : "",
"type" : "STRING",
"description" : ""
}, {
"id" : 63,
"name" : "",
"type" : "STRING",
"description" : ""
} ],
"highestFieldId" : 63,
"partitionKeys" : [ ],
"primaryKeys" : [ "id" ],
"options" : {
"bucket" : "8",
"scan.remove-normalize" : "true",
"deduplicate.ignore-delete" : "true",
"changelog-producer" : "none",
"file.format" : "parquet"
},
"comment" : "",
"timeMillis" :<PHONE_NUMBER>673
}
I didn‘t delete data before，but  the changlog of the upstream table may have -D data.I set deduplicate.ignore-delete is true just don't want -D data was write in this table，Or  some flink job don‘t consumer -D data when consuming this table.

I also find this duplicate data in the same bucket.

What about your table schema and did you delete data before? deduplicate.ignore-delete is true @herefree

I set deduplicate.ignore-delete = false, I find it didn‘t have duplicate primary key,but I not sure that the later versions fix this problem.

@herefree Could you give the detailed minimal reproduce steps so that we can reporduce this bug?


'remood' is now an own npm package

As it's important for further development & no one mentioned any concerns, I'm merging


Lock intervaltree version

intervaltree version 3.0 (pypi released 4h ago) has backwards incompatible changes: https://github.com/chaimleib/intervaltree/tree/dev

https://github.com/chaimleib/intervaltree/issues/77

Affecting Mbed OS master now, should be fixed asap. I always wonder why requirements are not more strict for versioning. Any major version can break the promise

/morph test


Moved postgres enums between schemas, sqlc replaces Go string types with interface{}

Version
1.17.2
What happened?
I ran a migration on our Postgres 14.5 databse to move enum types between schemas using SET SCHEMA, and then updated the relevent tables. sqlc generate then replaces the previously correct string types with interface{}
This:
type UpdateUserParams struct {
        ... other fields ...
	RoleType       RoleTypes
}

Becomes this:
type UpdateUserParams struct {
        ... other fields ...
	RoleType       interface{}
}

Relevant log output
No response
Database schema
ALTER TYPE role_types SET SCHEMA core;
ALTER TABLE core.users ALTER COLUMN role_type TYPE core.role_types;

SQL queries
-- name: UpdateUser :exec
UPDATE core.users
SET first_name = $2,
  last_name = $3,
  bio = $4,
  city = $5,
  state = $6,
  country = $7,
  profile_image_id = $8,
  role_type = $9
WHERE Id = $1;

Configuration
version: "2"
sql:
  - engine: "postgresql"
    queries: "sqlc/"
    schema: "./../../../db/sql/versioned-migrations/init"
    gen:
      go:
        sql_package: "pgx/v4"
        package: "db"
        out: "db"

Playground URL
No response
What operating system are you using?
macOS
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

This problem is fixed on sha 27ffceda! When will a new release be cut that includes this code? @kyleconroy


Add support for querying extended relationships to sample app

I haven't incorporated actually using the feature of the middleware, but there are examples in the comments.

@robertdp Can you add the exact same to code the rethinkdb example as well?

Done.


Integration between Noir and gnark's Backend

Functionality (tested manually)

[x] nargo execute
[x] nargo check
[x] nargo contract
[x] nargo gates
[x] nargo new
[x] nargo test
[x] nargo compile
[x] nargo verify
[x] nargo prove

Testing

[ ] Integration tests

 Fix preprocess

 Integration


Move devicePreference switch to UI

BTW, move sw.js to first page loading as which requires page reloading when service worker is registered. Which would impact the page scheduling when switch device to CPU in the previous code.

Example of Preview: https://honry.github.io/webnn-samples/image_classification/

@huningxin, PTAL, thanks!


Swift failing when generating Ubuntu2204 image

Description
When running the GenerateResourcesAndImages.ps1 it fails when running install-swift.sh
==> azure-arm.build_image: Downloading package from https://swift.org/builds/swift-5.10-release/ubuntu2204/swift-5.10-RELEASE/swift-5.10-RELEASE-ubuntu22.04.tar.gz to /tmp/swift-5.10-RELEASE-ubuntu22.04.tar.gz...
==> azure-arm.build_image: Package downloaded in 8 seconds
==> azure-arm.build_image: Downloading package from https://swift.org/keys/all-keys.asc to /tmp/all-keys.asc...
==> azure-arm.build_image: Package downloaded in 1 seconds
==> azure-arm.build_image: gpg: directory '/root/.gnupg' created
==> azure-arm.build_image: gpg: keybox '/root/.gnupg/swift' created
==> azure-arm.build_image: gpg: no valid OpenPGP data found.
==> azure-arm.build_image: gpg: Total number processed: 0
==> azure-arm.build_image: Script exited with non-zero exit status: 2. Allowed exit codes are: [0]

Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
N/A
Is it regression?
Yes, my last success was january release
Expected behavior
Install swift and move to next tool
Actual behavior
Erroring out on checking keys
Repro steps
Run generateResouresandimage.ps1 with -ImageType "Ubuntu2204"

Hey @GavinToddlds!
One of our nightly builds failed too. It should be transitive issue, but I'll wait for build to return green.

FWIW, I have seen this issue pretty consistently since Monday at 1:00 pm EDT, I have tried a new build each day (using the latest code each time).

@erik-bershel Thanks for the update. I'm seeing the issue today as well.

Just for the history and newcomers:
It seems to be not transitive. We are working on unlocking builds.

Heads up!
PR merged - feel free to update your forks or clones to continue builds.


[automation] Update go release version 1.19.3

What
Bump go release version with the latest release.
Further details
See changelog for 1.19.3
Automatically generated from https://apm-ci.elastic.co/job/apm-shared/job/bump-go-release-version-pipeline/

:green_heart: Build Succeeded

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

Expand to view the summary

Build stats

Start Time: 2022-11-07T04:17:15.776+0000

Duration: 7 min 50 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
19

Skipped
0

Total
19

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.


add daemon or watch mode equivalent of tye run

The idea is that we can leave the host and dashboard running, and services can drop in and out.

Just a thought, but could the dashboard be in a container that is automatically added to a tye.yaml?
It'd be useful to have a preexisting and non-trivial working component in a new tye project by default. Especially one that uses some of the newer goodies like Blazor, and potentially uses the very features that tye offers for microservices...

What does the dashboard being in a container gain you?

What does the dashboard being in a container gain you?

No must-haves, but aside from the built-in sample I mentioned above, I think it'd also be useful to a user of tye for a few other reasons:

Bootstrap: Bellwether service showing that everything is working (docker/dotnet core/kubernetes/tye/permissions/registry)
Bootstrap: A built-in dashboard is a great bootstrapping tool.
Decouples tye CLI from a web page - this has confused me a few times, as closing a terminal window rarely impacts a web page in my experience.
Can restart/shutdown the dashboard directly if it's not needed.
Can deploy the dashboard to k8s as well with deploy, which could keep the same experience as local dev, and give immediate access to logs, health (#19), metrics after deployment. Potentially even use k8s's downward APIs to help manage things if something like replication, and lifecycle control is planned from the dashboard itself (shutdown, restart, spin up five of these, etc).
I imagine tye CLI could be used to point to different hosts like kubectl's --context flag. But, I'm not sure how intertwined the dashboard and hosting functionality are.

Cool thing is tye already knows how to create containers and helm charts, could be like an embedded resource thing that turns into a container...but, just thinking out loud on that 🤔.

Decouples tye CLI from a web page - this has confused me a few times, as closing a terminal window rarely impacts a web page in my experience.

Yes I think that's one of the reasons for making that kind of experience in the first place. We'll have to do something like this anyways to make it run in the cluster.
I'm hesitant to rely on docker for core functionality but it might be fine as a mode.

Presume this would watch tye.yaml for changes and recreate containers based on changes to the .yml, rather than currently having to kill/restart tye run

Yes, we super want this 👍
The work that I did this milestone with diagnostics integration makes it even more important because those things are slow to start.


fix(scf): layer config bug

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Drag and Drop to Browser

Currently, drag and drop fails if you try to drag a file to a browser (like a drop field in a website to upload the file). I know that other IDEs like JetBrain's suite support this, but I know they are written in an entirely different language/manner. IDK much about electron or even if this is possible, but I think it would be a great feature to add!

Duplicate of #164


Add PostAggregators to generator cache keys for top-n queries

This PR is to fix #3719.

This change is

👍

@drcrallen, @gianm thanks for your review. I addressed comments.
Additionally, I added the below feature to CacheKeyBuilder.

When a collection is appended to CacheKeyBuilder, that collection is sorted by its items' byte representation. This is to guarantee that collections of same items but in different orders make the same result

@jihoonson, thx for the update. had a couple further comments on the new stuff.

@gianm, thanks. I addressed your comments.
I think we need more tests to verify query caching with various types of fields, aggregators, post aggregators, etc. To make the tests concrete, I think it would be better to add more classes which are specialized for each query type. These tests are parameterized with original query, renamed parameters, and parameters of different order. However, this will cause a huge change in tests. I'm not sure about adding these tests in this PR. Maybe better to add in a following PR? What do you think?

That test sounds great -- we don't have amazing coverage of caching and cache key right now. I think it makes sense to do it in a followup PR.

@gianm, fixed. Thanks!

Requesting more class docs for the cache helper, but not strong enough to block the PR

Going to merge this one then, but @jihoonson could you please do a follow up adding the javadocs that @drcrallen mentioned to CacheKeyBuilder? thx

@gianm, @drcrallen thanks for your review. I opened #3933 for adding docs.


SSH support, Loader prompt handling

-Added ssh support using paramiko library
-'loader> ' handle for EX or SRX devices

few minor updates

Merged your code with my changes for Avocent console servers ( #27 ) and everything works ok. Probably there need to be additional parameter to distinguish between console server models (Cisco/Avocent) to avoid editing source of module - some fast, dirty changes.
usage:
netconify --facts --ssh=console_server,22,console_user:port,console_pass -u user --passwd "password"

more info:

ssh port alias implementation on Avocent
trace of states


[ENG-6025] Hotfix - API and admin aren't inheriting settings from website

Purpose
Fix settings propagation from website to api and admin
Changes

changed import statement to import everything from website in api settings
removed plainly reassigned settings
added localhost as allowed domain to local-dist in admin

QA Notes
Settings may have been altered
Documentation

Side Effects

Ticket
ENG-6025

@opaduchak It looks like the last activity on this was Aug 1st. Seems like it should have been reviewed.


[SQLite] Support .returning in the latest SQLite

.returning() doesn't work on SQLite, however it looks like their latest version does support it now: https://nalgeon.github.io/sqlite-3-35/
Any chance of getting this working in Knex? Thanks

@umaar We depend on node-sqlite driver for that, which is only on 3.32.3 for now (https://github.com/mapbox/node-sqlite3/releases/tag/v5.0.1).
As soon as update version of driver is released, we'll check if any changes on our end will be needed for returning to work correctly with SQLite.

Thanks for raising an issue there! https://github.com/mapbox/node-sqlite3/issues/1453

The aforementioned https://github.com/TryGhost/node-sqlite3/issues/1453 has landed in version 5.0.3 of the driver. Is it now possible to move forward with this? https://github.com/microsoft/vscode-node-sqlite3/issues/15, related to this, was opened with the fork of the driver, but a corresponding issue does not seem to exist in the newly relocated upstream repo of the driver

yes, that's the plan

@kibertoad As sqlite3 has bundled SQLite with RETURNING support since v5.0.3, and better-sqlite3 since v7.1.4, would a PR now be welcome to resolve this issue?
I've hacked in the changes locally in my node_modules and they seem to be working well.

@simonplend Would be awesome! Tests should already exist: https://github.com/knex/knex/pull/4934

@kibertoad Great, I'll see what I can throw together tomorrow.

Released in 2.3.0


[BUG REPORT] The general idea is a bug i encountered while trying to suggest a feature

Version
0.6.0-pre.5
Description
Sometimes when you use the suggest feature and the bot dms you, the lightbulb will not appear, not allowing you to suggest a feature
Reproduction Steps
I came across this bug by using the command in the staff commands channel, simple as that
Other Information
I've only encountered this bug once so far, I'll likely see if it appears again
Submitter Information
Discord Tag: Shel#7239
Discord ID:<PHONE_NUMBER>47337216
Date/Time Submitted: 7/24/2020, 9:55:37 AM
Disclaimer: PLEASE READ
This issue was NOT written by the author of the repository OR the account that posted this issue. This issue was submitted through the program hosted in this repository, via Github's API, by someone that uses the program ("user"). The user can be found above.

Sometimes, the bot decides it doesn't want to react. I'm still looking into it.


warnings at the tutorial example

run the simple tutorial example from here but get two warnings:
D:\ProgramData\Anaconda3\lib\site-packages\sklearn\utils\validation.py:63: DataConversionWarning: A column-vector y was passed when a 1d array was expected. Please change the shape of y to (n_samples, ), for example using ravel().
  return f(*args, **kwargs)
D:\ProgramData\Anaconda3\lib\site-packages\dowhy\causal_estimators\propensity_score_stratification_estimator.py:61: FutureWarning: Index.ravel returning ndarray is deprecated; in a future version this will return a view on self.
  weighted_outcomes.columns = ["_".join(x) for x in weighted_outcomes.columns.ravel()]

you can safely ignore both these warnings.
For sklearn, the current behavior is the same for both column vector and 1d array.
The second warning is due to an update from Pandas. I've added a PR that will fix this warning in the next release.


The nightly schedule will not be executed.
Expected behavior?
The nightly schedule should be executed. The commit message instructs GitLab to not create a pipeline for the push, but the nightly schedule should still be executed. Similarly, Drone ignore CI SKIP for tag events.
Consider the following situation:

Have a nightly pipeline schedule for the master branch. As part of your CI process, you check used dependencies for security issues (e.g. using nsp). The idea is that you will get a "failed pipeline" email when a security issue is found in one of your javascript libraries.
Make a small fix to a readme file and add [ci skip] to the commit message
Don't do any commits for a few days
No pipeline schedules for the master branch will be running, and hence you won't be notified on security issues anymore

One could argue that we do not want to run scheduled pipelines for [ci skip] commits, but then we have to run a scheduled pipeline for the last commit of that branch that is not [ci skip].

Example taken from S. Schweizer as it clearly explains the issue applicable to Drone CI

we disabled [CI SKIP] for tag events and could do the same for cron events. It makes sense to me.

this behavior was changed in b950e28dd3c6f097a4503f6f9b90b805b728fc6a and is available in the latest docker image.


IR redundancy

this might be a little confusing due to the IO usage, and the logic may be a little flawed, but this is the base implementation

closing; merged into Championship branch


AutoSuggestBox Initial Value

Is your feature request related to a problem? Please describe.
I have a use case where AutoSuggestBox is perfect in every way, except for its inability to provide an initial value.
Describe the solution you'd like
Add 'initialValue' property to the AutoSuggestBox or something analogous that makes sense.
Describe alternatives you've considered
I've tried other controls including the ComboBox, which does some of what I need...but in a perfect world I'd be able to just provide an initial value to the AutoSuggestBox.

Hi! You can use the controller property in AutoSuggestBox to set an initial value:

Awesome, thanks :) That solves it! Cheers and I appreciate all the work on this, it has been very easy to work with.


Cannot properly create "representation"

When following the step:  "Enter "application/json" into the search box and select the application/json content type."
The search fails and I cannot add the proper representation. When looking in the dev console of my browser, I see a failed network call for the content-types.json. I suspect this is related.
This makes it difficult to follow the tutorial.

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

ID: 4df5cb3a-5bb7-c6c0-dbef-9cf9b51ea264
Version Independent ID: 68e97872-e73c-83a4-6856-3705a705e23c
Content: Mock API responses with the Azure portal
Content Source: articles/api-management/mock-api-responses.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

@esunder Thank you for your feedback! We will review and update as appropriate.

Hey @esunder If you're able to consistently reproduce this issue, could you share a screenshot of the console error as well as provide info on your browser?

Hi Mike,
I am not able to reproduce the issue today. You can close.
Thanks!
On Mon, Apr 13, 2020 at 3:32 AM Mike Urnun<EMAIL_ADDRESS>wrote:

Hey @esunder https://github.com/esunder If you're able to consistently
reproduce this issue, could you share a screenshot of the console error as
well as provide info on your browser?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/52002#issuecomment-612807130,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACXK6WKOZ4UAVWLER5UO4LRMLE3PANCNFSM4MEDDXXQ
.

Glad to hear that the issue is resolved, @esunder! We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


windowWidth not picking up on media queries

I have a site where several PNG images are stacked and positioned using "transform: translate(-50%,0);" to center them in the window. Using this method for positioning, the images are getting cut off for the rendering. So, as a fix, I was going to position all of the images at one width (1500px) without using the transform property and then set the windowWidth property in html2canvas to 1500px.
The iframe is loaded at 1500px, but the styles for that width are ignored. If I set my browser window to 1500px, the rendering comes out perfect. Is there anyway to pass styles to html2canvas only? Or have the iframe pickup on the media queries, regardless of the browser width?
I am using the latest, non-minified version of html2canvas... in Safari. The site is below. The get a rendering, click the contact dealer/get price button. Use the zip code "78602" so you don't actually get contacted by a real dealer. On form completion, the rendering is made. You will get an email with the image. I also have removeContainer set to false so you can see the iframe there as well.
http://www.shallowsportx3.com

@chadlamson did you ever find the solution to this problem? I'm getting the same issue where it seems windowWidth is being ignored and it defaults to window.innerWidth

@calebwelch1 Not really. I ended up using the onclone param to make adjustments to the elements I needed for the screenshot to look right.

@chadlamson Replying so quickly to one of your two year old questions, thank you sir! I found by adding the 'x' x-crop param it seems to respect the windowWidth value. I hadn't thought of trying onclone though i'll definitely look into using that as a fix. Cheers!

@calebwelch1 No problem! Glad you got it working.


Old Apple watch support???

Is there any way to allow, even for a little bit, ability for the older watch os to be supported?
I have a gen 1, got this app, was that it had watch support.... when it wasnt on my watch i finally saw that it needs W OS 5...
I am maxed at 4.3.2...

Hey Stady234, sorry to hear about this. I checked at OctoPod relies on several things that are only available on WatchOS 5.0. Will require some effort (no idea how much) to support 4.3. I will leave this ticket opened in case someone wants to contribute a backport to older versions.

@gdombiak Hey, any chance that You have a list of WatchOS 5 features that OctoPod uses? I'd like to try to tackle this issue by either removing features or finding alternatives / workarounds.

Hi @pranelio, can't remember now which features require WOS 5. IIRC, if you try to deploy it in the simulator to a Watch OS 4.2 or older it should report which things won't compile. I will see if I can get any other info and post it back.
Thanks for your help. :)
Gaston

Any progress?  I hope it isn't too much work, but it would be nice to have!

Hey Stady,
I'm currently not working on this. It is low on  my priority list so not sure if/when will get to this ticket. If someone wants to jump and help that would be awesome. Sorry for not giving the great news. :(

Understandable.  I will keep watch of any further development.  I will close ticket, no need to have it lingering there!  Keep up the good work!


The source 'IQueryable' doesn't implement 'IAsyncEnumerable'

Given I were to add:
public async Task<IList<User>> GetAllUsersAsync(CancellationToken cancellationToken)
{
    return await this.usersContext.Users.ToListAsync(cancellationToken);
}

to the UsersService. I appear to be unable to use this package to mock the 'Users' DB set without throwing an exception:-
[Fact]
public async Task Given_ListOfUser_When_GetAllUsers_CanExecuteSuccessfully()
{
    // Arrange
    var users = Fixture.Build<User>().CreateMany();
    var usersContextMock = new Mock<UsersContext>();
    usersContextMock.Setup(x => x.Set<User>()).ReturnsDbSet(users);
    var usersService = new UsersService(usersContextMock.Object);

    // Act
    await usersService.GetAllUsersAsync(CancellationToken.None);

    // Assert
}

System.InvalidOperationException
The source 'IQueryable' doesn't implement 'IAsyncEnumerable<Moq.EntityFrameworkCore.Examples.Users.Entities.User>'. Only sources that implement 'IAsyncEnumerable' can be used for Entity Framework asynchronous operations.

You would be right to question why an entire DB set is being returned by a method, I have questioned this myself.

Hi @WheelRich
Thank you for finding this. I will look on it and think about it.


Upgrade Rust deps

@pka does it make sense to target edition 2021?

@pka does it make sense to target edition 2021?

I don't see a major advantage right now. Sometimes users ask for building with an old rustc. Especially Debian users with their packaged version, which is currently 1.48.0. So I usually wait with updating rustc requirements as long as possible.

Ok down to 2018 so deps upgrade must be the cause of the test failures

Hmm.. looks like the test failures are due to something else entirely. They seem to have started with CI run of https://github.com/flatgeobuf/flatgeobuf/commit/b08fb2c6a6a11b2b438dbbc44c416fb5e27ce5a4 which has nothing to do with Rust.

Looks like behaviour of geozero feature write has changed to not mutate geometry collections, which make sense.. and hinted by comment https://github.com/flatgeobuf/flatgeobuf/blob/6bf6d7fcfa30add6da439a0387d1835e60c93fb6/src/rust/src/feature_writer.rs#L730. @pka can you confirm?

Looks like https://github.com/flatgeobuf/flatgeobuf/pull/226 did the trick. Rebased.


MWPW-141020: [Project PEP] Implement Analytics Enablement

Description
This PR enables analytics for PEP
Related Issue
Resolves: MWPW-141020
Testing instructions

open the after test URL and wait for the PEP modal to show up
open dev tools and watch the network tab, searching for calls to https://sstats.adobe.com/ee/irl1/v1/interact
click on the X button
the request payload for searched api call should have events[0].xdm.web.webInteraction.name equal to "Close Modal|PEP Modal_Photoshop" ( see screenshots )
delete the dismissedAppPrompts cookie so that the modal will show up again on refresh
click the "Stay on this page" button
the request payload for searched api call should have events[0].xdm.web.webInteraction.name equal to "Stay on this page|PEP Modal_Photoshop" ( see screenshots )

Screenshots

Test URLs
Milo:

Before: https://project-pep--milo--adobecom.hlx.page/drafts/rbogos/pep-prompt?imsClientId=fedsmilo
After: https://mwpw-141020-pep-analytics--milo--robert-bogos.hlx.page/drafts/rbogos/pep-prompt?imsClientId=fedsmilo

Ready for STAGE
QA verified - https://jira.corp.adobe.com/browse/MWPW-141020

As per JIRA ticket, this PR is Ready for Stage, hence marking respectively.

Hey @honstar! This was actually opened against a feature branch, the code for the whole functionality is not ready for stage or production, as we're waiting for additional details. I've added this detail to the stage PR already.
It might make sense to bookmark a filter with stories ready to be merged on one of the Slack channels, such as https://github.com/adobecom/milo/pulls?q=is%3Aopen+is%3Apr+label%3A"Ready+for+Stage"+base%3Astage
As a personal opinion, I think it's the developer's job to make sure they follow all the steps to have their PR looked at by the MPoC, MPoCs should not have to sort out PRs. We should probably also come up with a rule that if something is open for more than X weeks, it automatically gets closed.
CC: @SilviuLCF


Refactor test queue

FRONTEND PULL REQUEST
Related Issue

part of #3352
this removes ui dependence on DeviceSpecimenType

Changes Proposed

Optimize the queries for loading deviceTypes and simplify code drastically
Query devices for the active facility only (huge performance boost, especially in orgs with a lot of facilities)
Fix bug related to swab not updating on the card when its updated by someone else
Fix bug where use current date is not updated on the card when its updated by someone else
Handle the case when a device is deleted from the facility but its still on the card
Handle the case when a specimen type is removed from the device but it was on the card

Additional Information

there will be followup work to remove DeviceSpecimenTypes from the backend

before
query GetFacilityQueueMultiplex($facilityId: ID!) {
    queue(facilityId: $facilityId) {
      internalId
      pregnancy
      dateAdded
      symptoms
      symptomOnset
      noSymptoms
      deviceType {
        internalId
        name
        model
        testLength
      }
      deviceSpecimenType {
        internalId
      }
      patient {
        internalId
        telephone
        birthDate
        firstName
        middleName
        lastName
        gender
        testResultDelivery
        preferredLanguage
        email
        emails
        phoneNumbers {
          type
          number
        }
      }
      results {
        disease {
          name
        }
        testResult
      }
      dateTested
      correctionStatus
      reasonForCorrection
    }
    organization {
      testingFacility {
        id
        deviceTypes {
          internalId
          name
          model
          testLength
        }
        defaultDeviceSpecimen
      }
    }
    deviceSpecimenTypes {
      internalId
      deviceType {
        internalId
        name
        testLength
        supportedDiseases {
          name
        }
      }
      specimenType {
        internalId
        name
      }
    }
  }

after
query GetFacilityQueue($facilityId: ID!) {
  queue(facilityId: $facilityId) {
    internalId
    pregnancy
    dateAdded
    symptoms
    symptomOnset
    noSymptoms
    deviceType {
      internalId
      name
      model
      testLength
    }
    specimenType {
      internalId
      name
      typeCode
    }
    patient {
      internalId
      telephone
      birthDate
      firstName
      middleName
      lastName
      gender
      testResultDelivery
      preferredLanguage
      email
      emails
      phoneNumbers {
        type
        number
      }
    }
    results {
      disease {
        name
      }
      testResult
    }
    dateTested
    correctionStatus
    reasonForCorrection
  }
  facility(id: $facilityId) {
    name
    id
    deviceTypes {
      internalId
      name
      testLength
      supportedDiseases {
        internalId
        name
        loinc
      }
      swabTypes {
        internalId
        name
        typeCode
      }
    }
  }
}

Testing

How should reviewers verify this PR?
This PR mainly affects the test queue functionality, starting/submitting a test will cover its UI interactions

Screenshots / Demos

Video demonstrating the bug (hopefully it uploads): https://watch.screencastify.com/v/EjVQ5ZemZx4nurRkx45k

thanks @emmastephenson, I was able to replicate the bug on main, but I think my changes make it more likely to reproduce, will address it here

are the storybook diffs okay? 👀 it looks like the ready indicator one is different

are the storybook diffs okay? eyes it looks like the ready indicator one is different

yeah its different, but the before and after are both wrong, I'll get rid of the "Fail On Submit" since there is no way to make it fail on initial load


Data-loss bugs with priority

Hey Firebase folks,
Running into two bugs here, one that’s causing data loss.
I’ve lost about two days to this, but in the end, have a clean codepen that demonstrates it.  Hooray!
http://codepen.io/skoczen/pen/eNdJqd
Here's the bugs:
Bug 1. The list on the left isn’t ordered by priority, even though priorities are set, and they’re sorted correctly in forge.  This is what caused my original exploration, and appears to be a bug somewhere - or, angularfire doesn't work the way the docs lead me to believe.
You can see this one by just loading the pen, and clicking reset data.  The list on the left should be sorted by priority, but isn't.
Bug 2:  This is the scary one.  The instructions to replicate are in the codepen on the right, but in short, setting data with a priority, then setting another node in the same ref in a later request strips all the priority data off unrelated nodes!
Happy to do whatever I can to debug and help out on these - our development is totally blocked on them.
Thanks!
-Steven

@skoczen
I can't reproduce the data loss you are describing, but I can help you with your sorting problem.
The issue is that you are using orderByPriority incorrectly. That returns a new ref that points to sorted data, while the initial ref remains unchanged. You can actually think of refs as immutable data structures, even though the data they reference very mutable. A ref points to a storage location, with a prescribed sorting method for it's children. Those values (referenced location and sorting) can not be changed. Instead you can create a new reference that points to a new location using .child(), or a new reference that prescribes a new sorting strategy orderByX(). So ref.child('a').child('b').orderByPriority() actually creates 3 new refs, we just discard the middle two.
In your code you do the following:
ref.orderByPriority();

But you never assign the result of orderByPriority() to anything, so you don't have access to the sorted data. What you need to do is this:
var unsorted = new Firebase('myurl');
var sorted = unsorted.orderByPriority();

This is definitely not the first time I have seen people confused by this. Perhaps the docs could cover it better, but I will leave that to the Firebase team.
Unfortunately, your issues don't end there. orderByPriority will only affect the ordering of that nodes direct children (not it's grandchildren, great-grandchildren, etc). So calling orderByPriority where you did will only affect the ordering of that nodes two children (news_feed and hearts in this case), while the sorting of the deeper nodes remains unaffected.
Also, anytime you are doing an ng-repeat, you probably want to consider using $firebaseArray
So, putting that all together, this is probably more like what you want:
var ref = new Firebase("https://buddyup-bug-explorer.firebaseio.com/users/1");
$scope.me.newsfeed = $firebaseArray(ref.child('news_feed').orderByPriority());

You would also need to update your template to point the ng-repeat directive at me.newsfeed instead of me.data. I have updated your codepen with a working example.
Also, it is hard to tell where you are headed with such a simple example, but I would advise reading the docs on structuring your data, as well as the blog post on denormalizing your data. They are hard concepts, but critically important.

Hey @jamestalmage,
Most important stuff first:
Bug 2
I'm able to replicate bug #2 by following the instructions on the right, using a fresh, incognito browser.   It happens 100% of the time.  What results are you seeing?
Bug 1 (aka confusion)
Thanks for all the info on the sorting. I'd completely misunderstood the orderByPriority, thinking that it sorted in-place.  Makes more sense this way.
I've read those docs extensively, and we've got pretty heavily denormalized data structure - the challenge has been getting sorting and updating to work in a heavily race-conditioned setup (including clients and servers racing).  As such, I've shied away from $firebaseArray, as the docs are pretty strongly against using anything that's array-like in your setup.
From what I'm seeing in your details above though, using $firebaseArray doesn't take us down the dreaded firebase array road, but is instead a convenience wrapper for the front end.
One thing I'm trying to sort through on these refs is if (and at what number) there's a performance penalty for opening up too many.  Any insights?
Thanks much!

The cool part about $firebaseArray is that it works as an object with the server, using push ids, and as an array locally, giving you the best of both worlds.
Note also that if you're just getting started, I'd discourage using priorities and work with the new query tools, based on orderByChild(), which work of fields in the record. Those are where we are headed in the future.

@katowulf - got it.  About four months in, so would prefer not to do massive changes. Is priority going away though?
@jamestalmage, here's an animated gif of the data-loss bug:

Priority will continue to be supported for existing versions of the SDK. I'm guessing it will disappear in the next major iteration of the API--possible 3.x. That's purely speculation as none of this has been hashed out yet and it's a ways down the road map. However, consider moving to orderByChild() where possible as it has more robust capabilities and will be compatible with more features in the future.

Please start by updating to AngularFire 1.1.1 as there was a bug in the loading promise, which would also affect your $bindTo promise.
Internally, and as documented, AngularFire refers to priorities using $priority, not .priority. It will tolerate .priority in data, but this does not extend to the $bindTo function, due to some limitations in how $parse and $watch work. Try setting $priority in $scope.me.data instead. That should help.

@skoczen
Whoa, That just does not happen for me. The priorities stay put (even in your codepen).
Did you try my updated one? It's using newer versions of every library. Either way, it is still weird (I do not have the problem even using the older dependencies).
What browser are you using? Looks like OSX Chrome to me (which is what I tested on). Maybe try in Incognito mode so browser extensions are not in play (long shot).

@katowulf
Thanks for the info on deprecation - will see how much work it'd take to move all of our stuff over to orderByChild.  Losing the ordering in forge is a bummer though, especially for debugging - and the fact that we can explicitly order every node, and then not have to worry about missing orderBys on all our platforms  (about 70% of the data is injected by the server, not clients) is a big bonus.
Granted that this is all subject to change, would you guess that the version that drops priority would add the ability to set a default ordering key for the entire datastore?
Gotcha on $priority - we actually set them with setPriority, and only use .priority for writes via the REST api, but was trying to get the example all in one pen, so used .priority here.  Good to know it matters.
@jamestalmage
My pen has been updated to 1.1.1. No difference.
Here's chrome incognito (gif for completeness),

And Safari.  Latest versions of both.

Firefox just in case it was webkit.

Really, really weird that it's not showing for you.  I see this on versions from 0.9.x through to 1.1.1.
I've also seen it over the past two days, trying to work out why all the priorities were being stripped off our data, how, and when. It's very, very reproducible here, and really consistent in how it behaves.
What can I do to help repo this for you and get it solved?

@katowulf as a follow up, on the trail of your .priority vs $priority, the original case that triggered finding this bug:

Nodes with .priority are set via the REST api (since it's the only way I can find to set priority via python)
Data is saved in the same ref tree, but a different branch via the client. (Bound by object via .$bindTo)
.prioritys for all data in the tree are killed.

If .$bindTo ignores all .priority values, and $bindTo just writes an entire tree, instead of checking for node changes, this could cause the problem I'm describing.  It also means .$bindTo is frighteningly, frighteningly dangerous, and should never be used on any data that contains priorities.  It also (to me) feels like a bug - using .$bindTo, to me, shouldn't delete any data that was created elsewhere.
Thoughts?

You're never going to have good luck trying to maintain priorities on nested data. $bindTo doesn't have any way to know that there are priorities on nested child nodes. It is discouraged for any sort of nested collections in the docs, as is $firebaseObject. Nested priorities on child nodes are not going to be maintained there any more than they would if you called set() on on object which has nested child nodes (which is exactly what happens internally in $firebaseObject).
By the way, this discussion is one primary and motivating factor for switching to orderByChild() and dropping priority usage.
Ideally, if you want to manage a sorted collection, you should use $firebaseArray, which is designed for this. You also shouldn't nest your lists under your user object. As they grow, you're going to see performance degrade in fetching user profiles or iterating users in a list.
// preferably, move this to its own node in Firebase instead of nesting it in the user profile
var ref = new Firebase("https://buddyup-bug-explorer.firebaseio.com/users/1/news_feed");
var feeds = $firebaseArray(ref);

Regarding the question of ordering in your dashboard, I'd go ahead and continue to set priorities in addition to setting child values for the time being, until the dashboard allows you to sort these in a more meaningful way.

OK.
I finally reproduced, I did not follow the directions (I skipped step 2).
Looking into it now.

Not fixed, but I have narrowed it down a bit further.
See: http://codepen.io/jamestalmage/pen/mJrOWo
Instead of resetting data by setting a value on scope, I reset by calling ref.set directly.
You now no longer need step 2.
Basically $firebaseObject does not read priorities for child values, but it will write priorities back to firebase if you set .priority on the scope (but not $priority). This is a weird and inconsistent behavior that should probably be addressed.
Your options for now are:

Stop using priority and use a named child value and orderByChild queries.
Denormalize your data so you are not trying to bind scope to a node with children that have priority values.
Do not bind to that parent node, but bind to all the child values individually (using $firebaseArray and $firebaseObject as appropriate). This is probably not recommended unless you know the total data stored under the entire tree is very small (prefer denormalization).

Hey @jamestalmage  and @katowulf ,
Schema & denormalized data
So in regards to denormalized data, I'd love to get some clarity as to your meanings.
From my understanding, denormalizing means keeping a copy of the data in the most user-centric location, i.e. to limit total accesses needed for the data, instead minimizing total copies on the back-end (DRY).  The issue of nesting data seems separate. (But, as we're finding on this bug, relevant.)
In this case, here's my data tree, which seems reasonably denormalized to me:
SCHEMA A
- user
    - 1  (a user's data, read and write-limited to that user only, unless otherwise specified)
        - public_profile (object, read-access to other users)
        - profile (object)
        - news_feed (object, only relevant to the user last 100 used in template)
        - buddies (object, list of ids)
        - classes (list of ids)
        - etc (similar)
- class
    - 1
        - profile

From what I can see, this is cleanly denormalized data.  Identical stories will appear in many news feeds, and users keep local lists of their classes, buddies, and similar data.  In no cases would we ever be connecting to or iterating the user or class nodes.
The goal was to reduce connections and keep the tree small - so that a single user could just bind to their user node, and be done.  In practice, this worked well, except for the deletion of .priority nodes.
@jamestalmage , your third option suggests that instead of:
var userRef = new Firebase("https://" + window.firebase_endpoint + "/users/" + $scope.me.uid + "/");
$firebaseObject(userRef).$bindTo($scope, "me");

I should:
var profileRef = new Firebase("https://" + window.firebase_endpoint + "/users/" + $scope.me.uid + "/");
$firebaseObject(profileRef).$bindTo($scope, "me.profile");

var newsRef = new Firebase("https://" + window.firebase_endpoint +  "/users/" + $scope.me.uid + "/news_feed/");
$scope.me.news_feed = $firebaseArray(newsRef.limitToFirst(100));

// etc

This is certainly doable, as long as keeping ~20 open refs doesn't create a performance problem (I could find no docs on this.)
However, I'm also hearing you use "denormalize" to mean "flat" - which suggests that this would be a better structure.
SCHEMA B
-user_1_public_profile (object, read-access to other users)
-user_1_profile (object)
-user_1_news_feed (object, only relevant to the user last 100 used in template)
-user_1_buddies (object, list of ids)
-user_1_classes (list of ids)
-user_1_etc (similar)
-class_1_profile

In this case, the bindings would be similar to my second setup, but the security rules much hairier.  The number of connections seems constant.
So, a couple of questions on best-practices:

Which of these two schemas would you recommmend, and why?
Is there a maximum number of open references we should make sure we don't exceed? We'll be largely on mobile, expecting 3g.
What is the value range for "very small" in your "total data stored under the tree is very small"?

The .priority bug
Agreed it should be addressed somehow - or at the least, a giant red warning should live with the $bindTo documents noting that it will delete all .priority values on all child nodes with any save, and should never be used with .priority.
FWIW, I'd much prefer that the problem be addressed - having simple three-way data binding where we didn't have to worry about any of that stuff was one of the big selling points on firebase for us.  Since we're already invested, we'll clearly work around, but I'd have looked harder if I knew that things like this were true for $bindTo.
Finally, thanks for your quick responses, and hashing through all of this.  It's much appreciated.

~20 open refs will be no problem. The docs make reference to being able to add "thousands of listeners", and listeners are what matter in terms of bandwidth. (aside: Creating a ref does not cause any data to be transferred. Calling ref.set(..) or ref.on(..) does.)
As for denormalization, your original schema looks fine, with the only point of concern being the newsfeed. Could you have a separate tree for newsfeed items and use a limitTo(100) query? Basically anytime you are thinking array or list, it's a candidate for denormalization.
One other note. You probably should not be using numeric id's for users/classes. Instead use ref.push to create a random id for you.

@jamestalmage thanks for the response - couple questions/clarifications.
News feed: what's the advantage of
-user

Update: I think I see what your concern was, re: news_feed, as it's spec'd out above - that I'd be binding to the parent node, which would contain the news_feed list.  The concern makes sense in that case, and it's not clear from my example that we're not doing it.
If I've read that right, all good!

Agreed it should be addressed somehow - or at the least, a giant red warning should live with the $bindTo documents noting that it will delete all .priority values on all child nodes with any save, and should never be used with .priority.

This isn't a limitation of $bindTo. The same thing will happen with any $firebaseObject when you call $save(). There is already a big yellow warning in $bindTo that tells you to be careful using this with nested data structures, a warning in the Purpose of AngularFire section that says to avoid nested collections, and a note in the description of $firebaseObject that says it is not intended for collections.
@jamestalmage don't spend a lot of time working up a PR to try and fix this. I don't want to deal with the complexities of nested collections and child priorities--that's a deep rabbit hole of trouble. Since priorities are no longer the best way to handle sorting, I'm going to close this as won't fix.
The working solution here is to avoid priorities where possible, reference collections directly instead of nesting them in synchronized objects, or to ignore me and use $extend to change the behavior to whatever you want.

@katowulf and @jamestalmage
Ok then.  FWIW, the official firebase docs (where I've spent most of my time) don't mention anything about the deprecation of priority, and the behavior in that codepen took me completely by surprise.
The angularfire documentation on $bindTo also doesn't have a yellow box, or any mention that .priority will be deleted, or anything about nesting.
I do see a yellow box on the step-by-step-guild, but it only mentions performance, not silent deletion of data.
Maybe you're referring to some different documentation out there that I don't know about?
Maybe I'm being totally unreasonable, but if a part of the system doesn't behave consistently and there's a potential for data loss, there should be warnings everywhere possible. The firebase client warns if a orderBy is being performed on a child without an index. A similar warning on nodes with nested priorities seems reasonable to me. Especially since that data will be silently deleted on any write.
I lost two days to this bug, and read every single one of the pages you've linked multiple times before creating the pen and posting this issue.  Maybe I'm just a terrible reader, but it's possible that some combination of documentation, warnings, or bugfixes could make this easier on the next person.
Your call, of course.
Thanks again for the quick and detailed responses.

I understand that you had a bad experience with this and I appreciate the effort you've put into describing the problem and troubleshooting it here. It truly is encouraging to see someone going to great lengths to troubleshoot their own issues. Your patience is also commendable. I'll add a task to review the docs and see if the messaging around nested collections can be improved.
Note that "won't fix" does not mean "you were wrong" or in any way that I don't think the behavior here could be more desirable. It means that this is a difficult topic with a great deal of complexity and I'm choosing to punt on it because I don't see the benefit as being worth the cost. Mostly because there are readily available, simple answers to this:  referencing the collection directly in your Firebase ref (avoiding nesting), using $firebaseArray for collections, and using a child field instead of a priority.

Hey @katowulf ,
I totally dig the complexity, and I've punted on many similar things in my career, for similar reasons.  I did it on will just today.  I get it.
I think there's a big road hazard here that includes data loss, and it's not adequately marked.  You both were great in understanding and communicating the scope and cause of the problem - but without your help, I'd just have concluded that firebase was broken, unreliable, and probably unhappily shifted us to different technology.
Glad to hear you're adding a task to update the docs.  In it, I'd encourage a close read-through of the two docs I linked to (the only ones I can find from the firebase site.)
I can't find anything in those docs that state that priority values will be deleted without notice when using $firebaseObject, or an example of how to re-structure data that would otherwise fall into that pattern.  Both would be helpful, to me.
I've said my piece on this one, definitely do what you think is best.
Thanks again for the responsiveness and clarity.


Can I move the display of opponents to another location?

By, say, 50/20 pixels?

Its better to make it draggable, I think.

Yes, but simple coordinate x y in ini file will be fine for me.

Yes, but simple coordinate x y in ini file will be fine for me.

I moved it a bit in the latest release and added the X offset for you in the config file

Thanks a lot but how to configure it? should i enter x20y30? Or how?

Thanks a lot but how to configure it? should i enter x20y30? Or how?

It is an X axis offset - by default it is 0 and you can set it to any integer value like 30 or -20

There is a black pixel in the upper left corner of the screen. I can move it, can I save the position of this black pixel?

There is a black pixel in the upper left corner of the screen. I can move it, can I save the position of this black pixel?
Oh I didn't know that. Currently you can't save it but what you can do is to move it to wherever you want, take a screenshot and open it in paint and measure the X distance from the left. Current default position for it is 130 so you subtract 130 from the value you've measured and put it into the X offset in config.

Ok, thanks actually it's nothing difficult to change the position every time I start the game and that's what I meant :)

Ok, thanks actually it's nothing difficult to change the position every time I start the game and that's what I meant :)

Gotta make a proper positioning functionality once I have time for that

Great idea, good luck!

For the record, I actually fixed the enemy list offset in the latest commit. The offset param from the config should work now.
I didn't make a release with the fix as it is a very minor, mb once I do the drag I'll compile one.


Wont stop processing after an announcement made with /announce command

Describe the bug
After issuing the announce command without a photo, the form pops up and takes in its values, when submitted, the processing does not stop. It has gone on for 10 minutes already.
To Reproduce
Steps to reproduce the behavior:

Use announce without a photo

Expected behavior
Expected an announcement to be made with a title and the actual announcement
Screenshots

Desktop (please complete the following information):
Linux-Ubuntu-22.04

yeh encountered this bug as well. haven't tested it but one way of fixing it is by replying with interaction reply function. so far, all messages were sent using channel .send , we could fix this bug by setting the reply to ephemeral=true and set the message to like "announcement has been made" , or something like that.

This is a bug from the discord API itself


Add support for M1 Mac

PR for #11

This PR creates a dummy docker executable to make cwl-inspector recognize a docker executable and work properly under M1 Mac environment.


Added copy icons feature & refactored Icons.astro component code

What does this PR do?
This pull request includes the following changes:

Added copy icons feature
Refactored Icons.astro component code

This PR adds a new feature and improves the code of an existing component. Specifically, it adds copy icons feature which will help user to copy icons by clicking them. It also refactors the Icons.astro component code to improve its performance and readability.
Test Plan
I tested the code with the help of npm run test it shows no error all things are clear.
Related PRs and Issues
No related PR found
Have you read the Contributing Guidelines on issues?
(Yes)

Hi @ashrafchowdury, thank you for the PR! We're reworking the way Icons work right now, and would love to have the copy feature you implemented.
I'll go ahead and merge it on another branch, so we can add our work on top of it as well. Thank you for the contribution!


Apple Search Ads has data on Dashboard but no Keyword / Campaign attribution

I was able to get Apple Search Ads to be tracked on Branch.io with the latest releases, but it seems like the Campaign and Keyword attribution for custom events still not working. As you can see in the following screenshot:

It shows Campaign unpopulated, the same thing happens for Keywords.

Tracking code
import { BranchIo } from '@ionic-native/branch-io/ngx';

@Injectable({ providedIn: 'root' })
export class TrackerService {
  constructor(private branchIo: BranchIo) {}

  track(eventName: TrackingEvent | string, options = {}) {
    this.branchIo.sendBranchEvent(event, options);
  };
}

Environment
Ionic:

   Ionic CLI                     : 6.16.3
   Ionic Framework               : @ionic/angular 5.6.10
   @angular-devkit/build-angular : 12.1.0
   @angular-devkit/schematics    : 12.1.0
   @angular/cli                  : 12.1.0
   @ionic/angular-toolkit        : 4.0.0

Cordova:

   Cordova CLI       : 10.0.0
   Cordova Platforms : android 9.1.0, ios 6.2.0
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 5.0.0, (and 20 other plugins)

Branch Libs:

  @ionic-native/branch-io": "^5.34.0"
  branch-cordova-sdk": "^4.2.4"

Utility:

   cordova-res : not installed globally
   native-run  : not installed globally

System:

   ios-deploy : 1.11.4
   NodeJS     : v14.15.5
   npm        : 7.19.1
   OS         : macOS Big Sur

@echo-branch any updates on this?


can_sam.c

I would like to ask you if someone can help me to achive CAN clock at frequencies of 20, 40 or 80 MHz. To achieve these frequencies, PMC PCK5 must select the UPLLCK (480 MHz) as source clock and divide by 24,12, or 6. PCK5 allows the system bus
and processor clock to be modified without affecting the bit rate communication. I see that UPLLCK is not selected in can_sam.c

CC: @alexanderwachter


[nice to have] Autopadding

If I understand it right, there is no autopadding for binary blobs theirs row sizes are not a multiple of aliment. Is it possible to handle that somehow cleverly?

Would you mind tell me what did you mean by the autopadding with some example? I don't understand know what did you mean correctly.

Hey, I need a couple of days to test and write an sane answer. Unfortunately I only have a few hours per week for it. In general my question is about images with arbitrary widths. How good is your algorithm with it? As I understand it, each line should be padded to fill the alignment of 8. But what if it isn't?
I wanted to made a simple small example with 3 bytes data: xFF, x00, xFF to illustrate the problem. that can be a 8x3 or 6x4 image (just as simple as possible) but got some strange results. I think the dimension here are too small to make a sane example. But may be get a feeling of that my problem is.

My last stand is, that if a line breaks somethere inside of the byte, the byte is truncated and the new line begins with the next byte. Is it possible to avoid it? Will UFBL handle it some day?

My current algorithm assumes that the input image has some padding bits at the end of each rows to make next row starts at new byte. There is 4 alignment option for now. 1, 2, 4, 8.  For 8x3, you would be able to get correct result just by using 1 as the last argument when you call the labeling function, like Labeling_BMRS_X64(dest, source, 3, 8, 1). The default value of this last parameter is 8 for X64 algorithms. That's the reason why you got the incorrect result.
For 6x4 image without padding bits, however, my algorithm cannot handle it correctly for now. Please wait a little. I'm currently generalizing my algorithms to the case with alignment 0, and most-significant-bit-first formats.

By the way, it looks like PBM images also have some padding bits at the end of each rows. (I checked some of them.) Last bits of each rows are saved at the most-significant-bits, so the padding bits are at the least-significant-area. It also saves black as bit 1, and white as bit 0.

UFBL now supports various bitonal format, including most-significant-bit first one. Please check the latest version.


remove useless lambda wraper

There is one problem: this "useless lambda" is a workaround to bypass the fact, that http_date() called on line 1807, and defined on 2962.
@defnull, what about  to lift HTTP Utilities and MISC section up to line ~200?

There is one problem: this "useless lambda" is a workaround to bypass the fact, that http_date() called on line 1807, and defined on 2962.
@defnull, what about  to lift HTTP Utilities and MISC section up to line ~200?


Transitioning the Blaze project

Continuum Analytics (now Anaconda) no longer has funding for Blaze.  The number of Blaze developers is small and not very active.  Blaze was a very ambitious project and generated some really good ideas.  Some of the ideas could continue to live on perhaps as other projects.  There are now other libraries or combinations of libraries that can mostly handle the use-cases Blaze envisioned.
Other projects where the ideas of Blaze live on include:

Dask
Numba
Ibis
Intake
xnd

We should use this thread to discuss homes for sub-parts of Blaze.  For example, datashape is used by the Plures (xnd) project and should likely live there.
Odo is still an interesting "generalized copy" command that could be re-factored to use Intake
Is there anyone else interested in picking up Blaze development or parts of the Blaze list of projects?

Quansight is willing to take up the charge of ensuring Blaze ideas have a good home (in collaboration with Anaconda).   In particular, we will want to be sure that "odo" can live on --- likely using Intake as its data-ingest API.
Also, there are some good ideas that Anaconda open-sourced that used to be called IOPro that we will continue to find a home for.
If others have opinions on this, please jump in.

As a first step, I'm going to pair down the devs associated with @blaze/dev.  If you are eager to remain a Blaze dev or assist with the transition, please let me know.

Hey, I am glad to see there is more recent interest in blaze. At Quantopian, we
are still active users of blaze, but we haven't needed to make any big changes
recently. We are maintaining the components that we use, but we don't really
have the bandwidth to support all of the backends. The backends that we use
heavily are the postgres backend, the pandas/numpy backend, and the blaze
server. In my experience, the only other backends that get much use or
maintenance are the other SQL backends, particularly MSSQL.
We use both odo and blaze as part of our user facing APIs, so we have a strong
desire to preserve backwards compatibility in those two libraries. We have also
built extensions like warp prism
that use the odo registration API. Given the relative stability of odo, if
there's a desire to make major backwards-incompatible changes to odo, we'd
prefer for those to happen in a fork (e.g. odo2) rather than in the original
repo.
If we are looking for a new home for at least blaze and odo, Quantopian would be
willing to take them. If we took over these projects we would remove the blaze
backends that are unused so that we could release a tested, stable version. If
people wanted to add them back and actually maintain them that would be great,
but we think that removing unused code would be better than leaving it there but
broken.

We could split the various blaze backends into separate respective packages. That would ease the maintenance/development of blaze. Unused backends could be allowed to go defunct without holding back the core of blaze.

This is a good idea.   I think we are looking for what would take the least
amount of work at this point.  Joe, makes a good proposal that I think we
can use to keep the Blaze org active for awhile --- but I'm also OK with
moving the Blaze and odo projects to Quantopian repositories and removing
the Blaze org.
-Travis
On Mon, Jun 4, 2018 at 11:49 PM postelrich<EMAIL_ADDRESS>wrote:

We could split the various blaze backends into separate respective
packages. That would ease the maintenance/development of blaze. Unused
backends could be allowed to go defunct without holding back the core of
blaze.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/blaze/blaze/issues/1669#issuecomment-394580702, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAPjoBLNHHmMB0uNJA2CpAfXtlAma3Gyks5t5g3vgaJpZM4T9AT_
.

My personal preference would be to leave the Blaze organization. This group could hold repos for stable core and the split out backends. We use the Quantopian github organization for many things so it would not really be possible to make other people admins, but if we just use the blaze org we could.

Fair enough.  This makes sense.
On Tue, Jun 5, 2018, 9:06 AM Joe Jevnik<EMAIL_ADDRESS>wrote:

My personal preference would be to leave the Blaze organization. This
group could hold repos for stable core and the split out backends. We use
the Quantopian github organization for many things so it would not really
be possible to make other people admins, but if we just use the blaze org
we could.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/blaze/blaze/issues/1669#issuecomment-394722119, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAPjoPSTUaJgi0dvaTPLnyr9UPpW9D1-ks5t5pBYgaJpZM4T9AT_
.

Re: the relation between Ibis and Blaze+Dask
https://github.com/ibis-project/ibis/issues/2294#issuecomment-663053479

Has there been any update on the maintenance of the project? Should it be marked as archived or something similar? (At least to warn people that approach it for the first time, try spending some time on it, and then discover that it's not maintainted)

I would recommend taking a look at Lance


improve documentation

What does this PR do?

improve documentation : make auto-refresh examples consistent with example in docs/dataviz/README.md

How should this be manually tested? (if appropriate)
Are there any related issues open?
Screenshots (if appropriate)

Travis fails, but it doesn't seem due to the changes in this pull request. Some service doesn't seem to start?

Thanks, @ruleant! Nevermind the Travis issue.. I'll get that ironed out over the weekend. Appreciate your help!


Bbox loadingstrategy with ratio

I created a function to create a bbox loadingstrategy with a ratio, similar to the bboxRatio of openlayers2.
The commit in my forked repository is:
https://github.com/simonseyock/ol3/commit/023043d95f0ca669fbbf65d301093a82a88df3ee
I still have some questions before i would create a pull request:

do i need to goog.require('ol.extent') because i want to use the ol.extent.scaleFromCenter function which is not public?
Should i rather add an assert or throw an error if ratio is smaller than 1? - Or should i leave it like that?

I created an jsfiddle to play around with this functionality:
https://jsfiddle.net/simon_seyock/qmws0nxw/4/
it just outputs 'load' if another extent is requested.

Fiddling with the fiddle I noted that also ol.extent.clone is not public.


Make DateAndTime#between taking both date and timestamp

Codecov Report

Merging #441 (1359b32) into main (64df541) will decrease coverage by 0.17%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #441      +/-   ##
============================================
- Coverage     93.95%   93.77%   -0.18%
+ Complexity     2001     1997       -4
============================================
  Files           222      222
  Lines          4019     4019
  Branches        382      382
============================================
- Hits           3776     3769       -7
- Misses          146      155       +9
+ Partials         97       95       -2

Impacted Files
Coverage Δ

...java/net/datafaker/providers/base/DateAndTime.java
89.70% <100.00%> (+2.94%)
:arrow_up:

...ker/idnumbers/pt/br/IdNumberGeneratorPtBrUtil.java
92.59% <0.00%> (-3.71%)
:arrow_down:

.../main/java/net/datafaker/service/FakerContext.java
84.61% <0.00%> (-2.57%)
:arrow_down:

.../java/net/datafaker/service/FakeValuesService.java
85.96% <0.00%> (-1.30%)
:arrow_down:

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


Add semicolon preference to formatter options

Fixes #32831
Related: #18780
Corresponding VS Code PR: https://github.com/microsoft/vscode/pull/80828
Adds a first-class formatter option for optional semicolons, with three options:

Ignore (default): Don’t touch semicolons or lackthereof.
Insert: Add a real semicolon wherever ASI would.
Remove: Remove semicolons that are optional due to ASI.

Because new and reprinted nodes must come out of the writer with semicolons by default, a setting of “Ignore” will try to pick whether to keep or remove semicolons based on the current file content. (This is the same behavior as currently exists via #31801/#32903, but uses the formatter instead of a wrapper around EmitTextWriter. The change here is that the “smart” behavior can be disabled by picking a preference in the formatter.)
I tried this out on various files in the TypeScript codebase including checker.ts, validating by swapping our ESLint semicolon rule from always to never. The formatter successfully removed all semicolons and the file was lint-free, and same for doing the reverse.

I’m starting to feel like doing this through the existing formatter/rule infrastructure was an awkwardly roundabout approach, and it would be cleaner to add some kind of “formatter preprocessors” concept where a preprocessor operates similarly to a codefix; it gets some context (selection/range/file, formatter options) and returns some TextChanges that get applied before the main formatter (which could continue to operate exclusively on whitespace) runs. (Although separate preprocessors could potentially step on each others’ toes, which could get messy. One advantage of the approach I’ve taken here is that conflicting rules trying to take effect at the same position are properly excluded.)

Update: this now removes the last semicolon from single-line object-like types (that are run through the formatter—doesn’t effect compiler emit):
- type X = { w: string; x: { y: { z: string; }; }; };
+ type X = { w: string; x: { y: { z: string } } };

(To be more specific, when the semicolon preference is “I generally like semicolons,” it removes them from synthesized nodes that get inserted and it doesn’t try to insert them into pre-existing user code on “format document.”)

Update: this now removes the last semicolon from single-line object-like types (that are run through the formatter—doesn’t effect compiler emit):

Update: Reverted this because I think it makes more sense to do this in the emitter. Will probably look at that in a separate PR later.

Update: this now removes the last semicolon from single-line object-like types (that are run through the formatter—doesn’t effect compiler emit):

Update: Reverted this because I think it makes more sense to do this in the emitter. Will probably look at that in a separate PR later.

@andrewbranch Are there any plans to make it work in the near future?

@thermarthae thanks, opened #35042 to track 👍


Feat: add peerstore

Overview
Add peerstore to go-header to be used by exchange to store good peers and alleviate the centralization that is the result of relying on bootstrappers only. This is the implementation of the decision ADR 14
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #36 (9445c4a) into main (4a93da2) will decrease coverage by 0.49%.
The diff coverage is 45.16%.

@@            Coverage Diff             @@
##             main      #36      +/-   ##
==========================================
- Coverage   66.22%   65.73%   -0.49%
==========================================
  Files          35       37       +2
  Lines        2768     2828      +60
==========================================
+ Hits         1833     1859      +26
- Misses        785      818      +33
- Partials      150      151       +1

Impacted Files
Coverage Δ

p2p/options.go
40.78% <0.00%> (-2.88%)
:arrow_down:

p2p/peerstore/peerstore.go
0.00% <0.00%> (ø)

p2p/peer_tracker.go
77.39% <86.36%> (+1.20%)
:arrow_up:

p2p/exchange.go
81.41% <100.00%> (+0.16%)
:arrow_up:

p2p/peerstore/mock.go
100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes

@derrandz don't forget to sync.MutexWrap the in mem DS in tests pls 🙏🏻

@derrandz don't forget to sync.MutexWrap the in mem DS in tests pls 🙏🏻

I think I've done so 🤔 , pls point out where I've missed doing so 🙏🏻


ValueError: Error parsing Cloudflare IUAM Javascript challenge

Looks like it is broken again.  I guess Cloudflare changed their scripts.
Screen Output
c:\>anime-dl -u ploplord -p DukePloipsalots -r 480p -rn 9 -i http://www.crunchyroll.com/twin-star-exorcists
Trying to login...
Traceback (most recent call last):
  File "anime_dl\__main__.py", line 18, in <module>
  File "anime_dl\__main__.py", line 75, in main
  File "anime_dl\AnimeDL.py", line 30, in __init__
  File "anime_dl\sites\crunchyroll.py", line 54, in __init__
  File "anime_dl\sites\crunchyroll.py", line 82, in webpagedownloader
  File "requests\sessions.py", line 521, in get
  File "site-packages\cfscrape\__init__.py", line 47, in request
  File "site-packages\cfscrape\__init__.py", line 77, in solve_cf_challenge
  File "site-packages\cfscrape\__init__.py", line 107, in solve_challenge
ValueError: Error parsing Cloudflare IUAM Javascript challenge. Cloudflare may have changed their technique, or there may be a bug in the script.

Please read https://github.com/Anorov/cloudflare-scrape#updates, then file a bug report at https://github.com/Anorov/cloudflare-scrape/issues.
[9224] Failed to execute script __main__
c:\>

Oh, I should let you know, "ploplord" and "DukePlopsalots" are not my actual login credentials.  lol

and... I found my issue.  I was testing using -rn for a single episode number instead of multiple
eg.  -rn 9
vs
eg.  -rn 9-10

I knew the syntax and have used it properly lots of times, It just seemed to make sense that this could be done with a single digit as a possibility.  Programming does not work that way.  It is an exact science.
This could be marked as resolved or enhancement (to make it so you can just use range with episode number).


Branch leti 9381 fixed lock free realization

Sorry but it is not lock-free implementation.
Lock-free list cannot be built without atomic operations.


Add BackendJob.swift to cmake build

https://github.com/apple/swift-driver/pull/101 added this file, but it wasn't added to the CMake build which I think is causing SwiftPM to fail on CI.

@swift-ci test

@DougGregor no problem, I only happened to notice it because I had another commit in the failing run and saw the email! I think SwiftPM may also need an update to handle the new Job.Kind.backend enum case.

Should we add something to the CI to do a build with CMake?


Unable to opt-out of telemetry?

Not sure if this is the right place or I understood correctly the behind the scene.
I am using VSCode and a dev container for working on a dotnet project. Everytime I rebuild the container, I see the following in the C# output. I am using both C# and C# Dev Kit extensions (which also bring .NET Install Tool and IntelliCode for C# Dev Kit).
Installing Razor Telemetry Version = 7.0.0-preview.23627.2...
Platform: linux, x86_64, name=ubuntu, version=22.04

Downloading package 'Razor Language Server Telemetry (Linux / x64)' (9128 KB).................... Done!
Validating download...
Integrity Check succeeded.
Installing package 'Razor Language Server Telemetry (Linux / x64)'

All telemetry settings I could find in my stack are set to be disabled. The environment variable DOTNET_CLI_TELEMETRY_OPTOUT: true. The VSCode settings "telemetry.telemetryLevel": "off", and "dotnetAcquisitionExtension.enableTelemetry": false.
Could you please provide insight on what telemetry is gathered and what is the configuration to opt-out of this telemetry?

@sharky98 , we understand the difference here.  We fully expect that the setting for telemetry.telemetryLevel is evaluated at the time that the Razor Language Server starts and controls the telemetry it reports.  We do 'install' the Razor telemetry subsystem opportunistically so that it would be available for the future, but the setting is passed at https://github.com/dotnet/vscode-csharp/blob/dce7766fa201690da25894856e8a44b4ea09e6d7/src/razor/src/razorLanguageServerClient.ts#L251 and should disable telemetry for Razor at that point.
Does that give you the answer you need?

Thank you. It does answer my question.
However, I don't think the download and install should be done opportunistically.

Completely agree with @sharky98
Please add an opt in setting and don't download anything that takes up space and I don't need. Thanks!

@suchja if you need to know the telemetry setting there are two ways to verify

Check the output channel for telemetry events
In the razor log we show all of the arguments used to start the LSP Server. Look for "Server arguments" in the log. Telemetry level is one of them set with "--telemetryLevel"


about the object detector FPN code

thanks for sharing code. i am very interested in your code,could you release the object detector FPN code?
thank you

Our implementation of FPN isn't based on open-source deep learning framework. You can try the code of Detectron, whose performance is indeed higher than ours.

Our implementation of FPN isn't based on open-source deep learning framework. You can try the code of Detectron (https://github.com/roytseng-tw/Detectron.pytorch/), whose performance is indeed higher than ours.


replace speed monitor with composer one

Verified that flops count is printed as the same (for 125m).
Comparison plot for old monitor (brown) to new monitor (purple). Both runs on 4 gpus on an interactive instance, so slight difference seems expected to me.

I'm going to leave the print because I think it is useful. Separately from this PR, we should probably switch over to actually using logging so the user can control the level (I think vitaliy just added a verbose flag which could be used here as well)


DRILL-6123: Limit batch size for Merge Join based on memory

Merge join limits output batch size to 32K rows irrespective of row size. This can create large batches (in terms of memory), depending upon average row width. Changed the logic to figure out output row count based on memory specified with the new outputBatchSize option and average outgoing row width. Average outgoing row width will be sum of  left and right batch row widths. Output row count will be minimum of 1 and max of 64k.
Added AbstractRecordBatchMemoryManager class to be used across all operators. Restructured the code a little bit for that.

@sachouche @ilooner @paul-rogers Can one of you review this PR for me ?

@paul-rogers Thank you very much for the review. Updated the PR with review comments taken care of. Please take a look.


Environment variable filter improvements

Refer to the single commits for further details.

Merging despite the failed Markdown links check as https://api.reuse.software/ seems to be down at the moment.


Runfo edits issues when there is no change

I noticed that Runfo will continuously edit live issues, filling up the issue edit history and making it very difficult to go back and see trends.  @viktorhofer also mentioned that this is unbounded growth the GitHub's issue storage as well.

cc @jaredpar

@ViktorHofer also mentioned that this is unbounded growth the GitHub's issue storage as well.

How do you view this? Never seen issue storage displayed anywhere before.

I noticed that Runfo will continuously edit live issues, filling up the issue edit history and making it very difficult to go back and see trends

Let me see how easy that is to fix.

Verified the fix is working

2022-08-05T02:37:14.550 [Information] Executing 'issues-update-manual' (Reason='This function was programmatically called via the host APIs.', Id=b7397ac2-d2ce-4372-adff-ac95803705d6)
2022-08-05T02:37:17.122 [Information] Updating 415
2022-08-05T02:37:19.475 [Information] No change in body, skipping update
2022-08-05T02:37:19.476 [Information] Updated https://github.com/dotnet/runtime/issues/73343
2022-08-05T02:37:19.486 [Information] Executed 'issues-update-manual' (Succeeded, Id=b7397ac2-d2ce-4372-adff-ac95803705d6, Duration=5558ms)

How do you view this? Never seen issue storage displayed anywhere before.

AFAIK there's no way to access that data but these unnecessary updates might cause storage issues eventually. We saw something similar in https://github.com/dotnet/runtime/issues/68440 which we fixed by cleaning up the old workflow runs.


replace with an empty stack fails

if you start an app (and not navigate anywhere) and use $router.replace("...") it will throw an invalid vnode error, it happens in line https://github.com/hezhongfeng/vue-page-stack/blob/0425015a1f3d0ba609f8fc434a70357260efba51/src/components/VuePageStack.js#L68 as the stack is empty. I am not sure what the expected behavious is supposed to be but maybe one can assume the initial stack is just the root or do nothing to the previous view if the stack is empty.

thanks for your feedback. I will see it soon.

当路由复用时也会因为这句代码造成问题.  replace了同个路由, 但是参数改了, 这句代码强行销毁了实例 导致页面失去响应


There are no page templates yet

The 'page templates' option on the 'Choose a page type' screen doesn't actually work yet.
Each template will probably need a custom edit view.
For example, the 'Address' template will contain multiple fields, for each line of the address - not something that the 'from scratch' edit view could do.

Closing this issue for now. This is something that is on the trello backlog (ICEBOX?) to consider later in public beta


[Wiki: transitime installation guide] Order of installation steps

Bom dia, qual é ordem correta para instalação?
Good morning, what is the correct order for installation?

Hi.
Could you write your issues in English?
What are you trying to install? Are you following the Wiki instructions for TheTransitClock/transitime or Digitransit? Please shed some light on what you're trying to accomplish and I'll see if I can help.

Hi,
I am trying to install transitime, I would like to know the installation sequence, I am following the sequence of the side menu but it seems that the steps do not match.
Thanks

The steps in the sidebar are in the correct order - prerequisite installation, compilation, creating the database, populating it with data and running everything. What is not working or what error are you getting and at what steps?

good night,
when trying to install showed the link error:
http://<IP_ADDRESS>:8080/web/
openjdk version "1.8.0_312"
OpenJDK Runtime Environment (build 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07)
OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)

Please give some details regarding at what step you're encountering the error.
Maybe attaching a screenshot would make it more clear.

There's no obvious issue in the terminal screenshots you attached.
As a friendly suggestion, switch from using the default Digitalocean console to accessing your server via SSH using a local client like Putty, that would make it easier to copy, paste and scroll through commands.
I see that you generated the schema and after that tried importing data and creating an API key. But nowhere in between these do I see the MySQL commands required for actually importing the database schema to the desired database on your server.
Have you done that? You can use the mysql command to look inside the databse and check that stuff has actually (sudo mysql -u root; USE database; SHOW TABLES;) been done. Maybe also look in the logs (in the /tmp folder according to the copy-pasted commands) or actually try running the software (core) to see if it errors out or not.


[OTHER]Picamera2 Issue

Hi,
When I ran the raw.py example in RPI, I get this error:
@python raw.py
[0:09:27.408477190] [1997]  INFO Camera camera_manager.cpp:299 libcamera v0.0.0+4186-d1dc0373
[0:09:27.410801406] [1998] ERROR V4L2 v4l2_device.cpp:352 'imx477 10-001a': Unable to set controls: Device or resource busy
[0:09:27.430604169] [1998]  WARN RPI raspberrypi.cpp:1308 Mismatch between Unicam and CamHelper for embedded data usage!
[0:09:27.431468700] [1998]  INFO RPI raspberrypi.cpp:1425 Registered camera /base/soc/i2c0mux/i2c@1/imx477@1a to Unicam device /dev/media2 and ISP device /dev/media3
[0:09:27.432893147] [1997]  INFO Camera camera.cpp:841 Pipeline handler in use by another process
Camera init sequence did not complete.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 242, in init
self._open_camera()
File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 439, in _open_camera
raise RuntimeError(f"camera.acquire() returned unexpected code: {acq_code}")
RuntimeError: camera.acquire() returned unexpected code: -16
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/pi/11.py", line 5, in
picam2 = Picamera2()
File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 249, in init
raise RuntimeError("Camera init sequence did not complete.")
RuntimeError: Camera init sequence did not complete.
pi@raspberrypi:~ $
Do you have any idea what is the issue? what process should I follow to make sure no issues will happen?
It was working well and I was trying to capture multiple images with different exposures and the error happened out of the blue. And then, none of the example files ran at all. All have the same issue.
Thanks

Thanks for the report. It's a bit hard to guess what's happened there. It seems to be unable to open the camera, possibly because something else has ended up in a state where it's holding on to it and hasn't "died" properly. I presume you've tried a reboot to see if that clears the problem?
Obviously if you can pin down what you did to make it get into this state then we'd obviously want to look into it. Thanks.

Thanks @davidplowman
I reinstalled the picamera2 and RPI and the issue solved.


Documentation Title Links Don't Work on go.googlesource.com

The package currently directs users to https://go.googlesource.com/sublime-build/+/master/docs/configuration.md to help with configuration issues.
Unfortunately GitHub and go.googlesource.com use different patterns for generating the ids used for title links. On GitHub they are all lower case and on go.googlesource.com they are capitalized.
Two options:

Rewrite links to work with go.googlesource.com, breaking GitHub
Change plugin to direct users to GitHub version of docs, keeping links on go.googlesource.com broken

I'm inclined towards option 2 since I believe more people are likely to find the package on GitHub, since that is there Package Control will link to.

Thoughts @jbuberel?

We definitely do want all links to point to the github.com version. We should not have any end-user links referring to go.googlesource.com.

https://go-review.googlesource.com/#/c/16449/