[WIP] Minor refactor on the structure of the dataformat WRT M:M data

…s it relates to other many-related models.
Summary Change Description
Changed the "manytomany" key to "manyrelated" and mostly fleshed out that sub-dict.
Affected Issue Numbers

Partially addresses  #484

Code Review Notes
Most of these changes were made by a search & replace script of mine.  Very benign changes.  Just rearranged things to make more sense when applied to other many-related models.
Checklist

[ ] All issue requirements satisfied (or no linked issues)
[x] Linting passes.
[x] Migrations created & committed (or no model changes)
[x] Tests implemented (or no code changes)

[x] New test classes/functions tagged with @tag("multi_working")

[x] All (ci-run) tests pass

[x] Test function tag @tag("multi_working") added and test class/function tags @tag("multi_broken"), @tag("multi_unknown"), or @tag("multi_mixed") removed or changed.

The pylint errors are fixed in a separate PR.

Implemented suggested changes from another PR here. Remote tests run much faster than my local runs, so going into draft to work on the errors.

Implemented suggested changes from another PR here. Remote tests run much faster than my local runs, so going into draft to work on the errors.

Yeah, I highly recommend letting tests run on GitHub instead of locally. I usually create branches and only create a PR once the tests are passing.

Implemented suggested changes from another PR here. Remote tests run much faster than my local runs, so going into draft to work on the errors.

Yeah, I highly recommend letting tests run on GitHub instead of locally. I usually create branches and only create a PR once the tests are passing.

Well, I hadn't decided where I was going to implement the PR review items from the peak group label PR. In fact, I'd forgotten about them. Decided to implement them here after I'd already created the PR.
I usually run select tests I know I need to get to work locally. And I don't like to check in changes until they work. Usually, that's enough. But in some cases, I'm not 100% sure any other tests are broken or not. Currently, it takes 15m to run tests on github and much longer locally. So if I ever feel like I need to run all, I check in and push.
This was a special case.

Most of the changes are mundane, except the model file changes.

Man, I keep misstepping with this test failure. When I pushed before ending the workday yesterday, the tests I'd run (which succeeded) didn't include the newly re-named test, which of course failed.  Fixing it now.  This should finally be ready for review shortly.


Docs: Update issue templates

Codecov Report

Merging #3 (27a599a) into dev (acac9d0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev       #3   +/-   ##
=======================================
  Coverage   75.00%   75.00%
=======================================
  Files           4        4
  Lines          28       28
=======================================
  Hits           21       21
  Misses          7        7

Continue to review full report at Codecov.

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


Service cpus limit

Specify how much of the available CPU resources a service instance can use. For example, if the host machine has two CPUs and you set cpus: 1.5, the service instance will be guaranteed to be able to access at most one and a half of the CPUs. Kontena scheduler will automatically target deployment to nodes that have at least number of specified CPUs available.

Related #2450

@jakolehm waiting for status/merge, unless you still want to address the minor comments.


ARROW-9181: [C++] Instantiate fewer templates for cast kernels

I discovered this unnecessary template instantiation by looking at the symbol sizes in object files with nm --print-size --size-sort $OBJECT_FILE. This trims about 200K from libarrow.so in release builds on Linux.

+1. There's a doxygen failure
/arrow/cpp/src/arrow/compute/api_scalar.h:51: error: The following parameter of arrow::compute::Add(const Datum &left, const Datum &right, ArithmeticOptions options=ArithmeticOptions(), ExecContext *ctx=NULLPTR) is not documented:
  parameter 'options' (warning treated as error, aborting now)
Error: `docker-compose --file /home/runner/work/arrow/arrow/docker-compose.yml run --rm conda-cpp` exited with a non-zero exit code 1, see the process log above.

The docker-compose command was invoked with the following parameters:

I'll fix this in a new PR


Initial Setup

*Creates ECR Repository
*Creates IAM policies for ECR login, read, write

Did you want to redo this one to remove the roles and policy attachments to match the s3 mod?

Did you want to redo this one to remove the roles and policy attachments to match the s3 mod?

How about you modify this for Carbon how you'd like it to be done with roles/policy and then I can work with it for canteloupe?


Add support for :nth-child selector

I have the following style tag

However the style is being added to every cell in the table, not just the odd numbered rows.
The expected result:

         Test
         Test

         Test
         Test

         Test
         Test

         Test
         Test

The actual result:

         Test
         Test

         Test
         Test

         Test
         Test

         Test
         Test

Hi, thank you for reporting. This is a bug, and I suspect nth selector caches - going to check it over the weekend

The problem is that in the previous_sibling_element / next_sibling_element implementation the logic stops if a sibling is not an element node (e.g. text or comment), but it should look until an element node occurs or no sibling node at all.

The fix is released in 0.13.0

Thanks so much for fixing this. I appreciate the incredibly quick response and fix ❤

You are very welcome! :)


Wrong resolution when opening lumina in virtualbox

Hi,
I've installed Trident in virtualbox. The VM is open in full screen mode. When I log in and open the Lumina desktop, the wallpaper doesn't cover the whole screen, only a quarter of it. The rest of the screen is black.
And the desktop panel bar is not at the bottom of the screen : it's at the bottom of where the wallpaper stops. Verticaly speaking, it's in the middle of the screen. Horizontaly, it's on the left.
Right-clicking in the black area doesn't work : no menu opens. But I can move windows there (see screenshot below).
Changing the wallpaper solves this problem ... until I close the session. When I log in again, the bug is back.
I installed Xfce (using pkg, since AppCafe doesn't seem to work) to check if this problem was due to Lumina. No such problem with Xfce. So yes, it's due to Lumina.

I tried with beta2 and beta3. Same problem in both cases.

See if this is the same issue that you have

Hi,
Today, I tried installing the Lumina desktop on vanilla FreeBSD in another VM. It worked fine, covering my whole screen. It looks like I was not entirely right when I said the problem tied to Lumina.
To sum up :
Xfce on Trident --> OK
Lumina on FreeBSD --> OK
Lumina on Trident --> Bug
I hope this helps.
Regards

Documented issue:
<URL:https://github.com/project-trident/trident-core/issues/10#issuecomment-420398501>
John
<EMAIL_ADDRESS>

Have you tried to use RC3?
the default vbox install resolution is now 1024x768

right mouse button --> Display --> APPLY/SAVE
this will on subsequent openings, open in at desired resolution
this will need to be repeated, after you upgrade


Support css preprocessors

Description
The plugin is missing support for css based languages, like sass, scss, less, stylus, etc.
Describe the solution you'd like
Based on the babel configuration file, determinate which preprocessor the project is using and provide syntax highlighting for it.

Thanks for your feedback!
We already have auto-completion for scss, thanks to this pull request #5, I don't know if it's also working for less and stylus.
Regarding syntax highlighting, indeed it's not working.
If you have any idea, how to do it, feel free to open a pull request, I would really appreciate it. 😃

Alright, I'll try to come up with something in the upcoming days :)

@Divlo I added you on discord, I have some ideas if you are up to collaborate

Success, we now support SASS since this commit : https://github.com/Divlo/vscode-styled-jsx/commit/f72ea15fbd98b1d863973ff3a41560d2b4938ffe


unZipFromFile seems to not resolve the promise

Current Situation: unZipFromFile seems not to resolve the promise.
My part of the core:
const kiaUnzip = await startKia(`Unzip ${updateZip}`);
  const result = await unZipFromFile(updateZip, ".");
  if (!result) throw new Error(`Zip Extraction failed!`);
  await kiaUnzip.succeed(`Unzipped ${updateZip}`);

  const kiaZipDelete = await startKia(`Remove ${updateZip}`);
  await Deno.remove(updateZip);
  await kiaZipDelete.succeed(`Removed ${updateZip}`);

The output:
⠧ Unzip vscode-update.zip
But it should go on and delete the update zip file.
Do you have any idea what could be wrong there?

It seems that you are using an old version, try to use the latest version and let us know if you will encounter the same problem

Thanks for looking into it!
It was an old version! For some reason I had trusted the google search to give me the newest version, but this was obviously a bad idea :D


[Question] Is it possible to remap mouse buttons in the 3D viewport?

I specifically want to swap Mouse2 and Mouse3.
I know this scheme is inspired by Blender, but it can be no secret that Blender has very odd defaults, which is also why it's a must that it can be changed in the user preferences.

There are many channels for asking question.
https://godotengine.org/community

Closing since there was no activity in this discussion for a year.


python312Packages.aiohttp-zlib-ng: 0.3.1 -> 0.3.2

Diff: https://github.com/bdraco/aiohttp-zlib-ng/compare/refs/tags/v0.3.1...v0.3.2
Changelog: https://github.com/bdraco/aiohttp-zlib-ng/blob/0.3.2/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 322845 run on x86_64-linux 1

4 packages built:

python311Packages.aiohttp-zlib-ng
python311Packages.aiohttp-zlib-ng.dist
python312Packages.aiohttp-zlib-ng
python312Packages.aiohttp-zlib-ng.dist


Issues API: Bugfixing in update and show an issue (Issue: #254)

need the iid (not the id) for show() and update().
See also:

for show: https://docs.gitlab.com/ee/api/issues.html#single-issue
for update: https://docs.gitlab.com/ee/api/issues.html#edit-issue

Thank you!


fix: Lowercase "d" in "No data" label

Asana task: ad hoc / polish
Prettier made some formatting changes. The only real change is "D" -> "d" on line 250.

[ ] Tests added?

@hannahpurcell feel free to merge when you review this, I've got notifications disabled until 3:30


 This causes issues because the new pod has trouble running if the old pod doesn't terminate in a timely manner.
I am pasting the dripline-python log after I run helm upgrade. It doesn't appear that the pod acknowledged the halt signal, and it was killed violently.
2020-06-19T22:24:30[INFO    ] dripline(86) -> python got a master config:
{'dripline': {'alerts-exchange': 'alerts', 'broker': 'rabbitmq-app.default.svc.cluster.local', 'heartbeat-interval-s': 60, 'heartbeat-routing-key': 'heartbeat', 'loop-timeout-ms': 1000, 'max-payload-size': 10000, 'message-wait-ms': 1000, 'requests-exchange': 'requests'}, 'runtime-config': {'auth_file': '/etc/rabbitmq-secret/authentications.json', 'endpoints': [{'calibration': '2*{}', 'get_on_set': True, 'initial_value': 0.75, 'log_interval': 10, 'log_on_set': True, 'module': 'KeyValueStore', 'name': 'peaches'}, {'calibration': '1.*{}', 'initial_value': 1.75, 'module': 'KeyValueStore', 'name': 'chips'}, {'calibration': '1.*{}', 'initial_value': 4, 'module': 'KeyValueStore', 'name': 'waffles'}], 'module': 'Service', 'name': 'my_store'}}
2020-06-19T22:24:30[INFO    ] dripline(99) -> service built
2020-06-19T22:24:30[INFO    ] dripline.core.entity(150) -> should start logging every 0:00:10
2020-06-19T22:24:30[INFO    ] dripline(110) -> about to start the service
2020-06-19T22:24:30[INFO    ] dripline(112) -> services started, now to listen
2020-06-19T22:24:30[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:24:40[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:24:50[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:25:00[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:25:10[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:25:20[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:25:30[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:25:40[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:25:50[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:26:00[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:26:10[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:26:20[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:26:30[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:26:40[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:26:50[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:27:00[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:27:10[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:27:20[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:27:30[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:27:40[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:27:50[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:28:00[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:28:10[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:28:20[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:28:30[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
2020-06-19T22:28:40[INFO    ] dripline.implementations.key_value_store(26) -> in K.V.S. on_get
➜  ~

The tilde is when the pod finally terminated

I believe this will be resolved in https://github.com/project8/scarab/issues/74. The issue is that ctrl+c sends SIGINT, but k8s is sending SIGTERM, which is not currently seen by the scarab signal handler.

The situation seems to have improved.

improved but still problematic somehow, or actually resolved? If not resolved, could you clarify?

I actually don't know if it's fully resolved because of this fast_daq
issue. I don't know the origin of the fast_daq issue. But it seems to be
resolved with other pods.
On Mon, Jul 12, 2021 at 10:17 AM Ben LaRoque @.***>
wrote:

improved but still problematic somehow, or actually resolved? If not
resolved, could you clarify?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/driplineorg/dripline-python/issues/109#issuecomment-878451207,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEM5I33TKIQSZFVNQIUZLKDTXMPKJANCNFSM4ODDHVSA
.

Okay, fast_daq definitely doesn't use dripline-python, the problem is very likely DAQ code not part of the dripline library.
@nsoblath do you agree (can we close this ticket? do we need another ticket somewhere else?)

There is also an opt_cmd error I got when I tried to run a muxer
configure_scan command. That feels related to this error.
On Mon, Jul 12, 2021 at 11:38 AM Ben LaRoque @.***>
wrote:

Okay, fast_daq definitely doesn't use dripline-python, the problem is very
likely DAQ code not part of the dripline library.
@nsoblath https://github.com/nsoblath do you agree (can we close this
ticket? do we need another ticket somewhere else?)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/driplineorg/dripline-python/issues/109#issuecomment-878503680,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEM5I3YNIWBEZGAMZ3RESE3TXMY5DANCNFSM4ODDHVSA
.

@raphaelcervantes is your comment about the op_cmd error related to #139?
Assuming the answer is yes, and containers running dl-python are responding to signals (INT, TERM, KILL, as is relevant), then I think we can close this issue.
I'll wait until the end of the day for any answers/objections/other ideas, and then close the issue if there's no reason to keep it open.

@nsoblath I'd have to play around with the commands to get the hone in on the possible causes of failure. Give me tonight or tomorrow.

@nsoblath Yes, that's what I was referring to. So I think it's ok to close this issue. We can open up a new one with more specific issues if need be.


Support SHA instructions in SHA-256 proof.

The SHA-256 proof should be modified so that it also works when SHA instructions are used. Because these instructions are not widely deployed, the proof should still work when they are not present.

Append related PR https://github.com/awslabs/aws-lc/pull/81


Unified Pipeline support request by Bowen Xu: PrettierCheck is failing

Reported on Service API Toolset Teams channel.

The relevant PR has since been merged. Looks like it was an issue with the PR content, not the tooling. Closing.


Extracting a form does not use input names

Is there a reason why extracting a form does not use the names or ids of the inputs for the selectors?
I have a form with named inputs and ids, but all I'm getting as selectors is:
[method] .form-check:nth-child(3) [type]

So as soon as I rearrange the inputs, these rules will break.

The reason is me being lazy.
I used a 3rd-party library that finds the optimal selector.
At least it claims to do so.
Sadly this seems to totally not work in your case. Sorry.
Prefering ids over complicated selector chains would be way better.


C code clean-up

Suggest some clean-ups to remove compiler warnings...  I applied this locally in a "c-code_clean-up" branch...
In file: SGP4.c line 245
if (fabs(xnoh - rec->nodep) > pi) {
if (rec->nodep < xnoh)
{
rec->nodep = rec->nodep + twopi;
}
else
{
rec->nodep = rec->nodep - twopi;
}
}

Thank you, MsVerina.
I was able to make a quick edit.
Feel free to fork the code and make the C version (or any language version) exactly what you want it to be.


Expose some universe vars to devtools

Shows exposed plugin states (for example route and local) in devtools state panel. At least partially closes https://github.com/prodo-ai/prodo/issues/118.
(in the below screenshot, the app has no internal state, just route)

With empty app state, we could instead show this (ignore color change):

Plugins might need to define for themselves how their state should be rendered - e.g. for the firestore plugin, I wouldn't really want to see the db_cache (but perhaps would be fine if it was just called db)

At the moment, the firestore plugin can customize it only to the extent of choosing which variables to expose (eg. call exposeUniverseVariables(["db", "db_cache"]) will expose both, whereas exposeUniverseVariables(["db"]) would keep db_cache hidden). (Neither has actually been added yet, I only added route and local so far)
Did you have in mind a custom rendering function that would filter data to a more granular level, or change how it's displayed?

@coffee-cup this should be ready for re-review :)

Some minor suggestions

Add a title above the normal state section
If there is no state have a message saying so. App state is empty possibily
Add a minimal (grey and small) indication that the state is editable but the plugin state is not

State          (editable)
{
}

Plugin State
{
}

Do these look allright to you?

Only app state, no plugin state

Both app state and plugin state

No app state (but plugin state)

I like them!


BaseConfig update for transformers>=4.22,0

What does this PR do?
This PR updates the BaseConfig class to synchronize with the updates performed on the transformers.PretrainedConfig, and fixes the issue induced by the transformers 4.22 release, breaking the current BaseConfig.push_to_hub method.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Transparency doesn't turn off

If I uncheck the transparency option the taskbar is still transparent.
Even if Transparent=0 is set.

Have you tried restarting the explorer? Also, waiting a few seconds did the job for me!

Yes sadly didn't fixed it. The only solution that worked for me was to disable and enable the transparency effect in the settings app.
https://imgur.com/sm9lbBq

Commit cfe6324b6235f85a1984b0ffb950b7d287f3c22a solves that.
There is no executable yet. But you can compile it to test.

This release includes that fix
https://github.com/vhanla/TaskbarDock/tree/v0.1.62

https://github.com/TranslucentTB/TranslucentTB
if helps


usage: what is origKey?

I want to try out the usage example in README.md. But I don't know how to set origKey. So it gives me errors: Error: First shared hypercore must be the same. or Error: Another hypercore is stored here

@ZhouHansen the origKey is the public key of the hyperdrive archive you are trying to replicate, you can find it by doing something like this...
const drive = hyperdrive('some-drive')
drive.ready(() => {
    console.log(drive.key.toString('hex')) // will print key 0e9d0dc7fb......e33adb61338

    // do replication stuff
})

when you want to replicate/clone the drive you can supply it to your new drive instance
// on new machine somewhere supply the original public key
const key = '0e9d0dc7fb79...1bd31baefe33adb61338'
const drive = hyperdrive('cloned-drive', key)

// do the replication stuff

is that helpful?

@ZhouHansen it should work on the same machine, but might need to have two directories setup. in the directory that you are replicating the drive to, is there a hyperdrive instance still stored there? if so, I'd remove it and start fresh in that directory.

I do use two directories.

@austinfrey Thanks! It works after I start another two directories, There may be a hyperdrive instance remained, because I tried this in the same directories before. But why it not clear the instance automatically..

@ZhouHansen since it could be persisting a lot of data to disk, you might not want to start a replication fresh every time, so it's nice that it doesn't delete the old hyperdrive to create a new one each time. this way you can pick up replication where you left off if you restart your client or server.


Document.enities field is unusable when using data from Classifier output

Hello,
The wrapped_document, when using document.from_batch_process_metadata (or any other methods) will be missing entities field when using data from the Classifier.
When using output of splitter, everything works fine.
But with classifier - you wont get any important information like type and confidence.
from google.cloud.documentai_toolbox import document
import os

doc = document.Document.from_document_path(os.path.join(os.path.dirname(__file__), "output-document_split.json"))
print(doc.entities)
doc = document.Document.from_document_path(os.path.join(os.path.dirname(__file__), "output-document_classify.json"))
print(doc.entities)

output-document_split.json
output-document_classify.json

Looking further at the issue:
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/dataclasses.py", line 405, in wrapper
result = user_function(self)
File "", line 3, in repr
AttributeError: 'Entity' object has no attribute 'start_page'
Both start_page and end_page need to be made Optional (since this info is not provided by the Classifier)


Fix even more unresolved doc references in material

#31931

I messed up the merge on this one. Fixing...

Re-opened as https://github.com/flutter/flutter/pull/62520.


npm package 0.2.0 has old files

I was getting Error: Property eventis deprecated, usename`` but the code seems to use the newer property. After a lot of head scratching, I checked the distributed files in the package and found the discrepancy:

Yep, it looks like we haven't published a new release in a little. Will try to get on that soon!

A few new releases have been published since this issue, including the recent 0.4.0. Thanks for the issue!


MM-47782 Stop storing compact mode profile colours in localStorage

We might've gone a bit overboard with caching these colours in localStorage. It probably takes more time to load from localStorage anyway than it would to just regenerate them, even in a worst case scenario.
@nevyangelova This might conflict with your post PR
Ticket Link
https://mattermost.atlassian.net/browse/MM-47782
Release Note
Don't persist username colours in compact mode

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/e2e-tests

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/261095

@jgilliam17 With this PR, when you're in compact mode, users' names should still keep the same colours as they did before after a refresh. We just changed it so that we're doing it without caching anything in browser storage any more.


[search] optional rng, only shuffle when present (fixes #107)

Excellent, I was going to suggest this 👍👍👍 Could you also update the find_shor example in the docs accordingly?

If rng=None and linear scan is used, shouldn't the classical number of queries also be adjusted to what the linear scan actually does?

If rng=None and linear scan is used, shouldn't the classical number of queries also be adjusted to what the linear scan actually does?

So you mean actual queries = expected queries in this case? Yeah I think that makes sense.

Yes indeed, expected = actual if there is no randomness because the linear scan algorithm is deterministic.


Grammar error

Under the header: "Copy the instrumentation key", the sentence: "You will need copy to add the instrumentation key to your application's code" needs to be revised to make more sense

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

ID: 62abe2ea-d97b-66dd-27ff-3c2bda5b6ceb
Version Independent ID: 07e29ff9-c7a0-07bf-df25-7669a080c85f
Content: Create a new Azure Application Insights resource - Azure Monitor
Content Source: articles/azure-monitor/app/create-new-resource.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@kschairer ,
Thanks for brining this to our attention. We will investigate it further and update you shortly.

Raised a PR to update the document accordingly. https://github.com/MicrosoftDocs/azure-docs-pr/pull/103990
So the doc should be updated once it is approved.
Thanks again for bringing this to our attention. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Default AEM functionality gone missing after service pack update

Required Information
Previous state (working):

[<IP_ADDRESS>] AEM Version, including Service Packs
Adobe Experience Manager (<IP_ADDRESS>)
[4.2.0] ACS AEM Commons Version: 4.2.0

Current state(Not Working):

[<IP_ADDRESS>] AEM Version, including Service Packs
Adobe Experience Manager (<IP_ADDRESS>)
Product : AEM (<IP_ADDRESS>80328)
[5.4.0] ACS AEM Commons Version: 5.4.0
[Yes] Reproducible on Latest? yes

Expected Behavior
ACS Commons functionality disappeared after AEM upgrade managed by AMS.

Actual Behavior
But Instead of that,
This is what we're seeing right now (After Service Pack update).

Steps to Reproduce
Take a stable service pack AEM version where you can see instant Package option as shown above.
Upgrade to latest AEM service pack(Version mentioned at the beginning of this ticket).
install ACS commons 5.4.0

Check for "Instant Package" button [See above Screenshot] once installation is done.

@sampath5678 has AMS provided any thoughts on why and upgrade would change existing behavior in your AEM env? It doesnt seem an upgrade should break existing custom functionality in AEM?

@davidjgonzalez, Adobe support ticket was raised and response was that ACS is not a part of AEM default functionality so AMS is not responsible to further investigate the issue.


Bug in xss_clean() creating a hex characters in a different charset

A customer entered '... 30% about...' in a textbox field on one of our submission forms. We use xss_clean() on all our input data to filter out any possible XSS injections.
An error occurred when attempting to insert the resulting text into the database (mySQL).
We tracked the offending piece of code to:
	protected function _urldecodespaces($matches)
	{
		$input    = $matches[0];
		$nospaces = preg_replace('#\s+#', '', $input);
		return ($nospaces === $input)
			? $input
			: rawurldecode($nospaces);
	}

The issue we found was that there was a rule in the xss_clean() that searched for character injections that converted into HTML strings like: '% 3 c script % 3 ealert(document.domain)% 3 c /script % 3 e'.
In this case, the '% 3 c' would ordinarily be stripped as it would be interpreted as a ‘<’ character.
However, the algorithm detected '30% about' as having a '%ab' and thus encoded it into a character which then became incompatible with the character set we are using in the database and creating an error when inserting into the database.
We have now fixed this with the patch:
$nospaces = preg_replace('#\s+#', '%20', $input);
This converts whitespaces between the '%' and subsequent hex characters to an encoded space so that '30% about' becomes '30%%20about'. This seems to solve the problem for us.
I am not an XSS expert, so if someone could provide some feedback on this, that would be much appreciated.

Duplicate of #5125. I know that's not particularly helpful, but it is what it is.
What I can suggest is that you apply xss_clean() only during output, not before saving data to your database.

Thanks for that.
After reading the discussions I think what I did will work OK.
Appreciate the response,
Simon
From: Andrey Andreev<EMAIL_ADDRESS>Sent: Tuesday, 25 February 2020 9:38 pm
To: bcit-ci/CodeIgniter<EMAIL_ADDRESS>Cc: Simon Black<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [bcit-ci/CodeIgniter] Bug in xss_clean() creating a hex characters in a different charset (#5910)
Duplicate of #5125https://github.com/bcit-ci/CodeIgniter/issues/5125. I know that's not particularly helpful, but it is what it is.
What I can suggest is that you apply xss_clean() only during output, not before saving data to your database.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/bcit-ci/CodeIgniter/issues/5910?email_source=notifications&email_token=AOS7NOQPN5DN7A7VCYLOHSLRETKGVA5CNFSM4K2SRAL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM3BVWQ#issuecomment-590748378, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOS7NOTTWMCLJBOLX73OEW3RETKGVANCNFSM4K2SRALQ.

Thank you so much for this!


Add npm support

Refer to https://github.com/playcanvas/engine/pull/832, add npm support for playcanvas.

Hey, @daredevildave, what should happen with this PR? I've seen several folks ask about npm support. Any thoughts/feelings on this?

Sorry for bumping this again. Would really like to see this happen. :)

@JarnoVgr
That's very strange. When I publish 0.220.0, it works. However, I merge 0.221.0 and publish a new version, it sucks...
I think JSDOM should be a optional deps too.

@SHADOWELITE7 NPM is a package manager for open-source JS libraries. This allows end-users for tighter integration in their existing website/app/web-game workspace.

ooh that actually is very cool, thx for letting me know about it @JarnoVgr

I would like to see this happen as well, but I am not sure this is the right way to go about it.  Ideally you would want to have something like Rollup replace the current build.  The package.json should not be generated. IMO

@JarnoVgr
I know why the 0.221.0 release miss the build/ folder now. Because I run the build process in the master brunch, and it generate package.json. When I switch to my brunch, the package.json is still in build/. When npm pack, it will ignore the folder which contains package.json.

@Tatsujinichi Do you have any idea how can we require playcanvas engine in Node.js environment?

Regarding versioning hassle, you can use npm version patch|minor|major to do the following in 1 shot:

bump the version number in package.json at the given level (patch, minor, major)
tag your branch with the version number it became

I'm trying to debug an issue right now which may or may not be a PlayCanvas bug. I'm stuck with a minified engine file, which doesn't work. If PC was properly integrating into my project via package.json (ie: via NPM), it would not minify during development and my stack traces would be so much more readable.... I think this PR would make a lot of people happy. I know it would make my life a lot easier.

@ronkorving
I think the main problem is how can pc run in Node.js environment.
This PR use jsdom as optional dependence, which will include a lot of dependencies when you run npm install @scarletsky/playcanvas.

@ronkorving You could download both minified and normal file and put them next to each other. Some IDEs auto-detect the normaal version when you include the minified one in your HTML, which should make development easier as well. However, stacktraces/sourcemaps etc. are still somewhat wrong.

@JarnoVgr Absolutely, but do you know where I can get the non-minified file?

They're in the README.md/project page.
E.g.
Non-minified: https://code.playcanvas.com/playcanvas-latest.js
Minified: https://code.playcanvas.com/playcanvas-latest.min.js

@ronkorving You can also use the non-minified version in your development, and minify it with uglifyjs by yourself.

@scarletsky It would be nice if the REST API that I use to download my project would include both the minified and non-minified versions :)

Hi everyone. Sorry it took so long to merge this. Better late than never. 😉
I'm also now wondering if we should move to rollup...

@willeastcott Do you agree with the jsdom as optional dependence ?

Also check out webpack.
On Mar 18, 2018 3:44 PM, "Will Eastcott"<EMAIL_ADDRESS>wrote:

Hi everyone. Sorry it took so long to merge this. Better late than never.
😉
I'm also now wondering if we should move to rollup...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/playcanvas/engine/pull/931#issuecomment-373976555,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEyO7cd6Gxvjl9ClfJe1OZRDvd_EqncMks5tfgI0gaJpZM4NZ_rf
.

To be honest, @scarletsky, I'm not sure about jsdom.
I just looked at rollup and webpack. Despite webpack seeming to be more popular, rollup seems to be designed specifically for building and distributing JS libraries so I feel it's probably a better fit. With rollup, you can build a library for both Node and general browser usage. It would involve quite a significant edit to the sourcebase though.

@willeastcott
Some articles say webpack is better when you build application, while rollup is good for libraries.
The PlayEngine framework also use rollup as build tool. 😃
https://github.com/scarletsky/playengine/blob/master/rollup.config.js

Hey, @scarletsky, I want to remove jsdom from the dependencies here. With some small tweaks to the engine and by creating a small script to mock the Canvas/WebGLContext objects in the browser, PlayCanvas should work just fine. I'm going to test this but so far, it seems to work fine. Let me know if you have any objections.

@willeastcott
That's a good choice. I think jsdom is useless too.
I used to add jsdom because I want to require playcanvas in Node.js.
But with bundler's help, it seems we can require playcanvas easily.
For example, in webpack, just use the following code:
// webpack.config.js
new webpack.ProvidePlugin({
    pc: ['playcanvas', 'pc']
}),

// main.js
if (process.env.NODE_ENV === 'production') {
    global.pc = pc;
}

It can inject pc to our codebase without any hack. That means umd-wrapper no longer needed. 😃

Another tips is we can add @playcanvas scope in the name field in package.json:
- "name": "playcanvas",
+ "name": "@playcanvas/engine",

Users can run npm install @playcanvas/engine instead of npm install playcanvas.
With the scope, you can also publish @playcanvas/playcanvas-gltf, @playcanvas/xxxx 😃

OK, check out this work in progress PR. I'm close to being able to create a pc.Application without needing window or navigator.
As for the name scoping, interesting idea! This work is finally leading up to me publishing the engine on npm, so deciding on a naming convention is important.


Added improvements to Main menu & Movements

👉 Checklist

Please make sure to check off the following before submitting:

[ ✅]  I have reviewed my submission thoroughly.
[ ✅]  I have tested my code (if submission is related to coding) and run the game before pushing (to make sure the project compile).
[ ✅]  I have run the JUnit tests (if submission is related to coding).
[ ✅]  I have read the Code of Conduct and Contribution Guidelines.

✍ Description of the Pull Request

Please concisely describe the changes you have made.

Made changes to the main dinosaur menu by adding the dinosaur mascot in the middle
Made changes to the Start and Quit button sizing and position
Added mute button in Main menu to pause the start up music
added WASD spaceship movement along with the existing Arrow movement
Updated the control instructions for the WASD movements

Main menu Image

🔗 Issue link

Issue reference number and link goes here e.g. 'Fixes/Closes #<issue_number>'.

[ ] This Pull Request fixes the issue : 'Closes #'
[✅ ] This Pull Request does not fix an issue.

Thanks for taking the time to fill out this Pull Request! ❤ Thanks for contributing to this project 🦖

@PrethamMuthappa Heyyyy, thank you so much for your PR !!! Great work ! Could you just check the conflicts please ? I just merged one old PR (https://github.com/dylan-power/dinosaur-exploder/pull/104). Thanks and I am sorry for the inconvenience.

@jvondermarck Heyy, I checked into the two conflicting files , I did some changes to it , I am sorry I am not much aware of the github actions and workflow , but for now I guess the conflicts have been resolved, Thanks

@PrethamMuthappa Hello, thanks for resolving the conflicts, but there are many compilation errors. Could you run & test the game before pushing your changes please ? Thanks :)

@jvondermarck  heyy, I pulled the previous changes and fixed the errors which was showing , i tested the game and it runs as intended, I have no errors or any problem while running the game , thanks :)

Thanks so much for your contribution !!! Awesome work @PrethamMuthappa !


[FEAT] fetch_client_menu - add binding for sending window back to its orignal workspace

Hi, I have very similar functionality in awesomewm to fetch_client_menu but additional to moving windows with rofi I have also biding for sending windows back. With it I can toggle every open window seamlessly no matter what monitor or tag I am on. I would love to have something similar on hyprland and I think that in general this is a very useful functionality.
My approach involves capturing the original tag/workspace of a window when it's moved using rofi. Then this stored location is used in function for sending window back to its previous tag.
Here is my code from my awesome config for inspiration:
local awful = require("awful")
local gears = require("gears")

local move_return = {}
local moved_windows = {}

function move_return.move_window()
    local cmd = "echo -e \""
    for _, c in ipairs(client.get()) do
        if c.name and c.class then
            local window_label = c.class .. "  ✰  " .. c.name
            cmd = cmd .. window_label .. "\\n"
        end
    end
    cmd = cmd .. "\" | rofi -dmenu -i -p \"Window:\" -theme ~/.config/rofi/themes/launcher.rasi"

    awful.spawn.easy_async_with_shell(cmd, function(stdout)
        local selection = stdout:gsub("\n", "")
        if selection == "" then return end

        for _, c in ipairs(client.get()) do
            if c.class .. "  ✰  " .. c.name == selection then
                local s = awful.screen.focused()
                local original_tag = c.first_tag
                c:move_to_tag(s.selected_tag)
                c:raise()
                client.focus = c
                moved_windows[c.window] = original_tag
                return
            end
        end
    end)
end

function move_return.send_window_back()
    local focused_client = client.focus
    if focused_client and moved_windows[focused_client.window] then
        local original_tag = moved_windows[focused_client.window]
        focused_client:move_to_tag(original_tag)
        moved_windows[focused_client.window] = nil

        gears.timer.delayed_call(function()
            if #awful.screen.focused().clients > 0 then
                client.focus = awful.screen.focused().clients[1]
            else
                client.focus = nil
            end
        end)
    end
end

return move_return

--[[ Keybindings

awful.key({ modkey }, "e", move_return.move_window,
	{ description = "select and move window to current tag", group = "utils" }),

awful.key({ modkey, "Shift" }, "e", move_return.send_window_back,
	{ description = "send window back to its original tag", group = "utils" }),

--]]

This looks a bit fragile, what if the user manipulates the window without using the plugin ?
It should reset I guess...
it would only work well for very controlled sequences... but maybe that's fine.
I may have a look at it but with a low priority.

If the user manipulates the window, such as moving it to another workspace without using a plugin, then I think it doesn't matter. The saved workspace location will only reset the next time using fetch-client-menu or when window is sent back. So even after manipulating the window without using the plugin, the window will still return to the same place from which it was moved, if the keybinding was used. User just won't send the window back if he doesn't need it.
Please take a look at my script that I created today and see how I implemented saving workspace of the window before moving.
This script kinda replicate dwm/awesome tags behaviour so I can very easily toggle windows from all the workspaces into the single view.
#!/bin/bash

if [ $# -eq 0 ]; then
    echo "Usage: $0 <window_class>"
    exit 1
fi

WINDOW_CLASS="$1"

STORE_FILE="$HOME/.config/hypr/.win_store"

if [ ! -f "$STORE_FILE" ]; then
    touch "$STORE_FILE"
fi

CURRENT_WORKSPACE=$(hyprctl activeworkspace -j | jq '.id')

WINDOWS_INFO=$(hyprctl -j clients | jq --arg CLASS "$WINDOW_CLASS" -c '.[] | select(.class == $CLASS)')

echo "$WINDOWS_INFO" | while IFS= read -r WINDOW; do
    WINDOW_ADDRESS=$(echo "$WINDOW" | jq -r '.address')
    WINDOW_WORKSPACE=$(echo "$WINDOW" | jq '.workspace.id')

    if grep -q "$WINDOW_ADDRESS" "$STORE_FILE"; then
        ORIGINAL_WORKSPACE=$(grep "$WINDOW_ADDRESS" "$STORE_FILE" | cut -d ' ' -f 2)
        if [ "$WINDOW_WORKSPACE" -eq "$CURRENT_WORKSPACE" ]; then
            hyprctl dispatch movetoworkspacesilent "$ORIGINAL_WORKSPACE","address:$WINDOW_ADDRESS"
            sed -i "/$WINDOW_ADDRESS/d" "$STORE_FILE"
        else
            hyprctl dispatch movetoworkspace "$CURRENT_WORKSPACE","address:$WINDOW_ADDRESS"
        fi
    else
        echo "$WINDOW_ADDRESS $WINDOW_WORKSPACE" >> "$STORE_FILE"
        hyprctl dispatch movetoworkspace "$CURRENT_WORKSPACE","address:$WINDOW_ADDRESS"
    fi
done

And my keybindings:
bind = $mainMod CTRL, 1, exec, ~/.config/hypr/scripts/toggle-window neovim
bind = $mainMod CTRL, 2, exec, ~/.config/hypr/scripts/toggle-window Brave-browser
bind = $mainMod CTRL, 3, exec, ~/.config/hypr/scripts/toggle-window VSCodium
bind = $mainMod CTRL, 4, exec, ~/.config/hypr/scripts/toggle-window discord
bind = $mainMod CTRL, 5, exec, ~/.config/hypr/scripts/toggle-window obsidian

Are you able to test the git version to see if you are happy with the "unfetch_client" command ?

Works great. Thank you


Why enter and exit fullscreen on web pause video?

When I run example/ in Android and iOS, play video and press fullscreen toggle, the video continues playing, but when I do the same in Web platform the video always pause on enter and exit fullscreen.
I noticied that on PR #810 it is call VideoPlayerController.pause() intentionally, but when I check ChewieController.isPlaying to verify if video is playing and decide continue playing or not it works.
Is there any reason to do that on Web?

i am facing the same issue on android and ios as well

+1


Tan11389/set api key on basemap

Demonstrates how a user can use both an API key and named user credentials to control which portals and resources are consumed.

Hold off on merging - we may have another sample design change incoming


Question on secure server Expires HTTP header

I read on your manual on Challenge expiration point  that is good to use Expires HTTP header to secure server.
Can I use max-age HTTP header too or work only if I use Expires HTTP header?
How many time have to use? 3 sec, 30 sec, 60 min?
best regards,
Leonardo

Hi Leonardo, currently only the Expires header is supported. The max-age is a part of the Cache-Control header but the challenge should not be cached at all, the expires header only tells the widget that the challenge expires. So if you also send Cache-Control, it should contain no-cache.
The duration depends on your use case. Normally, when using the challengeurl attribute, the challenge is computed right away, but remember, it might take some time to the user to submit the form - for example they want to change something after verification. But generally recommended duration is 1 hour.
You should also check the expiration on your server as well (you can put the timestamp to the salt and parse it on the server when received for the verification).

Thank you very much,
regards,
Leonardo


update to heredoc format

Just a thought, the yaml heredoc format seriously increases readability of the json template.
Your call if you want to merge it or just make the changes yourself, heredoc makes my OCD rest easy :)

Nice, it's definitely more readable now. Thanks.


Ability to delete a single resource (ideally by "resource name")

Is your feature request related to a problem? Please describe.
I've just run amplify delete and deleted all resources in my environment (it did warn me)
Describe the solution you'd like
What i really would have liked to do was delete a single api-gateway or storage or lambda
Describe alternatives you've considered
I ran amplify delete, but this clearly isn't what I was looking for.
Additional context
I read the docs, but maybe I missed something?

@blomm You can just an amplify remove <category followup by an amplify push to remove a specific resource from the cloud.

are you sure? it's not documented.
when you say category, do you mean 'api' or 'storage'? ideally it would prompt me which resource with the category to remove, so I don't have to remove the whole 'category'

@blomm It asks you to remove a specific resource as a part of the workflow when you run ampllify remove <category>. Optionally you can run amplify remove <category> <resource-name>

thanks @kaustavghosh06, are you able to update the cli documentation to include this information, for others in the future?


Prepare releases and packaging

To bring this project further we can start tagging releases which also potentially will make it packable for distributions. With #57 we have a solid base for future changes we can build upon.

Script adjustments

[ ] Distributions will split data files from the script. The script and distributed data files will be placed in a read only directory. We should be able to find the injector executable (data files) and make sure to write downloaded files in appropriate folders (proton.json). We should probably look into XDG_DATA_DIRS and into XDG_CACHE_HOME for these, needs some investigation. Last resort should be the same folder in case of a checkout or manually download.
[ ] We should re-evaluate our self-update part since it will probably much more frequent be a plain download or repo installation instead of a git checkout. We should also consider a way to disable this check, maybe on path detection?
[ ] Evaluate providing a file similar to proton.json for the current used ets2 and ats versions.
[ ] Set up proton as default? Maybe default to ETS2? Sane defaults for everything?
[ ] Re-evaluate if we need to close steam for updating. The related issue was closed some time ago.
[ ] Try to get the current steam user automatic or try to hook into the current/latest session.
[ ] I probably missed something…

Github adjustments

[ ] We should create a new GitHub action which will create a changelog since the last release and bundle everything up in case someone finds the release section.
[ ] Start tagging releases
[ ] Remove the binary from the repo and include it in the release tarball
[ ] Update dependencies
[ ] I probably missed something…

Evaluate providing a file similar to proton.json for the current used ets2 and ats versions.

The easiest way is to get the information from stats.truckersmp.com:
#!/usr/bin/env python3

"""
Print supported ETS2/ATS version information.

This script gets information from https://stats.truckersmp.com/
"""

import html.parser
import urllib.request

class URL:
    """URLs."""

    stats = "https://stats.truckersmp.com"

def get_supported_game_versions():
    """Get supported ETS2/ATS version information."""
    html = ""
    with urllib.request.urlopen(URL.stats) as f:
        html += f.read().decode("utf-8")

    parser = StatsHTMLParser()
    parser.feed(html)
    return parser.data

class StatsHTMLParser(html.parser.HTMLParser):
    """HTML parser for stats.truckersmp.com."""

    _data = {}
    _name = None
    _supported_elem = False

    def handle_starttag(self, tag, attrs):
        """HTML start tag handler."""
        for attr in attrs:
            if (attr[0] == "id"
                    and len(attr) == 2
                    and attr[1].endswith("supported_version")):
                self._name = attr[1][:attr[1].index("_")]

    def handle_endtag(self, tag):
        """HTML end tag handler."""
        self._name = None

    def handle_data(self, data):
        """HTML data handler."""
        if self._name:
            self._data[self._name] = data

    @property
    def data(self):
        """Return supported version information."""
        return self._data

if __name__ == "__main__":
    print(get_supported_game_versions())

$ ./print_supported_version.py
{'ets2': '<IP_ADDRESS>s', 'ats': '<IP_ADDRESS>s'}

Another way is to find the string "Expected:" from core_*mp.dll:
$ upx -d core_ets2mp.dll
$ strings core_ets2mp.dll | grep "Expected:"
Expected: ver. <IP_ADDRESS>s [rev. e0862fcae485]
$ upx -d core_atsmp.dll
$ strings core_atsmp.dll | grep "Expected:"
Expected: ver. <IP_ADDRESS>s [rev. 8de099f4740c]

In any case, I think we don't need to provide or maintain the information.

Great find! Independent of the way we're choosing to get that information I don't think we can always update to the temporary_1_36 branch. Any idea how we can decide automatically if we need to update to the temporary or the public branch?

Re-evaluate if we need to close steam for updating. The related issue was closed some time ago.

I just tried again and while steam still looses connection ~~it hasn't asked me again to log in and provide a guard code.~~and asks me to log in again. But the 0 kb downloads of all proton games aren't there anymore. Maybe we can somehow avoid loosing connection in the first place.

Try to get the current steam user automatic

We can get the latest user from loginusers.vdf and see if they're authenticated.

try to hook into the current/latest session.

It seems possible to run some commands in the steam console but "force_install_dir" isn't recognized.

Any idea how we can decide automatically if we need to update to the temporary or the public branch?

It's difficult to decide automatically, but we might be able to avoid upgrading to TruckersMP-incompatible version by checking whether "It's time to downgrade!" announcement is present. As of May 3 2020, truckersmp.com says that "TruckersMP doesn't support the latest game version of American Truck Simulator yet."

We can get the latest user from loginusers.vdf and see if they're authenticated.

We use this file for detecting Steam installation directory and we don't know the path to [Steam installation directory]/config/loginusers.vdf before logging in.
We can use our own configuration file to allow users to omit -n (--account) option.

Set up proton as default?

I think it's fine, but I don't want to drop Wine support.

Maybe default to ETS2?

Fine, I think. Number of ETS2MP players is greater than ATSMP.

get the information from stats.truckersmp.com:

"It's time to downgrade!" announcement

There's even an API, https://api.truckersmp.com/v2/version
The games version is included in the executable we can compare them and decide if a downgrade is needed.

I think that's more elegant than scraping the website.

I don't want to drop Wine support.

Me neither. I think we should provide sane defaults to everything possible so when someone doesn't know what he's doing and just runs the script the script does something and it "just works".

we don't know the path to [Steam installation directory]/config/loginusers.vdf before logging in.

The file's already present before logging in if steam was started at least once. We can test the known paths and read the file if it's found.
When the file isn't found we can abort and ask to provide the login credentials.

When I start ETS2, "<IP_ADDRESS>s (64-bit)" is displayed, but the information in PE file is currently different from this. Check your screenshot carefully, it's not "<IP_ADDRESS>" but "<IP_ADDRESS>".
I tested with Python + pefile and I got the same result:
>>> import pefile
>>> ets2 = pefile.PE("/path/to/eurotrucks2.exe", fast_load=False)
>>> ets2.FileInfo[0][0].StringTable[0].entries
{b'CompanyName': b'SCS Software', b'FileDescription': b'Euro Truck Simulator 2 - Steam', b'FileVersion': b'<IP_ADDRESS> (e0862fcae48536b292a0960b776022fd68854e62)', b'InternalName': b'eurotrucks', b'LegalCopyright': b'Copyright (C) SCS Software 2013', b'LegalTrademarks': b'Euro Truck Simulator 2 (C) SCS Software 2013', b'OriginalFilename': b'eurotrucks2.exe', b'ProductName': b'Euro Truck Simulator 2', b'ProductVersion': b'<IP_ADDRESS>'}

Can we trust this information?

Hm, fair question. I've checked for ATS and it tells me VALUE "ProductVersion",    "1.37.1" so my guess is it's somewhat recent. Since we could downgrade only to 1.36 we don't have to care about the minor versions anyway? Blocking an update is more difficult however. Maybe scraping the website for this purpose is indeed better.

Looks like we've addressed all things we've came up with.
I don't know why but I somehow feel we should get rid of the short -c option.
Anything other missing? Maybe wanna chat (steam, irc, discord, …)?

I think we're already ready to release version 0.1.0.

I don't know why but I somehow feel we should get rid of the short -c option.

I guess many users want to use DXVK (d3d11) and it's easier to specify.
I also feel something strange, but I don't feel like changing it without a solid reason.

Anything other missing? Maybe wanna chat (steam, irc, discord, …)?

Do we add a short option for --beta (e.g. -b)?
What about the desc in create_arg_parser()?

As you already know, I'm not good at communicating in English.
Especially I cannot reply quickly...

No problem, would be fine ;)
What bothers me about -c is that's only a one-time command. And the actual DX11 argument only exists in a long version. I'll propose to remove -c and add -d for --enable-d3d11.

Do we add a short option for --beta (e.g. -b)?

-b is also a good addition.

2. What about the desc in create_arg_parser()?

That's what I meant with syncing the help texts.

Whoops, I seem to have accidentally already checked the box for waiting on user input in start_with_wine() which isn't resolved yet. Discussion was in #63


core/container/context: container env vars are only passed to WASI

this commit uses the new setup_envs() method from libcontainer and brings the following changes:

the Executor trait now provides a no-op for setup_envs, which means youki is no longer changing shim process's environment variables.
the container env vars are passed down to WASI context, meaning only the Wasm modules can see container env vars.
This sets a clear boundary between shim process and wasm workloads.

Note that the wasm runtime like Wasmtime is still running on the shim process, which means they will still see shim's env vars passed down from containerd
see more details at #619
TODO:

[ ] we should document the expectations of handling env vars for shim authors using the containerd_shim_wasm::container::Engine trait

cc @kate-goldenring this PR will make the boundary between shim process and wasi context clearer. For the spin shim configuration as described by 003-skips, I think what we need to do

call ctx.envs() to get a list of container env vars
take out spin execution vars like SPIN_APPLICATION_VARIABLE_PREFIX and use the to configure spin runtime
for the rest of vars, prefix with SPIN_VARIABLE to make them Spin application variables.

the nice thing is you no longer need to invoke process's env::var and env::set_var.

This benchmark CI failure is strange, not related to the changes I made and I even can't reproduce in my local...

the nice thing is you no longer need to invoke process's env::var and env::set_var.

@Mossaka, the Spin environment variables provider for application variables dynamically looks at the process env for SPIN_VARIABLE_ prefixed items. So we need to prefix the env vars and then reset them in the execution environment. I do think we will still need to use env::set_var unless we change the provider to support a static list of values

the nice thing is you no longer need to invoke process's env::var and env::set_var.

@Mossaka, the Spin environment variables provider for application variables dynamically looks at the process env for SPIN_VARIABLE_ prefixed items. So we need to prefix the env vars and then reset them in the execution environment. I do think we will still need to use env::set_var unless we change the provider to support a static list of values

I should clarify, after this PR merges, the container env vars should be in ctx.envs(). env::var() only gives you env vars from the shim process, which come from containerd, instead of the OCI spec. What you really want for the application variables are these from the OCI spec, IIUC.

What you really want for the application variables are these from the OCI spec, IIUC.

I agree that these are the ones we want. But i am pointing out that the env var provider is tightly tied to the assumption that it gets the application variables from it's environment (using env::var).

Can we somehow declare all the vars in ctx.envs() minus execution variables are Spin application variables?

We will need to update the env var provider to not fetch application variables from the environment rather from a different method. See here how the current provider references the environment for the application var:
https://github.com/fermyon/spin/blob/c4d6f456d51419296a6cae05722d66639dfbd7f6/crates/factor-variables/src/spin_cli/env.rs#L33-L34

i am pointing out that the env var provider is tightly tied to the assumption that it gets the application variables from it's environment (using env::var)

I see. If that's the case, I have no problem with calling env::set_var() to get them into the shim process. This will be called from shim's run_wasi method which the spin shim can decide what are app vars and what are execution vars since it can see both the shim process's vars and OCI spec vars.

I see. If that's the case, I have no problem with calling env::set_var() to get them into the shim process.

Sounds good. That is an easy start -- just get the vars from ctx.envs() first. If we find it to be odd behavior, we can refactor the provider in the future

Thanks, @Mossaka !


Question about your teaser image.

Hello,
I have a question with mpview.
I used mpview with your dataset.
But, I couldn't seen any scene like in your teaser image(exactly semantic panoramas).
what can i do to get panorama semantic images?
+) Is there any 2D object semantic data in matterport dataset? I couldn't find.
Thank you.

I have the same question
@yellowjs0304 did you find a solution or did you get around to how to obtain that data from the information available?
Many thanks!

@freddifederica Nope, I didn't get any info about it.

Hi, could you pls tell me how to use the mpview to output semantic images? (I have successfully compiled the c++ code)
I'm really confused about it.

the same confusion

The same query

The same query

Have you solve this problem? About the semantic panorama?
Thanks a lot!


Game logic

:heavy_check_mark: Change the logic of the game applying new classes
:heavy_check_mark: Adapted the original main to use the new classes
:heavy_check_mark: Refactor come of the function according to stickler recommendation of complexity factor

:heavy_check_mark: Remove inline comments following the recomendation
:heavy_check_mark: Remove print/puts/gets from clases
:heavy_check_mark: Fix Draw game after 9 moves
:heavy_check_mark: Refactor functions applying DRY rule

Hi team ! Very nice project! :wave:
You did a great job, approved  :+1:

NOTE the game asks the player to select from available moves and your board at first should be empty, please delete your default numbers from the board.

Go and merge to develop.
Goodluck in your last milestone Happy coding


On Using Prebuilt docker image

Hi,  I want to pull prebuilt docker image,
When I use the command  ./run.sh, the problem is:
bash: /home/apollo_ros_bridge/ros_pkgs/devel/setup.bash: No such file or directory
May I ask the solution to it?

That is normal since the Ros packages haven't been built in the shipped docker image. Once inside the Apollo Ros bridge docker, run catkin build for the workspace ros_pkgs. This should generate the setup.bash in the devel folder.


'flutter run -d linux' fails with "undefined reference to<EMAIL_ADDRESS>

Steps to Reproduce
$ flutter run -d linux
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
[  +73 ms] executing: [/home/lordtiva/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1
--pretty=format:%H
[  +19 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 8bd2e6585b0eda5ccdc10c1e1d35105e11f84424
[        ] executing: [/home/lordtiva/snap/flutter/common/flutter/] git tag --contains HEAD
[ +114 ms] Exit code 0 from: git tag --contains HEAD
[   +1 ms] executing: [/home/lordtiva/snap/flutter/common/flutter/] git describe --match *.*.*-*.*.pre --first-parent
--long --tags
[   +8 ms] Exit code 0 from: git describe --match *.*.*-*.*.pre --first-parent --long --tags
[        ] 1.20.0-7.0.pre-57-g8bd2e6585
[   +4 ms] executing: [/home/lordtiva/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] executing: [/home/lordtiva/snap/flutter/common/flutter/] git ls-remote --get-url origin
[   +2 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +25 ms] executing: [/home/lordtiva/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] master
[  +23 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[   +6 ms] executing: /home/lordtiva/Android/Sdk/platform-tools/adb devices -l
[  +21 ms] List of devices attached
[   +6 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +4 ms] executing: unzip -t -qq
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64/linux-x64-flutter-gtk.zip
[   +3 ms] Downloading linux-x64/linux-x64-flutter-gtk tools...
[   +5 ms] Downloading:
https://storage.googleapis.com/flutter_infra/flutter/9b3e3410f02681e446ca48038164a553ababb143/linux-x64/linux-x64-flutt
er-gtk.zip
[ +786 ms] Received response from server, collecting bytes...
[+3041 ms] Downloading linux-x64/linux-x64-flutter-gtk tools... (completed in 3,8s)
[        ] executing: unzip -o -q
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64/linux-x64-flutter-gtk.zip -d
/home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64
[ +695 ms] Exit code 0 from: unzip -o -q
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64/linux-x64-flutter-gtk.zip -d
/home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64
[  +13 ms] executing: unzip -t -qq
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64-profile/linux-x64-flutter-gtk.zip
[   +3 ms] Downloading linux-x64-profile/linux-x64-flutter-gtk tools...
[        ] Downloading:
https://storage.googleapis.com/flutter_infra/flutter/9b3e3410f02681e446ca48038164a553ababb143/linux-x64-profile/linux-x
64-flutter-gtk.zip
[ +355 ms] Received response from server, collecting bytes...
[+1925 ms] Downloading linux-x64-profile/linux-x64-flutter-gtk tools... (completed in 2,3s)
[        ] executing: unzip -o -q
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64-profile/linux-x64-flutter-gtk.zip -d
/home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64-profile
[ +428 ms] Exit code 0 from: unzip -o -q
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64-profile/linux-x64-flutter-gtk.zip -d
/home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64-profile
[   +9 ms] executing: unzip -t -qq
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64-release/linux-x64-flutter-gtk.zip
[   +4 ms] Downloading linux-x64-release/linux-x64-flutter-gtk tools...
[        ] Downloading:
https://storage.googleapis.com/flutter_infra/flutter/9b3e3410f02681e446ca48038164a553ababb143/linux-x64-release/linux-x
64-flutter-gtk.zip
[ +697 ms] Received response from server, collecting bytes...
[+1519 ms] Downloading linux-x64-release/linux-x64-flutter-gtk tools... (completed in 2,2s)
[        ] executing: unzip -o -q
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64-release/linux-x64-flutter-gtk.zip -d
/home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64-release
[ +344 ms] Exit code 0 from: unzip -o -q
/home/lordtiva/snap/flutter/common/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/9b3e3410f0
2681e446ca48038164a553ababb143/linux-x64-release/linux-x64-flutter-gtk.zip -d
/home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64-release
[  +17 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +109 ms] Generating
/home/lordtiva/counter/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +42 ms] Starting incremental build...
[   +1 ms] Initializing file store
[   +6 ms] Skipping target: gen_localizations
[   +3 ms] complete
[   +2 ms] Launching lib/main.dart on Linux in debug mode...
[   +3 ms] /home/lordtiva/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot
--sdk-root /home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/
--incremental --target=flutter --debugger-module-names --experimental-emit-debug-metadata
-Ddart.developer.causal_async_stacks=true --output-dill /tmp/flutter_tools.SVBROU/flutter_tool.FNWWTX/app.dill
--packages .packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avo
id-closure-call-instructions --enable-asserts --track-widget-creation --filesystem-scheme org-dartlang-root
--initialize-from-dill build/cache.dill.track.dill
[   +9 ms] Building Linux application...
[   +6 ms] <- compile package:counter/main.dart
[   +2 ms] executing: [build/linux/debug/] cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug /home/lordtiva/counter/linux
[  +90 ms] -- The CXX compiler identification is Clang 6.0.0
[   +2 ms] -- Check for working CXX compiler: /snap/flutter/21/usr/bin/clang++
[  +47 ms] -- Check for working CXX compiler: /snap/flutter/21/usr/bin/clang++ -- works
[        ] -- Detecting CXX compiler ABI info
[  +48 ms] -- Detecting CXX compiler ABI info - done
[   +2 ms] -- Detecting CXX compile features
[ +229 ms] -- Detecting CXX compile features - done
[   +3 ms] -- Found PkgConfig: /snap/flutter/21/usr/bin/pkg-config (found version "0.29.1")
[        ] -- Checking for module 'gtk+-3.0'
[   +9 ms] --   Found gtk+-3.0, version 3.22.30
[  +39 ms] -- Checking for module 'glib-2.0'
[   +7 ms] --   Found glib-2.0, version 2.56.4
[  +19 ms] -- Checking for module 'gio-2.0'
[   +7 ms] --   Found gio-2.0, version 2.56.4
[  +25 ms] -- Configuring done
[   +4 ms] -- Generating done
[        ] -- Build files have been written to: /home/lordtiva/counter/build/linux/debug
[   +2 ms] executing: ninja -C build/linux/debug install
[   +5 ms] ninja: Entering directory `build/linux/debug'
[+6064 ms] [1/6] Generating /home/lordtiva/counter/linux/flutter/ephemeral/libflutter_linux_gtk.so,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_basic_message_channel.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_binary_codec.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_binary_messenger.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_dart_project.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_engine.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_json_message_codec.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_json_method_codec.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_message_codec.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_method_call.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_method_channel.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_method_codec.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_method_response.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_plugin_registrar.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_plugin_registry.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_standard_message_codec.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_standard_method_codec.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_string_codec.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_value.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/fl_view.h,
/home/lordtiva/counter/linux/flutter/ephemeral/flutter_linux/flutter_linux.h, _phony_
[   +1 ms] [  +73 ms] executing: [/home/lordtiva/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1
--pretty=format:%H
[        ] [  +17 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [        ] 8bd2e6585b0eda5ccdc10c1e1d35105e11f84424
[        ] [        ] executing: [/home/lordtiva/snap/flutter/common/flutter/] git tag --contains HEAD
[        ] [ +118 ms] Exit code 0 from: git tag --contains HEAD
[        ] [   +1 ms] executing: [/home/lordtiva/snap/flutter/common/flutter/] git describe --match *.*.*-*.*.pre
--first-parent --long --tags
[        ] [   +8 ms] Exit code 0 from: git describe --match *.*.*-*.*.pre --first-parent --long --tags
[        ] [        ] 1.20.0-7.0.pre-57-g8bd2e6585
[        ] [   +5 ms] executing: [/home/lordtiva/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic
@{u}
[        ] [   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] [        ] origin/master
[        ] [        ] executing: [/home/lordtiva/snap/flutter/common/flutter/] git ls-remote --get-url origin
[        ] [   +1 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] [        ] https://github.com/flutter/flutter.git
[        ] [  +24 ms] executing: [/home/lordtiva/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[        ] [   +2 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] [        ] master
[        ] [  +23 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] [   +3 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ] [  +60 ms] Initializing file store
[        ] [   +9 ms] Skipping target: gen_localizations
[        ] [        ] unpack_linux: Starting due to {}
[        ] [  +50 ms] unpack_linux: Complete
[        ] [  +11 ms] kernel_snapshot: Starting due to {}
[        ] [  +17 ms] /home/lordtiva/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot
--sdk-root /home/lordtiva/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/
--target=flutter -Ddart.developer.causal_async_stacks=true -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avo
id-closure-call-instructions --enable-asserts --track-widget-creation --packages /home/lordtiva/counter/.packages
--output-dill /home/lordtiva/counter/.dart_tool/flutter_build/fdebf48d398ff59ebf28195c733943d8/app.dill --depfile
/home/lordtiva/counter/.dart_tool/flutter_build/fdebf48d398ff59ebf28195c733943d8/kernel_snapshot.d
package:counter/main.dart
[        ] [+4279 ms] kernel_snapshot: Complete
[        ] [ +356 ms] debug_bundle_linux_assets: Starting due to {}
[        ] [  +71 ms] debug_bundle_linux_assets: Complete
[        ] [ +419 ms] Persisting file store
[        ] [   +4 ms] Done persisting file store
[        ] [   +3 ms] build succeeded.
[        ] [   +4 ms] "flutter assemble" took 5.303ms.
[        ] [ +148 ms] ensureAnalyticsSent: 146ms
[        ] [   +1 ms] Running shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [        ] exiting with code 0
[ +301 ms] [2/6] Building CXX object CMakeFiles/counter.dir/flutter/generated_plugin_registrant.cc.o
[   +4 ms] [3/6] Building CXX object CMakeFiles/counter.dir/main.cc.o
[   +7 ms] [4/6] Building CXX object CMakeFiles/counter.dir/my_application.cc.o
[  +58 ms] [5/6] Linking CXX executable counter
[        ] FAILED: counter
[        ] : && /snap/flutter/21/usr/bin/clang++  -g  -L/snap/flutter/21/usr/lib/gcc/x86_64-linux-gnu/8
-L/snap/flutter/21/usr/lib/x86_64-linux-gnu -L/snap/flutter/21/usr/lib/ CMakeFiles/counter.dir/main.cc.o
CMakeFiles/counter.dir/my_application.cc.o CMakeFiles/counter.dir/flutter/generated_plugin_registrant.cc.o  -o counter
-L/home/lordtiva/counter/linux/flutter/ephemeral -Wl,-rpath,/home/lordtiva/counter/linux/flutter/ephemeral:
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libgtk-3.so /snap/flutter/current/usr/lib/x86_64-linux-gnu/libgdk-3.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libpango-1.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libatk-1.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libcairo-gobject.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libcairo.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so -lflutter_linux_gtk
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libgio-2.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libgobject-2.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libglib-2.0.so && :
[        ] //lib64/libblkid.so.1: undefined reference to<EMAIL_ADDRESS>[        ] clang: error: linker command failed with exit code 1 (use -v to see invocation)
[        ] ninja: build stopped: subcommand failed.
[   +1 ms] Building Linux application... (completed in 7,0s)
[        ] Exception: Build process failed
[   +1 ms] "flutter run" took 17.087ms.
[   +2 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:591:7)
           <asynchronous suspension>
           #2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:860:18)
           #3      _rootRunUnary (dart:async/zone.dart:1198:47)
           #4      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #5      _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #7      Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #8      Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
           #10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
           #11     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
           #12     _rootRunUnary (dart:async/zone.dart:1198:47)
           #13     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
           #14     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
           #15     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
           #16     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
           #17     Future._completeWithValue (dart:async/future_impl.dart:529:5)
           #18     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:567:7)
           #19     _rootRun (dart:async/zone.dart:1190:13)
           #20     _CustomZone.run (dart:async/zone.dart:1093:19)
           #21     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
           #22     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1037:23)
           #23     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #24     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #25     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
           #26     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

[ +152 ms] ensureAnalyticsSent: 151ms
[   +3 ms] Running shutdown hooks
[        ] Shutdown hook priority 4
[   +7 ms] Shutdown hooks complete
[   +1 ms] exiting with code 1

$ flutter analyze
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
Analyzing counter...
No issues found! (ran in 5.5s)

$ flutter doctor -v
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
[✓] Flutter (Channel master, 1.20.0-8.0.pre.57, on Linux, locale es_ES.UTF-8)
    • Flutter version 1.20.0-8.0.pre.57 at /home/lordchelo/snap/flutter/common/flutter
    • Framework revision 8bd2e6585b (hace 23 horas), 2020-07-11 12:15:19 -0700
    • Engine revision 9b3e3410f0
    • Dart version 2.9.0 (build 2.9.0-21.0.dev 06cb010247)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /home/lordchelo/Android/Sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /var/lib/snapd/snap/android-studio/90/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
    • cmake version 3.10.2
    • ninja version 1.8.2
    • pkg-config version 0.29.1

[✓] Android Studio (version 4.0)
    • Android Studio at /var/lib/snapd/snap/android-studio/90/android-studio
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.47.0)
    • VS Code at /usr/share/code
    • Flutter extension version 3.12.2

[✓] Connected device (3 available)
    • Linux (desktop)  • linux      • linux-x64      • Linux
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 83.0.4103.116

• No issues found!

Running on Fedora Workstation 32
$ uname -a Linux fedora-lan 5.7.8-200.fc32.x86_64 #1 SMP Thu Jul 9 14:34:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Failure is:
 FAILED: counter
[        ] : && /snap/flutter/21/usr/bin/clang++  -g  -L/snap/flutter/21/usr/lib/gcc/x86_64-linux-gnu/8
-L/snap/flutter/21/usr/lib/x86_64-linux-gnu -L/snap/flutter/21/usr/lib/ CMakeFiles/counter.dir/main.cc.o
CMakeFiles/counter.dir/my_application.cc.o CMakeFiles/counter.dir/flutter/generated_plugin_registrant.cc.o  -o counter
-L/home/lordtiva/counter/linux/flutter/ephemeral -Wl,-rpath,/home/lordtiva/counter/linux/flutter/ephemeral:
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libgtk-3.so /snap/flutter/current/usr/lib/x86_64-linux-gnu/libgdk-3.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libpango-1.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libatk-1.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libcairo-gobject.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libcairo.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so -lflutter_linux_gtk
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libgio-2.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libgobject-2.0.so
/snap/flutter/current/usr/lib/x86_64-linux-gnu/libglib-2.0.so && :
[        ] //lib64/libblkid.so.1: undefined reference to<EMAIL_ADDRESS>

cc @csells

@robert-ancell Thoughts on this build failure? Are we under-specifying our required library versions?

you can run : strings /lib64/libc.so.6 |grep GLIBC_
to Confirm whether it has been installed if not you may install it first
you can download from http://www.gnu.org/software/libc/

@yzg-github I have glibc 2.31 installed on my system

I just noticed that this (and the duplicate just filed) appear to be using the snap-based install. @kenvandine is there something missing from the image?

@MarcusTomlinson can you take a look at this?  I had tested this on Fedora 31 last month and it built fine, but now I can reproduce this.  I tried adding libblkid1 to the stage-snaps and it still fails.

Still waiting on https://github.com/flutter/flutter/pull/62979.


Update the digest to work with the latest imaging processing status file

nipoppy track now produces files like this
participant_id	bids_participant_id	session_id	bids_session_id	pipeline_name	pipeline_version	pipeline_step	status
001	sub-001	A	ses-A	pipeline1	0.1.0	step1	FAIL
001	sub-001	A	ses-A	pipeline1	0.1.0	step2	INCOMPLETE
001	sub-001	A	ses-A	pipeline1	0.2.0	default	SUCCESS
001	sub-001	A	ses-A	pipeline2	1.0.0	default	SUCCESS
001	sub-001	B	ses-B	pipeline2	1.0.0	default	UNAVAILABLE
002	sub-002	A	ses-A	pipeline1	0.2.0	default	SUCCESS
002	sub-002	A	ses-A	pipeline2	1.0.0	default	SUCCESS
002	sub-002	B	ses-B	pipeline2	1.0.0	default	SUCCESS

which is no longer compatible with the format expected by the digest.
Not sure how much work it would be to do the update but it would be nice to have it working with the latest Nipoppy format. Though I guess that will break things for NIMHANS if they are using the digest right now @nikhil153?

Note: This issue (PR #166) also requires regenerating and updating the internal paths to the 'pre-loaded' QPN imaging and phenotypic digests, previously expected to be at a path nipoppy-qpn/nipoppy/digest in the nipoppy-qpn repo. Now that this repo is deprecated and split into qpn_workflows and qpn_analysis, we should choose a location (maybe qpn_workflows/digest or qpn_workflows/tabular/digest?) to store the two digest files.
The QPN imaging and phenotypic digests should be regenerated to align with the latest digest schemas (which now should be aligned with the latest Nipoppy schema), including:

imaging digest: TSV with columns as defined in https://nipoppy.readthedocs.io/en/latest/schemas/index.html#imaging-bagel-file
phenotypic digest: TSV with columns as defined in https://github.com/neurobagel/digest/blob/update-proc-status-file-parsing/schemas/phenotypic_digest_schema.json

the main change is just the renaming of bids_id -> bids_participant_id, and session -> session_id, since digest relies on the same set of identifier columns across input files


Regex Matcher

Hi team,
Can any help me on that regex macher part how it work if we apply regex on the document and after processing where we will get that particular applied regex result?
Example -
Suppose we only want to extract the Phone no and Email id instead of whole data.

Hello,
You have to pass the regex in the configuration file for example:
config.cleaner[16][1].queries = [
{
    label: "phone number",
    regex: "[regex]"
      }
];

Then in the parsr response file you can get result in the metadata part

Thanks jordi, the above issue has been resolved.


Add transfertokens Extended RPC method

What current issue(s) does this address, or what feature is it adding?

Adds the transfertokens RPC method and tests

allows the user to easily transfer NEP5 tokens

How did you solve this problem?
Trial and Error
How did you make sure your solution works?
Unittest and personal testing on privatnet
Are there any special changes in the code that we should be aware of?
No
Please check the following, if applicable:

[x] Did you add any tests?
[x] Did you run make lint?
[x] Did you run make test?
[x] Are you making a PR to a feature branch or development rather than master?
[x] Did you add an entry to CHANGELOG.rst? (if not, please do)

Coverage increased (+0.1%) to 82.169% when pulling 658cde52e01ff985032e75343ee402cbe83ff516 on jseagrave21:transfertokens into fd5e1d928cd3860839f93b7a9c757779e1b82ada on CityOfZion:development.

Another option I could use instead of adding a verbose input would be to make all the print statements into exceptions. Then these exceptions would actually be visible via RPC response, I think. This would mean updating the tests but that would be too hard.
What do you think @ixje @localhuman ?

With the merging of #756 I'm going to close this and suggest to implement this as plugin in https://github.com/ixje/neopython-extended-rpc-server/ .


Adding commands for checks 117 and 118

Context
Recent update to AWSCLIv2 allows for account contact information to be collected
Description
Adding code to existing checks to make this possible
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Good to see you here JJ, thanks for your contribution!

Hey Toni! Just a small contribution. Be Well bud!


[packages/template][s]: add author display and blog layout component

Changes

added blog layout component
added authors type in contentlayer

Notes

Currently a default author will be given to all pages, if we only want eg. blog posts to receive author data as props, we could use a conditional in [[...slug]].jsx to only do this for blog posts
closes #239

@PhilippeduPreez can you please check why the checks are failing? :)

@olayway >there are also authors missing in the blogs list. If you mean the blog index page, I didn't see authors in the examples we drew inspiration from, so only displayed them in the actual blog post

After a looong debugging I've managed to make the tests from the blog.spec pass. It seems that when there is no search property set in the user config blog pages will show the following error, but no idea why only on blog pages... I'll continue working on it tomorrow morning.

After a looong debugging I've managed to make the tests from the blog.spec pass. It seems that when there is no search property set in the user config blog pages will show the following error, but no idea why only on blog pages... I'll continue working on it tomorrow morning.

It seems this is somehow related to blog layout and importing allAuthors from contentlayer, as replacing the import with just const allAuthors = [] seems to "fix" the issue. But I have no idea why and how these two things are related...


"n_jobs" doesn't work well

Hi, I just wanted to report an issue about n_jobs. Note I am using version 1.0.0. I am not quite sure if it is still an issue for the latest version.

The n_jobs parameter for automl.predict() appears to be non-functional.

The n_jobs=-1 parameter for automl.model.estimator.predict() seems use only 1 core

I just tried the lightgbm notebook example and all the cores are used in prediction time. Could you share your notebook?

I just tried the lightgbm notebook example and all the cores are used in prediction time. Could you share your notebook?

I found the problem now. automl.predict() uses all the cores but automl.model.estimator.predict(n_jobs=-1) doesn't. Thanks!

But you can see there is no difference between n_jobs for automl.predict()

But you can see there is no difference between n_jobs for automl.predict() @sonichi

Yes, that's an easy-to-fix problem:
https://github.com/microsoft/FLAML/blob/a64956a7c8f98db6a7de7e8cc5d0ce53e9c86a03/flaml/model.py#L257
should pass **kwargs to predict()
Would you like to make a PR?

There are more places like this to update, e.g.,
https://github.com/microsoft/FLAML/blob/a64956a7c8f98db6a7de7e8cc5d0ce53e9c86a03/flaml/model.py#L280
https://github.com/microsoft/FLAML/blob/a64956a7c8f98db6a7de7e8cc5d0ce53e9c86a03/flaml/model.py#L1324
https://github.com/microsoft/FLAML/blob/a64956a7c8f98db6a7de7e8cc5d0ce53e9c86a03/flaml/model.py#L2134

Thanks! Sure. I just made a PR.


Reduce duplication between help and readme

This slims down the readme so we don't duplicate information that's already in the help docs so it'll be easier to keep it up to date. It does look a bit small now, but I'm not sure what else to put in it.
@jhutchings1 what are your thoughts?

I'm now thinking we should include descriptions of the inputs parameters to each action and how to use them. I say this after looking at at other actions (e.g. https://github.com/actions/checkout and https://github.com/actions/upload-artifact) and noting that the help docs don't mention these inputs. What do people think?

I'm now thinking we should include descriptions of the inputs parameters to each action and how to use them. I say this after looking at at other actions (e.g. https://github.com/actions/checkout and https://github.com/actions/upload-artifact) and noting that the help docs don't mention these inputs. What do people think?

I think that's a good minbar for this action. We want to give people a basic understanding of the action here, but can point them at the help documentation for more context.

Sorry it took a long time, but I've updated this PR with what I think is a better balance between providing information and reducing duplication. The readme now contains information about the action inputs which should be enough for most people, and mentions the existance of the config file but points to the docs for all technical details.